Page History

...

• Agenda discussion - anything that needs to be added?
• Prioritized topics
  • "Ulf/HIM proposal" (Hierarchical Information Model)

1. Decide on name for the evolved data model.
2. Create a new COVESA Github repo based on the new name.
3. Decide on a directory structure that can accommodate rule set definitions for multiple domains and multiple information types.
4. Create a rudimentary README on the top level giving a high level description of the new data model.
5. Move the VSS "rules definition" (the documentation) from the VSS repo to an appropriate directory on this new repo.
6. Create a rule set for services that that meets the requirements from the "passenger car domain" (VSS).
7. On the VSS repo, create an initial service tree based on the rule set from the bullet above. Continue to evolve it in parallell with the existing VSS tree.
8. Analyze the impact on VSS-Tools that the above has, take action on the insights from that.
9. Try to influence the W3C automotive group to evolve VISSv2 to support the new data model.
10. If successful on the above bullet, create a new COVESA project that will develop a POC containing a technology stack based on the evolved W3C interface and COVESA data model.

• • • Discussion:
      • Ulf: Could be soft started as VSS subproject
      • Ulf: Do not see HIM file as input to vss-tools, it is the server that consumes it, it still work with initial trees
      • Erik: Suggestion:
        • Let Paul create a HIM repo (M/W/X)
        • Ulf to start working with repo, describe motivation, idea, and suggested increments/roadmap and basic architecture
          • Describe what problem we intend to solve, why do we create it.
        • Then let DEG discuss at regular interval, keep VSS meeting informed
        • When mature we can discuss how to involve more people
      • Decision: OK for Paul to create repo
      • Discuss relationship to VCS when we have the parts above ready
  • Adnan: SDV and Eclipse
• Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
• Prioritized topics for next meeting
• Date for next monthly report discussion

...