Henry Story

Would it be worth updating the documentation? For the moment it only mentions [web pack 4 support](https://scalacenter.github.io/scalajs-bundler/cookbook.html#how-to-use-webpack-4). I am trying to get going...

If I read it correctly this seems to follow from https://github.com/solid/authorization-panel/issues/73 "Client-Server symmetry" and also from follow your nose principles.

@csarven > I think the expectation in the Solid ecosystem is that content creator decides where to store the resource and the applicable authorization policy (whether they actively set that...

Your point @dmitrizagidulin goes in the same direction as the high confidentiality use case I put forward https://github.com/solid/authorization-panel/pull/96

@dmitrizagidulin wrote > I'd love to see an addition to the Web Access Control spec that denotes "The ACL policies for this resource are fully dependent on the ACL policies...

> I believe and always have, that the resource should link directly to its effective access control resource. It may also link to a resource that could be created to...

@kjetilk > but I'd be OK with adding more, as being explicit about it is often a good practice. Great :-) [1] We just need to come up with a...

@kjetilk here are some more detailed answers to your last two posts: > > **But** - and this is really the crux of the matter - if you only link...

@kjetilk wrote: > Indeed, I think it should be up to the client to choose where in the hierarchy it is most suitable to put access control (subject to control...

## Prior work Thanks @csarven for pointing to [spec #106](https://github.com/solid/specification/issues/106) and prior work. As I see we have quite a number of people who are for a header to point...