2002/ws/desc/test-suite assertion-coverage.xsl,1.4,1.5 assertion-coverage.xml,1.9,1.10 Assertion-coverage.html,1.9,1.10 assertions.xml,1.6,1.7 Dashboard.html,1.84,1.85

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

2002/ws/desc/test-suite assertion-coverage.xsl,1.4,1.5 assertion-coverage.xml,1.9,1.10 Assertion-coverage.html,1.9,1.10 assertions.xml,1.6,1.7 Dashboard.html,1.84,1.85

Philippe Le Hegaret via cvs-syncmail

Update of /sources/public/2002/ws/desc/test-suite
In directory hutz:/tmp/cvs-serv27992/test-suite

Modified Files:
        assertion-coverage.xsl assertion-coverage.xml
        Assertion-coverage.html assertions.xml Dashboard.html
Log Message:
Updated assertion coverage reports

Index: assertions.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/assertions.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -C 2 -d -r1.6 -r1.7
*** assertions.xml 15 Mar 2007 19:44:49 -0000 1.6
--- assertions.xml 27 Jun 2007 14:54:49 -0000 1.7
***************
*** 9,13 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-1007" class="component" part="1" section="2" subsection="01">Each XML Schema element declaration MUST have a unique QName.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-1008" class="component" part="1" section="2" subsection="01">Each XML Schema type definition MUST have a unique QName.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-1009" class="component" part="1" section="2" subsection="02">To avoid circular definitions, an interface MUST NOT appear as an element of the set of interfaces it extends, either directly or indirectly.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-1010" class="component" part="1" section="2" subsection="02">For each Interface component in the interfaces property of a Description component, the name property MUST be unique.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-1011" class="component" part="1" section="2" subsection="02">The list of xs:QName in an extendsattribute information item MUST NOT contain duplicates.</assertion>
--- 9,13 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-1007" class="component" part="1" section="2" subsection="01">Each XML Schema element declaration MUST have a unique QName.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-1008" class="component" part="1" section="2" subsection="01">Each XML Schema type definition MUST have a unique QName.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-1009" class="component" part="1" section="2" subsection="02">To avoid circular definitions, an interface MUST NOT appear in the set of interfaces it extends, either directly or indirectly.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-1010" class="component" part="1" section="2" subsection="02">For each Interface component in the interfaces property of a Description component, the name property MUST be unique.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-1011" class="component" part="1" section="2" subsection="02">The list of xs:QName in an extendsattribute information item MUST NOT contain duplicates.</assertion>
***************
*** 17,26 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFault-1015" class="component" part="1" section="2" subsection="03">In cases where, due to an interface extending one or more other interfaces, two or more Interface Fault components have the same value for their name property, then the component models of those Interface Fault components MUST be equivalent (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="InterfaceFault-1016" class="component" part="1" section="2" subsection="03">For the above reason, it is considered good practice to ensure, where necessary, that the local name of the name property of Interface Fault components within a namespace SHOULD be unique, thus allowing such derivation to occur without inadvertent error.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFault-1017" class="document" part="1" section="2" subsection="03">If the elementattribute information item has a value then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1018" class="component" part="1" section="2" subsection="04">This xs:anyURI MUST be an absolute IRI (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1019" class="component" part="1" section="2" subsection="04">These xs:anyURIs MUST be absolute IRIs (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1020" class="component" part="1" section="2" subsection="04">In cases where, due to an interface extending one or more other interfaces, two or more Interface Operation components have the same value for their name property, then the component models of those Interface Operation components MUST be equivalent (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="InterfaceOperation-1021" class="component" part="1" section="2" subsection="04">For the above reason, it is considered good practice to ensure, where necessary, that the name property of Interface Operation components within a namespace SHOULD be unique, thus allowing such derivation to occur without inadvertent error.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MEP-1022" class="component" part="1" section="2" subsection="04">A message exchange pattern is uniquely identified by an absolute IRI which is used as the value of the message exchange pattern property of the Interface Operation component, and it specifies the fault propagation ruleset that its faults obey.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1023" class="component" part="1" section="2" subsection="04">An Interface Operation component MUST satisfy the specification defined by each operation style identified by its style property.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1024" class="component" part="1" section="2" subsection="05">The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</assertion>
--- 17,26 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFault-1015" class="component" part="1" section="2" subsection="03">In cases where, due to an interface extending one or more other interfaces, two or more Interface Fault components have the same value for their name property, then the component models of those Interface Fault components MUST be equivalent (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="InterfaceFault-1016" class="component" part="1" section="2" subsection="03">For the above reason, it is considered good practice to ensure, where necessary, that the local name of the name property of Interface Fault components within a namespace SHOULD be unique, thus allowing such derivation to occur without inadvertent error.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFault-1017" class="document" part="1" section="2" subsection="03">If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1018" class="component" part="1" section="2" subsection="04">This xs:anyURI MUST be an absolute IRI (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1019" class="component" part="1" section="2" subsection="04">These xs:anyURIs MUST be absolute IRIs (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1020" class="component" part="1" section="2" subsection="04">In cases where, due to an interface extending one or more other interfaces, two or more Interface Operation components have the same value for their name property, then the component models of those Interface Operation components MUST be equivalent (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="InterfaceOperation-1021" class="component" part="1" section="2" subsection="04">For the above reason, it is considered good practice to ensure, where necessary, that the name property of Interface Operation components within a namespace SHOULD be unique, thus allowing such derivation to occur without inadvertent error.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MEP-1022" class="component" part="1" section="2" subsection="04">A message exchange pattern is itself uniquely identified by an absolute IRI, which is used as the value of the message exchange pattern property of the Interface Operation component, and which specifies the fault propagation ruleset that its faults obey.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-1023" class="component" part="1" section="2" subsection="04">An Interface Operation component MUST satisfy the specification defined by each operation style identified by its style property.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1024" class="component" part="1" section="2" subsection="05">The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</assertion>
***************
*** 28,49 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1026" class="component" part="1" section="2" subsection="05">The direction MUST be the same as the direction of the message identified by the message label property in the message exchange pattern of the Interface Operation component this is contained within.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1027" class="component" part="1" section="2" subsection="05">An xs:token with one of the values #any, #none, #other, or #element.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1028" class="component" part="1" section="2" subsection="05">When the message content model property has the value #any or #none the element declaration property MUST be empty.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1029" class="component" part="1" section="2" subsection="05">For each Interface Message Reference component in the interface message references property of an Interface Operation component, its message label property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1030" class="document" part="1" section="2" subsection="05">If the messageLabelattribute information item of an interface message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1031" class="document" part="1" section="2" subsection="05">If the messageLabelattribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1032" class="document" part="1" section="2" subsection="05">If the local name is input then the message exchange pattern MUST have at least one placeholder message with direction In.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1033" class="document" part="1" section="2" subsection="05">If the local name is output then the message exchange pattern MUST have at least one placeholder message with direction Out.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1034" class="document" part="1" section="2" subsection="05">If the local name is infault then the message exchange pattern MUST support at least one fault in the In direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1035" class="document" part="1" section="2" subsection="05">If the local name is outfault then the message exchange pattern MUST support at least one fault in the Out direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1036" class="document" part="1" section="2" subsection="05">If the elementattribute information item has a value then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1037" class="component" part="1" section="2" subsection="06">The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1038" class="component" part="1" section="2" subsection="06">The direction MUST be consistent with the direction implied by the fault propagation ruleset used in the message exchange pattern of the operation.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1039" class="component" part="1" section="2" subsection="06">For each Interface Fault Reference component in the interface fault references property of an Interface Operation component, the combination of its interface fault and message label properties MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1040" class="document" part="1" section="2" subsection="06">The messageLabelattribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given direction if the message exchange pattern of the parent Interface Operation component has more than one fault with that direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1041" class="document" part="1" section="2" subsection="06">The messageLabelattribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1042" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1043" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1044" class="component" part="1" section="2" subsection="07">If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components) then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1045" class="component" part="1" section="2" subsection="07">A Binding component that defines bindings for an Interface component MUST define bindings for all the operations and faults of that Interface component.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1046" class="component" part="1" section="2" subsection="07">Similarly, whenever a reusable Binding component (i.e. one that does not specify an Interface component) is applied to a specific Interface component in the context of an Endpoint component (see ), the Binding component MUST define bindings for each Interface Operation and Interface Fault component of the Interface component, via a combination of properties defined on the Binding component itself and default binding rules specific to its binding type.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1047" class="component" part="1" section="2" subsection="07">A Binding component that defines bindings for an Interface component MUST define bindings for all the faults of that Interface component that are referenced from any of the operations in that Interface component.</assertion>
--- 28,49 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1026" class="component" part="1" section="2" subsection="05">The direction MUST be the same as the direction of the message identified by the message label property in the message exchange pattern of the Interface Operation component this is contained within.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1027" class="component" part="1" section="2" subsection="05">An xs:token with one of the values #any, #none, #other, or #element.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1028" class="component" part="1" section="2" subsection="05">When the message content model property has the value #any or #none, the element declaration property MUST be empty.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1029" class="component" part="1" section="2" subsection="05">For each Interface Message Reference component in the interface message references property of an Interface Operation component, its message label property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1030" class="document" part="1" section="2" subsection="05">If the messageLabelattribute information item of an interface message reference element information item is present, then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1031" class="document" part="1" section="2" subsection="05">If the messageLabelattribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1032" class="document" part="1" section="2" subsection="05">If the local name is input then the message exchange pattern MUST have at least one placeholder message with direction In.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1033" class="document" part="1" section="2" subsection="05">If the local name is output then the message exchange pattern MUST have at least one placeholder message with direction Out.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1034" class="document" part="1" section="2" subsection="05">If the local name is infault then the message exchange pattern MUST support at least one fault in the In direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1035" class="document" part="1" section="2" subsection="05">If the local name is outfault then the message exchange pattern MUST support at least one fault in the Out direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceMessageReference-1036" class="document" part="1" section="2" subsection="05">If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1037" class="component" part="1" section="2" subsection="06">The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1038" class="component" part="1" section="2" subsection="06">The direction MUST be consistent with the direction implied by the fault propagation ruleset used in the message exchange pattern of the operation.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1039" class="component" part="1" section="2" subsection="06">For each Interface Fault Reference component in the interface fault references property of an Interface Operation component, the combination of its interface fault and message label properties MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFaultReference-1040" class="document" part="1" section="2" subsection="06">The messageLabelattribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given direction, if the message exchange pattern of the parent Interface Operation component has more than one fault with that direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1041" class="document" part="1" section="2" subsection="06">The messageLabelattribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1042" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1043" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1044" class="component" part="1" section="2" subsection="07">If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components), then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1045" class="component" part="1" section="2" subsection="07">A Binding component that defines bindings for an Interface component MUST define bindings for all the operations of that Interface component.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1046" class="component" part="1" section="2" subsection="07">Similarly, whenever a reusable Binding component (i.e. one that does not specify an Interface component) is applied to a specific Interface component in the context of an Endpoint component (see ), the Binding component MUST define bindings for each Interface Operation and Interface Fault component of the Interface component, via a combination of properties defined on the Binding component itself and default binding rules specific to its binding type.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-1047" class="component" part="1" section="2" subsection="07">A Binding component that defines bindings for an Interface component MUST define bindings for all the faults of that Interface component that are referenced from any of the operations in that Interface component.</assertion>
***************
*** 53,62 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingOperation-1051" class="component" part="1" section="2" subsection="09">For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingMessageReference-1052" class="component" part="1" section="2" subsection="10">For each Binding Message Reference component in the binding message references property of a Binding Operation component, the interface message reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1053" class="document" part="1" section="2" subsection="10">If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1054" class="document" part="1" section="2" subsection="10">If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-1055" class="component" part="1" section="2" subsection="11">For each Binding Fault Reference component in the binding fault references property of a Binding Operation component, the interface fault reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1056" class="document" part="1" section="2" subsection="11">The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1057" class="document" part="1" section="2" subsection="11">If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1058" class="document" part="1" section="2" subsection="11">If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-1059" class="component" part="1" section="2" subsection="11">There MUST be an Interface Fault Reference component in the interface fault references of the Interface Operation being bound with message label equal to the effective message label and with interface fault equal to an Interface Fault component with name equal to the actual value of the refattribute information item.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Service-1060" class="component" part="1" section="2" subsection="12">For each Service component in the services property of a Description component, the name property MUST be unique.</assertion>
--- 53,62 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingOperation-1051" class="component" part="1" section="2" subsection="09">For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingMessageReference-1052" class="component" part="1" section="2" subsection="10">For each Binding Message Reference component in the binding message references property of a Binding Operation component, the interface message reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1053" class="document" part="1" section="2" subsection="10">If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1054" class="document" part="1" section="2" subsection="10">If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-1055" class="component" part="1" section="2" subsection="11">For each Binding Fault Reference component in the binding fault references property of a Binding Operation component, the interface fault reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1056" class="document" part="1" section="2" subsection="11">The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1057" class="document" part="1" section="2" subsection="11">If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-1058" class="document" part="1" section="2" subsection="11">If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-1059" class="component" part="1" section="2" subsection="11">There MUST be an Interface Fault Reference component in the interface fault references of the Interface Operation being bound with message label equal to the effective message label and with interface fault equal to an Interface Fault component with name equal to the actual value of the refattribute information item.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Service-1060" class="component" part="1" section="2" subsection="12">For each Service component in the services property of a Description component, the name property MUST be unique.</assertion>
***************
*** 65,70 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Equivalence-1063" class="component" part="1" section="2" subsection="15">Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="QName-resolution-1064" class="document" part="1" section="2" subsection="17">A Description component MUST NOT have such broken references.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Compare-URI-IRI-1065" class="component" part="1" section="2" subsection="18">When such absolute URIs and IRIs are being compared to determine equivalence (see ) they MUST be compared character-by-character as indicated in .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1066" class="document" part="1" section="3" subsection="01">A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace unless an xs:import or xs:schemaelement information item for that namespace is present or the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Description-1067" class="component" part="1" section="3" subsection="01">For each component in the imported namespace, a corresponding Element Declaration component or Type Definition component MUST appear in the element declarations or type definitions property respectively of the Description component corresponding to the WSDL document that imports the schema, or that imports directly or indirectly a WSDL document that imports the schema.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Description-1068" class="component" part="1" section="3" subsection="01">Schema components not in an imported namespace MUST NOT appear in the element declarations or type definitions properties.</assertion>
--- 65,70 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Equivalence-1063" class="component" part="1" section="2" subsection="15">Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="QName-resolution-1064" class="document" part="1" section="2" subsection="17">A Description component MUST NOT have such broken references.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Compare-URI-IRI-1065" class="component" part="1" section="2" subsection="18">When such absolute URIs and IRIs are being compared to determine equivalence (see ), they MUST be compared character-by-character as indicated in .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1066" class="document" part="1" section="3" subsection="01">A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace UNLESS an xs:import or xs:schemaelement information item for that namespace is present OR the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Description-1067" class="component" part="1" section="3" subsection="01">For each component in the imported namespace, a corresponding Element Declaration component or Type Definition component MUST appear in the element declarations or type definitions property respectively of the Description component corresponding to the WSDL document that imports the schema, or that imports directly or indirectly a WSDL document that imports the schema.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Description-1068" class="component" part="1" section="3" subsection="01">Schema components not in an imported namespace MUST NOT appear in the element declarations or type definitions properties.</assertion>
***************
*** 74,78 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Description-1072" class="component" part="1" section="3" subsection="01">Schema components not defined or declared in the inlined schema document or included by xs:include MUST NOT appear in the element declarations or type definitions properties.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1073" class="document" part="1" section="3" subsection="01">A WSDL 2.0 document MUST NOT define the same element or type in more than one inlined schema.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-1074" class="document" part="1" section="3" subsection="02">A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:typeselement information item, which references, names, and locates the schema instance (an “import” element information item).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1075" class="document" part="1" section="3" subsection="02">A specification of extension syntax for an alternative schema language MUST use a namespace that is different than the namespace of XML Schema.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1076" class="document" part="1" section="3" subsection="02">The namespace used for an alternate schema language MUST be an absolute IRI.</assertion>
--- 74,78 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Description-1072" class="component" part="1" section="3" subsection="01">Schema components not defined or declared in the inlined schema document or included by xs:include MUST NOT appear in the element declarations or type definitions properties.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1073" class="document" part="1" section="3" subsection="01">A WSDL 2.0 document MUST NOT define the same element or type in more than one inlined schema.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-1074" class="document" part="1" section="3" subsection="02">A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:typeselement information item, which references, names, and locates the schema instance (an importelement information item).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1075" class="document" part="1" section="3" subsection="02">A specification of extension syntax for an alternative schema language MUST use a namespace that is different than the namespace of XML Schema.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-1076" class="document" part="1" section="3" subsection="02">The namespace used for an alternate schema language MUST be an absolute IRI.</assertion>
***************
*** 83,100 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Include-1081" class="document" part="1" section="4" subsection="01">The actual value of the targetNamespaceattribute information item of the included WSDL 2.0 document MUST match the actual value of the targetNamespaceattribute information item of the descriptionelement information item which is the [parent] of the includeelement information item.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1082" class="document" part="1" section="4" subsection="02">As with XML schema, any WSDL 2.0 document that references a foreign component MUST have a wsdl:importelement information item for the associated foreign namespace (but which does not necessarily provide a locationattribute information item that identifies the WSDL 2.0 document in which the referenced component is defined).</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1083" class="document" part="1" section="4" subsection="02">If a WSDL 2.0 document contains more than one wsdl:importelement information item for a given value of the namespaceattribute information item then they MUST provide different values for the locationattribute information item.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1084" class="document" part="1" section="4" subsection="02">This value MUST NOT match the actual value of targetNamespaceattribute information item in the enclosing WSDL 2.0 document.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1085" class="document" part="1" section="4" subsection="02">If the location attribute in the importelement information item is dereferencable then it MUST reference a WSDL 2.0 document.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1086" class="document" part="1" section="4" subsection="02">If the locationattribute information item of the importelement information item is dereferencable, then the actual value of the namespaceattribute information item MUST be identical to the actual value of the targetNamespaceattribute information item of the referenced WSDL 2.0 document.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="ImportInclude-1087" class="component" part="1" section="4" subsection="03">The semantics of an extension MUST NOT depend on how components are brought into a component model instance via &lt;import&gt; or &lt;include&gt;.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="Extension-1088" class="component" part="1" section="6" subsection="00">The meaning of an extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace IRI.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-1089" class="component" part="1" section="6" subsection="01">An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of the WSDL 2.0 document.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-1090" class="component" part="1" section="6" subsection="01">If a WSDL 2.0 document declares an extension as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-1091" class="component" part="1" section="6" subsection="01">Therefore, the Web service MUST support every extension that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension that is declared as mandatory.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-1092" class="document" part="1" section="7" subsection="00">It MUST NOT appear on a wsdl:description element or any of its children/descendants.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-1093" class="component" part="1" section="7" subsection="01">Its actual value MUST be a list of pairs of IRIs; where the first IRI of a pair, which MUST be an absolute IRI as defined in , indicates a WSDL 2.0 (or 1.1) namespace name, and, the second a hint as to the location of a WSDL 2.0 document defining WSDL 2.0 components (or WSDL 1.1 elements ) for that namespace name.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-1094" class="document" part="1" section="7" subsection="01">For each pair of IRIs, if the location IRI of the pair is dereferencable then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="NodeIdentity-2001" class="exchange" part="2" section="2" subsection="00">A node MAY be accessible via more than one physical address or transport.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="MEPDescriptiveness-2002" class="exchange" part="2" section="2" subsection="00">by some prior agreement, another node and/or the service MAY send other messages (to each other or to other nodes) that are not described by the pattern.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultPropagation-2003" class="exchange" part="2" section="2" subsection="02">Nodes that generate faults MUST attempt to propagate the faults in accordance with the governing ruleset, but it is understood that any delivery of a network message is best effort, not guaranteed.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultPropagation-2004" class="exchange" part="2" section="2" subsection="02">When a fault is generated, the generating node MUST attempt to propagate the fault, and MUST do so in the direction and to the recipient specified by the ruleset.</assertion>
--- 83,100 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Include-1081" class="document" part="1" section="4" subsection="01">The actual value of the targetNamespaceattribute information item of the included WSDL 2.0 document MUST match the actual value of the targetNamespaceattribute information item of the descriptionelement information item which is the [parent] of the includeelement information item.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1082" class="document" part="1" section="4" subsection="02">As with XML schema, any WSDL 2.0 document that references a foreign component MUST have a wsdl:importelement information item for the associated foreign namespace (but which does not necessarily provide a locationattribute information item that identifies the WSDL 2.0 document in which the referenced component is defined).</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1083" class="document" part="1" section="4" subsection="02">If a WSDL 2.0 document contains more than one wsdl:importelement information item for a given value of the namespaceattribute information item, then they MUST provide different values for the locationattribute information item.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1084" class="document" part="1" section="4" subsection="02">This value MUST NOT match the actual value of targetNamespaceattribute information item in the enclosing WSDL 2.0 document.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1085" class="document" part="1" section="4" subsection="02">If the location attribute in the importelement information item is dereferencable, then it MUST reference a WSDL 2.0 document.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-1086" class="document" part="1" section="4" subsection="02">If the locationattribute information item of the importelement information item is dereferencable, then the actual value of the namespaceattribute information item MUST be identical to the actual value of the targetNamespaceattribute information item of the referenced WSDL 2.0 document (see ).</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="ImportInclude-1087" class="component" part="1" section="4" subsection="03">The semantics of an extension MUST NOT depend on how components are brought into a component model instance via &lt;import&gt; or &lt;include&gt;.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="Extension-1088" class="component" part="1" section="6" subsection="00">The meaning of an extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace IRI.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-1089" class="component" part="1" section="6" subsection="01">An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of a WSDL 2.0 document.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-1090" class="component" part="1" section="6" subsection="01">If a WSDL 2.0 document declares an extension as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-1091" class="component" part="1" section="6" subsection="01">Therefore, the Web service MUST support every extension that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension that is declared as mandatory.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-1092" class="document" part="1" section="7" subsection="00">It MUST NOT appear on a wsdl:description element or any of its children/descendants.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-1093" class="component" part="1" section="7" subsection="01">Its actual value MUST be a list of pairs of IRIs; where the first IRI of a pair, which MUST be an absolute IRI as defined in , indicates a WSDL 2.0 (or 1.1) namespace name, and, the second a hint as to the location of a WSDL 2.0 document defining WSDL 2.0 components (or WSDL 1.1 elements ) for that namespace name.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-1094" class="document" part="1" section="7" subsection="01">For each pair of IRIs, if the location IRI of the pair is dereferencable, then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="NodeIdentity-2001" class="exchange" part="2" section="2" subsection="00">A node MAY be accessible via more than one physical address or transport.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="MEPDescriptiveness-2002" class="exchange" part="2" section="2" subsection="00">by some prior agreement, another node and/or the service MAY send messages (to each other or to other nodes) that are not described by the pattern.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultPropagation-2003" class="exchange" part="2" section="2" subsection="02">Nodes that generate faults MUST attempt to propagate the faults in accordance with the governing ruleset, but it is understood that any delivery of a network message is best effort, not guaranteed.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultPropagation-2004" class="exchange" part="2" section="2" subsection="02">When a fault is generated, the generating node MUST attempt to propagate the fault, and MUST do so in the direction and to the recipient specified by the ruleset.</assertion>
***************
*** 104,108 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultDelivery-2008" class="exchange" part="2" section="2" subsection="02">The fault message MUST be delivered to the same target node as the message it replaces, unless otherwise specified by an extension or binding extension. If there is no path to this node, the fault MUST be discarded.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="MessageTriggersFault-2009" class="exchange" part="2" section="2" subsection="02">When the Message Triggers Fault propagation rule is in effect, any message, including the first in the pattern, MAY trigger a fault message, which MUST have opposite direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultDelivery-2010" class="exchange" part="2" section="2" subsection="02">The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension of binding extension. Any node MAY propagate a fault message, and MUST not do so more than once for each triggering message. If there is no path to the originator, the fault MUST be discarded.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="NoFaults-2011" class="exchange" part="2" section="2" subsection="02">When the No Faults propagation rule is in effect, faults MUST NOT be propagated.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOnlyComposition-2012" class="component" part="2" section="2" subsection="03">The in-only message exchange pattern consists of exactly one message as follows:</assertion>
--- 104,108 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultDelivery-2008" class="exchange" part="2" section="2" subsection="02">The fault message MUST be delivered to the same target node as the message it replaces, unless otherwise specified by an extension or binding extension. If there is no path to this node, the fault MUST be discarded.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="MessageTriggersFault-2009" class="exchange" part="2" section="2" subsection="02">When the Message Triggers Fault propagation rule is in effect, any message, including the first in the pattern, MAY trigger a fault message, which MUST have opposite direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultDelivery-2010" class="exchange" part="2" section="2" subsection="02">The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension or binding extension. Any node MAY propagate a fault message, and MUST NOT do so more than once for each triggering message. If there is no path to the originator, the fault MUST be discarded.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="NoFaults-2011" class="exchange" part="2" section="2" subsection="02">When the No Faults propagation rule is in effect, faults MUST NOT be propagated.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOnlyComposition-2012" class="component" part="2" section="2" subsection="03">The in-only message exchange pattern consists of exactly one message as follows:</assertion>
***************
*** 151,157 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPHTTPProperties-2064" class="component" part="2" section="5" subsection="00">These properties MUST NOT be used unless the underlying protocol is HTTP.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2065" class="component" part="2" section="5" subsection="03">When formulating the SOAP envelope to be transmitted, the contents of the payload (i.e., the contents of the SOAP Body element information item of the SOAP envelope) MUST be what is defined by the corresponding Interface Message Reference component.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2066" class="message" part="2" section="5" subsection="03">If the value is #none then the payload MUST be empty.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2067" class="message" part="2" section="5" subsection="03">If the value is #element then the payload MUST be the element information item identified by the element declaration property of the Interface Message Reference component.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2068" class="component" part="2" section="5" subsection="03">If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2069" class="component" part="2" section="5" subsection="04">Every SOAP binding MUST indicate what version of SOAP is in use for the operations of the interface that this binding applies to.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2070" class="component" part="2" section="5" subsection="05">Every SOAP binding MUST indicate what underlying protocol is in use.</assertion>
--- 151,157 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPHTTPProperties-2064" class="component" part="2" section="5" subsection="00">These properties MUST NOT be used unless the underlying protocol is HTTP.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2065" class="component" part="2" section="5" subsection="03">When formulating the SOAP envelope to be transmitted, the contents of the payload (i.e., the contents of the SOAP Body element information item of the SOAP envelope) MUST be what is defined by the corresponding Interface Message Reference component.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2066" class="message" part="2" section="5" subsection="03">If the value is #none, then the payload MUST be empty.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2067" class="message" part="2" section="5" subsection="03">If the value is #element, then the payload MUST be the element information item identified by the element declaration property of the Interface Message Reference component.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2068" class="component" part="2" section="5" subsection="03">If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2069" class="component" part="2" section="5" subsection="04">Every SOAP binding MUST indicate what version of SOAP is in use for the operations of the interface that this binding applies to.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPBinding-2070" class="component" part="2" section="5" subsection="05">Every SOAP binding MUST indicate what underlying protocol is in use.</assertion>
***************
*** 172,178 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2085" class="component" part="2" section="6" subsection="04">When formulating the HTTP fault message to be transmitted, content encoding for a given Binding Fault component is determined as follows:</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2086" class="component" part="2" section="6" subsection="04">When formulating the HTTP message to be transmitted, the contents of the payload (i.e. the contents of the HTTP message body) MUST be what is defined by the corresponding Interface Message Reference or Interface Fault components, serialized as specified by the serialization format used.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2087" class="component" part="2" section="6" subsection="04">If the value is #none then the payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2088" class="component" part="2" section="6" subsection="04">If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined in an extension specification to indicate how to map those components into the HTTP envelope.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2089" class="component" part="2" section="6" subsection="04">The serialization rules for messages whose message content model is either #element or #any and for fault messages are as follows:</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPHeader-2090" class="component" part="2" section="6" subsection="04">If the http headers property as defined in section exists and is not empty in a Binding Message Reference or Binding Fault component, HTTP headers conforming to each HTTP Header component contained in this http headers property MAY be serialized as follows:</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPHeader-2091" class="component" part="2" section="6" subsection="04">The HTTP binding MUST NOT set an HTTP header field corresponding to the value of the name property already set by another mechanism, such as the HTTP stack or another feature.</assertion>
--- 172,178 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2085" class="component" part="2" section="6" subsection="04">When formulating the HTTP fault message to be transmitted, content encoding for a given Binding Fault component is determined as follows:</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2086" class="component" part="2" section="6" subsection="04">When formulating the HTTP message to be transmitted, the contents of the payload (i.e. the contents of the HTTP message body) MUST be what is defined by the corresponding Interface Message Reference or Interface Fault components, serialized as specified by the serialization format used.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2087" class="component" part="2" section="6" subsection="04">If the value is #none, then the payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2088" class="component" part="2" section="6" subsection="04">If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined in an extension specification to indicate how to map those components into the HTTP envelope.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2089" class="component" part="2" section="6" subsection="04">The serialization rules for messages whose message content model is either #element or #any, AND the serialization rules for fault messages, are as follows:</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPHeader-2090" class="component" part="2" section="6" subsection="04">If the http headers property as defined in section exists and is not empty in a Binding Message Reference or Binding Fault component, HTTP headers conforming to each HTTP Header component contained in this http headers property MAY be serialized as follows:</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPHeader-2091" class="component" part="2" section="6" subsection="04">The HTTP binding MUST NOT set an HTTP header field corresponding to the value of the name property already set by another mechanism, such as the HTTP stack or another feature.</assertion>
***************
*** 194,197 ****
--- 194,198 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPSerialization-2107" class="component" part="2" section="6" subsection="08">If the style property of the Interface Operation bound has a value of http://www.w3.org/ns/wsdl/style/iri as defined in , and if the http location property of the Binding Operation component is present, the value of the http location property component is used as a template</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPSerialization-2108" class="component" part="2" section="6" subsection="08">The resulting IRI MUST be mapped to an URI for use in the HTTP Request as per section 3.1 "Mapping of IRIs to URIs" of the IRI specification .</assertion>
+ <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPSerialization-2106" class="component" part="2" section="6" subsection="08">The http location property MUST conform to the following EBNF grammar, which represents the patterns for constructing the request IRI:</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPSerialization-2109" class="component" part="2" section="6" subsection="08">The local name in a template SHOULD match at least one element from the instance data of the input message.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPSerialization-2110" class="message" part="2" section="6" subsection="08">Cited elements (i.e. elements referenced in templates) MUST NOT carry an xs:nil attribute whose value is true</assertion>

Index: assertion-coverage.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/assertion-coverage.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -C 2 -d -r1.9 -r1.10
*** assertion-coverage.xml 15 Mar 2007 19:44:49 -0000 1.9
--- assertion-coverage.xml 27 Jun 2007 14:54:49 -0000 1.10
***************
*** 2,8 ****
  <?xml-stylesheet type="text/xsl" href="assertion-coverage.xsl"?>
 
! <assertions more-violations="0" two-violations="7" one-violation="132" part2="118" part1="94" message="4" exchange="13" document="43" component="152">
  <assertion part="1" count="4" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1044" class="component" name="Binding-1044">
! <synopsis>If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components) then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</synopsis>
  <test id="Binding-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-5B"/>
  <test id="Binding-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-6B"/>
--- 2,8 ----
  <?xml-stylesheet type="text/xsl" href="assertion-coverage.xsl"?>
 
! <assertions more-violations="0" two-violations="7" one-violation="132" part2="119" part1="94" message="4" exchange="13" document="43" component="153">
  <assertion part="1" count="4" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1044" class="component" name="Binding-1044">
! <synopsis>If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components), then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</synopsis>
  <test id="Binding-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-5B"/>
  <test id="Binding-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-6B"/>
***************
*** 11,15 ****
  </assertion>
  <assertion part="1" count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1045" class="component" name="Binding-1045">
! <synopsis>A Binding component that defines bindings for an Interface component MUST define bindings for all the operations and faults of that Interface component.</synopsis>
  <test id="Binding-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-1B"/>
  <test id="Binding-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-4B"/>
--- 11,15 ----
  </assertion>
  <assertion part="1" count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1045" class="component" name="Binding-1045">
! <synopsis>A Binding component that defines bindings for an Interface component MUST define bindings for all the operations of that Interface component.</synopsis>
  <test id="Binding-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-1B"/>
  <test id="Binding-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-4B"/>
***************
*** 52,56 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Compare-URI-IRI-1065" class="component" name="Compare-URI-IRI-1065">
! <synopsis>When such absolute URIs and IRIs are being compared to determine equivalence (see ) they MUST be compared character-by-character as indicated in .</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1001" class="component" name="Description-1001">
--- 52,56 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Compare-URI-IRI-1065" class="component" name="Compare-URI-IRI-1065">
! <synopsis>When such absolute URIs and IRIs are being compared to determine equivalence (see ), they MUST be compared character-by-character as indicated in .</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1001" class="component" name="Description-1001">
***************
*** 99,103 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-1089" class="component" name="Extensibility-1089">
! <synopsis>An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of the WSDL 2.0 document.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-1090" class="component" name="Extensibility-1090">
--- 99,103 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-1089" class="component" name="Extensibility-1089">
! <synopsis>An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of a WSDL 2.0 document.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-1090" class="component" name="Extensibility-1090">
***************
*** 114,118 ****
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2010" class="exchange" name="FaultDelivery-2010">
! <synopsis>The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension of binding extension. Any node MAY propagate a fault message, and MUST not do so more than once for each triggering message. If there is no path to the originator, the fault MUST be discarded.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagation-2003" class="exchange" name="FaultPropagation-2003">
--- 114,118 ----
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2010" class="exchange" name="FaultDelivery-2010">
! <synopsis>The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension or binding extension. Any node MAY propagate a fault message, and MUST NOT do so more than once for each triggering message. If there is no path to the originator, the fault MUST be discarded.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagation-2003" class="exchange" name="FaultPropagation-2003">
***************
*** 144,154 ****
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2087" class="component" name="HTTPBinding-2087">
! <synopsis>If the value is #none then the payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2088" class="component" name="HTTPBinding-2088">
! <synopsis>If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined in an extension specification to indicate how to map those components into the HTTP envelope.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2089" class="component" name="HTTPBinding-2089">
! <synopsis>The serialization rules for messages whose message content model is either #element or #any and for fault messages are as follows:</synopsis>
  </assertion>
  <assertion part="2" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingFault-2105" class="component" name="HTTPBindingFault-2105">
--- 144,154 ----
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2087" class="component" name="HTTPBinding-2087">
! <synopsis>If the value is #none, then the payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2088" class="component" name="HTTPBinding-2088">
! <synopsis>If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined in an extension specification to indicate how to map those components into the HTTP envelope.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2089" class="component" name="HTTPBinding-2089">
! <synopsis>The serialization rules for messages whose message content model is either #element or #any, AND the serialization rules for fault messages, are as follows:</synopsis>
  </assertion>
  <assertion part="2" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingFault-2105" class="component" name="HTTPBindingFault-2105">
***************
*** 212,215 ****
--- 212,218 ----
  <synopsis>The value of the http input serialization, http output serialization and http fault serialization properties is similar to the value allowed for the Accept HTTP header defined by the HTTP 1.1 specification, Section 14.1 (see ) and MUST follow the production rules defined in that section except for the following:</synopsis>
  </assertion>
+ <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2106" class="component" name="HTTPSerialization-2106">
+ <synopsis>The http location property MUST conform to the following EBNF grammar, which represents the patterns for constructing the request IRI:</synopsis>
+ </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2107" class="component" name="HTTPSerialization-2107">
  <synopsis>If the style property of the Interface Operation bound has a value of http://www.w3.org/ns/wsdl/style/iri as defined in , and if the http location property of the Binding Operation component is present, the value of the http location property component is used as a template</synopsis>
***************
*** 270,274 ****
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1083" class="document" name="Import-1083">
! <synopsis>If a WSDL 2.0 document contains more than one wsdl:importelement information item for a given value of the namespaceattribute information item then they MUST provide different values for the locationattribute information item.</synopsis>
  <test id="Import-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-5B"/>
  </assertion>
--- 273,277 ----
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1083" class="document" name="Import-1083">
! <synopsis>If a WSDL 2.0 document contains more than one wsdl:importelement information item for a given value of the namespaceattribute information item, then they MUST provide different values for the locationattribute information item.</synopsis>
  <test id="Import-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-5B"/>
  </assertion>
***************
*** 278,282 ****
  </assertion>
  <assertion part="1" count="4" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1085" class="document" name="Import-1085">
! <synopsis>If the location attribute in the importelement information item is dereferencable then it MUST reference a WSDL 2.0 document.</synopsis>
  <test id="Chameleon-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-2B"/>
  <test id="Import-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-2B"/>
--- 281,285 ----
  </assertion>
  <assertion part="1" count="4" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1085" class="document" name="Import-1085">
! <synopsis>If the location attribute in the importelement information item is dereferencable, then it MUST reference a WSDL 2.0 document.</synopsis>
  <test id="Chameleon-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-2B"/>
  <test id="Import-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-2B"/>
***************
*** 285,289 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1086" class="document" name="Import-1086">
! <synopsis>If the locationattribute information item of the importelement information item is dereferencable, then the actual value of the namespaceattribute information item MUST be identical to the actual value of the targetNamespaceattribute information item of the referenced WSDL 2.0 document.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#ImportInclude-1087" class="component" name="ImportInclude-1087">
--- 288,292 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1086" class="document" name="Import-1086">
! <synopsis>If the locationattribute information item of the importelement information item is dereferencable, then the actual value of the namespaceattribute information item MUST be identical to the actual value of the targetNamespaceattribute information item of the referenced WSDL 2.0 document (see ).</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#ImportInclude-1087" class="component" name="ImportInclude-1087">
***************
*** 311,315 ****
  </assertion>
  <assertion part="1" count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-1009" class="component" name="Interface-1009">
! <synopsis>To avoid circular definitions, an interface MUST NOT appear as an element of the set of interfaces it extends, either directly or indirectly.</synopsis>
  <test id="Interface-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-2B"/>
  <test id="Interface-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-3B"/>
--- 314,318 ----
  </assertion>
  <assertion part="1" count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-1009" class="component" name="Interface-1009">
! <synopsis>To avoid circular definitions, an interface MUST NOT appear in the set of interfaces it extends, either directly or indirectly.</synopsis>
  <test id="Interface-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-2B"/>
  <test id="Interface-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-3B"/>
***************
*** 343,347 ****
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1017" class="document" name="InterfaceFault-1017">
! <synopsis>If the elementattribute information item has a value then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</synopsis>
  <test id="InterfaceFault-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-1B"/>
  </assertion>
--- 346,350 ----
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1017" class="document" name="InterfaceFault-1017">
! <synopsis>If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</synopsis>
  <test id="InterfaceFault-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-1B"/>
  </assertion>
***************
*** 358,362 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-1040" class="document" name="InterfaceFaultReference-1040">
! <synopsis>The messageLabelattribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given direction if the message exchange pattern of the parent Interface Operation component has more than one fault with that direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1025" class="component" name="InterfaceMessageReference-1025">
--- 361,365 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-1040" class="document" name="InterfaceFaultReference-1040">
! <synopsis>The messageLabelattribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given direction, if the message exchange pattern of the parent Interface Operation component has more than one fault with that direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1025" class="component" name="InterfaceMessageReference-1025">
***************
*** 371,375 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1028" class="component" name="InterfaceMessageReference-1028">
! <synopsis>When the message content model property has the value #any or #none the element declaration property MUST be empty.</synopsis>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1029" class="component" name="InterfaceMessageReference-1029">
--- 374,378 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1028" class="component" name="InterfaceMessageReference-1028">
! <synopsis>When the message content model property has the value #any or #none, the element declaration property MUST be empty.</synopsis>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1029" class="component" name="InterfaceMessageReference-1029">
***************
*** 378,382 ****
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1036" class="document" name="InterfaceMessageReference-1036">
! <synopsis>If the elementattribute information item has a value then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</synopsis>
  <test id="InterfaceMessageReference-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceMessageReference-4B"/>
  </assertion>
--- 381,385 ----
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1036" class="document" name="InterfaceMessageReference-1036">
! <synopsis>If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</synopsis>
  <test id="InterfaceMessageReference-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceMessageReference-4B"/>
  </assertion>
***************
*** 454,466 ****
  </assertion>
  <assertion part="1" count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-1094" class="document" name="Location-1094">
! <synopsis>For each pair of IRIs, if the location IRI of the pair is dereferencable then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</synopsis>
  <test id="Location-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-6B"/>
  <test id="Location-7B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-7B"/>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MEP-1022" class="component" name="MEP-1022">
! <synopsis>A message exchange pattern is uniquely identified by an absolute IRI which is used as the value of the message exchange pattern property of the Interface Operation component, and it specifies the fault propagation ruleset that its faults obey.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPDescriptiveness-2002" class="exchange" name="MEPDescriptiveness-2002">
! <synopsis>by some prior agreement, another node and/or the service MAY send other messages (to each other or to other nodes) that are not described by the pattern.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPTermination-2006" class="exchange" name="MEPTermination-2006">
--- 457,469 ----
  </assertion>
  <assertion part="1" count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-1094" class="document" name="Location-1094">
! <synopsis>For each pair of IRIs, if the location IRI of the pair is dereferencable, then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</synopsis>
  <test id="Location-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-6B"/>
  <test id="Location-7B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-7B"/>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MEP-1022" class="component" name="MEP-1022">
! <synopsis>A message exchange pattern is itself uniquely identified by an absolute IRI, which is used as the value of the message exchange pattern property of the Interface Operation component, and which specifies the fault propagation ruleset that its faults obey.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPDescriptiveness-2002" class="exchange" name="MEPDescriptiveness-2002">
! <synopsis>by some prior agreement, another node and/or the service MAY send messages (to each other or to other nodes) that are not described by the pattern.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPTermination-2006" class="exchange" name="MEPTermination-2006">
***************
*** 472,479 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1030" class="document" name="MessageLabel-1030">
! <synopsis>If the messageLabelattribute information item of an interface message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1031" class="document" name="MessageLabel-1031">
! <synopsis>If the messageLabelattribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1032" class="document" name="MessageLabel-1032">
--- 475,482 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1030" class="document" name="MessageLabel-1030">
! <synopsis>If the messageLabelattribute information item of an interface message reference element information item is present, then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1031" class="document" name="MessageLabel-1031">
! <synopsis>If the messageLabelattribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1032" class="document" name="MessageLabel-1032">
***************
*** 490,519 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1041" class="document" name="MessageLabel-1041">
! <synopsis>The messageLabelattribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1042" class="document" name="MessageLabel-1042">
! <synopsis>If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1043" class="document" name="MessageLabel-1043">
! <synopsis>If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1053" class="document" name="MessageLabel-1053">
! <synopsis>If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</synopsis>
  <test id="BindingMessageReference-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-3B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1054" class="document" name="MessageLabel-1054">
! <synopsis>If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</synopsis>
  <test id="BindingMessageReference-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-2B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1056" class="document" name="MessageLabel-1056">
! <synopsis>The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</synopsis>
  <test id="BindingFaultReference-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1057" class="document" name="MessageLabel-1057">
! <synopsis>If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</synopsis>
  <test id="BindingFaultReference-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-3B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1058" class="document" name="MessageLabel-1058">
! <synopsis>If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</synopsis>
  <test id="BindingFaultReference-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B"/>
  </assertion>
--- 493,522 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1041" class="document" name="MessageLabel-1041">
! <synopsis>The messageLabelattribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1042" class="document" name="MessageLabel-1042">
! <synopsis>If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1043" class="document" name="MessageLabel-1043">
! <synopsis>If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</synopsis>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1053" class="document" name="MessageLabel-1053">
! <synopsis>If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</synopsis>
  <test id="BindingMessageReference-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-3B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1054" class="document" name="MessageLabel-1054">
! <synopsis>If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</synopsis>
  <test id="BindingMessageReference-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-2B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1056" class="document" name="MessageLabel-1056">
! <synopsis>The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.</synopsis>
  <test id="BindingFaultReference-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1057" class="document" name="MessageLabel-1057">
! <synopsis>If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</synopsis>
  <test id="BindingFaultReference-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-3B"/>
  </assertion>
  <assertion part="1" count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1058" class="document" name="MessageLabel-1058">
! <synopsis>If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</synopsis>
  <test id="BindingFaultReference-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B"/>
  </assertion>
***************
*** 636,640 ****
  </assertion>
  <assertion part="1" count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-1066" class="document" name="Schema-1066">
! <synopsis>A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace unless an xs:import or xs:schemaelement information item for that namespace is present or the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</synopsis>
  <test id="Chameleon-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-1B"/>
  <test id="Import-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-1B"/>
--- 639,643 ----
  </assertion>
  <assertion part="1" count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-1066" class="document" name="Schema-1066">
! <synopsis>A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace UNLESS an xs:import or xs:schemaelement information item for that namespace is present OR the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</synopsis>
  <test id="Chameleon-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-1B"/>
  <test id="Import-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-1B"/>
***************
*** 679,689 ****
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2066" class="message" name="SOAPBinding-2066">
! <synopsis>If the value is #none then the payload MUST be empty.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2067" class="message" name="SOAPBinding-2067">
! <synopsis>If the value is #element then the payload MUST be the element information item identified by the element declaration property of the Interface Message Reference component.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2068" class="component" name="SOAPBinding-2068">
! <synopsis>If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2069" class="component" name="SOAPBinding-2069">
--- 682,692 ----
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2066" class="message" name="SOAPBinding-2066">
! <synopsis>If the value is #none, then the payload MUST be empty.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2067" class="message" name="SOAPBinding-2067">
! <synopsis>If the value is #element, then the payload MUST be the element information item identified by the element declaration property of the Interface Message Reference component.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2068" class="component" name="SOAPBinding-2068">
! <synopsis>If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.</synopsis>
  </assertion>
  <assertion part="2" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2069" class="component" name="SOAPBinding-2069">
***************
*** 735,739 ****
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1074" class="document" name="Types-1074">
! <synopsis>A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:typeselement information item, which references, names, and locates the schema instance (an “import” element information item).</synopsis>
  </assertion>
  <assertion part="1" count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1077" class="document" name="Types-1077">
--- 738,742 ----
  </assertion>
  <assertion part="1" count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1074" class="document" name="Types-1074">
! <synopsis>A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:typeselement information item, which references, names, and locates the schema instance (an importelement information item).</synopsis>
  </assertion>
  <assertion part="1" count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1077" class="document" name="Types-1077">

Index: assertion-coverage.xsl
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/assertion-coverage.xsl,v
retrieving revision 1.4
retrieving revision 1.5
diff -C 2 -d -r1.4 -r1.5
*** assertion-coverage.xsl 28 Nov 2006 05:38:02 -0000 1.4
--- assertion-coverage.xsl 27 Jun 2007 14:54:49 -0000 1.5
***************
*** 141,145 ****
  <xsl:param name="part"/>
  <xsl:param name="width" select="1.0"/>
! <div style="border:1px solid black; padding:0px; width:{round($width*200)+2}px; height:18px; font-size:x-small; font-weight:bold">
  <xsl:variable name="total" select="count(assertions/assertion[@part=$part])"/>
  <xsl:variable name="none" select="count(assertions/assertion[@part=$part][@count = 0])"/>
--- 141,145 ----
  <xsl:param name="part"/>
  <xsl:param name="width" select="1.0"/>
! <div style="border:1px solid black; padding:0px; width:{round($width*200)+3}px; height:18px; font-size:x-small; font-weight:bold">
  <xsl:variable name="total" select="count(assertions/assertion[@part=$part])"/>
  <xsl:variable name="none" select="count(assertions/assertion[@part=$part][@count = 0])"/>

Index: Assertion-coverage.html
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/Assertion-coverage.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -C 2 -d -r1.9 -r1.10
*** Assertion-coverage.html 15 Mar 2007 19:44:49 -0000 1.9
--- Assertion-coverage.html 27 Jun 2007 14:54:49 -0000 1.10
***************
*** 15,21 ****
  <table>
  <tr>
! <td><b>212 assertions</b></td><td>
  <div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold">
! <span style="position:absolute">94</span><img alt="44% have coverage" width="89" height="16" src="green.gif"><span style="position:absolute">118</span><img alt="56% have no coverage" width="111" height="16" src="red.gif"></div>
  </td>
  </tr>
--- 15,21 ----
  <table>
  <tr>
! <td><b>213 assertions</b></td><td>
  <div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold">
! <span style="position:absolute">94</span><img alt="44% have coverage" width="88" height="16" src="green.gif"><span style="position:absolute">119</span><img alt="56% have no coverage" width="112" height="16" src="red.gif"></div>
  </td>
  </tr>
***************
*** 27,37 ****
  </tr>
  <tr>
! <td>Part 2 (118 assertions)</td><td>
! <div style="border:1px solid black; padding:0px; width:113px; height:18px; font-size:x-small; font-weight:bold">
! <span style="position:absolute">39</span><img alt="33% have coverage" width="37" height="16" src="green.gif"><span style="position:absolute">79</span><img alt="67% have no coverage" width="75" height="16" src="red.gif"></div>
  </td>
  </tr>
  </table>
! <p>Assertion breakdown: 152 component,
  43 document,
  13 exchange,
--- 27,37 ----
  </tr>
  <tr>
! <td>Part 2 (119 assertions)</td><td>
! <div style="border:1px solid black; padding:0px; width:115px; height:18px; font-size:x-small; font-weight:bold">
! <span style="position:absolute">39</span><img alt="33% have coverage" width="37" height="16" src="green.gif"><span style="position:absolute">80</span><img alt="67% have no coverage" width="75" height="16" src="red.gif"></div>
  </td>
  </tr>
  </table>
! <p>Assertion breakdown: 153 component,
  43 document,
  13 exchange,
***************
*** 53,60 ****
  <tbody>
  <tr>
! <td class="good">&nbsp;</td><td class="count">4</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1044">Binding-1044</a></td><td class="synopsis">If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components) then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-5B">Binding-5B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-6B">Binding-6B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chat-1B">Chat-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-1B">HTTPBinding-1B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1045">Binding-1045</a></td><td class="synopsis">A Binding component that defines bindings for an Interface component MUST define bindings for all the operations and faults of that Interface component.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-1B">Binding-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-4B">Binding-4B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chat-2B">Chat-2B</a>] </td>
  </tr>
  <tr>
--- 53,60 ----
  <tbody>
  <tr>
! <td class="good">&nbsp;</td><td class="count">4</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1044">Binding-1044</a></td><td class="synopsis">If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components), then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-5B">Binding-5B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-6B">Binding-6B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chat-1B">Chat-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-1B">HTTPBinding-1B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-1045">Binding-1045</a></td><td class="synopsis">A Binding component that defines bindings for an Interface component MUST define bindings for all the operations of that Interface component.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-1B">Binding-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-4B">Binding-4B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chat-2B">Chat-2B</a>] </td>
  </tr>
  <tr>
***************
*** 86,90 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Compare-URI-IRI-1065">Compare-URI-IRI-1065</a></td><td class="synopsis">When such absolute URIs and IRIs are being compared to determine equivalence (see ) they MUST be compared character-by-character as indicated in .</td><td class="class">component</td><td></td>
  </tr>
  <tr>
--- 86,90 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Compare-URI-IRI-1065">Compare-URI-IRI-1065</a></td><td class="synopsis">When such absolute URIs and IRIs are being compared to determine equivalence (see ), they MUST be compared character-by-character as indicated in .</td><td class="class">component</td><td></td>
  </tr>
  <tr>
***************
*** 128,132 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-1089">Extensibility-1089</a></td><td class="synopsis">An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of the WSDL 2.0 document.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
--- 128,132 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-1089">Extensibility-1089</a></td><td class="synopsis">An extension that is NOT marked as mandatory MUST NOT invalidate the meaning of any part of a WSDL 2.0 document.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
***************
*** 143,147 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2010">FaultDelivery-2010</a></td><td class="synopsis">The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension of binding extension. Any node MAY propagate a fault message, and MUST not do so more than once for each triggering message. If there is no path to the originator, the fault MUST be discarded.</td><td class="class">exchange</td><td></td>
  </tr>
  <tr>
--- 143,147 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2010">FaultDelivery-2010</a></td><td class="synopsis">The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension or binding extension. Any node MAY propagate a fault message, and MUST NOT do so more than once for each triggering message. If there is no path to the originator, the fault MUST be discarded.</td><td class="class">exchange</td><td></td>
  </tr>
  <tr>
***************
*** 173,183 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2087">HTTPBinding-2087</a></td><td class="synopsis">If the value is #none then the payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2088">HTTPBinding-2088</a></td><td class="synopsis">If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined in an extension specification to indicate how to map those components into the HTTP envelope.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2089">HTTPBinding-2089</a></td><td class="synopsis">The serialization rules for messages whose message content model is either #element or #any and for fault messages are as follows:</td><td class="class">component</td><td></td>
  </tr>
  <tr>
--- 173,183 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2087">HTTPBinding-2087</a></td><td class="synopsis">If the value is #none, then the payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2088">HTTPBinding-2088</a></td><td class="synopsis">If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined in an extension specification to indicate how to map those components into the HTTP envelope.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2089">HTTPBinding-2089</a></td><td class="synopsis">The serialization rules for messages whose message content model is either #element or #any, AND the serialization rules for fault messages, are as follows:</td><td class="class">component</td><td></td>
  </tr>
  <tr>
***************
*** 236,239 ****
--- 236,242 ----
  </tr>
  <tr>
+ <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2106">HTTPSerialization-2106</a></td><td class="synopsis">The http location property MUST conform to the following EBNF grammar, which represents the patterns for constructing the request IRI:</td><td class="class">component</td><td></td>
+ </tr>
+ <tr>
  <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2107">HTTPSerialization-2107</a></td><td class="synopsis">If the style property of the Interface Operation bound has a value of http://www.w3.org/ns/wsdl/style/iri as defined in , and if the http location property of the Binding Operation component is present, the value of the http location property component is used as a template</td><td class="class">component</td><td></td>
  </tr>
***************
*** 290,294 ****
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1083">Import-1083</a></td><td class="synopsis">If a WSDL 2.0 document contains more than one wsdl:importelement information item for a given value of the namespaceattribute information item then they MUST provide different values for the locationattribute information item.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-5B">Import-5B</a>] </td>
  </tr>
  <tr>
--- 293,297 ----
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1083">Import-1083</a></td><td class="synopsis">If a WSDL 2.0 document contains more than one wsdl:importelement information item for a given value of the namespaceattribute information item, then they MUST provide different values for the locationattribute information item.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-5B">Import-5B</a>] </td>
  </tr>
  <tr>
***************
*** 296,303 ****
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">4</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1085">Import-1085</a></td><td class="synopsis">If the location attribute in the importelement information item is dereferencable then it MUST reference a WSDL 2.0 document.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-2B">Chameleon-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-2B">Import-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-7B">Import-7B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-8B">Import-8B</a>] </td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1086">Import-1086</a></td><td class="synopsis">If the locationattribute information item of the importelement information item is dereferencable, then the actual value of the namespaceattribute information item MUST be identical to the actual value of the targetNamespaceattribute information item of the referenced WSDL 2.0 document.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
--- 299,306 ----
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">4</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1085">Import-1085</a></td><td class="synopsis">If the location attribute in the importelement information item is dereferencable, then it MUST reference a WSDL 2.0 document.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-2B">Chameleon-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-2B">Import-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-7B">Import-7B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-8B">Import-8B</a>] </td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1086">Import-1086</a></td><td class="synopsis">If the locationattribute information item of the importelement information item is dereferencable, then the actual value of the namespaceattribute information item MUST be identical to the actual value of the targetNamespaceattribute information item of the referenced WSDL 2.0 document (see ).</td><td class="class">document</td><td></td>
  </tr>
  <tr>
***************
*** 323,327 ****
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-1009">Interface-1009</a></td><td class="synopsis">To avoid circular definitions, an interface MUST NOT appear as an element of the set of interfaces it extends, either directly or indirectly.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-2B">Interface-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-3B">Interface-3B</a>] </td>
  </tr>
  <tr>
--- 326,330 ----
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-1009">Interface-1009</a></td><td class="synopsis">To avoid circular definitions, an interface MUST NOT appear in the set of interfaces it extends, either directly or indirectly.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-2B">Interface-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-3B">Interface-3B</a>] </td>
  </tr>
  <tr>
***************
*** 347,351 ****
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1017">InterfaceFault-1017</a></td><td class="synopsis">If the elementattribute information item has a value then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-1B">InterfaceFault-1B</a>] </td>
  </tr>
  <tr>
--- 350,354 ----
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1017">InterfaceFault-1017</a></td><td class="synopsis">If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-1B">InterfaceFault-1B</a>] </td>
  </tr>
  <tr>
***************
*** 359,363 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-1040">InterfaceFaultReference-1040</a></td><td class="synopsis">The messageLabelattribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given direction if the message exchange pattern of the parent Interface Operation component has more than one fault with that direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
--- 362,366 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-1040">InterfaceFaultReference-1040</a></td><td class="synopsis">The messageLabelattribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given direction, if the message exchange pattern of the parent Interface Operation component has more than one fault with that direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
***************
*** 371,375 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1028">InterfaceMessageReference-1028</a></td><td class="synopsis">When the message content model property has the value #any or #none the element declaration property MUST be empty.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
--- 374,378 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1028">InterfaceMessageReference-1028</a></td><td class="synopsis">When the message content model property has the value #any or #none, the element declaration property MUST be empty.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
***************
*** 377,381 ****
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1036">InterfaceMessageReference-1036</a></td><td class="synopsis">If the elementattribute information item has a value then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceMessageReference-4B">InterfaceMessageReference-4B</a>] </td>
  </tr>
  <tr>
--- 380,384 ----
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1036">InterfaceMessageReference-1036</a></td><td class="synopsis">If the elementattribute information item has a value, then it MUST resolve to an Element Declaration component from the element declarations property of the Description component.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceMessageReference-4B">InterfaceMessageReference-4B</a>] </td>
  </tr>
  <tr>
***************
*** 425,435 ****
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-1094">Location-1094</a></td><td class="synopsis">For each pair of IRIs, if the location IRI of the pair is dereferencable then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-6B">Location-6B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-7B">Location-7B</a>] </td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MEP-1022">MEP-1022</a></td><td class="synopsis">A message exchange pattern is uniquely identified by an absolute IRI which is used as the value of the message exchange pattern property of the Interface Operation component, and it specifies the fault propagation ruleset that its faults obey.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPDescriptiveness-2002">MEPDescriptiveness-2002</a></td><td class="synopsis">by some prior agreement, another node and/or the service MAY send other messages (to each other or to other nodes) that are not described by the pattern.</td><td class="class">exchange</td><td></td>
  </tr>
  <tr>
--- 428,438 ----
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-1094">Location-1094</a></td><td class="synopsis">For each pair of IRIs, if the location IRI of the pair is dereferencable, then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-6B">Location-6B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Location-7B">Location-7B</a>] </td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MEP-1022">MEP-1022</a></td><td class="synopsis">A message exchange pattern is itself uniquely identified by an absolute IRI, which is used as the value of the message exchange pattern property of the Interface Operation component, and which specifies the fault propagation ruleset that its faults obey.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPDescriptiveness-2002">MEPDescriptiveness-2002</a></td><td class="synopsis">by some prior agreement, another node and/or the service MAY send messages (to each other or to other nodes) that are not described by the pattern.</td><td class="class">exchange</td><td></td>
  </tr>
  <tr>
***************
*** 440,447 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1030">MessageLabel-1030</a></td><td class="synopsis">If the messageLabelattribute information item of an interface message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1031">MessageLabel-1031</a></td><td class="synopsis">If the messageLabelattribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
--- 443,450 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1030">MessageLabel-1030</a></td><td class="synopsis">If the messageLabelattribute information item of an interface message reference element information item is present, then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1031">MessageLabel-1031</a></td><td class="synopsis">If the messageLabelattribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
***************
*** 458,483 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1041">MessageLabel-1041</a></td><td class="synopsis">The messageLabelattribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1042">MessageLabel-1042</a></td><td class="synopsis">If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1043">MessageLabel-1043</a></td><td class="synopsis">If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1053">MessageLabel-1053</a></td><td class="synopsis">If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-3B">BindingMessageReference-3B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1054">MessageLabel-1054</a></td><td class="synopsis">If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-2B">BindingMessageReference-2B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1056">MessageLabel-1056</a></td><td class="synopsis">The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B">BindingFaultReference-2B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1057">MessageLabel-1057</a></td><td class="synopsis">If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-3B">BindingFaultReference-3B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1058">MessageLabel-1058</a></td><td class="synopsis">If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B">BindingFaultReference-2B</a>] </td>
  </tr>
  <tr>
--- 461,486 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1041">MessageLabel-1041</a></td><td class="synopsis">The messageLabelattribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1042">MessageLabel-1042</a></td><td class="synopsis">If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1043">MessageLabel-1043</a></td><td class="synopsis">If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</td><td class="class">document</td><td></td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1053">MessageLabel-1053</a></td><td class="synopsis">If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-3B">BindingMessageReference-3B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1054">MessageLabel-1054</a></td><td class="synopsis">If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingMessageReference-2B">BindingMessageReference-2B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1056">MessageLabel-1056</a></td><td class="synopsis">The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with direction equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B">BindingFaultReference-2B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1057">MessageLabel-1057</a></td><td class="synopsis">If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the message label of some placeholder message with direction equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-3B">BindingFaultReference-3B</a>] </td>
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-1058">MessageLabel-1058</a></td><td class="synopsis">If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with direction equal to the message direction.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/BindingFaultReference-2B">BindingFaultReference-2B</a>] </td>
  </tr>
  <tr>
***************
*** 566,570 ****
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-1066">Schema-1066</a></td><td class="synopsis">A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace unless an xs:import or xs:schemaelement information item for that namespace is present or the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-1B">Chameleon-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-1B">Import-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-3B">Import-3B</a>] </td>
  </tr>
  <tr>
--- 569,573 ----
  </tr>
  <tr>
! <td class="good">&nbsp;</td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-1066">Schema-1066</a></td><td class="synopsis">A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace UNLESS an xs:import or xs:schemaelement information item for that namespace is present OR the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-1B">Chameleon-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-1B">Import-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-3B">Import-3B</a>] </td>
  </tr>
  <tr>
***************
*** 599,609 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2066">SOAPBinding-2066</a></td><td class="synopsis">If the value is #none then the payload MUST be empty.</td><td class="class">message</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2067">SOAPBinding-2067</a></td><td class="synopsis">If the value is #element then the payload MUST be the element information item identified by the element declaration property of the Interface Message Reference component.</td><td class="class">message</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2068">SOAPBinding-2068</a></td><td class="synopsis">If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
--- 602,612 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2066">SOAPBinding-2066</a></td><td class="synopsis">If the value is #none, then the payload MUST be empty.</td><td class="class">message</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2067">SOAPBinding-2067</a></td><td class="synopsis">If the value is #element, then the payload MUST be the element information item identified by the element declaration property of the Interface Message Reference component.</td><td class="class">message</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2068">SOAPBinding-2068</a></td><td class="synopsis">If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ), then additional binding rules MUST be defined to indicate how to map those components into the SOAP envelope.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
***************
*** 653,657 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1074">Types-1074</a></td><td class="synopsis">A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:typeselement information item, which references, names, and locates the schema instance (an &ldquo;import&rdquo; element information item).</td><td class="class">document</td><td></td>
  </tr>
  <tr>
--- 656,660 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1074">Types-1074</a></td><td class="synopsis">A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:typeselement information item, which references, names, and locates the schema instance (an importelement information item).</td><td class="class">document</td><td></td>
  </tr>
  <tr>

Index: Dashboard.html
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/Dashboard.html,v
retrieving revision 1.84
retrieving revision 1.85
diff -C 2 -d -r1.84 -r1.85
*** Dashboard.html 27 Jun 2007 14:34:05 -0000 1.84
--- Dashboard.html 27 Jun 2007 14:54:49 -0000 1.85
***************
*** 15,19 ****
  .explanatory {font-size:smaller}
  </style></head><body><h2>WSDL 2.0 Interop Dashboard</h2><address>Generated June 27 2007,
! 1410</address><p class="explanatory">This page summarizes the results of interop testing of the
  <a href="http://www.w3.org/TR/wsdl20">WSDL 2.0 Core</a> and
  <a href="http://www.w3.org/TR/wsdl20-adjuncts">WSDL 2.0 Adjuncts</a> specifications,
--- 15,19 ----
  .explanatory {font-size:smaller}
  </style></head><body><h2>WSDL 2.0 Interop Dashboard</h2><address>Generated June 27 2007,
! 1452</address><p class="explanatory">This page summarizes the results of interop testing of the
  <a href="http://www.w3.org/TR/wsdl20">WSDL 2.0 Core</a> and
  <a href="http://www.w3.org/TR/wsdl20-adjuncts">WSDL 2.0 Adjuncts</a> specifications,
***************
*** 27,29 ****
  of the component model.</p></td></tr><tr><td></td><td colspan="3"><table><tr><td><strong>Woden</strong></td><td><strong>WSDL XSLT</strong></td><td><strong>Canon</strong></td></tr><tr><td style="border:1px solid black; padding:0px; width:201px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">81</span><img alt="79% passed" width="159" height="16" src="green.gif"></td><td style="border:1px solid black; padding:0px; width:201px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">101</span><img alt="99% passed" width="198" height="16" src="green.gif"></td><td style="border:1px solid black; padding:0px; width:201px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">81</span><img alt="79% passed" width="159" height="16" src="green.gif"></td></tr></table></td></tr><tr><td colspan="4"><hr></td></tr><tr><td><div class="heading">Message Exchange Test Results</div></td><td><p class="explanatory">(<a href="results-messages/Message-tests-results.html">details</a>)</p></td><td colspan="2"><p class="explanatory">These results represent the analysis of log files of message exchanges based
  on complex WSDL 2.0 documents, with each implementation run pair-wise against the others.</p></td></tr><tr><td colspan="4"><table xmlns="http://www.w3.org/2002/ws/desc/logs/"><thead><tr><th/><th><nobr>Canon</nobr> &gt;&gt; <nobr>Canon</nobr></th><th><nobr>Canon</nobr> &gt;&gt; <nobr>WSO2 WSAS</nobr></th><th><nobr>WSO2 WSAS</nobr> &gt;&gt; <nobr>Canon</nobr></th><th><nobr>WSO2 WSAS</nobr> &gt;&gt; <nobr>WSO2 WSAS</nobr></th></tr></thead><tbody><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-1G">MessageTest-1G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-4G">MessageTest-4G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">4</span><img alt="67% passed" width="100" height="16" src="green.gif"/><span style="position:absolute">2</span><img alt="33% failed" width="50" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">4</span><img alt="67% passed" width="100" height="16" src="green.gif"/><span style="position:absolute">2</span><img alt="33% failed" width="50" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">5</span><img alt="83% passed" width="125" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="17% failed" width="25" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-5G">MessageTest-5G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-6G">MessageTest-6G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">13</span><img alt="93% passed" width="139" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="7% failed" width="11" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#ModuleComposition-1G">ModuleComposition-1G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#LocationTemplate-1G">LocationTemplate-1G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">13</span><img alt="93% passed" width="139" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="7% failed" width="11" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">13</span><img alt="93% passed" width="139" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="7% failed" width="11" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#LocationTemplate-2G">LocationTemplate-2G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">5</span><img alt="83% passed" width="125" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="17% failed" width="25" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">5</span><img alt="83% passed" width="125" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="17% failed" width="25" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-2G">MessageTest-2G</a> (HTTP)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageMultipart-1G">MessageMultipart-1G</a> (HTTP)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">8</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-3G">MessageTest-3G</a> (HTTP)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">33</span><img alt="83% passed" width="124" height="16" src="green.gif"/><span style="position:absolute">7</span><img alt="18% failed" width="26" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">39</span><img alt="98% passed" width="146" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="3% failed" width="4" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">39</span><img alt="98% passed" width="146" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="3% failed" width="4" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">40</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr></tbody></table></td></tr><tr><td colspan="4"><hr></td></tr><tr><td><div class="heading">Validation Test Results</div></td><td><p class="explanatory">(<a href="results/Validation.html">details</a>)</p></td><td colspan="2"><p class="explanatory">These results represent the analysis of validation log files generated by validating implementations consuming both good and bad documents in the test suite.  Green and yellow both mean that the testcase was correctly validated, the difference being that a yellow indicates that the implementation did not correctly identify the specific assertion a "bad" testcase was designed fail on.</p></td></tr><tr><td></td><td colspan="3"><table><thead><tr><td><strong>Woden</strong></td><td><strong>Canon</strong></td></tr></thead><tbody><tr><td><div style="border:1px solid black; width:201px; height:16px; font-size:x-small; font-weight:bold"><span style="position:absolute">82</span><img alt="33.88429752066116% passed" width="67.76859504132231" height="16" src="green.gif"><span style="position:absolute">57</span><img alt="23.553719008264462% passed" width="47.107438016528924" height="16" src="yellow.gif"><span style="position:absolute">82</span><img alt="33.88429752066116% failed" width="67.76859504132231" height="16" src="red.gif"><span style="position:absolute">&nbsp;(21)</span></div></td><td><div style="border:1px solid black; width:201px; height:16px; font-size:x-small; font-weight:bold"><span style="position:absolute">65</span><img alt="26.859504132231404% passed" width="53.71900826446281" height="16" src="green.gif"><span style="position:absolute">82</span><img alt="33.88429752066116% passed" width="67.76859504132231" height="16" src="yellow.gif"><span style="position:absolute">73</span><img alt="30.165289256198346% failed" width="60.33057851239669" height="16" src="red.gif"><span style="position:absolute">&nbsp;(22)</span></div></td></tr></tbody></table></td></tr><tr><td colspan="4"><hr></td></tr><tr><td class="group" colspan="4"><h3>Test Suite Completeness</h3></td></tr><tr><td><div class="heading">Test Case Coverage</div></td><td><p class="explanatory">(<a href="Test-suite-coverage-summary.html">details</a>)</p></td><td colspan="2"><p class="explanatory">An analysis of the use of various parts of the WSDL syntax (elements, attributes, uris) in the test collection.  Green indicates 4 or more occurances of the construct, yellow indicates less than 4 occurances, and red indicates zero occurances.</p></td></tr><tr><td></td><td colspan="3"><div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold; margin:0px"><span style="position:absolute">73%</span><img alt="75 have good coverage" width="146" height="16" src="green.gif"><span style="position:absolute">27%</span><img alt="28 have minimal coverage" width="54" height="16" src="yellow.gif"></div></td></tr><tr><td colspan="4"><hr></td></tr><tr><td><div class="heading">Assertion Coverage</div></td><td><p class="explanatory">(<a href="Assertion-coverage.html">details</a>)</p></td><td colspan="2"><p class="explanatory">Count of assertions violated by "bad" testcases, compared with the total number of assertions
! identified in the specs.</p></td></tr><tr><td></td><td colspan="3"><div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">94</span><img alt="44% have coverage" width="89" height="16" src="green.gif"><span style="position:absolute">118</span><img alt="56% have no coverage" width="111" height="16" src="red.gif"></div></td></tr></table></body></html>
\ No newline at end of file
--- 27,29 ----
  of the component model.</p></td></tr><tr><td></td><td colspan="3"><table><tr><td><strong>Woden</strong></td><td><strong>WSDL XSLT</strong></td><td><strong>Canon</strong></td></tr><tr><td style="border:1px solid black; padding:0px; width:201px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">81</span><img alt="79% passed" width="159" height="16" src="green.gif"></td><td style="border:1px solid black; padding:0px; width:201px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">101</span><img alt="99% passed" width="198" height="16" src="green.gif"></td><td style="border:1px solid black; padding:0px; width:201px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">81</span><img alt="79% passed" width="159" height="16" src="green.gif"></td></tr></table></td></tr><tr><td colspan="4"><hr></td></tr><tr><td><div class="heading">Message Exchange Test Results</div></td><td><p class="explanatory">(<a href="results-messages/Message-tests-results.html">details</a>)</p></td><td colspan="2"><p class="explanatory">These results represent the analysis of log files of message exchanges based
  on complex WSDL 2.0 documents, with each implementation run pair-wise against the others.</p></td></tr><tr><td colspan="4"><table xmlns="http://www.w3.org/2002/ws/desc/logs/"><thead><tr><th/><th><nobr>Canon</nobr> &gt;&gt; <nobr>Canon</nobr></th><th><nobr>Canon</nobr> &gt;&gt; <nobr>WSO2 WSAS</nobr></th><th><nobr>WSO2 WSAS</nobr> &gt;&gt; <nobr>Canon</nobr></th><th><nobr>WSO2 WSAS</nobr> &gt;&gt; <nobr>WSO2 WSAS</nobr></th></tr></thead><tbody><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-1G">MessageTest-1G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">28</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-4G">MessageTest-4G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">4</span><img alt="67% passed" width="100" height="16" src="green.gif"/><span style="position:absolute">2</span><img alt="33% failed" width="50" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">4</span><img alt="67% passed" width="100" height="16" src="green.gif"/><span style="position:absolute">2</span><img alt="33% failed" width="50" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">5</span><img alt="83% passed" width="125" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="17% failed" width="25" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-5G">MessageTest-5G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">12</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-6G">MessageTest-6G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">13</span><img alt="93% passed" width="139" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="7% failed" width="11" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#ModuleComposition-1G">ModuleComposition-1G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#LocationTemplate-1G">LocationTemplate-1G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">13</span><img alt="93% passed" width="139" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="7% failed" width="11" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">13</span><img alt="93% passed" width="139" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="7% failed" width="11" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">14</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#LocationTemplate-2G">LocationTemplate-2G</a> (SOAP12)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">5</span><img alt="83% passed" width="125" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="17% failed" width="25" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">5</span><img alt="83% passed" width="125" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="17% failed" width="25" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">6</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-2G">MessageTest-2G</a> (HTTP)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">16</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageMultipart-1G">MessageMultipart-1G</a> (HTTP)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; text-align:center">&nbsp;</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">8</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr><tr><td style="font-size:smaller"><a href="results-messages/Message-tests-results.html#MessageTest-3G">MessageTest-3G</a> (HTTP)</td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">33</span><img alt="83% passed" width="124" height="16" src="green.gif"/><span style="position:absolute">7</span><img alt="18% failed" width="26" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">39</span><img alt="98% passed" width="146" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="3% failed" width="4" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">39</span><img alt="98% passed" width="146" height="16" src="green.gif"/><span style="position:absolute">1</span><img alt="3% failed" width="4" height="16" src="red.gif"/></td><td style="border:1px solid black; padding:0px; width:150px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">40</span><img alt="100% passed" width="150" height="16" src="green.gif"/></td></tr></tbody></table></td></tr><tr><td colspan="4"><hr></td></tr><tr><td><div class="heading">Validation Test Results</div></td><td><p class="explanatory">(<a href="results/Validation.html">details</a>)</p></td><td colspan="2"><p class="explanatory">These results represent the analysis of validation log files generated by validating implementations consuming both good and bad documents in the test suite.  Green and yellow both mean that the testcase was correctly validated, the difference being that a yellow indicates that the implementation did not correctly identify the specific assertion a "bad" testcase was designed fail on.</p></td></tr><tr><td></td><td colspan="3"><table><thead><tr><td><strong>Woden</strong></td><td><strong>Canon</strong></td></tr></thead><tbody><tr><td><div style="border:1px solid black; width:201px; height:16px; font-size:x-small; font-weight:bold"><span style="position:absolute">82</span><img alt="33.88429752066116% passed" width="67.76859504132231" height="16" src="green.gif"><span style="position:absolute">57</span><img alt="23.553719008264462% passed" width="47.107438016528924" height="16" src="yellow.gif"><span style="position:absolute">82</span><img alt="33.88429752066116% failed" width="67.76859504132231" height="16" src="red.gif"><span style="position:absolute">&nbsp;(21)</span></div></td><td><div style="border:1px solid black; width:201px; height:16px; font-size:x-small; font-weight:bold"><span style="position:absolute">65</span><img alt="26.859504132231404% passed" width="53.71900826446281" height="16" src="green.gif"><span style="position:absolute">82</span><img alt="33.88429752066116% passed" width="67.76859504132231" height="16" src="yellow.gif"><span style="position:absolute">73</span><img alt="30.165289256198346% failed" width="60.33057851239669" height="16" src="red.gif"><span style="position:absolute">&nbsp;(22)</span></div></td></tr></tbody></table></td></tr><tr><td colspan="4"><hr></td></tr><tr><td class="group" colspan="4"><h3>Test Suite Completeness</h3></td></tr><tr><td><div class="heading">Test Case Coverage</div></td><td><p class="explanatory">(<a href="Test-suite-coverage-summary.html">details</a>)</p></td><td colspan="2"><p class="explanatory">An analysis of the use of various parts of the WSDL syntax (elements, attributes, uris) in the test collection.  Green indicates 4 or more occurances of the construct, yellow indicates less than 4 occurances, and red indicates zero occurances.</p></td></tr><tr><td></td><td colspan="3"><div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold; margin:0px"><span style="position:absolute">73%</span><img alt="75 have good coverage" width="146" height="16" src="green.gif"><span style="position:absolute">27%</span><img alt="28 have minimal coverage" width="54" height="16" src="yellow.gif"></div></td></tr><tr><td colspan="4"><hr></td></tr><tr><td><div class="heading">Assertion Coverage</div></td><td><p class="explanatory">(<a href="Assertion-coverage.html">details</a>)</p></td><td colspan="2"><p class="explanatory">Count of assertions violated by "bad" testcases, compared with the total number of assertions
! identified in the specs.</p></td></tr><tr><td></td><td colspan="3"><div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">94</span><img alt="44% have coverage" width="88" height="16" src="green.gif"><span style="position:absolute">119</span><img alt="56% have no coverage" width="112" height="16" src="red.gif"></div></td></tr></table></body></html>
\ No newline at end of file