AREA | SHORT NAME | DESCRIPTION | EXPECTATIONS | SUB-PROJECT DETAILS | STATUS (RESULTS) |
---|
CATALOG | Develop main Standard Data Catalog | Add and improve to the set of signals described in the VSS Standard tree of signals | Growing the list is fairly straight forward in theory. OEMs may have a challenge since their internal data models are often incompatible. Those who provide input early may get advantages. → VSS on GitHub
| VSS development project
Weekly calls: Tuesdays, 1930 CET. Chat on W3C slack server in #vss channel | - usable status but continuous improvement expected |
(META)MODEL | Define standard Data model Rule Set / meta-model | Take part in discussions to improving the VSS "meta-model", i.e. the rules for modelling data, a.k.a. the VSS way to describe data. - Is the limited set of datatypes provided by VSS enough - have we found the "sweet spot" between simplicity and expressiveness?
- Example: We recently added Array support
- Enums are still not perfectly defined, need some tweaking
| → VSS documentation on GitHub | VSS development project details above | - usable status but continuous improvement expected |
ALIGNMENT | Align with SENSORIS | - Organizational agreement/alignment
- Understand intended scope of project
- Technical comparison of model/rule set
- Technical comparison of data items (catalog)
- Set plan for how the content plays a part in one-or-several standard catalogs
| All companies that are involved in SENSORiS development are expected to have their representatives join into this discussion to drive towards the common goal. | Separate continuation meeting needs to be booked | CVII introduction made
Short analysis was also performed. (recorded slide presentation) |
ALIGNMENT | Align with JASPAR | same as described for SENSORIS | All companies that are involved in JASPAR development are expected to have their representatives join into this discussion to drive towards the common goal. | Separate startup meeting needs to be booked | Short analysis was performed. (recorded slide presentation)
Alignment discussions not yet started. |
ALIGNMENT | Align with ISO Extended Vehicle | - Discuss if data definitions are within scope for ExVe specifications
- See if a standard model like VSS shall be referenced
|
| Separate startup meeting needs to be booked | Contacts established. Meeting pending |
TECHNOLOGY STACK
| VSS to AUTOSAR translator | Develop translators from VSS data description to AUTOSAR technology. Specifically: A translator with VSS as input, AUTOSAR-XML as output. | There is already an indirect way by doing VSS→Franca IDL (WIP) and then using Franca IDL → AUTOSAR XML converter, but this should aim to develop a direct converter. The vss-tools repository can host such translators (but companies are free to provide their own public repository). | vss-tools are discussed in: VSS development project details above
| Not started |
TECHNOLOGY STACK | VISS v2 | Complete the development of Vehicle Information Service Specification (The Web protocol for VSS data). |
| W3C Automotive Working Group
Weekly calls: Tuesdays 1300 EST. Chat on W3C slack server in #gen2 channel | Ongoing, relatively complete. Approaching usable state. |
TECHNOLOGY STACK | Other alternatives for data transfer protocol | Companies may prefer/propose other protocols and data transfer methods if there is a clear need for them – remember to avoid fragmentation. - In GENIVI CCS project we have had some early look at Apache NiFi and related technologies
- VSS to MQTT mapping - there is a brief high-level analysis done
- GraphQL has been demonstrated in both CCS and Android Automotive SIG (VHAL) projects.
- WAMP has been discussed as one possible solution for W3C "RPC" (working name) protocol
- ...other?
|
| GENIVI CCS Project project could be used for this
| ![(question)](/s/ypeau5/8804/xgjkrn/_/images/icons/emoticons/help_16.svg) |
ALIGNMENT | VSS in AUTOSAR | Promote the use of VSS data model within AUTOSAR |
| TODO | Need to start shared conversations |
|
|
|
|
|
|