Skip to content

Commit

Permalink
minor updates
Browse files Browse the repository at this point in the history
  • Loading branch information
tguild committed Sep 27, 2022
1 parent adcfce8 commit ed99c5d
Showing 1 changed file with 2 additions and 5 deletions.
7 changes: 2 additions & 5 deletions viss2-explainer.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,7 @@
Modern vehicles use hundreds of sensors which produce thousands of different data points, or signals, amounting to terabytes of data per vehicle per day.
There is no question vehicles are transforming, becoming connected, electric and autonomous all of which relies extensively on signals data.
To facilitate innovation and development on various use cases the W3C established a strategic alliance with COVESA and formed the Common Vehicle Interface
Initiative (CVII). At the center of this effort is a common data model for these vehicle signals, namely the Vehicle Signal Specification (VSS).
The W3C Automotive Working Group is creating the means to access this data in a standardized way with the Vehicle Information Service Specification (VISS).
The service can reside either in the vehicle, or in the cloud. Client applications can also reside in the vehicle, cloud or running on a nomad device
such as a smartphone.
Initiative (CVII). At the center of this effort is a common data model for these vehicle signals, namely the Vehicle Signal Specification ([VSS](https://covesa.github.io/vehicle_signal_specification/)) which has its own [explainer](https://www.covesa.global/sites/default/files/COVESA%20Vehicle%20Signal%20Specification_060122.pdf). The W3C Automotive Working Group is creating the means to access this data in a standardized way with the Vehicle Information Service Specification (VISS). The service can reside either in the vehicle, or in the cloud. Client applications can also reside in the vehicle, cloud or running on a nomad device such as a smartphone.


Vehicle signals, the definition and access to them, has historically been OEM proprietary. This has made it difficult for suppliers, commercial fleets,
Expand All @@ -27,7 +24,7 @@ General use for telematics - include EV, insurance, ...
The [W3C / COVESA CVII](https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interface+Initiative+-+Home) is broad in scope and VISS is an important
component, to address needs within the vehicle, cloud, AI/knowledge graph, service and solution level all centered on the common vehicle data model VSS.

VISS is a vital component in the realization of telematics use cases, such as fleet management, electric vehicle charging, driver behavior based
VISS is a vital component in the realization of telematics use cases, such as fleet management, electric vehicle charging, driver behavior and usage based
vehicle insurance, etc.
A standards based interface, and data model, supports interoperability between vehicle brands, and thus enables an open ecosystem where innovation of
new services can thrive.

0 comments on commit ed99c5d

Please sign in to comment.