2014-01-29

New mandatory regulations of WCMP 1.3 compared to version 1.2

The WMO Core Metadata Profile (WCMP) version 1.3 has more mandatory requirements compared to the previous version 1.2.  The Manual on WIS (update 2013, see my previous post for text) has following mention on this matter:

Note: metadata created using profile version 1.2 is compatible with that created under version 1.3 other than that the records may have been completed inconsistently and therefore may fail the version 1.3 conformance checking rules.

So it is natural to ask "What are the checking rules newly introduced?"  Please check following list.


  • 6.1.2 Each WIS Discovery Metadata record shall validate without error against the rule-based constraints listed in ISO/TS 19139:2007 Annex A (Table A.1). [These constraints cannot be tested by XSD (W3C XML Schema), so it is highly likely to fail to meet this requirement even if your records pass XSD validation]
  • 6.2.1 Each WIS Discovery Metadata record shall name explicitly all namespaces used within the record; use of default namespaces is prohibited.  [the latter part is a kind of difficult to detect, as the XPath language cannot find where the namespace declaration is present.]
  • 6.3.1 Each WIS Discovery Metadata record shall declare the following XML namespace for GML: http://www.opengis.net/gml/3.2. [WCMP1.2 preferred this namespace, but it was not in so strong language]
  • Intended scope of distribution
    • [§9.1 ¶1] The scope of distribution for data within WIS shall be expressed using the following controlled vocabulary: "GlobalExchange", “RegionalExchange” and “OriginatingCentre” (if the scope of distribution is documented).
    • Requirement 9.1.1: A WIS Discovery Metadata record describing data for global exchange via the WIS shall indicate the scope of distribution using the keyword “GlobalExchange” of type “dataCenterdataCentre” from thesaurus WMO_DistributionScopeCode.
  • Data policy
    • Requirement 9.3.1: A WIS Discovery Metadata record describing data for global exchange via the WIS shall indicate the WMO Data License as Legal Constraint (type: “otherConstraints”) using one and only one term from the WMO_DataLicenseCode code list.
    • [§9.3 ¶5] The presence of more than one WMO Data Policy statement in a single metadata record yields an ambiguous state; a WIS Discovery Metadata record describing data for global exchange shall declare only a single WMO Data Policy.
  • Requirement 9.3.2: A WIS Discovery Metadata record describing data for global exchange via the WIS shall indicate the GTS Priority as Legal Constraint (type: “otherConstraints”) using one and only one term from the WMO_GTSProductCategoryCode code list.
  • [§8.1 ¶9] WMO Core Metadata Profile mandates dateStamp in format YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS. [WCMP 1.2 has similar words, but it didn't say "shall"].

For entire test set, my working draft of the Schematron rule set (pretty-printed by a stylesheet on PC browser) is available here.

2 comments :

  1. Kate Roberts20/02/2014, 09:03

    Can the Data Policies for WMCP then be summarised as:

    For metadata to be included in the WIS,
    (a) it must be in the WMOProfile (v1.2 or 1.3).

    (b) it must include a keyword using WMO_DistributionScopeCode (with keywordTypeCode of 'dataCentre'); and

    (c) where the WMO_DistributionScopeCode used is "GlobalExchange', a WMO_DataLicenseCode and WMO_GTSProductCategoryCode must each also be provided, using ResourceConstraints/OtherConstraints

    ReplyDelete
    Replies
    1. Kate,

      The set of metadata records accepted on WIS should be superset of GlobalExchange. Otherwise the other codes will not make sense.

      And I don't want to exclude (automatically reject) MD records (which is precious contribution) simply because of not following WCMP. In 2010 I've argued so and IPET-MDI-I agreed (see Recommendation 19 http://www.wmo.int/pages/prog/www/WDM/IPET-MDI-I/report/Report_IPETMDI_I_20100503.htm#_Toc260662750). I'm sorry it is not so clear in the current Manual on WIS - this should be addressed again.

      Delete