Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 6.2
edited by Helena
on 2025/05/16 12:08
Change comment: There is no comment for this version
To version 3.1
edited by Helena
on 2025/05/15 15:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +8 Maintenance Agencies and Metadata Providers
Content
... ... @@ -1,10 +1,15 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 += 8 Maintenance Agencies and Metadata Providers =
4 4  
5 -All structural metadata in SDMX is owned and maintained by a maintenance agency (Agency identified by agencyID in the schemas). Similarly, all reference metadata (i.e., MetadataSets) is owned and maintained by a metadata provider organisation (MetadataProvider identified by metadataProviderID in the schemas). It is vital to the integrity of the structural metadata that there are no conflicts in agencyID and metadataProviderID. In order to achieve this, SDMX adopts the following rules:
3 +All structural metadata in SDMX is owned and maintained by a maintenance agency (Agency identified by agencyID in the schemas). Similarly, all reference metadata
6 6  
7 -1. Agencies are maintained in an AgencyScheme (which is a sub class of //OrganisationScheme//); Metadata Providers are maintained in a MetadataProviderScheme.
5 +(i.e., MetadataSets) is owned and maintained by a metadata provider organisation
6 +
7 +(MetadataProvider identified by metadataProviderID in the schemas). It is vital to the integrity of the structural metadata that there are no conflicts in agencyID and metadataProviderID. In order to achieve this, SDMX adopts the following rules:
8 +
9 +1. Agencies are maintained in an AgencyScheme (which is a sub class of //OrganisationScheme//); Metadata Providers are maintained in a
10 +
11 +MetadataProviderScheme.
12 +
8 8  1. The maintenance agency of the Agency/Metadata Provider Scheme must also be declared in a (different) AgencyScheme.
9 9  1. The "top-level" agency is SDMX and this agency scheme is maintained by SDMX.
10 10  1. Agencies registered in the top-level scheme can themselves maintain a single AgencyScheme and a single MetadataProviderScheme. SDMX is an agency in the SDMX AgencyScheme. Agencies in any AgencyScheme can themselves maintain a single AgencyScheme and so on.
... ... @@ -24,14 +24,115 @@
24 24  
25 25  The XML representing this structure is shown below.
26 26  
27 -[[image:1747385891229-249.png]]
32 +**<str:AgencySchemes>**
28 28  
34 +**<str:AgencyScheme agencyID="SDMX" id="AGENCIES">**
35 +
36 +**<com:Name xml:lang="en">Top-level Agency Scheme</com:Name>**
37 +
38 +**<str:Agency id="AA">**
39 +
40 +**<com:Name xml:lang="en">AA Name</com:Name>**
41 +
42 +**</str:Agency>**
43 +
44 +**<str:Agency id="BB">**
45 +
46 +**<com:Name xml:lang="en">BB Name</com:Name>**
47 +
48 +**</str:Agency>**
49 +
50 +**</str:AgencyScheme>**
51 +
52 +**<str:AgencyScheme agencyID="AA" id="AGENCIES">**
53 +
54 +**<com:Name xml:lang="en">AA Agencies</com:Name>**
55 +
56 +**<str:Agency id="CC">**
57 +
58 +**<com:Name xml:lang="en">CC Name</com:Name>**
59 +
60 +**</str:Agency>**
61 +
62 +**<str:Agency id="DD">**
63 +
64 +**<com:Name xml:lang="en">DD Name</com:Name>**
65 +
66 +**</str:Agency> &nbsp;&nbsp;**
67 +
68 +**</str:AgencyScheme>**
69 +
70 +**<str:AgencyScheme agencyID="BB" id="AGENCIES">**
71 +
72 +**<com:Name xml:lang="en">BB Agencies</com:Name>**
73 +
74 +**<str:Agency id="CC">**
75 +
76 +**<com:Name xml:lang="en">CC Name</com:Name>**
77 +
78 +**</str:Agency>**
79 +
80 +**<str:Agency id="DD">**
81 +
82 +**<com:Name xml:lang="en">DD Name</com:Name>**
83 +
84 +**</str:Agency> &nbsp;&nbsp;**
85 +
86 +**</str:AgencyScheme>**
87 +
88 +**<str:AgencyScheme agencyID="AA.DD" id="AGENCIES">**
89 +
90 +**<com:Name xml:lang="en">AA.DD Agencies</com:Name>**
91 +
92 +**<str:Agency id="EE">**
93 +
94 +**<com:Name xml:lang="en">EE Name</com:Name>**
95 +
96 +**</str:Agency>**
97 +
98 +**</str:AgencyScheme>**
99 +
100 +**</str:AgencySchemes>**
101 +
29 29  **Figure 17: Example Agency Schemes Showing a Hierarchy**
30 30  
31 -Examples of Structure definitions that show how Agencies are used, are presented below:
104 +Examples of Structure definitions that show how Agencies are used, are presented below:
32 32  
33 -[[image:1747386478432-897.png]]
106 +**<str:Codelist agencyID="SDMX" id="CL_FREQ" version="1.0.0" &nbsp;**
34 34  
108 +**urn="urn:sdmx:org.sdmx.infomodel.codelist.Codelist=SDMX:CL_FREQ(1.0.0)">**
109 +
110 +**<com:Name xml:lang="en">Frequency</com:Name>**
111 +
112 +**</str:Codelist>**
113 +
114 +**<str:Codelist agencyID="AA" id="CL_FREQ" version="1.0.0" &nbsp;**
115 +
116 +**urn="urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AA:CL_FREQ(1.0.0)">**
117 +
118 +**<com:Name xml:lang="en">Frequency</com:Name>**
119 +
120 +**</str:Codelist>**
121 +
122 +**<str:Codelist agencyID="AA.CC" id="CL_FREQ" version="1.0.0" &nbsp;**
123 +
124 +**urn="urn:sdmx:org.sdmx.infomodel.codelist.Codelist=AA.CC:CL_FREQ(1.0.0)">**
125 +
126 +**<com:Name xml:lang="en">Frequency</com:Name>**
127 +
128 +**</str:Codelist>**
129 +
130 +**<str:Codelist agencyID="BB.CC" id="CL_FREQ" version="1.0.0" &nbsp;&nbsp;&nbsp; urn="urn:sdmx:org.sdmx.infomodel.codelist.Codelist=BB.CC:CL_FREQ(1.0.0)">**
131 +
132 +|(((
133 +**<com:Name xml:lang="en">Frequency</com:Name> &nbsp;&nbsp;&nbsp;**
134 +
135 +**</str:Codelist> &nbsp;&nbsp;&nbsp;**
136 +)))
137 +
138 +
139 +
140 +
35 35  **Figure 18: Example Showing Use of Agency Identifiers**
36 36  
37 37  Each of these maintenance agencies has a Codelist with an identical id 'CL_FREQ'.
1747385891229-249.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -98.5 KB
Content
1747386478432-897.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content