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

Wrong DBPedia IRI in owl:sameAs links (and others) #1

Open
pchampin opened this issue Feb 24, 2017 · 1 comment
Open

Wrong DBPedia IRI in owl:sameAs links (and others) #1

pchampin opened this issue Feb 24, 2017 · 1 comment

Comments

@pchampin
Copy link

All the links to DBPedia that I have seen are wrong.

Take for example:
https://github.com/chronos-pramantha/RDFvocab/blob/master/ld%2Bjson/SolarSystem.json#L35

It points to http://live.dbpedia.org/data/Sun.ntriples, which is not an IRI denoting the Sun; instead, it is an IRI denoting the ntriple files describing the Sun. The correct IRI for the Sun itself is http://live.dbpedia.org/resource/Sun (which is the subject of most triples in the aforementioned ntriple files, by the way).

This is an easy mistake, all the more that DBpedia will redirect any request to correct IRI for the Sun itself. You can think of it as meaning "I can not serve you the resource you requested (i.e. the Sun itself!) but go and check that other resource instead (i.e. a description of the Sun)". This problem is known as httpRange-14 and is very nicely explained by http://www.jenitennison.com/2012/05/11/using-punning-to-answer-httprange-14.html.

@Mec-iS
Copy link
Contributor

Mec-iS commented Feb 24, 2017

Thanks @pchampin I have read the mailing list of this decade-long issue and it is for sure a seminal problem very difficult to be addressed.
For sure we cannot pretend to wire the entire Sun to the end-user... lol

The problem in the vocabulary came from my lack of expertise with RDF and the fact that at the time my prototype had only support for triples, so it was basically the only format I could process; so explained the bias and the wrong dereferencing.

I will fix it as soon as I can.

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