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: Wed, 13 Sep 2006 14:53:47 +0000
CC:
To: public-ws-policy-qa@w3.org
Message-Id: <E1GNW7X-0002eI-0v@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3710





------- Comment #1 from frederick.hirsch@nokia.com  2006-09-13 14:53 -------
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
Received on Wednesday, 13 September 2006 14:54:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:08 GMT