...

• 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-08-10

• F2F meeting for service API and tooling.
  • Notes
    • Adnan: preference mid of november
    • Sebastian: ETAS would be able to organise event
• AMM
  • Notes
    • Sebastian: Shall we extend half a day with session?
    • Paul: we have chance to go for Monday/Tuesday/Friday.
    • Paul: Submit idea for AMM until end of august.
• Service capabilities, name.
  
  • Notes
    • Adnan: Vehicle API Hub for SDV
    • Ted: Vehicle Defined Interfaces
    • Sebastian: General Vehicle API
    • Sebastian: Common Vehicle Interfaces
• How VSS is used?
  • Notes
    • Ulf: Last AMM we presented Kuksa and ViSS.
    • Paul: Others as well could provide input. How to motivate?
    • Adnan: We also have to understand what is the need. Companies should start explaining.
    • Sebastian: challenge is not lack of material, but a way how to present this.
    • Stephen: We have documentation, we just have to do the work.

Meeting Notes 2023-07-27

• Information: Erik on vacation August 1st -Sept 1st
• VSS review Monday Jul 31, 2023 ⋅ 3pm – 7pm (Central European Time - Berlin)
  • meet.google.com/eox-sqze-byx
  • Vehicle Signal Specification Review Workshop (Access restricted)
  • Stephen: Board request to do a review, first meeting next week. There are some old categories that require review.
  • Erik: Better to discuss/define principles rather than explicit existing signals.
• Diagram/Document Storage (Stephen)
  • There has been some discussion before, but with the rise in reuse of our materials as shown last week we need to move towards a solution to encourage reuse. I'll be creating a git rep for the Data Architecture/Infrastructure work, but there is the bigger picture of the Data EG, AOSP and Covesa as a whole. Illustration where does someone go to get current Covesa Data Expert Group scope diagram?
  • Erik: There have been discussion in the past, possibly use github rather than wiki. I created a draft (restricted access) at https://github.com/COVESA/data-expert-group some time ago
  • Halim: Could generate from git
• Interface/API way forward
  • Adnan:
    • Have one stream on IFEX, clear goal to define scope of IFEX.
    • One part on catalog/operations, also covering the service API. Discussion can start happening. Try to skip the "catalog" name
    • Need to find a catchier name, start looking at proposals
  • Stephen: Putting in context is useful
  • Adnan: With IFEX i could glue things together
  • Adnan: Would be good if Halim could collect some areas that would be use to describe
  • Adnan: Unsure if IFEX is mature enough. We need to have a definition of "final result"
  • Erik: Even if we trust IFEX concept, we should define the "input format" or "output format" that shall IFEX needs to work with
  • Adnan: Contribution to a Data Expert Group blogpost would be very welcome. Inform Adnan if you are interested.
• Way forward:
  • Paul: Maybe use VSC timeslot ys for regular meetings
  • Halim: We can start w Monday schedule, decide on other afterwards. Fridays would be better.
  • Adnan: Paul to drop Doodle poll
  • Pual: next meeting on this topic Monday 31st 19.00 CET 10AM Pacific (VSC timeslot and link)

...