Changes for page 5 Reference Metadata

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -24,16 +24,18 @@
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	+
27	27	**Figure 2: The high-level view of the MSD containing one Metadata Attribute Descriptor**
28	28
	30	+
29	29	**Figure 3: Wildcarded Target Objects as specified in a Metadataflow**
30	30
	33	+
31	31	**Figure 4: Specific Target Objects as specified in a Metadata Provision Agreement**
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		-1.
36		-11. Metadata Structure Definition
	38	+== 5.2 Metadata Structure Definition ==
37	37
38	38	An example is shown below.
39	39
...	...	@@ -41,25 +41,22 @@
41	41
42	42	This example shows the following hierarchy of Metadata Attributes:
43	43
44		-• Contact – this is presentational; no metadata is expected to be reported at this level
45		-
	46	+* Contact – this is presentational; no metadata is expected to be reported at this level
46	46	* Contact Name
47	47	* Address – this is also presentational; up to 3 addresses are allowed
	49	+** House Number
48	48
49		- § House Number
	51	+== 5.3 Metadata Set ==
50	50
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 ====
	55	+**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		-11. Reference Metadata in Data Structure Definition and Dataset
	61	+1. 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,11 +66,8 @@
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. o For each link to a Metadata Attribute, an Attribute Relationship may be specified (similarly to that for Data Attributes).
	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).
70	70	* In any Dataset complying with this DSD, Metadata Attributes may be reported according to the specified Attribute Relationship.
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		-
	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”).