TRACKER ISSUE-10: What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied?
satisfiability of constraints
What does it mean for permissions/prohibitions/duties if their constraint(s) are (un)satisfied?
State:
RAISED
Product:
POE - Information Model
Raised by:
Simon Steyskal
Opened on:
2016-11-08
Description:
http://w3c.github.io/poe/model/#constraint states:
"[...] If multiple Constraint entities are linked to the same Permission, Prohibition, or Duty entity, then all of the Constraint entities MUST be satisfied. That is, all the Constraint entities are (boolean) anded. [...]"
Without actually explaining the concept of "satisfying a Constraint entity".
=> How can someone "satisfy a Constraint entity"?
=> What does it mean for permissions/prohibitions/duties if their constraints are unsatisfied?
=> Is a permission having an unsatisfied constraint equivalent to a prohibition? (and vice versa)
=> Should a permission/prohibition having an unsatisfied constraint simply be ignored? If so, is it possible for "ignored" perm/proh to become "active" again?
simon
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3