...

• 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
• Discussions VSS
• Discussions VSS-tools
• Prioritized topics for next meeting

Meeting notes 2025-05-06

• AMM Next week
  
  • No VSS meeting next week (May 13th)
  • DEG cancelled next week
  • Possibly others as well
  • If you have sessions to the AMM please upload them to drive on link provided by Paul
• ACEA 42
  • Sebastian may want to update https://github.com/COVESA/vehicle_signal_specification/issues/180
  • To be answered
    • Does VSS fulfil more signals now
    • Is the list still the same?
  • Stefan: We have tried to do  a mapping
  • https://docs.google.com/spreadsheets/d/1Np9uLvwEESZ09dMcXoSvoyoyj5L_Le0k/edit?gid=1250108163#gid=1250108163
    • ACEA not mentioned
  • EU Data Act Project#March26,2025Agenda
• Data Arch Team
  • Stephen: Ai Semantic Reasoning, can define rules in knowledge layer, there will be a session at the AMM

Meeting notes 2025-04-22

• Capabilities
  • Paul to have PR ready next week.
• AMM:
  • Paul: Does anyone have any questions?

Meeting notes 2025-04-15

• Capabilities
  • Paul presented work on seating, will create a pull request

Meeting notes 2025-04-08

• AMM
  
  • Erik presented intended content for VSS Working Sessions, see Weekly Agenda and Meeting Notes
  • (Additional) catalog trees as potential extra topic, possibly better discussed at a later AMM
  • Ulf could possibly present something on related work CVI.

Meeting notes 2025-04-01

• Information/Discussion: EU Battery pass and VSS relationship
  • https://thebatterypass.eu/
  • https://www.dinmedia.de/en/technical-rule/din-dke-spec-99100/385692321
  • Created https://github.com/COVESA/vehicle_signal_specification/issues/818 for tracking
  • Sunil: Euro7 - data shall be available though the OBD port
  • Stefan: Could be relevant for VSS use cases. Not all aspects detailed out
  • Sunil: We have done some research
  • Erik: We need to discuss if there are any use-cases related to VSS, if anyone wants to use VSS to handle this
  • Daniel: Support for mapping to battery passport would be good, but we should not maintain the data
  • D: We could check that the Passport data structure would fit in VSS, if needed. Could serve as input to profiles
  • Sunil: Mostly static data
  • Sunil: What is relationship to data act
  • Stefan: Data act focus on personal data
  • Sebastian: No tooling provided by them
  • Erik: Please comment in the issue 818 if you are interested to do something related to battery pass in VSS/COVESA
  • Daniel: Possible tooling "battery spec to VSS"
  • https://github.com/batterypass/BatteryPassDataModel
• Modelling Language
  • Daniel: Feel free to add possible modelling languages at Vehicle Data Model Requirements and Proposed Solutions
  • Paul can give access if you do not have write access

Meeting notes 2025-03-25

• Profiles
  • Location - description in vss or vss-tools?
  • Sebastian Schildt:
    • Thinks vss is a good place, could be a new section on top level
    • Fits into overlay, but possibly rename
  • Erik: Overlay is a mechanism to realize profiles
  • S: Overlay are for two purposes, one is to compose models, one is to add additional attributes
  • Paul: Profiles are extensions that some members agree on.
  • Daniel: VSS_project offer model language and tooling as one artifact, then also catalog as artifact. We need to include this also in model.
  • Sebastian: Profiles are now mostly handled as examples, not really model or catalog.
  • Daniel: Checks should better be done by vss-tools
  • Erik: Please review https://github.com/COVESA/vss-tools/pull/445, continued discussion next week.
• Commercial Vehicle Profiles
• Capability-dicussions in COVESA
  • Daniel: What is status
  • Paul: Discussion on seating ongoing, tables on wiki, Capabilities Project - Seating Capabilities
  • D: How will COVESA formalize it?
  • E: Changing VSS catalog is easy, maybe more important to discuss what model changes that better would be needed. To be discussed at the AMM.
  • P: Ongoing discussion in IFEX project
  • P: Will schedule a time for discussing what to do with the capabilties

Meeting notes 2025-03-11

• Continued profile discussion
  • https://github.com/COVESA/vss-tools/pull/440
  • https://github.com/COVESA/vss-tools/issues/436
  • Input from Ford (Podalakuru, Chaitanya (C.) )
  • Daniel: COVESA can provide tooling and some fields
  • Sunil: Toyota Connected, London
    • Interested in CAN-signal mapping
    • Keep scaling internal
    • Can show next time
  • Stefan: For a specific use-case there need to be consent
  • Paul: Would be good to describe what would be common, to work on together
  • StefaN: For accident, define what would be common dataset.
  • P: What are you from Ford looking for, what is the actual gap in VSS.
  • C: If we can agree on schema, that would be great. Will discuss with team
  • C. Expect for example a schema for cyber security, would make it easy to switch between suppliers.
  • D: Schema/Syntax mechanism can be incorporated in tooling, content outside scope. Then we can see if concept is strong enough to represent some common concepts.
  • C: Can come up with profile, we can review, then check if additional validation is needed
• AMM
  • P: Working on agenda
  • E: Profiles will be mentioned
• Capabilities
  • P: Would be good to bring to this meeting. Possibly Paul or Melissa doing first presentation.
  • P: What we have observed and what we want to do.

Meeting notes 2025-03-04

• Discussion on profiles (see https://github.com/COVESA/vss-tools/issues/436)
  • Discussion on CAN signal mapping as example
  • FYI Paul Boyes 
  • Link to presented document: https://drive.google.com/file/d/1kFKMvsYzXVaNe5kP_faShfQ6ZwJyCY0s/view?pli=1
  • Erik presented https://github.com/COVESA/vss-tools/pull/440/files
  • Ted: Possibly use unique identifiers, keep clean and organized. Commercial Vehicles have some overlays, value check needed
  • Adnan: Think idea is great. We also have our own profiles, for CAN and SOME/IP, can possible open some of them.
  • A: Governance - only structure, or also content?
  • A: Common way to describe profile first step
  • E: Would be good to see what types of profiles members are interested in, like CAN, SOME/IP, safety, security, relationships
  • A: relationships: do they fit into VSS as profile? Is overlay perfect spot?
  • Ted: Conditional logic shall not be  written as text, there is open ticket in CV to make complex logic
• Video in VSS - https://github.com/COVESA/vehicle_signal_specification/issues/816
  • Ted: Presented the issue. Could be used for insurance and fleet use-cases
  • Ted: Wants to involve member companies using video
  • E: Metadata/commands only? Not video streams itself?
  • E: We have metadata for other areas like media,so not significantly different.
• AMM
  • If you have proposals contact Paul Boyes 
  • Profiles could be discussed in a session.
• VSS Explorer
  • Playground, https://vss.digital.auto/

Meeting notes  2025-02-25

Meeting notes  2025-02-11

• AMM Registration open
  • https://covesa.global/events/
• If you have proposals for presentations please add to wiki
  • AMM 202505 Technical Track Session Proposals
• Think of VSS-specific discussions
• Collection - Issue
• Erik away next week (Paul also away)
  • For now assumed Sebastian Schildt can lead it.

Meeting notes  2025-02-04

• Seat Capability Topic
  • A set of COVESA OEM members have discussed how seats better shall be represented in VSS
  • Paul: How to propose/introduce changes
  • Ulf: Smaller additions could be PR, larger better be discussed as issue first
  • Paul: Will discuss with them
  • Stephen: For older items we may not know how downstream projects are using it, maybe mention it in communication channels.

...