Changes for page Part IV. Data and Reference Metadata Namespaces

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -891,11 +891,11 @@
891	891
892	892	Likewise, all SDMX-compliant systems that do (or are configured to) support the //updatedAfter// URL parameter need to systematically retain the information about deleted data (or data-related reference metadata).
893	893
894		-All datasets – even with varying actions – within a single data message have always to be treated as **ACID transaction** to guarantee “transactional safety” (full data consistency and validity despite errors, power failures, and other mishaps). These datasets are to be processed in the order of appearance in the message. The advantage of such data messages is thus the ability to bundle separate *delete* and *replace* or *merge* actions into one transactional data message.
	894	+All datasets – even with varying actions – within a single data message have always to be treated as **ACID transaction** to guarantee “transactional safety” (full data consistency and validity despite errors, power failures, and other mishaps). These datasets are to be processed in the order of appearance in the message. The advantage of such data messages is thus the ability to bundle separate //delete// and //replace// or //merge// actions into one transactional data message.
895	895
896	896	**Recommended[^2] dataset actions in SDMX web service responses to GET data queries:**
897	897
898		-1. Without the *updatedAfter*, *includeHistory*, *detail*, *attributes* or *measures* URL parameters:
	898	+1. Without the //updatedAfter//, //includeHistory//, //detail//, //attributes// or //measures// URL parameters:
899	899
900	900	The response message should contain the retrieved data in a *Replace* dataset (instead of the previous *information* dataset).
901	901