Skip to content

Commit

Permalink
updates to Global Replay definition
Browse files Browse the repository at this point in the history
  • Loading branch information
tomkralidis committed Aug 2, 2024
1 parent 4faf37b commit eedd477
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 3 deletions.
11 changes: 9 additions & 2 deletions guide/sections/part2/global-services.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -222,12 +222,17 @@ wis2-gdc is managed as a free and open source project. Source code, issue track

===== Technical considerations

* The Global Replay provides Global Services and Data Consumers with a mechanism to search and query for notification messages of interest.
* The Global Replay provides Global Services and data consumers with a mechanism to search, query and subscribe to notification messages of interest.
* The Global Discovery Catalogue implements the OGC API – Features – Part 1: Core standardfootnote:[https://docs.ogc.org/is/17-069r4/17-069r4.html], adhering to the following conformance classes and their dependencies.
** Core
** GeoJSON
* The Global Replay implements the OGC API – Processes - Part 1: Core standardfootnote:[https://docs.ogc.org/is/18-062r2/18-062r2.html], adhering to the following conformance classes and their dependencies.
** Core
** OGC Process Description
** JSON
* A Global Replay shall subscribe to the topics `+origin/a/wis2/#+` and `+cache/a/wis2/#+`.
* The Global Replay will make notification messages available via the collection identifiers `wis2-notification-messages-cache` and `wis2-notification-messages-cache`.
* The Global Replay will make notification messages available via the collection identifier `wis2-notification-messages`.
* The Global Replay will provide a process to allow for users to subscribe to messages with various criteria (spatial and / or temporal extent, topic selection).
* A single Global Replay instance is sufficient for WIS2.
* Multiple Global Replay instances may be deployed for resilience.
* Global Replay instances operate independently of each other; each Global Replay instance will hold notification messages according to the required retention period. Global Replays do not need to synchronise between themselves.
Expand All @@ -247,6 +252,8 @@ wis2-grep provides functionality required for the Global Replay, providing the f

* notification messages subscription from the Global Broker
* notification message ingest and API publication
* user defined subscription for MQTT message replay
* OGC API - Features - Part 1: Core compliance
* OGC API - Processes - Part 1: Core compliance

wis2-grep is managed as a free and open source project. Source code, issue tracking and discussions are hosted in the open on GitHub: https://github.com/wmo-im/wis2-grep.
2 changes: 1 addition & 1 deletion guide/sections/part2/wis2-architecture.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ Please refer to the _Manual on WIS_, Volume II for details.

==== 2.4.6 Global Replay
* WIS2 may include a Global Replay.
* A Global Replay enables Global Services and data consumers to search and query notification messages published by the Global Broker.
* A Global Replay enables Global Services and data consumers to search, query and subscribe to notification messages published by the Global Broker.
* A Global Replay subscribes to notification messages via a Global Broker about the availability of new notification messages. It downloads a copy of the notification message and updates its local index.
* A Global Replay shall retain copies of notification messages for a duration compatible with the real-time or near real-time schedule of the data and not less than 24-hours.
* A Global Replay will delete notification messages from its local index once the retention period has expired.
Expand Down

0 comments on commit eedd477

Please sign in to comment.