Fullscreen
Loading...
 

This is the static archive copy of the old wiswiki, decommissioned on June 1 2020

Print

ipet-mdi-wmocp

Working page for WMO core profile


Wiki to summarize the state of the current discussion sourrounding the WMO core pfofile

Elements that need standardization

  • fileIdentifier (uncontroversial)
  • Data Policy (open)
  • GTS priority (open)

On the Data Policy:

  • DWD: gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString
  • JMA: gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString
  • MF: gmd:MD_LegalConstraints/gmd:useLimitations/gco:CharacterString
(argues that INSPIRE requires two consecutive gmd:resourceConstraints, the first one specifying "conditions applying to access and use", and including at least the gmd:useLimitation element. Not clear if these can be the same as the WIS encoding, given we settle for useLimitation)
  • CMA: ?? (evidence from their MD suggests gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString)
  • Chair: gmd:MD_Constraints/gmd:useLimitation/gco:CharacterString

What is not clear is where everybody stands regarding the need for having a "ressourceContraints/MD_LegalConstraints/useConstraints|accessConstraints/MD_restrictionCode@codelistValue="otherRestrictions".

On the GTS priority:

  • DWD: gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString
  • JMA: ??
  • MF: gmd:MD_LegalConstraints/gmd:useLimitations/gco:CharacterString
  • CMA: ?? (evidence from their MD suggests gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString)
  • Chair: gmd:MD_Constraints/gmd:useLimitation/gco:CharacterString

On the issue when a record can be considered unrestricted:

Everybody seems to agree that data can be unrestricted if there is no gmd:resourceConstraints/*/gmd:otherConstraints (what * means needs agreement), or a Data Policy element having a non WMO codelist value.



Page last modified on Monday 25 of July, 2011 12:41:36 CEST