Page History

...

• What parts of the projects were analysed and to what extent?
  • Motivation & problem spacespace 
    • VSS
      
      • Scope
      • Licenses
      • Applicable to different domains
    • Sensoris
    • CVIM
  • Data model & data characteristics
    • VSS
      
      • Encoding
      • Technologies
    • Sensoris
      • Encoding
      • Technologies
    • CVIM
    • ...
  • Contents
    
    • Specification
    • Tooling
    • Source code structure
  • Stakeholders
    • Current status
    • Roadmap
  • Metadata & policies (Unknown User (benjamin_klotz) , Benjamin has a special interest for metadata & policies of all existing projects)

...

The Vehicle Signal Specification proposal has been active since at least early 2016 when it originally outlined the intention to produce standard data descriptions among different car brands.

The first consideration, but as we can shall see not the only, consideration was that data signals on CAN networks tended to be completely proprietary and different among every car vendor.  The discussion of this may have led to the misunderstanding that VSS would stand or fall only on the condition of car OEMs being able to use the exact same CAN network standards, but this is not the case.   As we will see later, a standard like VSS is not only for the low-level network but also for other data exchange across cars, for cloud-based application, and for any place where development APIs need to be made common to increase third-party developer opportunities:

...

Please see draft in this document..

Table comparison (if applicable)

TBA.

Table comparison (if applicable)

TBA.

Think about if this still makes sense in the final structure

Stakeholders

Vehicle Signal Specification

...

Definition contributions from JLR, BMW, Volvo Cars (through W3C), Geotab.   Implementation in Kuksa project (Bosch – any other Tier 1s/2s?)

SensorIS

Bosch, ... look for the list.

Todo - Guru

TBA.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

There is good support for the ExVe standard which is demonstrated by market launch of ExVe compatible web services by several European OEMs already. European OEMs agreed to adopt the ExVe concept in 2016 which was followed by the finalisation and publication of the ISO standard in Q1, 2019.

Table comparison (if applicable)

Possible to clarify more?

CVIM

Mention original contributing companies.  No known extension / application of results howeverTBA.

Metadata & policies

...

What additional data is included in the data models?  E.g. connections to source sensor that made the measurement, usage of data, relationships between different parts.
(ontology work)

Policy - rules for how to connect different components?

Unknown User (benjamin_klotz) - please clarify what this means

Vehicle Signal Specification (Gunnar Andersson )

TBA.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

...

Table comparison (if applicable) (Unknown User (benjamin_klotz) To Be Confirmed)

TBA.

Conclusions

...

• We fulfilled purpose of document.  (which is ... comparison, finding commonality and drawing conclusions about which standards need to be considered)
• (VSS (or any common approach) is...) appropriate for aftermarket because of common standards so that innovative applications can be made.
• Conclusions about adoption.
• We have taken steps toward a common approach and ability to converge.

References

TBA.

Project Team

...