Wotcher TAG!

I'm requesting a TAG review of VISS 2 specifications.

[One paragraph summary of idea, ideally copy-pasted from Explainer introduction]

VISS is specifying a means to access vehicle signals data in a standardized way. The Data model is defined in another specification (VSS, jointly developed by W3C and COVESA).

• Explainer¹ (minimally containing user needs and example code): https://github.com/w3c/automotive/blob/gh-pages/viss2-explainer.md

• Specification URL: https://www.w3.org/TR/viss2-core/ and https://www.w3.org/TR/viss2-transport/

• Tests: [wpt folder(s), if available] None

• User research: [url to public summary/results of research] N/A

• Security and Privacy self-review²: The scope of this specification is narrow and does not describe a specific data model (VSS does describe such a model). That makes it rather difficult to analyze the privacy risks (in particular identify the information that could be particularly sensitive, although PII is not the core of data like what VSS describes). The WG and CG have also worked on best practices (https://www.w3.org/community/autowebplatform/wiki/Best_Practices). VISS 2 has improved on security and privacy thanks to the access control features of the protocol (see https://www.w3.org/TR/viss2-core/#access-control-model). The WG has also started studying other privacy-improving techniques like geofencing but it is clearly out-of-scope for these specifications.

• GitHub repo (if you prefer feedback filed there): https://github.com/w3c/automotive

• Primary contacts (and their relationship to the specification):

  • Carine Bournez (caribouW3), W3C staff
  • Ted Guild (tguild), Geotab, WG Chair

• Organization(s)/project(s) driving the specification: W3C Automotive WG, COVESA

• Key pieces of existing multi-stakeholder review or discussion of this specification:

• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: [please provide]
• The group where the work on this specification is currently being done:
• The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue):
• Major unresolved issues with or opposition to this specification:
• This work is being funded by:

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback