Difference between revisions of "Agency Scheme V10"

From FMR Knowledge Base
Jump to navigation Jump to search
(Identity)
 
(34 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:SDMX Structures]]
+
[[Category:SDMX 2.1 Structures]]
 +
== Overview ==
 +
[[File:SDMX Agency Diagram.PNG|Agency Diagram|thumbnail]]
 +
An Agency Scheme contains a non-hierarchic list of [[Agency V10|Agencies]] and is a type of [[Organisational_Schemes V10|Organsiation Scheme]].
 +
 
 +
Agencies own and maintain [[Maintainable V10|Maintainable]] structures.
 +
 
 +
The top-level Agency Scheme is the scheme for which SDMX is the maintenance agency and is termed the "SDMX Agency Scheme". Every Agency in every Agency Scheme must be related directly or indirectly via intervening Agency Schemes, to an Agency registered in the SDMX Agency Scheme. In this way each Agency can be identified uniquely by the combination of Agencies in the path from the SDMX Agency Scheme to the Agency Scheme in which it resides, plus its own identity in that scheme.
  
== Overview ==
+
In practice, organisations implementing SDMX create an Agency for themselves in a local copy of the SDMX Agency Scheme. Organisations can ask to be added to the master SDMX Agency Scheme which is maintained in the [https://registry.sdmx.org SDMX Global Registry], however for many this is unnecessary unless planning to publish structures for global use.
An SDMX Agency Scheme is a container for all [[Agency|Agencies]].
+
 
 +
Organisations can define sub-agencies by setting their own Agency as the owner rather than SDMX. Sub-agencies have IDs of the form ''[Agency ID].[Sub-agency]'', for instance ''XYZ.DEPTA''. In theory, Sub-agencies can themselves have Sub-agencies, but this approach is rarely used in practice.
  
 
==Structure Properties==
 
==Structure Properties==
 
{| class="wikitable"
 
{| class="wikitable"
 
! scope=row style="text-align: left;" | Structure Type  
 
! scope=row style="text-align: left;" | Structure Type  
| Standard SDMX Structural Metadata Artifact
+
| Standard SDMX Structural Metadata Artefact
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Maintainable
 
! scope=row style="text-align: left;"  | Maintainable
| [[Maintainable|Yes]]
+
| [[Maintainable_V10|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Identifiable
 
! scope=row style="text-align: left;"  | Identifiable
| [[Identifiable|Yes]]
+
| [[Identifiable V10|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Item Scheme
 
! scope=row style="text-align: left;"  | Item Scheme
| | [[Item_Scheme|Yes]]
+
| [[Item_Scheme|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
Line 31: Line 39:
 
==Context within the SDMX 2.1 Information Model==
 
==Context within the SDMX 2.1 Information Model==
  
[[File:L_AgencyScheme.png|900px]]
+
[[File:L_AgencyScheme.png|Agency Scheme|600px]]
 
 
== Identity ==
 
The SDMX Agency Scheme uses the Prefix of SDMX and has Identity of AGENCIES and the Name 'SDMX Agency Scheme'. This will hold all the Agencies created in the Registry.
 
 
 
If a Sub Agency is created the Prefix becomes the ID of the owning agency, with an ID of AGENCIES and the Name of 'AGENCIES' as shown in the example below.
 
 
 
[[File:AgencyScheme_List.PNG|900px]]<br>
 
 
 
 
 
 
 
Data Consumer Scheme is given the identity DATA_CONSUMER prefixed by the Identifier of the owning Agency. For example, GOT:DATA_CONSUMER would refer to the container for all Data Consumers owned by the Agency GOT.
 
 
 
If a Sub Agency existed with for example the ID of 'WEST', the Data Consumer Scheme would be named GOT.WEST:DATA_CONSUMERS, if [[Data_Consumers|Data Consumers]] had been created for the Sub Agency.
 
 
 
[[URN|You can seem more examples and information on Identities in this article]].
 
 
 
== Content ==
 
Other then an Identification, an Data Provider has a Name (multilingual), Description (multilingual) and can have zero to many [[Contacts|Contacts]].
 

Latest revision as of 08:53, 25 August 2022

Overview

Agency Diagram

An Agency Scheme contains a non-hierarchic list of Agencies and is a type of Organsiation Scheme.

Agencies own and maintain Maintainable structures.

The top-level Agency Scheme is the scheme for which SDMX is the maintenance agency and is termed the "SDMX Agency Scheme". Every Agency in every Agency Scheme must be related directly or indirectly via intervening Agency Schemes, to an Agency registered in the SDMX Agency Scheme. In this way each Agency can be identified uniquely by the combination of Agencies in the path from the SDMX Agency Scheme to the Agency Scheme in which it resides, plus its own identity in that scheme.

In practice, organisations implementing SDMX create an Agency for themselves in a local copy of the SDMX Agency Scheme. Organisations can ask to be added to the master SDMX Agency Scheme which is maintained in the SDMX Global Registry, however for many this is unnecessary unless planning to publish structures for global use.

Organisations can define sub-agencies by setting their own Agency as the owner rather than SDMX. Sub-agencies have IDs of the form [Agency ID].[Sub-agency], for instance XYZ.DEPTA. In theory, Sub-agencies can themselves have Sub-agencies, but this approach is rarely used in practice.

Structure Properties

Structure Type Standard SDMX Structural Metadata Artefact
Maintainable Yes
Identifiable Yes
Item Scheme Yes
SDMX Information Model Versions 1.0, 2.0, 2.1
URN - AgencyScheme namespace urn:sdmx:org.sdmx.infomodel.base.AgencyScheme
Example urn:sdmx:org.sdmx.infomodel.base.AgencyScheme=SDMX:AGENCIES(1.0)

Context within the SDMX 2.1 Information Model

Agency Scheme