- From: Yves Lafon <ylafon@w3.org>
- Date: Fri, 10 Apr 2009 15:33:35 -0400 (EDT)
- To: Bob Freund <bob@freunds.com>
- cc: David Snelling <David.Snelling@UK.Fujitsu.com>, Gilbert Pilz <gilbert.pilz@oracle.com>, Asir Vedamuthu <asirveda@microsoft.com>, Doug Davis <dug@us.ibm.com>, "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
On Thu, 9 Apr 2009, Bob Freund wrote:
> Would it be too bold to suggest folks consider to move NotifyTo to be a child
> of Subscribe?
> that way, then Delivery could be used (as an xs:Any) extension point, used by
> other specifications to mean anything they want at at cost of merely setting
> a SOAP mU header on delivery to get the fault behavior. Of course, the fault
> would change from modeNotRecognized to SOAP mU Fault, but the other stuff
> would still work.
> Is that half-way-ish approach that folks could consider?
I am wondering if the outcome of this is to allow two incompatible ways of
doing roughly the same thing in the same specification; and my question
is... what is the story for interoperability?
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Friday, 10 April 2009 19:33:45 UTC