Closed hhaddouch closed 10 months ago
The versioning will be part of the additional metadata but not part of the hierarchy. We could use version=1, version=2, etc.
@sebvi additional metadata can live in the notification message or in WMO Core Medata (WCMP2)
The versioning will be part of the additional metadata but not part of the hierarchy. We could use version=1, version=2, etc.
I agree that numeric version would be better than a string. There may be situations where the same fields could be sent multiple times with updates.
@sebvi suggested that apart from the keyword on versioning, it will be helpful to have another keyword to say what was the problem in the previous version.
FYI PR in https://github.com/wmo-im/wis2-notification-message/pull/48 to add an operation type to identify if a resource has been created (default), updated or deleted.
for WNM approach: wmo-im/wis2-notification-message#47 and https://wmo-im.github.io/wis2-notification-message/standard/wis2-notification-message-DRAFT.html#_links
for WCMP2 approach: https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.html#_properties_record_update_date
Close ?
NWPMD meeting on 2023.09.14
Need to clarify the mechanism of notification for a new version of a data file (e.g. in case published data files need to be replaced). The idea is to identify how users can be notified that a new version (corrective) version of data is published. On the GTS for observation data, we have this information(corrective) in the header. In WIS2 we can mention something like "correction" in the message!!
26 Juin 2023
DECISION
properties.operation is included in the notification message
value= create/update/delete, if multiple update messages are received, compare with pub_time
wis2-guide/Notification-mechanism-updated-data.adoc at transition · wmo-im/wis2-guide · GitHub