   From: Sergey Beryozkin <sberyozkin@zandar.com> Date: Wed, 7
May 2003 10:13:49 +0100 Message-ID:
<007301c31478$f923f460$1800a8c0@BERYOZKIN> To: "Arthur Ryman"
<ryman@ca.ibm.com> I spent some time yesterday trying to find a
case for a dynamic binding discovery, as related to R085. IMHO,
there're two possible approaches : 1. The endpoint reference [1]
returns an absolute URI handle (I'm borrowing the term from the
Grid OGSA spec - can't get the link for some reasons, sorry),
rather than an endpoint address. This means that the runtime
needs to query it for a WSDL from which it can get an address
and a binding. This bring more complexity on the client part.
The advantage is that a resource can be made accessible at
different endpoints over time; however, the same can be achieved
with [1], where  the endpoint reference can return different
addresses over time. 2. The endpoint reference [1] returns an
address (might be relative), as defined by [1], but there's no
statically available binding (if it's available,