Changes for page 4 Specific Item Schemes
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,0 +1,1 @@ 1 +Methodology.SDMX STANDARDS 3\.0\: SECTION 2\. INFORMATION MODEL\: UML CONCEPTUAL DESIGN.WebHome - 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,16 +216,32 @@ 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: d uriurn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits fromItem and 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 -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 222 222 223 - Throughtheinheritance from //NameableArtefact// both ConceptSchemeandConcept havethe associationto InternationalStringtosupport a multi-lingualname, an optional multilingual description, and an association toAnnotation to supportnotes (not shown).229 +(% style="color:#2ecc71" %)Concept(%%) inherits from Item and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]: 224 224 225 -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 226 226 227 - A partial ConceptScheme(whereisPartial is setto“true”) is identicaltoaConceptScheme andcontainsthe Concept andassociatednamesanddescriptions,just asinormalConceptScheme.However,its contentisa subsetfthe full ConceptScheme. The waythis worksisdescribed insection3.5.3.1onItemScheme.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). 228 228 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 + 229 229 === 4.5.3 Class Diagram Relationship === 230 230 231 231 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_d9b0bdf4.jpg||height="450" width="461"]] ... ... @@ -236,13 +236,13 @@ 236 236 237 237 ==== 4.5.4.1 Narrative ==== 238 238 239 -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. 240 240 241 -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(%%). 242 242 243 -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. 244 244 245 -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. 246 246 247 247 ==== 4.5.4.2 Definitions ==== 248 248 ... ... @@ -250,27 +250,25 @@ 250 250 |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description** 251 251 |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)((( 252 252 Inherits from 253 - 254 254 //ItemScheme// 255 -)))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 256 -|(% 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" %)((( 257 257 Inherits from 258 - 259 259 //Item// 260 -)))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics. 261 -|(% 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(%%). 262 262 |(% style="width:204px" %) |(% style="width:222px" %)coreRepresentation|(% style="width:337px" %)Associates a Representation. 263 -|(% style="width:204px" %) |(% style="width:222px" %)+ISOConcept|(% style="width:337px" %)Association to an ISO concept reference. 264 -|(% style="width:204px" %)ISOConceptReference|(% style="width:222px" %) |(% style="width:337px" %)The identity of an ISO concept definition. 265 -|(% style="width:204px" %) |(% style="width:222px" %)conceptAgency|(% style="width:337px" %)The maintenance agency of the concept scheme containing the concept. 266 -|(% style="width:204px" %) |(% style="width:222px" %)conceptSchemeID|(% style="width:337px" %)The identifier of the concept scheme. 267 -|(% 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(%%). 268 268 269 269 == 4.6 Category Scheme == 270 270 271 271 === 4.6.1 Context === 272 272 273 -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. 274 274 275 275 === 4.6.2 Class diagram Inheritance === 276 276 ... ... @@ -282,19 +282,30 @@ 282 282 283 283 ==== 4.6.3.1 Narrative ==== 284 284 285 -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]]: 286 286 287 -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 288 288 289 -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]]: 290 290 291 -id uri urn 310 +id 311 +uri 312 +urn 292 292 293 -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). 294 294 295 -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. 296 296 297 -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. 298 298 299 299 === 4.6.4 Class diagram Relationship === 300 300 ... ... @@ -302,7 +302,7 @@ 302 302 303 303 **Figure 24: Relationship Class diagram of the Category Scheme** 304 304 305 -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. 306 306 307 307 ==== 4.6.4.1 Definitions ==== 308 308 ... ... @@ -310,23 +310,20 @@ 310 310 |**Class**|(% colspan="2" %)**Feature**|**Description** 311 311 |CategoryScheme|(% colspan="2" %)((( 312 312 Inherits from 313 - 314 314 //ItemScheme// 315 -)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 316 -| |(% 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]]. 317 317 |Category|((( 318 318 Inherits from 319 - 320 320 //Item// 321 -)))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 322 -| |/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]]. 323 323 |Categorisation|((( 324 324 Inherits from 325 - 326 326 //MaintainableArtefact// 327 -)))|(% colspan="2" %)Associates an Identifable Artefact with a Category. 328 -| |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact. 329 -| |+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]]. 330 330 331 331 == 4.7 Organisation Scheme == 332 332 ... ... @@ -344,13 +344,13 @@ 344 344 345 345 The //OrganisationScheme// can be one of five types: 346 346 347 -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”. 348 -1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy). 349 -1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy). 350 -1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy). 351 -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. 352 352 353 -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. 354 354 355 355 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//. 356 356 ... ... @@ -360,85 +360,66 @@ 360 360 |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description** 361 361 |//OrganisationScheme//|(% style="width:246px" %)((( 362 362 Abstract Class Inherits from 363 - 364 364 //ItemScheme// 365 365 366 366 Sub classes are: 367 - 368 368 AgencyScheme 369 - 370 370 DataProviderScheme 371 - 372 372 MetadataProviderScheme DataConsumerScheme 373 - 374 374 OrganisationUnitScheme 375 375 )))|(% style="width:336px" %)A maintained collection of Organisations. 376 376 | |(% style="width:246px" %)/items|(% style="width:336px" %)((( 377 -Association to the 378 - 379 -Organisations in the scheme. 390 +Association to the Organisations in the scheme. 380 380 ))) 381 381 |//Organisation//|(% style="width:246px" %)((( 382 382 Abstract Class 394 +Inherits from //Item// 383 383 384 -Inherits from 385 - 386 -//Item// 387 - 388 388 Sub classes are: 389 - 390 390 Agency 391 - 392 392 DataProvider 393 - 394 394 MetadataProvider DataConsumer 395 - 396 396 OrganisationUnit 397 397 )))|(% 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. 398 -| |(% 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. 399 399 | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisations. 400 -|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. 401 -| |(% style="width:246px" %)name|(% style="width:336px" %)The designation of the Contact person by a linguistic expression. 402 -| |(% style="width:246px" %)organisationUnit|(% style="width:336px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works. 403 -| |(% 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. 404 -| |(% style="width:246px" %)telephone|(% style="width:336px" %)The telephone number of the Contact. 405 -| |(% style="width:246px" %)fax|(% style="width:336px" %)The fax number of the Contact. 406 -| |(% style="width:246px" %)email|(% style="width:336px" %)The Internet e-mail address of the Contact. 407 -| |(% style="width:246px" %)X400|(% style="width:336px" %)The X400 address of the Contact. 408 -| |(% 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(%%). 409 409 |AgencyScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Maintenance Agencies. 410 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Maintenance Agency in the scheme. 411 -|DataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Providers. 412 -| |(% 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. 413 413 |MetadataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Metadata Providers. 414 414 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Metadata Providers in the scheme. 415 -|DataConsumerScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Consumers. 416 -| |(% 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. 417 417 |OrganisationUnitScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Organisation Units. 418 418 | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme. 419 419 |Agency|(% style="width:246px" %)((( 420 420 Inherits from 421 - 422 422 //Organisation// 423 -)))|(% 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. 424 424 |DataProvider|(% style="width:246px" %)((( 425 425 Inherits from 426 - 427 427 //Organisation// 428 428 )))|(% style="width:336px" %)An organisation that produces data. 429 429 |MetadataProvider|(% style="width:246px" %)((( 430 430 Inherits from 431 - 432 432 //Organisation// 433 433 )))|(% style="width:336px" %)An organisation that produces reference metadata. 434 434 |DataConsumer|(% style="width:246px" %)((( 435 435 Inherits from 436 - 437 437 //Organisation// 438 438 )))|(% style="width:336px" %)An organisation using data as input for further processing. 439 439 |OrganisationUnit|(% style="width:246px" %)((( 440 440 Inherits from 441 - 442 442 //Organisation// 443 443 )))|(% style="width:336px" %)A designation in the organisational structure. 444 444 | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units ... ... @@ -457,7 +457,7 @@ 457 457 458 458 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. 459 459 460 -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: 461 461 462 462 Section 1 463 463 ... ... @@ -469,10 +469,12 @@ 469 469 1. linked to Datafow_3 470 470 1. linked to Datafow_4 471 471 472 -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). 473 473 474 -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 475 475 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 + 476 476 ==== 4.8.2.2 Definitions ==== 477 477 478 478 (% style="width:759.039px" %) ... ... @@ -479,19 +479,17 @@ 479 479 |(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description** 480 480 |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)((( 481 481 Inherits from 482 - 483 483 //ItemScheme// 484 -)))|(% 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. 485 485 |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category 486 486 |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)((( 487 487 Inherits from 488 - 489 489 //Item// 490 -)))|(% 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. 491 491 |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category. 492 -|(% 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. 493 493 |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)((( 494 -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. 495 495 ))) 496 496 497 497 {{putFootnotes/}}