-
Domain specific levels (level 9 and beyond) SHALL be determined by domain experts and user communities.
+Domain specific levels (level 8 and beyond) SHALL be determined by domain experts and user communities.
International Telecommunications Union (ITU): T.50 : International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange [9]
+IANA: Root Zone Database (2023) [10]
+Publish / Subscribe
PR
Permanent Representative
TLD
Top-level domain
URI
Uniform Resource Identifier
The structure of the topic hierarchy underpins the discovery and sharing of data in WIS, and requires standardization across all WIS services to provide consistent filter and access to the user.
Recalling that WIS is designed to support the WMO Unified Data Policy, the topic hierarchy must be aligned with WMO Res. 1 Cg-EXT-21 - Unified Data Policy.:[10]
+Recalling that WIS is designed to support the WMO Unified Data Policy, the topic hierarchy must be aligned with WMO Res. 1 Cg-EXT-21 - Unified Data Policy[11].
Final approval of the WTH updates will go through the WMO fast-track amendment process.[11]
+Final approval of the WTH updates will go through the WMO fast-track amendment process.[12]
Primary topic levels (levels 1-8): topic structure applies to all data and services in WIS
+Primary topic levels (levels 1-7): topic structure applies to all data and services in WIS
Domain specific topic subcategory levels (level 9 and beyond): topic structure proposed by domain experts and user communities. Note that the number of levels in this part may vary according to the requirements of various domains.
+Domain specific topic subcategory levels (level 8 and beyond): topic structure proposed by domain experts and user communities. Note that the number of levels in this part may vary according to the requirements of various domains.
B
Domain specific levels (level 9 and beyond) SHALL be determined by domain experts and user communities.
+Domain specific levels (level 8 and beyond) SHALL be determined by domain experts and user communities.
C
Domain specific levels (level 9 and beyond) SHALL be coordinated and integrated by the WMO Task Team on WIS Metadata.
+Domain specific levels (level 8 and beyond) SHALL be coordinated and integrated by the WMO Task Team on WIS Metadata.
once consensus is reached, TT-WISMD approves the proposal for inclusion into the next release of WTH
Final approval of the WTH updates will go through the WMO fast-track amendment process.[12]
+Final approval of the WTH updates will go through the WMO fast-track amendment process.[13]
G
A renaming or removal in the WMO Notification Message Format SHALL result in a major version update.
+A renaming or removal in the WMO Notification Message encoding SHALL result in a major version update.
D
All topic level definitions SHALL utilize dashes (-).
All topic level definitions SHALL utilize dashes (-) to separate words (e.g. sea-ice).
The centre identifier (centre-id) is an acronym as specified by the member and endorsed by the PR of the country and WMO. It is a single identifier comprised of a TLD and centre name, and represents the data publisher, distributor or issuing centre of a given dataset or data product/granule.
Requirement 4 |
+
+ /req/core/centre-id + |
+
A |
+
+
+A centre identifier SHALL be formatted as
+
+
+ + + |
+
B |
+
+ The |
+
Recommendation 5 |
+
+ /rec/core/centre-id + |
+
A |
+
+ Organizations operating with a |
+
B |
+
+ International organizations operating with a |
+
C |
+
+ Organizations wishing to test their WIS2 Node or Global Service MAY provide the |
+
Permission 6 |
+
+ /per/core/centre-id + |
+
A |
+
+ A centre identifier’s |
+
B |
+
+ Larger organizations providing multiple centres MAY use dashes in the |
+
C |
+
+ A centre providing a WIS service MAY further qualify the function within the |
+
For maximum utility and efficient management of topics, data, metadata, and reports need to be published to a minimum level. This helps with avoiding "pollution" of messages in higher level topics which are used to delineate core concepts (centre identification, notification types, data policy, etc.).
Requirement 4
Requirement 7
/req/core/publishing
Permission 5
Permission 8
/per/core/publishing
This requirement is not applicable to ATS testing.
+/conf/core/conventions
+/req/core/conventions
+Validate that a given topic meets the conventions of WTH.
+Check that all characters in the topic are lowercase.
+Check that all characters in the topic are based on ASCII T.50.
+Check that no characters in the topic contain dots (.).
/conf/core/centre-id
+/req/core/centre-id
+Validate that a centre identifier is valid.
+Check that the first component of the centre identifier is a valid TLD as defined by IANA[15].
+origin/a/wis2/can/eccc-msc/data/core/weather/surface-based-observations/synoporigin/a/wis2/ca-eccc-msc/data/core/weather/surface-based-observations/synopcache/a/wis2/deu/dwd/metadata/core/wcmp2cache/a/wis2/de-dwd/metadata/core/wcmp2OASIS: MQTT Version 5.0 (2019) [13]
+OASIS: MQTT Version 5.0 (2019) [16]
OASIS: MQTT Version 3.1.1 (2014) [14]
+OASIS: MQTT Version 3.1.1 (2014) [17]
Wikipedia: Publish-subscribe pattern (2023) [15]
+Wikipedia: Publish-subscribe pattern (2023) [18]
International Telecommunications Union (ITU): T.50 : International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange [16]
+International Telecommunications Union (ITU): T.50 : International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange [19]