OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsn message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsn] Interesting line in the WS-A charter


Ugo Corda wrote:
Message
This is essentially the same discussion taking place right now within the WS-Address WG (see http://lists.w3.org/Archives/Public/public-ws-addressing/2005Jan/thread.html, the thread "NEW ISSUE: EPR comparison rule doesn't support Web services gateways/routers").
Right.  The interesting points (to me) are that WSA got this far without running up against this charter-driven issue, and that this seems to make it all the more likely that refprops will get dropped.  I don't want to devote a lot of bandwidth to this here.  As you pointed out, this may not impact us very much.  This is more just a followup to my previous post on WSA and refprops.  Sorry I wasn't more clear.
 
Ugo
-----Original Message-----
From: David Hull [mailto:dmh@tibco.com]
Sent: Thursday, January 27, 2005 1:47 PM
To: wsn-oasis
Subject: [wsn] Interesting line in the WS-A charter

Note: the Architecture of the World Wide Web, First Edition indicates that distinct resources must be assigned to distinct URIs. This must be considered when refining the mechanism for the service specific message headers.
Read strictly, this would indicate that using reference parameters to further refine an endpoint reference is a no-no.  Read loosely, it's a no-op since we can presumably fudge on what constitutes an "endpoint" as opposed to a "resource"

As noted before, it's not clear what impact, if any, this may have on WSRF/WSN, but it seemed interesting.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]