W3C home > Mailing lists > Public > public-ws-addressing@w3.org > January 2005

Re: xml:id and opacity of refp's

From: Francisco Curbera <curbera@us.ibm.com>
Date: Thu, 6 Jan 2005 10:48:50 -0500
To: Rich Salz <rsalz@datapower.com>
Cc: Marc Hadley <Marc.Hadley@Sun.COM>, "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>, public-ws-addressing-request@w3.org
Message-ID: <OF904A41CA.E5CF2BE5-ON85256F81.0055A6B6-85256F81.0056DE4C@us.ibm.com>

Rich, Mark,

Sorry I was not clear. The idea is that if a requester starts making
assumptions about what's inside the runtime EPR information (URI+ref. p.)
it may create a dependency on that specific EPR that may not hold if the
service needs to reissue or update the EPR for that requester. The result
is that the requester app will not be able to access the server with the
updated EPR. I think this is the key point to stress because it protects
the ability of the requester to reach the service in the presence of EPR

As long as that principle is clear, I see no risk in assuming that
requesters may be looking into the EPR to avoid conflicts with ID values,
building EPR "encoding schemes" (similar to URI encoding schemes), or the


|         |           Rich Salz               |
|         |           <rsalz@datapower.com>   |
|         |           Sent by:                |
|         |           public-ws-addressing-req|
|         |           uest@w3.org             |
|         |                                   |
|         |                                   |
|         |           01/05/2005 07:36 PM     |
  |                                                                                                                                     |
  |       To:       Marc Hadley <Marc.Hadley@Sun.COM>                                                                                   |
  |       cc:       Francisco Curbera/Watson/IBM@IBMUS, "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>                     |
  |       Subject:  Re: xml:id and opacity of refp's                                                                                    |

> >  Opaqueness as an operating principle is important to protect
> > service requester interoperability.

Why?  I mean, what's the technical reason for this?


Rich Salz                  Chief Security Architect
DataPower Technology       http://www.datapower.com
XS40 XML Security Gateway  http://www.datapower.com/products/xs40.html
XML Security Overview      http://www.datapower.com/xmldev/xmlsecurity.html
Received on Thursday, 6 January 2005 15:49:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:08 UTC