Page History

...

Use them as base for the discussion

Erik 2023-07-18: Trying to provide a more detailed agenda proposal, to be discussed at DEG meeting this week

• Welcome and introduction (10 minutes)
• 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?
  • Reference implementations
    • Do you think COVESA shall be active doing reference implementations for Client/Servers/SDKs?
  • 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" and "north" i.e. support both for reporting actual value and for setting wanted value.
    • If so, focusing on thin API (like VISS and KUKSA.val) or fat (one method per signal)
  • Relationship to COVESA-AUTOSAR Vehicle API discussion

...