Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 13.3
edited by Elena
on 2025/06/17 13:46
Change comment: There is no comment for this version
To version 2.2
edited by Helena
on 2025/05/19 23:53
Change comment: Changed document title to [4 Specific Item Schemes].

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -Methodology.SDMX 2\.1 Standards\. Section 2\. Information model\: UML conceptual design.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.elenasemanticproorg
1 +xwiki:XWiki.helena
Tags
... ... @@ -1,1 +1,0 @@
1 -Annotation|Artefact|Attribute|Category|Category scheme|Code|Code list|Component|Concept|Concept scheme|Contact|Contact phone number|Data consumer|Data provider|Data set|Data structure definition|Dataflow|Hierarchy|Level|Maintenance agency|Measure|Metadata set|Metadata structure definition|Metadataflow|Reference metadata|Representation|Statistical data and metadata exchange|Structural metadata
Content
... ... @@ -1,16 +1,14 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 += {{id name="_Toc370986"/}}4 Specific Item Schemes =
4 4  
5 5  == {{id name="_Toc370987"/}}4.1 Introduction ==
6 6  
7 -The structures that are an arrangement of objects into [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
5 +The structures that are an arrangement of objects into hierarchies or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
8 8  
9 -* Codelist
10 -* ConceptScheme
11 -* CategoryScheme
7 +* Codelist//  //
8 +* ConceptScheme//  //
9 +* CategoryScheme//  //
12 12  * AgencyScheme, DataProviderScheme, DataConsumerScheme, OrganisationUnitScheme which all inherit from the abstract class //OrganisationScheme//
13 -* Reporting Taxonomy
11 +* Reporting Taxonomy//  //
14 14  
15 15  == {{id name="_Toc370988"/}}4.2 Inheritance View ==
16 16  
... ... @@ -20,8 +20,6 @@
20 20  
21 21  === {{id name="_Toc370990"/}}4.3.1 Class Diagram ===
22 22  
23 -[[image:1747732337979-971.png]]
24 -
25 25  **Figure 15 Class diagram of the Codelist**
26 26  
27 27  === {{id name="_Toc370991"/}}4.3.2 Explanation of the Diagram ===
... ... @@ -28,14 +28,14 @@
28 28  
29 29  ==== 4.3.2.1 Narrative ====
30 30  
31 -The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
27 +The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
32 32  
33 33  * id
34 34  * uri
35 35  * urn
36 36  * version
37 -* validFrom
38 -* validTo
33 +* validFrom//  //
34 +* validTo//  //
39 39  * isExternalReference
40 40  * serviceURL
41 41  * structureURL
... ... @@ -42,32 +42,35 @@
42 42  * final
43 43  * isPartial
44 44  
45 -The [[Code>>doc:sdmx:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
41 +The Code inherits from //Item// and has the following attributes:
46 46  
47 47  * id
48 48  * uri
49 49  * urn
50 50  
51 -Both Codelist and [[Code>>doc:sdmx:Glossary.Code.WebHome]] have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown).
47 +Both Codelist and Code 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).
52 52  
53 -Through the inheritance the Codelist comprise one or more [[Codes>>doc:sdmx:Glossary.Code.WebHome]], and the [[Code>>doc:sdmx:Glossary.Code.WebHome]] itself can have one or more child [[Codes>>doc:sdmx:Glossary.Code.WebHome]] in the (inherited) [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. Note that a child [[Code>>doc:sdmx:Glossary.Code.WebHome]] can have only one parent [[Code>>doc:sdmx:Glossary.Code.WebHome]] in this association. A more complex HierachicalCodelist which allow multiple parents and multiple [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] is described later.
49 +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 HierachicalCodelist which allow multiple parents and multiple hierarchies is described later.
54 54  
55 -A partial Codelist (where isPartial is set to “true”) is identical to a Codelist and contains the [[Code>>doc:sdmx:Glossary.Code.WebHome]] and associated names and descriptions, just as in a normal [[code list>>doc:sdmx:Glossary.Code list.WebHome]]. However, its content is a sub set of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
51 +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 code list. However, its content is a sub set of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
56 56  
57 57  ==== 4.3.2.2 Definitions ====
58 58  
55 +:
56 +
59 59  (((
60 -(% style="width:905.294px" %)
61 -|(% style="width:132px" %)**Class**|(% style="width:172px" %)**Feature**|(% style="width:598px" %)**Description**
62 -|(% style="width:132px" %)Codelist|(% style="width:172px" %)(((
58 +|**Class**|**Feature**|**Description**
59 +|Codelist|(((
63 63  Inherits from
61 +
64 64  //ItemScheme//
65 -)))|(% style="width:598px" %)A list from which some statistical (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) (coded (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%)) take their values.
66 -|(% style="width:132px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]]|(% style="width:172px" %)(((
63 +)))|A list from which some statistical concepts (coded concepts) take their values.
64 +|Code|(((
67 67  Inherits from
66 +
68 68  //Item//
69 -)))|(% style="width:598px" %)A language independent set of letters, numbers or symbols that represent a (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) whose meaning is described in a natural language.
70 -|(% style="width:132px" %) |(% style="width:172px" %)/hierarchy|(% style="width:598px" %)Associates the parent and the child [[codes>>doc:sdmx:Glossary.Code.WebHome]].
68 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
69 +||/hierarchy|Associates the parent and the child codes.
71 71  )))
72 72  
73 73  == {{id name="_Toc370992"/}}4.4 Concept Scheme and Concepts ==
... ... @@ -74,83 +74,84 @@
74 74  
75 75  === {{id name="_Toc370993"/}}4.4.1 Class Diagram - Inheritance ===
76 76  
77 -[[image:1747732287949-594.png]]
78 -
79 79  **Figure 16 Class diagram of the Concept Scheme**
80 80  
81 81  === {{id name="_Toc370994"/}}4.4.2 Explanation of the Diagram ===
82 82  
83 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
80 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
84 84  
85 -* id
86 -* uri
87 -* urn
88 -* version
89 -* validFrom
90 -* validTo
82 +* id//  //
83 +* uri//  //
84 +* urn//  //
85 +* version//  //
86 +* validFrom//  //
87 +* validTo//  //
91 91  * isExternalReference
92 92  * registryURL
93 93  * structureURL
94 94  * repositoryURL
95 -* final
96 -* isPartial
92 +* final//  //
93 +* isPartial//  //
97 97  
98 -(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) inherits from Item and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
95 +Concept inherits from Item and has the following attributes:
99 99  
100 100  * id
101 101  * uri
102 102  * urn
103 103  
104 -Through the inheritance from //NameableArtefact// both ConceptScheme and (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown).
101 +Through the inheritance from //NameableArtefact// both ConceptScheme and Concept 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).
105 105  
106 -Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), and the (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) itself can have one or more child (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) in the (inherited) [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. Note that a child (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) can have only one parent (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) in this association.
103 +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.
107 107  
108 -A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a sub set of the full ConceptScheme.
105 +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 sub set of the full ConceptScheme.
109 109  
110 110  The way this works is described in section 3.5.3.1 on ItemScheme.
111 111  
112 112  === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship ===
113 113  
114 -[[image:1747732242162-856.png]]
111 +**Figure 17: Relationship class diagram of the Concept Scheme**
115 115  
116 -**Figure 17: Relationship class diagram of the [[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]**
117 -
118 118  === {{id name="_Toc370996"/}}4.4.4 Explanation of the diagram ===
119 119  
120 120  ==== 4.4.4.1 Narrative ====
121 121  
122 -The ConceptScheme can have one or more (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%). A (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) can have zero or more child (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), thus supporting a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] of (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%). Note that a child (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) can have only one parent (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) in this association. The purpose of the [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] is to relate (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) that have a semantic relationship: for example a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%), or a [[CONTACT >>doc:Glossary.Contact.WebHome]]may have a PRIMARY_CONTACT as a child (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%). It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the MetadataStructureDefinition.
117 +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
123 123  
124 -The (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) when used on a structure like a DataStructureDefinition or a MetadataStructureDefinition, unless the specification of the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] is overridden in the relevant structure definition. In a hierarchical ConceptScheme the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] is inherited from the parent (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) unless overridden at the [[level>>doc:Glossary.Level.WebHome]] of the child (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%).
119 +MetadataStructureDefinition.
125 125  
126 -Note that the ConceptScheme is used as the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] of the MeasureDimension in a DataStructureDefinition (see 5.3.2). Each (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) in this ConceptScheme is a specific [[measure>>doc:sdmx:Glossary.Measure.WebHome]], each of which can be given a coreRepresentation. Thus the valid format of the observation for each [[measure>>doc:sdmx:Glossary.Measure.WebHome]] when reported in a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] for the MeasureDimension is specified in the (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%). This allows a different format for each [[measure>>doc:sdmx:Glossary.Measure.WebHome]]. This is covered in more detail in 5.3.
121 +The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a
127 127  
128 -The [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] is documented in more detail in the section on the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Base.
123 +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.
129 129  
130 -The (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) may be related to a (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) described in terms of the ISO/IEC 11179 standard. The ISOConceptReference identifies this (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) and [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] in which it is contained.
125 +Note that the ConceptScheme is used as the Representation of the MeasureDimension in a DataStructureDefinition (see 5.3.2). Each Concept in this ConceptScheme is a specific measure, each of which can be given a coreRepresentation. Thus the valid format of the observation for each measure when reported in a data set for the MeasureDimension is specified in the Concept. This allows a different format for each measure. This is covered in more detail in 5.3.
131 131  
127 +The Representation is documented in more detail in the section on the SDMX Base.
128 +
129 +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.
130 +
132 132  ==== 4.4.4.2 Definitions ====
133 133  
133 +:
134 +
134 134  (((
135 -(% style="width:931.294px" %)
136 -|(% style="width:195px" %)**Class**|(% style="width:210px" %)**Feature**|(% style="width:522px" %)**Description**
137 -|(% style="width:195px" %)ConceptScheme|(% style="width:210px" %)(((
136 +|**Class**|**Feature**|**Description**
137 +|ConceptScheme|(((
138 138  Inherits from
139 139  
140 140  //ItemScheme//
141 -)))|(% style="width:522px" %)The descriptive information for an arrangement or division of (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) into groups based on characteristics, which the objects have in common.
142 -|(% style="width:195px" %)(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]]|(% style="width:210px" %)(((
141 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
142 +|Concept|(((
143 143  Inherits from
144 144  
145 145  //Item//
146 -)))|(% style="width:522px" %)A (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) is a unit of knowledge created by a unique combination of characteristics.
147 -|(% style="width:195px" %) |(% style="width:210px" %)/hierarchy|(% style="width:522px" %)Associates the parent and the child (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%).
148 -|(% style="width:195px" %) |(% style="width:210px" %)coreRepresentation|(% style="width:522px" %)Associates a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]].
149 -|(% style="width:195px" %) |(% style="width:210px" %)+ISOConcept|(% style="width:522px" %)Association to an ISO (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) reference.
150 -|(% style="width:195px" %)ISOConceptReference|(% style="width:210px" %) |(% style="width:522px" %)The identity of an ISO (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) definition.
151 -|(% style="width:195px" %) |(% style="width:210px" %)conceptAgency|(% style="width:522px" %)The [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] of the [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] containing the (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%).
152 -|(% style="width:195px" %) |(% style="width:210px" %)conceptSchemeID|(% style="width:522px" %)The identifier of the [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]].
153 -|(% style="width:195px" %) |(% style="width:210px" %)conceptID|(% style="width:522px" %)The identifier of the (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%).
146 +)))|A concept is a unit of knowledge created by a unique combination of characteristics.
147 +||/hierarchy|Associates the parent and the child concept.
148 +||coreRepresentation|Associates a Representation.
149 +||+ISOConcept|Association to an ISO concept reference.
150 +|ISOConceptReference||The identity of an ISO concept definition.
151 +||conceptAgency|The maintenance agency of the concept scheme containing the concept.
152 +||conceptSchemeID|The identifier of the concept scheme.
153 +||conceptID|The identifier of the concept.
154 154  )))
155 155  
156 156  == {{id name="_Toc370997"/}}4.5 Category Scheme ==
... ... @@ -157,23 +157,19 @@
157 157  
158 158  === {{id name="_Toc370998"/}}4.5.1 Context ===
159 159  
160 -This package defines the structure that supports the definition of and relationships between [[categories>>doc:sdmx:Glossary.Category.WebHome]] in a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]. It is similar to the package for [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]. An example of a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] is one which categorises data – sometimes known as a subject matter domain scheme or a data [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]. Importantly, as will be seen later, the individual nodes in the scheme (the “[[categories>>doc:sdmx:Glossary.Category.WebHome]]”) can be associated to any set of IdentiableArtefacts in a Categorisation.
160 +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.
161 161  
162 162  === {{id name="_Toc370999"/}}4.5.2 Class diagram - Inheritance ===
163 163  
164 -(% class="wikigeneratedid" id="H" %)
165 -[[image:1747732448450-721.png]]
164 +====== Figure 18 Inheritance Class diagram of the Category Scheme ======
166 166  
167 -(% class="wikigeneratedid" id="HFigure18InheritanceClassdiagramoftheCategoryScheme" %)
168 -**Figure 18 Inheritance Class diagram of the [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]**
169 -
170 170  === {{id name="_Toc371000"/}}4.5.3 Explanation of the Diagram ===
171 171  
172 172  ==== 4.5.3.1 Narrative ====
173 173  
174 -The [[categories>>doc:sdmx:Glossary.Category.WebHome]] are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
170 +The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
175 175  
176 -* id
172 +* id//  //
177 177  * uri
178 178  * urn
179 179  * version
... ... @@ -183,49 +183,53 @@
183 183  * structureURL
184 184  * serviceURL
185 185  * final
186 -* isPartial
182 +* isPartial//  //
187 187  
188 -[[Category>>doc:sdmx:Glossary.Category.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]:
184 +Category inherits from //Item// and has the following attributes:
189 189  
190 190  * //id//
191 191  * //uri//
192 192  * //urn//
193 193  
194 -Both CategoryScheme and [[Category>>doc:sdmx:Glossary.Category.WebHome]] have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary.Annotation.WebHome]] to support notes (not shown on the model).
190 +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).
195 195  
196 -Through the inheritance the CategoryScheme comprise one or more [[Categorys>>doc:sdmx:Glossary.Category.WebHome]], and the [[Category>>doc:sdmx:Glossary.Category.WebHome]] itself can have one or more child [[Category>>doc:sdmx:Glossary.Category.WebHome]] in the (inherited) [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. Note that a child [[Category>>doc:sdmx:Glossary.Category.WebHome]] can have only one parent [[Category>>doc:sdmx:Glossary.Category.WebHome]] in this association.
192 +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.
197 197  
198 -A partial CategoryScheme (where isPartial is set to “true”) is identical to a CategoryScheme and contains the [[Category>>doc:sdmx:Glossary.Category.WebHome]] and associated names and descriptions, just as in a normal CategoryScheme. However, its content is a sub set of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
194 +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 sub set of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
199 199  
200 200  === {{id name="_Toc371001"/}}4.5.4 Class diagram - Relationship ===
201 201  
202 -[[image:1747732486733-495.png]]
198 +**Figure 19: Relationship Class diagram of the Category Scheme**
203 203  
204 -**Figure 19: Relationship Class diagram of the [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]**
200 +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
205 205  
206 -The CategoryScheme can have one or more [[Categorys>>doc:sdmx:Glossary.Category.WebHome]]. The [[Category>>doc:sdmx:Glossary.Category.WebHome]] is Identifiable and has identity information. A [[Category>>doc:sdmx:Glossary.Category.WebHome]] can have zero or more child [[Categorys>>doc:sdmx:Glossary.Category.WebHome]], thus supporting a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] of [[Categorys>>doc:sdmx:Glossary.Category.WebHome]]. Any IdentifiableArtefact can be +categorisedBy a [[Category>>doc:sdmx:Glossary.Category.WebHome]]. This is achieved by means of a Categorisation. Each Categorisation can associate one IdentifiableArtefact with one [[Category>>doc:sdmx:Glossary.Category.WebHome]]. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same [[Category>>doc:sdmx:Glossary.Category.WebHome]]. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the [[Category>>doc:sdmx:Glossary.Category.WebHome]]. From an implementation perspective this is necessary as Categorisation has no affect on the versioning of either the [[Category>>doc:sdmx:Glossary.Category.WebHome]] or the IdentifiableArtefact.
202 +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.
207 207  
208 208  ==== 4.5.4.1 Definitions ====
209 209  
206 +:
207 +
210 210  (((
211 -(% style="width:965.294px" %)
212 -|(% style="width:171px" %)**Class**|(% style="width:213px" %)**Feature**|(% style="width:577px" %)**Description**
213 -|(% style="width:171px" %)CategoryScheme|(% style="width:213px" %)(((
209 +|**Class**|**Feature**|**Description**
210 +|CategoryScheme|(((
214 214  Inherits from
212 +
215 215  //ItemScheme//
216 -)))|(% style="width:577px" %)The descriptive information for an arrangement or division of [[categories>>doc:sdmx:Glossary.Category.WebHome]] into groups based on characteristics, which the objects have in common.
217 -|(% style="width:171px" %) |(% style="width:213px" %)/items|(% style="width:577px" %)Associates the [[categories>>doc:sdmx:Glossary.Category.WebHome]].
218 -|(% style="width:171px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]]|(% style="width:213px" %)(((
214 +)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
215 +||/items|Associates the categories.
216 +|Category|(((
219 219  Inherits from
218 +
220 220  //Item//
221 -)))|(% style="width:577px" %)An item at any [[level>>doc:Glossary.Level.WebHome]] within a classification, typically tabulation [[categories>>doc:sdmx:Glossary.Category.WebHome]], sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
222 -|(% style="width:171px" %) |(% style="width:213px" %)/hierarchy|(% style="width:577px" %)Associates the parent and the child [[Category>>doc:sdmx:Glossary.Category.WebHome]].
223 -|(% style="width:171px" %)Categorisation|(% style="width:213px" %)(((
220 +)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
221 +||/hierarchy|Associates the parent and the child Category.
222 +|Categorisation|(((
224 224  Inherits from
224 +
225 225  MaintainableArtefact
226 -)))|(% style="width:577px" %)Associates anIdentifableArtefact with a [[Category>>doc:sdmx:Glossary.Category.WebHome]].
227 -|(% style="width:171px" %) |(% style="width:213px" %)+categorisedArtefact|(% style="width:577px" %)Associates the IdentifableArtefact.
228 -|(% style="width:171px" %) |(% style="width:213px" %)+categorisedBy|(% style="width:577px" %)Associates the [[Category>>doc:sdmx:Glossary.Category.WebHome]].
226 +)))|Associates anIdentifableArtefact with a Category.
227 +||+categorisedArtefact|Associates the IdentifableArtefact.
228 +||+categorisedBy|Associates the Category.
229 229  )))
230 230  
231 231  == {{id name="_Toc371002"/}}4.6 Organisation Scheme ==
... ... @@ -234,8 +234,7 @@
234 234  
235 235  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_dcd0149.png||height="456" width="580"]]
236 236  
237 -(% class="wikigeneratedid" id="HFigure20TheOrganisationSchemeclassdiagram" %)
238 -**Figure 20 The Organisation Scheme class diagram**
237 +====== Figure 20 The Organisation Scheme class diagram ======
239 239  
240 240  === {{id name="_Toc371004"/}}4.6.2 Explanation of the Diagram ===
241 241  
... ... @@ -245,81 +245,94 @@
245 245  
246 246  The //OrganisationScheme// can be one of four types:
247 247  
248 -1. AgencyScheme – contains Agency which is restricted to a flat list of agencies (i.e. there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]). Note that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] system of (Maintenance) Agency can be hierarchic and this is explained in more detail in the separate document “Technical Notes”.
249 -1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e. there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
250 -1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e. there is no [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]).
251 -1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /[[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association from Organisation.
247 +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 separate document “Technical Notes”.
248 +1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e. there is no hierarchy).
249 +1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e. there is no hierarchy).
250 +1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
252 252  
253 -[[Reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] can be attached to the //Organisation //by means of the metadata attachment mechanism. This mechanism is explained in the [[Reference Metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] section of this document (see section 7). This means that the model does not specify the specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] that can be attached to a DataProvider, DataConsumer,OrganisationUnit or Agency, except for limited [[Contact >>doc:Glossary.Contact.WebHome]]information.
252 +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, DataConsumer,OrganisationUnit or Agency, except for limited Contact information.
254 254  
255 255  A partial //OrganisationScheme// (where isPartial is set to “true”) is identical to a //OrganisationScheme// and contains the Organisation and associated names and descriptions, just as in a normal //OrganisationScheme// However, its content is a sub set of the full //OrganisationScheme//. The way this works is described in section 3.5.3.1 on ItemScheme.
256 256  
257 257  ==== 4.6.2.2 Definitions ====
258 258  
259 -(% style="width:845.294px" %)
260 -|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description**
261 -|(% style="width:181px" %)//OrganisationScheme//|(% style="width:217px" %)(((
258 +|**Class**|**Feature**|**Description**
259 +|//OrganisationScheme//|(((
262 262  Abstract Class Inherits from
261 +
263 263  //ItemScheme//
263 +
264 264  Sub classes are:
265 +
265 265  AgencyScheme
267 +
266 266  DataProviderScheme
269 +
267 267  DataConsumerScheme
271 +
268 268  OrganisationUnitScheme
269 -)))|(% style="width:429px" %)A maintained collection of Organisations.
270 -|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme.
271 -|(% style="width:181px" %)//Organisation//|(% style="width:217px" %)(((
273 +)))|A maintained collection of Organisations.
274 +||/items|Association to the Organisations in the scheme.
275 +|//Organisation//|(((
272 272  Inherits from
277 +
273 273  //Item//
279 +
274 274  Sub classes are:
281 +
275 275  Agency
283 +
276 276  DataProvider
285 +
277 277  DataConsumer
287 +
278 278  OrganisationUnit
279 -)))|(% style="width:429px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
280 -|(% style="width:181px" %) |(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the [[Contact>>doc:Glossary.Contact.WebHome]] information.
281 -|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations.
282 -|(% style="width:181px" %)(% style="color:#e74c3c" %)Contact|(% style="width:217px" %) |(% style="width:429px" %)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.
283 -|(% style="width:181px" %) |(% style="width:217px" %)name|(% style="width:429px" %)The designation of the [[Contact>>doc:Glossary.Contact.WebHome]] person by a linguistic expression.
284 -|(% style="width:181px" %) |(% style="width:217px" %)organisationUnit|(% style="width:429px" %)The designation of the organisational structure by a linguistic expression, within which [[Contact>>doc:Glossary.Contact.WebHome]] person works.
285 -|(% style="width:181px" %) |(% style="width:217px" %)responsibility|(% style="width:429px" %)The function of the contact person with respect to the organisation role for which this person is the [[Contact>>doc:Glossary.Contact.WebHome]].
286 -|(% style="width:181px" %) |(% style="width:217px" %)telephone|(% style="width:429px" %)The [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] of the [[Contact>>doc:Glossary.Contact.WebHome]].
287 -|(% style="width:181px" %) |(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the [[Contact>>doc:Glossary.Contact.WebHome]].
288 -|(% style="width:181px" %) |(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the [[Contact>>doc:Glossary.Contact.WebHome]].
289 -|(% style="width:181px" %) |(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the [[Contact>>doc:Glossary.Contact.WebHome]].
290 -|(% style="width:181px" %) |(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the [[Contact>>doc:Glossary.Contact.WebHome]].
291 -|(% style="width:181px" %)AgencyScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Maintenace Agencies.
292 -|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] in the scheme.
293 -|(% style="width:181px" %)DataProviderScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]].
294 -|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] in the scheme.
295 -|(% style="width:181px" %)DataConsumerScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]].
296 -|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the [[Data Consumers>>doc:sdmx:Glossary.Data consumer.WebHome]] in the scheme.
297 -|(% style="width:181px" %)OrganisationUnitScheme|(% style="width:217px" %) |(% style="width:429px" %)A maintained collection of Organisation Units.
298 -|(% style="width:181px" %) |(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme.
299 -|(% style="width:181px" %)Agency|(% style="width:217px" %)(((
289 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
290 +||+contact|Association to the Contact information.
291 +||/hierarchy|Association to child Organisations.
292 +|Contact||An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
293 +||name|The designation of the Contact person by a linguistic expression.
294 +||organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
295 +||responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
296 +||telephone|The telephone number of the Contact.
297 +||fax|The fax number of the Contact.
298 +||email|The Internet e-mail address of the Contact.
299 +||X400|The X400 address of the Contact.
300 +||uri|The URL address of the Contact.
301 +|AgencyScheme||A maintained collection of Maintenace Agencies.
302 +||/items|Association to the Maintenance Agency in the scheme.
303 +|DataProviderScheme||A maintained collection of Data Providers.
304 +||/items|Association to the Data Providers in the scheme.
305 +|DataConsumerScheme||A maintained collection of Data Consumers.
306 +||/items|Association to the Data Consumers in the scheme.
307 +|OrganisationUnitScheme||A maintained collection of Organisation Units.
308 +||/items|Association to the Organisation Units in the scheme.
309 +|Agency|(((
300 300  Inherits from
311 +
301 301  //Organisation//
302 -)))|(% style="width:429px" %)Responsible agency for maintaining [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] such as statistical classifications, glossaries, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] such as Data and [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], (% style="color:#e74c3c" %)[[Concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and [[Code lists>>doc:sdmx:Glossary.Code list.WebHome]].
303 -|(% style="width:181px" %)DataProvider|(% style="width:217px" %)(((
313 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
314 +|DataProvider|(((
304 304  Inherits from
316 +
305 305  //Organisation//
306 -)))|(% style="width:429px" %)An organisation that produces data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
307 -|(% style="width:181px" %)DataConsumer|(% style="width:217px" %)(((
318 +)))|An organisation that produces data or reference metadata.
319 +|DataConsumer|(((
308 308  Inherits from
321 +
309 309  //Organisation//
310 -)))|(% style="width:429px" %)An organisation using data as input for further processing.
311 -|(% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)(((
323 +)))|An organisation using data as input for further processing.
324 +|OrganisationUnit|(((
312 312  Inherits from
313 -//Organisation//
314 -)))|(% style="width:429px" %)A designation in the organisational structure.
315 -|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisation Units
316 316  
327 +//Organisation //
328 +)))|A designation in the organisational structure.
329 +||/hierarchy|Association to child Organisation Units
330 +
317 317  == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy ==
318 318  
319 319  === {{id name="_Toc371006"/}}4.7.1 Class Diagram ===
320 320  
321 -[[image:1747732548003-370.png]]
322 -
323 323  **Figure 21: Class diagram of the Reporting Taxonomy**
324 324  
325 325  === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram ===
... ... @@ -328,13 +328,14 @@
328 328  
329 329  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.
330 330  
331 -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 DataflowDefinition, or MetadataflowDefinition, and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each [[Category>>doc:sdmx:Glossary.Category.WebHome]] that is linked in this way will be linked to the same class (e.g. all [[Category>>doc:sdmx:Glossary.Category.WebHome]] in the scheme will link to a DataflowDefinition). 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:
343 +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 DataflowDefinition, or MetadataflowDefinition, 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 DataflowDefinition). 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:
332 332  
333 333  Section 1
334 334  
335 -1. linked to DatafowDefinition_1
336 -1. linked to DatafowDefinition_2
347 +~1. linked to DatafowDefinition_1
337 337  
349 +2 linked to DatafowDefinition_2
350 +
338 338  Section 2
339 339  
340 340  1. linked toDatafowDefinition_3
... ... @@ -346,19 +346,22 @@
346 346  
347 347  ==== 4.7.2.2 Definitions ====
348 348  
349 -(% style="width:1033.29px" %)
350 -|**Class**|**Feature**|(% style="width:687px" %)**Description**
362 +|**Class**|**Feature**|**Description**
351 351  |ReportingTaxonomy|(((
352 352  Inherits from
353 -//ItemScheme//
354 -)))|(% style="width:687px" %)A scheme which defines the composition structure of a data report where each [[component>>doc:sdmx:Glossary.Component.WebHome]] can be described by an independent [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition or Metdataflow Definition.
355 -| |items|(% style="width:687px" %)Associates the Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]]
365 +
366 +//ItemScheme //
367 +)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow Definition or Metdataflow Definition.
368 +||items|Associates the Reporting Category
356 356  |ReportingCategory|(((
357 357  Inherits from
371 +
358 358  //Item//
359 -)))|(% style="width:687px" %)A [[component>>doc:sdmx:Glossary.Component.WebHome]] that gives structure to the report and links to data and metadata.
360 -| |hierarchy|(% style="width:687px" %)Associates child Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]].
361 -| |+flow|(% style="width:687px" %)Association to the data and [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]] that link to metadata about the provisioning and related data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], and the structures that define them.
362 -| |+structure|(% style="width:687px" %)(((
363 -Association to the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which define the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] describing the data and metadata that are contained at this part of the report.
373 +)))|A component that gives structure to the report and links to data and metadata.
374 +||hierarchy|Associates child Reporting Category.
375 +||+flow|Association to the data and metadata flows that link to metadata about the provisioning and related data and metadata sets, and the structures that define them.
376 +||+structure|(((
377 +Association to the Data Structure Definition and Metadata Structure
378 +
379 +Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
364 364  )))
1747732242162-856.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -21.8 KB
Content
1747732287949-594.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -42.4 KB
Content
1747732337979-971.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -39.3 KB
Content
1747732448450-721.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -34.0 KB
Content
1747732486733-495.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -18.6 KB
Content
1747732548003-370.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -48.9 KB
Content
SDMX_2-1_SECTION_2_InformationModel_2020-07_dcd0149.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -122.6 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,1 +1,0 @@
1 -5