[Odrl-version2] Core Model: Roles, Parties and Assets

[David Martin]

The current ONIX definition of the Usage verb "include" is "Include a 
copy of a resource as part of another defined resource" (resource = 
asset).  The copy is not modified, but it has become part of another 
asset, which may itself then be the subject of other permissions and 
prohibitions because it includes licensed content.

Answering your questions:
1.  Yes, perhaps it is, except that in the use cases where ONIX 
"include" is used you wouldn't necessarily think of the result as a 
"collection" - in some cases you might, in others you certainly 
wouldn't.
2, 3.  Whenever a related entity is associated with an ONIX Usage, it is 
referenced by an identifier, which may be a term from the ONIX 
Dictionary or a label which has been assigned to a definition which is 
itself part of the ONIX expression (outside of the Usage entity).  In 
either case, the term or label may specify a single specific asset or a 
member of a class of assets, the latter being much more frequent in 
practice.

Renato, I don't think it is helpful to get hung up on a particular 
action/usage type, or a particular use case.  "Include" isn't the only 
one that can involve secondary assets, and I'm sure there will be others 
we haven't come across yet.  Nor, perhaps, should we worry too much 
about the ODRL vocabulary at this stage: as your documents say 
"Additional and/or different semantics may be defined in ODRL Profiles 
... for particular ODRL application areas defined by industry and 
community sectors".

What we are concerned about in the first instance is to ensure that the 
ODRL Model can be mapped to and from the core structural elements of an 
ONIX Usage without any loss of generality.  In most respects we are 
already pretty sure that it can, probably with some adjustment on the 
ONIX side.  However, we don't see how we can work without an option in 
ODRL to link an action to other defined assets, with roles, besides the 
(mandatory) primary asset.

David

In message <3E2B309D-A2A9-4615-9922-8D581E39F0DA at odrl.net>, 
"ri at odrl.net" <ri at odrl.net> writes
>Ok..let me try and refine the definition of "include" then (as I don't 
>think the current Common Voacb defn is correct)...
>
>Identifier: include
>Semantics: The act of including other assets with the asset
>Comments: The asset is not changed, but other assets can be assembled with it
>
>Questions:
>
>1 - is this similar to the current "aggregate" action?
>2 - do you need to specify (via a UID) what the "other assets" are?
>3 - or do you need to specify the class of the "other assets" - eg 
>"academic work", "thesis"...?
>
>Renato
>_______________________________________________
>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/3246 - Release Date: 11/09/10
>

-- 
David Martin
david at polecat.dircon.co.uk

Address in UK
117 Percy Road, HAMPTON TW12 2JS, UK
Telephone +44 (0)20 8286 8983 (or 8979 2516, if no reply)

In Tenerife
Rambla de Santa Cruz 153, Sexto, Puerta 21, 38001 Santa Cruz de Tenerife, SPAIN
Telephone +34 922 27 23 92
Mobile (in Spain only) +34 639 742 634