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.

Sign up for GitHub

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

Jump to bottom

(dcat) Support the content negotiation for ld+json #1215

Closed
riccardoAlbertoni opened this issue Jan 31, 2020 · 2 comments
Closed

(dcat) Support the content negotiation for ld+json #1215

riccardoAlbertoni opened this issue Jan 31, 2020 · 2 comments
Assignees
@plehegar
Labels
dcat
Projects
DCAT revision
Milestone
DCAT2 ratification

Comments

@riccardoAlbertoni
Copy link
Contributor

Testing the content negotiations with the command lines:
curl -H "Accept: text/html" https://www.w3.org/ns/dcat
curl -H "Accept: text/turtle" https://www.w3.org/ns/dcat
curl -H "Accept: application/rdf+xml" https://www.w3.org/ns/dcat
curl -H "Accept:application/ld+json" https://www.w3.org/ns/dcat

It works for text/html text/turtle and application/rdf+xml, but it seems to have problems with ld+json for which the server returns 

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><html><head><title>406 Not Acceptable</title></head><body><h1>Not Acceptable</h1><p>An appropriate representation of the requested resource could not be found on this server.</p>Available variants:<ul><li><a href="dcat.html">dcat.html</a> , type text/html</li><li><a href="dcat.rdf">dcat.rdf</a> , type application/rdf+xml</li><li><a href="dcat.ttl">dcat.ttl</a> , type text/turtle</li></ul></body></html> 

I guess in the future, we would like to deploy the negotiation also for jd+json adding the jd+json serialization in the returned list of the appropriate representations that can be requested.
@riccardoAlbertoni riccardoAlbertoni added dcat future-work issue deferred to the next standardization round labels Jan 31, 2020
@riccardoAlbertoni riccardoAlbertoni added this to the DCAT2 ratification milestone Jan 31, 2020
@riccardoAlbertoni riccardoAlbertoni added this to To do in DCAT revision via automation Jan 31, 2020
@plehegar
Copy link
Member

plehegar commented Feb 3, 2020

Fixed.I did publish a dcat.jsonld but forgot to update the variant file.

curl -H "Accept:application/ld+json" https://www.w3.org/ns/dcat

now works.

@plehegar plehegar self-assigned this Feb 3, 2020
@riccardoAlbertoni
Copy link
Contributor Author

Great! It works I am going to close this issue.

DCAT revision automation moved this from To do to Done Feb 3, 2020
@riccardoAlbertoni riccardoAlbertoni mentioned this issue Feb 4, 2020
Closed
@andrea-perego andrea-perego removed the future-work issue deferred to the next standardization round label Mar 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@plehegar plehegar

Labels
dcat
Projects
DCAT revision
  
Done
Milestone
DCAT2 ratification
Development

No branches or pull requests
3 participants
@plehegar @riccardoAlbertoni @andrea-perego