- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Sun, 18 Jun 2017 17:53:47 +0000
- To: public-poe-archives@w3.org
For XML it looks like we have a solution - but not for JSON(-LD): Examples 17 and 18 in the Information Model document's https://w3c.github.io/poe/model/#constraint-compound section show a "constraint" at the top level of the object. The object claims by its `"@type": "Offer"` to be a subclass of odrl:Policy. But in the ODRL ontology we have this specification of the constraint property: ``` :constraint a rdf:Property , owl:ObjectProperty, skos:Concept ; rdfs:isDefinedBy odrl: ; .... rdfs:domain [ a owl:Class ; owl:unionOf ( :Rule :AssetCollection :PartyCollection ) ; ] ; rdfs:range :Constraint . ``` This shows no :Policy (and no :Offer etc) in the rdfs:Domain, therefore Examples 17 and 18 are unfortunately invalid. So we could do something similar like for XML, it would even be better to have a definition that only a constraint referenced by a Compound Constraints may be a property of Policy - may be possible by some tricky RDF/OWL. -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/193#issuecomment-309292324 using your GitHub account
Received on Sunday, 18 June 2017 17:53:53 UTC