Skip to end of metadata
Go to start of metadata

This page lists the properties and relations that have been agreed* to be used to annotate research objects and/or its aggregated resources. Although some of them are (still?) not part of the RO model, this list will enable the interoperability between myExperiment and RODL ( and with other tools), so that annotations created in one tool are used and interpreted in the same way in the other, avoiding duplicate efforts from the users. This table is based on the annotation mapping discussion wiki page and the latest discussions in Poznan plenary. The properties/classes in blue are the suggested additions to our vocabularies. 

*Not yet, but that's the goal of the tables

General properties

Description

Property

Domain

Range

Label

Comment

Title

dct:title

Any resource

rdfs:Literal

 

 

Description

dct:description

Any resource

---

 

 

Creation date

dct:created

Any resource

rdfs:Literal

 

 

Modification date

dct:modified

Any resource

rdfs:Literal

 

 

Comments/notes

(do we need different property for 3rd parties?)

rdfs:comment

Any resource

rdfs:Literal

 

 

Ratings

mediaont:hasRating
(or meannot:hasRating?)

Any resource

---

 

 

Purpose

roterms:performsTask

Any resource

rdfs:Literal (skos:Concept?)

 

 

?(Research) Institution

dct:publisher

Any resource

foaf:Agent

 

 

Dependencies (e.g., execution environment)

dct:requires

subproperties
  roterms:requiresHardware
  roterms:requiresSoftware
  roterms:requiresDataset

Any resource

--- e.g., URI, name

 

 

License

dct:license

Any resource

LicenseDocument (URI?)

 

 

Citations

dct:isReferencedBy
(or cito:isCitedBy)

Any resource

----

 

 

Technical contact

roterms:technicalContact

Any resource

foaf:Agent

 

 

General documentation

cito:isDocumentedBy

Any resource

--- e.g., URI

 

 

Tags/keywords

roterms:keyword?

@Stian you suggest oa:Tag, but this is a class.
Is there any simple property from oa for this?

@no - it is built in to OA by simply declaring the body to be an oa:Tag and embedding the tag in cnt:chars. e.g.

http://www.openannotation.org/spec/core/20130208/core.html#Tagging


.. but perhaps supporting this would require API changes, so an roterms:keyword might be better for now.

RO

rdfs:Literal

 

 

Scientific domain

dct:subject

RO

Controlled vocabulary code**

 

 

Location (country)

pav:createdAt

RO

--- e.g., geo-location

 

 

RO creator (author)

pav:authoredBy

RO

foaf:Agent

 

See page 19 in arXiv:1304.7224

RO contributor

pav:contributedBy

RO

foaf:Agent

 

 

RO snapshot creator

roevo:wasSnapshotedBy

RO

prov:Agent

 

 

RO release/archive creator

roevo:wasArchivedBy

RO

prov:Agent

 

 

Aggregated Resource creator (author)

pav:authoredBy

Aggregated Resource

foaf:Agent

 

 

Aggregated Resource contributor

pav:contributedBy

Aggregated Resource

foaf:Agent

 

 

Aggregated Resource uploader

pav:createdBy

Proxy for Agg.Res

foaf:Agent

 

 

Aggregated Resource uploaded date

pav:createdOn

Proxy for Agg.Res

rdfs:Literal

 

 

Aggregated Resource provider (do we need it?)

pav:providedBy

Aggregated Resource

foaf:Agent

 

 

Aggregated Resource alternative (do we need it?)

resourcelist:alternate (or roterms:aternate?)

Aggregated Resource

---

 

 

Aggregated Resource type

rdf:type

Aggregated Resource

rdf:Class (see predefined values below)

 

 

** Which controlled vocabulary? Suggestion: dewey decimal classification (first few levels - http://www.oclc.org/dewey/resources/summaries.en.html) http://dewey.info/

Predefined resource types

rdf:Class

Label

Comment

wfdesc:ProcessImplementation, 
   wfdesc:WorkflowDefinition 
   wf4ever:WebService
   wf4ever:Script

Process Implementation

The implementation that is invoked when running the wfdesc:Process, like a wf4ever:Script or wf4ever:WebService. 
The process specifies the implementation using wfdesc:hasImplementation.
The implementation that is invoked when running the wfdesc:Process, like a wf4ever:Script or wf4ever:WebService. The process specifies the implementation using wfdesc:hasImplementation.

wfprov:Artifact
   wf4ever:Dataset
   wf4ever:Document
   wf4ever:Document
   wf4ever:File

Artifact

An artifact is a data value or item which wfprov:wasOutputFrom of a wfprov:ProcessRun or that the process run used as input (wfprov:usedInput). Such an artifact might also be a ro:Resource if it has been aggregated in the ro:ResearchObject (typically if the artifact was used or generated by a wfprov:WorkflowRun) - but this might always not be the case for intermediate values from wfprov:ProcessRun.

wf4ever:File
   wf4ever:ConfigurationFile?  
   wf4ever:BinaryFile?
  wf4ever:SoftwareDependencyFile?

File

A file wfprov:Artifact that was used or generated by a wfprov:WorkflowRun.

wfprov:WorkflowRun

Workflow Run

A workflow run is a process run which has been enacted by a workflow engine, according to a workflow definition. Such a process typically contains several subprocesses corresponding to process descriptions.

roterms:Sketch

Sketch

A graphical representation of an experiment/investigation

roterms:Hypothesis

Hypothesis

A supposition or proposed explanation made on the basis of limited evidence as a starting point for further investigation

roterms:ResearchQuestion

Research Question

The methodological point of departure of scholarly research in both the natural and social sciences. It determines (i) where and what kind of research the writer will be looking for and (ii) the specific objectives the study or paper will address

roterms:Conclusion

Conclusion

A proposition reached from given premises

roterms:Result

Result

An item of information obtained by experiment or some other scientific method; a quantity or formula obtained by calculation

roterms:ResultsPresentation

ResultsPresentation

 ??

roterms:ExampleInput

Example Input

 ?? -- remove ?--

roterms:ExampleOutput

Example Output

 ?? -- remove ?--

roterms:WorkflowRunBundle

Workflow Run Bundle

??

   roterms:ExampleRun
(subclass of wfprov:WorkflowRun)

Example Workflow Run

A workflow run that serves as an example of how to use this workflow. Example runs typically take only a small subset of inputs and have short execution time.

   roterms:ProspectiveRun
(subclass of wfprov:WorkflowRun)

Prospective Workflow Run

A workflow run that is ready to start executing, e.g. all workflow inputs and configuration options have been provided, but no outputs are available yet.

   roterms:ResultGenerationRun
(subclass of wfprov:WorkflowRun)

Results Generating Workflow Run

A workflow run that generated scientific results. Such workflow runs typically take complete data sets as inputs and may take longer to execute.

dct:BibliographicResource 

Bibliographic Resource

A book, article, or other documentary resource.

roterms:Paper

Paper

A bibliographic resource about an experiment/investigation (to be replaced by dct:BibliographicResource)

Predefined relations 

Description

relation

Domain

Range

Evolution relations (derived, revision, ...)
(see roevo)

prov:wasDerivedFrom

subproperties
   prov:wasRevisionOf
   prov:wasQuotedFrom
   prov:hadOriginalSource

Any resource

(prov:Entity)

Any resource

(prov:Entity)

Input used

wfprov:usedInput

wfprov:ProcessRun
   wfprov:WorkflowRun

Any resource
(wfprov:Artifact)

Output produced

wfprov:wasOutputFrom

wfprov:ProcessRun
   wfprov:WorkflowRun

Any resource
(wfprov:Artifact)

Input selected

roterms:inputSelected

wfdesc:Workflow

Any resource
(ro:Resource?)

Default value

(someWorkflow) wfdesc:hasInput (Parameter1)
(Parameter1) roterms:defaultValue (someWorkflowValue)

wfdesc:Workflow

roterms:WorkflowValue
e.g., Resource (URI), RDF file,
bytes

Example Input value

(someWorkflow) wfdesc:hasInput (Parameter1)
(Parameter1) roterms:exampleValue (someWorkflowValue)

wfdesc:Workflow

roterms:WorkflowValue
e.g., Resoure (URI), RDF file,
bytes  (same as roterms:ExampleInput?)

Example Output value

(someWorkflow) wfdesc:hasOutput (Parameter1)
(Parameter1) roterms:exampleValue (someWorkflowValue)

wfdesc:Workflow

roterms:WorkflowValue
e.g., Resoure (URI), RDF file,
bytes (same as roterms:ExampleOutput?)

Sub-workflow

wfdesc:hasSubWorkflow

wfdesc:Workflow

wfdesc:Workflow

Workflow description

wfprov:describedByWorkflow

wfprov:WorkflowRun

wfdesc:Workflow

Semantic type*

roterms:ofSemanticType 

wfdesc:Artifact

skos:Concept

Structural type*

roterms:ofStructuralType 

wfdesc:Artifact

owl:Thing e.g., URI to schema or specific class

Encoding*

dct:format

wfdesc:Artifact

dcterms:IMT [dcterms:MediaTypeOrExtent]

root URI of web service

wf4ever:rootURI

wf4ever:WebService

xsd:anyURI

* This properties are more general should go in first table i guess? Dont understand why you need semantictype relation, what else you need than the class type of the artifact?

Workflow specific properties

Description

Property

Domain

Range

Internal Identifier

dct:identifier

wfdesc:Workflow

UUID

Image

foaf:depiction

wfdesc:Workflow

foaf:Image

Type of process

rdf:type

wfdesc:Process

SOAP, REST, script...
Predefined values:

Process Implementation

wfdesc:hasImplementation

wfdesc:Process

wfdesc:ProcessImplementation

Workflow executor Agent

wfprov:wasInitiatedBy

wfprov:WorkflowRun

 foaf:Agent (prov:Person or prov:SoftwareAgent)

Time to execute

wfprov:durationInSeconds

wfprov:WorkflowRun

 xsd:double

Sample size

roterms:sampleSize

wfprov:Artifact

 Literal (e.g. "500 patients"  or "500000 lines")

Previous workflow executed

roterms:previousWorkflow

wfdesc:Workflow

 wfdesc:Workflow

Subsequent workflow executed

roterms:subsequentWorkflow

wfdesc:Workflow

 wfdesc:Workflow

Other properties in user table not included
  • RO/folder size (do we need this?)
  • Web pages to bibliography (what is this? do we need it?)
  • simlinks?
  • No labels