This page is about the weekly meeting in Data Expert Group (Thursdays 16.00 Central European Time every second week)
Quick link: https://covesa.my.webex.com/covesa.my/j.php?MTID=m53088c6ddb5734b991fe3a2311b4ae7 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
...
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
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
Upcoming topics
Topic | Details | Suggest by |
|
|
---|
Cross Group Artifacts | On topics, personally I would to advance discussions on the cross group artifacts. Things like data sets, schemas, VSS packaging, meta-data, governance and touchpoints. We know the data modelling discussion is being re-energised.There is also a proliferating set of projects. What synergies are there across them? What are the re-use and collaboration opportunities to do more with less?This should all be pragmatic, with a view towards outcomes. | |
|
|
Signal Relationships | Interest from Ford and BMW | |
|
|
Data availablity / Datasets | Request for sample data often mentioned | |
|
|
PoC | What would a good PoC look like? Available poC: - VISSR
- Eclipse Kuksa
- COVESA Central Data Service Playground
| |
|
|
Meeting notes 2025-04-17
Meeting notes 2025-04-03
- AMM Sessions
- 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
- The VISS WG has published the VISSv3.0 release candidate 1
https://github.com/COVESA/vehicle-information-service-specification/releases/tag/v3.0rc1
A review period is now started that will end at March 28.
Comments are very welcome. - AMM Agenda
Meeting notes 2025-02-06
- Jan to give presentation on Federate
- 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
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
- European data Act - Initial COVESA meeting held, Volvo Cars(M Feuer, Sonya to prepare charter with help of Volvo Cars colleagues)
- Monthly Asia Meeting (23rd, 8.00 CEST)
- Contribution process
- Winter time coming up, all meetings normally defined in european timezone.
Meeting notes 2024-10-10
- Stephen: Where to put diagrams
- AMM: Wrapup
- European data Act (Volvo - Wireless Car)
- 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
- AMM/Workshop Agenda
- No DEG meeting next week due to AMM
- Erik is preparing "DEG updates" slides for AMM
- DEG/VSS Asia meeting next week
- Practically impossible to participate from Michigan
- Paul to contact them
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
- 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 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.
...
- 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?)
...