Changes for page 4 Specific Item Schemes
Last modified by Helena K. on 2026/06/08 16:44
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 11 added, 11 removed)
- image42.png
- image43.png
- image44.png
- image45.png
- image46.png
- image47.png
- image48.png
- image49.png
- image50.png
- image51.png
- image52.png
- 1749246291075-895.jpeg
- 1749246291156-936.jpeg
- 1749246291164-838.jpeg
- 1749246291175-231.jpeg
- 1749246291179-291.jpeg
- 1749246291184-799.jpeg
- 1749246291189-654.jpeg
- 1749246291193-743.jpeg
- 1749246291197-631.jpeg
- 1749246291201-410.jpeg
- 1749246291205-630.jpeg
-
Objects (0 modified, 1 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,21 +4,33 @@ 4 4 5 5 == 4.1 Introduction == 6 6 7 -The structures that are an arrangement of objects into [[hierarchies>>doc:sdmx:Glossary2\.1.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:7 +The structures that are an arrangement of objects into hierarchies or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are: 8 8 9 -[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] 9 +Codelist 10 + 10 10 ConceptScheme 12 + 11 11 CategoryScheme 12 -AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme// 14 + 15 +AgencyScheme, DataProviderScheme, MetadataProviderScheme, 16 + 17 +DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme// 18 + 13 13 ReportingTaxonomy 20 + 14 14 TransformationScheme 22 + 15 15 RulesetScheme 24 + 16 16 UserDefinedOperatorScheme 26 + 17 17 NamePersonalisationScheme 28 + 18 18 CustomTypeScheme 30 + 19 19 VtlMappingScheme 20 20 21 -Note that the [[VTL>>doc:sdmx:Glossary2\.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]]).33 +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 23 == 4.2 Inheritance View == 24 24 ... ... @@ -28,7 +28,7 @@ 28 28 29 29 === 4.3.1 Class Diagram === 30 30 31 -[[image: image42.png]]43 +[[image:1749246291075-895.jpeg]] 32 32 33 33 **Figure 16: Class diagram of the Codelist** 34 34 ... ... @@ -36,118 +36,123 @@ 36 36 37 37 ==== 4.3.2.1 Narrative ==== 38 38 39 -The [[Codelist>>doc:sdmx:Glossary2\.1.Code list.WebHome]] inherits from the //ItemScheme// and therefore has the following[[attributes>>doc:sdmx:Glossary2\.1.Attribute.WebHome]]: id uri urn[[version>>doc:sdmx:Glossary2\.1.Version.WebHome]]validFrom validTo[[isExternalReference>>doc:sdmx:Glossary2\.1.isExternalReference.WebHome]] serviceURL structureURL isPartial51 +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:Glossary2\.1.Code.WebHome]]inherits from //Item// and has the following[[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]:53 +The Code inherits from //Item// and has the following attributes: 42 42 43 -id 44 -uri 45 -urn 55 +id uri urn 46 46 47 -Both [[Codelist>>doc:sdmx:Glossary2\.1.Code list.WebHome]]and[[Code>>doc:sdmx:Glossary2\.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:Glossary2\.1.Annotation.WebHome]]tosupport notes (not shown).57 +Both Codelist and Code have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown). 48 48 49 -Through the inheritance the [[Codelist>>doc:sdmx:Glossary2\.1.Code list.WebHome]]comprise one or more[[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]], and the[[Code>>doc:sdmx:Glossary2\.1.Code.WebHome]]itself can have one or more child[[Codes>>doc:sdmx:Glossary2\.1.Code.WebHome]]in the (inherited)[[hierarchy>>doc:sdmx:Glossary2\.1.Hierarchy.WebHome]] association. Note that a child[[Code>>doc:sdmx:Glossary2\.1.Code.WebHome]]can have only one parent[[Code>>doc:sdmx:Glossary2\.1.Code.WebHome]]in this association. A more complex Hierarhcy, which allows multiple parents is described later.59 +Through the inheritance the Codelist comprise one or more Codes, and the Code itself can have one or more child Codes in the (inherited) hierarchy association. Note that a child Code can have only one parent Code in this association. A more complex Hierarhcy, which allows multiple parents is described later. 50 50 51 -A partial [[Codelist>>doc:sdmx:Glossary2\.1.Code list.WebHome]](where isPartial is set to 'true') is identical to a[[Codelist>>doc:sdmx:Glossary2\.1.Code list.WebHome]]and contains the[[Code>>doc:sdmx:Glossary2\.1.Code.WebHome]]and associated names and descriptions, just as in a normal[[Codelist>>doc:sdmx:Glossary 2\.1.Codelist.WebHome]]. However, its content is a subset of the full[[Codelist>>doc:sdmx:Glossary 2\.1.Codelist.WebHome]].The way this works is described in section[[3.5.3.1>>doc:Methodology.SDMX3\.1 Standards\. Section2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on//ItemScheme//.61 +A partial Codelist (where isPartial is set to 'true') is identical to a Codelist and contains the Code and associated names and descriptions, just as in a normal Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//. 52 52 53 53 ==== 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]]|((( 65 +|**Class**|**Feature**|**Description** 66 +|Codelist|((( 58 58 Inherits from 68 + 59 59 //ItemScheme// 60 -)))| (% style="width:656px" %)A list from which some statistical[[concepts>>doc:sdmx:Glossary2\.1.Concept.WebHome]](coded[[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]]) take their values.61 -| [[Code>>doc:Glossary 2\.1.Code.WebHome]]|(((70 +)))|A list from which some statistical concepts (coded concepts) take their values. 71 +|Code|((( 62 62 Inherits from 73 + 63 63 Item 64 -)))| (% style="width:656px" %)A[[language>>doc:sdmx:Glossary2\.1.Language.WebHome]]independent set of letters, numbers or symbols that represent a[[concept>>doc:sdmx:Glossary2\.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:Glossary2\.1.Code list.WebHome]]with any[[Codelists>>doc:sdmx:Glossary2\.1.Code list.WebHome]] that it may extend.75 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language. 76 +| |hierarchy|Associates the parent and the child codes. 77 +| |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]]81 +[[image:1749246291156-936.jpeg]] 71 71 72 72 **Figure 17: Class diagram for Codelist Extension** 73 73 74 74 ==== 4.3.3.1 Narrative ==== 75 75 76 -A [[Codelist>>doc:sdmx:Glossary2\.1.Code list.WebHome]] may extend other[[Codelists>>doc:sdmx:Glossary2\.1.Code list.WebHome]]via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended[[Codelists>>doc:sdmx:Glossary2\.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:Glossary2\.1.Code.WebHome]]in the extending{{footnote}}TheCodelist that extends0..* Codelistsisthe'extending'Codelist,while the Codelist(s) that areinheritedis/arethe'extended' Codelist(s).{{/footnote}}[[Codelist>>doc:sdmx:Glossary 2\.1.Codelist.WebHome]]in case conflicting[[Codes>>doc:sdmx:Glossary2\.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:Glossary2\.1.Code.WebHome]]from the extended[[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].87 +A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[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:Glossary2\.1.Code.WebHome]]selection classes may have MemberValues in order to specify the subset of the[[Codes>>doc:sdmx:Glossary2\.1.Code.WebHome]]that should be included or excluded from the extended[[Codelist>>doc:sdmx:Glossary 2\.1.Codelist.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:Glossary2\.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:Glossary2\.1.Code.WebHome]]with common parts in their identifiers.89 +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 80 ==== 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]]. 93 +|**Class**|**Feature**|**Description** 94 +|CodelistExtension| |The association between Codelists that may extend other Codelists. 95 +| |prefix|A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts. 96 +| |sequence|((( 97 +The order that will be used when extending a 98 + 99 +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:Glossary2\.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:Glossary2\.1.Code.WebHome]]to be excluded when extending a[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].101 +|InclusiveCodeSelection| |The subset of Codes to be included when extending a Codelist. 102 +|ExclusiveCodeSelection| |The subset of Codes to be excluded when extending a Codelist. 91 91 |MemberValue|((( 92 92 Inherits from: 105 + 93 93 //SelectionValue// 94 -)))| (% style="width:655px" %)A collection of values based on[[Codes>>doc:sdmx:Glossary2\.1.Code.WebHome]]and their children.95 -| |cascadeValues| (% style="width:655px" %)A property to indicate if the child[[Codes>>doc:sdmx:Glossary2\.1.Code.WebHome]] of the selected[[Code>>doc:sdmx:Glossary2\.1.Code.WebHome]]shall be included in the selection. It is also possible to include children and exclude the[[Code>>doc:sdmx:Glossary2\.1.Code.WebHome]] by using the 'excluderoot' value.96 -| |value| (% style="width:655px" %)The value of the[[Code>>doc:sdmx:Glossary2\.1.Code.WebHome]]to include in the selection. It may include the ‘%’ character as a wildcard.107 +)))|A collection of values based on Codes and their children. 108 +| |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. 109 +| |value|The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard. 97 97 98 98 === 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]]115 +[[image:1749246291164-838.jpeg]] 103 103 104 104 **Figure 18: Inheritance for the GeoCodelist** 105 105 106 -[[image: image45.png]]119 +[[image:1749246291175-231.jpeg]] 107 107 108 108 **Figure 19: Class diagram for Geospatial Codelist** 109 109 110 110 ==== 4.3.4.1 Narrative ==== 111 111 112 -A //GeoCodelist// is a specialisation of [[Codelist>>doc:sdmx:Glossary2\.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:125 +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:Glossary2\.1.Code.WebHome]]that follows a pattern to represent a geo feature set.131 +The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code 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 122 ==== 4.3.4.2 Definitions ==== 123 123 124 -(% style="width:960.835px" %) 125 -|**Class**|**Feature**|(% style="width:559px" %)**Description** 137 +|**Class**|**Feature**|**Description** 126 126 |//GeoCodelist//|((( 127 127 Abstract Class Sub Classes: 140 + 128 128 GeographicCodelist 142 + 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:Glossary2\.1.Code list.WebHome]] that the[[Codelist>>doc:sdmx:Glossary2\.1.Code list.WebHome]]will become.144 +)))|The abstract class that represents a special type of Codelist, which includes geospatial information. 145 +| |geoType|The type of Geo Codelist that the Codelist will become. 132 132 |//GeoRefCode//|((( 133 133 Abstract Class 148 + 134 134 Sub Classes: 150 + 135 135 GeoFeatureSetCode 152 + 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:Glossary2\.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:Glossary2\.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:Glossary2\.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:Glossary2\.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:Glossary2\.1.Code.WebHome]]to one cell in the grid.154 +)))|The abstract class that represents a special type of Code, which includes geospatial information. 155 +|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. 156 +|GeoGridCodelist| |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth. 157 +| |gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist. 158 +|GeoFeatureSetCode| |A Code that has a geo feature set. 159 +| |value|The geo feature set of the Code, which represents a set of points defining a feature in a format defined a predefined pattern (see section 6). 160 +|GeoGridCode| |A Code that represents a Geo Grid Cell belonging in a specific grid definition. 161 +| |geoCell|The value used to assign the Code to one cell in the grid. 145 145 146 146 == 4.4 ValueList == 147 147 148 148 === 4.4.1 Class Diagram === 149 149 150 -[[image: image46.png]]167 +[[image:1749246291179-291.jpeg]] 151 151 152 152 **Figure 20: Class diagram of the ValueList** 153 153 ... ... @@ -155,76 +155,53 @@ 155 155 156 156 ==== 4.4.2.1 Narrative ==== 157 157 158 -A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]:175 +A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes: 159 159 160 -id 161 -uri 162 -urn 177 +id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL 163 163 164 -[[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] 165 -validFrom 166 -validTo 167 -[[isExternalReference>>doc:sdmx:Glossary 2\.1.isExternalReference.WebHome]] 168 -registryURL 169 -structureURL 170 -repositoryURL 179 +ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former. 171 171 172 - ValueIteminheritsfrom //EnumeratedItem//,whichadds anid,withrelaxed[[constraints>>doc:sdmx:Glossary2\.1.Constraint.WebHome]],to theformer.181 +Through the inheritance from //NameableArtefact// the ValueList has the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown). Similarly, the ValueItem, inherits the association to InternationalString and to the Annotation from the //EnumeratedItem//. 173 173 174 -Through the inheritance from //NameableArtefact// the ValueList has the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] to support notes (not shown). Similarly, the ValueItem, inherits the association to InternationalString and to the [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] from the //EnumeratedItem//. 175 - 176 176 The ValueList can have one or more ValueItems. 177 177 178 178 ==== 4.4.2.2 Definitions ==== 179 179 180 -(% style="width:929.835px" %) 181 -|**Class**|(% style="width:175px" %)**Feature**|(% style="width:632px" %)**Description** 182 -|ValueList|(% style="width:175px" %)((( 187 +|**Class**|**Feature**|**Description** 188 +|ValueList|((( 183 183 Inherits from 190 + 184 184 //EnumeratedList// 185 -)))| (% style="width:632px" %)A list from which some statistical concepts (enumerated concepts) take their values.186 -|ValueItem|( % style="width:175px" %)(((192 +)))|A list from which some statistical concepts (enumerated concepts) take their values. 193 +|ValueItem|((( 187 187 Inherits from 195 + 188 188 //EnumeratedItem// 189 -)))| (% style="width:632px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.197 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language. 190 190 191 191 == 4.5 Concept Scheme and Concepts == 192 192 193 193 === 4.5.1 Class Diagram - Inheritance === 194 194 195 -[[image: image47.png]]203 +[[image:1749246291184-799.jpeg]] 196 196 197 197 **Figure 21 Class diagram of the Concept Scheme** 198 198 199 199 === 4.5.2 Explanation of the Diagram === 200 200 201 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: 209 +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: 202 202 203 -id 204 -uri 205 -urn 206 -version validFrom validTo 207 -isExternalReference 208 -registryURL 209 -structureURL 210 -repositoryURL 211 -isPartial 211 +id uri urn 212 212 213 -Concept inherits from Item and has the following attributes: 214 - 215 -id 216 -uri 217 -urn 218 - 219 219 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). 220 220 221 221 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. 222 222 223 -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.SDMX3\.1 Standards\. Section2\.Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on ItemScheme.217 +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. 224 224 225 225 === 4.5.3 Class Diagram Relationship === 226 226 227 -[[image: image48.png]]221 +[[image:1749246291189-654.jpeg]] 228 228 229 229 **Figure 22: Relationship class diagram of the Concept Scheme** 230 230 ... ... @@ -242,25 +242,28 @@ 242 242 243 243 ==== 4.5.4.2 Definitions ==== 244 244 245 -(% style="width:912.835px" %) 246 -|(% style="width:170px" %)**Class**|(% style="width:184px" %)**Feature**|(% style="width:548px" %)**Description** 247 -|(% style="width:170px" %)((( 239 +|**Class**|**Feature**|**Description** 240 +|((( 248 248 ConceptScheme 249 -)))|(% style="width:184px" %)((( 242 + 243 + 244 +)))|((( 250 250 Inherits from 246 + 251 251 //ItemScheme// 252 -)))| (% style="width:548px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.253 -| (% style="width:170px" %)Concept|(% style="width:184px" %)(((248 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 249 +|Concept|((( 254 254 Inherits from 251 + 255 255 //Item// 256 -)))| (% style="width:548px" %)A concept is a unit of knowledge created by a unique combination of characteristics.257 -| (%style="width:170px" %)|(% style="width:184px" %)/hierarchy|(% style="width:548px" %)Associates the parent and the child concept.258 -| (%style="width:170px" %)|(% style="width:184px" %)coreRepresentation|(% style="width:548px" %)Associates a Representation.259 -| (%style="width:170px" %)|(% style="width:184px" %)+ISOConcept|(% style="width:548px" %)Association to an ISO concept reference.260 -| (% style="width:170px" %)ISOConceptReference|(%style="width:184px" %)|(% style="width:548px" %)The identity of an ISO concept definition.261 -| (%style="width:170px" %)|(% style="width:184px" %)conceptAgency|(% style="width:548px" %)The maintenance agency of the concept scheme containing the concept.262 -| (%style="width:170px" %)|(% style="width:184px" %)conceptSchemeID|(% style="width:548px" %)The identifier of the concept scheme.263 -| (%style="width:170px" %)|(% style="width:184px" %)conceptID|(% style="width:548px" %)The identifier of the concept.253 +)))|A concept is a unit of knowledge created by a unique combination of characteristics. 254 +| |/hierarchy|Associates the parent and the child concept. 255 +| |coreRepresentation|Associates a Representation. 256 +| |+ISOConcept|Association to an ISO concept reference. 257 +|ISOConceptReference| |The identity of an ISO concept definition. 258 +| |conceptAgency|The maintenance agency of the concept scheme containing the concept. 259 +| |conceptSchemeID|The identifier of the concept scheme. 260 +| |conceptID|The identifier of the concept. 264 264 265 265 == 4.6 Category Scheme == 266 266 ... ... @@ -270,7 +270,7 @@ 270 270 271 271 === 4.6.2 Class diagram Inheritance === 272 272 273 -[[image: image49.png]]270 +[[image:1749246291193-743.jpeg]] 274 274 275 275 **Figure 23 Inheritance Class diagram of the Category Scheme** 276 276 ... ... @@ -280,32 +280,21 @@ 280 280 281 281 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 282 282 283 -id 284 -uri 285 -urn 286 -version 287 -validFrom 288 -validTo 289 -isExternalReference 290 -structureURL 291 -serviceURL 292 -isPartial 280 +id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial 293 293 294 294 Category inherits from //Item// and has the following attributes: 295 295 296 -id 297 -uri 298 -urn 284 +id uri urn 299 299 300 300 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). 301 301 302 302 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. 303 303 304 -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.SDMX3\.1 Standards\. Section2\.Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on ItemScheme.290 +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. 305 305 306 306 === 4.6.4 Class diagram Relationship === 307 307 308 -[[image: image50.png]]294 +[[image:1749246291197-631.jpeg]] 309 309 310 310 **Figure 24: Relationship Class diagram of the Category Scheme** 311 311 ... ... @@ -313,30 +313,32 @@ 313 313 314 314 ==== 4.6.4.1 Definitions ==== 315 315 316 -(% style="width:935.835px" %) 317 -|**Class**|**Feature**|(% style="width:601px" %)**Description** 302 +|**Class**|**Feature**|**Description** 318 318 |CategoryScheme|((( 319 319 Inherits from 305 + 320 320 //ItemScheme// 321 -)))| (% style="width:601px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.322 -| |/items| (% style="width:601px" %)Associates the categories.307 +)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 308 +| |/items|Associates the categories. 323 323 |Category|((( 324 324 Inherits from 311 + 325 325 //Item// 326 -)))| (% style="width:601px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.327 -| |/hierarchy| (% style="width:601px" %)Associates the parent and the child Category.313 +)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 314 +| |/hierarchy|Associates the parent and the child Category. 328 328 |Categorisation|((( 329 329 Inherits from 317 + 330 330 //MaintainableArtefact// 331 -)))| (% style="width:601px" %)Associates an Identifable Artefact with a Category.332 -| |+categorisedArtefact| (% style="width:601px" %)Associates the Identifable Artefact.333 -| |+categorisedBy| (% style="width:601px" %)Associates the Category.319 +)))|Associates an Identifable Artefact with a Category. 320 +| |+categorisedArtefact|Associates the Identifable Artefact. 321 +| |+categorisedBy|Associates the Category. 334 334 335 335 == 4.7 Organisation Scheme == 336 336 337 337 === 4.7.1 Class Diagram === 338 338 339 -[[image: image51.png]]327 +[[image:1749246291201-410.jpeg]] 340 340 341 341 **Figure 25 The Organisation Scheme class diagram** 342 342 ... ... @@ -352,90 +352,107 @@ 352 352 1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy). 353 353 1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy). 354 354 1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy). 355 -1. (% style="background-color:#d35400" %)OrganisationUnitScheme(%%)– contains OrganisationUnit which does inherit the /hierarchy association from Organisation.343 +1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation. 356 356 357 357 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. 358 358 359 -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.SDMX3\.1 Standards\. Section2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on//ItemScheme//.347 +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//. 360 360 361 361 ==== 4.7.2.2 Definitions ==== 362 362 363 -(% style="width:946.835px" %) 364 -|**Class**|**Feature**|(% style="width:540px" %)**Description** 351 +|**Class**|**Feature**|**Description** 365 365 |//OrganisationScheme//|((( 366 366 Abstract Class 354 + 367 367 Inherits from 356 + 368 368 //ItemScheme// 358 + 369 369 Sub classes are: 360 + 370 370 AgencyScheme 362 + 371 371 DataProviderScheme 364 + 372 372 MetadataProviderScheme 366 + 373 373 DataConsumerScheme 368 + 374 374 OrganisationUnitScheme 375 -)))| (% style="width:540px" %)A maintained collection of Organisations.376 -| |/items| (% style="width:540px" %)Association to the Organisations in the scheme.370 +)))|A maintained collection of Organisations. 371 +| |/items|Association to the Organisations in the scheme. 377 377 |//Organisation//|((( 378 378 Abstract Class 374 + 379 379 Inherits from 376 + 380 380 //Item// 378 + 381 381 Sub classes are: 380 + 382 382 Agency 382 + 383 383 DataProvider 384 + 384 384 MetadataProvider 386 + 385 385 DataConsumer 388 + 386 386 OrganisationUnit 387 -)))| (% 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.388 -| |+contact| (% style="width:540px" %)Association to the Contact information.389 -| |/hierarchy| (% style="width:540px" %)Association to child Organisations.390 -|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.391 -| |name| (% style="width:540px" %)The designation of the Contact person by a linguistic expression.392 -| |organisationUnit| (% style="width:540px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.393 -| |responsibility| (% style="width:540px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.394 -| |telephone| (% style="width:540px" %)The telephone number of the Contact.395 -| |fax| (% style="width:540px" %)The fax number of the Contact.396 -| |email| (% style="width:540px" %)The Internet e-mail address of the Contact.397 -| |X400| (% style="width:540px" %)The X400 address of the Contact.398 -| |uri| (% style="width:540px" %)The URL address of the Contact.399 -|AgencyScheme| | (% style="width:540px" %)A maintained collection of Maintenance Agencies.400 -| |/items| (% style="width:540px" %)Association to the Maintenance Agency in the scheme.401 -|DataProviderScheme| | (% style="width:540px" %)A maintained collection of Data Providers.402 -| |/items| (% style="width:540px" %)Association to the Data Providers in the scheme.403 -|MetadataProviderScheme| | (% style="width:540px" %)A maintained collection of Metadata Providers.404 -| |/items| (% style="width:540px" %)Association to the Metadata Providers in the scheme.405 -|DataConsumerScheme| | (% style="width:540px" %)A maintained collection of Data Consumers.406 -| |/items| (% style="width:540px" %)Association to the Data Consumers in the scheme.407 -| (%%)(% style="background-color:#d35400" %)OrganisationUnitScheme| |(% style="width:540px" %)A maintained collection of Organisation Units.408 -| |/items| (% style="width:540px" %)Association to the Organisation Units in the scheme.390 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 391 +| |+contact|Association to the Contact information. 392 +| |/hierarchy|Association to child Organisations. 393 +|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. 394 +| |name|The designation of the Contact person by a linguistic expression. 395 +| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works. 396 +| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact. 397 +| |telephone|The telephone number of the Contact. 398 +| |fax|The fax number of the Contact. 399 +| |email|The Internet e-mail address of the Contact. 400 +| |X400|The X400 address of the Contact. 401 +| |uri|The URL address of the Contact. 402 +|AgencyScheme| |A maintained collection of Maintenance Agencies. 403 +| |/items|Association to the Maintenance Agency in the scheme. 404 +|DataProviderScheme| |A maintained collection of Data Providers. 405 +| |/items|Association to the Data Providers in the scheme. 406 +|MetadataProviderScheme| |A maintained collection of Metadata Providers. 407 +| |/items|Association to the Metadata Providers in the scheme. 408 +|DataConsumerScheme| |A maintained collection of Data Consumers. 409 +| |/items|Association to the Data Consumers in the scheme. 410 +|OrganisationUnitScheme| |A maintained collection of Organisation Units. 411 +| |/items|Association to the Organisation Units in the scheme. 409 409 |Agency|((( 410 410 Inherits from 414 + 411 411 //Organisation// 412 -)))| (% 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.416 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 413 413 |DataProvider|((( 414 414 Inherits from 419 + 415 415 //Organisation// 416 -)))| (% style="width:540px" %)An organisation that produces data.421 +)))|An organisation that produces data. 417 417 |MetadataProvider|((( 418 418 Inherits from 424 + 419 419 //Organisation// 420 -)))| (% style="width:540px" %)An organisation that produces reference metadata.426 +)))|An organisation that produces reference metadata. 421 421 |DataConsumer|((( 422 422 Inherits from 429 + 423 423 //Organisation// 424 -)))| (% style="width:540px" %)An organisation using data as input for further processing.431 +)))|An organisation using data as input for further processing. 425 425 |OrganisationUnit|((( 426 426 Inherits from 434 + 427 427 //Organisation// 428 -)))| (% style="width:540px" %)A designation in the organisational structure.429 -| |/hierarchy| (% style="width:540px" %)Association to child Organisation Units436 +)))|A designation in the organisational structure. 437 +| |/hierarchy|Association to child Organisation Units 430 430 431 -(% style="width:946.835px" %) 432 -|(% style="width:540px" %) 433 - 434 434 == 4.8 Reporting Taxonomy == 435 435 436 436 === 4.8.1 Class Diagram === 437 437 438 -[[image: image52.png]]443 +[[image:1749246291205-630.jpeg]] 439 439 440 440 **Figure 26: Class diagram of the Reporting Taxonomy** 441 441 ... ... @@ -459,22 +459,24 @@ 459 459 460 460 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). 461 461 462 -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.SDMX3\.1 Standards\. Section2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on//ItemScheme//.467 +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//. 463 463 464 464 ==== 4.8.2.2 Definitions ==== 465 465 466 -(% style="width:969.835px" %) 467 -|**Class**|**Feature**|(% style="width:668px" %)**Description** 471 +|**Class**|**Feature**|**Description** 468 468 |ReportingTaxonomy|((( 469 469 Inherits from 474 + 470 470 //ItemScheme// 471 -)))| (% 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.472 -| |/items| (% style="width:668px" %)Associates the Reporting Category473 -|ReportingCategory|Inherits from //Item//| (% style="width:668px" %)A component that gives structure to the report and links to data and metadata.474 -| |/hierarchy| (% style="width:668px" %)Associates child Reporting Category.475 -| |+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.476 -| |+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.476 +)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow. 477 +| |/items|Associates the Reporting Category 478 +|ReportingCategory|Inherits from //Item//|A component that gives structure to the report and links to data and metadata. 479 +| |/hierarchy|Associates child Reporting Category. 480 +| |+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. 481 +| |+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. 477 477 483 + 484 + 478 478 ---- 479 479 480 - {{putFootnotes/}}487 +[[~[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