59
results
-
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
-
The TSN-Change ontology aims at describing changes that occured from one version of a Territorial Statistical Nomenclature (TSN) (i.e., partition of the territory) and its subsequent (e.g., change in territorial units boundaries to reflect an administrative reorganisation). @en
-
This RDF ontology allows describing any Territorial Statistical Nomenclature (TSN) (i.e., partition of the territory) used as a support to socio-economic data (statistical data that describe territory in terms of population, unemployement rate, transport access, etc.). @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
-
The data.gov.au Dataset Ontology is an OWL ontology designed to describe the characteristics of datasets published on data.gov.au. The ontology contains elements which describe the publication, update, origin, governance, spatial and temporal coverage and other contextual information about the dataset. The ontology also covers aspects of organisational custodianship and governance. By using this ontology to describe datasets on data.gov.au publishers increase discoverability and enable the consumption of this information in other applications/systems as Linked Data. It further enables decentralised publishing of catalogs and facilitates federated dataset search across sites, e.g. in datasets that are published by the States. Other publishers of Linked Data may make assertions about data published using this ontology, e.g. they may publish information about the use of the dataset in other applications. @en
-
An ontology of UK Parliament @en
-
An ontology of UK central government @en
-
This ontology provides the predicates necessary to describe an arrival of a transit vehicle and its departure at a certain Stop. @en
-
The SEM Ontology defines entities that make up the context of an event: Events, Actors, Places, Times. @en
-
A vocabulary to describe touristic places: accommodations, points of interest, restaurants and attractions. @en
-
To facilitate efforts to transform the Federal Government to one that is citizen-centered, results-oriented, and market-based, the Office of Management and Budget (OMB) is developing the Federal Enterprise Architecture (FEA), a business-based framework for Governmentwide improvement. @en
-
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