Policy Conflict Strategy (eg32)

A policy from the W3C ODRL examples. The table gives the source and what the policy shows, in the source's words.

SourceWhat it shows
model#conflictExample Use Case: Two Policies are associated to the same target Asset http://example.com/asset:1212. The first Policy http://example.com/policy:0001 allows to use the Asset. The second Policy http://example.com/policy:0002 allows for the display of the Asset, but it prohibits print. Both policies explicitly state how to deal with conflicts through the conflict property being set to perm. Hence the Permissions will always override any Prohibitions. In this use case, since the print Action is a specialisation of the use Action, there could be a conflict. However, the perm conflict strategy means that the use Permission will override the print Prohibition.

Policy #

{
  "@context": "http://www.w3.org/ns/odrl.jsonld",
  "@type": "Policy",
  "uid": "http://example.com/policy:0001",
  "profile": "http://example.com/odrl:profile:40",
  "conflict": "perm",
  "permission": [
    {
      "target": "http://example.com/asset:1212",
      "action": "use",
      "assigner": "http://example.com/owner:181"
    }
  ]
}

Reading #

The sentences OdrlProse writes for this policy, without a profile.

Policy set http://example.com/policy:0001

A set of rules.

  • Written to the profile http://example.com/odrl:profile:40.
  • If a permission and a prohibition conflict, the permission wins.
  1. Anyone may use asset:1212, as permitted by the assigner owner:181.

The renderer raised no warning for this policy.

Back to the W3C ODRL examples or the catalog.