W3C home > Mailing lists > Public > public-ws-policy-qa@w3.org > September 2006

[Bug 3710] Clarify that policy assertion parameters are opaque to framework processing

From: <bugzilla@wiggum.w3.org>
Date: Tue, 12 Sep 2006 21:37:06 +0000
To: public-ws-policy-qa@w3.org
Message-Id: <E1GNFwI-0004xp-It@wiggum.w3.org>


           Summary: Clarify that policy assertion parameters are opaque to
                    framework processing
           Product: WS-Policy
           Version: FPWD
          Platform: Macintosh
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Framework
        AssignedTo: frederick.hirsch@nokia.com
        ReportedBy: frederick.hirsch@nokia.com
         QAContact: public-ws-policy-qa@w3.org


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"


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 

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.
Received on Tuesday, 12 September 2006 21:37:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:09 UTC