- From: Srinivas, Davanum M <Davanum.Srinivas@ca.com>
- Date: Fri, 3 Dec 2004 12:24:50 -0500
- To: "Mark Baker" <distobj@acm.org>, "David Orchard" <dorchard@bea.com>
- Cc: <public-ws-addressing@w3.org>
First I was going to tell Mark that what about SOAP over JMS? Then I remembered the jms url proposal from sonic folks. See [1] and [2] for the proposals. [3] for discussion. [1] http://marc.theaimsgroup.com/?l=axis-dev&m=105613809524476&q=p3 [2] http://marc.theaimsgroup.com/?l=axis-dev&m=103617964921940&q=p3 [3] http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=jms+url+syntax&q=b -- dims -----Original Message----- From: public-ws-addressing-request@w3.org [mailto:public-ws-addressing-request@w3.org] On Behalf Of Mark Baker Sent: Friday, December 03, 2004 11:42 AM To: David Orchard Cc: public-ws-addressing@w3.org Subject: Re: i0001: EPRs as identifiers - alternative proposal On Fri, Dec 03, 2004 at 08:01:30AM -0800, David Orchard wrote: > +1. URIs have infinite scale, see cantor's theorem. +1 > The reason for having RefPs has nothing to do with URI extensibility. > It has everything to do with configurability particularly having soap > specific software handle the RefP rather than URI software. That seems to implicitly assume that SOAP specific software isn't URI software. Perhaps that's the heart of the disagreement? So, I'll bite; why can't SOAP software also be URI software? Because one could reasonably interpret webarch as saying that it *should be*, at least if you want to benefit from the network effects of a global naming system, yada yada yada ... But if your answer would head back down that same rathole, then nevermind; I'll have to wait for the motivating example, I guess. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
Received on Friday, 3 December 2004 17:24:53 UTC