You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changing the requirement to RFC 9562 would allow data providers to use these new UUID versions making the specification more future proof but other introduced UUIDs like Nill UUID and Max UUID should probably excluded to ensure uniqueness.
The text was updated successfully, but these errors were encountered:
The id property SHALL be a Universally Unique Identifier (UUID).
It is true that the clause 1.4 Identifier then mentions the RFC 4122. But that can be relaxed. We (the TT-WISMD) team do not have any special preference for this type of UUID or other type, as long as it is unique. So you may even use Nill UUID (00000000-0000-0000-0000-000000000000) as long as you can guarantee that no one is ever going to use it again :-)
The WMN specification requires message identifiers to be UUIDs conforming to RFC 4122 (section 1.4, https://github.com/wmo-im/wis2-notification-message/blob/main/standard/sections/clause_7_normative_text.adoc) . This RFC has been superseeded by RFC 9562 recently including new UUID variants such as time-ordered UUIDv7.
Changing the requirement to RFC 9562 would allow data providers to use these new UUID versions making the specification more future proof but other introduced UUIDs like Nill UUID and Max UUID should probably excluded to ensure uniqueness.
The text was updated successfully, but these errors were encountered: