W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2001

Re: Encoding XML in URIs

From: Mark Baker <distobj@acm.org>
Date: Wed, 5 Sep 2001 23:51:32 -0400 (EDT)
Message-Id: <200109060351.XAA15572@markbaker.ca>
To: mnot@mnot.net (Mark Nottingham)
Cc: paulp@ActiveState.com (Paul Prescod), xml-dist-app@w3.org (XML Distributed Applications List)

Sorry for not contributing to this discussion earlier, but I was on
vacation and just now got caught up.

I think the discussion of encoding XML documents in a URI is missing
the point of the issue Hugo brought up in [1], about ensuring that

One way to look at this problem is that for an RPC or tunneled use
of SOAP over HTTP, the architecture of the Web is already being
disregarded.  I'm not sure why that one GET "axiom" should be
special, because so many other principles aren't being adherred to.
For example, from Tim's axioms 0a ("Universality 2")[2], and
arguably 1 ("Global Scope")[3].

For a binding of SOAP to HTTP that *does* respect principles of web
architecture, that axiom still holds, but needs no additional
consideration (in the binding) as it is up to the app developer to
obey it or not.

Once again I refer to the example in my "Soap Uses" note[4].  There,
GET is used in conjunction with SOAP.  Because the example follows
all principles of web architecture that I know about, it's also
entirely seemless.

 [1] http://lists.w3.org/Archives/Public/xml-dist-app/2001Aug/0202.html
 [2] http://www.w3.org/DesignIssues/Axioms.html#Universal
 [3] http://www.w3.org/DesignIssues/Axioms.html#unique
 [4] http://www.markbaker.ca/2001/07/SoapUses/

Received on Wednesday, 5 September 2001 23:50:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:15 UTC