Options

These were the options that we discussed at day 1 of Sept 2019 f2f

VISS

Drop Gen2 + REST given IVI platform uncertainty and lack of interest from some in exposing full signals access to eg Android environment. Add VSS versioning in current VISS to support VSS2.0 and subsequent. Maybe take some features from Gen2 and additional ideas for a VISS2 but generally turn focus on other data taxonomies that VISS can accomodate and relevant to in-vehicle data services.

Gen2

Plug away at features drawing influences from ViWi and VISS as before.

Stalled since 'data model' terminology debate, resolved at previous f2f. Revitalize effort including call for editors, lobbying for resources from managers of involved organizations.

Split Group

Define use cases for recommendations for which (ViWi/RSI, VISS) goes where, in-vehicle telematics (data sampling), headless apps for eg v2i, in-vehicle infotainment, back end REST. Some have hesitation on Graph via ViWi, should consult W3C Graph Business Group that is forming out of Graph workshop.

The two groups could potentially collaborate on some data taxonomies in common.

VSS in ViWi

Continue to encourage the group to explore alternatives currently on the table and try to find additional alternatives.

Please add to the list. We need a further understanding of Laurent's sbranch for example.

remove depth limit

Take ViWi as Gen2 base with the notable exception of the depth limit as some feel it doesn't represent tree like structures nor Graph well, see Adnan and Daniel's assessment (subject to clarification of understanding from Patrick). Others note REST doesn't have such limitations.

Current ViWi versioning and rbranch may be helpful.

Pros:

Cons:

Alternate URI Paths

/service/resource/element && VSS path representing tree

Pros:

Cons: