[Odrl-cc] Meaning hidden in the name of profile?

[Lars Gunnarsson]

Sorry for my delay in commenting on this issue.

Alternative 2:
Implying that the CC profile means "all permissions allowed" to my understanding actually means that we are hiding the semantic . Checking for this would then only be possible based on the name of the profile. In other words, any implementation will have to test whether the name is ODRL/CC and then from that point on handle this profile differently. This would mean that if somebody else wants to define a profile of their own with a similar meaning, but still not completely compatible with the ODRL/CC, then they can not do so. The will have to also imply that the name of their own profile means the same thing as ODRL/CC. But this now means that their implementation is no longer compatible with the rest of the world.

This is for sure not a good solution!

Alternative 1:
To me this seems to be the right place to describe what the ODRL/CC Profile is all about. Any implementations will have to consider the new Permission semantic, or else they will not be able to handle the ODRL/CC profile. 

I am not able to suggest how the syntax of this semantic should look like, as my experience is more in the area of implementing applications. There will probably be others on this list who can make suggestions on that.

If the syntax is designed nicely, so that it is clearly understood that this syntax means "any usage" and limitations then can be added (in a formal way), then we gain that any profile can make use of this (potentially a local profile of my own design, not published anywhere), and any implementation will be able to deal with it correctly (as long as it can deal with this specification). Sounds like a very good design to me!

Regards,

Lars Gunnarsson
Trans World Radio, Europe
Vienna, Austria

-----Original Message-----
From: odrl-cc-bounces at odrl.net [mailto:odrl-cc-bounces at odrl.net] On Behalf Of odrl-cc-request at odrl.net
Sent: Dienstag, 16. November 2004 12:27
To: odrl-cc at odrl.net
Subject: Odrl-cc Digest, Vol 2, Issue 2

Today's Topics:
   1. Re: Romeo Project (Renato Iannella)

----------------------------------------------------------------------
Date: Mon, 15 Nov 2004 12:16:21 +1000
From: Renato Iannella <renato at odrl.net>
Subject: [Odrl-cc] Re: Romeo Project
To: ODRL Creative Commons Profile WG <odrl-cc at odrl.net>
Message-ID: <5775C094-36AC-11D9-A70C-00306541C018 at odrl.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

On of the issues from the Romeo Report [1] was the need to explicitly express all the usage permissions (such as play, print give, etc) as this is the basis of the ODRL permission model. (The model will be revised in Version 2.O to cater for new requirements [2].)

There are two mechanisms that we could adopt to support this requirement.
1 - define a new Permission semantic to allow any "usage" permission
2 - imply that by using the ODRL/CC Profile, all permissions are
     allowed except those specified in the expression.

Is there any preferences? (or other options?)

Cheers

Renato Iannella
ODRL Initiative
http://odrl.net

[1]
<http://www.lboro.ac.uk/departments/ls/disresearch/romeo/
Romeo%20Studies%206.pdf>
[2] <http://odrl.net/2.0/v2req.html>


------------------------------

_______________________________________________
Odrl-cc mailing list
Odrl-cc at odrl.net
http://lists.odrl.net/mailman/listinfo/odrl-cc


End of Odrl-cc Digest, Vol 2, Issue 2
*************************************