Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 7.1
edited by Helena
on 2025/05/20 00:29
Change comment: There is no comment for this version
To version 10.1
edited by Helena
on 2025/05/20 00:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -113,6 +113,8 @@
113 113  
114 114  === {{id name="_Toc370976"/}}3.4.1 Class Diagram ===
115 115  
116 +[[image:1747690333052-506.png]]
117 +
116 116  **Figure 11: Class Diagram of Basic Data Types**
117 117  
118 118  === {{id name="_Toc370977"/}}3.4.2 Explanation of the Diagram ===
... ... @@ -162,9 +162,9 @@
162 162  (% class="wikigeneratedid" id="HFigure12TheItemSchemePattern" %)
163 163  **Figure 12 The Item Scheme Pattern**
164 164  
165 -===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram =====
167 +=== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram ===
166 166  
167 -**3.5.3.1 Narrative**
169 +==== 3.5.3.1 Narrative ====
168 168  
169 169  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 inherits 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 CategoryScheme. The associated Category are //Items//.
170 170  
... ... @@ -178,10 +178,8 @@
178 178  
179 179  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.
180 180  
181 -//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
183 +//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 agency as the //ItemScheme//).
182 182  
183 -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 agency as the //ItemScheme//).
184 -
185 185  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//.
186 186  
187 187  ==== 3.5.3.2 Definitions ====
1747690333052-506.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +67.4 KB
Content