Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/05/21 15:51
Change comment: There is no comment for this version
To version 9.1
edited by Helena
on 2025/05/23 01:07
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  
... ... @@ -448,7 +448,7 @@
448 448  
449 449  [[image:1747824123012-527.jpeg]]
450 450  
451 -*
451 +*
452 452  ** Figure 7: Example of Hierarchic Structure of Agencies
453 453  
454 454  The following organizations maintain an Agency Scheme.
... ... @@ -464,7 +464,7 @@
464 464  
465 465  An example of this is shown in the XML snippet below.
466 466  
467 -[[image:1747824123013-196.jpeg||height="309" width="446"]]
467 +[[image:1747832400104-286.png]]
468 468  
469 469  **Figure 8: Example Showing Use of Agency Identifiers**
470 470  
... ... @@ -478,7 +478,8 @@
478 478  
479 479  ==== 6.2.2.2 URN Structure ====
480 480  
481 -===== //Case Rules for URN// =====
481 +(% class="wikigeneratedid" id="HCaseRulesforURN" %)
482 +//Case Rules for URN//
482 482  
483 483  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.
484 484  
1747832400104-286.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +172.3 KB
Content