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

Resource Locator - proper URL form #80

Open
PeterParslow opened this issue Aug 23, 2022 · 0 comments
Open

Resource Locator - proper URL form #80

PeterParslow opened this issue Aug 23, 2022 · 0 comments
Labels
Elements Issue that primarily affects the GEMINI elements Guidance Issues that primarily affect the general or element guidance, not the "normative" parts

Comments

@PeterParslow
Copy link
Contributor

The Schematron rules, Gemini2-mi19, quite reasonably enforce that the Resource locator gmd:linkage/gmd:URL element contains a properly formed URL (they only allow http, https, and ftp - but in context allowing other IETF URL schemes is probably unwise!).

This IETF requirement is implicitly imported to ISO 19115 ("Domain" in table B.3.2.5, 'linkage' row); ISO 19139 encodes URL with xs:anyURI, which allows the use of URI fragments - so this ISO 19115 constraint can't be captured by the XSD check.

So far, so good.

We even hint at it in the "Domain" of Resource locator, except by stating "Valid URL" we leave the door open to URL fragments (relative URLs, without the scheme at the start).

I think it would be even better if we mention this in the GEMINI text, for example in the "Guidance" and / or Encoding guidance.

@PeterParslow PeterParslow added Guidance Issues that primarily affect the general or element guidance, not the "normative" parts Elements Issue that primarily affects the GEMINI elements labels Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Elements Issue that primarily affects the GEMINI elements Guidance Issues that primarily affect the general or element guidance, not the "normative" parts
Projects
Development

No branches or pull requests

1 participant