RE: odrl-ISSUE-12: Make asserting flexible values more flexible [ODRL Version 2.0 XML Encoding (Public) ]

Our RightsML group has discussed the comments below and the proposed change
- our response is:
- to add the attributes @rOpDataType and @rOpUnit is fine with us.
- from our view this would fit perfectly the needs for expressing amounts in
a currency.
- we acknowledge that the ODRL "pay" action has a mandatory requirement for
a linked asset object, thus excluding an "inline expression of an amount".
- what are the alternatives:
a) to modify the ODRL requirement
b) to overload the ODRL "pay" action by a RightsML "pay" action which does
not have this mandatory need.
c) to create a new "payamount" action which allows inline amounts: this
raises the issue of having actually the same semantics as "pay", only the
formal requirements are different - and this is not a perfect approach as
this is not easy to explain to users.
- in a ranking we would prefer a), next is b), actually a no-go is c).

Thanks to the ODRL team for considering and discussing the RightsML needs

Michael

> -----Original Message-----
> From: Renato Iannella [mailto:ri@semanticidentity.com]
> Sent: Thursday, July 05, 2012 7:33 AM
> To: ODRL Community Group
> Subject: Re: odrl-ISSUE-12: Make asserting flexible values more flexible
> [ODRL Version 2.0 XML Encoding (Public) ]
> 
> 
> On 2 Jul 2012, at 18:05, Michael Steidl (IPTC) wrote:
> 
> > Coming back to my initial proposal: we think of something like this
> > below for expressing that a minimum fee of 150 USD must be paid for the
> asset:
> >
> > <o:duty>
> > 	<o:action name="ov:pay"/>
> > 	<o:constraint name="ov:paymentvalue" operator="ov:gteq"
> > rightOperand="150.00" rOpDatatype="xs:decimal"
> rOpUnits="iso4217a:USD"
> > /> </o:duty>
> 
> You could do this (without the addition of the new attributes) by allowing
the
> value of the rightOperand to include the Currency.
> That is, you can define a new constraint action (payAmount) and the value
> must include the three character currency (from  ISO4217) followed by the
> decimal amount.
> 
> For example:
> 
>        <o:constraint name="ov:payAmount" operator="ov:eq"
> rightOperand="AUD123.50"/>
> 
> > To add a very close use case: setting the date of a payment (which
> > does not require units):
> > <o:constraint name="ov:paymentduedate" operator="ov:lteq"
> > rightOperand="2012-07-31" rOpDatatype="xs:date" />
> 
> Couldn't this be represented by our current date constraint action:
> 
>   <o:constraint name="ov:dateTime" operator="ov:lteq"
> rightOperand="2012-07-31"/>
> 
> (by definition, the dateTime action is always a ISO8601/XMLSchema date
> format)
> 
> Cheers...
> Renato Iannella
> Semantic Identity
> http://semanticidentity.com
> Mobile: +61 4 1313 2206
>

Received on Friday, 9 November 2012 09:41:36 UTC