Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19

From version 15.3
edited by Helena
on 2025/05/16 13:42
Change comment: There is no comment for this version
To version 15.10
edited by Helena
on 2025/05/16 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -88,14 +88,12 @@
88 88  
89 89  ==== 4.3.3.1 Narrative ====
90 90  
91 -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 wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^ 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.
91 +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{{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 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.
92 92  
93 93  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 ,,Code,,s (via the ,,cascadeValues,, property), or even include instances of the wildcard character ‘%’ in order to point to a set of ,,Code,,s with common parts in their identifiers.
94 94  
95 95  ==== 4.3.3.2 Definitions ====
96 96  
97 -:
98 -
99 99  (((
100 100  (% style="width:753.039px" %)
101 101  |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
... ... @@ -115,7 +115,7 @@
115 115  
116 116  === 4.3.4 Class Diagram – Geospatial Codelist ===
117 117  
118 -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.
119 119  
120 120  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]]
121 121  
... ... @@ -130,7 +130,6 @@
130 130  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:
131 131  
132 132  GeographicCodelist
133 -
134 134  GeoGridCodelist
135 135  
136 136  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.
... ... @@ -152,9 +152,7 @@
152 152  )))
153 153  |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
154 154  Abstract Class Sub Classes:
155 -
156 156  GeoFeatureSet
157 -
158 158  GeoGridCode
159 159  )))|The abstract class that represents a special type of Code, which includes geospatial information.
160 160  |(% 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.
... ... @@ -179,7 +179,16 @@
179 179  
180 180  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
181 181  
182 -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
183 183  
184 184  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
185 185  
... ... @@ -212,10 +212,26 @@
212 212  
213 213  === 4.5.2 Explanation of the Diagram ===
214 214  
215 -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:
216 216  
217 -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
218 218  
233 +Concept inherits from Item and has the following attributes:
234 +
235 +id
236 +uri
237 +urn
238 +
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.
... ... @@ -246,12 +246,10 @@
246 246  |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
247 247  |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
248 248  Inherits from
249 -
250 250  //ItemScheme//
251 251  )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
252 252  |(% style="width:204px" %)Concept|(% style="width:222px" %)(((
253 253  Inherits from
254 -
255 255  //Item//
256 256  )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
257 257  |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
... ... @@ -280,11 +280,22 @@
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 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
284 284  
285 285  Category inherits from //Item// and has the following attributes:
286 286  
287 -id uri urn
314 +id
315 +uri
316 +urn
288 288  
289 289  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).
290 290  
... ... @@ -306,19 +306,16 @@
306 306  |**Class**|(% colspan="2" %)**Feature**|**Description**
307 307  |CategoryScheme|(% colspan="2" %)(((
308 308  Inherits from
309 -
310 310  //ItemScheme//
311 311  )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
312 312  | |(% colspan="2" %)/items|Associates the categories.
313 313  |Category|(((
314 314  Inherits from
315 -
316 316  //Item//
317 317  )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
318 318  | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category.
319 319  |Categorisation|(((
320 320  Inherits from
321 -
322 322  //MaintainableArtefact//
323 323  )))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
324 324  | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
... ... @@ -356,17 +356,12 @@
356 356  |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
357 357  |//OrganisationScheme//|(% style="width:246px" %)(((
358 358  Abstract Class Inherits from
359 -
360 360  //ItemScheme//
361 361  
362 362  Sub classes are:
363 -
364 364  AgencyScheme
365 -
366 366  DataProviderScheme
367 -
368 368  MetadataProviderScheme DataConsumerScheme
369 -
370 370  OrganisationUnitScheme
371 371  )))|(% style="width:336px" %)A maintained collection of Organisations.
372 372  | |(% style="width:246px" %)/items|(% style="width:336px" %)(((
... ... @@ -376,19 +376,12 @@
376 376  )))
377 377  |//Organisation//|(% style="width:246px" %)(((
378 378  Abstract Class
400 +Inherits from //Item//
379 379  
380 -Inherits from
381 -
382 -//Item//
383 -
384 384  Sub classes are:
385 -
386 386  Agency
387 -
388 388  DataProvider
389 -
390 390  MetadataProvider DataConsumer
391 -
392 392  OrganisationUnit
393 393  )))|(% 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.
394 394  | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
... ... @@ -414,27 +414,22 @@
414 414  | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
415 415  |Agency|(% style="width:246px" %)(((
416 416  Inherits from
417 -
418 418  //Organisation//
419 419  )))|(% 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.
420 420  |DataProvider|(% style="width:246px" %)(((
421 421  Inherits from
422 -
423 423  //Organisation//
424 424  )))|(% style="width:336px" %)An organisation that produces data.
425 425  |MetadataProvider|(% style="width:246px" %)(((
426 426  Inherits from
427 -
428 428  //Organisation//
429 429  )))|(% style="width:336px" %)An organisation that produces reference metadata.
430 430  |DataConsumer|(% style="width:246px" %)(((
431 431  Inherits from
432 -
433 433  //Organisation//
434 434  )))|(% style="width:336px" %)An organisation using data as input for further processing.
435 435  |OrganisationUnit|(% style="width:246px" %)(((
436 436  Inherits from
437 -
438 438  //Organisation//
439 439  )))|(% style="width:336px" %)A designation in the organisational structure.
440 440  | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units
... ... @@ -489,3 +489,5 @@
489 489  |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
490 490  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.
491 491  )))
501 +
502 +{{putFootnotes/}}