Assertion Coverage Report

213 assertions
9444% have coverage11956% have no coverage
Part 1 (94 assertions)
5559% have coverage3941% have no coverage
Part 2 (119 assertions)
3933% have coverage8067% have no coverage

Assertion breakdown: 153 component, 43 document, 13 exchange, 4 message.

Testcase complexity: 132 testcases violate 1 assertion, 7 testcases violate 2 assertions, and 0 testcases violate 3 or more assertions.

StatusCountAssertionSynopsisClassTests
 4Binding-1044If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components), then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.component[Binding-5B] [Binding-6B] [Chat-1B] [HTTPBinding-1B]
 3Binding-1045A Binding component that defines bindings for an Interface component MUST define bindings for all the operations of that Interface component.component[Binding-1B] [Binding-4B] [Chat-2B]
 0Binding-1046Similarly, whenever a reusable Binding component (i.e. one that does not specify an Interface component) is applied to a specific Interface component in the context of an Endpoint component (see ), the Binding component MUST define bindings for each Interface Operation and Interface Fault component of the Interface component, via a combination of properties defined on the Binding component itself and default binding rules specific to its binding type.component
 1Binding-1047A Binding component that defines bindings for an Interface component MUST define bindings for all the faults of that Interface component that are referenced from any of the operations in that Interface component.component[BindingFaultReference-1B]
 1Binding-1048This xs:anyURI MUST be an absolute IRI as defined by .component[Binding-7B]
 1Binding-1049For each Binding component in the bindings property of a Description component, the name property MUST be unique.component[Binding-3B]
 2BindingFault-1050For each Binding Fault component in the binding faults property of a Binding component, the interface fault property MUST be unique.component[Binding-2B] [BindingFault-1B]
 0BindingFaultReference-1055For each Binding Fault Reference component in the binding fault references property of a Binding Operation component, the interface fault reference property MUST be unique.component
 1BindingFaultReference-1059There MUST be an Interface Fault Reference component in the interface fault references of the Interface Operation being bound with message label equal to the effective message label and with interface fault equal to an Interface Fault component with name equal to the actual value of the refattribute information item.component[BindingFaultReference-3B]
 1BindingMessageReference-1052For each Binding Message Reference component in the binding message references property of a Binding Operation component, the interface message reference property MUST be unique.component[BindingMessageReference-1B]
 1BindingOperation-1051For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique.component[BindingOperation-1B]
 0Compare-URI-IRI-1065When such absolute URIs and IRIs are being compared to determine equivalence (see ), they MUST be compared character-by-character as indicated in .component
 0Description-1001The value of the targetNamespaceattribute information item SHOULD be dereferencable.component
 0Description-1002It SHOULD resolve to a human or machine processable document that directly or indirectly defines the intended semantics of those components.component
 0Description-1003It MAY resolve to a WSDL 2.0 document that provides service description information for that namespace.component
 0Description-1004If a WSDL 2.0 document is split into multiple WSDL 2.0 documents (which may be combined as needed via ), then the targetNamespaceattribute information item SHOULD resolve to a master WSDL 2.0 document that includes all the WSDL 2.0 documents needed for that service description.document
 1Description-1005Zero or more element information items amongst its [children], in order as follows:document[TicketAgent-1B]
 1Description-1006Its value MUST be an absolute IRI (see ) and should be dereferencable.document[Description-2B]
 0Description-1067For each component in the imported namespace, a corresponding Element Declaration component or Type Definition component MUST appear in the element declarations or type definitions property respectively of the Description component corresponding to the WSDL document that imports the schema, or that imports directly or indirectly a WSDL document that imports the schema.component
 0Description-1068Schema components not in an imported namespace MUST NOT appear in the element declarations or type definitions properties.component
 0Description-1071For each component defined and declared in the inlined schema document or included by xs:include, a corresponding Element Declaration component or Type Definition component MUST appear in the element declarations property or type definitions property respectively of the Description component corresponding to the WSDL document that contains the schema, or that imports directly or indirectly a WSDL document that contains the schema.component
 0Description-1072Schema components not defined or declared in the inlined schema document or included by xs:include MUST NOT appear in the element declarations or type definitions properties.component
 2Endpoint-1061This xs:anyURI MUST be an absolute IRI as defined by .component[Service-14B] [Service-15B]
 1Endpoint-1062For each Endpoint component in the endpoints property of a Service component, the binding property MUST either be a Binding component with an unspecified interface property or a Binding component with an interface property equal to the interface property of the Service component.component[Service-4B]
 0Equivalence-1063Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules.component
 0Extensibility-1089An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of a WSDL 2.0 document.component
 0Extensibility-1090If a WSDL 2.0 document declares an extension as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension.component
 0Extensibility-1091Therefore, the Web service MUST support every extension that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension that is declared as mandatory.component
 0Extension-1088The meaning of an extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace IRI.component
 0FaultDelivery-2008The fault message MUST be delivered to the same target node as the message it replaces, unless otherwise specified by an extension or binding extension. If there is no path to this node, the fault MUST be discarded.exchange
 0FaultDelivery-2010The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension or binding extension. Any node MAY propagate a fault message, and MUST NOT do so more than once for each triggering message. If there is no path to the originator, the fault MUST be discarded.exchange
 0FaultPropagation-2003Nodes that generate faults MUST attempt to propagate the faults in accordance with the governing ruleset, but it is understood that any delivery of a network message is best effort, not guaranteed.exchange
 0FaultPropagation-2004When a fault is generated, the generating node MUST attempt to propagate the fault, and MUST do so in the direction and to the recipient specified by the ruleset.exchange
 0FaultPropagationModification-2005However, extensions or binding extensions MAY modify these rulesets.component
 0FaultReplacesMessage-2007When the Fault Replaces Message propagation rule is in effect, any message after the first in the pattern MAY be replaced with a fault message, which MUST have identical direction.exchange
 0HTTPAccessAuthentication-2127If the http authentication scheme property is present, then this property MUST be present.component
 0HTTPBinding-2083When formulating the HTTP message to be transmitted, the HTTP request method used MUST be selected using one of the following:component
 0HTTPBinding-2084When formulating the HTTP message to be transmitted, content encoding for a given Binding Message Reference component is determined as follows:component
 0HTTPBinding-2085When formulating the HTTP fault message to be transmitted, content encoding for a given Binding Fault component is determined as follows:component
 0HTTPBinding-2086When formulating the HTTP message to be transmitted, the contents of the payload (i.e. the contents of the HTTP message body) MUST be what is defined by the corresponding Interface Message Reference or Interface Fault components, serialized as specified by the serialization format used.component
 0HTTPBinding-2087If the value is #none, then the payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.component
 0HTTPBinding-2088If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined in an extension specification to indicate how to map those components into the HTTP envelope.component
 0HTTPBinding-2089The serialization rules for messages whose message content model is either #element or #any, AND the serialization rules for fault messages, are as follows:component
 1HTTPBindingFault-2105The fault definition SHOULD agree with the definition of the HTTP error codes, as specified in section 8 of .component[HTTPBinding-2B]
 0HTTPBindingFault-2106An integer value of this property identifies the error Status-Code as defined by that the service will use in case the fault is returned.component
 0HTTPBindingOperation-2093When formulating the HTTP Request, the HTTP Request IRI is an absolute IRI reference and is the value of the http location property of the Binding Operation component, resolved using the value of the address property of the Endpoint component (see section 5 of ).component
 0HTTPBindingOperation-2094The first one is transmitted using an HTTP request, and the second one is transmitted using the corresponding HTTP response.component
 0HTTPBindingOperation-2095In cases where only one single message is being sent, the message body of the HTTP response MUST be empty.component
 1HTTPBindingOperation-2098It MUST contain an IRI reference and MUST NOT include a fragment identifier component.component[HTTPBinding-5B]
 0HTTPBindingOperation-2100The value of the serialization format used for a message is a media type which MUST be covered by this range.component
 2HTTPBindingOperation-2101Wild cards (for example, application/*) SHOULD NOT be used in this attribute information item since they may lead to interoperability problems.component[HTTPBinding-3B] [HTTPBinding-4B]
 0HTTPCookies-2126A value of true means that the service relies on cookies and that the client MUST understand them.component
 0HTTPHeader-2090If the http headers property as defined in section exists and is not empty in a Binding Message Reference or Binding Fault component, HTTP headers conforming to each HTTP Header component contained in this http headers property MAY be serialized as follows:component
 0HTTPHeader-2091The HTTP binding MUST NOT set an HTTP header field corresponding to the value of the name property already set by another mechanism, such as the HTTP stack or another feature.component
 0HTTPHeader-2092If the value of an HTTP Header component's required property is true, the inclusion of this HTTP header field is REQUIREDcomponent
 1HTTPHeader-2102A Binding Message Reference or a Binding Fault component's http headers property MUST NOT contain multiple HTTP Header components with the same name property.component[HTTPBinding-6B]
 1HTTPHeader-2103This type MUST be a simple type.component[HTTPBinding-7B]
 0HTTPHeader-2104If the value is true, then the HTTP header field MUST be included in the message.component
 0HTTPQueryString-2115The instance data MUST NOT contain elements with an xs:nil attribute whose value is true.component
 0HTTPQueryString-2116When serializing an HTTP request that does not allow an HTTP message body, and when http location ignore uncited is true, any element NOT cited in the http location property MUST be defined in the schema as nillable, or have a default value, or appear no less frequently than specified by the minOccurs value. The element declaration SHOULD NOT combine a default value with nillable.component
 0HTTPSerialization-2099The value of the http input serialization, http output serialization and http fault serialization properties is similar to the value allowed for the Accept HTTP header defined by the HTTP 1.1 specification, Section 14.1 (see ) and MUST follow the production rules defined in that section except for the following:component
 0HTTPSerialization-2106The http location property MUST conform to the following EBNF grammar, which represents the patterns for constructing the request IRI:component
 0HTTPSerialization-2107If the style property of the Interface Operation bound has a value of http://www.w3.org/ns/wsdl/style/iri as defined in , and if the http location property of the Binding Operation component is present, the value of the http location property component is used as a templatecomponent
 0HTTPSerialization-2108The resulting IRI MUST be mapped to an URI for use in the HTTP Request as per section 3.1 "Mapping of IRIs to URIs" of the IRI specification .component
 0HTTPSerialization-2109The local name in a template SHOULD match at least one element from the instance data of the input message.component
 0HTTPSerialization-2110Cited elements (i.e. elements referenced in templates) MUST NOT carry an xs:nil attribute whose value is truemessage
 1HTTPSerialization-2111If this format is used then the style property of Interface Operation component being bound MUST contain a value of http://www.w3.org/ns/wsdl/style/iri as defined in , i.e. this serialization format may only be used to serialize the HTTP request corresponding to the initial message of an interface operation.component[HTTPBinding-8B]
 0HTTPSerialization-2112For the HTTP binding defined in this section (), application/x-www-form-urlencoded MAY be used as a serialization format for an input message (HTTP Request), but MUST NOT be used as a serialization format for an output or fault message (HTTP Response).component
 0HTTPSerialization-2113If not all elements from the instance data are cited in the http location property, or if the property is not present on the Binding Operation component, then additional serialization rules apply.component
 0HTTPSerialization-2114For elements of the instance data not cited in the http location property, a query string is constructed as follows.component
 0HTTPSerialization-2117If the HTTP request method used does not allow HTTP message body (e.g. GET and DELETE), and if the value of the http location ignore uncited property is false, then the following rules apply.component
 0HTTPSerialization-2118If the HTTP request method used does allow an HTTP message body (e.g. POST and PUT), then the following rules apply.component
 0HTTPSerialization-2119The Content-Type HTTP header field must have the value application/x-www-form-urlencoded.component
 0HTTPSerialization-2120The Content-Type HTTP header MUST have the value application/xml, or a media type compatible with application/xml as specified in section .component
 0HTTPSerialization-2121this serialization format may only be used to serialize the HTTP request corresponding to the initial message of an interface operation.component
 0HTTPSerialization-2122Specifically, for the HTTP binding defined in this section (), multipart/form-data MAY be used as a serialization format for an input message (HTTP Request), but MUST NOT be used as a serialization format for an output or fault message (HTTP Response).component
 0HTTPSerialization-2123The Content-Disposition header MUST have the value form-data, and its name parameter is the local name of the element.component
 0HTTPSerialization-2124The Content-Type header MUST have the value:component
 0HTTPSerialization-2125The instance data MUST NOT contain elements with an xs:nil attribute whose value is true.component
 2Import-1082As with XML schema, any WSDL 2.0 document that references a foreign component MUST have a wsdl:importelement information item for the associated foreign namespace (but which does not necessarily provide a locationattribute information item that identifies the WSDL 2.0 document in which the referenced component is defined).document[Description-1B] [Import-4B]
 1Import-1083If a WSDL 2.0 document contains more than one wsdl:importelement information item for a given value of the namespaceattribute information item, then they MUST provide different values for the locationattribute information item.document[Import-5B]
 1Import-1084This value MUST NOT match the actual value of targetNamespaceattribute information item in the enclosing WSDL 2.0 document.document[Import-6B]
 4Import-1085If the location attribute in the importelement information item is dereferencable, then it MUST reference a WSDL 2.0 document.document[Chameleon-2B] [Import-2B] [Import-7B] [Import-8B]
 0Import-1086If the locationattribute information item of the importelement information item is dereferencable, then the actual value of the namespaceattribute information item MUST be identical to the actual value of the targetNamespaceattribute information item of the referenced WSDL 2.0 document (see ).document
 0ImportInclude-1087The semantics of an extension MUST NOT depend on how components are brought into a component model instance via <import> or <include>.component
 1Include-1080The IRI indicated by location MUST resolve to a WSDL 2.0 document.document[Include-2B]
 1Include-1081The actual value of the targetNamespaceattribute information item of the included WSDL 2.0 document MUST match the actual value of the targetNamespaceattribute information item of the descriptionelement information item which is the [parent] of the includeelement information item.document[Include-1B]
 0InOnlyComposition-2012The in-only message exchange pattern consists of exactly one message as follows:component
 0InOnlyFaults-2013The in-only message exchange pattern uses the rule .exchange
 0InOutComposition-2015The in-out message exchange pattern consists of exactly two messages, in order, as follows:component
 0InOutFaults-2016The in-out message exchange pattern uses the rule .exchange
 2Interface-1009To avoid circular definitions, an interface MUST NOT appear in the set of interfaces it extends, either directly or indirectly.component[Interface-2B] [Interface-3B]
 1Interface-1010For each Interface component in the interfaces property of a Description component, the name property MUST be unique.component[Interface-5B]
 1Interface-1011The list of xs:QName in an extendsattribute information item MUST NOT contain duplicates.component[Interface-4B]
 1Interface-1012Its value, if present, MUST contain absolute IRIs (see ).document[Interface-1B]
 0InterfaceFault-1013An xs:token with one of the values #any, #none, #other, or #element.component
 0InterfaceFault-1014When the message content model property has the value #any or #none the element declaration property MUST be empty.component
 2InterfaceFault-1015In cases where, due to an interface extending one or more other interfaces, two or more Interface Fault components have the same value for their name property, then the component models of those Interface Fault components MUST be equivalent (see ).component[InterfaceFault-2B] [InterfaceFault-3B]
 1InterfaceFault-1016For the above reason, it is considered good practice to ensure, where necessary, that the local name of the name property of Interface Fault components within a namespace SHOULD be unique, thus allowing such derivation to occur without inadvertent error.component[InterfaceFault-3B]
 1InterfaceFault-1017If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.document[InterfaceFault-1B]
 0InterfaceFaultReference-1037The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.component
 1InterfaceFaultReference-1038The direction MUST be consistent with the direction implied by the fault propagation ruleset used in the message exchange pattern of the operation.component[InterfaceFaultReference-1B]
 1InterfaceFaultReference-1039For each Interface Fault Reference component in the interface fault references property of an Interface Operation component, the combination of its interface fault and message label properties MUST be unique.component[InterfaceFaultReference-2B]
 0InterfaceFaultReference-1040The messageLabelattribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given direction, if the message exchange pattern of the parent Interface Operation component has more than one fault with that direction.document
 0InterfaceMessageReference-1025An xs:token with one of the values in or out, indicating whether the message is coming to the service or going from the service, respectively.component
 1InterfaceMessageReference-1026The direction MUST be the same as the direction of the message identified by the message label property in the message exchange pattern of the Interface Operation component this is contained within.component[InterfaceMessageReference-2B]
 0InterfaceMessageReference-1027An xs:token with one of the values #any, #none, #other, or #element.component
 0InterfaceMessageReference-1028When the message content model property has the value #any or #none, the element declaration property MUST be empty.component
 1InterfaceMessageReference-1029For each Interface Message Reference component in the interface message references property of an Interface Operation component, its message label property MUST be unique.component[InterfaceMessageReference-3B]
 1InterfaceMessageReference-1036If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.document[InterfaceMessageReference-4B]
 1InterfaceOperation-1018This xs:anyURI MUST be an absolute IRI (see ).component[InterfaceOperation-3B]
 1InterfaceOperation-1019These xs:anyURIs MUST be absolute IRIs (see ).component[InterfaceOperation-4B]
 3InterfaceOperation-1020In cases where, due to an interface extending one or more other interfaces, two or more Interface Operation components have the same value for their name property, then the component models of those Interface Operation components MUST be equivalent (see ).component[InterfaceOperation-1B] [InterfaceOperation-5B] [InterfaceOperation-6B]
 1InterfaceOperation-1021For the above reason, it is considered good practice to ensure, where necessary, that the name property of Interface Operation components within a namespace SHOULD be unique, thus allowing such derivation to occur without inadvertent error.component[InterfaceOperation-5B]
 0InterfaceOperation-1023An Interface Operation component MUST satisfy the specification defined by each operation style identified by its style property.component
 0InterfaceOperation-2096202 when the MEP is http://www.w3.org/ns/wsdl/in-onlycomponent
 0InterfaceOperation-2097204 when the MEP is http://www.w3.org/ns/wsdl/robust-in-onlycomponent
 3IRIStyle-2051When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.component[IRI-1B] [IRI-2B] [IRI-3B]
 1IRIStyle-2052The sequence MUST only contain elements.component[IRI-4B]
 1IRIStyle-2053The sequence MUST contain only local element children.component[IRI-5B]
 1IRIStyle-2054The localPart of the element's QName MUST be the same as the Interface Operation component's name.component[IRI-6B]
 1IRIStyle-2055The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.component[IRI-7B]
 9IRIStyle-2056The children elements of the sequence MUST derive from xs:simpleType, and MUST NOT be of the type or derive from xs:QName, xs:NOTATION, xs:hexBinary or xs:base64Binary.component[IRI-8B] [IRI-9B] [IRI-10B] [IRI-11B] [IRI-12B] [IRI-13B] [IRI-14B] [IRI-15B] [IRI-16B]
 3Location-1092It MUST NOT appear on a wsdl:description element or any of its children/descendants.document[Location-1B] [Location-2B] [Location-3B]
 2Location-1093Its actual value MUST be a list of pairs of IRIs; where the first IRI of a pair, which MUST be an absolute IRI as defined in , indicates a WSDL 2.0 (or 1.1) namespace name, and, the second a hint as to the location of a WSDL 2.0 document defining WSDL 2.0 components (or WSDL 1.1 elements ) for that namespace name.component[Location-4B] [Location-5B]
 2Location-1094For each pair of IRIs, if the location IRI of the pair is dereferencable, then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.document[Location-6B] [Location-7B]
 0MEP-1022A message exchange pattern is itself uniquely identified by an absolute IRI, which is used as the value of the message exchange pattern property of the Interface Operation component, and which specifies the fault propagation ruleset that its faults obey.component
 0MEPDescriptiveness-2002by some prior agreement, another node and/or the service MAY send messages (to each other or to other nodes) that are not described by the pattern.exchange
 0MEPTermination-2006Generation of a fault, regardless of ruleset, terminates the exchange.exchange
 1MessageLabel-1024The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.component[InterfaceMessageReference-1B]
 0MessageLabel-1030If the messageLabelattribute information item of an interface message reference element information item is present, then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.document
 0MessageLabel-1031If the messageLabelattribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.document
 0MessageLabel-1032If the local name is input then the message exchange pattern MUST have at least one placeholder message with direction In.document
 0MessageLabel-1033If the local name is output then the message exchange pattern MUST have at least one placeholder message with direction Out.document
 0MessageLabel-1034If the local name is infault then the message exchange pattern MUST support at least one fault in the In direction.document
 0MessageLabel-1035If the local name is outfault then the message exchange pattern MUST support at least one fault in the Out direction.document
 0MessageLabel-1041The messageLabelattribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.document
 0MessageLabel-1042If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.document
 0MessageLabel-1043If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.document
 1MessageLabel-1053If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.document[BindingMessageReference-3B]
 1MessageLabel-1054If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.document[BindingMessageReference-2B]
 1MessageLabel-1056The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.document[BindingFaultReference-2B]
 1MessageLabel-1057If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.document[BindingFaultReference-3B]
 1MessageLabel-1058If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.document[BindingFaultReference-2B]
 0MessageTriggersFault-2009When the Message Triggers Fault propagation rule is in effect, any message, including the first in the pattern, MAY trigger a fault message, which MUST have opposite direction.exchange
 3MultipartStyle-2057When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.component[Multipart-1B] [Multipart-2B] [Multipart-3B]
 1MultipartStyle-2058The sequence MUST only contain elements.component[Multipart-4B]
 1MultipartStyle-2059The sequence MUST contain only local element children.component[Multipart-5B]
 2MultipartStyle-2060The attributes minOccurs and maxOccurs for these child elements MUST have a value 1.component[Multipart-6B] [Multipart-7B]
 1MultipartStyle-2061The localPart of the element's QName MUST be the same as the Interface Operation component's name.component[Multipart-8B]
 1MultipartStyle-2062The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.component[Multipart-9B]
 1MultipartStyle-2063The sequence MUST NOT contain multiple children element declared with the same local name.component[Multipart-10B]
 0NodeIdentity-2001A node MAY be accessible via more than one physical address or transport.exchange
 0NoFaults-2011When the No Faults propagation rule is in effect, faults MUST NOT be propagated.exchange
 0OperationSafety-2027However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.4 of .component
 0OperationSafety-2028An OPTIONAL safeattribute information item with the following Infoset properties:document
 7QName-resolution-1064A Description component MUST NOT have such broken references.document[Schema-3B] [Schema-4B] [Schema-5B] [Service-12B] [Service-13B] [Service-1B] [Service-2B]
 0RobustInOnlyComposition-2013The robust-in-only message exchange pattern consists of exactly one message as follows:component
 0RobustInOnlyFaults-2014The robust in-only message exchange pattern uses the rule .exchange
 1RPCStyle-2029If the RPC style is used by an Interface Operation component then its message exchange pattern property MUST have the value either http://www.w3.org/ns/wsdl/in-only or http://www.w3.org/ns/wsdl/in-out.component[RPC-28B]
 2RPCStyle-2030The value of the message content model property for the Interface Message Reference components of the interface message references property MUST be #element.component[RPC-1B] [RPC-2B]
 1RPCStyle-2031The content model of input and output element declaration elements MUST be defined using a complex type that contains a sequence from XML Schema.component[RPC-3B]
 1RPCStyle-2032The input sequence MUST only contain elements and element wildcards.component[RPC-4B]
 1RPCStyle-2033The input sequence MUST NOT contain more than one element wildcard.component[RPC-5B]
 1RPCStyle-2034The element wildcard, if present, MUST appear after any elements.component[RPC-6B]
 1RPCStyle-2035The output sequence MUST only contain elements.component[RPC-7B]
 1RPCStyle-2036Both the input and output sequences MUST contain only local element children.component[RPC-8B]
 1RPCStyle-2037The local name of input element's QName MUST be the same as the Interface Operation component's name.component[RPC-9B]
 1RPCStyle-2038Input and output elements MUST both be in the same namespace.component[RPC-14B]
 2RPCStyle-2039The complex type that defines the body of an input or an output element MUST NOT contain any local attributes.component[RPC-10B] [RPC-11B]
 1RPCStyle-2040If elements with the same qualified name appear as children of both the input and output elements, then they MUST both be declared using the same named type.component[RPC-15B]
 2RPCStyle-2041The input or output sequence MUST NOT contain multiple children elements declared with the same name.component[RPC-12B] [RPC-13B]
 3Schema-1066A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace UNLESS an xs:import or xs:schemaelement information item for that namespace is present OR the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .document[Chameleon-1B] [Import-1B] [Import-3B]
 1Schema-1069The referenced schema MUST contain a targetNamespaceattribute information item on its xs:schemaelement information item.document[Schema-1B]
 2Schema-1070The value of the targetNamespaceattribute information item of the xs:schemaelement information item of an imported schema MUST equal the value of the namespace of the importelement information item in the importing WSDL 2.0 document.document[Schema-1B] [Schema-2B]
 2Schema-1073A WSDL 2.0 document MUST NOT define the same element or type in more than one inlined schema.document[Schema-6B] [Schema-7B]
 0Schema-1075A specification of extension syntax for an alternative schema language MUST use a namespace that is different than the namespace of XML Schema.document
 0Schema-1076The namespace used for an alternate schema language MUST be an absolute IRI.document
 1Schema-1079If wsdlx:interface and wsdlx:binding are used together then they MUST satisfy the same consistency rules that apply to the interface property of a Service component and the binding property of a nested Endpoint component, that is either the binding refers the interface of the service or the binding refers to no interface.document[wsdlx-3B]
 1Service-1060For each Service component in the services property of a Description component, the name property MUST be unique.component[Service-3B]
 0SOAP12Binding-SOAPDetail-2081If any, the value of the SOAP Detail element MUST be the element information item identified by the element declaration property of the Interface Fault component.message
 0SOAPAction-2075A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component.component
 0SOAPBinding-2065When formulating the SOAP envelope to be transmitted, the contents of the payload (i.e., the contents of the SOAP Body element information item of the SOAP envelope) MUST be what is defined by the corresponding Interface Message Reference component.component
 0SOAPBinding-2066If the value is #none, then the payload MUST be empty.message
 0SOAPBinding-2067If the value is #element, then the payload MUST be the element information item identified by the element declaration property of the Interface Message Reference component.message
 0SOAPBinding-2068If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.component
 0SOAPBinding-2069Every SOAP binding MUST indicate what version of SOAP is in use for the operations of the interface that this binding applies to.component
 0SOAPBinding-2070Every SOAP binding MUST indicate what underlying protocol is in use.component
 0SOAPBindingFault-2071For every Interface Fault component contained in an Interface component, a mapping to a SOAP Fault MUST be described.component
 0SOAPBindingFault-2072when the value of the soap version is 1.2, the allowed QNames MUST be the ones defined by , section 5.4.6component
 0SOAPHeaderBlock-2077When its value is true, the SOAP header block MUST be decorated with a SOAP mustUnderstandattribute information item with a value of true; if so, the XML element declaration referenced by the element declaration property MUST allow this SOAP mustUnderstandattribute information item.component
 0SOAPHeaderBlock-2078If the value is true, then the SOAP header block MUST be included in the message.component
 0SOAPHeaderBlock-2079The value of the elementattribute information item MUST resolve to a global element declaration from the element declarations property of the Description component.component
 0SOAPHTTPProperties-2064These properties MUST NOT be used unless the underlying protocol is HTTP.component
 0SOAPHTTPSelection-2082This default binding rule is applicable when the value of the soap underlying protocol property of the Binding component is http://www.w3.org/2003/05/soap/bindings/HTTP/. If the SOAP MEP selected as specified above has the value http://www.w3.org/2003/05/soap/mep/request-response/ then the HTTP method used is POST. If the SOAP MEP selected has the value http://www.w3.org/2003/05/soap/mep/soap-response/ then the HTTP method used is GET.component
 0SOAPMEP-2074A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component.component
 0SOAPMEPDefault-2073A xs:anyURI, which is an absolute IRI as defined by , to the Binding component.component
 0SOAPMEPSelection-2080For a given Interface Operation component, if there is a Binding Operation component whose interface operation property matches the component in question and its soap mep property has a value, then the SOAP MEP is the value of the soap mep property. Otherwise, the SOAP MEP is the value of the Binding component's soap mep default, if any. Otherwise, the Interface Operation component's message exchange pattern property MUST have the value http://www.w3.org/ns/wsdl/in-out, and the SOAP MEP is the URI http://www.w3.org/2003/05/soap/mep/request-response/ identifying the SOAP Request-Response Message Exchange Pattern as defined in .component
 0SOAPModule-2076A xs:anyURI, which is an absolute IRI as defined by .component
 1Types-1007Each XML Schema element declaration MUST have a unique QName.component[Schema-6B]
 1Types-1008Each XML Schema type definition MUST have a unique QName.component[Schema-7B]
 0Types-1074A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:typeselement information item, which references, names, and locates the schema instance (an importelement information item).document
 2Types-1077The type of the wsdlx:interfaceattribute information item is an xs:QName that specifies the name property of an Interface component.document[wsdlx-1B] [wsdlx-4B]
 2Types-1078The type of the wsdlx:bindingattribute information item is an xs:QName that specifies the name property of a Binding component.document[wsdlx-2B] [wsdlx-5B]
 0WRPC-2042OPTIONAL, but MUST be present when the style is RPCcomponent
 0WRPC-2043Values for the second component MUST be chosen among the following four: "#in", "#out", "#inout" "#return".component
 1WRPC-2044The value of the first component of each pair (q, t) MUST be unique within the list.component[RPC-17B]
 1WRPC-2045For each child element of the input and output messages of the operation, a pair (q, t), whose first component q is equal to the qualified name of that element, MUST be present in the list, with the caveat that elements that appear with cardinality greater than one MUST be treated as a single element.component[RPC-18B]
 2WRPC-2046For each pair (q, #in), there MUST be a child element of the input element with a name of q. There MUST NOT be a child element of the output element with the name of q.component[RPC-19B] [RPC-20B]
 2WRPC-2047For each pair (q, #out), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.component[RPC-21B] [RPC-22B]
 2WRPC-2048For each pair (q, #inout), there MUST be a child element of the input element with a name of q. There MUST also be a child element of the output element with the name of q.component[RPC-23B] [RPC-24B]
 2WRPC-2049For each pair (q, #return), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.component[RPC-25B] [RPC-26B]
 1WRPC-2050Additionally, each even-numbered item (0, 2, 4, ...) in the list MUST be of type xs:QName and each odd-numbered item (1, 3, 5, ...) in the list MUST be of the subtype of xs:token described in the previous paragraph.document[RPC-27B]