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.
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.