- From: Mark Baker <distobj@acm.org>
- Date: Tue, 22 Feb 2005 07:14:08 -0500
- To: public-ws-addressing@w3.org
Ah, thanks Paul. I actually did look for a definition of "endpoint", only searching on the word alone seemed to yield a lot of false positives. 8-) FWIW, I'm not sure what role "entity, processor" serve in that definition, since both are specific kinds of resources. Would it not just be more succinct to remove them and say; "A Web service endpoint is a (referenceable) resource to which Web service messages can be addressed. Endpoint references convey the information needed to address a Web service endpoint." But +1 on Anish's proposal. Mark. On Tue, Feb 22, 2005 at 07:49:51AM -0000, paul.downey@bt.com wrote: > And our spec says: > > """ A Web service endpoint is a (referenceable) entity, processor, or resource to which Web service messages can be addressed. Endpoint references convey the information needed to address a Web service endpoint. """ > > http://www.w3.org/TR/2005/WD-ws-addr-core-20050215/ > > > -----Original Message----- > From: public-ws-addressing-request@w3.org on behalf of Mark Baker > Sent: Tue 22/02/2005 03:45 > To: public-ws-addressing@w3.org > Cc: > Subject: Re: NEW ISSUE: What is a logical address? > > > > > Anish, > > This sounds encouraging, but I'm unclear on what it would mean to say > that the URI identifies the *endpoint*. Would this prevent it from > identifying application layer resources like, say, a customer > account, a business agreement, or an invoice? > > Thanks. > > Mark. > > On Mon, Feb 21, 2005 at 11:29:54AM -0800, Anish Karmarkar wrote: > > with: > > [address] : URI (mandatory) > > An address URI that identifies the service endpoint and may be > > deferenceable. > > > -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
Received on Tuesday, 22 February 2005 12:14:45 UTC