Re: [poe] Compatibility with common patterns for linking assets to policies

@riannella  I am now quite unclear about what the 'resolution' is...

I see there is a hasPolicy from Asset to Policy, and dc:license is a subproperty of it.
(btw the Turtle file apparently uses dct: and your documentation used dc:. Probably both should have the same)
This seems to meet most of the original issue.

The only question mark is why
odrl:hasPolicy owl:inverseOf :target
has been removed.

The inverse axiom would certainly allow to infer correct statements for policies with direct attachement of targets as in example 24 at https://w3c.github.io/poe/model/

{
     "@context": "http://www.w3.org/ns/odrl.jsonld",
     "@type": "Policy",
     "uid": "http://example.com/policy:8888",
     "target": "http://example.com/music/1999.mp3",
[etc]

Then there is the issue of infering the hasPolicy links in the case when targets are attached to policies via rules. The owl:inverse wouldn't work if there is no direct link between the Policy and the target. But it could work if we add

  odrl:target  owl:propertyChainAxiom  ( [ owl:unionOf  ( odrl:permission odrl:prohibition ) ] odrl:target ) .

(this says that whenever there's a path policy-permission-target or policy-prohibition-target then one can infer a statement policy odrl:target target)

Of course this would require that this axiom is true, which is not clear. The "The processing model for Policies with multiple Assets, Parties, and Actions declared at the Policy-level" only propagates the target from a Policy to its attached Permissions or Prohibitions.


-- 
GitHub Notification of comment by aisaac
Please view or discuss this issue at https://github.com/w3c/poe/issues/184#issuecomment-310349942 using your GitHub account

Received on Thursday, 22 June 2017 11:12:29 UTC