Skip to Content

Changes for page 5 Reference Metadata

Last modified by Artur on 2025/09/10 11:19
From version 1.3
edited by Helena
on 2025/06/11 00:32
Change comment: There is no comment for this version
To version 1.1
edited by Helena
on 2025/06/11 00:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -32,7 +32,8 @@
32 32  
33 33  Note that the SDMX-ML schemas have specific XML elements for each identifiable object type because identifying, for instance, a Maintainable Object has different properties from an Identifiable Object which must also include the agencyId, version, and id of the Maintainable Object in which it resides.
34 34  
35 -== 5.2 Metadata Structure Definition ==
35 +1.
36 +11. Metadata Structure Definition
36 36  
37 37  An example is shown below.
38 38  
... ... @@ -40,22 +40,25 @@
40 40  
41 41  This example shows the following hierarchy of Metadata Attributes:
42 42  
43 -* Contact – this is presentational; no metadata is expected to be reported at this level
44 +• Contact – this is presentational; no metadata is expected to be reported at this level
45 +
44 44  * Contact Name
45 45  * Address – this is also presentational; up to 3 addresses are allowed
46 -** House Number
47 47  
48 -== 5.3 Metadata Set ==
49 + § House Number
49 49  
51 +1.
52 +11. Metadata Set
53 +
50 50  An example of reporting metadata according to the MSD described above, is shown below.
51 51  
52 -**Figure 6: Example Metadata Set**
56 +==== Figure 6: Example Metadata Set ====
53 53  
54 54  This example shows:
55 55  
56 56  1. The reference to the Metadata Provision Agreement and Metadata Target
57 57  1. The reported metadata attributes (AttributeSet)
58 -1. Reference Metadata in Data Structure Definition and Dataset
62 +11. Reference Metadata in Data Structure Definition and Dataset
59 59  
60 60  An important change of SDMX 3.0 is the ability to reference an MSD within a DSD, in order to report any Metadata Attributes defined in the former to Datasets of the latter.
61 61  
... ... @@ -62,8 +62,11 @@
62 62  This is achieved by the following:
63 63  
64 64  * In a DSD, the user may add a reference to one MSD.
65 -* In the Attribute Descriptor of the DSD, the user may include any Metadata Attributes defined in the linked MSD.
66 -** For each link to a Metadata Attribute, an Attribute Relationship may be specified (similarly to that for Data Attributes).
69 +* In the Attribute Descriptor of the DSD, the user may include any Metadata Attributes defined in the linked MSD. o For each link to a Metadata Attribute, an Attribute Relationship may be specified (similarly to that for Data Attributes).
67 67  * In any Dataset complying with this DSD, Metadata Attributes may be reported according to the specified Attribute Relationship.
68 -** The hierarchy of the Metadata Attributes defined in the MSD must be respected and they are reported in the same way as in a Metadataset, under the level they are related within the DSD, via their Attribute Relationship.
69 -* In Data Constraints, the user is allowed to restrict values for Metadata Attributes, in the same way as Data Attributes (more on this in section “10 Constraints”).
71 +
72 +o The hierarchy of the Metadata Attributes defined in the MSD must be respected and they are reported in the same way as in a Metadataset, under the level they are related within the DSD, via their Attribute Relationship.
73 +
74 +In Data Constraints, the user is allowed to restrict values for Metadata Attributes, in the same way as Data Attributes (more on this in section “10 Constraints”).
75 +
76 +