/
Interface Blueprints

Get Involved

◎ COVESA Community Calendar
◎ COVESA Getting Started
◎ Understanding and Engaging in COVESA
◎ Project Launch Process

Groups and Projects

Groups and Projects continued...

◎ Vehicle Signal Specification (VSS)
◎ AOSP App Framework
◎ Commercial Vehicle and Fleet Group
◎ Generative AI Group
◎ Central Data Service Playground

◎ Vehicle Data Model
◎ Cyberecurity Group
◎ In-Vehicle Payments Group
◎ Connected Safety
◎ All Groups and Projects

Resources

◎ COVESA Events
◎ Industry Events 2025
◎ Antitrust and Open Statement
◎ Member Visibility

Join/Sign Up

◎ Join COVESA
◎ Sign Up for Member Newsletter
◎ Request Wiki Account
◎ Request Access to Slack

Interface Blueprints

Feb 13, 2024

What makes good apis?

Criteria for interfaces?

Design approach 1st?

 

Hierarchy organization

How we organize apis

Reuse existing work e.g. ???  https://cloud.google.com/apis/design 

Common design patterns

  • Discovery

  • Versioning

    • Backwards compatibility

    • Lifecycle

    • Granularity e.g. service, entire tree VSS

  • Thick and Thin Data API

    • How works with VSS.  How grouped

Types of interfaces e.g. data, rpc

  • when do use?

  • Interface classification/level

 

Document VISS and Kuksa/Implementation decisions against blueprints.