Re: [poe] ambiguous semantics of duty constraints

I think the semantics for the second example is better matched if you use andSequence because the "should=>" is saying that the time constraint is first, followed by the payAmount constraint.

```
<http://example.com/policy:42>
    a odrl:Agreement ;
    odrl:obligation [ 
 # a odrl:Duty ;
        odrl:assignee <http://example.com/person:44> ;
        odrl:assigner <http://example.com/org:43> ;
        odrl:action odrl:compensate ;
        odrl:constraint [ 
            odrl:leftOperand cTime1 ;
            odrl:operator odrl:andSequence ;
            odrl:rightOperand cPay1 ;
        ]
    ] .
 
 cPay1:  a odrl:Constraint ;
         odrl:leftOperand odrl:payAmount ;
            odrl:operator odrl:eq ;
            odrl:rightOperand "500.00" ;
            odrl:unit <http://dbpedia.org/resource/Euro> .
 
 cTime1:  a odrl:Constraint ;
         odrl:leftOperand odrl:payAmount ;
            odrl:operator odrl:eq ;
            odrl:rightOperand "500.00" ;
            odrl:unit <http://dbpedia.org/resource/Euro> .
 
```
 


-- 
GitHub Notification of comment by riannella
Please view or discuss this issue at https://github.com/w3c/poe/issues/211#issuecomment-316911761 using your GitHub account

Received on Friday, 21 July 2017 06:04:12 UTC