W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

RE: i0001: EPRs as identifiers (why XML?)

From: Vinoski, Stephen <Steve.Vinoski@iona.com>
Date: Wed, 24 Nov 2004 08:53:52 -0500
Message-ID: <13AC4E67178F4D4EA31BB1BA645303132DBE02@amereast-ems2.boston.amer.iona.com>
To: "Rich Salz" <rsalz@datapower.com>
Cc: "Paco Curbera, Francisco" <curbera@us.ibm.com>, <public-ws-addressing@w3.org>

I don't expect this WG to go out of its way to address alternatives beyond XML
and SOAP. However, there's also no reason for this WG to go out of its way to
make things other than XML and SOAP impossible. I can't speak for Paco, but I think that's all that he and I are saying.

I'm all for simplicity, believe me. However, the more I study issue i026, which
is related to this discussion, the more I'm convinced that there are ways to
do it without compromising simplicity or focus. More on that later.

Disagree with the third paragraph, though. We currently do not have or need
complete mappings into and out of SOAP. WSDL can be used without SOAP. Sometimes
our WSDL-based systems have SOAP, sometimes they don't. SOAP is definitely not
some kind of canonical protocol for us, if that's what you're getting at.
We don't need no steenkin' canonical protocol. :-) To us, SOAP is just another
protocol in a series of protocols to come along over the years; some have stuck
around, and some haven't. It remains to be seen which bucket SOAP will fall into,
but the one thing you can be sure of is that a new protocol will come along to
either sit next to or replace SOAP -- it's inevitable. There's no shame or harm
in recognizing that fact.


-----Original Message-----
From: Rich Salz [mailto:rsalz@datapower.com]
Sent: Tuesday, November 23, 2004 7:12 PM
To: Vinoski, Stephen
Cc: Paco Curbera, Francisco; public-ws-addressing@w3.org
Subject: RE: i0001: EPRs as identifiers (why XML?)

In order to use ws-addressing outside of soap, you already have to
	map URI's to your addressing scheme
	map Infoset data to your data scheme
	define a "binding" of ws-addr data to your transports

It would be nice if this WG didn't make the job harder, but W3C Web
Services is about XML and SOAP, and other systems deserve courtesy, but
are most definitely second-class citizens.

You've already must have a complete mapping into and out of SOAP; to the
extent that WS-Addressing ties itself closer to SOAP, as opposed to being
a special case, then we've arguably made your job easier.

Rich Salz                  Chief Security Architect
DataPower Technology       http://www.datapower.com
XS40 XML Security Gateway  http://www.datapower.com/products/xs40.html
XML Security Overview      http://www.datapower.com/xmldev/xmlsecurity.html
Received on Wednesday, 24 November 2004 13:54:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:28:21 UTC