<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div>I think the details of how (b) is determined is the opportunity for innovation. OVMS should just supply the raw data and let the charge map vendors figure out how to best present the information to users.</div><div><br></div><div> Tom</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net">mark@webb-johnson.net</a>><br><span style="font-weight:bold">Reply-To: </span> OVMS Developers <<a href="mailto:ovmsdev@lists.teslaclub.hk">ovmsdev@lists.teslaclub.hk</a>><br><span style="font-weight:bold">Date: </span> Wednesday, December 11, 2013 at 9:54 PM<br><span style="font-weight:bold">To: </span> Christopher Cook <<a href="mailto:christopher.cook@webprofusion.com">christopher.cook@webprofusion.com</a>><br><span style="font-weight:bold">Cc: </span> OVMS Developers <<a href="mailto:ovmsdev@lists.teslaclub.hk">ovmsdev@lists.teslaclub.hk</a>><br><span style="font-weight:bold">Subject: </span> Re: [Ovmsdev] Sharing Data Publicly - Public Charges<br></div><div><br></div><div><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Chris,<div><br></div><div>From a user point of view, what do we need?</div><div><br></div><div>I guess, for each station:</div><div><br></div><div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>a) An indication of when someone last charged successfully</div><div>b) A 'star' style rating system to tell me how reliable it is</div><div>c) Pictures</div><div>d) Instructions</div><div>e) Comments</div></blockquote></div><div><br></div><div>I think OVMS can help with (a) and (b) primarily.</div><div><br></div><div>Regards, Mark.</div><div><br><div><div>On 12 Dec, 2013, at 1:45 pm, Christopher Cook <<a href="mailto:christopher.cook@webprofusion.com">christopher.cook@webprofusion.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div fpstyle="1" ocsi="0" style="font-family: Helvetica; font-size: 24px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;"><div class="moz-text-flowed" lang="x-western" style="font-family: -moz-fixed; font-size: 14px;">Hi Mark,<span class="Apple-converted-space"> </span><br><br>From my personal point of view this all sounds good, OCM is probably not the best place to store very fine-grained charging stats and is mostly interested in aggregated summaries instead - basically high level info that's useful from a user perspective. While OCM is indeed focused on charging location information we also need to help users by identifying quality/usage information (good and bad) with locations which is where comments/checkins comes in. We augment that with photos to allow users to illustrate stuff about the location.<span class="Apple-converted-space"> </span><br><br>Ideally if you could look-up OCM to confirm the (OCM Reference ID) identity of a charging location with the user at the time (choosing from nearest known locations?), then store that, which would help us then pull/associate data relevant to OCM later.<span class="Apple-converted-space"> </span><br><br>Ideally for us verbatim commentary would go to OCM as a normal comment/checkin submission - we could provide standard URL format for full comment/photo submissions etc via mobile browser - the user would then need to sign in to OCM normally. Obviously thats up to you but probably the simplest integration. We don't want to hold information of charging locations at private residences (someone's home) as the data protection/privacy issues are too complicated.<span class="Apple-converted-space"> </span><br><br>My own view of data licensing is that its a necessary evil, one I don't have a huge amount of interest in - I'd rather defer that to experts. Privacy is my main concern, infringing other peoples data license is obviously undesirable too, to varying degrees. People can get very upset about licensing, very quickly.<span class="Apple-converted-space"> </span><br><br>I say go for it, make sure users know what information will become public, and please provide an HTTP API for querying the (shared, public) stats for later aggregation by OCM.<span class="Apple-converted-space"> </span><br><br>Cheers,<span class="Apple-converted-space"> </span><br>Chris</div></div></div></blockquote></div><br></div></div></div>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</span></body></html>