- From: Víctor Rodríguez-Doncel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Jun 2017 09:00:07 +0000
- To: public-poe-archives@w3.org
About allowing: `<http://example.com/policy:01> odrl:permission odrl:present ` Pros: - A policy can be described as a resource (policy01) with a set of properties and values. Ideal for lazy implementors, easy storage/processing (a policy as a POJO, stored in a single table in a relational database, or in a couple of columns in a CSV file). - Easy understandability, "less lines in a powerpoint": nobody will be able to say "I dont understand simple ODRL policies". Developers of the world happy. Cons: - An extra burden for rigorous implementors, who will need to implement another branch to evaluate policies (big "if"). - The lack of elegance of specifying two manners to do the same - An additional source of contradictions (but already possible) @simonstey Am I missing anything else? I would like this to hear more opinions, but indeed I am ok for "minimising issues and complications" -- GitHub Notification of comment by vroddon Please view or discuss this issue at https://github.com/w3c/poe/issues/184#issuecomment-310014137 using your GitHub account
Received on Wednesday, 21 June 2017 09:00:14 UTC