[go: up one dir, main page]

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

Strange Behavior when the URI begins with a Space #58

Open
Kordishal opened this issue Feb 12, 2018 · 1 comment
Open

Strange Behavior when the URI begins with a Space #58

Kordishal opened this issue Feb 12, 2018 · 1 comment

Comments

@Kordishal
Copy link

In the NASA Name Authority File published at http://metadataregistry.org/vocabulary/show/id/453.html all the URIs begin with a single space. I have contacted the maintainer of this thesaurus on this issue and hope it will be fixed.

The problem with skosify is, that it does not reject the NASA file. Instead it prepends the local file structure to the URI. This is not a behavior I would expect from Skosify. Is this a bug or is there a specific reason this happens?

You can find the vocabulary at NASA Name Authority File

When testing it with your demo server the same thing happens:
http://demo.seco.tkk.fi/skosify/skosify/l6RJf0/

Additionally when processing this file locally all URIs lose one '/' after https -> https:/gsfcir.gsfc.nasa.gov/nasanaf/uri/1639"/.

When running with the debugger it did not add the file path. I am not sure if these are problems in skosify or in rdflib.

The easiest fix would be to simply reject such a vocabulary.

@osma
Copy link
Member
osma commented Feb 12, 2018

Wow, that's ... creative!

My guess is that this is rdflib behavior, but would need to investigate. I think adding the file path to URIs that it thinks are local is normal, but in this case clearly not ideal.

In any case the data needs to be fixed in the source.

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

2 participants