Page History

...

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

26th July 2023

...

2nd August 2023

• Knowledge Layer proposal
  • Christian Muehlbauer has posted his first outline
  • Steve: what would you like to achieve and how best to take this forward?
  • Details in the proposal but Christian would like to explore what would be needed to have a technology agnostic seperation between knowledge and the underlying areas. How would they interact and stay in sync etc.
  • After discussion about way forward, Christian happy for people to promote its existance. Paul/Steve will mention it to other groups. Christian will think how he would present the work in a future 1 hr type dedicated meeting to the topic.
• Document and diagram storage
  • Steve was planning on creating data-arch-doc.git rep to get us started.
  • He brought topic up in Thursday call. Erik mentioned the existing (little used currently) Data EG git rep. That is probably a good place for top level diagrams like the scope diagram.
• AMM planning
  • Steve has added a planning page here 2023 Autumn AMM (Data Architecture and Infrastructure) 
  • Steve: any feedback from request last week to consider what we want to discuss?
    • Christian Muehlbauer discussing internally about what we might be able to show. Workshop could discuss knowledge layer proposal.
    • Arnaldo Vera Some possibilities we are discussing: Tooling for conversion to JSON-schema. Realm for OTA. Connected car sync.
      • Steve mentions Adnan Bekan PR for a VSS vspec to json-schema tool. Arnaldo will take a look.
    • Stephen Lawrence Store/Server playground, Design doc publishing.
    • Ulf Bjorkengren plans to present update on HIM including new additions.
  • Paul Boyes interesting to see conceptual design/requirements for connecting signals to non-signal info/knowledge in-vehicle and on to cloud.
    • Discussion of how this relates to other areas. Some topics likely best as a wider group workshop, e.g. combining data models
    • Paul will be posting table for Thursday tracks for planning purposes
• Data Pattern proposal
  • Steve has restarted completing the text. Currently working on the publishing section
• Data Arch front page redo is open AI.

26th July 2023

• Data Pattern proposal
  • No change due to the collab meetings last week. Meetings confirm the need - see below.
  • Steve will return to completing the draft.
• Knowledge layer proposal
  
  • Christian catching up after holiday. Still intends to upload the proposal for feedback.
• Topics arising from collaboration meetings (EU Horizon, SDV Summit, Covesa Board F2F) last week
  • The Covesa Scope diagram was used in EU Horizon SDV group to discuss SDV. It was also used in SDV Summit.
  • This both shows Covesa materials being used externally and their value. Basically further proof of the need being addressed in the Data Pattern proposal
  • This flags again some recent topics: where to store them and enhancing discoverability for external people
  • Christian had been considering a diagram showing how Data Arch relates to the other topics. He'll have a go at drafting it.
• Git rep / where to put diagrams
  • We have had some discussion previously but now with the external use we need to move to a solution to encourage re-use.
  • Steve: I still am not in favor of a 'big bucket' repository containing all source and docs. Source should be organised by product for reuse. I would suggest starting with a git rep dedicated to documentation, e.g. data-arch-doc.git
• Discoverability
  • Feedback from last week shows discoverability could be improved.
  • Christian: when I first came to Covesa/VSS work I found it easiest to orientate myself from the VSS (Hugo) document website.
  • We know this and had been prioritising getting the tech work going. However now need to address it.
  • Three main touchpoints immediately come to mind:
    • data-arch-doc.git
      • Holding doc, diagram source
    • Hugo data arch documentation website
      • Serving rendered documents as per the document proposal
    • Confluence Data Arch landing page
• Reforming group landing page
  • Steve: I'll try and find the time to bring the Data Arch Landing Page up to date, e.g. show the Scope diagram there. At least a draft for review by the group.
• AMM
  • Steve: we need to start considering what we want to do at the AMM.
    • I would expect a Data Arch pillar intro as usual, possibly as part of Data EG intro.
    • I would also expect somekind of combination workshop + presentations for the Thursday as we have done in the past, but need your input.
  • AI: Consider what you want to discuss/present
• Discussion on process of creating content for Hugo documentation website
  • Christian: People may think it is a single persons viewpoint if its all markdown in a single git post
  • Steve: Yes collaboration on the text will be needed in many cases. I would suggest for such documents the draft text be worked on somewhere collab is easier. Confluence has inline comments for example. Of course direct to markdown or something else is also possible. Point is to make it easier to comment and discuss.
  • Steps could be:
    • Creation stage:
      • Collab on text (Confluence, whatever)
      • Convert to markdown(github)
      • Sign-off
    • Publishing stage:
      • Move markdown to Hugo tree
      • CI Runner generates Hugo site and publishes to production
        • <Possible to have a parallel CI for WIP if needed>

...