W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2002

Text for extensibility section

From: Glen Daniels <gdaniels@macromedia.com>
Date: Tue, 11 Jun 2002 09:10:52 +0200
Message-ID: <000d01c21117$200147b0$5002010a@MINIME>
To: <www-ws-desc@w3.org>

This is the text I came up with per yesterday's F2F discussion... comments



Any extension element may appear as an immediate child of an element in the
wsdl namespace.  Such an extension element is said to be processed if the WSDL
processor decides (through whatever means) that the parent wsdl-namespaced
element will be processed.  Note that it is possible for WSDL readers to
process only a subset of a given WSDL document.  For instance, a tool may wish
to focus on portTypes and operations only, with no need to examine bindings.

If an extension element is processed, and has a "wsdl:required" attribute with
the value "true", the processor MUST either agree to fully abide by all the
rules and semantics signalled by the extension element's QName, or immediately
cease processing (fault).  In particular, if the processor does not recognize
the QName it must fault.  If it does recognize the QName, and determines that
the extension in question is incompatible with any other aspect of the document
(including other extensions), it must also fault.

[ the first version of this text contained a sentence indicating that a
processor must "pre-determine" all extensions which would be processed for a
given document, and ensure that the combination of processed + required
extensions was understood in concert before proceeding, but after further
thought, I think it may be up to the processor to decide whether this sort of
thing is necessary.  Presumably, a given extension specification will indicate
whatever rules must be followed, including any changes to "normal" WSDL
processing ]
Received on Tuesday, 11 June 2002 03:11:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:23 UTC