29
results
-
A core ODP of the CEON ontology network, defining aspects of the process concept. @en
-
The Stories ontology was developed in collaboration with the BBC, with an aim to creating an ontology for narrative representation that could be applied across a diverse set of cases. These included accounts of events in Northern Ireland, the storylines of Doctor Who episodes, and key events of the Battle of Britain. @en
-
This Vocabulary provides the means to create a document which describes a large event or other connected series of events. The primary purpose is to help humans comprehend the programme, not describe absolute truth. A single event (or even series) may have multiple programmes. @en
-
An ontology for organising theatrical data. @en
-
This ontology deals with the notion of reified events - events seen as first-class objects. @en
-
This vocabulary is based on the EPC Information Services Specification http://www.gs1.org/sites/default/files/docs/epc/epcis_1_0_1-standard-20070921.pdf @en
-
The objective of gUFO is to provide a lightweight implementation of the Unified Foundational Ontology (UFO) [1-5] suitable for Semantic Web OWL 2 DL applications. Intended users are those implementing UFO-based lightweight ontologies that reuse gUFO by specializing and instantiating its elements. There are three implications of the use of the term lightweight. First of all, we have employed little expressive means in an effort to retain computational properties for the resulting OWL ontology. Second, we have selected a subset of UFO-A [1, 2] and UFO-B [3] to include here. In particular, there is minimalistic support for UFO-B (only that which is necessary to establish the participation of objects in events and to capture historical dependence between events). Third, a lightweight ontology, differently from a reference ontology, is designed with the purpose of providing an implementation artifact to structure a knowledge base (or knowledge graph). This has driven a number of pragmatic implementation choices which are discussed in comments annotated to the various elements of this implementation. The 'g' in gUFO stands for gentle. At the same time, "gufo" is the Italian word for "owl". For the source repository, see: <https://github.com/nemo-ufes/gufo> @en
-
A vocabulary to describe touristic places: accommodations, points of interest, restaurants and attractions. @en
-
The SEM Ontology defines entities that make up the context of an event: Events, Actors, Places, Times. @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
12