ID | Chapter | Section | Description | Required | Dependency | Implementation Specific | Defined by | Status | Testable |
WSI:SPEC:R9980 | 3 | 1.1 | An ENVELOPE MUST conform to the structure
specified in SOAP 1.1 Section 4, "SOAP Envelope" (subject to
amendment by the Profile). | true |
| false | technology | active | true |
WSI:SPEC:R1015 | 3 | 1.2 | A RECEIVER MUST generate a fault if they
encounter an envelope whose document element is not
soap:Envelope. | true |
| false | technology | active | true |
WSI:SPEC:R1014 | 3 | 1.3 | The children of the soap:Body
element in an ENVELOPE MUST be namespace qualified. | true |
| false | technology | active | true |
WSI:SPEC:R1008 | 3 | 1.4 | An ENVELOPE MUST NOT contain a Document
Type Declaration. | true |
| false | technology | active | true |
WSI:SPEC:R1009 | 3 | 1.4 | An ENVELOPE MUST NOT contain Processing
Instructions. | true |
| false | technology | active | true |
WSI:SPEC:R1033 | 3 | 1.4 | An ENVELOPE SHOULD NOT contain the
namespace declaration
xmlns:xml="http://www.w3.org/XML/1998/namespace". | true |
| false | technology | active | true |
WSI:SPEC:R1034 | 3 | 1.4 | A DESCRIPTION SHOULD NOT contain the
namespace declaration
xmlns:xml="http://www.w3.org/XML/1998/namespace". | true |
| false | technology | active | true |
WSI:SPEC:R1011 | 3 | 1.5 | An ENVELOPE MUST NOT have any element
children of soap:Envelope following the
soap:Body element. | true |
| false | technology | active | true |
WSI:SPEC:R1005 | 3 | 1.6 | An ENVELOPE MUST NOT contain
soap:encodingStyle attributes on any of the elements
whose namespace name is
"http://schemas.xmlsoap.org/soap/envelope/". | true |
| false | technology | active | true |
WSI:SPEC:R1006 | 3 | 1.6 | An ENVELOPE MUST NOT contain
soap:encodingStyle attributes on any element that is a
child of soap:Body. | true |
| false | technology | active | true |
WSI:SPEC:R1007 | 3 | 1.6 | An ENVELOPE described in an rpc-literal
binding MUST NOT contain soap:encodingStyle attribute
on any element that is a grandchild of soap:Body. | true |
| false | technology | active | true |
WSI:SPEC:R1013 | 3 | 1.7 | An ENVELOPE containing a
soap:mustUnderstand attribute MUST only use the
lexical forms "0" and "1". | true |
| false | technology | active | true |
WSI:SPEC:R1017 | 3 | 1.8 | A RECEIVER MUST NOT mandate the use of the
xsi:type attribute in envelopes except as required in
order to indicate a derived type (see XML Schema Part 1:
Structures, Section 2.6.1). | true |
| false | technology | active | true |
WSI:SPEC:R1032 | 3 | 1.9 | The soap:Envelope,
soap:Header, and soap:Body elements in an
ENVELOPE MUST NOT have attributes in the namespace
"http://schemas.xmlsoap.org/soap/envelope/". | true |
| false | technology | active | true |
WSI:SPEC:R1025 | 3 | 2.1 | A RECEIVER MUST handle envelopes in such a
way that it appears that all checking of mandatory header blocks is
performed before any actual processing. SOAP12 | true |
| false | technology | active | true |
WSI:SPEC:R1027 | 3 | 2.2 | A RECEIVER MUST generate a
"soap:MustUnderstand" fault when an envelope contains a mandatory
header block (i.e., one that has a soap:mustUnderstand
attribute with the value "1") targeted at the receiver (via
soap:actor) that the receiver does not
understand.SOAP12 | true |
| false | technology | active | true |
WSI:SPEC:R1028 | 3 | 2.3 | When a fault is generated by a RECEIVER,
further processing SHOULD NOT be performed on the SOAP envelope
aside from that which is necessary to rollback, or compensate for,
any effects of processing the envelope prior to the generation of
the fault. SOAP12 | true |
| false | technology | active | true |
WSI:SPEC:R1029 | 3 | 2.3 | Where the normal outcome of processing a
SOAP envelope would have resulted in the transmission of a SOAP
response, but rather a fault is generated instead, a RECEIVER MUST
transmit a fault in place of the response. SOAP12 | true |
| false | technology | active | true |
WSI:SPEC:R1030 | 3 | 2.3 | A RECEIVER that generates a fault SHOULD
notify the end user that a fault has been generated when practical,
by whatever means is deemed appropriate to the circumstance.
SOAP12 | true |
| false | technology | active | true |
WSI:SPEC:R1107 | 3 | 3.1 | A RECEIVER MUST interpret a SOAP message
as a Fault when the soap:Body of the message has a
single soap:Fault child. | true |
| false | technology | active | true |
WSI:SPEC:R1000 | 3 | 3.2 | When an ENVELOPE is a Fault, the
soap:Fault element MUST NOT have element children
other than faultcode, faultstring,
faultactor and detail. | true |
| false | technology | active | true |
WSI:SPEC:R1001 | 3 | 3.3 | When an ENVELOPE is a Fault, the element
children of the soap:Fault element MUST be
unqualified. | true |
| false | technology | active | true |
WSI:SPEC:R1002 | 3 | 3.4 | A RECEIVER MUST accept faults that have
any number of elements, including zero, appearing as children of
the detail element. Such children can be qualified or
unqualified. | true |
| false | technology | active | true |
WSI:SPEC:R1003 | 3 | 3.4 | A RECEIVER MUST accept faults that have
any number of qualified or unqualified attributes, including zero,
appearing on the detail element. The namespace of
qualified attributes can be anything other than
"http://schemas.xmlsoap.org/soap/envelope/". | true |
| false | technology | active | true |
WSI:SPEC:R1016 | 3 | 3.5 | A RECEIVER MUST accept faults that carry
an xml:lang attribute on the faultstring
element. | true |
| false | technology | active | true |
WSI:SPEC:R1004 | 3 | 3.6 | When an ENVELOPE contains a
faultcode element, the content of that element SHOULD
be either one of the fault codes defined in SOAP 1.1 (supplying
additional information if necessary in the detail
element), or a Qname whose namespace is controlled by the fault's
specifying authority (in that order of preference). | true |
| false | technology | active | true |
WSI:SPEC:R1031 | 3 | 3.6 | When an ENVELOPE contains a
faultcode element the content of that element SHOULD
NOT use of the SOAP 1.1 "dot" notation to refine the meaning of the
fault. | true |
| false | technology | active | true |
WSI:SPEC:R1141 | 3 | 4.1 | A MESSAGE MUST be sent using either
HTTP/1.1 or HTTP/1.0. | true |
| false | technology | active | true |
WSI:SPEC:R1140 | 3 | 4.1 | A MESSAGE SHOULD be sent using
HTTP/1.1. | true |
| false | technology | active | true |
WSI:SPEC:R1132 | 3 | 4.2 | A HTTP request MESSAGE MUST use the HTTP
POST method. | true |
| false | technology | active | true |
WSI:SPEC:R1108 | 3 | 4.2 | A MESSAGE MUST NOT use the HTTP Extension
Framework (RFC2774). | true |
| false | technology | active | true |
WSI:SPEC:R1109 | 3 | 4.3 | The value of the SOAPAction
HTTP header field in a HTTP request MESSAGE MUST be a quoted
string. | true |
| false | technology | active | true |
WSI:SPEC:R1119 | 3 | 4.3 | A RECEIVER MAY respond with a fault if the
value of the SOAPAction HTTP header field in a message
is not quoted. | true |
| false | technology | active | true |
WSI:SPEC:R1127 | 3 | 4.3 | A RECEIVER MUST NOT rely on the value of
the SOAPAction HTTP header to correctly process the
message.SOAP12 | true |
| false | technology | active | true |
WSI:SPEC:R1124 | 3 | 4.4 | An INSTANCE MUST use a 2xx HTTP status
code on a response message that indicates the successful outcome of
a HTTP request. | true |
| false | technology | active | true |
WSI:SPEC:R1111 | 3 | 4.4 | An INSTANCE SHOULD use a "200 OK" HTTP
status code on a response message that contains an envelope that is
not a fault. | true |
| false | technology | active | true |
WSI:SPEC:R1112 | 3 | 4.4 | An INSTANCE SHOULD use either a "200 OK"
or "202 Accepted" HTTP status code for a response message that does
not contain a SOAP envelope but indicates the successful outcome of
a HTTP request. | true |
| false | technology | active | true |
WSI:SPEC:R1130 | 3 | 4.5 | An INSTANCE MUST use the "307 Temporary
Redirect" HTTP status code when redirecting a request to a
different endpoint. | true |
| false | technology | active | true |
WSI:SPEC:R1131 | 3 | 4.5 | A CONSUMER MAY automatically redirect a
request when it encounters a "307 Temporary Redirect" HTTP status
code in a response. | true |
| false | technology | active | true |
WSI:SPEC:R1125 | 3 | 4.6 | An INSTANCE MUST use a 4xx HTTP status
code for a response that indicates a problem with the format of a
request. | true |
| false | technology | active | true |
WSI:SPEC:R1113 | 3 | 4.6 | An INSTANCE SHOULD use a "400 Bad Request"
HTTP status code, if a HTTP request message is malformed. | true |
| false | technology | active | true |
WSI:SPEC:R1114 | 3 | 4.6 | An INSTANCE SHOULD use a "405 Method not
Allowed" HTTP status code if a HTTP request message's method is not
"POST". | true |
| false | technology | active | true |
WSI:SPEC:R1115 | 3 | 4.6 | An INSTANCE SHOULD use a "415 Unsupported
Media Type" HTTP status code if a HTTP request message's
Content-Type header field-value is not permitted by its WSDL
description. | true |
| false | technology | active | true |
WSI:SPEC:R1126 | 3 | 4.7 | An INSTANCE MUST return a "500 Internal
Server Error" HTTP status code if the response envelope is a
Fault. | true |
| false | technology | active | true |
WSI:SPEC:R1120 | 3 | 4.8 | An INSTANCE MAY use the HTTP state
mechanism ("Cookies"). | true |
| false | technology | active | true |
WSI:SPEC:R1122 | 3 | 4.8 | An INSTANCE using Cookies SHOULD conform
to RFC2965. | true |
| false | technology | active | true |
WSI:SPEC:R1121 | 3 | 4.8 | An INSTANCE SHOULD NOT require consumer
support for Cookies in order to function correctly. | true |
| false | technology | active | true |
WSI:SPEC:R1123 | 3 | 4.8 | The value of the cookie MUST be considered
to be opaque by the CONSUMER. | true |
| false | technology | active | true |
WSI:SPEC:R0001 | 4 | 1 | Either an INSTANCE's WSDL 1.1 description,
its UDDI binding template, or both MUST be available to an
authorized consumer upon request. | true |
| false | technology | active | true |
WSI:SPEC:R2028 | 4 | 2.1 | A DESCRIPTION using the WSDL namespace
(prefixed "wsdl" in this Profile) MUST be valid according to the
XML Schema found at
"http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd". | true |
| false | technology | active | true |
WSI:SPEC:R2029 | 4 | 2.1 | A DESCRIPTION using the WSDL SOAP binding
namespace (prefixed "soapbind" in this Profile) MUST be valid
according to the XML Schema found at
"http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.xsd". | true |
| false | technology | active | true |
WSI:SPEC:R2001 | 4 | 2.2 | A DESCRIPTION MUST only use the WSDL
"import" statement to import another WSDL description. | true |
| false | technology | active | true |
WSI:SPEC:R2803 | 4 | 2.2 | In a DESCRIPTION, the namespace attribute
of the wsdl:import MUST NOT be a relative URI. | true |
| false | technology | active | true |
WSI:SPEC:R2002 | 4 | 2.2 | To import XML Schema Definitions, a
DESCRIPTION MUST use the XML Schema "import" statement. | true |
| false | technology | active | true |
WSI:SPEC:R2003 | 4 | 2.2 | A DESCRIPTION MUST use the XML Schema
"import" statement only within the xsd:schema element
of the types section. | true |
| false | technology | active | true |
WSI:SPEC:R2004 | 4 | 2.2 | In a DESCRIPTION the schemaLocation
attribute of an xsd:import element MUST NOT resolve to any document
whose root element is not "schema" from the namespace
"http://www.w3.org/2001/XMLSchema". | true |
| false | technology | active | true |
WSI:SPEC:R2009 | 4 | 2.2 | An XML Schema directly or indirectly
imported by a DESCRIPTION MAY include the Unicode Byte Order Mark
(BOM). | true |
| false | technology | active | true |
WSI:SPEC:R2010 | 4 | 2.2 | An XML Schema directly or indirectly
imported by a DESCRIPTION MUST use either UTF-8 or UTF-16
encoding. | true |
| false | technology | active | true |
WSI:SPEC:R2011 | 4 | 2.2 | An XML Schema directly or indirectly
imported by a DESCRIPTION MUST use version 1.0 of the eXtensible
Markup Language W3C Recommendation. | true |
| false | technology | active | true |
WSI:SPEC:R2007 | 4 | 2.3 | A DESCRIPTION MUST specify a non-empty
location attribute on the wsdl:import
element. | true |
| false | technology | active | true |
WSI:SPEC:R2008 | 4 | 2.4 | A CONSUMER MAY, but need not, retrieve a
WSDL description from the URI specified in the location attribute
on a wsdl:import element. | true |
| false | technology | active | true |
WSI:SPEC:R2022 | 4 | 2.5 | When they appear in a DESCRIPTION,
wsdl:import elements MUST precede all other elements
from the WSDL namespace except wsdl:documentation. | true |
| false | technology | active | true |
WSI:SPEC:R2023 | 4 | 2.5 | When they appear in a DESCRIPTION,
wsdl:types elements MUST precede all other elements
from the WSDL namespace except wsdl:documentation and
wsdl:import. | true |
| false | technology | active | true |
WSI:SPEC:R4004 | 4 | 2.6 | A DESCRIPTION MUST use version 1.0 of the
eXtensible Markup Language W3C Recommendation. | true |
| false | technology | active | true |
WSI:SPEC:R4005 | 4 | 2.7 | A DESCRIPTION SHOULD NOT contain the
namespace declaration
xmlns:xml="http://www.w3.org/XML/1998/namespace". | true |
| false | technology | active | true |
WSI:SPEC:R4002 | 4 | 2.8 | A DESCRIPTION MAY include the Unicode Byte
Order Mark (BOM). | true |
| false | technology | active | true |
WSI:SPEC:R4003 | 4 | 2.9 | A DESCRIPTION MUST use either UTF-8 or
UTF-16 encoding. | true |
| false | technology | active | true |
WSI:SPEC:R2005 | 4 | 2.10 | The targetNamespace attribute
on the wsdl:definitions element of a description that
is being imported MUST have same the value as the
namespace attribute on the wsdl:import
element in the importing DESCRIPTION. | true |
| false | technology | active | true |
WSI:SPEC:R2030 | 4 | 2.11 | In a DESCRIPTION the wsdl:documentation
element MAY be present as the first child element of wsdl:import,
wsdl:part and wsdl:definitions in addition to the elements cited in
the WSDL1.1 specification.WSDL20 | true |
| false | technology | active | true |
WSI:SPEC:R2025 | 4 | 2.12 | A DESCRIPTION containing WSDL extensions
MUST NOT use them to contradict other requirements of the
Profile. | true |
| false | technology | active | true |
WSI:SPEC:R2026 | 4 | 2.12 | A DESCRIPTION SHOULD NOT include extension
elements with a wsdl:required attribute value of
"true" on any WSDL construct (wsdl:binding,
wsdl:portType, wsdl:message,
wsdl:types or wsdl:import) that claims
conformance to the Profile. | true |
| false | technology | active | true |
WSI:SPEC:R2027 | 4 | 2.12 | If during the processing of a description,
a consumer encounters a WSDL extension element that has a
wsdl:required attribute with a boolean value of "true"
that the consumer does not understand or cannot process, the
CONSUMER MUST fail processing. | true |
| false | technology | active | true |
WSI:SPEC:R2101 | 4 | 3.1 | A DESCRIPTION MUST NOT use QName
references to WSDL components in namespaces that have been neither
imported, nor defined in the referring WSDL document. | true |
| false | technology | active | true |
WSI:SPEC:R2102 | 4 | 3.1 | A QName reference to a Schema component in
a DESCRIPTION MUST use the namespace defined in the
targetNamespace attribute on the
xsd:schema element, or to a namespace defined in the
namespace attribute on an xsd:import
element within the xsd:schema element. | true |
| false | technology | active | true |
WSI:SPEC:R2105 | 4 | 3.2 | All xsd:schema elements
contained in a wsdl:types element of a DESCRIPTION
MUST have a targetNamespace attribute with a valid and
non-null value, UNLESS the xsd:schema element has
xsd:import and/or xsd:annotation as its
only child element(s). | true |
| false | technology | active | true |
WSI:SPEC:R2110 | 4 | 3.3 | In a DESCRIPTION, declarations MUST NOT
extend or restrict the soapenc:Array type. | true |
| false | technology | active | true |
WSI:SPEC:R2111 | 4 | 3.3 | In a DESCRIPTION, declarations MUST NOT
use wsdl:arrayType attribute in the type declaration. | true |
| false | technology | active | true |
WSI:SPEC:R2112 | 4 | 3.3 | In a DESCRIPTION, elements SHOULD NOT be
named using the convention ArrayOfXXX. | true |
| false | technology | active | true |
WSI:SPEC:R2113 | 4 | 3.3 | An ENVELOPE MUST NOT include the
soapenc:arrayType attribute. | true |
| false | technology | active | true |
WSI:SPEC:R2114 | 4 | 3.4 | The target namespace for WSDL definitions
and the target namespace for schema definitions in a DESCRIPTION
MAY be the same.WSDL20 | true |
| false | technology | active | true |
WSI:SPEC:R2201 | 4 | 4.1 | A document-literal binding in a
DESCRIPTION MUST, in each of its soapbind:body
element(s), have at most one part listed in the parts
attribute, if the parts attribute is specified. | true |
| false | technology | active | true |
WSI:SPEC:R2209 | 4 | 4.1 | A wsdl:binding in a
DESCRIPTION SHOULD bind every wsdl:part of a
wsdl:message in the wsdl:portType to
which it refers with a binding extension element. | true |
| false | technology | active | true |
WSI:SPEC:R2210 | 4 | 4.1 | If a document-literal binding in a
DESCRIPTION does not specify the parts attribute on a
soapbind:body element, the corresponding abstract
wsdl:message MUST define zero or one
wsdl:parts. | true |
| false | technology | active | true |
WSI:SPEC:R2202 | 4 | 4.1 | A wsdl:binding in a
DESCRIPTION MAY contain soapbind:body element(s) that
specify that zero parts form the soap:Body. | true |
| false | technology | active | true |
WSI:SPEC:R2203 | 4 | 4.1 | An rpc-literal binding in a DESCRIPTION
MUST refer, in its soapbind:body element(s), only to
wsdl:part element(s) that have been defined using the
type attribute. | true |
| false | technology | active | true |
WSI:SPEC:R2211 | 4 | 4.1 | An ENVELOPE described with an rpc-literal
binding MUST NOT have the xsi:nil attribute with a
value of "1" or "true" on the part accessors. | true |
| false | technology | active | true |
WSI:SPEC:R2207 | 4 | 4.1 | A wsdl:message in a
DESCRIPTION MAY contain wsdl:parts that use the
elements attribute provided those
wsdl:parts are not referred to by a
soapbind:body in an rpc-literal binding. | true |
| false | technology | active | true |
WSI:SPEC:R2204 | 4 | 4.1 | A document-literal binding in a
DESCRIPTION MUST refer, in each of its soapbind:body
element(s), only to wsdl:part element(s) that have
been defined using the element attribute. | true |
| false | technology | active | true |
WSI:SPEC:R2208 | 4 | 4.1 | A binding in a DESCRIPTION MAY contain
soapbind:header element(s) that refer to
wsdl:parts in the same wsdl:message that
are referred to by its soapbind:body element(s). | true |
| false | technology | active | true |
WSI:SPEC:R2212 | 4 | 4.1 | An ENVELOPE MUST contain exactly one part
accessor element for each of the wsdl:part elements
bound to the envelope's corresponding soapbind:body
element. | true |
| false | technology | active | true |
WSI:SPEC:R2213 | 4 | 4.1 | In a doc-literal description where the
value of the parts attribute of soapbind:body is an empty string,
the corresponding ENVELOPE MUST have no element content in the
soap:Body element. | true |
| false | technology | active | true |
WSI:SPEC:R2214 | 4 | 4.1 | In a rpc-literal description where the
value of the parts attribute of soapbind:body is an empty string,
the corresponding ENVELOPE MUST have no part accessor elements. | true |
| false | technology | active | true |
WSI:SPEC:R2205 | 4 | 4.2 | A wsdl:binding in a
DESCRIPTION MUST refer, in each of its
soapbind:header, soapbind:headerfault and
soapbind:fault elements, only to
wsdl:part element(s) that have been defined using the
element attribute. | true |
| false | technology | active | true |
WSI:SPEC:R2206 | 4 | 4.3 | A wsdl:message in a
DESCRIPTION containing a wsdl:part that uses the
element attribute MUST refer, in that attribute, to a
global element declaration. | true |
| false | technology | active | true |
WSI:SPEC:R2301 | 4 | 5.1 | The order of the elements in the
soap:body of an ENVELOPE MUST be the same as that of
the wsdl:parts in the wsdl:message that
describes it. | true |
| false | technology | active | true |
WSI:SPEC:R2302 | 4 | 5.1 | A DESCRIPTION MAY use the
parameterOrder attribute of an
wsdl:operation element to indicate the return value
and method signatures as a hint to code generators. | true |
| false | technology | active | true |
WSI:SPEC:R2303 | 4 | 5.2 | A DESCRIPTION MUST NOT use
Solicit-Response and Notification type operations in a
wsdl:portType definition. | true |
| false | technology | active | true |
WSI:SPEC:R2304 | 4 | 5.3 | A wsdl:portType in a
DESCRIPTION MUST have operations with distinct values for their
name attributes. | true |
| false | technology | active | true |
WSI:SPEC:R2305 | 4 | 5.4 | A wsdl:operation element
child of a wsdl:portType element in a DESCRIPTION MUST
be constructed so that the parameterOrder attribute,
if present, omits at most 1 wsdl:part from the output
message. | true |
| false | technology | active | true |
WSI:SPEC:R2306 | 4 | 5.5 | A wsdl:message in a
DESCRIPTION MUST NOT specify both type and
element attributes on the same
wsdl:part. | true |
| false | technology | active | true |
WSI:SPEC:R2401 | 4 | 6.1 | A wsdl:binding element in a
DESCRIPTION MUST use WSDL SOAP Binding as defined in WSDL 1.1
Section 3. | true |
| false | technology | active | true |
WSI:SPEC:R2701 | 4 | 7.1 | The wsdl:binding element in a
DESCRIPTION MUST be constructed so that its
soapbind:binding child element specifies the
transport attribute. | true |
| false | technology | active | true |
WSI:SPEC:R2702 | 4 | 7.2 | A wsdl:binding element in a
DESCRIPTION MUST specify the HTTP transport protocol with SOAP
binding. Specifically, the transport attribute of its
soapbind:binding child MUST have the value
"http://schemas.xmlsoap.org/soap/http". | true |
| false | technology | active | true |
WSI:SPEC:R2705 | 4 | 7.3 | A wsdl:binding in a
DESCRIPTION MUST either be a rpc-literal binding or a
document-literal binding. | true |
| false | technology | active | true |
WSI:SPEC:R2706 | 4 | 7.4 | A wsdl:binding in a
DESCRIPTION MUST use the value of "literal" for the
use attribute in all soapbind:body,
soapbind:fault, soapbind:header and
soapbind:headerfault elements. | true |
| false | technology | active | true |
WSI:SPEC:R2709 | 4 | 7.5 | A wsdl:portType in a
DESCRIPTION MAY have zero or more wsdl:bindings that
refer to it, defined in the same or other WSDL documents. | true |
| false | technology | active | true |
WSI:SPEC:R2710 | 4 | 7.6 | The operations in a
wsdl:binding in a DESCRIPTION MUST result in operation
signatures that are different from one another. | true |
| false | technology | active | true |
WSI:SPEC:R2711 | 4 | 7.7 | A DESCRIPTION SHOULD NOT have more than
one wsdl:port with the same value for the
location attribute of the
soapbind:address element. | true |
| false | technology | active | true |
WSI:SPEC:R2712 | 4 | 7.8 | A document-literal binding MUST be
serialized as an ENVELOPE with a soap:Body whose child
element is an instance of the global element declaration referenced
by the corresponding wsdl:message part. | true |
| false | technology | active | true |
WSI:SPEC:R2714 | 4 | 7.9 | For one-way operations, an INSTANCE MUST
NOT return a HTTP response that contains an envelope. Specifically,
the HTTP response entity-body must be empty. | true |
| false | technology | active | true |
WSI:SPEC:R2750 | 4 | 7.9 | A CONSUMER MUST ignore an envelope carried
in a HTTP response message in a one-way operation. | true |
| false | technology | active | true |
WSI:SPEC:R2727 | 4 | 7.9 | For one-way operations, a CONSUMER MUST
NOT interpret a successful HTTP response status code (i.e., 2xx) to
mean the message is valid or that the receiver would process
it. | true |
| false | technology | active | true |
WSI:SPEC:R2716 | 4 | 7.10 | A document-literal binding in a
DESCRIPTION MUST NOT have the namespace attribute
specified on contained soapbind:body,
soapbind:header, soapbind:headerfault and
soapbind:fault elements. | true |
| false | technology | active | true |
WSI:SPEC:R2717 | 4 | 7.10 | An rpc-literal binding in a DESCRIPTION
MUST have the namespace attribute specified, the value
of which MUST be an absolute URI, on contained
soapbind:body elements. | true |
| false | technology | active | true |
WSI:SPEC:R2726 | 4 | 7.10 | An rpc-literal binding in a DESCRIPTION
MUST NOT have the namespace attribute specified on
contained soapbind:header,
soapbind:headerfault and soapbind:fault
elements. | true |
| false | technology | active | true |
WSI:SPEC:R2718 | 4 | 7.11 | A wsdl:binding in a
DESCRIPTION MUST have the same set of wsdl:operations
as the wsdl:portType to which it refers. | true |
| false | technology | active | true |
WSI:SPEC:R2719 | 4 | 7.12 | A wsdl:binding in a
DESCRIPTION MAY contain no soapbind:headerfault
elements if there are no known header faults. | true |
| false | technology | active | true |
WSI:SPEC:R2740 | 4 | 7.13 | A wsdl:binding in a
DESCRIPTION SHOULD contain a soapbind:fault describing
each known fault. | true |
| false | technology | active | true |
WSI:SPEC:R2741 | 4 | 7.13 | A wsdl:binding in a
DESCRIPTION SHOULD contain a soapbind:headerfault
describing each known header fault. | true |
| false | technology | active | true |
WSI:SPEC:R2742 | 4 | 7.13 | An ENVELOPE MAY contain fault with a
detail element that is not described by a
soapbind:fault element in the corresponding WSDL
description. | true |
| false | technology | active | true |
WSI:SPEC:R2743 | 4 | 7.13 | An ENVELOPE MAY contain the details of a
header processing related fault in a SOAP header block that is not
described by a soapbind:headerfault element in the
corresponding WSDL description. | true |
| false | technology | active | true |
WSI:SPEC:R2720 | 4 | 7.14 | A wsdl:binding in a
DESCRIPTION MUST use the part attribute with a schema
type of "NMTOKEN" on all contained soapbind:header and
soapbind:headerfault elements. | true |
| false | technology | active | true |
WSI:SPEC:R2749 | 4 | 7.14 | A wsdl:binding in a
DESCRIPTION MUST NOT use the parts attribute on
contained soapbind:header and
soapbind:headerfault elements. | true |
| false | technology | active | true |
WSI:SPEC:R2721 | 4 | 7.15 | A wsdl:binding in a
DESCRIPTION MUST have the name attribute specified on
all contained soapbind:fault elements. | true |
| false | technology | active | true |
WSI:SPEC:R2754 | 4 | 7.15 | In a DESCRIPTION, the value of the
name attribute on a soapbind:fault
element MUST match the value of the name attribute on
its parent wsdl:fault element. | true |
| false | technology | active | true |
WSI:SPEC:R2722 | 4 | 7.16 | A wsdl:binding in a
DESCRIPTION MAY specify the use attribute on contained
soapbind:fault elements. | true |
| false | technology | active | true |
WSI:SPEC:R2723 | 4 | 7.16 | If in a wsdl:binding in a
DESCRIPTION the use attribute on a contained
soapbind:fault element is present, its value MUST be
"literal". | true |
| false | technology | active | true |
WSI:SPEC:R2707 | 4 | 7.17 | A wsdl:binding in a
DESCRIPTION that contains one or more soapbind:body,
soapbind:fault, soapbind:header or
soapbind:headerfault elements that do not specify the
use attribute MUST be interpreted as though the value
"literal" had been specified in each case. | true |
| false | technology | active | true |
WSI:SPEC:R2724 | 4 | 7.18 | If an INSTANCE receives an envelope that
is inconsistent with its WSDL description, it SHOULD generate a
soap:Fault with a faultcode of "Client", unless a
"MustUnderstand" or "VersionMismatch" fault is generated. | true |
| false | technology | active | true |
WSI:SPEC:R2725 | 4 | 7.18 | If an INSTANCE receives an envelope that
is inconsistent with its WSDL description, it MUST check for
"VersionMismatch", "MustUnderstand" and "Client" fault conditions
in that order. | true |
| false | technology | active | true |
WSI:SPEC:R2729 | 4 | 7.19 | An ENVELOPE described with an rpc-literal
binding that is a response MUST have a wrapper element whose name
is the corresponding wsdl:operation name suffixed with
the string "Response". | true |
| false | technology | active | true |
WSI:SPEC:R2735 | 4 | 7.20 | An ENVELOPE described with an rpc-literal
binding MUST place the part accessor elements for parameters and
return value in no namespace. | true |
| false | technology | active | true |
WSI:SPEC:R2755 | 4 | 7.20 | The part accessor elements in a MESSAGE
described with an rpc-literal binding MUST have a local name of the
same value as the name attribute of the corresponding
wsdl:part element. | true |
| false | technology | active | true |
WSI:SPEC:R2737 | 4 | 7.21 | An ENVELOPE described with an rpc-literal
binding MUST namespace qualify the descendents of part accessor
elements for the parameters and the return value, as defined by the
schema in which the part accessor types are defined. | true |
| false | technology | active | true |
WSI:SPEC:R2738 | 4 | 7.22 | An ENVELOPE MUST include all
soapbind:headers specified on a
wsdl:input or wsdl:output of a
wsdl:operation of a wsdl:binding that
describes it. | true |
| false | technology | active | true |
WSI:SPEC:R2739 | 4 | 7.23 | An ENVELOPE MAY contain SOAP header blocks
that are not described in the wsdl:binding that
describes it. | true |
| false | technology | active | true |
WSI:SPEC:R2753 | 4 | 7.23 | An ENVELOPE containing SOAP header blocks
that are not described in the appropriate wsdl:binding
MAY have the mustUnderstand attribute on such SOAP
header blocks set to '1'. | true |
| false | technology | active | true |
WSI:SPEC:R2751 | 4 | 7.24 | The order of soapbind:header
elements in soapbind:binding sections of a DESCRIPTION
MUST be considered independent of the order of SOAP header blocks
in the envelope. | true |
| false | technology | active | true |
WSI:SPEC:R2752 | 4 | 7.24 | An ENVELOPE MAY contain more than one
instance of each SOAP header block for each
soapbind:header element in the appropriate child of
soapbind:binding in the corresponding description. | true |
| false | technology | active | true |
WSI:SPEC:R2744 | 4 | 7.25 | A HTTP request MESSAGE MUST contain a
SOAPAction HTTP header field with a quoted value equal
to the value of the soapAction attribute of
soapbind:operation, if present in the corresponding
WSDL description. | true |
| false | technology | active | true |
WSI:SPEC:R2745 | 4 | 7.25 | A HTTP request MESSAGE MUST contain a
SOAPAction HTTP header field with a quoted empty
string value, if in the corresponding WSDL description, the
soapAction of soapbind:operation is
either not present, or present with an empty string as its
value. | true |
| false | technology | active | true |
WSI:SPEC:R2747 | 4 | 7.26 | A CONSUMER MUST understand and process all
WSDL 1.1 SOAP Binding extension elements, irrespective of the
presence or absence of the wsdl:required attribute on
an extension element; and irrespective of the value of the
wsdl:required attribute, when present. | true |
| false | technology | active | true |
WSI:SPEC:R2748 | 4 | 7.26 | A CONSUMER MUST NOT interpret the presence
of the wsdl:required attribute on a
soapbind extension element with a value of "false" to
mean the extension element is optional in the envelopes generated
from the WSDL description. | true |
| false | technology | active | true |
WSI:SPEC:R2800 | 4 | 8 | A DESCRIPTION MAY use any construct from
XML Schema 1.0. | true |
| false | technology | active | true |
WSI:SPEC:R2801 | 4 | 8 | A DESCRIPTION MUST use XML Schema 1.0
Recommendation as the basis of user defined datatypes and
structures. | true |
| false | technology | active | true |
WSI:SPEC:R3100 | 5 | 1 | REGDATA of type uddi:bindingTemplate representing a conformant INSTANCE MUST contain the uddi:accessPoint element. | true |
| false | technology | active | true |
WSI:SPEC:R3002 | 5 | 2 | REGDATA of type uddi:tModel representing a conformant Web service type MUST use WSDL as the description language. | true |
| false | technology | active | true |
WSI:SPEC:R3003 | 5 | 2 | REGDATA of type uddi:tModel representing a conformant Web service type MUST be categorized using the uddi:types taxonomy and a categorization of "wsdlSpec". | true |
| false | technology | active | true |
WSI:SPEC:R3010 | 5 | 2 | REGDATA of type uddi:tModel representing a conformant Web service type MUST follow V1.08 of the UDDI Best Practice for Using WSDL in a UDDI Registry. | true |
| false | technology | active | true |
WSI:SPEC:R3011 | 5 | 2 | The wsdl:binding that is referenced by REGDATA of type uddi:tModel MUST itself conform to the Profile. | true |
| false | technology | active | true |
WSI:SPEC:R5000 | 6 | 1 | An INSTANCE MAY require the use of HTTPS. | true |
| false | technology | active | true |
WSI:SPEC:R5001 | 6 | 1 | If an INSTANCE requires the use of HTTPS, the location attribute of the soapbind:address element in its wsdl:port description MUST be a URI whose scheme is "https"; otherwise it MUST be a URI whose scheme is "http". | true |
| false | technology | active | true |
WSI:SPEC:R5010 | 6 | 1 | An INSTANCE MAY require the use of HTTPS with mutual authentication. | true |
| false | technology | active | true |