Consider What/Why for a Knowledge Layer connector

[slawr]

The Data Architecture team has discussed separation of concerns between the data/information layers and the knowledge layer in a DIKW (Data, Information, Knowledge, Wisdom) pyramid. Where the data layer is represented by the native vehicle data (e.g. CAN, SOME/IP), the Information layer by the VSS and adjacent data models and the Knowledge/Wisdom layers by reasoning etc.

@chrizmc provided input on one possible use case for the higher levels in the pyramid in the Early Planning https://wiki.covesa.global/display/WIK4/Early+planning#Earlyplanning-Usecasestobeexplored

A proposal has been made for the Playground to have a connector between the Information and Knowledge layers.

BMW have a component that might be open sourced that could be used as a possible implementation candidate and is described here by @claireqiu : https://wiki.covesa.global/display/WIK4/Artifact+JSON-RDF+Converter

The task here is to consider the logical concept for such a connector. Why it is needed and what is should support?

[slawr]

Set state to "in progress" as @claireqiu @chrizmc are considering a proposal for the AMM workshop

[slawr]

Side meeting held with participants (@claireqiu @chrizmc) at the AMM to discuss the connector and way forward. BMW will reply with updated proposal.

[chrizmc]

I think we can close this ticket as the Why and What was presented and discussed in Gothenburg by @claireqiu and @chrizmc:

https://wiki.covesa.global/download/attachments/98271360/COVESA_AMM24_Knowledge-Layer-Reasoning-RemoteServices-v4.pptx?version=1&modificationDate=1714035039541&api=v2

[slawr]

Thanks for the reminder @chrizmc. For the what I assume you are referring mostly to the later slides.

I don't think we need to be especially formal about documenting gates between the stages of the work and I agree the presentation does a good job of the motivations, problems and possible goals of the connector. So happy to close.

The kanban should reflect the backlog and work underway so we should seek to capture what the next steps look like. For now I'll put a simple task in the kanban to determine the next steps.

Update: Created https://github.com/orgs/COVESA/projects/8?pane=issue&itemId=61127166