Henry Story

> So please pinpoint the error in my reasoning above, so that I can see why there would be less different GET+Query requests than different GET`+Template requests. In the `GET`+_Query_...

> then our argument simply comes down to a different definition of “resource”. The question is what is it that is operated upon. In the definition of resource that I...

> just like the resource addressed in a SOAP service is also always the same for each request, regardless of the actual interaction. Except it is very different from SOAP,...

> > When doing a (http://example.org/card, application/sparql+query, DESCRIBE ) request, the resource the user is interested in is "the #me part of card", not "card". This is why I find...

I would like this to be open until the name is decided on. When I came to the solid specification meeting a couple of weeks ago, I mentioned to @timbl...

@acoburn [you gave some reasons in the 2n+1 thread](https://github.com/solid/web-access-control-spec/issues/99#issuecomment-946099801) about why you think that saving 2n+1 requests may be problematic, but [I did not find those reasons convincing](https://github.com/solid/web-access-control-spec/issues/99#issuecomment-946168671). Currently because...

Well there is a default currently and that is to use `http://www.trellisldp.org/ns/trellis#effectiveAcl`. The WAC spec should mention that, since its aim is to describe existing implementations. I am ok to...

> Evidence I'd accept in this case is actual performance measurements of applications. The simple maths and experience writing web applications for 25 years is quite enough for me. Requests...

> And we've verified experimentally that dozens of requests per second are not an issue: Does that study deal with clients needing to do access control? I could not find...

> Does that study deal with clients needing to do access control? >> No, with an even more complex Linked Data case that involves much more than 2n+1 and we...