[Wiki Front Page] Pages FeedConfluence Syndication Feedhttps://wiki.covesa.globalWeekly Agenda and Meeting NotesErik Jaegervalltag:wiki.covesa.global,2009:page-51052575-762024-03-28T15:49:01Z2022-12-08T14:26:51Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~erik.jaegervall
">Erik Jaegervall</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<h1 id="WeeklyAgendaandMeetingNotes-MeetingAgenda">Meeting Agenda</h1><ul><li>Welcome and Compliance statement</li></ul><p>Welcome to the COVESA Data Expert Group</p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(0,0,0);"> to be an</span> open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics</li></ul><ul><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-03-28">Meeting notes 2023-03-28</h1><ul><li>VISS<ul><li>Paul: Want to know status</li><li><a class="external-link" href="https://github.com/COVESA/vehicle-information-service-specification" rel="nofollow">https://github.com/COVESA/vehicle-information-service-specification</a></li><li><a class="external-link" href="https://github.com/COVESA/vissr" rel="nofollow">https://github.com/COVESA/vissr</a></li><li>Action to create PDF created by Erik, but PDFs are a bit ugly</li><li>Draft process/governance at <a class="external-link" href="https://github.com/COVESA/vehicle-information-service-specification/wiki/VISS-Governanance-and-Release-Process" rel="nofollow">https://github.com/COVESA/vehicle-information-service-specification/wiki/VISS-Governanance-and-Release-Process</a></li><li>We need to discuss with Ulf/Ted after AMM on way forward for VISS after v2</li><li>Stephen: Would be good if spec and implementation has a backlog</li></ul></li><li>AMM<ul><li>Folder with template and for upload <a class="external-link" style="text-decoration: none;text-align: left;" href="https://drive.google.com/drive/folders/1yaf1-wp4_1kaXAUDwNheY8AI53Wmyn8W?usp=sharing" rel="nofollow">https://drive.google.com/drive/folders/1yaf1-wp4_1kaXAUDwNheY8AI53Wmyn8W?usp=sharing</a></li><li>Erik/Adnan/Stephen to prepare draft DEG update (Wed 09.00) slide until next week</li><li>To be reviewed in meeting next week</li><li>Adnan might miss wrap-up Thursday</li><li>Wrap-up to be used to collect findings and action points going forward.</li><li>Paul: Make sure you have your presentation is ready and that the agenda/title/bio/ for your session is OK</li></ul></li><li>Federate Organization -(focusing on European public funded project) - Paul was involved in a discussion<ul><li>Rolling 3 year projects</li><li>Adnan: More calls will come from EU, next in line is middleware</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-03-21">Meeting notes 2023-03-21</h1><ul><li><a href="https://www.eventleaf.com/Attendee/Attendee/EventSession?eId=E%2FSSgkNJRIKah4DapvxnWw%3D%3D&ssnId=137154" class="external-link" rel="nofollow">Data Expert Group Working Session - Status Update</a><ul><li>How do we want to handle it</li><li>Ford/Blackberry presentations</li><li><p>1. What has been done since last AMM</p><p>2. What is the focus/being done at this AMM</p><p>3. What is the focus until next AMM</p></li><li>Agenda<ul><li>Intro: 5 minutes (Erik)<ul><li>Way of working</li></ul></li><li><a class="confluence-userlink user-mention" data-username="erik.jaegervall" href="https://wiki.covesa.global/display/~erik.jaegervall" data-linked-resource-id="363989" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Erik Jaegervall</a> : VSS+methods, VISS, ... (10 min)</li><li><a class="confluence-userlink user-mention" data-username="stephen.lawrence" href="https://wiki.covesa.global/display/~stephen.lawrence" data-linked-resource-id="361705" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Stephen Lawrence</a> : Architecture, Playground (10 min)</li><li> <a class="confluence-userlink user-mention" data-username="adnan.bekan@bmwgroup.com" href="https://wiki.covesa.global/display/~adnan.bekan@bmwgroup.com" data-linked-resource-id="34209860" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Adnan Bekan</a> : Vehicle API, AUTOSAR, CVI (10 min)</li><li>Questions & Discussions: 10 min<ul><li>Pillars and leads - need for reorg? To be continued to be discussed at wrap up at end of AMM</li></ul></li></ul></li><li>Label: Shall it be "working session" or something else ("technical presentation"?)</li><li>Material to be ready at latest Thursday before AMM for review</li><li>AP: Paul to create google drive folder</li></ul></li><li><a href="https://www.eventleaf.com/Attendee/Attendee/EventSession?eId=E%2FSSgkNJRIKah4DapvxnWw%3D%3D&ssnId=137882" class="external-link" rel="nofollow">Data Expert Group Review and Wrap-Up</a><ul><li>Just informal?</li></ul></li><li>VSS session wednesday (Pierre Pierre) possibly to be moved to Thursday morning (replacing the 9.00 open source session), AP: Paul to check with PP</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-03-07">Meeting notes 2023-03-07</h1><ul><li>Decision to cancel meeting March 14th due to collision with RemotiveLabs spotlight</li><li>Walkthrough of <a class="external-link" href="https://github.com/orgs/COVESA/projects/1" rel="nofollow">https://github.com/orgs/COVESA/projects/1</a><ul><li>Decision: Make project public (all has read access), if possible make Stephen/Adnan/Erik admin, give regular DEG participans write access</li><li>AP: Paul to make it public</li></ul></li><li>Also <a class="external-link" href="https://github.com/COVESA/data-expert-group" rel="nofollow">https://github.com/COVESA/data-expert-group</a> where have issues<ul><li>Make them public, review who has write/admin access</li><li>Paul: What gets into a DEG repo apart from issue</li><li>Stephen: Could be diagrams</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-02-29">Meeting notes 2023-02-29</h1><ul><li>Central Data Service Playground now very close to minimum viable product<ul><li>Operational: As we spin up things like online documentation makes sense to both leverage existing experience with say VSS and to do it in a consistent way with what exists to ease overall maintenance, e.g. similar operational patterns.<ul><li>Any existing artifacts we can leverage?</li><li>Tips, e.g. CI?</li></ul></li><li>Review: Will be increasingly asking people to try, review and give feedback.</li><li>Wider eco-system: Will be considering examples and connection of "lego" to other parts of Covesa eco-system.</li><li><a class="external-link" href="https://github.com/COVESA/cdsp" rel="nofollow">https://github.com/COVESA/cdsp</a></li></ul></li><li>Discuss Covesa approach to images in Docker Hub<ul><li>Need to understand what is required to upstream and maintain images of Covesa tech in Docker Hub</li><li>Any group experience we can leverage?</li></ul></li><li>Something related to VISS project transfer from W3C?<ul><li><a class="external-link" href="https://github.com/COVESA/vissr" rel="nofollow">https://github.com/COVESA/vissr</a></li></ul></li><li>Bosch open source pages mentions VSS - <a href="https://opensource.bosch.com/" class="external-link" rel="nofollow">https://opensource.bosch.com/</a></li><li>ChargeX</li><li>How to "refactor" meetings<ul><li>Not many subject or participants lately</li><li>Change to bi-weekly or on need basis (cancel if no agenda)?</li><li>Paul: Board wants to see the big picture, that is the topic of this meeting</li><li>Erik: Please propose topics for future DEG meetings</li><li>Erik: Possibly revive the backlog at <a class="external-link" href="https://github.com/orgs/COVESA/projects/1" rel="nofollow">https://github.com/orgs/COVESA/projects/1</a></li></ul></li><li>AMM<ul><li>DEG Update -message, discussion topics,</li><li>Proposal from Carina</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-02-15">Meeting notes 2023-02-15</h1><ul><li>VISS governance<br/><ul><li>If we want to handle VISS as a "standard", do we need a stricter process for merging changes and releasing new versions (compared to for example VSS)? Like formal review period, formal vote in TST?</li></ul></li><li>AMM Agenda</li><li>AMM Agenda - proposal from Carin<ul><li><em><span style="color: rgb(29,28,29);">With regards to planning for AMM agenda there was one idea / wish I had on the agenda that I'd like to run by the three of you... Many of the VSS sessions at AMMs are (and should be!) related to quite nitty gritty development by the working group. However; at the session I've been I've heard the repeated frustration from developers, mostly at OEMs, for how to match signals from proprietary ones to VSS in an efficient way. I've brought up the idea with our developers that it would be interesting with a brainstorming session at AMM Gothenburg or co-problem ideation for generating different potential solution paths for how to work efficiently /methodology / tooling /AI tests etc. The feedback from RemotiveLabs engineers was "we'd like to participate in such a sessions (we have ideas and even tickets for this internally ), but currently we are not equipped /prepared to lead such a session". For your information, we are planning to join the meeting in Gothenburg with 4-5 people (2-3 of which engineers i.e. you don't have to put up with only me and Emil this time hahah )... so I guess what I'm trying to do is propose to you guys if you like the idea that COVESA VSS chairs sets up a slot for this? (i.e. RemotiveLabs not involved more than anyone else who joins). Then anyone can take 5 minutes to explain an idea / proposals but to be a session where experiences and ideas are shared to connect further. Does this make sense? I think it would complement the other types of VSS sessions.</span></em></li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-TopicBacklog:">Topic Backlog:</h1><ul><li>Catena-X - shall we approach them? Do we want to collaborate, and if so how.<ul><li>Discussion January 2024?</li><li>TODO: Identify possible alternatives from technical/organizational perspective</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-02-08">Meeting notes 2023-02-08</h1><ul><li>Introduction<ul><li>Rachel Dismuke - Abalta</li></ul></li><li>AMM<ul><li><a href="https://wiki.covesa.global/display/WIK4/AMM+202404+Technical+Track+Session+Proposals">AMM 202404 Technical Track Session Proposals</a></li><li>Do we see a need for more time for DEG than the official agenda?<ul><li>Current assumption: Slots in official agenda are enough</li></ul></li><li>For privacy/consent - what does OEM want COVESA to do?</li></ul></li><li>Stellantis Deep Dive<ul><li>Feb 14th, ask paul if you want to join</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-02-01">Meeting notes 2023-02-01</h1><ul><li>AMM<ul><li>VSS Customization/Extension for commercial vehicles proposal (Erik/Ulf)- <a href="https://wiki.covesa.global/display/WIK4/AMM+202404+Technical+Track+Session+Proposals">AMM 202404 Technical Track Session Proposals</a></li><li>Cv BoF</li><li>Technical agenda available at <a href="https://wiki.covesa.global/display/WIK4/AMM+202404+Technical+Track+Planning">AMM 202404 Technical Track Planning</a></li></ul></li><li>COVESA Website update in progress</li><li>IEEE sensing group<ul><li><a class="external-link" href="https://standards.ieee.org/industry-connections/activities/ieee-iot-sensors-advisory-committee/" rel="nofollow">https://standards.ieee.org/industry-connections/activities/ieee-iot-sensors-advisory-committee/</a></li><li><a href="https://standards.ieee.org/wp-content/uploads/2023/03/IC23-001-01-IoT-Sensors-Advisory-Committee.pdf" class="external-link" rel="nofollow">https://standards.ieee.org/wp-content/uploads/2023/03/IC23-001-01-IoT-Sensors-Advisory-Committee.pdf</a></li></ul></li><li>Playground</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-01-25">Meeting notes 2023-01-25</h1><ul><li>VISS and API error codes - idea to have COVESA proposal/template</li><li>AMM<ul><li>Proposal table (open): <a href="https://wiki.covesa.global/display/WIK4/AMM+202404+Technical+Track+Session+Proposals">AMM 202404 Technical Track Session Proposals</a></li><li>Detailed planning (currently locked): <a href="https://wiki.covesa.global/display/WIK4/Weekly+Agenda+and+Meeting+Notes">Weekly Agenda and Meeting Notes</a></li><li>Root: <a href="https://wiki.covesa.global/display/WIK4/All+Member+Meeting+Planning">All Member Meeting Planning</a></li></ul></li><li>COVESA meeting with KTM</li><li>VSS branch discussion - <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/704" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/704</a></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-01-18:">Meeting notes 2023-01-18:</h1><ul><li>Catena-X<ul><li>Paul: We want at least an organizational connection to Catena-X, I need to names to reach out to</li><li>AP: Erik to check internally at Bosch on whom from Catena-X to contact.</li></ul></li><li>CES<ul><li>SDV Alliance (COVESA, SOAFEE, AUTOSAR, Eclipse SDV)</li></ul></li><li>AMM</li><li>Data Service Playground</li><li>VISS/W3C<ul><li>VISS (w3c automotive group will cease to exist), will be taken over by COVESA</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-12-14:">Meeting notes 2023-12-14:</h1><ul><li>Cancelled due to FMS meeting!</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-12-07:">Meeting notes 2023-12-07:</h1><ul><li>CV BoF</li><li>Next meeting<ul><li>CES Jan 9th-12th</li><li><strong>Next meeting Jan 18th!</strong></li><li>AP: <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> to remove all cancelled meetings</li></ul></li></ul><p><br/></p><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-11-09:">Meeting notes 2023-11-09:</h1><ul><li>FMS<ul><li>Meeting 14th Dec, driven by CV BoF</li><li>We need to monitor what impacts it will have on VSS catalog</li><li>Erik: Would be good if CV BoF could bring back to VSS a few possible changes, so we can discuss how well it fit to current VSS.</li><li>Ted: Data sampling campaign and how it can be represented is a possible topic</li></ul></li><li>SDV Alliance Demonstrator<ul><li>Trying to show pieces from COVESA/SDV/SOAFEE/AUTOSAR</li></ul></li><li>Ford/Alan has created a PR with VSS extensions, see <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/685" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/685</a><ul><li>We will need to discuss how to consider the extensions</li><li>If "official extensions" we need to agree how they shall be used in standard catalog and how tools should use them</li><li>If "inofficial", like a profile, we need to find a way on how to document profile extensions to VSS syntax</li></ul></li><li>Ted presented<ul><li><a class="external-link" href="https://www.w3.org/2023/11/proposed-web-networks-charter.html" rel="nofollow">https://www.w3.org/2023/11/proposed-web-networks-charter.html</a></li><li><p><a href="https://wiki.covesa.global/download/attachments/51052575/VSS_workshop_comments.pdf?version=1&modificationDate=1698329173345&api=v2" data-linked-resource-id="83689514" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="VSS_workshop_comments.pdf" data-nice-type="PDF Document" data-linked-resource-content-type="application/pdf" data-linked-resource-container-id="51052575" data-linked-resource-container-version="76">https://www.w3.org/2023/11/proposed-wg-das.html</a></p></li></ul></li><li><a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">https://github.com/orgs/COVESA/projects/1</a><ul><li>Erik: Start regular cleaning of it, possible quarterly, make sure at least Erik/Adnan/Stephen is present</li><li>AP: Erik to find a date for a cleanup before new year, taking one of the regular meetings,</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-11-02:">Meeting notes 2023-11-02:</h1><ul><li>FMS<br/><ul><li>Meeting Dec 14th (15-17 CET), 6 heavy duty truck manufacturers in EU, only OEMs</li><li>Idea: VSS could replace parts of FMS</li><li>Prep meeting?</li><li>Paul: How do we handle this? What does this mean?</li><li>Erik: Maybe we need a new format to support more extensive signal desxriptions</li><li>Erik: We could discuss possible cooperation methods, like:<ul><li>Every discussion handled in vss project meeting, FMS has no role</li><li>VSS refers to FMS standard, "FMS" owns the definition</li></ul></li></ul></li><li>Chargex<ul><li><a href="https://inl.gov/chargex/" class="external-link" rel="nofollow">https://inl.gov/chargex/</a></li><li>They are interested in VSS</li><li>Meeting in 3 weeks, want to learn about VSS</li></ul></li><li>Vehicle API</li><li><a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">https://github.com/orgs/COVESA/projects/1</a></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-10-26:">Meeting notes 2023-10-26:</h1><ul><li>Vehicle API<ul><li>AUTOSAR says: They will work in WG-CLD, everyone needs to be member</li><li>Paul: Good if they use VSS; but not really open</li></ul></li><li>Demonstrator (Fab4) - AUTOSAR-SOAFEE-COVESA-Eclipse SDV<ul><li>Work on finding a meeting slot in progress, candidate slots:<ul><li><p>2 November 1600 CET / 1000 US ET / 0700 US PT</p><p>3 November 1600 CET / 1000 US ET / 0700 US PT</p><p>6 November 1700 CET / 1100 US ET / 0800 US PT</p></li></ul></li></ul></li><li>VSS-VHAL Mapping<ul><li>COVESA has a mapping in "paused" state</li><li>Bosch has interest</li><li>Bosch has also a repo (<a href="https://github.com/eclipse-kuksa/kuksa-android-sdk" class="external-link" rel="nofollow">https://github.com/eclipse-kuksa/kuksa-android-sdk</a>) for direct access to VSS signals as an alternative solution</li><li>Adnan: Would be good if Bosch could show how KUKSA could be use to access hw-related data for Bosch components</li></ul></li><li>Common vehicle Interfaces<ul><li>First define blueprint, guiding principles, rather than agreeing on tools</li></ul></li><li>VSS release<ul><li>5.0 + 4.1</li><li>Static UID handling, official pull request (for 5.0) in progress, small demo next VSS tuesday meeting</li><li>Erik: If we think 2 weeks to merge UID, then 2 weeks release prep that means release candidate end of november, final release 2 weeks after.</li></ul></li><li>Simulation/Replay using VSS<ul><li>There is interest in starting a group/BoF</li><li>Jeff: Interested to see how we fit into VSS, plugin to connect optimization tool to read VSS signals.</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meetingnotes2023-10-19:">Meeting notes 2023-10-19:</h1><ul><li>AMM Followup<ul><li>Slides: <a href="https://wiki.covesa.global/display/WIK4/COVESA+All+Member+Meeting+~+October+10-12%2C+2023">COVESA All Member Meeting ~ October 10-12, 2023</a></li><li>Forbes articles<ul><li><a href="https://www.forbes.com/sites/edgarsten/2023/10/11/covesa-looks-to-topple-auto-software-tower-of-babel/" class="external-link" rel="nofollow">https://www.forbes.com/sites/edgarsten/2023/10/11/covesa-looks-to-topple-auto-software-tower-of-babel/</a></li><li><a href="https://www.forbes.com/sites/samabuelsamid/2023/10/12/general-motors-open-sources-interfaces-for-new-software-platform/?sh=383e27daa30d" class="external-link" rel="nofollow">https://www.forbes.com/sites/samabuelsamid/2023/10/12/general-motors-open-sources-interfaces-for-new-software-platform/?sh=383e27daa30d</a></li></ul></li><li>VSS Workshop<ul><li>AP: Erik to summarize comments (see <a href="https://wiki.covesa.global/download/attachments/51052575/VSS_workshop_comments.pdf?version=1&modificationDate=1698329173345&api=v2" data-linked-resource-id="83689514" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="VSS_workshop_comments.pdf" data-nice-type="PDF Document" data-linked-resource-content-type="application/pdf" data-linked-resource-container-id="51052575" data-linked-resource-container-version="76">VSS_workshop_comments.pdf</a>)</li></ul></li><li>Stephen - Should we go back to kanban board?<ul><li>AP: Everyone encouraged to clean-up until next week</li><li><a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">https://github.com/orgs/COVESA/projects/1</a></li><li>If you need/want access talk to <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> </li></ul></li><li>24/7 communication - slack?<ul><li>In VSS we have github issues/PRs, works quite well, but not many follows/comments</li><li>Ted: w3c slack to be merged into COVESA slack (AP <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> )</li><li>Do campaign when done</li></ul></li><li>Data arch - central data service proposal - there is interest to get it going</li><li>Discusssion on protobuf handling in VSS</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-10-05:">Meeting Notes 2023-10-05:</h1><ul><li>AMM</li><li>Common vehicle interface meeting<ul><li>Tomorrow round w Google, in a few weeks with Apple</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-09-28:">Meeting Notes 2023-09-28:</h1><p><br/></p><ul><li>AMM<ul><li>Agenda</li></ul></li><li>Blackberrry/Ford presentations<ul><li>Erik/Adnan/Paul to discuss - discussion page (restricted access) at <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=78840091">VSS Presentation and Proposal Feedback, Questions, and Actions</a></li><li>AMM VSS Working session Thursday afternoon</li><li>AP: Check with Blackberry and Ford presenters if they will be present Thursday afternoon</li></ul></li><li>Summary of interface pillar discussions</li><li>AUTOSAR collaboration status (Vehicle API)<ul><li>Joint meeting WG-MT & WG-CLD today, VSS model representation discussion</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-09-21:">Meeting Notes 2023-09-21:</h1><ul><li>AMM<ul><li>Architecture/Infrastructure Agenda: <a href="https://wiki.covesa.global/display/WIK4/Architecture+and+Infrastructure+Meeting+Minutes">Architecture and Infrastructure Meeting Minutes</a></li><li>DEG Presentation, See <a href="https://drive.google.com/drive/folders/1FpoxtZktITTI13GmZKcJDxCOci_piUur" class="external-link" rel="nofollow">https://drive.google.com/drive/folders/1FpoxtZktITTI13GmZKcJDxCOci_piUur</a></li></ul></li><li>Blackberry presentation<ul><li>Please read/review</li><li>AP: Paul to create wiki page to discuss Ford/Blackberry presentations and possible changes to VSS</li></ul></li><li>Follow-up<ul><li>Ford:<ul><li>AP Erik/adnan - No progress?</li><li>Presentation available at <a href="https://wiki.covesa.global/display/WIK4/Data+Models+and+Ontologies#DataModelsandOntologies-ProposalsandPresentations">Data Models and Ontologies#ProposalsandPresentations</a></li></ul></li><li>Catena-X<ul><li>AP erik - no progress</li></ul></li><li>Copyright<ul><li>AP Paul - no progress?</li></ul></li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-09-14">Meeting Notes 2023-09-14</h1><ul><li>Ford proposal discussion<ul><li>Adnan: Would good be discuss with their system architect - how it would affect real project use and deployment</li><li>Adnan: versioning/governance?</li><li>Erik: Should we identify topic-areas and questions, and share VSS background for those areas, as input to dicussing alternatives and way forward with Ford</li><li>Paul to share presentation/recording</li><li>Erik: Could we use a wiki page to collect questions.</li><li><a href="https://us06web.zoom.us/rec/share/WEXvkRfiFMfYCA_wNS9jjEK5sEw1iLkdkNVR2jw3lV6q0Q6yaIt-8z-2e9TlwBdj.mDeosF2rEQfdd7nM?startTime=1694523800000" class="external-link" rel="nofollow">https://us06web.zoom.us/rec/share/WEXvkRfiFMfYCA_wNS9jjEK5sEw1iLkdkNVR2jw3lV6q0Q6yaIt-8z-2e9TlwBdj.mDeosF2rEQfdd7nM?startTime=1694523800000</a><br/>Passcode: #+wbA5dy</li><li>Adnan: Lets discuss in DEG and come back with answers/alternatives</li><li>Erik/Adnan: We will setup a date for internal discussion when we have read the presentation</li></ul></li><li>Catena-X (<a href="https://catena-x.net/en/" class="external-link" rel="nofollow">https://catena-x.net/en/</a>)<ul><li>They have expressed an interest to talk to DEG, reserve time at normal meeting?</li><li>Paul: We both do a short presentation for each other</li><li>Tim: Would like to know more about start/goal/roadmap</li><li>Erik: Will check with them on suitable time to discuss</li></ul></li><li>Copyright (<a href="https://github.com/COVESA/vehicle_signal_specification/pull/643" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/643</a>)<ul><li>Paul: Steve suggest to discuss with OSO Gerald Spreitz, is a board level decision</li><li>Paul: Will set up discussion with Gerald, and I will inform TST</li></ul></li><li>AMM<ul><li>Check out official event site, that it seems to be ok</li><li>Propose change/additions as needed</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-09-07">Meeting Notes 2023-09-07</h1><ul><li>IAA Munich<ul><li>Adnan reported</li></ul></li><li>AUTOSAR WG-CLD<ul><li>COVESA Invited, meetings every Thursday 11-13 CET</li></ul></li><li>AMM<ul><li>Confirmed participation: Erik, Paul, Adnan, Ted, Ulf, Sebastian</li><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71073822">Internal planning page for COVESA AMM October 2023</a></li><li><a href="https://wiki.covesa.global/display/WIK4/Technical+Track+-+Working++Internal+planning+page+for+COVESA+AMM+October+2023">Technical Track - Working Internal planning page for COVESA AMM October 2023</a></li><li>Erik to create data Expert Group session draft, ready by Oct 6th<ul><li>Early draft to be discussed in this meeting next week</li><li>Template at <a href="https://drive.google.com/drive/folders/1FpoxtZktITTI13GmZKcJDxCOci_piUur" class="external-link" rel="nofollow">https://drive.google.com/drive/folders/1FpoxtZktITTI13GmZKcJDxCOci_piUur</a></li></ul></li><li><span style="color: rgb(153,204,0);">Vehicle Common Interfaces -sessions<br/></span><ul><li><span style="color: rgb(153,204,0);">Adnan to check with Halim to propose an agenda for the AMM sessions</span></li></ul></li><li><span style="color: rgb(0,0,0);">Should we have a session on "VSS catalog evolvement", to discuss topics like whether ODB shall be removed and so on...</span></li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-08-17">Meeting Notes 2023-08-17</h1><ul style="list-style-type: square;"><li>AMM topics should be updated on the wiki<ul style="list-style-type: square;"><li><a href="https://wiki.covesa.global/display/WIK4/AMM+Planning+October+10-12+2023+-+Technical+Session+and+Workshop+Proposals">AMM Planning October 10-12 2023 - Technical Session and Workshop Proposals</a></li></ul></li><li>RTTI<ul style="list-style-type: square;"><li>Will show demo on how to use VSS and DDS.</li></ul></li><li>Decision to take the break for next two weeks. We resume meetings in first week of September.</li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-08-10">Meeting Notes 2023-08-10</h1><ul><li>F2F meeting for service API and tooling.<ul><li>Notes<ul><li>Adnan: preference mid of november</li><li>Sebastian: ETAS would be able to organise event</li></ul></li></ul></li><li>AMM<ul><li>Notes<ul><li>Sebastian: Shall we extend half a day with session?</li><li>Paul: we have chance to go for Monday/<strong>Tuesday</strong>/<strong>Friday.</strong></li><li>Paul: Submit idea for AMM until end of august.</li></ul></li></ul></li><li>Service capabilities, name.<br/><ul><li>Notes<ul><li>Adnan: Vehicle API Hub for SDV</li><li>Ted: Vehicle Defined Interfaces</li><li>Sebastian: General Vehicle API</li><li>Sebastian: Common Vehicle Interfaces</li></ul></li></ul></li><li>How VSS is used?<ul><li>Notes<ul><li>Ulf: Last AMM we presented Kuksa and ViSS.</li><li>Paul: Others as well could provide input. How to motivate?</li><li>Adnan: We also have to understand what is the need. Companies should start explaining.</li><li>Sebastian: challenge is not lack of material, but a way how to present this.</li><li>Stephen: We have documentation, we just have to do the work.</li></ul></li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-07-27">Meeting Notes 2023-07-27</h1><ul><li>Information: Erik on vacation August 1st -Sept 1st</li><li>VSS review Monday Jul 31, 2023 ⋅ 3pm – 7pm (Central European Time - Berlin)<ul><li><a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmeet.google.com%2Feox-sqze-byx%3Fhs%3D224&data=05%7C01%7Cerj1lud%40bosch.com%7C00031ea7335541138eda08db8de8fafd%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C638259803998153991%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RhBjuzNLn7ovdbkUG7Lx1kMaC0RyP7P7kTEq4xHD9UY%3D&reserved=0" class="external-link" rel="nofollow">meet.google.com/eox-sqze-byx</a></li><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71074350">Vehicle Signal Specification Review Workshop</a> (Access restricted)</li><li>Stephen: Board request to do a review, first meeting next week. There are some old categories that require review.</li><li>Erik: Better to discuss/define principles rather than explicit existing signals.</li></ul></li><li>Diagram/Document Storage (Stephen)<ul><li><span style="color: rgb(29,28,29);">There has been some discussion before, but with the rise in reuse of our materials as shown last week we need to move towards a solution to encourage reuse. I'll be creating a git rep for the Data Architecture/Infrastructure work, but there is the bigger picture of the Data EG, AOSP and Covesa as a whole. Illustration where does someone go to get current Covesa Data Expert Group scope diagram?</span></li><li><span style="color: rgb(29,28,29);">Erik: There have been discussion in the past, possibly use github rather than wiki. I created a draft (restricted access) at <a href="https://github.com/COVESA/data-expert-group" class="external-link" rel="nofollow">https://github.com/COVESA/data-expert-group</a> some time ago</span></li><li><span style="color: rgb(29,28,29);">Halim: Could generate from git</span></li></ul></li><li><span style="color: rgb(29,28,29);">Interface/API way forward</span><ul><li><span style="color: rgb(29,28,29);">Adnan: </span><ul><li><span style="color: rgb(29,28,29);">Have one stream on IFEX, clear goal to define scope of IFEX. </span></li><li><span style="color: rgb(29,28,29);">One part on catalog/operations, also covering the service API. Discussion can start happening. Try to skip the "catalog" name</span></li><li><span style="color: rgb(29,28,29);">Need to find a catchier name, start looking at proposals</span></li></ul></li><li><span style="color: rgb(29,28,29);">Stephen: Putting in context is useful</span></li><li><span style="color: rgb(29,28,29);">Adnan: With IFEX i could glue things together</span></li><li><span style="color: rgb(29,28,29);">Adnan: Would be good if Halim could collect some areas that would be use to describe</span></li><li><span style="color: rgb(29,28,29);">Adnan: Unsure if IFEX is mature enough. We need to have a definition of "final result"</span></li><li><span style="color: rgb(29,28,29);">Erik: Even if we trust IFEX concept, we should define the "input format" or "output format" that shall IFEX needs to work with</span></li><li><span style="color: rgb(29,28,29);">Adnan: Contribution to a Data Expert Group blogpost would be very welcome. Inform Adnan if you are interested.</span></li></ul></li><li><span style="color: rgb(29,28,29);">Way forward:</span><ul><li><span style="color: rgb(29,28,29);">Paul: Maybe use VSC timeslot ys for regular meetings</span></li><li><span style="color: rgb(29,28,29);">Halim: We can start w Monday schedule, decide on other afterwards. Fridays would be better.</span></li><li><span style="color: rgb(29,28,29);">Adnan: Paul to drop Doodle poll</span></li><li><span style="color: rgb(29,28,29);">Pual: next meeting on this topic Monday 31st 19.00 CET 10AM Pacific (VSC timeslot and link)</span></li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-07-20">Meeting Notes 2023-07-20</h1><ul><li>Agenda 25th<ul><li>Info from Ulf (pasted to <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshops - Interface Pillar Alignment</a>)</li><li>Adnan: Will GM and Aptiv participate<ul><li>Richard Fernandes (GM): Planned that Halim will partipcate</li><li>Tim Welsch: Aptiv: yes</li></ul></li><li>Promote/Reminder (Paul?)</li><li>Cancellation of VSS next week (Can Paul do it?)<ul><li>AP: Erik to check with Paul</li></ul></li></ul></li><li>September meeting<ul><li>Seems feasible for Bosch/ETAS to have it next to ETAS connection, we can discuss more on Tuesday</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-07-13">Meeting Notes 2023-07-13</h1><ul><li>Online discussion July: </li><li><a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshops - Interface Pillar Alignment</a></li><li><p><em>Paul: Per our discussion last week, I propose that we have an online workshop from <strong>14:00 -16:00cet / 8am - 12pm ET / 5am - 9am PT on July 25th</strong>. Would that work for everyone?</em></p><ul><li><em>Erik:ok, </em></li><li><em>Ulf: Not so ok (vacation that week and some days before), maybe, week after would work</em></li><li><em>Adnan: It would work, can ping colleagues next week</em></li><li><em>Stephen: Would be OK</em></li><li><em>Tim: OK</em></li><li><em>Ted: OK</em></li><li><em>Erik: Maybe we shall go for 25th, even if some cannot join, there will always be some people that cannot join.</em></li><li><em>AP: Check with Gunnar (Erik can do)</em></li><li><em>Erik: What would be agenda for 25th, it is only 2 hours</em></li><li><em>Adnan: Align what people are expecting, what do they like see at end of succesful projects. We can go through active activities.</em></li><li><em>Adnan: Erik you could describe what you from Bosch would like to see, we can do similar from BMW side.</em></li><li><em>Decision: Have virtual meeting 25th, Erik to check if Paul want to send out invite.</em></li><li><em>Stephen: Important to align what people are expecting, possibly keep it technology agnostic.</em></li><li><em>Adnan: Two goals</em><ol><li><em>Aspect of common catalog</em></li><li><em>Tooling for translation</em><em>Use them as base for the discussion</em></li></ol></li></ul></li><li>September meeting<ul><li>F2F if enough persons are interested. Candidate is Sept 26 Stuttgart-area (before ETAS connection, Bosch/ETAS can most likely arrange a room)</li><li>AP: All check if the can join in person, virtual, or not al all<ul><li>Add participation to: <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshops - Interface Pillar Alignment</a></li></ul></li></ul></li><li>AMM<ul><li>Please indicate on <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshops - Interface Pillar Alignment</a> if you can and want to join a full day before the AMM</li></ul></li><li>Stephen: AUTOSAR Vehicle API things will be started again</li><li>Vacation planning:<ul><li>Adnan off 1-4th Aug and 19th Aug - 3rd September</li><li>Erik off 1st Aug - 3rd September</li><li>Stephen possibly off 26th-28th, nothing more in August</li><li>Stephen as backup chair for this meeting when Erik and Adnan is off.</li><li>But anyone can act as chair, but good if you have wiki write-access</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-07-06">Meeting Notes 2023-07-06</h1><ul><li>F2F<ul><li>No meeting Cologne in July<ul><li>But shall we have a web meeting around that time? 18th afternoon?</li></ul></li><li>Alternative F2F Dates/places<ul><li>Sept 26 Stuttgart-area (before ETAS connection, Bosch/ETAS can most likely arrange a room)</li><li>Lund, Sweden (next to Copenhagen), anytime, Bosch can most likely arrange a room</li><li>Other alternatives/proposals...</li></ul></li><li>Refactor <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshop Face to Face: July 18 and/or 19, 2023 Cologne, Germany - Interface Pillar Alignment</a> with new proposals, or create a new one?</li></ul></li><li>Notes:<ul><li>2-3 hours online session, Week of 17-21st July? or 24-27th? Erik and Adnan to sync and propose based on result. (board 19th and 20th)<ul><li>Paul 24th and 25th preferred</li></ul></li><li>F2F-date; Or Monday (October 9th) at AMM?<ul><li>Erik: If doing it AMM we should maybe have a virtual session in (early-mid) September as well</li></ul></li><li>Adnan: Want to have the (small) european group F2F in september, larger follow up at AMM.<ul><li>AP: Erik and Adnan to check internally on reasonable dates for a September F2F.</li></ul></li><li>Setephen: We need to have different lanes; IFEX/IDL is one, catalog another one. We need to define trhe lanes and make sure all are discussed.</li></ul></li><li>Vehicle API way forward</li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-06-29">Meeting Notes 2023-06-29</h1><ul><li>F2F<ul><li>Decision needed</li><li>No room</li><li>Paul: Possibly not the required mass of people</li><li>Adnan: These dates proposed due to board meeting, makes coordination simpler</li><li>Adnan: Ask people on how they want to contribute to the work, and then plan session<ul><li>Each party adds 2-3 bullet points</li></ul></li><li>Erik: So sync first, then agree on date?</li><li>Paul: Wants to know what everyone wants to contribute</li><li>Erik: Would it be better to aim for early September, to be able to decide on date on venue in advance</li><li>Paul: Will check for a hotel conference room, if not feasible reschedule for later, possibly at a member site</li></ul></li><li>HIM<ul><li><a href="https://github.com/COVESA/hierarchical_information_model" class="external-link" rel="nofollow">https://github.com/COVESA/hierarchical_information_model</a></li><li><a href="https://covesa.github.io/hierarchical_information_model/" class="external-link" rel="nofollow">https://covesa.github.io/hierarchical_information_model/</a></li></ul></li><li>Design Pattern<ul><li>Moving along, hopefully finished next week</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-06-22">Meeting Notes 2023-06-22</h1><p>Discussion Topics</p><ul><li>F2F - <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshop Face to Face: July 18-19, 2023 Cologne, Germany - Interface Pillar Alignment</a><ul><li>Current status; dates, venue, participants, ...<ul><li>COVESA Board 19-20 July</li><li>Alignment w AUTOSAR/SOAFEE/COVESA 18th</li></ul></li><li>Discussion (FTI <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> )<ul><li>Participation list updated. Will Ford/Ulf participate?</li><li>What is reason to let DEG and Board meeting overlap</li><li>Would having the DEG discussion on Monday be an option?</li><li>Lets continue discussion in Slack</li></ul></li></ul></li><li>Ted: Should we have a JSON viewer to allow easy navigation of the catalog.</li><li>Stephen: DEG Git repository - reluctant to create a big DEG Architecture repo. We need somewhere to put the markdown. Maybe "data-arch-doc".<ul><li>Will prepare a proposal</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-06-15">Meeting Notes 2023-06-15</h1><ul><li>Discussion Topics<br/><ul><li>Stephen presented <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71073902">Design Pattern / Data Architecture documentation proposal</a> </li><li>HIM & IFEX<ul><li>Ulf: Service taxanomy can possible be shared, but serves partially different purposes.</li><li>Ulf: HIM gives a possibility to describe procedure signatures, similar to how VSS describe signals, which then can be used by interface design like VISS</li><li>Ulf: I think we need a RPC model</li><li>Adnan: Service definition could reference other models, like referencing VSS position</li><li>Gunnar: Are you talking about abstract service/function definition, or more specific that can be generated to real service implementations/stubs</li><li>Adnan: I see VISS like an API definition, IFEX more as an IDL that be converted to a lot of things</li><li>Gunnar: If there is VISS API that supports RPC, it could be generated from IFEX</li><li>Gunnar on IFEX:<ul><li>Hierarchical namespace</li><li>A concept "interface" that specifies methods, properties, ... A combination of things we intend to expose that we can use to define a callable API</li><li>Namespaces of methods often related to software architecture, possibly we could have multiple hierachies.</li></ul></li><li>Gunnar: We need to identify what is missing</li><li>Adnan: Has studied IFEX VSS proposal, wants something more standardized compared to Franca, like Yaml/JSON-based. A framework that allows to import multiple inputs, like ARXML, Android, and generate to various formats.</li><li>Adnan: Possible technical track on next board f2f-meeting, (Cologne 19-20 July, SOAFEE/AUTOSAR 18th)</li><li>Gunnar: How we can support AUTOSAR in IFEX</li></ul></li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-06-08">Meeting Notes 2023-06-08</h1><ul><li>Prioritized topics for next meeting<ul><li>HIM&IFEX to be discussed June 15th</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-06-01">Meeting Notes 2023-06-01</h1><ul><li>Discussion<ul><li>"Ulf/HIM proposal" (Hierarchical Information Model)</li></ul></li></ul><p><em style="text-align: left;">1. Decide on name for the evolved data model.</em><br style="text-align: left;"/><em style="text-align: left;">2. Create a new COVESA Github repo based on the new name.</em><br style="text-align: left;"/><em style="text-align: left;">3. Decide on a directory structure that can accommodate rule set definitions for multiple domains and multiple information types.</em><br style="text-align: left;"/><em style="text-align: left;">4. Create a rudimentary README on the top level giving a high level description of the new data model.</em><br style="text-align: left;"/><em style="text-align: left;">5. Move the VSS "rules definition" (the documentation) from the VSS repo to an appropriate directory on this new repo.</em><br style="text-align: left;"/><em style="text-align: left;">6. Create a rule set for services that that meets the requirements from the "passenger car domain" (VSS).</em><br style="text-align: left;"/><em style="text-align: left;">7. On the VSS repo, create an initial service tree based on the rule set from the bullet above. Continue to evolve it in parallell with the existing VSS tree.</em><br style="text-align: left;"/><em style="text-align: left;">8. Analyze the impact on VSS-Tools that the above has, take action on the insights from that.</em><br style="text-align: left;"/><em style="text-align: left;">9. Try to influence the W3C automotive group to evolve VISSv2 to support the new data model.</em><br style="text-align: left;"/><em style="text-align: left;">10. If successful on the above bullet, create a new COVESA project that will develop a POC containing a technology stack based on the evolved W3C interface and COVESA data model.</em></p><ul><li style="list-style-type: none;"><ul><li style="list-style-type: none;"><ul><li>Discussion:<ul><li>Ulf: Could be soft started as VSS subproject</li><li>Ulf: Do not see HIM file as input to vss-tools, it is the server that consumes it, it still work with initial trees</li><li>Erik: Suggestion:<ul><li>Let Paul create a HIM repo (M/W/X)</li><li>Ulf to start working with repo, describe motivation, idea, and suggested increments/roadmap and basic architecture<ul><li>Describe what problem we intend to solve, why do we create it.</li></ul></li><li>Then let DEG discuss at regular interval, keep VSS meeting informed</li><li>When mature we can discuss how to involve more people</li></ul></li><li>Decision: OK for Paul to create repo</li><li>Discuss relationship to VCS when we have the parts above ready</li></ul></li></ul></li><li>Adnan: SDV and Eclipse</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-05-11">Meeting Notes 2023-05-11</h1><ul><li>Welcome and Compliance statement</li></ul><p>Welcome to the COVESA Data Expert Group</p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(0,0,0);"> to be an</span> open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li style="list-style-type: none;"><ul><li>API project - see <p><a href="https://wiki.covesa.global/display/WIK4/VSS+Meeting+Topics+and+Meeting+Notes">VSS Meeting Topics and Meeting Notes</a></p></li><li><a href="https://wiki.covesa.global/download/attachments/51052575/S2S-api_COVESA_V1.pptx?version=1&modificationDate=1683814006794&api=v2" data-linked-resource-id="64979593" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="S2S-api_COVESA_V1.pptx" data-nice-type="PowerPoint Presentation" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-linked-resource-container-id="51052575" data-linked-resource-container-version="76">S2S-api_COVESA_V1.pptx</a></li><li>Discussion:<ul><li>Paul: What do we want to explore needs to be defined. Start with a call with member - what do people want.</li><li>Erik: We need a realistic roadmap - what are people prepared to do? what can we achieve until next AMM or within next 12 months</li></ul></li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-05-04">Meeting Notes 2023-05-04</h1><ul><li>Welcome and Compliance statement</li></ul><p>Welcome to the COVESA Data Expert Group</p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(0,0,0);"> to be an</span> open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li style="list-style-type: none;"><ul><li>AMM Lessons Learned</li><li>Next AMM October 10th-12th, Troy, Mi, USA</li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-04-20">Meeting Notes 2023-04-20</h1><ul><li>Welcome and Compliance statement</li></ul><p>Welcome to the COVESA Data Expert Group</p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(0,0,0);"> to be an</span> open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>AMM<ul><li>EV-charging session</li></ul></li><li>Friday agenda<ul><li>9.00-14.00</li><li>Confluence page: <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+-+Workshop+20230428+-+Spring+AMM+-+In+Person">Data Expert Group - Workshop 20230428 - Spring AMM - In Person</a></li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-04-13">Meeting Notes 2023-04-13</h1><ul><li>Welcome and Compliance statement</li></ul><p>Welcome to the COVESA Data Expert Group</p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(0,0,0);"> to be an</span> open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>AMM<ul><li>DEG slides updated, VSC not mentioned</li></ul></li><li>Repository - best practices<ul><li>Paul will start describring the process.</li></ul></li><li>Friday agenda<ul><li>9.00-14.00</li><li>Confluence page: <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+-+Workshop+20230428+-+Spring+AMM+-+In+Person">Data Expert Group - Workshop 20230428 - Spring AMM - In Person</a></li><li>Items added</li></ul></li><li>Technical Steering Team - possible work split (AMM Friday?)</li><li><a href="https://github.com/COVESA/ifex" class="external-link" rel="nofollow">https://github.com/COVESA/ifex</a></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-04-06">Meeting Notes 2023-04-06</h1><ul><li>Welcome and Compliance statement</li></ul><p>Welcome to the COVESA Data Expert Group</p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(0,0,0);"> to be an</span> open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>AMM<ul><li>AP: Erik to remove "negative" part, check with Gunnar for actual plan</li></ul></li><li>Repository - best practices<ul><li>Paul will start describring the process.</li></ul></li><li>Friday agenda<ul><li>9.00-14.00</li><li>Paul to create confluence page</li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-MeetingNotes2023-03-30">Meeting Notes 2023-03-30</h1><ul><li>Compliance statement - TBD</li><li><p><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong><br style="text-align: left;"/><span style="color: rgb(29,28,29);">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.</span></p><p><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong><br style="text-align: left;"/><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(255,153,0);"> to be an</span> open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></p></li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>EV Charging Repo<ul><li>See <a href="https://github.com/COVESA/data-expert-group/issues/7" class="external-link" rel="nofollow">https://github.com/COVESA/data-expert-group/issues/7</a></li><li>Decisions:<ul><li>Create repo - ev_charging<code class="notranslate"> (or similar)</code><ul><li>AP Paul: Create repo and make Erik admin</li></ul></li><li>Suggest them to present their ideas/results for the DEG.</li></ul></li></ul></li><li>AMM<ul><li>Data Expert Group Presentation<ul><li><a href="https://docs.google.com/presentation/d/1iHwvC595g40eHk60BBotpsYaq6RrJb3E/edit#slide=id.p1" class="external-link" rel="nofollow">https://docs.google.com/presentation/d/1iHwvC595g40eHk60BBotpsYaq6RrJb3E/edit#slide=id.p1</a></li><li>We want to state workshop happened</li><li>Overall architecture and deployment scenarios agreed</li><li>Complex structs introduced into VSS</li><li>Whole wednesday track to be mentioned</li><li>Friday DEG internal working session</li></ul></li></ul></li><li>Compliance<ul><li>Was typo (see organe above)</li><li>IPR policy rework in progress</li><li>Link to text good so we have a "master" that we can copy and add to invites</li><li>Shall be read at start of meetings.</li></ul></li><li>EU initiative<ul><li>Workshop next week</li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-03-23">Meeting 2023-03-23</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li><em>AMM</em><ul><li><em>AMM presentation folder: <a href="https://drive.google.com/drive/folders/1Sf1wCf6v_qFM6gnHa1qu7AdIA6jLrQcg" class="external-link" rel="nofollow">https://drive.google.com/drive/folders/1Sf1wCf6v_qFM6gnHa1qu7AdIA6jLrQcg</a></em></li><li><em>Expected that template in that folder is used</em></li><li><em>Deployment Scenario Session Approach<br/></em><ul><li><em>Erik has added a draft presentation in the folder above. Erik will refactor images taken from Miro</em></li></ul></li><li><em>Data Architecture Workshop</em><ul><li><em>Stephen presented intended contents, see <a href="https://wiki.covesa.global/display/WIK4/Architecture+and+Infrastructure+Meeting+Minutes">Architecture and Infrastructure Meeting Minutes</a></em></li></ul></li><li><em>Friday Agenda - possible topics</em><ul><li><em>Release Planning?</em></li><li><em>Vehicle API</em></li><li><em>Governance - how to document decisions?</em></li><li><em>AP Paul: Create "page" for Friday. What to discuss - who is there...</em></li></ul></li></ul></li><li><em>Encourage colleagues to register to AMM</em></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-03-16">Meeting 2023-03-16</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li><em>AMM</em><ul><li><em>Agenda walkthrough</em></li><li><em>Vehicle API session?</em></li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-02-23">Meeting 2023-02-23</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li><em>Struct support - VSS and APIs<br/></em><ul><li><em>Example: Struct support in VISS not explicitly stated, likely not complex, need json representation<br/></em></li><li><em>AP: Erik to bring it up to VISS</em></li><li><em>Adnan expressed concern on struct usage</em></li><li><em>Ulf: guidance to be added to documentation.</em></li></ul></li><li><em>Atomic read/write of multiple signals</em><ul><li><em>Topic brought up by Bosch - recommendation/required for APIs?</em></li></ul></li><li><em>Stream Support <br/></em><ul><li><em>Events or Video/Audio?</em></li></ul></li><li><em>VehicleAPI</em><ul><li><em>Proposal documentation from erik: <a href="https://github.com/COVESA/data-expert-group" class="external-link" rel="nofollow">https://github.com/COVESA/data-expert-group</a></em></li></ul></li><li><em>AMM</em></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-02-09">Meeting 2023-02-09</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Adnan presents Vehicle diagram with zones and ethernet backbone<ul><li>Which integration points do we want to handle</li><li>COVESA scope<ul><li>Between zones</li><li>Zones to HU/TCU/COMPUTING</li><li>Communication from HU/TCU to Mobile/Cloud</li><li>For use-cases, what do we see as COVESA requirements</li></ul></li></ul></li><li>Vehicle API<ul><li>We can move forward internally.</li></ul></li><li>Workshop Feb 15th -16th - <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+-+Workshop+2023+-+Q1">Data Expert Group - Workshop 2023 - Q1</a><ul><li>See page</li></ul></li><li>AMM</li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-02-02">Meeting 2023-02-02</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Workshop Feb 15th -16th - <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+-+Workshop+2023+-+Q1">Data Expert Group - Workshop 2023 - Q1</a><ul><li>See page</li></ul></li><li>AMM</li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-01-26">Meeting 2023-01-26</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li></ul><p>Prioritized topics</p><ul><li style="list-style-type: none;"><ul><li>Workshop Feb 15th -16th<ul><li>Agenda<ul><li>AMM Topics</li><li>Release Planning</li><li>Way forward - Best Practices and Howtos</li><li>Vehicle API</li><li>Data Expert Group Retrospective<ul><li>What has worked well</li><li>What has not worked well</li></ul></li></ul></li><li>Ted: Create a poll, find people who can lead the topics</li><li>AP: Paul to put it on COVESA calender</li><li>Paul: Focus on ws shall be data expert group</li><li><a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+-+Workshop+2023+-+Q1" rel="nofollow">Confluence page created</a><ul><li><span style="color: rgb(255,0,0);"><strong>AP: All to propose subjects on confluence page until next week.</strong></span></li><li>Next week create rough agenda</li></ul></li></ul></li><li>AMM in Porto, Portugal, 25-27th April (Tuesday-Thursday)<br/><ul><li>Possibly assemble data expert group the day before or after for workshop</li><li>Ulf: Could be Tuesday morning, AMM typically starts at noon</li><li><span style="color: rgb(255,0,0);"><strong>AP: Everyone to check when they likely will/can arrive/leave, to find suitable slots</strong></span></li><li>Stephen: Board meeting might be on Tuesday morning</li><li>Paul: Board meetings Tuesday and Thursday mornings, according to Steve</li><li>Ulf: Then better to have our meeting Monday morning.</li><li>AP: Paul to create confluence page for planning</li></ul></li><li>VSS Schedule</li><li>Sign-offs<ul><li>All shall follow <a href="https://www.covesa.global/contribute" class="external-link" rel="nofollow">https://www.covesa.global/contribute</a></li><li>Github has check support, possibly could be inspired by W3C solution.</li><li>See <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository" class="external-link" rel="nofollow">https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository</a></li><li>AP: Paul to investigate what can be done on organizational level</li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting<ul><li>Workshop and AMM</li></ul></li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-01-19">Meeting 2023-01-19</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li><p>Roadmap Items - List them out in priority</p><ul><li>Possible items<ul><li>Best practices</li><li>Implementation guides</li></ul></li><li>Paul presented powerpoint</li></ul></li><li><p>Workshop - let’s get agreement on this and set it up</p><ul><li><a href="https://github.com/COVESA/data-expert-group/discussions/5" class="external-link" rel="nofollow">https://github.com/COVESA/data-expert-group/discussions/5</a></li><li><a href="https://github.com/COVESA/data-expert-group/discussions/6" class="external-link" rel="nofollow">https://github.com/COVESA/data-expert-group/discussions/6</a></li><li>Feb 15th -16th selected (<p>5 - 9am PT</p><p>1400-1700 CET</p><p>6:30-10:30pm IST</p><p>10pm - 2am JST)</p></li><li>Topics for first workshop<ul><li>Define roadmap, see above</li></ul></li></ul></li><li>Resources</li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-01-12">Meeting 2023-01-12</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Online Workshops (Paul, <a href="https://github.com/COVESA/data-expert-group/issues/4" class="external-link" rel="nofollow">https://github.com/COVESA/data-expert-group/issues/4</a>)<ul><li>See notes in issue</li><li>Paul presented ideas:</li><li><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="250" src="https://wiki.covesa.global/download/attachments/51052575/image2023-1-12_16-47-29.png?version=1&modificationDate=1673538450849&api=v2" data-image-src="https://wiki.covesa.global/download/attachments/51052575/image2023-1-12_16-47-29.png?version=1&modificationDate=1673538450849&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="54165569" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="image2023-1-12_16-47-29.png" data-base-url="https://wiki.covesa.global" data-linked-resource-content-type="image/png" data-linked-resource-container-id="51052575" data-linked-resource-container-version="76" alt=""></span></li><li>Ulf: Often difficult to find information on homepage, it should be possible to find a page for each project from home page. Then we can start to fill out.</li><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> : To create a poll for date</li><li>Stephen: Next week data architecture meeting will discuss topics for a workshop</li></ul></li><li>S<s>pring AMM planning</s></li><li><s>Presentation to board concerning VSS</s></li><li><s>COVESA-AUTOSAR charter - move to *.md repo (idea from Stephen)?</s></li></ul></li><li><s>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</s></li><li><s>Prioritized topics for next meeting</s></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2023-01-05">Meeting 2023-01-05</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>AUTOSAR -COVESA Collaboration<ul><li>Erik has updated charter with proposed deliverables, to be reviewed by Sami from AUTOSAR Cloud WG Group</li><li>Initial comments from Sami received, see <a href="https://github.com/COVESA/data-expert-group/issues/2" class="external-link" rel="nofollow">https://github.com/COVESA/data-expert-group/issues/2</a></li><li>Erik/Paul/Adnan to have meeting w Sami next two Fridays, in preparation for next steering group call</li><li>Ulf to present vehicle API proposal at the internal meeting Tuesday next week</li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Prioritized topics for next meeting</li><li>Date for next monthly report discussion</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2022-12-15">Meeting 2022-12-15</h1><p><br/></p><ul><li>Compliance statement<ul><li>TBD: Discussion ongoing on what needs to be informed at start of the meeting.</li></ul></li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>AUTOSAR sync meeting tomorrow<ul><li>Erik: Discussion last Friday w Erik, Adnan, Sami, see <a href="https://wiki.covesa.global/display/WIK4/Meeting+notes+from+Joint+meetings" rel="nofollow">notes</a></li><li>Stephen: What was decided on board meeting</li><li>Paul: Likely continue with/without AUTOSAR, lets see tomorrow</li><li>Erik: What does really exist in AUTOSAR, only specs but also implementation</li><li>Stephen: In Adaptive reference implementation of drivers</li><li>Stephen: Good mentioning VISS, but not be to prescriptive</li><li>Stephen: Good to have simulator for if AUTOSAR is black box</li><li>Stephen: Does not necessarily need to be Linux, could be any RTOS, does not matter for architecture</li><li>Erik: But matters for PoC</li><li>Ulf: Do not think the VehicleAPI shall be VISS, it is too complex, shall be thin. But VISS shall be easily be integratable on top of it.</li><li>Ulf: API abstracts details, Data Mapper shall not be too interesting from COVESA perspective.</li><li>Ulf: AUTOSAR might come with input to VSS catalog</li><li>Erik: Has scope of PoC been discussed?</li><li>Paul: No!</li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Info: Cancelled meeting due to New Year<ul><li>Meetings cancelled: Dec 22nd, Dec 29th</li><li>Sync on available participants for Jan 5th on Slack just before, cancel if needed</li></ul></li><li>Information<ul><li>Paul is going to propose big blocks related to roadmap handling. We shall say where we want to be for next AMM (Europe late April- early May).</li><li>Stephen going on vacation tomorrow</li></ul></li><li>Prioritized topics for next meeting</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2022-12-08">Meeting 2022-12-08</h1><p><br/></p><ul><li>Compliance statement<ul><li>Discussion ongoing on what needs to be informed at start of eah meeting.</li></ul></li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Monthly report to Board<ul><li>Currently handled informally by Paul</li><li>Paul can publish the slide he use for reporting, so DEG members can add/review as needed</li></ul></li></ul></li><li>Walk through ongoing topics in “<a href="https://github.com/orgs/COVESA/projects/1" class="external-link" rel="nofollow">Backlog/Kanban Board</a>”. Each Pillar should have a work product their group is working toward and status.</li><li>Cancelled meeting due to New Year<ul><li>Meetings cancelled: Dec 22nd, Dec 29th</li><li>Sync on available participants for Jan 5th on Slack just before, cancel if needed</li></ul></li><li>Information<ul><li>Workshop being planned for architecture pillar</li></ul></li><li>Prioritized topics for next meeting</li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2022-09-29">Meeting 2022-09-29</h1><h2 id="WeeklyAgendaandMeetingNotes-Participants">Participants</h2><p>Erik, Paul, Adnan, Joby, Stephen, Ted, Ulf</p><h2 id="WeeklyAgendaandMeetingNotes-Declined">Declined</h2><p>Tim Grieshammer</p><h2 id="WeeklyAgendaandMeetingNotes-ProposedAgenda">Proposed Agenda</h2><ul><li>Continued discussion on presentations for AMM<ul><li><a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Working+Internal+planning+page+for+COVESA+AMM+October+2022" rel="nofollow">Data Expert Group Working Internal planning page for COVESA AMM October 2022</a></li></ul></li><li>Review of presentation materials created so far.</li></ul><p><br/></p><h2 id="WeeklyAgendaandMeetingNotes-MinutesofMeetings">Minutes of Meetings</h2><ul><li>AMM Schedule<ul><li>General overview planned right now for 09.00-10.20</li><li>Agreed to reduce to 50-60 minutes</li><li>Adnan to prepare draft slides until next week, will synch with Erik</li><li>1 hour session for DEG leads at end of day</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2022-09-15">Meeting 2022-09-15</h1><h2 id="WeeklyAgendaandMeetingNotes-Participants.1">Participants</h2><p>Erik, Paul, Joby, Stephen, Ted</p><h2 id="WeeklyAgendaandMeetingNotes-Declined.1">Declined</h2><p>Tim Grieshammer</p><h2 id="WeeklyAgendaandMeetingNotes-ProposedAgenda.1">Proposed Agenda</h2><ul><li>Working model (at least until AMM)</li><ul><li>Agree on what shall be discussed in expert Group Meeting vs. subproject meetings (VSS, VSC, security, CVII, …)</li><li>Meeting frequency, time and dates</li></ul><li>What do we want to achieve until AMM<ul><li>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)</li><li>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 </li></ul></li><ul><li>Proposal from my side:</li></ul><li>AMM presentations and sessions – see <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Working+Internal+planning+page+for+COVESA+AMM+October+2022" rel="nofollow">https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Working+Internal+planning+page+for+COVESA+AMM+October+2022</a></li><li>If time permits, sync on status of all activities belonging to Data Expert Group</li></ul><p><br/></p><h2 id="WeeklyAgendaandMeetingNotes-MinutesofMeetings.1">Minutes of Meetings</h2><ul><li>Keep weekly meeting at this slot.</li><li>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.<ul><li>If possible, send to Erik in advance</li></ul></li><li>Next week discuss:<ul><li>Quick review of slides mentioned above, any gaps/inconsistencies, e.g. projects falling between the pillars.</li><li>AMM sessions - does plan need to be updated?</li></ul></li></ul><h1 id="WeeklyAgendaandMeetingNotes-Meeting2022-08-30">Meeting 2022-08-30</h1><p><br/></p><h5 id="WeeklyAgendaandMeetingNotes-Attendees">Attendees</h5><ul><li>Adnan Bekan</li><li>Erik Jaegervall</li><li>Joby Jester</li><li>Krishna Koppolu</li><li>Paul Boyes</li><li>Sebastian Schildt</li><li>Stephen Lawrence</li><li>Ted Guild</li><li>Thomas Spreckley</li><li>Tim Grieshammer</li></ul><h5 id="WeeklyAgendaandMeetingNotes-Notes">Notes</h5><p>Walk through overview of Data Expert Group with question and answer</p><ul><li>Discussed mapping of existing activities to group (see diagram in Charter above). Explained goal is not to disrupt current activities</li><li>Discussed distinctions between Security, Privacy, and Personal Privacy. Work to be done.</li><li>Discussed ideas for desired next steps.</li></ul><p><br/></p><p>Identified and confirmed the following leadership:</p><ul><li>Group Co-Chair, Best Practices Lead - <a class="confluence-userlink user-mention" data-username="erik.jaegervall" href="https://wiki.covesa.global/display/~erik.jaegervall" data-linked-resource-id="363989" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Erik Jaegervall</a></li><li>Group Co-Chair - TBD </li><li>Architecture/Infrastructure Lead - <a class="confluence-userlink user-mention" data-username="stephen.lawrence" href="https://wiki.covesa.global/display/~stephen.lawrence" data-linked-resource-id="361705" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Stephen Lawrence</a> </li><li>VSS Lead - <a class="confluence-userlink user-mention" data-username="adnan.bekan@bmwgroup.com" href="https://wiki.covesa.global/display/~adnan.bekan@bmwgroup.com" data-linked-resource-id="34209860" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Adnan Bekan</a>, <a class="confluence-userlink user-mention" data-username="Sebastian.Schildt@de.bosch.com" href="https://wiki.covesa.global/display/~Sebastian.Schildt@de.bosch.com" data-linked-resource-id="362542" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Sebastian Schildt</a> </li><li>VSC Lead - Tim Grieshammer</li><li>Security and Privacy Lead - Joby Jester</li></ul><p><br/></p><p>Discussed October AMM schedule.</p><p><br/></p><h5 id="WeeklyAgendaandMeetingNotes-NextSteps/ActionItems">Next Steps/Action Items</h5><ul><li>Coordinate next meeting <a class="confluence-userlink user-mention" data-username="erik.jaegervall" href="https://wiki.covesa.global/display/~erik.jaegervall" data-linked-resource-id="363989" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Erik Jaegervall</a> <ul><li>Topics:<br/><ul><li>Way of working and deliverables</li><li>6 month roadmap</li><li>AMM Presentation</li><li>Additional Group Co-Chair</li></ul></li></ul></li><li>Communication plan <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> </li><li>October AMM Scedule<ul><li>Create working copy for group <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a></li><li>Group to provide input and detail as to their thoughts @everybody</li></ul></li></ul>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/display/WIK4/Weekly+Agenda+and+Meeting+Notes">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=51052575&revisedVersion=76&originalVersion=75">View Changes Online</a>
</div>
</div>Erik Jaegervall2022-12-08T14:26:51ZAutomotive AOSP App Framework Standardization Expert GroupRichard Fernandestag:wiki.covesa.global,2009:page-64978970-1162024-03-27T20:23:24Z2023-03-20T23:06:17Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~richard.fernandes@gm.com
">Richard Fernandes</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<h1 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-GeneralInformation"><strong><style type='text/css'>/*<![CDATA[*/
div.rbtoc1711644959354 {padding: 0px;}
div.rbtoc1711644959354 ul {margin-left: 0px;}
div.rbtoc1711644959354 li {margin-left: 0px;padding-left: 0px;}
/*]]>*/</style><div class='toc-macro rbtoc1711644959354'>
<ul class='toc-indentation'>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-GeneralInformation'>General Information</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-MeetingNotes'>Meeting Notes</a>
<ul class='toc-indentation'>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-1stApril2024-Meetingcancelled'>1st April 2024 - Meeting cancelled</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-25thMarch2024-Agenda'>25th March 2024 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-18thMarch2024-Agenda'>18th March 2024 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-11thMarch2024-Meetingcancelled'>11th March 2024 - Meeting cancelled</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-26thFebruary2024-Agenda'>26th February 2024 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-19thFebruary2024-Agenda'>19th February 2024 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-12thFebruary2024-Meetingcancelled'>12th February 2024 - Meeting cancelled</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-5thFebruary2024-Agenda'>5th February 2024 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-29thJanuary2024-PushNotificationWorkshop(NoWeeklymeeting)'>29th January 2024 - Push Notification Workshop (No Weekly meeting)</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-22ndJanuary2024-Agenda'>22nd January 2024 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-15thJanuary2024-Agenda'>15th January 2024 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-4thDecember2023-Agenda'>4th December 2023 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-27thNovember2023-Agenda'>27th November 2023 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-20thNovember2023-Agenda'>20th November 2023 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-13thNovember2023'>13th November 2023</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-6thNovember2023'>6th November 2023</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-23rdOctober2023-Agenda'>23rd October 2023 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-16thOctober2023-Agenda'>16th October 2023 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-25thSeptember2023-Agenda'>25th September 2023 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-11thSeptember2023-Agenda'>11th September 2023 - Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-4thSeptember2023-CancelledduetopublicholidayinUS'>4th September 2023 - Cancelled due to public holiday in US</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-28thAugust2023-Cancelledbychairsduetokeypeoplebeingout.'>28th August 2023 - Cancelled by chairs due to key people being out.</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-21stAugust2023-MeetingAgenda'>21st August 2023 - Meeting Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-7thAugust2023-MeetingAgenda'>7th August 2023 - Meeting Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-31stJuly2023-MeetingAgenda'>31st July 2023 - Meeting Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-24thJuly2023-MeetingAgenda'>24th July 2023 - Meeting Agenda</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-17thJuly2023-Meetingcancelled'>17th July 2023 - Meeting cancelled</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-10thJuly2023-VirtualMeeting'>10th July 2023 - Virtual Meeting</a></li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-22June2023-FacetoFaceWorkshop'>22 June 2023 - Face to Face Workshop</a></li>
</ul>
</li>
<li><a href='#AutomotiveAOSPAppFrameworkStandardizationExpertGroup-Charter'>Charter</a></li>
</ul>
</div></strong><strong>General Information</strong></h1><p><strong><em>Welcome to the COVESA Automotive AOSP App Framework Standardization Expert Group Meeting!</em></strong></p><p><strong>Weekly Meeting:</strong> Monday, 5-6pm CEST (<a href="https://www.google.com/url?q=https://us06web.zoom.us/j/88558270170?pwd%3DbeQr4XUnWs3aikWXZLau75Uh5Re9QC.1&sa=D&source=calendar&ust=1698609819189293&usg=AOvVaw3sKr5zP8C8KsLoDC4WyZbF" class="external-link" rel="nofollow">Zoom Link</a>) (<a href="https://wiki.covesa.global/display/WIK4/COVESA+Common+Meeting+Schedule" rel="nofollow">Subscribe to Community Calendar</a> to stay up to date)</p><p><strong>Slack:</strong> <a href="https://covesacommunity.slack.com/archives/C05EB6A6J5R" class="external-link" rel="nofollow">https://covesacommunity.slack.com/archives/C05EB6A6J5R</a></p><p><strong>GitHub:</strong> <a href="https://github.com/COVESA/aosp-app-framework-standardizatiion" class="external-link" rel="nofollow">https://github.com/COVESA/aosp-app-framework-standardizatiion</a></p><p><strong>Chairs:</strong></p><ul><li><a class="confluence-userlink user-mention" data-username="Melina.Mascolo@bmw.de" href="https://wiki.covesa.global/display/~Melina.Mascolo@bmw.de" data-linked-resource-id="71074083" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Melina Mascolo</a> , BMW</li><li><a class="confluence-userlink user-mention" data-username="richard.fernandes@gm.com" href="https://wiki.covesa.global/display/~richard.fernandes@gm.com" data-linked-resource-id="71074084" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Richard Fernandes</a> , General Motors</li><li><a class="confluence-userlink user-mention" data-username="gabriel.gautron@forvia.com" href="https://wiki.covesa.global/display/~gabriel.gautron@forvia.com" data-linked-resource-id="90406971" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Gabriel Gautron</a> , FORVIA</li></ul><p><strong><span style="color: rgb(29,28,29);">Compliance statement:</span></strong></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the<span> </span><a href="https://covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><h1 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-MeetingNotes"><strong>Meeting Notes</strong></h1><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-1stApril2024-Meetingcancelled"><strong>1st April 2024 </strong><strong>- Meeting cancelled</strong></h2><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-25thMarch2024-Agenda"><strong>25th March 2024 - Agenda</strong></h2><ul><li>AMM agenda update - Richard/Co-Chair</li><li>Push Notification: Unified Push update - Gabriel/Co-Chair</li><li>Round table discussion</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-18thMarch2024-Agenda"><strong>18th March 2024 - Agenda</strong></h2><ul><li>Push Notification: Unified Push discussion - Co-Chairs and group members<ul><li>Agreement to invite Unified Push members to April AMM for the Push Notification discussion meeting.</li></ul></li><li>Entertainment - Video Streaming discussion - Tomek/3SS<ul><li>3SS will provide more information based on group members feedback by April AMM or maybe sooner.</li></ul></li><li>Round table discussion - Migrating Android code CR#334 <<a class="external-link" href="https://github.com/COVESA/vss-tools/pull/334" rel="nofollow">https://github.com/COVESA/vss-tools/pull/334</a>> - Richard/Co-Chair<ul><li>Group members in agreement to close CR.</li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-11thMarch2024-Meetingcancelled"><strong>11th March 2024 - Meeting cancelled</strong></h2><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-26thFebruary2024-Agenda"><strong>26th February 2024 - Agenda</strong></h2><ul><li>In-Vehicle Payments BOF discussion - Vamsi Putrevu/Mavi.io</li><li>Discuss AMM agenda sessions and Panel topics for this group (April 16-18th, Sweden).</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-19thFebruary2024-Agenda"><strong>19th February 2024 - Agenda</strong></h2><ul><li>Follow up on 3SS presented topic from February 5th.</li><li>Discuss Next Steps on UnifiedPush for Push Notification.</li><li>Discuss AMM agenda sessions for this group (April 16-18th, Sweden).<ul><li><p>Proposal:</p><p>"Quo vadis white label app stores - how to evolve the automotive app ecosystem"</p><ul><li>Where are we today (How many apps are available, which apps are available, do we see further growth)? What learnings do we already have?</li><li>What can we learn from other emerging/emerged ecosystems? What are potential reasons for failure?</li><li>What can be done to prevent failure and facilitate additional growth?</li><li>...</li></ul></li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-12thFebruary2024-Meetingcancelled"><strong>12th February 2024 - Meeting cancelled</strong></h2><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-5thFebruary2024-Agenda"><strong>5th February 2024 - Agenda</strong></h2><ul><li>Intro from 3SS about Entertainment topics needing standardization (including an OEM and App Store Provider survey)<ul><li><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/2401-3SS-COVESA-Video_Track_Initiative-Intro-Final.pdf?version=1&modificationDate=1707232265955&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/2401-3SS-COVESA-Video_Track_Initiative-Intro-Final.pdf?version=1&modificationDate=1707232265955&api=v2" data-linked-resource-id="92733585" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="2401-3SS-COVESA-Video_Track_Initiative-Intro-Final.pdf" data-mime-type="application/pdf" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="2401-3SS-COVESA-Video_Track_Initiative-Intro-Final.pdf" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/92733585/1" height="250" alt="" draggable="false" /></a></span><ul><li>Please contact Felix Walter (<a href="mailto:felix.walter@3ss.tv" class="external-link" rel="nofollow">felix.walter@3ss.tv</a> ) and Tomasz Dzikowski (t<a href="mailto:omasz.dzikowski@3ss.tv" class="external-link" rel="nofollow">omasz.dzikowski@3ss.tv</a>) if you would like to get involved in this topic or if you have any questions.</li></ul></li></ul></li><li>Next steps UnifiedPush / Push Notifications</li><li>AMM Session (April in Sweden)</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-29thJanuary2024-PushNotificationWorkshop(NoWeeklymeeting)"><strong>29th January 2024 - Push Notification Workshop (No Weekly meeting)</strong></h2><ul><li>Push Notification Protocol Presentation:<ul><li> <span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/PNS_Workshop_Presentation%201.pptx?version=1&modificationDate=1706731932182&api=v2" data-nice-type="PowerPoint Presentation" data-file-src="https://wiki.covesa.global/download/attachments/64978970/PNS_Workshop_Presentation%201.pptx?version=1&modificationDate=1706731932182&api=v2" data-linked-resource-id="92733495" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="PNS_Workshop_Presentation 1.pptx" data-mime-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="PNS_Workshop_Presentation 1.pptx" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/92733495/1" height="250" alt="" draggable="false" /></a></span></li></ul></li><li>Video Recording of the workshop:<ul><li>Link - <a class="external-link" style="text-decoration: underline;text-align: left;" href="https://us06web.zoom.us/rec/share/6DNS8KdaGcizDDLj64Klj8twB1iqnwaZaUch9OWlbuCBCgtLQG9CYrUwkVGFqzFk.N4MKJDETVVCgC8aD" rel="nofollow">https://us06web.zoom.us/rec/share/6DNS8KdaGcizDDLj64Klj8twB1iqnwaZaUch9OWlbuCBCgtLQG9CYrUwkVGFqzFk.N4MKJDETVVCgC8aD</a><br style="text-align: left;"/><span style="color: rgb(29,28,29);">--Passcode: jw2K2F%Q</span></li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-22ndJanuary2024-Agenda"><strong>22nd January 2024 - Agenda</strong></h2><ul><li>Shorter round: 30min only</li><li>Quick recap for push notifications workshop (29th January) for participants who could not make it last week</li><li>Round table discussions</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-15thJanuary2024-Agenda"><strong>15th January 2024 - Agenda</strong></h2><ul><li><p>Happy new year!</p></li><li>Reminder about push notifications workshop January 29th → Extended invite will follow</li><li>Short overview goal & agenda push notifications workshop<ul><li><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/Workshop_Preperation_WebPush_Proposal.pptx?version=1&modificationDate=1705508647166&api=v2" data-nice-type="PowerPoint Presentation" data-file-src="https://wiki.covesa.global/download/attachments/64978970/Workshop_Preperation_WebPush_Proposal.pptx?version=1&modificationDate=1705508647166&api=v2" data-linked-resource-id="90406972" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="Workshop_Preperation_WebPush_Proposal.pptx" data-mime-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-has-thumbnail="false" data-linked-resource-version="1" data-can-edit="false" aria-label="Workshop_Preperation_WebPush_Proposal.pptx" draggable="false"><img src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/17.19.9/_/download/resources/com.atlassian.confluence.plugins.confluence-view-file-macro:view-file-macro-resources/images/placeholder-medium-presentation.png" height="250" alt="" draggable="false" /><span class="title">Workshop_Preperation_WebPush_Proposal.pptx</span></a></span></li></ul></li><li>Round table discussions</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-4thDecember2023-Agenda"><strong>4th December 2023 - Agenda</strong></h2><ul><li>BMW/Maxi to provide overview of Push Notification Workshop goal (including what to be prepared for and who to bring to the Workshop)<br/>→ Will be published before Christmas on Wiki</li><li>Push Notification Workshop agenda:<ul><li>Mobis and Mercedes to provide feedback on current proposal.</li><li>Does Jan 29th, 2024 work for the group?<ul><li>Confirmed and agreed with the team (Time: 4-6PM/10AM-12PM)</li></ul></li></ul></li><li>External 360 Camera feedback.<ul><li>Feedback from Auto OEM and suppliers.<ul><li>Two sets of images - individual external camera or stitched images from the cameras.<ul><li>Need additional discussion, to be reviewed next year.</li></ul></li></ul></li></ul></li><li>Round table discussions</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-27thNovember2023-Agenda"><strong>27th November 2023 - Agenda</strong></h2><ul><li>Feedback from Mercedes on Camera API discussion (360 degree property)<ul><li>Link to discussion: <a class="external-link" href="https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics#AUTOMOTIVE_LENS_FACING" rel="nofollow">https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics#AUTOMOTIVE_LENS_FACING</a><ul><li>Action Item: Auto OEMs to investigate if the external 360 degree camera is accessible for 3rd Party app developers.</li></ul></li></ul></li><li>Who is planning to join CES 2024 and agenda.<ul><li>Please follow up with Mike Nunnery by December 1st, 2023.</li></ul></li><li>Joint date for push notification workshop → Does doodle work for everyone? Any preferred days in January?<ul><li>Tentative date: January 29th, 2024 (2-3h). Need team agreement.</li><li><u><strong>@All: Please confirm this date until next Monday</strong></u></li></ul></li><li>Meeting schedule for the remainder of the year.<ul><li>Last meeting for this group: December 4th, 2023. Regular meetings to begin January 15th, 2024. </li></ul></li><li>Round table discussions.<ul><li>Harman will publish their emulator in GitHub and give feedback next Monday, when it will be uploaded there.</li><li>Next steps: OEMs/Apps to check out emulator, identify gaps, joint workshop, aligning who will be responsible for which extensions.</li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-20thNovember2023-Agenda"><strong>20th November 2023 - Agenda</strong></h2><ul><li>Bi-weekly new time slot at 1pm (Germany), 7am (Detroit), 9pm (Tokyo), 4am (Los Angeles) to enable Honda to participate<br/>→ Works for everyone?<ul><li>No Concerns from the group.</li></ul></li><li>BMW push notifications update<ul><li>Maxi shared a presentation</li><li><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/Push_Notifcation_Features.pdf?version=1&modificationDate=1700821286120&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/Push_Notifcation_Features.pdf?version=1&modificationDate=1700821286120&api=v2" data-linked-resource-id="85197020" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="Push_Notifcation_Features.pdf" data-mime-type="application/pdf" data-has-thumbnail="false" data-linked-resource-version="1" data-can-edit="false" aria-label="Push_Notifcation_Features.pdf" draggable="false"><img src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/17.19.9/_/download/resources/com.atlassian.confluence.plugins.confluence-view-file-macro:view-file-macro-resources/images/placeholder-medium-pdf.png" height="250" alt="" draggable="false" /><span class="title">Push_Notifcation_Features.pdf</span></a></span></li></ul></li><li>Hyundai Mobis push notifications update<ul><li>Umang shared a presentation:<ul><li> <span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/PUSH%20NOTIFICATION.pptx?version=1&modificationDate=1700585535420&api=v2" data-nice-type="PowerPoint Presentation" data-file-src="https://wiki.covesa.global/download/attachments/64978970/PUSH%20NOTIFICATION.pptx?version=1&modificationDate=1700585535420&api=v2" data-linked-resource-id="85197004" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="PUSH NOTIFICATION.pptx" data-mime-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-has-thumbnail="false" data-linked-resource-version="1" data-can-edit="false" aria-label="PUSH NOTIFICATION.pptx" draggable="false"><img src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/17.19.9/_/download/resources/com.atlassian.confluence.plugins.confluence-view-file-macro:view-file-macro-resources/images/placeholder-medium-presentation.png" height="250" alt="" draggable="false" /><span class="title">PUSH NOTIFICATION.pptx</span></a></span></li></ul></li><li>Chairs to have a follow up meeting to bring Hyundai Mobis up to speed.</li></ul></li><li>January: Push notifications workshop<br/>→ Enable OEMs to bring in experts<ul><li>Looking for feedback from the group in the next meeting</li></ul></li><li>Newcomers updates</li><li>Exploring synergies with in-vehicle payment group</li><li>Are there round table discussions discussion points?<ul><li>Mercedes/Max to provide an update in the next meeting.</li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-13thNovember2023"><strong>13th November 2023</strong></h2><p><strong><span style="color: rgb(255,0,0);">Today's meeting is cancelled. </span></strong></p><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-6thNovember2023"><strong>6th November 2023</strong></h2><p><strong><span style="color: rgb(255,0,0);">Please note that beginning today the invite was switched to Zoom:</span> <a href="https://www.google.com/url?q=https://us06web.zoom.us/j/88558270170?pwd%3DbeQr4XUnWs3aikWXZLau75Uh5Re9QC.1&sa=D&source=calendar&ust=1698609819189293&usg=AOvVaw3sKr5zP8C8KsLoDC4WyZbF" class="external-link" rel="nofollow">Zoom Link</a></strong></p><ul><li><span>Main contact per Automotive OEM</span></li><li><span>Mercedes additional requirements on 360 degree camera and feedback.</span><ul><li><span>No representative from Mercedes, no feedback today.</span></li></ul></li><li><span>Request to have one or more Tier 1 taking over camera reference implementation</span><ul><li><span>To be discussed again next week.</span></li></ul></li><li><span>Push Notification, Next Steps Overview - BMW/Maxi</span><ul><li><span>Discussion pushed to next week as we didn't have all the OEMs</span></li></ul></li><li><span>Emulator Workshop Discussion</span><ul><li><span>Harman to have internal discussion on next steps </span></li></ul></li><li><span>Hyundai/Umang to share Push Notifications alternative proposal - November 20th, 2023</span></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-23rdOctober2023-Agenda"><strong>23rd October 2023 - Agenda</strong></h2><ul><li><span>Update from Mercedes about Push Notifications details about 360 degree camera:</span><ul><li><span>Request to have requirements that will support external 360 degree camera.</span></li><li><span>Mercedes will use their own services. Follow up needed on using COVESA interface (standardized API) - Mercedes feedback by November 6th, 2023.</span></li></ul></li><li><span>Overview from Harman and Snapp about emulator capabilities and alignment on next steps:</span><ul><li><span>Presentation from Saverio Labella/Harman: </span><ul><li><span><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/231023_HarmanIgniteAAOSEmulator.pdf?version=1&modificationDate=1698161537703&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/231023_HarmanIgniteAAOSEmulator.pdf?version=1&modificationDate=1698161537703&api=v2" data-linked-resource-id="78840678" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="231023_HarmanIgniteAAOSEmulator.pdf" data-mime-type="application/pdf" data-has-thumbnail="false" data-linked-resource-version="1" data-can-edit="false" aria-label="231023_HarmanIgniteAAOSEmulator.pdf" draggable="false"><img src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/17.19.9/_/download/resources/com.atlassian.confluence.plugins.confluence-view-file-macro:view-file-macro-resources/images/placeholder-medium-pdf.png" height="250" alt="" draggable="false" /><span class="title">231023_HarmanIgniteAAOSEmulator.pdf</span></a></span></span></li></ul></li><li><p>Link to COVESA Licensing - <a href="https://covesa.global/sites/default/files/COVESA-Public-Policy-for-Open-Source-Licensing.pdf" class="external-link" rel="nofollow">https://covesa.global/sites/default/files/COVESA-Public-Policy-for-Open-Source-Licensing.pdf</a></p></li><li><span>Need to decide as a group, where the emulator will be stored and who will update/maintain the emulator - Feedback from Chairs by November 6th, 2023.</span></li></ul></li><li><span>CES 2024: GM/Mercedes/Cariad regarding panel discussion and vehicle demo:</span><ul><li><span>GM - Decision currently on hold</span></li><li><span>Cariad - Internal discussion on this topic, feedback to follow</span></li><li><span>Mercedes - No plan at this moment</span></li><li><span>CES Registration details:</span><ul><li><span><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="400" src="https://wiki.covesa.global/download/attachments/64978970/image2023-10-23_12-13-54.png?version=1&modificationDate=1698077635798&api=v2" data-image-src="https://wiki.covesa.global/download/attachments/64978970/image2023-10-23_12-13-54.png?version=1&modificationDate=1698077635798&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="78840645" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="image2023-10-23_12-13-54.png" data-base-url="https://wiki.covesa.global" data-linked-resource-content-type="image/png" data-linked-resource-container-id="64978970" data-linked-resource-container-version="116" alt=""></span></span></li><li><p>Pictures from CES 2023, COVESA area - <a href="https://covesa.smugmug.com/COVESA-at-CES2023" class="external-link" rel="nofollow">https://covesa.smugmug.com/COVESA-at-CES2023</a></p></li></ul></li></ul></li><li><span style="color: rgb(29,28,29);">Maxi/BMW to discuss with Vamsi/</span><a href="http://mavi.io/" class="external-link" rel="nofollow"><span>mavi.io</span></a><span style="color: rgb(29,28,29);"> about how to bring both POCs together and how are next steps to define necessary feature set</span><ul><li><span style="color: rgb(29,28,29);">Mavi to follow up with BMW offline on the POC to verify if the API works.</span></li><li><span style="color: rgb(29,28,29);">Mavi to share the API with GM offline, to conduct internal POC and provide feedback.</span></li></ul></li><li><span>Internal and External camera reference implementation support from Tier 1, next steps:</span><ul><li>Faurecia Aptoide to provide feedback by <span>November 6th, 2023</span></li></ul></li></ul><ul><li style="list-style-type: none;"><ul><li>Harman <ul><li>Camera API <ul><li><span>Harman agreed with the Camera API proposal.</span></li><li><span>LENS_FACING_FRONT should be similar to AUTOMOTIVE_LENS_FACING and map to default camera, OEM to decide default mapping for INTERIOR_SEAT_ROW_1_LEFT|RIGHT|CENTER based on model and RHD/LHD</span></li><li><span>If a 3P wants to have finer controls documentation should include information on how to get the VehiclePropertyIds.INFO_DRIVER_SEAT in order to know if the car is RHD or LHD</span></li><li><span>3D surround camera may need specific Camera2 value, OEMs to request it. In the meantime it could be mapped by default to EXTERIOR_OTHER</span></li><li><span>Evaluating Emulator Virtual device support for testing (same virtual scenes + special text overly identifying automotive camera used)</span></li><li><span>3P feedback</span></li><ul><li><span>LENS_FACING_FRONT, LENS_FACING_BACKOk, in the future may consider specific cameras.</span></li></ul></ul><p style="margin-left: 0.375in;"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="400" src="https://wiki.covesa.global/download/attachments/64978970/image2023-10-23_12-5-47.png?version=2&modificationDate=1698077149842&api=v2" data-image-src="https://wiki.covesa.global/download/attachments/64978970/image2023-10-23_12-5-47.png?version=2&modificationDate=1698077149842&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="78840643" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="image2023-10-23_12-5-47.png" data-base-url="https://wiki.covesa.global" data-linked-resource-content-type="image/png" data-linked-resource-container-id="64978970" data-linked-resource-container-version="116" alt=""></span></p></li><li>Push Notification:<ul><li><span>Harman agreed with UnifiedPush proposal.</span></li><li><span>Harman is currently evaluating Common Emulator distributor for testing</span></li><li><span>3P feedback </span><ul><li><span>Using pushing, interesting, may need to check backend change</span></li></ul></li></ul></li></ul></li></ul></li><li><span>Honda and Hyundai: request to know who will participate and need to have an agreed time slot (across 3 time zones):</span><ul><li>Paul/COVESA and Richard/GM to follow up with Honda and Hyundai on this topic.</li></ul></li></ul><ul><li><span>Harman: Feedback from which 3rd Parties they could get feedback about camera /push notifications (e.g. Zoom/WebEx/TikTok)</span><ul><li><span>On going discussion with 3rd party app providers, mostly positive.</span></li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-16thOctober2023-Agenda"><strong>16th October 2023 - Agenda</strong></h2><ul><li>Debrief AMM Detroit: Presentations</li></ul><p><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/2023.10.11%20COVESA%20AOSP%20APP%20FRAMEWORK%20AMM%20OCT23%20%281%29.pptx?version=1&modificationDate=1697471295663&api=v2" data-nice-type="PowerPoint Presentation" data-file-src="https://wiki.covesa.global/download/attachments/64978970/2023.10.11%20COVESA%20AOSP%20APP%20FRAMEWORK%20AMM%20OCT23%20%281%29.pptx?version=1&modificationDate=1697471295663&api=v2" data-linked-resource-id="78840447" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="2023.10.11 COVESA AOSP APP FRAMEWORK AMM OCT23 (1).pptx" data-mime-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-has-thumbnail="false" data-linked-resource-version="1" data-can-edit="false" aria-label="2023.10.11 COVESA AOSP APP FRAMEWORK AMM OCT23 (1).pptx" draggable="false"><img src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/17.19.9/_/download/resources/com.atlassian.confluence.plugins.confluence-view-file-macro:view-file-macro-resources/images/placeholder-medium-presentation.png" height="250" alt="" draggable="false" /><span class="title">2023.10.11 COVESA AOSP APP FRAMEWORK AMM OCT23 (1).pptx</span></a></span><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/2023.10.11-COVESA-AMM-Alternative-to-Push-Notifications-Working-Session.pptx?version=1&modificationDate=1697471298626&api=v2" data-nice-type="PowerPoint Presentation" data-file-src="https://wiki.covesa.global/download/attachments/64978970/2023.10.11-COVESA-AMM-Alternative-to-Push-Notifications-Working-Session.pptx?version=1&modificationDate=1697471298626&api=v2" data-linked-resource-id="78840448" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="2023.10.11-COVESA-AMM-Alternative-to-Push-Notifications-Working-Session.pptx" data-mime-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-has-thumbnail="false" data-linked-resource-version="1" data-can-edit="false" aria-label="2023.10.11-COVESA-AMM-Alternative-to-Push-Notifications-Working-Session.pptx" draggable="false"><img src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/17.19.9/_/download/resources/com.atlassian.confluence.plugins.confluence-view-file-macro:view-file-macro-resources/images/placeholder-medium-presentation.png" height="250" alt="" draggable="false" /><span class="title">2023.10.11-COVESA-AMM-Alternative-to-Push-Notifications-Working-Session.pptx</span></a></span></p><ul><li>New OEMs joining AOSP Expert Group: Honda & Hyundai<br/>→ Asian appropriate timeslot needed<strong><br/></strong></li><li>Harman contact change<br/>→ Update Emulator / Camera API</li><li>Further OEMs needed for push notifications POC</li><li>Which app developers are willing to give input about features for push notifications implementation, besides Zoom/WebEx</li><li>Mercedes<br/>→ Camera API proposal works, however 360 degree camera not covered</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-25thSeptember2023-Agenda"><strong>25th September 2023 - Agenda</strong></h2><ul><li>Participants: Cariad, BMW, General Motors, Volvo, Harman, Faurecia Aptoide/Forvia, GrapeUp, RemotiveLabs, Elektrobit, COVESA, LTTS, Geotab, mavi.io</li><li>Overview expert group activities Detroit AMM</li><li>Mavi.io push notification MVP to be finalized this week<br/>→ More clarifications tbd.</li><li>WebEx is reviewing the push notification solution<br/>→ @Albert (Harman): To discuss with Zoom</li><li>2nd October → Bridge day in Germany: Weekly meeting to be cancelled?<br/>→ Next meeting 16.10.</li><li>Mercedes feedback work streams<br/>→ Camera API: End this week<br/>→ Push Notifications: Within next 2 weeks</li><li>Cariad: No hard date at this point due to internal availabilities</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-11thSeptember2023-Agenda"><strong>11th September 2023 - Agenda</strong></h2><ul><li>Participants: BMW, Cariad, General Motors, Mercedes, Ford, Faurecia Aptoide/Forvia, Intellias, Grapeup, RemotiveLabs, Elektrobit, Jimmy Technologies, Bosch, COVESA, LTTS, mavi.io</li><li>COVESA AMM in Detroit - activites on AOSP app framework standardization<ul><li>11/10<ul><li>9:00-9:45 - Status session to attract potential new members to the expert group. Onsite: Richard, Melina; Online: Camille</li><li>9:45-10:30 - working session on push notifications</li></ul></li></ul></li></ul><p>Members that will attend the working session:</p><ul><li style="list-style-type: none;"><ul><li style="list-style-type: none;"><ul><li>BMW</li><li><a href="http://Mavi.io" class="external-link" rel="nofollow">Mavi.io</a></li><li>GM</li><li>Elektrobit</li><li>Faurecia Aptoide</li></ul></li><li>12/10 pm : Panel discussion</li></ul></li></ul><p>Forvia as Moderator, GM, <a href="http://Mavi.io" class="external-link" rel="nofollow">Mavi.io</a>, STLA, potentially BMW. Open discussion on the topic</p><p>NB: Invitations to the AMM can be provided to companies (3rd party apps developers, OEMs...) that are or not members of COVESA so that they can join the sessions. Email to Mike Nunnery & Paul Boyes to get support in this invitation process</p><p><br/></p><ul><li><p>Presentation Push Notifications POC by BMW</p><ul><li><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/POC_UnifiedPush.pdf?version=1&modificationDate=1694616908791&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/POC_UnifiedPush.pdf?version=1&modificationDate=1694616908791&api=v2" data-linked-resource-id="78839955" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="POC_UnifiedPush.pdf" data-mime-type="application/pdf" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="POC_UnifiedPush.pdf" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/78839955/1" height="250" alt="" draggable="false" /></a></span></li><li><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/POC1_Covesa_Walkthrough.mp4?version=1&modificationDate=1694616924249&api=v2" data-nice-type="Multimedia" data-file-src="https://wiki.covesa.global/download/attachments/64978970/POC1_Covesa_Walkthrough.mp4?version=1&modificationDate=1694616924249&api=v2" data-linked-resource-id="78839956" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="POC1_Covesa_Walkthrough.mp4" data-mime-type="video/mp4" data-has-thumbnail="false" data-linked-resource-version="1" data-can-edit="false" aria-label="POC1_Covesa_Walkthrough.mp4" draggable="false"><img src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/17.19.9/_/download/resources/com.atlassian.confluence.plugins.confluence-view-file-macro:view-file-macro-resources/images/placeholder-medium-multimedia.png" height="250" alt="" draggable="false" /><span class="title">POC1_Covesa_Walkthrough.mp4</span></a></span></li></ul></li></ul><p>Next steps :</p><ul><li style="list-style-type: none;"><ul><li><span>POC walkthrough video can be used as a guideline, links to download apps are in the presentation</span></li><li><strong>All OEMs to test the installation of the 2 apps and the notify backend</strong><ul><li><span>before AMM to share feedback during the working session</span></li><li><span>Outcomes can be shared with members attending if attendance is not possible</span></li></ul></li><li><span><strong>POC by 3rd party apps dev to try to implement (<a href="http://Mavi.io" class="external-link" rel="nofollow">Mavi.io</a>) and provide feedback:</strong> any use case that can be difficult to support with this solution?</span></li><li><span>AMM working session on 11/10</span><ul><li><span style="letter-spacing: 0.0px;">Feedback</span></li><li><span style="letter-spacing: 0.0px;">Define what is missing and thus what COVESA needs to standardize to play those use cases</span></li></ul></li><li><span>Invite UnifiedPush team to join and discuss once common decision is done</span></li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-4thSeptember2023-CancelledduetopublicholidayinUS"><strong>4th September 2023 - Cancelled due to public holiday in US</strong></h2><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-28thAugust2023-Cancelledbychairsduetokeypeoplebeingout."><strong>28th August 2023 - Cancelled by chairs due to key people being out.</strong></h2><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-21stAugust2023-MeetingAgenda"><strong>21st August 2023 - Meeting Agenda</strong></h2><ul><li>Participants: BMW, Ford, General Motors, Mercedes, Volvo, Hyundai, Faurecia Aptoide/Forvia, GrapeUp, Intellias, Elektrobit, COVESA, Geotab</li><li>Paul Boyes: AMM Detroit<ul><li><p><strong>All members</strong> to provide their feedback on AMM Detroit attendance to Paul <strong>by next week</strong></p></li></ul></li><li>Align on CES plans (panel discussion <> vehicle demo)<br/>→ Which participants would be interested?<br/>→ What would we show during the vehicle demo?<ul><li><strong>Paul Boyes</strong> to discuss with Mike + Steve about the possibility to get a separate room at CES</li></ul></li><li>Overview milestone planning camera API & push notification<ul><li><strong>BMW</strong>: Slides to be shared on the wiki + Collaborative document to be prepared for everyone to be able to contribute</li></ul></li></ul><p style="margin-left: 40.0px;">→ <strong>OEM and Store Providers:</strong> timeline input needed </p><ul><li style="list-style-type: none;"><ul><li><strong>FAA / Harman</strong> to align on who reaches out which developer</li></ul></li></ul><p><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/230821_Workstream_Timelines.pptx?version=1&modificationDate=1692634297173&api=v2" data-nice-type="PowerPoint Presentation" data-file-src="https://wiki.covesa.global/download/attachments/64978970/230821_Workstream_Timelines.pptx?version=1&modificationDate=1692634297173&api=v2" data-linked-resource-id="75727097" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="230821_Workstream_Timelines.pptx" data-mime-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="230821_Workstream_Timelines.pptx" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/75727097/1" height="250" alt="" draggable="false" /></a></span></p><p>A copy has been placed on <a href="https://docs.google.com/presentation/d/1pMKeBRt03DEZ80lZG1dC5VUHRRtVhaEB/edit?usp=drive_link&ouid=111135011034856521381&rtpof=true&sd=true" class="external-link" rel="nofollow">Google Docs</a> for editing</p><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-7thAugust2023-MeetingAgenda"><strong>7th August 2023 - Meeting Agenda</strong></h2><ul><li>Participants: BMW, Ford, General Motors, Mercedes, Volvo, Remotive Labs, Faurecia Aptoide/Forvia, Harman, Bosch, LTTS, Mavi.io, Elektrobit, Jimmy Technologies, Geotab</li><li>Due to the Holiday next Tuesday (August 15th, 2023) in Europe, next meeting (August 14th, 2023) is cancelled.<ul><li><span>No concerns from the group</span></li></ul></li><li>Feedback from Mercedes and Cariad about camera API.<ul><li><span>Update will be provided at the end of summer.</span></li></ul></li><li>Statement that GM will be using uServices as a path moving forward. What is GM's path for the Emulator and potentially push notifications?<ul><li><span>GM will be providing presentation on uServices in the following meeting.</span></li><li><span>GM Presentation on uProtocol - </span><a href="https://docs.google.com/presentation/d/1yfJ_ynBGHQTcnG1GhyMQyhmO66KUdVEQN7UE24iNoeU/edit#slide=id.p" class="external-link" rel="nofollow"><span>Eclipse-uProtocol-Overview - Google Slides</span></a></li><li><span>GM is interested and will monitor the development of the Emulator and push notifications.</span></li></ul></li><li>GM to share timeline on using Android API approach<ul><li><span>GM is internally discussing this topic and will provide feedback in one of the upcoming meetings.</span></li></ul></li><li>Harman to Clarify next steps on contributing the Emulator:<ul><li><span>Harman needs to first join COVESA and then confirm with their legal team in regard to contributing the Emulator.</span></li></ul></li><li>Andrew Lakin/Forvia looking for feedback from companies that can contribute to the AOSP App Framework Panel discussion at the AMM in October.</li><li>Jose Freitas/FAA presented Push Notification presentation:<ul><li><span>Next steps: FAA/Harman to help lead and define who does what, e.g. who reaches out to which apps (e.g. Zoom/WebEx/TikTok)</span></li></ul></li></ul><p><span><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/2023.07.24-COVESA-App-Framework-Stand-WG-Push-notifications%20%20-%20FAA%20with%20BMW%20contribution.pdf?version=1&modificationDate=1692368145568&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/2023.07.24-COVESA-App-Framework-Stand-WG-Push-notifications%20%20-%20FAA%20with%20BMW%20contribution.pdf?version=1&modificationDate=1692368145568&api=v2" data-linked-resource-id="75727076" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="2023.07.24-COVESA-App-Framework-Stand-WG-Push-notifications - FAA with BMW contribution.pdf" data-mime-type="application/pdf" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="2023.07.24-COVESA-App-Framework-Stand-WG-Push-notifications - FAA with BMW contribution.pdf" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/75727076/1" height="250" alt="" draggable="false" /></a></span></span></p><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-31stJuly2023-MeetingAgenda"><strong>31st July 2023 - Meeting Agenda</strong></h2><ul><li>Participants: BMW, General Motors, Remotive Labs, Forvia, Harman, Mavi.io, GrapeUp, Elektrobit, Bosch, COVESA, Tietoevery, LTTS</li><li>Face to Face Meeting at 10 October 2023 in Troy, MI<ul><li><a href="https://docs.google.com/forms/d/e/1FAIpQLSeNsWQixpP18l52h9Wcy8g6M_YGzKJy296slqzuJLS0pj4MPA/viewform?usp=sf_link" class="external-link" rel="nofollow">Can you attend? Please let us know here</a></li></ul></li><li>CES Event planning</li><li>Communication channel: Slack does not seem to work for everyone<br/>→ Do we have counterproposals?</li><li>Involvement GrapeUp in camera stream</li><li>Feedback camera proposal</li><li>Defining next steps camera proposal<ul><li>Deliverable: Reference implementation published by COVESA; POC with 3rd Parties; testing capabilties for camera implementation via emulator (GrapeUp + Harman)</li><li>ToDo: Clarifying timeline for OEMs having this implemented</li><li>Timeline deliverable</li></ul></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-24thJuly2023-MeetingAgenda"><strong>24th July 2023 - Meeting Agenda</strong></h2><ul><li>Participants: Cariad, Ford, General Motors, Volvo, BMW, Faurecia, Harman, Snapp, Remotive Labs, Intellias, GrapeUp, Elektrobit, Jimmy Technologies, Bosch, COVESA, KPIT, Tietoevry, Geotab, Mavi.io</li><li>Emulator presentation (Snapp, Remotive Labs, Volvo)<br/>→ Slides from Snapp<br/><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/COVESA%20-%20AAOS%20emulator.pdf?version=1&modificationDate=1690214546084&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/COVESA%20-%20AAOS%20emulator.pdf?version=1&modificationDate=1690214546084&api=v2" data-linked-resource-id="71074329" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="COVESA - AAOS emulator.pdf" data-mime-type="application/pdf" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="COVESA - AAOS emulator.pdf" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/71074329/1" height="250" alt="" draggable="false" /></a></span><br/>→ Slides from RemotiveLabs/ Volvo <br/><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/Developing%20with%20Drive%20Playback_COVESA%20AOSP%2024th%20July%202023.pdf?version=1&modificationDate=1690214675841&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/Developing%20with%20Drive%20Playback_COVESA%20AOSP%2024th%20July%202023.pdf?version=1&modificationDate=1690214675841&api=v2" data-linked-resource-id="71074331" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="Developing with Drive Playback_COVESA AOSP 24th July 2023.pdf" data-mime-type="application/pdf" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="Developing with Drive Playback_COVESA AOSP 24th July 2023.pdf" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/71074331/1" height="250" alt="" draggable="false" /></a></span><br/>→ Input Harman would give for emulator topic:</li></ul><ul><li style="list-style-type: none;"><ol><li>System UI RROs and Settings Manager for System Bars and Navigation Bars. This allows, with one emulator, to simulate various OEM UIs</li><li>Multidisplay + Cluster Enablement (does not need Emulator downgrade to < 30.8.4.0)</li><li>Camera Enablement</li><li>Enablement for VIM3 HW</li><li>Various fixes (most backported from S, T or U)</li><li>Automotive Video Library integration</li><li>Unbundled Apps + Fixes</li><li><span>Car Companion Device + Phone Companion App (BLE passthrough needs special hw)</span></li></ol></li></ul><p style="margin-left: 40.0px;">→ Next steps:<br/><u>@Melina Mascolo (BMW): Setting up Slack Channel for Emulator: <a href="https://covesacommunity.slack.com/archives/C05JJNGSUH2" class="external-link" rel="nofollow">https://covesacommunity.slack.com/archives/C05JJNGSUH2</a></u></p><p style="margin-left: 40.0px;"><u>@Snapp/Harman/Volvo/RemotiveLabs: To align on next steps</u></p><ul><li>Status quo camera API<br/>→ Checked by Harman, BMW, Faurecia, <br/><u><span style="color: rgb(0,51,102);">→ Still need to be checked by: Cariad (31.7.), GM (31.7.), Mercedes, Volvo (after summer)<br/></span></u>→ Next step: Finding 1-2 app developers willing to do POC with this reference implementation</li><li>Push Notifications: Faurecia Aptoide created first overview for possible approaches<br/>→ Proposal will be shared by Faurecia Aptoide on this Confluence page<br/>→ To be reviewed August 7th<br/>→ Mavi.io willing to do an POC with their application for the reference implementation</li><li>Status update license for code and documentation (Apache?)<br/>→ Works for GM, Cariad, BMW, Snapp<br/><u>→ Needs to be checked by: RemotiveLabs/Volvo, Faurecia Aptoide</u></li><li>Vacation overview tbd.<br/>→ Which meetings can we keep during summer break<br/><u>→ Camille (Faurecia) to share vacation planner via Slack</u></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-17thJuly2023-Meetingcancelled"><strong>17th July 2023 - Meeting cancelled</strong></h2><ul><li>Meeting cancelled this week due to majority of the participants being OOO</li><li>Presentation of emulators from Snapp & RemotiveLabs will be done on 24th July</li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-10thJuly2023-VirtualMeeting"><strong>10th July 2023 - Virtual Meeting</strong></h2><p><u>ToDos are underlined <img class="emoticon emoticon-smile" src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)" /></u></p><ul><li><p>Participants: BMW, Cariad, General Motors, Mercedes, Forvia/Faurecia Aptoide, Harman, Snapp, Remotive Labs, Ansys, Intellias, GrapeUp, Bosch, drimaes, Elektrobit, KPIT, COVESA, Tietoevry, L&T Technologies, HAAS, Geotab</p></li><li><p>Preferred license: Potentially Apache<br/>→ <u>@All: 17.7. confirming if this license can be chosen for code and documentation</u></p></li><li><p><u>@Matthias Ostermeier (Cariad) & Albert Jordan (Harman): 17.7. Feedback if willing to contribute to collection of best pratices / developer documentation</u></p><p>→ Proposal: Starting a collection with learnings of different OEMs / App Store Providers</p><p>→ Longterm having more full-blown developer documentation</p></li><li><p>Differences between OEMs that Faurecia Aptoide found next to the ones listed in F2F Meeting: Media Player Integration, Car API, DRM, Toasts/Snackbar Usage</p><p>→ To be revisited after priority list</p></li><li>Handling of different workstreams:<ul><li>For now aligned within Monday meeting</li><li>Potentially seperate sessions needed where members can loop in their experts</li></ul></li><li><p>Stream Owners:</p><ol><li><p><strong>Cross-OEM Emulator:</strong> Juhani Lehtimäki (Snapp) with support of Emil Dautovic (Remotive Labs)</p><p><u>→ @Juhani Lehtimäki (Snapp) & Emil Dautovic (Remotive Labs): First session on emulator on 17th July</u></p></li><li><p><strong>Camera API:</strong> Manuel Saraiva (BMW)<br/><u>→ @All: 17.7. Clarifying if reference implementation in PDF document from F2F meeting (22.6.) works across OEMs</u> (<a href="https://wiki.covesa.global/download/attachments/64978970/230622_F2F_Meeting_Garching.pdf?version=1&modificationDate=1689063969292&api=v2" rel="nofollow">https://wiki.covesa.global/download/attachments/64978970/230622_F2F_Meeting_Garching.pdf?version=1&modificationDate=1689063969292&api=v2</a>)</p></li><li><p><strong>Push Notifications:</strong> tbd.</p><p><u>→ @José Freitas (Faurecia Aptoide): giving overview on 24th July</u></p><p><u>→ @Melina Mascolo (BMW): Sharing first proposal with José</u></p></li><li><p><strong>Best Practices:</strong> tbd.</p></li></ol></li><li><p>General communication channel for workstreams: Slack</p><p>→ Link will be shared with group</p></li><li><p><u>@All: 24.7. Clarifying if attending AMM in Detroit (10.-12.10.) would be possible</u></p><p>→ Idea would be to combine it with longer workshops, e.g. with communication app providers</p></li></ul><h2 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-22June2023-FacetoFaceWorkshop"><a href="https://wiki.covesa.global/display/WIK4/AOSP+App+Framework+Standardization+-+22+June+2023+-+Face+to+Face+Workshop">22 June 2023 - Face to Face Workshop</a></h2><ul><li><a href="https://wiki.covesa.global/display/WIK4/AOSP+App+Framework+Standardization+-+22+June+2023+-+Face+to+Face+Workshop">Details</a></li><li>Consolidated Meeting Notes, participants and presentations (in PDF)</li><li><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/230622_F2F_Meeting_Garching.pdf?version=1&modificationDate=1689063969292&api=v2" data-nice-type="PDF Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/230622_F2F_Meeting_Garching.pdf?version=1&modificationDate=1689063969292&api=v2" data-linked-resource-id="71074209" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="230622_F2F_Meeting_Garching.pdf" data-mime-type="application/pdf" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="230622_F2F_Meeting_Garching.pdf" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/71074209/1" height="250" alt="" draggable="false" /></a></span> </li></ul><p><br/></p><h1 id="AutomotiveAOSPAppFrameworkStandardizationExpertGroup-Charter">Charter </h1><p><span class="confluence-embedded-file-wrapper"><a class="confluence-embedded-file" href="https://wiki.covesa.global/download/attachments/64978970/2305_COVESA_Android_Automotive_V4.0.docx?version=1&modificationDate=1683829772627&api=v2" data-nice-type="Word Document" data-file-src="https://wiki.covesa.global/download/attachments/64978970/2305_COVESA_Android_Automotive_V4.0.docx?version=1&modificationDate=1683829772627&api=v2" data-linked-resource-id="64979606" data-linked-resource-type="attachment" data-linked-resource-container-id="64978970" data-linked-resource-default-alias="2305_COVESA_Android_Automotive_V4.0.docx" data-mime-type="application/vnd.openxmlformats-officedocument.wordprocessingml.document" data-has-thumbnail="true" data-linked-resource-version="1" data-can-edit="false" aria-label="2305_COVESA_Android_Automotive_V4.0.docx" draggable="false"><img src="https://wiki.covesa.global/rest/documentConversion/latest/conversion/thumbnail/64979606/1" height="250" alt="" draggable="false" /></a></span></p><p><br/></p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/display/WIK4/Automotive+AOSP+App+Framework+Standardization+Expert+Group">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=64978970&revisedVersion=116&originalVersion=115">View Changes Online</a>
</div>
</div>Richard Fernandes2023-03-20T23:06:17Z2024 Spring AMM Planning (Data Architecture and Infrastructure)Stephen Lawrencetag:wiki.covesa.global,2009:page-85196880-102024-03-27T18:36:32Z2023-11-10T16:55:22Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~stephen.lawrence
">Stephen Lawrence</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>Planning for the Data Architecture and Infrastructure sessions/workshops at the 2024 Spring AMM in Gothenburg, Sweden</p><h1 id="id-2024SpringAMMPlanning(DataArchitectureandInfrastructure)-DataArchThursAMsessions">Data Arch Thurs AM sessions</h1><div class="table-wrap"><table class="wrapped confluenceTable"><colgroup><col/><col/><col/></colgroup><tbody><tr><th scope="col" class="confluenceTh">Topic/Title</th><th scope="col" class="confluenceTh">Time</th><th scope="col" class="confluenceTh">Desc / comments</th></tr><tr><td class="confluenceTd">Playground Intro</td><td class="confluenceTd">9am-9:40 incl Qs</td><td class="confluenceTd">See desc below</td></tr><tr><td class="confluenceTd">Playground Technical</td><td class="confluenceTd">9:40-10:10 incl Qs</td><td class="confluenceTd">See desc below. Technical leads to use, e.g. can do X with MQTT, or<br/>time series analysis allows data quality/reduction/knowledge Y</td></tr><tr><td class="confluenceTd">Playground Use</td><td class="confluenceTd">10:30-11 incl Qs</td><td class="confluenceTd">See desc below. Make naturally bleed into workshop for 'next-steps'</td></tr><tr><td class="confluenceTd">Workshop</td><td class="confluenceTd">11-12:15</td><td class="confluenceTd">General workshop as we have done in the past</td></tr><tr><td class="confluenceTd">Flexible coffee break</td><td class="confluenceTd">10-10:30</td><td class="confluenceTd">Covesa arranging flexible period when coffee available</td></tr><tr><td class="confluenceTd">Lunch</td><td class="confluenceTd">12:15-1:30</td><td class="confluenceTd"><br/></td></tr></tbody></table></div><h1 id="id-2024SpringAMMPlanning(DataArchitectureandInfrastructure)-Workshoptopics?">Workshop topics?</h1><ul><li>Playground<ul><li>Backlog<br/><ul><li>What is the content for the next phase?</li></ul></li><li>Examples/uses we want to pursue</li><li>Knowledge layer</li><li>VISS<ul><li>Needs: pre-built Image, dockerfile for 'standard build'</li></ul></li><li>Data sets</li><li>Feeder components</li><li>Playground-aaS</li></ul></li></ul><h1 id="id-2024SpringAMMPlanning(DataArchitectureandInfrastructure)-CentralDataServicePlayground">Central Data Service Playground</h1><p>17th Jan Data Arch meeting discussed sessions address following three tracks (needs polishing):</p><ol><li><em>Intro focusing on the big picture</em>. Why? What? How? Less technology, more intent, purpose, how it can be useful (internals and touchpoints/examples). <br/><em>Goal</em>: Leave with big picture understanding of why it was created, current status, roadmap,</li><li><em>More detailed technical readout of the What/How</em>. Level 1/2 technical description of the components and their deployment.<br/><em>Goal: </em>Leave with understanding of what it is (internals) and how to get started</li><li><em>Using the Playground. </em>Focus on the using the Playground to illustrate an example or touchpoint under research.<br/><em>Goal: </em>Leave with understanding of how it can be used (externals) through an example.</li></ol><p><br/></p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/pages/viewpage.action?pageId=85196880">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=85196880&revisedVersion=10&originalVersion=9">View Changes Online</a>
</div>
</div>Stephen Lawrence2023-11-10T16:55:22ZArchitecture and Infrastructure Meeting MinutesStephen Lawrencetag:wiki.covesa.global,2009:page-46628897-1232024-03-27T15:47:00Z2022-11-09T15:28:00Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~stephen.lawrence
">Stephen Lawrence</a>
- "27th March agenda"
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>The minutes of the meetings for the Data Architecture and Infrastructure pillar of the Data Expert Group.</p><p>Historical note: the minutes for the previous project, the CVII Tech Stack, can be found here: <a href="https://wiki.covesa.global/display/WIK4/CVII+Technology+Stack+meeting+notes">CVII Technology Stack meeting notes</a></p><h2 id="ArchitectureandInfrastructureMeetingMinutes-27thMarch2024">27th March 2024</h2><p>Agenda:</p><ul class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Weaving in other sessions? Workshop at end of Playground 'use' session?</li><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=85196880">2024 Spring AMM Planning (Data Architecture and Infrastructure)</a></li></ul></li><li>Central Data Service Playground</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-20thMarch2024">20th March 2024</h2><p>Agenda:</p><ul class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Weaving in other sessions? Workshop at end of Playground 'use' session?</li></ul></li><li>Central Data Service Playground<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Status reports / Kanban review</li><li>Documentation site: content, theme</li><li>0.1.0 release</li><li>Knowledge Layer Connector</li></ul></li></ul><p>Minutes:</p><ul><li>Spring AMM sessions<ul><li>Paul: can make changes to the timings if you need.</li><li>Discussion of making the end of the morning a working session.</li><li><strong>AI: Need to calculate the timings. Three playground sessions, then working session.</strong></li></ul></li><li>Central Data Service Playground<ul><li>Status reports / Kanban review<ul><li>Steve:<ul><li>WAII VISS Server IoTDB documentation and runtime configuration for connector merged upstream. Will rebase Playground on upstream after spent some time on playground documentation.</li><li>Working on content for Playground doc site to add baseline why/why/how introduction and getting started. Work taking place on my fork and presented as WIP PR here <a href="https://github.com/COVESA/cdsp/pull/27" class="external-link" rel="nofollow">https://github.com/COVESA/cdsp/pull/27</a></li></ul></li><li>Arnaldo:<ul><li>Continuing work on Realm integration.</li></ul></li></ul></li><li>Documentation site<ul><li>Brief discussion of Hugo themes. Steve seems some limitations in the current Learn theme and has done some experiments with Hextra that adds useful features like Cards and has more normal heading type size scaling. Small example here <a href="https://slawr.github.io/cdsp-doc-hextra-trial/docs/" class="external-link" rel="nofollow">https://slawr.github.io/cdsp-doc-hextra-trial/docs/</a></li></ul></li><li>Discussion of 0.1.0 release around time of AMM release</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-13thMarch2024">13th March 2024</h2><p>Agenda:</p><ul class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Weaving in other sessions?</li></ul></li><li>Central Data Service Playground<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Covesa Board</li><li>Status reports / Kanban review</li><li>Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.</li><li>Roadmap/backlog/work package definition.<ul class="p-rich_text_list p-rich_text_list__ordered"><li>What does AMM release look like?</li><li>Feeders</li></ul></li><li>Possible online hosting of Playground</li></ul></li></ul><p>Minutes:</p><ul><li>Sml group: Swen, Steve, Paul, Haonan</li><li>Central Data Service Playground<ul><li>Steve presented the development status to the Covesa board today</li><li>Status<ul><li>Steve has sent PR upstream documenting use of Apache IoTDB as WAII Data Store backend. Covers for example runtime assumptions, e.g. schema, that a feeder or client developer would need to know about. Also how to seed the DB.</li><li>Content will be reusable in Playground.</li><li>He also rebased the code to add runtime configuration of the IoTDB connector through a config file on current upstream master and sent PR</li></ul></li><li>Discussion of Swen's idea for online hosting</li><li>Discussion of app embedded DB schema</li><li>Steve summarised what the content of the likely first 0.1.0 release will be and plans for roll out.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-6thMarch2024">6th March 2024</h2><p>Agenda:</p><ul class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions</li><li>Central Data Service Playground<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Status reports / Kanban review</li><li>Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.</li><li>Roadmap/backlog/work package definition.<ul class="p-rich_text_list p-rich_text_list__ordered"><li>What does AMM release look like?</li><li>Feeders</li></ul></li><li>Possible online hosting of Playground</li></ul></li></ul><ul class="p-rich_text_list p-rich_text_list__ordered"><li>AoB</li></ul><p><br/></p><p>Minutes:</p><ul><li>Sml group: Ulf, Swen, Steve</li><li>Central Data Service Playground<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Status reports<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Apache IoTDB<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Now upstream WAII VISS git rep move is complete Steve will rebase and upstream the config file support.</li><li>Extending WAII tutorial to document IoTDB connector is almost complete. Will send PR upstream.</li></ul></li></ul></li><li>Knowledge Layer Connector: Haonan has reported that <a href="https://wiki.covesa.global/display/WIK4/Artifact+JSON-RDF+Converter">Artifact JSON-RDF Converter</a> outline has been updated.</li><li>Discussion of the likely content of the pre-AMM release.</li><li>Discussion of the current thinking for roll-out: get initial documentation in place, roll-out to active Covesa devs, then wider membership/community using blog/e-blast.</li><li>Swen outlined the benefits and possible method for online hosting of the Playground.<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Wide ranging discussion of the possibilities: costs, connecting to other systems, scaling, flexibility etc.</li><li>Interesting idea that needs further discussion.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-28thFebruary2024">28th February 2024</h2><p>Agenda:</p><ul class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions</li><li>Central Data Service Playground<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Status reports<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Upstreaming Apache IoTDB support into WAII VISS Data Server</li><li>Apache IoTDB runtime configuration support</li><li>Online documentation</li></ul></li><li>Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.</li><li>Roadmap/backlog/work package definition. What does AMM release look like?</li><li>Feeders</li></ul></li><li>AoB</li></ul><p>Minutes:</p><ul><li>Central Data Service Playground<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Status reports<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Online documentation: Steve has merged Ulf's online documentation PR to add the Hugo setup. Next step is enabling the workflow to automatically build and publish any content.</li><li>Apache IoTDB state storage: Steve has added runtime configuration (where to find DB, what database path to use etc) support for the WAII IoTDB connector. It's available in his PR <a class="external-link" href="https://github.com/COVESA/cdsp/pull/20" rel="nofollow">https://github.com/COVESA/cdsp/pull/20</a>. He will send a PR upstream to WAII once its moved to its new home.</li><li>Realm state storage:<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Arnaldo had questions about how best to handle the paradigm difference between the typically complex documentation schema used in Realm and the key/value pair schema of VISS/WAII. A second challenge is Realm has C++, but no Go client/binding so how best to interface to WAII get/set methods in Go?</li><li>Discussion about possible approaches:<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Complex schema<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Steve: Same problem exists I think for the JSON-schema to RDF connector for the knowledge layer. We've started with simple with key/value pairs in the store for maximum flexibility, but approaches will need to be found for more complex schema as we go along.</li><li>Swen: I saw this problem when working with Realm cases. We added accessor methods to our solutions to allow interfacing to other systems.</li><li>Discussion wondering how BMW VISS implementation had addressed the same issue. Arnaldo/Haonan could look for internal suggestions.</li></ul></li><li>WAII connector<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Steve showed the three WAII methods to be supported (init, get, set) which have straight forward parameters.</li><li>Two ideas suggested:<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Use Go binding to other languages. Ulf had succesfully used a package that provided type conversions and binding for C.</li><li>If Realm has IPC support then it could be used form the Go methods. Ulf explains the Redis connector uses a unix socket.</li></ul></li></ul></li></ul></li></ul></li><li>Out of time to discuss Knowledge Layer Connector this week.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-21stFebruary2024">21st February 2024</h2><p>Agenda:</p><ol class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions</li><li>Central Data Service Playground<ol class="p-rich_text_list p-rich_text_list__ordered"><li>Status reports</li><li>Upstreaming Apache IoTDB support into WAII VISS Data Server</li><li>Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.</li><li>Online documentation</li><li>Roadmap/backlog/work package definition. What does AMM release look like?</li><li>Feeders incl WAII, Volvo/Remotive</li></ol></li><li>AoB</li></ol><p><br/></p><p>Minutes:</p><ul class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions: Paul would like any updates. Currently abstracts are missing.</li><li>Central Data Service Playground<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Status reports<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Apache IoTDB support<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Steve created <a href="https://github.com/w3c/automotive-viss2/pull/110" class="external-link" rel="nofollow">PR #110</a> in WAII upstream to add the Apache IoTDB support into WAII VISS Data Server. This was merged by the maintainers. Need to add documentation.</li><li>Steve also created Playground <a href="https://github.com/COVESA/cdsp/pull/20" class="external-link" rel="nofollow"> PR #20</a> to make it available in a WAII fork. Now changes are upstreamed this can be changed to update submodule to the upstream instead.</li></ul></li><li>Realm support: No update this week</li><li>Online documentation<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Hugo changes were merged but an issue was found in the signoff. Now updated, this will be merged again this week.</li></ul></li></ul></li><li>Knowledge Layer Connector<ul class="p-rich_text_list p-rich_text_list__ordered"><li>Some background noise on Haonan's end hampered discussion somewhat.</li><li>Haonan talked about generators to and from SHACL.</li><li>Work needed to understand how to connect existing tool, which uses web socket as transport and JSON-schema for message, to the VSS State Storage.</li><li>Some discussion of schemas in state storage. Danger is becoming bog downed in system design discussions of for example VSS tree vs graph. For know the KISS of VSS key/value pairs is beneficial in its flexibility.</li></ul></li><li>In coming weeks we need to consider roadmap/backlog/work package definition, in part so we know what we want to say at the AMM.</li><li>Steve outlined eco-system discussions related to EU Horizon and with Volvo/RemotiveLabs related to feeders.</li></ul></li><li>AoB<br/><ul class="p-rich_text_list p-rich_text_list__ordered"><li>Paul mentions the work on Covesa website related to project descriptions. Data Arch will need to check their entries.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-14thFebruary2024">14th February 2024</h2><p>Agenda:</p><ol class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions</li><li>Central Data Service Playground<ol class="p-rich_text_list p-rich_text_list__ordered"><li>Status</li><li>Knowledge layer connector</li></ol></li><li>AoB</li></ol><p><br/></p><p>Minutes:</p><ul><li>Central Data Service Playground<ul><li>Status <br/><ul><li>Online doc: AI for Steve to work with Ulf on his Hugo PR remains open</li><li>Steve has brought the Playground Kanban up to date.</li><li>Apache IoTDB: Steve has implemented 'set' connector for WAII locally. Code is available in his github fork. Preparing PR to both Playground and WAII.</li><li>Realm:<ul><li>Steve met with Humza/Arnaldo last Friday to show his integration into WAII</li><li>Currently Arnaldo considering how best to do the integration. Options include adding Realm as a State Storage backend for all data, e.g. like Redis and IoTDB, or using it in a supporting role where it makes sense, e.g. sync or in Example.</li></ul></li></ul></li><li>Ulf announced he is adding <a class="external-link" href="https://memcached.org/" rel="nofollow">https://memcached.org/</a> (fast simple key/value pair in-mem store) as an additional State Storage backend to the WAII VISS Data Server.</li><li>Knowledge layer connector<ul><li>Haonan has posted first draft of problem outline for the connector to slack in document form whilst she sort out Confluence access:<br/><a href="https://wiki.covesa.global/download/attachments/46628897/Covesa%20Playground%20Piece_%20Data%20Converter%20between%20DM%20and%20Reasoner-v21-20240214_101149.docx?version=1&modificationDate=1708528717286&api=v2" data-linked-resource-id="95256582" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Covesa Playground Piece_ Data Converter between DM and Reasoner-v21-20240214_101149.docx" data-nice-type="Word Document" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.wordprocessingml.document" data-linked-resource-container-id="46628897" data-linked-resource-container-version="123">Covesa Playground Piece_ Data Converter between DM and Reasoner-v21-20240214_101149.docx</a></li><li>Group needs to do background reading to come up to speed on the topic.</li></ul></li></ul></li></ul><p><br/></p><h2 id="ArchitectureandInfrastructureMeetingMinutes-7thFebruary2024">7th February 2024</h2><p>Agenda:</p><ol class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions</li><li>Central Data Service Playground<ol class="p-rich_text_list p-rich_text_list__ordered"><li>Based on discussion with <a class="confluence-userlink user-mention" data-username="Christian.CM.Muehlbauer@bmw.de" href="https://wiki.covesa.global/display/~Christian.CM.Muehlbauer@bmw.de" data-linked-resource-id="64979834" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Christian Muehlbauer</a> kick off discussion of Connector in the Playground between the data and knowledge layers</li><li>Ulf has sent a PR to add the Hugo online doc: Any discussion needed related to that, e.g. workflow, review</li><li>Database connectors: status, handling WAII changes</li><li>Feeders (time allowing)</li></ol></li><li>AoB</li></ol><p>Minutes:</p><ul><li>Spring AMM sessions: nothing to discuss this time</li><li>Central Data Service Playground<ul><li>New feature idea: Connector between the data and knowledge layers in the DIKW pyramid<ul><li>Kick off of discussion first discussed in previous weeks.</li><li>Possibility to use BMW Research WS to RDF Converter (see Christian presentation below). Christian has some personal leave in coming weeks. Haonan will step in.</li><li>Haonan offers to do technical overview presentation of converter.</li><li>Steve suggests using the proposed <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=85196928">Artifact design methodology (simplified)</a> as a means to working through what such a Connector should achieve for the Playground. No dissentors. Haonan agrees.</li><li>Way forward:<ul><li>Haonan will do a technical overview presentation in a future meeting. Goal: group better understands the converter. Date TBD once she is ready.</li><li>Haonan kindly agreed to do a first draft using the design methodology to define what a Playground Connector should be from her perspective (domain expertise). This can then be used as a basis for wider discussion in the group.</li><li>AI: Track in meetings.</li></ul></li></ul></li><li>Online documentation<ul><li>Ulf has posted PR to add Hugo static website generator. He needs support to add github workflow to automatically build the doc and publish. AI: Steve to work with Ulf on that.</li><li>Requst to review PR. Will look to merge in next week.</li></ul></li><li>Database Connectors<ul><li>Steve has the 'get' connection between WAII and Apache IoTDB done. Preparing to make code public. He expects 'set' to be added this week.</li><li>Humza reports that the Realm DB C++ process is done. Just need to integrate into WAII. After discussion Steve will meet with Humza/Arnaldo to do a quick return of experience with his integration to accelerate adding Realm.</li><li>Answer to question of how to manage WAII changes before they are upstreamed becoming more urgent. Steve will likely create WAII fork so they can be managed in the submodule to keep us moving.</li></ul></li><li>Feeders<ul><li>Short discussion of feeders</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-31stJanuary2024">31st January 2024</h2><p>Agenda:</p><ol><li>WAII update</li><li>Spring AMM sessions</li><li>Central Data Service Playground</li></ol><p>Minutes:</p><ul><li>WAII update<ul><li>Ulf gave an update on WAII improvements related to the new feeder mechanism.</li><li>Code is merged to master and documentation can be found in the tooling section of the on-line documentation in the tutorial</li></ul></li><li>Spring AMM<ul><li>Ulf has added some topics to related to WAII and Commerical vehicles to Paul's Proposal page</li><li>Arnaldo/Christian have sent a title topic related to touchpoints and the knowledge layer<ul><li>Abstract to be created</li><li>They say this is possibly less of a readout of existing work and could lead into the discussion of examples and using the Playground</li></ul></li><li>Discussion of the third part of the Playground session covering examples and using it and how to incorporate the other sessions</li><li>Thought needs to be given as to whether to have a formal workshop session in the programme or an informal one with involved members outside the programme</li></ul></li><li>Central Data Service Playground<ul><li>Status<ul><li>Steve has done initial integration of IoTDB connector into WAII. Builds and runs. Now need to debug integration issues.</li><li>Arnaldo continues to work on Realm integration. C++ backend nearing completion. Connecting to WAII after that.</li></ul></li><li>Phase 1 PoC<ul><li>What are the big picture things in the backlog? <br/><ul><li>Source license</li><li>On-line (Hugo) doc PoC<ul><li>Christian: It would be useful to paint the big picture of relationship to other projects. I can perhaps contribute something in that regard</li></ul></li></ul></li><li>Contributor outline</li><li>Source documenation</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-24thJanuary2024">24th January 2024</h2><p>Agenda:</p><ol class="p-rich_text_list p-rich_text_list__ordered"><li>Spring AMM sessions</li><li>Central Data Service Playground</li><li>AoB<ol class="p-rich_text_list p-rich_text_list__ordered"><li>(Ulf): WAII update</li></ol></li></ol><p><br/></p><p>Minutes:</p><ul><li>Spring AMM sessions<ul><li>Steve has added an outline for the three Playground sessions to the planning page.</li><li>Agreement in meeting to propose those as placeholders in Paul's planning</li><li>Ulf will add some sessions on his WAII work</li></ul></li><li>Playground<ul><li>Decision taken to merge Steve's PR to give the project master branch some structure. This will make it easier for others to parallel work.</li><li>Status<ul><li>Adding Realm: Arnaldo says he has the C++ process written to act as a Realm instance orchestrator</li><li>Adding IoTDB: Steve is working on connecting WAII to IoTDB using the IoTDB Golang client.</li></ul></li><li>Christian presents his initial thoughts overlaying the work BMW have presented in recent AMMs onto the Playground<ul><li><a href="https://wiki.covesa.global/download/attachments/46628897/Christian%20Proposal.pptx?version=1&modificationDate=1706210201139&api=v2" data-linked-resource-id="90407042" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Christian Proposal.pptx" data-nice-type="PowerPoint Presentation" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-linked-resource-container-id="46628897" data-linked-resource-container-version="123">Christian Proposal.pptx</a></li><li>General agreement that additional viewpoints are needed to logical and implementation in presenting the Playground and that shared diagrams are useful.</li><li>Discussion on what components might be open sourced and could be integrated. RDF converter would be a good candidate to examine for providing a connector between data and knowledge layers.</li><li>Christian will be taking some time off in coming weeks but is hoping Haonan can substitute as she is very familiar with the RDF converter.</li></ul></li><li>Open decision: need to agree how to handle WAII changes. Upstream, fork for git submodule or git subtree for example?</li></ul></li><li>AoB<ul><li>Ran out of time. Ulf prefers to defer WAII update to next time.</li></ul></li></ul><p><br/></p><h2 id="ArchitectureandInfrastructureMeetingMinutes-17thJanuary2024">17th January 2024</h2><p>Minutes:</p><ul><li>Discussion of Spring AMM sessions.<ul><li>AMM Commitee wants to make schedule public end of Jan</li><li>Data Arch planning page here <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=85196880">2024 Spring AMM Planning (Data Architecture and Infrastructure)</a>. Feel free to add your ideas there.</li><li>Steve proposes three linked themes for sessions on the Playground<ul><li>High level intro (why, what)</li><li>Technical overview (more detailed on how and the code)</li><li>Focus on using the playground through examples. Akin to the BMW presentations in prior AMMs.</li></ul></li><li>General agreement that would be good approach.</li></ul></li><li>Central Data Service Playground<ul><li>Steve summarises Friday meeting with Arnaldo and Christian/Haonan. Succesfully worked through Arnaldo's issues with WAII Docker bring up.</li><li>Arnaldo documented list of gaps in instructions for a clean build.</li><li>Steve used this to raise additional issues in WAII github with doc or code gaps.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-10thJanuary2024">10th January 2024</h2><p>Agenda:</p><ul><li>Central Data Service Playground</li><li>Database abstraction and feeders</li><li>AoB<ul><li>Ulf has WAII update</li></ul></li></ul><p>Minutes:</p><ul><li>WAII update from Ulf<ul><li>VISS specification contains consent meta-data mechanism in addition to security control. This consent mechanism is now implemented in WAII.</li><li>PoC demo of WAII consent together with AIDEN consent framework at Spring AMM. Ulf intends also to present.</li><li>Work continuing on new feeder architecture he presented in Detroit. He also intends to present update at AMM.</li></ul></li><li>Central Data Service Playground<ul><li>Steve outlined status:<ul><li>Been working with WAII maintainers to work through some some issues in upsteam documentation and docker configuration. Thanks to them for support.</li><li>Steve PR has a basic (incomplete) Playground docker deployment that now works.</li><li>Apache IoTDB is running as VSS Data Store. Can execute IoTDB CLI client in IoTDB container and communicate with the server.</li><li>WAII is running as VISS Data Server. Can execute WAII javascript HTML client in WAII container and communicate with the server.</li><li>Steve did live demo of above.</li></ul></li><li>Realm<ul><li>Arnaldo still planning to create a runtime app that can act as admin process for a Realm DB based backend.</li><li>He asks if C++ is best fit for client API?</li><li>Initial discussion suggests it would be. Other SDK options in Realm are orientated towards mobile development.</li><li>Christian makes good point that Flutter support would be useful for reusing the existing BMW code and supporting the mobile/cloud deployment.<ul><li>Christian needed to drop 30 mins in. Follow up on discussion of adopting existing BMW code to Playground required.</li></ul></li></ul></li><li>Arnaldo suggests side meeting with Steve to accelerate his work.<ul><li>Steve happy to meet.</li><li>Christian would also like to attend such a meeting so he can get up to speed. Early next week (post CES) best for him.</li><li>Steve will send invite. Arnaldo would like meeting Friday.</li></ul></li><li>DB abstraction / feeders<ul><li>Steve reports he has looked at kuksa CAN provider and thinks it could be interfaced.</li><li>Discussion of possible DB abstraction<ul><li>Steve: is there something we can do to encourage more joint work on feeders by making it easier to interface them northbound.</li><li>Gunnar suggests doing some native code to see if there is similarity</li></ul></li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-3rdJanuary2024">3rd January 2024</h2><ul><li>Small scale meeting kicking off new year.</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-13thDecember2023">13th December 2023</h2><p>Agenda:</p><ul><li>Central Data Service Playground: progress, roadmap</li><li>End of year holidays: When to end and restart?</li></ul><p>Minutes:</p><ul><li>Apologies: Ulf, Christian</li><li>Central Data Service Playground<ul><li>Progress: Steve reports some problems were found with WAII Docker support, but now addressed. Now working on IoTDB. Currently blocked by runtime issue. Asked for input upstream. We will not achieve the hope of having the base Docker up by 2023 work stop. Will need to push on with that at start of 2024.</li><li>Roadmap<ul><li>Covesa Board and officers are looking to build roadmaps early in 2024 for strategic development. Playground will be part of that. Suggest we get the Phase 1 PoC working asap in 2024, then use the review of that both to define Phase 2 as planned, but also seed the ideas for this Roadmap request.</li></ul></li></ul></li><li>End of year holidays:<ul><li>Richard informs GM will be finishing next week as well.</li><li>No meeting Weds 20th and 27th of December.</li><li>In 2024 do we restart on Weds 3rd or 10th of Jan? As 10th will be CES and many people will be there decision to restart on 3rd for those who can make it.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-6thDecember2023">6th December 2023</h2><p>Agenda:</p><ul><li>Central Data Service Playground</li><li>Autosar Vehicle API</li><li>BMW Knowledge Layer paper</li><li>AoB<ul><li>End of year holidays</li></ul></li></ul><p>Minutes:</p><ul><li>Apologies: Humza, Arnaldo</li><li>Steve summarised the status update given by Autosar Cloud WG earlier this work on their work on Autosar Vehicle API.<ul><li>Good work done on Autosar to VSS conversion.</li><li>Current concept is focused more on translation, with greater freedom on northbound protocol compared to the API Gateway concept they expressed before project setup. They are looking at VISS northbound for instance.</li><li>Look at the Cloud WG artifacts (Autosar membership required) for details.</li></ul></li><li>Christian gave an explanation of the Knowledge Layer paper that he mentioned previously that BMW were working on and is now published.<ul><li>Paper: <a href="https://www.scitepress.org/Documents/2023/122550/" class="external-link" rel="nofollow">https://www.scitepress.org/Documents/2023/122550/</a></li><li>Discussion of split between "query" front end language and data layer connector in backend providing data. In current implementation there is not a GraphQL Resolver style fetcher that could be connected to a DB. Instead the data schema is directly synched to the app logic.</li></ul></li><li>Central Data Service Playground<ul><li>Steve gave quick intro to Christian on source structure.</li><li>Further changes pushed since last week including fuller docker compose for the Playground with Apache IoTDB backend. To make changes more visible Steve has created a WIP PR in the Covesa git rep <a class="external-link" href="https://github.com/COVESA/cdsp/pull/16" rel="nofollow">https://github.com/COVESA/cdsp/pull/16</a></li><li>Christian has some ideas about using the Playground for Knowledge layer experiments. Will talk to Daniel about these and come back later.</li><li>Humza reported offline that MongoDB will look at Realm backend next week.</li></ul></li><li>End of year holidays<ul><li>Christian: will finish around middle of wk 51 (week before xmas) and back wk 2 in '24.</li><li>Ted: out xmas week</li><li>Steve: last full week is next week. Will finish early wk 51.</li><li>Result: Next week will be final meeting of '23.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-29thNovember2023">29th November 2023</h2><p>Agenda:</p><ul><li>Central Data Service Playground<ul><li>Updates<ul><li>Basic structure<ul><li>Doc, Examples, Docker, Source, Best Practices</li></ul></li><li>PR</li><li>Docker<ul><li>Compose structure</li><li>Docker Hub</li></ul></li></ul></li></ul></li><li>AoB</li></ul><p><br/></p><p>Minutes:</p><ul><li>Apologies: Humza, Arnaldo, Christian.</li><li>Central Data Service Playground<ul><li>Steve summarizes progress<ul><li>His hacking taking place in github fork <a class="external-link" href="https://github.com/slawr/cdsp/tree/phase1poc" rel="nofollow">https://github.com/slawr/cdsp/tree/phase1poc</a></li><li>WIP PR pushed to Covesa rep</li><li>Basic directory structure in place for Doc, Examples, Docker, Source</li><li>Best Practices/Design Guide file started to act as a notebook as we go to record guidance.</li><li>Discussion of Docker Compose approach including pushing images to Docker Hub.</li></ul></li></ul></li><li>AoB<ul><li>Paul reminds about the sync call with the Autosar Cloud WG Thursday. Brief discussion about their use of VISS. Need to hear what they have to say to progress.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-22ndNovember2023">22nd November 2023</h2><p>Agenda:</p><ul><li>Central Data Service Playground<ul><li>WAII State Storage abstraction discussion<ul><li>Source Ref: <br/><ul><li><a class="external-link" href="https://github.com/COVESA/ccs-components/tree/master/statestorage" rel="nofollow">https://github.com/COVESA/ccs-components/tree/master/statestorage</a></li><li><a href="https://github.com/w3c/automotive-viss2/tree/master/server/vissv2server/serviceMgr" class="external-link" rel="nofollow">https://github.com/w3c/automotive-viss2/tree/master/server/vissv2server/serviceMgr</a></li><li>Redis PR: <a class="external-link" href="https://github.com/w3c/automotive-viss2/pull/28/files#top" rel="nofollow">https://github.com/w3c/automotive-viss2/pull/28/files#top</a></li></ul></li><li>Topics:<ul><li>Lifecycle:<ul><li>Init: DB, client,..</li><li>Data Access: Get/Set/Sub</li><li>Shutdown: DB, client</li></ul></li><li>Schema sync:<ul><li>WAII Statemanger and feeder need to understand DB schema</li></ul></li></ul></li></ul></li></ul></li><li>AoB</li></ul><p><br/></p><p>Minutes:</p><ul><li>Central Data Service Playground<ul><li>MongoDB can only attend first 30 mins, so state storage discussion split into two 30 mins slots.</li><li>1st 30 mins (all)<ul><li>Paul asked about peoples perceptions of production readiness.</li><li>Ulf began description of WAII storage implementation</li></ul></li><li>2nd 30 mins (UIf, Humza, Arnaldo, Steve)<br/><ul><li>Ulf completed description</li><li>MongoDB asked Qs.</li><li>Some important notes<ul><li>Ulf has changed implementation on Master branch so Set writes directly to feeder for latency reasons</li><li>CCS State Storage github is just an example. It is not consumed by WAII and therefore WAII Service Manager implementation is in focus.</li></ul></li><li>Out of time. Continue discussion in Slack.</li><li>Ulf on holiday next two days.</li><li>Humza/Arnaldo busy with show next week. Following week they will look at Realm implementation.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-15thNovember2023">15th November 2023</h2><p>Agenda:</p><ul><li>Playground big picture: Continue discussion of what/why/how</li><li>Tasks towards the creation of the Playground PoC</li><li>Playground use cases both for us and externally</li><li>Spring AMM</li></ul><p><br/></p><p>Minutes:</p><ul><li>Big picture<ul><li>Ulf: interested in helping with WAII/VISS parts. The Realm Sync work between MongoDB and BMW would be an interesting feature to add.</li><li>Discussion of WAII State Storage abstraction and future possibilities.<ul><li>Ulf: Current implementation reflects needs of the VISS protocol.</li><li>Whilst it will not allow you access to full performance of the DBs its agreed that as a first step it makes sense to integrate to the current abstraction. Then consider internals to meet additional requirements as follow up work.</li><li>Realm is an application DB rather than a standalone service. Discussion of creating a thin Shim or Connector application to interface Realm to WAII State Storage abstraction.</li><li>Christian: Future work on the northbound state storage abstraction would be interesting topic.</li></ul></li></ul></li><li>Tasks for creation of Phase 1 PoC<ul><li>State Storage integration<ul><li>See above for discussion on Realm</li><li>A side meeting will be arranged for interested parties to discuss. Steve will post on slack.</li></ul></li><li>Steve outlines thoughts he had for source repository structure:<ul><li>Source of Central Data Service Playground itself<br/><ul><li>Docker <br/><ul><li>DockerFile for image</li><li>docker-compose spinning up image</li></ul></li><li>Yocto, SOA etc.</li></ul></li><li>Doc<ul><li>Playground (What, Why, How, Best Practices), Connections to other components, Dev, Use Cases etc.</li></ul></li><li>Scripts</li><li>Diagrams</li><li>Use Cases and examples (e.g. docker-compose collection for docker deployment)<br/><ul><li>hello-world</li><li>Christian's case</li><li>Sync</li><li>etc.</li></ul></li></ul></li></ul></li><li>Use cases and use outside the group<ul><li>Discussion of using docker-compose to organise use-case examples.</li><li>Discussion of possible uses of the playground within Covesa.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-8thNovember2023">8th November 2023</h2><p>Minutes:</p><ul><li><a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground">Central Data Service Playground</a><ul><li>Steve summarised the work over the last week.<ul><li>Main task tickets are now done for the Phase 1 PoC. In big picture terms main missing areas are testing and use cases.</li></ul></li><li>Caught Christian/Humza/Arnaldo up on last weeks discussions</li><li>Use Cases<ul><li>Christian posted an idea as input to slack and will add it to the Early Planning page. Some discussion of it has already taken place in Slack.</li></ul></li><li>Road map / timings<ul><li>Steve: It would be good to have Phase 1 running in some form by the end of year holidays. That's only 4-6 weeks away. AMM will come very quickly in 2024. Need to keep tempo up.</li><li>Christian: What is in Phase 1?</li><li>Steve: Some discussion in previous calls and the minutes but detail is not recorded. Goal was to quickly hack an early PoC that allowed us to trial somethings and have code to work with. But let's create a summary now.</li><li>Summary scope added to Early Planning page. Attendees agreed scope.</li></ul></li><li>MongoDB Realm<ul><li>Some discussion of Docker support and connecting it to WAII.</li><li>Arnaldo informs that like SQLite its intended to be linked to an app, rather than provide a standalone service.</li><li>Some discussion will be needed how best to interface it. Could create a shim to allow WAII to read/write to a Realm DB.</li><li>Arnaldo will consider Realm aspects.</li></ul></li><li>Proj Mgt<ul><li>Discussion of Github Project limitation that seems to require people to be a member of the COVESA organisation to be able to assign them in Project tickets. Paul will add missing people.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-1stNovember2023">1st November 2023</h2><p>Minutes:</p><ul><li><a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground">Central Data Service Playground</a><ul><li>Holiday today in Germany</li><li>Project Management<ul><li>Steve runs through what he has done for project setup. Github Project site and source rep created. Some tickets added. Links added to the project page.</li><li>People happy to try what has been created.</li></ul></li><li>Source license<ul><li>Steve: We will soon be creating code. Which license to use? There was some recent external queries about MPL-v2.</li><li>Paul: MPL-v2 remains the COVESA default.</li><li>No strong preferences expressed beyond something permissive.</li><li>Steve: Changing later can be a little painful so have a think and we can decide in a week or two. MPL-v2 is most likely candidate</li></ul></li><li>DBs<ul><li>No one present from MongoDB. DB discussed postponed. Steve will setup side meeting with Ulf and anyone interested in discuss WAII DB backend interface State Storage.</li></ul></li><li>Related projects<ul><li>WAII<ul><li>Ulf: Peter Wenzell's work on updated Docker support and feeder for RemotiveLabs sim playback has been merged to Master.</li></ul></li></ul></li><li>Requests:<ul><li>Please add any topic you think we should be investigating either to the Confluence Early Planning page or as a ticket to the Github Project.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-25thOctober2023">25th October 2023</h2><p>Agenda:</p><ul><li>AMM reminder: upload slides here <a href="https://wiki.covesa.global/display/WIK4/COVESA+All+Member+Meeting+~+October+10-12%2C+2023">COVESA All Member Meeting ~ October 10-12, 2023</a></li><li><a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground">Central Data Service Playground</a><br/><ul><li>Goal: kick-off and work breakdown</li></ul></li></ul><p>Minutes:</p><ul><li>Christian input:<ul><li>It would be good to define problems to be tackled down to guide project.</li><li>Similarly find use cases to illustrate/investigate problems</li><li>The group might maintain a set of use cases as a set of validation cases for the playground, e.g. made change but validation still passes.</li><li>Steve: <a class="confluence-userlink user-mention" data-username="Christian.CM.Muehlbauer@bmw.de" href="https://wiki.covesa.global/display/~Christian.CM.Muehlbauer@bmw.de" data-linked-resource-id="64979834" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Christian Muehlbauer</a> please consider adding (better version of my poor notes) this to the project page as input</li></ul></li><li>Ulf: VISS designed for wide range of use cases. This flexibility means that use cases may not be critical.</li><li>Ulf: Simulation only or deploy on h/w in a car?<ul><li>Steve: personally I think both is possible depending on what is being investigated.</li></ul></li><li>Humza: To what extent will the Playground contain application code to allow experimentation? Would there be controls demonstrating different setups for example.<ul><li>This lead to discussion of resources vs goals.</li><li>Steve: we are resource constrained. Personally I would have the base code implementing the playground, e.g. VISS+store and then alongside have the PoCs etc that show it being exercised. Then you have a seperation of intent and you avoid problems of maintaining use case PoCs over time if that is not required.<ul><li>Writes following tree to illustrate:</li><li>Playground functional base block: e.g. VISS + store</li><li>PoCs, e.g:<br/><ul><li>Large ECU sync PoC<ul><li>Multi instance of the containers representing ECUs</li><li>With some marshal app code to exercise it</li></ul></li><li>Internal trial PoC<ul><li>Figure out the latency of cool new protocol</li></ul></li></ul></li></ul></li><li>Christian draws good point to his earlier comment about validation cases. We might have some official 'exercise cases' that are maintained. Others agree based on discussion. The project/data-arch group may have some validation use cases that are maintained along with functional base block for validation and as they illustrate useful concept. Examples used for illustration in the discussion (not agreed list)<ul><li>High frequency data feed</li><li>Medium frequency data feed</li><li>Hello World</li></ul></li><li>Above discussions show that maintaining doc along side is important. Doc for use of functional base block, but also doc for the use cases. Supports understanding and adoption.</li></ul></li><li>Project management / operations<ul><li>PM task tool<ul><li>Steve: what do we use?</li><li>Paul: suggest github. JIRA hard to discover and hidden away.</li><li>Richard: we intend to use github in AOSP project.</li><li>Ulf: github</li><li>Steve: I dislike that github kanban boards have poor support for comments and know JIRA well, but happy to go with majority.</li><li>Steve: how do rest feel?</li><li>BMW, MongoDB happy with github</li><li><strong>Decision: </strong>Start with github kanban for project management</li><li><strong>Action: </strong>Steve to create. Others to fill in their backlog ideas once announced.</li></ul></li><li>Comms<ul><li>Steve: what to use? We should try and move more of the day to day discussion online to support 24/7 and different time zones.</li><li><strong>Decision: </strong>Covesa Community Slack. Create a new data-architecture channel.</li><li><strong>Action: </strong>Steve to create new channel and announce it.</li></ul></li><li>Phases<ul><li>In workshop we talked about using incremental delivery to iterate the playground. What are the major early phases?</li><li>Discussion favours doing simple early PoC code to help decide on source and project organisation.</li><li><strong>Decision: </strong>Needs refinement in the kanban board but first phase is 'create Playground PoC' along lines above.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-18thOctober2023">18th October 2023</h2><p>Agenda:</p><ul><li>Meeting invite: Christian, Sri</li><li>AMM wash-up<ul><li>Goal: what went well, could be better, sessions/input we should be aware of</li><li>General including input from related sessions, e.g. Ulf's southbound session</li><li>Data Architecture workshop<ul><li>Upload slides here <a href="https://wiki.covesa.global/display/WIK4/COVESA+All+Member+Meeting+~+October+10-12%2C+2023">COVESA All Member Meeting ~ October 10-12, 2023</a></li></ul></li></ul></li><li><a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+playground+proposal">Central Data Service playground proposal</a><ul><li>Goal: move towards project kick-off and work breakdown</li><li>Further input?</li><li>Agree next steps<ul><li>Do we have general agreement/understanding on what we are doing regarding the service itself initially (the big picture What) and can move to getting the ball rolling on the details (e.g. checking docker status and choosing requirements of some use cases) of the how?</li></ul></li><li>How to organise? e.g. Kanban, JIRA. Account for schedules and time zones by doing what we can online.</li></ul></li><li>AoB<ul><li>Adnan: serialisation<ul><li>Looking at msg serialisation between vehicle and car. Requirement to keep flexibility in terms of what is sent.</li><li>BMW will have a researcher looking into this. Can something be done in open? Payload only.</li><li>Looking for input.</li></ul></li></ul></li></ul><p>Minutes:</p><ul><li>Serialisation<ul><li>Adnan outlines (<a class="confluence-userlink user-mention" data-username="adnan.bekan@bmwgroup.com" href="https://wiki.covesa.global/display/~adnan.bekan@bmwgroup.com" data-linked-resource-id="34209860" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Adnan Bekan</a> correct me if my summary is incorrect):<ul><li>BMW will have a researcher looking into message serialisation between vehicle and car.</li><li>Scope is the payload only. Not the transport. However some flexibility in terms of what is sent in the payload is required.</li><li>Can something be done in the open in standardising this? Also looking for input on approaches.</li><li>Adnan notes the work done in the past during CVII Tech Stack days using AVRO with the esync alliance, but feels that is a heavyweight solution.</li></ul></li><li>Various suggestions made about some possible approaches, such as encoding methods that take advantage of sparcity or lack of change.</li><li>Steve: the cloud connection has been cold for a while but only because its been waiting for someone to run with it. This should be of interest a wide group. I would recommend writing an outline or proposal of what problems you want to tackle down, along with some requirements. From that other inputs can be gathered along with people to work on it and a project formed. This should be of interest to the Commercial Vehicle group for example and their telematics requirements.</li></ul></li><li>AMM wash-up<ul><li>Christian: various gateway solutions appearing, e.g. PennyBecker, HIM, Vehicle API etc. Implementations at different levels. Would be good to understand what they look to achieve as some are not directly comparable.</li><li>Arnaldo: difficulty for newcomers to get started. Wiki can be overcomplex to understand.<ul><li>Data Arch landing page needs cleanup / simplification.</li></ul></li><li>Neil: Agree. Some attendees talked to showed interest, but not everyone understands.</li><li>General agreement for the need for more guiding documents like HowTos.</li><li>Steve: I intend to remake the Data Arch landing page as discussed before the AMM to make it easier for newcomers.</li><li>Other sessions - Ulf southbound architecture session<ul><li>Steve: Peter Winzell said in the W3C slack that he was working on a southbound feeder to WAII connected to Redis. Is it related to your work.</li><li>Ulf: Peter is using the WAII feeder framework I described in my session. His feeder connects to the RemotiveLabs simulator. As part of his work he's also updated the WAII DockerFile to use the latest code.</li></ul></li></ul></li><li><a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+playground+proposal">Central Data Service playground proposal</a><ul><li>Only 10 mins remained. Will be main topic next week.</li><li>Steve: Please consider what the near term next steps are, what use cases you want to explore and how we should organise the work.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-12thOctober2023-AMMDataArchitectureWorkshop">12th October 2023 - AMM Data Architecture Workshop</h2><ul><li>(these are incomplete notes made after the event) </li><li>Workshop delivered as planned, except for compression of time on doc proposal:<ul><li>Mongo DB/BMW (9-9:45)</li><li>10-10:15 break</li><li>Central Data Service Playground (10:15 on)<br/><ul><li>Part 1: Readout of the proposal</li><li>Part 2: Workshop the base components and the possibilities for 'spins' using it<ul><li>As well as the names below <a class="confluence-userlink user-mention" data-username="piotr.krawczyk" href="https://wiki.covesa.global/display/~piotr.krawczyk" data-linked-resource-id="361352" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Piotr Krawczyk</a> <a class="confluence-userlink user-mention" data-username="neil@rti.com" href="https://wiki.covesa.global/display/~neil@rti.com" data-linked-resource-id="49643524" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Neil Puthuff</a> and <a class="confluence-userlink user-mention" data-username="halim.ragab@gm.com" href="https://wiki.covesa.global/display/~halim.ragab@gm.com" data-linked-resource-id="71074316" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Halim Ragab</a> actively engaged in the discussion, along with Arnaldo's colleagues. Apologies if I missed anyone from the list - let me know.<br/><ul><li>Piotr suggested MQTT as event queue (see whiteboard picture)</li><li>Halim was interested in the project but wanted to know the boundary performance (latency etc) of the Service to be able to understand how it would fit in the overall performance of an end to end touchpoint. He took an action to provide input on what GM requires.</li></ul></li><li>Outcome: Ford (<a class="confluence-userlink user-mention" data-username="ulf.bjorkengren" href="https://wiki.covesa.global/display/~ulf.bjorkengren" data-linked-resource-id="363862" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Ulf Bjorkengren</a>), BMW (<a class="confluence-userlink user-mention" data-username="Christian.CM.Muehlbauer@bmw.de" href="https://wiki.covesa.global/display/~Christian.CM.Muehlbauer@bmw.de" data-linked-resource-id="64979834" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Christian Muehlbauer</a>), MongoDB (<a class="confluence-userlink user-mention" data-username="arnaldo.vera@mongodb.com" href="https://wiki.covesa.global/display/~arnaldo.vera@mongodb.com" data-linked-resource-id="64979361" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Arnaldo Vera</a> <a class="confluence-userlink user-mention" data-username="humza.akhtar@mongodb.com" href="https://wiki.covesa.global/display/~humza.akhtar@mongodb.com" data-linked-resource-id="64979360" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Humza Akhtar</a>) and Renesas (<a class="confluence-userlink user-mention" data-username="stephen.lawrence" href="https://wiki.covesa.global/display/~stephen.lawrence" data-linked-resource-id="361705" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Stephen Lawrence</a> ) all expressed interest in actively contributing. Enough interest to begin the project.</li><li>Whiteboard Images:</li><li><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="250" src="https://wiki.covesa.global/download/attachments/46628897/Whiteboard2-deployment-and-next-steps.jpg?version=1&modificationDate=1697564067712&api=v2" data-image-src="https://wiki.covesa.global/download/attachments/46628897/Whiteboard2-deployment-and-next-steps.jpg?version=1&modificationDate=1697564067712&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="78840543" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Whiteboard2-deployment-and-next-steps.jpg" data-base-url="https://wiki.covesa.global" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="46628897" data-linked-resource-container-version="123" alt=""></span><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="250" src="https://wiki.covesa.global/download/attachments/46628897/Whiteboard-1.jpg?version=1&modificationDate=1697564064157&api=v2" data-image-src="https://wiki.covesa.global/download/attachments/46628897/Whiteboard-1.jpg?version=1&modificationDate=1697564064157&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="78840542" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Whiteboard-1.jpg" data-base-url="https://wiki.covesa.global" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="46628897" data-linked-resource-container-version="123" alt=""></span></li><li>Group shot after the end of the session:</li><li><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="250" src="https://wiki.covesa.global/download/attachments/46628897/End%20of%20session%20group%20shot.jpg?version=1&modificationDate=1697563999661&api=v2" data-image-src="https://wiki.covesa.global/download/attachments/46628897/End%20of%20session%20group%20shot.jpg?version=1&modificationDate=1697563999661&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="78840541" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="End of session group shot.jpg" data-base-url="https://wiki.covesa.global" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="46628897" data-linked-resource-container-version="123" alt=""></span></li></ul></li></ul></li><li>Documentation proposal discussion: 30 mins to be fitted in<ul><li>As the Playground workshop was going well this was condensed with Steve simply showing some slides on the wider eco-system need for documentation on HowTo's etc.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-4thOctober2023">4th October 2023</h2><ul><li>Christian back after a long holiday. Brought him up to speed and reconfirmed MongoDB/BMW session starting the Architecture workshop</li><li><a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+playground+proposal">Central Data Service playground proposal</a><ul><li>Steve had got enough of the draft outline written for the intention hopefully be clear. Ran through it with the group.</li><li>Little time left to discuss but Arnaldo, Christian and Ulf are postive about the discussion.</li><li>Once the runthrough is repeated for others in the work at the AMM an early task will be to get feedback from the Architecture members.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-27thSeptember2023">27th September 2023</h2><ul><li>AMM<ul><li>Discussion of what to report in the Data EG readout<ul><li>Data Arch<ul><li>Thurs AMM workshop</li><li>..</li><li>Ulf Southbound session</li></ul></li></ul></li><li>Data Arch workshop<ul><li>Arnaldo confirmed the MongoDB/BMW session.</li><li>Steve has written some of the outline for the <a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+playground+proposal">Central Data Service playground proposal</a> and went through it. Target will be to get more of it done for next week.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-20thSeptember2023">20th September 2023</h2><ul><li>AMM planning<ul><li>Workshop <br/><ul><li>Mongo DB/BMW input<ul><li>Christian on holiday. Arnaldo not present.</li><li>Steve: Anything discussed whilst I was away?</li><li>Paul B: Arnaldo does not want to run a PoC specific workshop in Detroit. MongoDB session currently moved out in schedule to accomodate possible workshop. Can move back if it makes sense.</li></ul></li><li>After discussion the running order from 6th Sept minutes still makes most sense. Basically take MongoDB/BMW sessions and <a class="confluence-userlink user-mention" data-username="ulf.bjorkengren" href="https://wiki.covesa.global/display/~ulf.bjorkengren" data-linked-resource-id="363862" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Ulf Bjorkengren</a> session on VISS southbound as input to move onto workshop the Central Data Service Playground propose.</li></ul></li></ul></li><li>Discussion of the Ford data model presentation prior Tues and the Blackberry IVY showcase webinar.</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-13thSeptember2023">13th September 2023</h2><ul><li>Paul Boyes facilitated meeting whilst Stephen was on holiday.</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-6thSeptember2023">6th September 2023</h2><ul><li>AMM planning<ul><li><a href="https://wiki.covesa.global/display/WIK4/AMM+Planning+October+10-12+2023+-+Technical+Session+and+Workshop+Proposals">AMM Planning October 10-12 2023 - Technical Session and Workshop Proposals</a></li><li>Thursday (9-12:15)<br/><ul><li>Mongo DB/BMW (9-9:30)<br/><ul><li>Christian says specifics depends on readiness of the PoC.</li><li>Plan A is to present evolution of the Tiered Sync they have been working on.</li><li>Recommends contacting Mongo DB to check what plan B is.</li></ul></li><li>Central Data Service Playground (9:30 on)<br/><ul><li>Part 1: Readout of the proposal (9:30-9:45/50)</li></ul></li><li>10-10:15 Break<ul><li>Part 2: Workshop the base components and the possibilities for 'spins' using it, e.g:<ul><li>Data models: knowledge layer, data models, VSSo</li><li>Interface pillar: IFEX, service definition, Vehicle API/Autosar</li><li>Data Architecture: Sync, reasoning at the edge etc.</li></ul></li></ul></li><li>Documentation proposal discussion: 30 mins to be fitted in</li></ul></li></ul></li><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71074417">Knowledge Layer proposal</a><ul><li>Christian will send slides for presentation he made last week</li></ul></li><li>Paul reminds about the Ford/VSSo presentation next week. See community calendar and slack for details</li><li>Holidays: <br/><ul><li>Christian: on holiday from 11th Sept, back 4th Oct. May check email/slack time to time.</li><li>Steve: holiday Tues 12th-Tues 19th.</li><li>Paul will host meeting next week.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-30thAugust2023">30th August 2023</h2><ul><li>Debrief of Christian's presentation of his <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71074417">Knowledge Layer proposal</a> Tues to VSSo group<ul><li>Has synergy with the Central Data Service playground</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-23rdAugust2023">23rd August 2023</h2><ul><li>Continue work on <a href="https://wiki.covesa.global/display/WIK4/Data+Architecture+Pillar+Proposals">Data Architecture Pillar Proposals</a></li><li>AMM planning</li><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71074417">Knowledge Layer proposal</a> presentation?</li><li>Holidays:<ul><li>Steve on holiday next week. Meeting? Yes, Paul will host.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-10thAugust2023">10th August 2023</h2><ul><li>With summer holidays a sparsely attended meeting this week. Started with 3, became 5 in 2nd half. As such more informal discussion.</li><li>Some discussion of Tim Welsch's meeting yesterday on Service Registry.</li><li>Some discussion of Christian's <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71074417">Knowledge Layer proposal</a> and what he is considering in certain areas.</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-2ndAugust2023">2nd August 2023</h2><ul><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71074417">Knowledge Layer proposal</a><ul><li><a class="confluence-userlink user-mention" data-username="Christian.CM.Muehlbauer@bmw.de" href="https://wiki.covesa.global/display/~Christian.CM.Muehlbauer@bmw.de" data-linked-resource-id="64979834" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Christian Muehlbauer</a> has posted his first outline</li><li>Steve: what would you like to achieve and how best to take this forward?</li><li>Details in the proposal but Christian would like to explore what would be needed to have a technology agnostic seperation between knowledge and the underlying areas. How would they interact and stay in sync etc.</li><li>After discussion about way forward, Christian happy for people to promote its existance. Paul/Steve will mention it to other groups. Christian will think how he would present the work in a future 1 hr type dedicated meeting to the topic.</li></ul></li><li>Document and diagram storage<ul><li>Steve was planning on creating data-arch-doc.git rep to get us started.</li><li>He brought topic up in Thursday call. Erik mentioned the existing (little used currently) Data EG git rep. That is probably a good place for top level diagrams like the scope diagram.</li></ul></li><li>AMM planning<ul><li>Steve has added a planning page here <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=75726889">2023 Autumn AMM (Data Architecture and Infrastructure)</a> </li><li>Steve: any feedback from request last week to consider what we want to discuss?<ul><li><a class="confluence-userlink user-mention" data-username="Christian.CM.Muehlbauer@bmw.de" href="https://wiki.covesa.global/display/~Christian.CM.Muehlbauer@bmw.de" data-linked-resource-id="64979834" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Christian Muehlbauer</a> discussing internally about what we might be able to show. Workshop could discuss knowledge layer proposal.</li><li><a class="confluence-userlink user-mention" data-username="arnaldo.vera@mongodb.com" href="https://wiki.covesa.global/display/~arnaldo.vera@mongodb.com" data-linked-resource-id="64979361" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Arnaldo Vera</a> Some possibilities we are discussing: Tooling for conversion to JSON-schema. Realm for OTA. Connected car sync.<ul><li>Steve mentions <a class="confluence-userlink user-mention" data-username="adnan.bekan@bmwgroup.com" href="https://wiki.covesa.global/display/~adnan.bekan@bmwgroup.com" data-linked-resource-id="34209860" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Adnan Bekan</a> <a href="https://github.com/COVESA/vss-tools/pull/296" class="external-link" rel="nofollow"> PR </a>for a VSS vspec to json-schema tool. Arnaldo will take a look.</li></ul></li><li><a class="confluence-userlink user-mention" data-username="stephen.lawrence" href="https://wiki.covesa.global/display/~stephen.lawrence" data-linked-resource-id="361705" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Stephen Lawrence</a> Store/Server playground, Design doc publishing.</li><li><a class="confluence-userlink user-mention" data-username="ulf.bjorkengren" href="https://wiki.covesa.global/display/~ulf.bjorkengren" data-linked-resource-id="363862" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Ulf Bjorkengren</a> plans to present update on HIM including new additions.</li></ul></li><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> interesting to see conceptual design/requirements for connecting signals to non-signal info/knowledge in-vehicle and on to cloud.<ul><li>Discussion of how this relates to other areas. Some topics likely best as a wider group workshop, e.g. combining data models</li><li>Paul will be posting table for Thursday tracks for planning purposes</li></ul></li></ul></li><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71073902">Data Pattern proposal</a><ul><li>Steve has restarted completing the text. Currently working on the publishing section</li></ul></li><li>Data Arch front page redo is open AI.</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-26thJuly2023">26th July 2023</h2><ul><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71073902">Data Pattern proposal</a><ul><li>No change due to the collab meetings last week. Meetings confirm the need - see below.</li><li>Steve will return to completing the draft.</li></ul></li><li>Knowledge layer proposal<br/><ul><li>Christian catching up after holiday. Still intends to upload the proposal for feedback.</li></ul></li><li>Topics arising from collaboration meetings (EU Horizon, SDV Summit, Covesa Board F2F) last week<ul><li>The Covesa Scope diagram was used in EU Horizon SDV group to discuss SDV. It was also used in SDV Summit.</li><li>This both shows Covesa materials being used externally and their value. Basically further proof of the need being addressed in the Data Pattern proposal</li><li>This flags again some recent topics: where to store them and enhancing discoverability for external people</li><li>Christian had been considering a diagram showing how Data Arch relates to the other topics. He'll have a go at drafting it.</li></ul></li><li>Git rep / where to put diagrams<ul><li>We have had some discussion previously but now with the external use we need to move to a solution to encourage re-use.</li><li>Steve: I still am not in favor of a 'big bucket' repository containing all source and docs. Source should be organised by product for reuse. I would suggest starting with a git rep dedicated to documentation, e.g. data-arch-doc.git</li></ul></li><li>Discoverability<ul><li>Feedback from last week shows discoverability could be improved.</li><li>Christian: when I first came to Covesa/VSS work I found it easiest to orientate myself from the VSS (Hugo) document website.</li><li>We know this and had been prioritising getting the tech work going. However now need to address it.</li><li>Three main touchpoints immediately come to mind:<ul><li>data-arch-doc.git<ul><li>Holding doc, diagram source</li></ul></li><li>Hugo data arch documentation website<ul><li>Serving rendered documents as per the document proposal</li></ul></li><li>Confluence Data Arch landing page</li></ul></li></ul></li><li>Reforming group landing page<ul><li>Steve: I'll try and find the time to bring the Data Arch Landing Page up to date, e.g. show the Scope diagram there. At least a draft for review by the group.</li></ul></li><li>AMM<ul><li>Steve: we need to start considering what we want to do at the AMM.<ul><li>I would expect a Data Arch pillar intro as usual, possibly as part of Data EG intro.</li><li>I would also expect somekind of combination workshop + presentations for the Thursday as we have done in the past, but need your input.</li></ul></li><li>AI: Consider what you want to discuss/present</li></ul></li><li>Discussion on process of creating content for Hugo documentation website<ul><li>Christian: People may think it is a single persons viewpoint if its all markdown in a single git post</li><li>Steve: Yes collaboration on the text will be needed in many cases. I would suggest for such documents the draft text be worked on somewhere collab is easier. Confluence has inline comments for example. Of course direct to markdown or something else is also possible. Point is to make it easier to comment and discuss.</li><li>Steps could be:<ul><li>Creation stage:<ul><li>Collab on text (Confluence, whatever)</li><li>Convert to markdown(github)</li><li>Sign-off</li></ul></li><li>Publishing stage:<ul><li>Move markdown to Hugo tree</li><li>CI Runner generates Hugo site and publishes to production<ul><li><Possible to have a parallel CI for WIP if needed></li></ul></li></ul></li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-19thJuly2023">19th July 2023</h2><ul><li>No meeting due to collaboration meetings F2F in Cologne</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-12thJuly2023">12th July 2023</h2><p>Agenda:</p><ul><li>Data Pattern / Arch proposal<ul><li>Discussion of changes since last week</li></ul></li><li>Knowledge layer<ul><li>No discussion as Christian on holiday</li></ul></li><li>Next meetings / holiday planning<ul><li>Ulf: 2 weeks after F2F</li><li>Arnaldo: last two weeks</li><li>Richard: 18-21st Aug.</li><li>Meeting cancelled Weds 19th due to meetings in Cologne</li></ul></li><li>News<ul><li>VISS WAII reference implementation<br/><ul><li>gRPC added to MQTT, WS and HTTP as transport protocol. Payload is compatiable with the others.</li><li>Discussion pending in W3C VISS standards group to add gRPC to VISSv2 standard.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-5thJuly2023">5th July 2023</h2><ul><li>Knowledge layer<ul><li>Christian has made further progress on his document.</li><li>Discussion of some of the points.</li><li>It is complete enough that Christian would soon like to get feedback and input and asks about how best to do that.</li><li>In terms of publicity Steve says Paul can help, but he would suggest other Data EG meetings and the slack.</li><li>In terms of publishing Steve says he was meaning to add a "Proposals" sub-page to the Data Arch Confluence to organsie proposals under including his own Doc proposal<ul><li>Steve creates <a href="https://wiki.covesa.global/x/fIE8B" rel="nofollow">https://wiki.covesa.global/x/fIE8B</a></li></ul></li></ul></li><li><a href="https://wiki.covesa.global/x/boA8B" rel="nofollow">Data Pattern / Data Architecture proposal</a><ul><li>Resolved new comment from Christian</li><li>The Current Situation section draft is now complete.</li><li>Started work on the proposal section. Added some bullets to the summary outline.</li></ul></li><li>Next few meetings<ul><li>Steve: I may have a funeral to attend next Weds. There is also the Board F2F the following week and I will not be able to run the meeting. Do you still want to meet?</li><li>Holidays:<ul><li>Christian: July 6→16th,</li><li>Ulf: not confirmed but expect End of July→mid Aug</li><li>Steve: considering a week at the end of July but would probably be around to run the meeting.</li></ul></li><li>As only three people on the call Steve will send an email to the group to see what people want to do.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-28thJune2023">28th June 2023</h2><ul><li>Knowledge Layer<ul><li><a class="confluence-userlink user-mention" data-username="Christian.CM.Muehlbauer@bmw.de" href="https://wiki.covesa.global/display/~Christian.CM.Muehlbauer@bmw.de" data-linked-resource-id="64979834" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Christian Muehlbauer</a> showed the state of his work (currently in Word doc) on his Knowledge Layer ideas.</li><li>Positive feedback for him to continue.</li><li>Some discussion of the implications.</li><li>Arnaldo raises point about sharing knowledge decision is analogous to conflict resolution in data centric arch sync. Who decides the knowledge, communicates it and receives an update. Only want to store state when it changes.</li><li>Steve suggested a top down approach to the description to seperate the most generic ideas from the more specific ones. Basically to avoid a 'must adopt it all to be relevant' issue.</li><li>Steve asked Christian to let us know when he wanted to get a wider view on the work.</li></ul></li><li><a href="https://wiki.covesa.global/x/boA8B" rel="nofollow">Data Pattern / Data Architecture proposal</a><ul><li>Steve has made some good progress since last week.</li><li>Majority of the text for the current state of play is now done.</li><li>Will now move onto next steps.</li><li>Socialised the initial proposal and the idea to use Hugo for publishing to Technical Steering Committee and Data Expert Group with no push back.</li></ul></li><li>Git rep naming<ul><li>Steve gave some thought to this after last weeks discussion.</li><li>Still reluctant to have a single 'big bucket' git rep for the usability and maintainability reasons that is not normally done in engineering practise.</li><li>However likely don't want 20 reps either.</li><li>Steve: How about as a starting point to have some level of classification to narrow its scope, e.g. data-arch-doc.git or data-arch-doc-arch-patterns.git?</li><li>No clear answer. Team asked to think on it as we will need to make a decision fairly soon.</li></ul></li><li>News<ul><li><a class="confluence-userlink user-mention" data-username="ulf.bjorkengren" href="https://wiki.covesa.global/display/~ulf.bjorkengren" data-linked-resource-id="363862" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Ulf Bjorkengren</a> has published documentation in his HIM proposal</li><li>In VSSo call there was a heads up that Daniel Wilms had a proposal for using GraphQL schema to create VSS graphs. Intention was to present to the VSS group in a couple of weeks.</li><li>Adnan explains that Data Centric Architectures has been listed as a need in the topics to be tackled within the EU Horizon SDV project.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-21stJune2023">21st June 2023</h2><ul><li>Data Arch rep naming discussion<ul><li>Short initial discussion of how to organise git repositories for the data arch pillar.</li><li>Single 'big bucket' vs project specific?</li><li>Ulf suggests big bucket</li><li>Steve concerned about maintainability of big bucket.</li><li>Steve: please consider what you want and we will discuss again</li></ul></li><li>Refining Steve's <a href="https://wiki.covesa.global/x/boA8B" rel="nofollow">Data Pattern / Data Architecture proposal</a> <ul><li>Steve outlined his idea to use online publishing paradigm already used in Covesa for VSS doc. Brings all the docs together and is useful to link to for non-engineers.</li><li>Feedback was positive.</li><li>Christian added comment about sync which is now resolved</li><li>In meeting added Knowledge layer as a topic to the content list<br/><ul><li>Christian working on outline based on idea he explained recently</li><li>Wants to know where he would put it?</li><li>Steve: need to resolve the question of data arch rep naming. In meantime depending on your format you can push to the google drive, create personal git rep, or I can create you one in my area.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-14thJune2023">14th June 2023</h2><ul><li>Knowledge layer (45 min)<ul><li><a class="confluence-userlink user-mention" data-username="Christian.CM.Muehlbauer@bmw.de" href="https://wiki.covesa.global/display/~Christian.CM.Muehlbauer@bmw.de" data-linked-resource-id="64979834" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Christian Muehlbauer</a> has noted that in the Covesa organisation slides showing the Data EG pillars that the knowledge layer is listed under the Data Models / Ontologies. Should it be in Data Architecture instead/as well?<ul><li>Discussion of the question. Christian has a draft diagram showing Machine Learning and Semantic Reasoning (requires ontologies like VSSo) acting on VSS data as a means for deriving high level knowledge. This is an example of how the Knowledge Layer is also applicable to Data Architecture. Ulf likes the diagram and mentions he intends to explore some of this in his HIM project.</li><li>One area of possible interest is standardised knowledge representations. You derive some knowledge from standard data. Is there a standard way to represent the knowledge? This has benefits in loosly coupling the knowledge, from possible consumers.</li><li>Conclusion is everyone agrees that it also applies to Data Architecture in such a context and could be considered part of the scope. Open question as to how to include it in such a summary slide. For sure it could be part of any Data Architecture pillar description that was not so space constrained.</li></ul></li></ul></li><li>Data Pattern / Data Architecture proposal (15 mins)<ul><li>As discussed last week Steve has started work on a proposal for Design Pattern and Data Architecture documentation which can be found here <a href="https://wiki.covesa.global/x/boA8B" rel="nofollow">https://wiki.covesa.global/x/boA8B</a></li><li>Principal aim is to use it facilitate what to create.</li><li>Short on time so quick run through. It's still a WIP towards a draft. Please edit or add in-line comments.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-7thJune2023">7th June 2023</h2><ul><li><a href="https://wiki.covesa.global/x/JYDHAg" rel="nofollow">Data Architecture Terminology</a>.<ul><li>Following last weeks discussion Steve has moved the Data Sync description from Data Store into its own section.</li></ul></li><li>Next steps in the high level work..<ul><li>S: There has been some useful conversations at the AMM and after that built understanding. I would like to focus a discussion on advancing the high level <em>shared </em>work in the group.</li><li>Revisiting needs<br/><ul><li>Top down<ul><li>We know there is a need for a set of shared high level views. Both internally in the group and externally as newcomers try to understand VSS and it's eco-system.</li><li>As we have discussed where sensible these should use logical components to avoid getting trapped down in the weeds in system architecture, product selection etc.</li><li>For illustration some examples:<ul><li>Terminology</li><li>Common patterns</li><li>Building blocks both descriptive and PoC (trial, playgrounds etc.)</li><li>User stories and deployment scenarios illustrating the combination of the above</li></ul></li></ul></li><li>A few of us have been illustrating some examples previously and most recently.<ul><li>e.g. Adnan last week showed some early high level diagrams in the field of VSS+methods / services / vehicle API<ul><li>Scenario 1: HVAC service <=> gateway (vehicle API - VSS Data model) | Autosar / RT / RTOS (southbound low level parts)<ul><li>RT area may contain proprietary information and ASIL that is contained.</li><li>Gateway provides abstraction API to e.g. get/set/sub VSS data</li><li>HVAC service provides service API to rest of system. Acting both as an abstraction and handler for the complexities of the southbound system. e.g. something like HVAC is often CAN based which brings complexity when trying to set values.</li></ul></li></ul></li><li>Felix illustrated two data store variants last week</li><li>Whilst thinking about it Steve was reminded of similar high level descriptions in <a href="http://github.com/slawr/vss-otaku" class="external-link" rel="nofollow">http://github.com/slawr/vss-otaku</a></li><li>Various earlier ones: Miro, Ulf's work, AMM etc.</li></ul></li></ul></li><li>S: I propose to combine high level description with these kind of light weight illustrative examples in diagram+text form as a way forward.<ul><li>I think I will follow the approach <a class="confluence-userlink user-mention" data-username="Daniel.Alvarez-Coello@bmwgroup.com" href="https://wiki.covesa.global/display/~Daniel.Alvarez-Coello@bmwgroup.com" data-linked-resource-id="64979646" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Daniel Alvarez</a> has taken to his <a href="https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts" rel="nofollow"> VSSo proposal </a>of a top down logical approach, avoiding solutions and write up a proposal for some documents that can be commented and the beginning of the next phase of shared work.</li></ul></li><li>Brain storming some classifications:<br/><ul><li>Patterns / building blocks:<ul><li>Data Server, Data Store<ul><li>Variants: Mobile App, in-vehicle app, Domain Data Service</li></ul></li><li>Integration<ul><li>Variants: data flow bi/uni-directional, conflict resolution, latency, volume, frequency</li></ul></li><li>Scenarios<ul><li>Snapshots focusing on specific areas: Vehicle API, Service + gateway (as in Adnan example above), etc.</li><li>Data EG Deployment scenarios: IVI, Smart device, Car2Cloud, Cloud2Cloud,</li><li>Data EG Touchpoints</li></ul></li></ul></li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-31stMay2023">31st May 2023 </h2><ul><li><a href="https://wiki.covesa.global/x/JYDHAg" rel="nofollow">Data Architecture Terminology</a>.<ul><li>Steve presented updated terminology that has a first pass approach to adding Data Store sync<ul><li>Felix suggested moving Sync into its own component description. That matches one of the options previously discussed. Steve happy to try it that way also.</li></ul></li><li>Wide ranging discussion of the needs and approaches to getting at a flexible, reusable set of high level component diagrams/descriptions</li><li>Felix diagrammed some options re the Data Server and Data Store variants. Discussion included differences between a 'fat' Data Store that might be connected to a Data Gateway, versus an in-vehicle application (e.g. following MVC design pattern) that has an API and local 'thin' Data Store dedicated to it.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-24thMay2023">24th May 2023</h2><ul><li><a href="https://wiki.covesa.global/x/JYDHAg" rel="nofollow">Data Architecture Terminology</a>.<ul><li>Steve has reworked the VSS-Feeder component text to be VSS Connector as discussed last week.</li><li>Discussion of handling Data Sync function as its own component so it can be a part of both Data Server and Data Store. Agreement to try it that way. Arnaldo will take a look at the description based on their experience with Realm Sync.</li></ul></li><li>PoC<ul><li>Ulf asks about the goals of the PoC. After summary from Steve (see 10th May minutes for summary) he thinks it could be useful and hopes to find some time to participate.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-17thMay2023">17th May 2023</h2><ul><li>Minutes made a week later and so may be less complete</li><li><a href="https://wiki.covesa.global/x/JYDHAg" rel="nofollow">Data Architecture Terminology</a>.<ul><li>Continued review discussion</li><li>Sync<ul><li>Christian provided input offline about including Sync as he has discussed in his presentations.</li><li>Open question was how best to include it and preserve the fact that the functional descriptions can be combined in a product. So whilst it might be most likely in the State Storage as he has been using it, it could be elsewhere. Perhaps describe it as component itself, which can then be used by either State Storage or Server?</li></ul></li><li>Data Feeders<ul><li>Ulf feels Feeder suggests a uni-directional flow Northbound when it could be in both directions. Can we rename to something else? He suggests Bridge but is open to alternatives.</li><li>Steve also suggests Connector.</li><li>Steve will try rewriting the description using the suggested names.</li></ul></li></ul></li><li>Diagrams<ul><li>Steve has started recreating the Deployment Scenario diagrams from the 2023 Q1 Workshop in Miro <a href="https://miro.com/app/board/uXjVPoh2zow=/?share_link_id=262317958896" class="external-link" rel="nofollow">https://miro.com/app/board/uXjVPoh2zow=/?share_link_id=262317958896</a> in DrawIO so they can be easily shared, and edited.</li><li>As a working area he has created the sub-folder <a href="https://drive.google.com/drive/folders/1SrLxqRX9UfV7ljMKlmfLxNVQg_etIXpF?usp=share_link" class="external-link" rel="nofollow">Deployment_scenarios</a> in the Data Arch scratch area of the Data Expert Group Google Drive.</li><li>First diagram to be converted was the top level Logical Architecture showing the Data Expert Group scope which can be found here <a href="https://drive.google.com/file/d/1qMDFxmVCFFBPZ30bI9sWoWestVIrg-1y/view?usp=share_link" class="external-link" rel="nofollow">Logical Architecture Overview.drawio.svg</a><ul><li>This was a first pass conversion. Not yet looked to see if it needs resizing to fit into common use cases in A4 document or slide</li></ul></li><li>Happy to get help in recreating the others..</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-10thMay2023">10th May 2023</h2><ul><li><a href="https://wiki.covesa.global/x/JYDHAg" rel="nofollow">Data Architecture Terminology</a>.<ul><li>Steve did first pass review and made some edits.</li><li>Got feedback from Felix.</li><li>Intention is that along with the diagrams this becomes the basis for 'logical component' discussion in the Data Expert Group</li></ul></li><li> Diagrams<ul><li>Christian: We should show that the data server/state storage combination in-vehicle can be reused in the cloud and mobile device as well, i.e. data centric architecture reuse of arch.</li></ul></li><li>PoC<ul><li>Christian: Is this intended to be public?</li><li>Steve: Yes</li><li>Illustrations to show possibilities:<ul><li>Covesa github all public</li><li>x86 docker<ul><li>Major components of the basic 'lego':<ul><li>VISS data server, e.g. WAII</li><li>State Storage, e.g. add Realm, Apache IoTDB</li></ul></li><li>Step 1: DBs via WAII (CCS) State Storage component</li><li>Step M..N trials using the basic lego to prove/investigate various topics:<ul><li>High frequency</li><li>Knowledge pyramid, AI at the edge</li><li>Multiple data models</li></ul></li></ul></li><li>Automotive H/W<ul><li>Generic code could be implemented on Automative H/W for some appropriate topics, e.g Latency Southbound</li></ul></li><li>Feedback:</li><li>Piotr: Could have a PoC variant that shows support for different OSs via vsock for example to show possibility of southbound data from various sources in the car.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-3rdMay2023">3rd May 2023</h2><ul><li>Welcome to Arnaldo Vera from MongoDB. Short overview of the work of the Data Architecture pillar.</li><li>People report successful AMM</li><li>Combining VSS with other data models<ul><li>Logistically neither Ulf or Christian get to each others presentations on this subject</li><li>Positive discussion to look at the proposals and find commonalities for way forward</li></ul></li><li>Logical Components / Terminology<ul><li>Discussion of the usefulness of logical component diagrams as found in the<a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group%3A+Architecture+and+Infrastructure"> CVII Tech Stack/CCS diagrams </a>and the <a href="https://wiki.covesa.global/x/JYDHAg" rel="nofollow">Terminology Dictionary</a>.</li><li>Avoids the competitive aspects of talking about products, falling into specific system architectures and gives a common approach for discussion.</li><li>Useful for design patterns, deployment scenarios and architecture documents.</li><li>How to move towards a common view?<ul><li>Review terminology list.</li><li>Christian will see how the components fit the i7 showcase demo.</li><li>Collectively iterate both the terminology and diagrams.</li></ul></li></ul></li><li>Data Server / State Storage PoC basic building block<ul><li>Steve summarised the discussion Thursday at the AMM to create a basic building block PoC consisting of a Data Server and State Storage.</li><li>The aim is a reusable component that could be configured to extend it for use in various deployment scenarios, e.g. connecting Vehicle API gateway.</li><li>At the same time the basic block could also be used to investigate connections between server and storage, e.g. low latency data.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-26thApril2023">26th April 2023</h2><ul><li>No meeting due to AMM</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-19thApril2023">19th April 2023</h2><ul><li>AMM planning<ul><li>Steve added an AMM sub-folder to the group scratch Google Drive:<ul><li><a href="https://drive.google.com/drive/folders/1R4HJc7g-q-3WmjXm1DyJfzdaHiv0Auvj?usp=share_link" class="external-link" rel="nofollow">https://drive.google.com/drive/folders/1R4HJc7g-q-3WmjXm1DyJfzdaHiv0Auvj?usp=share_link</a></li></ul></li><li>Tues Intro<ul><li>Steve has merged the prior outline into the template and uploaded a new working draft to the above folder.</li><li>Needs completing by Steve/Christian</li></ul></li><li>Thur Data Arch Workshop<ul><li>After discussion agreed final workshop makeup.</li><li>See planning page <a href="https://wiki.covesa.global/display/WIK4/2023+Spring+AMM+%28Data+Architecture+and+Infrastructure%29+Workshop">2023 Spring AMM (Data Architecture and Infrastructure) Workshop</a></li><li>Paul: we should invite the ontology group to the data model discussion.</li><li>AI: Need to ask data-science/ontology group to the session.</li></ul></li><li>Arrivals<ul><li>Christian arriving Sunday, but working on car Monday. Steve Sunday. Felix Monday.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-12thApril2023">12th April 2023</h2><ul><li>AMM planning<ul><li>Tues Intro<ul><li>Steve/Christian discussed the outline.</li><li>Steve will redo the draft outline in the AMM template towards end of the week.</li><li>Christian will work on his Data Centric slides in parallel.</li><li>Aim to merge and finalise next week</li></ul></li><li>Wed Deployment Scenarios<ul><li>Nothing new to discuss</li></ul></li><li>Thur Data Arch Workshop<ul><li>No outlines yet from Christian or Felix (see last week) for their proposals, or Felix's workshop.</li><li>Christian: I am meeting with Felix tomorrow in Munich and should be able to finalise my session afterwords.</li><li>Discussion of Deployment Scenarios proposal. See workshop planning page for notes.</li><li>Piotr: Might be idea to put Deployment first in the running order as somewhat of an introduction.</li><li>Piotr: One topic for discussion could be the management of version compatibility between components<ul><li>Piotr describes some examples. Such as Vehicle API supporting different VSS versions</li><li>Steve: Interesting questions. Can you create something like a summary of the problem scope and what needs to be tackled? That could then be used in various ways at the AMM, e.g. Vehicle API workshop Friday and afterwords.</li><li>Piotr: yes.</li></ul></li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-5thApril2023">5th April 2023</h2><ul><li>AMM planning<ul><li>Intro<ul><li>Steve: As the Intro contains slides from Christian on his views on Data Centric Arch would he like to present that part?</li><li>Christian: OK</li></ul></li><li>Deployment Scenarios<ul><li>Steve expresses concern that we (Data EG) advance the Deployment Scenarios whilst at the AMM. 1.5h session is not enough..</li></ul></li><li>Data Arch Workshop<ul><li>Share updates and proposals:<ul><li>Christian thinks he can do a Different Data Domains (approx 20-30 mins)<ul><li>Presentation on BMW experience.</li><li>Starting from using personal data as example of different data domain and moving to data middleware.</li><li>Steve: m/w may be handy bridge towards follow on discussion of persistence</li></ul></li><li>Felix: Persistence<ul><li>Presentation on classifying different persistence options</li></ul></li><li>Steve: Persistence<ul><li>Steve: My usual topics:<br/><ul><li>Data Server to Data Store connection, including high volume data</li><li>How Data Store can support Data Centric Arch, e.g. Data analytics using TS DB features</li><li>etc.</li></ul></li></ul></li><li><strong>AI:</strong> Add outlines for each proposed session to the planning page so ppl have an idea of what is to be discussed and what the hoped for outcome is.</li></ul></li></ul></li><li>Thurs PM/Friday<ul><li>Return of experience: Felix proposed a workshop using tech from the work between BMW and Mongo.</li><li><strong>AI (Felix): </strong>add outline to the planning page as above.</li><li>From discussion this could be scheduled Thurs PM</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-22ndMarch2023">22nd March 2023</h2><p>Agenda:</p><ul><li>Roadmap creation<br/><ul><li>Any updates on internal discussions / Action Items</li></ul></li><li>AMM Sessions: Intro, Deployment Scenarios, Workshop</li></ul><p><br/></p><ul><li>Roadmap creation<ul><li>Updates on internal discussions / Action Items?<ul><li>Christian summarised the result of BMW discussions about the AMM. It's not finalised by some update on results from the internal PoC work should be possible. Unclear at the moment if its a longer session, video of the PoC, or some slides.</li></ul></li></ul></li><li>Organisation<ul><li>A <a href="https://wiki.covesa.global/display/WIK4/Planning+Pages">Data Arch Planning Page</a> has been added into the Data Arch Confluence tree to organise planning pages. Including a sub-page for the upcoming <a href="https://wiki.covesa.global/x/MIDfAw" rel="nofollow">AMM Data Arch Workshop</a></li></ul></li><li>AMM<ul><li>Steve summarised the three main Data Arch sessions:<ul><li>Tues PM: "Data Arch Intro (currently called "Data Centric Arch" in schedule)" (Steve/Adnan)</li><li>Weds PM : "Deployment Scenarios" diagrams (Adnan/Erik/Steve)</li><li>Thurs AM: 9-11am Data Arch Workshop (all)</li><li>In addition there is a Data Expert Group general update that will mention the Data Arch pillar (Steve) and Friday an all day Data EG Workshop which of course will include Data Arch topics</li></ul></li><li>Data Arch Intro<ul><li>Steve showed a rough outline of the ppt discussed previously<ul><li><a href="https://wiki.covesa.global/download/attachments/46628897/Data%20Arch%20Intro.pptx?version=1&modificationDate=1679513256136&api=v2" data-linked-resource-id="64979008" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Data Arch Intro.pptx" data-nice-type="PowerPoint Presentation" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-linked-resource-container-id="46628897" data-linked-resource-container-version="123">Data Arch Intro.pptx</a></li></ul></li><li>Group agrees with the approach</li></ul></li><li>Workshop<ul><li>Steve: I would like to have a topic skeleton for us to follow to keep things on track and avoid too much unproductive tak</li><li>Felix suggests 3-4 topics if we have two hours</li><li>Felix and Steve both interested in Data Storage/Persistance.</li><li>Christian suggests requirements of "Different Data Domains (which means also models)"</li><li>Discussion of possibilities <br/><ul><li>Felix offers to do 10 mins on OSS version (minus sync) of Realm</li><li>Steve shows the diagram hacked on last week which facilitates discussion of relationship between storage, server and feeder (Felix away last week). Interested in possibilities that functional storage brings, e.g. alternator health example. Felix makes good suggestion to have cleaned-up version which includes high level topics to tackle down (saves jumping around slides in discussion)</li></ul></li><li>Group agrees this is a way forward. Needs further work.</li><li><strong>AI (Steve): </strong>Provide a placeholder abstract for the Thursday workshop. Website currently shows the one from last year.</li><li>Timings<ul><li>Steve: Thursday PM is not packed with sessions so we may be able to expand if needed.</li><li>Felix: I do not leave until Sunday.</li><li>Steve: I am the same.</li><li>Steve: Friday is more a general Data Expert Group workshop but we can of course bring Data Arch topics.</li></ul></li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-15thMarch2023">15th March 2023</h2><ul><li>Welcomed new participant from Aicas.</li><li>AMM<ul><li>Friday workshop<ul><li>Paul: who can make it?</li><li>Christian: BMW (Christian/Adnan/Andre) has an appointment Friday. Need to have internal discussion about what we can do that day</li><li>Piotr: Flying later, should be available in the morning.</li><li>Ulf: Need to leave in the afternoon for my flight</li><li>Steve: available all day</li></ul></li><li>Steve: That's useful as it shows that the Thursday morning workshop 9-11am will be important moment when we all there. Need to plan to use that time and Friday AM wisely and have an outline of what we are discussing.</li></ul></li><li>In-vehicle Data Stores<ul><li>Steve reports that he's restarted work adding further storage options as backend to WAII VISS server. Shows rough diagram to illustrate.</li><li>Initial discussion of some possibilities that could enable</li><li>Christian: the diagram shows data store holding VSS data. Wouldn't it be useful for other data models also to be stored?</li><li>Steve: Completely agree. The box is a hold over from the Covesa Tech Stack in-vehicle diagram and should be amended. This is definitely about the arch supporting the various data models required.</li><li>Piotr brings up some possibilities using a message queue as a data feeder northbound and southbound of data server</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-8thMarch2023">8th March 2023</h2><p>Agenda:</p><ul><li>Roadmap creation</li><li>AMM organisers need to finalise schedule</li></ul><p><br/></p><p>Minutes:</p><ul><li>AMM schedule<ul><li>Weds<ul><li>Paul: There will me a mgt level VSSo session (as opposed to down in the weeds of VSSo syntax) to be delivered by VSSo team<ul><li>Explain use case and ask for more..</li></ul></li></ul></li><li>Thurs technical track<ul><li>Currently Data Architecture scheduled 9:00-11:00<ul><li>Technical intro</li><li>... <tbd></li><li>Steve: We need to decide an abstract for this session ASAP</li></ul></li></ul></li><li>Friday workshop</li></ul></li><li>Discussion / updates<ul><li>Christian summarized some internal discussion. Defining other data domains. Personal data one example. Lessons learned from a few years ago (explained in earlier AMM presentation) starting with using VSS which moved to need for VSSo. He will be talking to Daniel Alverez. BMW may present something at AMM but not yet clear.</li><li>Felix: Interest in data persistence in-vehicle and data models. They are interested in performant needs for query of automotive data, e.g. GPS data as an area filter.</li><li>Steve: we have just released v2 of our OSS <a href="https://www.renesas.com/us/en/blogs/anyone-can-easily-start-introducing-renesas-new-development-environment-r-car-s4-whitebox-sdk" class="external-link" rel="nofollow"> Whitebox SDK </a>for our R-Car S4 SoC. Included is a Yocto recipe for the WAII VISS Server. The OSS nature of the SDK means it will be a natural integration point for me for our work.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-1stMarch2023">1st March 2023</h2><ul><li>Ulf outlines his plan to present forest of data model idea at AMM</li><li>Christian: Internally we have been looking at Ontologies and generation of data models. So interested to discuss Ulf's forest of data model ideas.</li><li>Piotr: Interested in interfacing southbound native data via messaging northbound to VSS.</li><li>Moving forward..<ul><li>Steve: Need to keep eye on mid-term and the roadmap. What we do together. If there is not an appetite to document an architecture as a first step what are we doing instead? Work on viewpoints/touchpoints to find commonalities? Perhaps document some fragments or illustrations - I feel we there are some interesting discussions but we are not capturing.</li><li>Ulf will document his "VISS" viewpoint over next couple of weeks.</li><li>Christian will sketch some areas he is interested in. He will also discuss internally?</li><li>AMM<ul><li>Intro presentation<ul><li>What<ul><li>Scope diagram</li><li>Goals/motivations and some questions</li></ul></li><li>How<ul><li>Documenting Viewpoints/touchpoints</li><li>Call to action on input/participation</li></ul></li></ul></li><li>What sessions for Thursday? Want to encourage broard input but also need to keep eye on the roadmap</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-22ndFebruary2023">22nd February 2023</h2><p>Agenda:</p><ul><li>Workshop debrief<ul><li>Do we have agreement on some high level points?<ul><li>Acceptance of the zone arch diagram from Miro</li><li>Creation of Data Arch / Pattern<ul><li>Outline:<ul><li><p>Document Goals, Motivations, Questions - Stephen, Andre, Christian, Adnan</p></li><li><p>Illustrate Design Patterns - Stephen, Andre, Christian, Adnan</p></li><li><p>POC Definition [ongoing] - Stephen, Andre, Christian, Adnan</p></li></ul></li></ul></li></ul></li></ul></li><li>Arch / Pattern outline Qs<ul><li>General approach / form</li></ul></li></ul><p>Minutes:</p><ul><li>Debrief<ul><li>General agreement around the high level arch diagram and results from the workshop.</li><li>Ulf: Detail - Revisit arched line from computing to HU in top level diagram</li><li>Ulf: More than one arch may be possible, e.g. data centric, interface centric (e.g. CCS centricity around VISS)</li></ul></li><li>Roadmap<ul><li>Steve outlined some possible approaches to describing a data architecture and associated patterns electronically.<ul><li>As discussed in the workshop moving from the general (Goals, Motivations, Questions) to specifics such as Design Patterns and Touchpoint illustrations.</li></ul></li><li>Andre will have internal discussion about this</li><li>Goal remains to build out a work plan</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-15thFebruary2023">15th February 2023</h2><ul><li>Normal hourly meeting cancelled in favor of two afternoons (Weds, Thurs) of workshops to advance the general data architecture discussion.</li><li>See Miro <a href="https://miro.com/app/board/uXjVPoh2zow=/" class="external-link" rel="nofollow">https://miro.com/app/board/uXjVPoh2zow=/</a></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-8thFebruary2023">8th February 2023</h2><ul><li><p>Two themes:</p><ul><li>The general data centric data architecture pattern<ul><li>Motivations/goals</li><li>Key questions to be answered</li><li>Data domains:<ul><li>Autosar, Telematic, IVI, etc</li></ul></li><li>Data characterisation:</li></ul></li><li>More descriptive/prescriptive orientations of the pattern for specific use cases or touchpoints<ul><li>e.g. Android touch-point:<ul><li>Methods of signal abstraction via VHAL or VSS Data Server</li><li>App connection via cloud and in-vehicle</li></ul></li></ul></li></ul></li><li>Workshop<ul><li>Agreement building<ul><li>Opening<ul><li>Motivations/goals</li><li>Key questions to be answered</li></ul></li><li>Data domains:</li></ul></li><li>Roadmap</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-1stFebruary2023">1st February 2023</h2><ul><li>Useful long discussion on finding common ground. Overran by 30 mins.</li><li>Recognition that a workshop soon would be useful to facilitate longer discussion.</li><li>Working towards this 'central text' Design Pattern<ul><li>Data model and technology agnostic</li><li>Capable of supporting multiple touch points from same arch (robust, flexible etc)</li><li>Capable of multiple data domains sharing same data m/w</li><li>Explain requirements but avoid deep heavy specification setting</li><li>Vehicle is not a single IT blob. Need to engage with reality of requirements from different domains in outlining use cases and touch points: Hard RT vs needs of Analytics, signal read vs storage for processing.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-25thJanuary2023">25th January 2023</h2><ul><li>Steve: Let's continue discussion of BMW presentation with goal of moving towards a roadmap</li><li>Christian is waiting for permission to make presentation public</li><li>Christian: Requirements are definitely an interesting collaboration point for us</li><li>Felix: Alternative approaches to meet the requirements</li><li>Ulf: I've forwarded the presentation within Ford waiting for feedback</li><li>Christian: Slide 7<ul><li>Important point is the architecture supporting other data models and personal data (arch not be VSS specific)</li><li>VSSo not just for data integration but enabling knowledge transfer</li></ul></li><li>Steve: to my mind we seem to be moving towards a central design pattern from which others and implementations may be spun off</li><li>Proposal sketch: Design Pattern: Data Centric Arch including requirements<ul><li>Patterns for Touchpoints</li><li>Implementations/PoCs proving such<ul><li>e.g Realm showing VSS sync via middleware</li></ul></li></ul></li><li>General agreement this makes sense.</li><li>Ulf: The implementation section matches what I am working on in Ford</li><li>Next steps:<br/><ul><li>Start to plan the central Design Pattern</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-18thJanuary2023">18th January 2023</h2><p>Agenda:</p><ul><li>BMW presenting input for the roadmap</li></ul><p><br/></p><ul><li>Adnan/Christian Muehlbauer from BMW presented their input into the early 2023 roadmap<ul><li>Presentation: <a href="https://wiki.covesa.global/download/attachments/46628897/2023_01_18_COVESA_Data_Middleware_V2.0.pptx?version=1&modificationDate=1674836644431&api=v2" data-linked-resource-id="57475115" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="2023_01_18_COVESA_Data_Middleware_V2.0.pptx" data-nice-type="PowerPoint Presentation" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-linked-resource-container-id="46628897" data-linked-resource-container-version="123">2023_01_18_COVESA_Data_Middleware_V2.0.pptx</a></li><li>Initial discussion during the remaining time shows overlap in interests between participants. Needs expanding upon. Participants commit to returning next week to continue discussions.</li><li>Shows in part the usefulness of the proposed longer workshops which might take some of the questions and requirements raised and provide the time for longer discussion.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-11thJanuary2023">11th January 2023</h2><p>(Paul's notes from the meeting)</p><ul><li>Adnan - will bring in arch and use cases for next meeting including use cases</li><li>Goal is to settle on piece that is useful and focus on a piece of the architecture</li><li>Setting up direction for data architecture<ul><li>Setup high level arch</li><li>Requirements - like <a href="http://objectbox.io" class="external-link" rel="nofollow">objectbox.io</a></li><li>List use cases</li><li>In workshop provide hands on experience</li></ul></li><li>What is the initial purpose? What are we trying to<br/>get?<ul><li>Exploring solutions to data architecture</li><li>Learning how things are built and Thought<br/>leadership!</li><li>What solutions look like when provided requirements</li><li>Learn how to shape with requirements then look at what solutions</li><li>Community requirements</li><li>Let vendors show their solutions</li></ul></li><li>Christian will provide first proposal</li><li>Ted<ul><li>Be able to receive data from OEM - $0.60 a month - Curve logging</li><li>Want to work on TCU’s directly</li><li>Willing to work with us</li></ul></li><li>Adnan - How to improve data handling between car and cloud.</li><li>Stephen - use 80% vss but need to be able to handle other data in addition</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-4thJanuary2023">4th January 2023</h2><p>Agenda:</p><ul><li>Continue roadmap discussion including possibility of virtual workshop</li></ul><p><br/></p><ul><li>Thoughts over xmas?<ul><li>Ulf has been considering his thin API proposal over xmas and will update in the next Autosar sync call. Has proposal to extend beyond data into procedure calls for services.</li><li>Steve repeated his intention to resume work on extending state storage to support time series DBs including Apache IoTDB</li></ul></li><li>Discussion of connection between state storage, VSS servers and the proposed vehicle API</li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-7thDecember2022">7th December 2022</h2><ul><li>EG project announcements<ul><li>Update on Autosar Collaboration</li></ul></li><li>Xmas break<ul><li>Steve can only remotely phone in next week, which would be the last meeting before Xmas. Nic can't make it.</li><li>Decision taken to break for Xmas early. This is the last meeting of the year. Thanks to all who contributed.</li><li>Request: think about the Design Pattern goals over xmas</li></ul></li><li>Data Arch Theme discussion<ul><li>Proposal to hold a virtual workshop for multiple hours early next year to accelerate the design pattern discussion.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-30thNovember2022">30th November 2022</h2><ul><li>Project status<ul><li>Majority of VSS call taken up with VSS struct support discussion. Best practices good/bad one of the focus points next.</li><li>Ted summarised VISS/VSSo updates</li></ul></li><li>Data Arch Theme discussion<ul><li>GraphQL<ul><li>Andre: Nice for query. Problematic to have generalised set method. Have to do heavy development in schema for setter. Complicates cross vehicle model support.</li><li>GraphQL still of interest in the tech landscape but VISS is the more obvious first priority</li></ul></li><li>Discussion of existing high level in-vehicle data architecture diagram. What it was created for and its limitations.</li><li>Ulf showed how his V2C proposal could address data needs</li><li>(Data) Design Patterns<ul><li>Discussion of in-vehicle architecture leads back to the existing topic of local data reduction at the edge/within function and smart exchange between functions<ul><li>Local processing generating higher logic data possibly at lower frequency, e.g. engine management does local monitoring and then externally reports decisions</li><li>Reduces in-vehicle network traffic</li><li>Reduces costs associated with data transmission to the cloud</li><li>This is an obvious candidate for a design pattern: benefits, how it may be done, VSS/VISS role in that.</li></ul></li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-23rdNovember2022">23rd November 2022</h2><ul><li>Project status<ul><li>VSS struct support heads up</li><li>VSSo meetings have restarted</li><li>Status of the collaboration between Covesa and Autosar and work on Autosar Gateway/Vehicle API</li></ul></li><li>Data Arch Themes<ul><li>Given prior input on peoples interest Steve outlined an early roadmap for work that could create both PoCs and data patterns and which is easily adopted into related Covesa projects such as the Autosar Gateway and Android.<br/><ul><li>VSS Data Server<ul><li>GraphQL (Covesa C++)</li><li>VISS Data Server</li><li>Aim: demonstrating two possibilities</li></ul></li><li>VSS Data Store<ul><li>Connection to Data Server</li><li>Embedded app DB (e.g. Realm), 'full' DB (e.g. IoTDB)</li><li>Aim: demonstrating two possibilities</li></ul></li><li>Target: x86 (e.g container) => embedded h/w</li></ul></li><li>Discussion:<ul><li>Piotr: suggests adding VM to x86 targets as it allows investigation of concepts like VirtIO that may be harder in containers</li><li>Ulf: It makes sense to follow a pluggable architecture</li><li>Piotr makes the good point that the data architecture diagrams will need to evolve to cover higher function needs such as the proposed Vehicle API as well as the current coverage for data.</li></ul></li></ul></li><li>AoB<ul><li>Ulf presented his proposal for a thin API approach to the Vehicle API requirements for the Autosar collaboration.<ul><li>This is not yet public. He will work on enabling that with goal to present it to the Autosar working group once it gets going.</li></ul></li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-16thNovember2022">16th November 2022</h2><ul><li>Brief recap of Covesa project status</li><li>Continuing discussion of future work<ul><li>Paul: what would people like to see?<ul><li>Felix: interested in GraphQL and connection of databases as data back-end. Along with what benefits data store may enable, e.g. processing at the edge.</li><li>Nick: ability for apps devs to discover what signals are available and on what terms, e.g. frequency.</li></ul></li><li>Answered Felix's question about what work had gone on before.</li><li>Future is very much open to be set by the group. Cloud needs picking up again - with VSS/VISS now established the original work on CCS could move to other aspects. In-vehicle the component landscape is sketched but much work to be done selecting patterns based on data needs.</li><li>Steve showed a draft high level data arch diagram showing the proposed Autosar gateway communicating with QM data architecture.</li><li>Agreement that the interest around data architecture presented and discussed at the AMM is a useful starting point both for PoC investigation and likely creation of data patterns. Let's continue the discussions with a view to creating a strategy.</li></ul></li></ul><h2 id="ArchitectureandInfrastructureMeetingMinutes-9thNovember2022">9th November 2022</h2><ul><li>Introductions as we have newcomers Felix Reichenbach (MongoDB) and Francois Ozog (Shokubai.tech)</li><li>Project updates<ul><li>Steve summarises VSS, VSC, VSSo status and EG Leadership discussions around governance and project reporting</li></ul></li><li>Roadmap<ul><li>Discussion of possible data patterns. What are people interested in?<ul><li>Felix: One area is GraphQL data server shown in the architecture. Would be interesting to have embedded implementation backending to data store.<ul><li>Steve outlines some of the work to date on that including the GraphQL libraries in the Covesa github.</li></ul></li><li>Francois outlines his interests around function abstractions.<ul><li>Steve summarises work in that area in Covesa and suggests background reading.</li></ul></li></ul></li></ul></li></ul>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/display/WIK4/Architecture+and+Infrastructure+Meeting+Minutes">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=46628897&revisedVersion=123&originalVersion=122">View Changes Online</a>
</div>
</div>Stephen Lawrence2022-11-09T15:28:00ZCommon Vehicle Interfaces Meeting Topics and Meeting NotesPaul Boyestag:wiki.covesa.global,2009:page-78839850-382024-03-26T16:34:27Z2023-09-05T22:18:58Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~pboyes@covesa.global
">Paul Boyes</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-/*<![CDATA[*/div.rbtoc1711644959553{padding:0px;}div.rbtoc1711644959553ul{margin-left:0px;}div.rbtoc1711644959553li{margin-left:0px;padding-left:0px;}/*]]>*/#CommonVehicleInterfacesMeetingTopicsandMeetin"><span style="color: rgb(255,0,0);"><em><style type='text/css'>/*<![CDATA[*/
div.rbtoc1711644959553 {padding: 0px;}
div.rbtoc1711644959553 ul {margin-left: 0px;}
div.rbtoc1711644959553 li {margin-left: 0px;padding-left: 0px;}
/*]]>*/</style><div class='toc-macro rbtoc1711644959553'>
<ul class='toc-indentation'>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-'></a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-GeneralAgenda'>General Agenda</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-03-26'>Agenda 2024-03-26</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-03-19'>Agenda 2024-03-19</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-03-12'>Agenda 2024-03-12</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-27'>Agenda 2024-02-27</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-20'>Agenda 2024-02-20</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-13'>Agenda 2024-02-13</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-06'>Agenda 2024-02-06</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-01-30'>Agenda 2024-01-30</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-01-23'>Agenda 2024-01-23</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-01-16'>Agenda 2024-01-16</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2023-11-28'>Agenda 2023-11-28</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2023-11-21'>Agenda 2023-11-21</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2023-11-14'>Agenda 2023-11-14</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-11-7'>Meeting notes 2023-11-7</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-10-24'>Meeting notes 2023-10-24</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-10-24.1'>Meeting notes 2023-10-24</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-10-17'>Meeting notes 2023-10-17</a></li>
<li><a href='#CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-09-05'>Meeting notes 2023-09-05</a></li>
</ul>
</div><br/></em></span></h1><p><br/></p><p><em>This page intends to contain the agenda for next meeting and notes from previous meeting. </em></p><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-GeneralAgenda">General Agenda</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA Common Vehicle Interfaces Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><p>Agenda discussion - anything that needs to be added?</p><ul><li>Prioritized Topics:<ul><li><a href="https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interfaces+-+Capabilities">Capabilities</a> - create a list of common vehicle capabilities/function to be expose via api</li><li><a href="https://github.com/COVESA/ifex" class="external-link" rel="nofollow">IFEX</a> (Interface Exchange) - <span style="color: rgb(31,35,40);">a general interface description and transformation technology<span> </span></span></li><li><a href="https://github.com/COVESA/uservices" class="external-link" rel="nofollow">uServices</a> - <span style="color: rgb(31,35,40);">definition of common vehicle services usimg protobuf as the interface definition language</span></li><li>Vehicle Signal Specification over Data Distributiion Service </li><li><a href="https://www.w3.org/TR/viss2-core/" class="external-link" rel="nofollow">Vehical Information Service Specification (VISS)</a> - <span style="color: rgb(0,0,0);">a service for accessing vehicle information, signals from sensors on control units within a vehicle's network. It exposes this information using COVESA Vehicle Signal Specification (VSS).</span></li><li><a href="https://wiki.covesa.global/display/WIK4/Vehicle+API" rel="nofollow">Vehicle API </a>- <span style="color: rgb(23,43,77);">will expose vehicle data as defined and described by COVESA's<span> </span></span><a href="https://wiki.covesa.global/display/WIK4/VSS+Resources+at+a+Glance" rel="nofollow">Vehicle Signal Specification<span> </span></a><span style="color: rgb(23,43,77);">to a variety of agreed upon touch-points in and out of the vehicle</span></li><li><span style="color: rgb(23,43,77);">Hierarchical Information Model (<a href="https://github.com/COVESA/hierarchical_information_model" class="external-link" rel="nofollow">HIM</a>)</span></li><li><span style="color: rgb(23,43,77);">Interface Blueprint</span></li></ul></li></ul><h1 style="" id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-03-26">Agenda 2024-03-26</h1><ul><li>IFEX <ul><li>protobuf</li><li>GRPC</li><li>AUTOSAR</li><li>How to create appropriate layered def<ul><li><a class="external-link" href="https://github.com/gunnar-mb/uservices/pull/1" rel="nofollow">https://github.com/gunnar-mb/uservices/pull/1</a></li></ul></li></ul></li><li>VISS/VISSR<ul><li>Ready to announce move to COVESA next week</li></ul></li><li>uServices<ul><li>How do we reuse this of definitions? Interface behavior? Logic?</li></ul></li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-03-19">Agenda 2024-03-19</h1><ul><li>Pick up where we left off last week.<ul><li>Commodity catalog submissions - anything new?</li></ul></li><li>Walk through nascent backlog<ul><li><a href="https://github.com/orgs/COVESA/projects/10" class="external-link" rel="nofollow">https://github.com/orgs/COVESA/projects/10</a></li></ul></li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-03-12">Agenda 2024-03-12</h1><ul><li>Contribute Commodity Catalog Call for Submission<ul><li>Start with submissions on seating, cabin climate from BMW, Mercedes, Ford, GM</li></ul></li><li>Stronger Agenda - Potential Comments<ul><li>Signal discovery at interface level </li><li>Blueprints<ul><li>e.g. Errors. Ford has common errors</li></ul></li><li>Commodity Service<ul><li>never compared to VHAL<ul><li>BMW - Connected VHAL properties </li><li>Start with Seating and HVAC</li><li>Action Item: Provide Seating HVAC - Try to get Seating capabilities</li><li>Ping Gunnar about commits</li><li>Getting this offline and readiness</li></ul></li></ul></li><li>IFEX - Overlay for AUTOSAR for ARXML VHAL/SOMEIP</li><li>HIM Rule set</li><li>User Identity<ul><li>ActionItem: What work can we work on as a group, key fob related to vehicle signals and how related to user identity</li><li>Extension for key fob on VSS</li></ul></li><li>Authentication</li><li>Some requests have OBD / Emmisions regulations<ul><li>How is this handled in VISS and Kuksa</li></ul></li><li>Very specific topics like IFEX <> uServices</li></ul></li><li>Backlog in GitHub</li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-27">Agenda 2024-02-27</h1><ul><li>vsomeip<ul><li><span style="letter-spacing: 0.0px;">Get overview from GM.</span></li></ul></li><li><span style="letter-spacing: 0.0px;">VISS repos</span><br/><ul><li><span style="letter-spacing: 0.0px;"><a style="text-decoration: none;text-align: left;" class="external-link" href="http://github.com/COVESA/vehicle-information-service-specification" rel="nofollow">http://github.com/COVESA/vehicle-information-service-specification</a><span style="color: rgb(29,28,29);"><span> </span>and<span> </span></span><a style="text-decoration: none;text-align: left;" class="external-link" href="http://github.com/COVESA/vissr" rel="nofollow">http://github.com/COVESA/vissr</a></span></li></ul></li><li>IFEX Protobuf</li><li>Central Data Service Playground mvp running</li><li>AMM<ul><li>VISS presentations/sessions</li><li>VISS overview, status, announcement</li></ul></li><li>blueprint brainstorm</li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-20">Agenda 2024-02-20</h1><ul><li>blueprint brainstorm<ul><li>Paul to post a start</li></ul></li><li>VISS to COVESA<ul><li>Automotive WG closed</li><li>create repos in COVESA and move from w3c</li><li>Names spec (VISS) and implementation (VISS-)</li><li>use respec for spec</li></ul></li><li>AMM<ul><li>VISS presentations/sessions</li><li>VISS overview, status, announcement</li></ul></li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-13">Agenda 2024-02-13</h1><ul><li>Licensing meeting this week with AUTOSAR - Discussion</li><li>Blueprint brainstorm</li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-02-06">Agenda 2024-02-06</h1><ul><li>Licensing meeting this week with AUTOSAR</li><li>VISS in progress of moving to COVESA</li><li>IFEX and uServices </li><li>Blueprint Patterns<ul><li>Discovery Patterns</li><li>Notification</li><li>Request Response</li><li>Configurability</li><li>Ease of Use</li><li>Level of API - 3rd party app, lower level SDV, or...</li></ul></li><li>Next Week - Brainstorm Blueprints<ul><li>Share Common Pain Points</li></ul></li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-01-30">Agenda 2024-01-30</h1><ul><li>Licensing meeting this week with AUTOSAR</li><li>VISS in progress of moving to COVESA</li><li>IFEX and uServices </li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-01-23">Agenda 2024-01-23</h1><ul><li>IFEX and uServices - synch status<ul><li>Protobuf "option" meaning discussed - it is used for configuration parameters that modify the behavior of the interface. Need to determine how this will manifest in IFEX.</li></ul></li><li>VISSv2<ul><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> to setup meeting regarding mechanical transfer to COVESA</li></ul></li><li>ARXML License Discussion<ul><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> to get concrete what can/can't be done</li></ul></li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2024-01-16">Agenda 2024-01-16</h1><ul><li>Digital key - Ted</li><li>IFEX and uservices - synch meeting - </li><li><a class="confluence-userlink user-mention" data-username="ted.guild" href="https://wiki.covesa.global/display/~ted.guild" data-linked-resource-id="360545" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Ted Guild</a> Start topic of identity in CVI - <a class="confluence-userlink user-mention" data-username="ted.guild" href="https://wiki.covesa.global/display/~ted.guild" data-linked-resource-id="360545" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Ted Guild</a> <a class="confluence-userlink user-mention" data-username="erik.jaegervall" href="https://wiki.covesa.global/display/~erik.jaegervall" data-linked-resource-id="363989" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Erik Jaegervall</a> <a class="confluence-userlink user-mention" data-username="halim.ragab@gm.com" href="https://wiki.covesa.global/display/~halim.ragab@gm.com" data-linked-resource-id="71074316" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Halim Ragab</a> to bring initial <a href="https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interfaces+-+Use+Cases" rel="nofollow">use cases</a> forward <a class="confluence-userlink user-mention" data-username="gandersson" href="https://wiki.covesa.global/display/~gandersson" data-linked-resource-id="362783" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Gunnar Andersson</a> happy to support if needed in IFEX</li><li><a class="confluence-userlink user-mention" data-username="halim.ragab@gm.com" href="https://wiki.covesa.global/display/~halim.ragab@gm.com" data-linked-resource-id="71074316" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Halim Ragab</a> IFEX to/from uservices and IFEX to/from someip</li><li><a class="confluence-userlink user-mention" data-username="adnan.bekan@bmwgroup.com" href="https://wiki.covesa.global/display/~adnan.bekan@bmwgroup.com" data-linked-resource-id="34209860" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Adnan Bekan</a> Android and Apple APIs - extract all functions an list for discussion</li><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> to arrange for moving VISS to COVESA<ul><li>@remotive labs working on feeder opportunity for work</li><li>identify shared work in VISS</li></ul></li><li>Playground forming container with VISS<ul><li>Mongo adding Realm</li><li>BMW working on knowledge layer</li></ul></li><li>Scoping catalog work</li><li>blueprints look at existing initiatives</li><li>Identity - </li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2023-11-28">Agenda 2023-11-28</h1><p>Prioritized Topics:</p><ul><li>Capability Lists Review</li><li>IFEX and uservices</li><li>ACTION ITEM: <a class="confluence-userlink user-mention" data-username="adnan.bekan@bmwgroup.com" href="https://wiki.covesa.global/display/~adnan.bekan@bmwgroup.com" data-linked-resource-id="34209860" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Adnan Bekan</a> Look at Android 14 - Vehicle Attributes and APIs for capabilities (Seats, Steering Wheel....) Link</li><li>ACTION ITEM: <a class="confluence-userlink user-mention" data-username="mmorr183@ford.com" href="https://wiki.covesa.global/display/~mmorr183@ford.com" data-linked-resource-id="85196855" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Melissa Morris</a> Melissa to do the exact same thing for Seats as HVAC - Week of Dec 5</li><li>ACTION ITEM: @everyone VSS and IFEX discussion read doc</li><li>ACTION ITEM: @everyone Review capabilities outlined in uservices</li><li>Goal: <a class="confluence-userlink user-mention" data-username="gandersson" href="https://wiki.covesa.global/display/~gandersson" data-linked-resource-id="362783" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Gunnar Andersson</a> , <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> , @everyoneAgreed common/computable representation/description of common capabilities at a logical level<ul><li>Is IFEX mature enough to define common capabilities</li><li>Attempt to define HVAC interfaces in IFEX </li></ul></li><li>Domain Priority<ul><li>HVAC</li><li>Seats</li></ul></li><li>Playground: @everyone - Provide examples of what is needed input in Playground. What examples would be useful? What is the goal of that example?<ul><li>Try it out and get involved.</li></ul></li><li>What representation? Why? Show a reference implementation on <a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground" rel="nofollow">Playground</a></li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2023-11-21">Agenda 2023-11-21</h1><p>Prioritized Topics:</p><ul><li>Capability Lists Review</li><li>IFEX and uservices</li><li>ACTION ITEM: Melissa to do the exact same thing for Seats as HVAC - Week of Dec 5</li><li>ACTION ITEM: VSS and IFEX discussion read doc</li><li>ACTION ITEM: Review capabilities outlined in uservices</li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Agenda2023-11-14">Agenda 2023-11-14</h1><p>Prioritized Topics:</p><ul><li>Capability Lists Review</li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-11-7">Meeting notes 2023-11-7</h1><ul><li>Attendees<ul><li><a class="confluence-userlink user-mention" data-username="adnan.bekan@bmwgroup.com" href="https://wiki.covesa.global/display/~adnan.bekan@bmwgroup.com" data-linked-resource-id="34209860" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Adnan Bekan</a></li><li><a class="confluence-userlink user-mention" data-username="halim.ragab@gm.com" href="https://wiki.covesa.global/display/~halim.ragab@gm.com" data-linked-resource-id="71074316" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Halim Ragab</a> </li><li><a class="confluence-userlink user-mention" data-username="magnus.feuer@mercedes-benz.com" href="https://wiki.covesa.global/display/~magnus.feuer@mercedes-benz.com" data-linked-resource-id="75726927" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Magnus Feuer</a> </li><li>@Mellisa Morris</li><li><a class="confluence-userlink user-mention" data-username="richard.fernandes@gm.com" href="https://wiki.covesa.global/display/~richard.fernandes@gm.com" data-linked-resource-id="71074084" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Richard Fernandes</a></li><li><a class="confluence-userlink user-mention" data-username="shareef.hakim@ford.com" href="https://wiki.covesa.global/display/~shareef.hakim@ford.com" data-linked-resource-id="62062669" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Shareef Hakim</a> </li><li><a class="confluence-userlink user-mention" data-username="stephen.lawrence" href="https://wiki.covesa.global/display/~stephen.lawrence" data-linked-resource-id="361705" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Stephen Lawrence</a> </li><li>@Swetha Patil</li><li><a class="confluence-userlink user-mention" data-username="ulf.bjorkengren" href="https://wiki.covesa.global/display/~ulf.bjorkengren" data-linked-resource-id="363862" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Ulf Bjorkengren</a> </li></ul></li><li>Prioritized Topics:<ul><li>Provide overview and background to new attendees</li><li>Re-sync on next steps</li><li>Discussion of how best to align</li></ul></li><li>Action Items<ul><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> and others Identify diagram(s) to serve as simple stack diagram for group reference. </li><li>@OEMs/Everyone Bring capability lists to next weeks meeting in whatever format you have them. <ul><li>Current lists include:<ul><li><a href="https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interfaces+-+Capabilities">Common Vehicle Interfaces - Capabilities</a> (you may add another section/create another page, link... here. The main thing is to provide your list)</li><li><a href="https://github.com/COVESA/uservices" class="external-link" rel="nofollow">https://github.com/COVESA/uservices</a></li></ul></li></ul></li><li>@everyone review previous work<br/><ul><li><a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshops - Interface Pillar Alignment</a><ul><li>Presentation Links within:<ul><li><em style="text-align: left;"><a href="https://wiki.covesa.global/download/attachments/71073952/IFEX-quick-what-and-why-v2.0.pdf?version=1&modificationDate=1692553926731&api=v2" rel="nofollow">IFEX-quick-what-and-why-v2.0.pdf</a></em></li><li><a href="https://wiki.covesa.global/download/attachments/71073952/COVESA_VSS_OpenAPI.pdf?version=1&modificationDate=1691759739448&api=v2" rel="nofollow">COVESA VSS OpenAPI</a></li></ul></li></ul></li><li>AMM Presentations about interfaces<ul><li><a href="https://wiki.covesa.global/download/attachments/78840403/COVESA_SDV_presentation.pdf?version=1&modificationDate=1698672487208&api=v2" rel="nofollow"><span style="color: rgb(23,43,77);">From Concept to Reality:</span><span style="color: rgb(23,43,77);"> <span> </span></span><span style="color: rgb(23,43,77);">How Data-Centric Vehicle APIs Shape Software-Defined Vehicle</span></a><a href="http://COVESA_SDV_presentation.pdf" class="external-link" rel="nofollow"> </a></li><li><span style="color: rgb(23,43,77);"><a href="https://wiki.covesa.global/download/attachments/78840403/HIM%20and%20an%20interface%20using%20it.pptx?version=1&modificationDate=1698449080055&api=v2" rel="nofollow">The Hierarchical Information Model (HIM) and an Interface Using It</a></span></li><li><span style="color: rgb(23,43,77);"><a href="https://wiki.covesa.global/download/attachments/78840403/Beyond_the_car_Shareef_Hakim_Day_2_13_30_final.pdf?version=1&modificationDate=1697562010433&api=v2" rel="nofollow">Beyond the Car - Advancing Commercial Vehicles - The Transforming Software to Meet the Needs of Owners, Drivers and Fleet Managers</a></span></li><li><span style="color: rgb(23,43,77);"><a href="https://wiki.covesa.global/download/attachments/78840403/Day_2_1011-11_30_HR_COVESA_uServices_COVESA_AMM_Oct_2023.pdf?version=1&modificationDate=1698679020286&api=v2" rel="nofollow">uServices - A Step towards a standardized vehicle Interfaces for SDV</a></span></li></ul></li><li>Links and text posted during meeting<br/><ul><li><div class="confluence-information-macro confluence-information-macro-information"><p class="title conf-macro-render">Chat</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>You (Nov 7, 2023, 8:12 AM)<br/><a href="https://github.com/COVESA/uservices" class="external-link" rel="nofollow">https://github.com/COVESA/uservices</a><br/><a href="https://github.com/COVESA/ifex" class="external-link" rel="nofollow">https://github.com/COVESA/ifex</a><br/> <br/>Ulf (Ford)  (Nov 7, 2023, 8:15 AM)<br/><a href="https://github.com/COVESA/hierarchical_information_model" class="external-link" rel="nofollow">https://github.com/COVESA/hierarchical_information_model</a><br/> <br/>Stephen Lawrence (Nov 7, 2023, 8:23 AM)<br/><a href="https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground" rel="nofollow">https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground</a><br/> <br/>Stephen Lawrence (Nov 7, 2023, 8:52 AM)<br/>Original diagrams from MBition <a href="https://wiki.covesa.global/display/WIK4/Vehicle+Service+Catalog+%28VSC%29+-+Common+Interface+Description+Model?preview=/22643862/22644665/covesa_amm_2022_-_vsc.pptx#VehicleServiceCatalog(VSC)CommonInterfaceDescriptionModel-PresentationsfromApril2022AllMemberMeeting" rel="nofollow">https://wiki.covesa.global/display/WIK4/Vehicle+Service+Catalog+%28VSC%29+-+Common+Interface+Description+Model?preview=/22643862/22644665/covesa_amm_2022_-_vsc.pptx#VehicleServiceCatalog(VSC)CommonInterfaceDescriptionModel-PresentationsfromApril2022AllMemberMeeting</a><br/> <br/>Stephen Lawrence (Nov 7, 2023, 8:59 AM)<br/>There is some focus on IDLs as well in that presentation but that is because at the time (start of project) people expected it to be addressed.</p></div></div></li></ul></li></ul></li></ul></li></ul><p><br/></p><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-10-24">Meeting notes 2023-10-24</h1><ul><li>Prioritized Topics:<ul><li>Gunnar looking at converting uServices</li><li>Blueprints<ul><li>Looked at <a class="external-link" href="https://apiblueprint.org/" rel="nofollow">https://apiblueprint.org/</a></li><li>uServices - look to extract patterns, look at options when Halim back<ul><li>business logic separated from deployment</li><li>Number of rows... Number of seat rows? Constant or set at design </li></ul></li></ul></li><li>Ford - Meet Shareef/Ford at Nov 7 during regularly scheduled meeting</li></ul></li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-10-24.1">Meeting notes 2023-10-24</h1><ul><li>Prioritized Topics:<ul><li>Blueprint<ul><li><a href="https://cloud.google.com/apis/design" class="external-link" rel="nofollow">https://cloud.google.com/apis/design</a></li><li>Need to capture high level "what matters"</li><li>Stay on high level</li><li>Align with VSS structure</li><li>AI: Adnan to put together outline on wiki</li></ul></li><li>Ford - Meet with on Nov 2<ul><li>Blueprint</li><li>Catalog/Capabilities</li><li>Meet Nov 2 from 9-10am ET</li></ul></li><li>BMW to provide feedback on IFEX</li><li>Apple<ul><li>Can we get API documentation from Apple?</li><li>AI: Halim and Adnan to work internally</li></ul></li><li>Google<ul><li>Followed up </li><li>We need to get back to them when we have something</li></ul></li><li>Automotive API (formerly Vehicle API)</li></ul></li></ul><p><br/></p><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-10-17">Meeting notes 2023-10-17</h1><ul><li>Prioritized Topics:<ul><li>AMM Review</li></ul></li></ul><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>AMM review<ul><li>Define scope of each project,</li><li>project interconnectivity/interplay</li><li>Participants</li><li>Action: Paul to start the above</li><li>Action: Ford to find rep</li><li>Action: Reach out to Honda</li><li>Action: Reach out to Hyundai</li><li>Proposed: once a month Asia friendly model. Do more discussions in writng. Slack, GitHub, Wiki...</li><li>Direct contribution needed</li><li>IFEX looking at translation to uServices and vice versa</li><li>Action: GM to meet with Mbitiion re IFEX</li><li>Catalog → OpenAPI and/or uServices and/or IFEX or HIM<ul><li>Simple easy to follow. Guidance to follow. How to document?</li></ul></li><li>Blueprint for how API's should be described<ul><li>How granular?</li><li>Governance</li><li>Action: Get Google documentation</li><li>Coherency, safety security, performance, access control</li><li>Action: Start outline </li></ul></li></ul></li></ul><p><br/></p><ul><li>Prioritized Topics:<ul><li>Capabilities</li><li>IFEX</li><li>uServices</li><li>DDS</li><li>VISS</li><li>HIM</li><li>Vehicle API </li></ul></li><li>Prioritized topics for next meeting</li></ul><h1 id="CommonVehicleInterfacesMeetingTopicsandMeetingNotes-Meetingnotes2023-09-05">Meeting notes 2023-09-05</h1><ul><li>Prioritized Topics:<ul><li>Discussed How to handle this Common Vehicle Interfaces meeting. Agreed to start listing service capabilities.</li><li>Action Item: <a class="confluence-userlink user-mention" data-username="halim.ragab@gm.com" href="https://wiki.covesa.global/display/~halim.ragab@gm.com" data-linked-resource-id="71074316" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Halim Ragab</a> to start a <a href="https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interfaces+-+Capabilities" rel="nofollow">Capabilities</a> page and <a href="https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interfaces+-+Use+Cases">Usecases</a> page</li><li> AMM:<ul><li>Block out time for discussions</li><li>Discuss Use cases, why common vehicle interfaces matter?<ul><li>Integrating with the vehicle </li><li>Mapping to VHAL</li></ul></li><li>Capabilities<ul><li>Report on and discuss <a href="https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interfaces+-+Capabilities" rel="nofollow">page/doc</a></li></ul></li><li>Meet with Google to discuss integration via common interfaces/services<ul><li>Create good example and present prior to AMM</li></ul></li></ul></li></ul></li></ul><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/display/WIK4/Common+Vehicle+Interfaces+Meeting+Topics+and+Meeting+Notes">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=78839850&revisedVersion=38&originalVersion=37">View Changes Online</a>
</div>
</div>Paul Boyes2023-09-05T22:18:58ZVSS Meeting Topics and Meeting NotesErik Jaegervalltag:wiki.covesa.global,2009:page-48529442-1322024-03-26T15:47:45Z2022-11-24T08:56:36Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~erik.jaegervall
">Erik Jaegervall</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<h1 id="VSSMeetingTopicsandMeetingNotes-"><span style="color: rgb(255,0,0);"><em><br/></em></span></h1><p><br/></p><p><em>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.</em></p><p><em>See <a href="https://wiki.covesa.global/display/WIK4/COVESA+Common+Meeting+Schedule">COVESA Common Meeting Schedule</a> for meeting link. The meeting is open to anyone.</em></p><h1 id="VSSMeetingTopicsandMeetingNotes-GeneralAgenda">General Agenda</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized Topics:</li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Discussions VSS</li><li>Discussions VSS-tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-03-25:">Meeting notes 2024-03-25:</h1><ul><li>Head& Eye<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/731" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/731</a></li><li>More time needed?</li></ul></li><li>Franca support<ul><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/735" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/735</a></li><li>(Copy in <a href="https://github.com/COVESA/vss-tools/issues/336" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/issues/336</a>)</li><li>Anyone using/interested? If not - discontinue? (Move to obsolete?) Or just list "known limitations"</li><li>MoM:<ul><li>PPB: if no one interested - possibly handle it as inactive PRs</li><li>Adnan: do not think anyone is using it</li></ul></li></ul></li><li>"Inactive" PRs<ul><li>Do we want to close them after a certain time of inactivity, if no-one seems to be interested in driving them forward?</li><li>MoM<ul><li>PPB: Have no issue closing if there are no progress. Close things at least not touched in a year</li><li>Stefan: discuss in session, archive or take up</li><li>Ulf: A year</li><li>PPB: But not automatic, check last two</li><li>Adnan: Do it AMM, try to schedule time</li></ul></li></ul></li><li>AMM<ul><li>VSS Workshop (PPB) moved to Thursday - 45 minutes, start 8.45</li><li>Also <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/733" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/733</a>?</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-03-18:">Meeting notes 2024-03-18:</h1><ul><li>AOSP<ul><li>Merge ok</li></ul></li><li>VSS vs. VSS-tools compatibility<ul><li>Shall VSS-tools vX.y be required to support anything else than VSS X.Y?</li><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/734" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/734</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/discussions/732" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/discussions/732</a></li><li>Adnan: Nice to support, but how big is the effort, not easy if requires too much work</li><li>Daniel: What about packing the same version of the tool.</li><li>Erik: Advantage for Eclipse Velocitas if the vss-tools "engine" can support also older versions.</li><li>Erik: Would be quite easy to at least check which old VSS versions that are supported for each release</li><li>Erik: Depends on if resources are available.</li></ul></li><li>Overlay and remove<ul><li>Shall new keyword "state" be considered to be part of "std VSS syntax", i.e. described in VSS doc<ul><li>Alternative is to consider it just as a VSS-tools-specific feature</li></ul></li><li><a class="external-link" href="https://github.com/nwesem/vss-tools/pulls" rel="nofollow">https://github.com/nwesem/vss-tools/pulls</a></li><li>Adnan: Does not really understand the use of active/inactive</li><li>Daniel: Is it intended only for exporter, or also other function</li><li>Adnan: Inactive/active fills a different purpose, not needed for vss-tools for purpose of removing signals of tree</li></ul></li><li>Terminology:<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/733" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/733</a></li></ul></li><li>AMM<ul><li><p>Topics for discussion:</p></li><li>Raw vs. derived signals; does VSS need to define or state how signals are derived?<ul><li>Is this useful to clients?</li></ul></li><li>For signals derived through ML; should confidence level, variance, precision, error, etc. be reported?<ul><li>Is this useful to clients?</li></ul></li><li>How should model-generated derived signals such as "driver attentiveness" be represented (in the absence of a standard)?<ul><li>Confidence percentage? Enum?</li></ul></li><li>To what level of specificity should VSS describe signals?<ul><li>Leave semantics to OEMs (flexibility for OEMs but affects portability) or define them precisely?</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-03-12:">Meeting notes 2024-03-12:</h1><ul><li>Adnan -overlay and remove node<ul><li>See <a class="external-link" href="https://github.com/nwesem/vss-tools/pull/2" rel="nofollow">https://github.com/nwesem/vss-tools/pull/2</a> - not ready for official VSS repo yet</li><li>Keyword "deleted"</li><li>Comments welcome</li><li>Pierre Pierre: Interested, will share some feedback. We have thought of a private "x-delete" but better if public/agreed</li></ul></li><li>AMM Planning<ul><li>We should plan content for the VSS Working Session Wed 16.45-17.30. Here is one possible agenda, but it can be adapted as needed if there are other topics someone wants to bring up.<p><br/></p><p>Agenda</p><p><br/></p><ul><li>5 minutes – introduction to VSS maintainer team (i.e. Erik, Adnan, Sebastian) and general requirements if we should refactor VSS</li><li>Recap & Way Forward (10 min each) – Quick recap of the topic and discuss if there is anyone that wants to drive the topic.</li><ul><li><s>VSS Type Representation and Reusable Properties</s></li><li><s>Tree vs. Flat Structure</s></li><li><s>Instance Handling</s></li><li><s>Overlays</s></li></ul><li><s>Other topics (10 min)</s></li></ul><p>A potential abstract for the official agenda could be something like below, unless someone else has a better proposal:</p><p><em>“ At the last AMM we discussed several potential improvement areas for VSS like property support and refactored instance handling. In this session we will continue the discussion and align on VSS roadmap for 2024-2025</em></p></li><li>Discussion<ul><li>PPB: Value discussing various concepts (40 minutes)<ul><li>A number of signals are "raw" signals, others derived. Sometimes it matters how they are derived</li><li>Driver attentiveness/sleepiness, what is meaning of 63% sleepiness, how to handle confidence</li><li>VIN - is static/attribute, what should we do we signals if value comes regularly but never change</li></ul></li><li>Erik: Would be great if you present it PPB</li><li>Daniel: Aspects of having derived information, all participants of the driving env. Concentrate on model, rather than individual signals like VIN - have a session <span>4:00 PM - 4:45 PM <span class="session_weekday">Wed (Towards a Vehicle DATA Specification), but would like to have some time in working session as well</span></span></li><li><span><span class="session_weekday">Paul: need agenda, slides does not be prepared </span></span></li><li><span><span class="session_weekday">Paul: There might be remote participants</span></span></li></ul></li><li><span><span class="session_weekday">AP: PPB to prepare slides</span></span></li><li><span><span class="session_weekday">AP: Erik to propose agenda/abstract</span></span></li></ul></li><li>VSS data (time series) discussion<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/discussions/729" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/discussions/729</a></li><li>PPB: We hear often requests. We have simulator files with timestamps</li><li>Daniel: I have to call action</li><li>Erik: Please discuss</li></ul></li><li>VSS Release Planning<ul><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/689" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/689</a></li><li>Erik: "5.0 Only" - only some minor signal rename and datatype changes, but they have been for quite a while</li><li>PPB: The delete functionality could be nice to have in 5.0 - a major capability</li><li>Erik: That would be ok, good to announce that 5.0 will include delete</li><li>Erik: working assumption - wait with 5.0 until delete-functionality</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-03-05:">Meeting notes 2024-03-05:</h1><ul><li>Info - COVESA Spotlight on VSS featuring RemotiveLabs March 14th 16.00 CET<ul><li>See community calendar</li><li>Will likely be recorded</li><li>Erik: DEG 14th will likely be cancelled</li></ul></li><li>NOTE: Daylight changing in US next week, note that all COVESA meeting should be anchored in EU timezones</li><li>Paul: AMM schedule is full/finalized, official site shall be up to date, check <a class="external-link" href="https://www.eventleaf.com/e/AMMGothenburg2024" rel="nofollow">https://www.eventleaf.com/e/AMMGothenburg2024</a> and report errors to Paul</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-02-27:">Meeting notes 2024-02-27:</h1><ul><li>Introduction</li><li>Info from maintainer (Erik)<ul><li>Closed all issues issued <=2021 with no interaction in 2023 or 2024. I.e. >2 years old and >1 year of inactivity. Feel free to reopen if you consider topic still relevant.</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-02-20:">Meeting notes 2024-02-20:</h1><ul><li>AMM VSS Topics - Topic proposals<ul><li>VSS Working Session 9.45-11.30 Wednesday (DEG also have some time for working sessions)<ul><li>Moved to afternoon 15.30-17.30 for allow for remote participation</li></ul></li><li>Anything particular someone wants to bring up or present?</li><li>Suggestions:<ul><li>Erik: Instance handling and "VSS Expanded Tree" - How do you want to handle instances? How do you handle instances today<ul><li>Pause <a href="https://github.com/COVESA/vehicle_signal_specification/pull/718" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/718</a> until then</li></ul></li><li>VSS Format and Tooling (Erik)</li></ul></li></ul></li><li>General AMM<ul><li>Still possible to propose slots to Paul but filling up</li></ul></li><li>New and old PRs</li><li>New issues</li><li>Issue handling - general<ul><li>What to do with issues where there has not been any progress in many months<ul><li>Keep forever or decide on an auto-close policy?<ul><li>Should be doable at least for suggestions/discussions</li><li>For limitations/defects - possibly manage elsewhere? Like in documentation for the related tool.</li></ul></li></ul></li><li>Example: Signal Accuracy - <a href="https://github.com/COVESA/vehicle_signal_specification/issues/105" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/105</a><ul><li>Possible improvement area, but no-one seems to be interesting actively driving it</li></ul></li><li>Example: Emission standards - <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/394" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/394</a><ul><li>Possible improvement area, but no-one seems to be interesting actively driving it</li></ul></li><li>Issues are of different types today, some maybe fit better as discussion, but also then we have a question on how long we want them to exist<br/><ul><li>Possible improvement areas</li><li>Actual limitations/error (which no-one intends to fix)</li></ul></li><li>Proposed Handling (to be discussed):<ul><li>Close issues after 6 months of inactivity</li><li>If we have agreed/decided something in the discussion - reflect that in VSS or VSS-tools documentation before closing the issues</li><li>If the issue concerns a known limitation/error, then document that in a file for known limitations in the repo<ul><li>Example: Generator <code>vspec2something</code> cannot handle the signal name <code>ggg</code> as that is a a reserved word in <code>something</code> .</li></ul></li></ul></li><li>MoM:<ul><li>Daniel: think it is good to have something, so that issues are decreasing</li><li>No objection to closing inactive items</li></ul></li></ul></li><li>Android tooling<ul><li><a class="external-link" href="https://github.com/COVESA/vss-tools/issues/192" rel="nofollow">https://github.com/COVESA/vss-tools/issues/192</a></li><li>Erik:<ul><li>My assumption is that we want to keep the work but that no-one intends to create a real tool out of it in the next year(s)</li><li>Suggestions:<ul><li>Create a better branch name and add a wiki page explaining purpose of the branch</li><li>Or integrate it into current as "prototype"</li></ul></li><li>MoM (old): Think about it, discussion to be continued</li><li>MoM: No opinion</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-02-13:">Meeting notes 2024-02-13:</h1><ul><li>Release Planning<ul><li>See <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/689" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/689</a></li><li>See notes in issue</li></ul></li><li>Branch usage:<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/wiki/Release-Instructions-and-Checklist" class="external-link" rel="nofollow">Release Instruction</a> updated according to discussion.</li><li>Erik: Suggesting the following issues/PRs shall be closed at next meeting unless there are comments/remarks<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/646" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/646</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/704" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/704</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/707" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/707</a></li></ul></li><li>Please review, items above will be closed before next meeting unless comments</li><li>AP Erik: Add note in those items</li></ul></li><li>Unit handling<ul><li>Conclusion from last discussion is that we will do no more in VSS, it is primarily an API topic</li><li>Documentation added as suggested in <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/717" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/717</a></li><li>Then possibly close<ul><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/discussions/680" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/discussions/680</a></li><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/690" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/690</a></li></ul></li><li>Erik: suggesting merge discussion next week</li></ul></li><li>Wheel speed - and possibly a wider discussion on "overlapping signals"<ul><li>Summary: Today we have individual wheel speed measured as km/h</li><li>Request for rad/s (possibly degrees/s would work as well)</li><li>Q: Anyone objecting having both km/h and degrees/s, as they may support partially different usecases.</li><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/678" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/678</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/discussions/677" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/discussions/677</a></li><li>MoM: No direct objection</li></ul></li><li>Instance handling (Left/Right vs Driver/Paseenger)<ul><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/718" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/718</a></li></ul></li><li>Android tooling<ul><li><a href="https://github.com/COVESA/vss-tools/issues/192" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/issues/192</a></li><li>Erik:<ul><li>My assumption is that we want to keep the work but that no-one intends to create a real tool out of it in the next year(s)</li><li>Suggestions:<ul><li>Create a better branch name and add a wiki page explaining purpose of the branch</li><li>Or integrate it into current as "prototype"</li></ul></li><li>MoM: Think about it, discussion to be continued</li></ul></li></ul></li><li>Use of discussions instead of issues<ul><li>Discussion started at <a href="https://github.com/COVESA/vehicle_signal_specification/discussions/715" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/discussions/715</a></li><li>Nick: Discussion could be used for more informal discussions, Q&A,</li><li>Erik: But if so not necessarily something to discuss at this meeting</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-02-06:">Meeting notes 2024-02-06:</h1><ul><li>AMM Topics<ul><li>Please send proposals to Paul - <a href="https://wiki.covesa.global/display/WIK4/AMM+202404+Technical+Track+Session+Proposals">AMM 202404 Technical Track Session Proposals</a></li><li>AMM registration open at <a class="external-link" href="https://www.eventleaf.com/e/AMMGothenburg2024" rel="nofollow">https://www.eventleaf.com/e/AMMGothenburg2024</a> (not yet linked from global COVESA homepage)</li><li>Discussion of VSS topics, see <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/discussions/714" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/discussions/714</a></li></ul></li><li>Use of discussions instead of issues<ul><li>Discussion started at <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/discussions/715" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/discussions/715</a></li></ul></li><li>Branch usage:<ul><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/704" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/704</a></li><li>Recent comments:<ul><li>From Stephen that we shall announce if we intend to remove a branch, use "deprecation"</li></ul></li><li>AP: Erik to update wiki, to be announced/reviewed when finished, if ok issue can be closed</li></ul></li><li>Tarball<ul><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/711" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/711</a></li><li>Sebastian: Is it worth the effort, how needed is it?</li><li>Erik: use case (downstream project) that needs it identified, so we know requirements.</li><li>AP: erik check with Scott if it actually needed if branches exist</li></ul></li><li>precond<ul><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/703" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/703</a></li><li>No more comments - merge decision</li></ul></li><li>digital keys<ul><li>PR on hold, internal discussions.</li></ul></li><li>OBD deprecation:<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/701" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/701</a></li><li>no more comments, merge decision next week?</li></ul></li><li>New PR:<ul><li>Engine fluid: <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/710" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/710</a></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-01-30:">Meeting notes 2024-01-30:</h1><ul><li>Overlay issues (vss-tools issue 193-195)<ul><li>How to remove/rename nodes, detecting duplicates</li><li>BMW assigned a person to look at it, proposal possibly end of february</li><li>Pierre Pierre: I have some ideas for node removal</li><li>Adnan: Please comment in <a class="external-link" href="https://github.com/COVESA/vss-tools/issues/194" rel="nofollow">https://github.com/COVESA/vss-tools/issues/194</a></li><li>Pieer Pierre: Has added comments</li></ul></li><li>Branch Usage<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/704" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/704</a></li><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/707" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/707</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/646" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/646</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/wiki/Release-Instructions-and-Checklist" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/wiki/Release-Instructions-and-Checklist</a></li><li>Summary: Release branches are strongly prefferred by some downstream projects, access by tag is not sufficient</li><li>Erik: Proposed (revised) branch/tag-handling presented in 707. Proposal - review until next meeting. Decision to accept/reject proposal at next meeting. If accepted changes shall be reflected wiki</li><li>Possibly add file archive: <a href="https://github.com/COVESA/vehicle_signal_specification/issues/711" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/711</a> (handle as separate issue)</li></ul></li><li>NEW: Static UID improvement - <a class="external-link" href="https://github.com/COVESA/vss-tools/pull/326" rel="nofollow">https://github.com/COVESA/vss-tools/pull/326</a><ul><li>Erik: Minor improvement, rebase/squash needed. Anyone wants to keep it open until next meeting, or ok to merge if rebased/squashed</li><li>Decision: Merge when maintainer happy</li></ul></li><li>Datatype checks - <a href="https://github.com/COVESA/vss-tools/pull/325" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/325</a><ul><li>Erik: No comments receives, ok to merge?</li><li>MoM: Merge</li></ul></li><li>Tool restructure - <a href="https://github.com/COVESA/vss-tools/pull/311" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/311</a><ul><li>Erik: Merge decision? To be merged after 326 to avoid conflicts, if any</li><li>MoM: Ok to merge, after the static id PR has been merged</li></ul></li><li>NEW: Github actions update -<ul><li><a class="external-link" href="https://github.com/COVESA/vss-tools/pull/327" rel="nofollow">https://github.com/COVESA/vss-tools/pull/327</a></li><li><a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/709" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/709</a></li><li>Erik:Trivial - may be merged soon</li></ul></li><li>Battery precondition - <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/703" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/703</a><ul><li>Erik: Time updated - merge decision at next meeting unless outstanding comments</li></ul></li><li>Digital key - <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/pull/702" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/702</a><ul><li>Erik: Time updated - merge decision at next meeting unless outstanding comments</li><li>Adnan: Have communicated internally, waiting for reply</li><li>Erik: Check status next week, if needed postpone merge decision until BMW review finished</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-01-23:">Meeting notes 2024-01-23:</h1><ul><li>Tool restructuring <a href="https://github.com/COVESA/vss-tools/pull/311" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/311</a></li><li>Datatype check <a class="external-link" href="https://github.com/COVESA/vss-tools/pull/325" rel="nofollow">https://github.com/COVESA/vss-tools/pull/325</a></li><li>VSS PRs<ul><li>text (iso) reprsentation for time</li><li>obd - deprecate first</li></ul></li><li>Multi unit support <a href="https://github.com/COVESA/vehicle_signal_specification/issues/690" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/690</a></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2024-01-16:">Meeting notes 2024-01-16:</h1><ul><li>VSS 4.1 Released</li><li>AMM April 16-18 Gothenburg, Sweden<br/><ul><li>Technical Sessions Planning in progress</li></ul></li><li>CES - big interest in VSS</li><li>Digital Key<ul><li>Ted<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/702" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/702</a></li><li>Big interest withon commercial vehicles</li><li>Important not to compete with CCC, complement rather than compete</li><li>We need to be careful not to infringe on CCC license</li></ul></li></ul></li><li>Overlay problem<ul><li>Adnan:<ul><li>Overlay (to redefine/overwrite attribute or add attributes) is case sensitive, could result in two signals.</li><li>How to prevent it?</li><li>Alt 1: Do a case insensitive merge (keep orig name)</li><li>Alt 2: Give warning if diff just by case somewhere (and error if in strict mode?)</li><li>If warning - handle it like they are the same</li><li>Will possibly create PR</li></ul></li></ul></li><li>New VSS PRs</li><li>VSS-style issue (enforce style, allowed values)</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-12-19:">Meeting notes 2023-12-19:</h1><ul><li>VSS 4.1<ul><li>pre-release available at <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.1" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.1</a></li><li>Adnan: Something that needs to be fixed</li><li>Erik: Pre-release yanked, awaiting fix from Adnan</li></ul></li><li>Screen mirroring - <a href="https://github.com/COVESA/vehicle_signal_specification/pull/699" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/699</a></li><li>Issue690<ul><li>BMW use processing w overlays, what makes sense in VSS is to create separate file with conversion factors, which could be used for conversion. Repetition in vss-tree would be too much to handle.</li><li>When we are all back present the proposal from Erik</li><li>Daniel: We could use examples for different APIs</li><li>Erik: AP to present possible solution Jan 16th</li></ul></li><li>FMS/ACEA<ul><li><a href="https://wiki.covesa.global/download/attachments/48529442/onbord%20API%20-%20COVESA%20meeting%20presentation%2020231214.pdf?version=1&modificationDate=1702999937523&api=v2" data-linked-resource-id="88211529" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="onbord API - COVESA meeting presentation 20231214.pdf" data-nice-type="PDF Document" data-linked-resource-content-type="application/pdf" data-linked-resource-container-id="48529442" data-linked-resource-container-version="132">Presentation</a></li></ul></li><li>Meeting Jan 9th cancelled due to CES</li><li>Next official meeting Jan 16th - create issues or bring up topic on slack if needed</li><li>Catena:<ul><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> - when you will you send out invitation?</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-12-12:">Meeting notes 2023-12-12:</h1><ul style="list-style-type: square;"><li>Catena-x topic.<ul style="list-style-type: square;"><li>Adnan: We had some discussions about VSS and Catena.</li><li>Achim: Proposal on how to harmonize activities.</li><li>Achim: Find alignment among companies that are willing to contribute.</li><li>Achim: We should be prepared for the catena extension and make alignment there. Next step: Ford, Bosch, BMW to find alignment regarding vehicle domain. <br/><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> will setup a meeting.</li></ul></li><li>Overview VSS-Tools, VSS.</li><li>Issue 690 - continued discussion.<ul style="list-style-type: square;"><li>Nick prepared overview on how to handle units.</li><li>Adnan presented high-level approach he uses at BMW.</li><li>Erik to present solution proposal. We need more input.</li></ul></li><li>Meeting pause for christmas/new year? 26th and 2nd of January we will take a break.</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-12-05:">Meeting notes 2023-12-05:</h1><ul><li>FMS/ACEA meeting<ul><li>Ongoing discussion how/if VSS can be used</li><li>FMS - Fleet Management System standard, created by European association of vehicle manfacturers (ACEA)</li><li><a href="https://www.fms-standard.com/" class="external-link" rel="nofollow">https://www.fms-standard.com/</a></li><li><a class="external-link" href="https://github.com/eclipse-sdv-blueprints/fleet-management" rel="nofollow">https://github.com/eclipse-sdv-blueprints/fleet-management</a></li><li><a class="external-link" href="https://github.com/eclipse-sdv-blueprints/fleet-management/blob/main/spec/mapping-fms4-to-vss.md" rel="nofollow">https://github.com/eclipse-sdv-blueprints/fleet-management/blob/main/spec/mapping-fms4-to-vss.md</a></li></ul></li><li>Catena-X (Achim)<ul><li><a class="external-link" href="https://catena-x.net/en/benefits" rel="nofollow">https://catena-x.net/en/benefits</a></li><li>European initiative to originally exchange manufacturing data (quality, availability, ...), increased scope to "Digital Twin", behavior and field quality</li><li>Currently focusing on European market</li><li><a href="https://projects.eclipse.org/projects/automotive.tractusx" class="external-link" rel="nofollow">https://projects.eclipse.org/projects/automotive.tractusx</a></li><li><a class="external-link" href="https://eclipse-tractusx.github.io/" rel="nofollow">https://eclipse-tractusx.github.io/</a> - went public some weks ago.</li><li>Partial overlap Catena-X and VSS data</li><li>"Endurance Estimator" API</li><li>First decision - do we in COVESA want to interact? If so proposal to Catena-X to join COVESA</li><li>Sebastian: Catena are aware of VSS</li><li>Achim: We can convert a VSS ontology to a Catena aspect model.</li><li>Sebastian: Can we "convert them" to VSS or uServices</li><li><strong>Erik: Shall we let Data Expert Group analyze and identify alternatives on how to continue.</strong></li><li>Paul: Discuss possibly January</li><li>Achim: Not all data relevant for VSS, but where we overlap they could use VSS</li><li>Ted: What about ASAM (<a class="external-link" href="https://www.asam.net/standards/detail/sovd/" rel="nofollow">https://www.asam.net/standards/detail/sovd/</a>)</li><li>Achim: No semantics in ASAM</li><li>Adnan: Will check internally</li></ul></li><li>VSS 4.1 Status<ul><li>Release Candidate at <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.1rc0" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.1rc0</a></li><li>Unless anything critical reported before Dec 15th and not fixed, 4.1 will be released, likely Dec 15th or 18th</li></ul></li><li>New PRs/Issues<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/690" class="external-link" rel="nofollow">Issue 690</a> - continue discussion next week</li><li>Notifications - <a class="external-link" href="https://github.com/COVESA/vehicle_signal_specification/issues/694" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/694</a></li><li>Left/Right vs Driver/Passenger - <a href="https://github.com/COVESA/vehicle_signal_specification/pull/695" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/695</a></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-11-28:">Meeting notes 2023-11-28:</h1><ul><li>Prioritized Topics<ul><li>VSS 4.1<ul><li>Static Id: <a href="https://github.com/COVESA/vss-tools/pull/305" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/305</a></li><li>Quantities: <a href="https://github.com/COVESA/vss-tools/pull/312" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/312</a></li><li>Proposal: Will be merged Friday unless any comments</li><li>Creation of beta release Friday or Monday</li></ul></li><li>Tool restructuring - "abstract tool"</li><li>Ford Ontology - <a href="https://github.com/COVESA/vehicle_signal_specification/pull/685" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/685</a><ul><li>Proposal for documentation as "VSS extension"</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-11-21:">Meeting notes 2023-11-21:</h1><ul><li>Prioritized Topics<ul><li>Release Preparation<ul><li>Static id PR status - no news</li></ul></li><li>Unit discussion<ul><li>Ready to merge?<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/669" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/669</a></li><li><a href="https://github.com/COVESA/vss-tools/pull/307" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/307</a></li></ul></li></ul></li><li>Umang PRs</li><li>Support for multiple units - <a href="https://github.com/COVESA/vehicle_signal_specification/issues/690" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/690</a></li><li><s>Ford Ontology PR</s> - Postponed due to lack of time</li><li>Other PRs</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-11-14:">Meeting notes 2023-11-14:</h1><ul><li>Prioritized Topics<ul><li>Release Preparation<ul><li>Static id PR status - no news</li></ul></li><li>5.0?<ul><li>Pierre: We can add "5.0" signals as overlays, so we can use torque as overlay.</li><li>Decision: Keep 5.0 on hold, open up to release 5.0 in April/May (or earlier if needed)</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-11-07:">Meeting notes 2023-11-07:</h1><ul><li>Prioritized Topics<ul><li>Release Preparation<ul><li>Decision needed - shall we only release 4.1 and not 5.0?<ul><li>Potential rationale: The only "major changes" we have is unit/datatype/semantic change of 5-10 signals. Historically not sufficient for a "major" release, or?</li><li>Working assumption: We do not release 5.0 now as no requests, plan for spring instead</li><li>AP: Erik to check with <a class="confluence-userlink user-mention" data-username="ppblais@blackberry.com" href="https://wiki.covesa.global/display/~ppblais@blackberry.com" data-linked-resource-id="64979187" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Pierre Pierre Blais</a> if Blackberry sees a value in a major relase now</li><li>If your organization wants a 5.0 before Christmas, please let us now</li><li>AP: Erik to update 4.X branches (cherry pick)</li></ul></li><li>Timeframe static id change<ul><li>Adnan: working on hash support in addition to sequential id, compared 64 bit sv 32 bit hash.</li><li>Adnan: For hashing path, type, unit and datatype is used</li><li>Erik: we could create new pr from niclas fork if needed</li></ul></li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-10-31:">Meeting notes 2023-10-31:</h1><ul><li>Prioritized Topics<ul><li>Static UID - draft PR at <a href="https://github.com/COVESA/vss-tools/pull/305" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/305</a><ul><li>New script <code>vspecID.py</code> </li><li>Give vspec files as both input and output</li><li>You can specify prefix with "gen-layer-ID-offset", first 64 reserved for COVESA. WIth id layer 4 bytes, otherwise 3 bytes</li><li>Adds a staticUID string, like '0x02345678'</li><li>"--validate-static-uid <old.vspec>" gives option to keep/replace if changed, if compatible (like name check)</li><li>You maintain static id files yourself</li><li>Once you have the generated <strong>.vspec/</strong> .yaml, then with overlay you can run all other tools, like vspec2json</li><li>Erik: Can be included in minor release, as it does not affect UUID</li><li>Pierre: The Blackberry model serves the same purpose, different approach</li><li>Pierre: How to manage addressing by old name, if name is changed.</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-10-24:">Meeting notes 2023-10-24:</h1><ul><li>Prioritized Topics:<ul><li>Summer time alignment<ul><li>Ends Oct 29 Europe</li><li>Historically COVESA meetings often anchored in European time zone</li><li>Currently conflict - VSS anchored in european, but CVI anchored after</li><li>Suggestion - keep european time for VSS next week, move CVI</li><li>AP <a class="confluence-userlink user-mention" data-username="erik.jaegervall" href="https://wiki.covesa.global/display/~erik.jaegervall" data-linked-resource-id="363989" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Erik Jaegervall</a> to sync with <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> </li><li>AP: Send out reminder on slack</li></ul></li><li>Copyright<ul><li>AP: <a class="confluence-userlink user-mention" data-username="erik.jaegervall" href="https://wiki.covesa.global/display/~erik.jaegervall" data-linked-resource-id="363989" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Erik Jaegervall</a> to follow up with <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> </li><li>Conclusion: Go with proposal</li><li>AP: Erik update PR for next meeting, then please review</li></ul></li><li>(U)UID:<ul><li>Draft at <a href="https://github.com/adobekan/vss-tools/tree/static_id_generator" class="external-link" rel="nofollow">https://github.com/adobekan/vss-tools/tree/static_id_generator</a>, official PR to come</li><li>Idea is that everyone can maintain there own static id file, no "official" version maintained</li><li>10-15 minute demo next week</li><li>Can keep multiple leaf name with same id.</li></ul></li><li>General info from Paul<ul><li>Please put company name in zoom "user name" - make it easier to understand who you are talking to</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-10-17:">Meeting notes 2023-10-17:</h1><ul><li>Prioritized Topics:<ul><li>AMM recap<ul><li>VSS discussion points<ul><li>Erik showed some slides</li><li>AP: Erik to summarize response/comments (See <a href="https://wiki.covesa.global/download/attachments/48529442/VSS_workshop_comments.pdf?version=1&modificationDate=1698153379279&api=v2" data-linked-resource-id="78840666" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="VSS_workshop_comments.pdf" data-nice-type="PDF Document" data-linked-resource-content-type="application/pdf" data-linked-resource-container-id="48529442" data-linked-resource-container-version="132">VSS_workshop_comments.pdf</a>)</li><li>AP: erik to create issues for topics that seems to have traction, so that we can make decision</li><li>Adnan: Daniel Alvarez wanted to create proposal related to model/ontology, align with proposal from Alan</li><li>Erik: Shall we possibly do a similar presentation online "evolvement workshop" in January?</li><li>Paul: Seems good</li><li>AP: Paul to propose date/time for a session in late January</li></ul></li></ul></li><li>JSON schema</li></ul></li></ul><p><br/></p><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-10-03:">Meeting notes 2023-10-03:</h1><ul><li>Prioritized Topics:<ul><li>VSS session AMM Thursday<ul><li>Intention to discuss Ford/Blackberry proposals as well as other recurring topics</li><li>AP: Check with Paul - join the two sessions</li><li>Will someone from Ford (Alan?) and Blackberry (Pierre?) participate?<ul><li>Ford possibly remote</li><li>Pierre will leave at lunch Thursday</li></ul></li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-09-26:">Meeting notes 2023-09-26:</h1><ul><li>Prioritized Topics:<ul><li>Presentations <br/><ul><li>Blackberry: <a href="https://wiki.covesa.global/display/WIK4/COVESA+Spotlight+Sessions">COVESA Spotlight Sessions</a></li><li>Ford: <a href="https://wiki.covesa.global/display/WIK4/Data+Models+and+Ontologies#DataModelsandOntologies-ProposalsandPresentations">Data Models and Ontologies#ProposalsandPresentations</a></li><li>Erik & Adnan to follow up with Paul on how to continue discussion</li><li>Session (VSS evolvement) at AMM for brainstorming/discussion</li></ul></li><li>No regular meeting October 10th (AMM)</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-09-19:">Meeting notes 2023-09-19:</h1><ul><li>Prioritized Topics:<ul><li>Tero from Profilience introduced him self.</li><li>COVESA Spotlight - BlackBerry IVY, next after this meeting, they will show how they use VSS</li><li>4.1-planning - UUID, any timeplan<ul><li>Adnan: Draft PR in about 3 weeks,</li><li>Erik: Great if draft ready before AMM</li><li>Adnan: Concerning instances, have id for "top" definition (class) rather than individual instances</li></ul></li><li>Struct support and DDSIDL<ul><li><a href="https://github.com/COVESA/vss-tools/pull/262" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/262</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/576/files" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/576/files</a></li><li>Adding more metadata as propes in 576 has some similarities to what proposed by Ford. No further work has been performed on this PR</li><li>Krishna:<ul><li>Would like to go back to our original idea of supporting VSS as is and continue with 262.</li><li>Will rebase 262</li><li>Should likely be possible to close around 1 month from now</li></ul></li><li>Erik: That works well with 4.1 plans, feature freeze some time after AMM...</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-09-12:">Meeting notes 2023-09-12:</h1><ul><li>Prioritized Topics:<ul><li>Short discussion on Ford presentation on "their VSS representation"<ul><li>"Changing VSS to ontology"</li><li>Potential implications: Use a new VSS source format, generate "old VSS format" from it?</li><li>Gunnar: need for discussion on how to bridge the gap between their representation and current VSS</li><li>Daniel: adopting some steps is possible, keep alignment to existing VSS Yaml important. Some proposals presented are aligned with ideas/proposal from ontology team</li></ul></li><li> Major/Minor<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/634" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/634</a></li><li>See <a href="https://github.com/COVESA/vehicle_signal_specification/wiki/VSS-Version-Governance-(Major-Minor)" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/wiki/VSS-Version-Governance-(Major-Minor)</a></li><li>Topics:<ul><li>Deprecation</li><li>How long to maintain "minor releases" (Suggestion 1 year, but at least 6 months after next major)</li></ul></li></ul></li><li>4.1 release - any "must haves"?<ul><li>Bosch suggestion: <a href="https://github.com/COVESA/vss-tools/pull/293" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/293</a></li><li>Daniel: The UUID replacement, Adnan is working on it, maybe, ...</li></ul></li><li>Instance handling issue for discussion:<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/642" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/642</a></li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-09-05">Meeting notes 2023-09-05</h1><ul><li>Prioritized Topics:<ul><li>Anything new?</li><li>AMM:<ul><li>If you have presentations for the AMM give them Paul</li><li><a href="https://wiki.covesa.global/display/WIK4/AMM+Planning+October+10-12+2023+-+Technical+Session+and+Workshop+Proposals">AMM Planning October 10-12 2023 - Technical Session and Workshop Proposals</a></li><li><a href="https://wiki.covesa.global/display/WIK4/Technical+Track+-+Working++Internal+planning+page+for+COVESA+AMM+October+2023">Technical Track - Working Internal planning page for COVESA AMM October 2023</a> (no longer up to date)</li><li><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=71073822">Internal planning page for COVESA AMM October 2023</a> (Limited access)</li><li>Please review, please suggest to Paul, or bring up in next DEG meeting or bring it up in Slack, agenda deadline sept 12th</li></ul></li><li>Paul:<ul><li>COVESA wants technical representation at ETAS dev summit late September<ul><li><a href="https://www.etas.com/en/company/etas-developer-summit-2023-on-september-28.php" class="external-link" rel="nofollow">https://www.etas.com/en/company/etas-developer-summit-2023-on-september-28.php</a></li></ul></li></ul></li><li>Release planning<ul><li>Need for any more release 2023<ul><li>Sebastian: Good to have a minor release this year. Major before spring AMM.</li><li>Paul: Cadence is good/important. AMM suggested by board.</li><li>Erik: Plan release for AMM, but postpone if any bigger things is in pipeline.</li></ul></li><li>Major/Minor in parallel (<a href="https://github.com/COVESA/vehicle_signal_specification/pull/637" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/637</a>, <a href="https://github.com/COVESA/vehicle_signal_specification/issues/634" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/634</a>), is there a need?</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-08-15">Meeting notes 2023-08-15</h1><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized Topics:<ul><li>Anything VSS related things we/you want to do at AMM<ul><li>BlackBerry looking into having a demo and presentation</li><li>COX automotive will attend</li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools<ul><li><a href="https://github.com/COVESA/vss-tools/pull/296" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/296</a></li><li>Could be a bridge into the JSON schema/ OpenAPI ecosystem</li><li><a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshops - Interface Pillar Alignment</a> (Meeting right after VSS ) </li></ul></li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><ul><li style="list-style-type: none;"><ul><li>Erik and Adnan on holiday next two weeks, should we cancel one? We might discuss in Slack. Make the decision early enough so it can be cancelled via Shared Calendar by <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> </li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-08-08">Meeting notes 2023-08-08</h1><ul><li>General Topics<ul><li>COX automotive → automatic mapping of data source<ul><li>Ulf: no active work at the moment. Trend is existing but we would have to push the activity.</li><li>Adnan: Volvo is working on this topic and they have presented work on last AMM in Porto.</li><li>V.Raiker (Ford) - Interest for a WS on the next AMM</li><li><a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> Could you please create wiki page where we can collect requirements for automatic mappings and as well existining activities.</li></ul></li></ul></li><li>PR Status<br/><ul><li>No new PR or issues.</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-08-01">Meeting notes 2023-08-01</h1><ul><li>Presentation of VSS and Spread by Daniel Wilms<ul><li>Presentation coming</li></ul></li><li>Adnan: <a href="https://github.com/COVESA/vss-tools/pull/296" class="external-link" rel="nofollow">Pull request</a> on example shown in latest interface workshop</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-07-18(Draft)">Meeting notes 2023-07-18 (Draft)</h1><ul><li>DEG Interface Pillar Meeting July 25th<ul><li>Draft agenda: <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+Workshops+-+Interface+Pillar+Alignment">Data Expert Group Workshops - Interface Pillar Alignment</a></li><li><strong>This means VSS meeting will likely be cancelled next week</strong></li></ul></li><li>Id elements</li><li>Next meeting: Daniel Wilms to present representation of VSS using GraphQL</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-07-11">Meeting notes 2023-07-11</h1><ul><li>Notes taken in issues/PRs</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-06-27">Meeting notes 2023-06-27</h1><ul><li>Ulf presented the updated HIM repo (<a href="https://github.com/COVESA/hierarchical_information_model" class="external-link" rel="nofollow">https://github.com/COVESA/hierarchical_information_model</a>)<ul><li>AP: Erik to check if doc can be generated</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-06-20">Meeting notes 2023-06-20</h1><ul><li>No prioritized topics</li><li>Please check <a href="https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts">Defining the COVESA data modeling strategy and its associated artifacts</a> as it tries cover also other domains. Add comments/question in wiki</li><li>Syntax checking (related to <a href="https://github.com/COVESA/vehicle_signal_specification/issues/599" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/599</a>)<br/><p>Meeting notes:</p><p>- Daniel: See <a href="https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts" rel="nofollow">https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts</a>, would be better to have a standard format like RDF as source format.<br/>- Erik: So let tools use on RDF directly and generate other format from that?<br/>- Daniel; yes, still have *.vspec as experts but generated to RDF - let RDF be official format.<br/>- Fulup: Do not think people will parse from RDF directly, vspec->RDF->json seems complicated<br/>- Ulf: Keep YAml/vspec as single source of truth. It should be possible to generate RDF<br/>- Erik: Is a vspec2rdf tool all we need (short time)<br/>- Daniel: vspec2ttl already partially do it<br/>- Paul: Important to not slow down VSS progress<br/>- Fulup: Would love to have a tool that let my select which parts and get a normalized output with normalized quotes</p>-Pierre: Isn’t RDF more restrictive in its syntax than YAML, which would make conversion from YAML to RDF somewhat difficult?</li><li>We would likely have to put some restrictions into what can be represented in YAML so that it can be converted to RDF.</li><li>Paul: A session with data guys would be helpful. RDF is well established</li><li>Erik: Maybe would be good to agree on a long-term roadmap for VSS source format and tooling, what do we want the source format and tooling to look like in 5 years</li><li>Paul: Will arrange a more in-depth session</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-06-13">Meeting notes 2023-06-13</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized Topics:</li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-06-06">Meeting notes 2023-06-06</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li><li>Gunnar: introduction of IFEX and VSS.</li><li>Link to VSSo proposal <a href="https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts">Defining the COVESA data modeling strategy and its associated artifacts</a></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-05-22">Meeting notes 2023-05-22</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>DCO Github app (rather than action)<ul><li>See <a href="https://github.com/COVESA/vss-tools/pull/290" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/290</a> as example</li></ul></li><li>"Service APIs"/functions call still of interest. Questions: How would it fit with the VSSo proposal/The "HIM" proposal. Adnan maybe to provide some information how they handle it internally</li></ul></li></ul><p><em>1. Decide on name for the evolved data model.</em></p><p><em>2. Create a new COVESA Github repo based on the new name.</em></p><p><em>3. Decide on a directory structure that can accommodate rule set definitions for multiple domains and multiple information types.</em></p><p><em>4. Create a rudimentary README on the top level giving a high level description of the new data model.</em></p><p><em>5. Move the VSS "rules definition" (the documentation) from the VSS repo to an appropriate directory on this new repo.</em></p><p><em>6. Create a rule set for services that that meets the requirements from the "passenger car domain" (VSS).</em></p><p><em>7. On the VSS repo, create an initial service tree based on the rule set from the bullet above. Continue to evolve it in parallell with the existing VSS tree.</em></p><p><em>8. Analyze the impact on VSS-Tools that the above has, take action on the insights from that.</em></p><p><em>9. Try to influence the W3C automotive group to evolve VISSv2 to support the new data model.</em></p><p><em>10. If successful on the above bullet, create a new COVESA project that will develop a POC containing a technology stack based on the evolved W3C interface and COVESA data model.</em></p><ul><li style="list-style-type: none;"><ul><li> Discussion:<ul><li>Ulf presented the proposal above</li><li>Erik: Will be discussed in DEG group, VSC relationship to be sorted out.</li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-05-23">Meeting notes 2023-05-23</h1><p><em>(Erik will not join)</em></p><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Release 4.0 Status<ul><li>V4.0 released <a href="https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.0" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.0</a></li><li>Topics addressed during RC-phase. If someone wants an alternative solution as long term solution they are welcome to create a PR<ul><li><code>d</code> added as prefix to string literals that could be numbers, like <code>'33'</code>. Just using <code>_33</code> is not supported by all code generators working on DDS IDL.</li><li>Type checker for structs updated to support arrays of struct</li><li>Error now given if type root is not a branch (as some tools like vspec2protobuf can not handle struct as root)</li></ul></li><li>Daniel to introduce what has been done in VSSo: <a href="https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts">Defining the COVESA data modeling strategy and its associated artifacts</a><ul><li>Please read if interested, (you may post comments on the Wiki page)</li><li>Daniel will be back in 3 weeks to personally answer question <img class="emoticon emoticon-smile" src="https://wiki.covesa.global/s/ypeau5/8804/xgjkrn/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)" /></li></ul></li></ul></li><li>"Service APIs"/functions call still of interest. Questions: How would it fit with the VSSo proposal/The "HIM" proposal. Adnan maybe to provide some information how they handle it internally</li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS<ul><li>Time Remaining Signals: <a href="https://github.com/COVESA/vehicle_signal_specification/pull/610" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/610</a> <ul><li>Signals are useful</li><li>Discussion about naming, see PR comments</li></ul></li><li>Traction Battery <a href="https://github.com/COVESA/vehicle_signal_specification/pull/601" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/601</a><ul><li>Charging.Mode refactored - please review</li></ul></li></ul></li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-05-16">Meeting notes 2023-05-16</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Release 4.0 Status<ul><li>RC2 created<br/><ul><li>For DDSIDL we now add a <code>d</code> as prefix for string numeric literals, i.e. '33' → d33</li><li>Pypi packaging: <a href="https://github.com/COVESA/vss-tools/pull/281" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/281</a><ul><li>Sebastian: Check if we can add README (for Project description)</li><li>Paul: There are other repos using VSS in the name</li><li>AP: Paul to create pypi account. Erik to add Paul as owners. Paul to check if Steve Crumb wants/have an account.</li></ul></li></ul></li><li>Need for decision: OK to release?<ul><li>Decision: Release</li><li>Decision: Delete RC releases, keep RC tags (Erik update wiki for release instructions)</li></ul></li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS<ul><li>Traction Battery <a href="https://github.com/COVESA/vehicle_signal_specification/pull/601" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/601</a><ul><li>Continued internal discussion at Bosch needed for Charging.Mode signal.</li></ul></li></ul></li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS<ul><li>Virtual signals: <a href="https://github.com/COVESA/vehicle_signal_specification/issues/595" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/595</a></li><li>Maritime data (Fulup): <a href="https://github.com/COVESA/vehicle_signal_specification/issues/607" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/607</a></li></ul></li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting<ul><li>Daniel to introduce what has been done in VSSo (wiki page)</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-05-09">Meeting notes 2023-05-09</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Release 4.0 Status<ul><li>RC exists</li><li>One regression DDSIDL: <a href="https://github.com/COVESA/vss-tools/pull/277" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/277</a></li><li>Also some minor fixes (broken links)</li><li><em>Name of dev-version</em><ul><li>Preferred "4.1-dev" (and not develop)</li><li>AP: Erik to change and document!</li></ul></li></ul></li><li>Pypi packaging: <a href="https://github.com/COVESA/vss-tools/pull/273" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/273</a><br/><ul><li>Interest? <a href="https://test.pypi.org/project/vss-tools/" class="external-link" rel="nofollow">https://test.pypi.org/project/vss-tools/</a>?</li></ul></li><li>Traction Battery <a href="https://github.com/COVESA/vehicle_signal_specification/pull/601" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/601</a></li><li>Virtual signals: <a href="https://github.com/COVESA/vehicle_signal_specification/issues/595" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/595</a></li><li>API definition:<ul><li>Achim: presents</li><li>Not only data API, but also service</li><li>Needs to create API publishing format</li><li>Decision: Is data expert group right host?</li><li>Paul: DEG is right place - we can use VSC slot?</li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Open Pull Requests VSS-Tools<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-05-02">Meeting notes 2023-05-02</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Release 4.0 Planning<ul><li>Agree on what needs to be in - which PRs/features<ul><li>Struct overlay and documentation.<ul><li>Overlay part fixed, minor doc update remaining.</li></ul></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/540" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/540</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/546" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/546</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/577" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/577</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/574" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/574</a><ul><li>Still relevant?</li></ul></li></ul></li><li>Proposal from meeting before AMM<br/><ul><li>Feature Freeze May 2nd (just after AMM)</li><li>Pre-release/Release-candidate to be released first week of May<ul><li>To be done by Erik</li></ul></li><li>Actual release two weeks later</li><li>Any fixes (PRs) needed for VSS 4.0 after release candidate must be directed to specific branch (release/4.0)<ul><li>Erik to describe release candidate workflow</li></ul></li></ul></li></ul></li><li>New Issue 586.</li><li>Best practices - VSS design principles<ul><li>Stephen<ul><li>Would be good to have design principles that we can refer to, like doing X is aligned with principle Y</li><li>I will ask Felix and Daniel to get input, like on "what is a branch" from a data science view</li><li>I will drive it.</li></ul></li><li>Daniel: I can support</li><li>Nick: Would be a good idea, a lot of collective opinions is not documented<ul><li>Including how we express what language to use (american vs english), date formats, ...</li></ul></li><li>Erik: Where to handle calls/meetings, in this or in other. This meeting is often quite busy.</li><li>Where/how to be synched on slack</li><li>Announced in this meeting.</li><li>Daniel: One ontology work that is ongoing is to come up with keywords, calls 30 minutes before this one, I can share link</li></ul></li><li>Fulup presented <a href="https://github.com/eclipse/kuksa.val.feeders/issues/94" class="external-link" rel="nofollow">https://github.com/eclipse/kuksa.val.feeders/issues/94</a><ul><li>Concerns "security tags" in VSS - an area where COVESA might do something</li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Open Pull Requests VSS-Tools<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Issues VSS<ul><li>Please check <a href="https://github.com/COVESA/vehicle_signal_specification/issues/567" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/567</a></li></ul></li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting<ul><li>VSS 4.0 release planning<ul><li>Remaining features</li><li>Date for release and release candidate</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-MeetingNotes2023-04-18">Meeting Notes 2023-04-18</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Structs Status<ul><li>IDL: <a href="https://github.com/COVESA/vss-tools/pull/262" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/262</a><ul><li>Related: <a href="https://github.com/COVESA/vehicle_signal_specification/pull/576/files" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/576/files</a></li><li>Discussion:<ul><li>Sebastian: Proposal is a bit different, new concept, nothing prevents merging PR from Krishna so old style converter support structs, or wait with both</li><li>Neil: Do we want to restruct existing signals in catalog</li><li>Krishna: Not yet</li><li>Sebastian - but do we want hints, if tools are "perfect"?</li><li>Adnan: Could be an idea to collect starting points for struct candidates (after 4.0)</li><li>Ulf: A signal represent a datapoint, captured at a specific time, similar approach for structs, all properties within the struct are all captured at the same point in them. fits well to GPS, but not for example door/window signals as they are not captured at same point in time.</li></ul></li><li>Decision: Do not add IDL for 4.0</li></ul></li><li>For VSS 4.0 - status (to be confirmed):<ul><li>Done: Protobuf, JSON, CSV, Yaml</li><li>Ongoing: DDSIDL</li><li>Not done: Overlays, Multi -vt, Franca, Binary, Ttl (contrib), Graphql</li><li>Needs revisit: Documentation (to indicate status)</li></ul></li><li>Discussion:<ul><li>Sebastian: What is our long term approach - will struct support in long run be added to Franca, Binary, Ttl (contrib), Graphql</li><li>Krishna: Needs expertise support</li><li>Ulf: Binary will come a few weeks after AMM</li><li>Pierre: What if we later detect if we need to change syntax of structs to support e.g. Graphql</li><li>Krishna: Seems to be acceptance of releasing VSS 4.0 with limitations, but fast resolving of remaining topics wanted</li><li>Erik: Ok to relase VSS 4.0, plan remaining tools/limitations to VSS 4.1</li><li>Daniel: Could possibly contribute to TTL, dependency to VSSo, refactoring discussion in progress</li><li>Neil: Have we an idea what signals should be put in struct</li><li>Stephen: Not intending to refactor existing tree. Best practices document needed.</li><li>Erik: What we have said so far - structs shall be restrictevly used in standard catalog, possible candidate Position (lat/lon)</li><li>Daniel: Not clear to me when to use struct vs aggregate. Risk using aggregate on branches if there is no rule-set to branches. There should simple rule-set for branches in general. No clear criteria used as of today.</li><li>Erik: branches as of today is mostly to get unique names</li><li>Krishna: Overlays and doc can be fixed for relase, but can we release withou strucs</li></ul></li></ul></li><li>Release 4.0 Planning<ul><li>Agree on what needs to be in - which PRs/features<ul><li>Struct overlay and documentation.<ul><li>Krishna has not bandwith to overlay. Erik may have time, Neil as well.</li></ul></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/540" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/540</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/546" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/546</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/577" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/577</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/574" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/574</a></li></ul></li><li>Proposal<ul><li>Feature Freeze April 27th (just after AMM)</li><li>Pre-release/Release-candidate to be released first week of May<ul><li>To be done by Erik</li></ul></li><li>Actual release two weeks later</li><li>Any fixes (PRs) needed for VSS 4.0 after release candidate must be directed to specific branch (release/4.0)<ul><li>Erik to describe release candidate workflow</li></ul></li></ul></li></ul></li><li>Screen off PR - <a href="https://github.com/COVESA/vehicle_signal_specification/pull/577" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/577</a><ul><li>How to represent "off time" - duration or absolute time?<ul><li>Duration in seconds</li></ul></li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Open Pull Requests VSS-Tools<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Issues VSS<ul><li>Please check <a href="https://github.com/COVESA/vehicle_signal_specification/issues/567" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/567</a></li></ul></li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting<ul><li>VSS 4.0 release planning<ul><li>Remaining features</li><li>Date for release and release candidate</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Agenda2023-04-11">Agenda 2023-04-11</h1><ul><li>Welcome and Compliance statement</li></ul><p><em>Welcome to the COVESA VSS Meeting!</em></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Structs Status</li><li>Display Idle Time - see <a href="https://github.com/COVESA/vehicle_signal_specification/issues/567" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/567</a></li><li>List DTCs in VSS<ul><li>Currently there are signals for DTCs in OBD branch, but just a list of strings</li><li>Question: Shall we model "all" DTCs in the model?</li><li>Sebastian: Currently no ongoing work to model DTCs in VSS</li><li>V Raikar: Should signals corresponding to DTCs be represented in tree?</li><li>Erik: We have some signals representing errors today, but they are just boolean</li><li>Erik: A more specific proposal/idea would be interesting to discuss in this meeting.</li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Open Pull Requests VSS-Tools<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Issues VSS<ul><li>Please check <a href="https://github.com/COVESA/vehicle_signal_specification/issues/567" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/567</a></li></ul></li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting<ul><li>VSS 4.0 release planning<ul><li>Remaining features</li><li>Date for release and release candidate</li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-MeetingNotes2023-04-04">Meeting Notes 2023-04-04</h1><ul><li>Compliance statement</li></ul><p><br/></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><p><br/></p><ul><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Structs Status<ul><li>Textual Update - Use "ComplexDataTypes"</li><li>ProtoBuf - convention one file per message</li><li>DDSIDL - is extension style valid</li></ul></li><li>UUID update (postponed from next meeting)<ul><li>Adnan:<ul><li>Idea use UUID to define signal/property, not location</li><li>For binary exchange we need to share schema in advance. Can we use small UUIDs. One byte to identify vendor/overlay, other two bytes for every specific leaf. Stored in a unique way.</li></ul></li><li>Krishna: We need to optimize transfer, assign unique identifier based on VSS. Shall it be left to implementer?</li><li>Erik: Should be possible to support multiple UUID-technologies in vss-tools</li><li>Sebastian: Canonical UUIDs with clear formula so they are reproducable are great</li><li>Nick: Have you considered ASN.1?</li></ul></li><li>EV-charging repository: <a href="https://github.com/COVESA/ev_charging" class="external-link" rel="nofollow">https://github.com/COVESA/ev_charging</a></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Open Pull Requests VSS-Tools<ul><li>Please review, minor ones will be merged next week unless there are remarks</li></ul></li><li>Issues VSS<ul><li>Please check <a href="https://github.com/COVESA/vehicle_signal_specification/issues/567" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/567</a></li></ul></li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-MeetingNotes2023-03-28">Meeting Notes 2023-03-28</h1><ul><li>Compliance statement</li></ul><p><br/></p><p><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong><br style="text-align: left;"/><span style="color: rgb(29,28,29);">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.</span></p><p><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong><br style="text-align: left;"/><span style="color: rgb(29,28,29);">Further, COVESA aspires to the an open and royalty-free organization. The discussions and contributions made during this session are governed by the <a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></p><p><br/></p><ul><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Consolidating structs<ul><li>Initial exporters - approach currently to get two files, ones for signals and one for types</li><li>Two files may not make sense for all exporters</li><li>Two files pro - matches input</li><li>One file pros - consolidated view, self sufficient,</li><li>Krishna wants input - what do we want.</li><li>Ulf: Value in one file, but configurable (where applicable) best</li><li>Sebastian: We do not need to do the same for all exporters. Better to have discussion tool by tool.</li><li>JSON:<ul><li>Krishna: One usage imported into other tool, would be easier with single tool.</li><li>Sebastian: One file better</li><li>Could be user option.</li><li>Krishna: Will make output argument optional. if not present single file will be generated.</li></ul></li></ul></li><li>UUID update (postpone to next meeting)</li><li>Jeremy Vaysettes (Michelin)</li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-03-21">Meeting notes 2023-03-21</h1><p><br/></p><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<br/><ul><li>Albert Kos: Gaia-X - (<a href="http://www.gaiax4ageda.de/" class="external-link" rel="nofollow">http://www.gaiax4ageda.de/</a>) interesting to get surrounding objects into VSS. Possible to setup a meeting?<ul><li>Sebastian: <a class="confluence-userlink user-mention" data-username="pboyes@covesa.global" href="https://wiki.covesa.global/display/~pboyes@covesa.global" data-linked-resource-id="12134612" data-linked-resource-version="2" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Paul Boyes</a> could organize meeting if needed</li><li>Ulf: No meeting necessarily needed, you could issue/PR.</li><li>Albert to start by creating issues (in 3 weeks)</li></ul></li><li>VSS-Tools - Line endings JSON?<ul><li>Result - no line breaks</li></ul></li><li>Tool limitations</li></ul></li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-03-14">Meeting notes 2023-03-14</h1><p><br/></p><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Intro to VSS - 16.00 CET Tomorrow</li><li>VSS-Tools - Line endings JSON?<ul><li>Result - no line breaks</li></ul></li><li>Issue 526</li></ul></li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-03-07">Meeting notes 2023-03-07</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>AMM topics.<ul><li>Schedule is starting to form. Contact is PaulB.</li><li>Working sessions will be on 26th and 27th. Focus on Data, VSS.</li><li>Current proposals <a href="https://wiki.covesa.global/display/WIK4/AMM+Planning+April+25-27+2023+-+Technical+Session+and+Workshop+Proposals">AMM Planning April 25-27 2023 - Technical Session and Workshop Proposals</a></li></ul></li><li>PRs for AMM VSS Workshop<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/555" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/555</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/526" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/526</a></li></ul></li></ul></li><li>Decision on old open PRs<ul><li>PR <a href="https://github.com/COVESA/vehicle_signal_specification/pull/526" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/526</a> We will wait for the input. Take connectivity as topic for VSS workshop.</li><li>NIck will add aditional documentation about connectivity into the PR 526.</li></ul></li><li>Open Pull Requests VSS<ul><li>PR</li></ul></li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-02-28">Meeting notes 2023-02-28</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>INFO: VSS 3.1 released</li><li>Wanted features for VSS 4.0 end of April (before AMM?)<ul><li>Structs support, but what more?</li><li>Moving documentation to new repo?<ul><li>Meeting notes -seems reasonable</li></ul></li></ul></li><li>AMM - what sessions are needed/wanted. What do we want to cover in the workshops<ul><li>Ulf: Slot/presentation on how evolving VSS ("multiple trees")<ul><li>Erik: Related to charging station tree discussion, we need to discuss governance of new catalogs, like where and how shall charging station tree be stored and maintained</li></ul></li><li>Sebastian: CAN Feeder - dbc mapping</li><li>Sebastian: Security approaches - KUKSA tokens changes and comparison to VISS</li><li>Adnan: VSSo and Taxonomy - see <a href="https://github.com/COVESA/vehicle_signal_specification/issues/548" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/548</a></li></ul></li><li>Open PRs - quite a lot</li><li>VSS structure<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/issues/548" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/548</a></li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-02-21">Meeting notes 2023-02-21</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Renew meeting invitation</li><li>Release planning VSS 3.1 (late February)<br/><ul><li>Remaining PRs/Features needed before we can release VSS 3.1<ul><li>Suggestions:<ul><li><a href="https://github.com/COVESA/vss-tools/pull/218" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/218</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/535" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/535</a></li><li>Basic struct documentation/placeholder?<ul><li>Erik to add "simple" doc for VSS 3.1, krishna to continue extending for VSS 4.0</li></ul></li></ul></li><li>AP: Erik to check with Paul on how to communicate that we have released VSS 3.1<ul><li>Compare with <a href="https://wiki.covesa.global/pages/viewpage.action?pageId=36077607">Reminiscing and Release of VSS Version 3.0</a></li></ul></li><li>AP: Erik: to prepare release</li></ul></li><li>PRs that better shall wait until after VSS3.1<ul><li>All other</li></ul></li></ul></li><li>Renault Meeting</li><li><s>VSPEC restructure - <a href="https://github.com/COVESA/vehicle_signal_specification/issues/527" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/527</a></s><ul><li><s>If agreed - best implemented and merged just after VSS 3.1 release - would cause conflicts to most other open PRs</s></li><li><s>Preferably "quick review process" to minimize time when there are conflicts</s></li></ul></li><li><s>Moving documentation to new repository (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/543" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/543</a>)</s><ul><li><s>Possible candidate for VSS 4.0?</s></li></ul></li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting<h3 id="VSSMeetingTopicsandMeetingNotes-w3cauto">w3cauto</h3></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meetingnotes2023-02-14">Meeting notes 2023-02-14</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Struct support<ul><li>Status report</li><li>Exporters - how do we expect them to handle struct data<ul><li>Struct information generated in same file or other file</li><li>Likely straightforward to implement support in vspec2json, vspec2csv, vspec2yaml</li><li>Volunteers for vspec2binary, vspec2ddsidl, vspec2franca, vspec2graphql?<ul><li>And contrib tools: vspec2protobuf, vspec2ttl</li><li>Daniel Alvarez will likely look at the vspec2ttl</li><li>Ulf feel responsibility for binary tool.</li><li>Sebastian can check with those who developed vspec2ddsidl</li></ul></li><li>AP: Erik to update or create issue to track what is needed for the major release in April</li></ul></li></ul></li><li>Workshop this week<ul><li>Agenda at <a href="https://wiki.covesa.global/display/WIK4/Data+Expert+Group+-+Workshop+2023+-+Q1">Data Expert Group - Workshop 2023 - Q1</a></li><li>All welcome</li><li>Attendees: erik, Ulf, Daniel (partially, 14-16 CET), Adnan, Sebastian (partially, +0.25)</li><li>AP: Paul to cancel related COVESA meetings during the same timeslots.</li></ul></li><li>"Extra day" at AMM for deeper discussions, possibly Friday after AMM, possibly half-day</li><li>New Pull requests</li></ul></li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting<ul><li>Planning for minor release (around end of February, possibly the week Feb 27th - March 3rd)<ul><li>What to include and what not to include:<ul><li>Possibly wait with left/right - driver/passenger conversion until major, as breaking backward compatibility</li></ul></li></ul></li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-MeetingNotes2023-02-07">Meeting Notes 2023-02-07</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li></ul><ul><li>PRs up for decision<ul><li>Power Optimize: <a href="https://github.com/COVESA/vehicle_signal_specification/pull/528" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/528</a></li><li>Steering angle: <a href="https://github.com/COVESA/vehicle_signal_specification/pull/530" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/530</a></li></ul></li><li>Prioritized topics<ul><li>Daniel issue</li><li>Connectivity PRs - Cole Gerdemann to present<br/><ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/526" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/526</a></li><li><a href="https://github.com/COVESA/vss-tools/pull/207" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/207</a></li></ul></li><li>VSS-Tools struct support<ul><li>Status update from Krishna</li><li>Align on merge model - small PRs require quick reviews.<ul><li>OK if merge if reviewed by at least one maintainer (Erik/Adnan/Sebastian)<ul><li>Meeting notes. Agreed</li></ul></li><li>Wait with merging non-related PRs? (To minimize rebase effort)<ul><li>Notes: Likely not need for struct work</li></ul></li></ul></li></ul></li><li>VSS file restructuring<br/><ul><li>Erik to present draft - see <a href="https://github.com/COVESA/vehicle_signal_specification/issues/527" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/527</a></li></ul></li><li>COVESA data expert group Workshop 2 halfdays, Feb 15th+16th, everyone free to participate, see COVESA calendar<ul><li>If interested join data Expert Group slack channel or mailing list.</li></ul></li></ul></li></ul><ul><li>Walk through Pull Requests and Issues VSS</li><li>Walk through Pull Requests and Issues VSS-Tools</li><li>Topics on hold</li><li>Older issues VSS & VSS-tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meeting2023-01-31">Meeting 2023-01-31</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li></ul><ul><li>Decision on old open PRs<ul><li>Overlay support for expanded instances - <a href="https://github.com/COVESA/vss-tools/pull/203" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/203</a></li><li>Mypy<ul><li><a href="https://github.com/COVESA/vss-tools/pull/210" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/210</a></li><li><a href="https://github.com/COVESA/vss-tools/pull/209" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/209</a> (if signoff added)</li><li><a href="https://github.com/COVESA/vss-tools/pull/212" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/212</a></li></ul></li><li>Cleanup - <a href="https://github.com/COVESA/vss-tools/pull/211" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/211</a></li></ul></li><li>Prioritized topics<ul><li>Connectivity PRs - Cole Gerdemann to present (postponed)<br/><ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/526" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/526</a></li><li><a href="https://github.com/COVESA/vss-tools/pull/207" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/207</a></li></ul></li><li>Discussion: Why using left/right instead of passenger/driver for example for door<ul><li>Adnan : Possibly to create a pull request</li></ul></li></ul></li></ul><ul><li>Walk through Pull Requests and Issues VSS</li><li>Walk through Pull Requests and Issues VSS-Tools</li><li>Topics on hold</li><li>Older issues VSS & VSS-tools</li><li>Prioritized topics for next meeting</li></ul><p><br/></p><h1 id="VSSMeetingTopicsandMeetingNotes-Meeting2023-01-24">Meeting 2023-01-24</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Old Pull Requests (where there is no "ongoing" discussion or recent changes - merge decision pending)<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/521" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/521</a></li><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/509" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/509</a></li><li><a href="https://github.com/COVESA/vss-tools/pull/204" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/204</a></li><li><a href="https://github.com/COVESA/vss-tools/pull/205" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/205</a></li><li><a href="https://github.com/COVESA/vss-tools/pull/206" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/206</a></li></ul></li><li>Struct Proposal</li></ul></li></ul><pre class="c-mrkdwn__pre">Work Package for Struct Proposal:
Details of the proposal in [PR 511](<a href="https://github.com/COVESA/vehicle_signal_specification/pull/511/" style="text-decoration: none;" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/511/</a>)
A. Minor release with experimental struct support
1. vss-tools can take in a types spec file and process sensor tree and the type tree together. struct/type support will be marked as an experimental feature.
a. Syntactic check of struct definition
b. Semantic check of type references in sensors
c. Demonstrate working using the JSON exporter
2. Add disclaimer/warning when customer is using experimental feature
3. Warning in exporters that structs are not yet supported
4. Warning in overlays that structs are not yet supported
5. Experimental feature documentation
Effort: 3 weeks
B. Exporters release
1. Add support for struct types in other text-based available exporters in vss-tools - CSV, YAML
Effort: 1 week
C. Major release
1. Overlay support
2. Documentation update
3. Add support for non-text exporters as needed - protobuf, DDSIDL, etc.
4. Add guidance around when and how to use struct types
Effort: 4 weeks</pre><p><br/></p><ul><li style="list-style-type: none;"><ul><li style="list-style-type: none;"><ul><li>Notes:<ul><li>Krishna can contribute to A, unsure about B and C</li><li>Target: End of February for minor release</li><li>Possible Target: Major release late April</li><li>Paul: AMM likely in Porto, Portugal, 25-27th April</li></ul></li></ul></li><li>Introduction of new issues/PRs (very short)<ul><li>Time units/datatypes - introduction <a href="https://github.com/COVESA/vehicle_signal_specification/issues/525" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/525</a></li><li>Power Optimize - Introduction of Bosch proposal <a href="https://github.com/COVESA/vehicle_signal_specification/pull/528" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/528</a><br/><ul><li>Potential replacement for <a href="https://github.com/COVESA/vehicle_signal_specification/pull/520" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/520</a></li></ul></li><li>Connectivity PR - Introduction as preparation for next week discussion<ul><li>Units: <a href="https://github.com/COVESA/vss-tools/pull/207" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/207</a></li><li>Signals: <a href="https://github.com/COVESA/vehicle_signal_specification/pull/526" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/526</a></li></ul></li><li>Cleanup - <a href="https://github.com/COVESA/vss-tools/pull/211" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/pull/211</a></li><li>Mypy (3 PRs)</li></ul></li></ul></li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Paul Boyes: COVESA Workshop planned for February 15th-16th (online, two halfdays, <span style="color: rgb(29,28,29);">5 - 9am PT</span><br style="text-align: left;"/><span style="color: rgb(29,28,29);">1400-1700 CET</span><br style="text-align: left;"/><span style="color: rgb(29,28,29);">6:30-10:30pm IST</span><br style="text-align: left;"/><span style="color: rgb(29,28,29);">10pm - 2am JST</span>)<ul><li>Action point: Paul will send out invite and ask for topics</li></ul></li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meeting2023-01-17">Meeting 2023-01-17</h1><p><em>If you have a topic you want to prioritize please add it here. We do however have the ambition to regularly discuss recent issues and pull requests, so no need to explicitly mentions a PR unless it needs to be prioritized:</em></p><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Neil Puthuff (RTI) presenting some initial observations as new to COVESA/VSS<ul><li>Reference: <a href="https://docs.google.com/document/d/1dHHMIlIZpsbnVsTiiza4Suua-vVbfR1xm11KNKdAm38/edit" class="external-link" rel="nofollow">https://docs.google.com/document/d/1dHHMIlIZpsbnVsTiiza4Suua-vVbfR1xm11KNKdAm38/edit</a> </li><li>Grouping of signals - is there a mechanism to group signals.</li><li>Best way forward - create issues for most important areas to describe problem and wanted solution and continue discussion</li></ul></li><li>Ford proposal - Fleet based range prediction<br/><ul><li>Christoph Schierjott presents <a href="https://wiki.covesa.global/display/WIK4/EV+Charging+Event+Data+Aggregation+Project">EV Charging Event Data Aggregation Project</a></li><li>Data upload of various data to cloud</li><li>Cloud calculates correction factor individually and sends down to vehicle to correct fleet range prediction</li></ul></li><li>Power Optimize<ul><li><a href="https://github.com/COVESA/vehicle_signal_specification/pull/520#issuecomment-1385456662" class="external-link" rel="nofollow">Mobis Architecture</a><ul><li>Intention is to have a power manager that will select scheme, either based on user request or for example based on that remaining power drops below 20%</li></ul></li><li>Pre-information Bosch proposal<ul><li>Erik: Bosch has some ideas on representation that will be presented in the Power Optimize meeting this week</li></ul></li></ul></li></ul></li><li>Open Pull Requests VSS<ul><li>Closed: <a href="https://github.com/COVESA/vehicle_signal_specification/pull/523" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/523</a></li></ul></li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meeting2023-01-10">Meeting 2023-01-10</h1><p><em>If you have a topic you want to prioritize please add it here. We do however have the ambition to regularly discuss recent issues and pull requests, so no need to explicitly mentions a PR unless it needs to be prioritized:</em></p><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>None</li></ul></li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Information from Paul<ul><li>Big interest at CES</li><li>We need to have a bigger discussion late January or February to how to simplify use of VSS.</li><li>Paul to discuss with Data Expert Group (Erik, Adnan) on how to proceed.</li></ul></li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meeting2022-12-20">Meeting 2022-12-20</h1><p><em><br/></em></p><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Aggregate vs. structs - when do we see it need to be kept<ul><li>From last week - Ulf/Erik: In favor of deprecating/removing aggregate keyword</li><li>Since then: Ulf requested a credible example, Erik stated that if we are to keep it we should better propose/specify how tools shall handle it</li><li>Adnan: Allow aggregate on deployment level, can use it when needed. For now good to only have it as information.</li><li>Krishna: Thinks aggregate makes changes, struct does not affect it. If we want to depricate we can do it later</li><li>Ulf: Does not have a strong opinion</li><li>Adnan: Good to document when structs vs aggregate shall be used</li><li>Erik: Can update the PR</li><li>Erik: Do you Krishna have interest in doing actual work.</li><li>Krishna: In January will start working on it, can help Erik</li><li>Erik; Then we can discuss later when we think it will be ready for VSS 4.0 release</li></ul></li><li>Information: <a href="https://github.com/COVESA/vss-tools/issues/201" class="external-link" rel="nofollow">Overlays after expansion</a><ul><li>Internal Bosch discussion if it would be better to refactor tooling so that only one parameter needed and tool is "smart enough" to deduce if given path refers to extended entity or not.</li></ul></li><li>Discussion: <a href="https://github.com/COVESA/vehicle_signal_specification/pull/520" class="external-link" rel="nofollow">PowerOptimize PR</a><ul><li>Chandra: Intention to have one branch in each area, for infotainment we see brightness and audio volume</li><li>Chandra: Does not intend to duplicate, only want one signal, need only one</li><li>Erik: Isn't PowerOptimize only one of many use-cases for e.g. brightness, why need a PowerOptimize branch</li><li>Chandra: If scattered more difficult to find</li><li>Sebastian: OEM needs to decide what is part of his power optimization, do not understand the value of having them in separate branch</li><li>Adnan: What is difference</li><li>Pradeep: Adding a feature set, complete algorithm,</li><li>Adnan: If you are only proposing values, then it makes sense</li><li>Sebastian: Alternative usages could be e.g. overlay</li><li>Chandra: When we explain we see some signals are duplicated</li><li>Adnan: Best solution would if you prepare and show architecture on how it is intended</li><li>Adnan: Have not seen scope. Like to learn how</li><li>Pradeep: Do you have any public link describing how it is supposed to work.</li><li>Adnan: if you create some simple document you can attach it, then we can try to find best way</li></ul></li><li>UUID elements<ul><li>Adnan: Is anyone using UUIDs at the moment</li><li>Sebastian: We have never used them</li><li>Adnan: We saw a potential of UUID, could help versioning. We could UUID hash to validate. Has anyone any ideas. Otherwise we might create improvement proposal.</li><li>Sebastian: UUID are as of today generated based on tree structure.</li><li>Adnan: We need more, e.g. history. How do we move leave but keep UUID.</li><li>Sebastian: Could be a hash of only name/description/....</li><li>Erik: Please Adnan create an issue and ask if someone use UUIDs - if not you are free to do anything.</li></ul></li></ul></li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting<ul><li><strong>Note: Dec 27th cancelled</strong></li><li>Meeting as usual Jan 3rd</li></ul></li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-AgendaforMeeting2022-12-13">Agenda for Meeting 2022-12-13</h1><p><em><br/></em></p><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Aggregate vs. structs - when do we see it need to be kept<ul><li>Ulf/Erik: In favor of deprecating/removing aggregate keyword</li><li>Erik: Seems proposal is quite stable, lets wait discussing work packages until Jrishna is back, as he seemed interested in implementing in vss-tools</li></ul></li><li>Summary for vote of Allowed (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/502" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/502</a>)<ul><li>vote result: allow int and float for now</li></ul></li><li>Meeting cancellations due to new year<ul><li>Availability of participants Dec 20th?</li><li>Suggest cancelling Dec 27th?</li><li>Availability of participants Jan 3rd? (Erik unavailable)</li><li>Decision: Cancel Dec 27th, wait with decision on Dec 20th and Jan 3rd</li><li>Availability: (Paul: all, Ted: all, Umang: all, Ulf: all)</li><li>Erik to check with Adnan (and Krishna)</li></ul></li><li>Open Pull Requests (vss+tools, except struct) - approve/object before next week.<ul><li>See PRs</li></ul></li><li>Information: New <a href="https://github.com/COVESA/vehicle_signal_specification/issues/516" class="external-link" rel="nofollow">issue</a> for proposal from last week</li><li>Information: <a href="https://github.com/COVESA/vss-tools/issues/201" class="external-link" rel="nofollow">Overlays after expansion</a></li></ul></li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><h1 id="VSSMeetingTopicsandMeetingNotes-Meeting2022-12-06">Meeting 2022-12-06</h1><p><em><br/></em></p><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Continued struct decision, focus on recommendations/limitations, why we need it, rationale (<a href="https://github.com/COVESA/vehicle_signal_specification/pull/511" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/511</a>)<ul><li>Meeting notes:<ul><li>Krishna - for types - there could be subtrees working as namespace. Erik to improve description.</li><li>Adnan - we need to come up with how to use "Aggregate"</li><li>Krishna - could be useful for aggregating</li><li>Adnan - we need to explain advantage of aggregate vs struct</li><li>Erik to create proposal in document</li><li>If no further comments, next step is to identify work packages in detail and do estimation for roadmap</li></ul></li></ul></li><li>Ulf <a href="https://docs.google.com/presentation/d/1PHijKSHKbP2ZjmWJ4qm4GKuGID5B0TNn/edit?usp=share_link&ouid=102950097033494215951&rtpof=true&sd=true" class="external-link" rel="nofollow">presented some roadmap ideas</a> (15-20 minutes)<ul><li>Proposals:<ul><li>Reason - to get a domain agnostic taxanomy</li><li>Move "rule set" to new specification project, VSS keeps the catalog.</li></ul></li><li>Sebastian: Could be an idea to scope it to "mobility only"</li><li>Erik: Could at least be idea to have a vision/mission for the "rule set" to primarily support mobility use cases</li><li>Daniel: Integrating/reference domains in Yaml does not make sense, Ontology is a better choice. This is the next step of VSSo.</li><li>How to proceed:<ul><li>Document to be uploaded</li><li>Discussion to be continued at some later time (not urgent)</li><li>Interesting topic for next AMM, including VSS ↔ VSSo relationship</li></ul></li></ul></li><li>Summary for vote of Allowed (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/502" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/502</a>)<ul><li>Wait until next week</li></ul></li><li>PR/Change governance (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/515" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/515</a>)</li><li><s>Overlays on expanded tree (<a href="https://github.com/COVESA/vss-tools/issues/201" class="external-link" rel="nofollow">https://github.com/COVESA/vss-tools/issues/201</a>)</s></li><li><s>Release Cadence/Roadmap (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/513" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/513</a>)</s></li></ul></li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><p><br/></p><h1 id="VSSMeetingTopicsandMeetingNotes-Meeting2022-11-29">Meeting 2022-11-29</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics<ul><li>Struct Proposal (<a href="https://github.com/COVESA/vehicle_signal_specification/pull/511" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/pull/511</a>)<ul><li>See PR, agreed to change proposal to have struct definitions in separate file. Erik to update proposal</li></ul></li><li>Release Cadence (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/513" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/513</a>)<ul><li>Skipped due to lack of time</li></ul></li><li>Roadmap (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/508" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/508</a>)<ul><li>Skipped due to lack of time</li></ul></li><li>Support for "allowed" (<a href="https://github.com/COVESA/vehicle_signal_specification/issues/502" class="external-link" rel="nofollow">https://github.com/COVESA/vehicle_signal_specification/issues/502</a>)<ul><li>Voting next week</li></ul></li><li>PR/Change governance<ul><li>Skipped due to lack of time</li></ul></li></ul></li><li>Open Pull Requests VSS<ul><li>Skipped due to lack of time</li></ul></li><li>Open Pull Requests VSS-Tools<ul><li>Skipped due to lack of time</li></ul></li><li>Issues VSS<ul><li>Skipped due to lack of time</li></ul></li><li>Issues VSS-Tools<ul><li>Skipped due to lack of time</li></ul></li><li>Prioritized topics for next meeting<ol><li>Continued struct decision, focus on recommendations/limitations, why we need it, rationale</li><li>Ulf to present some roadmap ideas (15-20 minuets)</li><li>Summary for vote of Allowed</li><li>Release cadence/Roadmap</li></ol></li></ul><p><br/></p><h1 id="VSSMeetingTopicsandMeetingNotes-AgendaTemplate">Agenda Template</h1><ul><li>Compliance statement - TBD</li><li>Welcome and agenda discussion - anything that needs to be added?</li><li>Prioritized topics</li><li>Decision on old open PRs</li><li>Open Pull Requests VSS</li><li>Open Pull Requests VSS-Tools</li><li>Issues VSS</li><li>Issues VSS-Tools</li><li>Prioritized topics for next meeting</li></ul><p><br/></p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/display/WIK4/VSS+Meeting+Topics+and+Meeting+Notes">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=48529442&revisedVersion=132&originalVersion=131">View Changes Online</a>
</div>
</div>Erik Jaegervall2022-11-24T08:56:36ZVSS Resources at a GlancePaul Boyestag:wiki.covesa.global,2009:page-34209833-662024-03-22T18:33:12Z2022-08-16T23:11:32Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~pboyes@covesa.global
">Paul Boyes</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>f<span class="confluence-embedded-file-wrapper image-right-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image image-right" draggable="false" height="150" src="https://wiki.covesa.global/download/attachments/34209833/vss-logo.png?version=1&modificationDate=1660723645303&api=v2" data-image-src="https://wiki.covesa.global/download/attachments/34209833/vss-logo.png?version=1&modificationDate=1660723645303&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="34209854" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="vss-logo.png" data-base-url="https://wiki.covesa.global" data-linked-resource-content-type="image/png" data-linked-resource-container-id="34209833" data-linked-resource-container-version="66" alt=""></span></p><p style="text-align: left;">This page is an aggregation of links to various Vehicle Signal Specifications resources. It is intended to provide a quick reference access to everything VSS. If you do not find what you are looking for or see things that are missing, please let <a href="mailto:paul.boyes@covesa.global" class="external-link" rel="nofollow">us</a> know.</p><p style="text-align: left;"><br/></p><p style="text-align: left;"><span style="color: rgb(255,0,0);"><strong>***If you want to dive right into the <a href="https://github.com/COVESA/vehicle_signal_specification" class="external-link" rel="nofollow">spec</a> or <a href="https://covesa.github.io/vehicle_signal_specification/" class="external-link" rel="nofollow">documentation</a> go to <a href="https://github.com/COVESA/vehicle_signal_specification" class="external-link" rel="nofollow">GitHub</a>***</strong></span></p><h2 style="text-align: left;" id="VSSResourcesataGlance-TableofContents">Table of Contents</h2><p style="text-align: left;"><u><strong><style type='text/css'>/*<![CDATA[*/
div.rbtoc1711644959705 {padding: 0px;}
div.rbtoc1711644959705 ul {list-style: circle !important;margin-left: 0px;}
div.rbtoc1711644959705 li {margin-left: 0px;padding-left: 0px;}
/*]]>*/</style><div class='toc-macro rbtoc1711644959705'>
<ul class='toc-indentation'>
<li><a href='#VSSResourcesataGlance-TableofContents'>Table of Contents</a></li>
<li><a href='#VSSResourcesataGlance-COVESAVSSWiki'>COVESA VSS Wiki</a></li>
<li><a href='#VSSResourcesataGlance-CalendarandCollaborationChannels(mailinglistsandSlack)'>Calendar and Collaboration Channels (mailing lists and Slack)</a></li>
<li><a href='#VSSResourcesataGlance-GitHub'>GitHub</a></li>
<li><a href='#VSSResourcesataGlance-PresentationsandDecks'>Presentations and Decks</a></li>
<li><a href='#VSSResourcesataGlance-HowandwhereVSSisused?'>How and where VSS is used?</a>
<ul class='toc-indentation'>
<li><a href='#VSSResourcesataGlance-OEMAdoption'>OEM Adoption</a></li>
<li><a href='#VSSResourcesataGlance-OpenSourceImplementations'>Open Source Implementations</a></li>
<li><a href='#VSSResourcesataGlance-SpotlightSeries'>Spotlight Series</a></li>
</ul>
</li>
<li><a href='#VSSResourcesataGlance-JointProjectswithW3C'>Joint Projects with W3C</a></li>
</ul>
</div></strong></u></p><h2 style="text-align: left;" id="VSSResourcesataGlance-COVESAVSSWiki"><u><strong>COVESA VSS Wiki</strong></u></h2><p>The VSS page on this wiki is a good starting point that leads/points to all of the other locations. </p><ul><li><span><a href="https://www.covesa.global/sites/default/files/COVESA%20Vehicle%20Signal%20Specification%20-%20Enabling%20Ecosystems_20240105.pdf" class="external-link" rel="nofollow">VSS Overview</a> - High level overview of VSS</span></li><li><span><a href="https://wiki.covesa.global/display/WIK4/Introduction+to+Vehicle+Signal+Specification" rel="nofollow">Introduction to VSS Sessions</a> - Every Quarter, starting Q1 2023, there is an Intro to VSS. Presentation and recording of the session are available.</span></li><li><span><a href="https://wiki.covesa.global/display/WIK4/VSS+-+Vehicle+Signal+Specification#VSSVehicleSignalSpecification-UnderstandingVSS" rel="nofollow">Understanding VSS</a> - Presentations and decks starting with an introduction to those unfamiliar with VSS followed by some deeper dives into VSS and related VSS Ontology</span></li><li><span><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=12124193">Vehicle Data Models - Overview and Gap Analysis</a> - Survey of vehicle data models</span></li><li><span>Weekly Meetings - See the <a href="https://wiki.covesa.global/display/WIK4/COVESA+Common+Meeting+Schedule" rel="nofollow">Community Calendar</a></span></li><li><span><a href="https://wiki.covesa.global/display/WIK4/VSS+Meeting+Topics+and+Meeting+Notes" rel="nofollow">Weekly meeting: Agenda and Notes</a></span></li></ul><p><br/></p><h2 id="VSSResourcesataGlance-CalendarandCollaborationChannels(mailinglistsandSlack)"><u><strong>Calendar and Collaboration Channels (mailing lists and Slack)</strong></u></h2><ul><li><a href="https://wiki.covesa.global/display/WIK4/COVESA+Common+Meeting+Schedule" rel="nofollow">COVESA Community Calendar</a></li><li><a href="https://wiki.covesa.global/display/WIK4/COVESA+Communication+Channels+and+Calendars">COVESA Communication Channels</a></li></ul><p><br/></p><h2 id="VSSResourcesataGlance-GitHub"><u><strong>GitHub</strong></u></h2><p>GitHub is where almost all of the VSS project work is maintained. The<a href="https://github.com/COVESA/vehicle_signal_specification" class="external-link" rel="nofollow"> main page</a> contains links to </p><ul style="text-decoration: none;"><li><p><a href="https://covesa.github.io/vehicle_signal_specification/" class="external-link" rel="nofollow">Documentation</a></p></li><ul><li><p>A straight forward set of topics that give a good overview of VSS</p></li></ul><li><p><a href="https://github.com/COVESA/vehicle_signal_specification/releases/" class="external-link" rel="nofollow">Releases</a></p></li><ul><li><p>Release links with lists of what has changed</p></li></ul><li><p><a href="https://github.com/COVESA/vehicle_signal_specification/tree/master/spec" class="external-link" rel="nofollow">Specificatio</a>n/Catalog</p></li><ul><li><p>VSS specification refers to the standard catalog. It is maintained in yaml. It is fully expected that not everyone will implement all data elements/signals and they will likely implement some number of proprietary elements/signals. VSS is still a useful methodology/rule set for defining interoperable models.</p></li></ul><li><p><a href="https://github.com/covesa/vss-tools/tree/a869c2b737e2b440ddd9609f692dff0cda57bfa6" class="external-link" rel="nofollow">Tools</a></p></li><ul><li><p>Tools are maintained in a separate repository</p></li></ul><li><p><a href="https://github.com/COVESA/vehicle_signal_specification/wiki" class="external-link" rel="nofollow">GitHub Project wiki</a></p></li><ul><li><p>VSS project team uses the <a href="https://github.com/COVESA/vehicle_signal_specification/wiki" class="external-link" rel="nofollow">VSS wik</a>i for documenting a variety of things including releases.</p></li></ul><li><p><a href="https://github.com/COVESA/vehicle_signal_specification/pulls" class="external-link" rel="nofollow">Pull Requests </a></p></li><ul><li><p>All edits and updates are presented to the team through Pull Requests and are discussed in weekly meetings.</p></li></ul><li><p><a href="https://github.com/COVESA/vehicle_signal_specification/issues" class="external-link" rel="nofollow">Issues</a></p></li><ul><li><p>All <a href="https://github.com/COVESA/vehicle_signal_specification/issues" class="external-link" rel="nofollow">issues</a> are tracked through GitHub issues</p></li></ul></ul><h2 id="VSSResourcesataGlance-PresentationsandDecks"><u><strong>Presentations and Decks</strong></u></h2><ul><li class="title style-scope ytd-video-primary-info-renderer" style="text-decoration: none;">Introduction to Vehicle Signal Specification at COVESA AMM October 2022 (<a href="https://wiki.covesa.global/download/attachments/32079873/Day_1_AB_230%20COVESA%20Intro%20to%20VSS_AMM202204%20Final.pptx?version=1&modificationDate=1666624078429&api=v2" rel="nofollow">deck</a>)</li><li class="title style-scope ytd-video-primary-info-renderer" style="text-decoration: none;">Introduction to Vehicle Signal Specification (<a href="https://www.youtube.com/watch?v=UOtOOsbg5Vg" class="external-link" rel="nofollow">presentation</a>) at COVESA AMM April 2022 (<a href="https://wiki.covesa.global/download/attachments/16614221/COVESA%20Intro%20to%20VSS_AMM2022%20Final%206.pptx?version=1&modificationDate=1655845714187&api=v2" data-linked-resource-id="27099356" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="COVESA Intro to VSS_AMM2022 Final 6.pptx" data-nice-type="PowerPoint Presentation" data-linked-resource-content-type="application/vnd.openxmlformats-officedocument.presentationml.presentation" data-linked-resource-container-id="16614221" data-linked-resource-container-version="35">deck</a>)</li><li class="title style-scope ytd-video-primary-info-renderer" style="text-decoration: none;">VSS and VSS Ontology (<a href="https://www.youtube.com/watch?v=heaL5lf9Nv0" class="external-link" rel="nofollow">presentation</a>) at at COVESA AMM Spring 2022 (<a href="https://wiki.covesa.global/download/attachments/16614221/2022_04_26_amm_vss_intro.drawio.pdf?version=1&modificationDate=1656025102032&api=v2" data-linked-resource-id="27099404" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="2022_04_26_amm_vss_intro.drawio.pdf" data-nice-type="PDF Document" data-linked-resource-content-type="application/pdf" data-linked-resource-container-id="16614221" data-linked-resource-container-version="35">deck</a>)</li></ul><h2 id="VSSResourcesataGlance-HowandwhereVSSisused?"><u><strong>How and where VSS is used?</strong></u></h2><p>There are various implementations where VSS is used as data model for vehicle data. </p><h3 id="VSSResourcesataGlance-OEMAdoption">OEM Adoption</h3><ul><li>BMW<ul><li><span style="color: rgb(37,37,37);">Mapped proprietary descriptions of vehicle data to VSS, for millions of cars.<br/></span></li><li><span style="color: rgb(37,37,37);">Employing GraphQL to create a backend single access layer for querying data coming from various storage and streaming systems. Demonstrated backend application based on this solution. While for data streaming use cases, other technologies that are supporting VSS might be in place.</span></li></ul></li><li><span style="color: rgb(37,37,37);">Volvo</span><ul><li><span style="color: rgb(37,37,37);">VISS implementation, exposing VSS within the vehicle</span></li><li><a href="https://wiki.covesa.global/download/attachments/34209833/SignalSetMatching.pdf?version=1&modificationDate=1665513470183&api=v2" data-linked-resource-id="41353227" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="SignalSetMatching.pdf" data-nice-type="PDF Document" data-linked-resource-content-type="application/pdf" data-linked-resource-container-id="34209833" data-linked-resource-container-version="66">Ideas for Vehicle Signal Set Matching</a></li><li><a href="https://wiki.covesa.global/download/attachments/34209833/Dynamic%20weight%20generation%20for%20vehicle%20signal%20set%20matching.pdf?version=1&modificationDate=1688336707262&api=v2" data-linked-resource-id="71074130" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Dynamic weight generation for vehicle signal set matching.pdf" data-nice-type="PDF Document" data-linked-resource-content-type="application/pdf" data-linked-resource-container-id="34209833" data-linked-resource-container-version="66">Dynamic weight generation for vehicle signal set matching.pdf</a></li></ul></li><li><span style="color: rgb(37,37,37);">Ford </span><ul><li><span style="color: rgb(37,37,37);"><a href="https://wiki.covesa.global/display/WIK4/EV+Charging+Event+Data+Aggregation+Project" rel="nofollow">EV Charging Event Data Aggregation</a> project led by Ford is actively updating the VSS model for EV Charging </span></li><li><span style="color: rgb(37,37,37);">Internally working with VSS as a starting point for a variety of data related and development projects</span></li></ul></li><li><span style="color: rgb(37,37,37);">Mercedes </span><ul><li><span style="color: rgb(37,37,37);">Internally working with VSS as a starting point for a variety of data related and development projects</span></li></ul></li></ul><h3 id="VSSResourcesataGlance-OpenSourceImplementations">Open Source Implementations</h3><ul class="MailOutline"><li><a href="https://www.digitalplaybook.org/index.php?title=Overview:_playground.digital.auto" class="external-link" rel="nofollow">playground.digital.auto</a> - <span style="color: rgb(34,34,34);">playground for ideation and collaboration between digital.auto participants using VSS and python.</span> </li><li><a href="https://aoscloud.io" class="external-link" rel="nofollow">Aos Edge</a> - A software first approach to the connected vehicle.<ul class="MailOutline"><li>Provides a protected VSS data server that uses the VISS protocol, VISS client library and a 'getting started' example using VSS as the data model.</li><li><a href="https://github.com/aoscloud" class="external-link" rel="nofollow">Source repositories</a></li></ul></li><li><a href="https://www.eclipse.org/kuksa/" class="external-link" rel="nofollow">Eclipse Kuksa</a> - Building blocks for the Software Defined Vehicle<ul><li><a href="https://www.eclipse.org/kuksa/resources/" class="external-link" rel="nofollow">Repositories and other Resources</a></li></ul></li><li><a href="https://aws.amazon.com/iot-fleetwise/" class="external-link" rel="nofollow">AWS IoT Fleetwise</a> - Fleet Management software<ul><li><a href="https://github.com/aws/aws-iot-fleetwise-edge" class="external-link" rel="nofollow">Repositories</a></li></ul></li><li><a href="https://github.com/w3c/automotive-viss2" class="external-link" rel="nofollow">W3C Vehicle Information Service Specification</a> - data service for serving VSS data on multiple topologies</li></ul><h3 id="VSSResourcesataGlance-SpotlightSeries">Spotlight Series</h3><p style="text-align: left;"><a href="https://wiki.covesa.global/display/WIK4/COVESA+Spotlight+Sessions" rel="nofollow">COVESA<span> </span><span class="il">Spotlight</span></a><span> </span>is a series where member organizations from the COVESA Community present their use/implementation of COVESA's<a href="https://global.us18.list-manage.com/track/click?u=4c5fada0aa3f5d36000173e2e&id=7e7824d9df&e=a4643ed831" style="text-decoration: underline;" class="external-link" rel="nofollow"><span> </span>Vehicle Signal Specification</a> answering the following questions:</p><ul style="text-align: left;"><li>Why VSS was used? / The value of using VSS?</li><li>How VSS was used?</li><li>What could be improved in VSS?</li></ul><p>You can find the past presentations from the series <a href="https://wiki.covesa.global/display/WIK4/COVESA+Spotlight+Sessions" rel="nofollow">here</a>. If you are interested in presenting your VSS implementation, please contact the <a href="mailto://paul.boyes@covesa.global" class="external-link" rel="nofollow">Community Director</a>.</p><p><br/></p><p><br/></p><h2 id="VSSResourcesataGlance-JointProjectswithW3C"><strong>Joint Projects with W3C</strong></h2><p style="margin-left: 40.0px;">Covesa has joint projects to develop and standardize certain technology through the W3C process.</p><ul><li style="list-style-type: none;"><ul><li>Vehicle Information Service Specification (VISS) <ul><li><a href="https://www.w3.org/TR/viss2-core/" class="external-link" rel="nofollow">VISS Core</a></li><li><a href="https://www.w3.org/TR/viss2-transport/" class="external-link" rel="nofollow">VISS Transport</a></li></ul></li><li>Vehicle Signal Specification Ontology<ul><li><a href="https://www.w3.org/groups/wg/auto/publications#card-9358" class="external-link" rel="nofollow">VSSo Core</a></li><li><a href="https://www.w3.org/groups/wg/auto/publications#card-9357" class="external-link" rel="nofollow">VSSo</a></li></ul></li></ul></li></ul><p><br/></p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/display/WIK4/VSS+Resources+at+a+Glance">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=34209833&revisedVersion=66&originalVersion=65">View Changes Online</a>
</div>
</div>Paul Boyes2022-08-16T23:11:32ZIn Vehicle Payments Birds of a FeatherJens Kohnentag:wiki.covesa.global,2009:page-85196956-152024-03-22T14:14:41Z2023-11-17T20:26:07Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.covesa.global/display/~jens@starfish.team
">Jens Kohnen</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<h2 id="InVehiclePaymentsBirdsofaFeather-/*<![CDATA[*/div.rbtoc1711644959738{padding:0px;}div.rbtoc1711644959738ul{margin-left:0px;}div.rbtoc1711644959738li{margin-left:0px;padding-left:0px;}/*]]>*/#InVehiclePaymentsBirdsofaFeather-General#InVehiclePaymentsBirdso"><strong><em><style type='text/css'>/*<![CDATA[*/
div.rbtoc1711644959738 {padding: 0px;}
div.rbtoc1711644959738 ul {margin-left: 0px;}
div.rbtoc1711644959738 li {margin-left: 0px;padding-left: 0px;}
/*]]>*/</style><div class='toc-macro rbtoc1711644959738'>
<ul class='toc-indentation'>
<li><a href='#InVehiclePaymentsBirdsofaFeather-'></a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-General'>General</a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-Charter'>Charter</a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-WalletProjectCharter'>Wallet Project Charter</a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-Agenda&MeetingNotes'>Agenda & Meeting Notes</a>
<ul class='toc-indentation'>
<li><a href='#InVehiclePaymentsBirdsofaFeather-21stofMarch2024'>21st of March 2024</a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-15thofFebruary2024'>15th of February 2024</a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-18thofJanuary2024'>18th of January 2024</a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-14thofDecember2023'>14th of December 2023</a></li>
<li><a href='#InVehiclePaymentsBirdsofaFeather-16thofNovemeber2023'>16th of Novemeber 2023</a></li>
</ul>
</li>
</ul>
</div></em></strong></h2><p><strong><em><a href="https://wiki.covesa.global/pages/viewpage.action?pageId=12124760">Previous Work Done by the IVP SIG</a></em></strong></p><h2 id="InVehiclePaymentsBirdsofaFeather-General"><strong><em>General</em></strong></h2><p><strong><em>Welcome to the COVESA In Vehicle Payments Birds of a Feather!</em></strong></p><p><strong>Monthly Meeting: </strong>Third Thursday of every Month, 9-10am PT, 12-1pm ET, 6-7pm CET (<a href="https://us06web.zoom.us/j/89753620936?pwd=MVqy1wA3yCEnw5ETLwYnGf4RPq3XSY.1" class="external-link" rel="nofollow">Zoom Link</a>) (<a href="https://wiki.covesa.global/display/WIK4/COVESA+Common+Meeting+Schedule" rel="nofollow">Subscribe to Community Calendar</a><span> </span>to stay up to date)</p><p><strong>Slack:</strong><span> <a href="https://join.slack.com/t/covesacommunity/shared_invite/zt-27b4ddgr6-w26SFVX4~Q7dFR7ZmplcWA" class="external-link" rel="nofollow">Join COVESA Community Slack Workspace</a> (</span><a href="https://covesacommunity.slack.com" class="external-link" rel="nofollow">https://covesacommunity.slack.com</a>) - Channel:<a href="https://covesacommunity.slack.com/archives/C062FSND1GU" class="external-link" rel="nofollow"> in-vehicle-payments</a></p><h2 id="InVehiclePaymentsBirdsofaFeather-Charter"><strong>Charter</strong></h2><p><a href="https://docs.google.com/document/d/16j9lX5ymx8oVso1GDIqoUdnFU8IxGq2533r6CZHG2YM/edit?usp=sharing" class="external-link" rel="nofollow">Doc</a></p><h2 id="InVehiclePaymentsBirdsofaFeather-WalletProjectCharter"><strong>Wallet Project Charter</strong></h2><p><a href="https://docs.google.com/document/d/1cCD5Dmeu-P1P4yV2BH6AQqs94BaSuuqeJ0BeBixmyk4/edit?usp=sharing" class="external-link" rel="nofollow">Doc</a></p><p><br/></p><p><em><strong><span style="color: rgb(29,28,29);">Antitrust</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">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.</span></em></p><p><br/></p><p><em><strong><span style="color: rgb(29,28,29);">Open and Royalty-Free</span></strong></em><br style="text-align: left;"/><em><span style="color: rgb(29,28,29);">Further, COVESA aspires<span style="color: rgb(0,0,0);"><span> </span>to be an</span><span> </span>open and royalty-free organization. The discussions and contributions made during this session are governed by the<span> </span><a href="https://www.covesa.global/sites/default/files/COVESA%20IPR%20Policy%20Amended%2013Oct2021%20final.pdf" class="external-link" rel="nofollow">COVESA Intellectual Property policy</a>. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.</span></em></p><h2 id="InVehiclePaymentsBirdsofaFeather-Agenda&MeetingNotes"><strong>Agenda & Meeting Notes</strong></h2><h3 id="InVehiclePaymentsBirdsofaFeather-21stofMarch2024"><strong>21st of March 2024</strong></h3><ul><li>Welcome and introductions<ul><li>List of participants<ul><li>Jens Kohnen (<a href="https://hellgate.io" class="external-link" rel="nofollow">Starfish</a>)</li><li>Vamsi Putrevu (<a href="http://Mavi.io" class="external-link" rel="nofollow">Mavi.io</a>)</li><li>Paul Boyes (COVESA)</li><li>Maria Trudgeon (GM)</li><li>Richard Fernandes (GM)</li><li>Nick Telford-Reed (Endava)</li><li>Jose Freitas (Faurecia Aptoide)</li><li>Rachel Dismuke (Abalta)</li><li>Jim Greene (Next Wave Advisors)</li><li>Dan Dinges (NN)</li><li>Robert Bronninger (BMW)</li></ul></li><li>Brief introduction of members, their role, and organization they represent.</li></ul></li><li><a href="https://www.eventleaf.com/e/AMMGothenburg2024#ss" class="external-link" rel="nofollow">All Member Meeting</a> in April<ul><li>Discussion of topics for the thought leadership session on April 18th 2pm<ul><li>Payment Authentication in car</li><li>Document and understand regulations from different regions</li><li>In-Vehicle commerce - Payment via phone vs car</li><li>Payment credentials on device vs on cloud</li><li>Alternative Payment Methods / Non card payments</li><li>Business models of In-Car Payments Payments</li></ul></li><li>Current panelist are joining from<ul><li>Starfish</li><li>Mavi.io</li><li>Endava</li><li>Aptiv</li><li>Further panelists and thought leaders are highly welcome - please reach out to <a href="https://www.linkedin.com/in/jenskohnen/" class="external-link" rel="nofollow">Jens Kohnen</a> (jens@starfish.team)</li></ul></li><li>The working session of the IVP group will be held on April 18th 3:15pm</li></ul></li><li>Next steps<ul><li>During the AMM the problem statements for the working group will be aligned and started to be worked on</li></ul></li><li>Next events<ul><li>COVESA All Member Meeting<br/>April 16-18, 2024<br/>Gothenburg, Sweden</li><li>Next IVP Call<br/>16.05.2024</li></ul></li></ul><h3 id="InVehiclePaymentsBirdsofaFeather-15thofFebruary2024"><strong>15th of February 2024</strong></h3><ul><li>Welcome and Introductions<ul><li>List of participants<ul><li>Jens Kohnen (<a href="https://starfish.team" class="external-link" rel="nofollow">Starfish</a>)</li><li>Vamsi Putrevu (<a href="http://Mavi.io" class="external-link" rel="nofollow">Mavi.io</a>)</li><li>Paul Boyes (COVESA)</li><li>Mike Nunnery (COVESA)</li><li>Maria Trudgeon (GM)</li><li>Richard Fernandes (GM)</li><li>Sri Palacharla (GM)</li><li>Nick Telford-Reed (Endava)</li><li>Paula Silverthorn (Endava)</li><li>Jose Freitas (Faurecia Aptoide)</li><li>Rachel Dismuke (Abalta)</li><li>Slavyan Nakev (QaiWare)</li></ul></li><li>Brief introduction of each member, their role, and organization they represent.</li><li>Objectives and expectations towards the IVP group</li></ul></li><li><p>Recap and discussion on problem statements to be tackled within this group</p><ul><li><p>Proposal 1: Standard for OEM and Third-Party Integration<br/>(as combination of the first 2 we discussed last time):</p><ul><li><p>Problem Statement:<br/>Automotive Original Equipment Manufacturers (OEMs) encounter significant challenges in incorporating third-party service providers into their in-car entertainment ecosystems, compounded by the lack of a standardized approach for the integration of payment, billing, invoicing, and master data exchange processes. This complexity is further exacerbated when attempting to create a uniform API interface that allows third-party applications to conduct transactions for various use cases such as parking, charging, and purchasing food directly from the vehicle's interface. The absence of an industry-wide standard leads to each OEM and third-party provider independently tackling these issues, resulting in inefficiencies and a disjointed user experience.</p></li><li><p>Solution Proposal:<br/>The proposed initiative aims to tackle the dual challenges faced by OEMs and third-party service providers by establishing a common industry standard that not only streamlines the integration of services into in-car entertainment systems but also defines a standard API interface for third-party apps. This standard will facilitate seamless payment, billing, invoicing, and master data exchange, alongside ensuring technical integration is both efficient and scalable. By doing so, it will enable a consistent and user-friendly interface for in-car transactions across various services and applications, enhancing the overall digital experience within vehicles.</p></li><li><p>Potential Action Items:<br/>Convene a working group consisting of representatives from automotive OEMs, third-party service providers, app developers, and tier 1 suppliers to collaboratively define the scope and specifications of the proposed industry standard.<br/>Develop a comprehensive framework for the standardization of payment, billing, invoicing, and master data exchange processes, including technical integration guidelines.<br/>Define a uniform API interface that can be implemented by OEMs and/or app stores, ensuring compatibility and ease of integration for third-party applications.</p></li></ul></li><li><p>Proposal 2: In-Car Wallet Interface for Apps:</p><ul><li><p>Problem statement:<br/>OEMs face a challenge in standardizing an API interface that 3rd party apps can access to conduct payments usecases such as parking, charging, buying food etc.</p></li><li><p>Solution Proposal:<br/>Define a standard interface (APIs) that will be implemented by the OEM and/or app stores and tier 1s</p></li></ul></li><li><p>Proposal 3: Relevant payment methods</p><ul><li><p>Problem statement: <br/>Validate if other payment methods than credit cars play a relevant role to be implemented as method for in-car payment</p></li></ul></li><li><p>Proposal 4: OTA</p><ul><li><p>Problem statement: <br/>OEM face the issue that updates / replacements of rolled-out applications in vehicles is a problem. Typically not all relevant vehicles are updated and OTA.</p></li><li><p>Solution proposal: Define a consensus on huch much payment credential is stored in the vehicle vs. the cloud with all the implication to security, authentication, etc. .</p></li></ul></li></ul></li><li>Next steps<ul><li>Group members to reflect on the problem statement the IVP group is aiming to work on</li><li>During next IVP call, the topic shall be defined and the agenda for the group workshop during the AMM working session shall be defined</li></ul></li><li>Next events<ul><li>COVESA All Member Meeting<br/>April 16-18, 2024<br/>Gothenburg, Sweden</li><li>Next IVP Call<br/>21.03.2024</li></ul></li></ul><h3 id="InVehiclePaymentsBirdsofaFeather-18thofJanuary2024"><strong>18th of January 2024</strong></h3><ul><li>Permission to record the call was given.</li><li>Welcome and Introductions<ul><li>List of participants<ul><li>Jens Kohnen (Starfish)</li><li>Vamsi Putrevu (Mavi.io)</li><li>Paul Boyes (COVESA)</li><li>Mike Nunnery (COVESA)</li><li>Maria Trudgeon (GM)</li><li>Richard Fernandes (GM)</li><li>Robert Bronninger (BMW)</li><li>Michael Gross (Endava)</li><li>Henry Bauer (Endava)</li><li>Paula Silverthorn (Endava)</li><li>Emilian Stoilkov (QaiWare)</li><li>Georgi Radev (QaiWare)</li></ul></li><li>Brief introduction of each member, their role, and organization they represent.</li><li>Objectives and expectations towards the IVP group</li></ul></li></ul><ul><li>Proposed problem statements to be tackled within this group:<ul><li>Proposal 1:<ul><li>Problem Statement: OEMs face a challenge in integrating third-party service providers into their in-car entertainment systems, necessitating a complex process that involves payment, billing, invoicing, and master data exchange, along with technical integration between the entities. This issue is compounded by the lack of a standardized approach, resulting in each automotive OEM and third-party provider independently grappling with the same problem.</li><li>Solution proposal: To address the prevalent challenge faced by OEMs and third-party service providers in integrating services into in-car entertainment systems. This project aims to establish a common industry standard to streamline payment, billing, invoicing, master data exchange, and technical integration processes.</li><li>Action items:</li></ul></li><li>Proposal 2:<ul><li><p>In-Car Wallet Interface for Apps:</p><ul><li><p>Problem:<br/>OEMs face a challenge in standardizing an API interface that 3rd party apps can access to conduct payments usecases such as parking, charging, buying food etc.</p></li><li>Solution Proposal:<br/>Define a standard interface (APIs) that will be implemented by the OEM and/or app stores and tier 1s</li></ul></li></ul></li><li>Proposal 3:<ul><li>Validate if other payment methods than credit cars play a relevant role to be implemented as method for in-car payment</li></ul></li><li>Proposal 4:<ul><li>Problem statement: OEM face the issue that updates / replacements of rolled-out applications in vehicles is a problem. Typically not all relevant vehicles are updated and OTA. </li><li>Solution proposal: Limit the app exposure in the vehicle and hold as much of logic and code as possible in the backend. As proposal for this group it should be discussed and an overall architecture approach which caters for this problem and defines how 3rd party app provide their solution → Frontend vs. Backend Integration.</li></ul></li><li><a href="https://covesa.global/events" class="external-link" rel="nofollow">Next events</a><ul><li>COVESA All Member Meeting<ul><li>April 16-18, 2024<br/>Gothenburg, Sweden</li><li>Call to action: Participants and potential working group</li></ul></li><li>IVP Group call: February 15, 2024</li></ul></li><li>Action item: The participants agreed on further elaborate on the problem statements in the next IVP call.</li></ul></li></ul><h3 id="InVehiclePaymentsBirdsofaFeather-14thofDecember2023"><strong>14th of December 2023</strong></h3><ul><li>Who will be at CES? And, what are you doing?<ul><li>mavi.io will be there all week</li><li>Starfish will be there</li></ul></li><li>Should we meet at CES?<ul><li>Have presence at booth at CES with QR code to register contact info for updates </li></ul></li><li>Problem Statement</li></ul><h3 id="InVehiclePaymentsBirdsofaFeather-16thofNovemeber2023"><strong>16th of Novemeber 2023</strong></h3><ul><li><a class="confluence-userlink user-mention" data-username="jens@starfish.team" href="https://wiki.covesa.global/display/~jens@starfish.team" data-linked-resource-id="71073914" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.covesa.global">Jens Kohnen</a> and @Vamsi Putrevu will serve as chairs. It was agreed there is a need for OEM chair(s) in addition.</li><li>It was agreed the next meeting will be on 14th of Dec. See Community Calendar for details. </li><li>Charter was reviewed.</li><li>It was agreed there is a need for clear problem statement(s) that this group intends to work on.</li><li>Action Item: Participants will bring clear problem statements to the next meeting.</li><li>The following areas of categorization were discussed:<ul><li>Feature on demand</li><li>parking, fuel, charging - scale from vehicle platform</li><li>vehicle as a platform - direct service provider</li></ul></li><li>It was suggested that the relationships between VSS and AOSP groups should be explored.</li></ul><p><br/></p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.covesa.global/display/WIK4/In+Vehicle+Payments+Birds+of+a+Feather">View Online</a>
·
<a href="https://wiki.covesa.global/pages/diffpagesbyversion.action?pageId=85196956&revisedVersion=15&originalVersion=14">View Changes Online</a>
</div>
</div>Jens Kohnen2023-11-17T20:26:07Z