search

wmo-im / wcmp

WMO Core Metadata Profile
https://github.com/wmo-im/wcmp
6 stars 6 forks source link

Define KPI K Data Policy Possible combination #27

Closed efucile closed 3 years ago

efucile commented 4 years ago

working on this branch https://github.com/wmo-im/wmcp/blob/KPI-K/KPI/K.adoc

efucile commented 4 years ago

@amilan17 to produce an example of multiple resource constraints

martaguti commented 4 years ago

Updated an initial proposal , containing :

amilan17 commented 4 years ago

Examples of repeatable resourceConstraint elements from the NCEI Metadata Template. 


<gmd:resourceConstraints xlink:title="Distribution Liability">
    <gmd:MD_LegalConstraints>
        <gmd:accessConstraints>
            <gmd:MD_RestrictionCode codeList="https://data.noaa.gov/resources/iso19139/schema/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions"> otherRestrictions </gmd:MD_RestrictionCode>
        </gmd:accessConstraints>
        <gmd:otherConstraints>
            <gco:CharacterString> Distribution liability: NOAA and NCEI make no warranty, expressed or implied, regarding these data, nor does the fact of distribution constitute such a warranty. NOAA and NCEI cannot assume liability for any damages caused by any errors or omissions in these data. If appropriate, NCEI can only certify that the data it distributes are an authentic copy of the records that were accepted for inclusion in the NCEI archives. </gco:CharacterString>
        </gmd:otherConstraints>
    </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
<gmd:resourceConstraints xlink:title="Use Liability">
    <gmd:MD_LegalConstraints>
        <gmd:useConstraints>
            <gmd:MD_RestrictionCode codeList="https://data.noaa.gov/resources/iso19139/schema/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions"> otherRestrictions </gmd:MD_RestrictionCode>
        </gmd:useConstraints>
        <gmd:otherConstraints>
            <gco:CharacterString> Use liability: NOAA and NCEI cannot provide any warranty as to the accuracy, reliability, or completeness of furnished data. Users assume responsibility to determine the usability of these data. The user is responsible for the results of any application of this data for other than its intended purpose. </gco:CharacterString>
        </gmd:otherConstraints>
    </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
<gmd:resourceConstraints xlink:title="NCEI Data Citation Statement">
    <gmd:MD_LegalConstraints>
        <gmd:useLimitation>
            <gmd:MD_RestrictionCode codeList="https://data.noaa.gov/resources/iso19139/schema/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
        </gmd:useLimitation>
        <gmd:otherConstraints>
            <gco:CharacterString>Cite as: {{Last, F. M., F. M. Last, and F. M. Last}}. {{YYYY}}. {{Title}}. {{Version}}. [indicate subset used]. NOAA National Centers for Environmental Information. https://doi.org/{{DOI}}. Accessed [date]. </gco:CharacterString>
        </gmd:otherConstraints>
    </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
martaguti commented 4 years ago

Hi @amilan17 , That's an interesting use case of multiple resourceConstraints. Could you express the same idea by putting everything in one block of resourceConstraints?

martaguti commented 4 years ago

In the last TelCo we brought the discussion about whether every record should implement WMO_DatalicenceCode

Below is an example of Year of Polar Prediction (YOPP) dataset under a Creative Commons Attribution License


<gmd:resourceConstraints>
  <gmd:MD_LegalConstraints>
    <gmd:useLimitation>
      <gco:CharacterString>This work is licensed under the Creative Commons Attribution 3.0 License (URL: https://creativecommons.org/licenses/by/3.0/)</gco:CharacterString>
    </gmd:useLimitation>
    <gmd:useConstraints>
      <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="license">license</gmd:MD_RestrictionCode>
    </gmd:useConstraints>
    <gmd:otherConstraints>
      <gmx:Anchor xlink:href="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</gmx:Anchor>
    </gmd:otherConstraints>
  </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>

Should we recommend instead the implementation of WMOOther e.g.


<gmd:resourceConstraints>
  <gmd:MD_LegalConstraints>
    <gmd:useLimitation>
      <gco:CharacterString>This work is licensed under the Creative Commons Attribution 3.0 License </gco:CharacterString>
    </gmd:useLimitation>
    <gmd:accessConstraints>
      <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
    </gmd:accessConstraints>
    <gmd:useConstraints>
      <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
    </gmd:useConstraints>
    <gmd:otherConstraints>
      <gmx:Anchor xlink:href="http://wis.wmo.int/2013/codelists/WMOCodeLists.xml#WMO_DataLicenseCode_WMOOther">WMOOther</gmx:Anchor>
    </gmd:otherConstraints>
    <gmd:otherConstraints>
      <gmx:Anchor xlink:href="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</gmx:Anchor>
    </gmd:otherConstraints>
  </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
amilan17 commented 4 years ago

@martaguti - It is valid ISO to put everything into one one resourceConstraints block and I believe that the same ideas can expressed, because these statements are prefaced with 'Distribution Liability' and 'Use Liability'.

josusky commented 4 years ago

@martaguti you have there a minor typo, a repeated "xlink:href":

<gmx:Anchor xlink:href="xlink:href="http://wis.wmo.int/...

However, the more problematic in my opinion is the use of WMOOther that has a special meaning - it presents some kind of restriction (it covers for example OPMET data). And that restriction, if I am not mistaken, is not compatible with Creative Commons Attribution License. The original definition seems quite OK to me - if the intention was to tell that the data usage shall respect a specific license (in this case a permissive one) that does not match any of traditional WMO/GTS limitations.

martaguti commented 4 years ago

Hi @josusky,

Thanks for spotting the typo, I've fixed it now. The presence of WMOOther for metadata records that are not Essential / Additional or No limitations was discussed in the last TelCo. Or in other words do the records need to have always one of the codes from WMO_DataLicenceCode?

@gaubert or @kateroberts mentioned they would look back on previous discussions.

I found the following report , it is old though 2013 . Decisions 1, 10 and 11 refer to the topic.

TT-ApMD-2-FinalReport.docx

gaubert commented 4 years ago

Hi @martaguti @josusky @amilan17

The conclusion of the report you mentionned Marta are correct from my understand. If you look at decision 10 and 11. WMOOther should be included if you want to make data policies that is not WMO Additional or Essential applicable in the WMO communities. This is what is implemented for instance by EUMETSAT for our DCPC products. Products that are not qualified by WMO Additional or Essential and available via the GISCs.

This is here an example of a metadata record with have:

<gmd:resourceConstraints>
            <gmd:MD_LegalConstraints>
              <gmd:useLimitation>
                <gco:CharacterString>-</gco:CharacterString>
              </gmd:useLimitation>
              <gmd:useLimitation>
                <gco:CharacterString>geossDataCore</gco:CharacterString>
              </gmd:useLimitation>
              <gmd:useLimitation>
                <gco:CharacterString>geossNoMonetaryCharge</gco:CharacterString>
              </gmd:useLimitation>
              <gmd:useLimitation>
                <gco:CharacterString>geossuserRegistration</gco:CharacterString>
              </gmd:useLimitation>
              <gmd:useLimitation>
                <gco:CharacterString>geossAttribution</gco:CharacterString>
              </gmd:useLimitation>
              <gmd:accessConstraints>
                <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="copyright" />
              </gmd:accessConstraints>
              <gmd:useConstraints>
                <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="copyright" />
              </gmd:useConstraints>
            <gmd:otherConstraints>
              <gco:CharacterString>WMOOther</gco:CharacterString>
            </gmd:otherConstraints>
            <gmd:otherConstraints>
              <gco:CharacterString>http://www.eumetsat.int/website/home/Data/DataDelivery/DataRegistration/DataLicensing/index.html</gco:CharacterString>
            </gmd:otherConstraints>
          </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>

GISCDWD

martaguti commented 3 years ago

Hi @wmo-im/tt-wismd,

Please review Data Policy KPI. I have entered a possible score and adapted to the new format. https://github.com/wmo-im/wcmp/blob/KPI-K/KPI/K.adoc

I haven't sent a pull request to master yet as it would be nice to get consensus on scoring.

Talk soon

tomkralidis commented 3 years ago

Thanks @martaguti , this is great work. Agree on needing to discuss scoring (see #71) tomorrow.

tomkralidis commented 3 years ago

Implemented in https://github.com/wmo-im/wcmp/pull/80