/
Weekly Agenda 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 2025
◎ Antitrust and Open Statement
◎ Member Visibility

Join/Sign Up

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

Weekly Agenda and Meeting Notes

Jul 25, 2025

This page is about the weekly meeting in Data Expert Group (Thursdays 16.00 Central European Time every second week)

Quick link: us06web.zoom.us/j/81407434870?pw...

If it does not work check COVESA Common Meeting Schedule

 

NOTE: Meeting is sometimes cancelled on short notice. We typically communicate that here and/or in the COVESA Slack channel for Data Expert Group. If no-one shows up within 5 minutes the meeting is likely cancelled!

 

Meeting Agenda

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

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

  • 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

 

Meeting notes 2025-07-24

  • Seating capability discussions

Meeting notes 2025-05-15 (AMM Wrap Up)

  • Ulf

    • Successfull AMM

    • Presentation time is short, should we possibly add a day more?

  • Paul

    • Got many call of presentations, too many based on times available

    • 25 min sessions good for business presentations, technical may need more

  • U: Maybe 3 days for Europe AMM, 2 days in US AMMs.

  • P: Special topics/groups may have a day before the AMM

  • E: Last AMM we had a tech day the day before, quite successful. But someone must be host/moderator

  • P: Tech summit/day ok for board

  • U: Tech summit different than having an extra day

  • P: Cost is main reason for not having 3 days

  • E: The option for next two AMMs (Ann Arbor, Porto) is an extra tech day

  • E: We could check if there is any interest for a tech day at next AMM

    • Collect ideas, check if there are people interested in acting as moderators and people willing to discuss

    • Decide at latest in august if we should have one.

  • Stephen: Travel restrictions

  • E/P: Virtual events is an alternative.

  • Sebastian: Tech sessions vary between reporting and workshops.

  • Sebastian: Give group/project updates more visibility

  • E: possibly have 1 hour project update in the big room at start of AMM

  • Sebastian: Location ok

  • Erik: Location good

  • E: We need to discuss VDM timeline and how to evaluate

  • P: Two months timeline

  • Ted: There needs to be an online instance, so people can test it, and compare

  • S: We need to careful in how we communicate it. We need to have answers to questions.

  • E: VDM candidate for tech summit/day.

  • P: TST wants it to be called VDM, not VSS next gen

  • S: Is it powered by VSS, inspired by VSS, ....?

  • Achim: Truck OEMs view that VSS is the stable solution is lost as they hear of VDM

  • (A lot of discussion on VSS/VDM co-existence going forward)

  • P: VDM have to prove itself.

Meeting notes 2025-04-03

  • AMM Sessions

    • Data Expert Group Update
      Data Expert Group Status Update
      9:30 AM - 9:55 AM Wed

      • Just mention key persons and present later presentations?

      • Adnan: Mention capabilties,

      • Adnan: What has happened sincle last AMM

      • Adnan: Mention Tooling - comparison between alternatives (VDM reqs and solutions)

      • Introduce working sessions: Overlays - Profiles - Data Models

      • AP: Erik to prepare

    • Introduction to VSS:  A Deeper Dive, 10:00 AM - 10:25 AM Wed, Sebastian Schildt

    •  

    • VSS -Working Session 1 Thu Morning

      • General Overlay-Profile_VDM

      • Overlays - how you can use it

      • What extensions are you using

      • Concrete use-cases

      • AP: Ted to prepare something

    • VSS -Working Session 2 Thu Morning

      • Overlays with hands on.

      • Potential overlays that could become profiles

      • AP: Adnan to prepare with support from Ted

    • VSS-Working Session 3 Thu Morning

      • Toolings/Datamodel

      • Daniel as host? Chetanya?

      • AP: Adnan to check if Daniel can prepare/host

      • TODO: Check relationship to other presentations from Daniel

    • 4:00 PM - 4:25 PM Thursday
      Data Expert Group - Wrap-Up

      • AP: Erik to be host

  • AP: Present first iterations of slides and "summary for agenda" at next meeting April 17th

Meeting notes 2025-03-20

  • VSS-discussions

    • Is "Profile" a good name - we already use the term "profile" for other cases like the "motorbike profile"

    • For network serialization -we may have different needs for different networks

    • Will be a starting point, could influence "Vss next gen"

    • Erik can refactor his PR to "allow" contributions, then we can see what happens from there. For now skip formal syntax, limited interest.

Meeting notes 2025-03-06

Meeting notes 2025-02-06

  • Jan to give presentation on Federate

    • postponed

  • Cross group artifacts

    • Stephen:

      • We can pick up some tickets here, inform/coordinate

      • Recurring: data sets, metadata,

      • AOSP emulator - could be expressed as need, but maybe they do not have time/knowledge to do it

    • Erik: VSS-profile proposed at https://github.com/COVESA/vss-tools/issues/436

  • PoC

    • erik: what do we want to achieve?, there is VISSR and Eclipse kuksa showing VSS usage from different aspects. Also architecture playground

  • Datasets

  • Signal relationships vs. tree (classic VSS)

    • Ulf: layered approach needed

  • Snapp blogpost

  • For next meeting try to identify topic

    • Volunteers welcome.

Meeting notes 2025-01-23

  • Android

    • AOSP workstream started, checking what already exist

    • Compare seat concept

    • Will be recurring meeting

  • Playground

    • Stephen has updated playground to latest VISSR

  • VISS v3 in review, last date for comment Feb 21

  • Meetings schedule/setup:

    • Erik: It has not been much activity in this meeting lately. Special topics have been handled in separate meetings. I think we need to do something

      • Only have the meeting when/if we have topics to discus?

      • Change schedule, bi-weekly/monthly?

      • Or does someone have time/interest to drive topics?

    • Ulf: Every second week ok (from Slack)

    • Paul: Meeting was intended to guide/align all activities in DEG

    • Ted: Could collapse TST and DEG to one

    • Paul: The CVI meeting is quite similar to this one

    • Stephen: use this slot for more of general presentations

    • Erik: Good if we have agenda on what will be discussed

    • Paul: Lets move it to lower freqency.

    • Erik: Change this to biweekly, gives possibility to use every other second week for other general public presentations?

    • ted: Shift some topics from other groups to here, let them invite others

    • Stephen: prefer high quality updates

    • Paul: Proposal - move to every two weeks, try to present agenda in advance

    • Decided, Paul to update calendar!

  • Federate

    • Would be great if Jan present in two weeks

Meeting notes 2024-11-14

  • PauI: I would like to discuss/ideate on best way to figure out adoption rates particularly for VSS.  Start to discuss discretely scoped projects (e.g. tools, how-to, …) that would be useful to COVESA.

  • Github project created for VSOMEIP - see https://github.com/orgs/COVESA/projects/13

  • Capabilities project

Meeting notes 2024-10-31

  • AOSP wanted direction has an overlap with what happens in the data part of Data Expert Group

  • Adnan: Need to figure out how to engage in capability discussion

  • Swen: Will give update on data exchange platform in commercial vehicle call

Meeting notes 2024-10-24

  • Winter time in EU Oct 27th (Us Nov 3rd) - so meetings shifted 1 hour next week for persons not in EU

  • Paul: VSOMEIP - discussing with them on contrib process, trying to get them to create a list before things being implemented

  • Contribution process - continued discussion

    • Paul to create draft on wiki

  • CVI - Gunnar suggesting a regular developer meeting for IFEX.

  • Seats discussed in Capabilities Project - Capabilities Project - Seating Capabilities

  • AOSP doing survey

Meeting notes 2024-10-17

Meeting notes 2024-10-10

  • Stephen: Where to put diagrams

  • AMM: Wrapup

  • European data Act (Volvo - Wireless Car)

    • Paul working with Magnus

  • API Standardization

    • Will be reviewed at next TST

    • Erik: Think it would be good to be more specific on whats to be done in the short term - actual deliverables.

  • Capabilities

    • Stephen: JasPar has a workgroup related to vehicle API. Might be one way to involve the Japanese OEMs

 

 

Meeting notes 2024-10-02 Cancelled!

Meeting notes 2024-09-19

 

Meeting notes 2024-09-05

Meeting notes 2024-08-22

  • Workshop Tuesday, Sept 24

    • Proposed Agenda Topics

      • Top down requirements for scaling VSS to adjacent domains

      • VSS role in Data-Centric Architectures

      • Standardization

      • API Design with VSS

      • Enabling and Realizing Cross Cutting Use Cases

Meeting notes 2024-08-08

  • Erik on vacation rest of month

  • Workshop Tuesday

    • Erik: Heard that NXP will be the venue

  • Proposed AMM VSS Topics (for the AMM 202409 Technical Track Planning "Data Expert Group - VSS" sessions)

    • VSS - What is new in VSS 5.0

      • In this session we will present what is new in VSS tools 5.0 and discuss how the changes in vss-tools may affect you.

    • Requirement Management for the COVESA VSS Project

      • At the moment we do not have any formal requirements for the VSS syntax, catalog and tooling.
        We also do not know what requirements and expectations downstream projects as well as COVESA members have on the VSS project.
        In this session we propose a methodology for how to collect and manage VSS requirements.

Meeting notes 2024-08-01

  • Workshop Tuesday

    • DEG-related topics (2-3 hour, morning)

      • VSS Roadmap (Daniel points, collect requirements)

      • CVI-roadmap/relationship, playground relationship

        • What work products would be useful

      • What is needed for adoption

      • AI influence - how will it affect VSS/CVI/Architecture - interfaces

        • Could be used to identify usecases we need to cover within COVESA

      • GM/Ford input - how do they want to influence/contribute to the work, what do you expect from COVESA

    • API workshop (2.5 hour, afternoon)

    • AP: Create agenda until next week

    • NXP has venue for 40 person

    • Bosch has space

    • To be decided before next meeting

      • Paul to figure out and decide on where

  • AMM Planning

    • AP: Erik and Adnan to propose content for VSS/DEG slots

      • May be replaced with other sessions

Meeting notes 2024-07-25

  • Topics for the workshop day before the AMM

    • Catch 22

      • No-one will come if we do not have interesting topics

      • But no reason to have a workshop on interesting topics if no-one will come

    • Erik: Try to have an agenda (or decide to cancel by August 8th?)

Action points

  • Bring up the discussion on the CVI meeting (Erik & Paul)

  • Bring up in VSS meeting (Erik)

  • Erik to propose rough agenda for next meeting

    • 9.00 - 16.00 (1 hour lunch), or 10.00 -17.00

    • Location not decided yet, not at AMM site  (Possibly The 5th Novi)

Meeting notes 2024-07-18

  • VSS Japan-friendly timeslot (15.00 24th July JST, 8.00 24th CEST, 23.00 23rd Pacific)

  • Digitial.Auto PR access (review by TST 29th)

  • Data Arch (Stephen)

    • PR in Playground - working on example

    • Would like to look at commercial vehicle guidelines

    • BMW continuing with knowledge layer connector

Meeting notes 2023-07-11

  • Automotive API with AUTOSAR

    • Ulf and Steve attended meeting.  A doc will be sent to VISS and VSS for review at some point

  • Hugo doc theme Learn deprecated.  ReLearn or Hextra are suggested as path forward.   https://themes.gohugo.io/ 

    • Projects should update as they can

  • Commercial Vehicle EG approved.  

    • Comments in charter should be addressed and cleaned up.

  • AOSP and VSS 

    • Insurance elements proposed for VSS

 

Meeting notes 2024-07-04 CANCELLED!

Meeting notes 2024-06-27

  • Paul: Daniel Alvarez and Dough/Cariad met and they seem to be aligned

  • API Standardization Charter

    • Proposed to work as part of CVi meeting

Meeting notes 2024-06-13

Meeting notes 2024-05-30

Meeting notes 2024-05-23

  • Regular checkins between HIM/Commercial Vehicle Information Specifications

    • e.g. Overlays vs HIM

  • Common Vehicle Interfaces

  • Naming

    • Avoid similar names/acronyms if possible

  • Central Data Service Playground

    • BMW close to knowledge layer contribution