From 95e7907d0b6315a0f993d55a70e0cd7e4a28aee9 Mon Sep 17 00:00:00 2001 From: Jason Fox Date: Wed, 19 Nov 2025 14:36:23 +0100 Subject: [PATCH] Clarify what to do while merging two Attributes --- md/clause-8.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/md/clause-8.md b/md/clause-8.md index 663a462..7cb0b7e 100644 --- a/md/clause-8.md +++ b/md/clause-8.md @@ -681,11 +681,13 @@ attribute is present at the Entity level: In case of conflicting information for an Attribute, where a _`datasetId`_ is duplicated, but there are differences in the other attribute data, if an _`expiresAt`_ _DateTime_ is present on the Attribute and the date lies in the -past, it shall be discarded, thereafter the one with the most recent -_`observedAt`_ _DateTime_, if present, and otherwise the one with the most -recent _`modifiedAt`_ _DateTime_ shall be provided. If no other mechanism for -determining the most current Attribute instance is found, the NGSI-LD system -shall choose the Attribute instance at random and the result is indeterminate. +past, it shall be discarded. Thereafter, any attribute data where an +_`observedAt`_ _DateTime_ is present shall take precedence, with the one with +the most recent _`observedAt`_ _DateTime_ being provided. If no _`observedAt`_ +is present, the attribute data with the most recent _`modifiedAt`_ _DateTime_ +shall be provided. If no other mechanism for determining the most current +Attribute instance is found, the NGSI-LD system shall choose the Attribute +instance at random and the result is indeterminate. When conflicting information is received for the non-reified _`expiresAt`_ attribute at an Entity level: -- GitLab