Changes for page 3 SDMX Base Package

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

From version 40.5
edited by Helena K.
on 2026/06/08 16:10
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,9 +206,9 @@
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  
© Semantic R&D Group, 2026