/
VSS Meeting Topics and Meeting Notes

Get Involved

◎ COVESA Community Calendar
◎ COVESA Getting Started
◎ Understanding and Engaging in COVESA
◎ Project Launch Process

Groups and Projects

Groups and Projects continued...

◎ Vehicle Signal Specification (VSS)
◎ AOSP App Framework
◎ Commercial Vehicle and Fleet Group
◎ Generative AI Group
◎ Central Data Service Playground

◎ Vehicle Data Model
◎ Cyberecurity Group
◎ In-Vehicle Payments Group
◎ Connected Safety
◎ All Groups and Projects

Resources

◎ COVESA Events
◎ Industry Events 2026
◎ Antitrust and Open Statement
◎ Member Visibility

Join/Sign Up

◎ Join COVESA
◎ Sign Up for Member Newsletter
◎ Request Wiki Account
◎ Request Access to Slack

VSS Meeting Topics and Meeting Notes

 

 

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.

Notes from previous years can be found in subpages!

General Agenda

  • Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

Message from Antitrust and Open Statements

 

Antitrust Note Well
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.

Contributing to COVESA Activities

Companies and individuals contributing to COVESA activities should understand the COVESA IP Policy and know that all COVESA work products, including software and documents, will be released under an open source license as described in the Public Policy for Open Source Licensing. Contributors must also follow COVESA’s Export Controls and Sanctions Compliance Policy. Before a contribution can be accepted, contributors must provide their name, contributing organization if the contribution is not personal, email address, and country.

COVESA is not a standards body. Any COVESA activity that requires a formal specification must first be approved by the Board of Directors and then moved to a formal standards development organization.

Please do not contribute ideas or code that may involve patents unless you disclose to other participants, through meeting minutes or pull requests, that use of the contribution could potentially infringe 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

  • Prioritized topics for next meeting

Meeting notes 2026-09-01

Meeting notes 2026-08-25

  • Jeremy: VSS tool - exporter cpp

  • J - We do not export current version of VSS - no exporter does that

    • E: No guarantee that the std catalog VSS signal exist if using customing tree

    • E: I see no problem extracting VSS version from signal tree and adding it in output, as long as we do not crash if the signal is not there.

    • J: Could be something added by exporter

    • D - could be good practice. But can be difficult for changed trees.

    • D - could introduce common flag to exporters to export metadata file

    • J - can try on c++ exporter

    • J: As of today we can have multiple sources, which version to take. Like overlays

    • D - We can specify base version

    • D - Check compose command

  • twenty.com - has joined, possibly bot

    • Not a COVESA initiative

    • U: Should better be known who initiated it

  • AMM - October Michigan

    • P: Wants to know what we want to do

    • Reach out to Paul if you work for a COVESA member and do not know who is the contact

Meeting notes 2026-08-18

Meeting notes 2026-07-28

  • Paul to set up a call with Erik et al on Automotive world preparations

Meeting notes Jul 14, 2026

Meeting notes 2026-06-23

  • VSS 6.1 status

    • D - Needs to publish model ledger, will publish latest changes. Hope to get done this week

    • D - Can then check with current

    • D - Still missing - namespace. Will check it out

  • Instance handling

  • Enum constants (see PR from Ted)

    • T: Inclined to redraw common constants proposals, as it may give problems.

  • s-core

  • Meeting schedule for summer - who can host the meeting

    • Erik on vacation or business trip 29/6-21/7 and 10-14/8

    • Paul not here June 30th

    • Unclear if @adnan.bekan@bmwgroup.com can host?

    • Cancelled 30/6

    • For other keep an eye on slack to see if it is cancelled

Meeting notes 2026-06-16

  •  

Meeting notes 2026-06-02

  • Daniel to present

  • Erik off next week. Can @Paul Boyes @adnan.bekan@bmwgroup.com or @Sebastian.Schildt host? Cancellation (if needed) will be communicated on slack

Meeting notes 2026-05-26

  • Daniel to present - postponed to next week

Meeting notes 2026-05-19

  • Release Plan

    • 6.1 June - after new compose/diff tool added, before franca removed

    • AP: Erik to check if there any backward incompatible changes on main

  • Security group

    • Metadata for security, classification for security/privacy

    • Discussion on June 3rd, see community calendar

  • Jaspar - how to bring things back to VSS

Meeting notes 2026-05-12

Meeting notes 2026-05-05

  • Paul - Anything we want to say related to VSS roadmap

    • E: One topics is defining guidelines/rules for the catalog. They exist sometimes today but only in our heads.

    • E: Tooling side - VDM prepareness

      • D. Intends to have a continuous integration VSS to VDM

    • D. Specification registry, future proof entries

    • D. Semi-automating concepts, make it easier to create draft proposals

    • D. Enable reuse of other vocubalarities

  • P: Export Control - you have to be verified to commit

  • D. Sometimes final users wants a somewhat different output. We could have a generic mapping engine. Can configure if they want a partially different output.

  • How does people want to use LLMs together with VSS

    • Natural language exploration, like analyze requirements like “I want to analyze a crash, what VSS signal could be useful for this purpose?”

Meeting notes 2026-04-28

  • AMM

    •  

  • OCX - Anyone was there?

    • s-core -

  • Automotive world in Japan, September, COVESA technical sessions planned

  • Fall COVESA AMM in October in Novi, Michigan

  • Jaspar

    • https://www.jaspar.jp/en

    • https://yoriito.dev/

    • https://github.com/yoriito

    • Especially interesting for us is https://github.com/yoriito/yoriito-vss

    • See https://github.com/yoriito/yoriito-vss/blob/main/scripts/create_vspec.sh for how they build their VSS (overlay plus VSS)

    • Noticed changes - using numbers for batteries and electric motors.

    • How to get started:

    • git clone https://github.com/yoriito/yoriito-vss cd yoriito-vss python3 -m venv .venv source .venv/bin/activate pip install -r requirements.txt scripts/create_vspec.sh

Meeting notes 2026-04-14

  • No meeting next week (AMM)

    • @Paul Boyes - please remove it from calendar unless you already have done so

  •  

Meeting notes 2026-04-07

  • AMM

    • Introduction to VSS:  A Deeper Dive

      • Erik to present

    • Data Expert Group - Community Update

    • Data Expert Group - VSS Next and VDM Next

      • Adnan to sync with Daniel if he could lead

      • E: General VSS going forward without anything really revolutionary. We have interesting collaborations w ACEA/FMS, Jaspar

      • Stephen: Governance

      • Adnan: Lets not confuse people

      • E: isnt it decided that VSS will remain supported, used and not changing drastically

    • Joint Vehicle Signal Specification/Commercial and Fleet Vehicle Expert Group Working Session

Meeting notes 2026-03-31

Meeting notes 2026-03-24

Meeting notes 2026-03-17

Meeting notes 2026-03-10

  • FMS/ACEA Enum topic

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

    • Ted: FMS/ACEA wants enum

    • Ted: In J1939 often use as enum for boolean values

    • T: Ford proposed some time ago extra metadata for datapoints, like e.g. error.

    • T: I think we should avoid enums just to represent J1939 errors in boolean values

    • Segej: Has looked in velocitas broker and have seen error handling, but not part of VISS so our broker does not do the error handling

    • S: if we have a boolean we want to handle it as a boolean. If API can handle error it would be great. If we cannot rely on API for error handling we need to handle it on signal level.

    • S: Can we have error handling mentioned in VISS

    • Ulf: Would say VISS already handle this. But could extend if we see problems

    • E: See e.g. https://raw.githack.com/COVESA/vehicle-information-service-specification/main/spec/VISSv3.0_Transport.html#common-error-scenarios

    • Ulf: We should maybe not discuss here, lets discuss offline.

    • E: AP to check what VSS spec says on error handling. Think we say that VSS does not specify it, but refer to the API

    • S: VSS signals are logical signals. For J1939 do we state somewhere that a specific J1939 error code corresponds to a particular (VISS) error code

    • U: VISS should potentially not mention J1939

    • E: But adding a supplement that specifies J1939-VISS mapping would not be a problem

    • U: Yes

    • S: We have standardized error codes. Our implementation should know how to do the mapping.

    • U: Seems to be an implementation issue to me. VISS have bi-weekly meetings

    • E: better be discussed in VISS meeting, if it mainly concern VISS error codes

    • Daniel: Sees similarities with other protocols, like in the past OBD

    • As of today we do not support enum, we have alowed values

    • E: presented https://github.com/COVESA/vehicle_signal_specification/pull/885 as example for possibly syntax

    • D : Finds this complex. What could be done is have two different types of allowed values. One as today. Instead of type string pass “enum”.

    • image-20260310-155325.png

      E: Way forward if some changes are to be implemented

      • Someone to continue refining syntax

      • The testing it out in vss-tools, implement support

    • D : We lack method to reuse existing standards

    • E: Please continue discuss issue and PR.

Meeting notes 2026-03-03

  • FMS - enum topic

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

    • Ted: Could bring them to this call

    • T: API aspect

    • U: Both text or value representation would be usable in VISS

    • E: Way forward if we are going to implement/extend VSS

      • Syntax proposal PR

      • Analysis how it impact vss-tools and exporters

      • PR for exporters

      • Impact on downstream projects (VISS, VISSR, Kuksa, …)

    • T: Some prefer enum instead of boolean as it is enum in FMS

    • Armin Keller will visit AMM, and Abdul Sellami from Volvo

  • AMM

Meeting notes 2026-02-23

  • AMM VSS Topics

    • Jeremy - VSS catalog for trucks

      • Erik part of FMS/ACEA discussion

      • Ted: ACEA and COVESA has a liasion agreement for fleet management, J1939, …

      • Ted: Scania/Volvo may present at AMM

    • Erik: VSS Governance if we have additions from FMS/ACEA and Jaspar

      • Changed meeting times (sometimes Asian friendly?)

    • Daniel: Workshop - allowed values as separate set of definitions, e.g. for enum

      • Ted: Working on enum PR/issue together with Scania

  • Jeremy presented issue https://github.com/COVESA/vehicle_signal_specification/issues/883

Meeting notes 2026-02-17

  • Erik: Suggestion that we discuss AMM topics next week

  • Paul: FMS will present, possibly joint working session with VSS

  • Paul: Jaspar will also be there, wants to announce what is going on

  • P: VDM call for models, check post on slack

  • P: Encourage participants to check out how VDM fit their needs

  • E: Some ideas to discuss

    • VDM collaboration/sync implications (roundtrip?)

    • Collaboration model with FMS/Jaspar - how is VSS project affected. Changed meeting schedule?

  • P: Have started a schedule draft

  • P: up to 3 hours available for VSS workshops

  • P: Use of AI, Fleet mgmt, …., could be interesting talks. Many topics proposed

  •  

Meeting notes 2026-02-10

Meeting notes 2026-02-03

Meeting notes 2026-01-27

Meeting notes 2026-01-20

  • 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