Sarven Capadisli

The Protocol uses *RDF document* https://www.w3.org/TR/rdf11-concepts/#dfn-rdf-document (in a *concrete RDF syntax*).

FWIW, HTTP, LDP specs use ABNF. wac-allow, Accept-Put is also in ABNF.

It does make sense and thanks for raising this. Although the first two statements are not or need not be stated as a new requirement (already covered by RFC 3986):...

I find the use cases to include "basic" information about contained resources in the container description compelling. Applications can immediately provide simple functionality by keeping the number of requests/connections minimal....

>best way to do this for whom? Agree from a server's point of view but not particularly attractive from an application's point of view. It is quite a burden for...

@acoburn >This is not what I am suggesting. I know. I said that as the current solution to meet the needs. Querying, pagination or something else is currently not possible...

@namedgraph I presume you can filter based on authorization policy per resource? And the response time for request to /photos/ with different access controls on each contained item is marginally...

@jeff-zucker >Would it make any sense to have the listing of a container's contents follow the permissions on the container rather than the permissions on the contents? No because each...

* https://www.w3.org/TR/ldp-paging/ * https://www.w3.org/TR/activitystreams-core/#paging Created issue for resource paging: https://github.com/solid/specification/issues/230

@gibsonf1 If paging is required, I can't see why more than one mechanism is needed. The number of items to include for a paged resource would either be a client...