This page intends to contain the agenda for next VISS meeting (Mondays 16.00-17.00 CET) and notes from previous meeting. Below 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.

Policies

• 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. e. all should take turn. A reason for not taking it is if one expect to speak much at the meeting.

• Strive for backwards compatibility. Non-backwards compatibility, anyone can ask for a voting, requires 2/3 of votes to be accepted.
• VISSR deep technical discussion should be handled on the VISSR Slack channel and its Github Issues page.

Specification development page

The writing of the specification is done at https://github.com/COVESA/vehicle-information-service-specification.

Welcome and Compliance statement

Welcome to the COVESA VISS 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 VISS
  • Issues VISS
  • Discussions VISS
  • VISSR information
    • Major PRs
    • Q&A
• Other
• Prioritized topics for next meeting

Meeting notes  2024-11-11

• Prioritized Topics:
  • Data compression PR
  • validate keyword revisit

Meeting notes  2024-10-28

• Prioritized Topics: 
  • VISS3.0 roadmap and schedule
  • validate keyword: should we try to get VSS to make it a 1st class citizen? Let us try.
• Other
  • ACEA interest in VISS and HIM
    • Presented at a COVESA - ACEA FMS meeting Oct 23. 

Meeting notes  2024-10-14

• Prioritized Topics: 
  • Review VISS PRs
  • VISSR v3.0 status
    • Master branch is now for v3 development, and a v2.0 branch is created for the VISSv2.0 release.
    • Initial v3.0 features merged - multiple tree support, server capabilities tree added, plus a few more features.
• Other
  • VISS/SDV meeting summary
    • No real progress on alignment
  • VISS direction?
    • EU data act?
    • Broader applicability, trucks etc.
    • Overview description? Explainer. Might need some update. Write a white paper?← Ulf will start on this.

Meeting notes  2024-09-30

• Prioritized Topics: 
  • Review VISS PRs
    • Decision to merge File transfer PR
• Other
  • VISS/SDV meeting in Lund Oct 7@13.00 CET
    • Arranged by Thomas Spreckley
  • AMM comments
    • https://drive.google.com/file/d/168y0h8mE3udeRAX1sUkZqnehQac-I1CC/view?usp=drive_link

Meeting notes  2024-09-16

• Prioritized Topics: 
  • Review VISSR PR: https://github.com/COVESA/vissr/pull/43
    • Not discussed due to lack of time
  • Review VISS PRs on Server capabilities and File transfer: https://github.com/COVESA/vehicle-information-service-specification/pulls
    • Discussion will continue at next meeting. 
• Other
  • AMM presentation and presenter
    • Ted will add VISS intro and Autosar deployment info

Meeting notes  2024-09-02

• Prioritized Topics: 
  • Review JSON schema addition
  • Review PRs
• Other
  • Review AMM presentation draft
    • Uploaded: https://drive.google.com/drive/folders/1sft7AGaBsmvBBtNRaduNBF7mi2_0mqTU

Meeting notes  2024-08-19

• Prioritized Topics: 
  • Review JSON schema addition
  • Review PRs
• Other
  • Review AMM presentation draft

Meeting notes  2024-07-08

• Prioritized Topics: 
  • Review Payload Encoding document update
    • https://raw.githack.com/COVESA/vehicle-information-service-specification/main/spec/VISSv2.x_PayloadEncoding.html
      • It is appropriate to include the entire proto-file in the spec.
      • The code for the actual payload encoding/decoding should not be part of the spec, but if there are implementation issues that could lead to non-interoperabe implementations that should be addressed in the spec.
  • https://github.com/COVESA/vehicle_signal_specification/issues/749
  • Status update presentation at the AMM
    • Decision to do it. Peter and Ulf volunteer, anyone else is welcome to join.
  • Adding encoding into AsyncAPI?
• Other
  • Summer recess. Skip next meeting July 22 and Aug 5. Next is Aug 19.
  • AUTOSAR - Paul checks if meeting with this group.

Meeting notes  2024-06-24

• Prioritized Topics: 
  • Roadmap creation

• General topics:
  • Open Pull Requests VISS
  • Issues VISS
    • Three part documentation proposal
      • Steve: In Transport doc - mention for each protocol what is the difference to primary description.
      • Versioning of Payload encoding?
      • Decision: Go with the three document structure (can be reversed if found bad).

Meeting notes  2024-06-10

• Prioritized Topics: 
  • Roadmap creation
    • New features for the next VISS version, continued discussion
      • Payload defintions instead of transport protocol definitions could be the first feature to add?
        • Keep the documentation structure with two docs - CORE and EXAMPLES?
        • How define the payloads? For each method (get/set/..), define the mandatory and optional payload fields of request/response/subscription messages.
        • Serialization definition? JSON in VISSv2. Needs more precise definition?
          • Protobuf serialization definition in proto file (https://github.com/COVESA/vissr/blob/master/grpc_pb/VISSv2.proto)?
      • File transfer support? Download/Upload?
      • More filters - event when buffer is full, ...
    • VISSR issues
      • Polish documentation. Attract more users?
        • Docker containers, open data sets, 
      • AGT not well integrated with Docker
      • Complicated to generate a binary VSS tree. Pre-built?
      • Concurrency bugs in server?
    • ISO standardization of VSS (VISS)?

Meeting notes  2024-05-27

• Prioritized Topics: 
  • Roadmap creation
    • New features for the next VISS version, continued discussion
      • Payload defintions instead of transport protocol definitions could be the first feature to add?
  • Other
    • Low attendance due to US holiday.

Meeting notes  2024-05-13

• Intro: Names, company, contribution?
• Prioritized Topics: 
  • Roadmap creation
  • New features for the next VISS version 
    • VISS tied to VSS and passenger vehicles. As there is a need for additional information models, maybe adapt for Hierarchical Information Model (HIM) proposal 
      • ATA TMC (several attendees from their Data Science team in attendance) express interest in additional data models
      • Question on how to accommodate VSS within HIM, explained as a higher level wrapper and backwards compliant
        • Similar rules to be applied to the other data models
        • Resistance to extend VSS beyond vehicle signals
        • Wally: either HIM, VSS overlays or perhaps a third approach could work for ATA needs
          • Suggest we define what we want the model to support to evaluate
          • Stephen: is the first goal the semantics side - metadata?
          • Diagnostics capabilities, trailer or specialty equipment are the data models being discussed
        • Peter: there are existing services work within COVESA that need alignment with this
        • Ulf: we may end up with merging of ideas or competition and see which prevails 
        • OpenAPI approach wasn't conducive to automotive purposes, hence VISS
    • Define payload that can be transported across multiple protocols, could possibly support OpenAPI (would need to add subscriptions) 
  • Suggest we solicit input from AutoSAR (Erik) and BMW on Android (Adnan or Andre)
• Meeting split between VISS (specification) and VISSR (Reference implementation of VISS)
  • Informational update on VISSR on regular call, deep technical as time allows or call participant warrants otherwise details will be on slack & github
  • Also welcome questions from participants, can inform the specification work as well
  • Tagged releases
• VISSR branching/release strategy for next VISS version
• Policy notes reviewed
  • Paul/Stephen: Reminder to please add company name in your display name.
• CVIS Charter