xsd.2_1.SDMXStructureConstraint.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of SdmxSourceUtil Show documentation
Show all versions of SdmxSourceUtil Show documentation
Open source reference implementation of SDMX
The newest version!
SDMX Constraint Structure Module
The constraint structure module defines the structure of attachment and content constraint constructs.
ConstraintBaseType is an abstract base type that forms the basis of the main abstract ConstraintType. It requires that a name be provided.
ConstraintType is an abstract base type that specific types of constraints (content and attachment) restrict and extend to describe their details. The inclusion of a key or region in a constraint is determined by first processing the included key sets, and then removing those keys defined in the excluded key sets. If no included key sets are defined, then it is assumed the all possible keys or regions are included, and any excluded key or regions are removed from this complete set.
ConstraintAttachment describes the collection of constrainable artefacts that the constraint is attached to.
AttachmentConstraintType describes the details of an attachment constraint by defining the data or metadata key sets or component regions that attributes or reference metadata may be attached in the constraint attachment objects.
ContentConstraintBaseType is an abstract base type that forms the basis for the ContentConstraintType.
ConstraintAttachment describes the collection of constrainable artefacts that the constraint is attached to.
DataKeySet defines a collection of full or partial data keys.
MetadataKeySet defines a collection of metadata keys.
CubeRegion describes a set of dimension values which define a region and attributes which relate to the region for the purpose of describing a constraint.
MetadataTargetRegion describes a set of target object values for a given report structure which define a region, and the metadata attribute which relate to the target for the purpose of describing a constraint.
ContentConstraintType describes the details of a content constraint by defining the content regions, key sets, or release information for the constraint attachment objects. Note that if the constraint is for a data provider, then only release calendar information is relevant, as there is no reliable way of determining which key family is being used to frame constraints in terms of cube regions or key sets.
ReleaseCalendar defines dates on which the constrained data is to be made available.
ReferencePeriod is used to report start date and end date constraints.
The type attribute indicates whether this constraint states what data is actually present for the constraint attachment, or if it defines what content is allowed. The default value is "Actual", meaning the data actually present for the constraint attachment.
ReleaseCalendarType describes information about the timing of releases of the constrained data. All of these values use the standard "P7D" - style format.
Periodicity is the period between releases of the data set.
Offset is the interval between January first and the first release of data within the year.
Tolerance is the period after which the release of data may be deemed late.
KeySetType is an abstract base type for defining a collection of keys.
Key contains a data or metadata key, which are sets of component values which identify the data or metadata.
The isIncluded attribute indicates whether the keys defined in this key set are inclusive or exclusive to the constraint.
DataKeySetType defines a collection of full or partial data keys (dimension values).
Key contains a set of dimension values which identify a full set of data.
MetadataKeySetType defines a collection of metadata keys (identifier component values).
Key contains a set of target object values for a specified report structure which serve to identify which object reference metadata conforming to the specified report structure is available for.
ConstraintAttachmentType describes a collection of references to constrainable artefacts.
DataProvider is reference to a data provider to which the constraint is attached. If this is used, then only the release calendar is relevant. The referenced is provided as a URN and/or a full set of reference fields.
DataSet is reference to a data set to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields.
MetadataSet is reference to a metadata set to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields.
SimpleDataSource describes a simple data source, which is a URL of a SDMX-ML data or metadata message.
DataStructure is reference to a data structure definition to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields. A constraint which is attached to more than one data structure must only express key sets and/or cube regions where the identifiers of the dimensions are common across all structures to which the constraint is attached.
QueryableDataSource describes a queryable data source to which the constraint is attached.
MetadataStructure is reference to a metadata structure definition to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields. A constraint which is attached to more than one metadata structure must only express key sets and/or target regions where the identifiers of the target objects are common across all structures to which the constraint is attached.
QueryableDataSource describes a queryable data source to which the constraint is attached.
Dataflow is reference to a data flow to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields. A constraint can be attached to more than one dataflow, and the dataflows do not necessarily have to be usages of the same data structure. However, a constraint which is attached to more than one data structure must only express key sets and/or cube regions where the identifiers of the dimensions are common across all structures to which the constraint is attached.
QueryableDataSource describes a queryable data source to which the constraint is attached.
Metadataflow is reference to a metadata flow to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields. A constraint can be attached to more than one metadataflow, and the metadataflows do not necessarily have to be usages of the same metadata structure. However, a constraint which is attached to more than one metadata structure must only express key sets and/or target regions where the identifiers of the target objects are common across all structures to which the constraint is attached.
QueryableDataSource describes a queryable data source to which the constraint is attached.
ProvisionAgreementReference is reference to a provision agreement to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields. A constraint can be attached to more than one provision aggreement, and the provision agreements do not necessarily have to be references structure usages based on the same structure. However, a constraint which is attached to more than one provision agreement must only express key sets and/or cube/target regions where the identifier of the components are common across all structures to which the constraint is attached.
QueryableDataSource describes a queryable data source to which the constraint is attached.
AttachmentConstraintAttachmentType defines the structure for specifying the object to which an attachment constraints applies.
DataSet is reference to a data set to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields. Multiple instance can only be used if they have the same underlying structure.
MetadataSet is reference to a metadata set to which the constraint is attached. The referenced is provided as a URN and/or a full set of reference fields. Multiple instance can only be used if they have the same underlying structure.
SimpleDataSource describes a simple data source, which is a URL of a SDMX-ML data or metadata message. Multiple instance can only be used if they have the same underlying structure.
ContentConstraintAttachmentType defines the structure for specifying the target object(s) of a content constraint.