...

• Agenda discussion - anything that needs to be added?
• Prioritized Topics:
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting notes  2023-06-

...

27

• Ulf presented the updated HIM repo (https://github.com/COVESA/hierarchical_information_model)
  • AP: Erik to check if doc can be generated

Meeting notes  2023-06-20

• No prioritized topics
• Please check Defining the COVESA data modeling strategy and its associated artifacts as it tries cover also other domains. Add comments/question in wiki
• Syntax checking (related to https://github.com/COVESA/vehicle_signal_specification/issues/599)
  

  Meeting notes:

  - Daniel: See https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts, would be better to have a standard format like RDF as source format.
  - Erik: So let tools use on RDF directly and generate other format from that?
  - Daniel; yes, still have *.vspec as experts but generated to RDF - let RDF be official format.
  - Fulup: Do not think people will parse from RDF directly, vspec->RDF->json seems complicated
  - Ulf: Keep YAml/vspec as single source of truth. It should be possible to generate RDF
  - Erik: Is a vspec2rdf tool all we need (short time)
  - Daniel: vspec2ttl already partially do it
  - Paul: Important to not slow down VSS progress
  - Fulup: Would love to have a tool that let my select which parts and get a normalized output with normalized quotes

  -Pierre: Isn’t RDF more restrictive in its syntax than YAML, which would make conversion from YAML to RDF somewhat difficult?
• We would likely have to put some restrictions into what can be represented in YAML so that it can be converted to RDF.
• Paul: A session with data guys would be helpful. RDF is well established
• Erik: Maybe would be good to agree on a long-term roadmap for VSS source format and tooling, what do we want the source format and tooling to look like in 5 years
• Paul: Will arrange a more in-depth session

Meeting notes  2023-06-13

• Welcome and Compliance statement

...