Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Helena on 2025/09/10 11:19
From version 3.1
edited by Helena
on 2025/06/07 00:56
Change comment: There is no comment for this version
To version 5.2
edited by Helena
on 2025/06/08 14:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Annotation|Artefact|Attribute|Category|Category scheme|Code|Code list|Component|Concept scheme|Contact phone number|Data consumer|Data provider|Data structure definition|Dataflow|Hierarchy|Maintenance agency|Metadata set|Metadata structure definition|Metadataflow|Reference metadata|Representation|Statistical data and metadata exchange|Structural metadata|Validation and transformation language|isExternalReference
Content
... ... @@ -1,76 +1,70 @@
1 -=== 4.1 Introduction ===
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 -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:
5 +== 4.1 Introduction ==
4 4  
5 -Codelist
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:
6 6  
9 +Codelist
7 7  ConceptScheme
8 -
9 9  CategoryScheme
10 -
11 11  AgencyScheme, DataProviderScheme, MetadataProviderScheme,
12 -
13 13  DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
14 -
15 15  ReportingTaxonomy
16 -
17 17  TransformationScheme
18 -
19 19  RulesetScheme
20 -
21 21  UserDefinedOperatorScheme
22 -
23 23  NamePersonalisationScheme
24 -
25 25  CustomTypeScheme
26 -
27 27  VtlMappingScheme
28 28  
29 -Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
22 +Note that the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
30 30  
31 -=== 4.2 Inheritance View ===
24 +== 4.2 Inheritance View ==
32 32  
33 33  The inheritance and relationship views are shown together in each of the diagrams in the specific sections below.
34 34  
35 -=== 4.3 Codelist ===
28 +== 4.3 Codelist ==
36 36  
37 -==== 4.3.1 Class Diagram ====
30 +=== 4.3.1 Class Diagram ===
38 38  
39 39  [[image:1749246291075-895.jpeg]]
40 40  
41 41  **Figure 16: Class diagram of the Codelist**
42 42  
43 -==== 4.3.2 Explanation of the Diagram ====
36 +=== 4.3.2 Explanation of the Diagram ===
44 44  
45 -===== 4.3.2.1 Narrative =====
38 +==== 4.3.2.1 Narrative ====
46 46  
47 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
40 +The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]: id uri urn (% style="color:#e74c3c" %)version(%%) validFrom validTo [[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]] serviceURL structureURL isPartial
48 48  
49 -The Code inherits from //Item// and has the following attributes:
42 +The [[Code>>doc:sdmx:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
50 50  
51 -id uri urn
44 +id
45 +uri
46 +urn
52 52  
53 -Both Codelist and Code have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown).
48 +Both Codelist and [[Code>>doc:sdmx:Glossary.Code.WebHome]] have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown).
54 54  
55 -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 Hierarhcy, which allows multiple parents is described later.
50 +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 Hierarhcy, which allows multiple parents is described later.
56 56  
57 -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 Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
52 +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 Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
58 58  
59 -===== 4.3.2.2 Definitions =====
54 +==== 4.3.2.2 Definitions ====
60 60  
61 -|**Class**|**Feature**|**Description**
56 +(% style="width:912.835px" %)
57 +|**Class**|**Feature**|(% style="width:656px" %)**Description**
62 62  |Codelist|(((
63 63  Inherits from
64 -
65 65  //ItemScheme//
66 -)))|A list from which some statistical concepts (coded concepts) take their values.
67 -|Code|(((
61 +)))|(% style="width:656px" %)A list from which some statistical (% style="color:#e74c3c" %)concepts(%%) (coded (% style="color:#e74c3c" %)concepts(%%)) take their values.
62 +|[[Code>>doc:sdmx:Glossary.Code.WebHome]]|(((
68 68  Inherits from
69 -
70 70  Item
71 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
72 -| |hierarchy|Associates the parent and the child codes.
73 -| |extends|Associates a Codelist with any Codelists that it may extend.
65 +)))|(% style="width:656px" %)A language independent set of letters, numbers or symbols that represent a (% style="color:#e74c3c" %)concept(%%) whose meaning is described in a natural language.
66 +| |hierarchy|(% style="width:656px" %)Associates the parent and the child [[codes>>doc:sdmx:Glossary.Code.WebHome]].
67 +| |extends|(% style="width:656px" %)Associates a Codelist with any Codelists that it may extend.
74 74  
75 75  ==== 4.3.3 Class Diagram – Codelist Extension ====
76 76  
... ... @@ -78,33 +78,31 @@
78 78  
79 79  **Figure 17: Class diagram for Codelist Extension**
80 80  
81 -===== 4.3.3.1 Narrative =====
75 +==== 4.3.3.1 Narrative ====
82 82  
83 -A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending[[^^~[1~]^^>>path:#_ftn1]] Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.
77 +A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of [[Codes>>doc:sdmx:Glossary.Code.WebHome]]. Besides that, the prefix property is used to ensure uniqueness of inherited [[Codes>>doc:sdmx:Glossary.Code.WebHome]] in the extending[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]](%%) Codelist in case conflicting [[Codes>>doc:sdmx:Glossary.Code.WebHome]] must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of [[Codes>>doc:sdmx:Glossary.Code.WebHome]] from the extended Codelists.
84 84  
85 -The code selection classes may have MemberValues in order to specify the subset of the Codes that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a Code, including its children Codes (via the cascadeValues property), or even include instances of the wildcard character ‘%’ in order to point to a set of Codes with common parts in their identifiers.
79 +The [[code>>doc:sdmx:Glossary.Code.WebHome]] selection classes may have MemberValues in order to specify the subset of the [[Codes>>doc:sdmx:Glossary.Code.WebHome]] that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a [[Code>>doc:sdmx:Glossary.Code.WebHome]], including its children [[Codes>>doc:sdmx:Glossary.Code.WebHome]] (via the cascadeValues property), or even include instances of the wildcard character ‘%’ in order to point to a set of [[Codes>>doc:sdmx:Glossary.Code.WebHome]] with common parts in their identifiers.
86 86  
87 -**4.3.3.2 Definitions**
81 +==== 4.3.3.2 Definitions ====
88 88  
89 -|**Class**|**Feature**|**Description**
90 -|CodelistExtension| |The association between Codelists that may extend other Codelists.
91 -| |prefix|A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
92 -| |sequence|(((
93 -The order that will be used when extending a
94 -
95 -Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
83 +(% style="width:970.835px" %)
84 +|**Class**|**Feature**|(% style="width:655px" %)**Description**
85 +|CodelistExtension| |(% style="width:655px" %)The association between Codelists that may extend other Codelists.
86 +| |prefix|(% style="width:655px" %)A prefix to be used for a Codelist used in a extension, in order to avoid [[Code>>doc:sdmx:Glossary.Code.WebHome]] Conflicts.
87 +| |sequence|(% style="width:655px" %)(((
88 +The order that will be used when extending a Codelist, for resolving [[Code>>doc:sdmx:Glossary.Code.WebHome]] conflicts. The latest Codelist used overrides any previous Codelist.
96 96  )))
97 -|InclusiveCodeSelection| |The subset of Codes to be included when extending a Codelist.
98 -|ExclusiveCodeSelection| |The subset of Codes to be excluded when extending a Codelist.
90 +|InclusiveCodeSelection| |(% style="width:655px" %)The subset of [[Codes>>doc:sdmx:Glossary.Code.WebHome]] to be included when extending a Codelist.
91 +|ExclusiveCodeSelection| |(% style="width:655px" %)The subset of [[Codes>>doc:sdmx:Glossary.Code.WebHome]] to be excluded when extending a Codelist.
99 99  |MemberValue|(((
100 100  Inherits from:
101 -
102 102  //SelectionValue//
103 -)))|A collection of values based on Codes and their children.
104 -| |cascadeValues|A property to indicate if the child Codes of the selected Code shall be included in the selection. It is also possible to include children and exclude the Code by using the 'excluderoot' value.
105 -| |value|The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
95 +)))|(% style="width:655px" %)A collection of values based on [[Codes>>doc:sdmx:Glossary.Code.WebHome]] and their children.
96 +| |cascadeValues|(% style="width:655px" %)A property to indicate if the child [[Codes>>doc:sdmx:Glossary.Code.WebHome]] of the selected [[Code>>doc:sdmx:Glossary.Code.WebHome]] shall be included in the selection. It is also possible to include children and exclude the [[Code>>doc:sdmx:Glossary.Code.WebHome]] by using the 'excluderoot' value.
97 +| |value|(% style="width:655px" %)The value of the [[Code>>doc:sdmx:Glossary.Code.WebHome]] to include in the selection. It may include the ‘%’ character as a wildcard.
106 106  
107 -==== 4.3.4 Class Diagram – Geospatial Codelist ====
99 +=== 4.3.4 Class Diagram – Geospatial Codelist ===
108 108  
109 109  The geospatial support is implemented via an extension of the normal Codelist. This is illustrated in the following diagrams.
110 110  
... ... @@ -116,339 +116,320 @@
116 116  
117 117  **Figure 19: Class diagram for Geospatial Codelist**
118 118  
119 -===== 4.3.4.1 Narrative =====
111 +==== 4.3.4.1 Narrative ====
120 120  
121 -A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special Codes, i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property:
113 +A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special [[Codes>>doc:sdmx:Glossary.Code.WebHome]], i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property:
122 122  
123 123  GeographicCodelist
124 124  
125 125  GeoGridCodelist
126 126  
127 -The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code that follows a pattern to represent a geo feature set.
119 +The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the [[Code>>doc:sdmx:Glossary.Code.WebHome]] that follows a pattern to represent a geo feature set.
128 128  
129 129  The latter, i.e., GeoGridCodelist, comprises a set of GridCodes, which are related to the gridDefinition specified in the GeoGridCodelist.
130 130  
131 -===== 4.3.4.2 Definitions =====
123 +==== 4.3.4.2 Definitions ====
132 132  
133 -|**Class**|**Feature**|**Description**
125 +(% style="width:960.835px" %)
126 +|**Class**|**Feature**|(% style="width:559px" %)**Description**
134 134  |//GeoCodelist//|(((
135 135  Abstract Class Sub Classes:
136 -
137 137  GeographicCodelist
138 -
139 139  GeoGridCodelist
140 -)))|The abstract class that represents a special type of Codelist, which includes geospatial information.
141 -| |geoType|The type of Geo Codelist that the Codelist will become.
131 +)))|(% style="width:559px" %)The abstract class that represents a special type of Codelist, which includes geospatial information.
132 +| |geoType|(% style="width:559px" %)The type of Geo Codelist that the Codelist will become.
142 142  |//GeoRefCode//|(((
143 143  Abstract Class
144 -
145 145  Sub Classes:
146 -
147 147  GeoFeatureSetCode
148 -
149 149  GeoGridCode
150 -)))|The abstract class that represents a special type of Code, which includes geospatial information.
151 -|GeographicCodelist| |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
152 -|GeoGridCodelist| |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
153 -| |gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
154 -|GeoFeatureSetCode| |A Code that has a geo feature set.
155 -| |value|The geo feature set of the Code, which represents a set of points defining a feature in a format defined a predefined pattern (see section 6).
156 -|GeoGridCode| |A Code that represents a Geo Grid Cell belonging in a specific grid definition.
157 -| |geoCell|The value used to assign the Code to one cell in the grid.
138 +)))|(% style="width:559px" %)The abstract class that represents a special type of [[Code>>doc:sdmx:Glossary.Code.WebHome]], which includes geospatial information.
139 +|GeographicCodelist| |(% style="width:559px" %)A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
140 +|GeoGridCodelist| |(% style="width:559px" %)A [[code list>>doc:sdmx:Glossary.Code list.WebHome]] that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
141 +| |gridDefinition|(% style="width:559px" %)Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
142 +|GeoFeatureSetCode| |(% style="width:559px" %)A [[Code>>doc:sdmx:Glossary.Code.WebHome]] that has a geo feature set.
143 +| |value|(% style="width:559px" %)The geo feature set of the [[Code>>doc:sdmx:Glossary.Code.WebHome]], which represents a set of points defining a feature in a format defined a predefined pattern (see section 6).
144 +|GeoGridCode| |(% style="width:559px" %)A [[Code>>doc:sdmx:Glossary.Code.WebHome]] that represents a Geo Grid Cell belonging in a specific grid definition.
145 +| |geoCell|(% style="width:559px" %)The value used to assign the [[Code>>doc:sdmx:Glossary.Code.WebHome]] to one cell in the grid.
158 158  
159 -=== 4.4 ValueList ===
147 +== 4.4 ValueList ==
160 160  
161 -==== 4.4.1 Class Diagram ====
149 +=== 4.4.1 Class Diagram ===
162 162  
163 163  [[image:1749246291179-291.jpeg]]
164 164  
165 165  **Figure 20: Class diagram of the ValueList**
166 166  
167 -==== 4.4.2 Explanation of the Diagram ====
155 +=== 4.4.2 Explanation of the Diagram ===
168 168  
169 -===== 4.4.2.1 Narrative =====
157 +==== 4.4.2.1 Narrative ====
170 170  
171 -A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
159 +A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
172 172  
173 -id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
161 +id// //uri// //urn// //(% style="color:#e74c3c" %)version(%%)// //validFrom// //validTo// //[[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]] registryURL structureURL repositoryURL
174 174  
175 -ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
163 +ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed (% style="color:#e74c3c" %)constraints(%%), to the former.
176 176  
177 -Through the inheritance from //NameableArtefact// the ValueList has 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). Similarly, the ValueItem, inherits the association to InternationalString and to the Annotation from the //EnumeratedItem//.
165 +Through the inheritance from //NameableArtefact// the ValueList has 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). Similarly, the ValueItem, inherits the association to InternationalString and to the [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] from the //EnumeratedItem//.
178 178  
179 179  The ValueList can have one or more ValueItems.
180 180  
181 -===== 4.4.2.2 Definitions =====
169 +==== 4.4.2.2 Definitions ====
182 182  
183 -|**Class**|**Feature**|**Description**
184 -|ValueList|(((
171 +(% style="width:929.835px" %)
172 +|**Class**|(% style="width:175px" %)**Feature**|(% style="width:632px" %)**Description**
173 +|ValueList|(% style="width:175px" %)(((
185 185  Inherits from
186 -
187 187  //EnumeratedList//
188 -)))|A list from which some statistical concepts (enumerated concepts) take their values.
189 -|ValueItem|(((
176 +)))|(% style="width:632px" %)A list from which some statistical (% style="color:#e74c3c" %)concepts(%%) (enumerated (% style="color:#e74c3c" %)concepts(%%)) take their values.
177 +|ValueItem|(% style="width:175px" %)(((
190 190  Inherits from
191 -
192 192  //EnumeratedItem//
193 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
180 +)))|(% style="width:632px" %)A language independent set of letters, numbers or symbols that represent a (% style="color:#e74c3c" %)concept(%%) whose meaning is described in a natural language.
194 194  
195 -=== 4.5 Concept Scheme and Concepts ===
182 +== 4.5 Concept Scheme and Concepts ==
196 196  
197 -==== 4.5.1 Class Diagram - Inheritance ====
184 +=== 4.5.1 Class Diagram - Inheritance ===
198 198  
199 199  [[image:1749246291184-799.jpeg]]
200 200  
201 -**Figure 21 Class diagram of the Concept Scheme**
188 +**Figure 21 Class diagram of the [[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]**
202 202  
203 -==== 4.5.2 Explanation of the Diagram ====
190 +=== 4.5.2 Explanation of the Diagram ===
204 204  
205 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits from Item and has the following attributes:
192 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]: id uri urn (% style="color:#e74c3c" %)version(%%) validFrom validTo [[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]] registryURL structureURL repositoryURL isPartial (% style="color:#e74c3c" %)Concept(%%) inherits from Item and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
206 206  
207 -id uri urn
194 +id
195 +uri
196 +urn
208 208  
209 -Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multilingual description, and an association to Annotation to support notes (not shown).
198 +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 multilingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown).
210 210  
211 -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.
200 +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.
212 212  
213 -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 subset of the full ConceptScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
202 +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 subset of the full ConceptScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
214 214  
215 -==== 4.5.3     Class Diagram Relationship ====
204 +=== 4.5.3 Class Diagram Relationship ===
216 216  
217 217  [[image:1749246291189-654.jpeg]]
218 218  
219 219  **Figure 22: Relationship class diagram of the Concept Scheme**
220 220  
221 -==== 4.5.4 Explanation of the diagram ====
210 +=== 4.5.4 Explanation of the diagram ===
222 222  
223 -===== 4.5.4.1 Narrative =====
212 +==== 4.5.4.1 Narrative ====
224 224  
225 -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 MetadataStructureDefinition.
214 +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.
226 226  
227 -The Concept can be associated with a coreRepresentation. The coreRepresentation is the specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a 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.
216 +The (% style="color:#e74c3c" %)Concept(%%) can be associated with a coreRepresentation. The coreRepresentation is the 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(%%).
228 228  
229 -The Representation is documented in more detail in the section on the SDMX Base.
218 +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.
230 230  
231 -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.
220 +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.
232 232  
233 -===== 4.5.4.2 Definitions =====
222 +==== 4.5.4.2 Definitions ====
234 234  
235 -|**Class**|**Feature**|**Description**
236 -|(((
224 +(% style="width:912.835px" %)
225 +|(% style="width:170px" %)**Class**|(% style="width:184px" %)**Feature**|(% style="width:548px" %)**Description**
226 +|(% style="width:170px" %)(((
237 237  ConceptScheme
238 -
239 -
240 -)))|(((
228 +)))|(% style="width:184px" %)(((
241 241  Inherits from
242 -
243 243  //ItemScheme//
244 -)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
245 -|Concept|(((
231 +)))|(% style="width:548px" %)The descriptive information for an arrangement or division of (% style="color:#e74c3c" %)concepts(%%) into groups based on characteristics, which the objects have in common.
232 +|(% style="width:170px" %)(% style="color:#e74c3c" %)Concept|(% style="width:184px" %)(((
246 246  Inherits from
247 -
248 248  //Item//
249 -)))|A concept is a unit of knowledge created by a unique combination of characteristics.
250 -| |/hierarchy|Associates the parent and the child concept.
251 -| |coreRepresentation|Associates a Representation.
252 -| |+ISOConcept|Association to an ISO concept reference.
253 -|ISOConceptReference| |The identity of an ISO concept definition.
254 -| |conceptAgency|The maintenance agency of the concept scheme containing the concept.
255 -| |conceptSchemeID|The identifier of the concept scheme.
256 -| |conceptID|The identifier of the concept.
235 +)))|(% style="width:548px" %)A (% style="color:#e74c3c" %)concept(%%) is a unit of knowledge created by a unique combination of characteristics.
236 +|(% style="width:170px" %) |(% style="width:184px" %)/hierarchy|(% style="width:548px" %)Associates the parent and the child (% style="color:#e74c3c" %)concept(%%).
237 +|(% style="width:170px" %) |(% style="width:184px" %)coreRepresentation|(% style="width:548px" %)Associates a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]].
238 +|(% style="width:170px" %) |(% style="width:184px" %)+ISOConcept|(% style="width:548px" %)Association to an ISO (% style="color:#e74c3c" %)concept(%%) reference.
239 +|(% style="width:170px" %)ISOConceptReference|(% style="width:184px" %) |(% style="width:548px" %)The identity of an ISO (% style="color:#e74c3c" %)concept(%%) definition.
240 +|(% style="width:170px" %) |(% style="width:184px" %)conceptAgency|(% style="width:548px" %)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(%%).
241 +|(% style="width:170px" %) |(% style="width:184px" %)conceptSchemeID|(% style="width:548px" %)The identifier of the [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]].
242 +|(% style="width:170px" %) |(% style="width:184px" %)conceptID|(% style="width:548px" %)The identifier of the (% style="color:#e74c3c" %)concept(%%).
257 257  
258 -=== 4.6 Category Scheme ===
244 +== 4.6 Category Scheme ==
259 259  
260 -==== 4.6.1 Context ====
246 +=== 4.6.1 Context ===
261 261  
262 -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.
248 +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.
263 263  
264 -==== 4.6.2 Class diagram Inheritance ====
250 +=== 4.6.2 Class diagram Inheritance ===
265 265  
266 266  [[image:1749246291193-743.jpeg]]
267 267  
268 268  **Figure 23 Inheritance Class diagram of the Category Scheme**
269 269  
270 -===== 4.6.3    Explanation of the Diagram =====
256 +=== 4.6.3 Explanation of the Diagram ===
271 271  
272 -====== 4.6.3.1 Narrative ======
258 +==== 4.6.3.1 Narrative ====
273 273  
274 -The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
260 +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]]:
275 275  
276 -id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
262 +id
263 +uri
264 +urn
265 +version
266 +validFrom
267 +validTo
268 +[[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]]
269 +structureURL
270 +serviceURL
271 +isPartial
277 277  
278 -Category inherits from //Item// and has the following attributes:
273 +[[Category>>doc:sdmx:Glossary.Category.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
279 279  
280 -id uri urn
275 +id
276 +uri
277 +urn
281 281  
282 -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).
279 +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).
283 283  
284 -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.
281 +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.
285 285  
286 -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 subset of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
283 +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 subset of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
287 287  
288 -===== 4.6.4     Class diagram Relationship =====
285 +=== 4.6.4 Class diagram Relationship ===
289 289  
290 290  [[image:1749246291197-631.jpeg]]
291 291  
292 -**Figure 24: Relationship Class diagram of the Category Scheme**
289 +**Figure 24: Relationship Class diagram of the [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]**
293 293  
294 -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 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 effect on the versioning of either the CategoryScheme or the IdentifiableArtefact.
291 +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 effect on the versioning of either the CategoryScheme or the IdentifiableArtefact.
295 295  
296 -====== 4.6.4.1 Definitions ======
293 +==== 4.6.4.1 Definitions ====
297 297  
298 -|**Class**|**Feature**|**Description**
295 +(% style="width:935.835px" %)
296 +|**Class**|**Feature**|(% style="width:601px" %)**Description**
299 299  |CategoryScheme|(((
300 300  Inherits from
301 -
302 302  //ItemScheme//
303 -)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
304 -| |/items|Associates the categories.
305 -|Category|(((
300 +)))|(% style="width:601px" %)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.
301 +| |/items|(% style="width:601px" %)Associates the [[categories>>doc:sdmx:Glossary.Category.WebHome]].
302 +|[[Category>>doc:sdmx:Glossary.Category.WebHome]]|(((
306 306  Inherits from
307 -
308 308  //Item//
309 -)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
310 -| |/hierarchy|Associates the parent and the child Category.
305 +)))|(% style="width:601px" %)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.
306 +| |/hierarchy|(% style="width:601px" %)Associates the parent and the child [[Category>>doc:sdmx:Glossary.Category.WebHome]].
311 311  |Categorisation|(((
312 312  Inherits from
313 -
314 314  //MaintainableArtefact//
315 -)))|Associates an Identifable Artefact with a Category.
316 -| |+categorisedArtefact|Associates the Identifable Artefact.
317 -| |+categorisedBy|Associates the Category.
310 +)))|(% style="width:601px" %)Associates an Identifable [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]] with a [[Category>>doc:sdmx:Glossary.Category.WebHome]].
311 +| |+categorisedArtefact|(% style="width:601px" %)Associates the Identifable [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]].
312 +| |+categorisedBy|(% style="width:601px" %)Associates the [[Category>>doc:sdmx:Glossary.Category.WebHome]].
318 318  
319 -=== 4.7 Organisation Scheme ===
314 +== 4.7 Organisation Scheme ==
320 320  
321 -==== Class Diagram ====
316 +=== 4.7.1 Class Diagram ===
322 322  
323 323  [[image:1749246291201-410.jpeg]]
324 324  
325 325  **Figure 25 The Organisation Scheme class diagram**
326 326  
327 -===== 4.7.2    Explanation of the Diagram =====
322 +=== 4.7.2 Explanation of the Diagram ===
328 328  
329 -====== 4.7.2.1 Narrative ======
324 +==== 4.7.2.1 Narrative ====
330 330  
331 331  The //OrganisationScheme// is abstract. It contains //Organisation// which is also abstract. The //Organisation// can have child //Organisation//.
332 332  
333 333  The //OrganisationScheme// can be one of five types:
334 334  
335 -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 SDMX Standards Section 6 “Technical Notes”.
336 -1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
337 -1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
338 -1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
339 -1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
330 +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 [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”.
331 +1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
332 +1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
333 +1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
334 +1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /[[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association from Organisation.
340 340  
341 -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, MetadataProvider, DataConsumer, OrganisationUnit or Agency, except for limited Contact information.
336 +[[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, MetadataProvider, DataConsumer, OrganisationUnit or Agency, except for limited (% style="color:#e74c3c" %)Contact(%%) information.
342 342  
343 343  A partial //OrganisationScheme// (where isPartial is set to “true”) is identical to an //OrganisationScheme// and contains the //Organisation// and associated names and descriptions, just as in a normal //OrganisationScheme//. However, its content is a subset of the full //OrganisationScheme//. The way this works is described in section 3.5.3.1 on //ItemScheme//.
344 344  
345 -====== 4.7.2.2 Definitions ======
340 +==== 4.7.2.2 Definitions ====
346 346  
347 -|**Class**|**Feature**|**Description**
342 +(% style="width:946.835px" %)
343 +|**Class**|**Feature**|(% style="width:540px" %)**Description**
348 348  |//OrganisationScheme//|(((
349 349  Abstract Class
350 -
351 351  Inherits from
352 -
353 353  //ItemScheme//
354 -
355 355  Sub classes are:
356 -
357 357  AgencyScheme
358 -
359 359  DataProviderScheme
360 -
361 361  MetadataProviderScheme
362 -
363 363  DataConsumerScheme
364 -
365 365  OrganisationUnitScheme
366 -)))|A maintained collection of Organisations.
367 -| |/items|Association to the Organisations in the scheme.
354 +)))|(% style="width:540px" %)A maintained collection of Organisations.
355 +| |/items|(% style="width:540px" %)Association to the Organisations in the scheme.
368 368  |//Organisation//|(((
369 369  Abstract Class
370 -
371 371  Inherits from
372 -
373 373  //Item//
374 -
375 375  Sub classes are:
376 -
377 377  Agency
378 -
379 379  DataProvider
380 -
381 381  MetadataProvider
382 -
383 383  DataConsumer
384 -
385 385  OrganisationUnit
386 -)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
387 -| |+contact|Association to the Contact information.
388 -| |/hierarchy|Association to child Organisations.
389 -|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.
390 -| |name|The designation of the Contact person by a linguistic expression.
391 -| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
392 -| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
393 -| |telephone|The telephone number of the Contact.
394 -| |fax|The fax number of the Contact.
395 -| |email|The Internet e-mail address of the Contact.
396 -| |X400|The X400 address of the Contact.
397 -| |uri|The URL address of the Contact.
398 -|AgencyScheme| |A maintained collection of Maintenance Agencies.
399 -| |/items|Association to the Maintenance Agency in the scheme.
400 -|DataProviderScheme| |A maintained collection of Data Providers.
401 -| |/items|Association to the Data Providers in the scheme.
402 -|MetadataProviderScheme| |A maintained collection of Metadata Providers.
403 -| |/items|Association to the Metadata Providers in the scheme.
404 -|DataConsumerScheme| |A maintained collection of Data Consumers.
405 -| |/items|Association to the Data Consumers in the scheme.
406 -|OrganisationUnitScheme| |A maintained collection of Organisation Units.
407 -| |/items|Association to the Organisation Units in the scheme.
366 +)))|(% style="width:540px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
367 +| |+contact|(% style="width:540px" %)Association to the (% style="color:#e74c3c" %)Contact(%%) information.
368 +| |/hierarchy|(% style="width:540px" %)Association to child Organisations.
369 +|(%%)(% style="color:#e74c3c" %)Contact| |(% style="width:540px" %)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.
370 +| |name|(% style="width:540px" %)The designation of the (% style="color:#e74c3c" %)Contact(%%) person by a linguistic expression.
371 +| |organisationUnit|(% style="width:540px" %)The designation of the organisational structure by a linguistic expression, within which (% style="color:#e74c3c" %)Contact(%%) person works.
372 +| |responsibility|(% style="width:540px" %)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(%%).
373 +| |telephone|(% style="width:540px" %)The [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] of the (% style="color:#e74c3c" %)Contact(%%).
374 +| |fax|(% style="width:540px" %)The fax number of the (% style="color:#e74c3c" %)Contact(%%).
375 +| |email|(% style="width:540px" %)The Internet e-mail address of the (% style="color:#e74c3c" %)Contact(%%).
376 +| |X400|(% style="width:540px" %)The X400 address of the (% style="color:#e74c3c" %)Contact(%%).
377 +| |uri|(% style="width:540px" %)The URL address of the (% style="color:#e74c3c" %)Contact(%%).
378 +|AgencyScheme| |(% style="width:540px" %)A maintained collection of Maintenance Agencies.
379 +| |/items|(% style="width:540px" %)Association to the [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] in the scheme.
380 +|DataProviderScheme| |(% style="width:540px" %)A maintained collection of [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]].
381 +| |/items|(% style="width:540px" %)Association to the [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] in the scheme.
382 +|MetadataProviderScheme| |(% style="width:540px" %)A maintained collection of Metadata Providers.
383 +| |/items|(% style="width:540px" %)Association to the Metadata Providers in the scheme.
384 +|DataConsumerScheme| |(% style="width:540px" %)A maintained collection of [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]].
385 +| |/items|(% style="width:540px" %)Association to the [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]] in the scheme.
386 +|OrganisationUnitScheme| |(% style="width:540px" %)A maintained collection of Organisation Units.
387 +| |/items|(% style="width:540px" %)Association to the Organisation Units in the scheme.
408 408  |Agency|(((
409 409  Inherits from
410 -
411 411  //Organisation//
412 -)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
391 +)))|(% style="width:540px" %)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.
413 413  |DataProvider|(((
414 414  Inherits from
415 -
416 416  //Organisation//
417 -)))|An organisation that produces data.
395 +)))|(% style="width:540px" %)An organisation that produces data.
418 418  |MetadataProvider|(((
419 419  Inherits from
420 -
421 421  //Organisation//
422 -)))|An organisation that produces reference metadata.
399 +)))|(% style="width:540px" %)An organisation that produces [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
423 423  |DataConsumer|(((
424 424  Inherits from
425 -
426 426  //Organisation//
427 -)))|An organisation using data as input for further processing.
403 +)))|(% style="width:540px" %)An organisation using data as input for further processing.
428 428  |OrganisationUnit|(((
429 429  Inherits from
430 -
431 431  //Organisation//
432 -)))|A designation in the organisational structure.
433 -| |/hierarchy|Association to child Organisation Units
407 +)))|(% style="width:540px" %)A designation in the organisational structure.
408 +| |/hierarchy|(% style="width:540px" %)Association to child Organisation Units
434 434  
410 +== 4.8 Reporting Taxonomy ==
435 435  
412 +=== 4.8.1 Class Diagram ===
436 436  
437 -=== 4.8 Reporting Taxonomy ===
438 -
439 -==== 4.8.1 Class Diagram ====
440 -
441 441  [[image:1749246291205-630.jpeg]]
442 442  
443 443  **Figure 26: Class diagram of the Reporting Taxonomy**
444 444  
445 -===== 4.8.2 Explanation of the Diagram =====
418 +=== 4.8.2 Explanation of the Diagram ===
446 446  
447 -====== 4.8.2.1 Narrative ======
420 +==== 4.8.2.1 Narrative ====
448 448  
449 449  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.
450 450  
451 -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 Dataflow, or Metadataflow, 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 Dataflow). 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:
424 +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 [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]], 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 [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]). 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:
452 452  
453 453  Section 1
454 454  
... ... @@ -460,23 +460,23 @@
460 460  1. linked to Datafow_3
461 461  1. linked to Datafow_4
462 462  
463 -Here, the nodes of Section 1 and Section 2 would not be linked to Dataflow but the other would be linked to a Dataflow (and hence the DataStructureDefinition).
436 +Here, the nodes of Section 1 and Section 2 would not be linked to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] but the other would be linked to a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (and hence the DataStructureDefinition).
464 464  
465 465  A partial ReportingTaxonomy (where isPartial is set to “true”) is identical to a ReportingTaxonomy and contains the ReportingCategory and associated names and descriptions, just as in a normal ReportingTaxonomy. However, its content is a sub set of the full ReportingTaxonomy The way this works is described in section 3.5.3.1 on //ItemScheme//.
466 466  
467 -====== 4.8.2.2 Definitions ======
440 +==== 4.8.2.2 Definitions ====
468 468  
469 -|**Class**|**Feature**|**Description**
442 +(% style="width:969.835px" %)
443 +|**Class**|**Feature**|(% style="width:668px" %)**Description**
470 470  |ReportingTaxonomy|(((
471 471  Inherits from
472 -
473 473  //ItemScheme//
474 -)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
475 -| |/items|Associates the Reporting Category
476 -|ReportingCategory|Inherits from //Item//|A component that gives structure to the report and links to data and metadata.
477 -| |/hierarchy|Associates child Reporting Category.
478 -| |+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.
479 -| |+structure|Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
447 +)))|(% style="width:668px" %)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]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]].
448 +| |/items|(% style="width:668px" %)Associates the Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]]
449 +|ReportingCategory|Inherits from //Item//|(% style="width:668px" %)A [[component>>doc:sdmx:Glossary.Component.WebHome]] that gives structure to the report and links to data and metadata.
450 +| |/hierarchy|(% style="width:668px" %)Associates child Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]].
451 +| |+flow|(% style="width:668px" %)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.
452 +| |+structure|(% style="width:668px" %)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.
480 480  
481 481  
482 482