Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 26.2
edited by Helena
on 2025/06/11 00:14
Change comment: There is no comment for this version
To version 25.1
edited by Helena
on 2025/06/08 21:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,1 +1,0 @@
1 -Agency scheme|Artefact|Attribute|Category|Category scheme|Code|Code list|Component|Concept scheme|Data consumer|Data consumer scheme|Data provider|Data provider scheme|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchy|Identifiable artefact|Item scheme|Maintainable artefact|Maintenance agency|Measure|Member selection|Metadata repository|Metadata set|Metadata structure definition|Metadataflow|Nameable artefact|Notification|Organisation unit scheme|Provision agreement|Reference metadata|Reference period|Representation|SDMX Information Model|SDMX Registry|SDMX-JSON|SDMX-ML|Series key|Statistical data and metadata exchange|Structural metadata|Subscription|Time period|Timeliness|Validation and transformation language|Versionable artefact|isExternalReference
Content
... ... @@ -385,8 +385,6 @@
385 385  
386 386  An example of this is shown in the XML snippet below:
387 387  
388 -[[image:1749590035576-196.png]]
389 -
390 390  **Figure 8: Example Showing Use of Agency Identifiers**
391 391  
392 392  Each of these [[maintenance agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]] has an identical [[Code list>>doc:sdmx:Glossary.Code list.WebHome]] with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure.
1749590035576-196.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -46.8 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]