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

Extensions

From: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
Date: Thu, 23 May 2002 15:57:11 -0700
Message-ID: <2E33960095B58E40A4D3345AB9F65EC1075E9D95@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
To: "WS-Desc WG (Public)" <www-ws-desc@w3.org>
Roberto, thank you for patiently explaining the current proposal during
the teleconference this morning.

Just to make sure I understand the proposal, can it be accurately
restated as?

-----

A WSDL parser MUST recognize a foreign EII if and only if one of the
following is true:

(a) The foreign EII has a wsdl:required AII that is true, or

(b) The foreign EII namespace is declared with a wsdl:extension EII,
that EII has a wsdl:required AII that is true, and the foreign EII does
not have a wsdl:required AII.

-----

(a) is what we have in WSDL 1.1 today. (b) adds the global declaration
but allows a wsdl:required AII on the foreign element to override the
global declaration.

Attached is a table that I crunched down to the two rules above.

For completeness, let's allow AII extensions via (something like)
<xs:anyAttribute namespace="#other" processContents="#lax"/>.

Of course, because the wsdl:required AII cannot be attached to a
(foreign) AII, only the global setting in the wsdl:extension EII can be
used to indicate whether a WSDL parser MUST or MAY recognize such an
AII.

--Jeff


Received on Thursday, 23 May 2002 18:57:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:20 GMT