Proposals and description of concrete work activities to meet the goals of CVII, and the (sub)-project organization for each individual topic.
Virtual All Member Meeting 2020 - Slides and Recordings can be found here.
Community slide deck can be found on the parent page.
Table of Contents
Completed to a usable state - in many cases still ongoing for further improvement (continuous improvement)
Notice of blocker/issue. Improvement necessary
Notice of serious problem or to indicate a cancelled activity.
Ongoing and no major problems are anticipated
Early stages and no major problem anticipated
Not started, but no problem anticipated
To be defined
Topic overview
(a more detailed version follows below)
General
AREA | SHORT NAME | SUB-PROJECT DETAILS |
---|---|---|
INFORMATION / MARKETING / DISSEMINATION | All-hands information & sync. meeting | TBD |
HIGH-LEVEL ORGANIZATION | Steering committee (?) | TBD |
INFORMATION / MARKETING / DISSEMINATION | Informational webinars |
Additional - please propose. |
ALIGNMENT | Company-specific alignments (see details below) | Need individual one-on-one between GENIVI-W3C and companies |
HIGH-LEVEL ORGANIZATION | (NEW) Which other companies (e.g. OEM, Tier1, or other) and Organizations should we talk to, according to you? (E.g. Which others are you already working with, or comfortable to collaborate with in this area?) | |
(META)MODEL | Specify relationship and cooperation between VSC and VSS models | Currently discussed in two separate meetings: VSS & VSSo development project W3C "RPC" meeting (note, no separate meeting for the VSC exists at this time. Both VSC and protocol are developed in the "RPC" meeting as a start) |
Vehicle Data
AREA | SHORT NAME | SUB-PROJECT |
---|---|---|
CATALOG | Develop main Standard Data Catalog | VSS & VSSo development project |
(META)MODEL | Define standard Data model Rule Set / meta-model | VSS & VSSo development project |
(META)MODEL | Specify relationship and cooperation between VSC and VSS models e.g: VSC can refer to VSS signal definitions VSS has limited datatype expressiveness –> recommend use of VSC for arbitrarily complex data structures. | VSS & VSSo development project W3C "RPC" meeting |
ALIGNMENT | Align with SENSORIS | |
ALIGNMENT | Align with JASPAR | |
ALIGNMENT | Align with ISO Extended Vehicle | |
ALIGNMENT | other orgs. VDA? ASAM? MONET? ... ISO smart city, ISO intelligent transport systems, ISO open geospatial consortium, | |
TECHNOLOGY STACK | VSS to AUTOSAR translator | CVII Technology Stack track Weekly calls: Wednesday 8 AM PST, 11 AM EST, 1700 CET. |
TECHNOLOGY STACK | VISS v2 | W3C Automotive Working Group Weekly calls: Tuesdays 11 AM PST, 1 PM EST, 20:00 CET. |
TECHNOLOGY STACK | Other alternatives for data transfer protocol | GENIVI CCS Project |
ALIGNMENT | VSS in AUTOSAR | TODO |
ALIGNMENT | Company-specific alignments (see details below) | Need individual one-on-one between GENIVI-W3C and companies |
Vehicle Services (a.k.a. Function Interfaces, a.k.a. APIs)
AREA | Short Name | Sub-project org.
|
---|---|---|
(META)MODEL | Define standard Data model Rule Set / meta-model | W3C "RPC" meeting |
CATALOG | Develop main Standard Service Catalog | W3C "RPC" meeting |
TECHNOLOGY STACK (Development) | Define "remote procedure call" web protocol(s) | W3C "RPC" meeting |
TECHNOLOGY STACK (Analysis) | Define in-vehicle standards for service/procedure invocation. | Set up a general Technology-Stack meeting series? |
TECHNOLOGY STACK (Development) | Develop code library X | TBD |
TECHNOLOGY STACK (Development) | Develop translator Y | TBD |
Detailed view:
Expand the following view to see the detailed matrix:
General Questions
- Which topic in the matrix will you provide resources to?
- Which topics are still missing?
- Are the already existing proposed (sub) projects appropriate for you?
- Is there any hindrance for you to participate in those existing proposed projects (GENIVI, W3C participation)
- Which (new) sub-project meeting will your company start and lead?
- Which parts (sub-trees in the hierarchy) of the standard data / services catalog will you provide input to?
- Which technologies would you like to propose in the "agreed-upon" technology stack?
- How can we start discussing your internal structure (organizational/technical) to understand how the CVII best supports it?
- E.g.: Which standards do you use today?
- Where is it realistic to introduce the new standards?
- Where (in your particular system) shall there be translation between legacy/proprietary and the new standards?
- Will your company further support the development of these types of activities by joining GENIVI and/or W3C?
Partial Reply RB GmbH (Bosch)
Which topic in the matrix will you provide resources to?
CATALOG Develop main Standard Data Catalog (META)MODEL Define standard Data model Rule Set / meta-model ALIGNMENT Align with SENSORIS - Which topics are still missing?
- Not completely "missing", but "Services/RPC" are an important point, Currently (VSC) almost nothing, and not clear how it will "tie into" VSS without reinventing the wheel
- Gunnar: Good point. There are already discussions (in VSS call and RPC/VSC meeting) and some proposed strategy for this. But I think it's important enough to add, so I created a line in the table.
- In terms of ARA:: Com there are two perfectly matching mechanisms => Events and Methods => IMHO VSS is the perfect base for that discussion
- Gunnar: +1. To each company: please help us identify who (involved in AUTOSAR) can be part of driving that discussion.
- Kind of reference implementation (partly covered by kuksa.val) but whole stack is missing
- Gunnar: The key is to identify which parts are promoted as either "reference" or simply "good" implementation of each technology. What already exists vs. what is missing from a complete stack ought to be described (use a diagram), and then broken down into development project for the missing parts.
- Would a CVI Dev Kit help?
- Gunnar: One way we often do this is develop the components, then produce a demo that integrates them all. The demo should be placed in a combined repository (using appropriate technology such as references/git-submodules etc.)
- But if we can create a "dev kit" (with components, and documentations for how to integrate them) this is even more flexible.
- Not completely "missing", but "Services/RPC" are an important point, Currently (VSC) almost nothing, and not clear how it will "tie into" VSS without reinventing the wheel
- Are the already existing proposed (sub) projects appropriate for you?
- VSS & VSSo development project, W3C VISSv2
- Working on VSS standard
- Working on, invite participation in C++ kuksa.val VISS server https://github.com/eclipse/kuksa.val , hopefully VISSv2 in future
- Is there any hindrance for you to participate in those existing proposed projects (GENIVI, W3C participation)
- not a W3C member yet
- VSS & VSSo development project, W3C VISSv2
- Which technologies would you like to propose in the "agreed-upon" technology stack?
- a more "binary" representation of requests in transport protocols instead of JSON (e.g CBOR, protobuf...)
- Gunnar: +1. This is a clear technology stack subproject.
- best practice how to extend/widen/leverage VSS data model to a fully semantic digital twin for knowledge engineering in backend
- DDS, MQTT, D-BUS, DAPR.IO, ...
- Gunnar: Indeed these are additional useful technologies. Other stakeholders may also give their view on priorities.
- a more "binary" representation of requests in transport protocols instead of JSON (e.g CBOR, protobuf...)
[ ] Ted Guild Can you help out to link to W3C meeting information. In particular I could only write "bi-weekly" but that does not specify exactly when. A link to wiki or mailing list where invites are sent, will help.
Comments
- Scope does not include to define who has access data
- Might be impacted by work by The Automotive Alliance?