Benjamin Klotz - at.projects.genivi.org
24
April 18, 2018 | Extension of the Vehicle Signal Specification Benjamin Klotz PhD student, BMW Group, EURECOM
Transcript of Benjamin Klotz - at.projects.genivi.org
April 18 2018 | Extension of the Vehicle Signal Specification
Benjamin KlotzPhD student BMW Group EURECOM
Initial context
2 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Front camera
Radar
Tire pressure sensorPark assistant
Steering angle sensor
Wheel speed sensor
Blind spot detection
Adaptive cruise control
Temperature sensor
Oil temperature sensor
Vehicle height sensor
bull Adapt infotainment from
online use favorite
playlists and volume
bull Drive your car in front of
the building you are
leaving
bull hellip
nameaccelerator_pedal_positionvalue0timestamp1361454211483000
namefuel_levelvalue23478279timestamp1361454211485000
nametorque_at_transmissionvalue1timestamp1361454211488000
Driving context
3 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal data model
Driving
Contexts
Web services
Smart home
Smart city
Goalsbull Personalization
bull Awareness
bull Data fusion
hellip
Enabling interoperability through the
signal data model
VSS in a nutshell
5 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Figure
bull 451 branches
bull 1103 leavesndash 43 attributes
ndash 1060 signals including
bull (700 seat-related)
bull 268 with unit SignalAttribute
Body
Weight
Raindetection Intensity
Type UInt8
Unit percent
Description ldquohelliprdquo
Value restriction or
free
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Attribute
Signal
Signal entries
Examples
Gearbox-sensed speed DrivetrainTransmissionSpeed
Engine speed DrivetrainEngineSpeed
GPS-sensed speed CabinInfotainmentSpeed
Left door lock BodyRow1DoorLeftIsLocked
Right mirror tilt CabinMirrorRightTilt
Ontologies for (car) signals [1]
6 | April 18 2018 | Copyright copy GENIVI Alliance 2017
The Semantic Sensor Network (SSN) ontology
is an ontology for describing
bull sensors
bull and their observations
bull the involved procedures
bull the studied features of interest
bull the samples used to do so
bull and the observed properties
bull as well as actuators actuations
[1] httpswwww3orgTRvocab-ssn
SSN follows a horizontal and vertical modularization
architecture by including a lightweight but self-contained
core ontology called SOSA (Sensor Observation
Sample and Actuator) for its elementary classes and
properties
- A W3C and OGC recommendation (19 October 2017)
- Supports a wide range of applications and use cases including satellite imagery large-scale
scientific monitoring industrial and household infrastructures social sensing citizen science
observation-driven ontology engineering and the Web of Things
7 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SOSASSN observation amp sensor pattern
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
rdftype
sosaResult222kmh^^cdtspeed
222^^xsddouble
qudtKilometerPerHour
qudtnumericValuequdtunit
sosahasSimpleResult
sosaphenomenonTime
geolat
geolon
Speed
bull Definition of a signal
bull Definition of a sensor
bull Well-defined units
bull Geolocation
No formal definition of
bull ldquospeedrdquo or other observable properties
bull ldquospeedometerrdquo or other car sensorsactuators
bull ldquoCarrdquo or vehicle parts
BUT
2018-04-18T133612Z^^xsddateTime
481374300deg115754900deg
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Initial context
2 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Front camera
Radar
Tire pressure sensorPark assistant
Steering angle sensor
Wheel speed sensor
Blind spot detection
Adaptive cruise control
Temperature sensor
Oil temperature sensor
Vehicle height sensor
bull Adapt infotainment from
online use favorite
playlists and volume
bull Drive your car in front of
the building you are
leaving
bull hellip
nameaccelerator_pedal_positionvalue0timestamp1361454211483000
namefuel_levelvalue23478279timestamp1361454211485000
nametorque_at_transmissionvalue1timestamp1361454211488000
Driving context
3 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal data model
Driving
Contexts
Web services
Smart home
Smart city
Goalsbull Personalization
bull Awareness
bull Data fusion
hellip
Enabling interoperability through the
signal data model
VSS in a nutshell
5 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Figure
bull 451 branches
bull 1103 leavesndash 43 attributes
ndash 1060 signals including
bull (700 seat-related)
bull 268 with unit SignalAttribute
Body
Weight
Raindetection Intensity
Type UInt8
Unit percent
Description ldquohelliprdquo
Value restriction or
free
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Attribute
Signal
Signal entries
Examples
Gearbox-sensed speed DrivetrainTransmissionSpeed
Engine speed DrivetrainEngineSpeed
GPS-sensed speed CabinInfotainmentSpeed
Left door lock BodyRow1DoorLeftIsLocked
Right mirror tilt CabinMirrorRightTilt
Ontologies for (car) signals [1]
6 | April 18 2018 | Copyright copy GENIVI Alliance 2017
The Semantic Sensor Network (SSN) ontology
is an ontology for describing
bull sensors
bull and their observations
bull the involved procedures
bull the studied features of interest
bull the samples used to do so
bull and the observed properties
bull as well as actuators actuations
[1] httpswwww3orgTRvocab-ssn
SSN follows a horizontal and vertical modularization
architecture by including a lightweight but self-contained
core ontology called SOSA (Sensor Observation
Sample and Actuator) for its elementary classes and
properties
- A W3C and OGC recommendation (19 October 2017)
- Supports a wide range of applications and use cases including satellite imagery large-scale
scientific monitoring industrial and household infrastructures social sensing citizen science
observation-driven ontology engineering and the Web of Things
7 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SOSASSN observation amp sensor pattern
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
rdftype
sosaResult222kmh^^cdtspeed
222^^xsddouble
qudtKilometerPerHour
qudtnumericValuequdtunit
sosahasSimpleResult
sosaphenomenonTime
geolat
geolon
Speed
bull Definition of a signal
bull Definition of a sensor
bull Well-defined units
bull Geolocation
No formal definition of
bull ldquospeedrdquo or other observable properties
bull ldquospeedometerrdquo or other car sensorsactuators
bull ldquoCarrdquo or vehicle parts
BUT
2018-04-18T133612Z^^xsddateTime
481374300deg115754900deg
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Driving context
3 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal data model
Driving
Contexts
Web services
Smart home
Smart city
Goalsbull Personalization
bull Awareness
bull Data fusion
hellip
Enabling interoperability through the
signal data model
VSS in a nutshell
5 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Figure
bull 451 branches
bull 1103 leavesndash 43 attributes
ndash 1060 signals including
bull (700 seat-related)
bull 268 with unit SignalAttribute
Body
Weight
Raindetection Intensity
Type UInt8
Unit percent
Description ldquohelliprdquo
Value restriction or
free
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Attribute
Signal
Signal entries
Examples
Gearbox-sensed speed DrivetrainTransmissionSpeed
Engine speed DrivetrainEngineSpeed
GPS-sensed speed CabinInfotainmentSpeed
Left door lock BodyRow1DoorLeftIsLocked
Right mirror tilt CabinMirrorRightTilt
Ontologies for (car) signals [1]
6 | April 18 2018 | Copyright copy GENIVI Alliance 2017
The Semantic Sensor Network (SSN) ontology
is an ontology for describing
bull sensors
bull and their observations
bull the involved procedures
bull the studied features of interest
bull the samples used to do so
bull and the observed properties
bull as well as actuators actuations
[1] httpswwww3orgTRvocab-ssn
SSN follows a horizontal and vertical modularization
architecture by including a lightweight but self-contained
core ontology called SOSA (Sensor Observation
Sample and Actuator) for its elementary classes and
properties
- A W3C and OGC recommendation (19 October 2017)
- Supports a wide range of applications and use cases including satellite imagery large-scale
scientific monitoring industrial and household infrastructures social sensing citizen science
observation-driven ontology engineering and the Web of Things
7 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SOSASSN observation amp sensor pattern
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
rdftype
sosaResult222kmh^^cdtspeed
222^^xsddouble
qudtKilometerPerHour
qudtnumericValuequdtunit
sosahasSimpleResult
sosaphenomenonTime
geolat
geolon
Speed
bull Definition of a signal
bull Definition of a sensor
bull Well-defined units
bull Geolocation
No formal definition of
bull ldquospeedrdquo or other observable properties
bull ldquospeedometerrdquo or other car sensorsactuators
bull ldquoCarrdquo or vehicle parts
BUT
2018-04-18T133612Z^^xsddateTime
481374300deg115754900deg
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Enabling interoperability through the
signal data model
VSS in a nutshell
5 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Figure
bull 451 branches
bull 1103 leavesndash 43 attributes
ndash 1060 signals including
bull (700 seat-related)
bull 268 with unit SignalAttribute
Body
Weight
Raindetection Intensity
Type UInt8
Unit percent
Description ldquohelliprdquo
Value restriction or
free
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Attribute
Signal
Signal entries
Examples
Gearbox-sensed speed DrivetrainTransmissionSpeed
Engine speed DrivetrainEngineSpeed
GPS-sensed speed CabinInfotainmentSpeed
Left door lock BodyRow1DoorLeftIsLocked
Right mirror tilt CabinMirrorRightTilt
Ontologies for (car) signals [1]
6 | April 18 2018 | Copyright copy GENIVI Alliance 2017
The Semantic Sensor Network (SSN) ontology
is an ontology for describing
bull sensors
bull and their observations
bull the involved procedures
bull the studied features of interest
bull the samples used to do so
bull and the observed properties
bull as well as actuators actuations
[1] httpswwww3orgTRvocab-ssn
SSN follows a horizontal and vertical modularization
architecture by including a lightweight but self-contained
core ontology called SOSA (Sensor Observation
Sample and Actuator) for its elementary classes and
properties
- A W3C and OGC recommendation (19 October 2017)
- Supports a wide range of applications and use cases including satellite imagery large-scale
scientific monitoring industrial and household infrastructures social sensing citizen science
observation-driven ontology engineering and the Web of Things
7 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SOSASSN observation amp sensor pattern
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
rdftype
sosaResult222kmh^^cdtspeed
222^^xsddouble
qudtKilometerPerHour
qudtnumericValuequdtunit
sosahasSimpleResult
sosaphenomenonTime
geolat
geolon
Speed
bull Definition of a signal
bull Definition of a sensor
bull Well-defined units
bull Geolocation
No formal definition of
bull ldquospeedrdquo or other observable properties
bull ldquospeedometerrdquo or other car sensorsactuators
bull ldquoCarrdquo or vehicle parts
BUT
2018-04-18T133612Z^^xsddateTime
481374300deg115754900deg
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
VSS in a nutshell
5 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Figure
bull 451 branches
bull 1103 leavesndash 43 attributes
ndash 1060 signals including
bull (700 seat-related)
bull 268 with unit SignalAttribute
Body
Weight
Raindetection Intensity
Type UInt8
Unit percent
Description ldquohelliprdquo
Value restriction or
free
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Attribute
Signal
Signal entries
Examples
Gearbox-sensed speed DrivetrainTransmissionSpeed
Engine speed DrivetrainEngineSpeed
GPS-sensed speed CabinInfotainmentSpeed
Left door lock BodyRow1DoorLeftIsLocked
Right mirror tilt CabinMirrorRightTilt
Ontologies for (car) signals [1]
6 | April 18 2018 | Copyright copy GENIVI Alliance 2017
The Semantic Sensor Network (SSN) ontology
is an ontology for describing
bull sensors
bull and their observations
bull the involved procedures
bull the studied features of interest
bull the samples used to do so
bull and the observed properties
bull as well as actuators actuations
[1] httpswwww3orgTRvocab-ssn
SSN follows a horizontal and vertical modularization
architecture by including a lightweight but self-contained
core ontology called SOSA (Sensor Observation
Sample and Actuator) for its elementary classes and
properties
- A W3C and OGC recommendation (19 October 2017)
- Supports a wide range of applications and use cases including satellite imagery large-scale
scientific monitoring industrial and household infrastructures social sensing citizen science
observation-driven ontology engineering and the Web of Things
7 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SOSASSN observation amp sensor pattern
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
rdftype
sosaResult222kmh^^cdtspeed
222^^xsddouble
qudtKilometerPerHour
qudtnumericValuequdtunit
sosahasSimpleResult
sosaphenomenonTime
geolat
geolon
Speed
bull Definition of a signal
bull Definition of a sensor
bull Well-defined units
bull Geolocation
No formal definition of
bull ldquospeedrdquo or other observable properties
bull ldquospeedometerrdquo or other car sensorsactuators
bull ldquoCarrdquo or vehicle parts
BUT
2018-04-18T133612Z^^xsddateTime
481374300deg115754900deg
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Ontologies for (car) signals [1]
6 | April 18 2018 | Copyright copy GENIVI Alliance 2017
The Semantic Sensor Network (SSN) ontology
is an ontology for describing
bull sensors
bull and their observations
bull the involved procedures
bull the studied features of interest
bull the samples used to do so
bull and the observed properties
bull as well as actuators actuations
[1] httpswwww3orgTRvocab-ssn
SSN follows a horizontal and vertical modularization
architecture by including a lightweight but self-contained
core ontology called SOSA (Sensor Observation
Sample and Actuator) for its elementary classes and
properties
- A W3C and OGC recommendation (19 October 2017)
- Supports a wide range of applications and use cases including satellite imagery large-scale
scientific monitoring industrial and household infrastructures social sensing citizen science
observation-driven ontology engineering and the Web of Things
7 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SOSASSN observation amp sensor pattern
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
rdftype
sosaResult222kmh^^cdtspeed
222^^xsddouble
qudtKilometerPerHour
qudtnumericValuequdtunit
sosahasSimpleResult
sosaphenomenonTime
geolat
geolon
Speed
bull Definition of a signal
bull Definition of a sensor
bull Well-defined units
bull Geolocation
No formal definition of
bull ldquospeedrdquo or other observable properties
bull ldquospeedometerrdquo or other car sensorsactuators
bull ldquoCarrdquo or vehicle parts
BUT
2018-04-18T133612Z^^xsddateTime
481374300deg115754900deg
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
7 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SOSASSN observation amp sensor pattern
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
rdftype
sosaResult222kmh^^cdtspeed
222^^xsddouble
qudtKilometerPerHour
qudtnumericValuequdtunit
sosahasSimpleResult
sosaphenomenonTime
geolat
geolon
Speed
bull Definition of a signal
bull Definition of a sensor
bull Well-defined units
bull Geolocation
No formal definition of
bull ldquospeedrdquo or other observable properties
bull ldquospeedometerrdquo or other car sensorsactuators
bull ldquoCarrdquo or vehicle parts
BUT
2018-04-18T133612Z^^xsddateTime
481374300deg115754900deg
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
8 | April 18 2018 | Copyright copy GENIVI Alliance 2017
SSNSOSA with a VSS ontology
sosaObservable
Property
sosaSensor
sosaObservationsosaisObservedBy
Speed
rdftype
sosaResult
222kmh^^cdtUCUM
222^^xsddouble
qudtUnit
qudtunit
sosahasSimple
Result
vssSpeedometer
vssSpeed
vssObservableSignal
rdfssubClassOf
rdfssubClassOf
rdfssubClassOf
vssTransmission
vssDrivetrain
vssInternal
Combustion
vsspartOf vsspartOfvsshasSignal
vssBranch
rdfssubClassOf
4Nm^^cdttorque
vssmaxTorque
rdftype
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
What is required
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
From VSS spec to the VSS ontology
10 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSAdd sensors and actuators
Map to existing Ontologies
- SSNSOSA
- QUDT (unit)
Apply consistency policies
Generate definition of VSS concepts
Manually validate and clean the generated ontology
VSSontology
Modeling policies1 VSS concepts have unique names
2 All signals are either observable actuable or both
3 All signals have either a sensor or an actuator
4 All branches are part of the top ldquovssVehiclerdquo branch
5 All position-dependent branches have a property ldquopositionrdquo
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Modeling choice 1 unique names for unique concepts
11 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals represent the same phenomenon sensed by different sensors
ndash Ex DrivetrainSpeed (sensed by the gearbox) and InfotainmentSpeed (sensed by the GPS)
vssVehicleSpeed
vssObservableSignalvssTransmission
vssBranch
vssInfotainment
rdfssubClassOf
sosaSensor
vssSpeedometer
vssGPS
rdfssubClassOf
rdfssubClassOf
ldquovssVehicleSpeedrdquo is a unique phenomenon
observed by different sensors
Producing different signals Names are clarified to avoid homonymy
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Modeling choice 2 signals are observable actuable or
both
12 | April 18 2018 | Copyright copy GENIVI Alliance 2017
bull Some signals are attached to sensors other to actuators or
both For instance
ndash DrivetrainTransmissionSpeed observes a speedometer
ndash MirrorRightHeating only acts on a heater
ndash InfotainmentMediaVolume observesacts on the media volume
sosaObservableProperty
sosaSensor
sosaObservationsosaisObservedBy
sosaActuableProperty
sosaActuator
sosaActuationsosaisActedBy
rdfssubClassOf
vssActuableSignal
vssObservableSignal
vssVehicleSpeed
vssHeating
vssMediaVolume
rdfssubClassOf
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
13 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 3 all signals have a sensor or actuator
vssVehicleSpeed
vssObservableSignal
vssTransmission
vssBranch
rdfssubClassOf
sosaSensor
vssSpeedometer
rdfssubClassOf
vssVehiclevsspartOf
rdfssubClassOf
Signals SensorsActuators Branches and parts
Produced by [sensor]
Consumed by [actuator]
Contains
(vsspartOf)
vsshasSignal
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
14 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 4 all branches are vsspartOf vssVehicle
vsspartOf
vssVehicle
vssBody
vssADAS
vssCabin
vssChassis
vssDrivetrain
vssOBD
vssBranch
rdfssubClassOf Signal
Body
ADAS
Cabin
Chassis
Drivetrain
OBD
Vehicle
Current VSS structure VSSontology structure
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
15 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Modeling choice 5 position ne branch- Ex DoorLeftIsLocked MirrorRightTilt
- Branches vssDoor and vssMirror have vsshasPosition property with limited potential values (ldquoLeftrdquordquoRightrdquordquoRow1rdquo hellip)
vssDoorIsLocked
rdfssubClassOf
vssDoor
vssMirror
vssBranch
rdfssubClassOf
rdfssubClassOf
LeftDoorLock
vssMirrorTilt
rdfssubClassOf
RightMirrorTilt
vsshasPosition
ldquoLeftrdquo^^cdt ldquoRightrdquo^^cdt
Door2 Mirror3
vssSignal
Branch
Position
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
vsoAutomobile
Application linking signals to a heterogeneous context
16 | April 18 2018 | Copyright copy GENIVI Alliance 2017
p1
p2
p3 p4 p5
p6
p7
p8 p9
p10p11
p12
Aggressive behavior
Neutral
Safe behavior
Traffic
jam
Close event
Closed
road
Driving
Contexts
Web services
Smart home
Smart city
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
What about OEM-specific concepts
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Ontological specification
bull 84 formally-defined vehicle parts
bull ~300 formally-defined signals
bull ~40 formally-defined attributes
18 | April 18 2018 | Copyright copy GENIVI Alliance 2017
VSSo
cookbook
Ontological
specification
Base VSSo
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
VSS private branchPrivate branchbull OEM-specific concepts
bull Extension of VSS
bull Merged into VSS when
generating specifications
19 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Private OEM-specific ontology cookbook1 Write VSS-compliant specification of private concepts (new signals attributes and branches)
Follow the VSS policies just as when creating a private branch
2 Generate the ontology using the existing tool
3 Validate the ontology
Check the unicity of concepts and definitions (in the private branch and if possible with VSSo)
4 Define a private namespace for your ontology integrating VSSo
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Do you have questions
Thank you for your attention
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Branch examples
vssBranch a rdfsClass owlClass
rdfslabel Branchen
rdfscomment Branch of the vehicle Either a component (Body Chassis) or the complete vehicleen
vssObstacleDetection a rdfsClass owlClass
rdfssubClassOf vssBranch
rdfslabel ObstacleDetectionen
rdfscomment SignalAttributeADASObstacleDetection Signals form Obstacle Sensor Systemen
rdfssubClassOf [
a owlRestriction
owlonProperty vsspartOf
owlallValuesFrom vssADAS
]
rdfssubClassOf [
a owlRestriction
owlonProperty vsshasSignal
owlallValuesFrom [owlunionOf vssObstacleDetectionIsActive vssObstacleDetectionError]
]
21 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Signal examplesvssObservableSignal a rdfsClass owlClass
rdfssubClassOf sosaObservableProperty
rdfslabel Observable signalen
rdfscomment All observable signals that can dynamically be updated by the vehicleen
vssAmbientAirTemperature a rdfsClass owlClass
rdfssubClassOf vssObservableSignal
rdfslabel AmbientAirTemperatureen
rdfscomment SignalVehicleAmbientAirTemperature Ambient air temperatureen
rdfssubClassOf [
a owlRestriction
owlonProperty sosaisObservedBy
owlallValuesFrom vssThermometer
]
rdfssubClassOf [
a owlRestriction
owlonProperty qudtunit
owlallValuesFrom vocabDegreeCelcius
]22 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Signal examples
vssattribute a owlObjectProperty
rdfslabel Attributeen
rdfscomment Attribute signals that do not change during the power cycle of a vehicleen
rdfsdomain vssBranch
vssdriveType a owlDatatypeProperty
rdfssubPropertyOf vssattribute
rdfslabel DriveTypeen
rdfscomment AttributeDrivetrainTransmissionDriveType Drive typeen
rdfsdomain vssTransmission
rdfsrange [owloneOf(unknownen Front-wheel driveen Rear-wheel driveen
All-wheel driveen)]
23 | April 18 2018 | Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
Thank you
Visit GENIVI at httpwwwgeniviorg or httpprojectsgeniviorg
Contact us helpgeniviorg
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries
Copyright copy GENIVI Alliance 2017
![[LETTER OF APPLICATION – MG KLOTZ] 1 Documents... · [LETTER OF APPLICATION – MG KLOTZ] 3 for the rules of engagement, quality and resources, as a Colleague providing mentorship](https://static.fdocuments.in/doc/165x107/600e87d4cc5f556d543a8391/letter-of-application-a-mg-klotz-1-documents-letter-of-application-a.jpg)
