Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 3.4
edited by Helena
on 2025/05/20 12:03
Change comment: There is no comment for this version
To version 12.1
edited by Artur
on 2025/05/27 15:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.SDMX 2\.1 Standards\. Section 2\. Information model\: UML conceptual design.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  == {{id name="_Toc370987"/}}4.1 Introduction ==
6 6  
7 -The structures that are an arrangement of objects into hierarchies or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
7 +The structures that are an arrangement of objects into [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
8 8  
9 9  * Codelist
10 10  * ConceptScheme
... ... @@ -20,6 +20,8 @@
20 20  
21 21  === {{id name="_Toc370990"/}}4.3.1 Class Diagram ===
22 22  
23 +[[image:1747732337979-971.png]]
24 +
23 23  **Figure 15 Class diagram of the Codelist**
24 24  
25 25  === {{id name="_Toc370991"/}}4.3.2 Explanation of the Diagram ===
... ... @@ -26,7 +26,7 @@
26 26  
27 27  ==== 4.3.2.1 Narrative ====
28 28  
29 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
31 +The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
30 30  
31 31  * id
32 32  * uri
... ... @@ -40,31 +40,32 @@
40 40  * final
41 41  * isPartial
42 42  
43 -The Code inherits from //Item// and has the following attributes:
45 +The [[Code>>doc:sdmx:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
44 44  
45 45  * id
46 46  * uri
47 47  * urn
48 48  
49 -Both Codelist and Code have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown).
51 +Both Codelist and [[Code>>doc:sdmx:Glossary.Code.WebHome]] have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown).
50 50  
51 -Through the inheritance the Codelist comprise one or more Codes, and the Code itself can have one or more child Codes in the (inherited) hierarchy association. Note that a child Code can have only one parent Code in this association. A more complex HierachicalCodelist which allow multiple parents and multiple hierarchies is described later.
53 +Through the inheritance the Codelist comprise one or more [[Codes>>doc:sdmx:Glossary.Code.WebHome]], and the [[Code>>doc:sdmx:Glossary.Code.WebHome]] itself can have one or more child [[Codes>>doc:sdmx:Glossary.Code.WebHome]] in the (inherited) [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. Note that a child [[Code>>doc:sdmx:Glossary.Code.WebHome]] can have only one parent [[Code>>doc:sdmx:Glossary.Code.WebHome]] in this association. A more complex HierachicalCodelist which allow multiple parents and multiple [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] is described later.
52 52  
53 -A partial Codelist (where isPartial is set to “true”) is identical to a Codelist and contains the Code and associated names and descriptions, just as in a normal code list. However, its content is a sub set of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
55 +A partial Codelist (where isPartial is set to “true”) is identical to a Codelist and contains the [[Code>>doc:sdmx:Glossary.Code.WebHome]] and associated names and descriptions, just as in a normal [[code list>>doc:sdmx:Glossary.Code list.WebHome]]. However, its content is a sub set of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
54 54  
55 55  ==== 4.3.2.2 Definitions ====
56 56  
57 57  (((
58 -|**Class**|**Feature**|**Description**
59 -|Codelist|(((
60 +(% style="width:905.294px" %)
61 +|(% style="width:132px" %)**Class**|(% style="width:172px" %)**Feature**|(% style="width:598px" %)**Description**
62 +|(% style="width:132px" %)Codelist|(% style="width:172px" %)(((
60 60  Inherits from
61 61  //ItemScheme//
62 -)))|A list from which some statistical concepts (coded concepts) take their values.
63 -|Code|(((
65 +)))|(% style="width:598px" %)A list from which some statistical (% style="color:#e74c3c" %)concepts(%%) (coded (% style="color:#e74c3c" %)concepts(%%)) take their values.
66 +|(% style="width:132px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]]|(% style="width:172px" %)(((
64 64  Inherits from
65 65  //Item//
66 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
67 -| |/hierarchy|Associates the parent and the child codes.
69 +)))|(% style="width:598px" %)A language independent set of letters, numbers or symbols that represent a (% style="color:#e74c3c" %)concept(%%) whose meaning is described in a natural language.
70 +|(% style="width:132px" %) |(% style="width:172px" %)/hierarchy|(% style="width:598px" %)Associates the parent and the child [[codes>>doc:sdmx:Glossary.Code.WebHome]].
68 68  )))
69 69  
70 70  == {{id name="_Toc370992"/}}4.4 Concept Scheme and Concepts ==
... ... @@ -71,11 +71,13 @@
71 71  
72 72  === {{id name="_Toc370993"/}}4.4.1 Class Diagram - Inheritance ===
73 73  
77 +[[image:1747732287949-594.png]]
78 +
74 74  **Figure 16 Class diagram of the Concept Scheme**
75 75  
76 76  === {{id name="_Toc370994"/}}4.4.2 Explanation of the Diagram ===
77 77  
78 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
83 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
79 79  
80 80  * id
81 81  * uri
... ... @@ -90,43 +90,40 @@
90 90  * final
91 91  * isPartial
92 92  
93 -Concept inherits from Item and has the following attributes:
98 +(% style="color:#e74c3c" %)Concept(%%) inherits from Item and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
94 94  
95 95  * id
96 96  * uri
97 97  * urn
98 98  
99 -Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown).
104 +Through the inheritance from //NameableArtefact// both ConceptScheme and (% style="color:#e74c3c" %)Concept(%%) have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown).
100 100  
101 -Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more Concepts, and the Concept itself can have one or more child Concepts in the (inherited) hierarchy association. Note that a child Concept can have only one parent Concept in this association.
106 +Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more (% style="color:#e74c3c" %)Concepts(%%), and the (% style="color:#e74c3c" %)Concept(%%) itself can have one or more child (% style="color:#e74c3c" %)Concepts(%%) in the (inherited) [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. Note that a child (% style="color:#e74c3c" %)Concept(%%) can have only one parent (% style="color:#e74c3c" %)Concept(%%) in this association.
102 102  
103 -A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the Concept and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a sub set of the full ConceptScheme.
108 +A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the (% style="color:#e74c3c" %)Concept(%%) and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a sub set of the full ConceptScheme.
104 104  
105 105  The way this works is described in section 3.5.3.1 on ItemScheme.
106 106  
107 107  === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship ===
108 108  
114 +[[image:1747732242162-856.png]]
109 109  
110 -**Figure 17: Relationship class diagram of the Concept Scheme**
116 +**Figure 17: Relationship class diagram of the [[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]**
111 111  
112 112  === {{id name="_Toc370996"/}}4.4.4 Explanation of the diagram ===
113 113  
114 114  ==== 4.4.4.1 Narrative ====
115 115  
116 -The ConceptScheme can have one or more Concepts. A Concept can have zero or more child Concepts, thus supporting a hierarchy of Concepts. Note that a child Concept can have only one parent Concept in this association. The purpose of the hierarchy is to relate concepts that have a semantic relationship: for example a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent concept, or a CONTACT may have a PRIMARY_CONTACT as a child concept. It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the
122 +The ConceptScheme can have one or more (% style="color:#e74c3c" %)Concepts(%%). A (% style="color:#e74c3c" %)Concept(%%) can have zero or more child (% style="color:#e74c3c" %)Concepts(%%), thus supporting a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] of (% style="color:#e74c3c" %)Concepts(%%). Note that a child (% style="color:#e74c3c" %)Concept(%%) can have only one parent (% style="color:#e74c3c" %)Concept(%%) in this association. The purpose of the [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] is to relate (% style="color:#e74c3c" %)concepts(%%) that have a semantic relationship: for example a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent (% style="color:#e74c3c" %)concept(%%), or a (% style="color:#e74c3c" %)CONTACT(%%) may have a PRIMARY_CONTACT as a child (% style="color:#e74c3c" %)concept(%%). It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the MetadataStructureDefinition.
117 117  
118 -MetadataStructureDefinition.
124 +The (% style="color:#e74c3c" %)Concept(%%) can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the (% style="color:#e74c3c" %)Concept(%%) when used on a structure like a DataStructureDefinition or a MetadataStructureDefinition, unless the specification of the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] is overridden in the relevant structure definition. In a hierarchical ConceptScheme the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] is inherited from the parent (% style="color:#e74c3c" %)Concept(%%) unless overridden at the (% style="color:#e74c3c" %)level(%%) of the child (% style="color:#e74c3c" %)Concept(%%).
119 119  
120 -The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a
126 +Note that the ConceptScheme is used as the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] of the MeasureDimension in a DataStructureDefinition (see 5.3.2). Each (% style="color:#e74c3c" %)Concept(%%) in this ConceptScheme is a specific [[measure>>doc:sdmx:Glossary.Measure.WebHome]], each of which can be given a coreRepresentation. Thus the valid format of the observation for each [[measure>>doc:sdmx:Glossary.Measure.WebHome]] when reported in a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] for the MeasureDimension is specified in the (% style="color:#e74c3c" %)Concept(%%). This allows a different format for each [[measure>>doc:sdmx:Glossary.Measure.WebHome]]. This is covered in more detail in 5.3.
121 121  
122 -MetadataStructureDefinition, unless the specification of the Representation is overridden in the relevant structure definition. In a hierarchical ConceptScheme the Representation is inherited from the parent Concept unless overridden at the level of the child Concept.
128 +The [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] is documented in more detail in the section on the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Base.
123 123  
124 -Note that the ConceptScheme is used as the Representation of the MeasureDimension in a DataStructureDefinition (see 5.3.2). Each Concept in this ConceptScheme is a specific measure, each of which can be given a coreRepresentation. Thus the valid format of the observation for each measure when reported in a data set for the MeasureDimension is specified in the Concept. This allows a different format for each measure. This is covered in more detail in 5.3.
130 +The (% style="color:#e74c3c" %)Concept(%%) may be related to a (% style="color:#e74c3c" %)concept(%%) described in terms of the ISO/IEC 11179 standard. The ISOConceptReference identifies this (% style="color:#e74c3c" %)concept(%%) and [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] in which it is contained.
125 125  
126 -The Representation is documented in more detail in the section on the SDMX Base.
127 -
128 -The Concept may be related to a concept described in terms of the ISO/IEC 11179 standard. The ISOConceptReference identifies this concept and concept scheme in which it is contained.
129 -
130 130  ==== 4.4.4.2 Definitions ====
131 131  
132 132  (((
... ... @@ -136,19 +136,19 @@
136 136  Inherits from
137 137  
138 138  //ItemScheme//
139 -)))|(% style="width:522px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
140 -|(% style="width:195px" %)Concept|(% style="width:210px" %)(((
141 +)))|(% style="width:522px" %)The descriptive information for an arrangement or division of (% style="color:#e74c3c" %)concepts(%%) into groups based on characteristics, which the objects have in common.
142 +|(% style="width:195px" %)(% style="color:#e74c3c" %)Concept|(% style="width:210px" %)(((
141 141  Inherits from
142 142  
143 143  //Item//
144 -)))|(% style="width:522px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
145 -|(% style="width:195px" %) |(% style="width:210px" %)/hierarchy|(% style="width:522px" %)Associates the parent and the child concept.
146 -|(% style="width:195px" %) |(% style="width:210px" %)coreRepresentation|(% style="width:522px" %)Associates a Representation.
147 -|(% style="width:195px" %) |(% style="width:210px" %)+ISOConcept|(% style="width:522px" %)Association to an ISO concept reference.
148 -|(% style="width:195px" %)ISOConceptReference|(% style="width:210px" %) |(% style="width:522px" %)The identity of an ISO concept definition.
149 -|(% style="width:195px" %) |(% style="width:210px" %)conceptAgency|(% style="width:522px" %)The maintenance agency of the concept scheme containing the concept.
150 -|(% style="width:195px" %) |(% style="width:210px" %)conceptSchemeID|(% style="width:522px" %)The identifier of the concept scheme.
151 -|(% style="width:195px" %) |(% style="width:210px" %)conceptID|(% style="width:522px" %)The identifier of the concept.
146 +)))|(% style="width:522px" %)A (% style="color:#e74c3c" %)concept(%%) is a unit of knowledge created by a unique combination of characteristics.
147 +|(% style="width:195px" %) |(% style="width:210px" %)/hierarchy|(% style="width:522px" %)Associates the parent and the child (% style="color:#e74c3c" %)concept(%%).
148 +|(% style="width:195px" %) |(% style="width:210px" %)coreRepresentation|(% style="width:522px" %)Associates a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]].
149 +|(% style="width:195px" %) |(% style="width:210px" %)+ISOConcept|(% style="width:522px" %)Association to an ISO (% style="color:#e74c3c" %)concept(%%) reference.
150 +|(% style="width:195px" %)ISOConceptReference|(% style="width:210px" %) |(% style="width:522px" %)The identity of an ISO (% style="color:#e74c3c" %)concept(%%) definition.
151 +|(% style="width:195px" %) |(% style="width:210px" %)conceptAgency|(% style="width:522px" %)The [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] of the [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] containing the (% style="color:#e74c3c" %)concept(%%).
152 +|(% style="width:195px" %) |(% style="width:210px" %)conceptSchemeID|(% style="width:522px" %)The identifier of the [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]].
153 +|(% style="width:195px" %) |(% style="width:210px" %)conceptID|(% style="width:522px" %)The identifier of the (% style="color:#e74c3c" %)concept(%%).
152 152  )))
153 153  
154 154  == {{id name="_Toc370997"/}}4.5 Category Scheme ==
... ... @@ -155,17 +155,21 @@
155 155  
156 156  === {{id name="_Toc370998"/}}4.5.1 Context ===
157 157  
158 -This package defines the structure that supports the definition of and relationships between categories in a category scheme. It is similar to the package for concept scheme. An example of a category scheme is one which categorises data – sometimes known as a subject matter domain scheme or a data category scheme. Importantly, as will be seen later, the individual nodes in the scheme (the “categories”) can be associated to any set of IdentiableArtefacts in a Categorisation.
160 +This package defines the structure that supports the definition of and relationships between [[categories>>doc:sdmx:Glossary.Category.WebHome]] in a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]. It is similar to the package for [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]. An example of a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] is one which categorises data – sometimes known as a subject matter domain scheme or a data [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]. Importantly, as will be seen later, the individual nodes in the scheme (the “[[categories>>doc:sdmx:Glossary.Category.WebHome]]”) can be associated to any set of IdentiableArtefacts in a Categorisation.
159 159  
160 160  === {{id name="_Toc370999"/}}4.5.2 Class diagram - Inheritance ===
161 161  
162 -====== Figure 18 Inheritance Class diagram of the Category Scheme ======
164 +(% class="wikigeneratedid" id="H" %)
165 +[[image:1747732448450-721.png]]
163 163  
167 +(% class="wikigeneratedid" id="HFigure18InheritanceClassdiagramoftheCategoryScheme" %)
168 +**Figure 18 Inheritance Class diagram of the [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]**
169 +
164 164  === {{id name="_Toc371000"/}}4.5.3 Explanation of the Diagram ===
165 165  
166 166  ==== 4.5.3.1 Narrative ====
167 167  
168 -The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
174 +The [[categories>>doc:sdmx:Glossary.Category.WebHome]] are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
169 169  
170 170  * id
171 171  * uri
... ... @@ -179,51 +179,47 @@
179 179  * final
180 180  * isPartial
181 181  
182 -Category inherits from //Item// and has the following attributes:
188 +[[Category>>doc:sdmx:Glossary.Category.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
183 183  
184 184  * //id//
185 185  * //uri//
186 186  * //urn//
187 187  
188 -Both CategoryScheme and Category have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown on the model).
194 +Both CategoryScheme and [[Category>>doc:sdmx:Glossary.Category.WebHome]] have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown on the model).
189 189  
190 -Through the inheritance the CategoryScheme comprise one or more Categorys, and the Category itself can have one or more child Category in the (inherited) hierarchy association. Note that a child Category can have only one parent Category in this association.
196 +Through the inheritance the CategoryScheme comprise one or more [[Categorys>>doc:sdmx:Glossary.Category.WebHome]], and the [[Category>>doc:sdmx:Glossary.Category.WebHome]] itself can have one or more child [[Category>>doc:sdmx:Glossary.Category.WebHome]] in the (inherited) [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. Note that a child [[Category>>doc:sdmx:Glossary.Category.WebHome]] can have only one parent [[Category>>doc:sdmx:Glossary.Category.WebHome]] in this association.
191 191  
192 -A partial CategoryScheme (where isPartial is set to “true”) is identical to a CategoryScheme and contains the Category and associated names and descriptions, just as in a normal CategoryScheme. However, its content is a sub set of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
198 +A partial CategoryScheme (where isPartial is set to “true”) is identical to a CategoryScheme and contains the [[Category>>doc:sdmx:Glossary.Category.WebHome]] and associated names and descriptions, just as in a normal CategoryScheme. However, its content is a sub set of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
193 193  
194 194  === {{id name="_Toc371001"/}}4.5.4 Class diagram - Relationship ===
195 195  
196 -**Figure 19: Relationship Class diagram of the Category Scheme**
202 +[[image:1747732486733-495.png]]
197 197  
198 -The CategoryScheme can have one or more Categorys. The Category is Identifiable and has identity information. A Category can have zero or more child Categorys, thus supporting a hierarchy of Categorys. Any IdentifiableArtefact can be +categorisedBy a Category. This is achieved by means of a Categorisation. Each
204 +**Figure 19: Relationship Class diagram of the [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]**
199 199  
200 -Categorisation can associate one IdentifiableArtefact with one Category. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same Category. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the Category. From an implementation perspective this is necessary as Categorisation has no affect on the versioning of either the Category or the IdentifiableArtefact.
206 +The CategoryScheme can have one or more [[Categorys>>doc:sdmx:Glossary.Category.WebHome]]. The [[Category>>doc:sdmx:Glossary.Category.WebHome]] is Identifiable and has identity information. A [[Category>>doc:sdmx:Glossary.Category.WebHome]] can have zero or more child [[Categorys>>doc:sdmx:Glossary.Category.WebHome]], thus supporting a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] of [[Categorys>>doc:sdmx:Glossary.Category.WebHome]]. Any IdentifiableArtefact can be +categorisedBy a [[Category>>doc:sdmx:Glossary.Category.WebHome]]. This is achieved by means of a Categorisation. Each Categorisation can associate one IdentifiableArtefact with one [[Category>>doc:sdmx:Glossary.Category.WebHome]]. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same [[Category>>doc:sdmx:Glossary.Category.WebHome]]. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the [[Category>>doc:sdmx:Glossary.Category.WebHome]]. From an implementation perspective this is necessary as Categorisation has no affect on the versioning of either the [[Category>>doc:sdmx:Glossary.Category.WebHome]] or the IdentifiableArtefact.
201 201  
202 202  ==== 4.5.4.1 Definitions ====
203 203  
204 -:
205 -
206 206  (((
207 -|**Class**|**Feature**|**Description**
208 -|CategoryScheme|(((
211 +(% style="width:965.294px" %)
212 +|(% style="width:171px" %)**Class**|(% style="width:213px" %)**Feature**|(% style="width:577px" %)**Description**
213 +|(% style="width:171px" %)CategoryScheme|(% style="width:213px" %)(((
209 209  Inherits from
210 -
211 211  //ItemScheme//
212 -)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
213 -| |/items|Associates the categories.
214 -|Category|(((
216 +)))|(% style="width:577px" %)The descriptive information for an arrangement or division of [[categories>>doc:sdmx:Glossary.Category.WebHome]] into groups based on characteristics, which the objects have in common.
217 +|(% style="width:171px" %) |(% style="width:213px" %)/items|(% style="width:577px" %)Associates the [[categories>>doc:sdmx:Glossary.Category.WebHome]].
218 +|(% style="width:171px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]]|(% style="width:213px" %)(((
215 215  Inherits from
216 -
217 217  //Item//
218 -)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
219 -| |/hierarchy|Associates the parent and the child Category.
220 -|Categorisation|(((
221 +)))|(% style="width:577px" %)An item at any (% style="color:#e74c3c" %)level(%%) within a classification, typically tabulation [[categories>>doc:sdmx:Glossary.Category.WebHome]], sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
222 +|(% style="width:171px" %) |(% style="width:213px" %)/hierarchy|(% style="width:577px" %)Associates the parent and the child [[Category>>doc:sdmx:Glossary.Category.WebHome]].
223 +|(% style="width:171px" %)Categorisation|(% style="width:213px" %)(((
221 221  Inherits from
222 -
223 223  MaintainableArtefact
224 -)))|Associates anIdentifableArtefact with a Category.
225 -| |+categorisedArtefact|Associates the IdentifableArtefact.
226 -| |+categorisedBy|Associates the Category.
226 +)))|(% style="width:577px" %)Associates anIdentifableArtefact with a [[Category>>doc:sdmx:Glossary.Category.WebHome]].
227 +|(% style="width:171px" %) |(% style="width:213px" %)+categorisedArtefact|(% style="width:577px" %)Associates the IdentifableArtefact.
228 +|(% style="width:171px" %) |(% style="width:213px" %)+categorisedBy|(% style="width:577px" %)Associates the [[Category>>doc:sdmx:Glossary.Category.WebHome]].
227 227  )))
228 228  
229 229  == {{id name="_Toc371002"/}}4.6 Organisation Scheme ==
... ... @@ -232,7 +232,8 @@
232 232  
233 233  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_dcd0149.png||height="456" width="580"]]
234 234  
235 -====== Figure 20 The Organisation Scheme class diagram ======
237 +(% class="wikigeneratedid" id="HFigure20TheOrganisationSchemeclassdiagram" %)
238 +**Figure 20 The Organisation Scheme class diagram**
236 236  
237 237  === {{id name="_Toc371004"/}}4.6.2 Explanation of the Diagram ===
238 238  
... ... @@ -242,94 +242,81 @@
242 242  
243 243  The //OrganisationScheme// can be one of four types:
244 244  
245 -1. AgencyScheme – contains Agency which is restricted to a flat list of agencies (i.e. there is no hierarchy). Note that the SDMX system of (Maintenance) Agency can be hierarchic and this is explained in more detail in the separate document “Technical Notes”.
246 -1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e. there is no hierarchy).
247 -1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e. there is no hierarchy).
248 -1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
248 +1. AgencyScheme – contains Agency which is restricted to a flat list of agencies (i.e. there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]). Note that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] system of (Maintenance) Agency can be hierarchic and this is explained in more detail in the separate document “Technical Notes”.
249 +1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e. there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
250 +1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e. there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
251 +1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /[[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association from Organisation.
249 249  
250 -Reference metadata can be attached to the //Organisation //by means of the metadata attachment mechanism. This mechanism is explained in the Reference Metadata section of this document (see section 7). This means that the model does not specify the specific reference metadata that can be attached to a DataProvider, DataConsumer,OrganisationUnit or Agency, except for limited Contact information.
253 +[[Reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] can be attached to the //Organisation //by means of the metadata attachment mechanism. This mechanism is explained in the [[Reference Metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] section of this document (see section 7). This means that the model does not specify the specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] that can be attached to a DataProvider, DataConsumer,OrganisationUnit or Agency, except for limited (% style="color:#e74c3c" %)Contact(%%) information.
251 251  
252 252  A partial //OrganisationScheme// (where isPartial is set to “true”) is identical to a //OrganisationScheme// and contains the Organisation and associated names and descriptions, just as in a normal //OrganisationScheme// However, its content is a sub set of the full //OrganisationScheme//. The way this works is described in section 3.5.3.1 on ItemScheme.
253 253  
254 254  ==== 4.6.2.2 Definitions ====
255 255  
256 -|**Class**|**Feature**|**Description**
257 -|//OrganisationScheme//|(((
259 +(% style="width:845.294px" %)
260 +|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description**
261 +|(% style="width:181px" %)//OrganisationScheme//|(% style="width:217px" %)(((
258 258  Abstract Class Inherits from
259 -
260 260  //ItemScheme//
261 -
262 262  Sub classes are:
263 -
264 264  AgencyScheme
265 -
266 266  DataProviderScheme
267 -
268 268  DataConsumerScheme
269 -
270 270  OrganisationUnitScheme
271 -)))|A maintained collection of Organisations.
272 -| |/items|Association to the Organisations in the scheme.
273 -|//Organisation//|(((
269 +)))|(% style="width:429px" %)A maintained collection of Organisations.
270 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme.
271 +|(% style="width:181px" %)//Organisation//|(% style="width:217px" %)(((
274 274  Inherits from
275 -
276 276  //Item//
277 -
278 278  Sub classes are:
279 -
280 280  Agency
281 -
282 282  DataProvider
283 -
284 284  DataConsumer
285 -
286 286  OrganisationUnit
287 -)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
288 -| |+contact|Association to the Contact information.
289 -| |/hierarchy|Association to child Organisations.
290 -|Contact| |An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
291 -| |name|The designation of the Contact person by a linguistic expression.
292 -| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
293 -| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
294 -| |telephone|The telephone number of the Contact.
295 -| |fax|The fax number of the Contact.
296 -| |email|The Internet e-mail address of the Contact.
297 -| |X400|The X400 address of the Contact.
298 -| |uri|The URL address of the Contact.
299 -|AgencyScheme| |A maintained collection of Maintenace Agencies.
300 -| |/items|Association to the Maintenance Agency in the scheme.
301 -|DataProviderScheme| |A maintained collection of Data Providers.
302 -| |/items|Association to the Data Providers in the scheme.
303 -|DataConsumerScheme| |A maintained collection of Data Consumers.
304 -| |/items|Association to the Data Consumers in the scheme.
305 -|OrganisationUnitScheme| |A maintained collection of Organisation Units.
306 -| |/items|Association to the Organisation Units in the scheme.
307 -|Agency|(((
279 +)))|(% style="width:429px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
280 +|(% style="width:181px" %) |(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the (% style="color:#e74c3c" %)Contact(%%) information.
281 +|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations.
282 +|(% style="width:181px" %)(% style="color:#e74c3c" %)Contact|(% style="width:217px" %) |(% style="width:429px" %)An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
283 +|(% style="width:181px" %) |(% style="width:217px" %)name|(% style="width:429px" %)The designation of the (% style="color:#e74c3c" %)Contact(%%) person by a linguistic expression.
284 +|(% style="width:181px" %) |(% style="width:217px" %)organisationUnit|(% style="width:429px" %)The designation of the organisational structure by a linguistic expression, within which (% style="color:#e74c3c" %)Contact(%%) person works.
285 +|(% style="width:181px" %) |(% style="width:217px" %)responsibility|(% style="width:429px" %)The function of the (% style="color:#e74c3c" %)contact(%%) person with respect to the organisation role for which this person is the (% style="color:#e74c3c" %)Contact(%%).
286 +|(% style="width:181px" %) |(% style="width:217px" %)telephone|(% style="width:429px" %)The [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] of the (% style="color:#e74c3c" %)Contact(%%).
287 +|(% style="width:181px" %) |(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the (% style="color:#e74c3c" %)Contact(%%).
288 +|(% style="width:181px" %) |(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the (% style="color:#e74c3c" %)Contact(%%).
289 +|(% style="width:181px" %) |(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the (% style="color:#e74c3c" %)Contact(%%).
290 +|(% style="width:181px" %) |(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the (% style="color:#e74c3c" %)Contact(%%).
291 +|(% style="width:181px" %)AgencyScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Maintenace Agencies.
292 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] in the scheme.
293 +|(% style="width:181px" %)DataProviderScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]].
294 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] in the scheme.
295 +|(% style="width:181px" %)DataConsumerScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]].
296 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]] in the scheme.
297 +|(% style="width:181px" %)OrganisationUnitScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Organisation Units.
298 +|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme.
299 +|(% style="width:181px" %)Agency|(% style="width:217px" %)(((
308 308  Inherits from
309 -
310 310  //Organisation//
311 -)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
312 -|DataProvider|(((
302 +)))|(% style="width:429px" %)Responsible agency for maintaining [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] such as statistical classifications, glossaries, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] such as Data and [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], (% style="color:#e74c3c" %)Concepts(%%) and [[Code>>doc:sdmx:Glossary.Code.WebHome]] lists.
303 +|(% style="width:181px" %)DataProvider|(% style="width:217px" %)(((
313 313  Inherits from
314 -
315 315  //Organisation//
316 -)))|An organisation that produces data or reference metadata.
317 -|DataConsumer|(((
306 +)))|(% style="width:429px" %)An organisation that produces data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
307 +|(% style="width:181px" %)DataConsumer|(% style="width:217px" %)(((
318 318  Inherits from
319 -
320 320  //Organisation//
321 -)))|An organisation using data as input for further processing.
322 -|OrganisationUnit|(((
310 +)))|(% style="width:429px" %)An organisation using data as input for further processing.
311 +|(% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)(((
323 323  Inherits from
313 +//Organisation//
314 +)))|(% style="width:429px" %)A designation in the organisational structure.
315 +|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisation Units
324 324  
325 -//Organisation //
326 -)))|A designation in the organisational structure.
327 -| |/hierarchy|Association to child Organisation Units
328 -
329 329  == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy ==
330 330  
331 331  === {{id name="_Toc371006"/}}4.7.1 Class Diagram ===
332 332  
321 +[[image:1747732548003-370.png]]
322 +
333 333  **Figure 21: Class diagram of the Reporting Taxonomy**
334 334  
335 335  === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram ===
... ... @@ -338,14 +338,13 @@
338 338  
339 339  In some data reporting environments, and in particular those in primary reporting, a report may comprise a variety of heterogeneous data, each described by a different Structure. Equally, a specific disseminated or published report may also comprise a variety of heterogeneous data. The definition of the set of linked sub reports is supported by the ReportingTaxonomy.
340 340  
341 -The ReportingTaxonomy is a specialised form of ItemScheme. Each ReportingCategory of the ReportingTaxonomy can link to one or more //StructureUsage// which itself can be one of DataflowDefinition, or MetadataflowDefinition, and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each Category that is linked in this way will be linked to the same class (e.g. all Category in the scheme will link to a DataflowDefinition). Note that a ReportingCategory can have child ReportingCategory and in this way it is possible to define a hierarchical ReportingTaxonomy. It is possible in this taxonomy that some ReportingCategory are defined just to give a reporting structure. For instance:
331 +The ReportingTaxonomy is a specialised form of ItemScheme. Each ReportingCategory of the ReportingTaxonomy can link to one or more //StructureUsage// which itself can be one of DataflowDefinition, or MetadataflowDefinition, and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each [[Category>>doc:sdmx:Glossary.Category.WebHome]] that is linked in this way will be linked to the same class (e.g. all [[Category>>doc:sdmx:Glossary.Category.WebHome]] in the scheme will link to a DataflowDefinition). Note that a ReportingCategory can have child ReportingCategory and in this way it is possible to define a hierarchical ReportingTaxonomy. It is possible in this taxonomy that some ReportingCategory are defined just to give a reporting structure. For instance:
342 342  
343 343  Section 1
344 344  
345 -~1. linked to DatafowDefinition_1
335 +1. linked to DatafowDefinition_1
336 +1. linked to DatafowDefinition_2
346 346  
347 -2 linked to DatafowDefinition_2
348 -
349 349  Section 2
350 350  
351 351  1. linked toDatafowDefinition_3
... ... @@ -357,22 +357,19 @@
357 357  
358 358  ==== 4.7.2.2 Definitions ====
359 359  
360 -|**Class**|**Feature**|**Description**
349 +(% style="width:1033.29px" %)
350 +|**Class**|**Feature**|(% style="width:687px" %)**Description**
361 361  |ReportingTaxonomy|(((
362 362  Inherits from
363 -
364 -//ItemScheme //
365 -)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow Definition or Metdataflow Definition.
366 -| |items|Associates the Reporting Category
353 +//ItemScheme//
354 +)))|(% style="width:687px" %)A scheme which defines the composition structure of a data report where each [[component>>doc:sdmx:Glossary.Component.WebHome]] can be described by an independent [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition or Metdataflow Definition.
355 +| |items|(% style="width:687px" %)Associates the Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]]
367 367  |ReportingCategory|(((
368 368  Inherits from
369 -
370 370  //Item//
371 -)))|A component that gives structure to the report and links to data and metadata.
372 -| |hierarchy|Associates child Reporting Category.
373 -| |+flow|Association to the data and metadata flows that link to metadata about the provisioning and related data and metadata sets, and the structures that define them.
374 -| |+structure|(((
375 -Association to the Data Structure Definition and Metadata Structure
376 -
377 -Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
359 +)))|(% style="width:687px" %)A [[component>>doc:sdmx:Glossary.Component.WebHome]] that gives structure to the report and links to data and metadata.
360 +| |hierarchy|(% style="width:687px" %)Associates child Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]].
361 +| |+flow|(% style="width:687px" %)Association to the data and [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]] that link to metadata about the provisioning and related data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], and the structures that define them.
362 +| |+structure|(% style="width:687px" %)(((
363 +Association to the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which define the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] describing the data and metadata that are contained at this part of the report.
378 378  )))
1747732242162-856.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +21.8 KB
Content
1747732287949-594.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +42.4 KB
Content
1747732337979-971.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +39.3 KB
Content
1747732448450-721.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +34.0 KB
Content
1747732486733-495.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +18.6 KB
Content
1747732548003-370.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +48.9 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +5