77
results
-
Global City Indicator Foundation Ontology developed by the Information Engineering Group, Mechanical & Industrial Engineering, University of Toronto. Contains the foundation ontologies required to represent ISO 37120 city indicators, including Placenames, Time, Measurement, Provenance, Statistics, Validity and Trust. See: Fox, M.S., (2013), "A Foundation Ontology for Global City Indicators", Global City Institute Working Paper, Vol. 1, No.4, pp. 1-45. Global Cities Institute, University of Toronto. Updated 24 June 2014: http://www.eil. Based on the Global City Indicators Facility, University of Toronto: http://www.cityindicators.org/Deliverables/Core%20and%20Supporting%20Indicators%20Table%20SEPTEMBER%202011.pdf. Contact: Mark S. Fox, msf@eil.utoronto.ca @en
-
ISO 37120 – Sustainable Development and Resilience of Communities – Indicators for City Services and Quality of Life (under TC268) http://ontology.eil.utoronto.ca/ISO37120.html This OWL file defines a class for each indicator defined in the ISO 37120 standard. Names for each indicator are provided. Text definitions are provided only for Economy, Education and Energy indicators, due to copyright restrictions imposed by ISO. This file is meant to provide a single URI for each indicator. An ontology for representing an indicator's supporting data plus meta information such as provenance, validity and trust can be found in: http://ontology.eil.utoronto.ca/GCI/Foundation/GCI-Foundation.owl Documentation of the ontology can be found in: http://eil.utoronto.ca/smartcities/papers/GCI-Foundation-Ontology.pdf @en
-
Open 311 Ontology This ontology generalizes the concepts that appear in 311 open data files published by several cities (Toronto, New York, Chicago, Vancouver) across North America. It provides a generis representation of 311 data that other cities can map their data onto and be used as a means of achieving interoperability. @en
-
This ontology defines concepts related to federation of internet infrastructures. @en
-
Extends owl-time ontology with support for several timelines, acting as a backbone to adress time interval/instants. Mainly designed with a multimedia use-case in mind. @en
-
This is a vocabulary for modeling jobs offer in Spain. @en
-
An ontology to describe competences and human capabilities @en
-
A vocabulary for the Social and Solidarity Economy (SSE). This vocabulary is designed to be used in combination with the metadata schemes/vocabularies/ontologies: dcterms, good relations, foaf, vcard, organization and schema.org - this is defined in the Dublin Core Application Profile of the SSE. Developed by the ESSGlobal group of the Intercontinental Network for Promoting the Social and Solidarity Economy (RIPESS) Organisation. @en
-
A lightweight ontology for representing semantic trajectories and contextual elements in terms of features of interests and episodes. @en
-
Defines the common bibliographic terms for the description of enumeration and chronology of periodicals @en
-
The News Storyline Ontology is a generic model for describing and organising the stories news organisations tell. The ontology is intended to be flexible to support any given news or media publisher's approach to handling news stories. At the heart of the ontology, is the concept of Storyline. @en
-
This vocabulary provides supplementary terms for organisations wishing to publish open data about themselves. @en
-
This version of the OSLO Exchange Standard provides a minimum set of classes and properties for describing a natural person, i.e. the individual as opposed to any role they may play in society or the relationships they have to other people, organisations and property; all of which contribute significantly to the broader concept of identity. The vocabulary is closely integrated with the Person, Organisation and Location Vocabularies published by the W3C in the Gov Linked Data Project. The OSLO specification is the result of a public-private partnership initiated by V-ICT-OR, the Flemish Organization for ICT in Local Government. @en
-
In a typical (uni)temporal data model every resource's appearance (and disappearance) is being tracked. Numerous systems accomplish unitemporal tracking, either externally by e.g. using git to record the insertion or deletion of a resource, or internally by e.g. using prov:generatedAtTime and prov:invalidatedAtTime. This axis of time is known as *system time*, and none of TempO's concern because for one there is readily available support, and moreover because unitemporal tracking is used for principally true statements, i.e. those that have always been (considered) true or will always be (considered) true. TempO addresses bitemporal and tritemporal setups: Resources which are (known or believed to be) valid and efficacious for some time. A second time axis orthogonal to system time is introduced, that is a resource can be valid even though it is currently not in the system, or, conversely, can be already or still invalid by the time it enters the system. Efficacy, sometimes called decision time, is yet another concept orthogonal to validity, i.e. a resource that is no longer or not yet valid can be efficacious. The converse, a valid but inefficacious resource in the system, is *usually* not encountered but TempO does not impose restrictions on the shape of the time area. In general the necessity for tracking both validity and efficacy arises in areas where concepts are assigned a code or label that is subject to reuse following invalidation. Tracking efficacy and validity concurrently then allows for fine-grained control over how much future knowledge or how much past knowledge we tolerate in a datset. Example: -------- Czechoslovakia was founded in 1918 but became part of Germany, Hungary and Poland in 1938. It was reestablished in 1945 but split into two sovereign states in 1993. The ISO 3166 country code for Czechoslovakia used to be 'CS', assigned in 1974, published in February 1978, and invalidated with the country's split. In 2003 ISO 3166 reassigned the country code 'CS' to Serbia and Montenegro. The facts were assembled in 2018 and written down as follows: cc:CSHH a cc:ISO3166-CountryCode ; rdfs:label "CS" ; cc:refersTo "Czechoslovakia" ; prov:generatedAtTime "2018-02-29T04:00:00Z"^^xsd:dateTime . tempo:validFrom "1978-02"^^xsd:gYearMonth ; tempo:validTill "1993-01-01"^^xsd:date ; tempo:efficaciousFrom "1918"^^xsd:gYear , "1945"^^xsd:gYear ; tempo:efficaciousTill "1938"^^xsd:gYear , "2003"^^xsd:gYear . The use of the country code 'CS' in a statement from 1988 can be resolved to cc:CSHH, as of today, free from ambiguity; it was valid back then after all and we know that today. The same query in 2017 (point-in-time query) would have yielded no results because the information hadn't been in the system back then. Point-in-time queries, however, are not TempO's major concern so only as-of-today queries are assumed from now on. Following the country's split it is highly likely that news reports from, say, 1994 highlighting the then-recent past would still have used 'CS' to refer to cc:CSHH. According to the resource this is possible, a query for 'CS' in 1994 would bring up cc:CSHH as it is efficacious but marked as invalidated. On the other end of history, the use of the code 'CS' in, say, 1976 is plausible. The code was decided on but not yet formally published. A query for 'CS' as used in 1976 would bring up cc:CSHH, marked as anachronistic. Going back further, a statement from, say 1942, using the code 'CS' must clearly refer to something else. A query for 'CS' as used in 1976 would yield not yield any results. -- The ontology IRI http://purl.org/tempo/ always resolve to the latest version of TempO. Particular versionIRIs such as http://purl.org/tempo/0.1/ can be used by clients to force the import of a particular version. The goal of TempO is to allow for temporal constraints with control over how much future or past is permissible directly on the published resource, and as such, TempO does not restrict domain/ranges. @en
-
The participation ontology is a simple model for describing the roles that people play within groups. It is intended that specific domains will create subclasses of roles within their own areas of expertise. @en