[Ovmsdev] Sharing Data Publicly - Public Charges

Christopher Cook christopher.cook at webprofusion.com
Thu Dec 12 13:45:44 HKT 2013

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.


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

More information about the OvmsDev mailing list