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

Sort out content negotiation #11

Open
3 of 4 tasks
matt-wallis opened this issue Nov 15, 2016 · 0 comments
Open
3 of 4 tasks

Sort out content negotiation #11

matt-wallis opened this issue Nov 15, 2016 · 0 comments

Comments

@matt-wallis
Copy link
Contributor

matt-wallis commented Nov 15, 2016

This is a catch-all issue - other more specific ones may be created too.
Reference doc: W3C: Best Practice Recipes for Publishing RDF Vocabularies/Content Negotiation.
We need to choose a recipe: essglobal uses RDF and Single HTML document (using PURLs) with a slash namespace, which means I think we follow recipe 4a.

The Best Practice doc refers to a content negotiation testing service but it suffered a DNS lookup failure when I tried it :-( Needs more investigation.

We need content negotiation for:

  • RDF/XML
  • SKOS
  • HTML
  • Turtle
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

1 participant