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

RE: i0001: EPRs as identifiers - alternative proposal

From: Francisco Curbera <curbera@us.ibm.com>
Date: Sun, 5 Dec 2004 23:04:47 -0500
To: <paul.downey@bt.com>
Cc: mpeel@novell.com, public-ws-addressing@w3.org, public-ws-addressing-request@w3.org
Message-ID: <OF87671594.F985B270-ON85256F62.0015F691-85256F62.0016691D@us.ibm.com>

Hi Paul,

I am trying to say (with limited success it seems) that EPRs are service
endpoint addresses, and that it is often the case that from the address the
identifier may be inferred. That does not make the address an identifier. I
believe that we are agreeing here, unless I am missing something.

BTW, "Come alone" is a great example embedded policy :-)


                      Sent by:                        To:       Francisco Curbera/Watson/IBM@IBMUS, <mpeel@novell.com>                         
                      public-ws-addressing-req        cc:       <public-ws-addressing@w3.org>                                                  
                      uest@w3.org                     Subject:  RE: i0001: EPRs as identifiers - alternative proposal                          
                      12/03/2004 08:52 AM                                                                                                      

Paco wrote:

> Even for the hosting system, it is different to
> say that the EPR is the identifier from saying that
> it can be used to find out the identifier.

Seems to me you're saying that an EPR isn't an identifier,
or an even an address from which identity might be inferred.

It's a set of directions: put the message in the waste
paper basket by the most southerly entrance in Hyde park.
Come alone.

Received on Monday, 6 December 2004 04:05:21 UTC

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