-
Notifications
You must be signed in to change notification settings - Fork 22
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
ACL Expiry #10
Comments
i would let the apps clean the acl (so acl can be more transparent and policies would be easy to renew) |
Note that RDF is monotonic, so if a graph is true, deleting statements leaves it true. Having an optional constraint like acl:validTill 2016-06-30 doesn't work like this. Ways to get around it are many -- have a separate class TimedAuthenticaion for example where the validTill is required. This also means old systems will fail safe. |
@timbl Can you explain a bit more, about monotonic? What do you mean about deleting statements? Does that mean our PATCH verb is useless? |
@nicola I agree the cleaning process shouldn't be part of the specs, but I believe the server is more in charge of cleaning. It can happen with every write to the resource or it can rely on server implementation. Poor applications shouldn't cause a lot of dummy triples on the pod. @timbl does this mean in an authorization rule containing In this case, why don't we consider |
@dmitrizagidulin do you think @timbl 's point also applies for |
@ghanemabdo not sure.. I need to understand this subject better; I'll see if I can ask him about it today. @nicola - don't forget that many (most?) apps won't have read/write access to the |
Adding a new triple to an authorization with predicate
acl:validTill
is probably a needed use case. It says an authorization rule is valid till a particular time. The ACL resource should be cleaned removing expired aurthorizations.The text was updated successfully, but these errors were encountered: