Versions Compared

Old Version 282

changes.mady.by.user Sabine Hofschen

Saved on

compared with

New Version 283

changes.mady.by.user Sabine Hofschen

Saved on

Key

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

...

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.


Meeting Notes 2025

Agenda candidates for 2025-07-21

  • Participants:
  • info discussion vehicle data on July, 17.

  • COVESA AOSP blog
  • AOSP App host.
  • Droidcon planning.
  • AMM working sessions planning.
  • Entertainment/CARMA discussion next steps - COVESA back button?
  • see below potential next topics.

Minutes 2025-07-14

  • Participants: COVESA, GM, Appning by Forvia, Ford, BMW, Paradox Cat, Allianz
  • Fall AMM planning
    • technical call for papers coming soon.
    • status update in the beginning, working sessions then.
    • to be discussed: hybrid meetings.
    • working session doesnt need to have a tech talk included.
    • ask Forvia who are having a close subsidiary, for support / discussion on what could be organized,
      in a vehicle?
    • demo what is already possible, show apps downloaded from the app store → to enable devs in the end:
      idea: COVESA data playground for data points we agree upon before. Use case specific overlays like for fleet.
      challenge: OEM offering of data points + see below Vehicle data.
    Ideas for a COVESA AOSP blog
  • AOSP Host discussion.
  • Vehicle data next steps discussion.
    • looking for an open - source solution, e.g. VSS/VHAL mapping.
    • as of today, only speed and a few others are available → devs cannot ideate on anything.
    • find the use cases on which to open up for devs.
    • idea: This would be a great opportunity to make vss available to apps directly, then we can define our own permissions.
    • idea: this group to do a joint specification on the data side which goes through list of properties, their specifics. then develop alongside this. 
    • work in progress (mapper, permission model) (Jan). → for that, a COVESA SDK would be needed.
    • → follow-ups together with ParadoxCat and Elektrobit.
  • not discussed:
    How to find the next big topic for us, candidates (from AMM Berlin presentation):



...