Add note to Guide about how data consumers should handle notification messages with updates #218
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dealing with update messages, tracking pubtime etc. as discussed by ET-W2IT in Nov-2025. See #142 (comment)
Collaborator
|
@6a6d74 looks like you'll need to rebase, based on main branch. |
amilan17
reviewed
Jan 5, 2026
|
|
||
| A discovery metadata record or notification message may provide more than one download link. The preferred link will be identified as "canonical" (link relation: "rel": "canonical" footnote:[See Internet Assigned Numbers Authority (IANA) Link Relations: https://www.iana.org/assignments/link-relations/link-relations.xhtml]). | ||
|
|
||
| A data consumer should expect to receive multiple notification messages about the same data item. Nor should data consumers assume that messages arrive in time-sequence order (i.e., newest published message, as indicated by ``properties.pubtime``, arriving last). Consequently, for notification messages relating to the same data item (i.e., notification messages with identical ``properties.data_id``), they should: |
Member
There was a problem hiding this comment.
Adjust one of the sentences?
"A data consumer should NOT expect to receive multiple notification messages about the same data item. Nor should data consumers assume..."
OR
"A data consumer should expect to receive multiple notification messages about the same data item. However, data consumers should NOT assume..."
Collaborator
Author
There was a problem hiding this comment.
I took the second suggestion.
Amending text as suggested by @amilan17
tomkralidis
approved these changes
Jan 6, 2026
6a6d74
added a commit
that referenced
this pull request
Jan 6, 2026
… messages with updates Clarify expectations for data consumers regarding notification messages and their processing. This replaces PR #218
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed by ET-W2IT. See #142