Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Helena K. on 2026/06/08 16:44
From version 36.5
edited by Helena K.
on 2026/06/08 16:28
Change comment: There is no comment for this version
To version 3.1
edited by Helena K.
on 2025/06/07 00:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,172 +1,176 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 +=== 4.1 Introduction ===
4 4  
5 -== 4.1 Introduction ==
3 +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:
6 6  
7 -The structures that are an arrangement of objects into [[hierarchies>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
5 +Codelist
8 8  
9 -[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]
10 10  ConceptScheme
8 +
11 11  CategoryScheme
12 -AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
10 +
11 +AgencyScheme, DataProviderScheme, MetadataProviderScheme,
12 +
13 +DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
14 +
13 13  ReportingTaxonomy
16 +
14 14  TransformationScheme
18 +
15 15  RulesetScheme
20 +
16 16  UserDefinedOperatorScheme
22 +
17 17  NamePersonalisationScheme
24 +
18 18  CustomTypeScheme
26 +
19 19  VtlMappingScheme
20 20  
21 -Note that the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] related schemes (the last 6 of the above list) are detailed in a dedicated section below ([[section 15>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.15 Validation and Transformation Language.WebHome]]).
29 +Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
22 22  
23 -== 4.2 Inheritance View ==
31 +=== 4.2 Inheritance View ===
24 24  
25 25  The inheritance and relationship views are shown together in each of the diagrams in the specific sections below.
26 26  
27 -== 4.3 Codelist ==
35 +=== 4.3 Codelist ===
28 28  
29 -=== 4.3.1 Class Diagram ===
37 +==== 4.3.1 Class Diagram ====
30 30  
31 -[[image:image42.png]]
39 +[[image:1749246291075-895.jpeg]]
32 32  
33 33  **Figure 16: Class diagram of the Codelist**
34 34  
35 -=== 4.3.2 Explanation of the Diagram ===
43 +==== 4.3.2 Explanation of the Diagram ====
36 36  
37 -==== 4.3.2.1 Narrative ====
45 +===== 4.3.2.1 Narrative =====
38 38  
39 -The [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]: id uri urn [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] validFrom validTo [[isExternalReference>>doc:sdmx:Glossary 2\.1.isExternalReference.WebHome]] serviceURL structureURL isPartial
47 +The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
40 40  
41 -The [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]:
49 +The Code inherits from //Item// and has the following attributes:
42 42  
43 -id
44 -uri
45 -urn
51 +id uri urn
46 46  
47 -Both [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] to support notes (not shown).
53 +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).
48 48  
49 -Through the inheritance the [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] comprise one or more [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]], and the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] itself can have one or more child [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in the (inherited) [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] association. Note that a child [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] can have only one parent [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in this association. A more complex Hierarhcy, which allows multiple parents is described later.
55 +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.
50 50  
51 -A partial [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] (where isPartial is set to 'true') is identical to a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and contains the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] and associated names and descriptions, just as in a normal [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. However, its content is a subset of the full [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on //ItemScheme//.
57 +A partial Codelist (where isPartial is set to 'true') is identical to a Codelist and contains the Code and associated names and descriptions, just as in a normal Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
52 52  
53 -==== 4.3.2.2 Definitions ====
59 +===== 4.3.2.2 Definitions =====
54 54  
55 -(% style="width:912.835px" %)
56 -|**Class**|**Feature**|(% style="width:656px" %)**Description**
57 -|(%%)(% style="background-color:#d35400" %)[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]|(((
61 +|**Class**|**Feature**|**Description**
62 +|Codelist|(((
58 58  Inherits from
64 +
59 59  //ItemScheme//
60 -)))|(% style="width:656px" %)A list from which some statistical [[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] (coded [[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]]) take their values.
61 -|[[Code>>doc:Glossary 2\.1.Code.WebHome]]|(((
66 +)))|A list from which some statistical concepts (coded concepts) take their values.
67 +|Code|(((
62 62  Inherits from
69 +
63 63  Item
64 -)))|(% style="width:656px" %)A [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] independent set of letters, numbers or symbols that represent a [[concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] whose meaning is described in a natural [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]].
65 -| |[[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]|(% style="width:656px" %)Associates the parent and the child [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]].
66 -| |extends|(% style="width:656px" %)Associates a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] with any [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that it may extend.
71 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
72 +| |hierarchy|Associates the parent and the child codes.
73 +| |extends|Associates a Codelist with any Codelists that it may extend.
67 67  
68 68  ==== 4.3.3 Class Diagram – Codelist Extension ====
69 69  
70 -[[image:image43.png]]
77 +[[image:1749246291156-936.jpeg]]
71 71  
72 72  **Figure 17: Class diagram for Codelist Extension**
73 73  
74 -==== 4.3.3.1 Narrative ====
81 +===== 4.3.3.1 Narrative =====
75 75  
76 -A [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] may extend other [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] for conflict resolution of [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]]. Besides that, the prefix property is used to ensure uniqueness of inherited [[Codes>>doc:sdmx:Glossary 2\.1.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>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] in case conflicting [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] from the extended [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].
83 +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[[^^~[1~]^^>>path:#_ftn1]] Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.
77 77  
78 -The [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] selection classes may have MemberValues in order to specify the subset of the [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] that should be included or excluded from the extended [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. A MemberValue may have a value that corresponds to a [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]], including its children [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] (via the cascadeValues property), or even include instances of the wildcard character ‘%’ in order to point to a set of [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] with common parts in their identifiers.
85 +The code selection classes may have MemberValues in order to specify the subset of the Codes that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a Code, including its children Codes (via the cascadeValues property), or even include instances of the wildcard character ‘%’ in order to point to a set of Codes with common parts in their identifiers.
79 79  
80 -==== 4.3.3.2 Definitions ====
87 +**4.3.3.2 Definitions**
81 81  
82 -(% style="width:970.835px" %)
83 -|**Class**|**Feature**|(% style="width:655px" %)**Description**
84 -|CodelistExtension| |(% style="width:655px" %)The association between [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that may extend other [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].
85 -| |prefix|(% style="width:655px" %)A prefix to be used for a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] used in a extension, in order to avoid [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] Conflicts.
86 -| |sequence|(% style="width:655px" %)(((
87 -The order that will be used when extending a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], for resolving [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] conflicts. The latest [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] used overrides any previous [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].
89 +|**Class**|**Feature**|**Description**
90 +|CodelistExtension| |The association between Codelists that may extend other Codelists.
91 +| |prefix|A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
92 +| |sequence|(((
93 +The order that will be used when extending a
94 +
95 +Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
88 88  )))
89 -|InclusiveCodeSelection| |(% style="width:655px" %)The subset of [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] to be included when extending a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].
90 -|ExclusiveCodeSelection| |(% style="width:655px" %)The subset of [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] to be excluded when extending a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].
97 +|InclusiveCodeSelection| |The subset of Codes to be included when extending a Codelist.
98 +|ExclusiveCodeSelection| |The subset of Codes to be excluded when extending a Codelist.
91 91  |MemberValue|(((
92 92  Inherits from:
101 +
93 93  //SelectionValue//
94 -)))|(% style="width:655px" %)A collection of values based on [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] and their children.
95 -| |cascadeValues|(% style="width:655px" %)A property to indicate if the child [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] of the selected [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] shall be included in the selection. It is also possible to include children and exclude the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] by using the 'excluderoot' value.
96 -| |value|(% style="width:655px" %)The value of the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] to include in the selection. It may include the ‘%’ character as a wildcard.
103 +)))|A collection of values based on Codes and their children.
104 +| |cascadeValues|A property to indicate if the child Codes of the selected Code shall be included in the selection. It is also possible to include children and exclude the Code by using the 'excluderoot' value.
105 +| |value|The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
97 97  
98 -=== 4.3.4 Class Diagram – Geospatial Codelist ===
107 +==== 4.3.4 Class Diagram – Geospatial Codelist ====
99 99  
100 100  The geospatial support is implemented via an extension of the normal Codelist. This is illustrated in the following diagrams.
101 101  
102 -[[image:image44.png]]
111 +[[image:1749246291164-838.jpeg]]
103 103  
104 104  **Figure 18: Inheritance for the GeoCodelist**
105 105  
106 -[[image:image45.png]]
115 +[[image:1749246291175-231.jpeg]]
107 107  
108 108  **Figure 19: Class diagram for Geospatial Codelist**
109 109  
110 -==== 4.3.4.1 Narrative ====
119 +===== 4.3.4.1 Narrative =====
111 111  
112 -A //GeoCodelist// is a specialisation of [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that includes geospatial information, by comprising a set of special [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]], i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property:
121 +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:
113 113  
114 114  GeographicCodelist
115 115  
116 116  GeoGridCodelist
117 117  
118 -The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] that follows a pattern to represent a geo feature set.
127 +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.
119 119  
120 120  The latter, i.e., GeoGridCodelist, comprises a set of GridCodes, which are related to the gridDefinition specified in the GeoGridCodelist.
121 121  
122 -==== 4.3.4.2 Definitions ====
131 +===== 4.3.4.2 Definitions =====
123 123  
124 -(% style="width:960.835px" %)
125 -|**Class**|**Feature**|(% style="width:559px" %)**Description**
133 +|**Class**|**Feature**|**Description**
126 126  |//GeoCodelist//|(((
127 127  Abstract Class Sub Classes:
136 +
128 128  GeographicCodelist
138 +
129 129  GeoGridCodelist
130 -)))|(% style="width:559px" %)The abstract class that represents a special type of [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], which includes geospatial information.
131 -| |geoType|(% style="width:559px" %)The type of Geo [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that the [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] will become.
140 +)))|The abstract class that represents a special type of Codelist, which includes geospatial information.
141 +| |geoType|The type of Geo Codelist that the Codelist will become.
132 132  |//GeoRefCode//|(((
133 133  Abstract Class
144 +
134 134  Sub Classes:
146 +
135 135  GeoFeatureSetCode
148 +
136 136  GeoGridCode
137 -)))|(% style="width:559px" %)The abstract class that represents a special type of [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]], which includes geospatial information.
138 -|GeographicCodelist| |(% style="width:559px" %)A special [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
139 -|GeoGridCodelist| |(% style="width:559px" %)A [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
140 -| |gridDefinition|(% style="width:559px" %)Contains a regular expression string corresponding to the grid definition for the GeoGridCodelist.
141 -|GeoFeatureSetCode| |(% style="width:559px" %)A [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] that has a geo feature set.
142 -| |value|(% style="width:559px" %)The geo feature set of the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]], which represents a set of points defining a feature in a format defined a predefined pattern (see section 6).
143 -|GeoGridCode| |(% style="width:559px" %)A [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] that represents a Geo Grid Cell belonging in a specific grid definition.
144 -| |geoCell|(% style="width:559px" %)The value used to assign the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] to one cell in the grid.
150 +)))|The abstract class that represents a special type of Code, which includes geospatial information.
151 +|GeographicCodelist| |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
152 +|GeoGridCodelist| |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
153 +| |gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
154 +|GeoFeatureSetCode| |A Code that has a geo feature set.
155 +| |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).
156 +|GeoGridCode| |A Code that represents a Geo Grid Cell belonging in a specific grid definition.
157 +| |geoCell|The value used to assign the Code to one cell in the grid.
145 145  
146 -== 4.4 ValueList ==
159 +=== 4.4 ValueList ===
147 147  
148 -=== 4.4.1 Class Diagram ===
161 +==== 4.4.1 Class Diagram ====
149 149  
150 -[[image:image46.png]]
163 +[[image:1749246291179-291.jpeg]]
151 151  
152 152  **Figure 20: Class diagram of the ValueList**
153 153  
154 -=== 4.4.2 Explanation of the Diagram ===
167 +==== 4.4.2 Explanation of the Diagram ====
155 155  
156 -==== 4.4.2.1 Narrative ====
169 +===== 4.4.2.1 Narrative =====
157 157  
158 158  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
159 159  
160 -id
161 -uri
162 -urn
163 -version
164 -validFrom
165 -validTo
166 -isExternalReference
167 -registryURL
168 -structureURL
169 -repositoryURL
173 +id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
170 170  
171 171  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
172 172  
... ... @@ -174,62 +174,49 @@
174 174  
175 175  The ValueList can have one or more ValueItems.
176 176  
177 -==== 4.4.2.2 Definitions ====
181 +===== 4.4.2.2 Definitions =====
178 178  
179 -(% style="width:929.835px" %)
180 -|**Class**|(% style="width:175px" %)**Feature**|(% style="width:632px" %)**Description**
181 -|ValueList|(% style="width:175px" %)(((
183 +|**Class**|**Feature**|**Description**
184 +|ValueList|(((
182 182  Inherits from
186 +
183 183  //EnumeratedList//
184 -)))|(% style="width:632px" %)A list from which some statistical concepts (enumerated concepts) take their values.
185 -|ValueItem|(% style="width:175px" %)(((
188 +)))|A list from which some statistical concepts (enumerated concepts) take their values.
189 +|ValueItem|(((
186 186  Inherits from
191 +
187 187  //EnumeratedItem//
188 -)))|(% style="width:632px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
193 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
189 189  
190 -== 4.5 Concept Scheme and Concepts ==
195 +=== 4.5 Concept Scheme and Concepts ===
191 191  
192 -=== 4.5.1 Class Diagram - Inheritance ===
197 +==== 4.5.1 Class Diagram - Inheritance ====
193 193  
194 -[[image:image47.png]]
199 +[[image:1749246291184-799.jpeg]]
195 195  
196 196  **Figure 21 Class diagram of the Concept Scheme**
197 197  
198 -=== 4.5.2 Explanation of the Diagram ===
203 +==== 4.5.2 Explanation of the Diagram ====
199 199  
200 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
205 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits from Item and has the following attributes:
201 201  
202 -id
203 -uri
204 -urn
205 -version validFrom validTo
206 -isExternalReference
207 -registryURL
208 -structureURL
209 -repositoryURL
210 -isPartial
207 +id uri urn
211 211  
212 -Concept inherits from Item and has the following attributes:
213 -
214 -id
215 -uri
216 -urn
217 -
218 218  Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multilingual description, and an association to Annotation to support notes (not shown).
219 219  
220 220  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.
221 221  
222 -A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the Concept and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a subset of the full ConceptScheme. The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on ItemScheme.
213 +A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the Concept and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a subset of the full ConceptScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
223 223  
224 -=== 4.5.3 Class Diagram Relationship ===
215 +==== 4.5.3     Class Diagram Relationship ====
225 225  
226 -[[image:image48.png]]
217 +[[image:1749246291189-654.jpeg]]
227 227  
228 228  **Figure 22: Relationship class diagram of the Concept Scheme**
229 229  
230 -=== 4.5.4 Explanation of the diagram ===
221 +==== 4.5.4 Explanation of the diagram ====
231 231  
232 -==== 4.5.4.1 Narrative ====
223 +===== 4.5.4.1 Narrative =====
233 233  
234 234  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.
235 235  
... ... @@ -239,109 +239,103 @@
239 239  
240 240  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.
241 241  
242 -==== 4.5.4.2 Definitions ====
233 +===== 4.5.4.2 Definitions =====
243 243  
244 -(% style="width:912.835px" %)
245 -|(% style="width:170px" %)**Class**|(% style="width:184px" %)**Feature**|(% style="width:548px" %)**Description**
246 -|(% style="width:170px" %)(((
235 +|**Class**|**Feature**|**Description**
236 +|(((
247 247  ConceptScheme
248 -)))|(% style="width:184px" %)(((
238 +
239 +
240 +)))|(((
249 249  Inherits from
242 +
250 250  //ItemScheme//
251 -)))|(% style="width:548px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
252 -|(% style="width:170px" %)Concept|(% style="width:184px" %)(((
244 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
245 +|Concept|(((
253 253  Inherits from
247 +
254 254  //Item//
255 -)))|(% style="width:548px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
256 -|(% style="width:170px" %) |(% style="width:184px" %)/hierarchy|(% style="width:548px" %)Associates the parent and the child concept.
257 -|(% style="width:170px" %) |(% style="width:184px" %)coreRepresentation|(% style="width:548px" %)Associates a Representation.
258 -|(% style="width:170px" %) |(% style="width:184px" %)+ISOConcept|(% style="width:548px" %)Association to an ISO concept reference.
259 -|(% style="width:170px" %)ISOConceptReference|(% style="width:184px" %) |(% style="width:548px" %)The identity of an ISO concept definition.
260 -|(% style="width:170px" %) |(% style="width:184px" %)conceptAgency|(% style="width:548px" %)The maintenance agency of the concept scheme containing the concept.
261 -|(% style="width:170px" %) |(% style="width:184px" %)conceptSchemeID|(% style="width:548px" %)The identifier of the concept scheme.
262 -|(% style="width:170px" %) |(% style="width:184px" %)conceptID|(% style="width:548px" %)The identifier of the concept.
249 +)))|A concept is a unit of knowledge created by a unique combination of characteristics.
250 +| |/hierarchy|Associates the parent and the child concept.
251 +| |coreRepresentation|Associates a Representation.
252 +| |+ISOConcept|Association to an ISO concept reference.
253 +|ISOConceptReference| |The identity of an ISO concept definition.
254 +| |conceptAgency|The maintenance agency of the concept scheme containing the concept.
255 +| |conceptSchemeID|The identifier of the concept scheme.
256 +| |conceptID|The identifier of the concept.
263 263  
264 -== 4.6 Category Scheme ==
258 +=== 4.6 Category Scheme ===
265 265  
266 -=== 4.6.1 Context ===
260 +==== 4.6.1 Context ====
267 267  
268 268  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.
269 269  
270 -=== 4.6.2 Class diagram Inheritance ===
264 +==== 4.6.2 Class diagram Inheritance ====
271 271  
272 -[[image:image49.png]]
266 +[[image:1749246291193-743.jpeg]]
273 273  
274 274  **Figure 23 Inheritance Class diagram of the Category Scheme**
275 275  
276 -=== 4.6.3 Explanation of the Diagram ===
270 +===== 4.6.3    Explanation of the Diagram =====
277 277  
278 -==== 4.6.3.1 Narrative ====
272 +====== 4.6.3.1 Narrative ======
279 279  
280 280  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
281 281  
282 -id
283 -uri
284 -urn
285 -version
286 -validFrom
287 -validTo
288 -isExternalReference
289 -structureURL
290 -serviceURL
291 -isPartial
276 +id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
292 292  
293 293  Category inherits from //Item// and has the following attributes:
294 294  
295 -id
296 -uri
297 -urn
280 +id uri urn
298 298  
299 299  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).
300 300  
301 301  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.
302 302  
303 -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>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on ItemScheme.
286 +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.
304 304  
305 -=== 4.6.4 Class diagram Relationship ===
288 +===== 4.6.4     Class diagram Relationship =====
306 306  
307 -[[image:image50.png]]
290 +[[image:1749246291197-631.jpeg]]
308 308  
309 309  **Figure 24: Relationship Class diagram of the Category Scheme**
310 310  
311 311  The CategoryScheme can have one or more Categorys. The Category is Identifiable and has identity information. A Category can have zero or more child Categorys, thus supporting a hierarchy of Categorys. Any IdentifiableArtefact can be +categorisedBy a Category. This is achieved by means of a Categorisation. Each Categorisation can associate one IdentifiableArtefact with one Category. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same Category. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the Category. From an implementation perspective this is necessary as Categorisation has no effect on the versioning of either the CategoryScheme or the IdentifiableArtefact.
312 312  
313 -==== 4.6.4.1 Definitions ====
296 +====== 4.6.4.1 Definitions ======
314 314  
315 -(% style="width:935.835px" %)
316 -|**Class**|**Feature**|(% style="width:601px" %)**Description**
298 +|**Class**|**Feature**|**Description**
317 317  |CategoryScheme|(((
318 318  Inherits from
301 +
319 319  //ItemScheme//
320 -)))|(% style="width:601px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
321 -| |/items|(% style="width:601px" %)Associates the categories.
303 +)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
304 +| |/items|Associates the categories.
322 322  |Category|(((
323 323  Inherits from
307 +
324 324  //Item//
325 -)))|(% style="width:601px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
326 -| |/hierarchy|(% style="width:601px" %)Associates the parent and the child Category.
309 +)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
310 +| |/hierarchy|Associates the parent and the child Category.
327 327  |Categorisation|(((
328 328  Inherits from
313 +
329 329  //MaintainableArtefact//
330 -)))|(% style="width:601px" %)Associates an Identifable Artefact with a Category.
331 -| |+categorisedArtefact|(% style="width:601px" %)Associates the Identifable Artefact.
332 -| |+categorisedBy|(% style="width:601px" %)Associates the Category.
315 +)))|Associates an Identifable Artefact with a Category.
316 +| |+categorisedArtefact|Associates the Identifable Artefact.
317 +| |+categorisedBy|Associates the Category.
333 333  
334 -== 4.7 Organisation Scheme ==
319 +=== 4.7 Organisation Scheme ===
335 335  
336 -=== 4.7.1 Class Diagram ===
321 +==== Class Diagram ====
337 337  
338 -[[image:image51.png]]
323 +[[image:1749246291201-410.jpeg]]
339 339  
340 340  **Figure 25 The Organisation Scheme class diagram**
341 341  
342 -=== 4.7.2 Explanation of the Diagram ===
327 +===== 4.7.2    Explanation of the Diagram =====
343 343  
344 -==== 4.7.2.1 Narrative ====
329 +====== 4.7.2.1 Narrative ======
345 345  
346 346  The //OrganisationScheme// is abstract. It contains //Organisation// which is also abstract. The //Organisation// can have child //Organisation//.
347 347  
... ... @@ -351,96 +351,115 @@
351 351  1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
352 352  1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
353 353  1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
354 -1. (% style="background-color:#d35400" %)OrganisationUnitScheme(%%) – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
339 +1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
355 355  
356 356  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.
357 357  
358 -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>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on //ItemScheme//.
343 +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//.
359 359  
360 -==== 4.7.2.2 Definitions ====
345 +====== 4.7.2.2 Definitions ======
361 361  
362 -(% style="width:946.835px" %)
363 -|**Class**|**Feature**|(% style="width:540px" %)**Description**
347 +|**Class**|**Feature**|**Description**
364 364  |//OrganisationScheme//|(((
365 365  Abstract Class
350 +
366 366  Inherits from
352 +
367 367  //ItemScheme//
354 +
368 368  Sub classes are:
356 +
369 369  AgencyScheme
358 +
370 370  DataProviderScheme
360 +
371 371  MetadataProviderScheme
362 +
372 372  DataConsumerScheme
364 +
373 373  OrganisationUnitScheme
374 -)))|(% style="width:540px" %)A maintained collection of Organisations.
375 -| |/items|(% style="width:540px" %)Association to the Organisations in the scheme.
366 +)))|A maintained collection of Organisations.
367 +| |/items|Association to the Organisations in the scheme.
376 376  |//Organisation//|(((
377 377  Abstract Class
370 +
378 378  Inherits from
372 +
379 379  //Item//
374 +
380 380  Sub classes are:
376 +
381 381  Agency
378 +
382 382  DataProvider
380 +
383 383  MetadataProvider
382 +
384 384  DataConsumer
384 +
385 385  OrganisationUnit
386 -)))|(% style="width:540px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
387 -| |+contact|(% style="width:540px" %)Association to the Contact information.
388 -| |/hierarchy|(% style="width:540px" %)Association to child Organisations.
389 -|Contact| |(% style="width:540px" %)An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
390 -| |name|(% style="width:540px" %)The designation of the Contact person by a linguistic expression.
391 -| |organisationUnit|(% style="width:540px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
392 -| |responsibility|(% style="width:540px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
393 -| |telephone|(% style="width:540px" %)The telephone number of the Contact.
394 -| |fax|(% style="width:540px" %)The fax number of the Contact.
395 -| |email|(% style="width:540px" %)The Internet e-mail address of the Contact.
396 -| |X400|(% style="width:540px" %)The X400 address of the Contact.
397 -| |uri|(% style="width:540px" %)The URL address of the Contact.
398 -|AgencyScheme| |(% style="width:540px" %)A maintained collection of Maintenance Agencies.
399 -| |/items|(% style="width:540px" %)Association to the Maintenance Agency in the scheme.
400 -|DataProviderScheme| |(% style="width:540px" %)A maintained collection of Data Providers.
401 -| |/items|(% style="width:540px" %)Association to the Data Providers in the scheme.
402 -|MetadataProviderScheme| |(% style="width:540px" %)A maintained collection of Metadata Providers.
403 -| |/items|(% style="width:540px" %)Association to the Metadata Providers in the scheme.
404 -|DataConsumerScheme| |(% style="width:540px" %)A maintained collection of Data Consumers.
405 -| |/items|(% style="width:540px" %)Association to the Data Consumers in the scheme.
406 -|(%%)(% style="background-color:#d35400" %)OrganisationUnitScheme| |(% style="width:540px" %)A maintained collection of Organisation Units.
407 -| |/items|(% style="width:540px" %)Association to the Organisation Units in the scheme.
386 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
387 +| |+contact|Association to the Contact information.
388 +| |/hierarchy|Association to child Organisations.
389 +|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.
390 +| |name|The designation of the Contact person by a linguistic expression.
391 +| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
392 +| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
393 +| |telephone|The telephone number of the Contact.
394 +| |fax|The fax number of the Contact.
395 +| |email|The Internet e-mail address of the Contact.
396 +| |X400|The X400 address of the Contact.
397 +| |uri|The URL address of the Contact.
398 +|AgencyScheme| |A maintained collection of Maintenance Agencies.
399 +| |/items|Association to the Maintenance Agency in the scheme.
400 +|DataProviderScheme| |A maintained collection of Data Providers.
401 +| |/items|Association to the Data Providers in the scheme.
402 +|MetadataProviderScheme| |A maintained collection of Metadata Providers.
403 +| |/items|Association to the Metadata Providers in the scheme.
404 +|DataConsumerScheme| |A maintained collection of Data Consumers.
405 +| |/items|Association to the Data Consumers in the scheme.
406 +|OrganisationUnitScheme| |A maintained collection of Organisation Units.
407 +| |/items|Association to the Organisation Units in the scheme.
408 408  |Agency|(((
409 409  Inherits from
410 +
410 410  //Organisation//
411 -)))|(% style="width:540px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
412 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
412 412  |DataProvider|(((
413 413  Inherits from
415 +
414 414  //Organisation//
415 -)))|(% style="width:540px" %)An organisation that produces data.
417 +)))|An organisation that produces data.
416 416  |MetadataProvider|(((
417 417  Inherits from
420 +
418 418  //Organisation//
419 -)))|(% style="width:540px" %)An organisation that produces reference metadata.
422 +)))|An organisation that produces reference metadata.
420 420  |DataConsumer|(((
421 421  Inherits from
425 +
422 422  //Organisation//
423 -)))|(% style="width:540px" %)An organisation using data as input for further processing.
427 +)))|An organisation using data as input for further processing.
424 424  |OrganisationUnit|(((
425 425  Inherits from
430 +
426 426  //Organisation//
427 -)))|(% style="width:540px" %)A designation in the organisational structure.
428 -| |/hierarchy|(% style="width:540px" %)Association to child Organisation Units
432 +)))|A designation in the organisational structure.
433 +| |/hierarchy|Association to child Organisation Units
429 429  
430 -(% style="width:946.835px" %)
431 -|(% style="width:540px" %)
432 432  
433 -== 4.8 Reporting Taxonomy ==
434 434  
435 -=== 4.8.1 Class Diagram ===
437 +=== 4.8 Reporting Taxonomy ===
436 436  
437 -[[image:image52.png]]
439 +==== 4.8.1 Class Diagram ====
438 438  
441 +[[image:1749246291205-630.jpeg]]
442 +
439 439  **Figure 26: Class diagram of the Reporting Taxonomy**
440 440  
441 -=== 4.8.2 Explanation of the Diagram ===
445 +===== 4.8.2 Explanation of the Diagram =====
442 442  
443 -==== 4.8.2.1 Narrative ====
447 +====== 4.8.2.1 Narrative ======
444 444  
445 445  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.
446 446  
... ... @@ -458,22 +458,24 @@
458 458  
459 459  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).
460 460  
461 -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>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on //ItemScheme//.
465 +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//.
462 462  
463 -==== 4.8.2.2 Definitions ====
467 +====== 4.8.2.2 Definitions ======
464 464  
465 -(% style="width:969.835px" %)
466 -|**Class**|**Feature**|(% style="width:668px" %)**Description**
469 +|**Class**|**Feature**|**Description**
467 467  |ReportingTaxonomy|(((
468 468  Inherits from
472 +
469 469  //ItemScheme//
470 -)))|(% style="width:668px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
471 -| |/items|(% style="width:668px" %)Associates the Reporting Category
472 -|ReportingCategory|Inherits from //Item//|(% style="width:668px" %)A component that gives structure to the report and links to data and metadata.
473 -| |/hierarchy|(% style="width:668px" %)Associates child Reporting Category.
474 -| |+flow|(% style="width:668px" %)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.
475 -| |+structure|(% style="width:668px" %)Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
474 +)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
475 +| |/items|Associates the Reporting Category
476 +|ReportingCategory|Inherits from //Item//|A component that gives structure to the report and links to data and metadata.
477 +| |/hierarchy|Associates child Reporting Category.
478 +| |+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.
479 +| |+structure|Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
476 476  
481 +
482 +
477 477  ----
478 478  
479 -{{putFootnotes/}}
485 +[[~[1~]>>path:#_ftnref1]] The Codelist that extends 0..* Codelists is the 'extending' Codelist, while the Codelist(s) that are inherited is/are the 'extended' Codelist(s).
image42.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image43.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -36.8 KB
Content
image44.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -103.3 KB
Content
image45.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -36.1 KB
Content
image46.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -54.8 KB
Content
image47.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 KB
Content
image48.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -34.9 KB
Content
image49.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -38.0 KB
Content
image50.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -33.5 KB
Content
image51.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -111.9 KB
Content
image52.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -54.8 KB
Content
1749246291075-895.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
1749246291156-936.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +42.9 KB
Content
1749246291164-838.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +58.9 KB
Content
1749246291175-231.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +40.1 KB
Content
1749246291179-291.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +39.1 KB
Content
1749246291184-799.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +41.0 KB
Content
1749246291189-654.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +25.6 KB
Content
1749246291193-743.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +46.9 KB
Content
1749246291197-631.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +27.5 KB
Content
1749246291201-410.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +38.1 KB
Content
1749246291205-630.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +50.9 KB
Content
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -5
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +5
© Semantic R&D Group, 2026