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

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

From: Asir Vedamuthu <asirveda@microsoft.com>
Date: Sat, 13 Jan 2007 02:24:37 -0800
Message-ID: <1E0F0378382054439F14D5450650478F0BFD785A@RED-MSG-42.redmond.corp.microsoft.com>
To: "Yalcinalp, Umit" <umit.yalcinalp@sap.com>, <public-ws-policy@w3.org>

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

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

Regards,
 
Asir S Vedamuthu
Microsoft Corporation






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 Saturday, 13 January 2007 10:27:03 GMT

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