Skip to Content
Last modified by Elena on 2025/09/10 11:19
From version 2.28
edited by Helena
on 2025/07/02 15:32
Change comment: There is no comment for this version
To version 2.31
edited by Helena
on 2025/07/02 15:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -524,9 +524,9 @@
524 524  |(% style="width:267px" %)**SDMX Facet**|(% style="width:729px" %)**XML Schema Facet**
525 525  |(% style="width:267px" %)minLength|(% style="width:729px" %)xs:minLength
526 526  |(% style="width:267px" %)maxLength|(% style="width:729px" %)xs:maxLength
527 -|(% style="width:267px" %)minValue[^1]|(% style="width:729px" %)if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
528 -|(% style="width:267px" %)maxValue[^1]|(% style="width:729px" %)if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
529 -|(% style="width:267px" %)decimals[^1]|(% style="width:729px" %)xs:fractionDigits
527 +|(% style="width:267px" %)minValue{{footnote}}Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric.{{/footnote}}|(% style="width:729px" %)if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
528 +|(% style="width:267px" %)maxValue^^1^^|(% style="width:729px" %)if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
529 +|(% style="width:267px" %)decimals^^1^^|(% style="width:729px" %)xs:fractionDigits
530 530  |(% style="width:267px" %)pattern|(% style="width:729px" %)xs:pattern
531 531  
532 532  [^1]: Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric.
... ... @@ -901,9 +901,9 @@
901 901  
902 902  2. Without the //updatedAfter// and //includeHistory//, but with //detail//, //attributes// or //measures// URL parameters:
903 903  
904 -The response message should contain the retrieved data in a *Merge* dataset (instead of the previous *Information* dataset).
904 +The response message should contain the retrieved data in a //Merge// dataset (instead of the previous *Information* dataset).
905 905  
906 -3. With the *updatedAfter* URL parameter:
906 +3. With the //updatedAfter// URL parameter:
907 907  
908 908  The response must include the information of all previously updated, inserted and deleted data or data-related reference metadata, even if bulk deletions have been used. One of the two approaches are possible:
909 909  
... ... @@ -914,16 +914,14 @@
914 914  
915 915  The DB synchronization use case requires that the generated response must always allow achieving to replicate the exact same punctual data content as currently stored in the queried data source.
916 916  
917 -1. With the *includeHistory* URL parameter:
918 -
919 - Using a number of datasets with *Delete*, *Replace* or *Merge* actions and limited in their validity time span that allow achieving to replicate the exact same punctual data contents as previously stored in the queried data source.
917 +~1. With the *includeHistory* URL parameter:
920 920  
921 -1. With the *asOf* URL parameter:
922 -
923 - The recommendations of 1 and 2 apply depending on the other parameters. In addition, the returned dataset should have its validity time span limited to the point in time requested in the *asOf* parameter.
919 +Using a number of datasets with *Delete*, *Replace* or *Merge* actions and limited in their validity time span that allow achieving to replicate the exact same punctual data contents as previously stored in the queried data source.
924 924  
925 -[^2]: So far this is recommended for systems that do not require backward-compatibility. Later, with SDMX 4.0, this may generally be made mandatory.
921 +2. With the *asOf* URL parameter:
926 926  
923 +The recommendations of 1 and 2 apply depending on the other parameters. In addition, the returned dataset should have its validity time span limited to the point in time requested in the *asOf* parameter.
924 +
927 927  == 4.2 Reference Metadata Actions ==
928 928  
929 929  Reference metadata defined by a Metadataflow or a MetadataProvisionAgreement are exchanged within reference metadatasets, which are maintainable and thus for actions behave like structural metadata (artefacts): When interacting with SDMX Rest web services, the HTTP action verbs GET, PUT and POST are used to indicate the intended action per web request. Consequently, different actions cannot be bundled and executed with “transactional ACIDity”. Note that metadatasets retrieved using the HTTP header “Accept-Language” may contain only partial languages, and thus should be marked with its *isPartialLanguage* property set to true. Submitting such a partial metadataset to update an SDMX storage system will only add or update the included languages but not change other languages.