The DITA RDF ontology translates the semantics of a subset of the vocabulary described in the DITA 1.2 specification in a format that can be understood in the semantic Web of data. By Colin Maudry, licensed under the terms of the Unlicense (public domain). @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
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
wfm- The Workflow Motif Ontology
http://purl.org/net/wf-motifs
Ontology for describing Workflow Motifs. Workflow Motifs outline the kinds of data-intensive activities that are observed in workflows (data-operation motifs) and the different manners in which activities are implemented within workflows (workflow-oriented motifs). @en
wo- Weighting Ontology
http://purl.org/ontology/wo/core#
The Weighting Ontology specification provides a vocabulary for describing weightings and their referenced scales, on/ for the Semantic Web. @en
pr- Property Reification Vocabulary
http://purl.org/ontology/prv/core#
A vocabulary for describing the ontology design pattern of property reification. @en
awol- Atom Syndication Ontology
http://bblfish.net/work/atom-owl/2006-06-06/
The AtomOWL ontology is inspired from the work done by the atom working group. This ontology is working off the rfc 4287 published among othe places at http://www.atompub.org/rfc4287.html . The AtomOWL ontology uses as much as possible the same terms as the format there to make the relation easy to understand. The AtomOWL name space is slightly different from the atom namespace [see post http://www.imc.org/atom-syntax/mail-archive/msg16476.html]. But this is a good thing as it helps distinguish the ontology from the rfc 4287 serialisation. @en
graphql- GraphQL Vocabulary
http://datashapes.org/graphql
A vocabulary to annotate RDF schemas (in particular SHACL shapes) with metadata to define mappings to GraphQL. @en
This ontology establishes classes corresponding to stereotypes used in ISO-conformant models, as used in the rules for conversion of the ISO TC 211 Harmonized Model from the UML to OWL representations @en
An OWL representation of the Sampling Features Schema described in clauses 8-10 of ISO 19156:2011 Geographic Information - Observations and Measurements. @en
ends- Vocabulary of endpoint status (availability, responseTime)
http://labs.mondeca.com/vocab/endpointStatus
Endpoint Status vocabulary intends to describe endpoint availability @en
hr- hRESTS Ontology
http://iserve.kmi.open.ac.uk/ns/hrests
hRESTS is a vocabulary for describing RESTful Web services @en
msm- Minimal Service Model
http://iserve.kmi.open.ac.uk/ns/msm
A simple RDF(S) ontology able to capture (part of) the semantics of both Web services and Web APIs @en
mexcore- MEX Core Vocabulary
http://mex.aksw.org/mex-core
MEX is an RDF vocabulary designed to facilitate interoperability between published machine learning experiments results on the Web. The mex-core layer represents the core information gathered from a basic machine learning experiment design. @en