Basic European Road OTL
type: Ontology
imports: prov
imports: cmo-simple-cdt
creator: <http://www.roadotl.eu>
description: The European Road OTL core definitions.
abstract: This is the main ontology within the European Road OTL framework that serves as a hub for linking concepts (schema elements) and data between different domain ontologies. This ontology uses cmo and prov-o as upper ontologies to provide a basic and proven structure. Based on these, it defines a number of basic concepts relevant for road asset management from a lifecycle perspective such as: - Provenance based on the w3c prov-o ontology - The General AEC Reference Model (GARM) [Gielingh, 2008 - A THEORY FOR THE MODELLING OF COMPLEX AND DYNAMIC SYSTEMS - https://www.itcon.org/papers/2008_27.content.03759.pdf] - Distinction between physical and spatial objects - Decomposition of objects (assembly/part) - Connectivity between objects through ports and connections - Location and shape - Activities - Baselines (lifecycle stages) - Suitability - Linked documents (also to non-Linked data) - Quantities and units This ontology can be used as a basic data model according to the above listing. To provide more semantics, e.g. regarding asset classification, providing location/shape or other detailed information for the objects, several ways may be employed including schema level linking (as was done between this ontology and other ontologies developed by INTERLINK) or multiple typing of individuals using more than one rdf:type statements for each individual.
created: 2018-08-27
preferred namespace prefix: eurotl
version info: Version 0.91

Creator
description: Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
has version: creator-006
issued: 1999-07-02
modified: 2008-01-14
comment: An entity primarily responsible for making the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Description
description: Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
has version: description-006
issued: 1999-07-02
modified: 2008-01-14
comment: An account of the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Title
has version: title-006
issued: 1999-07-02
modified: 2008-01-14
comment: A name given to the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

boundBy
type: ObjectProperty
domain: SpatialObject
range: PhysicalObject
comment: Indicates that a spatial object is bounded by a physical object

byTechnicalSolution
type: ObjectProperty
domain: Fulfilment
range: TechnicalSolution
comment: Specifies the technical solution for a fulfillment

conformantToBaseline
type: ObjectProperty
domain: Baseline
range: Baseline
comment: Connects a baseline to another baseline from a conformance point-of-view

containedIn
type: ObjectProperty
domain: PhysicalObject
range: SpatialObject
comment: Specifies that a physical object is contained in a spatial object

fromPhase
type: ObjectProperty
domain: Baseline
range: LifecyclePhase
comment: Specifies that a baseline is valid for a lifecycle phase

fromTemplate
type: ObjectProperty
domain: TechnicalSolution
range: TechnicalSolution
comment: Indicates that the subject uses the object as a template, making all statements about the object true also for the subject

hasBaseLine
type: ObjectProperty
domain: Object
range: Baseline
comment: Associates an object or revision to a baseline

hasIssue
type: ObjectProperty
range: Issue
comment: Associates a condition to a thing

hasConnection
type: ObjectProperty
type: FunctionalProperty
type: SymmetricProperty
domain: Port
range: Port
comment: A connection between a port an another port

hasDocument
type: ObjectProperty
domain: Object
range: Document
comment: Associates a document with an object

hasFunction
type: ObjectProperty
domain: FunctionalUnit
range: Function
comment: Associates a function with a functional unit

hasGeometry
type: ObjectProperty
range: Geometry
comment: Associates geometry to a thing

hasPort
type: ObjectProperty
type: InverseFunctionalProperty
domain: Object
range: Port
comment: Associates a port with an object

hasRepresentation
type: ObjectProperty
domain: PhysicalObject
comment: Associates something (such as an IFC model) which represents a physical object

hasRequirement
type: ObjectProperty
domain: Function
range: Requirement
comment: Associates a requirement to a function

hasSuitability
type: ObjectProperty
range: Suitability
comment: Associates suitability with a thing

ofFunctionalUnit
type: ObjectProperty
domain: Fulfilment
range: FunctionalUnit
comment: Specifies which functional unit a fulfillment concerns

propertyReference
type: ObjectProperty
domain: Requirement
range: DatatypeProperty
type: DatatypeProperty
comment: Associates a datatype property with a requirement

hasDocumentFragmentReference
type: DatatypeProperty
domain: Object
range: string
comment: A reference to a referencerable subset of a document such as one element in an XML document

hasReference
type: DatatypeProperty
domain: Document
range: anyURI
comment: A reference to a URI that identifies a document

AGORALocation
type: Class
subclass of: ISO17572DynamicLocationReference
comment: A dynamic location reference as defined by ISO 17572-3. Included here as a placeholder

Accident
type: Class
subclass of: InstantaneousEvent
comment: an unfortunate incident that happens unexpectedly and unintentionally, typically resulting in damage or injury. Class is included as an example/placeholder

Address
type: Class
subclass of: LocationByIdentifier
comment: An identification of the fixed location of a property. The full address is a hierarchy consisting of components such as geographic names, with an increasing level of detail, e.g.: town, then street name, then house number or name. It may also include a post code or other postal descriptors. The address may include a path of access but this depends on the function of the address. [INSPIRE]

Baseline
type: Class
subclass of: Object
subclass of: Restriction
  on property: alternateOf
  all values from: Baseline
subclass of: Restriction
  on property: conformantToBaseline
  min cardinality: 0
subclass of: Restriction
  on property: fromPhase
  min cardinality: 0
subclass of: Restriction
  on property: hasSuitability
  min cardinality: 0
subclass of: Restriction
  on property: alternateOf
  max qualified cardinality: 1
  on class: Baseline
comment: Applicable definitions from [http://everyspec.com/MIL-HDBK/MIL-HDBK-0001-0099/MIL-HDBK-61A_15177/] are: (1) An agreed-to description of the attributes of a product, at a point in time, which serves as a basis for defining change. (2) An approved and released document, or a set of documents, each of a specific revision; the purpose of which is to provide a defined basis for managing change. (3) The currently approved and released configuration documentation. Translated to the EUROTL a baseline refers to a named collection of objects (or object revisions) that represents a state at a certain point in time (such as at the end of a lifecycle stage). A baseline may be used as basis for data exchange, approval, alternatives etc and may conceptually be compared to a file or a folder consisting of files. Objects or object revisions are connected to a baseline with the objectProperty eurotl:hasBaseline. Within this ontology, a baseline may be associated with e.g. a lifecycle phase, suitability etc

Issue
type: Class
subclass of: Entity
comment: The state for an object, either observed or predicted

Crossing
type: Class
subclass of: SpatialObject
comment: A place where two or more roads or railways intersect

Document
type: Class
subclass of: Error8
subclass of: Entity
subclass of: Restriction
  on property: hasReference
  min cardinality: 0
comment: A proxy for any document which from the view of the european road OTL is considered as one unit. Examples of documents may be IFC STEP files, XML documents, Excel documents, CAD drawings, PDF documents etc. A document may be related to any object

Fulfilment
type: Class
subclass of: Object
subclass of: Restriction
  on property: byTechnicalSolution
  cardinality: 1
subclass of: Restriction
  on property: ofFunctionalUnit
  cardinality: 1
comment: The objectified relationship between a technical solution (eurotl:byTechnicalSolution) and a functional unit (eurotl:ofFunctionalUnit). There may be many different technical solutions which fulfills a functional unit.

Function
type: Class
subclass of: Object
subclass of: Restriction
  on property: hasRequirement
  min cardinality: 0
comment: A purpose of a thing

FunctionalPort
type: Class
subclass of: Port
comment: A port which belongs to a functional unit

FunctionalUnit
type: Class
subclass of: Object
subclass of: Restriction
  on property: hasFunction
  min cardinality: 0
comment: Defines the role of a subsystem or part in a larger whole. It defines also requirements and boundary conditions for the subsystem or part. [Gielingh, 2008 - A theory for the modelling of complex and dynamic systems - https://www.itcon.org/papers/2008_27.content.03759.pdf]

GeographicalName
type: Class
subclass of: LocationByIdentifier
comment: Spatial reference in the form of a label or code that identifies a location

Geometry
type: Class
subclass of: Object
comment: the shape and relative arrangement of the parts of something

ISO17572DynamicLocationReference
type: Class
subclass of: Location
comment: A dynamic location reference as defined by ISO 17572. Included here only as a placeholder.

InspectionActivity
type: Class
subclass of: Activity
comment: An activity with the purpose of inspecting something. May result in e.g. observed conditions for objects

IntervalRequirement
type: Class
subclass of: Error5
subclass of: Error6
subclass of: Requirement
subclass of: Restriction
  on property: propertyReference
  cardinality: 1
comment: A requirement for a property value to exist within a specified interval

Lane
type: Class
subclass of: SpatialObject
comment: a division of a road marked off with painted lines and intended to separate single lines of traffic according to speed or direction

LifecyclePhase
type: Class
comment: A named subset of the whole lifecycle of an activity or object

LocationByCoordinates
type: Class
subclass of: Location
subclass of: Restriction
  on property: hasGeometry
  min cardinality: 1
comment: A location defined by means of coordinates

LocationByIdentifier
type: Class
subclass of: Location
comment: A location defined by a known geographic place using some identifier

LocationByTransformation
type: Class
subclass of: Location
comment: A location defined by a transformation (translation, reflection, rotation, scaling)

LocationCode
type: Class
subclass of: LocationByIdentifier
comment: A system for identifying an area anywhere on earth based on pre-defined codes such as Open Location Code (OLC) or TMC Location Codes

MaintenanceActivity
type: Class
subclass of: Activity
comment: An activity with the purpose of maintaining something. May result in e.g. new and improved conditions for objects

Material
type: Class
subclass of: Object
comment: the matter from which a thing is or can be made

Object
type: Class
subclass of: Error7
subclass of: Entity
subclass of: Restriction
  on property: hasBaseLine
  min cardinality: 0
subclass of: Restriction
  on property: hasIssue
  min cardinality: 0
subclass of: Restriction
  on property: hasDocument
  min cardinality: 0
subclass of: Restriction
  on property: atLocation
  min cardinality: 0
subclass of: Restriction
  on property: hasDocumentFragmentReference
  min cardinality: 0
comment: An object of interest in the context of a construction process

OpenLRLocation
type: Class
subclass of: ISO17572DynamicLocationReference
comment: A dynamic location reference as defined by http://www.openlr.org. Included here as a placeholder

PhysicalObject
type: Class
subclass of: Object
subclass of: Restriction
  on property: hasPort
  min cardinality: 0
subclass of: Restriction
  on property: hasRepresentation
  min cardinality: 0
comment: An object with defined shape, material and location in space and time

Port
type: Class
subclass of: Object
subclass of: Restriction
  on property: hasConnection
  max cardinality: 1
comment: A boundary connection point which allows an object to be connected to boundary connection points of other objects

RealisationActivity
type: Class
subclass of: Activity
comment: An activity with the purpose of constructing something. May result in e.g. realized/installed objects

ReplacementActivity
type: Class
subclass of: Activity
comment: An activity with the purpose of replacing something with something else. May result in e.g. new technical solution for a certain functional unit

Requirement
type: Class
subclass of: Object
comment: Something that is needed or that must be done

SpatialObject
type: Class
subclass of: Object
comment: An abstract representation of a real-world phenomenon related to a specific location or geographical area

Suitability
type: Class
subclass of: Thing
comment: Meta-data describing the permitted use of an information deliverable

TechnicalPort
type: Class
subclass of: Port
comment: A port which belongs to a technical solution

TechnicalSolution
type: Class
subclass of: Object
subclass of: Restriction
  on property: hasIssue
  min cardinality: 0
comment: A Technical Specification describes the subsystem or part, independent of its role in the larger whole. In the course of a design process, it can also be seen as a solution for a design problem. A Technical Solution contains a full specification of an artifact and/or process on a particular level of (de)composition. It contains also Functional Units of subsystems or parts, but not the technical details of these subsystems or parts. This principle keeps a specification modular.[Gielingh, 2008 - A theory for the modelling of complex and dynamic systems - https://www.itcon.org/papers/2008_27.content.03759.pdf]

Build
type: NamedIndividual
type: LifecyclePhase
comment: Represents the (end of) the construction phase

Design
type: NamedIndividual
type: LifecyclePhase
comment: Represents the (end of) the design phase

Plan
type: NamedIndividual
type: LifecyclePhase
comment: Represents the (end of) the planning phase

Operate
type: NamedIndividual
type: LifecyclePhase
comment: Represents the phase where a construction exists in the real world and is intended to be service/use

Suitability Accepted
type: NamedIndividual
type: Suitability
comment: Indicates that something was accepted

Suitability ForAcceptance
type: NamedIndividual
type: Suitability
comment: Indicates that acceptance is requested but not yet achieved

Suitability ForInformation
type: NamedIndividual
type: Suitability
comment: Indicates the something is for information only

min cardinality: 0

min cardinality: 0

min cardinality: 0

min cardinality: 0

Dublin Core Metadata Element Set, Version 1.1
modified: 2012-06-14
publisher: DCMI

Contributor
description: Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
has version: contributor-006
issued: 1999-07-02
modified: 2008-01-14
comment: An entity responsible for making contributions to the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Coverage
description: Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
has version: coverage-006
issued: 1999-07-02
modified: 2008-01-14
comment: The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Date
description: Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
has version: date-006
issued: 1999-07-02
modified: 2008-01-14
comment: A point or period of time associated with an event in the lifecycle of the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Format
description: Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME].
has version: format-007
issued: 1999-07-02
modified: 2008-01-14
comment: The file format, physical medium, or dimensions of the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Identifier
description: Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
has version: identifier-006
issued: 1999-07-02
modified: 2008-01-14
comment: An unambiguous reference to the resource within a given context.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Language
description: Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
has version: language-007
issued: 1999-07-02
modified: 2008-01-14
comment: A language of the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Publisher
description: Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
has version: publisher-006
issued: 1999-07-02
modified: 2008-01-14
comment: An entity responsible for making the resource available.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Relation
description: Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
has version: relation-006
issued: 1999-07-02
modified: 2008-01-14
comment: A related resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Rights
description: Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
has version: rights-006
issued: 1999-07-02
modified: 2008-01-14
comment: Information about rights held in and over the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Source
description: The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
has version: source-006
issued: 1999-07-02
modified: 2008-01-14
comment: A related resource from which the described resource is derived.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Subject
description: Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary.
has version: subject-007
issued: 1999-07-02
modified: 2012-06-14
comment: The topic of the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Type
description: Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
has version: type-006
issued: 1999-07-02
modified: 2008-01-14
comment: The nature or genre of the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.