Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 9.3
edited by Helena
on 2025/05/23 13:00
Change comment: There is no comment for this version
To version 4.1
edited by Helena
on 2025/05/21 15:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SDMX 2.1 Standards. Section 5. Registry Specification – Logical Interfaces
1 +SDMX 2.1 Standards. Section. 5. Registry Specification – Logical Interfaces
Content
... ... @@ -326,7 +326,7 @@
326 326  Subscription management involves a user submitting a subscription request which contains:
327 327  
328 328  * a query or constraint expression in terms of a filter which defines the events for which the user is interested (e.g. new data for a specific dataflow, or for a domain category, or changes to a Data Structure Definition).
329 -* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto : ) and HTTP POST (a normal http:~/~/ address)
329 +* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address)
330 330  * request for a list of submitted subscriptions
331 331  * deletion of a subscription
332 332  
... ... @@ -427,8 +427,6 @@
427 427  
428 428  The Maintenance Agency in SDMX is maintained in an Agency Scheme which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
429 429  
430 -[[image:1747994320263-112.png]]
431 -
432 432  **Figure 6: Agency Scheme Model**
433 433  
434 434  The Agency in SDMX is extremely important. The Agency Id system used in SDMX is an n-level structure. The top level of this structure is maintained by SDMX. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The Agency Scheme has a fixed id and version and is never declared explicitly in the SDMX object identification mechanism.
... ... @@ -450,7 +450,8 @@
450 450  
451 451  [[image:1747824123012-527.jpeg]]
452 452  
453 -**Figure 7: Example of Hierarchic Structure of Agencies**
451 +*
452 +** Figure 7: Example of Hierarchic Structure of Agencies
454 454  
455 455  The following organizations maintain an Agency Scheme.
456 456  
... ... @@ -465,7 +465,7 @@
465 465  
466 466  An example of this is shown in the XML snippet below.
467 467  
468 -[[image:1747832400104-286.png]]
467 +[[image:1747824123013-196.jpeg||height="309" width="446"]]
469 469  
470 470  **Figure 8: Example Showing Use of Agency Identifiers**
471 471  
... ... @@ -479,8 +479,7 @@
479 479  
480 480  ==== 6.2.2.2 URN Structure ====
481 481  
482 -(% class="wikigeneratedid" id="HCaseRulesforURN" %)
483 -//Case Rules for URN//
481 +===== //Case Rules for URN// =====
484 484  
485 485  For the URN, all parts of the string are case sensitive. The Id of any object must be UPPER CASE. Therefore, CRED_ext_Debt is invalid and it should be CRED_EXT_DEBT.
486 486  
1747832400104-286.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -172.3 KB
Content
1747994320263-112.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -13.9 KB
Content