Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Helena on 2025/09/10 11:19
From version 5.5
edited by Helena
on 2025/06/08 14:56
Change comment: There is no comment for this version
To version 5.1
edited by Helena
on 2025/06/08 01:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,1 +1,0 @@
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
... ... @@ -4,22 +4,33 @@
4 4  
5 5  == 4.1 Introduction ==
6 6  
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:
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:
8 8  
9 9  Codelist
10 +
10 10  ConceptScheme
12 +
11 11  CategoryScheme
14 +
12 12  AgencyScheme, DataProviderScheme, MetadataProviderScheme,
16 +
13 13  DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
18 +
14 14  ReportingTaxonomy
20 +
15 15  TransformationScheme
22 +
16 16  RulesetScheme
24 +
17 17  UserDefinedOperatorScheme
26 +
18 18  NamePersonalisationScheme
28 +
19 19  CustomTypeScheme
30 +
20 20  VtlMappingScheme
21 21  
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).
33 +Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
23 23  
24 24  == 4.2 Inheritance View ==
25 25  
... ... @@ -37,34 +37,33 @@
37 37  
38 38  ==== 4.3.2.1 Narrative ====
39 39  
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
51 +The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
41 41  
42 -The [[Code>>doc:sdmx:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
53 +The Code inherits from //Item// and has the following attributes:
43 43  
44 -id
45 -uri
46 -urn
55 +id uri urn
47 47  
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).
57 +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).
49 49  
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.
59 +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.
51 51  
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//.
61 +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//.
53 53  
54 54  ==== 4.3.2.2 Definitions ====
55 55  
56 -(% style="width:912.835px" %)
57 -|**Class**|**Feature**|(% style="width:656px" %)**Description**
65 +|**Class**|**Feature**|**Description**
58 58  |Codelist|(((
59 59  Inherits from
68 +
60 60  //ItemScheme//
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]]|(((
70 +)))|A list from which some statistical concepts (coded concepts) take their values.
71 +|Code|(((
63 63  Inherits from
73 +
64 64  Item
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.
75 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
76 +| |hierarchy|Associates the parent and the child codes.
77 +| |extends|Associates a Codelist with any Codelists that it may extend.
68 68  
69 69  ==== 4.3.3 Class Diagram – Codelist Extension ====
70 70  
... ... @@ -74,27 +74,29 @@
74 74  
75 75  ==== 4.3.3.1 Narrative ====
76 76  
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 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.
87 +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[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[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.
78 78  
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.
89 +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.
80 80  
81 81  ==== 4.3.3.2 Definitions ====
82 82  
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.
93 +|**Class**|**Feature**|**Description**
94 +|CodelistExtension| |The association between Codelists that may extend other Codelists.
95 +| |prefix|A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
96 +| |sequence|(((
97 +The order that will be used when extending a
98 +
99 +Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
89 89  )))
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.
101 +|InclusiveCodeSelection| |The subset of Codes to be included when extending a Codelist.
102 +|ExclusiveCodeSelection| |The subset of Codes to be excluded when extending a Codelist.
92 92  |MemberValue|(((
93 93  Inherits from:
105 +
94 94  //SelectionValue//
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.
107 +)))|A collection of values based on Codes and their children.
108 +| |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.
109 +| |value|The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
98 98  
99 99  === 4.3.4 Class Diagram – Geospatial Codelist ===
100 100  
... ... @@ -110,39 +110,43 @@
110 110  
111 111  ==== 4.3.4.1 Narrative ====
112 112  
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:
125 +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:
114 114  
115 115  GeographicCodelist
116 116  
117 117  GeoGridCodelist
118 118  
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.
131 +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.
120 120  
121 121  The latter, i.e., GeoGridCodelist, comprises a set of GridCodes, which are related to the gridDefinition specified in the GeoGridCodelist.
122 122  
123 123  ==== 4.3.4.2 Definitions ====
124 124  
125 -(% style="width:960.835px" %)
126 -|**Class**|**Feature**|(% style="width:559px" %)**Description**
137 +|**Class**|**Feature**|**Description**
127 127  |//GeoCodelist//|(((
128 128  Abstract Class Sub Classes:
140 +
129 129  GeographicCodelist
142 +
130 130  GeoGridCodelist
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.
144 +)))|The abstract class that represents a special type of Codelist, which includes geospatial information.
145 +| |geoType|The type of Geo Codelist that the Codelist will become.
133 133  |//GeoRefCode//|(((
134 134  Abstract Class
148 +
135 135  Sub Classes:
150 +
136 136  GeoFeatureSetCode
152 +
137 137  GeoGridCode
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.
154 +)))|The abstract class that represents a special type of Code, which includes geospatial information.
155 +|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.
156 +|GeoGridCodelist| |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
157 +| |gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
158 +|GeoFeatureSetCode| |A Code that has a geo feature set.
159 +| |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).
160 +|GeoGridCode| |A Code that represents a Geo Grid Cell belonging in a specific grid definition.
161 +| |geoCell|The value used to assign the Code to one cell in the grid.
146 146  
147 147  == 4.4 ValueList ==
148 148  
... ... @@ -156,37 +156,29 @@
156 156  
157 157  ==== 4.4.2.1 Narrative ====
158 158  
159 -A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
175 +A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
160 160  
161 -id
162 -uri
163 -urn
164 -(% style="color:#e74c3c" %)version(%%)
165 -validFrom
166 -validTo
167 -[[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]]
168 -registryURL
169 -structureURL
170 -repositoryURL
177 +id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
171 171  
172 -ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed (% style="color:#e74c3c" %)constraints(%%), to the former.
179 +ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
173 173  
174 -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//.
181 +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//.
175 175  
176 176  The ValueList can have one or more ValueItems.
177 177  
178 178  ==== 4.4.2.2 Definitions ====
179 179  
180 -(% style="width:929.835px" %)
181 -|**Class**|(% style="width:175px" %)**Feature**|(% style="width:632px" %)**Description**
182 -|ValueList|(% style="width:175px" %)(((
187 +|**Class**|**Feature**|**Description**
188 +|ValueList|(((
183 183  Inherits from
190 +
184 184  //EnumeratedList//
185 -)))|(% style="width:632px" %)A list from which some statistical (% style="color:#e74c3c" %)concepts(%%) (enumerated (% style="color:#e74c3c" %)concepts(%%)) take their values.
186 -|ValueItem|(% style="width:175px" %)(((
192 +)))|A list from which some statistical concepts (enumerated concepts) take their values.
193 +|ValueItem|(((
187 187  Inherits from
195 +
188 188  //EnumeratedItem//
189 -)))|(% 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.
197 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
190 190  
191 191  == 4.5 Concept Scheme and Concepts ==
192 192  
... ... @@ -198,30 +198,16 @@
198 198  
199 199  === 4.5.2 Explanation of the Diagram ===
200 200  
201 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
209 +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:
202 202  
203 -id
204 -uri
205 -urn
206 -(% style="color:#e74c3c" %)version(%%) validFrom validTo
207 -[[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]]
208 -registryURL
209 -structureURL
210 -repositoryURL
211 -isPartial
211 +id uri urn
212 212  
213 -(% style="color:#e74c3c" %)Concept(%%) inherits from Item and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
213 +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).
214 214  
215 -id
216 -uri
217 -urn
215 +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.
218 218  
219 -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).
217 +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.
220 220  
221 -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.
222 -
223 -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.
224 -
225 225  === 4.5.3 Class Diagram Relationship ===
226 226  
227 227  [[image:1749246291189-654.jpeg]]
... ... @@ -232,41 +232,44 @@
232 232  
233 233  ==== 4.5.4.1 Narrative ====
234 234  
235 -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.
229 +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.
236 236  
237 -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(%%).
231 +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.
238 238  
239 -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.
233 +The Representation is documented in more detail in the section on the SDMX Base.
240 240  
241 -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.
235 +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.
242 242  
243 243  ==== 4.5.4.2 Definitions ====
244 244  
245 -(% style="width:912.835px" %)
246 -|(% style="width:170px" %)**Class**|(% style="width:184px" %)**Feature**|(% style="width:548px" %)**Description**
247 -|(% style="width:170px" %)(((
239 +|**Class**|**Feature**|**Description**
240 +|(((
248 248  ConceptScheme
249 -)))|(% style="width:184px" %)(((
242 +
243 +
244 +)))|(((
250 250  Inherits from
246 +
251 251  //ItemScheme//
252 -)))|(% 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.
253 -|(% style="width:170px" %)(% style="color:#e74c3c" %)Concept|(% style="width:184px" %)(((
248 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
249 +|Concept|(((
254 254  Inherits from
251 +
255 255  //Item//
256 -)))|(% style="width:548px" %)A (% style="color:#e74c3c" %)concept(%%) is a unit of knowledge created by a unique combination of characteristics.
257 -|(% style="width:170px" %) |(% style="width:184px" %)/hierarchy|(% style="width:548px" %)Associates the parent and the child (% style="color:#e74c3c" %)concept(%%).
258 -|(% style="width:170px" %) |(% style="width:184px" %)coreRepresentation|(% style="width:548px" %)Associates a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]].
259 -|(% style="width:170px" %) |(% style="width:184px" %)+ISOConcept|(% style="width:548px" %)Association to an ISO (% style="color:#e74c3c" %)concept(%%) reference.
260 -|(% style="width:170px" %)ISOConceptReference|(% style="width:184px" %) |(% style="width:548px" %)The identity of an ISO (% style="color:#e74c3c" %)concept(%%) definition.
261 -|(% 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(%%).
262 -|(% style="width:170px" %) |(% style="width:184px" %)conceptSchemeID|(% style="width:548px" %)The identifier of the [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]].
263 -|(% style="width:170px" %) |(% style="width:184px" %)conceptID|(% style="width:548px" %)The identifier of the (% style="color:#e74c3c" %)concept(%%).
253 +)))|A concept is a unit of knowledge created by a unique combination of characteristics.
254 +| |/hierarchy|Associates the parent and the child concept.
255 +| |coreRepresentation|Associates a Representation.
256 +| |+ISOConcept|Association to an ISO concept reference.
257 +|ISOConceptReference| |The identity of an ISO concept definition.
258 +| |conceptAgency|The maintenance agency of the concept scheme containing the concept.
259 +| |conceptSchemeID|The identifier of the concept scheme.
260 +| |conceptID|The identifier of the concept.
264 264  
265 265  == 4.6 Category Scheme ==
266 266  
267 267  === 4.6.1 Context ===
268 268  
269 -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.
266 +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.
270 270  
271 271  === 4.6.2 Class diagram Inheritance ===
272 272  
... ... @@ -278,59 +278,50 @@
278 278  
279 279  ==== 4.6.3.1 Narrative ====
280 280  
281 -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]]:
278 +The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
282 282  
283 -id
284 -uri
285 -urn
286 -version
287 -validFrom
288 -validTo
289 -[[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]]
290 -structureURL
291 -serviceURL
292 -isPartial
280 +id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
293 293  
294 -[[Category>>doc:sdmx:Glossary.Category.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
282 +Category inherits from //Item// and has the following attributes:
295 295  
296 -id
297 -uri
298 -urn
284 +id uri urn
299 299  
300 -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).
286 +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).
301 301  
302 -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.
288 +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.
303 303  
304 -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.
290 +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.
305 305  
306 306  === 4.6.4 Class diagram Relationship ===
307 307  
308 308  [[image:1749246291197-631.jpeg]]
309 309  
310 -**Figure 24: Relationship Class diagram of the [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]**
296 +**Figure 24: Relationship Class diagram of the Category Scheme**
311 311  
312 -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.
298 +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.
313 313  
314 314  ==== 4.6.4.1 Definitions ====
315 315  
316 -(% style="width:935.835px" %)
317 -|**Class**|**Feature**|(% style="width:601px" %)**Description**
302 +|**Class**|**Feature**|**Description**
318 318  |CategoryScheme|(((
319 319  Inherits from
305 +
320 320  //ItemScheme//
321 -)))|(% 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.
322 -| |/items|(% style="width:601px" %)Associates the [[categories>>doc:sdmx:Glossary.Category.WebHome]].
323 -|[[Category>>doc:sdmx:Glossary.Category.WebHome]]|(((
307 +)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
308 +| |/items|Associates the categories.
309 +|Category|(((
324 324  Inherits from
311 +
325 325  //Item//
326 -)))|(% 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.
327 -| |/hierarchy|(% style="width:601px" %)Associates the parent and the child [[Category>>doc:sdmx:Glossary.Category.WebHome]].
313 +)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
314 +| |/hierarchy|Associates the parent and the child Category.
328 328  |Categorisation|(((
329 329  Inherits from
317 +
330 330  //MaintainableArtefact//
331 -)))|(% style="width:601px" %)Associates an Identifable [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]] with a [[Category>>doc:sdmx:Glossary.Category.WebHome]].
332 -| |+categorisedArtefact|(% style="width:601px" %)Associates the Identifable [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]].
333 -| |+categorisedBy|(% style="width:601px" %)Associates the [[Category>>doc:sdmx:Glossary.Category.WebHome]].
319 +)))|Associates an Identifable Artefact with a Category.
320 +| |+categorisedArtefact|Associates the Identifable Artefact.
321 +| |+categorisedBy|Associates the Category.
334 334  
335 335  == 4.7 Organisation Scheme ==
336 336  
... ... @@ -348,85 +348,105 @@
348 348  
349 349  The //OrganisationScheme// can be one of five types:
350 350  
351 -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”.
352 -1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
353 -1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
354 -1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
355 -1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /[[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association from Organisation.
339 +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”.
340 +1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
341 +1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
342 +1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
343 +1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
356 356  
357 -[[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.
345 +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.
358 358  
359 359  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//.
360 360  
361 361  ==== 4.7.2.2 Definitions ====
362 362  
363 -(% style="width:946.835px" %)
364 -|**Class**|**Feature**|(% style="width:540px" %)**Description**
351 +|**Class**|**Feature**|**Description**
365 365  |//OrganisationScheme//|(((
366 366  Abstract Class
354 +
367 367  Inherits from
356 +
368 368  //ItemScheme//
358 +
369 369  Sub classes are:
360 +
370 370  AgencyScheme
362 +
371 371  DataProviderScheme
364 +
372 372  MetadataProviderScheme
366 +
373 373  DataConsumerScheme
368 +
374 374  OrganisationUnitScheme
375 -)))|(% style="width:540px" %)A maintained collection of Organisations.
376 -| |/items|(% style="width:540px" %)Association to the Organisations in the scheme.
370 +)))|A maintained collection of Organisations.
371 +| |/items|Association to the Organisations in the scheme.
377 377  |//Organisation//|(((
378 378  Abstract Class
374 +
379 379  Inherits from
376 +
380 380  //Item//
378 +
381 381  Sub classes are:
380 +
382 382  Agency
382 +
383 383  DataProvider
384 +
384 384  MetadataProvider
386 +
385 385  DataConsumer
388 +
386 386  OrganisationUnit
387 -)))|(% 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.
388 -| |+contact|(% style="width:540px" %)Association to the (% style="color:#e74c3c" %)Contact(%%) information.
389 -| |/hierarchy|(% style="width:540px" %)Association to child Organisations.
390 -|(%%)(% 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.
391 -| |name|(% style="width:540px" %)The designation of the (% style="color:#e74c3c" %)Contact(%%) person by a linguistic expression.
392 -| |organisationUnit|(% style="width:540px" %)The designation of the organisational structure by a linguistic expression, within which (% style="color:#e74c3c" %)Contact(%%) person works.
393 -| |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(%%).
394 -| |telephone|(% style="width:540px" %)The [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] of the (% style="color:#e74c3c" %)Contact(%%).
395 -| |fax|(% style="width:540px" %)The fax number of the (% style="color:#e74c3c" %)Contact(%%).
396 -| |email|(% style="width:540px" %)The Internet e-mail address of the (% style="color:#e74c3c" %)Contact(%%).
397 -| |X400|(% style="width:540px" %)The X400 address of the (% style="color:#e74c3c" %)Contact(%%).
398 -| |uri|(% style="width:540px" %)The URL address of the (% style="color:#e74c3c" %)Contact(%%).
399 -|AgencyScheme| |(% style="width:540px" %)A maintained collection of Maintenance Agencies.
400 -| |/items|(% style="width:540px" %)Association to the [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] in the scheme.
401 -|DataProviderScheme| |(% style="width:540px" %)A maintained collection of [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]].
402 -| |/items|(% style="width:540px" %)Association to the [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] in the scheme.
403 -|MetadataProviderScheme| |(% style="width:540px" %)A maintained collection of Metadata Providers.
404 -| |/items|(% style="width:540px" %)Association to the Metadata Providers in the scheme.
405 -|DataConsumerScheme| |(% style="width:540px" %)A maintained collection of [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]].
406 -| |/items|(% style="width:540px" %)Association to the [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]] in the scheme.
407 -|OrganisationUnitScheme| |(% style="width:540px" %)A maintained collection of Organisation Units.
408 -| |/items|(% style="width:540px" %)Association to the Organisation Units in the scheme.
390 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
391 +| |+contact|Association to the Contact information.
392 +| |/hierarchy|Association to child Organisations.
393 +|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.
394 +| |name|The designation of the Contact person by a linguistic expression.
395 +| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
396 +| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
397 +| |telephone|The telephone number of the Contact.
398 +| |fax|The fax number of the Contact.
399 +| |email|The Internet e-mail address of the Contact.
400 +| |X400|The X400 address of the Contact.
401 +| |uri|The URL address of the Contact.
402 +|AgencyScheme| |A maintained collection of Maintenance Agencies.
403 +| |/items|Association to the Maintenance Agency in the scheme.
404 +|DataProviderScheme| |A maintained collection of Data Providers.
405 +| |/items|Association to the Data Providers in the scheme.
406 +|MetadataProviderScheme| |A maintained collection of Metadata Providers.
407 +| |/items|Association to the Metadata Providers in the scheme.
408 +|DataConsumerScheme| |A maintained collection of Data Consumers.
409 +| |/items|Association to the Data Consumers in the scheme.
410 +|OrganisationUnitScheme| |A maintained collection of Organisation Units.
411 +| |/items|Association to the Organisation Units in the scheme.
409 409  |Agency|(((
410 410  Inherits from
414 +
411 411  //Organisation//
412 -)))|(% 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.
416 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
413 413  |DataProvider|(((
414 414  Inherits from
419 +
415 415  //Organisation//
416 -)))|(% style="width:540px" %)An organisation that produces data.
421 +)))|An organisation that produces data.
417 417  |MetadataProvider|(((
418 418  Inherits from
424 +
419 419  //Organisation//
420 -)))|(% style="width:540px" %)An organisation that produces [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
426 +)))|An organisation that produces reference metadata.
421 421  |DataConsumer|(((
422 422  Inherits from
429 +
423 423  //Organisation//
424 -)))|(% style="width:540px" %)An organisation using data as input for further processing.
431 +)))|An organisation using data as input for further processing.
425 425  |OrganisationUnit|(((
426 426  Inherits from
434 +
427 427  //Organisation//
428 -)))|(% style="width:540px" %)A designation in the organisational structure.
429 -| |/hierarchy|(% style="width:540px" %)Association to child Organisation Units
436 +)))|A designation in the organisational structure.
437 +| |/hierarchy|Association to child Organisation Units
430 430  
431 431  == 4.8 Reporting Taxonomy ==
432 432  
... ... @@ -442,7 +442,7 @@
442 442  
443 443  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.
444 444  
445 -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:
453 +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:
446 446  
447 447  Section 1
448 448  
... ... @@ -454,23 +454,23 @@
454 454  1. linked to Datafow_3
455 455  1. linked to Datafow_4
456 456  
457 -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).
465 +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).
458 458  
459 459  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//.
460 460  
461 461  ==== 4.8.2.2 Definitions ====
462 462  
463 -(% style="width:969.835px" %)
464 -|**Class**|**Feature**|(% style="width:668px" %)**Description**
471 +|**Class**|**Feature**|**Description**
465 465  |ReportingTaxonomy|(((
466 466  Inherits from
474 +
467 467  //ItemScheme//
468 -)))|(% 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]].
469 -| |/items|(% style="width:668px" %)Associates the Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]]
470 -|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.
471 -| |/hierarchy|(% style="width:668px" %)Associates child Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]].
472 -| |+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.
473 -| |+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.
476 +)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
477 +| |/items|Associates the Reporting Category
478 +|ReportingCategory|Inherits from //Item//|A component that gives structure to the report and links to data and metadata.
479 +| |/hierarchy|Associates child Reporting Category.
480 +| |+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.
481 +| |+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.
474 474  
475 475  
476 476