Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 22.8
edited by Helena
on 2025/06/08 16:55
Change comment: There is no comment for this version
To version 22.7
edited by Helena
on 2025/06/08 16:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -361,9 +361,11 @@
361 361  * Agencies registered in the top-level scheme can themselves maintain a single Agency Scheme. Agencies in these second-tier schemes can themselves maintain a single Agency Scheme and so on.
362 362  * The AgencyScheme has a fixed version, i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other Artefacts follow.
363 363  * There can be only one AgencyScheme maintained by any one Agency. It has a fixed id of AGENCIES.
364 -* The /hierarchy of Organisation is not inherited by Maintenance Agency – thus each Agency Scheme is a flat list of Maintenance Agencies.
365 -* The format of the agency identifier is agencyID.agencyID etc. The top-level agency in this identification mechanism is the agency registered in the SDMX agency scheme. In other words, SDMX is not a part of the hierarchical ID structure for agencies. However, SDMX is, itself, a maintenance agency and is contained in the top-level Agency Scheme.
366 366  
365 +• The /hierarchy of Organisation is not inherited by Maintenance Agency – thus each Agency Scheme is a flat list of Maintenance Agencies.
366 +
367 +• The format of the agency identifier is agencyID.agencyID etc. The top-level agency in this identification mechanism is the agency registered in the SDMX agency scheme. In other words, SDMX is not a part of the hierarchical ID structure for agencies. However, SDMX is, itself, a maintenance agency and is contained in the top-level Agency Scheme.
368 +
367 367  This supports a hierarchical structure of agencyID.
368 368  
369 369  An example is shown below.