[Ovmsdev] Sharing Data Publicly - Public Charges

Tom Saxton tom at idleloop.com
Fri Dec 13 02:52:31 HKT 2013

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.


From:  Mark Webb-Johnson <mark at webb-johnson.net>
Reply-To:  OVMS Developers <ovmsdev at lists.teslaclub.hk>
Date:  Wednesday, December 11, 2013 at 9:54 PM
To:  Christopher Cook <christopher.cook at webprofusion.com>
Cc:  OVMS Developers <ovmsdev at lists.teslaclub.hk>
Subject:  Re: [Ovmsdev] Sharing Data Publicly - Public Charges


>From a user point of view, what do we need?

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20131212/38264bd8/attachment.htm>

More information about the OvmsDev mailing list