ID | Chapter | Section | Description | Required | Dependency | Implementation Specific | Defined by | Status | Testable |
WSI:SPEC:R2931 | 3 | 1 |
The entity body of the root part of multipart/related MESSAGE MUST be a soap:Envelope.
| true |
| false | technology | active | true |
WSI:SPEC:R2945 | 3 | 1 |
The Content-Type HTTP header field-value in a MESSAGE MUST be either
"multipart/related" or "text/xml". | true |
| false | technology | active | true |
WSI:SPEC:R2932 | 3 | 1 |
If the Content-Type HTTP header field-value in a MESSAGE has a
media-type of "multipart/related" then the Content-Type HTTP header
field-value in that message MUST have the type parameter with a value of "text/xml".
| true |
| false | technology | active | true |
WSI:SPEC:R2915 | 3 | 2 |
The entity body of the root part of a multipart/related MESSAGE MUST be serialized using either UTF-8 or UTF-16 character encoding.
| true |
| false | technology | active | true |
WSI:SPEC:R2916 | 3 | 2 |
Non-root parts of a multipart/related MESSAGE MAY use any character encoding.
| true |
| false | technology | active | true |
WSI:SPEC:R2925 | 3 | 3 |
If the WSDL description lists at least one non-root MIME part,
the corresponding MESSAGE MUST have a Content-Type
HTTP header field-value with a media-type of "multipart/related".
| true |
| false | technology | active | true |
WSI:SPEC:R2917 | 3 | 4 |
A MESSAGE containing zero attachment parts MUST be sent using a content-type
of either "text/xml" as though a SOAP HTTP binding were used or
"multipart/related" when the WSDL description for the message specifies
the mime:multipartRelated element on the corresponding
wsdl:input or wsdl:output element in
its wsdl:binding. | true |
| false | technology | active | true |
WSI:SPEC:R2902 | 3 | 4 |
A SENDER MUST NOT send a message using SOAP with
Attachments if the corresponding wsdl:input
or wsdl:output element in the
wsdl:binding does not specify the WSDL
MIME Binding.
| true |
| false | technology | active | true |
WSI:SPEC:R2918 | 3 | 5 |
A RECEIVER MAY ignore a URI reference to an attachment in an envelope.
| true |
| false | technology | active | true |
WSI:SPEC:R2919 | 3 | 6 |
A MESSAGE MAY contain soap:Envelopes carried as attachments in
parts that are not the root part of the message.
| true |
| false | technology | active | true |
WSI:SPEC:R2920 | 3 | 7 |
An INSTANCE MAY send a fault with attachments if and only if the wsdl:output
element is described using the WSDL MIME binding.
| true |
| false | technology | active | true |
WSI:SPEC:R2933 | 3 | 8 |
If a description binds a wsdl:message part to a
mime:content element, then the corresponding MIME part's
content-id field-value in a MESSAGE MUST conform to the
content-id part encoding.
| true |
| false | technology | active | true |
WSI:SPEC:R2921 | 3 | 9 |
A RECEIVER MUST NOT infer any semantics from the ordering of non-root MIME parts in a message.
| true |
| false | technology | active | true |
WSI:SPEC:R2929 | 3 | 9 |
A MESSAGE MAY have its MIME parts in any order provided that the identity of the root part is maintained.
| true |
| false | technology | active | true |
WSI:SPEC:R2922 | 3 | 10 |
If the Content-Type HTTP header field-value in a message does not have a start parameter, a RECEIVER MUST treat the first body part of the MIME package as the root part.
| true |
| false | technology | active | true |
WSI:SPEC:R2934 | 3 | 11 |
The Content-Transfer-Encoding field of a part in a multipart/related
MESSAGE MUST have a value of "7bit", "8bit", "binary",
"quoted-printable" or "base64".
| true |
| false | technology | active | true |
WSI:SPEC:R2935 | 3 | 11 |
The encoding of the body of a part in a multipart/related MESSAGE MUST
conform to the encoding indicated by the Content-Transfer-Encoding
field-value, as specified by RFC2045. [clarification]
| true |
| false | technology | active | true |
WSI:SPEC:R2936 | 3 | 12 |
In a MESSAGE, all MIME encapsulation boundary strings MUST be preceded with the ascii
characters CR (13) and LF (10) in that sequence.
| true |
| false | technology | active | true |
WSI:SPEC:R2901 | 4 | 1 |
A DESCRIPTION MUST use either the WSDL MIME Binding as described in
WSDL 1.1 Section 5 or WSDL SOAP binding as described in WSDL 1.1
Section 3 on each of the wsdl:input or wsdl:output elements of a wsdl:binding.
| true |
| false | technology | active | true |
WSI:SPEC:R2941 | 4 | 2 |
A wsdl:binding in a DESCRIPTION SHOULD bind every wsdl:part of a
wsdl:message in the wsdl:portType to which it refers to one of
soapbind:body, soapbind:header, soapbind:fault
, soapbind:headerfault, or mime:content | true |
| false | technology | active | true |
WSI:SPEC:R2903 | 4 | 3 |
A mime:content element in a DESCRIPTION MUST NOT reference a wsdl:part that is not present in the respective wsdl:input or wsdl:output of the corresponding wsdl:operation of the corresponding wsdl:portType..
| true |
| false | technology | active | true |
WSI:SPEC:R2904 | 4 | 3 |
A mime:content element in a DESCRIPTION MUST NOT be bound to a sub-component of an element or type referenced by a wsdl:part.
| true |
| false | technology | active | true |
WSI:SPEC:R2946 | 4 | 3 |
In a DESCRIPTION, a mime:content element MUST include the part attribute.
| true |
| false | technology | active | true |
WSI:SPEC:R2940 | 4 | 4 |
In a DESCRIPTION, a wsdl:part defined with the ref:swaRef
schema type SHOULD only be bound to a soapbind:body, or a
soapbind:header in a MIME binding.
| true |
| false | technology | active | true |
WSI:SPEC:R2928 | 4 | 4 |
In an ENVELOPE, a URI reference that is typed using the ref:swaRef
schema type MUST resolve to a MIME part in the same message as the envelope.
| true |
| false | technology | active | true |
WSI:SPEC:R2911 | 4 | 5 |
A mime:multipartRelated element in a DESCRIPTION MUST contain exactly one mime:part element, amongst its child mime:part elements, containing a soapbind:body child.
| true |
| false | technology | active | true |
WSI:SPEC:R2905 | 4 | 6 |
The soapbind:header element in a DESCRIPTION MAY be included as a child of the mime:part element.
| true |
| false | technology | active | true |
WSI:SPEC:R2906 | 4 | 6 |
A soapbind:header element in a DESCRIPTION MUST NOT be included in a mime:part that is not the root part, containing the soapbind:body element.
| true |
| false | technology | active | true |
WSI:SPEC:R2907 | 4 | 7 |
MIME parts in a DESCRIPTION MUST be defined using an element with a local name of part in the namespace of the WSDL MIME Binding extension.
| true |
| false | technology | active | true |
WSI:SPEC:R2908 | 4 | 7 |
The mime:part element in a DESCRIPTION MUST NOT have a name attribute.
| true |
| false | technology | active | true |
WSI:SPEC:R2909 | 4 | 8 |
Multiple mime:content child elements of a mime:part element in a DESCRIPTION MUST reference the same wsdl:part.
| true |
| false | technology | active | true |
WSI:SPEC:R2910 | 4 | 9 |
A mime:content in a DESCRIPTION MUST reference a wsdl:part that is defined using either the type attribute or the element attribute.
| true |
| false | technology | active | true |
WSI:SPEC:R2942 | 4 | 9 |
In a MESSAGE, a message part bound to a mime:content that refers to global element declaration (via the element attribute of the wsdl:part
element) MUST be serialized within the MIME part as a serialization of
an XML infoset whose root element is described by the referenced
element. | true |
| false | technology | active | true |
WSI:SPEC:R2943 | 4 | 9 |
In a DESCRIPTION, if a message part is bound to a mime:content that refers
to a type (via the type attribute of the wsdl:part element), then the value
of that type attribute MUST be ignored in favor of media type of the type attribute of
the mime:content element.
| true |
| false | technology | active | true |
WSI:SPEC:R2944 | 4 | 9 |
In a DESCRIPTION, if a wsdl:part element refers to a global element declaration (via the element attribute of the wsdl:part element) then the value of the type attribute of a mime:content element that binds that part MUST be a content type suitable for carrying an XML serialization.
| true |
| false | technology | active | true |
WSI:SPEC:R2912 | 4 | 10 |
A RECEIVER MUST NOT assume that the order of mime:part elements specified in a WSDL description is the same as the order of MIME parts in the message.
| true |
| false | technology | active | true |
WSI:SPEC:R2947 | 4 | 10 |
In a DESRIPTION, a mime:part element that contains a soapbind:body child element MAY appear in any position amongst the other child elements of a mime:multipartRelated element.
| true |
| false | technology | active | true |
WSI:SPEC:R2913 | 4 | 11 |
A Fault MESSAGE MAY be serialized as either text/xml or
multipart/related, if the wsdl:output child element of the corresponding
binding operation in a description has a child mime:multipartRelated
element.
| true |
| false | technology | active | true |
WSI:SPEC:R2930 | 4 | 12 |
A wsdl:fault element in a DESCRIPTION MUST NOT have mime:multipartRelated element as its child element.
| true |
| false | technology | active | true |
WSI:SPEC:R2923 | 4 | 13 |
A SENDER MAY send non-root MIME parts not described in the
WSDL MIME binding.
| true |
| false | technology | active | true |
WSI:SPEC:R2926 | 4 | 13 |
A MESSAGE MUST include all of the MIME parts described by its WSDL MIME binding.
| true |
| false | technology | active | true |
WSI:SPEC:R2927 | 4 | 14 |
The root part of a MESSAGE MUST be conformant with all the
requirements for an envelope in version 1.1 of the Basic Profile.
| true |
| false | technology | active | true |