To properly have a proper temporal usage control odrl rule, I need to limit the amount of constraints to the exactly one (such that only temporal UC is done).
In the Solid Agent repository, I have experimented with such a rule. However, when multiple constraints are present in the odrl policy, the UC engine will still grant the permission (without checking the others).
With Notation3 built-ins, it is possible to limit the cardinality for certain Basic Graph Patterns.
So, in this repository (similarly to crud-engine) there should be a proper temporal odrl rule engine.
As an example, following N3 rule (+ data) will result in a conclusion, only if there is at least one constraint in the ucon rule:
To properly have a proper temporal usage control odrl rule, I need to limit the amount of constraints to the exactly one (such that only temporal UC is done).
In the Solid Agent repository, I have experimented with such a rule. However, when multiple constraints are present in the odrl policy, the UC engine will still grant the permission (without checking the others).
With Notation3 built-ins, it is possible to limit the cardinality for certain Basic Graph Patterns.
So, in this repository (similarly to crud-engine) there should be a proper temporal odrl rule engine.
As an example, following N3 rule (+ data) will result in a conclusion, only if there is at least one constraint in the ucon rule:
With as a conclusion
Uncommenting
<http://example.org/1705937573496#permission> odrl:constraint <test>.
results in no conclusion.Many thanks to @josd for letting me craft this rule.