Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

access and usage constraints #169

Open
pvgenuchten opened this issue Jun 12, 2022 · 0 comments
Open

access and usage constraints #169

pvgenuchten opened this issue Jun 12, 2022 · 0 comments

Comments

@pvgenuchten
Copy link
Contributor

pvgenuchten commented Jun 12, 2022

in the sample i noticed this section on constraints:

accessconstraints: otherRestrictions

This seems inspired by how things are done in ISO19115, unfortunately ISO also is not quite optimal.

More important then access constraints is under which conditions/license the work can be (re)used (CC0, CC-BY, ...) (legal-usage-constaints?).

otherRestrictions is not a proper value by itself, in iso it is usually combined with a second statement to indicate what the other restrictions are.

<gmd:resourceConstraints>
        <gmd:MD_LegalConstraints>
          <gmd:accessConstraints>
            <gmd:MD_RestrictionCode codeListValue="otherRestrictions"/>
          </gmd:accessConstraints>
          <gmd:otherConstraints>
            <gmx:Anchor xlink:href="http://creativecommons.org/publicdomain/mark/1.0/deed.nl">No limitation</gmx:Anchor>
          </gmd:otherConstraints>
        </gmd:MD_LegalConstraints>
      </gmd:resourceConstraints>

If accessConstraints are enforced, it is interesting to state the reason why public access is limited; INSPIRE suggested this codelist with relevant argumentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant