[Odrl-version2] resumption of containers & model update

[Alapan Arnab]

Hi,
Please see my note on interpretation on this issue on my previous email.

Alapan
On Mon, 2006-01-30 at 10:17 +0100, Susanne Guth wrote:
> Hi Renato,
> 
> I agree, we have to make this clear:
> 
> What about distinguishing the following cases:
> 
> Case 1.) Either permissions OR (exclusive) prohibitions are allowed: In this
> world we can follow our former spec, saying 
> 
>  "Permissions are what you are allowed to perform on the target **and
> nothing else**"
> 
>  "Prohibitions are what you are NOT allowed to perform on the target **but
> everything else** is allowed."
> 
> Case 2.) Permissions AND Prohibitions are allowed: In this world we could
> state:
> 
>  "Permissions are what you are allowed to perform on the target **and
> nothing else**"
> 
>  "Prohibitions are what you are explicitly NOT allowed to perform on the
> target **and anything else is still not allowed."
> 
> With this second case, we could cover the CC licenses, I think. Don't we?
> 
> +++++++++++++++
> 
> With this, we treat Prohibitions under certain conditions differently. Is
> that problematic? Vicky? If we run into troubles, then I would suggest to
> only go with solution/case 2.
> 
> So long
> Susanne
> 
> 
> > 
> > Thanks Susi - I like the update!
> > 
> > > 2.) I kept prohibitions as they were. However, this issue need further
> > > discussion. The important question is if we can formalise the model  
> > > with
> > > prohibitions in it... vicky I count on you here :)
> > 
> > We also need to be able to express the semantics of Permissions/ 
> > Prohibitions in the
> > (less formal) Model. In particular, the conflict that arises when  
> > both are used in
> > a single expression (or expressions that are merged/inherited...)
> > 
> > In the current V2 Model, we only say that Permissions are what you  
> > are allowed to
> > perform on the Target, and Prohibitions what you are not.
> > 
> > Remember in V1.1 we said that Permissions are what you are allowed to  
> > perform on
> > the target **and nothing else** - that last bit is the important  
> > difference.
> > 
> > a) Consider the following:
> >   Permission = Display
> >   Prohibition = Print
> > 
> > The person can display the target but not print it.
> > 
> > What about editing? It certainly does not say I can't do it.
> > But it does not say that I can either.
> > 
> > 
> > How can we define the semantics of Permissions/Prohibitions so that  
> > when they
> > both appear, it is clear what they both mean?
> > 
> > Perhaps we need a way to indicate if they represent a "closed set" of  
> > actions?
> > 
> > Cheers...  Renato
> > 
> > 
> > _______________________________________________
> > ODRL-Version2 mailing list
> > ODRL-Version2 at odrl.net
> > http://lists.odrl.net/mailman/listinfo/odrl-version2
> > 
> 
-- 
Alapan Arnab
Data Networks Architecture (DNA) Laboratory
Department of Computer Science
University of Cape Town
Rondebosch, 7700
South Africa

Tel: +27 21 650 3127
Web: http://people.cs.uct.ac.za/~aarnab/
Blog: http://idiots-mind.blogspot.com
----------
"You must always believe that you can be the best, but you must never
believe you have achieved it".
Juan Manuel Fangio