- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Sep 2017 09:08:46 +0000
- To: public-poe-archives@w3.org
nitmws has just created a new issue for https://github.com/w3c/poe: == XML Schema issues == I had a look at the ODRL XML Schema at http://w3c.github.io/poe/vocab/ODRL22.xsd - referrenced from the CR Vocabl document, in the non-normative section [5.3 XML ](https://www.w3.org/TR/2017/CR-odrl-vocab-20170926/#xml) and found details which do not align the the IM of the CR: * Policy/@profile and @inheritFrom take only a single URI. A simpleType defined as list of xs:anyURI could be used to solve that issue. * Asset/@partOf: same as above. * Constraint type: the @rightOperand takes the simpleType listOfValues - fine. But the @rightOperandReference takes only a single URI. Solution same as above. * what about Logical Constraints? This class is not implemented by the XML Schema. * using the o:Duty type for consequences and remedies is questionable: the IM defines these properties should not have a consequence property, using this type allows to have consequences (and this way and endless nesting of consequences :-( ). A new type like DutyNoConseq should be defined without a consequence child element. Please view or discuss this issue at https://github.com/w3c/poe/issues/276 using your GitHub account
Received on Friday, 29 September 2017 09:08:36 UTC