update tld convention (#206) (#210)

* Delete WIS2-Development directory

* update tld convention (#206)

Author: tomkralidis

guide/sections/part2/global-services.adoc

@@ -92,7 +92,7 @@ In the following sections, and for each Global Service, a set of metrics is defi
 * A Global Broker will republish a message only once. It will record the message identifier (``id``) (as defined in the WIS2 Notification Message) of messages already published and will discard subsequent identical messages (those with the same message ``id``). This is the anti-loop feature of the Global Broker.
 * When publishing a message to the local broker, the metric ``wmo_wis2_gb_messages_published_total`` will be increased by 1.
 * All above-defined metrics will be made available on HTTPS endpoints that the Global Monitor will ingest from regularly.
-* As a convention, the Global Broker centre-id will be ``tld-{centre-name}-global-broker``.
+* As a convention, the Global Broker centre-id will be ``{tld}-{centre-name}-global-broker``.
 * A Global Broker should operate with a fixed IP address so that WIS2 Nodes can permit access to download resources based on IP address filtering. A Global Broker should also operate with a publicly resolvable Domain Name System (DNS) name pointing to that IP address. The WMO Secretariat must be informed of the IP address and/or hostname and any subsequent changes.
 
 ==== 2.7.4 Global Cache
@@ -121,7 +121,7 @@ In WIS2, Global Caches provide access to WMO core data for data consumers. This
 * If core data are not cached on a Global Cache (that is, if the data are flagged as ``"cache": false`` or if the Global Cache decides not to cache these data), the Global Cache shall nevertheless republish the WIS2 Notification Message to the ``cache/a/wis2/...`` topic. In this case, the message id will be changed, and the rest of the message will not be modified.
 * A Global Cache should operate with a fixed IP address so that WIS2 Nodes can permit access to download resources based on IP address filtering. A Global Cache should also operate with a publicly resolvable DNS name pointing to that IP address. The WMO Secretariat must be informed of the IP address and/or hostname, and any subsequent changes.
 * A Global Cache should validate the integrity of the resources it caches and only accept data that match the integrity value from the WIS2 Notification Message. If the WIS2 Notification Message does not contain an integrity value, the Global Cache should accept the data as valid. In this case, the Global Cache may add an integrity value to the message it republishes.
-* As a convention, the Global Cache centre-id will be ``tld-{centre-name}-global-cache``.
+* As a convention, the Global Cache centre-id will be ``{tld}-{centre-name}-global-cache``.
 
 ===== 2.7.4.2 Practices and procedures
 
@@ -183,7 +183,7 @@ In WIS2, Global Caches provide access to WMO core data for data consumers. This
 * A Global Discovery Catalogue will generate and store a zip file of all WCMP2 records once a day; this file will be made be accessible via HTTP. The zipfile will include a directory named after the centre-id of the Global Discovery Catalogue containing all WCMP2 records.
 * A Global Discovery Catalogue will publish a WIS2 Notification Message of its zip file of all WCMP2 records on its centre-id's +metadata+ topic (for example, `origin/a/wis2/centre-id/metadata`, where `centre-id` is the centre identifier of the Global Discovery Catalogue).
 * A Global Discovery Catalogue may initialize itself (cold start) from a zip file of all WCMP2 records published.
-* As a convention, a Global Discovery Catalogue's centre-id will be ``tld-{centre-name}-global-discovery-catalogue``.
+* As a convention, a Global Discovery Catalogue's centre-id will be ``{tld}-{centre-name}-global-discovery-catalogue``.
 
 ===== 2.7.5.2 Global Discovery Catalogue Reference Implementation: wis2-gdc
 
@@ -212,5 +212,5 @@ wis2-gdc is managed as a free and open source project. Source code, issue tracki
 * The Global Monitor will collect metrics as defined in the OpenMetrics standard.
 * The Global Monitor will monitor the "health" (that is, the performance) of components at NCs/DCPCs, as well as Global Services.
 * The Global Monitor will provide a web-based dashboard that displays the WIS2 system performance and data availability.
-* As a convention, the Global Monitor centre-id will be ``tld-{centre-name}-global-monitor``.
+* As a convention, the Global Monitor centre-id will be ``{tld}-{centre-name}-global-monitor``.
 * The main task of the Global Monitor will be to regularly query the metrics provided by the relevant WIS2 entities, aggregate and process the data and then provide the results to the end user in a suitable presentation.