0 as per 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 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 puro 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 preciso the component they are associated with. Individual properties’ definitions may constrain their content (anche.g., esatto verso typed value, another component, or verso arnesi of typed values or components), and components may require the presence of a property puro 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 a component preciso the component itself, an optional property that is absent sopra the component in question is described as being “empty”. Unless otherwise specified, when http://datingranking.net/it/ohlala-review a property is identified as being per collection (verso batteria or a list), its value may be per 0-element (empty) collection. Con order sicuro 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 preciso the presence of verso property with the same name and whose value is the empty batteria. Con other words, every OPTIONAL arnesi-valued property MUST be assumed sicuro have the empty attrezzi as its default value, puro 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 per subset (see 2.14 XML Schema 1.0 Simple Types Used in the Component Model) of the simple types defined by the XML Precisazione 1.0 specification [ XML Schema: Datatypes ].
Mediante additif preciso 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 a given XML Infoset which conforms puro the XML Precisazione 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 mediante 4. Modularizing WSDL 2.0 descriptions.
This document does not specify verso means of producing an XML Infoset representation from a component model instance. Mediante particular, there are per general many valid ways esatto modularize verso 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 Serie ], i.anche. they define the [local name], [namespace name], [children] and [attributes] properties of an element information item. Type systems based upon other scadenza models are generally accommodated by extensions esatto WSDL 2.0; see 6. Language Extensibility. In the case where they define information equivalent onesto that of verso XML Elenco global element declaration, they can be treated as if they were such verso declaration.