+1 for Jonathan's proposal. Jonathan Marsh wrote: > I still don't see why a simpler proposal won't work: > > 1) Open the content model to elements and attributes in other > namespaces. > 2) Mark required extensions with a <wsdl:extension namespace="..."/> > element. > 3) An interpreter of the WSDL document, encountering an element or > attribute marked as a required extension but not recognizing the > namespace of that element, must interpret the entire WSDL document as > "not understood". > 4) Certain elements can accept "architected extensions" which means they > don't have to be declared using the extension mechanism. These are not > really extensions at all, just boundaries between embedded namespaces.Received on Wednesday, 22 May 2002 12:09:09 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:23 UTC