This page intends to contain the agenda for next meeting and notes from previous meeting. 

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

Agenda  2023-11-14

Prioritized Topics:

• Capability Lists Review

Meeting notes  2023-11-7

• Attendees
  • Adnan Bekan
  • Halim Ragab 
  • Magnus Feuer 
  • @Mellisa Morris
  • Richard Fernandes
  • Shareef Hakim 
  • Stephen Lawrence 
  • @Swetha Patil
  • Ulf Bjorkengren 
• Prioritized Topics:
  • Provide overview and background to new attendees
  • Re-sync on next steps
  • Discussion of how best to align
• Action Items
  • Paul Boyes and others Identify diagram(s) to serve as simple stack diagram for group reference.  
  • @OEMs/Everyone  Bring capability lists to next weeks meeting in whatever format you have them.  
    • Current lists include:
      • Common Vehicle Interfaces - Capabilities (you may add another section/create another page, link... here.  The main thing is to provide your list)
      • https://github.com/COVESA/uservices
  • @everyone review previous work
    
    • Data Expert Group Workshops - Interface Pillar Alignment
      • Presentation Links within:
        • IFEX-quick-what-and-why-v2.0.pdf
        • COVESA VSS OpenAPI
    • AMM Presentations about interfaces
      • From Concept to Reality:  How Data-Centric Vehicle APIs Shape Software-Defined Vehicle 
      • The Hierarchical Information Model (HIM) and an Interface Using It
      • Beyond the Car - Advancing Commercial Vehicles - The Transforming Software to Meet the Needs of Owners, Drivers and Fleet Managers
      • uServices - A Step towards a standardized vehicle Interfaces for SDV
    • Links and text posted during meeting
      

      • Chat

        You (Nov 7, 2023, 8:12 AM)
        https://github.com/COVESA/uservices
        https://github.com/COVESA/ifex
         
        Ulf (Ford)  (Nov 7, 2023, 8:15 AM)
        https://github.com/COVESA/hierarchical_information_model
         
        Stephen Lawrence (Nov 7, 2023, 8:23 AM)
        https://wiki.covesa.global/display/WIK4/Central+Data+Service+Playground
         
        Stephen Lawrence (Nov 7, 2023, 8:52 AM)
        Original diagrams from MBition https://wiki.covesa.global/display/WIK4/Vehicle+Service+Catalog+%28VSC%29+-+Common+Interface+Description+Model?preview=/22643862/22644665/covesa_amm_2022_-_vsc.pptx#VehicleServiceCatalog(VSC)CommonInterfaceDescriptionModel-PresentationsfromApril2022AllMemberMeeting
         
        Stephen Lawrence (Nov 7, 2023, 8:59 AM)
        There is some focus on IDLs as well in that presentation but that is because at the time (start of project) people expected it to be addressed.

Meeting notes  2023-10-24

• Prioritized Topics:
  • Gunnar looking at converting uServices
  • Blueprints
    • Looked at https://apiblueprint.org/
    • uServices - look to extract patterns, look at options when Halim back
      • business logic separated from deployment
      • Number of rows... Number of seat rows?  Constant or set at design 
  • Ford - Meet Shareef/Ford at Nov 7 during regularly scheduled meeting

Meeting notes  2023-10-24

• Prioritized Topics:
  • Blueprint
    • https://cloud.google.com/apis/design
    • Need to capture high level "what matters"
    • Stay on high level
    • Align with VSS structure
    • AI: Adnan to put together outline on wiki
  • Ford - Meet with on Nov 2
    • Blueprint
    • Catalog/Capabilities
    • Meet Nov 2 from 9-10am ET
  • BMW to provide feedback on IFEX
  • Apple
    • Can we get API documentation from Apple?
    • AI:  Halim and Adnan to work internally
  • Google
    • Followed up 
    • We need to get back to them when we have something
  • Automotive API (formerly Vehicle API)

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