We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

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-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) to present some initial observations as new to COVESA/VSS
    • Status of EV charging project
  • Open Pull Requests VSS
  • 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
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting


Meeting 2022-11-29


Agenda Template

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



  • No labels

Privacy Policy | Cookie Policy