Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

collection ownership checks must cascade to all subelements of a collection #19

Open
balmas opened this issue Mar 8, 2017 · 0 comments

Comments

@balmas
Copy link
Contributor

balmas commented Mar 8, 2017

A client application creates data items which are named graphs. One graph may reference part of another graph. Each graph is a distinctly identifiable object. The graphs may belong to multiple collections. We would like to be able to enforce update/delete access to these graphs based upon ownership of one or more of the collections to which it belongs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant