Versions Compared

Old Version 53

changes.mady.by.user Ulf Bjorkengren

Saved on

compared with

New Version Current

changes.mady.by.user Ulf Bjorkengren

Saved on

Key

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

...

  • CVIS-status-2024-fall.pptx It is expected that all meeting participants have read the compliance statement. Every meeting will start with a reminder.

  • Every meeting will start with appointment of note taker. Notes can be on-line, or off-line and if so mailed to moderator within 24 hours. Fair scheduling, i. CVIS-file-repoe. all should take turn. A reason for not taking it is if one expect to speak much at the meeting.

  • Strive for making signal objects reusable by other signal specifications. 

Specification development page

The writing of the signal specifications are done at https://github.com/COVESA/commercial-vehicle-information-specifications.

Welcome and Compliance statement

Welcome to the COVESA CVIS 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.

...

  • Strive for making signal objects reusable by other signal specifications. 

Specification development page

The writing of the signal specifications are done at https://github.com/COVESA/commercial-vehicle-information-specifications.

Welcome and Compliance statement

Welcome to the COVESA CVIS 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 Template

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • xxx
  • General topics:
    • Open Pull Requests CVIS
    • Issues CVIS
    • Discussions CVIS
  • Other
  • Prioritized topics for next meeting


Meeting notes  2025-05-05

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • HIM configurator updates
      • Supports calling the vspec tool from both Linux and Windows
      • vspec tool overlays supported
      • overlays on instantiated nodes supported
    • Overlays creator tool added
      • Pick parts of tree from a YAML tree, apply to another tre using HIM configurator overlays.
    • VSS-core2 added. Uses overlays/instantiation overlays.
      • VSS-core uses Global / Local variation points.
    • AMM short f2f meeting?
      • Can we identify a suitable time?
        • We meet Wednesday 13.30 at the room where Ulf will present "An Automotive API and Data Model that caters to all types of vehicles" at 14.00.

Meeting notes  2025-04-23

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:

    • Traton presents ACEA PoC

      • Postponed for next meeting

    • HIM configurator update

      • Overlays support

      • Make file usage removed

Meeting notes  2025-04-07

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Continue the Truck tree analysis.
      • The discussion led to the understanding that any single signal is a potential candidate to be removed, and that there must be a practical solution to that. The VariationPoint feature can do it, but it is not a scalable solution if large numbers of signals needs to be removed.
        • Different options were discussed, both subtractive (removal from VSS-core) and additive (pick from VSS-core).
        • The discussion will continue, and hopefully different solutions will be proposed.
    • Overview HIM configurator features.
    • Review of the CVIS status AMM presentation (draft version).
    • Ted: Regulatory signals

Meeting notes  2025-03-24

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • HIM configurator  generated Truck tree analysis
    • AMM presentations
      • "Status update of the Commercial Vehicle Information Specifications (CVIS) project" is scheduled 04:20 - 4:40pm on May 14
      • "An Automotive API and Data Model that caters to all types of vehicles" is scheduled 02:00 - 2:25pm on May 14
      • Paul: It is possible to have additional break-out meetings. Please consider the need for this until next meeting.
    • Overview HIM configurator features
      • Moved to next meeting.
    • HIM configurator syntax
      • Sergej proposed that the vspec2 syntax is extended to support Google template syntax, thus enabling logic operations.
      • Ulf proposed that this logic is implemented using any computer language in a tool that generates the JSON based input files to the HIM configurator, and keeps the "simpler" syntax in the vspec2 files.
      • Both proposals can exist in parallel, they will lead to the same end result - configured signal trees in the formats set by the used VSS-tools exporters.

Meeting notes  2025-03-10

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Him configurator on Windows
    • HIM configurator road map
    • AMM presentation
    • VSS-core - no compromises
      • The VSS-core tree is vehicle type agnostic. The HIM configurator configures it into a vehicle specific tree.
      • This concept is applicable to most vehicle types like Car, Truck, Bus, Van, etc.

Meeting notes  2025-02-24

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • xxx
    General topics:
    • Open Pull Requests CVIS
    • Issues CVIS
    • Discussions CVIS
  • Other
    • VSS-core analysis
      • VSS-core analysis.pptx
      • cvis.yaml
      • Look at the cvis.yaml file for ideas on what can be "pruned". Create a PR directly on Github, or a list that we can discuss at next meeting.
    Prioritized topics for next meeting

Meeting notes  2025-02-10

...