Determine how to dynamically authorize access to reference lists on inherited instances

[justinwb]

From https://gitter.im/solid/data-interoperability-panel?at=6138b630f3449e13a4608150:

I believe that was related to cases where (for example) I grant you access to project 5, with inherited access to project 5’s tasks, and then i add a new task to project 5. you should automatically have access to that new task so i think this was meant to capture the need for the authz system to authorize by relationship

[elf-pavlik]

I think we would need to specify Reference List that externalizes relations first, including it's life cycle. Next step would be how authorization handles it in a way that doesn't surface usage of that externalized bridge resource to the user.

Possibly Shape Trees spec would need to extend definition of referenced shape tree to define that Reference List is being used. IMO that decision should be made at level of defining shape tree.

[justinwb]

Per session on 10/26 - @justinwb will take up an action item to detail this scenario in full, including the resource hierarchy, shape trees, and shape tree references.