...

• 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-06-22

Discussion Topics

• F2F - Data Expert Group Workshop Face to Face: July 18-19, 2023 Cologne, Germany - Interface Pillar Alignment
  • Current status; dates, venue, participants, ...
    • COVESA Board 19-20 July
    • Alignment w AUTOSAR/SOAFEE/COVESA 18th
  • Discussion (FTI Paul Boyes )
    • Participation list updated. Will Ford/Ulf participate?
    • What is reason to let DEG and Board meeting overlap
    • Would having the DEG discussion on Monday be an option?
    • Lets continue discussion in Slack
• Ted: Should we have a JSON viewer to allow easy navigation of the catalog.
• Stephen: DEG Git repository - reluctant to create a big DEG Architecture repo. We need somewhere to put the markdown. Maybe "data-arch-doc".
  • Will prepare a proposal

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

...