Re: Divorcing the data from the Access API

Are you referring to the W3C Vehicle API Creation Guidelines?

http://lists.w3.org/Archives/Public/public-autowebplatform/2014Feb/att-0023/W3C_Vehicle_API_Creation_Guidelines_v4.docx

Paul J. Boyes
--------------------------------
Mobile:   206-276-9675
Skype:  pauljboyes




On Apr 29, 2014, at 5:03 PM, Lucinda Lewis <cindy.lewis@me.com> wrote:

Hi there,

Didn't Tina mention there was more detail in another document? If you could point me at the earlier draft, I will revise it.

Thanks,
Cindy


On Apr 29, 2014, at 6:57 PM, Rees, Kevron wrote:

On Tue, Apr 29, 2014 at 2:24 PM, Paul Boyes <pb@opencar.com> wrote:
Kevron,

The normative use cases should probably go with the vehicle_spec.html


Good catch.  Correction made.


Paul J. Boyes
--------------------------------
Mobile:   206-276-9675
Skype:  pauljboyes




On Apr 29, 2014, at 11:32 AM, Rees, Kevron <kevron.m.rees@intel.com> wrote:

I forgot to include live links to my proposed changes:

http://rawgit.com/tripzero/automotive-bg/master/vehicle_spec.html
http://rawgit.com/tripzero/automotive-bg/master/data_spec.html

On Tue, Apr 29, 2014 at 11:31 AM, Rees, Kevron <kevron.m.rees@intel.com>
wrote:

https://github.com/w3c/automotive-bg/pull/28

I've got the first merge that separates the data from the main access
APIs.  We discusses modularizing the specification in the last face to
face meeting in Santa Clara.

I probably don't have the abstract correct for the vehicle data
specification, so any help there would be appreciated.

Any other comments welcome.

Kevron