RE: NEW ISSUE 4209: Example 3.1 does not follow the algorithm/definition in merging policies

Great, let me summarize the proposed change: replace example 3.1 in Section 3.3 Attachment draft[1] with the following example:

<wsp:Policy
    xmlns:wsp="http://www.w3.org/2006/07/ws-policy" >
  <wsp:All>
    <rmp:RMAssertion
       xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602" >
      <rmp:InactivityTimeout Milliseconds="600000" />
      <rmp:BaseRetransmissionInterval Milliseconds="3000" />
      <rmp:ExponentialBackoff />
      <rmp:AcknowledgementInterval Milliseconds="200" />
    </rmp:RMAssertion>
  </wsp:All>
  <wsp:All>
    <sp:AsymmetricBinding
        xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy" >
      <wsp:Policy>
        <!-- Details omitted for readability -->
        <sp:IncludeTimestamp />
        <sp:OnlySignEntireHeadersAndBody />
      </wsp:Policy>
    </sp:AsymmetricBinding>
  </wsp:All>
</wsp:Policy>

[1] http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117/#XMLElementAttachement

Regards,
 
Asir S Vedamuthu
Microsoft Corporation

-----Original Message-----
From: Yalcinalp, Umit [mailto:umit.yalcinalp@sap.com] 
Sent: Sunday, January 14, 2007 10:08 PM
To: Asir Vedamuthu; public-ws-policy@w3.org
Subject: RE: NEW ISSUE 4209: Example 3.1 does not follow the algorithm/definition in merging policies


> -----Original Message-----
> From: Asir Vedamuthu [mailto:asirveda@microsoft.com] 
> Sent: Saturday, Jan 13, 2007 2:25 AM
> To: Yalcinalp, Umit; public-ws-policy@w3.org
> Subject: RE: NEW ISSUE 4209: Example 3.1 does not follow the 
> algorithm/definition in merging policies
> 
> >Fix the example to reflect the merge
> >algorithms intent by introducing wsp:All
> >as appropriate wrappers.
> 
> I think you are asking for:
> 
> <wsp:Policy
>     xmlns:wsp="http://www.w3.org/2006/07/ws-policy" >
>   <wsp:All>
>     <rmp:RMAssertion
>        xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602" >
>       <rmp:InactivityTimeout Milliseconds="600000" />
>       <rmp:BaseRetransmissionInterval Milliseconds="3000" />
>       <rmp:ExponentialBackoff />
>       <rmp:AcknowledgementInterval Milliseconds="200" />
>     </rmp:RMAssertion>
>   </wsp:All>
>   <wsp:All>
>     <sp:AsymmetricBinding
>         
> xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy" >
>       <wsp:Policy>
>         <!-- Details omitted for readability -->
>         <sp:IncludeTimestamp />
>         <sp:OnlySignEntireHeadersAndBody />
>       </wsp:Policy>
>     </sp:AsymmetricBinding>
>   </wsp:All>
> </wsp:Policy>
> 
> The above policy expression is equivalent to Example 3.1 in 
> Section 3.3 [1]. If the above policy expression is easier to 
> read then +1.

Yes, that is the form I am looking for and this will eliminate the confusion. The example is not about readibility, it is about following what the "merging" algorithm dictates as I quoted: 

{...replacing their wsp:Policy element with a 
> wsp:All element, and placing each as children of a wrapper 
> wsp:Policy element.}

The expressions may be equivalent, but we do not have any algorithm to convert the form you have quoted to the so called equivalent form as stated in the example, because the example is not about normalization and does not follow the normalization either. We do not have a reverse normalization algorithm where the wsp:All elements are removed. 

The example is about merging. The reader expects to see what the merging algorithm tells us to do, namely encapsulating the expressions with wsp:All. Our examples should not be confusing.  

Lets go ahead and replace the example. 

> 
> [1] 
> http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117/#XMLEle
> mentAttachement 
> 
> Regards,
>  
> Asir S Vedamuthu
> Microsoft Corporation
> 
> 

--umit

> 
> 
> 
> 
> From: public-ws-policy-request@w3.org 
> [mailto:public-ws-policy-request@w3.org] On Behalf Of Yalcinalp, Umit
> Sent: Friday, January 12, 2007 3:52 PM
> To: public-ws-policy@w3.org
> Subject: NEW ISSUE: Example 3.1 does not follow the 
> algorithm/definition in merging policies
> 
> 
> Title: Example 3.1 does not follow the algorithm in merging policies 
> Description: The example 3.1 claims to be result of merging. 
> The merge is defined to be 
> { 
> Definition: a merge consists of serializing each policy as a 
> policy expression, replacing their wsp:Policy element with a 
> wsp:All element, and placing each as children of a wrapper 
> wsp:Policy element.] The resulting policy expression is 
> considered to represent the combined policy of all of the 
> attachments to that policy subject.
> } 
> The resulting example does not contain any replacement of 
> wsp:All elements with a wsp:Policy element and does not 
> follow the definition. 
> Justification: The example is confusing and does not follow 
> the description of the merge. 
> Proposal: Fix the example to reflect the merge algorithms 
> intent by introducing wsp:All as appropriate wrappers. 
> This is also files as [Issue 4209]. 
> [Issue 4209] 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=4209 
> ---------------------- 
> Dr. Umit Yalcinalp 
> Research Scientist 
> SAP Labs, LLC 
> Email: umit.yalcinalp@sap.com Tel: (650) 320-3095 
> SDN: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/36238 
> -------- 
> "Nearly all men can stand adversity, but if you want to test 
> a man's character, give him power." Abraham Lincoln. 
> 
>

Received on Monday, 15 January 2007 16:51:40 UTC