Consider ACP matcher for conditional by relationship

[justinwb]

On proposal

ACP

Details

ACP provides extensibility for additional matchers. I suggest considering an additional matcher can evaluate access to a given resource based on the presence of a specified graph relationship, as detailed in Use Cases and Requirements. Solid is both graph and resource-based, and more complex objects may be comprised of multiple resources outside of what can be captured solely by a containment hierarchy. The ability to match by graph relationship would allow the authorization system to perform more robust matches based on the native data model, but care would need to be taken to ensure performance lookups (e.g. only allow direct relationships vs indirect).

Acceptance criteria

What actions are needed to resolve this issue? (checklist)

• Extend an ACP implementation to demonstrate the functionality (e.g. use the documented use case as an example). Prove that it can be implemented feasibly, in a secure and performant way.
• Add to the specification, or a derivative specification for a matcher extension.