157
results
-
Defines the common bibliographic terms for the description of enumeration and chronology of periodicals @en
-
The Weighting Ontology specification provides a vocabulary for describing weightings and their referenced scales, on/ for the Semantic Web. @en
-
The RECO ontology defines the vocabulary for representing preferences-as-constraints and preferences-as-ratings as RDF graphs. This lightweight vocabulary provides domain-independent means to describe user profiles in a coherent and context-aware way. RECO has been designed as an extension of both Friend-Of-A-Friend (FOAF) and Who Am I! (WAI) ontologies. @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
-
This is an ontology representation of the climatic data variables defined by Climate and Forecast (CF) standard names vocabulary (http://cf-pcmdi.llnl.gov/documents/cf-standard-names/), maintained by the Program for Climate Model Diagnosis and Intercomparison (http://cf-pcmdi.llnl.gov/ ) which is intended for use with climate and forecast data, in the atmosphere, surface and ocean domains. @en
-
This ontology is part of the Agriculture Meteorology example showcasing the ontology developed by the W3C Semantic Sensor Networks incubator group (SSN-XG). It is published here in order to generalize the potential usage and the alignment with other standardization efforts of the SSN ontology. @en
-
This ontology is partially based on the SysML QUDV (Quantities, Units, Dimensions and Values) proposed by a working group of the SysML 1.2 Revision Task Force (RTF), working in close coordination with the OMG MARTE specification group. In order to generalize its potential usage and alignment with other standardization efforts concerning quantities and units, the QU ontology has been further developed as a complement to the Agriculture Meteorology example showcasing the ontology developed by the W3C Semantic Sensor Networks incubator group (SSN-XG). @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
-
SemSur, the Semantic Survey Ontology, is a core ontology for describing individual research problems, approaches, implementations and evaluations in a structured, comparable way. @en
-
The FIESTA-IoT ontology takes inspiration from the well-known Noy et al. methodology for reusing and interconnecting existing ontologies. To build the ontology, we leverage a number of core concepts from various mainstream ontologies and taxonomies, such as Semantic Sensor Network (SSN), M3-lite (a lite version of M3 ontology), WGS84, IoT-lite, Time, and DUL ontology. @en
-
FIESTA-Priv Ontology @en
-
The IoT-Taxonomy-lite is adapted from M3-lite taxonomy. This taxonomy is refactored and defines many other concepts such as subclasses of Feature-of-Interest and Quality-of-Observation. @en
-
M3 lite taxonomy is designed for the FIESTA-IOT H2020 EU project. We refactor, clean and simplify the M3 ontology designed by Eurecom (Amelie Gyrard). M3 ontology lite is currently aligned with the quantity taxonomy used by several testbeds: SmartSantander (Spain), University of Surrey (United Kingdom), KETI (Korea) and Com4Innov (France). @en
-
Vocabulary for describing issues (or problems) and corresponding symptoms and solutions to a broad variety of contexts. It is intended to provide a generic, reusable core ontology that can be extended or specialized for use in domain-specific situations, aimed at supporting linked data publishing. The solutions are represented by procedures, which are possible workflows for solving corresponding issues. @en
-
A Vocabulary for Incorporating Predictive Models into the Linked Data Web @en