The European Road OTL core definitions.
Basic European Road OTL
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.
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.
An entity primarily responsible for making the resource.
Creator
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 may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
An account of the resource.
Description
A name given to the resource.
Title
Indicates that a spatial object is bounded by a physical object
Specifies the technical solution for a fulfillment
Connects a baseline to another baseline from a conformance point-of-view
Specifies that a physical object is contained in a spatial object
Specifies that a baseline is valid for a lifecycle phase
Indicates that the subject uses the object as a template, making all statements about the object true also for the subject
Associates an object or revision to a baseline
Associates a condition to a thing
A connection between a port an another port
Associates a document with an object
Associates a function with a functional unit
Associates geometry to a thing
Associates a port with an object
Associates something (such as an IFC model) which represents a physical object
Associates a requirement to a function
Associates suitability with a thing
Specifies which functional unit a fulfillment concerns
A reference to a referencerable subset of a document such as one element in an XML document
A reference to a URI that identifies a document
A dynamic location reference as defined by ISO 17572-3. Included here as a placeholder
an unfortunate incident that happens unexpectedly and unintentionally, typically resulting in damage or injury. Class is included as an example/placeholder
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]
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
The state for an object, either observed or predicted
A place where two or more roads or railways intersect
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
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.
A purpose of a thing
A port which belongs to a functional unit
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]
Spatial reference in the form of a label or code that identifies a location
the shape and relative arrangement of the parts of something
A dynamic location reference as defined by ISO 17572. Included here only as a placeholder.
An activity with the purpose of inspecting something. May result in e.g. observed conditions for objects
A requirement for a property value to exist within a specified interval
a division of a road marked off with painted lines and intended to separate single lines of traffic according to speed or direction
A named subset of the whole lifecycle of an activity or object
A location defined by means of coordinates
A location defined by a known geographic place using some identifier
A location defined by a transformation (translation, reflection, rotation, scaling)
A system for identifying an area anywhere on earth based on pre-defined codes such as Open Location Code (OLC) or TMC Location Codes
An activity with the purpose of maintaining something. May result in e.g. new and improved conditions for objects
the matter from which a thing is or can be made
An object of interest in the context of a construction process
A dynamic location reference as defined by http://www.openlr.org. Included here as a placeholder
An object with defined shape, material and location in space and time
A boundary connection point which allows an object to be connected to boundary connection points of other objects
An activity with the purpose of constructing something. May result in e.g. realized/installed objects
An activity with the purpose of replacing something with something else. May result in e.g. new technical solution for a certain functional unit
Something that is needed or that must be done
An abstract representation of a real-world phenomenon related to a specific location or geographical area
Meta-data describing the permitted use of an information deliverable
A port which belongs to a technical solution
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]
Represents the (end of) the construction phase
Represents the (end of) the design phase
Represents the (end of) the planning phase
Represents the phase where a construction exists in the real world and is intended to be service/use
Indicates that something was accepted
Indicates that acceptance is requested but not yet achieved
Indicates the something is for information only
Dublin Core Metadata Element Set, Version 1.1
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.
An entity responsible for making contributions to the resource.
Contributor
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.
The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
Coverage
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].
A point or period of time associated with an event in the lifecycle of the resource.
Date
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].
The file format, physical medium, or dimensions of the resource.
Format
Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
An unambiguous reference to the resource within a given context.
Identifier
Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
A language of the resource.
Language
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.
An entity responsible for making the resource available.
Publisher
Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
A related resource.
Relation
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
Information about rights held in and over the resource.
Rights
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.
A related resource from which the described resource is derived.
Source
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary.
The topic of the resource.
Subject
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.
The nature or genre of the resource.
Type
Associates a datatype property with a requirement