Re: is the uniqueness constraint on top level components sufficient?

Hi Gudge,

> I think you will find that as far as our spec is concerned there is
> always EXACTLY ONE definitions container even in cases where the
> contents of that container came from multiple locations.

That's for included or imported stuff right? Is there anything
in the spec which says that *all* stuff for the target namespace
are part of EXACTLY ONE definitions container? If so then we're
in business. If not its certainly possible for two documents 
to point to the same namespace yet not be aware of each other:

<definitions targetNamespace="">
   ... stuff for one service ...

<definitions targetNamespace="">
   ... stuff for another service ...


Received on Friday, 19 September 2003 14:21:14 UTC