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

Accept RDFsource and NonRDFSource in Link header #65

Open
csarven opened this issue Jan 5, 2016 · 0 comments
Open

Accept RDFsource and NonRDFSource in Link header #65

csarven opened this issue Jan 5, 2016 · 0 comments

Comments

@csarven
Copy link
Member

csarven commented Jan 5, 2016

Making POST/PUT requests with:
Link: <http://www.w3.org/ns/ldp#RDFSource>; rel="type" and
Link: <http://www.w3.org/ns/ldp#NonRDFSource>; rel="type"
should be honoured. The server defaults it to its superclass ldp:Resource - this is fine if the type is not recognized, wanted, or simply having it there by default any way, as long as the other conditions are met (IMO, that's a good thing). However, not applying the specific class makes it more difficult to distinguish between ldp:RDFSource and ldp:NonRDFSource resources - the client will have have to look at the Content-Type as a fallback.

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