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

Namespace URL report #15

Closed
ronaldtse opened this Issue Feb 27, 2019 · 9 comments

Comments

Projects
None yet
5 participants
@ronaldtse
Copy link
Contributor

commented Feb 27, 2019

We've just received this report regarding namespaces. See below.

Dear colleges.

The namespaces urls are giving us error, we use them at the beginning of our metadata. Have you change the urls? Is it something temporal?

xmlns:gco="http://www.isotc211.org/2005/gco"
xmlns:gmd="http://www.isotc211.org/2005/gmd"
xmlns:gmx="http://www.isotc211.org/2005/gmx" ...
Thank you.

Regards. Margarita

The issue is that these are namespace URIs, not actual HTTP URLs. For example, the file for http://www.isotc211.org/2005/gmd is at https://www.isotc211.org/2005/gmd/gmd.xsd.

This also relates to #5 .

Any thoughts? @jetgeo @tedhabermann @PeterParslow

@smrgeoinfo

This comment has been minimized.

Copy link

commented Feb 27, 2019

Yes, that is the answer. Those strings ("http://ww.isotc211.org/2005/gco") are identifiers (http URI's technically). They do not necessarily resolve to a useful representation although it has become common practice to set them up so they do resolve to something. They could equally well be UUID's or URNs. The schemaLocation property binds the identifier to a web location (URL) where the xml schema can be gotten.

@ronaldtse

This comment has been minimized.

Copy link
Contributor Author

commented Feb 27, 2019

Thanks @smrgeoinfo , let me contact Margarita and let her know that this is the official response.

However, while technically this is not supposed to be an issue, but there have already been two questions on this. I think this means that there are implementations that depend on the resolvability of these links (confusing with schemaLocation).

What's your take?

@ronaldtse

This comment has been minimized.

Copy link
Contributor Author

commented Feb 27, 2019

(I'd like to add that this user is from the Generalitat Valenciana, http://www.gva.es/)

@smrgeoinfo

This comment has been minimized.

Copy link

commented Feb 27, 2019

I would assert that an application that depends on resolvability of a namespace URI is not consistent with the xml specifications, and does not need to be supported by 3rd parties (e.g. ISO). I'd be interested to hear if there are other opinions on the subject.

@dr-shorthair

This comment has been minimized.

Copy link

commented Feb 27, 2019

@PeterParslow

This comment has been minimized.

Copy link

commented Feb 27, 2019

It is a sad fact of life that "developers"* will use technologies (such as XML) with very limited understanding, and move on quickly if they don't get quick results :)

I was tempted to say "developers of today" :)

@ronaldtse

This comment has been minimized.

Copy link
Contributor Author

commented Mar 19, 2019

Following up on this issue, can we create an "FAQ" page so people can find answers without asking us?

@jetgeo

This comment has been minimized.

Copy link
Contributor

commented Mar 19, 2019

Agree, a FAQ page is good to have for a number of reasons.

@ronaldtse

This comment has been minimized.

Copy link
Contributor Author

commented Mar 25, 2019

Added FAQ question in 9058117 now.

@ronaldtse ronaldtse closed this Mar 25, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.