W3C home > Mailing lists > Public > public-ws-addressing@w3.org > May 2007

Re: Examples to Resolve Issue LC136

From: David Hull <dmh@tibco.com>
Date: Mon, 21 May 2007 09:28:56 -0400
Message-ID: <46519E98.8080300@tibco.com>
To: tom@coastin.com
CC: WS-Addressing <public-ws-addressing@w3.org>
A small update:  In view of WSP's recent clarification on sets vs. bags,
it appears that the intersected policies should look like

<wsp:Policy>
    <wsp:ExactlyOne>
        <wsp:All> <--requires addr and nonAnon jabber responses-->
            <wsam:Addressing> <-  requires nonAnonymous responses -->
                <wsp:Policy>
                    <wsp:ExactlyOne>
                        <wsp:All>
                            <NonAnonymousResponses />
                        </wsp:All>
                    </wsp:ExactlyOne>
                </wsp:Policy>
            </wsam:Addressing>
            <wstr:jabber/> <-- requires response in jabber request-->
            <wsam:Addressing> <-  requires nonAnonymous responses -->
                <wsp:Policy>
                    <wsp:ExactlyOne>
                        <wsp:All>
                            <NonAnonymousResponses />
                        </wsp:All>
                    </wsp:ExactlyOne>
                </wsp:Policy>
            </wsam:Addressing>
            <wstr:jabber/> <-- requires response in jabber request-->
        </wsp:All>
    </wsp:ExactlyOne>
</wsp:Policy>

i.e., with each assertion appearing twice.

I'm not sure what difference, if any, this might make.

Tom Rutt wrote:
> This body part will be downloaded on demand.
Received on Monday, 21 May 2007 13:29:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:19 GMT