- From: Michael Steidl \(IPTC\) <mdirector@iptc.org>
- Date: Wed, 27 Sep 2017 19:17:33 +0200
- To: <vrodriguez@fi.upm.es>
- Cc: "'W3C POE WG'" <public-poe-wg@w3.org>
- Message-ID: <066801d337b4$81b1caf0$851560d0$@iptc.org>
Hi Victor, thanks for numbering all the items on the POE/ODRL Validation page - https://www.w3.org/2016/poe/wiki/Validation Now I have added them to the Implementation Report sheet at <https://goo.gl/iXnonW> https://goo.gl/iXnonW And noticed a few issues: * Items V11 . V15 are about the role of a profile in a Policy and the headlines say ". only ODRL . can be used". But: this must be ". only ODRL Core . can be used" as we have two different ODRL vocabularies, Core and Common. (The internal text mentions this in some cases correctly, in some not.) Please make the need for ODRL Core visible. * A very special case is V 13. In absence of profile, only ODRL left operands can be used In this case even using ODRL Core will not help as the Core vocabulary does not include any leftOperands = a profile is a mandatory requirement for adding a Constraint to a Rule. Therefore the heading must be In absence of profile, no Constraints can be used (leftOperand defined by the profile is required) * In this context V14 and V15 is questionable: without profile no Constraint - therefore the existence of an operator cannot be checked and a Logical Constraint cannot point to any constraints. Ok, that's it. Please let me know about fixing this as I should update the Report sheet. Thanks, Michael
Received on Wednesday, 27 September 2017 17:18:10 UTC