Meeting

...

Agenda

• Welcome and Compliance statement

...

• Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
• Prioritized topics for next meetingHIM/IFEX to be discussed June 15th
• Date for next monthly report discussion

Meeting Notes 2023-06-

...

15

• Discussion Topics
  
  • Stephen presented Design Pattern / Data Architecture documentation proposal 
  • HIM & IFEX
    • Ulf: Service taxanomy can possible be shared, but serves partially different purposes.
    • Ulf: HIM gives a possibility to describe procedure signatures, similar to how VSS describe signals, which then can be used by interface design like VISS
    • Ulf: I think we need a RPC model
    • Adnan: Service definition could reference other models, like referencing VSS position
    • Gunnar: Are you talking about abstract service/function definition, or more specific that can be generated to real service implementations/stubs
    • Adnan: I see VISS like an API definition, IFEX more as an IDL that be converted to a lot of things
    • Gunnar: If there is VISS API that supports RPC, it could be generated from IFEX
    • Gunnar on IFEX:
      • Hierarchical namespace
      • A concept "interface" that specifies methods, properties, ... A combination of things we intend to expose that we can use to define a callable API
      • Namespaces of methods often related to software architecture, possibly we could have multiple hierachies.
    • Gunnar: We need to identify what is missing
    • Adnan: Has studied IFEX VSS proposal, wants something more standardized compared to Franca, like Yaml/JSON-based. A framework that allows to import multiple inputs, like ARXML, Android, and generate to various formats.
    • Adnan: Possible technical track on next board f2f-meeting, (Cologne 19-20 July, SOAFEE/AUTOSAR 18th)
    • Gunnar: How we can support AUTOSAR in IFEX

Meeting Notes 2023-06-08

• Prioritized topics for next meeting
  • HIM&IFEX to be discussed June 15th

Meeting Notes 2023-06-01

• Discussion

• Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

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
  • "Ulf/HIM proposal" (Hierarchical Information Model)

...

• • • Discussion:
      • Ulf: Could be soft started as VSS subproject
      • Ulf: Do not see HIM file as input to vss-tools, it is the server that consumes it, it still work with initial trees
      • Erik: Suggestion:
        • Let Paul create a HIM repo (M/W/X)
        • Ulf to start working with repo, describe motivation, idea, and suggested increments/roadmap and basic architecture
          • Describe what problem we intend to solve, why do we create it.
        • Then let DEG discuss at regular interval, keep VSS meeting informed
        • When mature we can discuss how to involve more people
      • Decision: OK for Paul to create repo
      • Discuss relationship to VCS when we have the parts above ready
  • Adnan: SDV and Eclipse
• Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
• Prioritized topics for next meeting
Date for next monthly report discussion

Meeting Notes 2023-05-11

• Welcome and Compliance statement

...