This page intends to contain the agenda for next meeting 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.

Proposed Agenda 2023-03-28

• Compliance statement

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to the an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting notes 2023-03-21

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  
  • Albert Kos: Gaia-X - (http://www.gaiax4ageda.de/) interesting to get surrounding objects into VSS. Possible to setup a meeting?
    • Sebastian: Paul Boyes could organize meeting if needed
    • Ulf: No meeting necessarily needed, you could issue/PR.
    • Albert to start by creating issues (in 3 weeks)
  • VSS-Tools - Line endings JSON?
    • Result - no line breaks
  • Tool limitations
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting notes 2023-03-14

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Intro to VSS - 16.00 CET Tomorrow
  • VSS-Tools - Line endings JSON?
    • Result - no line breaks
  • Issue 526
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting notes 2023-03-07

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • AMM topics.
    • Schedule is starting to form. Contact is PaulB.
    • Working sessions will be on 26th and 27th. Focus on Data, VSS.
    • Current proposals AMM Planning April 25-27 2023 - Technical Session and Workshop Proposals
  • PRs for AMM VSS Workshop
    • https://github.com/COVESA/vehicle_signal_specification/pull/555
    • https://github.com/COVESA/vehicle_signal_specification/pull/526
• Decision on old open PRs
  • PR https://github.com/COVESA/vehicle_signal_specification/pull/526 We will wait for the input. Take connectivity as topic for VSS workshop.
  • NIck will add aditional documentation about connectivity into the PR 526.
• Open Pull Requests VSS
  • PR
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting notes 2023-02-28

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • INFO: VSS 3.1 released
  • Wanted features for VSS 4.0 end of April (before AMM?)
    • Structs support, but what more?
    • Moving documentation to new repo?
      • Meeting notes -seems reasonable
  • AMM - what sessions are needed/wanted. What do we want to cover in the workshops
    • Ulf: Slot/presentation on how evolving VSS ("multiple trees")
      • 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
    • Sebastian: CAN Feeder - dbc mapping
    • Sebastian: Security approaches - KUKSA tokens changes and comparison to VISS
    • Adnan: VSSo and Taxonomy - see https://github.com/COVESA/vehicle_signal_specification/issues/548
  • Open PRs - quite a lot
  • VSS structure
    • https://github.com/COVESA/vehicle_signal_specification/issues/548
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting notes 2023-02-21

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Renew meeting invitation
  • Release planning VSS 3.1 (late February)
    
    • Remaining PRs/Features needed before we can release VSS 3.1
      • Suggestions:
        • https://github.com/COVESA/vss-tools/pull/218
        • https://github.com/COVESA/vehicle_signal_specification/pull/535
        • Basic struct documentation/placeholder?
          • Erik to add "simple" doc for VSS 3.1, krishna to continue extending for VSS 4.0
      • AP: Erik to check with Paul on how to communicate that we have released VSS 3.1
        • Compare with Reminiscing and Release of VSS Version 3.0
      • AP: Erik: to prepare release
    • PRs that better shall wait until after VSS3.1
      • All other
  • Renault Meeting
  • VSPEC restructure - https://github.com/COVESA/vehicle_signal_specification/issues/527
    • If agreed - best implemented and merged just after VSS 3.1 release - would cause conflicts to most other open PRs
    • Preferably "quick review process" to minimize time when there are conflicts
  • Moving documentation to new repository (https://github.com/COVESA/vehicle_signal_specification/issues/543)
    • Possible candidate for VSS 4.0?
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

  w3cauto

Meeting notes 2023-02-14

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Struct support
    • Status report
    • Exporters - how do we expect them to handle struct data
      • Struct information generated in same file or other file
      • Likely straightforward to implement support in vspec2json, vspec2csv, vspec2yaml
      • Volunteers for vspec2binary, vspec2ddsidl, vspec2franca, vspec2graphql?
        • And contrib tools: vspec2protobuf, vspec2ttl
        • Daniel Alvarez will likely look at the vspec2ttl
        • Ulf feel responsibility for binary tool.
        • Sebastian can check with those who developed vspec2ddsidl
      • AP: Erik to update or create issue to track what is needed for the major release in April
  • Workshop this week
    • Agenda at Data Expert Group - Workshop 2023 - Q1
    • All welcome
    • Attendees: erik, Ulf, Daniel (partially, 14-16 CET), Adnan, Sebastian (partially, +0.25)
    • AP: Paul to cancel related COVESA meetings during the same timeslots.
  • "Extra day" at AMM for deeper discussions, possibly Friday after AMM, possibly half-day
  • New Pull requests
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting
  • Planning for minor release (around end of February, possibly the week Feb 27th - March 3rd)
    • What to include and what not to include:
      • Possibly wait with left/right - driver/passenger conversion until major, as breaking backward compatibility

Meeting Notes 2023-02-07

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?

• PRs up for decision
  • Power Optimize: https://github.com/COVESA/vehicle_signal_specification/pull/528
  • Steering angle: https://github.com/COVESA/vehicle_signal_specification/pull/530
• Prioritized topics
  • Daniel issue
  • Connectivity PRs - Cole Gerdemann to present
    
    • https://github.com/COVESA/vehicle_signal_specification/pull/526
    • https://github.com/COVESA/vss-tools/pull/207
  • VSS-Tools struct support
    • Status update from Krishna
    • Align on merge model - small PRs require quick reviews.
      • OK if merge if reviewed by at least one maintainer (Erik/Adnan/Sebastian)
        • Meeting notes. Agreed
      • Wait with merging non-related PRs? (To minimize rebase effort)
        • Notes: Likely not need for struct work
  • VSS file restructuring
    
    • Erik to present draft - see https://github.com/COVESA/vehicle_signal_specification/issues/527
  • COVESA data expert group Workshop 2 halfdays, Feb 15th+16th, everyone free to participate, see COVESA calendar
    • If interested join data Expert Group slack channel or mailing list.

• Walk through Pull Requests and Issues VSS
• Walk through Pull Requests and Issues VSS-Tools
• Topics on hold
• Older issues VSS & VSS-tools
• Prioritized topics for next meeting

Meeting 2023-01-31

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?

• Decision on old open PRs
  • Overlay support for expanded instances - https://github.com/COVESA/vss-tools/pull/203
  • Mypy
    • https://github.com/COVESA/vss-tools/pull/210
    • https://github.com/COVESA/vss-tools/pull/209 (if signoff added)
    • https://github.com/COVESA/vss-tools/pull/212
  • Cleanup - https://github.com/COVESA/vss-tools/pull/211
• Prioritized topics
  • Connectivity PRs - Cole Gerdemann to present (postponed)
    
    • https://github.com/COVESA/vehicle_signal_specification/pull/526
    • https://github.com/COVESA/vss-tools/pull/207
  • Discussion: Why using left/right instead of passenger/driver for example for door
    • Adnan : Possibly to create a pull request

• Walk through Pull Requests and Issues VSS
• Walk through Pull Requests and Issues VSS-Tools
• Topics on hold
• Older issues VSS & VSS-tools
• Prioritized topics for next meeting

Meeting 2023-01-24

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Old Pull Requests (where there is no "ongoing" discussion or recent changes - merge decision pending)
    • https://github.com/COVESA/vehicle_signal_specification/pull/521
    • https://github.com/COVESA/vehicle_signal_specification/pull/509
    • https://github.com/COVESA/vss-tools/pull/204
    • https://github.com/COVESA/vss-tools/pull/205
    • https://github.com/COVESA/vss-tools/pull/206
  • Struct Proposal

Work Package for Struct Proposal:
Details of the proposal in [PR 511](https://github.com/COVESA/vehicle_signal_specification/pull/511/)

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

• • • Notes:
      • Krishna can contribute to A, unsure about B and C
      • Target: End of February for minor release
      • Possible Target: Major release late April
      • Paul: AMM likely in Porto, Portugal, 25-27th April
  • Introduction of new issues/PRs (very short)
    • Time units/datatypes - introduction https://github.com/COVESA/vehicle_signal_specification/issues/525
    • Power Optimize - Introduction of Bosch proposal https://github.com/COVESA/vehicle_signal_specification/pull/528
      
      • Potential replacement for https://github.com/COVESA/vehicle_signal_specification/pull/520
    • Connectivity PR - Introduction as preparation for next week discussion
      • Units: https://github.com/COVESA/vss-tools/pull/207
      • Signals: https://github.com/COVESA/vehicle_signal_specification/pull/526
    • Cleanup - https://github.com/COVESA/vss-tools/pull/211
    • Mypy (3 PRs)
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Paul Boyes: COVESA Workshop planned for February 15th-16th (online, two halfdays, 5 - 9am PT
  1400-1700 CET
  6:30-10:30pm IST
  10pm - 2am JST)
  • Action point: Paul will send out invite and ask for topics
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting 2023-01-17

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:

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Neil Puthuff (RTI) presenting some initial observations as new to COVESA/VSS
    • Reference: https://docs.google.com/document/d/1dHHMIlIZpsbnVsTiiza4Suua-vVbfR1xm11KNKdAm38/edit 
    • Grouping of signals - is there a mechanism to group signals.
    • Best way forward - create issues for most important areas to describe problem and wanted solution and continue discussion
  • Ford proposal - Fleet based range prediction
    
    • Christoph Schierjott presents EV Charging Event Data Aggregation Project
    • Data upload of various data to cloud
    • Cloud calculates correction factor individually and sends down to vehicle to correct fleet range prediction
  • Power Optimize
    • Mobis Architecture
      • 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%
    • Pre-information Bosch proposal
      • Erik: Bosch has some ideas on representation that will be presented in the Power Optimize meeting this week
• Open Pull Requests VSS
  • Closed: https://github.com/COVESA/vehicle_signal_specification/pull/523
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting 2023-01-10

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:

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • None
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Information from Paul
  • Big interest at CES
  • We need to have a bigger discussion late January or February to how to simplify use of VSS.
  • Paul to discuss with Data Expert Group (Erik, Adnan) on how to proceed.
• Prioritized topics for next meeting

Meeting 2022-12-20

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Aggregate vs. structs - when do we see it need to be kept
    • From last week - Ulf/Erik: In favor of deprecating/removing aggregate keyword
    • 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
    • Adnan: Allow aggregate on deployment level, can use it when needed. For now good to only have it as information.
    • Krishna: Thinks aggregate makes changes, struct does not affect it. If we want to depricate we can do it later
    • Ulf: Does not have a strong opinion
    • Adnan: Good to document when structs vs aggregate shall be used
    • Erik: Can update the PR
    • Erik: Do you Krishna have interest in doing actual work.
    • Krishna: In January will start working on it, can help Erik
    • Erik; Then we can discuss later when we think it will be ready for VSS 4.0 release
  • Information: Overlays after expansion
    • 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.
  • Discussion: PowerOptimize PR
    • Chandra: Intention to have one branch in each area, for infotainment we see brightness and audio volume
    • Chandra: Does not intend to duplicate, only want one signal, need only one
    • Erik: Isn't PowerOptimize only one of many use-cases for e.g. brightness, why need a PowerOptimize branch
    • Chandra: If scattered more difficult to find
    • Sebastian: OEM needs to decide what is part of his power optimization, do not understand the value of having them in separate branch
    • Adnan: What is difference
    • Pradeep: Adding a feature set, complete algorithm,
    • Adnan: If you are only proposing values, then it makes sense
    • Sebastian: Alternative usages could be e.g. overlay
    • Chandra: When we explain we see some signals are duplicated
    • Adnan: Best solution would if you prepare and show architecture on how it is intended
    • Adnan: Have not seen scope. Like to learn how
    • Pradeep: Do you have any public link describing how it is supposed to work.
    • Adnan: if you create some simple document you can attach it, then we can try to find best way
  • UUID elements
    • Adnan: Is anyone using UUIDs at the moment
    • Sebastian: We have never used them
    • 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.
    • Sebastian: UUID are as of today generated based on tree structure.
    • Adnan: We need more, e.g. history. How do we move leave but keep UUID.
    • Sebastian: Could be a hash of only name/description/....
    • Erik: Please Adnan create an issue and ask if someone use UUIDs - if not you are free to do anything.
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting
  • Note: Dec 27th cancelled
  • Meeting as usual Jan 3rd

Agenda for Meeting 2022-12-13

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Aggregate vs. structs - when do we see it need to be kept
    • Ulf/Erik: In favor of deprecating/removing aggregate keyword
    • Erik: Seems proposal is quite stable, lets wait discussing work packages until Jrishna is back, as he seemed interested in implementing in vss-tools
  • Summary for vote of Allowed (https://github.com/COVESA/vehicle_signal_specification/issues/502)
    • vote result: allow int and float for now
  • Meeting cancellations due to new year
    • Availability of participants Dec 20th?
    • Suggest cancelling Dec 27th?
    • Availability of participants Jan 3rd? (Erik unavailable)
    • Decision: Cancel Dec 27th, wait with decision on Dec 20th and Jan 3rd
    • Availability: (Paul: all, Ted: all,  Umang: all, Ulf: all)
    • Erik to check with Adnan (and Krishna)
  • Open Pull Requests (vss+tools, except struct) - approve/object before next week.
    • See PRs
  • Information: New issue for proposal from last week
  • Information: Overlays after expansion
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting 2022-12-06

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Continued struct decision, focus on recommendations/limitations, why we need it, rationale (https://github.com/COVESA/vehicle_signal_specification/pull/511)
    • Meeting notes:
      • Krishna - for types - there could be subtrees working as namespace. Erik to improve description.
      • Adnan - we need to come up with how to use "Aggregate"
      • Krishna - could be useful for aggregating
      • Adnan - we need to explain advantage of aggregate vs struct
      • Erik to create proposal in document
      • If no further comments, next step is to identify work packages in detail and do estimation for roadmap
  • Ulf presented some roadmap ideas (15-20 minutes)
    • Proposals:
      • Reason - to get a domain agnostic taxanomy
      • Move "rule set" to new specification project, VSS keeps the catalog.
    • Sebastian: Could be an idea to scope it to "mobility only"
    • Erik: Could at least be idea to have a vision/mission for the "rule set" to primarily support mobility use cases
    • Daniel: Integrating/reference domains in Yaml does not make sense, Ontology is a better choice. This is the next step of VSSo.
    • How to proceed:
      • Document to be uploaded
      • Discussion to be continued at some later time (not urgent)
      • Interesting topic for next AMM, including VSS ↔ VSSo relationship
  • Summary for vote of Allowed (https://github.com/COVESA/vehicle_signal_specification/issues/502)
    • Wait until next week
  • PR/Change governance (https://github.com/COVESA/vehicle_signal_specification/issues/515)
  • Overlays on expanded tree (https://github.com/COVESA/vss-tools/issues/201)
  • Release Cadence/Roadmap (https://github.com/COVESA/vehicle_signal_specification/issues/513)
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting

Meeting 2022-11-29

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
  • Struct Proposal (https://github.com/COVESA/vehicle_signal_specification/pull/511)
    • See PR, agreed to change proposal to have struct definitions in separate file. Erik to update proposal
  • Release Cadence (https://github.com/COVESA/vehicle_signal_specification/issues/513)
    • Skipped due to lack of time
  • Roadmap (https://github.com/COVESA/vehicle_signal_specification/issues/508)
    • Skipped due to lack of time
  • Support for "allowed" (https://github.com/COVESA/vehicle_signal_specification/issues/502)
    • Voting next week
  • PR/Change governance
    • Skipped due to lack of time
• Open Pull Requests VSS
  • Skipped due to lack of time
• Open Pull Requests VSS-Tools
  • Skipped due to lack of time
• Issues VSS
  • Skipped due to lack of time
• Issues VSS-Tools
  • Skipped due to lack of time
• Prioritized topics for next meeting
  1. Continued struct decision, focus on recommendations/limitations, why we need it, rationale
  2. Ulf to present some roadmap ideas (15-20 minuets)
  3. Summary for vote of Allowed
  4. Release cadence/Roadmap

Agenda Template

• Compliance statement - TBD
• Welcome and agenda discussion - anything that needs to be added?
• Prioritized topics
• Decision on old open PRs
• Open Pull Requests VSS
• Open Pull Requests VSS-Tools
• Issues VSS
• Issues VSS-Tools
• Prioritized topics for next meeting