0 as verso batteria 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 per servizio of WSDL 2.0 components and properties that satisfy all the requirements given in this specification as indicated by keywords whose interpretation is defined by RFC 2119 [ IETF RFC 2119 ].

Components are typed collections of properties that correspond to 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 Set ].

Properties are unordered and unique with respect to the component they are associated with. Individual properties’ definitions may constrain their content (ancora.g., preciso per typed value, another component, or verso 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 a component puro the component itself, an optional property that is absent sopra the component in question is described as being “empty”. Unless otherwise specified, when per property is identified as being per collection (verso set or per list), its value may be a 0-element (empty) collection. Con order preciso simplify the presentation of the rules that deal with sets of components, for all OPTIONAL properties whose type is a serie, the absence of such verso property from a component MUST be treated as semantically equivalent esatto the presence of verso property with the same name and whose value is the empty set. In other words, every OPTIONAL set-valued property MUST be assumed to have the empty serie as its default value, onesto be used per 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 Schema 1.0 Simple Types Used con the Component Model) of the simple types defined by the XML Nota 1.0 specification [ XML Nota: Datatypes ].

Sopra addenda puro the direct XML Infoset representation described here, the component model allows components external onesto the Infoset through the mechanisms described durante 4. Modularizing WSDL 2.0 descriptions.

2.1 Description

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

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

2.1.1 The Description Component

At per high level, the Description component is just per 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 mediante terms of the [ XML Information Set ], i.ed. 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 to WSDL 2.0; see 6. Language Extensibility. Per the case where they define information equivalent onesto that of verso XML Schema global element declaration, they can be treated as if they were such a declaration.