W3C home > Mailing lists > Public > public-review-announce@w3.org > October 2016

FPWD: Vehicle Signal Server Specification

From: Notifier <notifier@aries.w3.org>
Date: Thu, 20 Oct 2016 14:59:01 +0000
Vehicle Signal Server Specification

https://www.w3.org/TR/2016/WD-vehicle-information-service-20161020/

Abstract


The W3C Vehicle Signal Server Specification defines a WebSocket based API that enables client applications to GET, SET, SUBSCRIBE and UNSUBSCRIBE to vehicle signals and data attributes.

The purpose of the specification is to promote a Server API that enables application development in a consistent manner across participating automotive manufacturers.

It is recommended that this Vehicle Signal Server Specification (VSSS) is read in conjunction with the W3C Vehicle Signal Client Specification (VSCS) and the GENIVI Vehicle Signal Specification (VSS).

The Vehicle Signal Client Specification defines an API that wraps the data access and security primitives defined in this Server Specification. It has been defined to support the development of &#x27;standards-compliant&#x27; JavaScript libraries that can be used by web based clients.

It is assumed that native clients (written for example in C/C++) and managed runtime clients (written in languages like Java or C#) invoke the WebSocket Server API using standard WebSocket libraries that have been created specifically for those languages.

The GENIVI Vehicle Signal Specification (VSS) defines the set of vehicle signals and data that are exposed via this Server Specification. The term &#x27;signal&#x27; is used here to represent an item of data that can vary over time, for example vehicle speed, whilst the term &#x27;static data&#x27; is used to denote a temporally unchanging property like vehicle width.

This Server Specification describes a discovery mechanism that defines the set of signals and data that a particular client can access at a particular point in time. It is recognized that some automobile manufacturers may expose more signals and data than others. The Vehicle Signal Specification supports both extensibility and the ability to define private branches.

In addition, the &#x27;tree&#x27; of signals that is accessible at any point in time may also vary depending on standard access control principles. That is, it can vary based on the identity of the user (person or organisation) requesting the data and/or the device (e.g. vehicle) where the request originates.

To support this, the Server Specification describes a token based mechanism that can optionally be used to pass tokens to the WebSocket Server to represent the user of an application and the device that the application is running on.

The target platform supported by the specification is exclusively passenger vehicles. Use of this specification for non-passenger applications (for example heavy machinery, marine and airline infotainment) is not prohibited, but is not covered in the design or content of the API and therefore may be insufficient.

An example use case could be the implementation of a &#x27;Home Mechanic&#x27; application that provides warnings if any the following need attention: tire pressure, engine oil level, washer fluid level and battery charge level. Future use case innovations in transportation, safety, navigation, smart energy grids, smart transportation, consumer infotainment and personalisation are all possible through this specification.

Web developers building interoperable applications based upon this API, will help empower a common web platform across consumer devices and passenger vehicles within the Web of Things.

Status of the Document


This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This document was published by the Automotive Working Group as a First Public Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-automotive@w3.org (subscribe, archives). All comments are welcome.

Publication as a First Public Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 1 September 2015 W3C Process Document.
Received on Thursday, 20 October 2016 14:59:04 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 20 October 2016 14:59:05 UTC