Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 16.1
edited by Helena
on 2025/05/16 13:48
Change comment: There is no comment for this version
To version 15.4
edited by Helena
on 2025/05/16 13:43
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,6 +128,7 @@
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 +
131 131  GeoGridCodelist
132 132  
133 133  The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code that follows a pattern to represent a geo feature set.
... ... @@ -149,7 +149,9 @@
149 149  )))
150 150  |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
151 151  Abstract Class Sub Classes:
153 +
152 152  GeoFeatureSet
155 +
153 153  GeoGridCode
154 154  )))|The abstract class that represents a special type of Code, which includes geospatial information.
155 155  |(% colspan="2" %)GeographicCodelist|(% colspan="4" %) |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
... ... @@ -174,16 +174,7 @@
174 174  
175 175  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
176 176  
177 -id
178 -uri
179 -urn
180 -version
181 -validFrom
182 -validTo
183 -isExternalReference
184 -registryURL
185 -structureURL
186 -repositoryURL
180 +id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
187 187  
188 188  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
189 189  
... ... @@ -216,26 +216,10 @@
216 216  
217 217  === 4.5.2 Explanation of the Diagram ===
218 218  
219 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
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:
220 220  
221 -id
222 -uri
223 -urn
224 -version
225 -validFrom
226 -validTo
227 -isExternalReference
228 -registryURL
229 -structureURL
230 -repositoryURL
231 -isPartial
215 +id uri urn
232 232  
233 -Concept inherits from Item and has the following attributes:
234 -
235 -id
236 -uri
237 -urn
238 -
239 239  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).
240 240  
241 241  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.
... ... @@ -266,10 +266,12 @@
266 266  |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
267 267  |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
268 268  Inherits from
247 +
269 269  //ItemScheme//
270 270  )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
271 271  |(% style="width:204px" %)Concept|(% style="width:222px" %)(((
272 272  Inherits from
252 +
273 273  //Item//
274 274  )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
275 275  |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
... ... @@ -298,22 +298,11 @@
298 298  
299 299  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
300 300  
301 -id
302 -uri
303 -urn
304 -version
305 -validFrom
306 -validTo
307 -isExternalReference
308 -structureURL
309 -serviceURL
310 -isPartial
281 +id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
311 311  
312 312  Category inherits from //Item// and has the following attributes:
313 313  
314 -id
315 -uri
316 -urn
285 +id uri urn
317 317  
318 318  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).
319 319  
... ... @@ -335,16 +335,19 @@
335 335  |**Class**|(% colspan="2" %)**Feature**|**Description**
336 336  |CategoryScheme|(% colspan="2" %)(((
337 337  Inherits from
307 +
338 338  //ItemScheme//
339 339  )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
340 340  | |(% colspan="2" %)/items|Associates the categories.
341 341  |Category|(((
342 342  Inherits from
313 +
343 343  //Item//
344 344  )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
345 345  | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category.
346 346  |Categorisation|(((
347 347  Inherits from
319 +
348 348  //MaintainableArtefact//
349 349  )))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
350 350  | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
... ... @@ -382,12 +382,17 @@
382 382  |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
383 383  |//OrganisationScheme//|(% style="width:246px" %)(((
384 384  Abstract Class Inherits from
357 +
385 385  //ItemScheme//
386 386  
387 387  Sub classes are:
361 +
388 388  AgencyScheme
363 +
389 389  DataProviderScheme
365 +
390 390  MetadataProviderScheme DataConsumerScheme
367 +
391 391  OrganisationUnitScheme
392 392  )))|(% style="width:336px" %)A maintained collection of Organisations.
393 393  | |(% style="width:246px" %)/items|(% style="width:336px" %)(((
... ... @@ -397,12 +397,19 @@
397 397  )))
398 398  |//Organisation//|(% style="width:246px" %)(((
399 399  Abstract Class
400 -Inherits from //Item//
401 401  
378 +Inherits from
379 +
380 +//Item//
381 +
402 402  Sub classes are:
383 +
403 403  Agency
385 +
404 404  DataProvider
387 +
405 405  MetadataProvider DataConsumer
389 +
406 406  OrganisationUnit
407 407  )))|(% style="width:336px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
408 408  | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
... ... @@ -428,22 +428,27 @@
428 428  | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
429 429  |Agency|(% style="width:246px" %)(((
430 430  Inherits from
415 +
431 431  //Organisation//
432 432  )))|(% style="width:336px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
433 433  |DataProvider|(% style="width:246px" %)(((
434 434  Inherits from
420 +
435 435  //Organisation//
436 436  )))|(% style="width:336px" %)An organisation that produces data.
437 437  |MetadataProvider|(% style="width:246px" %)(((
438 438  Inherits from
425 +
439 439  //Organisation//
440 440  )))|(% style="width:336px" %)An organisation that produces reference metadata.
441 441  |DataConsumer|(% style="width:246px" %)(((
442 442  Inherits from
430 +
443 443  //Organisation//
444 444  )))|(% style="width:336px" %)An organisation using data as input for further processing.
445 445  |OrganisationUnit|(% style="width:246px" %)(((
446 446  Inherits from
435 +
447 447  //Organisation//
448 448  )))|(% style="width:336px" %)A designation in the organisational structure.
449 449  | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units
... ... @@ -484,11 +484,13 @@
484 484  |(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description**
485 485  |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)(((
486 486  Inherits from
476 +
487 487  //ItemScheme//
488 488  )))|(% style="width:428px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
489 489  |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category
490 490  |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)(((
491 491  Inherits from
482 +
492 492  //Item//
493 493  )))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata.
494 494  |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.