ODRL Requirement 1.7 - Issues List
"Provide a "NOT" expression."
Last modified: 3st December 2004
- Editor(s): The ODRL Initiative
Back to Requirements Document.
Specification Draft:
-
Issue Summary:
This is the list of issues the ODRL Initiative has considered, when addressing the respective requirement (see above).
IssueID: |
State: |
Comment |
issue01 - How to provide a "NOT" expression? |
in discussion |
- |
issue02 - What risk do we face with a "NOT" expression?
|
in discussion |
- |
Please send additional comments to the odrlV2 discussion list at any time.
Issue Details:
- issue01 - How to provide a "NOT" expression?
Please see new "Prohibition" element in the draft data model of the contribution made to the discussion list.
This element can be used just as the Permission element. With a "Prohibition" element everything is allowed except the Actions that are stated.
- issue01 - What risks do we face with a "NOT" expression?
Rightsholders may forget some usages they want to prohibit. With a "Prohibition" element everything is allowed except the stated permissions and thus, rightsholders might grant access rights that s/he did not mean to.