Basic Profile 1.1 Test Assertions Version 1.1

Abstract

This document contains the test assertions for the WS-I Basic Profile definition. These test assertions are used by the analyzer testing tool to determine if a Web service is conformant to the Basic Profile.

A "candidate" element is one that is to be verified for conformance. The binding of the tModel if <wsi-analyzerConfig:uddiReference> is given or the <wsi-analyzerConfig:wsdlElement> in the configuration file of the Analyzer define a candidate element for verification. A verification on an element also implies that the same verification is made for all the elements that it uses. That is, the elements it uses also become candidate elements. Verification it based on the following transitivity rules, applied recursively.

For WSDL element references:

• A verification on a wsdl:port is inherited by the referenced wsdl:bindings
• A verification on a wsdl:binding is inherited by the referenced wsdl:portTypes
• A verification on a wsdl:portType is inherited by the referenced wsdl:operations
• A verification on a wsdl:operation is inherited by the referenced wsdl:messages

For UDDI references:

• A verification on a uddi:bindingTemplate is inherited by the referenced uddi:tModel
• A verification on a uddi:tModel is inherited by the referenced wsdl:binding

The analyzer specification contains a detailed explanation of all of the fields listed in this document.

Notice

The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or WS-I. The material contained herein is provided on an "AS IS" basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material and WS-I hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THIS MATERIAL.

IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR WS-I BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

Feedback

The Web Services-Interoperability Organization (WS-I) would like to receive input, suggestions and other feedback ("Feedback") on this work from a wide variety of industry participants to improve its quality over time.

By sending email, or otherwise communicating with WS-I, you (on behalf of yourself if you are an individual, and your company if you are providing Feedback on behalf of the company) will be deemed to have granted to WS-I, the members of WS-I, and other parties that have access to your Feedback, a non-exclusive, non-transferable, worldwide, perpetual, irrevocable, royalty-free license to use, disclose, copy, license, modify, sublicense or otherwise distribute and exploit in any manner whatsoever the Feedback you provide regarding the work. You acknowledge that you have no expectation of confidentiality with respect to any Feedback you provide. You represent and warrant that you have rights to provide this Feedback, and if you are providing Feedback on behalf of a company, you represent and warrant that you have the rights to provide Feedback on behalf of your company. You also acknowledge that WS-I is not required to review, discuss, use, consider or in any way incorporate your Feedback into future versions of its work. If WS-I does incorporate some or all of your Feedback in a future version of the work, it may, but is not obligated to include your name (or, if you are identified as acting on behalf of your company, the name of your company) on a list of contributors to the work. If the foregoing is not acceptable to you and any company on whose behalf you are acting, please do not provide any Feedback.

WS-I members should direct feedback on this document to wsi_testing@lists.ws-i.org; non-members should direct feedback to wsi-tools@ws-i.org.

NOTE

Test assertion headings that have this background color are disabled and will not be processed by the analyzer.

Table of Contents

Profile Definitions
Test Assertion Artifacts
discovery
description
message
envelope
Test Assertion Counts
Profile Requirements Index
Appendix A: Referenced Specifications

Profile Definitions

Test Assertion Artifacts

• discovery
• description
• message
• envelope

The Basic Profile requires support for UDDI V2.0.

Specification Reference List:

• The UDDI Version 2.04 API Published Specification, Dated 19 July 2002
• UDDI Version 2.03 Data Structure Reference, Published Specification, Dated 19 July 2002
• Version 2.0 UDDI XML Schema 2001
• V1.08 of the UDDI Best Practice for Using WSDL in a UDDI Registry

Test Assertion: BP3001

Context:
For a candidate uddi:tModel

Assertion Description:
The uddi:tModel element uses WSDL as the description language and the uddi:tModel contains a reference to a WSDL binding. The uddi:overviewDoc/uddi:overviewURL element contains a reference to a WSDL definition, which uses a namespace of http://schemas.xmlsoap.org/wsdl/. The uddi:overviewURL may use the fragment notation to resolve to a specific wsdl:binding.

Failure Message:
The uddi:tModel does not reference a WSDL based Web service definition or the uddi:tModel does not reference a wsdl:binding.

Failure Detail Description:
{tModel key}{uddi:overviewDoc}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP3002

Context:
For a candidate uddi:bindingTemplate

Assertion Description:
The uddi:bindingTemplate element contains a uddi:accessPoint element, with a non-empty value.

Failure Message:
The uddi:bindingTemplate does not contain an uddi:accessPoint element, or it is empty.

Failure Detail Description:
bindingTemplate key

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP3003

Context:
For a candidate uddi:tModel

Assertion Description:
The uddi:tModel is categorized using the uddi:types taxonomy, as "wsdlSpec": the uddi:keyedReference element has a tModelKey attribute value equal to "uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4" and a keyValue attribute value equal to "wsdlSpec".

Failure Message:
The uddi:tModel is not categorized using the uddi:types taxonomy with a categorization of "wsdlSpec".

Failure Detail Description:
{tModel key}{categoryBag}

Comments:
[Not specified]

Return to top of document.

Context:
Driver testable.

Assertion Description:
Driver testable.

Failure Message:

Failure Detail Description:

Comments:
All of these profile requirements are testable only by using a driver test program, since a test assertion would require application-level knowledge of the message exchange.

Return to top of document.

The Basic Profile requires support for XML Schema 1.0 and WSDL 1.1.

Specification Reference List:

• Web Services Description Language (WSDL) 1.1
• XML Schema Part 1: Structures
• XML Schema Part 2: Datatypes

Test Assertion: BP2201

Context:
For a candidate Web service definition within a WSDL document with a XML declaration statement.

Assertion Description:
The XML declaration statement uses UTF-8 or UTF-16 for the encoding.

Failure Message:
XML declaration statement within WSDL document does not use expected encoding (UTF-8 or UTF-16).

Failure Detail Description:
XML declaration statement.

Comments:
checks WSDL encoding.

Return to top of document.

Test Assertion: BP2202

Context:
For a candidate wsdl:types element within a WSDL document which imports an XML schema directly or indirectly.

Assertion Description:
The imported schema uses UTF-8 or UTF-16 for the encoding.

Failure Message:
The XML declaration statement within the imported XML Schema does not use expected encoding (UTF-8 or UTF-16).

Failure Detail Description:
XML declaration statement.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2700

Context:
For a candidate wsdl:definitions element within a WSDL document.

Assertion Description:
The wsdl:definitions is a well-formed XML 1.0 document.

Failure Message:
The wsdl:definitions is not a well-formed XML 1.0 document.

Failure Detail Description:
Error message from the XML parser

Comments:
1st step in a 3-phase verification process: XML+namespace+schemavalid.

Return to top of document.

Test Assertion: BP2102

Context:
For a candidate wsdl:types element, with XML schema import elements

Assertion Description:
Each XML schema import statement (xsd:import) is only used to directly reference an XML schema definition, which has "schema" from XML namespace "http://www.w3.org/2001/XMLSchema" as root element. It does not contain a reference to another document embedding the XML schema definition (e.g. WSDL).

Failure Message:
An XML schema import element references something other than an XML schema definition: the referenced element does not have "schema" from XML namespace "http://www.w3.org/2001/XMLSchema" as root element.

Failure Detail Description:
Defective XML schema import element.

Comments:
NOTE: XML schema definitions within a WSDL document must adhere to the same rules as XML schema definitions which appear in separate XSD files. For example, two WSDL definitions can not contain the same complex type definition for the same targetNamespace.

Return to top of document.

Test Assertion: BP2011

Context:
For a candidate wsdl:types element within a WSDL document, which imports an XML schema directly or indirectly

Assertion Description:
The imported XML schema is a well-formed XML 1.0 document and if it contains an XML declaration, it is version 1.0.

Failure Message:
The imported XML schema is not a well-formed XML 1.0 document.

Failure Detail Description:
{Error message from the XML parser}{imported XML schema}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2701

Context:
For a candidate wsdl:definitions element within a WSDL document.

Assertion Description:
The wsdl:definitions namespace has value: http://schemas.xmlsoap.org/wsdl/.

Failure Message:
The wsdl:definitions namespace is not: http://schemas.xmlsoap.org/wsdl/.

Failure Detail Description:

Comments:
2nd step in a 3-phase verification process: XML+namespace+schemavalid.

Return to top of document.

Test Assertion: BP2703

Context:
For a candidate description within a WSDL document

Assertion Description:
If it uses the WSDL namespace, then it conforms to the schema located at http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd, and if it uses the WSDL-SOAP binding namespace then it conforms to the schema located at http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.xsd.

Failure Message:
WSDL definition does not conform to the schema located at http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.xsd for some element using the WSDL-SOAP binding namespace, or does not conform to the schema located at http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd for some element using the WSDL namespace.

Failure Detail Description:
Error message from the XML parser.

Comments:
A description using WSDL-SOAP namespace is prefixed soapbind: in this doc as well as in the profile def. This verification is 3rd step in a 3-phase verification process: XML+namespace+schemavalid.

Return to top of document.

Test Assertion: BP2034

Context:
For a candidate description within a WSDL document

Assertion Description:
The candidate description does not contain the namespace declaration xmlns:xml="http://www.w3.org/XML/1998/namespace".

Failure Message:
The candidate description contains the namespace declaration xmlns:xml="http://www.w3.org/XML/1998/namespace".

Failure Detail Description:
[Not specified]

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2018

Context:
For a candidate Web service definition with wsdl:types elements

Assertion Description:
The wsdl:types elements occur either as first children in the WSDL namespace of the wsdl:definitions element, or they are only preceded by wsdl:documentation element(s) and/or wsdl:import(s) element(s).

Failure Message:
wsdl:types element(s) in the WSDL namespace of the wsdl:definitions element were preceded by child elements other than wsdl:documentation or wsdl:import elements.

Failure Detail Description:

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2208

Context:
For a candidate wsdl:operation in a wsdl:portType definition

Assertion Description:
The wsdl:operation element is either a WSDL request/response or a one-way operation (no Notification or Sollicit-Response).

Failure Message:
wsdl:operation was not a request/response or one-way operation.

Failure Detail Description:
Operation.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2010

Context:
For a candidate wsdl:portType definition

Assertion Description:
name attributes of Operations are unique in the wsdl:portType definition

Failure Message:
name attributes are not unique within the portType definition.

Failure Detail Description:
list of duplicate name(s) and of elements that use them.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2020

Context:
For a candidate wsdl:binding element, if the style attribute of the contained soapbind:binding is "rpc" and the use attribute is "literal".

Assertion Description:
The namespace attribute is specified on all soapbind:body elements and the value of the namespace attribute is an absolute URI.

Failure Message:
A soapbind:body element does not have a namespace attribute, or the namespace attribute value is not an absolute URI.

Failure Detail Description:
soapbind:body elements that failed the assertion

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2021

Context:
For a candidate wsdl:binding element

Assertion Description:
The wsdl:input element and wsdl:output element of each operation uses the attribute name "part" with a Schema type of "NMTOKEN" and does not use "parts", for both soapbind:header elements and soapbind:headerfault elements.

Failure Message:
The wsdl:input element or wsdl:output element of an operation does not use the attribute name "part" with a Schema type of "NMTOKEN" for soapbind:header elements or soapbind:headerfault elements, or it uses "parts".

Failure Detail Description:
wsdl:input element or wsdl:output element of the defective operation.

Comments:
Generally BP2703 will fail as a pre-req first because this will not pass a specialized schema check.

Return to top of document.

Test Assertion: BP2402

Context:
For a candidate wsdl:binding element

Assertion Description:
The wsdl:binding element has a soapbind:binding child element.

Failure Message:
The wsdl:binding element does not use a soapbind:binding element as defined in section "3 SOAP Binding." of the WSDL 1.1 specification.

Failure Detail Description:
wsdl:binding.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2022

Context:
For a candidate wsdl:binding element

Assertion Description:
the name attribute is specified on the soapbind:fault element.

Failure Message:
Defective soapbind:fault element: the name attribute is not specified on the soapbind:fault element.

Failure Detail Description:
Defective soapbind:fault element

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2032

Context:
For a candidate wsdl:binding element

Assertion Description:
the name attribute that is specified on the soapbind:fault element matches the value specified on the parent element wsdl:fault.

Failure Message:
Defective soapbind:fault element: the "name" attribute value does not match the value of the "name" attribute on the parent element wsdl:fault.

Failure Detail Description:
Defective soapbind:fault element

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2404

Context:
For a candidate wsdl:binding element

Assertion Description:
The contained soap:binding element has a "transport" attribute, which has value: http://schemas.xmlsoap.org/soap/http.

Failure Message:
Transport attribute of the soap:binding does not contain http://schemas.xmlsoap.org/soap/http.

Failure Detail Description:
soap:binding element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2012

Context:
For a candidate wsdl:binding element, if the style attribute of the binding is "document" and use is "literal"

Assertion Description:
The binding (in soapbind:body elements) only refers to part elements that have been defined using the "element" attribute.

Failure Message:
The binding (in soapbind:body elements) refers to part(s) of a soap:body element that do not have the "element" attribute.

Failure Detail Description:
soapbind:body element(s) that have non "element" parts attributes.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2406

Context:
For a candidate wsdl:binding element, if the use attribute is specified on the soapbind:body, soapbind:fault, soapbind:header, or soapbind:headerfault elements.

Assertion Description:
The use attribute has a value of "literal".

Failure Message:
The use attribute of a soapbind:body, soapbind:fault, soapbind:header and soapbind:headerfault does not have value of "literal".

Failure Detail Description:
Defective soapbind:body, soapbind:fault, soapbind:header, or soapbind:headerfault elements.

Comments:
R2707 is not the verified Req, but an assumed Req for this verification.

Return to top of document.

Test Assertion: BP2019

Context:
FFor a candidate wsdl:binding element, if the "style" attribute of the contained soap:binding is "document" and use attribute is "literal"

Assertion Description:
The "namespace" attribute is not specified in any contained soapbind:body, soapbind:header, soapbind::headerfault, soapbind:fault elements

Failure Message:
The binding is of style "document" and use "literal", and the "namespace" attribute is specified in some soapbind:body, soapbind:header, soapbind::headerfault, soapbind:fault element

Failure Detail Description:
Contained element with namespace attribute.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2013

Context:
For a candidate wsdl:binding element, if the "style" attribute of the contained soap:binding is "rpc" and use attribute is "literal"

Assertion Description:
The binding (in soapbind:body elements) only refers to part elements that have been defined using the "type" attribute

Failure Message:
soap:binding (in soapbind:body elements) refers to part(s) that do not have the "type" attribute.

Failure Detail Description:
{binding}{message with failed part}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2014

Context:
For a candidate wsdl:operation with a parameterOrder attribute, if referred to by a candidate rpc-literal wsdl:binding element

Assertion Description:
The parameterOrder attribute omits at most 1 part from an output wsdl:message.

Failure Message:
An operation associated with an rpc-literal binding has a parameterOrder attribute that omits more than 1 part.

Failure Detail Description:
{defective portType}{output wsdl:message}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2017

Context:
For a candidate wsdl:binding

Assertion Description:
The "style" attribute of each operation in the contained soap:binding has the same value of "document" or "rpc", for all operations of the wsdl:binding.

Failure Message:
The "style" attribute of an operation in soap:binding, does not have the same value of "document" or "rpc", as other operations of the binding.

Failure Detail Description:
defective soap:binding element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2101

Context:
For a candidate wsdl:definition, if it contains wsdl:import statements

Assertion Description:
Each wsdl:import statement is only used to import another WSDL description.

Failure Message:
A wsdl:import element does not contain a reference to another WSDL description.

Failure Detail Description:
wsdl:import element(s) that does not reference a WSDL description.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2098

Context:
For a candidate wsdl:import element

Assertion Description:
The "location" attribute is specified for the wsdl:import element, and has a non-empty value.

Failure Message:
A wsdl:import element does not have a "location" attribute, or has an empty value for the location attribute.

Failure Detail Description:
Defective wsdl:import element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2803

Context:
For a candidate wsdl:import element

Assertion Description:
The "namespace" attribute's value is not a relative URI.

Failure Message:
The wsdl:import element's "namespace" attribute value is a relative URI.

Failure Detail Description:
Defective wsdl:import element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2103

Context:
For each a candidate wsdl:definitions

Assertion Description:
For the referenced definitions as well as all imported descriptions, The XML schema import statement is only used within an xsd:schema element.

Failure Message:
A XML schema import element was found outside of an xsd:schema element.

Failure Detail Description:
Defective XML schema import element.

Comments:
This assertion is processed once for each WSDL description which fulfills the context criteria. The target for this assertion is the definitions element, because the XML schema import element might be specified anywhere within a WSDL document.

Return to top of document.

Test Assertion: BP2104

Context:
For a candidate wsdl:import

Assertion Description:
The targetNamespace attribute on the wsdl:definitions element for the imported WSDL description has the same value as the namespace attribute on the wsdl:import element that imported the WSDL description.

Failure Message:
The targetNamespace attribute on the wsdl:definitions element for an imported WSDL description does not have the same value as the namespace attribute on the wsdl:import element that imported the WSDL description.

Failure Detail Description:
wsdl:import element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2105

Context:
For a candidate wsdl:definitions with wsdl:import elements

Assertion Description:
wsdl:import elements occur either as first children elements in the WSDL namespace of the wsdl:defintitions element, or they are only preceded by wsdl:documentation elements.

Failure Message:
A wsdl:import element in the WSDL namespace under the wsdl:definitions element, is preceded by child elements other than wsdl:documentation elements.

Failure Detail Description:
Display the WSDL import element(s) that failed the assertion.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2416

Context:
For a candidate wsdl:definitions

Assertion Description:
Every QName in the WSDL document that is not referring to a schema component, is either using the target namespace of this WSDL or the target namespace of a directly imported WSDL component.

Failure Message:
A QName reference that does not refer to a schema component, is using neither the target namespace of this WSDL nor the target namespace of a directly imported WSDL component.

Failure Detail Description:
Defective QName(s).

Comments:
This assertion is processed once for each WSDL description which fulfills the context criteria. Only direct WSDL imports are considered for QName resolution. Note that this test does not require resolving the qualified element itself in the imported namespace: only the namespace is verified. Some sub cases of R2101 related to schema target namespaces, are not handled here and are covered by another TA covering R2102 (BP2417).

Return to top of document.

Test Assertion: BP2417

Context:
For a candidate wsdl:definitions

Assertion Description:
Every QName in the WSDL document and its imports, that is referring to a schema component, uses the namespace defined in the targetNamespace attribute on the xs:schema element, or a namespace defined in the namespace attribute on an xs:import element within the xs:schema element.

Failure Message:
A QName reference that is referring to a schema component, uses a namespace not defined in the targetNamespace attribute on the xs:schema element, or in the namespace attribute on an xs:import element within the xs:schema element.

Failure Detail Description:
Defective QName(s).

Comments:
This assertion is processed once for each WSDL description which fulfills the context criteria. Only the subcases of R2101 that are related to schema imports are covered by this test, as these overlap with R2102 requirements.

Return to top of document.

Test Assertion: BP2107

Context:
For a candidate wsdl:types element containing an xsd:schema element

Assertion Description:
The xsd:schema element contains 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).

Failure Message:
A xsd:schema element contained in a wsdl:types element does not have a targetNamespace attribute with a valid and non-null value, while having child element(s) other than xsd:import or xsd:annotation.

Failure Detail Description:
Defective xsd:schema element(s).

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2108

Context:
For a candidate wsdl:types

Assertion Description:
The type soapenc:Array does not appear in these declarations, and the wsdl:arrayType attribute is not used in the type declaration.

Failure Message:
An Array declaration uses - restricts or extends - the soapenc:Array type, or the wsdl:arrayType attribute is used in the type declaration.

Failure Detail Description:
Defective declaration(s).

Comments:
R2110 and R2111 have been interpreted as applying to any declaration, as we cannot assume the intent of declaring arrays, which is untestable.

Return to top of document.

Test Assertion: BP2110

Context:
For a candidate wsdl:types that is used by an rpc-literal binding

Assertion Description:
The declaration does not use the naming convention ArrayOfXXX.

Failure Message:
A declaration is using the convention ArrayOfXXX.

Failure Detail Description:
Defective declaration(s).

Comments:
R2112 has been interpreted as applying to any declaration, as we cannot assume the intent of declaring arrays, which is untestable. However, R2112 should only concern "wrapper elements", i.e. RPC-lit cases. The narrowing of the context here, is not sufficient to restrict properly the application of this TA.

Return to top of document.

Test Assertion: BP2111

Context:
For a candidate wsdl:binding, which contains a document-literal soap:binding

Assertion Description:
If the "parts" attribute is present, then the soapbind:body element(s) have at most one part listed in the parts attribute.

Failure Message:
One or more soapbind:body element(s) in a document-literal soap:binding does not have at most one part listed in the parts attribute.

Failure Detail Description:
Defective soapbind:body element(s).

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2112

Context:
For a candidate wsdl:binding, with a style "rpc" attribute and containing at least a soapbind:body element

Assertion Description:
No wsdl:part referred by such a soapbind:body element is defined using the "element" attribute.

Failure Message:
The referred wsdl:part element uses the "element" attribute in an rpc-literal soapbind:body.

Failure Detail Description:
{soapbind:body}{wsdl:part element(s)}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2113

Context:
For a candidate wsdl:binding element

Assertion Description:
When they contain references to message parts, the soapbind:header, soapbind:headerfault and soapbind:fault elements only refer to wsdl:part element(s) that have been defined using the "element" attribute.

Failure Message:
The soapbind:header, soapbind:headerfault or soapbind:fault elements refer to wsd:part element(s) that are not defined using only the "element" attribute.

Failure Detail Description:
Defective wsdl:binding and wsdl:part elements.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2115

Context:
For a candidate wsdl:message

Assertion Description:
An "element" attribute on any wsdl:part element refers to a global element declaration.

Failure Message:
A wsdl:message element containing a wsdl:part element that uses the "element" attribute does not refer, via that attribute, to a global element declaration.

Failure Detail Description:
Defective wsdl:message element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2116

Context:
For a candidate wsdl:message element

Assertion Description:
The wsdl:message element does not contain part elements that use both "type" and "element" attributes.

Failure Message:
A wsdl:message element has at least one wsdl:part element that contains both type and element attributes.

Failure Detail Description:
Defective wsdl:message element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2117

Context:
For a candidate wsdl:binding element, referred to by an rpc-literal soap:binding

Assertion Description:
The rpc-literal binding does not have a namespace attribute specified on a contained soapbind:header, soapbind:headerfault, and soapbind:fault element.

Failure Message:
An rpc-literal binding has the namespace attribute specified on contained soapbind:header, soapbind:headerfault and soapbind:fault elements.

Failure Detail Description:
{Defective wsdl:binding}{defective soapbind:header, soapbind:headerfault, or soapbind:fault element}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2118

Context:
For a candidate wsdl:binding element

Assertion Description:
The list (or set) of wsdl:operation elements for the contained wsdl:binding is the same as the list of wsdl:operations for the referred wsdl:portType.

Failure Message:
A wsdl:binding does not have the same list of wsdl:operations as the wsdl:portType to which it refers.

Failure Detail Description:
{unmatching wsdl:binding element}{unmatching portType element}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2114

Context:
For a candidate wsdl:binding element

Assertion Description:
Every wsdl:part from each wsdl:message in the associated wsdl:portType is referenced either by the soapbind:body, soapbind:header, soapbind:fault, or soapbind:headerfault.

Failure Message:
A wsdl:binding does not 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 or soapbind:headerfault.

Failure Detail Description:
{Defective wsdl:binding element}{message with part(s) unbound}

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2119

Context:
For a candidate wsdl:binding, which is of type document-literal

Assertion Description:
If it does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message defines zero or one wsdl:part.

Failure Message:
A document-literal binding which does not specify the parts attribute, has more than one wsdl:part in the associated wsdl:message element.

Failure Detail Description:
Defective wsdl:binding element.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2120

Context:
For a candidate wsdl:binding

Assertion Description:
Each operation referenced by the binding results in a unique wire signature.

Failure Message:
A binding has operations that are not unique.

Failure Detail Description:
Defective wsdl:operation element(s).

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP2122

Context:
For a candidate wsdl:types element

Assertion Description:
The data type definition if any within the wsdl:types element is an XML schema definition defined in the XML Schema 1.0 Recommendation with the namespace URI "http://www.w3.org/2001/XMLSchema".

Failure Message:
A wsdl:types element contained a data type definition that is not an XML schema definition.

Failure Detail Description:
Defective data type definition.

Comments:
Validating the data type definitions includes any imported XML schema definitions.

Return to top of document.

Test Assertion: BP2123

Context:
For a candidate wsdl:definitions, if it contains a wsdl:port, wsdl:binding, wsdl:portType, wsdl:operation, or wsdl:message that claims conformance to the Profile.

Assertion Description:
Contained WSDL extension elements do not use the wsdl:required attribute value of "true".

Failure Message:
An extension element within a WSDL element that claims conformance to the Basic Profile has a wsdl:required attribute with a value of "true".

Failure Detail Description:
Display the extension element that failed the assertion.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP4200

Context:
For a candidate wsdl:definitions element containing an extension element or attribute from a namespace other than "http://schemas.xmlsoap.org/wsdl/soap/".

Assertion Description:
The WSDL contains an extension element or attribute that does not belong to the "http://schemas.xmlsoap.org/wsdl/soap/".

Detail Description:
The use of a WSDL extension element or attribute from a namespace other than "http://schemas.xmlsoap.org/wsdl/soap/" may require out of band negotiation.

Comments:
Extension elements other than those belonging to one of the following namespaces (...) are considered extensibility points.

Return to top of document.

Test Assertion: BP4201

Context:
For a candidate wsdl:import element, where the location attribute or the namespace attribute has a value that is a relative URI, or a for soap:address element where the location attribute is a relative URI.

Assertion Description:
The use of a relative URI as the value for a wsdl:import location or namespace attribute, or for a soap:address location attribute may require out of band coordination.

Detail Description:
The element(s) in question.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP4202

Context:
For an XML schema definition defined in the wsdl:types element, or imported directly or indirectly by a schema definition defined in the wsdl:types element, which contains any schema annotation elements.

Assertion Description:
An XML schema definition defined in the wsdl:types element, or imported directly or indirectly by a schema definition defined in the wsdl:types element, may use schema annotation elements as an extensibility mechanism.

Detail Description:
The annotation elements included in the schema.

Comments:
Schema annotations are an extensibility point.

Return to top of document.

Test Assertion: BP2998

Context:
Driver testable.

Assertion Description:
Driver testable.

Failure Message:

Failure Detail Description:

Comments:
All of these profile requirements are testable only by using a driver test program, since a test assertion would require application-level knowledge of the message exchange.

Return to top of document.

Test Assertion: BP2999

Context:
Not testable.

Assertion Description:
Not testable.

Failure Message:

Failure Detail Description:

Comments:
All of these profile requirements are NOT testable, or NOT testable using the current test tools. For example, some of these test assertions represent capabilities which can not be validated. Note, BP2200 is NOT testable using the current test tools because any BOM detected within a WSDL document is pre-processed by the WSDL reader/parser and hence becomes inaccessible. Note, R2724 could be tested. If a request is inconsistent with the WSDL for the request, we could flag returning a non-error response. We currently do not check the status of a request when we are processing the response. However this is within the scope of the test-tools and we are tracking this omission defect/feature in bugzilla RE: bug#: 8.

Return to top of document.

The Basic Profile requires support for SOAP 1.1 and HTTP 1.0 or 1.1.

Specification Reference List:

• Simple Object Access Protocol (SOAP) 1.1
• Extensible Markup Language (XML) 1.0 (Second Edition)
• RFC2616: Hypertext Transfer Protocol -- HTTP/1.1
• RFC2965: HTTP State Management Mechanism
• RFC2818: HTTP Over TLS
• RFC2246: The TLS Protocol Version 1.0
• The SSL Protocol Version 3.0
• RFC2459: Internet X.509 Public Key Infrastructure Certificate and CRL Profile

Test Assertion: BP1004

Context:
For a candidate request message in the message log file

Assertion Description:
The request message is a POST message, without any use of framework extension.

Failure Message:
The message is not an HTTP POST message, or makes use of HTTP framework extension.

Failure Detail Description:
All HTTP headers.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1006

Context:
For a candidate request message in the message log file, when a SOAPAction header is present

Assertion Description:
The SOAPAction header contains a quoted string of any value, including "".

Failure Message:
SOAPAction HTTP header does not contain a quoted string.

Failure Detail Description:
All HTTP headers.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1116

Context:
For a candidate request message in the message log file, when a SOAPAction header is present

Assertion Description:
The SOAPAction header contains a quoted string that has same value as the value of the soapbind:operation/@soapAction attribute, and an empty string ("") if there is no such attribute.

Failure Message:
SOAPAction header does not contain the correct string value.

Failure Detail Description:
{All HTTP headers}{soapAction value from the soap:binding}.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1001

Context:
For a candidate message in the log file, that is either a POST HTTP request, or a response to a POST HTTP request

Assertion Description:
If it is a request, the arg #2 of POST is <HTTP/1.1>. If absent, first line of the body is: HTTP-Version = HTTP/1.1. If it is a response, it starts with <HTTP/1.1>

Failure Message:
The message is not sent using HTTP/1.1.

Failure Detail Description:
All HTTP headers.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1002

Context:
For a candidate message in the log file, that is either a POST HTTP request, or a response to a POST HTTP request

Assertion Description:
If it is a request, the arg #2 of POST is <HTTP/1.1> or <HTTP/1.0>. If absent, first line of the body is: HTTP-Version = HTTP/1.1. (or HTTP/1.0). If it is a response, it starts with <HTTP/1.1> or <HTTP/1.0>

Failure Message:
The message is not sent using HTTP/1.1 or HTTP/1.0.

Failure Detail Description:
All HTTP headers.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1010

Context:
For a candidate response message in the message log file, which is bound to a One-Way wsdl:operation

Assertion Description:
It does not contain a soap:Envelope: the HTTP entity-body is empty

Failure Message:
One-Way operation response contains a soap:Envelope (HTTP entity-body must be empty)

Failure Detail Description:

Comments:
Need the request to determine if it is a One-Way. We could have targeted the request as well (as primary entry), and correlate with the response.

Return to top of document.

Test Assertion: BP1101

Context:
For a candidate response message in the log file, that does not contain a SOAP message and that does not contain an HTTP 4xx status code

Assertion Description:
The response message, if successfully processed at HTTP level, is sent using either a "200 OK" or "202 Accepted" HTTP status code.

Failure Message:
A response message without a SOAP message, is not using either a "200 OK" or "202 Accepted" HTTP status code, though successful at HTTP level.

Failure Detail Description:
Complete message.

Comments:
This test assertion is targeted at one-way operations.

Return to top of document.

Test Assertion: BP1103

Context:
For a candidate response message in the message log file, associated with a request message that does not contain an HTTP POST method

Assertion Description:
The response contains a "405 Method not Allowed" HTTP status code.

Failure Message:
The response message to a request that was not a POST message, did not contain an 405 HTTP status code.

Failure Detail Description:
Both the request and response message.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP4103

Context:
For a candidate message in the message log file containing an HTTP Authentication header field with an authentication mechanism other than "Basic" or "Digest"

Assertion Description:
The message contains an HTTP Authentication header field with an authentication mechanism other than "Basic" or "Digest".

Detail Description:
HTTP authentication allows for extension schemes, arbitrary digest hash algorithms and parameters.

Comments:
HTTP Authentication is an extensibility point for HTTP 1.1.

Return to top of document.

Test Assertion: BP4104

Context:
For a candidate message in the message log file containing an HTTP Header field that is not from the following list of specified header fields: (http://www.mnot.net/drafts/draft-nottingham-http-header-reg-00.txt)

Assertion Description:
The message contains an HTTP Header field that is not from the following list of specified header fields: (http://www.mnot.net/drafts/draft-nottingham-http-header-reg-00.txt)

Detail Description:
HTTP allows arbitrary headers to occur in messages.

Comments:
If all HTTP headers in a message are in the standardized list of draft-nottingham-http-header-reg-00 it will cause the informationalassertion 4104 to be notApplicable; otherwise 4101 will pass and headers not in the draft-nottingham-http-header-reg-00 will be listed.

Return to top of document.

Test Assertion: BP4105

Context:
For a candidate message in the message log file containing a Content-encoding HTTP header field with a value other than "gzip", "compress" or "deflate"

Assertion Description:
The contained Content-encoding HTTP header field has a value other than "gzip", "compress" or "deflate".

Detail Description:
The set of content-codings allowed by HTTP is open-ended.

Comments:
Any Content-encoding header field with a value other than the specified list is considered to be an extensibility point.

Return to top of document.

Test Assertion: BP4106

Context:
For a candidate response message in the message log file containing a transfer-encoding HTTP header field with a value other than "chunked"

Assertion Description:
The contained transfer-encoding HTTP header field has a value other than "chunked".

Detail Description:
Any Transfer-encoding header field with a value other than chunked is considered to be an extensibility point.

Comments:
Any Transfer-encoding header field with a value other than chunked is considered to be an extensibility point.

Return to top of document.

Test Assertion: BP4107

Context:
For a request message containing an Upgrade header field in the HTTP Headers.

Assertion Description:
The request message contains an Upgrade header field in the HTTP Headers.

Detail Description:
The Upgrade header field is considered an HTTP Extensibility point.

Comments:
The Upgrade header field is considered an HTTP Extensibility point.

Return to top of document.

Context:
Driver testable.

Assertion Description:
Driver testable.

Failure Message:

Failure Detail Description:

Comments:
All of these profile requirements are testable only by using a driver test program, since a test assertion would require application-level knowledge of the message exchange.

Return to top of document.

Test Assertion: BP1999

Context:
Not testable.

Assertion Description:
Not testable.

Failure Message:

Failure Detail Description:

Comments:
All of these profile requirements are NOT testable. Some of these test assertions represent capabilities which can not be validated.

Return to top of document.

SOAP 1.1 defines a structure for transmitting messages, the envelope. The profile mandates the use of that structure.

Specification Reference List:

• SOAP 1.1, Section 4

Test Assertion: BP1107

Context:
For a candidate response envelope containing a soap:Fault element

Assertion Description:
The contained soap:Fault element is defined in the wsdl:binding.

Failure Message:
The response envelope contained soap:Fault element(s), but they were not defined in the WSDL description.

Failure Detail Description:
Undefined soap:Fault element(s).

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1308

Context:
For a candidate envelope containing a soap:Body element

Assertion Description:
No child element of soap:Body has a soap:encodingStyle attribute.

Failure Message:
A child of the soap:Body element has a soap:encodingStyle attribute.

Failure Detail Description:
SOAP message

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1011

Context:
For a candidate envelope in a request message

Assertion Description:
The content of the envelope matches the definition in the WSDL document. In case of a doc-lit binding, the child element of soap:body is an instance of the global element declaration referenced by the corresponding wsdl:part. If the message has "parts", the order of the part elements in the soap:body of the wired message, is same as that of the wsdl:partS, in the wsdl:message that describes it for each of the wsdl:part elements bound to the envelope's corresponding soapbind:body element.

Failure Message:
The content of the envelope does not match the wsdl:message definition. The order of parts in soap:body does not match the order of wsdl:partS in wsdl:message that describes it for each of the wsdl:part elements bound to the envelope's corresponding soapbind:body element; or the child element of soap:body is not an instance of the global element declaration referenced by the corresponding wsdl:part.

Failure Detail Description:
Non-matching WSDL operation and envelope.

Comments:
R2710, R2742 R2743 and R2748 used as "assumed" reqts, not reqts to verify. The soap:encodingStyle verification done by pre-req BP1308 on children, is not done for grand-children (BP1318 coul dnot be a pre-req)

Return to top of document.

Test Assertion: BP1013

Context:
For a candidate envelope in a response message, if it does not contain a soap:Fault

Assertion Description:
The content of the envelope matches the definition in the WSDL document. In case of an rpc-lit binding, the body contains a wrapper element that matches theoperation name. In case of a doc-lit binding, the child element of soap:body is an instance of the global element declaration referenced by the corresponding wsdl:part. If the message has "parts", the order of the part elements in the soap:body of the wired message, is same as that of the wsdl:partS, in the wsdl:message that describes it for each of the wsdl:part elements bound to the envelope's corresponding soapbind:body element.

Failure Message:
The content of the envelope does not match the wsdl:message definition. The order of parts in soap:body does not match the order of wsdl:partS in wsdl:message that describes it for each of the wsdl:part elements bound to the envelope's corresponding soapbind:body element; or it has a doc-lit binding but the child element of soap:body is not an instance of the global element declaration referenced by the corresponding wsdl:part; or it has an rpc-lit binding but no wrapper element.

Failure Detail Description:
Non-matching WSDL operation and envelope.

Comments:
R2710, R2742 R2743 and R2748 used as "assumed" reqts, not reqts to verify. The test assertion also verifies the wrapper element in case of an rpc-binding (in a same way as BP1005 which could not be a pre-requisite due to a narrower context)

Return to top of document.

Test Assertion: BP1204

Context:
For a candidate envelope

Assertion Description:
The soap:body of the envelope does not contain the soapenc:arrayType attribute.

Failure Message:
The soap:body of an envelope contains the soapenc:arrayType attribute.

Failure Detail Description:
SOAP envelope.

Comments:
R2113 has been interpreted as applying to any message body, as it is unclear how to narrow to serialized array declarations. The narrowing of the context here,may not be sufficient to restrict properly the application of this TA.

Return to top of document.

Test Assertion: BP1301

Context:
For a candidate envelope containing a "mustUnderstand" attribute

Assertion Description:
The "mustUnderstand" attribute in the envelope has one of two values: 1, 0.

Failure Message:
The "mustUnderstand" attribute in an envelope has a value different from: 1, 0.

Failure Detail Description:
SOAP envelope, plus envelope of a request message if it is a response.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1305

Context:
For a candidate envelope in a response message containing a soap:Fault element

Assertion Description:
The soap:Fault element is contained in an HTTP 500 message with "Server" Error code.

Failure Message:
The soap:Fault message is not returned in an HTTP 500 message.

Failure Detail Description:
SOAP envelope.

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1306

Context:
For a candidate envelope in a response message containing a soap:Fault element

Assertion Description:
The soap:Fault element does not have children other than soap:faultcode, soap:faultstring, soap:faultactor or soap:detail.

Failure Message:
One or more soap:Fault child elements are not standard, i.e. is neither soap:faultcode, soap:faultstring, soap:faultactor nor soap:detail.

Failure Detail Description:
SOAP envelope

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1031

Context:
For a candidate envelope in a response message containing a soap:Fault element

Assertion Description:
The content of the soap:Fault element does not make use of the SOAP 1.1 dot notation, i.e. is a string without a dot character in it.

Failure Message:
A soap:Fault element makes use of the SOAP 1.1 dot notation.

Failure Detail Description:
SOAP envelope

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1032

Context:
For a candidate envelope

Assertion Description:
The soap:Envelope, soap:Header, and soap:Body elements do not have any attributes in the namespace "http://schemas.xmlsoap.org/soap/envelope/"

Failure Message:
A soap:Envelope, soap:Header, or soap:Body element has an attribute in the namespace "http://schemas.xmlsoap.org/soap/envelope/".

Failure Detail Description:
SOAP envelope

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1033

Context:
For a candidate envelope

Assertion Description:
The SOAP envelope does not contain the namespace declaration xmlns:xml="http://www.w3.org/XML/1998/namespace".

Failure Message:
The SOAP envelope contains the namespace declaration xmlns:xml="http://www.w3.org/XML/1998/namespace".

Failure Detail Description:
SOAP envelope

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1316

Context:
For a candidate envelope in a response message containing a soap:Fault element

Assertion Description:
The soap:Fault element children (soap:faultcode, soap:faultstring, soap:faultactor or soap:detail) are unqualified.

Failure Message:
One or more soap:Fault child elements are qualified.

Failure Detail Description:
SOAP envelope

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1307

Context:
For a candidate envelope containing elements with namespace "http://schemas.xmlsoap.org/soap/envelope/"

Assertion Description:
The envelope contains elements that are namespaced "http://schemas.xmlsoap.org/soap/envelope/" do not have a soap:encodingStyle attribute.

Failure Message:
The envelope contains one or elements namespaced "http://schemas.xmlsoap.org/soap/envelope/" having a soap:encodingStyle attribute.

Failure Detail Description:
SOAP envelope

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1318

Context:
For a candidate non-fault envelope containing a soap:body with at least one grandchild, and is referred by an rpc-literal binding

Assertion Description:
The grandchild elements of soap:Body referred by an rpc-literal binding do not have a soap:encodingStyle attribute.

Failure Message:
At least one grandchild of the soap:Body element referred by an rpc-literal binding has a soap:encodingStyle attribute.

Failure Detail Description:
SOAP envelope

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1008

Context:
For a candidate non-fault envelope containing a soap:body with at least one element, and that is referred by a binding style rpc-literal

Assertion Description:
The envelope has part accessor elements for parameters and return value, in no namespaces, but the descendants of these are namespace qualified as defined by the schema in which their types are defined.

Failure Message:
The envelope has part accessor elements for parameters and return value, within namespaces, or the descendants of these elements are not namespace qualified as defined by the schema in which their types are defined.

Failure Detail Description:

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1211

Context:
For a candidate non-fault envelope containing a soap:body with at least one element, and that is referred by a binding style rpc-literal

Assertion Description:
Part accessor elements in the envelope do not have an xsi:nil attribute with a value of "1" or "true".

Failure Message:
Envelope referenced by an rpc-literal binding has part accessor elements with an xsi:nil attribute with a value of "1" or "true".

Failure Detail Description:

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1212

Context:
For a candidate non-fault envelope containing a soap:body with at least one element

Assertion Description:
The envelope contains exactly one part accessor element for each of the wsdl:part elements bound to the envelope's corresponding soapbind:body element.

Failure Message:
The content of the soap:Body element is inconsistent with its description. The envelope does not contain exactly one part accessor element for each of the wsdl:part elements bound to the envelope's corresponding soapbind:body element.

Failure Detail Description:

Comments:
[Not specified]

Return to top of document.

Test Assertion: BP1213