Versions Compared

Old Version 55

changes.mady.by.user Erik Jaegervall

Saved on

compared with

New Version Current

changes.mady.by.user Erik Jaegervall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

See COVESA Common Meeting Schedule for meeting link. The meeting is open to anyone.

General Agenda

  • Welcome and Compliance statement

...

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

...

  • Agenda discussion - anything that needs to be added?
  • Prioritized Topics:
  • Decision on old open PRs
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Discussions VSS
  • Discussions VSS-tools
  • Prioritized topics for next meeting

Meeting notes  2024-07-02

  • Paul: Want to get proposals for technical presentation by end of July, finished by end Mid August
  • Erik on business trip next week (Adnan back?)

Meeting notes  2024-06-25

  • API Standardization charter - > Listen in to the CVII meeting after the VSS meeting if you like
  • VSS-tools PRs
  • VSS PRS
  • VSS Issue (Daniel Alvarez)

Meeting notes  2024-06-18

Agenda  2024-06-11

Agenda  2024-06-04


  • AMM Info
    • Novi, Detroit-area, USA
    • 25-26 Sept, on 24th opportunity to have technical F2F sessions, related to VSS or other
    • Paul: Good to take the opportunity F2F
    • Erik: We need to start thinking on possible topics, especially for the 24th, also for 25-26th
  • VSS Release Status - VSS 4.2 released - https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.2
    • OK to remove pre-release tag
  • Presentation - Sending VSS data with Protobuf
    • By Kaan Bulut, Student at Techn Univ Munich, Thesis done in collab with BMW
    • Multiple options
      • Generate messages for all leafs (flat)
      • Generate all message as key (key-value pair)
      • vpec2protobuf -hierarchy of messages
    • Compaibility - backward/forward/full

Image Added

Image Added

Meeting notes  2024-05-28

Meeting notes  2024-05-21

  • Future of VSSo (Paul)
    • There has been proposals on modeling fron Ford and BMW
    • Paul is happy to help if someone wants to drive it forward
    • Gunnar: The proposal from Swen - adding info on source of data items, has been discussed, adding metadata or ontology
    • Gunnar: Found some drafts on layers, we should put them somewhere

VSS Layers was discussed in Cloud & Connected Services project, end of 2019 and beginning of 2020.

The VSS Layers draft was attached to the page.
Direct link: https://wiki.covesa.global/download/attachments/12124613/VSS%20composable%20layers%20-%20draft%2020200114.pdf?api=v2

Minutes from CCS are here, but there is a lot…
https://wiki.covesa.global/pages/viewpage.action?pageId=12124613


Meeting notes  2024-05-14

  • VSS Release 4.2
  • "GraphQL as VSS Language"-info
    • Adnan: The presentation from Swen Schisler could be good as a COVESA blog post
    • Paul: To check
    • References

Meeting notes  2024-05-07

Meeting notes  2024-04-30


Meeting notes  2024-04-23

VSS-Tools PRs

  • 343 to be merged
    Python active support until 2026
  • 344 has to be checked and reviewed
  • 346 to review and merged
  • 347 to be checked by Erik, how to automate version

VSS-Tools Issues

Close issue 194 it is merged now.

Vspec PRs

  • 731 stays open 
    - PierPierB 
        - Comments are documenting summary of the discussion.
        - euro ncap is quite interesting document and it would be great to use this as base for the alignment of this topic.
        - Stefan will check as well with Allianz
  • 737
    - Resolution might be limited(Stefan)
    - What about orientation of screen?
    - What is the main usage and do we have any usecases? Are we missing anything on top.
  • 659
    • Ppb new comment reference to euro cap 


Issue VSpec

  • 735 related to issue spec to franca


We had new visitors.
Sivashankar Yoganathan
AB: Do you have myb some use cases or requirements to share?
SY: We could do exchange and understand requirements.
SY: what is missing is frequency of the signals, but we can discuss more details
SY: possible exchange in two weeks, 
AB: slot in the meeting for 15-20 min. 10min presentations, 10 min talk. cca 07.5.2024
StefanS: Would be great to have this discussion

New people from MOTER that joined us 
Mohair Yadav from Ford as well.

ViSS status.

Ulf and Peter
- Ulf: ViSS is stabilised in covesa repo and everyone can use it
- Peter: demo went well as well on the side of Volvo 

Meeting notes  2024-04-18 (April 2024 AMM Working Session on Raw vs. Derived signals):

  • The definition of derived signals is not as straightforward as the definition of raw signals
    • Distraction levels of 0% and 100% are clear but what does 66% or 34.5% distracted really mean?
    • Should distraction really be represented as a percentage? Or, perhaps an enum?
  • Units are one way in which clarity can be achieved
    • Requires introspection (ability to ask the model) support in the API or equivalent
  • Even if enums are used to "bucketize" or categorize the values, interpretation of what each bucket means is still important or not necessarily clear
    • For example, what is a crash and severity of crash can have different interpretations depending on culture, context, etc.
    • Same for aggressiveness
  • How could we make available information on how a signal is derived?
    • Where it may be needed or useful
    • How can this be expressed to the user?
    • Does it need to be digital?
  • Margins of error and calculations may vary in time
    • Remaining distance based on fuel consumption varies over time
    • Some signals from which a derived signal is generate may become unavailable or become available again
    • The rate of incoming signals may affect the derivation
    • How do we plan to repesent this?
  • Even an OEM may not know how some signals are derived
    • The Tier-1 may have their own way of doing the derivation and this is not available to the OEM
  • What is a raw signal?
    • Is there such a beast?
    • Clearly there are some, but perhaps the great majority of signals are derived?
  • Would adding all the information discussed above impact simplicity?
    • One main goal of VSS is simplicity
    • Perhaps less precise definitions of signal values is actually simpler
  • Should we define the set of parameters to evaluate in order to decide if a derived signal should be added to the signal catalog?
    • Is portability of applications (where they can rely on a "standard" definition of a signal) a concern?
      • And therefore should the signal catalog only contain clearly defined signals as opposed to leaving definition to interpretation?
    • Options to consider:
      • Determine if the signal should be made part of the catalog or left for manufacturers to add using overlays
      • Require that signal definitions refer to a standard
      • Allow liberal interpretation, but mention in signal definition comments that interpretation is left to the implementation

Meeting notes  2024-04-09:

  • Crash detection/events - car immobilized
    • Stefan: Do we have anything?
    • Adnan: PRs welcome
    • Erik: Sometimes we create a temporary *.md file and add it to PR for discussion.. PPB to put down initial thoughts in *.md
  • AMM
    • No regular VSS meeting next week
      • Erik has asked Paul to delete
    • VSS Deep Dive being prepared by Sebastian Schildt
  • Head& Eye
  • VSS-tools
    • A lot ...

Meeting notes  2024-04-02:

Meeting notes  2024-03-25:

Meeting notes  2024-03-18:

  • AOSP
    • Merge ok
  • VSS vs. VSS-tools compatibility
  • Overlay and remove
    • Shall new keyword "state" be considered to be part of "std VSS syntax", i.e. described in VSS doc
      • Alternative is to consider it just as a VSS-tools-specific feature
    • https://github.com/nwesem/vss-tools/pulls
    • Adnan: Does not really understand the use of active/inactive
    • Daniel: Is it intended only for exporter, or also other function
    • Adnan: Inactive/active fills a different purpose, not needed for vss-tools for purpose of removing signals of tree
  • Terminology:
  • AMM

    • Topics for discussion:

    • Raw vs. derived signals; does VSS need to define or state how signals are derived?
      • Is this useful to clients?
    • For signals derived through ML; should confidence level, variance, precision, error, etc. be reported?
      • Is this useful to clients?
    • How should model-generated derived signals such as "driver attentiveness" be represented (in the absence of a standard)?
      • Confidence percentage? Enum?
    • To what level of specificity should VSS describe signals?
      • Leave semantics to OEMs (flexibility for OEMs but affects portability) or define them precisely?

Meeting notes  2024-03-12:

  • Adnan -overlay and remove node
    • See https://github.com/nwesem/vss-tools/pull/2 - not ready for official VSS repo yet
    • Keyword "deleted"
    • Comments welcome
    • Pierre Pierre: Interested, will share some feedback. We have thought of a private "x-delete" but better if public/agreed
  • AMM Planning
    • 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.


      Agenda


      • 5 minutes – introduction to VSS maintainer team (i.e. Erik, Adnan, Sebastian) and general requirements if we should refactor VSS
      • Recap & Way Forward (10 min each) – Quick recap of the topic and discuss if there is anyone that wants to drive the topic.
        • VSS Type Representation and Reusable Properties
        • Tree vs. Flat Structure
        • Instance Handling
        • Overlays
      • Other topics (10 min)

      A potential abstract for the official agenda could be something like below, unless someone else has a better proposal:

      “ 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

    • Discussion
      • PPB: Value discussing various concepts (40 minutes)
        • A number of signals are "raw" signals, others derived. Sometimes it matters how they are derived
        • Driver attentiveness/sleepiness, what is meaning of 63% sleepiness, how to handle confidence
        • VIN - is static/attribute, what should we do we signals if value comes regularly but never change
      • Erik: Would be great if you present it PPB
      • Daniel: Aspects of having derived information, all participants of the driving env. Concentrate on model, rather than individual signals like VIN - have a session 4:00 PM - 4:45 PM Wed (Towards a Vehicle DATA Specification), but would like to have some time in working session as well
      • Paul: need agenda, slides does not be prepared
      • Paul: There might be remote participants
    • AP: PPB to prepare slides
    • AP: Erik to propose agenda/abstract
  • VSS data (time series) discussion
  • VSS Release Planning
    • https://github.com/COVESA/vehicle_signal_specification/issues/689
    • Erik: "5.0 Only" - only some minor signal rename and datatype changes, but they have been for quite a while
    • PPB: The delete functionality could be nice to have in 5.0 - a major capability
    • Erik: That would be ok, good to announce that 5.0 will include delete
    • Erik: working assumption - wait with 5.0 until delete-functionality

Meeting notes  2024-03-05:

  • Info - COVESA Spotlight on VSS featuring RemotiveLabs March 14th 16.00 CET
    • See community calendar
    • Will likely be recorded
    • Erik: DEG 14th will likely be cancelled
  • NOTE: Daylight changing in US next week, note that all COVESA meeting should be anchored in EU timezones
  • Paul: AMM schedule is full/finalized, official site shall be up to date, check https://www.eventleaf.com/e/AMMGothenburg2024 and report errors to Paul

Meeting notes  2024-02-27:

  • Introduction
  • Info from maintainer (Erik)
    • 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.

Meeting notes  2024-02-20:

  • AMM VSS Topics - Topic proposals
    • VSS Working Session 9.45-11.30 Wednesday (DEG also have some time for working sessions)
      • Moved to afternoon 15.30-17.30 for allow for remote participation
    • Anything particular someone wants to bring up or present?
    • Suggestions:
  • General AMM
    • Still possible to propose slots to Paul but filling up
  • New and old PRs
  • New issues
  • Issue handling - general
    • What to do with issues where there has not been any progress in many months
      • Keep forever or decide on an auto-close policy?
        • Should be doable at least for suggestions/discussions
        • For limitations/defects - possibly manage elsewhere? Like in documentation for the related tool.
    • Example: Signal Accuracy - https://github.com/COVESA/vehicle_signal_specification/issues/105
      • Possible improvement area, but no-one seems to be interesting actively driving it
    • Example: Emission standards - https://github.com/COVESA/vehicle_signal_specification/issues/394
      • Possible improvement area, but no-one seems to be interesting actively driving it
    • 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
      • Possible improvement areas
      • Actual limitations/error (which no-one intends to fix)
    • Proposed Handling (to be discussed):
      • Close issues after 6 months of inactivity
      • If we have agreed/decided something in the discussion - reflect that in VSS or VSS-tools documentation before closing the issues
      • If the issue concerns a known limitation/error, then document that in a file for known limitations in the repo
        • Example: Generator vspec2something  cannot handle the signal name ggg as that is a a reserved word in something .
    • MoM:
      • Daniel: think it is good to have something, so that issues are decreasing
      • No objection to closing inactive items
  • Android tooling
    • https://github.com/COVESA/vss-tools/issues/192
    • Erik:
      • 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)
      • Suggestions:
        • Create a better branch name and add a wiki page explaining purpose of the branch
        • Or integrate it into current as "prototype"
      • MoM (old): Think about it, discussion to be continued
      • MoM: No opinion

Meeting notes  2024-02-13:

Meeting notes  2024-02-06:

Meeting notes  2024-01-30:

Meeting notes  2024-01-23:

Meeting notes  2024-01-16:

  • VSS 4.1 Released
  • AMM April 16-18 Gothenburg, Sweden
    • Technical Sessions Planning in progress
  • CES - big interest in VSS
  • Digital Key
  • Overlay problem
    • Adnan:
      • Overlay (to redefine/overwrite attribute or add attributes) is case sensitive, could result in two signals.
      • How to prevent it?
      • Alt 1: Do a case insensitive merge (keep orig name)
      • Alt 2: Give warning if diff just by case somewhere (and error if in strict mode?)
      • If warning - handle it like they are the same
      • Will possibly create PR
  • New VSS PRs
  • VSS-style issue (enforce style, allowed values)

Meeting notes  2023-12-19:

  • VSS 4.1
  • Screen mirroring - https://github.com/COVESA/vehicle_signal_specification/pull/699
  • Issue690
    • 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.
    • When we are all back present the proposal from Erik
    • Daniel: We could use examples for different APIs
    • Erik: AP to present possible solution Jan 16th
  • FMS/ACEA
  • Meeting Jan 9th cancelled due to CES
  • Next official meeting Jan 16th - create issues or bring up topic on slack if needed
  • Catena:
    • Paul Boyes - when you will you send out invitation?

Meeting notes  2023-12-12:

  • Catena-x topic.
    • Adnan: We had some discussions about VSS and Catena.
    • Achim: Proposal on how to harmonize activities.
    • Achim: Find alignment among companies that are willing to contribute.
    • Achim: We should be prepared for the catena extension and make alignment there. Next step: Ford, Bosch, BMW to find alignment regarding vehicle domain.
      Paul Boyes will setup a meeting.
  • Overview VSS-Tools, VSS.
  • Issue 690 - continued discussion.
    • Nick prepared overview on how to handle units.
    • Adnan presented high-level approach he uses at BMW.
    • Erik to present solution proposal. We need more input.
  • Meeting pause for christmas/new year? 26th and 2nd of January we will take a break.

Meeting notes  2023-12-05:

Meeting notes  2023-11-28:

Meeting notes  2023-11-21:

Meeting notes  2023-11-14:

  • Prioritized Topics
    • Release Preparation
      • Static id PR status - no news
    • 5.0?
      • Pierre: We can add "5.0" signals as overlays, so we can use torque as overlay.
      • Decision: Keep 5.0 on hold, open up to release 5.0 in April/May (or earlier if needed)

Meeting notes  2023-11-07:

  • Prioritized Topics
    • Release Preparation
      • Decision needed - shall we only release 4.1 and not 5.0?
        • 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?
        • Working assumption: We do not release 5.0 now as no requests, plan for spring instead
        • AP: Erik to check with Pierre Pierre Blais if Blackberry sees a value in a major relase now
        • If your organization wants a 5.0 before Christmas, please let us now
        • AP: Erik to update 4.X branches (cherry pick)
      • Timeframe static id change
        • Adnan: working on hash support in addition to sequential id, compared 64 bit sv 32 bit hash.
        • Adnan: For hashing path, type, unit and datatype is used
        • Erik: we could create new pr from niclas fork if needed

Meeting notes  2023-10-31:

  • Prioritized Topics
    • Static UID - draft PR at https://github.com/COVESA/vss-tools/pull/305
      • New script vspecID.py 
      • Give vspec files as both input and output
      • You can specify prefix with "gen-layer-ID-offset", first 64 reserved for COVESA. WIth id layer 4 bytes, otherwise 3 bytes
      • Adds a staticUID string, like '0x02345678'
      • "--validate-static-uid <old.vspec>" gives option to keep/replace if changed, if compatible (like name check)
      • You maintain static id files yourself
      • Once you have the generated .vspec/ .yaml, then with overlay you can run all other tools, like vspec2json
      • Erik: Can be included in minor release, as it does not affect UUID
      • Pierre: The Blackberry model serves the same purpose, different approach
      • Pierre: How to manage addressing by old name, if name is changed.

Meeting notes  2023-10-24:

  • Prioritized Topics:
    • Summer time alignment
      • Ends Oct 29 Europe
      • Historically COVESA meetings often anchored in European time zone
      • Currently conflict - VSS anchored in european, but CVI anchored after
      • Suggestion - keep european time for VSS next week, move CVI
      • AP Erik Jaegervall to sync with Paul Boyes 
      • AP: Send out reminder on slack
    • Copyright
      • AP: Erik Jaegervall to follow up with Paul Boyes 
      • Conclusion: Go with proposal
      • AP: Erik update PR for next meeting, then please review
    • (U)UID:
    • General info from Paul
      • Please put company name in zoom "user name" - make it easier to understand who you are talking to

Meeting notes  2023-10-17:

  • Prioritized Topics:
    • AMM recap
      • VSS discussion points
        • Erik showed some slides
        • AP: Erik to summarize response/comments (See VSS_workshop_comments.pdf)
        • AP: erik to create issues for topics that seems to have traction, so that we can make decision
        • Adnan: Daniel Alvarez wanted to create proposal related to model/ontology, align with proposal from Alan
        • Erik: Shall we possibly do a similar presentation online "evolvement workshop" in January?
        • Paul: Seems good
        • AP: Paul to propose date/time for a session in late January
    • JSON schema


Meeting notes  2023-10-03:

  • Prioritized Topics:
    • VSS session AMM Thursday
      • Intention to discuss Ford/Blackberry proposals as well as other recurring topics
      • AP: Check with Paul - join the two sessions
      • Will someone from Ford (Alan?) and Blackberry (Pierre?) participate?
        • Ford possibly remote
        • Pierre will leave at lunch Thursday

Meeting notes  2023-09-26:

Meeting notes  2023-09-19:

  • Prioritized Topics:
    • Tero from Profilience introduced him self.
    • COVESA Spotlight - BlackBerry IVY, next after this meeting, they will show how they use VSS
    • 4.1-planning - UUID, any timeplan
      • Adnan: Draft PR in about 3 weeks,
      • Erik: Great if draft ready before AMM
      • Adnan: Concerning instances, have id for "top" definition (class) rather than individual instances
    • Struct support and DDSIDL

Meeting notes  2023-09-12:

Meeting notes  2023-09-05

Meeting notes  2023-08-15

  • Agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Anything VSS related things we/you want to do at AMM
      • BlackBerry looking into having a demo and presentation
      • COX automotive will attend
  • Decision on old open PRs
  • Open Pull Requests VSS
  • Open Pull Requests VSS-Tools
  • Issues VSS
  • Issues VSS-Tools
  • Prioritized topics for next meeting
    • 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 Paul Boyes 

Meeting notes  2023-08-08

  • General Topics
    • COX automotive → automatic mapping of data source
      • Ulf: no active work at the moment. Trend is existing but we would have to push the activity.
      • Adnan: Volvo is working on this topic and they have presented work on last AMM in Porto.
      • V.Raiker (Ford) - Interest for a WS on the next AMM
      • Paul Boyes Could you please create wiki page where we can collect requirements for automatic mappings and as well existining activities.
  • PR Status
    • No new PR or issues.

Meeting notes  2023-08-01

  • Presentation of VSS and Spread by Daniel Wilms
    • Presentation coming
  • Adnan:  Pull request on example shown in latest interface workshop

Meeting notes  2023-07-18 (Draft)

Meeting notes  2023-07-11

  • Notes taken in issues/PRs

Meeting notes  2023-06-27

Meeting notes  2023-06-20

  • No prioritized topics
  • Please check Defining the COVESA data modeling strategy and its associated artifacts as it tries cover also other domains. Add comments/question in wiki
  • Syntax checking (related to https://github.com/COVESA/vehicle_signal_specification/issues/599)

    Meeting notes:

    - Daniel: See https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts, would be better to have a standard format like RDF as source format.
    - Erik: So let tools use on RDF directly and generate other format from that?
    - Daniel; yes, still have *.vspec as experts but generated to RDF - let RDF be official format.
    - Fulup: Do not think people will parse from RDF directly, vspec->RDF->json seems complicated
    - Ulf: Keep YAml/vspec as single source of truth. It should be possible to generate RDF
    - Erik: Is a vspec2rdf tool all we need (short time)
    - Daniel: vspec2ttl already partially do it
    - Paul: Important to not slow down VSS progress
    - Fulup: Would love to have a tool that let my select which parts and get a normalized output with normalized quotes

    -Pierre: Isn’t RDF more restrictive in its syntax than YAML, which would make conversion from YAML to RDF somewhat difficult?
  • We would likely have to put some restrictions into what can be represented in YAML so that it can be converted to RDF.
  • Paul: A session with data guys would be helpful. RDF is well established
  • 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
  • Paul: Will arrange a more in-depth session

Meeting notes  2023-06-13

  • Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

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 be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.


  • Agenda discussion - anything that needs to be added?
  • Prioritized Topics:
  • 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-06-06

  • Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

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 be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.


Meeting notes  2023-05-22

  • Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

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 be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.


  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
    • DCO Github app (rather than action)
    • "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

1. Decide on name for the evolved data model.

2. Create a new COVESA Github repo based on the new name.

3. Decide on a directory structure that can accommodate rule set definitions for multiple domains and multiple information types.

4. Create a rudimentary README on the top level giving a high level description of the new data model.

5. Move the VSS "rules definition" (the documentation) from the VSS repo to an appropriate directory on this new repo.

6. Create a rule set for services that that meets the requirements from the "passenger car domain" (VSS).

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.

8. Analyze the impact on VSS-Tools that the above has, take action on the insights from that.

9. Try to influence the W3C automotive group to evolve VISSv2 to support the new data model.

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.

    •  Discussion:
      • Ulf presented the proposal above
      • Erik: Will be discussed in DEG group, VSC relationship to be sorted out.
  • 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-05-23

(Erik will not join)

  • Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

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 be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.


  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Release 4.0 Status
      • V4.0 released  https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.0
      • Topics addressed during RC-phase. If someone wants an alternative solution as long term solution they are welcome to create a PR
        • d added as prefix to string literals that could be numbers, like '33'. Just using _33 is not supported by all code generators working on DDS IDL.
        • Type checker for structs updated to support arrays of struct
        • Error now given if type root is not a branch (as some tools like vspec2protobuf can not handle struct as root)
      • Daniel to introduce what has been done in VSSo: Defining the COVESA data modeling strategy and its associated artifacts
        • Please read if interested, (you may post comments on the Wiki page)
        • Daniel will be back in 3 weeks to personally answer question (smile)
    • "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
  • 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-05-16

  • Welcome and Compliance statement

Welcome to the COVESA VSS Meeting!

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 be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.


  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Release 4.0 Status
      • RC2 created
        • For DDSIDL we now add a d as prefix for string numeric literals, i.e. '33' → d33
        • Pypi packaging: https://github.com/COVESA/vss-tools/pull/281
          • Sebastian: Check if we can add README (for Project description)
          • Paul: There are other repos using VSS in the name
          • AP: Paul to create pypi account. Erik to add Paul as owners. Paul to check if Steve Crumb wants/have an account.
      • Need for decision: OK to release?
        • Decision: Release
        • Decision: Delete RC releases, keep RC tags (Erik update wiki for release instructions)
  • Decision on old open PRs
  • Open Pull Requests VSS

    Meeting notes  2023-05-09

    ...