-
Notifications
You must be signed in to change notification settings - Fork 0
Ontologies
The original Dublin Core™ of thirteen (later fifteen) elements was first published in the report of a workshop in 1995. In 1998, this was formalized in the Internet Engineering Task Force standard RFC 5791, and discussions began about making it a standard of the (US) National Information Standards Organization (NISO). The European Committee for Standardization (CEN) published the Dublin Core Metadata Element Set as CWA 13874. The element set was then published as the US standard ANSI/NISO Z39.85-2001 and as an international standard, ISO 15836-2003. The most recent updates of these standards are RFC 5791 (2010), Z39-85-2012, and ISO 15836-1:2017. ISO 15836 Part 2, covering several dozen properties and classes that have been added to DCMI namespaces since 1999, was published in 2019.
Starting in 2002, DCMI grew into the role of "de facto" standards agency by maintaining its own, updated documentation for DCMI Metadata Terms. The DCMI Usage Board currently serves as the maintenance agency for ISO 15836.
In addition to these semantic specifications, DCMI working groups have developed specifications on other topics of relevance to metadata, such as encoding syntaxes, usage guidelines, and metadata models. In the rapidly evolving environment of the World Wide Web, most of these specifications have been superseded over time, sometimes after influencing subsequent work by other technical communities, notably the World Wide Web Consortium.
This document discusses the Function Ontology: a way to semantically declare and describe implementation-independent functions, and their relations to related concepts such as parameters, outputs, related problems, algorithms, mappings to concrete implementations, and executions.
A list of the publications concerning the Function Ontology can be viewed at https://fno.io/.
The main scientific publication is Implementation-independent function reuse [10.1016/j.future.2019.10.006].
The Ontology for Media Resources 1.0 describes a core vocabulary of properties and a set of mappings between different metadata formats of media resources hat describe media resources published on the Web (as opposed to local archives, museums, or other non-web related and non-shared collections of media resources). The purpose of these mappings is to provide metadata representations that describe the characteristics and behavior of media resources in an interoperable manner, thereby enabling different applications to share and reuse these metadata.
The PROV Ontology (PROV-O) expresses the PROV Data Model [PROV-DM] using the OWL2 Web Ontology Language (OWL2) [OWL2-OVERVIEW]. It provides a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. It can also be specialized to create new classes and properties to model provenance information for different applications and domains. The PROV Document Overview describes the overall state of PROV, and should be read before other PROV documents.
This document defines the Semantic Web Services Ontology (SWSO). The ontology is expressed in two forms: FLOWS, the First-order Logic Ontology for Web Services; and ROWS, the Rules Ontology for Web Services, produced by a systematic translation of FLOWS axioms into the SWSL-Rules language. FLOWS has been specified in SWSL-FOL, the first-order logic language developed by SWSO's sister SWSL effort.
The potential to achieve dynamic, scalable and cost-effective infrastructure for electronic transactions in business and public administration has driven recent research efforts towards so-called Semantic Web services, that is enriching Web services with machine-processable semantics. Supporting this goal, the Web Service Modeling Ontology (WSMO) provides a conceptual framework and a formal language for semantically describing all relevant aspects of Web services in order to facilitate the automation of discovering, combining and invoking electronic services over the Web.
This workflow ontology is used to capture both sequential and state-based workflows. A workflow is an instantiation of the Workflow class (or subclass) in the ontology. The ontology captures the structure of the workflow - using classes, and a specific workflow - in the instances, e.g. a voting workflow. When used, we need another layer to capture an executable workflow, e.g., the voting workflow for user 1 when in state 3.