This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Issue 1. Clarify that core Framework policy processing does not apply to descendants of policy assertion parameters 2. Clarify wording in 4.3.2 in Framework "Policy Assertion Nesting" Proposal In 4.3.2 in Framework a. Replace /Assertion/*/wsp:Policy with "Note:" (note that this XPath would incorrectly include nested policy expressions, since it should be /Assertion/<parameter>/*/wsp:Policy b. replace "the descendants of an assertion, e.g." with "the descendants of an assertion parameter, e.g." 3. Make more general statement of scope of policy processing in updated introduction to 4 (Policy Expression) See text Chris proposed: This specification does not define processing for arbitrary wsp:Policy Element Information Items in any context other than as an Element Information Item in the [children] property of an Element Information Item that is in the [children] property of an element Information Item defined in section 4.1.
In template format: Description - Clarify that assertion parameters are opaque to generic policy framework processing Justification - current specification states that assertion parameters do not have descendant policy elements processed, but some clarity and editorial correction needed. Two aspects: 1. Clarify that core Framework policy processing does not apply to descendants of policy assertion parameters 2. Clarify wording in 4.3.2 in Framework "Policy Assertion Nesting" Target - WS-Policy Framework [1] Proposal: In 4.3.2 in Framework a. Replace "/Assertion/*/wsp:Policy" with "Note:" (note that this XPath would incorrectly include nested policy expressions, since it should be /Assertion/<parameter>/*/wsp:Policy b. replace "the descendants of an assertion, e.g." with "the descendants of an assertion parameter, e.g." 3. Make more general statement of scope of policy processing in updated introduction to 4 (Policy Expression) See text Chris proposed: This specification does not define processing for arbitrary wsp:Policy Element Information Items in any context other than as an Element Information Item in the [children] property of an Element Information Item that is in the [children] property of an element Information Item defined in section 4.1. Test: clarity of document on this point. [1] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;%20charset=utf-8
Resolved according to entire proposal http://www.w3.org/2006/09/14-ws-policy-irc#T21-08