New issue; WS-Addressing SOAP binding & app protocols

Hello TAG,

I attempted to raise[1] an issue with the WS Addressing WG recently,
regarding what I felt to be a serious architectural flaw with the
WS-Addressing SOAP binding[2].  In a nutshell, it requires that the URI
in the "Address" component of a WS-Addressing EPR be serialized into a
wsa:To SOAP header, independent of the underlying protocol.  IMO, a
Web-architecture consistent means of doing this would be to serialize it
to the Request-URI when using SOAP with HTTP, or the "RCPT TO:" value
when using SOAP with SMTP, etc...  Unfortunately, the WG disagreed with
me that this was a problem, and declined[3] to accept it as an issue.

I believe the reasoning that was given for the issue being declined
was flawed.  It claimed that additional bindings could be defined, which
is true, but does nothing to address the issue with the SOAP binding and
its suitability for use with application protocols (indeed, one possible
resolution would be to claim that it should only be used with transport
protocols).  But it's clear to me that the status quo with the SOAP
binding is inconsistent with the architecture of the Web (and the
Internet too), so I respectfully request that the TAG consider this as a
new issue.

Thanks!  And Happy New Year to all.


Mark Baker.   Ottawa, Ontario, CANADA.

Received on Monday, 3 January 2005 05:04:11 UTC