Sarven Capadisli
Sarven Capadisli
Aligning representations of document and container resources with REST via single and compound state
There needs to be a guarantee that RDF encoded client-managed statements are available in Turtle and JSON-LD representations. Otherwise, it misses the point on accepting resource states in Turtle or...
Aligning representations of document and container resources with REST via single and compound state
Context: optionally (re "MAY") setting client-managed part of container state. Then the system can only guarantee server-managed information. Having a MUST to include RDF from any accepted representation available back...
Aligning representations of document and container resources with REST via single and compound state
@elf-pavlik Restricting the protocol as such would unfortunately be counter to *existing* publishing practices, updating resources in alternative ways, having any URI for a WebID as well as it being...
Aligning representations of document and container resources with REST via single and compound state
[Keeping this brief because as I see it, there is no new or significant information to respond to. Everything here, related issues, chats, meetings, drinks... over the past ~10 years...
Aligning representations of document and container resources with REST via single and compound state
Matthieu, that's not what I'm saying. Either all clients need to handle RDFa or servers need to make its resource available in Turtle/JSON-LD. We are requiring the server to come...
Aligning representations of document and container resources with REST via single and compound state
Ted, I'm glad to see you back! :) I think we are saying/thinking the same thing.. just to double check: For PATCH + application/sparql-update, only the RDF graph of resource's...
Aligning representations of document and container resources with REST via single and compound state
Ted, you're doing great. Thanks for the feedback. >>I have particular concerns with the idea that "only the RDF graph of resource's state is intended to be updated". Intended by...
/me rubs eyes. This feature is currently unspecified in the Protocol spec. Availability or generation of representations are typically managed by a server, and thus it would be simpler for...
Can we move any new information in this issue to https://github.com/solid/web-access-control-spec/issues/99 and then close this issue? or is the request in this repo to have one that can be used...
There is a related requirement in the Solid Protocol: write requests on representation URLs when different from the resource URL are to 307/308 to the original resource. When there is...