Re: Kevron - Tizen Web API Specification

I should also add that the specification link draft is missing many of the
data properties Tizen will expose through it's web interface.  The IDL has
a more complete list:

http://otcshare.github.io/automotive-message-broker/docs/amb.idl

cheers,
Kevron


On Thu, Apr 25, 2013 at 5:35 PM, Cindy Lewis <cindy.lewis@me.com> wrote:

> Greetings!
>
> Although I did not attend Barcelona, I have read the IRC transcriptions. I
> have (at least) one question, and one minor typo in the specification.
>
> I support the idea of subteams to accelerate the work. If the first push
> is mainly to refine the existing API, could we begin to work on some of the
> app to app API needs? As someone pointed out "the group is very interested
> in reusing already defined APIs if possible and helping to fill in gaps if
> there are any."
>
> This is great news for cars yet to come off the assembly line, but I am
> hopeful we can set specifications for app developers to rely upon to build
> applications for cars already on the highway.
>
> One specification typo:
> Item 15
> The VehiclePowerMode<http://otcshare.github.io/automotive-message-broker/docs/vehicle_spec.html#idl-def-VehiclePowerMode> interface
> represents the current vehidle power mode.
> "Vehicle" is misspelled.
>
> Cheers!
> Cindy Lewis
>
> On Apr 22, 2013, at 9:33 AM, Rees, Kevron wrote:
>
> Attached is my presentation about the Tizen Vehicle Web API specification.
>  The status of the specification is work in progress.  The specification
> can be found here:
>
> http://otcshare.github.io/automotive-message-broker/docs/vehicle_spec.html
>
> <Web API presentation.pdf>
>
>
>