Explanation of the diagram

A DataStructureDefinition defines the Dimensions, MeasureDimension,TimeDimension, DataAttributes, and PrimaryMeasure, that comprise the valid structure of data and related attributes that are contained in a DataSet, which is defined by a DataflowDefinition.

The DataflowDefinition may also have additional metadata attached that defines qualitative information and Constraints on the use of the DataStructureDefinition such as the sub set of Codes used in a Dimension. Each DataflowDefinition has a maximum of one DataStructureDefinition specified which defines the structure of any DataSets to be reported/disseminated.

There are three types of dimension (DimensionComponent):

  • Dimension
  • MeasureDimension
  • TimeDimension

The purpose of a MeasureDimension is to specify formally the meaning of the measures (because the PrimaryMeasure typically has a generic meaning e.g. observation value) and to enable multiple measures to be defined and reported in a StructureSpecificDataSet.

The TimeDimension is used to specify the Concept used to convey the time period of the observation in a data set. The TimeDimension must contain a valid representation of time and cannot be coded.

The PrimaryMeasure is the observable phenomenon, and, although there can be only one PrimaryMeasure.

The DataAttribute defines a characteristic of data that are collected or disseminated. The DataAttribute can be specified as being mandatory, or conditional. A DataAttribute is specified as being +relatedTo an AttributeRelationship which defines the constructs to which the DataAttribute is to be reported present in a DataSet.

The DataAttribute can be specified as being related to one of the following artefacts:

  • DataSet (NoSpecifiedRelationship)
  • Dimension or set of Dimensions (DimensionRelationship)
  • Set of Dimensions specified by a GroupKey
  • Observation (PrimaryMeasureRelationship)

A data set comprises the collection of data values and associated metadata that are collected or disseminated according to a known DataStructureDefinition. Note that the DataSet must conform to the DataStructureDefinition associated to the DataflowDefinition for which this DataSet is an “instance of data”. In the actual DataSet as exchanged there must, of course, be a reference to the DataStructureDefinition and optionally a DataflowDefinition, but the DataStructureDefinition is not necessarily exchanged with the data.However, the structural metadata in the DataStructureDefinition can be used by an application to validate the contents of the DataSet in terms of the valid content of a KeyValue as defined by the Representation in the DataStructureDefinition.

An organisation playing the role of DataProvider can be responsible for one or more DataSet.

A DataSet can be formatted either as a generic data set (GenericDataSet,GenericTimeseriesDataSet) or a DataStructureDefinition specific data set (StructureSpecificDataSet, StructureSpecificTimeseriesDataSet).

  • The generic data set is structured in exactly the same way no matter which DataStructureDefinition the DataSet expresses.
  • The structured data set is structured according to one specific DataStructureDefinition. Depending on the syntax chosen for the implementation the structured data set should support better validation at the syntax level.

A DataSet is a collection of a set of Observations that share the same dimensionality,which is specified by a set of unique components (Dimension, MeasureDimension,TimeDimension) defined in the DimensionDescriptor of the DataStructureDefinition, together with associated AttributeValues that define specific characteristics about the artefact to which it is attached. - DataSet, Observation, set of Dimensions. It is structured in terms of a SeriesKey to which Observations arereported.

  • No labels