The AUTOMOTIVE ONTOLOGY (AUTO) defines the shared conceptual structures in the automotive industry. It is an OWL ontology. It is built upon the auto schema.org extension created by the W3C Automotive Ontology Community Group. AUTO's development process follows the best practices established by the EDMC FIBO Community.
License: MIT License
There is resource ClearanceLamp in VehicleParts that has multiple labels.
This violates one of the EDMC principles - see https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
Slightly modified class tree. Completed missing descriptions (skos:definition, skos:example, skos:comment) from SAE-J3016 documentation, removed repetitions. Added autonomy classes.
Ontology uses the illegal punning, where one IRI is used for an ObjectProperty and DataProperty- see the warnings below:
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/model in punning not allowed [ObjectProperty: model, DataProperty: model]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/track in punning not allowed [ObjectProperty: track, DataProperty: track]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/row3PosCount in punning not allowed [ObjectProperty: row3PosCount, DataProperty: row3PosCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/wheelDiameter in punning not allowed [DataProperty: wheelDiameter, ObjectProperty: wheelDiameter]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/brand in punning not allowed [ObjectProperty: brand, DataProperty: brand]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/height in punning not allowed [ObjectProperty: height, DataProperty: height]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/fuelType in punning not allowed [DataProperty: fuelType, ObjectProperty: fuelType]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/row5PosCount in punning not allowed [ObjectProperty: row5PosCount, DataProperty: row5PosCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/refuelPosition in punning not allowed [ObjectProperty: refuelPosition, DataProperty: refuelPosition]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/row4PosCount in punning not allowed [ObjectProperty: row4PosCount, DataProperty: row4PosCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/bodyType in punning not allowed [DataProperty: bodyType, ObjectProperty: bodyType]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/tireWidth in punning not allowed [ObjectProperty: tireWidth, DataProperty: tireWidth]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/tankCapacity in punning not allowed [DataProperty: tankCapacity, ObjectProperty: tankCapacity]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/rowCount in punning not allowed [ObjectProperty: rowCount, DataProperty: rowCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/doorCount in punning not allowed [ObjectProperty: doorCount, DataProperty: doorCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/year in punning not allowed [ObjectProperty: year, DataProperty: year]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/displacement in punning not allowed [DataProperty: displacement, ObjectProperty: displacement]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/steeringWheelSide in punning not allowed [DataProperty: steeringWheelSide, ObjectProperty: steeringWheelSide]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/row1PosCount in punning not allowed [DataProperty: row1PosCount, ObjectProperty: row1PosCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/row2PosCount in punning not allowed [DataProperty: row2PosCount, ObjectProperty: row2PosCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/driveType in punning not allowed [ObjectProperty: driveType, DataProperty: driveType]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/towWeight in punning not allowed [DataProperty: towWeight, ObjectProperty: towWeight]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/wheelbase in punning not allowed [DataProperty: wheelbase, ObjectProperty: wheelbase]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/wmi in punning not allowed [DataProperty: wmi, ObjectProperty: wmi]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/length in punning not allowed [DataProperty: length, ObjectProperty: length]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/transmissionType in punning not allowed [DataProperty: transmissionType, ObjectProperty: transmissionType]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/vin in punning not allowed [ObjectProperty: vin, DataProperty: vin]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/axleCount in punning not allowed [DataProperty: axleCount, ObjectProperty: axleCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/engineConfiguration in punning not allowed [ObjectProperty: engineConfiguration, DataProperty: engineConfiguration]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/maxTorque in punning not allowed [DataProperty: maxTorque, ObjectProperty: maxTorque]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/maxPower in punning not allowed [ObjectProperty: maxPower, DataProperty: maxPower]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/wheelWidth in punning not allowed [ObjectProperty: wheelWidth, DataProperty: wheelWidth]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/driverPostion in punning not allowed [DataProperty: driverPostion, ObjectProperty: driverPostion]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/width in punning not allowed [DataProperty: width, ObjectProperty: width]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/wheelCount in punning not allowed [DataProperty: wheelCount, ObjectProperty: wheelCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/grossWeight in punning not allowed [ObjectProperty: grossWeight, DataProperty: grossWeight]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/curbWeight in punning not allowed [DataProperty: curbWeight, ObjectProperty: curbWeight]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/gearCount in punning not allowed [DataProperty: gearCount, ObjectProperty: gearCount]
WARN 18:00:21 Illegal redeclarations of entities: reuse of entity https://spec.edmcouncil.org/auto/ontology/VS/VehicleSignals/tireDiameter in punning not allowed [ObjectProperty: tireDiameter, DataProperty: tireDiameter]
For the explanation why this kind of punning should be avoided see https://pure.uva.nl/ws/files/763164/68628_06.pdf page 59: "Punning enables straightforward meta modelling without the impact on decidability that RDF and OWL Full modelling have. Because of interaction with the semantics of OWL Full, punning is not allowed between data and object properties."
There is resource ActuableSignal in VehicleSignals that has multiple labels.
This violates one of the EDMC principles - see https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
There are multiple resources in VehicleCore that have multiple labels.
This violates one of the EDMC principles.
The great many resources in Vehicle signals ontology do not have the required annotations, in particular labels.
There are multiple resources in VehicleSignals that do not have labels.
This violates one of the EDMC principles - see https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
Some labels in https://spec.edmcouncil.org/auto/ontology/DE/TrafficEnvironment/ do not follow the standards defined in https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
The classes added in #86 need similar logical descriptions as the other classes.
We need to specify the configuration for onto-viewer.
Auto ontology does not implement the Prod/Dev structure of FIBO.
As an explanatory note on 'Trip' says: "Performance of the DDT during a given trip may be accomplished in whole or in part by a driver, driving automation system, or both." the relation should not be of type 'exactly 1'. I would rather put 'some.'
I assume here that instances of class 'Operate Motor Vehicle' and its subclass 'Sustained Operation Of A Vehicle' are homogeneous because they are in the whole of a certain level of autonomy. Then a trip in which the level of autonomy is changing should be related to many different instances of 'Operate Motor Vehicle.'
Line 23 in 167266f
Some labels in https://spec.edmcouncil.org/auto/ontology/DE/TrafficIncidents/ do not follow the standards defined in https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
Some labels in https://spec.edmcouncil.org/auto/ontology/VC/VehicleCore/ do not follow the standards defined in https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
There are multiple resources in VehicleSignals that do not have labels.
This violates one of the EDMC principles - see https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
There are multiple resources in VehicleSignals that do not have labels, specifically, among others:
This violates one of the EDMC principles - see https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
There are three subclasses of https://spec.edmcouncil.org/auto/ontology/DE/CarControl/OperationalEffort and https://spec.edmcouncil.org/auto/ontology/DE/CarControl/TacticalEffort that are not satisfiable:
Note that also https://spec.edmcouncil.org/auto/ontology/DE/CarControl/DynamicDrivingTask is not satisfiable.
The reason for these issues is that OperationalEffort and TacticalEffort are claimed to be disjoint.
The set of hygiene tests needs to be updated.
All actual references to the resources from https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/Values are now gone, but there are some references in metadata files to IRI https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/Values.
They are not needed and can be safely removed.
Some labels in https://spec.edmcouncil.org/auto/ontology/DE/CarControl/ do not follow the standards defined in https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
Multiple classes and relations in Auto are missing definitions.
auto-dev ontology makes frequent use of the xsd:date datatype:
This datatype is not allowed in an OWL 2.0 ontology, i.e., xsd:date is not a datatype recognised by OWL 2.0 - see: https://www.w3.org/TR/owl2-syntax/#Datatype_Maps. On the other hand, auto-dev makes use of the qualified cardinality restrictions, which requires OWL 2.0.
This incongruency should be removed, preferrably by replacing xsd:date with xsd:dateTime datatype.
At least xsd:date should be removed as the range from vehicleModelDate and dateVehicleFirstRegistered - currently both properties have xsd:date and xsd:dateTime as ranges, which Pellet reasoner finds wrong:
See also: edmcouncil/fibo#983 (comment).
There are multiple violations of given rule:
Every class, property, and individual must have a label, at a minimum, with additional annotations as described below. It should be the natural language (American English) representation of that entity, space-separated, including the language tag for English.
In resources:
https://spec.edmcouncil.org/auto/ontology/DE/TrafficEnvironment/Junction and all its subclasses are not satisfiable because the former is claimed to be a subclass of https://spec.edmcouncil.org/auto/ontology/DE/TrafficEnvironment/RoadPart and https://spec.edmcouncil.org/auto/ontology/DE/TrafficEnvironment/PartOfTrafficway, which are claimed to be disjoint.
The current set of hygiene tests was a copy of those from FIBO.
We need to adapt them to the needs of the AUTO ontologies.
Resource Angle doesn't have a label
Every class, property, and individual must have a label, at a minimum, with additional annotations as described below. It should be the natural language (American English) representation of that entity, space-separated, including the language tag for English.
Resource Location has multiple labels.
FIBO enforces both unique labels and unique names conventions, even across namespaces. There is content in the provisional and informative ontologies that does not adhere to these policies, but for any released ontology, we require unique naming and unique labeling.
Resource bodyStyle has multiple labels.
FIBO enforces both unique labels and unique names conventions, even across namespaces. There is content in the provisional and informative ontologies that does not adhere to these policies, but for any released ontology, we require unique naming and unique labeling.
One restriction on FullDrivingAutomation makes this level of automation dependent on a human action.
I think this is wrong or at least incongruent with the textual definition.
We need to add the appropriate copyright information to VehicleAutomationLevels.rdf.
Dear EDMC AUTO community,
I am thrilled to share some exciting news with all of you! Our paper titled Ontology of Autonomous Driving based on the SAE J3016 standard has been accepted for publication in the prestigious Semantic Web journal. This is a significant milestone in our journey towards advancing autonomous driving technologies and standards.
You can access the full text of the paper by following this link: PDF. We encourage you to read and explore the comprehensive insights presented in the paper, which will undoubtedly contribute to the collective knowledge of the autonomous driving field.
Furthermore, we have also published an OWL version of the ontology associated with the paper. This resource will be valuable for those looking to implement and work with the ontology in their projects. The ontology has been created within a project led by Piotr Kulicki and The John Paul II Catholic University of Lublin (NCN 2017/26/M/HS1/01092). You can find the ontology in the project's GitHub repository here: ontology-autonomous-driving.
As a suggestion, we encourage you to consider adding the paper to the documentation of the EDMC AUTO repository. This will provide a centralized location for all related resources and make it easier for users to access and reference the paper in the context of the ontology.
We believe that this work will be instrumental in advancing the state-of-the-art in autonomous driving, and we hope that it serves as a valuable resource for the EDMC AUTO community and beyond. Feel free to provide feedback, ask questions, or engage in discussions related to the paper and ontology on the GitHub repository.
Thank you for your continued support and enthusiasm for our research endeavors. We look forward to your involvement and contributions as we continue to drive innovation in the field of autonomous driving.
Best regards,
Robert Trypuz
Former Member, The John Paul II Catholic University of Lublin
There are multiple resources in VehicleSignals which are missing labels, that contradicts to the guide requirements.
Some labels in https://spec.edmcouncil.org/auto/ontology/VC/VehicleParts/ do not follow the standards defined in https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#naming-and-labeling-conventions.
We are going to start developing an ontology for vehicle automation levels, which will be based on J3016 “Levels of Driving Automation” standard.
Condition is ambiguous, and subclasses of 'condition' in AutonomousVehicles fall under different meanings:
I think it would better not be one class.
Auto seems to use three FIBO ontologies:
<owl:imports rdf:resource="https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/Analytics/"/>
<owl:imports rdf:resource="https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/"/>
<owl:imports rdf:resource="https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/Values/"/>
It seems to me that the last one is no longer in FIBO, so its references in auto should be removed.
As far as I can see it is not used there in any substantial way.
auto-vs-vsso is claimed to be created at 2018-01-10, which values does not belong to the lexical space of xsd:dateTime datatype.
auto-vs-vsso: rdf:type owl:Ontology ;
rdfs:comment "The GENIVI VSS Ontology (VSSO) has been initially created by Benjamin Klotz, Daniel Wilms, and Raphael Troncy (see http://automotive.eurecom.fr/vsso). VSSO, as created by Benjamin Klotz, Daniel Wilms, and Raphael Troncy, is available under the Creative Commons Attribution 4.0 International license; see http://creativecommons.org/licenses/by/4.0/. VSSO describes the car's attributes, branches and signals defined in GENIVI's Vehicle Signal Specification."@en ;
rdfs:label "Vehicle Signals Ontology (VSSO)" ;
terms:abstract "This Vehicle Signals Ontology (VSSO) describes the car's parts and signals. It is based on the GENIVI's Vehicle Signal Specification." ;
terms:created "2018-01-10"^^xsd:dateTime ;
In order to publish VehicleAutomationLevels.rdf we need to change the metadata ontologies.
These two properties seem to be duplicates:
I suggest we keep 1 because it is more often used and better described.
The recent changes in the AV domain require updates of metadata ontology files.
See
ERROR:https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Provisional is referenced by hasMaturityLevel but has no type.
in jenkins job PR-54 console
Missing import
<owl:imports rdf:resource="https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/"/>
before the following lines:
Line 50 in 167266f
Line 52 in 167266f
Line 48 in 167266f
In the current version of auto-dev automation levels are modelled both as classes and as named individuals, e.g., the level of high driving automation is modelled as:
I think that either invididuals or classes must be removed.
Given edmcouncil/ontology-publisher#81 we need to add the set of queries specific for vocabulary creation for auto.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.