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

Issue 3710 - clarify that assertion parameters are opaque to framework policy processing

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Wed, 13 Sep 2006 07:55:15 -0700
Message-Id: <AAB5B6E5-F736-450B-A272-BE653A435EC1@nokia.com>
Cc: Hirsch Frederick <frederick.hirsch@nokia.com>
To: public-ws-policy@w3.org

Issue 3710 added- <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3710>

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]


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.

Test: clarity of document on this point.

[1] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy- 

regards, Frederick

Frederick Hirsch
Received on Wednesday, 13 September 2006 14:58:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:15 UTC