Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19

From version 13.2
edited by Helena
on 2025/05/15 10:31
Change comment: There is no comment for this version
To version 18.1
edited by Helena
on 2025/05/16 23:15
Change comment: There is no comment for this version

Summary

Details

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