Policy improvement

In many cases, the Asset (target) and Parties (assigner, assignee) are the same for multiple Permissions and Prohibitions in an ODRL Policy.

It maybe a useful change to support the Asset/Party at the Policy level, which means that these values all apply to the enclosed Perms/Prohibs (and conversely means that the Perms/Prohibs do not define these values). 

If you look at this example: http://w3c.github.io/poe/vocab/#sc-example8 <http://w3c.github.io/poe/vocab/#sc-example8>

It would then look like:
{
    "policytype": "http://www.w3.org/ns/odrl/2/Agreement",
    "policyid": "http://example.com/policy:3433",
    "conflict": "perm",
    "target": "http://example.com/music:1234908",
    "assigner": "http://example.com/sony:10",
    "assignee": "http://example.com/billie:888"
    "permissions": [{
        "action": "http://www.w3.org/ns/odrl/2/play",
    }],
    "prohibitions": [{
        "action": "http://oma.org/drm:ringtone",
    }]
}


Renato Iannella, Monegraph
Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group