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

Dereferenceable IRIs and content negotiation #13

Open
andrefs opened this issue Mar 11, 2021 · 4 comments
Open

Dereferenceable IRIs and content negotiation #13

andrefs opened this issue Mar 11, 2021 · 4 comments

Comments

@andrefs
Copy link

andrefs commented Mar 11, 2021

Hello,

(Not sure whether this is the best place to raise this issue, but I couldn't find any other contact information on YAGO's homepage.)

When dereferencing YAGO's IRIs I am obtaining an HTML response. I'm trying to obtain an RDF response.

I've tried sending an Accept header or looking for a <link rel="alternate" type="some rdf media type" href="..."> in the HTML but neither approach is working.

Am I missing something or is YAGO incapable of dereferencing IRIs in RDF format?

Thanks

@Tpt
Copy link
Collaborator

Tpt commented Mar 11, 2021

Hi! It's indeed a great place to raise issues about YAGO 4.

Thank you for reporting this problem. Content negotiation should work but it seems it does not indeed.
curl -H "accept: text/turtle" https://yago-knowledge.org/resource/Julius_Caesar returns me HTML and not Turtle.

@mclegrand Have you tweaked the nginx configuration after my departure?

@mclegrand
Copy link

@mclegrand Have you tweaked the nginx configuration after my departure?

No, I did not touch anything, The main event that happened recently was a power outage affecting the server room a few weeks ago but it should just have restarted the server normally

@Tpt
Copy link
Collaborator

Tpt commented Mar 11, 2021

@mclegrand Thank you! Sorry for disturbing you.

I am not sure what cause this problem. YAGO website should be able to properly handle content negotiation using this code. I do not have access to the server anymore so I am not able to have a look at its configuration or logs to debug this problem. Sorry.

@almereyda
Copy link

This seems fixed now, and could be closed:

$ curl -s -H "accept: text/turtle" https://yago-knowledge.org/resource/Julius_Caesar | head -n 12
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sesame: <http://www.openrdf.org/schema/sesame#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix fn: <http://www.w3.org/2005/xpath-functions#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix hint: <http://www.bigdata.com/queryHints#> .
@prefix bd: <http://www.bigdata.com/rdf#> .
@prefix bds: <http://www.bigdata.com/rdf/search#> .

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

4 participants