Changes for page 4 Specific Item Schemes

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

From version 16.1
edited by Helena
on 2025/05/16 13:48
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,7 +4,7 @@
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 10  ConceptScheme
... ... @@ -18,7 +18,7 @@
18 18  CustomTypeScheme
19 19  VtlMappingScheme
20 20  
21 -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).
22 22  
23 23  == 4.2 Inheritance View ==
24 24  
... ... @@ -36,7 +36,7 @@
36 36  
37 37  ==== 4.3.2.1 Narrative ====
38 38  
39 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
39 +The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
40 40  
41 41  id
42 42  uri
... ... @@ -49,20 +49,18 @@
49 49  structureURL
50 50  isPartial
51 51  
52 -The Code inherits from //Item// and has the following attributes:
52 +The [[Code>>doc:xwiki:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
53 53  
54 54  id
55 55  uri
56 56  urn
57 57  
58 -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).
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).
59 59  
60 -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.
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.
61 61  
62 -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
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//.
63 63  
64 -//ItemScheme//.
65 -
66 66  ==== 4.3.2.2 Definitions ====
67 67  
68 68  (% style="width:743.039px" %)
... ... @@ -71,12 +71,12 @@
71 71  Inherits from
72 72  
73 73  //ItemScheme//
74 -)))|(% 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.
75 75  |Code|(((
76 76  Inherits from
77 77  
78 78  Item
79 -)))|(% 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.
80 80  | |hierarchy|(% style="width:465px" %)Associates the parent and the child codes.
81 81  | |extends|(% style="width:465px" %)Associates a Codelist with any Codelists that it may extend.
82 82  
... ... @@ -88,9 +88,9 @@
88 88  
89 89  ==== 4.3.3.1 Narrative ====
90 90  
91 -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{{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 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.
92 92  
93 -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.
94 94  
95 95  ==== 4.3.3.2 Definitions ====
96 96  
... ... @@ -98,17 +98,17 @@
98 98  (% style="width:753.039px" %)
99 99  |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
100 100  |(% style="width:184px" %)CodelistExtension|(% style="width:145px" %) |(% style="width:421px" %)The association between Codelists that may extend other Codelists.
101 -|(% 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 Conflicts.
102 -|(% style="width:184px" %) |(% style="width:145px" %)sequence|(% style="width:421px" %)The order that will be used when extending a Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
103 -|(% style="width:184px" %)InclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of Codes to be included when extending a Codelist.
104 -|(% style="width:184px" %)ExclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of Codes to be excluded when extending a Codelist.
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.
105 105  |(% style="width:184px" %)MemberValue|(% style="width:145px" %)(((
106 106  Inherits from:
107 107  
108 108  //SelectionValue//
109 -)))|(% style="width:421px" %)A collection of values based on Codes and their children.
110 -|(% style="width:184px" %) |(% style="width:145px" %)cascadeValues|(% style="width:421px" %)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 -|(% style="width:184px" %) |(% style="width:145px" %)value|(% style="width:421px" %)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 ===
... ... @@ -125,12 +125,12 @@
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 131  GeoGridCodelist
132 132  
133 -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.
134 134  
135 135  The latter, i.e., GeoGridCodelist, comprises a set of GridCodes, which are related to the gridDefinition specified in the GeoGridCodelist.
136 136  
... ... @@ -151,14 +151,14 @@
151 151  Abstract Class Sub Classes:
152 152  GeoFeatureSet
153 153  GeoGridCode
154 -)))|The abstract class that represents a special type of Code, which includes geospatial information.
152 +)))|The abstract class that represents a special type of [[Code>>doc:xwiki:Glossary.Code.WebHome]], which includes geospatial information.
155 155  |(% 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.
156 -|(% colspan="2" %)GeoGridCodelist|(% colspan="4" %) |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
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.
157 157  |(% colspan="2" %) |(% colspan="4" %)gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
158 -|(% colspan="2" %)GeoFeatureSetCode|(% colspan="4" %) |A Code that has a geo feature set.
159 -|(% colspan="2" %) |(% colspan="4" %)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 -|(% colspan="2" %)GeoGridCode|(% colspan="4" %) |A Code that represents a Geo Grid Cell belonging in a specific grid definition.
161 -|(% colspan="2" %) |(% colspan="4" %)geoCell|The value used to assign the Code to one cell in the grid.
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.
162 162  
163 163  == 4.4 ValueList ==
164 164  
... ... @@ -172,7 +172,7 @@
172 172  
173 173  ==== 4.4.2.1 Narrative ====
174 174  
175 -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]]:
176 176  
177 177  id
178 178  uri
... ... @@ -185,9 +185,9 @@
185 185  structureURL
186 186  repositoryURL
187 187  
188 -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.
189 189  
190 -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//.
191 191  
192 192  The ValueList can have one or more ValueItems.
193 193  
... ... @@ -197,14 +197,12 @@
197 197  |**Class**|**Feature**|(% style="width:421px" %)**Description**
198 198  |ValueList|(((
199 199  Inherits from
200 -
201 201  //EnumeratedList//
202 -)))|(% style="width:421px" %)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.
203 203  |ValueItem|(((
204 204  Inherits from
205 -
206 206  //EnumeratedItem//
207 -)))|(% style="width:421px" %)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.
208 208  
209 209  == 4.5 Concept Scheme and Concepts ==
210 210  
... ... @@ -216,7 +216,7 @@
216 216  
217 217  === 4.5.2 Explanation of the Diagram ===
218 218  
219 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
215 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
220 220  
221 221  id
222 222  uri
... ... @@ -230,17 +230,17 @@
230 230  repositoryURL
231 231  isPartial
232 232  
233 -Concept inherits from Item and has the following attributes:
229 +(% style="color:#2ecc71" %)Concept(%%) inherits from Item and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
234 234  
235 235  id
236 236  uri
237 237  urn
238 238  
239 -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).
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).
240 240  
241 -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.
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.
242 242  
243 -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.
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.
244 244  
245 245  === 4.5.3 Class Diagram Relationship ===
246 246  
... ... @@ -252,13 +252,13 @@
252 252  
253 253  ==== 4.5.4.1 Narrative ====
254 254  
255 -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.
256 256  
257 -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(%%).
258 258  
259 -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.
260 260  
261 -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.
262 262  
263 263  ==== 4.5.4.2 Definitions ====
264 264  
... ... @@ -267,24 +267,24 @@
267 267  |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
268 268  Inherits from
269 269  //ItemScheme//
270 -)))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
271 -|(% style="width:204px" %)Concept|(% style="width:222px" %)(((
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" %)(((
272 272  Inherits from
273 273  //Item//
274 -)))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
275 -|(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child 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(%%).
276 276  |(% style="width:204px" %) |(% style="width:222px" %)coreRepresentation|(% style="width:337px" %)Associates a Representation.
277 -|(% style="width:204px" %) |(% style="width:222px" %)+ISOConcept|(% style="width:337px" %)Association to an ISO concept reference.
278 -|(% style="width:204px" %)ISOConceptReference|(% style="width:222px" %) |(% style="width:337px" %)The identity of an ISO concept definition.
279 -|(% style="width:204px" %) |(% style="width:222px" %)conceptAgency|(% style="width:337px" %)The maintenance agency of the concept scheme containing the concept.
280 -|(% style="width:204px" %) |(% style="width:222px" %)conceptSchemeID|(% style="width:337px" %)The identifier of the concept scheme.
281 -|(% style="width:204px" %) |(% style="width:222px" %)conceptID|(% style="width:337px" %)The identifier of the concept.
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(%%).
282 282  
283 283  == 4.6 Category Scheme ==
284 284  
285 285  === 4.6.1 Context ===
286 286  
287 -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.
288 288  
289 289  === 4.6.2 Class diagram Inheritance ===
290 290  
... ... @@ -296,7 +296,7 @@
296 296  
297 297  ==== 4.6.3.1 Narrative ====
298 298  
299 -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]]:
300 300  
301 301  id
302 302  uri
... ... @@ -309,17 +309,17 @@
309 309  serviceURL
310 310  isPartial
311 311  
312 -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]]:
313 313  
314 314  id
315 315  uri
316 316  urn
317 317  
318 -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).
319 319  
320 -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.
321 321  
322 -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.
323 323  
324 324  === 4.6.4 Class diagram Relationship ===
325 325  
... ... @@ -327,7 +327,7 @@
327 327  
328 328  **Figure 24: Relationship Class diagram of the Category Scheme**
329 329  
330 -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.
331 331  
332 332  ==== 4.6.4.1 Definitions ====
333 333  
... ... @@ -336,19 +336,19 @@
336 336  |CategoryScheme|(% colspan="2" %)(((
337 337  Inherits from
338 338  //ItemScheme//
339 -)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
340 -| |(% 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]].
341 341  |Category|(((
342 342  Inherits from
343 343  //Item//
344 -)))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
345 -| |/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]].
346 346  |Categorisation|(((
347 347  Inherits from
348 348  //MaintainableArtefact//
349 -)))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
350 -| |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
351 -| |+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]].
352 352  
353 353  == 4.7 Organisation Scheme ==
354 354  
... ... @@ -366,13 +366,13 @@
366 366  
367 367  The //OrganisationScheme// can be one of five types:
368 368  
369 -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”.
370 -1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
371 -1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
372 -1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
373 -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.
374 374  
375 -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.
376 376  
377 377  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//.
378 378  
... ... @@ -391,9 +391,7 @@
391 391  OrganisationUnitScheme
392 392  )))|(% style="width:336px" %)A maintained collection of Organisations.
393 393  | |(% style="width:246px" %)/items|(% style="width:336px" %)(((
394 -Association to the
395 -
396 -Organisations in the scheme.
390 +Association to the Organisations in the scheme.
397 397  )))
398 398  |//Organisation//|(% style="width:246px" %)(((
399 399  Abstract Class
... ... @@ -405,31 +405,31 @@
405 405  MetadataProvider DataConsumer
406 406  OrganisationUnit
407 407  )))|(% 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.
408 -| |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
402 +| |(% style="width:246px" %)+(% style="color:#2ecc71" %)contact|(% style="width:336px" %)Association to the (% style="color:#2ecc71" %)Contact(%%) information.
409 409  | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisations.
410 -|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.
411 -| |(% style="width:246px" %)name|(% style="width:336px" %)The designation of the Contact person by a linguistic expression.
412 -| |(% style="width:246px" %)organisationUnit|(% style="width:336px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
413 -| |(% style="width:246px" %)responsibility|(% style="width:336px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
414 -| |(% style="width:246px" %)telephone|(% style="width:336px" %)The telephone number of the Contact.
415 -| |(% style="width:246px" %)fax|(% style="width:336px" %)The fax number of the Contact.
416 -| |(% style="width:246px" %)email|(% style="width:336px" %)The Internet e-mail address of the Contact.
417 -| |(% style="width:246px" %)X400|(% style="width:336px" %)The X400 address of the Contact.
418 -| |(% style="width:246px" %)uri|(% style="width:336px" %)The URL address of the Contact.
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(%%).
419 419  |AgencyScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Maintenance Agencies.
420 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Maintenance Agency in the scheme.
421 -|DataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Providers.
422 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Providers in the scheme.
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.
423 423  |MetadataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Metadata Providers.
424 424  | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Metadata Providers in the scheme.
425 -|DataConsumerScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Consumers.
426 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Consumers 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.
427 427  |OrganisationUnitScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Organisation Units.
428 428  | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
429 429  |Agency|(% style="width:246px" %)(((
430 430  Inherits from
431 431  //Organisation//
432 -)))|(% style="width:336px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
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.
433 433  |DataProvider|(% style="width:246px" %)(((
434 434  Inherits from
435 435  //Organisation//
... ... @@ -462,7 +462,7 @@
462 462  
463 463  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.
464 464  
465 -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:
466 466  
467 467  Section 1
468 468  
... ... @@ -474,10 +474,12 @@
474 474  1. linked to Datafow_3
475 475  1. linked to Datafow_4
476 476  
477 -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).
478 478  
479 -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
480 480  
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 +
481 481  ==== 4.8.2.2 Definitions ====
482 482  
483 483  (% style="width:759.039px" %)
... ... @@ -485,16 +485,16 @@
485 485  |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)(((
486 486  Inherits from
487 487  //ItemScheme//
488 -)))|(% style="width:428px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
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.
489 489  |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category
490 490  |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)(((
491 491  Inherits from
492 492  //Item//
493 -)))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata.
489 +)))|(% style="width:428px" %)A [[component>>doc:xwiki:Glossary.Component.WebHome]] that gives structure to the report and links to data and metadata.
494 494  |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.
495 -|(% style="width:177px" %) |(% style="width:152px" %)+flow|(% style="width:428px" %)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.
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.
496 496  |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
497 -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.
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.
498 498  )))
499 499  
500 500  {{putFootnotes/}}