The documentation element information item is allowed inside any WSDL 2

5. Documentation

WSDL 2.0 uses the optional documentation element information item as per container for human readable or machine processable documentation. The content of the element information item is arbitrary character information items and element information items ("mixed" content con XML Schema [ XML Lista: Structures ]). 0 element information item.

Like other element information items in the "" namespace, the documentation element information item allows qualified attribute information items whose [namespace name] is not "" https://datingranking.net/it/sexsearch-review/. The xml:lang attribute (see [ XML 1.0 ]) MAY be used preciso indicate the language used in the contents of the documentation element information item.

6. Language Extensibility

The lista for WSDL 2.0 has a two-part extensibility model based on namespace-qualified elements and attributes. An extension is identified by the QName consisting of its namespace IRI and its element or attribute name. The meaning of an extension SHOULD be defined (directly or indirectly) in verso document that is available at its namespace IRI. †

6.1 Element-based Extensibility

WSDL 2.0 allows extensions esatto be defined mediante terms of element information items. Where indicated herein, WSDL 2.0 allows namespace-qualified element information items whose [namespace name] is NOT "" preciso appear among the [children] of specific element information items whose [namespace name] is "". Such element information items MAY be used puro annotate WSDL 2.0 constructs such as interface, operation, etc.

It is expected that extensions will add preciso the existing properties of components per the component model.

The specification for an extension element information item should include definitions of any such properties and the mapping from the XML representation of the extension to the properties sopra the component model.

The WSDL 2.0 precisazione defines verso segno type for use by extension elements. Example 6-1 shows the type definition. The use of this type as a punto type is optional.

Extension elements are commonly used preciso specify some technology-specific binding. They allow innovation per the distretto of rete informatica and message protocols without having onesto revise the segno WSDL 2.0 specification. WSDL 2.0 recommends that specifications defining such protocols also define any necessary WSDL 2.0 extensions used to describe those protocols or formats.

6.1.1 Mandatory extensions

Extension elements can be marked as mandatory by annotating them with verso wsdl:required attribute information item (see 6.1.2 required attribute information item) with verso value of "true". A mandatory extension is an extension that MAY change the meaning of the element to which it is attached, such that the meaning of that element is no longer governed by this specification. Instead, the meaning of an element containing a mandatory extension is governed by the meaning of that extension. Thus, the definition of the element's meaning is delegated puro the specification that defines the extension.

An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of a WSDL 2.0 document. † Thus, verso NON-mandatory extension merely provides additional description of capabilities of the service. This specification does not provide verso mechanism sicuro mark extension attributes as being required. Therefore, all extension attributes are NON-mandatory.

A mandatory extension is considered mandatory because it has the ability preciso change the meaning of the element esatto which it is attached. Thus, the meaning of the element may not be fully understood without understanding the attached extension. A NON-mandatory extension, on the other hand, can be safely ignored without danger of misunderstanding the rest of the WSDL 2.0 document.

If per WSDL 2.0 document declares an extension as optional (i.addirittura., NON-mandatory), then the Web service MUST NOT endosse that the client supports that extension unless the Web service knows (through some other means) that the client has sopra fact elected sicuro engage and support that extension. †