...
Meeting notes 2024-05-13
- Intro: Names, company, contribution?
- Prioritized Topics:
- Roadmap creation
- New features for the next VISS version
- VISS tied to VSS and passenger vehicles. As there is a need for additional information models, maybe adapt for Hierarchical Information Model (HIM) proposal
- ATA TMC (several attendees from their Data Science team in attendance) express interest in additional data models
- Question on how to accommodate VSS within HIM, explained as a higher level wrapper and backwards compliant
- Similar rules to be applied to the other data models
- Resistance to extend VSS beyond vehicle signals
- Wally: either HIM, VSS overlays or perhaps a third approach could work for ATA needs
- Suggest we define what we want the model to support to evaluate
- Stephen: first goal is semantics side - metadata
- Diagnostics capabilities, trailer or specialty equipment are the data models being discussed
- Peter: there are existing services work within COVESA that need alignment with this
- Ulf: we may end up with merging of ideas or competition and see which prevails
- OpenAPI approach wasn't conducive to automotive purposes, hence VISS
- Define payload that can be transported across multiple protocols, could possibly support OpenAPI (would need to add subscriptions)
- Suggest we solicit input from AutoSAR (Erik) and BMW on Android (Adnan or Andre)
- Meeting split between VISS (specification) and VISSR (Reference implementation of VISS)
- Informational update on VISSR on regular call, deep technical as time allows or call participant warrants otherwise details will be on slack & github
- Also welcome questions from participants, can inform the specification work as well
- Tagged releases
- VISSR branching/release strategy for next VISS version
- Policy notes .reviewed Please
- Reminder to please add company name in your display name.
Intro: Names, company, contribution? - CVIS Charter
{"serverDuration": 115, "requestCorrelationId": "055878e602c8efc9"}