- From: Doug Davis <dug@us.ibm.com>
- Date: Wed, 15 Dec 2004 09:22:56 -0500
- To: Rich Salz <rsalz@datapower.com>
- Cc: Hugo Haas <hugo@w3.org>, "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>
- Message-ID: <OFB242E557.97E05BB3-ON85256F6B.004D8991-85256F6B.004F0180@us.ibm.com>
But then what the point of the comparison assertion then? If anything could influence it, even the time of day, then WSA's claim about their equality is really meaningless - isn't it? It seems that the metadata itself must be retrieved for the two EPR (and in their proper context) and then that metadata itself compared. Perhaps the current (or suggested) text would make more sense if I understood the use-case it was addressing (no pun intended :-) - does anyone have that? And, if, as you suggest, its the application's job to take them all into account then the spec should probably say that since as written it implies that a simple EPR comparison is enough to draw some very broad conclusions. -Dug Rich Salz <rsalz@datapower.com> Sent by: public-ws-addressing-request@w3.org 12/15/2004 09:04 AM To Doug Davis/Raleigh/IBM@IBMUS cc Hugo Haas <hugo@w3.org>, "public-ws-addressing@w3.org" <public-ws-addressing@w3.org> Subject Re: i014 - Metadata Update/Reconciliation: a proposal > It seems to me that there are lots of factors that may > influence the metadata associated with an EPR and WSA can't possibly take > them all into account. WSA doesn't take them all into account; it requires the application(s) involved to take them all into account. That may be an undue burden. Or not: does "we're the same server" mean "we'll always answer the same to everyone"? Of course not. /r$ -- 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 Wednesday, 15 December 2004 14:23:31 UTC