IRI:
http://purl.org/wf4ever/ro
Version IRI:
https://raw.github.com/wf4ever/ro/0.1.1/ro.owl
Current version:
0.1.1
Imported Ontologies:
http://purl.org/NET/dc_owl2dl/terms_od (visualise it with LODE)
http://purl.org/ao/core/ (visualise it with LODE)
http://purl.org/wf4ever/ore-owl (visualise it with LODE)
http://xmlns.com/foaf/0.1/ (visualise it with LODE)
Other visualisation:
Ontology source

Abstract

This ontology shows how AO and ORE ontologies can be used together to define a ResearchObject. This ontology is further customized by the wf4ever ontology.

Table of Content

  1. Classes
  2. Object Properties
  3. Data Properties
  4. Namespace Declarations

Classes

aggregated annotationc back to ToC or Class ToC

IRI: http://purl.org/wf4ever/ro#AggregatedAnnotation

An annotation aggregated within an ro:ResearchObject. Instances of this class are used to annotated resources aggregated within the aggregating research object, proxies of these resources, or the research object itself. In other words, if :ro is the ro:ResearchObject this annotation has been ore:isAggregatedBy, then the annotation should have at least one ao:annotatesResource which is an ore:AggregatedResource which is ore:isAggregatedBy :ro, or the annotated resource is an ore:Proxy which ore:proxyIn :ro, or the annotated resource is :ro. It is possible for the annotation to also annotate non-aggregated resources, but as above, at least one of them needs to be part of the RO or the RO itself. As a subclass of ro:SemanticAnnotation the ao:body must point to an rdfg:Graph which contains the actual annotation.
has super-classes
semantic annotationc
aggregated resource
creator some agent
created some date time
annotates resource some research objectc or aggregated resource or proxy
is aggregated by some research objectc

folderc back to ToC or Class ToC

IRI: http://purl.org/wf4ever/ro#Folder

An ro:Folder is a special kind of ore:Aggregation where every ro:AggregatedResource must have a ro:FolderEntry proxy with a unique ro:entryName within that folder. Note that all resources which are aggregated within an (potentially nested) ro:Folder SHOULD also be aggregated by the same ro:ResearchObject this ro:Folder is aggregated within. Such folders can be nested and (optionally) used to organize the resources of the research object into a file-like structure. All such resources should also be aggregated by the ro:ResearchObject
has super-classes
resourcec
aggregation

folder entryc back to ToC or Class ToC

IRI: http://purl.org/wf4ever/ro#FolderEntry

An ro:FolderEntry is any ore:Proxy instance that associates a resources aggregated within an ro:Folder with a ro:entryName. This name is (case-sensitive) unique within a given folder.
is equivalent to
entry namedp some string
proxy in some folderc
has super-classes
proxy
is in domain of
entry namedp
has keys
proxy in , entry namedp

manifestc back to ToC or Class ToC

IRI: http://purl.org/wf4ever/ro#Manifest

The ro:Manifest is used to describe an ro:ResearchObject. This identifies the resource for the manifest which lists all the aggregations of the research object, typically called ".ro/manifest.rdf" relative to the research object this manifest ore:describes.
is equivalent to
describes some research objectc
has super-classes
resource map

research objectc back to ToC or Class ToC

IRI: http://purl.org/wf4ever/ro#ResearchObject

A research object aggregates a number of resources. A resource can be a workflow, web service, document, data item, data set, workflow run, software or a research object.
is equivalent to
is described by some manifestc
has super-classes
aggregation
created some date time
creator some agent

resourcec back to ToC or Class ToC

IRI: http://purl.org/wf4ever/ro#Resource

An ro:Resource is an ore:AggregatedResource which ore:isAggregatedBy an ro:ResearchObject. This specialisation requires that there exists an ore:Proxy which is ore:proxyFor this resource, and which is ore:proxyIn the same ro:ResearchObject the resource ore:isAggregatedBy. Any annotations on such a proxy will descrive the ro:Resource within that particular ro:ResearchObject, in particular dct:creator and dct:created on the proxy will specify who added the resource to the aggregation at what time. Note that annotations (ro:AggregatedAnnotation) can be added to both the ro:Resource and the ore:Proxy - depending on if the annotation is seen to be globally true (such as the provenance of how the resource was created) or locally true within the Research Object (such as the the resource playing the role of a wf4ever:Dataset). Not all resources aggregated by an ro:ResearchObject are ro:Resource instances, in particular ro:AggregatedAnnotations will also be aggregated, but will not be "true" RO resources (and thus don't need their own ore:Proxy). Aggregated resources MAY also be organised in (potentially nested) ro:Folders to reflect a file-system like structure. Note that any such resources SHOULD also be aggregated in the "mother" ro:ResearchObject.
has super-classes
aggregated resource
is aggregated by some research objectc
inverse proxy for some proxy in some research objectc
has sub-classes
folderc
is in range of
annotates aggregated resourceop

semantic annotationc back to ToC or Class ToC

IRI: http://purl.org/wf4ever/ro#SemanticAnnotation

An ro:SemanticAnnotation is a specialisation of ao:Annotation which requires that ao:body points to an RDF Graph. This might be a Named Graph or a resource which can be resolved separately from the URI given by ao:body. This graph SHOULD mention the resources identified by ao:annotatesResource from this annotation, preferably by using their URIs as subject or object of statements. Note that this use of ao:body is distinct from ao:hasTopic, which also allows the association of a an RDF Graph with an ao:Annotation, but which also implies that this graph is the "topic" (subproperty of bookmark:hasTopic) of the annotated resource. This class does not require this interpretation, it is merely enough that the annotation body mentions the annotated resource, for instance to give it a dc:title or to relate two annotated resources. Also note that the next version of the AO ontology (v2) might change this definition of ao:hasTopic, removing the need for this class.
has super-classes
annotation
body only graph
has sub-classes
aggregated annotationc

Object Properties

annotates aggregated resourceop back to ToC or Object Property ToC

IRI: http://purl.org/wf4ever/ro#annotatesAggregatedResource

ro:annotatesAggregatedResource specifies that an ao:Annotation annotates an aggregated ro:Resource. When used on an ro:AggregatedAnnotation, both the domain and range of this property must ore:isAggregatedBy the same ro:ResearchObject. TODO: Should also ro:ResearchObject and ore:Proxy be in the range of this property, or is this subproperty even needed?
has super-properties
annotates resource
has domain
annotation
has range
resourcec

Data Properties

entry namedp back to ToC or Data Property ToC

IRI: http://purl.org/wf4ever/ro#entryName

This functional property specifies the name of a ro:FolderEntry within an ro:Folder. This name must be case-sensitively unique within the ro:Folder, similar to a filename in a directory. TODO: Need a functional property to specify the top level folder structure of an {{ro:ResearchObject}}?

has characteristics: functional

has domain
folder entryc
has range
string

Namespace Declarations back to ToC

default namespace
http://purl.org/wf4ever/ro#
0-1
http://xmlns.com/foaf/0.1/
0-1-1
https://raw.github.com/wf4ever/ro/0.1.1/
ao
http://purl.org/ao/
bookmark
http://www.w3.org/2002/01/bookmark#
dc-owl2dl
http://purl.org/NET/dc_owl2dl/
docs
http://www.wf4ever-project.org/wiki/display/docs/
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfg-1
http://www.w3.org/2004/03/trix/rdfg-1/
rdfs
http://www.w3.org/2000/01/rdf-schema#
terms
http://www.openarchives.org/ore/terms/
user
http://www.w3.org/2001/Annotea/User/
wf4ever
http://purl.org/wf4ever/
wiki
http://code.google.com/p/annotation-ontology/wiki/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.