Henry Story

I don't think we are at the point of having to decide on MUST or MAY. We are at the point of wanting a name for the relation, either a...

> do not think it solves the issue being discussed here. could you elaborate @acoburn ?

@acoburn two points: 1) the most requested interaction on ACL should be to read them, not to write to them. For that we need a direct link to the effective...

> have yet to be convinced that this mechanism will ultimately make things easier. Well it will save 2n+1 requests to find them, that I made crystal clear above. There...

> And now you need to traverse the entire tree downwards to find out what the access controls in that resource actually mean. Why? There should be no effective ACL...

Thanks @acoburn for drawing out the example nicely [as you did above](https://github.com/solid/web-access-control-spec/issues/99#issuecomment-946195182). Your first answer > Create a new ACL resource associated with /container/child3/grandchild3b and add that user there. This...

Very helpful. Just a reminder that there is simple easy to understand argument to [remove the Control Mode](https://github.com/solid/web-access-control-spec/issues/94), with more logical/mathematical arguments to support that in [Specification issue #303](https://github.com/solid/specification/issues/303). Also,...

Oh Wow! This is issue "101 Switching Protocols"!

No, this issue is to report on the conensus that emerges.

The wiki was where ideas that were discussed by Dan Connolly and TimBL and others MIT folks on IRC where put together initially. Then things were consolidated on the github...