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

Re: Extensions

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Tue, 28 May 2002 09:42:05 +0600
Message-ID: <004301c205f9$d0172ad0$c267b809@lankabook2>
To: "Jeffrey Schlimmer" <jeffsch@windows.microsoft.com>, "WS-Desc WG \(Public\)" <www-ws-desc@w3.org>
Hi Jeffrey,

Your table has too many cells for my liking! It looks like an
interop nightmare is being created ..

Why don't we go with the simpler model ala WSDL 1.1 for
requiredness? You get per-element "gotta have it" capability
and that's it. If needed we can put an ed note in the working
draft saying we're considering adding more flexibility and
see whether we get feedback asking for it.


----- Original Message ----- 
From: "Jeffrey Schlimmer" <jeffsch@windows.microsoft.com>
To: "WS-Desc WG (Public)" <www-ws-desc@w3.org>
Sent: Friday, May 24, 2002 4:57 AM
Subject: Extensions

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

Received on Monday, 27 May 2002 23:43:54 UTC

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