Re: [NEW ISSUE] 4235 clarification needed to sect 4.3 to indicate that the normalization algorithm can be applied to wsp:Policy element used as XML element policy attachment

All,

Another approach has been preliminarily discussed during the initial f2f 
discussions of issue 4235. Rather than simply add a
note, as originally proposed, change the specific starting point for the 
normal form algorithm to be the EII of the root of the
policy expression to be normalized.

Roughly, this would involve:

<PaulC> Proposal:
<PaulC> 1. Start with the Element Information Item E (as defined in the 
XML Information Set [XML Information Set]) of the policy expression. The 
[namespace name] of E is always "http://www.w3.org/@@@@/@@/ws-policy". In 
the base case, the [local name] property of E is "Policy"; in the 
recursive case, the [local name] property of E is "Policy", "ExactlyOne", 
or "All".
<PaulC> 2. and change "D" to "E" in subsequent steps. 

It has also been suggested by Umit that we could do both. e.g. make the 
changes as outlined above, and add a corresponding note that
indicates that you extract the policy expression from its element context 
and treat it separately.

Some also observed that we needed to possibly specify how you find the 
"root" of the policy expression.

We will pick up discussion from this point during tomorrow's f2f 
discussion after we address the wsdl1.1 identifiers issues.

Cheers,

Christopher Ferris
STSM, Software Group Standards Strategy
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/page/chrisferris
phone: +1 508 377 9295

public-ws-policy-request@w3.org wrote on 01/16/2007 04:18:42 PM:

> 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=4235 
> 
> Title: clarification needed to sect 4.3 to indicate that the 
> normalization algorithm can be applied to wsp:Policy element used as
> XML element policy attachment 
> 
> Description: 
> http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-
> framework.html?content-type=text/html;%
> 20charset=utf-8#Compact_Policy_Expression 
> 
> The algorithm starts with a document information item. However, the 
algorithm
> is meant to be applied in situations where the compact form policy 
expressions
> are included in another base document using the attachment mechanisms 
defined
> in WS-Policy 1.5 - Attachments. Obviously, in such situations, it is 
intended
> that the policy expression be taken out of context and treated as ifit 
were a
> separate document. 
> 
> Justification: Could be misunderstood. 
> 
> Type: editorial 
> 
> Proposal: Add a note to section 4.3 that says roughly the following: 
> 
> Note: compact policy expressions that are included in other XML 
> documents, such 
> as WSDL, as described in WS-Policy 1.5 - Attachments, are treated, 
> for purposes 
> of normalization, as if they were extracted out of thier embedded 
context and
> considered independently as a document. 
> 
> Cheers, 
> 
> Christopher Ferris
> STSM, Software Group Standards Strategy
> email: chrisfer@us.ibm.com
> blog: http://www.ibm.com/developerworks/blogs/page/chrisferris
> phone: +1 508 377 9295