This section describes the conceptual model of WSDL 2

0 as per arnesi of components with attached properties, which collectively describe verso Web service. This model is called the Component Model of WSDL 2.0. Verso valid WSDL 2.0 component model is a set of WSDL 2.0 components and properties that satisfy all the requirements given mediante this specification as indicated by keywords whose interpretation is defined by RFC 2119 [ IETF RFC 2119 ].

Components are typed collections of properties that correspond preciso different aspects of Web services. Each subsection herein describes per different type of component, its defined properties, and its representation as an XML Infoset [ XML Information Servizio ].

Properties are unordered and unique with respect onesto the component they are associated with. Individual properties’ definitions may constrain their content (e.g., puro a typed value, another component, or per arnesi of typed values or components), and components may require the presence of verso property to be considered conformant. Such properties are marked as REQUIRED, whereas those that are not required to be present are marked as OPTIONAL. By convention, when specifying the mapping rules from the XML Infoset representation of per component to the component itself, an optional property that is absent con the component durante question is described as being “empty”. Unless otherwise specified, when verso property is identified as being per collection (verso set or verso list), its value may be verso 0-element (empty) collection. Mediante order preciso simplify the presentation of the rules that deal with sets of components, for all OPTIONAL properties whose type is per arnesi, the absence of such verso property from per component MUST be treated as semantically equivalent puro the presence of a property with the same name and whose value is the empty arnesi. Con other words, every OPTIONAL servizio-valued property MUST be assumed preciso have the empty set as its default value, to be used con case the property is absent.

Component definitions are serializable per XML 1.0 format but are independent of any particular serialization of the component model. Component definitions use per subset (see 2.14 XML Schema 1.0 Simple Types Used mediante the Component Model) of the simple types defined by the XML Specifica 1.0 specification [ XML Specifica: Datatypes ].

Per accessit esatto the direct XML Infoset representation described here, the component model allows components external preciso the Infoset through the mechanisms described per 4. Modularizing WSDL 2.0 descriptions.

2.1 Description

Verso component model can come funziona swapfinder be extracted from verso given XML Infoset which conforms to the XML Precisazione for WSDL 2.0 by recursively mapping Information Items esatto their identified components, starting with the wsdl:description element information item. This includes the application of the mechanisms described in 4. Modularizing WSDL 2.0 descriptions.

This document does not specify verso means of producing an XML Infoset representation from per component model instance. Durante particular, there are sopra general many valid ways esatto modularize a given component model instance into one or more XML Infosets.

2.1.1 The Description Component

At verso high level, the Description component is just verso container for two categories of components: WSDL 2.0 components and type system components.

Type system components describe the constraints on verso message’s content. By default, these constraints are expressed per terms of the [ XML Information Batteria ], i.di nuovo. they define the [local name], [namespace name], [children] and [attributes] properties of an element information item. Type systems based upon other tempo models are generally accommodated by extensions sicuro WSDL 2.0; see 6. Language Extensibility. In the case where they define information equivalent puro that of a XML Lista global element declaration, they can be treated as if they were such a declaration.