Changes for page 3 SDMX Base Package

Last modified by Helena K. on 2026/06/08 16:18

From version 40.8
edited by Helena K.
on 2026/06/08 16:15
Change comment: There is no comment for this version
To version 40.2
edited by Helena K.
on 2026/06/08 16:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -120,32 +120,32 @@
120 120  
121 121  ==== 3.4.2.1 Narrative ====
122 122  
123 -The FacetType and FacetValueType enumerations are used to specify the valid format of the content of a non-enumerated [[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] or the usage of a [[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] when specified for use on a //[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]// on a //Structure// (such as a [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] in a DataStructureDefinition). The description of the various types can be found in the chapter on ConceptScheme (section 4.5).
123 +The FacetType and FacetValueType enumerations are used to specify the valid format of the content of a non-enumerated Concept or the usage of a Concept when specified for use on a //Component// on a //Structure// (such as a Dimension in a DataStructureDefinition). The description of the various types can be found in the chapter on ConceptScheme (section 4.5).
124 124  
125 125  The ActionType enumeration is used to specify the action that a receiving system should take when processing the content that is the object of the action. It is enumerated as follows:
126 126  
127 -* Append: Data or metadata is an [[incremental update>>doc:sdmx:Glossary 2\.1.Incremental update.WebHome]] for an existing data/[[metadata set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]] or the provision of new data or documentation ([[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in (% id="confict-imterms-29" %)version(%%) 1.0 of the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Technical Standards.
127 +* Append: Data or metadata is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in (% id="confict-imterms-29" %)version(%%) 1.0 of the SDMX Technical Standards.
128 128  * Replace: Data/metadata is to be replaced and may also include additional data/metadata to be appended.
129 129  * Delete: Data/Metadata is to be deleted.
130 130  * Information: Data and metadata are for information purposes.
131 131  
132 -The ToValueType data type contains the [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] to support transformations defined in the StructureMap (see Section 0).
132 +The ToValueType data type contains the attributes to support transformations defined in the StructureMap (see Section 0).
133 133  
134 -The ConstraintRoleType data type contains the [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] that identify the purpose of a [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] (allowableContent, actualContent).
134 +The ConstraintRoleType data type contains the attributes that identify the purpose of a Constraint (allowableContent, actualContent).
135 135  
136 -The ComponentRoleType data type contains the predefined [[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] roles that can be assigned to any [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]].
136 +The ComponentRoleType data type contains the predefined Concept roles that can be assigned to any Component.
137 137  
138 -The CascadeValues data type contains the possible values for a MemberValue within a CubeRegion, in order to enable cascading to all children [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] of a selected [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]], while including/excluding the latter in the selection.
138 +The CascadeValues data type contains the possible values for a MemberValue within a CubeRegion, in order to enable cascading to all children Codes of a selected Code, while including/excluding the latter in the selection.
139 139  
140 -The VersionType data types provides the details for versioning according to [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Standards Section 6, paragraph “4.3 Versioning”.
140 +The VersionType data types provides the details for versioning according to SDMX versioning rules, as explained in SDMX Standards Section 6, paragraph “4.3 Versioning”.
141 141  
142 142  == 3.5 The Item Scheme Pattern ==
143 143  
144 144  === 3.5.1 Context ===
145 145  
146 -The [[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
146 +The Item Scheme is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
147 147  
148 -The //ItemScheme// is the basis for CategoryScheme, [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], ConceptScheme, ReportingTaxonomy, //OrganisationScheme//, TransformationScheme, CustomTypeScheme, NamePersonalisationScheme, RulesetScheme, VtlMappingScheme and UserDefinedOperatorScheme.
148 +The //ItemScheme// is the basis for CategoryScheme, Codelist, ConceptScheme, ReportingTaxonomy, //OrganisationScheme//, TransformationScheme, CustomTypeScheme, NamePersonalisationScheme, RulesetScheme, VtlMappingScheme and UserDefinedOperatorScheme.
149 149  
150 150  === 3.5.2 Class Diagram ===
151 151  
... ... @@ -157,15 +157,15 @@
157 157  
158 158  ==== 3.5.3.1 Narrative ====
159 159  
160 -The //ItemScheme// is an abstract class which defines a set of //Item// (this class is also abstract). Its main purpose is to define a mechanism which can be used to create taxonomies which can classify other parts of the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. It is derived from //MaintainableArtefact// which gives it the ability to be annotated, have identity, naming, versioning and be associated with an Agency. An example of a concrete class is a ConceptScheme. The associated [[Concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] are //Item//s.
160 +The //ItemScheme// is an abstract class which defines a set of //Item// (this class is also abstract). Its main purpose is to define a mechanism which can be used to create taxonomies which can classify other parts of the SDMX Information Model. It is derived from //MaintainableArtefact// which gives it the ability to be annotated, have identity, naming, versioning and be associated with an Agency. An example of a concrete class is a ConceptScheme. The associated Concepts are //Item//s.
161 161  
162 -In an exchange environment an //ItemScheme// is allowed to contain a sub-set of the //Item//s in the maintained //ItemScheme//. If such an ItemScheme is disseminated with a sub-set of the //Item//s then the fact that this is a sub-set is denoted by setting the isPartial [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] to "true".
162 +In an exchange environment an //ItemScheme// is allowed to contain a sub-set of the //Item//s in the maintained //ItemScheme//. If such an ItemScheme is disseminated with a sub-set of the //Item//s then the fact that this is a sub-set is denoted by setting the isPartial attribute to "true".
163 163  
164 -A “partial” //ItemScheme// cannot be maintained independently in its partial form i.e., it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g., names and descriptions) cannot deviate from the content in the full //ItemScheme//. Furthermore, the id of the //ItemScheme// where isPartial is set to "true" is the same as the id of the full //ItemScheme// (agencyId, id, [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]]). This is important as this is the id that that is referenced in other structures (e.g., a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] referenced in a [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]) and this id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
164 +A “partial” //ItemScheme// cannot be maintained independently in its partial form i.e., it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g., names and descriptions) cannot deviate from the content in the full //ItemScheme//. Furthermore, the id of the //ItemScheme// where isPartial is set to "true" is the same as the id of the full //ItemScheme// (agencyId, id, version). This is important as this is the id that that is referenced in other structures (e.g., a Codelist referenced in a DSD) and this id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
165 165  
166 -The purpose of a partial //ItemScheme// is to support the exchange and dissemination of a subset //ItemScheme// without the need to maintain multiple //ItemScheme//s which contain the same //Item//s. For instance, when a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] is used in a DataStructureDefinition it is sometimes the case that only a sub-set of the [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] are relevant. In this case a partial [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] can be constructed using the [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] mechanism explained later in this document.
166 +The purpose of a partial //ItemScheme// is to support the exchange and dissemination of a subset //ItemScheme// without the need to maintain multiple //ItemScheme//s which contain the same //Item//s. For instance, when a Codelist is used in a DataStructureDefinition it is sometimes the case that only a sub-set of the Codes in a Codelist are relevant. In this case a partial Codelist can be constructed using the Constraint mechanism explained later in this document.
167 167  
168 -//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]], a name and a description in the form of an InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e., it implicitly has the same agencyId as the //ItemScheme//).
168 +//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn attributes, a name and a description in the form of an InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e., it implicitly has the same agencyId as the //ItemScheme//).
169 169  
170 170  The //Item// can be hierarchic and so one //Item// can have child //Item//s. The restriction of the hierarchic association is that a child //Item// can have only parent //Item//.
171 171  
... ... @@ -179,7 +179,7 @@
179 179  Direct sub classes are:
180 180  CategoryScheme
181 181  ConceptScheme
182 -[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]
182 +Codelist
183 183  ReportingTaxonomy
184 184  //OrganisationScheme//
185 185  TransformationScheme
... ... @@ -188,15 +188,15 @@
188 188  VtlMappingScheme
189 189  UserDefinedOperatorScheme
190 190  )))|(% style="width:583px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
191 -| |(% style="width:297px" %)isPartial|(% style="width:583px" %)Denotes whether the [[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] contains a subset of the full set of Items in the maintained scheme.
191 +| |(% style="width:297px" %)isPartial|(% style="width:583px" %)Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
192 192  | |(% style="width:297px" %)/items|(% style="width:583px" %)Association to the Items in the scheme.
193 193  |//Item//|(% style="width:297px" %)(((
194 194  Inherits from:
195 195  //NameableArtefact//
196 196  Direct sub classes are
197 -[[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]
198 -[[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]]
199 -[[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]]
197 +Category
198 +Concept
199 +Code
200 200  ReportingCategory
201 201  //Organisation//
202 202  Transformation
... ... @@ -206,15 +206,15 @@
206 206  VtlMapping
207 207  UserDefinedOperator
208 208  )))|(% style="width:583px" %)(((
209 -The Item is an item of content in an [[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]]. This may be a node in a taxonomy or ontology, a [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in a [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] etc. Node that at the conceptual level the Organisation is not hierarchic.
209 +The Item is an item of content in an Item Scheme. This may be a node in a taxonomy or ontology, a code in a code list etc. Node that at the conceptual level the Organisation is not hierarchic.
210 210  )))
211 -| |(% style="width:297px" %)[[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]|(% style="width:583px" %)This allows an Item optionally to have one or more child Items
211 +| |(% style="width:297px" %)hierarchy|(% style="width:583px" %)This allows an Item optionally to have one or more child Items
212 212  
213 213  == 3.6 The Structure Pattern ==
214 214  
215 215  === 3.6.1 Context ===
216 216  
217 -The Structure Pattern is a basic architectural pattern which allows the specification of complex tabular structures which are often found in statistical data (such as [[Data (% id="confict-imterms-88" %)Structure(%%) Definition>>doc:Glossary 2\.1.Data structure definition.WebHome]], and [[Metadata (% id="confict-imterms-89" %)Structure(%%) Definition>>doc:Glossary 2\.1.Metadata structure definition.WebHome]]). A Structure is a set of ordered lists. A pattern to underpin this tabular structure has been developed, so that commonalities between these structure definitions can be supported by common software and common syntax structures.
217 +The Structure Pattern is a basic architectural pattern which allows the specification of complex tabular structures which are often found in statistical data (such as Data (% id="confict-imterms-88" %)Structure(%%) Definition, and Metadata (% id="confict-imterms-89" %)Structure(%%) Definition). A Structure is a set of ordered lists. A pattern to underpin this tabular structure has been developed, so that commonalities between these structure definitions can be supported by common software and common syntax structures.
218 218  
219 219  === 3.6.2 Class Diagrams ===
220 220  
... ... @@ -232,31 +232,31 @@
232 232  
233 233  The //Structure// is an abstract class which contains a set of one or more //ComponentList//(s) (this class is also abstract). An example of a concrete //Structure// is DataStructureDefinition.
234 234  
235 -The //ComponentList// is a list of one or more //[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]//(s//)//. The //ComponentList// has several concrete descriptor classes based on it: DimensionDescriptor, GroupDimensionDescriptor, MeasureDescriptor, and AttributeDescriptor of the DataStructureDefinition and MetadataAttributeDescriptor of the MetadataStructureDefinition.
235 +The //ComponentList// is a list of one or more //Component//(s//)//. The //ComponentList// has several concrete descriptor classes based on it: DimensionDescriptor, GroupDimensionDescriptor, MeasureDescriptor, and AttributeDescriptor of the DataStructureDefinition and MetadataAttributeDescriptor of the MetadataStructureDefinition.
236 236  
237 -The //[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]// is contained in a //ComponentList//. The type of //[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]// in a //ComponentList// is dependent on the concrete class of the ComponentList as follows:
237 +The //Component// is contained in a //ComponentList//. The type of //Component// in a //ComponentList// is dependent on the concrete class of the ComponentList as follows:
238 238  
239 -DimensionDescriptor: [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]], TimeDimension
240 -GroupDimensionDescriptor: [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]], TimeDimension
241 -MeasureDescriptor: [[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]]
239 +DimensionDescriptor: Dimension, TimeDimension
240 +GroupDimensionDescriptor: Dimension, TimeDimension
241 +MeasureDescriptor: Measure
242 242  AttributeDescriptor: DataAttribute, MetadataAttributeRef
243 243  MetadataAttributeDescriptor: MetadataAttribute
244 244  
245 -Each //[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]// takes its semantic (and possibly also its [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]]) from a [[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] in a ConceptScheme. This is represented by the conceptIdentity association to [[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]].
245 +Each //Component// takes its semantic (and possibly also its representation) from a Concept in a ConceptScheme. This is represented by the conceptIdentity association to Concept.
246 246  
247 -The //[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]// may also have a localRepresentation. This allows a concrete class, such as [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]], to specify its [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] which is local to the //Structure// in which it is contained (for [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] this will be DataStructureDefinition), and thus overrides any coreRepresentation specified for the [[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]].
247 +The //Component// may also have a localRepresentation. This allows a concrete class, such as Dimension, to specify its representation which is local to the //Structure// in which it is contained (for Dimension this will be DataStructureDefinition), and thus overrides any coreRepresentation specified for the Concept.
248 248  
249 -The [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] can be enumerated or non-enumerated. The valid content of an enumerated [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] is specified either in an //ItemScheme// which can be one of [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], ValueList or //GeoCodelist//. The valid content of a non-enumerated [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] is specified as one or more Facet(s) (for example, these may specify minimum and maximum values). For any [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] this is achieved by one of more
249 +The Representation can be enumerated or non-enumerated. The valid content of an enumerated representation is specified either in an //ItemScheme// which can be one of Codelist, ValueList or //GeoCodelist//. The valid content of a non-enumerated representation is specified as one or more Facet(s) (for example, these may specify minimum and maximum values). For any Attribute this is achieved by one of more
250 250  
251 -ExtendedFacet(s), which allow the additional [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of XHTML.
251 +ExtendedFacet(s), which allow the additional representation of XHTML.
252 252  
253 -The types of [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] that are valid for specific [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] is expressed in the model as a [[constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] on the association:
253 +The types of representation that are valid for specific components is expressed in the model as a constraint on the association:
254 254  
255 -* The [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]], DataAttribute, [[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]], MetadataAttribute may be enumerated and, if so, use an //EnumeratedList//.
256 -* The [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] and [[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]] may be non-enumerated and, if so, use one or more Facet(s), note that the FacetValueType applicable to the TimeDimension is restricted to those that represent time.
255 +* The Dimension, DataAttribute, Measure, MetadataAttribute may be enumerated and, if so, use an //EnumeratedList//.
256 +* The Dimension and Measure may be non-enumerated and, if so, use one or more Facet(s), note that the FacetValueType applicable to the TimeDimension is restricted to those that represent time.
257 257  * The MetadataAttribute and DataAttribute may be non-enumerated and, if so, use one or more ExtendedFacet(s).
258 258  
259 -The //Structure// may be used by one or more //StructureUsage//(s). An example of this, in terms of concrete classes, is that a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] (link to MetadataStructureDefinition).
259 +The //Structure// may be used by one or more //StructureUsage//(s). An example of this, in terms of concrete classes, is that a Dataflow (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the Metadataflow (link to MetadataStructureDefinition).
260 260  
261 261  ==== 3.6.3.2 Definitions ====
262 262  
... ... @@ -266,17 +266,17 @@
266 266  Inherits from:
267 267  //MaintainableArtefact//
268 268  Sub classes are:
269 -[[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]
270 -[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]]
271 -)))|(% style="width:897px" %)An [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] whose [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] are described by a Structure. In concrete terms (sub-classes) an example would be a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] which is linked to a given structure – in this case the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]].
272 -| |structure|(% style="width:897px" %)An association to a Structure specifying the structure of the [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]].
269 +Dataflow
270 +Metadataflow
271 +)))|(% style="width:897px" %)An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow which is linked to a given structure – in this case the Data Structure Definition.
272 +| |structure|(% style="width:897px" %)An association to a Structure specifying the structure of the artefact.
273 273  |Structure|(((
274 274  Inherits from:
275 275  //MaintainableArtefact//
276 276  Sub classes are:
277 277  DataStructureDefinition MetadataStructureDefinition
278 -)))|(% style="width:897px" %)Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical [[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]], [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], and their organisation in a data or [[metadata structure definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]], defined by a centre institution, usually for the exchange of statistical information with its partners.
279 -| |grouping|(% style="width:897px" %)A composite association to one or more [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] lists.
278 +)))|(% style="width:897px" %)Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical concepts, code lists, and their organisation in a data or metadata structure definition, defined by a centre institution, usually for the exchange of statistical information with its partners.
279 +| |grouping|(% style="width:897px" %)A composite association to one or more component lists.
280 280  |//ComponentList//|(((
281 281  Inherits from:
282 282  //IdentifiableArtefact//
... ... @@ -285,30 +285,30 @@
285 285  GroupDimensionDescriptor
286 286  MeasureDescriptor
287 287  AttributeDescriptor MetadataAttributeDescriptor
288 -)))|(% style="width:897px" %)An abstract definition of a list of [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]]. A concrete example is a [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] Descriptor, which defines the list of [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] in a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]].
289 -| |[[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]]|(% style="width:897px" %)An aggregate association to one or more [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] which make up the list.
290 -|//[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]//|(((
288 +)))|(% style="width:897px" %)An abstract definition of a list of components. A concrete example is a Dimension Descriptor, which defines the list of Dimensions in a Data Structure Definition.
289 +| |components|(% style="width:897px" %)An aggregate association to one or more components which make up the list.
290 +|//Component//|(((
291 291  Inherits from:
292 292  //IdentifiableArtefact//
293 293  Sub classes are:
294 -[[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]]
294 +Measure
295 295  //AttributeComponent
296 296  DimensionComponent//
297 -)))|(% style="width:897px" %)A [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] List and hence a Structure. [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] is refined through its sub-classes.
298 -| |conceptIdentity|(% style="width:897px" %)Association to a (% style="color:#e74c3c" %)Concept(%%) in a [[Concept Scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]] that identifies and defines the semantic of the [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]].
297 +)))|(% style="width:897px" %)A Component is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a Component List and hence a Structure. Component is refined through its sub-classes.
298 +| |conceptIdentity|(% style="width:897px" %)Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component.
299 299  | |localRepresentation|(% style="width:897px" %)(((
300 -Association to the [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of the [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] if this is different from the coreRepresentation of the (% style="color:#e74c3c" %)Concept(%%), which the [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] uses (ConceptUsage).
300 +Association to the Representation of the Component if this is different from the coreRepresentation of the Concept, which the Component uses (ConceptUsage).
301 301  )))
302 -|[[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]]| |(% style="width:897px" %)The allowable value or format for [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] or (% style="color:#e74c3c" %)Concept
303 -| |+enumerated|(% style="width:897px" %)Association to an enumerated list that contains the allowable content for the [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] when reported in a data or [[metadata set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]]. The type of enumerated list that is allowed for any concrete [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] is shown in the (% style="color:#e74c3c" %)constraints(%%) on the association.
304 -| |+nonEnumerated|(% style="width:897px" %)Association to a set of [[Facets>>doc:sdmx:Glossary 2\.1.Facet.WebHome]] that define the allowable format for the content of the [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] when reported in a data or [[metadata set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]].
305 -|[[Facet>>doc:sdmx:Glossary 2\.1.Facet.WebHome]]| |(% style="width:897px" %)Defines the format for the content of the [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] when reported in a data or [[metadata set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]].
306 -| |facetType|(% style="width:897px" %)A specific content type, which is constrained by the [[Facet>>doc:sdmx:Glossary 2\.1.Facet.WebHome]] Type enumeration.
307 -| |facetValueType|(% style="width:897px" %)The format of the value of a [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] when reported in a data or [[metadata set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]]. This is constrained by the [[Facet>>doc:sdmx:Glossary 2\.1.Facet.WebHome]] Value Type enumeration.
308 -| |+itemSchemeFacet|(% style="width:897px" %)Defines the format of the identifiers in an [[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] used by a [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]. Typically, this would define the number of characters (length) of the identifier.
309 -|ExtendedFacet| |(% style="width:897px" %)This has the same function as [[Facet>>doc:sdmx:Glossary 2\.1.Facet.WebHome]] but allows additionally an XHTML [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]]. This is constrained for use with a Metadata [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] and a Data [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]].
302 +|Representation| |(% style="width:897px" %)The allowable value or format for Component or Concept
303 +| |+enumerated|(% style="width:897px" %)Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association.
304 +| |+nonEnumerated|(% style="width:897px" %)Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set.
305 +|Facet| |(% style="width:897px" %)Defines the format for the content of the Component when reported in a data or metadata set.
306 +| |facetType|(% style="width:897px" %)A specific content type, which is constrained by the Facet Type enumeration.
307 +| |facetValueType|(% style="width:897px" %)The format of the value of a Component when reported in a data or metadata set. This is constrained by the Facet Value Type enumeration.
308 +| |+itemSchemeFacet|(% style="width:897px" %)Defines the format of the identifiers in an Item Scheme used by a Component. Typically, this would define the number of characters (length) of the identifier.
309 +|ExtendedFacet| |(% style="width:897px" %)This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute and a Data Attribute.
310 310  
311 -The specification of the content and use of the sub classes to //ComponentList// and //[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]]// can be found in the section in which they are used (DataStructureDefinition and MetadataStructureDefinition). Moreover, the FacetType SentinelValues is explained in the datastructure [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] diagram (see 5.3.2.2), since it only concerns DataStructureDefinitions.
311 +The specification of the content and use of the sub classes to //ComponentList// and //Component// can be found in the section in which they are used (DataStructureDefinition and MetadataStructureDefinition). Moreover, the FacetType SentinelValues is explained in the datastructure representation diagram (see 5.3.2.2), since it only concerns DataStructureDefinitions.
312 312  
313 313  ==== 3.6.3.3 Representation Constructs ====
314 314  
© Semantic R&D Group, 2026