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 14.1
edited by Helena
on 2025/05/15 10:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,15 +7,27 @@
7 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 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 21  Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
... ... @@ -36,24 +36,11 @@
36 36  
37 37  ==== 4.3.2.1 Narrative ====
38 38  
39 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
51 +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 -id
42 -uri
43 -urn
44 -version
45 -validFrom
46 -validTo
47 -isExternalReference
48 -serviceURL
49 -structureURL
50 -isPartial
51 -
52 52  The Code inherits from //Item// and has the following attributes:
53 53  
54 -id
55 -uri
56 -urn
55 +id uri urn
57 57  
58 58  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).
59 59  
... ... @@ -88,12 +88,14 @@
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{{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.
90 +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" %)^^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.
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  
96 +:
97 +
97 97  (((
98 98  (% style="width:753.039px" %)
99 99  |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
... ... @@ -485,7 +485,7 @@
485 485  |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.
486 486  |(% style="width:177px" %) |(% style="width:152px" %)+flow|(% style="width:428px" %)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.
487 487  |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
488 -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.
489 -)))
489 +Association to the Data Structure
490 490  
491 -{{putFootnotes/}}
491 +Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
492 +)))