Versions Compared

Old Version 1

changes.mady.by.user Gunnar Andersson

Saved on

compared with

New Version Current

changes.mady.by.user Gunnar Andersson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add links to VISS specifications
Warning

This is a historical page.  As part of preparation work for the CCS project and the initial stages of working towards a unified approach to vehicle data, all related projects were surveyed and this was the "snapshot" view at the time.  By now these projects have progressed, and we have continued convergence and collaboration in this area.  For up to date status of the VISSv2 and other related projects in W3C and elsewhere, we recommend starting at the CVII initiative.


Links to readable specifications (from the README in the W3C Automotive & Transportation WG GitHub repository)

(warning)
Snapshot status (2019-06-24)

...

As part of the investigation of all relevant standards and technologies in the Vehicle Connected Services project, this is a brief summary of the current (2019-06-24) state of the W3C Automotive working group standard for Vehicle Services Interface specification  (formerly VISS), version 2.0.

The VISS version 1.0 is still in Candidate Recommendation status.   The version 2.0 specification is currently named Vehice Services Interface (VSI?).  Version 2 is currently being defined and often referred to inside group discussions simply as "Gen 2".

GENIVI Alliance participates actively in the W3C specification definition, in part through shared member companies, but also with GENIVI representatives (GENIVI & W3C have a collaboration agreement and GENIVI is set up as an official member of W3C).

Two-part Specification

The W3C specification is split into two parts: Core and Transport.   The Core specification "describes the VSI messaging layer" whereas the Transport specification includes the "mapping of the messaging layer to selected transports".

...

  • Status/error codes (following HTTP standards)
  • "The payload shall have JSON format."
  • Two protocols noted so far: HTTPS (the main driver for VISS v2) and "Secure Websockets" (like VISSv1)
  • Wildcards and Queries
  • The HTTPS chapter includes examples how to access data in the described data tree, such as:
GET VSS-Root/Car/Drivetrain/InternalCombustionEngine/RPM HTTP/1.1

  • ...and Wildcards:

/VSS-Root/Cabin/Door/*/*/IsLocked HTTP/1.1 

(warning) NOTE: Some discussions whether wildcards should be completely replaced by new Queries approach.


Note about current status:

...