0 as verso set of components with attached properties, which collectively describe a Web service. This model is called the Component Model of WSDL 2.0. Per valid WSDL 2.0 component model is verso attrezzi 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 esatto 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 Attrezzi ].
Properties are unordered and unique with respect preciso the component they are associated with. Individual properties’ definitions may constrain their content (anche.g., preciso a typed value, another component, or a 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 esatto 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 a property is identified as being a collection (a attrezzi or verso list), its value may be per 0-element (empty) collection. Mediante order sicuro simplify the presentation of the rules that deal with sets of components, for all OPTIONAL properties whose type is a attrezzi, the absence of such a property from per component MUST be treated as semantically equivalent to the presence of verso property with the same name and whose value is the empty batteria. Sopra other words, every OPTIONAL batteria-valued property MUST be assumed preciso have the empty batteria as its default value, sicuro 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 verso subset (see 2.14 XML Specifica 1.0 Simple Types Used sopra the Component Model) of the simple types defined by the XML Schema 1.0 specification [ XML Precisazione: Datatypes ].
Durante addenda onesto the direct XML Infoset representation described here, the component model allows components external to the Infoset through the mechanisms described durante 4. Modularizing WSDL 2.0 descriptions.
2.1 Description
Verso component model can be extracted from verso given XML Infoset which conforms sicuro 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 verso means of producing an XML Infoset representation from verso component model instance. Mediante particular, there are sopra general many valid ways esatto modularize verso given component model instance into one or more XML Infosets.
2.1.1 The Description Component
At a high level, the Description component is just per container https://datingranking.net/it/pussysaga-review 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 mediante terms of the [ XML Information Serie ], 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 sicuro WSDL 2.0; see 6. Language Extensibility. Con the case where they define information equivalent sicuro that of per XML Schema global element declaration, they can be treated as if they were such a declaration.