GENIAL! Basic Ontology
language en

GENIAL! Basic Ontology

Release: 2024-09-12

This version:
http://w3id.org/gbo/0.2.4
Latest version:
http://w3id.org/gbo
Revision:
0.2.4
Authors:
Frank Wawrzik
Contributors:
Christoph Grimm
Peter Neumann
Imported Ontologies:
bfo.owl
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
https://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Frank Wawrzik. GENIAL! Basic Ontology. Revision: 0.2.4. Retrieved from: http://w3id.org/gbo/0.2.4
Vocabulary maintained at:
https://github.com/wawrzik/GENIALOntologies/tree/master/OntologyModuleSuite/GENIAL!BasicOntology
Ontology Specification Draft

Abstract

The GENIAL! Basic Ontology is a heavyweight ontology built for the structuring of and reasoning with system and electronic engineering artifacts.

Introduction back to ToC

The GENIAL! Basic Ontology (GBO) was designed to describe the areas of systems engineering and electronic development. The goal is to be able to consistenly describe systems and their parts in a physical way, but also with all its related factors for their development. Thus their properties, their functions, requirements and their dependencies can also be described. This ontology facilitates building complete knowledge bases for electronic devices, in comparison to for example the semantic sensor network ontology or the digital reference ontology. This is due to its structure and selected terms, which can represent these devices as a whole.
GBO is built upon two features. The first one includes the incorporation and usage of the Basic Formal Ontology (BFO). All concepts are aligned with BFO and BFO's design principles are consistently applied to GBO and the knowledge base content that is created with GBO. Further GBO is built according to the ISO26262 standard in automotive electronic safety, which makes electronic safety and automotive development a related topic. The second feature is a heavyweight approach to ontology modelling. The definitions of ISO26262 have been formalized meticulously and are available for reasoning purposes. GBO is intended to be specifically used with reasoners in order to improve the overall quality of knowlege bases or knowledge graphs built with GBO. This is a different approach than how most ontologies are currently built. The goal is to build an extensive high quality knowledge base of systems and electronic engineering. One application, but not limited to it, is the exchange of knowledge in the automotive value chain. Key terms to describe physical systems are: system, hardware, software, component, hardware component, hardware part, hardware subpart, hardware elementary subpart, software component and software unit.
Figure 1 gives a core overview of the physical parts of the ontology and how they are aligned with BFO. Figure 2 gives a core overview with functions and properties. Both Figures are identical for version 0.2.3 and 0.2.4.
gboCoreOverview2
Fig. 2 GENIAL! Basic Ontology Core 2 (click to enlarge)
gboCoreOverview1
Fig. 1 GENIAL! Basic Ontology Core 1 (click to enlarge)

Namespace declarations

Table 1: Namespaces used in the document
[Ontology NS Prefix]<http://w3id.org/gbo>
dc<http://purl.org/dc/elements/1.1/>
foaf<http://xmlns.com/foaf/0.1/>
gbo<http://w3id.org/gbo#>
obo<http://purl.obolibrary.org/obo/>
om-2<http://www.ontology-of-units-of-measure.org/resource/om-2/>
owl<http://www.w3.org/2002/07/owl#>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns#>
rdfs<http://www.w3.org/2000/01/rdf-schema#>
sosa<http://www.w3.org/ns/sosa/>
terms<http://purl.org/dc/terms/>
vann<http://purl.org/vocab/vann/>
xml<http://www.w3.org/XML/1998/namespace>
xsd<http://www.w3.org/2001/XMLSchema#>

GENIAL! Basic Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

GENIAL! Basic Ontology: Description back to ToC

Basic Ontology with general vocabulary for serving as a ground to execute basic tasks of the tool AGILA and share common upper level for all classes in GENIAL!. It supports the modelling of microlectronic components like sensors, acutators, processors and software along the automotive value chain.

Cross-reference for GENIAL! Basic Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by GENIAL! Basic Ontology.

Classes

actuatingc back to ToC or Class ToC

IRI: http://w3id.org/gbo#actuating

A gbo:function to change or control an object
has super-classes
function c
is disjoint with
hardware elementary subpart c

actuatorc back to ToC or Class ToC

IRI: http://w3id.org/gbo#actuator

An actuator is a hardware component that implements some actuating function and is responsible for moving or controlling a mechanism or system.
Not defined in ISO26262
has super-classes
Actuator c, hardware component c

automatic cruise controlc back to ToC or Class ToC

IRI: http://w3id.org/gbo#automatic_cruise_control

An “automatic cruise control” is a vehicle function that can be implemented, using different ECUs and a variety of sensor technology (e.g. Radar, Lidar, Camera).
has super-classes
vehicle function c

camerac back to ToC or Class ToC

IRI: http://w3id.org/gbo#camera

has super-classes
sensor c

componentc back to ToC or Class ToC

IRI: http://w3id.org/gbo#component

According to ISO26262: non-system level element (3.41) that is logically or technically separable and is comprised of more than one hardware part (3.71) or one or more software units (3.159). A component is a part of a system (3.163).
Example 
A microcontroller
is equivalent to
non system level element c and (((comprised of op some hardware part c) and (comprised of op min 2 hardware part c)) or ((comprised of op some software component c) or (comprised of op some software unit c))) and (part of directly op some system c)
has sub-classes
controller c, hardware component c, software component c

contextc back to ToC or Class ToC

IRI: http://w3id.org/gbo#context

The circumstances that form the setting for an event, statement or idea and in terms of which it can be fully understood, e.g. Market, legal frame conditions
has sub-classes
legal boundary conditon c, market c

controllerc back to ToC or Class ToC

IRI: http://w3id.org/gbo#controller

has super-classes
component c

dependencyc back to ToC or Class ToC

IRI: http://w3id.org/gbo#dependency

A gbo:property that is a boolean or arithmetic function / equation on properties. Used to be calculated with GENIAL constraint propagation. As string in LaTex syntax.
has super-classes
property c
is in range of
depends on op

ECUc back to ToC or Class ToC

IRI: http://w3id.org/gbo#electronic_control_unit

has super-classes
system c

elementc back to ToC or Class ToC

IRI: http://w3id.org/gbo#element

Continuant that is (according to ISO 26262) a system (3.163), components (3.21) (hardware or software), hardware parts (3.71), or software units (3.159)
has super-classes
B F O 0000002 c
has sub-classes
non system level element c, system level element c
is in domain of
has property op, implements op
is in range of
is implemented by op

embedded softwarec back to ToC or Class ToC

IRI: http://w3id.org/gbo#embedded_software

a software that is (according to ISO 26262) fully-integrated software to be executed on a processing element (3.113)
has super-classes
software c

engineered objectc back to ToC or Class ToC

IRI: http://w3id.org/gbo#engineered_object

An object created, designed or engineered by humans.
has super-classes
B F O 0000030 c
has sub-classes
hardware c, mechanical object c, system level element c

functionc back to ToC or Class ToC

IRI: http://w3id.org/gbo#function

A bfo:function that an element (e.g. system, component, hardware or software) implements.
has super-classes
B F O 0000034 c
has sub-classes
actuating c, processing c, sensing c, vehicle function c
is in domain of
is implemented by op

functional requirementc back to ToC or Class ToC

IRI: http://w3id.org/gbo#functional_requirement

A requirement that specifies something the system should do.
Source
https://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/
has super-classes
requirement c

hardwarec back to ToC or Class ToC

IRI: http://w3id.org/gbo#hardware_element

From definition of element: Note 1 to entry: When “software element” or “hardware element” is used, this phrase denotes an element of software only or an element of hardware only, respectively.
is equivalent to
hardware component c or hardware elementary subpart c or hardware part c or hardware subpart c
has super-classes
engineered object c, non system level element c
is disjoint with
software c

hardware componentc back to ToC or Class ToC

IRI: http://w3id.org/gbo#hardware_component

No ISO definition. Formal Definition derived from other definitions.
Example 
actuator
multi core
sensor
is equivalent to
hardware c and (comprised of op only hardware part c) and (comprised of op min 2 hardware part c)
has super-classes
component c
has sub-classes
actuator c, sensor c
is disjoint with
software component c, hardware elementary subpart c, hardware part c, hardware subpart c

hardware elementary subpartc back to ToC or Class ToC

IRI: http://w3id.org/gbo#hardware_elementary_subpart

smallest portion of a hardware subpart (3.73) considered in safety (3.132) analysis
Example 
A flip-flop of the ALU with its logic cone, a register.
is equivalent to
hardware c and (part of directly op only hardware subpart c)
is disjoint with
actuating c, hardware component c, hardware part c, hardware subpart c

hardware partc back to ToC or Class ToC

IRI: http://w3id.org/gbo#hardware_part

A piece of hardware that is (according to ISO 26262) a portion of a hardware component (3.21) at the first level of hierarchical decomposition.
Example 
The CPU of a microcontroller, a resistor, flash array of a microcontroller.
is equivalent to
hardware c and (part of directly op only component c)
has sub-classes
processing element c
is disjoint with
hardware component c, hardware elementary subpart c, hardware subpart c

hardware subpartc back to ToC or Class ToC

IRI: http://w3id.org/gbo#hardware_subpart

Portion of a hardware part (3.71) that can be logically divided and represents second or greater level of hierarchical decomposition.
Example 
ALU of a CPU of a microcontroller
register bank of a CPU
is equivalent to
hardware c and (has part directly op only hardware elementary subpart c or hardware subpart c) and (part of directly op only hardware part c or hardware subpart c)
is disjoint with
hardware component c, hardware elementary subpart c, hardware part c

itemc back to ToC or Class ToC

IRI: http://w3id.org/gbo#item

System level element that is (according to ISO26262) system (3.163) or combination of systems (3.163), to which ISO 26262 is applied, that implements a function or part of a function at the vehicle level. Note 1 to entry: See vehicle function (3.178).
is equivalent to
(system c or (has part op some system c) or (part of op some system c)) and (implements op only vehicle function c)
has super-classes
system level element c

lidarc back to ToC or Class ToC

IRI: http://w3id.org/gbo#lidar

has super-classes
sensor c

marketc back to ToC or Class ToC

IRI: http://w3id.org/gbo#market

has super-classes
context c

material objectc back to ToC or Class ToC

IRI: http://w3id.org/gbo#material_object

has super-classes
B F O 0000030 c

measurec back to ToC or Class ToC

IRI: http://www.ontology-of-units-of-measure.org/resource/om-2/measure

A bfo:quality that are amounts of quantities.
has super-classes
B F O 0000019 c
is in domain of
has unit op
is in range of
has value op

mechanical objectc back to ToC or Class ToC

IRI: http://w3id.org/gbo#mechanical_object

An engineered object that has mechanical characteristics. They can be either dominant mechanical characteristics like in a vehicle or wheel or less dominant like in a battery.
Example 
vehicle
has super-classes
engineered object c

non functional requirementc back to ToC or Class ToC

IRI: http://w3id.org/gbo#non_functional_requirement

A requirement that describes how the system works.
Source
https://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/
has super-classes
requirement c

non system level elementc back to ToC or Class ToC

IRI: http://w3id.org/gbo#non_system_level_element

An element that is not on the system-level
has super-classes
element c
has sub-classes
hardware c, software c
is disjoint with
system level element c

operating timec back to ToC or Class ToC

IRI: http://w3id.org/gbo#operating_time

A quantity that is (according to ISO 26262) a cumulative time that an item (3.84) or element (3.41) is functioning, including degraded modes.
has super-classes
quantity c

performancec back to ToC or Class ToC

IRI: http://w3id.org/gbo#performance

a gbo:property on how well a person, machine, etc. does a piece of work or an activity
Source
https://dictionary.cambridge.org/dictionary/english/performance
has super-classes
property c

processingc back to ToC or Class ToC

IRI: http://w3id.org/gbo#processing

A gbo:function to calculate a set of instructions or software
has super-classes
function c

processing elementc back to ToC or Class ToC

IRI: http://w3id.org/gbo#processing_element

(according to ISO26262) hardware part (3.71) providing a set of functions for data processing, normally consisting of a register set, an execution unit, and a control unit
has super-classes
hardware part c
is in domain of
executes op
is in range of
is executed by op

propertyc back to ToC or Class ToC

IRI: http://w3id.org/gbo#property

A quality or characteristic of an element, hardware, software or function. A property has a boolean, integer, or real variable through the measure class. Specifically properties can be unquantified and quantified. But quantified properties are quantities.
Example 
drag coefficient
power
temperature
has super-classes
B F O 0000019 c
has sub-classes
dependency c, performance c, quantity c, requirement c
is in domain of
depends on op, has value op
is in range of
has property op

quantityc back to ToC or Class ToC

IRI: http://www.ontology-of-units-of-measure.org/resource/om-2/quantity

A quantity is a (property that is quanitifiable and a) representation of a quantifiable (standardised) aspect (such as length, mass, and time) of a phenomenon (e.g., a star, a molecule, or a food product). Quantities are classified according to similarity in their (implicit) metrological aspect, e.g. the length of my table and the length of my chair are both classified as length.
has super-classes
property c
has sub-classes
operating time c

radarc back to ToC or Class ToC

IRI: http://w3id.org/gbo#radar

has super-classes
sensor c

requirementc back to ToC or Class ToC

IRI: http://w3id.org/gbo#requirement

A property that is wanted or needed.
Source
https://www.merriam-webster.com/dictionary/requirement
has super-classes
property c
has sub-classes
functional requirement c, non functional requirement c

sensingc back to ToC or Class ToC

IRI: http://w3id.org/gbo#sensing

A gbo:function to perceive an object
has super-classes
function c

sensorc back to ToC or Class ToC

IRI: http://w3id.org/gbo#sensor

Hardware component that implements some sensing function.
Not defined in ISO26262
Example 
accelerometer
humidity sensor
radar
has super-classes
Sensor c, hardware component c
has sub-classes
camera c, lidar c, radar c

social objectc back to ToC or Class ToC

IRI: http://w3id.org/gbo#social_object

An object or object aggregate that stands in a social role.
Example 
organisation
person
has super-classes
B F O 0000040 c

softwarec back to ToC or Class ToC

IRI: http://w3id.org/gbo#software_element

From definition of element: Note 1 to entry: When “software element” or “hardware element” is used, this phrase denotes an element of software only or an element of hardware only, respectively.
has super-classes
B F O 0000031 c, non system level element c
has sub-classes
embedded software c
is in domain of
is executed by op
is in range of
executes op
is disjoint with
hardware c

software componentc back to ToC or Class ToC

IRI: http://w3id.org/gbo#software_component

one or more softwareunits (3.159)
is equivalent to
software c and (comprised of op some software unit c) and (comprised of op only software unit c) and (comprised of op min 1 software unit c)
has super-classes
component c
is disjoint with
hardware component c

software unitc back to ToC or Class ToC

IRI: http://w3id.org/gbo#software_unit

a piece of software that is (according to ISO26262) an atomic level software component (3.157) of the software architecture (3.1) that can be subjected to stand-alone testing (3.169)
is equivalent to
software c and (comprised of op only software c) and (comprised of op exactly 0 software c)

systemc back to ToC or Class ToC

IRI: http://w3id.org/gbo#system

System level element that is according to ISO 26262: set of components (3.21) or subsystems that relates at least a sensor, a controller and an actuator with one another. Note 1 to entry: The related sensor or actuator can be included in the system, or can be external to the system.
is equivalent to
system level element c and ((comprised of op some actuator c) and (comprised of op some controller c) and (comprised of op some sensor c))
has sub-classes
ECU c

system level elementc back to ToC or Class ToC

IRI: http://w3id.org/gbo#system_level_element

An element that is on the system level
has super-classes
element c, engineered object c
has sub-classes
item c
is disjoint with
non system level element c

unitc back to ToC or Class ToC

IRI: http://www.ontology-of-units-of-measure.org/resource/om-2/unit

A quality that is any standard used for comparison in measurements.
has super-classes
B F O 0000019 c
is in range of
has unit op

vehicle functionc back to ToC or Class ToC

IRI: http://w3id.org/gbo#vehicle_function

A gbo:function that is (according to ISO26262) behaviour of the vehicle, intended by the implementation of one or more items (3.84), that is observable by the customer.
Example 
An “automatic cruise control” is a vehicle function that can be implemented, using different ECUs and a variety of sensor technology (e.g. Radar, Lidar, Camera).
has super-classes
function c
has sub-classes
automatic cruise control c

Object Properties

depends onop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#depends_on

Links properties with dependencies.

has characteristics: symmetric

has domain
property c
has range
dependency c

executesop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#executes

Relates a processing unit to the software which runs on it
has domain
processing element c
has range
software c
is inverse of
is executed by op

has partop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#has_part

models hierarchical de-composition/integration
is inverse of
part of op

has part directlyop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#has_part_directly

models hierarchical de-composition/integration of direct parts

has propertyop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#has_property

links elements to their properties
has domain
element c
has range
property c
is inverse of
property of op

has unitop back to ToC or Object Property ToC

IRI: http://www.ontology-of-units-of-measure.org/resource/om-2/hasUnit

Links measure with their unit
has domain
measure c
has range
unit c

has valueop back to ToC or Object Property ToC

IRI: http://www.ontology-of-units-of-measure.org/resource/om-2/hasValue

Links properties or quantities to their measure (concrete value)
has domain
property c
has range
measure c

implementsop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#implements

Links elements their functions
has domain
element c
is inverse of
is implemented by op

is executed byop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#is_executed_by

Relates the software to the processing unit on which it runs
has domain
software c
has range
processing element c
is inverse of
executes op

is implemented byop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#is_implemented_by

Links functions to their elements
has domain
function c
has range
element c
is inverse of
implements op

part ofop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#part_of

models hierarchical de-composition/integration
has sub-properties
part of directly op
is inverse of
has part op

part of directlyop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#part_of_directly

has super-properties
part of op

property ofop back to ToC or Object Property ToC

IRI: http://w3id.org/gbo#property_of

links properties back to their components
is inverse of
has property op

Legend back to ToC

c: Classes
op: Object Properties

References back to ToC

Frank Wawrzik and Andreas Lober. A reasoner-challenging ontology from the microelectronics domain. In ISWC 2021 The 20th International Semantic Web Conference - Semantic Reasoning Evaluation Challenge (SemREC), 10 2021.
F. Wawrzik, K. A. Rafique, F. Rahman, C. Grimm, Ontology learning applications of knowledge base construction for microelectronic systems information, Information 14 (2023). URL: https://www.mdpi.com/2078-2489/14/3/176. doi:10.3390/info14030176.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.