- This is a draft of the report being created by the OMAuto Incubator Group at OMA. Feel free to edit this story if you have something of value to contribute.
If you want to add or delete an image on this page, download the file OMAuto Incubator Report Diagrams.Pptx PowerPoint deck and follow the instructions. If you don't have PowerPoint, follow these instructions:
...
6.1 W3C Automotive Web API (Sanjeev-owner; Alan-editor)
6.1.1 Overview and objective of project
The Automotive Working Group develops APIs to expose vehicle data and information from an automotive network bus(es) (eg. MOST and CAN). The specification is broken into two parts:
- Vehicle Information Specification containing durable, unchanging access methods for obtaining vehicle information;
- Vehicle Data Specification to specify agreed upon standardized data elements as well as the method for extending data elements to OEM specific elements.
var vehicle = new WebSocket("wss://wwwivi", "wvvss1.0");
Authorize
GET
SET
Subscribe
Unsubscribe
getVSS - helps provide only a subset of the information.
- can be controlled by vendor.
Request/Response mechanism over websockets
vehicle.send('{action' : 'subscribe', "path" :"body.mirrors.left", 'reqid' : "[some unique id] }");
Secure Web Socket
Connection Established
REQ : getVSS
RES : VSS File
REQ/RES : get/set/sub/unsub
onopen, onmessage, readyState
Demo
Prepare self-signed certificate
How does the client address IP based ns non-IP transports
6.1.2 API's defined
6.2 OMA GotAPI and DWAPI
...