Skip to Content

Changes for page 5 Reference Metadata

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