rdfs:comment"A relation that defines the destination of an automotive object. For example, in a platoon, the current platoon leader defines the platoon destination. Following vehicles will share (partially) the route of the leader and can, therefore, have different final destinations.";
rdfs:comment"A relation to express that, during the forming state, a vehicle member of a platoon is given an estimated rendezvous location for joining the platoon. It is expressed in global coordinates (lat, long, alt), e.g. according to WGS 84.";
rdfs:comment"A relation between an entity and its identifier (s4auto:Identifier) which is used to identify 1) a vehicle (station) during data exchange with other devices/stations 2) a platoon during data exchange with other devices/stations, 3) a parking spot within a parking area during data exchange with other devices/stations. In all cases, this identifier may be a pseudonym. It may change over space and/or over time."@en;
rdfs:label"hasIdentifier"@en.
### https://saref.etsi.org/saref4auto/hasMember
:hasMemberrdf:typeowl:ObjectProperty;
owl:inverseOf:isMemberOf;
rdfs:comment"A general relationship to express that an entity can have members"@en;
rdfs:comment"A relatiA relation to express that a vehicle member of a platoon has a platoon position that is defined as the index of the vehicle in the platoon starting from zero (leader) up to N (trailing vehicle)"@en;
rdfs:comment"A relation to specify that in a platoon a vehicle can assume roles such as: unknown, leader, follower, ready-for-leading, trailing, etc."@en;
rdfs:comment"A relation to specify that in a platoon a vehicle can assume roles such as: unknown, leader, follower, ready-for-leading, trailing, etc."@en;
rdfs:label"hasPlatoonRole"@en.
rdfs:label"hasPlatoonRole"@en.
### https://saref.etsi.org/saref4auto/hasPosition
:hasPositionrdf:typeowl:ObjectProperty;
rdfs:range:RelativePosition;
rdfs:comment"A relation to define the position of an entity"@en;
rdfs:comment"A relation between an entity, e.g., a vehicle or road entity, and RelativePosition to represent its relative position (e.g., a car is x,y,z in front of another car)"@en;
rdfs:comment"A relation to express that a device can use different types of properties, such as speed, position of detected road objects (e.g., bicycles, vehicles). This applies in particular to the ElectronicControlUnit and TrafficLightController classes."@en;
rdfs:comment"A relation to express that a device can use different types of properties, such as speed, position of detected road objects (e.g., bicycles, vehicles). This applies in particular to the ElectronicControlUnit and TrafficLightController classes."@en;
rdfs:comment"A relation to express that, during the forming state, a vehicle member of a platoon is given an estimated time for joining";
rdfs:label"hasEstimatedJoiningTime"@en.
### https://saref.etsi.org/saref4auto/hasIDValue
:hasIDValuerdf:typeowl:DatatypeProperty;
rdfs:comment"A relationship to define the value of an indentifier"@en;
rdfs:label"hasIDValue"@en.
### https://saref.etsi.org/saref4auto/hasMaxSize
### https://saref.etsi.org/saref4auto/hasMaxSize
:hasMaxSizerdf:typeowl:DatatypeProperty;
:hasMaxSizerdf:typeowl:DatatypeProperty;
rdfs:comment"A relation to express the max size of a platoon. Note that it is defined as a datatype property as this is a fixed/static value of the platoon that does not change over time. In contrast, the current size of the platoon may change over time and is therefore defined as a property (see s4auto:Size)."@en;
rdfs:rangexsd:integer;
rdfs:comment"A relation to express the max size of a platoon. Note that it is defined as a datatype property as this is a fixed/static value of the platoon that does not change over time. In contrast, the current size of the platoon may change over time and is therefore defined as a property (see s4auto:PlatoonSize)."@en;
rdfs:comment"A class to define common information related to an address. It is out of scope of SAREF4AUTO to define the details of such an address. It is instead recommended to reuse existing ontologies that specify how to model an address in terms of Street, Postal Code, City, Region, Country, etc."@en;
rdfs:comment"The final destination of a vehicle or a platoon, or the final point of a route"@en;
rdfs:label"EndPoint"@en.
### https://saref.etsi.org/saref4auto/Identifier
:Identifierrdf:typeowl:Class;
rdfs:subClassOf[rdf:typeowl:Restriction;
owl:onProperty:hasIDValue;
owl:someValuesFromxsd:string
];
rdfs:comment"A class used to identify 1) a vehicle (station) during data exchange with other devices/stations 2) a platoon during data exchange with other devices/stations, 3) a parking spot within a parking area during data exchange with other devices/stations. In all cases, this identifier may be a pseudonym. It may change over space and/or over time."@en;
rdfs:comment"A level of automation is defined for a vehicle that it is platooning. For example, in the ENSEMBLE project there are three levels of platoon automation defined: Level A, Level B, Level C. Level C represents the highest level of automation for platooning in terms of longitudinal and lateral control, shortest time gap supported, wider range of situations handled and support for merging of entire platoons."@en;
rdfs:comment"A vehicle member of a platoon has a platoon position that is defined as the index of the vehicle in the platoon starting from zero (leader) up to N (trailing vehicle)."@en;
rdfs:label"PlatoonPosition"@en.
### https://saref.etsi.org/saref4auto/PlatoonRole
### https://saref.etsi.org/saref4auto/PlatoonRole
:PlatoonRolerdf:typeowl:Class;
:PlatoonRolerdf:typeowl:Class;
rdfs:subClassOf:Role;
rdfs:subClassOf:Role;
rdfs:comment"In platoon a vehicle can assume roles such as: unknown, leader, follower, ready-for-leading, trailing, etc."@en;
rdfs:comment"In platoon a vehicle can assume roles such as: unknown, leader, follower, ready-for-leading, trailing, etc."@en;
rdfs:label"PlatoonRole"@en.
rdfs:label"PlatoonRole"@en.
### https://saref.etsi.org/saref4auto/Point
:Pointrdf:typeowl:Class;
rdfs:subClassOfgeosp:Geometry,
<http://www.w3.org/2003/01/geo/wgs84_pos#Point>;
rdfs:comment"A geo point in SAREF4AUTO"@en;
rdfs:label"Point"@en.
### https://saref.etsi.org/saref4auto/Position
:Positionrdf:typeowl:Class;
rdfs:subClassOf[rdf:typeowl:Restriction;
owl:onProperty:hasConfidence;
owl:someValuesFrom:Confidence
];
rdfs:comment"The position of an entity in the automotive domain"@en;
rdfs:comment"It is the estimated location where the vehicle member joins the platoon. It is expressed in global coordinates (lat, long, alt), e.g. according to WGS 84."@en;
rdfs:comment"Sensors such as cameras, radars that are deployed along the road (e.g. at intersections and at poles along a highway). Road side sensors perform measurements, such as speed, position (relative or absolute), dimension, direction, etc. of road objects."@en;
rdfs:comment"Sensors such as cameras, radars that are deployed along the road (e.g. at intersections and at poles along a highway). Road side sensors perform measurements, such as speed, position (relative or absolute), dimension, direction, etc. of road objects."@en;
rdfs:comment"Position with respect to road topology (e.g. road, segment or lane) and lane characteristics (highway lane, road lane, bicycle lane, pavement, off-road)."@en;
rdfs:label"Road Topology Position"@en.
### https://saref.etsi.org/saref4auto/Role
### https://saref.etsi.org/saref4auto/Role
:Rolerdf:typeowl:Class;
:Rolerdf:typeowl:Class;
rdfs:comment"The role that can be assumed by a vehicle or a platoon"@en;
rdfs:comment"The role that can be assumed by a vehicle or a platoon"@en;
rdfs:comment"The route of a vehicle or of a platoon. The route of a platoon is defined as the route of the current vehicle leader in the platoon that other follower vehicles (partially) share"@en;
rdfs:comment"The route of a vehicle or of a platoon. The route of a platoon is defined as the route of the current vehicle leader in the platoon that other follower vehicles (partially) share. The route is a geo:Feature and can thus have a geometry."@en;
rdfs:label"Route"@en.
rdfs:label"Route"@en.
### https://saref.etsi.org/saref4auto/RoutePoint
:RoutePointrdf:typeowl:Class;
rdfs:subClassOf:Point;
rdfs:comment"The intermediate points of a route"@en;
rdfs:comment"A universally unique identifier (UUID) is a 128-bit number used to identify items and is also known as: globally unique identifier (GUID). In its canonical textual representation, the sixteen octets of a UUID are represented as 32 hexadecimal (base 16) digits, displayed in five groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 alphanumeric characters and four hyphens). UUID are documented in ISO/IEC 11578:1996 \"Information technology – Open Systems Interconnection – Remote Procedure Call (RPC)\" and in ITU-T Rec. X.667 ISO/IEC 9834-8:2005."@en;
rdfs:label"UUID"@en.
### https://saref.etsi.org/saref4auto/Vehicle
### https://saref.etsi.org/saref4auto/Vehicle
:Vehiclerdf:typeowl:Class;
:Vehiclerdf:typeowl:Class;
rdfs:subClassOfsaref:FeatureOfInterest,
rdfs:subClassOfsaref:FeatureOfInterest,
:AutomotiveObject,
:AutomotiveObject,
s4syst:System,
s4syst:System,
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasAbsolutePosition;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:AbsolutePosition
owl:hasValue:AbsolutePosition
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasFeatureKind;
owl:onProperty:hasFeatureKind;
owl:someValuesFrom:VehicleKind
owl:someValuesFrom:VehicleKind
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasAutomationLevel;
owl:onPropertysaref:hasState;
owl:someValuesFrom:AutomationLevel
owl:hasValue:VehicleAutomationLevel
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasBrakeCapacity;
owl:onPropertysaref:hasState;
owl:someValuesFrom:BrakeCapacity
owl:hasValue:PlatoonAutomationLevel
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasDestinationAddress;
owl:onProperty:hasBrakeCapacity;
owl:someValuesFrom:Address
owl:hasValue:BrakeCapacity
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasDestinationEndPoint;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:EndPoint
owl:hasValue:Destination
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasEnvironment;
owl:onProperty:hasEnvironment;
owl:someValuesFrom:VehicleEnvironment
owl:someValuesFrom:VehicleEnvironment
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasEstimatedRendezvousLocation;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:RendezvousLocation
owl:hasValue:RendezvousLocation
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasHeight;
owl:onProperty:hasHeight;
owl:someValuesFrom:Height
owl:hasValue:Height
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasIdentifier;
owl:onPropertysaref:hasIdentifier;
owl:someValuesFrom:Identifier
owl:minCardinality1
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onPropertysaref:hasProperty;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:Length
owl:hasValue:Length
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onPropertysaref:hasState;
owl:onPropertysaref:hasState;
owl:someValuesFrom:PlatoonVehicleState
owl:someValuesFrom:PlatoonVehicleState
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasPlatoonPosition;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:PlatoonPosition
owl:hasValue:PlatoonPosition
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasPlatoonRole;
owl:onProperty:hasPlatoonRole;
owl:someValuesFrom:PlatoonRole
owl:someValuesFrom:PlatoonRole
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasRelativePosition;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:RelativePosition
owl:hasValue:RelativePosition
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasRoadTopologyPosition;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:RoadTopologyPosition
owl:hasValue:RoadTopologyPosition
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onPropertysaref:hasRoute;
owl:onPropertysaref:hasProperty;
owl:someValuesFrom:Route
owl:someValuesFrom:Route
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasProperty;
owl:onProperty:hasProperty;
owl:someValuesFrom:Width
owl:hasValue:Width
],
[rdf:typeowl:Restriction;
owl:onProperty:isMemberOfPlatoon;
owl:someValuesFrom:Platoon
],
[rdf:typeowl:Restriction;
owl:onProperty:isMemberOfVehicleEnvironment;
owl:someValuesFrom:VehicleEnvironment
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onPropertys4syst:hasSubSystem;
owl:onPropertys4syst:hasSubSystem;
owl:someValuesFrom:ElectronicControlUnit
owl:someValuesFrom:ElectronicControlUnit
],
],
[rdf:typeowl:Restriction;
[rdf:typeowl:Restriction;
owl:onProperty:hasEstimatedJoiningTime;
owl:onPropertysaref:hasProperty;
owl:someValuesFromxsd:dateTime
owl:hasValue:EstimatedJoiningTime
];
];
rdfs:comment"A vehicle is the main object of interest in the automotive domain. Example of types of vehicles are car, truck, public transport and two-wheeler. See ETSI TS 102 894-2 spec for full list of vehicles, which are type of \"stations\". See also the SENSORIS data model for possible type of vehicles. The main IoT device considered in the vehicle is the ECU (part of the vehicle on board equipment, or OBE), see s4auto:ElectronicControlUnit class."@en;
rdfs:comment"A vehicle is the main object of interest in the automotive domain. Example of types of vehicles are car, truck, public transport and two-wheeler. See ETSI TS 102 894-2 spec for full list of vehicles, which are type of \"stations\". See also the SENSORIS data model for possible type of vehicles. The main IoT device considered in the vehicle is the ECU (part of the vehicle on board equipment, or OBE), see s4auto:ElectronicControlUnit class."@en;
rdfs:comment"The role the vehicle plays in traffic. If not specified, it is assumed that it takes a default value. Otherwise, possible values to be specified are: publicTransport, specialTransport, dangerousGoods, roadWork, rescue, emergency, safetyCar, agriculture, commercial, military, roadOperator, taxi."@en;
rdfs:comment"Non-motorized road users as well as users of VRU vehicles (L class of vehicles, for example mopeds or motorcycles, etc.) participating to the road traffic";
rdfs:comment"Non-motorized road users as well as users of VRU vehicles (L class of vehicles, for example mopeds or motorcycles, etc.) participating to the road traffic";
rdfs:comment"A Property for the automotive domain"@en;
rdfs:comment"A Property for the automotive domain"@en;
rdfs:label"Width"@en.
rdfs:label"Width"@en.
:Originrdf:typesaref:Property;
rdfs:comment"The origin of an entity (e.g., a vehicle or a route)"@en;
rdfs:label"Origin"@en.
:Destinationrdf:typesaref:Property;
rdfs:comment"The destination of an automotive object. For example, in a platoon, the current platoon leader defines the platoon destination. Following vehicles will share (partially) the route of the leader and can, therefore, have different final destinations."@en;
rdfs:label"Origin"@en.
:RoutePointrdf:typesaref:Property;
rdfs:comment"The intermediate point of a route."@en;
rdfs:label"Route Point"@en.
:Positionrdf:typesaref:Property;
rdfs:comment"The position of an entity in the automotive domain"@en;
rdfs:label"Position"@en.
:Addressrdf:typesaref:Property;
skos:broader:Position;
rdfs:comment"A position defined in terms of an address. It is out of scope of SAREF4AUTO to define the details of such an address. It is instead recommended to reuse existing ontologies that specify how to model an address in terms of Street, Postal Code, City, Region, Country, etc."@en;
rdfs:label"Address"@en.
:AbsolutePositionrdf:typesaref:Property;
skos:broader:Position;
rdfs:comment"Absolute position of an entity, e.g., a vehicle or road entity, defined in some coordinate system (e.g., a car is x,y,z)"@en;
rdfs:label"Absolute Position"@en.
:RelativePositionrdf:typesaref:Property;
skos:broader:Position;
rdfs:comment"Relative position of an entity, e.g., a vehicle or road entity, with respect to another entity, defined in some coordinate system (e.g., a car is x,y,z in front of another car)"@en;
rdfs:label"Relative Position"@en.
:RoadTopologyPositionrdf:typesaref:Property;
skos:broader:Position;
rdfs:comment"Position with respect to road topology (e.g. road, segment or lane) and lane characteristics (highway lane, road lane, bicycle lane, pavement, off-road)."@en;
rdfs:label"Road Topology Position"@en.
:PlatoonPositionrdf:typesaref:Property;
skos:broader:Position;
rdfs:comment"A position defined as the index of the vehicle in the platoon starting from zero (leader) up to N (trailing vehicle)"@en;
rdfs:label"Platoon Position"@en.
:JoiningTimerdf:typesaref:Property;
rdfs:comment"The time a vehicle is joining a platoon";
rdfs:label"Joining Time"@en.
:RendezvousLocationrdf:typesaref:Property;
rdfs:comment"The location where the vehicle member joins a platoon";
rdfs:label"Rendez-vous Location"@en.
### SAREF patterns for states: Categorizing states for the automotive domain
### SAREF patterns for states: Categorizing states for the automotive domain
rdfs:comment"The state of shape of an entity: i.e., Sphere, Torus, Cylinder, Cone, Ellipsoid, Cube, Cuboid, Pyramid, Prism, Multiple shapes"@en;
rdfs:comment"The state of shape of an entity: i.e., Sphere, Torus, Cylinder, Cone, Ellipsoid, Cube, Cuboid, Pyramid, Prism, Multiple shapes"@en;
rdfs:label"Shape"@en.
rdfs:label"Shape"@en.
### SAREF Pattern for states: automation level
:PlatoonAutomationLevelrdf:typesaref:State;
rdfs:comment"A level of automation is defined for a vehicle that it is platooning. For example, in the ENSEMBLE project there are three levels of platoon automation defined: Level A, Level B, Level C. Level C represents the highest level of automation for platooning in terms of longitudinal and lateral control, shortest time gap supported, wider range of situations handled and support for merging of entire platoons."@en;
rdfs:label"PlatoonAutomationLevel"@en.
:PlatoonAutomationLevelArdf:typesaref:State;
skos:broader:PlatoonAutomationLevel;
rdfs:label"Platoon Automation Level A"@en;
rdfs:comment"Platoon Automation Level A [Source: ENSEMBLE project]."@en.
:PlatoonAutomationLevelBrdf:typesaref:State;
skos:broader:PlatoonAutomationLevel;
rdfs:label"Platoon Automation Level B"@en;
rdfs:comment"Platoon Automation Level B [Source: ENSEMBLE project]."@en.
:PlatoonAutomationLevelCrdf:typesaref:State;
skos:broader:PlatoonAutomationLevel;
rdfs:label"Platoon Automation Level C"@en;
rdfs:comment"Platoon Automation Level C [Source: ENSEMBLE project]."@en.
:VehicleAutomationLevelrdf:typesaref:State;
rdfs:comment"""According to SAE J3016, there are five levels of automation for a vehicle:
- Level 0: No Driving Automation.
- Level 1: Driver assistance.
- Level 2: Partial driving automation.
- Level 3: Conditional driving automation.
- Level 4: High driving automation.
- Level 5: Full Driving automation."""@en;
rdfs:label"Vehicle Automation Level"@en.
:VehicleAutomationLevel0rdf:typesaref:State;
skos:broader:VehicleAutomationLevel;
rdfs:label"Vehicle Automation Level 0"@en;
rdfs:comment"Vehicle Automation Level 0: No Driving Automation [Source: SAE J3016]."@en.
rdfs:comment"Vehicle Automation Level 4: High driving automation [Source: SAE J3016]."@en.
:VehicleAutomationLevel5rdf:typesaref:State;
skos:broader:VehicleAutomationLevel;
rdfs:label"Vehicle Automation Level 5"@en;
rdfs:comment"Vehicle Automation Level 5: Full Driving automation [Source: SAE J3016]."@en.
### SAREF Pattern for identifiers
:hasStationIDrdf:typeowl:DatatypeProperty;
rdfs:subPropertyOfsaref:hasIdentifier;
rdfs:comment"Links vehicles and platoons to their identifier as defined in ETSI TS 102 894-2."@en;
rdfs:label"has Station ID"@en.
:hasUUIDrdf:typeowl:DatatypeProperty;
rdfs:subPropertyOfsaref:hasIdentifier;
rdfs:comment"A universally unique identifier (UUID) is a 128-bit number used to identify items and is also known as: globally unique identifier (GUID). In its canonical textual representation, the sixteen octets of a UUID are represented as 32 hexadecimal (base 16) digits, displayed in five groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 alphanumeric characters and four hyphens). UUID are documented in ISO/IEC 11578:1996 \"Information technology – Open Systems Interconnection – Remote Procedure Call (RPC)\" and in ITU-T Rec. X.667 ISO/IEC 9834-8:2005."@en;