This section describes the conceptual model of WSDL 2

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

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

Properties are unordered and unique with respect preciso the component they are associated with. Individual properties’ definitions may constrain their content (ed.g., sicuro a typed value, another component, or per batteria 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 a component puro the component itself, an optional property that is absent mediante the component durante question is described as being “empty”. Unless otherwise specified, when per property is identified as being verso collection (per serie or a list), its value may be a 0-element (empty) collection. In order onesto simplify the presentation of the rules that deal with sets of components, for all OPTIONAL properties whose type is per servizio, the absence of such a property from verso component MUST be treated as semantically equivalent to the presence of verso property with the same name and whose value is the empty serie. Con other words, every OPTIONAL servizio-valued property MUST be assumed esatto have the empty attrezzi as its default value, onesto be used in case the property is absent.

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

Con addenda preciso the direct XML Infoset representation described here, the component model allows components external puro the Infoset through the mechanisms described per 4. Modularizing WSDL 2.0 descriptions.

2.1 Description

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

This document does not specify verso means of producing an XML Infoset representation from a component model instance. Durante particular, there are mediante general many valid ways to 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 a container for two categories of components: WSDL 2.0 components and type system components.

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