From d7e41457fc0a707abe5ab4ed80fb369a5d61b73f Mon Sep 17 00:00:00 2001 From: Anna Milan Date: Wed, 23 Oct 2024 04:02:43 +0200 Subject: [PATCH] edits from LSP in preparation for publication (#232) --- .../recommendations/core/PER_contacts.adoc | 2 +- .../recommendations/core/PER_data_policy.adoc | 4 +- standard/recommendations/core/PER_pids.adoc | 2 +- .../recommendations/core/REC_data_policy.adoc | 2 +- .../core/REC_distribution.adoc | 12 +-- .../recommendations/core/REC_keywords.adoc | 2 +- standard/recommendations/core/REC_links.adoc | 2 +- standard/recommendations/core/REC_status.adoc | 4 +- .../requirements/core/REQ_conformance.adoc | 2 +- standard/requirements/core/REQ_contacts.adoc | 2 +- .../requirements/core/REQ_identifier.adoc | 2 +- standard/requirements/core/REQ_links.adoc | 2 +- standard/requirements/core/REQ_type.adoc | 2 +- .../requirements/core/REQ_validation.adoc | 2 +- .../requirements/requirements_class_core.adoc | 2 +- .../sections/clause_7_normative_text.adoc | 100 +++++++++--------- 16 files changed, 73 insertions(+), 71 deletions(-) diff --git a/standard/recommendations/core/PER_contacts.adoc b/standard/recommendations/core/PER_contacts.adoc index 78ffb41..92a6598 100644 --- a/standard/recommendations/core/PER_contacts.adoc +++ b/standard/recommendations/core/PER_contacts.adoc @@ -2,6 +2,6 @@ [width="90%",cols="2,6a"] |=== ^|*Permission {counter:per-id}* |*/per/core/contacts* -^|A |The `+properties.contacts+` property MAY provide more than one contact via multiple objects or a single contact object with multiple roles. +^|A |The `+properties.contacts+` property MAY provide more than one contact via multiple objects, or a single contact object with multiple roles. |=== //per5 \ No newline at end of file diff --git a/standard/recommendations/core/PER_data_policy.adoc b/standard/recommendations/core/PER_data_policy.adoc index 42d3bd1..e93137b 100644 --- a/standard/recommendations/core/PER_data_policy.adoc +++ b/standard/recommendations/core/PER_data_policy.adoc @@ -3,8 +3,8 @@ |=== ^|*Permission {counter:per-id}* |*/per/core/data_policy* ^|A|For core data (when `+properties.wmo:dataPolicy+` property is `+core+`), attribution licensing MAY be provided as needed. -^|B|For core data (when `+properties.wmo:dataPolicy+` is `+core+`) or recommended data (when `+properties.wmo:dataPolicy+` is `+recommended+`, and the data is compatible with free and unrestricted principles), a license or public domain statement that is compatible with free and unrestricted principles (such as, link:https://creativecommons.org/publicdomain/zero/1.0/[Creative Commons CC0]) MAY be expressed as a link object with the `license` link relation. -^|C|For core data (when `+properties.wmo:dataPolicy+` is `+core+`) or recommended data (when `+properties.wmo:dataPolicy+` is `+recommended+`), a copyright statement MAY be expressed in `+properties.rights+` +^|B|For core data (when `+properties.wmo:dataPolicy+` is `+core+`) or recommended data (when `+properties.wmo:dataPolicy+` is `+recommended+`, and the data is compatible with free and unrestricted principles), a license or public domain statement that is compatible with free and unrestricted principles (such as link:https://creativecommons.org/publicdomain/zero/1.0/[Creative Commons CC0]) MAY be expressed as a link object with the `license` link relation. +^|C|For core data (when `+properties.wmo:dataPolicy+` is `+core+`) or recommended data (when `+properties.wmo:dataPolicy+` is `+recommended+`), a copyright statement MAY be expressed in `+properties.rights+`. ^|D|For core data (when `+properties.wmo:dataPolicy+` is `+core+`) or recommended data (when `+properties.wmo:dataPolicy+` is `+recommended+`), a link object MAY be expressed with `+rel=copyright+`. |=== //per8 \ No newline at end of file diff --git a/standard/recommendations/core/PER_pids.adoc b/standard/recommendations/core/PER_pids.adoc index 385fe48..d4331d0 100644 --- a/standard/recommendations/core/PER_pids.adoc +++ b/standard/recommendations/core/PER_pids.adoc @@ -2,7 +2,7 @@ [width="90%",cols="2,6a"] |=== ^|*Permission {counter:per-id}* |*/per/core/pids* -^|A |A WCMP record MAY provide a persistent identifier to cite research or resource identification using a persistent identifier scheme/framework. +^|A |A WCMP record MAY provide a persistent identifier to cite research or for resource identification, using a persistent identifier scheme/framework. ^|B |A WCMP record MAY provide a persistent identifier as a link object with `+rel=cite-as+` if there is an online citation or reference. |=== //per7 \ No newline at end of file diff --git a/standard/recommendations/core/REC_data_policy.adoc b/standard/recommendations/core/REC_data_policy.adoc index c5a9a59..a9b4c15 100644 --- a/standard/recommendations/core/REC_data_policy.adoc +++ b/standard/recommendations/core/REC_data_policy.adoc @@ -6,7 +6,7 @@ ^|B|To express any conditions on use of a given dataset, the `+properties.rights+` property SHOULD be used. ^|C|For core data or recommended data compatible with free and unrestricted principles, `+properties.rights+` SHOULD be declared with exactly the following statement: - Users are granted free and unrestricted access to this data, without charge and with no conditions on use. Users are requested to attribute the producer of this data. WMO Unified Data Policy (Resolution 1 (Cg-Ext 2021)) + Users are granted free and unrestricted access to this data, without charge and with no conditions on use. Users are requested to attribute the producer of this data. WMO Unified Data Policy (Resolution 1 (Cg-Ext 2021)). ^|D|For core or recommended data not in the public domain, a copyright statement SHOULD be expressed as either a `+properties.rights+` statement or a link object with `+rel=copyright+`. |=== //rec12 \ No newline at end of file diff --git a/standard/recommendations/core/REC_distribution.adoc b/standard/recommendations/core/REC_distribution.adoc index 66061fa..edaa43e 100644 --- a/standard/recommendations/core/REC_distribution.adoc +++ b/standard/recommendations/core/REC_distribution.adoc @@ -5,11 +5,11 @@ ^|A |A WCMP record SHOULD describe additional distribution information with the `+links.distribution+` property to qualify a given service link. This information SHOULD be used to build the discovery information and allow the user to find and choose the appropriate service for accessing the data. ^|B |The `+links.distribution.availableFormats+` property SHOULD describe the different formats that can be retrieved using the service link. ^|C |The `+links.distribution.availableFormats.name+` property SHOULD describe the available format short name. -^|D |The `+links.distribution.availableFormats.description+` SHOULD describe the associated format. -^|E |The `+links.distribution.availableFormats.typicalFilename+` SHOULD describe the filenames that are available from the service link. -^|F |The `+links.distribution.availableFormats.typicalFilesize+` SHOULD describe the typical filesize available from the service link. -^|G |The `+links.distribution.availableFormats.numberOfFiles+` SHOULD describe the typical number of files received during a given period (day, month, ...) when using the service link. It SHOULD follow the pattern X per day, X per month. -^|H |The `+links.distribution.availableFormats.documentation+` SHOULD be a `+link+` for accessing the documentation associated with the format. -^|I |The `+links.distribution.availableFormats.samples+` SHOULD be an array of direct links to representative samples of the data. +^|D |The `+links.distribution.availableFormats.description+` property SHOULD describe the associated format. +^|E |The `+links.distribution.availableFormats.typicalFilename+` property SHOULD describe the filenames that are available from the service link. +^|F |The `+links.distribution.availableFormats.typicalFilesize+` property SHOULD describe the typical file size available from the service link. +^|G |The `+links.distribution.availableFormats.numberOfFiles+` property SHOULD describe the typical number of files received during a given period (day, month, ...) when using the service link. It SHOULD follow the pattern X per day, X per month. +^|H |The `+links.distribution.availableFormats.documentation+` property SHOULD be a `+link+` for accessing the documentation associated with the format. +^|I |The `+links.distribution.availableFormats.samples+` property SHOULD be an array of direct links to representative samples of the data. |=== //rec14 \ No newline at end of file diff --git a/standard/recommendations/core/REC_keywords.adoc b/standard/recommendations/core/REC_keywords.adoc index 678477f..191a783 100644 --- a/standard/recommendations/core/REC_keywords.adoc +++ b/standard/recommendations/core/REC_keywords.adoc @@ -2,6 +2,6 @@ [width="90%",cols="2,6a"] |=== ^|*Recommendation {counter:rec-id}* |*/rec/core/keywords* -^|A |A WCMP record SHOULD provide a `+properties.keywords+` property, as a list of freeform text or tags that are not based on a controlled vocabulary. +^|A |A WCMP record SHOULD provide a `+properties.keywords+` property, as a list of free text or tags that are not based on a controlled vocabulary. |=== //rec2 \ No newline at end of file diff --git a/standard/recommendations/core/REC_links.adoc b/standard/recommendations/core/REC_links.adoc index 360b445..f456ca9 100644 --- a/standard/recommendations/core/REC_links.adoc +++ b/standard/recommendations/core/REC_links.adoc @@ -2,7 +2,7 @@ [width="90%",cols="2,6a"] |=== ^|*Recommendation {counter:rec-id}* |*/rec/core/links* -^|A |A WCMP record's links SHOULD be provided using secure protocols (such as, HTTPS or MQTTS). +^|A |A WCMP record's links SHOULD be provided using secure protocols (such as HTTPS or MQTTS). ^|B |The `+links+` property SHOULD provide a `+type+` property with a valid media type from IANA or as designated by WMO. |=== //rec13 \ No newline at end of file diff --git a/standard/recommendations/core/REC_status.adoc b/standard/recommendations/core/REC_status.adoc index 39a2833..9e009f1 100644 --- a/standard/recommendations/core/REC_status.adoc +++ b/standard/recommendations/core/REC_status.adoc @@ -4,8 +4,8 @@ ^|*Recommendation {counter:rec-id}* |*/rec/core/status* ^|A |A WCMP record SHOULD provide a `+properties.status+` property to identify the operational status of a given dataset. ^|B |A WCMP record SHOULD provide a `+properties.status.id+` property to identify the concept of the status (see Annex D for possible codelists to use). -^|C |A WCMP record SHOULD provide a `+properties.status.title+` property to provide a human readable title for the concept. -^|D |A WCMP record SHOULD provide a `+properties.status.description+` property to provide a human readable description for the concept. +^|C |A WCMP record SHOULD provide a `+properties.status.title+` property to provide a human-readable title for the concept. +^|D |A WCMP record SHOULD provide a `+properties.status.description+` property to provide a human-readable description for the concept. ^|E |A WCMP record SHOULD provide a `+properties.status.url+` property to provide further description of the concept via the given URI. |=== //rec11 \ No newline at end of file diff --git a/standard/requirements/core/REQ_conformance.adoc b/standard/requirements/core/REQ_conformance.adoc index 0a0fd71..4941615 100644 --- a/standard/requirements/core/REQ_conformance.adoc +++ b/standard/requirements/core/REQ_conformance.adoc @@ -2,7 +2,7 @@ [width="90%",cols="2,6a"] |=== ^|*Requirement {counter:req-id}* |*/req/core/conformance* -^|A |A WCMP record SHALL provide information on conformance via the OARec record `+conformsTo+` property. +^|A |A WCMP record SHALL provide information on conformance via the OGC API – Records (OARec) record `+conformsTo+` property. ^|B |The `+conformsTo+` property SHALL advertise conformance to WCMP. |=== //req3 diff --git a/standard/requirements/core/REQ_contacts.adoc b/standard/requirements/core/REQ_contacts.adoc index 983d593..5d4d219 100644 --- a/standard/requirements/core/REQ_contacts.adoc +++ b/standard/requirements/core/REQ_contacts.adoc @@ -4,6 +4,6 @@ ^|*Requirement {counter:req-id}* |*/req/core/contacts* ^|A |A WCMP record SHALL provide at least one contact via the `+properties.contacts+` property. ^|B |The `+properties.contacts+` SHALL provide an `+organization+` property. -^|C |The `+roles+` property, when specified, SHALL provide a role type from the WCMP role type codelist. +^|C |The `+roles+` property, when specified, SHALL provide a role type from the WCMP role type code list. |=== //req11 \ No newline at end of file diff --git a/standard/requirements/core/REQ_identifier.adoc b/standard/requirements/core/REQ_identifier.adoc index 2b79803..24bf5f5 100644 --- a/standard/requirements/core/REQ_identifier.adoc +++ b/standard/requirements/core/REQ_identifier.adoc @@ -4,7 +4,7 @@ ^|*Requirement {counter:req-id}* |*/req/core/identifier* ^|A |A WCMP record SHALL provide an identifier via the `+id+` property. ^|B |The `+id+` property SHALL have the following notation: `+urn:wmo:md:{centre_id}:{local_identifier}+`. -^|C |The ``centre_id`` SHALL be based on the associated vocabulary specified in Appendix D: WIS2 Topic Hierarchy. +^|C |The ``centre_id`` SHALL be based on the associated vocabulary specified in Appendix D. WIS2 Topic Hierarchy. ^|D |The `+id+` property SHALL include a local identifier as defined by the data publisher. The local identifier SHALL NOT have spaces or accented characters. |=== //req2 diff --git a/standard/requirements/core/REQ_links.adoc b/standard/requirements/core/REQ_links.adoc index 8e505e6..5e3d58a 100644 --- a/standard/requirements/core/REQ_links.adoc +++ b/standard/requirements/core/REQ_links.adoc @@ -5,7 +5,7 @@ ^|A |A WCMP record SHALL provide a `+links+` property. ^|B |The `+links+` property SHALL contain at least one link to the data access service allowing users to download the data. ^|C |The `+links+` property SHALL contain a Web Accessible Folder (WAF) or an API link for non-real-time data (such as climate records or hydrometric data archives). -^|D |The `+links+` property SHALL contain access control information for data, products, and services that require authentication or authorization. +^|D |The `+links+` property SHALL contain access control information for data, products and services that require authentication or authorization. ^|E |For representing MQTT links, the URI scheme SHALL be `+mqtt+` (default port 1883) or `+mqtts+` (default port 8883) for secure transport layer security (TLS) encrypted connections. ^|F |The `+links+` property SHALL provide the `channel` property of the MQTT topic for real-time data under which the data publication notifications will be accessible from the WIS2 Global Broker, following the WIS2 Topic Hierarchy. ^|G |The `+links+` property SHALL include a valid link:https://www.iana.org/assignments/link-relations/link-relations.xml[IANA] link relation or a link:https://codes.wmo.int/wis/link-type[WIS link type] code. diff --git a/standard/requirements/core/REQ_type.adoc b/standard/requirements/core/REQ_type.adoc index 6ac15eb..cc4f90c 100644 --- a/standard/requirements/core/REQ_type.adoc +++ b/standard/requirements/core/REQ_type.adoc @@ -3,6 +3,6 @@ |=== ^|*Requirement {counter:req-id}* |*/req/core/type* ^|A |A WCMP record SHALL provide a `+properties.type+` property. -^|B |The `+properties.type+` property SHALL be a valid code from the link:https://codes.wmo.int/wis/resource-type[WIS resource type] codelist. +^|B |The `+properties.type+` property SHALL be a valid code from the link:https://codes.wmo.int/wis/resource-type[WIS resource type] code list. |=== //req4 \ No newline at end of file diff --git a/standard/requirements/core/REQ_validation.adoc b/standard/requirements/core/REQ_validation.adoc index 6a48b45..4549417 100644 --- a/standard/requirements/core/REQ_validation.adoc +++ b/standard/requirements/core/REQ_validation.adoc @@ -3,7 +3,7 @@ |=== ^|*Requirement {counter:req-id}* |*/req/core/validation* ^|A |Each WCMP record SHALL validate without error against the WCMP schema. -^|B |Each WCMP record SHALL provide `+id+`, `+type+`, `+geometry+` and `+properties+` properties for GeoJSON compliance. +^|B |Each WCMP record SHALL provide id (see <<_1_4_identifier>>), type (see <<_1_6_properties_type>>), geometry (see <<_1_11_1_geospatial_extent>>) and properties (see, for example, <<_1_7_properties_title>>) for GeoJSON compliance. ^|C |The `+type+` property SHALL be set to a fixed value of `+Feature+` for GeoJSON compliance. |=== //req1 diff --git a/standard/requirements/requirements_class_core.adoc b/standard/requirements/requirements_class_core.adoc index 44d281c..a121521 100644 --- a/standard/requirements/requirements_class_core.adoc +++ b/standard/requirements/requirements_class_core.adoc @@ -7,5 +7,5 @@ |Dependency |link:https://json-schema.org[JSON Schema] (2022) |Dependency |The GeoJSON Format link:https://datatracker.ietf.org/doc/html/rfc7946[(IETF: RFC-7946 (2016))] |Dependency |OGC API - Features - Part 1: Core corrigendum link:https://docs.opengeospatial.org/is/17-069r4/17-069r4.html[(OGC: OGC 17-069r)] -|Pre-conditions |The record conforms to OGC API - Records - Core: Part 1: Requirements Class: Record Core +|Preconditions |The record conforms to the Requirements Class “Record Core” of link:https://docs.ogc.org/DRAFTS/20-004.html[OGC API - Records - Part 1: Core] |=== \ No newline at end of file diff --git a/standard/sections/clause_7_normative_text.adoc b/standard/sections/clause_7_normative_text.adoc index 13415b3..31e9498 100644 --- a/standard/sections/clause_7_normative_text.adoc +++ b/standard/sections/clause_7_normative_text.adoc @@ -1,7 +1,7 @@ == WMO Core Metadata Profile (Version 2) Note: This section of working draft document is the same as Appendix F in the https://library.wmo.int/idurl/4/68731[_Manual on the WMO Information System_] (WMO-No. 1060), Volume II. -WMO Core Metadata Profile (WCMP) is an extension of the OGC API – Features standard and shall be encoded in GeoJSON. The normative provisions in this standard are denoted by the base URI (``http://wis.wmo.int/spec/wcmp/2``) and requirements are denoted by partial URIs relative to this base. Property names, values and examples are represented with ``shaded text`` in this document. +WMO Core Metadata Profile (WCMP) is an extension of the OGC API – Features standard and shall be encoded in GeoJSON. The normative provisions in WCMP (version 2) are denoted by the base URI (``http://wis.wmo.int/spec/wcmp/2``) and requirements are denoted by partial URIs relative to this base. Property names, values and examples are represented with ``shaded text`` in this document. :sectnums!: === 1. Requirements Class "Core" @@ -26,7 +26,7 @@ The table below provides an overview of the set of properties that may be includ |``conformsTo`` |**Required** -|The version of WCMP associated that the record conforms to (see <<_1_5_conformance>>) +|The version of WCMP associated to which the record conforms (see <<_1_5_conformance>>) |``properties.type`` |**Required** @@ -90,11 +90,11 @@ The table below provides an overview of the set of properties that may be includ |``properties.wmo:dataPolicy`` |**Conditional** -|Classification code of ``core`` or ``recommended`` based on the WMO Data Policy (Resolution 1 (Cg-Ext(2021)))footnote:[Resolution 1 (Cg-Ext(2021)) – WMO Unified Policy for the International Exchange of Earth System Data (World Meteorological Congress: Abridged Final Report of the Extraordinary Session (WMO-No. 1281))]. **Required** for datasets (see <<_1_18_properties_wmo_data_policy>>) +|Classification code of ``core`` or ``recommended``, based on the WMO Unified Data Policy (Resolution 1 (Cg-Ext(2021)))footnote:[Resolution 1 (Cg-Ext(2021)) – WMO Unified Policy for the International Exchange of Earth System Data (World Meteorological Congress: Abridged Final Report of the Extraordinary Session (WMO-No. 1281))]. **Required** for datasets (see <<_1_18_properties_wmo_data_policy>>) |``properties.rights`` |Optional -|A statement that concerns all rights not addressed by the license such as a copyright statement +|A statement that concerns all rights not addressed by the license, such as a copyright statement (see <<_1_18_properties_wmo_data_policy>>) |``links`` @@ -104,7 +104,7 @@ The table below provides an overview of the set of properties that may be includ |``linkTemplates`` |Optional -|Online link templates for dynamic / API access (see <<_1_19_2_templated_links>>) +|Online link templates for dynamic/API access (see <<_1_19_2_templated_links>>) |``properties.*`` |Optional @@ -112,7 +112,7 @@ The table below provides an overview of the set of properties that may be includ |=== -==== 1.2. WCMP record representation +==== 1.2. WMO Core Metadata Profile record representation WCMP record can be represented in various ways internally, in WIS systems and software tools, but its external representation is GeoJSON. @@ -120,14 +120,14 @@ include::../recommendations/core/REC_media_type.adoc[] ==== 1.3 Validation -The WCMP record schema is based on _OGC API - Records - Part 1: Core: Requirements Class: Record Core_ schema and the associated information model. WCMP records compliant with WCMP schema are therefore compliant with the _OGC API - Records_ record schema. +The WCMP record schema is based on the Requirements Class "Record Core" of OGC API – Records – Part 1: Core schema and the associated information model. WCMP records compliant with the WCMP schema are therefore compliant with the OGC API – Records record schema. include::../requirements/core/REQ_validation.adoc[] ==== 1.4 Identifier The `+id+` property is a unique identifier -of the dataset. A record identifier is essential for querying and identifying records within the GDC. +of the dataset. A record identifier is essential for querying and identifying records within the Global Discovery Catalogue (GDC). .Example @@ -141,7 +141,7 @@ include::../recommendations/core/PER_identifier.adoc[] ==== 1.5 Conformance -The `+conformsTo+` property to identifies the version of the WCMP standard that the metadata record conforms to. Conformance identification is valuable for version +The `+conformsTo+` property identifies the version of the WCMP standard to which the metadata record conforms. Conformance identification is valuable for version detection and handling of content. .Example @@ -157,12 +157,12 @@ include::../requirements/core/REQ_conformance.adoc[] ==== 1.6 Properties / Type -The `+type+` property identifies the type of resource that the metadata record describes using values from the resource type codelist. While most metadata records will be set to `dataset`, -WCMP can also describe additional resources, such as services and processes. +The `+type+` property identifies the type of resource that the metadata record describes, using values from the resource type code list in the WMO Codes Registry. While most metadata records will be set to `dataset`, +a WCMP record can also describe additional resources, such as services and processes. A **dataset** is the primary granularity of a WCMP record describing a collection of data granules. -A **service** is an API or web service providing a discovery, visualization, or access mechanism that operates on data. +A **service** is an API or web service providing a discovery, visualization or access mechanism that operates on data. A **process** is a workflow or execution to provide custom functionality to calculate a given output or product. @@ -183,7 +183,7 @@ include::../requirements/core/REQ_type.adoc[] The `+title+` property is a human-readable name of the dataset. -.Example +.Example: [source,json] ---- @@ -217,7 +217,7 @@ include::../requirements/core/REQ_description.adoc[] The `+keywords+` property is a list of keywords, tags or specific phrases associated with the resource, but are not referenced to a particular vocabulary or knowledge organization system. -.Example +.Example: [source,json] ---- @@ -239,7 +239,7 @@ include::../recommendations/core/REC_keywords.adoc[] The `+themes+` property is a list of concepts that are referenced to a vocabulary or knowledge organization system used to classify the resource. -A theme's `+scheme+` property provides a remote reference to a controlled vocabulary, codelist or knowledge organization system. +A theme's `+scheme+` property provides a remote reference to a controlled vocabulary, code list or knowledge organization system. A concept's `+id+` provides an identifier for the given concept, as well as optional `+title+`, `+description+` and `+url+` properties to further describe the concept as desired. @@ -308,7 +308,7 @@ A WCMP metadata record can have one or more themes. ... } ---- -.Example: Themes object with of the earth-system-discipline from the WMO Topic Hierarchy +.Example: Themes object with the `+earth-system-discipline+` from the WMO Topic Hierarchy [source,json] ---- @@ -340,7 +340,7 @@ include::../recommendations/core/PER_themes.adoc[] The `+geometry+` property is the general bounding spatial extent of the dataset in the geographic coordinate system. Geospatial bounding extents provide a useful indicator of the location of the dataset to facilitate search and map displays in the GDC. -.Examples +.Examples: [source,json] ---- @@ -381,17 +381,17 @@ The `+additionalExtents.spatial.bbox+` property provides the ability to list one to many minimum bounding geometries for a given dataset, where: * The minimum longitude is the westernmost coordinate of the limit of the dataset extent, expressed in longitude decimal degrees as a -signed number between -180 and 180, less than or equal to the maximum longitude. +signed number between -180 and 180, less than or equal to the maximum longitude; * The minimum latitude is the southernmost coordinate of the limit of the dataset extent, expressed in latitude decimal degrees as a -signed number between -90 and 90, less than or equal to the maximum latitude. +signed number between -90 and 90, less than or equal to the maximum latitude; * The maximum longitude is the easternmost coordinate of the limit of the dataset extent, expressed in longitude decimal degrees as a -signed number between -180 and 180, greater than or equal to the minimum longitude. +signed number between -180 and 180, greater than or equal to the minimum longitude; * The maximum latitude is the northernmost coordinate of the limit of the dataset extent, expressed in latitude decimal degrees as a signed number between -90 and 90, greater than or equal to the minimum latitude. This property also facilitates catalogue searches with geospatial predicate (such as, within extent). -.Example +.Example: [source,json] ---- @@ -411,11 +411,11 @@ include::../recommendations/core/PER_extent_geospatial.adoc[] The `+time+` property describes the general bounding extent of the dataset and the temporal resolution. -Temporal extents provide a useful indicator of the date and time period of the dataset and facilitates temporal searching in the GDC. +Temporal extents provide a useful indicator of the date and time period of the dataset and facilitate temporal searching in the GDC. -In addition, the temporal resolution provides a useful indicator of the data update frequency (for example, for real-time datasets). If only times are given for the interval, it is implicitly assumed that those are recurring every day. In cases where no time indication can be derived, it is applicable to state the value of `+null+`. +In addition, the temporal resolution provides a useful indicator of the data update frequency (for example, for real-time datasets). If only times are given for the interval, it is implicitly assumed that those are recurring every day. A null value can be used if a time indication cannot be derived. -.Examples +.Examples: [source,json] ---- @@ -459,8 +459,8 @@ In addition, the temporal resolution provides a useful indicator of the data upd "time": null ---- -To ensure clarity, an additional human-readable explanation is given in the `+properties.description+`. -Further time-related characteristics (for example, frequency of modifications, available data, etc.) should be added in `+properties.themes+`. +To ensure clarity, an additional human-readable explanation is given in the `+properties.description+` property. +Further time-related characteristics (for example, frequency of modifications, available data and so forth) should be added in `+properties.themes+`. Some cases might be more complex due to the product's characteristics. If necessary, further granularity can be indicated by the `+additionalExtents.temporal+` property (see <<_1_11_4_additional_temporal_extents>>). @@ -515,9 +515,9 @@ include::../recommendations/core/PER_extent_temporal_service.adoc[] ===== 1.11.4 Additional temporal extents The `+additionalExtents.temporal+` property is for describing other temporal extents associated with the dataset. For example, it may be useful to represent multiple time instances or to identify other temporal reference systems. -Temporal extents can be fully bound or open in either direction. An `+additionalExtents.temporal.resolution+` property is able express the temporal granularity at which a given dataset's data is measured, generated, or reported. +Temporal extents can be fully bound or open in either direction. An `+additionalExtents.temporal.resolution+` property is able to express the temporal granularity at which a given dataset's data are measured, generated or reported. -.Example +.Example: [source,json] ---- @@ -543,7 +543,7 @@ include::../recommendations/core/PER_extent_temporal.adoc[] ==== 1.12 Properties / Contacts -The `+contacts+` property is the information associated with one or more responsible parties of the resource. +The `+contacts+` property is the information associated with one or more parties responsible for the resource. .Example: Contacts object with all contact details @@ -666,9 +666,9 @@ include::../recommendations/core/PER_pids.adoc[] ==== 1.15 Properties / Record creation date -The `+created+` property is a single date that the WCMP metadata record was created. Note that this date is not the start or end time of a given dataset. See <<_1_11_3_temporal_extent>> for more information on defining dataset temporal extents. +The `+created+` property is a single date, being the date that the WCMP metadata record was created. Note that this date is not the start or end time of a given dataset. See <<_1_11_3_temporal_extent>> for more information on defining dataset temporal extents. -.Example +.Example: [source,json] ---- @@ -685,7 +685,7 @@ include::../requirements/core/REQ_record_creation_date.adoc[] The `+updated+` property is the date that the WCMP metadata record was last updated. Note, that this date is not the start or end time of a given dataset. See <<_1_11_3_temporal_extent>> for more information on defining dataset temporal extents. -.Example +.Example: [source,json] ---- @@ -700,7 +700,9 @@ include::../recommendations/core/REC_record_update_date.adoc[] ==== 1.17 Properties / Status -The `+status+` property identifies the lifecycle of a given dataset. +The `+status+` property identifies the life cycle of a given dataset. + +.Example: [source,json] ---- @@ -717,7 +719,7 @@ include::../recommendations/core/REC_status.adoc[] ==== 1.18 Properties / WMO data policy -The `+wmo:dataPolicy+` property is a codelist that identifies the classification of the dataset exchange as described by the WMO Data Policy (Resolution 1 (Cg-Ext(2021)))footnote:[Resolution 1 (Cg-Ext(2021)) – WMO Unified Policy for the International Exchange of Earth System Data (World Meteorological Congress: Abridged Final Report of the Extraordinary Session (WMO-No. 1281))] for the international exchange of Earth system data. The codelist values are `+core+` or `+recommended+`. The `+wmo:dataPolicy+` property is required if the metadata record describes a dataset. +The `+wmo:dataPolicy+` property is a codelist that identifies the classification of the dataset exchange as described by the WMO Unified Data Policy (Resolution 1 (Cg-Ext(2021)))footnote:[Resolution 1 (Cg-Ext(2021)) – WMO Unified Policy for the International Exchange of Earth System Data (World Meteorological Congress: Abridged Final Report of the Extraordinary Session (WMO-No. 1281))] for the international exchange of Earth system data. The code list values are `+core+` or `+recommended+`. The `+wmo:dataPolicy+` property is required if the metadata record describes a dataset. Licensing and copyright are expressed via the `+links+` property (see <<_1_19_links_and_distribution_information>>), providing access, license and attribution details as required. Conditions on use of the data should be indicated for transparency and clarification. @@ -797,9 +799,9 @@ include::../recommendations/core/PER_data_policy.adoc[] ===== 1.19.1 Overview -The `+links+` property describes URLs and APIs for accessing the dataset or for subscribing to dataset notifications. Links are the primary mechanism for interacting with the data and provide an "actionable" workflow to enhance and improve the user experience with "less clicks" for subscriptions and downloads. +The `+links+` property describes URLs and APIs for accessing the dataset or for subscribing to dataset notifications. Links are the primary mechanism for interacting with the data, and provide an "actionable" workflow to enhance and improve the user experience with "less clicks" for subscriptions and downloads. -The `+links+` property may also describe URLs for related documentation, related data, or visual images of the dataset. +The `+links+` property may also describe URLs for related documentation, related data or visual images of the dataset. The table below provides an overview of the properties of a link object. @@ -809,12 +811,12 @@ The table below provides an overview of the properties of a link object. |``href`` |**Required** -|The link destination or target, or URL. +|The link destination or target, or URL |``rel`` |Optional |The relationship that the link bears in the context of the WCMP record. This is a controlled vocabulary defined - by link:https://www.iana.org/assignments/link-relations/link-relations.xhtml[IANA link relations] or link:https://codes.wmo.int/wis/link-type[WIS link type] extensions. (see table <<_1_19_5_link_relation_selection>>) + by link:https://www.iana.org/assignments/link-relations/link-relations.xhtml[IANA link relations] or link:https://codes.wmo.int/wis/link-type[WIS link type] extensions (see table in <<_1_19_5_link_relation_selection>>). |``type`` |Optional @@ -830,11 +832,11 @@ The table below provides an overview of the properties of a link object. |``channel`` |**Conditional** -|For data made available via MQTT, the topic to which a user may subscribe to for notifications and access +|For data made available via MQTT, the topic to which a user may subscribe for notifications and access |``security`` |Optional -|For access controlled data, a description of the access control mechanism applied (see <<_1_19_4_access_control>>) +|For access-controlled data, a description of the access control mechanism applied (see <<_1_19_4_access_control>>) |``distribution`` |Optional @@ -916,9 +918,9 @@ For recommended data, the ``links`` property may also provide links to services ===== 1.19.2 Templated links -Templated links allow for specifying a pattern of a link in support API interaction (where parameter values are variable). +Templated links allow for specifying a pattern of a link in support of API interaction (where parameter values are variable). -.Example: A templated link object of a WMS service providing API access to images +.Example: A templated link object of a Web Map Service (WMS) providing API access to images [source,json] ---- "linkTemplates": [{ @@ -1059,10 +1061,10 @@ links to data and services. |Online documentation |`about` -|OpenAPI endpoint (such as, JSON or YAML) +|OpenAPI endpoint (such as JSON or YAML) |`service-desc` -|OpenAPI endpoint in HTML (such as, Swagger, ReDoc) +|OpenAPI endpoint in HTML (such as Swagger or ReDoc) |`service-doc` |OGC WMS, WFS, WCS, CSW, WPS Capabilities @@ -1074,10 +1076,10 @@ links to data and services. |A link providing a single data granule |`item` -|A link to numerous stations that the dataset is based on +|A link to numerous stations on which the dataset is based |`stations` -|A link to a single station that the dataset is based on +|A link to a single station on which the dataset is based |`station` |citation @@ -1086,7 +1088,7 @@ links to data and services. |A search portal or web application |`search` -|A zipfile of data, or bulk download +|A zip file of data, or bulk download |`enclosure` |A browse graphic of a dataset @@ -1100,7 +1102,7 @@ links to data and services. ==== 1.20 Additional properties A WCMP record can be extended as required for organizational purposes by adding properties (of any type) in the -record. Additional properties do not break compliance to WCMP. +record. Additional properties do not render a record non-compliant with WCMP. .Example: @@ -1135,4 +1137,4 @@ include::../recommendations/core/PER_additional_properties.adoc[] • http://codes.wmo.int/wis/topic-hierarchy/notification-type ==== 2.2 WMO schemas server -Validation, examples and other resources are published at https://schemas.wmo.int/wcmp. +Validation schemas, examples and other resources are published at https://schemas.wmo.int/wcmp.