InformationFlowDefinition¶
Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::Process::InformationFlowDefinition
Definition¶
The relationships between parameters across steps is described by the information flow definition. Each relationship creates a pathway for an information object to follow.
Examples¶
The output of one parameter might be the input of another one. Think of a Business Process Model and Notation (BPMN) diagram or an extract, transform, and load (ETL) pipeline definition as the sum of these relationships.
Explanatory notes¶
In DDI Lifecycle an information flow definition was referred to in terms of a “binding”.
Diagram
Attributes
Name |
Inherited from |
Description |
Data Type |
Multiplicity |
Default value |
|---|---|---|---|---|---|
identifier |
- own class - |
Identifier for objects requiring short- or long-lasting referencing and management. |
0..1 |
Associations
Direction |
Association |
Description |
Multiplicity of InformationFlowDefinition |
Package of Other Class |
Other Class |
Multiplicity of other class |
Aggregation Kind |
Inherited from |
|---|---|---|---|---|---|---|---|---|
to |
ControlLogic has InformationFlowDefinition |
A control construct has zero or more information flow definitions each of which provides the control construct with zero or more input and output parameters used or produced in the step/sub-step with which it is associated. |
0..* |
- own package - |
0..* |
none |
- own class - |
|
from |
InformationFlowDefinition from Parameter |
From parameters are the outputs from a control construct produced in its step/sub-step. |
0..* |
- own package - |
0..1 |
none |
- own class - |
|
from |
InformationFlowDefinition to Parameter |
To parameters are the inputs to a control construct used in its step/sub-step. |
0..* |
- own package - |
0..* |
none |
- own class - |
Syntax representations / encodings
All syntax representations except the Canonical XMI are provided as reference points for specific implementations, or for use as defaults if sufficient in the form presented.
Fragment for the class InformationFlowDefinition (entire model as XMI)
1<packagedElement xmlns:StandardProfile="http://www.eclipse.org/uml2/5.0.0/UML/Profile/Standard"
2 xmlns:uml="http://www.eclipse.org/uml2/5.0.0/UML"
3 xmlns:xmi="http://www.omg.org/spec/XMI/20131001"
4 xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition"/>
11 <body>Definition
12============
13The relationships between parameters across steps is described by the information flow definition. Each relationship creates a pathway for an information object to follow.
14
15Examples
16==========
17The output of one parameter might be the input of another one. Think of a Business Process Model and Notation (BPMN) diagram or an extract, transform, and load (ETL) pipeline definition as the sum of these relationships.
18
19Explanatory notes
20===================
21In DDI Lifecycle an information flow definition was referred to in terms of a "binding".</body>
22 </ownedComment>
23 <name>InformationFlowDefinition</name>
24 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-identifier"
25 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-identifier"
26 xmi:type="uml:Property">
27 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-identifier-ownedComment"
28 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-identifier-ownedComment"
29 xmi:type="uml:Comment">
30 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-identifier"/>
31 <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
32 </ownedComment>
33 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-identifier-lowerValue"
34 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-identifier-lowerValue"
35 xmi:type="uml:LiteralInteger"/>
36 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-identifier-upperValue"
37 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-identifier-upperValue"
38 xmi:type="uml:LiteralUnlimitedNatural">
39 <value>1</value>
40 </upperValue>
41 <name>identifier</name>
42 <isID>true</isID>
43 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
44 </ownedAttribute>
45 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-ownedAttribute_1"
46 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-ownedAttribute_1"
47 xmi:type="uml:Property">
48 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-ownedAttribute_1-lowerValue"
49 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-ownedAttribute_1-lowerValue"
50 xmi:type="uml:LiteralInteger"/>
51 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-ownedAttribute_1-upperValue"
52 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-ownedAttribute_1-upperValue"
53 xmi:type="uml:LiteralUnlimitedNatural">
54 <value>1</value>
55 </upperValue>
56 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition_from_Parameter"/>
57 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Process-Parameter"/>
58 </ownedAttribute>
59 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-ownedAttribute_2"
60 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-ownedAttribute_2"
61 xmi:type="uml:Property">
62 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-ownedAttribute_2-lowerValue"
63 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-ownedAttribute_2-lowerValue"
64 xmi:type="uml:LiteralInteger"/>
65 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition-ownedAttribute_2-upperValue"
66 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#InformationFlowDefinition-ownedAttribute_2-upperValue"
67 xmi:type="uml:LiteralUnlimitedNatural">
68 <value>*</value>
69 </upperValue>
70 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Process-InformationFlowDefinition_to_Parameter"/>
71 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Process-Parameter"/>
72 </ownedAttribute>
73</packagedElement>
Fragment for the class InformationFlowDefinition (entire XML Schema)
1<xs:element name="InformationFlowDefinition"
2 type="InformationFlowDefinitionXsdType"
3 xml:id="InformationFlowDefinition">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Process::InformationFlowDefinition -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ============
8 The relationships between parameters across steps is described by the information flow definition. Each relationship creates a pathway for an information object to follow.
9
10 Examples
11 ==========
12 The output of one parameter might be the input of another one. Think of a Business Process Model and Notation (BPMN) diagram or an extract, transform, and load (ETL) pipeline definition as the sum of these relationships.
13
14 Explanatory notes
15 ===================
16 In DDI Lifecycle an information flow definition was referred to in terms of a "binding".</xs:documentation>
17 </xs:annotation>
18</xs:element>
19<xs:complexType name="InformationFlowDefinitionXsdType"
20 xml:id="InformationFlowDefinitionXsdType">
21 <xs:annotation>
22 <xs:documentation>Definition
23 ============
24 The relationships between parameters across steps is described by the information flow definition. Each relationship creates a pathway for an information object to follow.
25
26 Examples
27 ==========
28 The output of one parameter might be the input of another one. Think of a Business Process Model and Notation (BPMN) diagram or an extract, transform, and load (ETL) pipeline definition as the sum of these relationships.
29
30 Explanatory notes
31 ===================
32 In DDI Lifecycle an information flow definition was referred to in terms of a "binding".</xs:documentation>
33 </xs:annotation>
34 <xs:sequence>
35 <xs:element name="identifier"
36 type="IdentifierXsdType"
37 minOccurs="0"
38 maxOccurs="1"
39 xml:id="InformationFlowDefinition-identifier">
40 <xs:annotation>
41 <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
42 </xs:annotation>
43 </xs:element>
44 <xs:element name="InformationFlowDefinition_from_Parameter"
45 minOccurs="0"
46 maxOccurs="1"
47 xml:id="InformationFlowDefinition_from_Parameter">
48 <xs:annotation>
49 <xs:documentation>From parameters are the outputs from a control construct produced in its step/sub-step.</xs:documentation>
50 </xs:annotation>
51 <xs:complexType>
52 <xs:complexContent>
53 <xs:restriction base="AssociationReferenceXsdType">
54 <xs:sequence>
55 <xs:element name="ddiReference"
56 type="InternationalRegistrationDataIdentifierXsdType"
57 minOccurs="0"
58 maxOccurs="1"
59 xml:id="InformationFlowDefinition_from_Parameter-ddiReference"/>
60 <xs:element name="validType"
61 minOccurs="0"
62 maxOccurs="unbounded"
63 xml:id="InformationFlowDefinition_from_Parameter-validType">
64 <xs:simpleType>
65 <xs:restriction base="xs:NMTOKEN">
66 <xs:enumeration value="Parameter"/>
67 </xs:restriction>
68 </xs:simpleType>
69 </xs:element>
70 </xs:sequence>
71 </xs:restriction>
72 </xs:complexContent>
73 </xs:complexType>
74 </xs:element>
75 <xs:element name="InformationFlowDefinition_to_Parameter"
76 minOccurs="0"
77 maxOccurs="unbounded"
78 xml:id="InformationFlowDefinition_to_Parameter">
79 <xs:annotation>
80 <xs:documentation>To parameters are the inputs to a control construct used in its step/sub-step.</xs:documentation>
81 </xs:annotation>
82 <xs:complexType>
83 <xs:complexContent>
84 <xs:restriction base="AssociationReferenceXsdType">
85 <xs:sequence>
86 <xs:element name="ddiReference"
87 type="InternationalRegistrationDataIdentifierXsdType"
88 minOccurs="0"
89 maxOccurs="1"
90 xml:id="InformationFlowDefinition_to_Parameter-ddiReference"/>
91 <xs:element name="validType"
92 minOccurs="0"
93 maxOccurs="unbounded"
94 xml:id="InformationFlowDefinition_to_Parameter-validType">
95 <xs:simpleType>
96 <xs:restriction base="xs:NMTOKEN">
97 <xs:enumeration value="Parameter"/>
98 </xs:restriction>
99 </xs:simpleType>
100 </xs:element>
101 </xs:sequence>
102 </xs:restriction>
103 </xs:complexContent>
104 </xs:complexType>
105 </xs:element>
106 </xs:sequence>
107</xs:complexType>
Fragment for the class InformationFlowDefinition (main ontology)
1# class InformationFlowDefinition
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Process::InformationFlowDefinition
3cdi:InformationFlowDefinition
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "InformationFlowDefinition";
6 rdfs:comment "Definition \n============ \nThe relationships between parameters across steps is described by the information flow definition. Each relationship creates a pathway for an information object to follow. \n\nExamples \n========== \nThe output of one parameter might be the input of another one. Think of a Business Process Model and Notation (BPMN) diagram or an extract, transform, and load (ETL) pipeline definition as the sum of these relationships. \n\nExplanatory notes \n=================== \nIn DDI Lifecycle an information flow definition was referred to in terms of a \"binding\"."@en;
7
8.
9
10cdi:InformationFlowDefinition-identifier
11 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12 rdfs:label "identifier";
13 rdfs:comment "Identifier for objects requiring short- or long-lasting referencing and management."@en;
14 rdfs:domain cdi:InformationFlowDefinition;
15 rdfs:range cdi:Identifier;
16.
17
18
19cdi:InformationFlowDefinition_from_Parameter
20 a rdf:Property, owl:ObjectProperty, ucmis:Association;
21 # ASSOCIATION
22 rdfs:label "from";
23 skos:altLabel "InformationFlowDefinition_from_Parameter";
24 rdfs:comment "From parameters are the outputs from a control construct produced in its step/sub-step."@en;
25 rdfs:domain cdi:InformationFlowDefinition;
26 rdfs:range cdi:Parameter;
27.
28
29cdi:InformationFlowDefinition_to_Parameter
30 a rdf:Property, owl:ObjectProperty, ucmis:Association;
31 # ASSOCIATION
32 rdfs:label "to";
33 skos:altLabel "InformationFlowDefinition_to_Parameter";
34 rdfs:comment "To parameters are the inputs to a control construct used in its step/sub-step."@en;
35 rdfs:domain cdi:InformationFlowDefinition;
36 rdfs:range cdi:Parameter;
37.
Fragment for the class InformationFlowDefinition (main JSON-LD)
1{
2 "@context": [
3 {
4 "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
5 "xsd": "http://www.w3.org/2001/XMLSchema#",
6 "InformationFlowDefinition": "cdi:InformationFlowDefinition",
7 "identifier": {
8 "@id": "cdi:InformationFlowDefinition-identifier",
9 "@type": "@id",
10 "@context": "Identifier.jsonld"
11 },
12
13 "from": {
14 "@id": "cdi:InformationFlowDefinition_from_Parameter",
15 "@type": "@id" },
16 "to": {
17 "@id": "cdi:InformationFlowDefinition_to_Parameter",
18 "@type": "@id" },
19 "has_OF_ControlLogic": {
20 "@reverse": "cdi:ControlLogic_has_InformationFlowDefinition",
21 "@type": "@id"
22 },
23 " comment ": "tag:json-should-support-trailing-commas"
24 }
25 ],
26 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:11.",
27 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Process::InformationFlowDefinition"
28}
