Henry Story

It may be that a better name for `:include` would be `:import`. (now updated) Indeed the idea came from [owl:imports](https://www.w3.org/TR/2012/REC-owl2-primer-20121211/#Ontology_Management/). Could one re-use owl:imports for this?

I have drawn up a possible layout of access control rules to illustrate how this would work. 1. We have a root `ldp:BasicContainer` in which there is a root `/.acl`...

One open question is how far one can make this work with the ideas from [Re-using Policies](https://github.com/solid/authorization-panel/issues/184), where an ACR has an ` authorizes ` relation to each of the...

We came up with a rule above that applies to all contents recursively of a container. What else can one do? A rule that applies only to the ACRs of...

In the next month I should have a new proposal for HttpSig in authentication. That should slowly have ripple effects on Authorization. I am still finishing an implementation of the...

I have so much on my plate with priority much higher than UCRs, but I will try to link the folks on EU projects related to LinkedData that have their...

I like the diagram with top level concepts and subconcepts below them. It helps a lot. First it identifies two main interaction types: `Read` and `Write`. I think we have...

It may be worth converting this to a `Discussions`, as I can see it being quite a branching topic, and then gather the consensus that arises there to form them...

> @bblfish consensus was reached on the delete requires write on container was reached in [solid/specification#197](https://github.com/solid/specification/issues/197) I think to change that, we should see if we can derive it from...

We could tag "issues" as discussions, so that when we get round to count what needs to be resolved we don't count those open ended ones. That would give us...