This page intends to contain the agenda for next VSS meeting (Tuesdays 16.00-17.00 CET) and notes from previous meeting. At the bottom is a template for the agenda. General agenda points like discussion on PRs and issues may be skipped if discussion on prioritized topics takes too long time.

See COVESA Common Meeting Schedule for meeting link. The meeting is open to anyone.

If a meeting is cancelled it is typically

• Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

Antitrust

Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free

Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

• 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

• Where/how to store ACEA/FMS signals

• Paul presenting issue https://github.com/COVESA/vehicle_signal_specification/issues/877

  • No objections during the meeting.

  • It is necessary to complete the list of signals for the PR.

  • @Paul Boyes will go into second round to complete list of signals.

• Adnan have sent notification to David about PR https://github.com/COVESA/vehicle_signal_specification/pull/855

• S2DM PR from Daniel Alvarez, merged.

• SD2M: Daniel presented https://github.com/COVESA/vss-tools/pull/475

• Erik on business trip next week

  • Can @adnan.bekan@bmwgroup.com or @Paul Boyes host it?

• VSS 6.0

  • 6.0 released and set as “latest release”

  • Erik intends to merge back changes from the release branches later this week and make master branches “ready” for continue development

• FMS branches

  • E: There have not been any detailed discussion on where to put FMS additions (customization/addition for commercial vehicles).

  • E: Alternatives:

    • Overlay within std catalog (master branch)

    • Separate branch in covesa vss repo

    • Fork of vss within covesa

    • Separate repo within covesa (if starting tree from scratch)

    • Repo outside covesa

• AMM Porto

  • Submissions welcome, registration open

•  

• VSS 6.0 release decision

  • RC available since Dec 18th

  • No comments/remarks received

  • OK to release

• AMM Porto

  • Registration open at COVESA All Member Meeting | April 22-23, 2026 | Porto, Portugal

  • Contact Paul if you are interested in presenting something

  • Start thinking if there are some VSS-specific topics you want us to discuss

  • VDM-VSS co-existence is one topic

• FMS “own branch”

  • Fleet Management, ACEA

  • Wants a branch for themselves, maybe in own github

  • Ted: Some differences, how to handle variations. either branch or own tree

  • E: Placeholder for fuel systemdiscussion at https://github.com/COVESA/vehicle_signal_specification/issues/875

  • Stephen: Opportunity to discuss how to tackle this in general.

• Enum - https://github.com/COVESA/vehicle_signal_specification/issues/873

• UDS discussion (in slack)

  • T: How do we reconcile diagnostics and services. E.g. single data point in VSS that refer to diagnostics server address.

  • T: May need to be discussed in TST

• CES

  • A lot of interest in VSS

  • COVESA CES2026 Networking Event - COVESAPreview

  • Sensors/actuators -

• We will cancel 23/12-6/1

  • Next meeting Jan 13th

• Paul: Safety Pull Request in progress, is airbag deployed and similar

• Charles Fairchild from Cox Automotive presented himself.

• VSS 6.0

  • Intended PRs (if approved)

    • https://github.com/COVESA/vss-tools/pull/473

    • PR from ted

• Discussed https://github.com/COVESA/vehicle_signal_specification/pull/824 and https://github.com/COVESA/vehicle_signal_specification/issues/827

• Holiday break

  • We will cancel 23/12-6/1

  • Paul to clean up calendar

• VSS release 6.0

  • Paul: AGL asked for release date last week

  • Erik: Planning to create (pre) release before christmas

• Ted: Issues - 822 827

• MDS Meeting/Discussion

  • @Edward Guild @Paul Boyes

• JasPar

• AUTOSAR

• FMS

• S2DM

• Holiday Meetings

• Release Plan

• Paul: MoU in JASPAR in progress

• Erik: Will miss next meeting

  • Paul to check if Adnan or Sebastian Schildt can join

• PRs discussed

• Winter time in Europe, Meeting is in European time

• AMM - News?

  • Ted: Intersting road safety discussion, automated incident reports based on VSS

  • T: Jaspar presence

  • Richard: Was not much attendance

  • T: Much less Europeans, missed some of the usual attendants

  • T: Next fall meeting in Japan

  • S: Greater engagement from Japanese Tier 1

  • S: May need more formal communication - on individual opinion vs project opinion

  • P: Big interest in jaspar, Commercial vehicles, VDM

  • P: Ai presentations

  • COVESA All Member Meeting ~ October 22-23, 2025

• Discussion on indicator proposals - see https://github.com/COVESA/vehicle_signal_specification/issues/852

  • ACEA/FMS are not that fond of using "Infotainment" as part of the branch as that may imply that the signals are part of Qm and not part of cluster.

• E: Does project have anything against using a shorter path that is idependendant to whether the indicator typically is shown in Infotainment (center console, QM) or Cluster (ASIL). Like using something like Vehicle.HMI.Telltale1 or

• Vehicle.HMI.IndicatorLights.Acc
  
  

• Erik away next week

• AMM Updates

  • Putting up online sessions in the community calendar

  • Will confirm participation with "mandatory participants" (like Erik in DEG Update)

  • S: DEG Update - who will present?

    • Paul and Stephen to host DEG update

    • Erik to provide VSS update slide(s)

• Questions from Honda

  • See https://github.com/COVESA/vehicle_signal_specification/issues/857

  • AP - Paul to arrange meeting to better understand there problem

  • Check if we should add one struct (e.g. lat/lon) to tree to show concept.

• Discussion on indicator proposals - see https://github.com/COVESA/vehicle_signal_specification/issues/852

  • Zoltan Baksa from Bosch intended to participate

• AMM

  • PauL: We have a time block, what do you want to discuss/cover? ROS2?

  • DEG Update

    • Paul or Stephen as host

    • Stephen short info on data arch

    • Erik can provide something about VSS

    • Daniel can provide something about VDM

  • VSS working session

    • Use slot for VDM-related discussion

    • D: Could do a hands on session. Like showing how to work with vspec in a domain outside VSS

    • P: Could be great

    • P: Will sync with Daniel, adjust agenda as necessary

  • E: Final check next week

• VDM presentation

  • https://us06web.zoom.us/rec/share/xkR_h2DF23_Bk0DPNA9fhYCRV7_89sfnJFmBs3bEF8FTZPCWsMn4dco4lq-j4K4.Ji5tNa08nv-RKf-g

• Discussion on indicator proposals - see https://github.com/COVESA/vehicle_signal_specification/issues/852

  • Zoltan Baksa from Bosch intended to participate

• Battery capacity - https://github.com/COVESA/vehicle_signal_specification/pull/849 closed?

• VSPEC2TTL

  • Non-functional - any value in keeping it

  • https://github.com/COVESA/vss-tools/issues/403

  • Ap: Erik to create PR to remove it

Cancelled

• Release VSS 6.0?

  • E: We have some topics that were not included in VSS 5.1, and some upcoming topics like https://github.com/COVESA/vss-tools/pull/463

  • E: When do we think a 6.0 (of VSS and VSS-tools) would make sense

  • E: Would it be an idea to release 6.0 before end of year

  • D: The s2dm exporter could be released as part of minor, no backward problem

  • P: One major before end of year could make sense

  • E: As of today we have some "minor" (but backward incompatible) changes that has been in master for quite a while

• IAA

  • D: Visisted Friday. OEMs moving to digital in-car concepts, similar concepts. European brands took main stage. batteries, digital mirrors, ...

  • D: Website/social-networks has some content

• AMM

  • E: Will not be able to join

  • D: Not fixed who will visit.

  • D: As VDM is now a Covesa project, preparing material, Chetanya/Ford can possibly present.

  • D: Requests on what you want to see related to VDM would be beneficial, please propose.

  • P: VSS/VDM time in the morning, I have some suggestions for topics but please provide proposals.

• Paul: Starting a page on VDM/VSS co-existance requirements, page will show up with content on wiki soon

• D: Possibility to arbitrary select VSS properties/signals, e.g. profile. Do we have something to reuse?

  • E: I think we have some overlay support to remove individual signals see https://covesa.github.io/vehicle_signal_specification/extensions/overlay/index.html#deleting-nodes, but that likely does not suffice

  • D: Would be good to be able to select what subtree of the tree to export. Could be used to populate database

  • D: Arbitrary grouping/selection could help

  • E: Have not seen anything more generic

• Ulf: It would be great if participants at IAA could say something about it:

  • Candidates: Sebastian Schildt, Daniel A will visit it on Friday

• Paul: FMS topic - a proposal how to add data from ACEA/FMS in the pipeline

  • Some info at https://github.com/COVESA/vehicle_signal_specification/issues/827

• Paul: Getting a lot of proposals for AMM.

• Jeremy, Michelin:

  • TorqueDistribution has given as headache, Torque Management branch recently added

  • Looking for torque, have two different signals that gives torque for each axle, today we use torque distribution and multiply with engine torque

  • Erik: There are some background in https://github.com/COVESA/vehicle_signal_specification/blob/1624e7a95e574b4618222e7d4bc3d68e7cee4112/docs-gen/content/catalog/vehicle_motion_management.md, based on proposal from Bosch

  • Erik: feel free to add an issue and we can then discuss it in a later meeting, I can involve persons from Bosch that was part of the Bosch proposal

• Sebastian: Next week IAA in Munich, Germany.

• New site https://covesa.atlassian.net/wiki/spaces/WIK4/pages/39067665/VSS+Meeting+Topics+and+Meeting+Notes

• Need to do forget password, all should have received invite (?)

• Paul to add big disclaimer/redirect on old page

• Paul

  • AMM agenda starts showing up

  • You tell me what to do (about 1-1.5 hours for “generic” VSS topics)

  • VSS and VDM relationship – status

• Adnan: Unclear if someone from BMW will present anything regarding to VDM at the AMM

• Erik: if someone has any topics they want to bring up as part of the “VSS slot” please let me or Paul know it

Erik is still on vacation.

• PR and Issue Review

  • Merge new Mirror Yaw signal

  • Merged individual  TireTemperature signals for rubber and air

• Erik on vacation August 7th-22nd

  • Paul can host

  • @adnan.bekan@bmwgroup.com @Sebastian.Schildt - are you off next weeks?

  • Possibly cancel if no one of them can join

• Start thinking about topics for the VSS working sessions at the AMM

  • One suggestion - Github projects for VSS - see https://github.com/COVESA/vehicle_signal_specification/issues/841

• Paul/Daniel: All of you are very welcome to the Vehicle Data Model meeting on Thursdays

• D: We are going to present something at the next AMM, how to mirror VSS in VDM.

• VSS 5.1 released

  • https://github.com/COVESA/vehicle_signal_specification/releases

  • Please test/check

• Seats - any comments on https://github.com/COVESA/vehicle_signal_specification/pull/838 preventing merge?

• Martin: Vehicle Health Management

  • Provide basic units, like in the example below

  • In previous meeting someone proposed open telemetry

  • Many things in common - but they do not mention VSS

  • For service oriented vehicle - did not see anything related to VSS

  • M: What is you idea/view. Shall I create a Pull Request

  • P: Think it was Adnan who talked about it

  • P: Did open telemetry specify something similar

  • S: Would be good to try to model it in VSS, could be useful in a VSS meeting.

  • S: We may need to dicuss how generic it is, can it be modelled in VSS

  • S: Would help if you put in a Yaml spec (PR)

  • M: Have tested it with Kuksa

  • M: Connected this subtree to VSS in demo, but uncertain where it should be in std catalog. Example is ECU but could be else

  • M: I already have yaml file, can add it in a PR

  • S: Would be most helpful

  • S: branch does not matter that much for now

  • E: Making a PR wouldd be great to continue

  • P: From TST - we should have a step on diagnostics

  • Ted: COVESA and Eclipse looking at areas to collaborate, Diagnostics could be an area

• AMM

  • Call for proposals open - please contact Paul or add to planning page AMM 202510 Technical Track Session Proposals

Open

• Release Planning

  • Erik: Suggests that we only release vss, not vss-tools. Rationale is that it would be quite cumbersome to isolate the non-breaking changes on vss-tools master branch. The removal of "–uuid" is a breaking change.

  • Also removed the pattern and obstacle changes

  • New RC created https://github.com/COVESA/vehicle_signal_specification/releases/tag/v5.1rc1

  • Sebastian S: Tools are separated, nothing would prevent us from releasing vss-tools 6.0 separately.

  • S: Focus on VSS 5.1 just nu, but should not block vss-tools 6.0 after the 5.1 release.

  • E. Sounds like a good approach.

  • E: To update table in https://github.com/COVESA/vss-tools

  • AP: Please review 5.1 (rc1) until end of week, if no remarks ready to release

• Release planning

  • https://github.com/COVESA/vehicle_signal_specification/issues/815

  • https://github.com/COVESA/vehicle_signal_specification/issues/833

  • Erik: Seems we want a strict approach.

    • Is changing GraphQL tool consider backward compatible, i.e. no changes in vss-tools breaks compatibility.

    • Suggestion: Cherry-pick vss changes except VIN and obstacle (let them wait for 6.0), but include GraphQL change (vss-tool) and pattern (Vss-tool)  in 5.1

      • Agreed

      • AP: Erik to create 5.1 RC1, hopefully this week

    • Ulf: Want better criteria on what goes for minor and major

    • Erik: We have https://covesa.github.io/vehicle_signal_specification/governance/index.html - it could off course be rephrased. Pull Requests welcome.

• Mirror pan

  • https://github.com/COVESA/vehicle_signal_specification/issues/835

• Teds Issues

  • https://github.com/COVESA/vehicle_signal_specification/issues/830

  • https://github.com/COVESA/vehicle_signal_specification/issues/827

• PlantUML

  • https://github.com/COVESA/vss-tools/pull/456

• Erik off (also next week)

• VSS 5.1 release candidate at  https://github.com/COVESA/vehicle_signal_specification/releases/tag/v5.1rc0, please review

• VSS-tools 5.1 pre-release at https://pypi.org/project/vss-tools/#history

• VSS 5.1 release - see https://github.com/COVESA/vehicle_signal_specification/issues/815

  • Decision: OK to include all current master changes in 5.1

  • If we are to create a 5.1 soon - anything critical to include

    • Decision: No

  • Erik to create release candidate this week

• Erik away next week

  • @Sebastian.Schildt @adnan.bekan@bmwgroup.com - could you host it?

• X.Y.Z.V.W,    Segments like V.W with two branches should be unqiue

• Issue cleanup to be done

  • of older non-changed issues