>Use of a policy framework element to contain a nested assertion enables nested assertions to be distinguished from assertion parameters and processed appropriately The major difference between using assertion parameter and a nested assertion is the intersection ability, the above sentence does not make sense Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122 Frederick Hirsch <frederick.hirsch @nokia.com> To Sent by: public-ws-policy@w3.org public-ws-policy- cc request@w3.org Hirsch Frederick <frederick.hirsch@nokia.com> Subject 08/21/2006 12:01 Proposed change to Framework 3.1 PM I propose the following change to 3.1, "Policy Assertion" in the latest editor's draft of the policy framework [1]. The change is shown as a red-line to 3.1, in the attached PDF. This is proposed as a partial resolution to bug report 3549 [2] and as a replacement to previous proposals regarding text to clarify the framework with regards to this issue. I propose the issue with regards to the normalization procedure in 4.2 (as also noted in the bug report) should be made a separate issue. This normalization procedure does not appear to explicitly pass through parameters. regards, Frederick Frederick Hirsch Nokia [1] <http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy- framework.html?content-type=text/html;%20charset=utf-8> [2] <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3549> [attachment "policy-framework-3549-proposal.pdf" deleted by Anthony Nadalin/Austin/IBM]
(image/gif attachment: graycol.gif)
(image/gif attachment: pic28670.gif)
(image/gif attachment: ecblank.gif)
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:40 GMT