i052: What is a logical address?

I find the term "dereference", while possibly accurate to the Web Arch
definition, to be unlikely to clarify things to our general readership.
But perhaps you could dereference jmarsh@microsoft.com with some
additional justification :-).

If we're trying to say something like "a client, through configuration
or other means, MAY choose to use a different value in the underlying
protocol's address field (if one exists) than specified by [address]"
let's just say it.  As is I'm not sure what the proposal is trying to
accomplish.

> -----Original Message-----
> From: public-ws-addressing-request@w3.org [mailto:public-ws-
> addressing-request@w3.org] On Behalf Of Mark Nottingham
> Sent: Tuesday, February 22, 2005 1:46 PM
> To: Anish Karmarkar
> Cc: public-ws-addressing@w3.org
> Subject: Re: NEW ISSUE: What is a logical address?
> 
> 
> This is now issue 052;
>    http://www.w3.org/2002/ws/addr/wd-issues/#i052
> 
> 
> On Feb 21, 2005, at 11:29 AM, Anish Karmarkar wrote:
> 
> >
> > Title:
> > What is a logical address?
> >
> > Description:
> > In the core spec [1], it is stated that the [address] property and
> the
> > wsa:Address EII may be a logical address for the service endpoint.
> > The last published WD [2] described wsa:Address as a 'logical
> address
> > or identifier'. The word 'identifier' was removed in the current ed.
> > draft. I'm not sure if this was an oversight or an effect of
> resolving
> > issue 1.
> >
> > Justification:
> > The core spec uses the term "logical address" without explaining
> what
> > it means. I have been getting some questions from our implementation
> > team as to what a logical address means and how it is used. AFAIK,
> > this is a new term that is being introduced without any explanation
> or
> > definition of the term.
> >
> > Target:
> > Core
> >
> > Proposal:
> > I understand this term to mean that the URI in the [address]
> property
> > identifies the service endpoint. I know this WG has been a little
> shy
> > with the term "identifier", but I don't think there is an issue with
> > using URIs as identifiers -- thats what they are meant for. In
> > resolving issue 1 we have already stated that EPRs are not
> > identifiers, so the next question that comes to mind is -- what is
> it
> > that identifies a service endpoint? In calling the [address]
> property
> > the service endpoint identifier, both the questions of "what is a
> > logical endpoint?" and "how do I identify a service endpoint?" are
> > answered. Using my interpretation of 'logical address', I would like
> > to put forward the following strawman proposal:
> >
> > In section 2.1 --
> >
> > Replace:
> >  [address] : URI (mandatory)
> >     An address URI for the endpoint. This may be a network address
> or a
> >     logical address.
> >
> > with:
> >  [address] : URI (mandatory)
> >     An address URI that identifies the service endpoint and may be
> >     deferenceable.
> >
> > In section 2.2 --
> >
> > Replace:
> >  /wsa:EndpointReference/wsa:Address
> >     This REQUIRED element (of type xs:anyURI) specifies the
> [address]
> >     property of the endpoint reference. This address may be a
> logical
> >     address for the service endpoint.
> >
> > with:
> >  /wsa:EndpointReference/wsa:Address
> >     This REQUIRED element (of type xs:anyURI) specifies the
> [address]
> >     property of the endpoint reference. This address identifies the
> >     service endpoint and may be dereferenceable.
> >
> >
> > This is only a strawman, so please do send suggestion for changes.
> >
> > -Anish
> > --
> >
> > [1]
> > http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-
> > core.html
> > [2] http://www.w3.org/TR/2004/WD-ws-addr-core-20041208/
> >
> >
> 
> --
> Mark Nottingham   Principal Technologist
> Office of the CTO   BEA Systems
>

Received on Thursday, 24 February 2005 01:35:53 UTC