897
results
How to
  • wf-invoc - Workflow Invocation Ontology
    http://purl.org/net/wf-invocation
    Wf-invoc is a simple profile of the P-plan ontology to describe how workflow steps are invoked within a workflow execution. @en
  • tsnc - Territorial Statistical Nomenclature Change Ontology
    http://purl.org/net/tsnchange#
    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
  • opmv - Open Provenance Model Vocabulary
    http://purl.org/net/opmv/ns#
    OPMV, the Open Provenance Model Vocabulary, provides terms to enable practitioners of data publishing to publish their data responsibly. @en
  • p-plan - The P-PLAN Ontology
    http://purl.org/net/p-plan#
    The Ontology for Provenance and Plans (P-Plan) is an extension of the PROV-O ontology [PROV-O] created to represent the plans that guided the execution of scientific processes. P-Plan describes how the plans are composed and their correspondence to provenance records that describe the execution itself. @en
  • prvt - Provenance Vocabulary types
    http://purl.org/net/provenance/types#
    Extends the Provenance Vocabulary by defining subclasses of the types of provenance elements introduced in the core ontology. @en
  • dvia - The visualization vocabulary for LOD applications
    http://purl.org/ontology/dvia
    dvia is an RDF vocabulary designed to facilitate interoperability between visualization applications published on the Web. @en
  • is - Info Service Ontology
    http://purl.org/ontology/is/core#
    The Information Service Ontology specification provides basic concepts and properties for describing different information services, e.g. Wikipedia, MusicBrainz, Freebase @en
  • ofrd - Fridge and Freezer Vocabulary
    http://purl.org/opdm/refrigerator#
    Vocabulary to describe fridges and freezers @en
  • wi - The Weighted Interests Vocabulary
    http://purl.org/ontology/wi/core#
    The Weighted Interests Vocabulary specification provides basic concepts and properties for describing describing preferences (interests) within contexts, their temporal dynamics and their origin on/ for the Semantic Web. @en
  • qb4o - Vocabulary for publishing OLAP data cubes
    http://purl.org/qb4olap/cubes
    This vocabulary allows to publish and operate with OLAP cubes in RDF @en
  • pr - Property Reification Vocabulary
    http://purl.org/ontology/prv/core#
    A vocabulary for describing the ontology design pattern of property reification. @en
  • service - The Service Ontology
    http://purl.org/ontology/service
    A micro-ontology that defines the general concept of a service. @en
  • 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
  • conversion - Conversion Ontology
    http://purl.org/twc/vocab/conversion/
    Ontology used to describe interpretations of tabular literals to produce RDF @en
  • rev - Review Vocabulary
    http://purl.org/stuff/rev#
    Vocabulary for expressing reviews and ratings @en