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

[ri at odrl.net]

On 10 Nov 2010, at 19:49, David Martin wrote:

> 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.

I am trying to better understand the use case to determine how the *current* model could apply...

The current ODRL model utilises Constraints to "restrict" the Permissions. I am trying to ascertain if this would work in this case, and future cases, where the action is about "other assets".

If "include" means "The act of including other assets with the asset" - by itself, this would allow you to literally include any asset with the asset.

If we had a (new) "resource" constraint, then we could apply this to "include" and others.

Example:

  <o:permission>
        <o:asset uid="urn:journal-x:article5"/>
        <o:action name="o:include"/>
        <o:constraint name="o:resource" operator="o:eq" rightOperand="onix:thesis"/>
        ...
  </o:permission>


Cheers

Renato Iannella
ODRL Initiative
http://odrl.net