Updated vsso [instances, annotation]

[danielwilms]

Output of new tooling in https://github.com/COVESA/vss-tools/pull/160

• DVP now instances
• use of skos:definition instead of rdfs:comment
• rdfs:comment where vss uses comments (new in 3.0)
• dot notated path in separate annotation property

Signed-off-by: Daniel Wilms Daniel.DW.Wilms@bmw.de

[felix-loesch]

Great to see that DVP are now instances!

Can we add the linkage from the DVP instance to the VehicleComponent? For example, vsso-signals:EngineCoolantTemp vsso-core:belongsToVehicleComponent vsso-signal:Engine)

[danielwilms]

@felix-loesch, that's something we have to discuss later. It's possible only, if we instantiate the vehicle components as well...So I decided yesterday to discuss it first, before I implement it.

[danielwilms]

Decision in meeting on 2022/05/16: creating the vehicle components as instances:

• possible to create subclass structure later on
• currently not sufficient information in VSS to have sub-classes in generation
• work well together with DVP as instances

[danielwilms]

Meeting 2022/06/13:

Point from the PR:

Shall there be an instance of vsso:Vehicle or punning of vsso-core:Vehicle? Challenge araises, when you use the partOf relationship.

Option 1: No root instance node of vehicle components Option 2: Connecting to vsso-core:Vehicle, but then annotation property is necessary Option 3: Having an instance vsso:Vehicle as über-VehicleComponent as root of the instances

we go for now with option 3 and discuss further.

[danielwilms]

@danielwilms checks if option3 is implemented. If so, PR can be merged. Otherwise merged after implementation.

[jdacoello]

@danielwilms to provide update on status of implementation of option 3.

[danielwilms]

Implementation done. ttl file to be updated.

[danielwilms]

ttl file added. Ready to merge.