70
results
-
This document gives URIs to all terms used within Datex II. the Datex standard was developed for information exchange between traffic management centres, traffic information centres and service providers in Europe @en
-
The SEM Ontology defines entities that make up the context of an event: Events, Actors, Places, Times. @en
-
The File Ontology for Geometry formats (FOG) describes meaningful relations towards geometry snippets in RDF literals, geometry files on relative or absolute URLs and ontology-based geometry descriptions. The defined properties in this ontology are related towards each other and additional metadata is provided, such as file extension and related specifications/sources (incl. entries in dbpedia and Wikidata). The initial version of the ontology (v0.0.1) was documented in: Bonduel, Mathias, Wagner, Anna, Pauwels, Pieter, Vergauwen, Maarten, & Klein, Ralf (2019). Including Widespread Geometry Formats in Semantic Graphs Using RDF Literals. In Proceedings of the European Conference on Computing in Construction (EC3 2019). Chania, Greece. @en
-
The Geometry Metadata Ontology contains terminology to Coordinate Systems (CS), length units and other metadata (file size, software of origin, etc.). GOM is designed to be at least compatible with OMG (Ontology for Managing Geometry) and FOG (File Ontology for Geometry formats), and their related graph patterns. In addition, GOM provides terminology for some experimental data structures to manage (marked as vs:term_status = unstable): * transformed geometry (e.g. a prototype door geometry that is reused for all doors of this type). This is closely related to the transformation of Coordinate Systems @en
-
The Ontology for Managing Geometry (OMG) is an ontology for describing geometry descriptions of objects. It provides means to support the application of multiple geometry descriptions of the same object as well as the description of the geometry evolution over time. The OMG is based the concepts introduced in the Ontology for Property Management (OPM) ontology. This ontology was created within the research project SCOPE, funded by the German Federal Ministry for Economic Affairs and Energy (BMWi). The initial version of the ontology (v0.0.1) is documented in: Wagner, Anna, Bonduel, Mathias, Pauwels, Pieter & Rüppel, Uwe(2019). Relating Geometry Descroptions to its Derivatives on the Web. In Proceedings of the European Conference on Computing in Construction (EC3 2019). Chania, Greece. @en
-
The Procedural Knowledge Ontology (PKO) addresses the Procedural Knowledge (PK) domain, and models procedures, their executions, and related resources and agents. @en
-
This ontology defines feature of interest and their properties, as an extension of the core classes of the SSN ontology (https://www.w3.org/ns/ssn/). A feature of interest is an abstraction of a real world phenomena (thing, person, event, etc). A feature of interest is then defined in terms of its properties, which are qualifiable, quantifiable, observable or operable qualities of the feature of interest. Alignments to other ontologies are proposed in external documents: - [SSNAlignment](https://w3id.org/seas/SSNAlignment) proposes an alignment to the [SSN ontology](http://www.w3.org/ns/ssn/). - [QUDTAlignment](https://w3id.org/seas/QUDTAlignment) proposes an alignment to the [QUDT ontology](http://qudt.org/). @en
-
The vocabulary allows for the description of data about scientific events such as conferences, symposiums and workshops. @en
-
Ontology 'Usability' created to describe and store information about interactions of user with a software user interface @en
-
Ontology for representing exceptions to reporting of parents, for entities registered with a Legal Entity Identifier. The Global Legal Identifier System (GLEIS) requires that legal entities with an LEI provide information on their ultimate and direct accounting consolidating parents. Relationship reporting is mandatory with exceptions allowed for certain well-defined reasons. This ontology provides a simple structure for recording reasons for each exception by LEI. @en