Skip to Content

Changes for page 5 Reference Metadata

Last modified by Artur on 2025/09/10 11:19
From version 1.4
edited by Helena
on 2025/06/11 00:33
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
... ... @@ -24,18 +24,16 @@
24 24  
25 25  The high-level view of the MSD, as well as the way the Metadataflow and Metadata Provision Agreement specify the Targets:
26 26  
27 -
28 28  **Figure 2: The high-level view of the MSD containing one Metadata Attribute Descriptor**
29 29  
30 -
31 31  **Figure 3: Wildcarded Target Objects as specified in a Metadataflow**
32 32  
33 -
34 34  **Figure 4: Specific Target Objects as specified in a Metadata Provision Agreement**
35 35  
36 36  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.
37 37  
38 -== 5.2 Metadata Structure Definition ==
35 +1.
36 +11. Metadata Structure Definition
39 39  
40 40  An example is shown below.
41 41  
... ... @@ -43,22 +43,25 @@
43 43  
44 44  This example shows the following hierarchy of Metadata Attributes:
45 45  
46 -* 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 +
47 47  * Contact Name
48 48  * Address – this is also presentational; up to 3 addresses are allowed
49 -** House Number
50 50  
51 -== 5.3 Metadata Set ==
49 + § House Number
52 52  
51 +1.
52 +11. Metadata Set
53 +
53 53  An example of reporting metadata according to the MSD described above, is shown below.
54 54  
55 -**Figure 6: Example Metadata Set**
56 +==== Figure 6: Example Metadata Set ====
56 56  
57 57  This example shows:
58 58  
59 59  1. The reference to the Metadata Provision Agreement and Metadata Target
60 60  1. The reported metadata attributes (AttributeSet)
61 -1. Reference Metadata in Data Structure Definition and Dataset
62 +11. Reference Metadata in Data Structure Definition and Dataset
62 62  
63 63  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.
64 64  
... ... @@ -65,8 +65,11 @@
65 65  This is achieved by the following:
66 66  
67 67  * In a DSD, the user may add a reference to one MSD.
68 -* In the Attribute Descriptor of the DSD, the user may include any Metadata Attributes defined in the linked MSD.
69 -** 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).
70 70  * In any Dataset complying with this DSD, Metadata Attributes may be reported according to the specified Attribute Relationship.
71 -** 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.
72 -* 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 +