...
- 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
...
...
...
...
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
...
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
...
- General Overlay-Profile_VDM
- Overlays - how you can use it
- What extensions are you using
- Concrete use-cases
- AP: Ted to prepare something
...
- Overlays with hands on.
- Potential overlays that could become profiles
- AP: Adnan to prepare with support from Ted
...
- 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
...
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
- 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
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
- 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
- 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.
...
- Continued discussion on presentations for AMM
- Review of presentation materials created so far.
Minutes of Meetings
- AMM Schedule
- General overview planned right now for 09.00-10.20
- Agreed to reduce to 50-60 minutes
- Adnan to prepare draft slides until next week, will synch with Erik
- 1 hour session for DEG leads at end of day
Meeting 2022-09-15
Participants
Erik, Paul, Joby, Stephen, Ted
Declined
Tim Grieshammer
Proposed Agenda
- Working model (at least until AMM)
- Agree on what shall be discussed in expert Group Meeting vs. subproject meetings (VSS, VSC, security, CVII, …)
- Meeting frequency, time and dates
- What do we want to achieve until AMM
- Identification of current activities that falls under data expert Group (What are they doing? How active are they? What has been delivered/contributed last 6 months? Roadmap for next 6 months)
- Identification of a limited number of gaps/inconsistencies that needs to be prioritized by the Data Expert Group – e.g. what shall be our main focus until next AMM
- AMM presentations and sessions – see https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Working+Internal+planning+page+for+COVESA+AMM+October+2022
- Review of presentation materials created so far.If time permits, sync on status of all activities belonging to Data Expert Group
Minutes of Meetings
- AMM Schedule
- General overview planned right now for 09.00-10.20
- Agreed to reduce to 50-60 minutes
- Adnan to prepare draft slides until next week, will synch with Erik
- 1 hour session for DEG leads at end of day
Meeting 2022-09-15
Participants
Erik, Paul, Joby, Stephen, Ted
Declined
Tim Grieshammer
Proposed Agenda
- Working model (at least until AMM)
- Agree on what shall be discussed in expert Group Meeting vs. subproject meetings (VSS, VSC, security, CVII, …)
- Meeting frequency, time and dates
- What do we want to achieve until AMM
- Identification of current activities that falls under data expert Group (What are they doing? How active are they? What has been delivered/contributed last 6 months? Roadmap for next 6 months)
- Identification of a limited number of gaps/inconsistencies that needs to be prioritized by the Data Expert Group – e.g. what shall be our main focus until next AMM
- AMM presentations and sessions – see https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Working+Internal+planning+page+for+COVESA+AMM+October+2022
- If time permits, sync on status of all activities belonging to Data Expert Group
Minutes of Meetings
- Keep weekly meeting at this slot.
- All pillar leads to prepare 1-2 slides on what current/recent activities and plans on what to do going forward (e.g. until next AMM). Can be more or less detailed. Either already now present detailed ambition until next AMM, or state that detailed ambition will be discussed during AMM or after AMM.
- If possible, send to Erik in advance
- Next week discuss:
- Quick review of slides mentioned above, any gaps/inconsistencies, e.g. projects falling between the pillars.
- AMM sessions - does plan need to be updated?
Meeting 2022-08-30
Attendees
- Adnan Bekan
- Erik Jaegervall
- Joby Jester
- Krishna Koppolu
- Paul Boyes
- Sebastian Schildt
- Stephen Lawrence
- Ted Guild
- Thomas Spreckley
- Tim Grieshammer
Notes
Walk through overview of Data Expert Group with question and answer
- Discussed mapping of existing activities to group (see diagram in Charter above). Explained goal is not to disrupt current activities
- Discussed distinctions between Security, Privacy, and Personal Privacy. Work to be done.
- Discussed ideas for desired next steps.
Identified and confirmed the following leadership:
- Group Co-Chair, Best Practices Lead - Erik Jaegervall
- Group Co-Chair - TBD
- Architecture/Infrastructure Lead - Stephen Lawrence
- VSS Lead - Adnan Bekan, Sebastian Schildt
- VSC Lead - Tim Grieshammer
- Security and Privacy Lead - Joby Jester
Discussed October AMM schedule.
Next Steps/Action Items
...
- Topics:
- Way of working and deliverables
- 6 month roadmap
- AMM Presentation
- Additional Group Co-Chair
...
- Keep weekly meeting at this slot.
- All pillar leads to prepare 1-2 slides on what current/recent activities and plans on what to do going forward (e.g. until next AMM). Can be more or less detailed. Either already now present detailed ambition until next AMM, or state that detailed ambition will be discussed during AMM or after AMM.
- If possible, send to Erik in advance
- Next week discuss:
- Quick review of slides mentioned above, any gaps/inconsistencies, e.g. projects falling between the pillars.
- AMM sessions - does plan need to be updated?
Meeting 2022-08-30
Attendees
- Adnan Bekan
- Erik Jaegervall
- Joby Jester
- Krishna Koppolu
- Paul Boyes
- Sebastian Schildt
- Stephen Lawrence
- Ted Guild
- Thomas Spreckley
- Tim Grieshammer
Notes
Walk through overview of Data Expert Group with question and answer
- Discussed mapping of existing activities to group (see diagram in Charter above). Explained goal is not to disrupt current activities
- Discussed distinctions between Security, Privacy, and Personal Privacy. Work to be done.
- Discussed ideas for desired next steps.
Identified and confirmed the following leadership:
- Group Co-Chair, Best Practices Lead - Erik Jaegervall
- Group Co-Chair - TBD
- Architecture/Infrastructure Lead - Stephen Lawrence
- VSS Lead - Adnan Bekan, Sebastian Schildt
- VSC Lead - Tim Grieshammer
- Security and Privacy Lead - Joby Jester
Discussed October AMM schedule.
Next Steps/Action Items
- Coordinate next meeting Erik Jaegervall
- Topics:
- Way of working and deliverables
- 6 month roadmap
- AMM Presentation
- Additional Group Co-Chair
- Communication plan Paul Boyes
- October AMM Scedule
- Create working copy for group Paul Boyes
- Group to provide input and detail as to their thoughts @everybody
Obsolete Parts Below
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
|
...