Interface TransformationConfigTags
public interface TransformationConfigTags
These definitions are necessary for converting Workflow-trees to Workflow-NESTGraphs. They
connect the internal functionality of each necessary entity, to the name in the
transformation-config.xml - file. In this case the name of the internal functionality always
corresponds to the name in the transformation-config.xml. However, a different naming is possible
and due to programming habits the definition of strings are not done in the same file as the code
lies.
The transformation-config.xml offers configuration for transforming the tree structure of workflows into NESTGraph-workflows. As NESTGraph explicitly specifies relations, which are implicitly known in the tree structure of workflows, additional definitions have to be provided. Usertypes (model.xml) are necessary to provide this additional definition. The benefit of using usertypes (model.xml) for semantic descriptions is, that one is then also able to use the CAKE I - similarity measurement (sim.xml) for calculating similarities between semantic descriptions.
- Author:
- Alexander Stromer
-
Field Summary
Modifier and TypeFieldDescriptionstatic final String
static final String
the semantic classes of task and dataflow also have this attribute.static final String
static final String
the default datasemantic-usertype has to contain this attribute, to set the optional name for DataNodesstatic final String
the semantic classes of task, subworkflow and node have to have this attribute.static final String
the semantic classes of task and node have to have this attribute.static final String
many semantic classes (task, workflow, subworkflow, node) have to contain this attribute in order to store the status of this itemstatic final String
the default edgesemantic-usertype has to contain this attribute, to set the types for PartOfEdges and DataflowEdgesstatic final String
the default datasemantic-usertype has to contain this attribute, to set the value of a DataNodestatic final String
NESTGraphs do allow semantic descriptions for edges (tree workflows dont allow that as they dont have any explicit specification of edges).static final String
As tree workflows already distinguishes between DataItems and other items in the workflow, the DataItems provide a name and value by themselves.static final String
NESTGraphs do allow semantic descriptions for edges (tree workflows dont allow that as they dont have any explicit specification of edges).static final String
Nodes (AND/XOR/LOOP) also need to store their statusstatic final String
Subworkflows need to store their statusstatic final String
Tasks need to store their status in NESTGraph, so we have to know the SemanticClass we should use when transformingstatic final String
The workflow also has a global status, so we need the SemanticClass we should usestatic final String
if the DataItem is used as outputstatic final String
if the DataItem is used as outputstatic final String
if the DataItem is used as outputstatic final String
if the DataItem is used as outputstatic final String
if the DataItem is used as outputstatic final String
if the DataItem is used as outputstatic final String
if the DataItem is used as outputstatic final String
static final String
static final String
if the DataItem is used as inputstatic final String
if the PartOfEdge is connected to a controlflowitem (like AND_SPLIT, AND_JOIN, ..)static final String
if the PartOfEdge is connected to a subworkflowstatic final String
if the PartOfEdge is connected to a taskstatic final String
if DataItem is only used as input for tasksstatic final String
if DataItem is used as input AND output for tasksstatic final String
if DataItem is only used as ouptut for tasksstatic final String
if DataItem is not used directly for tasks but rather as a parameter for the workflow / not as input or outputstatic final String
static final String
static final String
static final String
static final String
if the DataItem is used as outputstatic final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
static final String
-
Field Details
-
CLASS_DEFAULT_EDGESEMANTIC
NESTGraphs do allow semantic descriptions for edges (tree workflows dont allow that as they dont have any explicit specification of edges). You have to provide a usertype for semantic descriptions of edges for the transformation.- See Also:
-
CLASS_DEFAULT_CONTROLEDGESEMANTIC
NESTGraphs do allow semantic descriptions for edges (tree workflows dont allow that as they dont have any explicit specification of edges). You have to provide a usertype for semantic descriptions of edges for the transformation.- See Also:
-
CLASS_DEFAULT_DATASEMANTIC
As tree workflows already distinguishes between DataItems and other items in the workflow, the DataItems provide a name and value by themselves. However, for NESTGraph-similarity-computation, these items have to be accessable through the semantic description. Therefore ANY DataNode in the NestGraph has to have a semantic description to hold the value of the DataItem and an optional name (e.g. name: color; value: green)- See Also:
-
CLASS_DEFAULT_TASKSEMANTIC
Tasks need to store their status in NESTGraph, so we have to know the SemanticClass we should use when transforming- See Also:
-
CLASS_DEFAULT_NODESEMANTIC
Nodes (AND/XOR/LOOP) also need to store their status- See Also:
-
CLASS_DEFAULT_WORKFLOWSEMANTIC
The workflow also has a global status, so we need the SemanticClass we should use- See Also:
-
CLASS_DEFAULT_SUBWORKFLOWSEMANTIC
Subworkflows need to store their status- See Also:
-
ATT_SYS_TYPE
the default edgesemantic-usertype has to contain this attribute, to set the types for PartOfEdges and DataflowEdges- See Also:
-
ATT_SYS_NAME
the default datasemantic-usertype has to contain this attribute, to set the optional name for DataNodes- See Also:
-
ATT_SYS_VALUE
the default datasemantic-usertype has to contain this attribute, to set the value of a DataNode- See Also:
-
ATT_SYS_STATUS
many semantic classes (task, workflow, subworkflow, node) have to contain this attribute in order to store the status of this item- See Also:
-
ATT_SYS_SEQUENCE_ID
the semantic classes of task, subworkflow and node have to have this attribute. this is a workaround for keeping the sequence ID in NESTGraph- See Also:
-
ATT_SYS_SEQUENCE_STATUS
the semantic classes of task and node have to have this attribute. this is a workaround for keeping the sequence status in NESTGraph- See Also:
-
ATT_NAME
the semantic classes of task and dataflow also have this attribute.- See Also:
-
VAL_IS_INPUT
if DataItem is only used as input for tasks- See Also:
-
VAL_IS_OUTPUT
if DataItem is only used as ouptut for tasks- See Also:
-
VAL_IS_INTERMEDIATE
if DataItem is used as input AND output for tasks- See Also:
-
VAL_IS_PARAMETER
if DataItem is not used directly for tasks but rather as a parameter for the workflow / not as input or output- See Also:
-
VAL_HAS_TASK
if the PartOfEdge is connected to a task- See Also:
-
VAL_HAS_SUBWORKFLOW
if the PartOfEdge is connected to a subworkflow- See Also:
-
VAL_HAS_CONTROL
if the PartOfEdge is connected to a controlflowitem (like AND_SPLIT, AND_JOIN, ..)- See Also:
-
VAL_CONSUMES
if the DataItem is used as input- See Also:
-
VAL_PRODUCES
if the DataItem is used as output- See Also:
-
VAL_AND_JOIN
- See Also:
-
VAL_AND_SPLIT
- See Also:
-
VAL_XOR_JOIN
- See Also:
-
VAL_XOR_SPLIT
- See Also:
-
VAL_LOOP_JOIN
- See Also:
-
VAL_LOOP_SPLIT
- See Also:
-
VAL_OR_JOIN
- See Also:
-
VAL_OR_SPLIT
- See Also:
-
VAL_TASK_TYPE_UNKNOWN
- See Also:
-
VAL_TASK_TYPE_WORKLISTTASK
- See Also:
-
VAL_TASK_TYPE_SERVICETASK
- See Also:
-
VAL_TASK_TYPE_USERTASK
- See Also:
-
VAL_TASK_TYPE_SENDTASK
- See Also:
-
VAL_TASK_TYPE_RECEIVETASK
- See Also:
-
VAL_TASK_TYPE_PLACEHOLDERTASK
- See Also:
-
VAL_STATUS_UNKNOWN
- See Also:
-
VAL_STATUS_READY
- See Also:
-
VAL_STATUS_ACTIVE
- See Also:
-
VAL_STATUS_COMPLETED
- See Also:
-
VAL_STATUS_FAILED
- See Also:
-
VAL_STATUS_OMITTING
- See Also:
-
VAL_STATUS_OMITTED
- See Also:
-
VAL_STATUS_BLOCKED
- See Also:
-
VAL_STATUS_SUSPENDED
- See Also:
-
DATANODE_ID_PREFIX
if the DataItem is used as output- See Also:
-
EDGE_ID_PREFIX
if the DataItem is used as output- See Also:
-
SUBWFL_ID_PREFIX
if the DataItem is used as output- See Also:
-
CONTROLFLOW_END_PREFIX
if the DataItem is used as output- See Also:
-
NESTGRAPH_WORKFLOWNODE_ID_PREFIX
if the DataItem is used as output- See Also:
-
UIGRAPH_STARTNODE_ID
if the DataItem is used as output- See Also:
-
UIGRAPH_ENDNODE_ID
if the DataItem is used as output- See Also:
-
ATT_STREAM_TYPE
- See Also:
-
ATT_FEATURE_LIST
- See Also:
-