- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Mon, 31 Jan 2005 09:38:19 -0800
- To: <public-ws-addressing@w3.org>
I have an action to "flesh out proposal for comparison of URIs, and ask whether destination should be included in the list." 3.1.1 Comparing URIs The values of the Message Addressing Properties [action], [message id], and [relationship] are absolute URIs. The purpose of these URIs is primarily identification, rather than resource retrieval. As such, simple string comparison as indicated in [Internationalized Resource Identifiers (IRIs)] Section 5.3.1 is sufficient to determine equivalence the URIs. Enhancement 1: Add [destination] to the above list of properties. Is [destination] used primarily for identification, or does it also serve at the transport level, in which case simple string comparison might not be appropriate in some circumstances. Enhancement 2: There is also the [address] property in the EPRs. If we add [destination], does it also make sense to prescribe similar treatment for [address]? > -----Original Message----- > From: Mark Nottingham [mailto:mark.nottingham@bea.com] > Sent: Thursday, January 20, 2005 7:07 PM > To: Jonathan Marsh > Cc: public-ws-addressing@w3.org > Subject: Re: NEW ISSUE: Comparison of URIs used as identifiers. [i046] > > This is now issue i046; > http://www.w3.org/2002/ws/addr/wd-issues/#i046 > > > On Jan 15, 2005, at 8:31 AM, Jonathan Marsh wrote: > > > > > Several of the URIs defined by WS-Addressing are used primarily for > > identification rather than primarily dereferencing: [message id], > > [relationship], and [action]. In other specifications, how to > compare > > values of these properties is usually defined. WS-Addressing would > > benefit from a section like this as well. > > > > I propose we essentially copy the WSDL 2.0 section on this into the > > WS-A > > spec: > > http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html? > > cont > > ent-type=text/html;%20charset=utf-8#uricompare > > > > > > > > > > -- > Mark Nottingham Principal Technologist > Office of the CTO BEA Systems
Received on Monday, 31 January 2005 17:38:51 UTC