Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Helena on 2025/09/10 11:19
From version 3.3
edited by Helena
on 2025/06/08 01:06
Change comment: There is no comment for this version
To version 5.1
edited by Helena
on 2025/06/08 01:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,7 +38,7 @@
38 38  
39 39  == 4.3 Codelist ==
40 40  
41 -==== 4.3.1 Class Diagram ====
41 +=== 4.3.1 Class Diagram ===
42 42  
43 43  [[image:1749246291075-895.jpeg]]
44 44  
... ... @@ -84,7 +84,7 @@
84 84  
85 85  ==== 4.3.3.1 Narrative ====
86 86  
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" %)^^~[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.
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.
88 88  
89 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.
90 90  
... ... @@ -322,15 +322,15 @@
322 322  
323 323  == 4.7 Organisation Scheme ==
324 324  
325 -==== Class Diagram ====
325 +=== 4.7.1 Class Diagram ===
326 326  
327 327  [[image:1749246291201-410.jpeg]]
328 328  
329 329  **Figure 25 The Organisation Scheme class diagram**
330 330  
331 -===== 4.7.2    Explanation of the Diagram =====
331 +=== 4.7.2 Explanation of the Diagram ===
332 332  
333 -====== 4.7.2.1 Narrative ======
333 +==== 4.7.2.1 Narrative ====
334 334  
335 335  The //OrganisationScheme// is abstract. It contains //Organisation// which is also abstract. The //Organisation// can have child //Organisation//.
336 336  
... ... @@ -346,7 +346,7 @@
346 346  
347 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//.
348 348  
349 -====== 4.7.2.2 Definitions ======
349 +==== 4.7.2.2 Definitions ====
350 350  
351 351  |**Class**|**Feature**|**Description**
352 352  |//OrganisationScheme//|(((
... ... @@ -436,19 +436,17 @@
436 436  )))|A designation in the organisational structure.
437 437  | |/hierarchy|Association to child Organisation Units
438 438  
439 +== 4.8 Reporting Taxonomy ==
439 439  
441 +=== 4.8.1 Class Diagram ===
440 440  
441 -=== 4.8 Reporting Taxonomy ===
442 -
443 -==== 4.8.1 Class Diagram ====
444 -
445 445  [[image:1749246291205-630.jpeg]]
446 446  
447 447  **Figure 26: Class diagram of the Reporting Taxonomy**
448 448  
449 -===== 4.8.2 Explanation of the Diagram =====
447 +=== 4.8.2 Explanation of the Diagram ===
450 450  
451 -====== 4.8.2.1 Narrative ======
449 +==== 4.8.2.1 Narrative ====
452 452  
453 453  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.
454 454  
... ... @@ -468,7 +468,7 @@
468 468  
469 469  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//.
470 470  
471 -====== 4.8.2.2 Definitions ======
469 +==== 4.8.2.2 Definitions ====
472 472  
473 473  |**Class**|**Feature**|**Description**
474 474  |ReportingTaxonomy|(((