Page History

...

• Knowledge Layer
  • Christian Muehlbauer showed the state of his work (currently in Word doc) on his Knowledge Layer ideas.
  • Positive feedback for him to continue.
  • Some discussion of the implications.
  • Arnaldo raises point about sharing knowledge decision is analogous to conflict resolution in data centric arch sync. Who decides the knowledge, communicates it and receives an update. Only want to store state when it changes.
  • Steve suggested a top down approach to the description to seperate the most generic ideas from the more specific ones. Basically to avoid a 'must adopt it all to be relevant' issue.
  • Steve asked Christian to let us know when he wanted to get a wider view on the work.
• Data Pattern / Data Architecture proposal
  • Steve has made some good progress since last week.
  • Majority of the text for the current state of play is now done.
  • Will now move onto next steps.
  • Socialised the initial proposal and the idea to use Hugo for publishing to Technical Steering Committee and Data Expert Group with no push back.
• Git rep naming
  • Steve gave some thought to this after last weeks discussion.
  • Still reluctant to have a single 'big bucket' git rep for the usability and maintainability reasons that is not normally done in engineering practise.
  • However likely don't want 20 reps either.
  • Steve: How about as a starting point to have some level of classification to narrow its scope, e.g. data-arch-doc.git or data-arch-doc-arch-patterns.git?
  • No clear answer. Team asked to think on it as we will need to make a decision fairly soon.
• News
  • Ulf Bjorkengren has published documentation in his HIM proposal
  • In VSSo call there was a heads up that Daniel Wilms had a proposal for using GraphQL schema to create VSS graphs. Intention was to present to the VSS group in a couple of weeks.

21st June 2023

...

• Data Arch rep discussion
  • Big bucket vs project focus
  naming discussion
  • Short initial discussion of how to organise git repositories for the data arch pillar.
  • Single 'big bucket' vs project specific?
  • Ulf suggests big bucket
  • Steve concerned about maintainability of big bucket.
  • Steve: please consider what you want and we will discuss again
• Refining Steve's Data Pattern / Data Architecture proposal 
  • Steve outlined his idea to use online publishing paradigm already used in Covesa for VSS doc. Brings all the docs together and is useful to link to for non-engineers.
  • Feedback was positive.
  • Christian added comment about sync which is now resolved
  • In meeting added Knowledge layer as a topic to the content list
    
    • Christian working on outline based on idea he explained recently
    • Wants to know where he would put it?
    • Steve: need to resolve the question of data arch rep naming. In meantime depending on your format you can push to the google drive, create personal git rep, or I can create you one in my area.
  Steve's Document proposal refining
  • Agreement on doc publishing
  • Christian point about sync resolved
  • Added Knowledge layer
    
    • Christian working on outline.
    • Which rep?

14th June 2023

• Knowledge layer (45 min)
  • Christian Muehlbauer has noted that in the Covesa organisation slides showing the Data EG pillars that the knowledge layer is listed under the Data Models / Ontologies. Should it be in Data Architecture instead/as well?
    • Discussion of the question. Christian has a draft diagram showing Machine Learning and Semantic Reasoning (requires ontologies like VSSo) acting on VSS data as a means for deriving high level knowledge. This is an example of how the Knowledge Layer is also applicable to Data Architecture. Ulf likes the diagram and mentions he intends to explore some of this in his HIM project.
    • One area of possible interest is standardised knowledge representations. You derive some knowledge from standard data. Is there a standard way to represent the knowledge? This has benefits in loosly coupling the knowledge, from possible consumers.
    • Conclusion is everyone agrees that it also applies to Data Architecture in such a context and could be considered part of the scope. Open question as to how to include it in such a summary slide. For sure it could be part of any Data Architecture pillar description that was not so space constrained.
• Data Pattern / Data Architecture proposal (15 mins)
  • As discussed last week Steve has started work on a proposal for Design Pattern and Data Architecture documentation which can be found here https://wiki.covesa.global/x/boA8B
  • Principal aim is to use it facilitate what to create.
  • Short on time so quick run through. It's still a WIP towards a draft. Please edit or add in-line comments.

...