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.

General Agenda

• Welcome and Compliance statement

Welcome to the COVESA Common Vehicle Interfaces 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:
  • Capabilities - create a list of common vehicle capabilities/function to be expose via api
  • IFEX (Interface Exchange) - a general interface description and transformation technology 
  • uServices - definition of common vehicle services usimg protobuf as the interface definition language
  • Vehicle Signal Specification over Data Distributiion Service - 
  • Vehical Information Service Specification (VISS) -  a service for accessing vehicle information, signals from sensors on control units within a vehicle's network. It exposes this information using COVESA Vehicle Signal Specification (VSS).
  • Vehicle API - will expose vehicle data as defined and described by COVESA's Vehicle Signal Specification to a  variety of agreed upon touch-points in and out of the vehicle
• Prioritized topics for next meeting

Meeting notes  2023-10-17

• Prioritized Topics:
  • AMM Review

• Agenda discussion - anything that needs to be added?
• AMM review
  • Define scope of each project,
  • project interconnectivity/interplay
  • Participants
  • Action:  Paul to start the above
  • Action:  Ford to find rep
  • Action:  Reach out to Honda
  • Action:  Reach out to Hyundai
  • Proposed:  once a month Asia friendly model.  Do more discussions in writng.  Slack, GitHub, Wiki...
  • Direct contribution needed
  • IFEX looking at translation to uServices and vice versa
  • Action:  GM to meet with Mbitiion re IFEX
  • Catalog → OpenAPI and/or uServices and/or IFEX or HIM
    • Simple easy to follow.  Guidance to follow.  How to document?
  • Blueprint for how API's should be described
    • How granular?
    • Governance
    • Action:  Get Google documentation
    • Coherency, safety security, performance, access control
    • Action:  Start outline 

• Prioritized Topics:
  • Capabilities
  • IFEX
  • uServices
  • DDS
  • VISS
  • HIM
  • Vehicle API 
• Prioritized topics for next meeting

Meeting notes  2023-09-05

• Prioritized Topics:
  • Discussed How to handle this Common Vehicle Interfaces meeting.  Agreed to start listing service capabilities.
  • Action Item: Halim Ragab to start a Capabilities page and Usecases page
  •  AMM:
    • Block out time for discussions
    • Discuss Use cases, why common vehicle interfaces matter?
      • Integrating with the vehicle 
      • Mapping to VHAL
    • Capabilities
      • Report on and discuss page/doc
    • Meet with Google to discuss integration via common interfaces/services
      • Create good example and present prior to AMM