RE: NEW ISSUE: EPR comparison rule doesn't support Web services gateways/routers

<snip />

> 
> Metadata such as WSDL and Policy surrounding endpoints *may*, or
indeed
> *may not* differ for a whole host of different reasons, including
having
> more than one description mechanism for an endpoint, other
interactions
> which may have taken place, username being used, content negotiation,
> out of band data, etc, etc. Therefore this sentence is at best
redundant,
> worst misleading.
> 
> As with the EPR life cycle, we should push how EPRs and any
surrounding
> meta-data may be employed, compared and cached firmly out of scope and
> in the domain of specs layering upon Addressing.
> 
> So in the absence of a compelling requirement for specifying EPR
> comparison in *this* specification, I feel we should put EPR
comparison
> out of our misery and ditch the whole of section 2.3.
> 

+1

.savas.

Received on Friday, 28 January 2005 21:39:27 UTC