No subject

Fri Sep 27 23:39:33 HKT 2013

e best place to store very fine-grained charging stats and is mostly intere=
sted in aggregated summaries instead - basically high level info that's use=
ful from a user perspective. While OCM is indeed focused on charging locati=
on information we also need to help users by identifying quality/usage info=
rmation (good and bad) with locations which is where comments/checkins come=
s in. We augment that with photos to allow users to illustrate stuff about =
the location.

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 kn=
own locations?), then store that, which would help us then pull/associate d=
ata relevant to OCM later.

Ideally for us verbatim commentary would go to OCM as a normal comment/chec=
kin submission - we could provide standard URL format for full comment/phot=
o 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 integr=
ation. We don't want to hold information of charging locations at private r=
esidences (someone's home) as the data protection/privacy issues are too co=

My own view of data licensing is that its a necessary evil, one I don't hav=
e 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 unde=
sirable too, to varying degrees. People can get very upset about licensing,=
 very quickly.

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.


Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
<script id=3D"tinyhippos-injected">if ( {
le("bootstrap").inject(window, document); }</script><script id=3D"tinyhippo=
s-injected">if ( {"bootstrap").inject(=
window, document); }</script><style type=3D"text/css" id=3D"owaParaStyle"><=
<body fpstyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
<div class=3D"moz-text-flowed" style=3D"font-family: -moz-fixed; font-size:=
 14px;" lang=3D"x-western">
Hi Mark, <br>

More information about the OvmsDev mailing list