94
119
119
5539
39
3980
80| 213 assertions |
94
119 |
| Part 1 (94 assertions) |
55
39 |
| Part 2 (119 assertions) |
39
80 |
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.
| Status | Count | Assertion | Synopsis | Class | Tests |
|---|---|---|---|---|---|
| 4 | Binding-1044 | If 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] | |
| 3 | Binding-1045 | A 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] | |
| 0 | Binding-1046 | Similarly, 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 | ||
| 1 | Binding-1047 | A 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] | |
| 1 | Binding-1048 | This xs:anyURI MUST be an absolute IRI as defined by . | component | [Binding-7B] | |
| 1 | Binding-1049 | For each Binding component in the bindings property of a Description component, the name property MUST be unique. | component | [Binding-3B] | |
| 2 | BindingFault-1050 | For 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] | |
| 0 | BindingFaultReference-1055 | For 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 | ||
| 1 | BindingFaultReference-1059 | There 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] | |
| 1 | BindingMessageReference-1052 | For 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] | |
| 1 | BindingOperation-1051 | For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique. | component | [BindingOperation-1B] | |
| 0 | Compare-URI-IRI-1065 | When such absolute URIs and IRIs are being compared to determine equivalence (see ), they MUST be compared character-by-character as indicated in . | component | ||
| 0 | Description-1001 | The value of the targetNamespaceattribute information item SHOULD be dereferencable. | component | ||
| 0 | Description-1002 | It SHOULD resolve to a human or machine processable document that directly or indirectly defines the intended semantics of those components. | component | ||
| 0 | Description-1003 | It MAY resolve to a WSDL 2.0 document that provides service description information for that namespace. | component | ||
| 0 | Description-1004 | If 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 | ||
| 1 | Description-1005 | Zero or more element information items amongst its [children], in order as follows: | document | [TicketAgent-1B] | |
| 1 | Description-1006 | Its value MUST be an absolute IRI (see ) and should be dereferencable. | document | [Description-2B] | |
| 0 | Description-1067 | For 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 | ||
| 0 | Description-1068 | Schema components not in an imported namespace MUST NOT appear in the element declarations or type definitions properties. | component | ||
| 0 | Description-1071 | For 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 | ||
| 0 | Description-1072 | Schema 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 | ||
| 2 | Endpoint-1061 | This xs:anyURI MUST be an absolute IRI as defined by . | component | [Service-14B] [Service-15B] | |
| 1 | Endpoint-1062 | For 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] | |
| 0 | Equivalence-1063 | Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules. | component | ||
| 0 | Extensibility-1089 | An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of a WSDL 2.0 document. | component | ||
| 0 | Extensibility-1090 | If 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 | ||
| 0 | Extensibility-1091 | Therefore, 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 | ||
| 0 | Extension-1088 | The meaning of an extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace IRI. | component | ||
| 0 | FaultDelivery-2008 | The 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 | ||
| 0 | FaultDelivery-2010 | The 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 | ||
| 0 | FaultPropagation-2003 | Nodes 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 | ||
| 0 | FaultPropagation-2004 | When 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 | ||
| 0 | FaultPropagationModification-2005 | However, extensions or binding extensions MAY modify these rulesets. | component | ||
| 0 | FaultReplacesMessage-2007 | When 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 | ||
| 0 | HTTPAccessAuthentication-2127 | If the http authentication scheme property is present, then this property MUST be present. | component | ||
| 0 | HTTPBinding-2083 | When formulating the HTTP message to be transmitted, the HTTP request method used MUST be selected using one of the following: | component | ||
| 0 | HTTPBinding-2084 | When formulating the HTTP message to be transmitted, content encoding for a given Binding Message Reference component is determined as follows: | component | ||
| 0 | HTTPBinding-2085 | When formulating the HTTP fault message to be transmitted, content encoding for a given Binding Fault component is determined as follows: | component | ||
| 0 | HTTPBinding-2086 | When 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 | ||
| 0 | HTTPBinding-2087 | If 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 | ||
| 0 | HTTPBinding-2088 | If 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 | ||
| 0 | HTTPBinding-2089 | The serialization rules for messages whose message content model is either #element or #any, AND the serialization rules for fault messages, are as follows: | component | ||
| 1 | HTTPBindingFault-2105 | The fault definition SHOULD agree with the definition of the HTTP error codes, as specified in section 8 of . | component | [HTTPBinding-2B] | |
| 0 | HTTPBindingFault-2106 | An 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 | ||
| 0 | HTTPBindingOperation-2093 | When 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 | ||
| 0 | HTTPBindingOperation-2094 | The first one is transmitted using an HTTP request, and the second one is transmitted using the corresponding HTTP response. | component | ||
| 0 | HTTPBindingOperation-2095 | In cases where only one single message is being sent, the message body of the HTTP response MUST be empty. | component | ||
| 1 | HTTPBindingOperation-2098 | It MUST contain an IRI reference and MUST NOT include a fragment identifier component. | component | [HTTPBinding-5B] | |
| 0 | HTTPBindingOperation-2100 | The value of the serialization format used for a message is a media type which MUST be covered by this range. | component | ||
| 2 | HTTPBindingOperation-2101 | Wild 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] | |
| 0 | HTTPCookies-2126 | A value of true means that the service relies on cookies and that the client MUST understand them. | component | ||
| 0 | HTTPHeader-2090 | If 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 | ||
| 0 | HTTPHeader-2091 | The 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 | ||
| 0 | HTTPHeader-2092 | If the value of an HTTP Header component's required property is true, the inclusion of this HTTP header field is REQUIRED | component | ||
| 1 | HTTPHeader-2102 | A 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] | |
| 1 | HTTPHeader-2103 | This type MUST be a simple type. | component | [HTTPBinding-7B] | |
| 0 | HTTPHeader-2104 | If the value is true, then the HTTP header field MUST be included in the message. | component | ||
| 0 | HTTPQueryString-2115 | The instance data MUST NOT contain elements with an xs:nil attribute whose value is true. | component | ||
| 0 | HTTPQueryString-2116 | When 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 | ||
| 0 | HTTPSerialization-2099 | The 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 | ||
| 0 | HTTPSerialization-2106 | The http location property MUST conform to the following EBNF grammar, which represents the patterns for constructing the request IRI: | component | ||
| 0 | HTTPSerialization-2107 | If 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 template | component | ||
| 0 | HTTPSerialization-2108 | The 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 | ||
| 0 | HTTPSerialization-2109 | The local name in a template SHOULD match at least one element from the instance data of the input message. | component | ||
| 0 | HTTPSerialization-2110 | Cited elements (i.e. elements referenced in templates) MUST NOT carry an xs:nil attribute whose value is true | message | ||
| 1 | HTTPSerialization-2111 | If 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] | |
| 0 | HTTPSerialization-2112 | For 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 | ||
| 0 | HTTPSerialization-2113 | If 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 | ||
| 0 | HTTPSerialization-2114 | For elements of the instance data not cited in the http location property, a query string is constructed as follows. | component | ||
| 0 | HTTPSerialization-2117 | If 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 | ||
| 0 | HTTPSerialization-2118 | If the HTTP request method used does allow an HTTP message body (e.g. POST and PUT), then the following rules apply. | component | ||
| 0 | HTTPSerialization-2119 | The Content-Type HTTP header field must have the value application/x-www-form-urlencoded. | component | ||
| 0 | HTTPSerialization-2120 | The Content-Type HTTP header MUST have the value application/xml, or a media type compatible with application/xml as specified in section . | component | ||
| 0 | HTTPSerialization-2121 | this serialization format may only be used to serialize the HTTP request corresponding to the initial message of an interface operation. | component | ||
| 0 | HTTPSerialization-2122 | Specifically, 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 | ||
| 0 | HTTPSerialization-2123 | The Content-Disposition header MUST have the value form-data, and its name parameter is the local name of the element. | component | ||
| 0 | HTTPSerialization-2124 | The Content-Type header MUST have the value: | component | ||
| 0 | HTTPSerialization-2125 | The instance data MUST NOT contain elements with an xs:nil attribute whose value is true. | component | ||
| 2 | Import-1082 | As 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] | |
| 1 | Import-1083 | If 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] | |
| 1 | Import-1084 | This value MUST NOT match the actual value of targetNamespaceattribute information item in the enclosing WSDL 2.0 document. | document | [Import-6B] | |
| 4 | Import-1085 | If 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] | |
| 0 | Import-1086 | If 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 | ||
| 0 | ImportInclude-1087 | The semantics of an extension MUST NOT depend on how components are brought into a component model instance via <import> or <include>. | component | ||
| 1 | Include-1080 | The IRI indicated by location MUST resolve to a WSDL 2.0 document. | document | [Include-2B] | |
| 1 | Include-1081 | The 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] | |
| 0 | InOnlyComposition-2012 | The in-only message exchange pattern consists of exactly one message as follows: | component | ||
| 0 | InOnlyFaults-2013 | The in-only message exchange pattern uses the rule . | exchange | ||
| 0 | InOutComposition-2015 | The in-out message exchange pattern consists of exactly two messages, in order, as follows: | component | ||
| 0 | InOutFaults-2016 | The in-out message exchange pattern uses the rule . | exchange | ||
| 2 | Interface-1009 | To avoid circular definitions, an interface MUST NOT appear in the set of interfaces it extends, either directly or indirectly. | component | [Interface-2B] [Interface-3B] | |
| 1 | Interface-1010 | For each Interface component in the interfaces property of a Description component, the name property MUST be unique. | component | [Interface-5B] | |
| 1 | Interface-1011 | The list of xs:QName in an extendsattribute information item MUST NOT contain duplicates. | component | [Interface-4B] | |
| 1 | Interface-1012 | Its value, if present, MUST contain absolute IRIs (see ). | document | [Interface-1B] | |
| 0 | InterfaceFault-1013 | An xs:token with one of the values #any, #none, #other, or #element. | component | ||
| 0 | InterfaceFault-1014 | When the message content model property has the value #any or #none the element declaration property MUST be empty. | component | ||
| 2 | InterfaceFault-1015 | In 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] | |
| 1 | InterfaceFault-1016 | For 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] | |
| 1 | InterfaceFault-1017 | If 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] | |
| 0 | InterfaceFaultReference-1037 | The value of this property MUST match the name of a placeholder message defined by the message exchange pattern. | component | ||
| 1 | InterfaceFaultReference-1038 | The 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] | |
| 1 | InterfaceFaultReference-1039 | For 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] | |
| 0 | InterfaceFaultReference-1040 | The 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 | ||
| 0 | InterfaceMessageReference-1025 | An 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 | ||
| 1 | InterfaceMessageReference-1026 | The 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] | |
| 0 | InterfaceMessageReference-1027 | An xs:token with one of the values #any, #none, #other, or #element. | component | ||
| 0 | InterfaceMessageReference-1028 | When the message content model property has the value #any or #none, the element declaration property MUST be empty. | component | ||
| 1 | InterfaceMessageReference-1029 | For 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] | |
| 1 | InterfaceMessageReference-1036 | If 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] | |
| 1 | InterfaceOperation-1018 | This xs:anyURI MUST be an absolute IRI (see ). | component | [InterfaceOperation-3B] | |
| 1 | InterfaceOperation-1019 | These xs:anyURIs MUST be absolute IRIs (see ). | component | [InterfaceOperation-4B] | |
| 3 | InterfaceOperation-1020 | In 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] | |
| 1 | InterfaceOperation-1021 | For 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] | |
| 0 | InterfaceOperation-1023 | An Interface Operation component MUST satisfy the specification defined by each operation style identified by its style property. | component | ||
| 0 | InterfaceOperation-2096 | 202 when the MEP is http://www.w3.org/ns/wsdl/in-only | component | ||
| 0 | InterfaceOperation-2097 | 204 when the MEP is http://www.w3.org/ns/wsdl/robust-in-only | component | ||
| 3 | IRIStyle-2051 | When 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] | |
| 1 | IRIStyle-2052 | The sequence MUST only contain elements. | component | [IRI-4B] | |
| 1 | IRIStyle-2053 | The sequence MUST contain only local element children. | component | [IRI-5B] | |
| 1 | IRIStyle-2054 | The localPart of the element's QName MUST be the same as the Interface Operation component's name. | component | [IRI-6B] | |
| 1 | IRIStyle-2055 | The complex type that defines the body of the element or its children elements MUST NOT contain any attributes. | component | [IRI-7B] | |
| 9 | IRIStyle-2056 | The 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] | |
| 3 | Location-1092 | It MUST NOT appear on a wsdl:description element or any of its children/descendants. | document | [Location-1B] [Location-2B] [Location-3B] | |
| 2 | Location-1093 | Its 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] | |
| 2 | Location-1094 | For 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] | |
| 0 | MEP-1022 | A 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 | ||
| 0 | MEPDescriptiveness-2002 | by 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 | ||
| 0 | MEPTermination-2006 | Generation of a fault, regardless of ruleset, terminates the exchange. | exchange | ||
| 1 | MessageLabel-1024 | The value of this property MUST match the name of a placeholder message defined by the message exchange pattern. | component | [InterfaceMessageReference-1B] | |
| 0 | MessageLabel-1030 | If 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 | ||
| 0 | MessageLabel-1031 | If 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 | ||
| 0 | MessageLabel-1032 | If the local name is input then the message exchange pattern MUST have at least one placeholder message with direction In. | document | ||
| 0 | MessageLabel-1033 | If the local name is output then the message exchange pattern MUST have at least one placeholder message with direction Out. | document | ||
| 0 | MessageLabel-1034 | If the local name is infault then the message exchange pattern MUST support at least one fault in the In direction. | document | ||
| 0 | MessageLabel-1035 | If the local name is outfault then the message exchange pattern MUST support at least one fault in the Out direction. | document | ||
| 0 | MessageLabel-1041 | The 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 | ||
| 0 | MessageLabel-1042 | If 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 | ||
| 0 | MessageLabel-1043 | If 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 | ||
| 1 | MessageLabel-1053 | If 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] | |
| 1 | MessageLabel-1054 | If 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] | |
| 1 | MessageLabel-1056 | The 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] | |
| 1 | MessageLabel-1057 | If 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] | |
| 1 | MessageLabel-1058 | If 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] | |
| 0 | MessageTriggersFault-2009 | When 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 | ||
| 3 | MultipartStyle-2057 | When 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] | |
| 1 | MultipartStyle-2058 | The sequence MUST only contain elements. | component | [Multipart-4B] | |
| 1 | MultipartStyle-2059 | The sequence MUST contain only local element children. | component | [Multipart-5B] | |
| 2 | MultipartStyle-2060 | The attributes minOccurs and maxOccurs for these child elements MUST have a value 1. | component | [Multipart-6B] [Multipart-7B] | |
| 1 | MultipartStyle-2061 | The localPart of the element's QName MUST be the same as the Interface Operation component's name. | component | [Multipart-8B] | |
| 1 | MultipartStyle-2062 | The complex type that defines the body of the element or its children elements MUST NOT contain any attributes. | component | [Multipart-9B] | |
| 1 | MultipartStyle-2063 | The sequence MUST NOT contain multiple children element declared with the same local name. | component | [Multipart-10B] | |
| 0 | NodeIdentity-2001 | A node MAY be accessible via more than one physical address or transport. | exchange | ||
| 0 | NoFaults-2011 | When the No Faults propagation rule is in effect, faults MUST NOT be propagated. | exchange | ||
| 0 | OperationSafety-2027 | However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.4 of . | component | ||
| 0 | OperationSafety-2028 | An OPTIONAL safeattribute information item with the following Infoset properties: | document | ||
| 7 | QName-resolution-1064 | A Description component MUST NOT have such broken references. | document | [Schema-3B] [Schema-4B] [Schema-5B] [Service-12B] [Service-13B] [Service-1B] [Service-2B] | |
| 0 | RobustInOnlyComposition-2013 | The robust-in-only message exchange pattern consists of exactly one message as follows: | component | ||
| 0 | RobustInOnlyFaults-2014 | The robust in-only message exchange pattern uses the rule . | exchange | ||
| 1 | RPCStyle-2029 | If 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] | |
| 2 | RPCStyle-2030 | The 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] | |
| 1 | RPCStyle-2031 | The 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] | |
| 1 | RPCStyle-2032 | The input sequence MUST only contain elements and element wildcards. | component | [RPC-4B] | |
| 1 | RPCStyle-2033 | The input sequence MUST NOT contain more than one element wildcard. | component | [RPC-5B] | |
| 1 | RPCStyle-2034 | The element wildcard, if present, MUST appear after any elements. | component | [RPC-6B] | |
| 1 | RPCStyle-2035 | The output sequence MUST only contain elements. | component | [RPC-7B] | |
| 1 | RPCStyle-2036 | Both the input and output sequences MUST contain only local element children. | component | [RPC-8B] | |
| 1 | RPCStyle-2037 | The local name of input element's QName MUST be the same as the Interface Operation component's name. | component | [RPC-9B] | |
| 1 | RPCStyle-2038 | Input and output elements MUST both be in the same namespace. | component | [RPC-14B] | |
| 2 | RPCStyle-2039 | The complex type that defines the body of an input or an output element MUST NOT contain any local attributes. | component | [RPC-10B] [RPC-11B] | |
| 1 | RPCStyle-2040 | If 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] | |
| 2 | RPCStyle-2041 | The input or output sequence MUST NOT contain multiple children elements declared with the same name. | component | [RPC-12B] [RPC-13B] | |
| 3 | Schema-1066 | A 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] | |
| 1 | Schema-1069 | The referenced schema MUST contain a targetNamespaceattribute information item on its xs:schemaelement information item. | document | [Schema-1B] | |
| 2 | Schema-1070 | The 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] | |
| 2 | Schema-1073 | A WSDL 2.0 document MUST NOT define the same element or type in more than one inlined schema. | document | [Schema-6B] [Schema-7B] | |
| 0 | Schema-1075 | A specification of extension syntax for an alternative schema language MUST use a namespace that is different than the namespace of XML Schema. | document | ||
| 0 | Schema-1076 | The namespace used for an alternate schema language MUST be an absolute IRI. | document | ||
| 1 | Schema-1079 | If 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] | |
| 1 | Service-1060 | For each Service component in the services property of a Description component, the name property MUST be unique. | component | [Service-3B] | |
| 0 | SOAP12Binding-SOAPDetail-2081 | If 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 | ||
| 0 | SOAPAction-2075 | A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component. | component | ||
| 0 | SOAPBinding-2065 | When 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 | ||
| 0 | SOAPBinding-2066 | If the value is #none, then the payload MUST be empty. | message | ||
| 0 | SOAPBinding-2067 | If 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 | ||
| 0 | SOAPBinding-2068 | If 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 | ||
| 0 | SOAPBinding-2069 | Every SOAP binding MUST indicate what version of SOAP is in use for the operations of the interface that this binding applies to. | component | ||
| 0 | SOAPBinding-2070 | Every SOAP binding MUST indicate what underlying protocol is in use. | component | ||
| 0 | SOAPBindingFault-2071 | For every Interface Fault component contained in an Interface component, a mapping to a SOAP Fault MUST be described. | component | ||
| 0 | SOAPBindingFault-2072 | when the value of the soap version is 1.2, the allowed QNames MUST be the ones defined by , section 5.4.6 | component | ||
| 0 | SOAPHeaderBlock-2077 | When 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 | ||
| 0 | SOAPHeaderBlock-2078 | If the value is true, then the SOAP header block MUST be included in the message. | component | ||
| 0 | SOAPHeaderBlock-2079 | The value of the elementattribute information item MUST resolve to a global element declaration from the element declarations property of the Description component. | component | ||
| 0 | SOAPHTTPProperties-2064 | These properties MUST NOT be used unless the underlying protocol is HTTP. | component | ||
| 0 | SOAPHTTPSelection-2082 | This 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 | ||
| 0 | SOAPMEP-2074 | A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component. | component | ||
| 0 | SOAPMEPDefault-2073 | A xs:anyURI, which is an absolute IRI as defined by , to the Binding component. | component | ||
| 0 | SOAPMEPSelection-2080 | For 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 | ||
| 0 | SOAPModule-2076 | A xs:anyURI, which is an absolute IRI as defined by . | component | ||
| 1 | Types-1007 | Each XML Schema element declaration MUST have a unique QName. | component | [Schema-6B] | |
| 1 | Types-1008 | Each XML Schema type definition MUST have a unique QName. | component | [Schema-7B] | |
| 0 | Types-1074 | A 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 | ||
| 2 | Types-1077 | The 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] | |
| 2 | Types-1078 | The 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] | |
| 0 | WRPC-2042 | OPTIONAL, but MUST be present when the style is RPC | component | ||
| 0 | WRPC-2043 | Values for the second component MUST be chosen among the following four: "#in", "#out", "#inout" "#return". | component | ||
| 1 | WRPC-2044 | The value of the first component of each pair (q, t) MUST be unique within the list. | component | [RPC-17B] | |
| 1 | WRPC-2045 | For 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] | |
| 2 | WRPC-2046 | For 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] | |
| 2 | WRPC-2047 | For 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] | |
| 2 | WRPC-2048 | For 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] | |
| 2 | WRPC-2049 | For 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] | |
| 1 | WRPC-2050 | Additionally, 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] |