Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

4.1             General

4.1.1               There are 15 9 technical specifications (WIS2-TechSpecs) that define the interfaces to the major WIS2 functions. The specifications for these interfaces are described in more detail in Appendix D and are named and numbered as follows:

  1. Uploading  PUBLICATION of metadata for data and products SERVICES

  2. Uploading EXCHANGE of data and products;

  3. Centralization of globally distributed dataPROVISION OF GLOBAL SERVICES;

  4. Maintenance of user identification and role informationOPERATING A GLOBAL BROKER;

  5. Consolidated view of distributed identification and role informationOPERATING A GLOBAL CACHE;

  6. Authentication of a user OPERATING A GLOBAL DISCOVERY CATALOGUE;

  7. Publishing metadata as a National Center or Data Collection and Production CenterAuthorization of a user role;

  8. Operating data Exchange as a National Center or Data Collection and Production CenterDAR metadata (WIS discovery metadata) catalogue search and retrieval;

  9. Monitoring compliance Consolidated view of distributed DAR metadata (WIS discovery metadata) catalogues;

10.  Downloading files via dedicated networks;

11.  Downloading files via non-dedicated networks;

12.  Downloading files via other methods;

13.  Maintenance of dissemination metadata;

14.  Consolidated view of distributed dissemination metadata catalogues;

15.  Reporting of quality of service.

4.1.2               NCs shall support seven of the 15 technical specifications, specifically WIS-TechSpec-1, -2, -45, -1011, -1112, -12 13 and -15. An NC can arrange through bilateral agreements for another NC, a DCPC or a GISC to perform functions on its behalf.

4.1.3               According to the particular requirements of a DCPC in its programme role, DCPCs shall support up to 13 14 of the 15 16 technical specifications. DCPCs are not required to support WIS-TechSpec-3 4 or WIS-TechSpec-910.

4.1.4               WIS GISCs shall support all 15 16 technical specifications.

4.1.5               Any DCPC or NC is welcome to implement interfaces beyond the minimum required. Accordingly, the technical specification is mandatory wherever application of the interface is applied.

4.1.6               The WIS2GTS file-naming convention shall be used for files and the associated metadata record whenever necessary. The GTS WIS2 file-naming convention is documented in Annex

the Manual on the Global Telecommunication System (WMO-No. 386), Part II, Attachment II-15.

4.2             WIS-TechSpec-1: Uploading  PUBLICATION of metadata for data and products SERVICES

4.2.1               This specification requires that each metadata record uploaded shall be represented in compliance with the WMO Core Metadata Profile WCMP2 based on OGC API records ISO 19115, as specified in Part V, with a unique identifier.

4.2.2               Uploading shall use methods prescribed by the receiver, which is typically the host of a WIS DAR metadata (WIS discovery metadata) catalogue. NC/DCPC shares a new dataset. They publish a discovery metadata record to their local catalogue describing this dataset.

4.2.3               Discovery, access and retrieval metadata should be provided prior to the files or messages associated with the metadata. NC/DCPC propagate metadata message to the Global Discovery Catalogue via the Global Cache

4.2.4               For updating the DAR metadata (WIS discovery metadata) catalogue, GISCs should support two kinds of maintenance facilities: a file-upload facility for batch updating (add, replace or delete metadata records treated as separate files) and an online form for changing metadata entries in the DAR metadata (WIS discovery metadata) catalogue (add, change or delete elements in a record, as well as whole records).

4.2.5               GISCs shall maintain the updated DAR metadata (WIS discovery metadata) catalogue as a searchable resource (see WIS-TechSpec-8).

4.2.6               See also sections 3.5.2 (Receive information from the GISC area), 3.6.2 (Collect information from the DCPC area), 3.6.3 (Collect programme-related information) and 3.6.4 (Production support of programme-related information).

4.3             WIS-TechSpec-2: Uploading EXCHANGE of data and products

4.3.1               This specification requires that uploaded data or products shall be represented in the manner prescribed by the relevant programme, including, where appropriate, the Manual on the Global Telecommunication System (WMO-No. 386), Part II, Attachment II-2, and the Manual on Codes (WMO-No. 306), as well as other WMO Manuals and the GTS file-naming convention as noted in 4.1.6.

4.3.2               Data and products should be handled as specified in the Manual on the Global Telecommunication System (WMO-No. 386), Part I, 1.3, Design principles of the GTS, and other WMO Manuals specific to the relevant programme.

4.3.3               See also 3.5.2 (Receive information from the GISC area), 3.6.2 (Collect information from the DCPC area), 3.6.3 (Collect programme-related information) and 3.6.4 (Production support of programme-related information).

4.4             WIS-TechSpec-3: Centralization of globally distributed dataPROVISION OF GLOBAL SERVICES

4.4.1               (General description of all the global services) This specification requires that the Manual on the Global Telecommunication System (WMO-No. 386), Part I, Attachment I-3, is applied, as appropriate, to the centralized copies of information intended for global exchange (described in 3.5.1).

4.4.2               Warnings shall be transmitted end-to-end within WIS within two minutes.

4.4.3               See also 3.5.3 (Exchange information with other GISCs) and 3.5.5 (Maintain a 24-hour cache).

4.5             WIS-TechSpec-4: Maintenance of user identification and role informationOPERATING A GLOBAL BROKER

4.5.1               User identification and role information shall be represented and communicated using methods prescribed by the receiver, which is typically the host of an identification and role-information database.

Note:    The term “user identification” in the given context does not imply that a user is personally identifiable. Administrators of authentication and authorization at WIS centres need to share updated identification and role information as a resource that is available across WIS centres. The sharing of this information by administrators is also necessary to prevent the inappropriate disclosure of any personally identifiable information.

4.5.2               User identification and role information maintenance should satisfy timeliness requirements of the application and host centre.

4.5.3               See also 3.5.5 (Maintain a 24-hour cache) and 3.6.7 (Provide access to information).

4.6             WIS-TechSpec-5: Consolidated view of distributed identification and role informationOPERATING A GLOBAL CACHE

4.6.1               This interface for a consolidated view of distributed identification and role information is not yet required (see also Note in 4.5.1).

4.6.2               WIS centres that do exchange identification and role information should do so using data-encryption technologies.

4.6.3               See also 3.5.5 (Maintain a 24-hour cache) and 3.6.7 (Provide access to information).

4.7             WIS-TechSpec-6: Authentication of a userOPERATING A GLOBAL DISCOVERY CATALOGUE

4.7.1               WIS centres should employ authentication standards, which may include public key infrastructure techniques.

Note:    Commercial, off-the-shelf authentication software based on industry and/or international standards should be preferred.

4.7.2               User authentication should satisfy application-specific and host centre processing constraints, and shall provide a quality of service that meets user requirements.

4.7.3               See also 3.5.5 (Maintain a 24-hour cache) and 3.6.7 (Provide access to information).

4.8             WIS-TechSpec-7: Publishing metadata as a National Center or Data Collection and Production CenterAuthorization of a user role

4.8.1          WIS centres should employ government-endorsed standards for user authorization software, techniques and procedures.

4.8.2               User authorization should satisfy application-specific and host centre processing constraints. User authorization shall also provide a quality of service that meets user requirements.

4.8.3               See also 3.5.5 (Maintain a 24-hour cache) and 3.6.7 (Provide access to information).

4.9             WIS-TechSpec-8: Operating data Exchange as a National Center or Data Collection and Production CenterDAR metadata (WIS discovery metadata) catalogue search and retrieval

4.9.1          This specification requires that each metadata catalogue host shall support the Search and Retrieve via URL (SRU) specification of the ISO 23950 Information Search and Retrieval Protocol. A WIS-compliant SRU server shall support SRU version 1.1, the SRU searchRetrieve operation, the SRU Explain operation, the diagnostic schema for returning errors and the SRU Contextual Query Language (CQL) level 2.

4.9.2               In addition to full text search, a WIS-compliant SRU server shall search at least eight indexes as character strings (abstract, title, author, keywords, format, identifier, type and Coordinate Reference System (CRS)); at least five indexes as ordered dates (creationDate, modificationDate, publicationDate, beginningDate, endingDate); and the index “bounding” as geographic coordinates (decimal degrees and space delimited, in the following order: north, west, south, east).

4.9.3               The search service shall provide a quality of service that meets user requirements.

4.9.4               See also 3.5.6 (Discovery, access and retrieval) and 3.6.8 (Describe information with metadata).

4.10           WIS-TechSpec-9: Monitoring complianceConsolidated view of distributed DAR metadata (WIS discovery metadata) catalogues

4.10.1       GISCs should exchange metadata catalogue updates using version 2 of the Open Archives Initiative–Protocol for Metadata Harvesting (OAI-PMH).

4.10.2             The exchange of metadata catalogue updates should satisfy the requirement for distributed instances of DAR metadata (WIS discovery metadata) not to diverge in content by more than one day. A mechanism for rapid update on an emergency basis should also be provided.

4.10.3             See also 3.5.6 (Discovery, access and retrieval).

4.11           WIS-TechSpec-10: Downloading files via dedicated networks

4.11.1       This specification requires that downloaded data or products shall be represented in the manner prescribed by the relevant programme, including, where appropriate, the Manual on the Global Telecommunication System (WMO-No. 386), Part II, Attachment II-2, as well as other WMO Manuals and the GTS file-naming convention, as noted in 4.1.6.

4.11.2       Data and products should be handled as specified in the Manual on the Global Telecommunication System (WMO-No. 386), Part I, 1.3, Design principles of the GTS, and other WMO Manuals that are specific to the relevant programme.

4.11.3       See also 3.5.4 (Disseminate information to the GISC area) and 3.6.5 (Provide information intended for global exchange).

4.12           WIS-TechSpec-11: Downloading files via non-dedicated networks

4.12.1       This specification requires that downloaded data or products shall be represented and communicated in a manner appropriate to the relevant programme.

4.12.2       Data and products should be handled as specified in the Manual on the Global Telecommunication System (WMO-No. 386), Part I, 1.3, Design principles of the GTS, and other WMO Manuals that are specific to the relevant programme.

4.12.3       See also 3.5.4 (Disseminate information to the GISC area) and 3.6.5 (Provide information intended for global exchange).

4.13           WIS-TechSpec-12: Downloading files via other methods

4.13.1       This specification requires that downloaded data or products shall be represented and communicated in a manner appropriate to the relevant programme.

4.13.2       Data and products should be handled as specified in the Manual on the Global Telecommunication System (WMO-No. 386), Part I, 1.3, Design principles of the GTS, and other WMO manuals, specific to the relevant programme.

4.13.3       See also 3.5.4 (Disseminate information to the GISC area) and 3.6.5 (Provide information intended for global exchange).

4.14           WIS-TechSpec-13: Maintenance of dissemination metadata

4.14.1       This specification requires that the dissemination metadata (including subscription information, such as accounts and delivery particulars) shall be represented and communicated as prescribed by the host of the database containing dissemination metadata.

4.14.2       Requests for changes to dissemination for information that are not part of the routine global exchange may be subject to the notification period for changes specified in GTS. Otherwise, changes to dissemination should apply within one day.

4.14.3       See also 3.5.6 (Discovery, access and retrieval) and 3.6.5 (Provide information intended for global exchange).

4.15           WIS-TechSpec-14: Consolidated view of distributed dissemination metadata catalogues

4.15.1       This interface is not yet required; however, it may be needed as part of a back-up arrangement between Centres.

4.15.2       See also 3.5.6 (Discovery, access and retrieval).

4.16           WIS-TechSpec-15: Reporting of quality of service

4.16.1       This specification requires that reporting of quality of service shall be represented and communicated as prescribed by the host of the centralized reporting database.

4.16.2       Reports should be sent on a schedule determined by the centralized reporting manager, based on the needs of WIS centres.

4.16.3       See also 3.5.7 (Network connectivity of GISC), 3.5.8 (Coordinate telecommunications in the GISC area), 3.5.9 (Recovery arrangements of GISC), 3.5.10 (Performance monitoring of a GISC), 3.6.9 (Recovery arrangements of a DCPC) and 3.6.10 (Performance monitoring of a DCPC).

  • No labels