- From: Renato Iannella <renato.iannella@monegraph.com>
- Date: Tue, 29 Nov 2016 21:43:18 +1000
- To: benedict.whittamsmith@thomsonreuters.com
- Cc: public-poe-wg@w3.org
Received on Tuesday, 29 November 2016 11:43:56 UTC
Thanks Ben, just trying to extract the real semantics of “unit-of-count”… From your example, we can see its used to “multiple the amount to pay” (pay per X) as in: > :constraint4-1 a odrl:Constraint ; > odrl:payAmount "65.28"^^xsd:decimal ; > odrl:unit <http://cvx.iptc.org/iso4217a:EUR <http://cvx.iptc.org/iso4217a:EUR>> ; > tr:unitOfCount tr:AccessID ; And then (latter in the example, and ignoring the extended relations stuff for now) it is used to indicate what data to report back on the odrl:inform Duty > On the 15th of every month you must report usage by providing a list of either Access IDs or Physical IDs: > :duty5 a odrl:Duty ; > odrl:action odrl:inform ; > odrl:timeInterval "15"^^xsd:gDay > odrl:operation odrl:xor > odrl:constraint :constraint5-1, :constraint5-2 . > :constraint5-1 a odrl:Constraint ; > tr:unitOfCount tr:AccessIDList . > :constraint5-2 a odrl:Constraint ; > tr:unitOfCount tr:PhysicalIDList . Have I got that right? Renato Iannella, Monegraph Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group
Received on Tuesday, 29 November 2016 11:43:56 UTC