RO terms

A proposition reached from given premises

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.

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

An input parameter that is optional, meaning a value is not (always) neccessary for executing the associated process (workflow). An optional parameter may receive no value.

When the value of the optional parameter is not provided, the execution of the associated process may internally assume a value, which can be explicitly described using roterms:defaultParameter.

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

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.

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

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

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

A graphical representation of an experiment/investigation

A (potential) workflow value. The value is a piece of data that was used or generated by a wfdesc:WorkflowRun (as a wfprov:Artifact). It can also be used to specify a value that is suggested for a wfdesc:Parameter given by roterms:exampleValue or roterms:defaultValue.

A value can be provided in different forms, indicated as a subclass of roterms:WorkflowValue:

wfprov:Artifact refers directly to the resource by URI

cnt:ContentAsText - inlining the textual value with cnt:chars.

cnt:ContentAsBase64 - inlining the bytes in base64-encoding using cnt:bytes.

co:Collection / co:List listing nested roterms:WorkflowValue instances.

The default value for a wfdesc:Input or wfdesc:Configuration.

The default value is not a suggested value (see roterms:exampleValue), it is the value that is inherently assumed if no value is provided by the workflow run.

The value is given as an roterms:WorkflowValue instance, which allows specification of the value typically as text (cnt:chars), Base64 encoded bytes (cnt:bytes) or a collection of these (co:element).

An example value for a given input or output parameter. The value is given as an roterms:WorkflowValue instance, which allows specification of the value typically as text (cnt:chars), Base64 encoded bytes (cnt:bytes) or a collection of these (co:element).

The wfdesc:Artifact describes a potential wfdesc:WorkflowValue which is of the given semantic type.

The range of this property is given as skos:Concept, because it is envisioned that URIs from any existing (general and domain-specific) vocabularies could be used. It MAY be used with URIs identifying owl:Class-es; indicating that when a workflow is run, its wfprov:Artifact's would be instances of that type.

Unlike the structural type (see roterms:ofStructuralType), the semantic type defines the domain-specific meaning or role of the expected value, for instance Genome Sequence or X-ray image.

The wfdesc:Artifact describes a potential wfdesc:WorkflowValue which is of the given structural type.

The format (media type) of the value SHOULD be specified using dct:format. This property MAY be used when the format is not specific enough, for instance dct:format [ rdv:value "application/xml" ] specifies the serialization as XML, while roterms:ofStructuralType might point to the XML schema.

The range of this property is undefined, it is expected that format-specific classes would define how to define the structural requirements.

The resource is intended to functionally perform the given task.

This property does not specify a domain, but SHOULD generally have a subject like software, workflows and services. It MAY however also be used with agents, such as an foaf:Organization or crowd sourcing.

This property does not specify the task (beyond being a skos:Concept), as it is intended to reuse existing vocabularies. A task might be for general purposes like copying a file and calculating a numeric average, or domain-specific tasks like aligning genome sequences and identifying galaxies.

Previous workflow that is or should be execute

The resource requires the given dataset to function. Although the range is dcat:Dataset, this property does not specify how to detail the dataset, it might be a general requirement (any reference genome) or a particular dataset (an XML file located at a specific URI).

The resource requires the given hardware to function. This property has no particular requirements on how to specify the hardware, it might be a general requirement (x86 Intel architecture) or a particular machine (the super computer Blue Gene).

The resource requires the given software to function. This property has no particular requirements on how to specify the software, it might be a general requirement (Linux), or a particular software installation (python-minimal 2.6.5-0ubuntu1).

Subsequent workflow is or should be execute

The technical support contact for the resource, given as a foaf:Agent.

This property does not specify a domain, but could be used on resources like software, workflows, services, vocabularies, datasets, etc.

The agent SHOULD have a foaf:name. It SHOULD have one of foaf:mbox, foaf:phone or foaf:homepage. The agent may be a foaf:Person (e.g. technical contact), foaf:Group (e.g. mailing lists) or other kind of agent (like automated support).

e.g., 500 patients or 500000 lines