InformationFlowDefinition

Generalization is Identifiable.

Superclass hierarchy

Definition

The relationships between parameters across steps is described by the InformationFlowDefinition. Each relationship creates a pathway for an InformationObject to follow.

Examples

The output of one parameter might be the input of another one. Think of a BPMN (Business Process Model and Notation) diagram or an ETL (Extract Transform and Load) pipeline definition as the sum of these relationships.

Explanatory notes

In previous versions of DDI an InformationFlowDefinition was referred to in terms of a “binding”.


Subclasses


Inherited Properties

Name

Description

Data Type

Multi- plicity

agency

Agency expressed as filed with the DDI Agency ID registry [registry.ddialliance.org] with optional additional sub-agency extensions.

:ref:``

1..1

id

ID conforming to the allowed structure of the DDI Identifier and must be unique within the Agency.

:ref:``

1..1

isPersistent

Default value is false indicating that the content of the current version may change (may be in development mode). Set to true when the content of this version will no longer change.

:ref:``

1..1

isUniversallyUnique

Default value is false. If the id of the object was created as a Universally Unique ID (UUID) set to true.

:ref:``

1..1

localId

Locally used identifier unique with a specified context, such as a variable name within a dataset.

LocalIdFormat

0..*

version

Version number of the object.

:ref:``

1..1

versionDate

Date and time the object was changed expressed in standard ISO formats.

XSDdate

0..1

versionRationale

Reason for making a new version of the object.

RationaleDefinition

0..1

versionResponsibility

Contributor who has the ownership and responsibility for the current version.

:ref:``

0..1

Associations

Multiplicity

Association

Navigable Class

Multiplicity

0..*

InformationFlowDefinition_to_Parameters

Parameters

0..*

0..*

InformationFlowDefinition_from_Parameters

Parameters

0..1

TBD

Diagram

TBD