[Odrl-version2] Core Model: Roles, Parties and Assets
David Martin
david at polecat.dircon.co.uk
Tue Nov 9 22:25:05 EST 2010
No, I'm not talking about a Duty. In the ONIX vocabulary, Include is a
Usage Type (or Action Name) which relates to a freestanding act which
may be either Permitted or Prohibited. Including a licensed content
part in a course pack is not a Duty associated with another Action -
it's an Action in its own right. Of course, we understand that Include
may also be part of a Duty, if it's a matter of including a credit or
acknowledgement, for example.
From the very first stages of looking at the ODRL model, we identified
the fact that it allows only one Asset to be associated with an Action
(other than via Duty) as a limitation which we would have to ask you to
consider removing. The ONIX Usage entity has a mandatory Used Resource
(= ODRL Asset), but it also has an optional Usage Related Resource,
repeatable with role values to express the nature of the association.
We believe this is an essential element for some permissions and
prohibitions.
I hope, however, that I'm not misunderstanding the scope of Duty in the
ODRL context.
David Martin
EDItEUR
In message <2CCD8136-B20B-4446-A80D-D664F486C6E7 at odrl.net>,
"ri at odrl.net" <ri at odrl.net> writes
>
>On 9 Nov 2010, at 00:28, David Martin wrote:
>
>> This crops up all the time in licensing of electronic resources to
>>academic libraries, often in connection with what ONIX would call an
>>"Include" permission. For example: "include licensed content part in
>>printed course pack" or "include licensed content part in digital
>>instructional material" or include licensed content part in academic
>>work" (such as a thesis or dissertation). The asset (or, in ONIX
>>language, resource) used is a licensed content part, and there is
>>another ("target") asset or resource which is the thing in which a
>>copy of the original asset may be included.
>
>OK - I think we touched on this use case at the Namur Meeting...
>
>In this case, we can define a Duty (action="include") and link to the
>Asset (eg the license content part)
>
>(Duties can have Assets associated with them, but not direct from an Action.)
>
>Cheers
>
>Renato Iannella
>ODRL Initiative
>http://odrl.net
>
>
>
>_______________________________________________
>Odrl-version2 mailing list
>Odrl-version2 at odrl.net
>http://odrl.net/mailman/listinfo/odrl-version2_odrl.net
>
>
>-----
>No virus found in this message.
>Checked by AVG - www.avg.com
>Version: 10.0.1153 / Virus Database: 424/3244 - Release Date: 11/08/10
>
--
David Martin
david at polecat.dircon.co.uk
More information about the Odrl-version2
mailing list