Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Proposal nameAuthorReference resourcesMain idea(s)
Transforming from a vehicle centric data model to a domain agnostic information model

View file
nameTransforming from a data model to an information model.pptx
height150

Presented at COVESA AMM 
Porto (April 2023)


Defining the COVESA data modeling strategy and its associated artifacts

View file
nameCOVESA_Ontologies_AMM_04.2023.pptx
height150

Presented at COVESA AMM 
Porto (April 2023)

  • Use the right tool for the job.
    • Do not try to cover multiple domains with only one tree.
    • There are other types of data models that are more expressive than a tree.
  • Use a standard language to express cross-references (e.g., RDF).
  • Use ontologies to handle data integration and the identification of resources.
  • Provide the mechanisms to sync a tree to an ontology, and standardise the steps to follow.
  • Do you need a data model, or are you looking for a use-case specific data schema?
  • For more details, see the extended description.
GraphQL schema as contract

Daniel Wilms

(SPREAD GmbH)

View file
name2023_08_01_vss_presentation.pdf
height150

Presented at VSS data modeling group on  


Integrating Vehicle Signals with VSS and Metadata

Alan Freedman

(Ford)

Passcode: #+wbA5dy

View file
nameVSS Extensions and Ford Signal Ontology.pptx
height150



Vehicle DATA Specification

Daniel Alvarez 

(BMW AG)


Daniel Wilms

(SPREAD GmbH)

COVESA_Towards vehicle DATA specification_AMM_04.2024.pdf

  • Uncovering the current limitations of VSS.
  • A proposal that combines the features of the multiple approaches that have been presented so far into one.


VSS modeling language evolution

View file
nameVSS next.pdf
height150

Presented during an open discussion with the technical steering team and VSS contributors on .

  • Evolve the VSS modeling language by doing one of the following:
    • Replace the VSPEC modeling language (custom YAML) by a well-established language (e.g., GraphQL SDL), or
    • Further extend the current language but commit more resources or capacity for the development of the tools

...