Page History

...

Historical note: the minutes for the previous project, the CVII Tech Stack, can be found here: CVII Technology Stack meeting notes

11th

...

December 2024

Agenda:

• Status sharing including Playground Kanban

...

• Heads up on Rami's VSS Data Modeling for NoSQL Document Databases proposal
• Taking stock and thinking ahead to early 2025

Minutes:

• No meeting. Only Steve and Iyaz joined.

4th December 2024

Agenda:

• Status sharing including Playground Kanban
• Christian has an updated Knowledge Layer C4 Model to share
• Any input on VSS Database schema generator proposal
• Data Architecture Team confluence page updates
• Need to start considering Xmas breaks

Minutes:

• Xmas breaks
  • Steve last day is Friday 13th.
  • Decisions: Next weeks call 11th Dec is last of the year. First meeting of 2025 is 8th Jan.
• Playground
  • Kanban:
    • Steve went through his changes:
      • Add initial C4 Model diagrams to Github. See \diagrams\*.drawio.svg. The google drive file with multiple tabs is now a working copy for the newer diagrams.
      • Document Playground online documentation site. See \doc\readme.md
      • Redid the Data Architecture team confluence landing page. Further future improvements possible. Christian likes that it summarises the focus on data-centric arch and the info layers.
      • Following the topic coming up again last week drafted a proposal for DB Schema generation for VSS based on the existing diagram. Proposal can be found in the Data Arch confluence wiki VSS Database Schema Generator. Asked for feedback on slack. Daniel Alvarez provided some input on VSS channel regarding handling of VSS instances and whether working from an API spec would help.
    • Christian summarised BMW team changes:
      • Some updates to the RemotiveLab feeder to limit the inputs. Made for the current code base and use-case. Expect to improve this in the future.
      • He has updated C4 Models for the KL and IL changes.
        • Extended CDSP Container diagram. Added L3 for IL and KL.
        • He will ask Haonan to fill out KL container components.
        • Steve will add the diagrams to the google drive file.
• NoSQL Document DBs
  • Rami Pinto explained that MongoDB have a draft proposal for the work he mentioned last week to describe best practices for integrating VSS data into a NoSQL DB.
  • They will present this in an upcoming meeting. He's away next week. May wait till next year.

27th November 2024

Agenda:

• Status sharing including Playground Kanban
  • C4 Model pull request is ready for review
• We can continue Knowledge Layer discussions from last week
• Rami from MongoDB wanted to discuss DB enablement, automation and best practices

Minutes:

• Playground
  • Status
    • Christian is absent from the meeting (travelling)
    • Haonan is back from vacation and summarises her recent work on the knowledge layer.
    • Steve summarises the short term backlog for Haonan.
  • DB enablement, automation and best practices
    • Rami explains how MongoDB is looking to become more involved again. How does Atlas fit in?
    • In terms of the Knowledge Layer work the proposed sync meeting with Christian is needed.
    • Some additional possibilities are discussed:
      • Rami suggests best practices for Document databases. They had a customer conversation recently where they asked about how best to integrate VSS
      • Example showing how to integrate with Atlas
      • Steve outlined the previous discussions about a DB DDL schema generator for VSS.
      • Rami is encouraged to bring proposals.

20th November 2024

Agenda:

• Playground
  • C4 Models
    • PR for Github - readme, location, discoverability
    • Christian Container model extension
    • Deployment diagram - dev vs live
  • IoTDB version update
  • VISSR version update
  • Christian:
    • Discussion RealmOS instead of RealmSDK within Information Layer
    • MongoDB Atlas as additional backend?

Minutes:

• Playground
  • Answering questions from newcomes from Cobrasphere and MongoDB
  • C4 Models
    • Christian introduces his draft extension of the CDSP Container diagram to include the Knowledge Layer components
      • Steve: great to see this. Very helpful for discussion. We might remove the Fleet and Insurance example boxes to simplify. Also some minor points about connectors.
    • Steve has a WIP PR to add the L1 Context Diagram and L2 Container Diagram to the source
    • Steve shows some hacking he did for a Deployment diagram for the CDSP core in a development environment.
  • IoTDB version update
    • Steve was targetting v1.3.2, but v1.3.3 dropped a couple of hours ago which adds AINode (LLMs in SQL) and improvements in sync and subscriptions. So will likely refocus on that.
    • Also need to schedule the sync discussion with their community.
  • Knowledge Layer
    • Christian suggests that with deprecation of RealmSDK that KL will move to adopt Realm OSS community edition instead. This will leave a unfufilled requirement for DB sync.
    • MongoDB interested in how Atlas can be utilised in cloud side implementation. Christian wonders if it should be an additional backend to the DB abstraction (Information Layer)?
      • Conclusion: Further discussion needed.

13th November 2024

Agenda:

• Playground kanban and status exchange
• Data-arch discussion in Monday's AOSP call
• Capabilities API

Minutes:

• Steve summarised data-arch discussion in Monday's AOSP call that Richard gave us the heads-up about.
  • Steve mentioned to them work elsewhere in COVESA they could leverage, e.g. Capabilities API Seat as a source.
  • Conclusion: They are very early in their discussions. Should monitor and input where possible.
• Steve summarised status of Capabilities API work

6th November 2024

Minutes:

• Playground
  • Knowledge Layer
    • Input from Christian before meeting:
      • Knowledge Layer Connector is now largely finished. Now they are testing triple formatting and writing rules.
      • They are also starting to connect the RemotiveLabs feeder to the Information Layer Connector.
    • Steve has started to look again at the code as preparing for review. He sees some topics in the IoTDB integration that need aligning with what already exists, e.g. database paths and handling of VSS path naming.
  • Steve has started to look at the VISSR and IoTDB version upgrades.
• AOSP
  • Richard summarises the result of the AOSP group survey about what should be next. One of the findings relates to southbound data transformation. What that may mean in terms of work streams will be discussed in the AOSP call this Monday.
• Ulf reported that the CVIS work for Commercial vehicles has restarted in recent weeks.

30th October 2024

Agenda:

• Catch-up after two week hiatus
• KL updates from Christian
• Data sets
• OEM news

Minutes:

• Playground
  • Knowledge Layer
    
    • Christian gave a summary of updates to the Knowledge Layer pull request over the two week hiatus, including a walk through of the document for the hello world example
    • The example requires one additional data key that is not in VSS. Ulf mentions work on HIM merged in current VISSR that could be used to model the two data models (VSS and personal data)
    • Christian: Has RDFox been in contact about licensing?
    • Steve: not seen it yet, but not completely through my email backlog.
    • Christian will ask.
  • Data sets
    • Whilst in Japan Steve recorded some travel data (speed, location and elevation) on the bullet train with an eye on transforming them into VSS for use as an open data set.
  • OEMs
    • Steve mentions that during a Honda keynote at the recent Open Source Summit in Japan by Tsubouchi-san there was mention of an in-vehicle data lake that appears to support the approach of the Playground for hybrid in-vehicle and off-board data processing.
      Image Added
      Source:

      Widget Connector
      url https://www.youtube.com/watch?v=aTLETMQLl3g

23rd October 2024

Meeting cancelled due to holidays

16th October 2024

Meeting cancelled due to holidays

9th October 2024

Agenda:

• Christian is back at work after his break and has some points to discuss related to the Knowledge Layer
• From there I would like to continue the process of discussing what's next.

• • Reminder at the AMM I presented the following high level list that we discussed previously:

• • • Complete Knowledge Layer initial development
    • VISSR, IoTDB version update
    • General:

• • • • Outreach
      • Data sets
      • Use-cases / Examples / patterns / etc.
      • Improving guides
      • Expanding Feeders

• AoB

• • I will be on holiday for two weeks from next Tues 15th to Tues 29th. So we need to decide if we cancel the next two calls or if you still wish to meet.

Minutes:

Minutes:

• Playground
  • Catch up on Knowledge Layer.
    • Haonan now adding Knowledge components to PR
    • Discussion of documentation and impact of MongoDB announcing deprecation of embedded components
      • Christian favours merge, then looking for alternatives.
    • Discussion of use-cases. Christian will create Github task ticket to outline the use-case and its development.
  • Version updates
    • Steve outlines benefits (improvements to stream and sync) of moving to 1.3.x IoTDB
    • Ulf informs that his updates to VISSR to speed up subscriptions (feeder can inform server of a change, rather than server use polling) are now merged
• AoB
  • Discision taken to cancel Weds 16th and 23rd meetings. Next will be Weds 30th.

2nd October 2024

Agenda:

• Fall  AMM wash-up
• Start the process of discussing what's next. At the AMM I presented the following high level list that we discussed previously:

• • Complete Knowledge Layer initial development
  • VISSR, IoTDB version update
  • General:

• • • Outreach
    • Data sets
    • Use-cases / Examples / patterns / etc.
    • Improving guides
    • Expanding Feeders

• AoB

Minutes:

• AMM
  • Discussed feedback and themes, e.g:
    • Cloud
    • Coalesching understanding around APIs
    • AOSP future workstreams
• Playground next steps
  • Steve: please consider over coming weeks what interests you, what can be tackled etc.
  • High level list from AMM presentation:
    • Complete Knowledge Layer initial development
      • Need to align with BMW on the MongoDB announcement that they are deprecated embedded components, e.g. Sync and Device SDK (Realm).
    • VISSR, IoTDB version update
      • VISSR
        • Ulf suggests waiting for merge of his changes to allow feeders to inform the server when data has changed in a subscription, which removes need for polling.
        • Steve mentions that he would like to tackle the issue of a pre-built VISSR docker image.
      • IoTDB
        • Currently 1.2.x is used. 1.3.x has useful improvements including in sync and streaming.
        • Further out AI support for LLM execution in SQL is coming in AINode support.
    • General:
      • Outreach
        • Paul: consider having a standalone webinar
        • Steve: good idea. Was also intending to do a series of blogs on Playground both general and specific (e.g. down-sample example)
      • Data sets
        • Steve: Talking to James Hunt from Aicas at AMM he suggested looking at the motorsport set they use
        • PIVOT project the other likely hunting ground
        • RemotiveLabs announced new VSS features in their data sets at the AMM.
      • Use-cases / Examples / patterns / etc.
      • Improving guides
        • Improve Introduction/Overview section using Detroit Playground Presentation as input, e.g. C4 Model diagrams.
        • Would like to add Integration Guides that tell ppl what they need for succesful connections, e.g. feeder integration, without needing to be an expert on complete system.
      • Expanding Feeders
        • Steve discussed uProtocol Simulator with Halim (GM) and DDS with Neil (RTI) at AMM
• AoB
  • Steve will be on holiday 15th-22nd of this month.

25th September 2024

• Cancelled due to Fall AMM

18th September 2024

Agenda:

• Fall  AMM
• Continuation of the Knowledge Layer Connector discussion if BMW are present and there are topics to discuss
• AoB
  • Ulf: VISSR feeder improvements

Minutes:

• Fall AMM
  • Steve outlines the Playground session presentation
  • Paul: Are you happy to present the 10min section about experimentation in the Tues workshop?
  • Steve: Yes
  • Richard: Halim will be present at the AMM.
• AoB
  • VISSR
    • Ulf outlined the work the VISSR project is doing to improve efficiency for subscriptions. Rather than polling, the feeder informs the server when there is a change. See PR for details https://github.com/COVESA/vissr/pull/43
  • AOSP
    • Richard: the AOSP group is looking for ppl interested in working on making VSS signals available to AOSP apps.
    • Steve: Is that mapping to Android VHAL or a parallel server for greater range of properties/signals?
    • Richard: Both of interest.
    • Discussion of the pluses and minuses and some of the prior work.
    • Ulf: VISS could be used for that case.

11th September 2024

Agenda:

• Playground Kanban "stand-up meeting": In-progress task status, major new items
• Fall  AMM
• Knowledge Layer Connector update: BMW want to give an update on their work on the Knowledge Layer components
• AoB

Minutes:

• Playground Kanban
  • Steve has fixed issue #57 (online doc ToC not rendered correctly).
  • Updates from BMW - see below
• Fall AMM
  • Steve and Haonan will discuss Knowledge Layer slides offline
• Knowledge Layer components
  • Andre reports that BMW have made good internal progress on engineering the knowledge layer components and wants to discuss how to progress publically in terms of PRs etc.
  • Steve suggests following:
    • 1st step would be concentrating on getting the Knowledge layer components public as the info layer ones currently are so we can all see what is being talked about. This could be in the existing PR or a new one if you prefer.
    • Commits can be added as you go to get early feedback. No need for "big bang" single push at the end of development.
    • With AMM coming that gives you some weeks to prepare.
    • Suggested 2nd step would be to consider the modelling of the components, e.g. extend C4 model, to support discussion and review
  • Steve's non-exhaustive list of related topics to be discussed during and after this process as input:
    • Information Layer abstraction
      • data get/set limitations vs data tablet and higher level queries.
        • Need: Agree how to document current limitations and not limit research in higher level and faster queries.
      • database path consolidation for the various containers, e.g. VISS access vs information layer set need to coordinate (now) where to get the data in the DB
        
        • Need: out of the box components work together
    • Use cases for online documentation
      • Currently intended for more general abstracted documentation and guides that need a lot of cross-referencing, e.g. integration guides
        • Need: Add appropriate doc for the newly introduced features
    • Architecture communication / arch visualisation / C4 model
      • Need: Need arch view of the Playground and how the new features are integrated at different levels of abstraction to be able to discuss within the group and outside.
    • Docker images and packaging of CDSP Core building blocks
      • Pre-built images?
      • Need: Agree on how to handle the dockerisation of Core building blocks in a consistent manner.
  • Discussion:
    • Agreement that current naming of Knowledge and Info layer 'boxes' in current C4 Model are not correct (Steve just added them as placeholders).
      • Collectively need to come up with what is 'better'.
      • Haonan says that Knowledgebase would be traditional way from knowledge perspective but it is also perhaps a little outdated.
      • Ulf suggests "Knowledge Server" as starting point for KL part and both Haonan/Steve agree that is better. Steve changes diagram.
    • Andre happy to add appropriate online documentation
    • Docker
      • Andre wonders about flexibility in selecting docker containers to include when using docker compose.
      • Sebastian says as end user he would simply consume Dockerfiles and deploy with kubernates but sees desire for 'easy' starting point
      • Steve agrees balance needed between out of box experience and both flexibility and maintainability. Docker compose does not preclude someone from really doing some bespoke for themselves.

Knowledge Layer Sync topic input:

• Information Layer abstraction
  • data get/set limitations vs data tablet and higher level queries
  • database path consolidation for the various containers, e.g. VISS access vs information layer set.
• Use cases for online documentation
  • Currently intented for more general abstracted documentation and guides that need a lot of cross-referencing, e.g. integration guides
• Architecture communication / arch visualisation / C4 model
  • Clearly communicating options at different levels of abstraction
• Docker images and packaging of CDSP Core building blocks
  • Pre-built images

4th September 2024

Agenda:

...