Section 2.3 in Editors' draft

The section ends with

    Therefore, a consuming application should assume that different XML
    Schemas, WSDL definitions and policies apply to endpoint references
    whose addresses differ.


Shouldn't this properly read (changes italicized):

    Therefore, a consuming application should /not /assume that /the
    same /XML Schemas, WSDL definitions and policies apply to endpoint
    references whose addresses differ.

That is, EPRs with different destination addresses might still happen to 
use the same schemas and WSDL, but we can't assume that.

While we're at it, should "should not" be "MUST NOT"?

Received on Tuesday, 8 February 2005 21:53:46 UTC