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.

• 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.

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

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.

• 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

• Compliance statement

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

• Prioritized Topics

  • VISSv3.1 release candidate 0

    • The COVESA VISS project has released the VISSv3.1 release candidate 0.
      https://github.com/COVESA/vehicle-information-service-specification/releases/tag/v3.1rc0
      Comments will be collected at the VISS GitHub repo
      https://github.com/COVESA/vehicle-information-service-specification/issues/114
      The review period will be open until March 15.

  • The VISS reference implementation (https://github.com/COVESA/vissr) has been updated to support v3.1 (#issue100 is not implemented) so it is possible to evaluate v3.1 on running code.

• Compliance statement

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

• Prioritized Topics

  • VISS roadmap discussion continued

  • Unified Diagnostic Services: discussion on Slack #vss channel

  • VISSR release 1.0

• Compliance statement

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

• Prioritized Topics

  • VISS roadmap discussion

  • Meeting winter recess

    • Meetings Dec 8, Dec 22 and Jan 5 are cancelled. Next meeting Jan 19

• Compliance statement

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

• Prioritized Topics

  • VISS roadmap discussion

• Compliance statement

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

• Prioritized Topics

  • AMM presentation

    • Will add an introductory slide on VISSR

  • VISS road map

  • WG meeting Oct 27 cancelled

• Compliance statement

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

• Prioritized Topics

  • Inquiry Regarding Transport Security in VISS-Core (Section 6.1) · Issue #96

    • Isaac added a comment to the issue after it was discussed by the WG. The issue will soonn be closed.

  • Send timestamp · Issue #100

    • The proposal from Volvo Group is relevant and the proposed solution looks ok. The issue will be revisited when work on a next VISS version is started.

  • VISSv3.1 proposal: Support the HIM Data profile.

    • Backwards compatible with VISSv3.0

    • Provides comprehensible support for multiple trees

      • VISSv3.0 uses up to three trees: Vehicle/Server/Types

      • Separate trailer tree is likely to be needed in CVIS.

      • Opens the door for all sorts of vehicle types.

    • A v3.1 draft is available at the v3.1 branch.

    • Feedback is welcome. The proposal will be presented at the coming AMM.

• Compliance statement

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

• Prioritized Topics

  • Inquiry Regarding Transport Security in VISS-Core (Section 6.1) · Issue #96

    • Short discussion Isaac, Ulrich, Ulf. To be continued in 2 weeks.

  • Send timestamp · Issue #100

• Compliance statement

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

• Prioritized Topics

  • ACEA-COVESA MoU

    • https://www.acea.auto/press-release/auto-makers-and-covesa-sign-memorandum-of-understanding-to-advance-interoperability-in-commercial-vehicles/

  • VAPI – A connectivity agnostic Vehicle API for access to signals and services

    • https://raw.githack.com/UlfBj/vehicle-api/main/spec/VAPIv1.0.html

  • Out-of-order Set requests

• Prioritized Topics:

  • Allow TLS to be configurable (AUTOSAR model)?

    • What kind of configuration shall be supported?

    • How does a client discover what configuration is needed?

    • To discuss this further the AUTOSAR configuration alternatives need to be presented to this group.

      • Ulrich and Richard will look into trying to obtain relevant information

  • The OpenSDV-Initiative presentation from last meeting was opened and discussed. The mentioned lack of support in VSS/VISS could be features to address in a next version of VISS.

  • Summer recess

    • Cancel meetings July21 and Aug 4. Restart on Aug 18

• Prioritized Topics:

• Discuss VSS/VISS issues mentioned in https://wiki.covesa.global/display/WIK4/Interface+Definition?preview=/53510150/142213755/OpenSDV-initiative_intro2COVESA.pdf

• Summer recess

• Meeting cancelled due to low participation.

• Prioritized Topics:

  • Initiate ideation and planning of what is next in the pipe

  • Summer recess

    • Continue at least through June before the summer recess starts.

• Prioritized Topics:

  • Review RC2 comments and actions

    • PR#93, Filter combinations update merged. AUTOSAR will be notified about it.

  • V3.0 release decision

    • If no comments on PR#93 by Thursday the V3.0 release will be published.

  • Skip meeting May 12?

    • If v3.0 is released then meeting is skipped.

• Prioritized Topics:

  • Review of AMM draft presentation (see link in meeting notes below)

• Prioritized Topics:

  • Review of VISSv3.0 release candidate 1.

    • Updated from AUTOSAR comments, one outstanding comment to discuss.

      • COVESA-VISSv3.0-Core-RC1_comments.pdf contains AUTOSAR comments

      • https://github.com/COVESA/vehicle-information-service-specification/issues/62 contains summary of comments and actions taken.

      • Action on comment on file transfer: Keep as is, add sentence that gives a rationale.

    • Wonsuk readability updates.

  • VISSv3.0 release planning

    • Create RC2, after checking with Wonsuk. Leave open for 2-3 weeks.

  • AMM presentation

    • "VISS and VISSR projects” is scheduled 02:00 - 2:25pm on May 15

      • Draft presentation: Spring AMM 2025 - Day2_200_Bjorkengren_VISS-and-VISSR-projects.pptx

• Prioritized Topics:

  • Review of VISSv3.0 release candidate 0 updates.

    • Merged to main. See log at Issue #48.

    • Create RC 1?

      • Decision taken to create RC1 from current main branch, with a review period until March 28.

• Prioritized Topics:

  • Review of received VISSv3.0 release candidate 0 comments.

    • AUTOSAR Feedback.pdf

    • VISSv3 Feedback 3-3.pdf  Received 2025-02-20

    • RC0-review-comments.docx Contains supplementary comments to 2025-02-20.

    • In-line error reporting

    • Review comment implementations

  • AMM presentation planning

  • VISSR status

    • Docker issues

    • Feeder template

  • Try to get VISS into other projects, e. g. Eclipse?

• Prioritized Topics:

  • Review of received VISSv3.0 release candidate 0 comments.

    • See comments at https://github.com/COVESA/vehicle-information-service-specification/issues/48

    •  Core with AUTOSAR comments.pdf

    • Transport Examples with AUTOSAR comments.pdf

    • Core with AUTOSAR comments-2.pdf

  • AMM presentation planning ← To be discussed at next meeting

  • VISSR status ← To be discussed at next meeting

  • Try to get VISS into other projects, e. g. Eclipse? ← To be discussed at next meeting

• Prioritized Topics:

  • Review of VISSv3.0 release candidate 0: https://github.com/COVESA/vehicle-information-service-specification/releases/tag/v3.0rc0

  • Review of invite message for VISSv3.0 review

  • Review list of reviewers

  • Decision taken to distribute the invitation for review of the release candidate 0.

• Other

  • VISSR status

    • Development of a test client that will be started together with server and feeder by a script to automatically run a set of requests over the different protocols.

• Prioritized Topics:

  • Error code PR

    • Ted: Error message list should be labelled non-exhaustive.

  • VISS adoption

• Other

  • AUTOSAR meeting about VISSv3.0 error codes 241212

  • Christmas recess: Dec 23 and Jan 6, back Jan 20

• Prioritized Topics:

  • Data compression PR

    • Decision to merge

  • VISSR pre-built image?

    • Ulf, Steve and Peter to look at what can be done.

• Prioritized Topics:

  • Data compression PR

    • Ulf will update with sequence diagram etc to make it clearer.

  • Explainer issue

    • Peter will look at it.

  • validate keyword revisit

    • We will ask for an improved make file that includes support for "-e newKey" usage.

  • VISSR file transfer support merged

  • Paul asked for VISSR documentation on a simple to follow Hello World example on how VSS can be used.

    • Ulf will look into this, and also talk to Steve about CDSP VISSR usage.

• 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. 

• 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.

• 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

• 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

• Prioritized Topics: 

  • Review JSON schema addition

  • Review PRs

• Other

  • Review AMM presentation draft

    • Uploaded: https://drive.google.com/drive/folders/1sft7AGaBsmvBBtNRaduNBF7mi2_0mqTU

• Prioritized Topics: 

  • Review JSON schema addition

  • Review PRs

• Other

  • Review AMM presentation draft

• 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.

• 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).

• 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)?