Workflow¶
Parent definition¶
Tag definition¶
<workflow></workflow>
Attributes¶
| Name | Data type and values | Mandatory | For WPS |
|---|---|---|---|
| id | Character String type, not empty | Yes | Yes |
| title | Character String type, not empty | No | Yes |
| abstract | Character String type, not empty | No | Yes |
Table 9: Workflow attributes.
Workflow version¶
Description¶
The version number of the Workflow.
Tag definition¶
<workflow>
<workflowVersion></workflowVersion>
</workflow>
Attributes¶
None
Example¶
<workflowVersion>1.0</workflowVersion>
Nodes¶
Description¶
Every step of the workflow needs a node section to define the I/O and the sequence of actions.
Tag definition¶
<workflow>
<node></node>
</workflow>
Attributes¶
| Name | Data type and values | Mandatory |
|---|---|---|
| id | Character String type, not empty | Yes |
Table 10: Node attributes.
Job¶
Description¶
Every node instantiates a job template.
Tag definition¶
<node>
<job></job>
</node>
Attributes¶
| Name | Data type and values | Mandatory |
|---|---|---|
| id | Character String type, not empty, picked from the job templates section | Yes |
Table 11: Job attributes.
Sources¶
Description¶
Here you can define the inputs of the workflow’s step. According to the cardinality of the source, the process will be instantiated in a number of different processes.
Tag definition¶
<node>
<sources>
<source></source>
</sources>
</node>
Attributes¶
| Name | Data type and values | Mandatory | If “scope = runtime” |
|---|---|---|---|
| id | Character String type, not empty | No | Yes |
| refid | sourceType data structure, Table 13 | No | Yes |
| title | Character String type, not empty | No | Yes |
| abstract | Character String type, not empty | No | Yes |
| scope | Scope data structure, Table 4 | No |
Table 12: Source attributes.
| id | Data type and values | Definition |
|---|---|---|
| string:list | Character String type, not empty | A list of strings comma separated |
| file:urls | Character String type, not empty | The full path of a file containing the list of inputs |
| cas:series | Character String type, not empty | The description URL of a catalogue series (cas). Each dataset returned by the query will be an input |
| wf:node | Character String type, not empty | The id of a previous node from which to take the output |
Table 13: sourceType data structure.
Parameters¶
Description¶
The workflow parameters for the node. You can override the attributes and values of the default parameters section of the relative job template. It is not possible to add new parameters in this section.
Tag definition¶
<node>
<parameters>
<parameter></parameter>
</parameters>
</node>
Attributes (for the single parameter)¶
| Name | Data type and values | Mandatory |
|---|---|---|
| id | Character String type, not empty. It must be one of the parameters defined in the JobTemplates | Yes |
| scope | Scope data structure, Table 4 | No |
| type | Type data structure, Table 5 | No |
| target | Query parameter from the description of the source catalogue (mandatory in case of type=”opensearch”) | No |
Table 14: Parameters attributes.
Possible values (for the single parameter)¶
The possible values for the single parameter are the same as for the Default Parameters. So in the case of type=”LiteralData” (default “type” if not defined), the parameter element can be defined with:
- no values
- a string value
- a list of <options>