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

Add payload and representations in RDF #196

Merged
merged 7 commits into from
Oct 11, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions main/resource-access.bs
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,26 @@ Issue:
Pertaining to events and loss of control mitigation:
https://github.com/solid/specification/issues/41#issuecomment-534679278

### Representations ### {#representations}

When a server creates a resource on HTTP `PUT`, `POST` or `PATCH` requests
such that the request's representation data encodes an *RDF document*
[[!RDF11-CONCEPTS]] (as determined by the `Content-Type` header), the server
MUST accept `GET` requests on this resource when the value of the `Accept`
header requests a representation in `text/turtle` or `application/ld+json`
[[!Turtle]] [[!JSON-LD11]].
[[Source](https://github.com/solid/specification/issues/45)]
[[Source](https://github.com/solid/specification/issues/69)]
[[Source](https://github.com/solid/specification/issues/109)]
[[Source](https://github.com/solid/specification/issues/195)]

When a `PUT`, `POST`, `PATCH` or `DELETE` method request targets a
representation URL that is different than the resource URL, the server MUST
respond with a `307` or `308` status code and `Location` header specifying the
preferred URI reference.
[[Source](https://github.com/solid/specification/issues/109)]


## Auxiliary Resources ## {#rm}

### Background and Need ### {#ar-need}
Expand Down