W3C home > Mailing lists > Public > public-ws-policy@w3.org > January 2007

RE: NEW ISSUE 4224: [Framework] Section 4, last paragraph content is too restrictive - policy element information items are processed in multiple contexts

From: Daniel Roth <Daniel.Roth@microsoft.com>
Date: Mon, 15 Jan 2007 12:25:38 -0800
To: Daniel Roth <Daniel.Roth@microsoft.com>, "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-ID: <E2903CF1E4B5B144B559237FDFB291CE4E5EC9C6@NA-EXMSG-C117.redmond.corp.microsoft.com>
Fixed typo in the subject field.

Daniel Roth

________________________________
From: public-ws-policy-request@w3.org [mailto:public-ws-policy-request@w3.org] On Behalf Of Daniel Roth
Sent: Monday, January 15, 2007 12:14 PM
To: public-ws-policy@w3.org
Subject: NEW ISSUE 4224: [Framewokrk] Section 4, last paragraph content is too restrictive - policy element information items are processed in multiple contexts

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

TITLE:  Section 4, last paragraph content is too restrictive - policy element information items are processed in multiple contexts

TARGET:  Web Services Policy 1.5 - Framework

DESCRIPTION:

The content in Section 4, last paragraph reads:

"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 below."

This statement was intended to indicate that wsp:Policy elements embedded in assertion parameters or other extensions are not processed by the framework.  However, this statement is too restrictive.  It doesn't allow for processing the root wsp:Policy element.  Also, it doesn't allow for processing policy expressions in the compact form.


There is already text in section 4.3.2 [2] that clarifies that policy expressions within assertion parameters should not be processed:


Note: This specification does not define processing for arbitrary wsp:Policy Element Information Items in the descendants of an assertion parameter, e.g., in the [children] property of one of the [children] as in <Lorem><Ipsum><wsp:Policy> ... </wsp:Policy></Ipsum></Lorem>.


JUSTIFICATION:

The current statement about the processing of wsp:Policy elements is inaccurate.

PROPOSAL:

Remove the last paragraph in Section 4

To add further clarity, we also suggest that the example in the Note in section 4.3.2 be broken out as a fully formatted example with a root wsp:Policy element:

Example ??
<wsp:Policy>
<Lorem>
<Ipsum>
<wsp:Policy> ...
</wsp:Policy>
</Ipsum>
</Lorem>
<wsp:Policy>

Daniel Roth

[1] http://www.w3.org/TR/2006/WD-ws-policy-20061117/#rPolicy_Expression
[2] http://www.w3.org/TR/2006/WD-ws-policy-20061117/#Policy_Assertion_Nesting
Received on Monday, 15 January 2007 20:25:46 GMT

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