No subject
Fri Sep 27 23:39:33 HKT 2013
I guess, for each station:
> a) An indication of when someone last charged successfully
> b) A 'star' style rating system to tell me how reliable it is
> c) Pictures
> d) Instructions
> e) Comments
I think OVMS can help with (a) and (b) primarily.
Regards, Mark.
On 12 Dec, 2013, at 1:45 pm, Christopher Cook
<christopher.cook at webprofusion.com> wrote:
> Hi Mark,
>
> 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.
>
> 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.
>
> 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.
>
> 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.
>
> 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.
>
> Cheers,
> Chris
_______________________________________________ OvmsDev mailing list
OvmsDev at lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
--B_3469690362_103871052
Content-type: text/html;
charset="US-ASCII"
Content-transfer-encoding: quoted-printable
<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -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 t=
he raw data and let the charge map vendors figure out how to best present th=
e information to users.</div><div><br></div><div> Tom</div><div>=
<br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-family:Calibri; f=
ont-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BOR=
DER-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=3D"font-weight:bold">From: </span> Mark Webb-Johnson <<a=
href=3D"mailto:mark at webb-johnson.net">mark at webb-johnson.net</a>><br><span =
style=3D"font-weight:bold">Reply-To: </span> OVMS Developers <<a href=3D"mail=
to:ovmsdev at lists.teslaclub.hk">ovmsdev at lists.teslaclub.hk</a>><br><span s=
tyle=3D"font-weight:bold">Date: </span> Wednesday, December 11, 2013 at 9:54 P=
M<br><span style=3D"font-weight:bold">To: </span> Christopher Cook <<a href=
=3D"mailto:christopher.cook at webprofusion.com">christopher.cook at webprofusion.co=
m</a>><br><span style=3D"font-weight:bold">Cc: </span> OVMS Developers <=
<a href=3D"mailto:ovmsdev at lists.teslaclub.hk">ovmsdev at lists.teslaclub.hk</a>&g=
t;<br><span style=3D"font-weight:bold">Subject: </span> Re: [Ovmsdev] Sharing =
Data Publicly - Public Charges<br></div><div><br></div><div><meta http-equiv=
=3D"Content-Type" content=3D"text/html charset=3Diso-8859-1"><div style=3D"word-wrap=
: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-spac=
e;">Chris,<div><br></div><div>From a user point of view, what do we need?</d=
iv><div><br></div><div>I guess, for each station:</div><div><br></div><div><=
blockquote style=3D"margin: 0 0 0 40px; border: none; padding: 0px;"><div>a) A=
n 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</di=
v><div>d) Instructions</div><div>e) Comments</div></blockquote></div><div><b=
r></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=3D"mailto:christopher.cook at webprofusion.com">=
christopher.cook at webprofusion.com</a>> wrote:</div><br class=3D"Apple-inter=
change-newline"><blockquote type=3D"cite"><div fpstyle=3D"1" ocsi=3D"0" style=3D"fon=
t-family: Helvetica; font-size: 24px; font-style: normal; font-variant: norm=
al; font-weight: normal; letter-spacing: normal; line-height: normal; orphan=
s: auto; text-align: start; text-indent: 0px; text-transform: none; white-sp=
ace: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px=
;"><div style=3D"direction: ltr; font-family: Tahoma; font-size: 10pt;"><div c=
lass=3D"moz-text-flowed" lang=3D"x-western" style=3D"font-family: -moz-fixed; font=
-size: 14px;">Hi Mark,<span class=3D"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 inter=
ested in aggregated summaries instead - basically high level info that's use=
ful from a user perspective. While OCM is indeed focused on charging locatio=
n information we also need to help users by identifying quality/usage inform=
ation (good and bad) with locations which is where comments/checkins comes i=
n. We augment that with photos to allow users to illustrate stuff about the =
location.<span class=3D"Apple-converted-space"> </span><br><br>Ideally if=
you could look-up OCM to confirm the (OCM Reference ID) identity of a charg=
ing location with the user at the time (choosing from nearest known location=
s?), then store that, which would help us then pull/associate data relevant =
to OCM later.<span class=3D"Apple-converted-space"> </span><br><br>Ideall=
y for us verbatim commentary would go to OCM as a normal comment/checkin sub=
mission - we could provide standard URL format for full comment/photo submis=
sions etc via mobile browser - the user would then need to sign in to OCM no=
rmally. 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.<s=
pan class=3D"Apple-converted-space"> </span><br><br>My own view of data l=
icensing is that its a necessary evil, one I don't have a huge amount of int=
erest in - I'd rather defer that to experts. Privacy is my main concern, inf=
ringing other peoples data license is obviously undesirable too, to varying =
degrees. People can get very upset about licensing, very quickly.<span class=
=3D"Apple-converted-space"> </span><br><br>I say go for it, make sure use=
rs know what information will become public, and please provide an HTTP API =
for querying the (shared, public) stats for later aggregation by OCM.<span c=
lass=3D"Apple-converted-space"> </span><br><br>Cheers,<span class=3D"Apple-=
converted-space"> </span><br>Chris</div></div></div></blockquote></div>=
<br></div></div></div>_______________________________________________
OvmsDev mailing list
<a href=3D"mailto:OvmsDev at lists.teslaclub.hk">OvmsDev at lists.teslaclub.hk</a>
<a href=3D"http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.t=
eslaclub.hk/mailman/listinfo/ovmsdev</a>
</span></body></html>
--B_3469690362_103871052--
More information about the OvmsDev
mailing list