Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 15.4
edited by Helena
on 2025/05/16 13:43
Change comment: There is no comment for this version
To version 15.9
edited by Helena
on 2025/05/16 13:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -113,7 +113,7 @@
113 113  
114 114  === 4.3.4 Class Diagram – Geospatial Codelist ===
115 115  
116 -The geospatial support is implemented via an extension of the normal ,,Codelist,,. This is illustrated in the following diagrams.
116 +The geospatial support is implemented via an extension of the normal //Codelist//. This is illustrated in the following diagrams.
117 117  
118 118  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]]
119 119  
... ... @@ -128,7 +128,6 @@
128 128  A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special Codes, i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property:
129 129  
130 130  GeographicCodelist
131 -
132 132  GeoGridCodelist
133 133  
134 134  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.
... ... @@ -150,9 +150,7 @@
150 150  )))
151 151  |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
152 152  Abstract Class Sub Classes:
153 -
154 154  GeoFeatureSet
155 -
156 156  GeoGridCode
157 157  )))|The abstract class that represents a special type of Code, which includes geospatial information.
158 158  |(% colspan="2" %)GeographicCodelist|(% colspan="4" %) |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
... ... @@ -177,7 +177,16 @@
177 177  
178 178  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
179 179  
180 -id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
177 +id
178 +uri
179 +urn
180 +version
181 +validFrom
182 +validTo
183 +isExternalReference
184 +registryURL
185 +structureURL
186 +repositoryURL
181 181  
182 182  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
183 183  
... ... @@ -210,10 +210,26 @@
210 210  
211 211  === 4.5.2 Explanation of the Diagram ===
212 212  
213 -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:
219 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
214 214  
215 -id uri urn
221 +id
222 +uri
223 +urn
224 +version
225 +validFrom
226 +validTo
227 +isExternalReference
228 +registryURL
229 +structureURL
230 +repositoryURL
231 +isPartial
216 216  
233 +Concept inherits from Item and has the following attributes:
234 +
235 +id
236 +uri
237 +urn
238 +
217 217  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).
218 218  
219 219  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.
... ... @@ -244,12 +244,10 @@
244 244  |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
245 245  |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
246 246  Inherits from
247 -
248 248  //ItemScheme//
249 249  )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
250 250  |(% style="width:204px" %)Concept|(% style="width:222px" %)(((
251 251  Inherits from
252 -
253 253  //Item//
254 254  )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
255 255  |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
... ... @@ -278,11 +278,22 @@
278 278  
279 279  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
280 280  
281 -id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
301 +id
302 +uri
303 +urn
304 +version
305 +validFrom
306 +validTo
307 +isExternalReference
308 +structureURL
309 +serviceURL
310 +isPartial
282 282  
283 283  Category inherits from //Item// and has the following attributes:
284 284  
285 -id uri urn
314 +id
315 +uri
316 +urn
286 286  
287 287  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).
288 288