- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Dec 2016 13:21:02 +0000
- To: public-poe-archives@w3.org
My 5 cents on that: asset and party properties should be added to the Policy and not deprecated for Permission/Prohibition/Duty. The processing rule should be: the related assets and parties of a P/P/D are the assets and parties of this P/P/D instance or if not existing of the parenting policy instance. This way a processor would have to search "bottom up" but only for properties of the same name and structure. But: that triggers more thoughts: what about constraints and duties shared across multiple P/P/Ds? I have to say frankly the @id and @idref design of the XML syntax was never my good friend - and also not used in any of the XML examples. Was something like that ever defined for JSON? And this reference-by-structure design could be a consistent approach across different syntaxes. -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/82#issuecomment-266012192 using your GitHub account
Received on Friday, 9 December 2016 13:21:09 UTC