Page History

...

• Welcome and introduction (10 minutes)
• Round the table - how do you use APIs today?, what are your general expectations
• BMW Idea: OpenAPI/AsyncAPI presentation
• Gunnar: Update on IFEX and VSC
• GM/Halim: GM collaboration and contribution to Vehicle Services
  • VSC / IFEX License discussion. Is it possible to switch to Apache?
• RTI: Expanding VSS beyond present footprint
• Discussion on work-areas for the interface pillar. Target is to identify the work-areas and how important they are considered by participating organizations. Some possible work-area proposals below
  • Common IDL
    • Is there a value in agreeing on a "common IDL format" (existing or new) that could be used for describing services?
    • If so, why? Some possible reasons:
      • Foundation for a common catalog
      • Foundation for implementation of reference cliensts/servers/SDKs
      • Simplifies translation/mapping between other IDLs,
  • IDL translation capabilities
    • What type of translations are of interest?
    • What do you need? Just a specification (like ARXML to Protobuf), or actually also tooling?
    • What are you willing to work-on?
  • Common service catalog
    • Do you see a value in a common catalog for services (like for example FOTA, diagnostics, ...)?
    • Do you think it actually is feasible? What is needed for success? The catalog part of VSC has so far not really been any success!
    • Do you see any candidate areas where chances of success is bigger than for others?
  • Service Capabilities as an abstraction mechanism (input from Stephen Lawrence )
    • MBition, BMW and GM have all expressed interest in defining interfaces (in a technology agnostic manner) that describe 'basic' capabilities (e.g. move seat to X) on which value added services are built and can be reconfigured.
    • Just as VSS can be considered an abstraction mechanism for data, a Service Capabilities Catalog could be considered an abstraction mechanism for VSS+methods.
    • Do we see value in discussing Capabilities as an abstraction mechanism? Two potential topics come to mind:
      • Ground discussion in likely deployment scenarios. I mean that largely as a verticality discussion in the stack as to what it may be interfacing too (e.g. Vehicle API) rather than a transport or protocol selection discussion. In this way powerful, but overly complex approaches can be avoided if the problem space is simpler. It also naturally links discussion to other work streams in Covesa such as Vehicle API and data architecture.
      • Grouping Capabilities into Catalogs - this is related to the Service Catalog topic as the interfaces for the capabilities may be bundled into functional groups that form the basis for a catalog that is either unique to the provider (internal + trusted partners) or in its more open form a cross industry catalog. I list the topic separately from a Common Service Catalog as if a decision to not pursue a Common Catalog is made Capabilities remains a useful organising concept.
    • It is also related to the VSS Relationship topic as VSS should be the natural data model for the interface data.
  • Reference implementations
    • Do you think COVESA shall be active doing reference implementations for Client/Servers/SDKs? Or is that better handled by other downstream projects (like W3C and Eclipse SDV)
      
  • VSS relationship
    • Shall COVESA define one or more APIs (using the "Common IDL") for accessing VSS data?
      • As a real API definition, or just as requirements on an API definition. Potential requirements include:
        • Support for atomic read/write/subscribe of multiple signals
        • Support for both "south" (the one providing values or actuating requests) and "north" (the one reading values and requesting actuation) i.e. support both for reporting actual value and for setting wanted value.
        • Metadata to be provided (like timestamp)
        • Error codes or scenarios - why was an actuation not fulfilled?
    • If so, focusing on thin API (like VISS and KUKSA.val) or fat (one method per signal)
    • Need for possibility specifying services that references VSS-signals, for example service to set 3 VSS signals in a single call
  • Relationship to COVESA-AUTOSAR Vehicle API discussion
• Target: Agree on what is feasible to focus on in the short term
  • What is possible to achieve until Spring AMM
• Way forward
  • F2F September - next to ETAS connection?
    • If so - time and agenda
  • Session at AMM (Monday?)

...

Notes from Ulf

...