22
results
How to
  • tempo - TempO - Temporal Ontology
    http://purl.org/tempo
    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
  • tvc - The Time-indexed Value in Context
    http://www.essepuntato.it/2012/04/tvc
    A pattern for the description of scenarios that involve entities having some value during a particular time and within a particular context. @en
  • tm - A vocabulary for temporal objects in Geographic Information
    http://def.seegrid.csiro.au/isotc211/iso19108/2002/temporal
    An OWL representation of part of the model for Temporal objects and reference systems from ISO 19108:2002 Geographic Information - Temporal Schema @en
  • oh - The Opening Hours vocabulary
    http://semweb.mmlab.be/ns/oh
    A vocabulary to describe opening hours using calendars (recommended: iCal, RDFCal or schema.org) published on the Web. @en
  • tzont - Time Zone Ontology
    http://www.w3.org/2006/timezone
    A vocabulary to describe time zones and their geographical coverage. @en
  • te - Time Entry
    http://www.w3.org/2006/time-entry
    An entry sub-ontology of time (OWL-Time). @en
  • cal - Internet Calendaring and Scheduling Core Object Specification
    http://www.w3.org/2002/12/cal/ical
    A vocabulary for description of events and calendars @en
  • step - Semantic Trajectory Episodes
    http://purl.org/net/step
    A lightweight ontology for representing semantic trajectories and contextual elements in terms of features of interests and episodes. @en
  • interval - Intervals Ontology
    http://reference.data.gov.uk/def/intervals
    An ontology for time intervals @en
  • ncal - NEPOMUK Calendar Ontology
    http://www.semanticdesktop.org/ontologies/2007/04/02/ncal
    The NEPOMUK Calendaring Ontology intends to provide vocabulary for describing calendaring data (events, tasks, journal entries) which is an important part of the body of information usually stored on a desktop. It is an adaptation of the ICALTZD ontology created by the W3C RDF Calendar Task Force of the Semantic Web Interest Group in the Semantic Web Activity. @en
  • time - Time Ontology
    http://www.w3.org/2006/time
    This vocabulary defines temporal entities such as time intervals, their properties and relationships. @en
  • atts - Air Traffic Temporal and Spacial Vocabulary
    https://data.nasa.gov/ontologies/atmonto/general#
    Defines temporal / spatial concepts and general-purpose datastructures @en
  • tl - The Timeline Ontology
    http://purl.org/NET/c4dm/timeline.owl
    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
  • seast - The SEAS Time Ontology.
    https://w3id.org/seas/TimeOntology
    This ontology defines: - a set of subclasses of `seas:Evaluation` to better interpret evaluations of quantifiable properties. - a set of sub properties of `seas:hasProperty` to qualify time-related properties. @en
  • gtm - Gouda Time Machine Ontology
    https://www.goudatijdmachine.nl/def
    The Gouda Time Machine Ontology describes the geo-temporal classes and properties used within the Gouda Time Machine. @en