0 as verso 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 per arnesi 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 onesto different aspects of Web services. Each subsection herein describes a different type of component, its defined properties, and its representation as an XML Infoset [ XML Information Set ].
Properties are unordered and unique with respect puro the component they are associated with. Individual properties’ definitions may constrain their content (e.g., onesto a typed value, another component, or per attrezzi of typed values or components), and components may require the presence of per property sicuro be considered conformant. Such properties are marked as REQUIRED, whereas those that are not required preciso be present are marked as OPTIONAL. By convention, when specifying the mapping rules from the XML Infoset representation of per component puro the component itself, an optional property that is absent durante the component sopra question is described as being “empty”. Unless otherwise specified, when verso property is identified as being per collection (a set or verso list), its value may be verso 0-element (empty) collection. Sopra order onesto simplify the presentation of the rules that deal with sets of components, for all OPTIONAL properties whose type is per servizio, upforit the absence of such verso property from a component MUST be treated as semantically equivalent puro the presence of verso property with the same name and whose value is the empty set. Durante other words, every OPTIONAL attrezzi-valued property MUST be assumed onesto have the empty serie as its default value, puro be used durante case the property is absent.
Component definitions are serializable in XML 1.0 format but are independent of any particular serialization of the component model. Component definitions use per subset (see 2.14 XML Elenco 1.0 Simple Types Used durante the Component Model) of the simple types defined by the XML Schema 1.0 specification [ XML Elenco: Datatypes ].
Durante additif esatto 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
Verso component model can be extracted from per given XML Infoset which conforms to the XML Precisazione 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 con 4. Modularizing WSDL 2.0 descriptions.
This document does not specify a means of producing an XML Infoset representation from a component model instance. Mediante particular, there are in 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 a 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 con terms of the [ XML Information Arnesi ], i.ed. they define the [local name], [namespace name], [children] and [attributes] properties of an element information item. Type systems based upon other datazione models are generally accommodated by extensions puro WSDL 2.0; see 6. Language Extensibility. Per the case where they define information equivalent preciso that of per XML Schema global element declaration, they can be treated as if they were such a declaration.