...
The "vehicle" object, represents an instance of the Vehicle Signal Server connection that can provide access to Vehicle Data through the W3C Information API. The supported methods are :
- Authorize - Authorize a client to access the Vehicle API (TLS)
- GET - Gets the value of a parameter, like body.mirrors.left
- SET - Sets the value for a parameter
- Subscribe - Subscribe to status changes
- Unsubscribe
- getVSS - helps provide only a subset of the informationget the JSON representation, to be used in GET/SET/SUBSCRIBE/UNSUBSCRIBE API.
The message format is JSON. The "Authorize" method helps the server to provide secure access to vehicle data based on Below is a simple flow diagram that explains the communication between W3C automotive clients and servers.
As the name implies, the W3C Vehicle Data Specification The getVSS API provides a JSON payload representation of the entire set of VSS attributes accessible to the client.
This can be controlled by the vendor.
The client is notified via standard websocket styled asynchronous callbacks about different events like
1 onopen
2. onmessage
that represents the vehicle information accessible to clients. The authorization mechanism helps implement role based access to vehicle data.
Given below is an example of how a web client would invoke a "Subscribe" request to the vehicle server.
This example, registers the client to be notified about changes to "body.mirrors.left" by the vehicle server. The client can process the changes via Javascript callbacks.
The W3C Automotive Business Group recently met at the Genivi AMM in San Franciso and showed their demo implementation of the above API. With less than 100 lines of Javascript, developers can easily integrate Vehicle data into their apps and services. Here's a screenshot of the demo.
Security is handled using TLS and the certificates need to be signed using a CSA.
6.1.2 API's defined
6.2 OMA GotAPI and DWAPI
...