Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.8
edited by Helena
on 2025/06/08 23:30
Change comment: There is no comment for this version
To version 1.9
edited by Helena
on 2025/06/08 23:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -579,8 +579,7 @@
579 579  
580 580  Full details can be found in the SDMX RESTful web services specification.
581 581  
582 -1.
583 -11. Structural Metadata Querying Best Practices
582 +== 4.4 Structural Metadata Querying Best Practices ==
584 584  
585 585  When querying for structural metadata, the ability to state how references should be resolved is quite powerful. However, this mechanism is not always necessary and can create an undue burden on the systems processing the queries if it is not used properly.
586 586  
... ... @@ -588,7 +588,6 @@
588 588  
589 589  When the referenced object is not known, then the reference resolution mechanism could be used. For example, suppose one wanted to find all category schemes and the related categorisations for a given maintenance agency. In this case, one could query for the category scheme by the maintenance agency and specify that parent and sibling references should be resolved. This would result in the categorisations which reference the categories in the matched schemes to be returned, as well as the object which they categorise.
590 590  
591 -
592 592  ----
593 593  
594 594  [[~[1~]>>path:#_ftnref1]] Regular expressions, as specified in [[W3C XML Schema Definition Language (XSD)>>url:https://www.w3.org/TR/xmlschema11-2/]][[ >>url:https://www.w3.org/TR/xmlschema11-2/]][[1.1 Part 2: Datatypes>>url:https://www.w3.org/TR/xmlschema11-2/]][[.>>url:https://www.w3.org/TR/xmlschema11-2/]]