From Susanne.Guth at gmx.net Mon Feb 14 07:35:53 2005 From: Susanne.Guth at gmx.net (Susanne Guth) Date: Sat Jun 2 13:28:04 2007 Subject: [Odrl-version2] New ODRL Requirements Document released! References: <27511.1101264970@www52.gmx.net> Message-ID: <5617.1108326953@www30.gmx.net> Dear ODRL Community! Thank you for all the valuable input to the ODRL Version 2 Requirements Document. Please find the updated document "ODRL Initiative Requirements Working Draft: 13. Februar 2005" at http://odrl.net/2.0/v2req.html The phase of actively gathering requirements is now closed. The main focus of the Version 2 working group is now to create the new specification documents. However, the requirements documents is still subject to further changes. Therefore, any comments on the requirements document are still appreciated and extremely valuable for the ODRL Initiative. Please send your thoughts, critics, technical comments, new requirements, or other notes to odrl-version2 interest list (please find list details at http://odrl.net/2.0/) Cheers Susanne Guth Renato Iannella **************** -- Susanne Guth susanne@odrl.net ODRL Initiative http://odrl.net/ Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail From renato at odrl.net Tue Feb 15 13:55:06 2005 From: renato at odrl.net (Renato Iannella) Date: Sat Jun 2 13:28:04 2007 Subject: [Odrl-version2] Permissions and Prohibitions Message-ID: Dear all - an issue for discussion on if Permissions and Prohibitions can occur together (see the early model [1]) in the same expression. A1) Permissions indicate the actions you are allowed to do *and* only these actions B1) Prohibitions indicate the actions you are not allowed to do *but* everything else is OK If A1 and B1 are mutually exclusive, then it is OK. However, if you put them together in an expression, you need to refine the rules, like: A2) Permissions indicate the actions you are allowed to do B2) Prohibitions indicate the actions you are not allowed to do C) If A2 occurs and no B2, then you can only do A2 D) If B2 occurs and no A2, then you can do anything except B2 E) If A2 and B2 occurs, you can only do A2 and not B2 (Rule E is a bit redundant in that if you can only do A2, then that also means you can't do B2) An example of where Permissions and Prohibitions may be used together is in the Creative Commons licenses. (In the ODRL CC Profile [2], we have turned CC Prohibitions into negative Constraints.) The issue is do we keep the Permissions and Prohibitions as mutually exclusive or we have some refined rules and allow them both to appear in the same expression. Cheers Renato Iannella ODRL Initiative http://odrl.net [1] [2] From Susanne.Guth at gmx.net Fri Feb 18 22:50:27 2005 From: Susanne.Guth at gmx.net (Susanne Guth) Date: Sat Jun 2 13:28:04 2007 Subject: [Odrl-version2] Permissions and Prohibitions References: Message-ID: <11577.1108727427@www17.gmx.net> Dear all! This is really a tricky, difficult topic. For implementors anything that does not follow the rules A1 and B1 is hard and leaves room for ambiguity. I would like to add that Renato's rule E is one of the hardest: > E) If A2 and B2 occurs, you can only do A2 and not B2 But what about the things that are not specified, are they allowed? or are they forbidden? If we decide against A1 and B1 then we would need rule E adapted, such as E-New) If A2 and B2 occurs, you can only do A2 and not B2, and everything that is not specified is forbidden. Please note that the prohibition entity is addressing requirement 1.7 Susanne > > Dear all - an issue for discussion on if Permissions and Prohibitions > can occur together (see the early model [1]) in the same expression. > > A1) Permissions indicate the actions you are allowed to do *and* only > these actions > B1) Prohibitions indicate the actions you are not allowed to do *but* > everything else is OK > > If A1 and B1 are mutually exclusive, then it is OK. > However, if you put them together in an expression, you need to refine > the rules, like: > > A2) Permissions indicate the actions you are allowed to do > B2) Prohibitions indicate the actions you are not allowed to do > C) If A2 occurs and no B2, then you can only do A2 > D) If B2 occurs and no A2, then you can do anything except B2 > E) If A2 and B2 occurs, you can only do A2 and not B2 > > (Rule E is a bit redundant in that if you can only do A2, then that > also means > you can't do B2) > > An example of where Permissions and Prohibitions may be used together > is in > the Creative Commons licenses. (In the ODRL CC Profile [2], we have > turned > CC Prohibitions into negative Constraints.) > > The issue is do we keep the Permissions and Prohibitions as mutually > exclusive > or we have some refined rules and allow them both to appear in the same > expression. > > Cheers > > Renato Iannella > ODRL Initiative > http://odrl.net > > [1] > [2] > > _______________________________________________ > ODRL-Version2 mailing list > ODRL-Version2@odrl.net > http://lists.odrl.net/mailman/listinfo/odrl-version2 > -- Susanne Guth susanne@odrl.net ODRL Initiative http://odrl.net/ Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail