0 as verso 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 per arnesi of WSDL 2.0 components and properties that satisfy all the requirements given con 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 per different type of component, its defined properties, and its representation as an XML Infoset [ XML Information Serie ].
Properties are unordered and unique with respect onesto the component they are associated with. Individual properties’ definitions may constrain their content (e.g., sicuro a typed value, another component, or per servizio of typed values or components), and components may require the presence of a property esatto be considered conformant. Such properties are marked as REQUIRED, whereas those that are not required sicuro be present are marked as OPTIONAL. By convention, when specifying the mapping rules from the XML Infoset representation of a component onesto the component itself, an optional property that is absent con the component con question is described as being “empty”. Unless otherwise specified, when a property is identified as being verso collection (verso set or a list), its value may be a 0-element (empty) collection. Mediante order to simplify the presentation of the rules that deal with sets of components, for all OPTIONAL properties whose type is verso set, the absence of such a property from per component MUST be treated as semantically equivalent onesto the presence of per property with the same name and whose value is the empty set. Sopra other words, every OPTIONAL servizio-valued property MUST be assumed esatto have the empty serie as its default value, to be used sopra 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 verso subset (see 2.14 XML Precisazione 1.0 Simple Types Used in the Component Model) of the simple types defined by the XML Nota 1.0 specification [ XML incontri sugar daddy for me Lista: Datatypes ].
Sopra addenda preciso the direct XML Infoset representation described here, the component model allows components external sicuro the Infoset through the mechanisms described durante 4. Modularizing WSDL 2.0 descriptions.
Per component model can be extracted from a given XML Infoset which conforms puro the XML Schema for WSDL 2.0 by recursively mapping Information Items preciso 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 per means of producing an XML Infoset representation from a component model instance. Con particular, there are in general many valid ways sicuro modularize verso 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 per message’s content. By default, these constraints are expressed in terms of the [ XML Information Attrezzi ], i.ed. they define the [local name], [namespace name], [children] and [attributes] properties of an element information item. Type systems based upon other data models are generally accommodated by extensions onesto WSDL 2.0; see 6. Language Extensibility. Sopra the case where they define information equivalent puro that of a XML Nota global element declaration, they can be treated as if they were such a declaration.