[poe] EXAMPLE 19 makes no sense

• From: simon via GitHub <sysbot+gh@w3.org>
• Date: Mon, 26 Jun 2017 13:00:56 +0000
• To: public-poe-archives@w3.org
• Message-ID: <issues.opened-238535404-1498482054-sysbot+gh@w3.org>

simonstey has just created a new issue for https://github.com/w3c/poe:

== EXAMPLE 19 makes no sense ==
https://w3c.github.io/poe/model/#constraint-compound: 
> Example Use Case:The Policy below shows a Permission to play the target asset that can either be a maximum of 100 times, or unlimited play until the end of 2017 but not both.

```json
{
    "@context": "http://www.w3.org/ns/odrl.jsonld",
    "@type": "Offer",
    "uid": "http://example.com/policy:88",
    "permission": [{
        "target": "http://example.com/book/1999.mp3",
        "assigner": "http://example.com/org/paisley-park",
        "action": "play",
        "constraint": [{
                "leftOperand": "http://example.com/policy:88/C1",
                "operator": "xor",
                "rightOperand": "http://example.com/policy:88/C2"
            }],
    }],
   "constraint": [{
       "uid": "http://example.com/policy:88/C1",
       "leftOperand": "count",
       "operator": "lteq",
       "rightOperand": "100"
   },
   {
       "uid": "http://example.com/policy:88/C2",
       "leftOperand": "dateTime",
       "operator": "lteq",
       "rightOperand": "2017-12-31"
   }]
}  
```
what's the intended semantics of this permission? C1 is satisfied from the very beginning, so the permission is not in effect before 1.1.2018 and can then be exercised 100 times.

Please view or discuss this issue at https://github.com/w3c/poe/issues/205 using your GitHub account

Received on Monday, 26 June 2017 13:01:02 UTC