RE: [ws-rx] compromise proposal for I122-124

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Although I understand it may not be easier to get an agreement on this
in RSP WG, that sounds to me more relevant of its charter... 

The requirement in WS-RX charter to be "composable" with WSS and others
does not mean having to fully specify a composition solution in this
specification (I mean, where do we stop on that path w/r to other
RM-composable specs?)

-Jacques

-----Original Message-----
From: Bob Freund-Hitachi [mailto:bob.freund@hitachisoftware.com] 
Sent: Thursday, July 13, 2006 1:01 PM
To: tom@coastin.com; wsrx
Subject: RE: [ws-rx] compromise proposal for I122-124

And leave interop to the ws-I rsp WG?
I hope not.
-bob

-----Original Message-----
From: Tom Rutt [mailto:tom@coastin.com] 
Sent: Thursday, July 13, 2006 3:45 PM
To: wsrx
Subject: [ws-rx] compromise proposal for I122-124

Just a thought.

What if we define the two high level soap header elements
sequenceSTR
sequenceSSL

Add the text from gil, and leave the way the str is bound to the 
sequence to be outside the WSRM spec.

That is, do not specifiy either the Oracle or Microsoft way to confey 
the STR.

Tom Rutt

-- 
----------------------------------------------------
Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133