[Odrl-version2] RE: ODRL-Version2 Digest, Vol 9, Issue 7

[Renato Iannella]

On 29 Aug 2005, at 22:58, Vicky Weissman wrote:




> Can you give some examples of what you'd want to do with the "and"  
> and "or"
> constraint containers?  Do you remember which solutions were  
> proposed and
> what people didn't like about them?
>
>
>
>

In V1.1, we had an explicit XML container mechanism that allowed you  
to say
that you have Permission X <or> Y (not both) - by default, all  
Permissions
were and-ed. This container was a bit messy.

There seems to be 3 alternatives:

1 - Put all the <or> options into separate Offers

2 - Link the alternate Permissions as Prohibitions - that is - You  
are Permitted
     to do X and Y, but you are Prohibited to do X if you have done Y  
(and vice versa)

3 - Keep the <or> structure in the V2 model






> Suppose that the Cornell library signs an agreement with the ACM.  The
> agreement is that any member of the Cornell community (student,  
> faculty, or
> staff) can print any ACM article up to 5 times.  Could such an  
> agreement be
> written in ODRL?  If the answer is yes, what happens to next year's  
> incoming
> class?  At the time the agreement was made, they were not members  
> of the
> Cornell community nor were their identities known, but intuitively  
> they
> should be able to make copies once they join Cornell.  With this  
> example in
> mind, I think membership should be determined at the time a request  
> is made
> (e.g., when Alice asks to copy an ACM article) and not assumed to  
> be known
> when the agreement is signed.  What do you think?
>
>
>
>

Yes. This is were a REL and an access control language differ. A REL  
should express the
policy (ie any member of Cornell), and a "system" needs to  
dynamically check the
access credentials to ensure the Policy is Ok.





> I would like to create an algorithm that can be used to determine  
> whether a
> set of ODRL licenses imply a permission, but I might not get to  
> this for
> awhile because of other commitments.  Is there a particular date by  
> which you
> need to have this for it to be considered for the new release or  
> should I
> just get to it as soon as possible?
>
>
>
>

Whenever you can Vicky!

Cheers

Renato Iannella
ODRL Initiative
http://odrl.net