Changes for page Part IV. Data and Reference Metadata Namespaces
Last modified by Elena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -897,9 +897,9 @@ 897 897 898 898 ~1. Without the //updatedAfter//, //includeHistory//, //detail//, //attributes// or //measures// URL parameters: 899 899 900 -The response message should contain the retrieved data in a //Replace//dataset (instead of the previous *information* dataset).900 +The response message should contain the retrieved data in a *Replace* dataset (instead of the previous *information* dataset). 901 901 902 -2. Without the //updatedAfter//and//includeHistory//, but with//detail//,//attributes//or//measures//URL parameters:902 +2. Without the *updatedAfter* and *includeHistory*, but with *detail*, *attributes* or *measures* URL parameters: 903 903 904 904 The response message should contain the retrieved data in a *Merge* dataset (instead of the previous *Information* dataset). 905 905 ... ... @@ -912,7 +912,8 @@ 912 912 * a //Delete// dataset for entirely deleted observations, for entirely deleted sets of (data-related reference metadata) attribute values attached to specific dimension combinations and for individually deleted mesure, attribute and reference metadata values and 913 913 a //Merge// dataset for all other updated or inserted observation, attribute and data-related reference metadata values. 914 914 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. 915 + 916 + 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 917 1. With the *includeHistory* URL parameter: 918 918