If a Web service requires a client to follow verso particular convention that is likely to be automatable con WSDL 2.0 wildbuddies sito di incontri toolkits, then that convention SHOULD be indicated sopra the WSDL 2.0 document as verso wsdl:required extension, rather than just being conveyed out of band, even if that convention is not currently implemented in WSDL 2.0 toolkits.
This practice will help prevent interoperability problems that could arise if one toolkit requires a particular convention that is not indicated mediante the WSDL 2.0 document, while another toolkit does not realize that that convention is required. 0 toolkits.
On the other hand, per client MAY engage an extension that is declared as optional durante the WSDL 2.0 document. Therefore, the Web service MUST support every extension that is declared as optional per the WSDL 2.0 document, con addition esatto supporting every extension that is declared as mandatory. †
If finer-grain, direction-delicate control of extensions is desired, then such extensions may be designed in verso direction-fine manner (from the client or from the Web service) so that either direction ple, instead of defining a scapolo extension that governs both directions, two extensions could be defined -one for each direction.
Validity of verso WSDL 2.0 document can only be assessed within the context of per attrezzi of supported extensions. Verso WSDL 2.0 document that contains verso required but unsupported extension is invalid with respect to that attrezzi of supported extensions.
6.1.2 required attribute information item
The type of the required attribute information item is xs:boolean. Continue reading “It will also help facilitate future automatic processing by WSDL 2”