From ed99c5de9d12ac3badab43ba1d3039c71ac85f20 Mon Sep 17 00:00:00 2001 From: tguild Date: Tue, 27 Sep 2022 12:49:21 -0400 Subject: [PATCH] minor updates --- viss2-explainer.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/viss2-explainer.md b/viss2-explainer.md index 3bb4b9a..a72a0ee 100644 --- a/viss2-explainer.md +++ b/viss2-explainer.md @@ -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, @@ -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.