- From: Jonathan Marsh via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 16 Nov 2006 14:22:09 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/test-suite
In directory hutz:/tmp/cvs-serv3782/test-suite
Modified Files:
assertions-report.xsl test-suite-coverage-summary.xml
build.xml assertions.xml coverage.xsl
Added Files:
yellow.gif assertion-coverage.xsl assertions-extractor.xsl
dashboard.xsl Dashboard.html Assertion-coverage.html
assertion-coverage.xml assertions-collect-results.xsl
green.gif red.gif
Log Message:
Integrated into Dashboard.html generation, including misc. improvements and renaming.
--- NEW FILE: assertions-collect-results.xsl ---
<?xml version="1.0" encoding="UTF-8"?>
<!--
This stylesheet has not been automatically generated. Do
edit it!
-->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="tm"
xmlns:tm="http://www.w3.org/2006/02/wsdl/TestMetadata" version="1.0">
<xsl:strip-space elements="*" />
<xsl:output method="xml" indent="yes" />
<xsl:template match="/">
<ViolatesAssertions>
<xsl:for-each select='test-suite/test-case'>
<xsl:variable name='test-id' select='@id'/>
<xsl:for-each select="document(@href)/tm:TestMetadata//tm:ViolatesAssertion">
<ViolateAssertion assertion='{.}' test-id='{$test-id}'
origin="{normalize-space(ancestor::tm:TestMetadata/tm:Identifier)}">
</ViolateAssertion>
</xsl:for-each>
</xsl:for-each>
</ViolatesAssertions>
</xsl:template>
</xsl:stylesheet>
Index: test-suite-coverage-summary.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/test-suite-coverage-summary.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -C 2 -d -r1.19 -r1.20
*** test-suite-coverage-summary.xml 15 Nov 2006 11:41:10 -0000 1.19
--- test-suite-coverage-summary.xml 16 Nov 2006 14:22:06 -0000 1.20
***************
*** 5,11 ****
<coverage>
! <DSTAMP>20061115</DSTAMP>
! <TSTAMP>0638</TSTAMP>
! <TODAY>November 15 2006</TODAY>
<total>171</total>
<good>67</good>
--- 5,11 ----
<coverage>
! <DSTAMP>20061116</DSTAMP>
! <TSTAMP>0621</TSTAMP>
! <TODAY>November 16 2006</TODAY>
<total>171</total>
<good>67</good>
***************
*** 39,42 ****
--- 39,47 ----
<item xpath="/wsdl:description/wsdl:interface/wsdl:operation[@pattern='http://www.w3.org/2006/01/wsdl/robust-in-only']" count="5"/>
<item xpath="/wsdl:description/wsdl:interface/wsdl:operation[@pattern='http://www.w3.org/2006/01/wsdl/in-out']" count="131"/>
+ <item xpath="/wsdl:description/wsdl:interface/wsdl:operation[@pattern='http://www.w3.org/2006/01/wsdl/in-opt-out']" count="0"/>
+ <item xpath="/wsdl:description/wsdl:interface/wsdl:operation[@pattern='http://www.w3.org/2006/01/wsdl/out-only']" count="0"/>
+ <item xpath="/wsdl:description/wsdl:interface/wsdl:operation[@pattern='http://www.w3.org/2006/01/wsdl/robust-out-only']" count="1"/>
+ <item xpath="/wsdl:description/wsdl:interface/wsdl:operation[@pattern='http://www.w3.org/2006/01/wsdl/out-in']" count="0"/>
+ <item xpath="/wsdl:description/wsdl:interface/wsdl:operation[@pattern='http://www.w3.org/2006/01/wsdl/out-opt-in']" count="0"/>
<item xpath="/wsdl:description/wsdl:interface/wsdl:operation/wsdl:input" count="174"/>
<item xpath="/wsdl:description/wsdl:interface/wsdl:operation/wsdl:input/@messageLabel" count="107"/>
***************
*** 70,73 ****
--- 75,84 ----
<item xpath="/wsdl:description/wsdl:service/wsdl:endpoint" count="51"/>
<item xpath="/wsdl:description/wsdl:service/wsdl:endpoint/@address" count="31"/>
+ <item xpath="/wsdl:description//wsdl:feature" count="0"/>
+ <item xpath="/wsdl:description//wsdl:feature/@required" count="0"/>
+ <item xpath="/wsdl:description/wsdl:interface/wsdl:feature" count="0"/>
+ <item xpath="/wsdl:description/wsdl:interface/wsdl:operation/wsdl:feature" count="0"/>
+ <item xpath="/wsdl:description/wsdl:binding/wsdl:feature" count="0"/>
+ <item xpath="/wsdl:description//wsdl:property" count="0"/>
<item xpath="/wsdl:description/wsdl:binding/@wsoap:version" count="6"/>
<item xpath="/wsdl:description/wsdl:binding/@wsoap:protocol" count="34"/>
--- NEW FILE: green.gif ---
(This appears to be a binary file; contents omitted.)
--- NEW FILE: assertion-coverage.xsl ---
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html" indent="yes"/>
<xsl:template match="/">
<html lang="en-us">
<head>
<title>Assertion Coverage Report</title>
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/base.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<style type="text/css"> .border th, .border td { border: 1px solid black; padding:
0.5ex } .border th { background: #ccc } .good { background: green } .bad {
background: red } .class, .count { text-align: center } .bar { font-weight:
bold; } .synopsis { font-size: small } </style>
</head>
<body>
<h1>Assertion Coverage Report</h1>
<xsl:call-template name="assertion-summary"/>
<p>
<xsl:value-of select="count(assertions/assertion)"/> assertions
(<xsl:value-of select="assertions/@component"/> component,
<xsl:value-of select="assertions/@document"/> document,
<xsl:value-of select="assertions/@exchange" /> exchange,
<xsl:value-of select="assertions/@message"/> message).
<xsl:value-of select="assertions/@part1"/> for part 1,
<xsl:value-of select="assertions/@part2"/> for part 2.
</p>
<table class="border">
<thead>
<tr>
<th>Status</th>
<th>Count</th>
<th>Assertion</th>
<th>Synopsis</th>
<th>Class</th>
<th>Tests</th>
</tr>
</thead>
<tbody>
<xsl:for-each select="assertions/assertion">
<xsl:sort select="@name"/>
<tr>
<td>
<xsl:attribute name="class">
<xsl:choose>
<xsl:when test="@count = 0">bad</xsl:when>
<xsl:otherwise>good</xsl:otherwise>
</xsl:choose>
</xsl:attribute>
<xsl:text> </xsl:text>
</td>
<td class="count">
<xsl:value-of select="@count"/>
</td>
<td>
<a href="{@href}">
<xsl:value-of select="@name"/>
</a>
</td>
<td class="synopsis">
<xsl:value-of select="synopsis"/>
</td>
<td class="class">
<xsl:value-of select="@class"/>
</td>
<td>
<xsl:for-each select="test">
<xsl:text>[</xsl:text>
<a href="{@href}">
<xsl:value-of select="@id"/>
</a>
<xsl:text>] </xsl:text>
</xsl:for-each>
</td>
</tr>
</xsl:for-each>
</tbody>
</table>
</body>
</html>
</xsl:template>
<xsl:template name="assertion-summary">
<div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold">
<xsl:variable name="total" select="count(assertions/assertion)"/>
<xsl:variable name="none" select="count(assertions/assertion[@count = 0])"/>
<xsl:variable name="some" select="count(assertions/assertion[@count > 0])"/>
<xsl:variable name="percentage-none" select="$none div $total"/>
<xsl:variable name="percentage-some" select="$some div $total"/>
<xsl:if test="$percentage-some > .01">
<span style="position:absolute">
<xsl:value-of select="$some"/>
</span>
<img src="green.gif" height="16" width="{round(200*$percentage-some)}" alt="{round($percentage-some * 100)}% have coverage"/>
</xsl:if>
<xsl:if test="$percentage-none > .01">
<span style="position:absolute">
<xsl:value-of select="$none"/>
</span>
<img src="red.gif" height="16" width="{round(200*$percentage-none)}" alt="{round($percentage-none* 100)}% have no coverage"/>
</xsl:if>
</div>
</xsl:template>
</xsl:stylesheet>
--- NEW FILE: red.gif ---
(This appears to be a binary file; contents omitted.)
Index: assertions.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/assertions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C 2 -d -r1.2 -r1.3
*** assertions.xml 7 Jul 2006 15:59:54 -0000 1.2
--- assertions.xml 16 Nov 2006 14:22:06 -0000 1.3
***************
*** 15,21 ****
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-0026" 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-0027" 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="InterfaceFault-0028" class="component" part="1" section="2" subsection="02">The namespace name of the name property of each Interface Fault in this set MUST be the same as the namespace name of the name property of this Interface component.</assertion>
- <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceOperation-0029" class="component" part="1" section="2" subsection="02">The namespace name of the name property of each Interface Operation in this set MUST be the same as the namespace name of the name property of this Interface component.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-0030" 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-0031" class="document" part="1" section="2" subsection="02">Its value, if present, MUST contain absolute IRIs (see ).</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFault-0032" class="component" part="1" section="2" subsection="03">For each Interface Fault component in the interface faults property of an Interface component, the name property must be unique.</assertion>
--- 15,20 ----
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-0026" 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-0027" 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-0030" 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-0028" class="component" part="1" section="2" subsection="02">The list of xs:QName in an extendsattribute information item MUST NOT contain duplicates.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Interface-0031" class="document" part="1" section="2" subsection="02">Its value, if present, MUST contain absolute IRIs (see ).</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="InterfaceFault-0032" class="component" part="1" section="2" subsection="03">For each Interface Fault component in the interface faults property of an Interface component, the name property must be unique.</assertion>
***************
*** 88,92 ****
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-1300003" class="document" part="1" section="3" subsection="01">Similarly, components defined in an inlined XML schema are NOT automatically referenceable within WSDL 2.0 document that imported (using wsdl:import) the WSDL 2.0 document that inlines the schema (see for more details).</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-0018" 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="Schema-0019" class="document" part="1" section="3" subsection="01">The xs:schemaelement information item MUST contain a targetNamespaceattribute information item.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Types-0023" 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-0021" 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>
--- 87,90 ----
***************
*** 101,104 ****
--- 99,103 ----
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Import-0071" 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-0072" class="document" part="1" section="4" subsection="02">If the location attribute in the importelement information item is dereferencible then it MUST reference a WSDL 2.0 document and 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-1400002" 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 <import> or <include>.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="Extension-1600000" 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-0073" 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>
***************
*** 114,138 ****
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="FaultPropagationModification-2200103" class="component" part="2" section="2" subsection="02">However, extensions or binding extensions MAY modify these rulesets.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MEPTermination-2200104" class="exchange" part="2" section="2" subsection="02">Generation of a fault, regardless of ruleset, terminates the exchange.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="FaultReplacesMessage-2200201" class="exchange" part="2" section="2" subsection="02">Any message after the first in the pattern MAY be replaced with a fault message, which MUST have identical direction.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultDelivery-2200202" 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-2200301" class="exchange" part="2" section="2" subsection="02">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-2200302" 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-2200401" class="exchange" part="2" section="2" subsection="02">Faults MUST NOT be propagated.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOnlyComposition-2200501" class="component" part="2" section="2" subsection="03">This pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOnlyFaults-2200502" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustInOnlyComposition-2200601" class="component" part="2" section="2" subsection="03">This pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustInOnlyFaults-2200602" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOutComposition-2200701" class="component" part="2" section="2" subsection="03">This pattern consists of exactly two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOutFaults-2200702" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOptOutComposition-2200801" class="component" part="2" section="2" subsection="03">This pattern consists of one or two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOptOutFaults-2200802" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOnlyComposition-2200901" class="component" part="2" section="2" subsection="03">This pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOnlyFaults-2200902" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustOutOnlyComposition-2201001" class="component" part="2" section="2" subsection="03">This pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustOutOnlyFaults-2201002" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutInComposition-2201101" class="component" part="2" section="2" subsection="03">This pattern consists of exactly two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutInFaults-2201102" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOptInComposition-2201201" class="component" part="2" section="2" subsection="03">This pattern consists of one or two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOptInFaults-2201202" class="exchange" part="2" section="2" subsection="03">This pattern uses the rule .</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="OperationSafety-2300001" class="component" part="2" section="3" subsection="01">However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.4 of .</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="OperationSafety-2300002" class="document" part="2" section="3" subsection="01">An OPTIONAL safeattribute information item with the following Infoset properties:</assertion>
--- 113,137 ----
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="FaultPropagationModification-2200103" class="component" part="2" section="2" subsection="02">However, extensions or binding extensions MAY modify these rulesets.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MEPTermination-2200104" class="exchange" part="2" section="2" subsection="02">Generation of a fault, regardless of ruleset, terminates the exchange.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="FaultReplacesMessage-2200201" class="exchange" part="2" section="2" subsection="02">When the Fault Replaces Message propagation rule is in effect, any message after the first in the pattern MAY be replaced with a fault message, which MUST have identical direction.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="FaultDelivery-2200202" 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-2200301" class="exchange" part="2" section="2" subsection="02">When the Message Triggers Fault propagation rule is in effet, 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-2200302" 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-2200401" 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-2200501" class="component" part="2" section="2" subsection="03">The in-only message exchange pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOnlyFaults-2200502" class="exchange" part="2" section="2" subsection="03">The in-only message exchange pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustInOnlyComposition-2200601" class="component" part="2" section="2" subsection="03">The robust in-only message exchange pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustInOnlyFaults-2200602" class="exchange" part="2" section="2" subsection="03">The robust in-only message exchange pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOutComposition-2200701" class="component" part="2" section="2" subsection="03">The in-out message exchange pattern consists of exactly two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOutFaults-2200702" class="exchange" part="2" section="2" subsection="03">The in-out message exchange pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOptOutComposition-2200801" class="component" part="2" section="2" subsection="03">The in-optional-out message exchange pattern consists of one or two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="InOptOutFaults-2200802" class="exchange" part="2" section="2" subsection="03">The in-optional-out message exchange pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOnlyComposition-2200901" class="component" part="2" section="2" subsection="03">The out-only message exchange pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOnlyFaults-2200902" class="exchange" part="2" section="2" subsection="03">The out-only message exchange pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustOutOnlyComposition-2201001" class="component" part="2" section="2" subsection="03">The robust out-only message exchange pattern consists of exactly one message as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RobustOutOnlyFaults-2201002" class="exchange" part="2" section="2" subsection="03">The robust out-only message exchange pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutInComposition-2201101" class="component" part="2" section="2" subsection="03">The out-in message exchange pattern consists of exactly two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutInFaults-2201102" class="exchange" part="2" section="2" subsection="03">The out-in message exchange pattern uses the rule .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOptInComposition-2201201" class="component" part="2" section="2" subsection="03">The out-optional-in message exchange pattern consists of one or two messages, in order, as follows:</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="OutOptInFaults-2201202" class="exchange" part="2" section="2" subsection="03">The out-optional-in message exchange pattern uses the rule .</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="OperationSafety-2300001" class="component" part="2" section="3" subsection="01">However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.4 of .</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="false" id="OperationSafety-2300002" class="document" part="2" section="3" subsection="01">An OPTIONAL safeattribute information item with the following Infoset properties:</assertion>
***************
*** 144,148 ****
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5012" class="component" part="2" section="4" subsection="01">The element wildcard, if present, MUST appear after any elements.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5013" class="component" part="2" section="4" subsection="01">The output sequence MUST only contain elements.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5014" class="component" part="2" section="4" subsection="01">The sequence MUST contain only local element children.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5015" class="component" part="2" section="4" subsection="01">The local name of input element's QName MUST be the same as the Interface Operation component's name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5016" class="component" part="2" section="4" subsection="01">Input and output elements MUST both be in the same namespace.</assertion>
--- 143,147 ----
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5012" class="component" part="2" section="4" subsection="01">The element wildcard, if present, MUST appear after any elements.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5013" class="component" part="2" section="4" subsection="01">The output sequence MUST only contain elements.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5014" class="component" part="2" section="4" subsection="01">Both the input and output sequences MUST contain only local element children.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5015" class="component" part="2" section="4" subsection="01">The local name of input element's QName MUST be the same as the Interface Operation component's name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5016" class="component" part="2" section="4" subsection="01">Input and output elements MUST both be in the same namespace.</assertion>
***************
*** 150,170 ****
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5018" class="component" part="2" section="4" subsection="01">If elements with the same qualified name appear as children of both the input and output elements, then they MUST both be declared using the same named type.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5019" class="component" part="2" section="4" subsection="01">The input or output sequence MUST NOT contain multiple children elements declared with the same name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5020" class="component" part="2" section="4" subsection="01">Values for the second component MUST be chosen among the following four: "#in", "#out", "#inout" "#return".</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5021" class="component" part="2" section="4" subsection="01">The value of the first component of each pair (q, t) MUST be unique within the list.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5022" class="component" part="2" section="4" subsection="01">For each child element of the input and output messages of the operation, a pair (q, t) whose first component q is equal to the qualified name of that element MUST be present in the list, with the caveat that elements that appear with cardinality greater than one MUST be treated as a single element.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5023" class="component" part="2" section="4" subsection="01">For each pair (q, #in), there MUST be a child element of the input element with a name of q and there MUST NOT be a child element of the output element with the same name.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5024" class="component" part="2" section="4" subsection="01">For each pair (q, #out), there MUST be a child element of the output element with a name of q and there MUST NOT be a child element of the input element with the same name.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5025" class="component" part="2" section="4" subsection="01">For each pair (q, #inout), there MUST be a child element of the input element with a name of q and there MUST be a child element of the output element with the same name. Furthermore, those two elements MUST have the same type.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5026" class="component" part="2" section="4" subsection="01">For each pair (q, #return), there MUST be a child element of the output element with a name of q and there MUST NOT be a child element of the input element with the same name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5027" class="document" part="2" section="4" subsection="01">Additionally, each even-numbered item (0, 2, 4, ...) in the list MUST be of type xs:QName and each odd-numbered item (1, 3, 5, ...) in the list MUST be of the subtype of xs:token described in the previous paragraph.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5028" class="component" part="2" section="4" subsection="02">When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5029" class="component" part="2" section="4" subsection="02">The sequence MUST only contain elements.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5030" class="component" part="2" section="4" subsection="02">The sequence MUST contain only local element children. These child elements MAY contain the nillable attribute.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5031" class="component" part="2" section="4" subsection="02">The localPart of the element's QName MUST be the same as the Interface Operation component's name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5032" class="component" part="2" section="4" subsection="02">The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5034" class="component" part="2" section="4" subsection="02">If the children elements of the sequence are defined using an XML Schema type, they MUST derive from xs:simpleType, and MUST NOT be of the type or derive from xs:QName, xs:NOTATION, xs:hexBinary or xs:base64Binary.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5035" class="component" part="2" section="4" subsection="03">When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5036" class="component" part="2" section="4" subsection="03">The sequence MUST only contain elements.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5081" class="component" part="2" section="4" subsection="03">The sequence MUST contain only local element children. These child elements MAY contain the nillable attribute, and the attributes minOccurs and maxOccurs MUST have a value 1.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5037" class="component" part="2" section="4" subsection="03">The localPart of the element's QName MUST be the same as the Interface Operation component's name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5038" class="component" part="2" section="4" subsection="03">The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</assertion>
--- 149,171 ----
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5018" class="component" part="2" section="4" subsection="01">If elements with the same qualified name appear as children of both the input and output elements, then they MUST both be declared using the same named type.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="RPCStyle-5019" class="component" part="2" section="4" subsection="01">The input or output sequence MUST NOT contain multiple children elements declared with the same name.</assertion>
+ <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5019" class="component" part="2" section="4" subsection="01">OPTIONAL, but MUST be present when the style is RPC</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5020" class="component" part="2" section="4" subsection="01">Values for the second component MUST be chosen among the following four: "#in", "#out", "#inout" "#return".</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5021" class="component" part="2" section="4" subsection="01">The value of the first component of each pair (q, t) MUST be unique within the list.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5022" class="component" part="2" section="4" subsection="01">For each child element of the input and output messages of the operation, a pair (q, t), whose first component q is equal to the qualified name of that element, MUST be present in the list, with the caveat that elements that appear with cardinality greater than one MUST be treated as a single element.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5023" class="component" part="2" section="4" subsection="01">For each pair (q, #in), there MUST be a child element of the input element with a name of q. There MUST NOT be a child element of the output element with the name of q.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5024" class="component" part="2" section="4" subsection="01">For each pair (q, #out), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5025" class="component" part="2" section="4" subsection="01">For each pair (q, #inout), there MUST be a child element of the input element with a name of q. There MUST also be a child element of the output element with the name of q.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5026" class="component" part="2" section="4" subsection="01">For each pair (q, #return), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="WRPC-5027" class="document" part="2" section="4" subsection="01">Additionally, each even-numbered item (0, 2, 4, ...) in the list MUST be of type xs:QName and each odd-numbered item (1, 3, 5, ...) in the list MUST be of the subtype of xs:token described in the previous paragraph.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5028" class="component" part="2" section="4" subsection="02">When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5029" class="component" part="2" section="4" subsection="02">The sequence MUST only contain elements.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5030" class="component" part="2" section="4" subsection="02">The sequence MUST contain only local element children.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5031" class="component" part="2" section="4" subsection="02">The localPart of the element's QName MUST be the same as the Interface Operation component's name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5032" class="component" part="2" section="4" subsection="02">The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="IRIStyle-5034" class="component" part="2" section="4" subsection="02">The children elements of the sequence MUST derive from xs:simpleType, and MUST NOT be of the type or derive from xs:QName, xs:NOTATION, xs:hexBinary or xs:base64Binary.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5035" class="component" part="2" section="4" subsection="03">When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5036" class="component" part="2" section="4" subsection="03">The sequence MUST only contain elements.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5081" class="component" part="2" section="4" subsection="03">The sequence MUST contain only local element children.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5082" class="component" part="2" section="4" subsection="03">The attributes minOccurs and maxOccurs for these child elements MUST have a value 1.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5037" class="component" part="2" section="4" subsection="03">The localPart of the element's QName MUST be the same as the Interface Operation component's name.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="MultipartStyle-5038" class="component" part="2" section="4" subsection="03">The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</assertion>
***************
*** 187,192 ****
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPHTTPSelection-5054" class="component" part="2" section="5" subsection="10">This default binding rule is applicable when the value of the soap underlying protocol property of the Binding component is http://www.w3.org/2003/05/soap/bindings/HTTP/. If the SOAP MEP selected as specified above has the value http://www.w3.org/2003/05/soap/mep/request-response/ then the HTTP method used is POST. If the SOAP MEP selected has the value http://www.w3.org/2003/05/soap/mep/soap-response/ then the HTTP method used is GET.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPHTTPGeneration-5055" class="component" part="2" section="5" subsection="10">If the SOAP MEP selected is http://www.w3.org/2003/05/soap/mep/soap-response/ then the value of the SOAP http://www.w3.org/2003/05/soap/mep/ImmediateDestination property MUST be generated using the HTTP binding extension's rules for generating an IRI for HTTP GET (see ).</assertion>
- <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-2600001" class="component" part="2" section="6" subsection="00">a Binding component MAY exist without indicating a specific Interface component that it applies to. In this case there MUST NOT be any Binding Operation or Binding Fault components present in the Binding component.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-5056" class="component" part="2" section="6" subsection="03">When formulating the HTTP message to be transmitted, the HTTP request method used MUST be selected using one of the following:</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-5057" class="component" part="2" section="6" subsection="03">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-5061" class="component" part="2" section="6" subsection="03">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>
--- 188,194 ----
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPHTTPSelection-5054" class="component" part="2" section="5" subsection="10">This default binding rule is applicable when the value of the soap underlying protocol property of the Binding component is http://www.w3.org/2003/05/soap/bindings/HTTP/. If the SOAP MEP selected as specified above has the value http://www.w3.org/2003/05/soap/mep/request-response/ then the HTTP method used is POST. If the SOAP MEP selected has the value http://www.w3.org/2003/05/soap/mep/soap-response/ then the HTTP method used is GET.</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="SOAPHTTPGeneration-5055" class="component" part="2" section="5" subsection="10">If the SOAP MEP selected is http://www.w3.org/2003/05/soap/mep/soap-response/ then the value of the SOAP http://www.w3.org/2003/05/soap/mep/ImmediateDestination property MUST be generated using the HTTP binding extension's rules for generating an IRI for HTTP GET (see ).</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-5056" class="component" part="2" section="6" subsection="03">When formulating the HTTP message to be transmitted, the HTTP request method used MUST be selected using one of the following:</assertion>
+ <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-5058" class="component" part="2" section="6" subsection="03">When formulating the HTTP message to be transmitted, the HTTP transfer coding used MUST be selected using one of the following:</assertion>
+ <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-5059" class="component" part="2" section="6" subsection="03">When formulating the HTTP fault message to be transmitted, the HTTP transfer coding used MUST be selected using one of the following:</assertion>
<assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327" required="true" id="HTTPBinding-5057" class="component" part="2" section="6" subsection="03">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-5061" class="component" part="2" section="6" subsection="03">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>
--- NEW FILE: assertion-coverage.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="assertion-coverage.xsl"?>
<assertions part2="122" part1="106" message="3" exchange="18" document="50" component="157">
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0054" class="component" name="Binding-0054">
<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="Chat-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chat-1B"/>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0055" class="component" name="Binding-0055">
<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="Chat-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chat-2B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0056" class="component" name="Binding-0056">
<synopsis>This xs:anyURI MUST be an absolute IRI as defined by .</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0057" class="component" name="Binding-0057">
<synopsis>For each Binding component in the bindings property of a Description component, the name property MUST be unique.</synopsis>
<test id="Binding-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-3B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingFault-0058" class="component" name="BindingFault-0058">
<synopsis>For each Binding Fault component in the binding faults property of a Binding component, the interface fault property MUST be unique.</synopsis>
<test id="Binding-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-2B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingFaultReference-0061" class="component" name="BindingFaultReference-0061">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingFaultReference-0062" class="component" name="BindingFaultReference-0062">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingMessageReference-0060" class="component" name="BindingMessageReference-0060">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingOperation-0059" class="component" name="BindingOperation-0059">
<synopsis>For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Compare-URI-IRI-0068" class="component" name="Compare-URI-IRI-0068">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-0024" class="component" name="Description-0024">
<synopsis>Each WSDL 2.0 or type system component of the same kind MUST be uniquely identified by its qualified name.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-0025" class="document" name="Description-0025">
<synopsis>Its value MUST be an absolute IRI (see ) and should be dereferenceable.</synopsis>
<test id="Description-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Description-2B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201000" class="document" name="Description-1201000">
<synopsis>WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0 Information Sets (Infosets), that is one or more descriptionelement information items.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201001" class="component" name="Description-1201001">
<synopsis>The value of the targetNamespaceattribute information item SHOULD be dereferenceable.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201002" class="component" name="Description-1201002">
<synopsis>It SHOULD resolve to a human or machine processable document that directly or indirectly defines the intended semantics of those components.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201003" class="component" name="Description-1201003">
<synopsis>It MAY resolve to a WSDL 2.0 document that provides service description information for that namespace.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201004" class="document" name="Description-1201004">
<synopsis>If a WSDL 2.0 document is split into multiple WSDL 2.0 documents (which may be combined as needed via ), then the targetNamespaceattribute information item SHOULD resolve to a master WSDL 2.0 document that includes all the WSDL 2.0 documents needed for that service description.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201005" class="document" name="Description-1201005">
<synopsis>Zero or more element information items amongst its [children], in order as follows:</synopsis>
<test id="TicketAgent-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/TicketAgent-1B"/>
</assertion>
<assertion count="4" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Endpoint-0064" class="component" name="Endpoint-0064">
<synopsis>This xs:anyURI MUST be an absolute IRI as defined by .</synopsis>
<test id="Service-14B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-14B"/>
<test id="Service-15B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-15B"/>
<test id="Service-14B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-14B"/>
<test id="Service-15B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-15B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Endpoint-0065" class="component" name="Endpoint-0065">
<synopsis>For each Endpoint component in the endpoints property of a Service component, the name property MUST be unique.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Endpoint-0066" class="component" name="Endpoint-0066">
<synopsis>For each Endpoint component in the endpoints property of a Service component, the binding property MUST either be a Binding component with an unspecified interface property or a Binding component with an interface property equal to the interface property of the Service component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Equivalence-0067" class="component" name="Equivalence-0067">
<synopsis>Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0073" class="component" name="Extensibility-0073">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0074" class="component" name="Extensibility-0074">
<synopsis>If a WSDL 2.0 document declares an extension, Feature or Property as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension, Feature or Property, unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension, Feature or Property.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0075" class="component" name="Extensibility-0075">
<synopsis>Therefore, the Web service MUST support every extension, Feature or Property that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension, Feature or Property that is declared as mandatory.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extension-1600000" class="component" name="Extension-1600000">
<synopsis>The meaning of an extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace IRI.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2200202" class="exchange" name="FaultDelivery-2200202">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2200302" class="exchange" name="FaultDelivery-2200302">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagation-2200101" class="exchange" name="FaultPropagation-2200101">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagation-2200102" class="exchange" name="FaultPropagation-2200102">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagationModification-2200103" class="component" name="FaultPropagationModification-2200103">
<synopsis>However, extensions or binding extensions MAY modify these rulesets.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultReplacesMessage-2200201" class="exchange" name="FaultReplacesMessage-2200201">
<synopsis>When the Fault Replaces Message propagation rule is in effect, any message after the first in the pattern MAY be replaced with a fault message, which MUST have identical direction.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Feature-1207001" class="component" name="Feature-1207001">
<synopsis>This IRI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Feature that it identifies.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#FeatureRef-0046" class="component" name="FeatureRef-0046">
<synopsis>This xs:anyURI MUST be an absolute IRI as defined by .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#FeatureRef-0047" class="component" name="FeatureRef-0047">
<synopsis>The ref property of a Feature component MUST be unique within the features property of an Interface, Interface Fault, Interface Operation, Interface Message Reference, Interface Fault Reference, Binding, Binding Fault, Binding Operation, Binding Message Reference, Binding Fault Reference, Service, or Endpoint component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPAccessAuthentication-5080" class="component" name="HTTPAccessAuthentication-5080">
<synopsis>If the http authentication scheme property is present, then this property MUST be present.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2603001" class="component" name="HTTPBinding-2603001">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5056" class="component" name="HTTPBinding-5056">
<synopsis>When formulating the HTTP message to be transmitted, the HTTP request method used MUST be selected using one of the following:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5057" class="component" name="HTTPBinding-5057">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5058" class="component" name="HTTPBinding-5058">
<synopsis>When formulating the HTTP message to be transmitted, the HTTP transfer coding used MUST be selected using one of the following:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5059" class="component" name="HTTPBinding-5059">
<synopsis>When formulating the HTTP fault message to be transmitted, the HTTP transfer coding used MUST be selected using one of the following:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5061" class="component" name="HTTPBinding-5061">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5062" class="component" name="HTTPBinding-5062">
<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 count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingFault-2606003" class="component" name="HTTPBindingFault-2606003">
<synopsis>The fault definition SHOULD agree with the definition of the HTTP error codes, as specified in section 8 of .</synopsis>
<test id="HTTPBinding-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-2B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingFault-2607002" class="component" name="HTTPBindingFault-2607002">
<synopsis>An integer value of this property identifies the error Status-Code as defined by that the service will use in case the fault is returned.</synopsis>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2604001" class="component" name="HTTPBindingOperation-2604001">
<synopsis>Wild cards (for example, application/*) SHOULD NOT be used in this attribute information item since they may lead to interoperability problems.</synopsis>
<test id="HTTPBinding-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-3B"/>
<test id="HTTPBinding-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-4B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2605001" class="component" name="HTTPBindingOperation-2605001">
<synopsis>The first is transmitted using an HTTP request, and the second is transmitted using the corresponding HTTP response.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2605002" class="component" name="HTTPBindingOperation-2605002">
<synopsis>This IRI is combined with the base IRI specified in the address property of the Endpoint component to form the full IRI for the HTTP request to invoke the operation.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2605003" class="component" name="HTTPBindingOperation-2605003">
<synopsis>The value of the serialization format used for a message is a media type which MUST be covered by this range.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-5065" class="component" name="HTTPBindingOperation-5065">
<synopsis>In cases where only one message is being sent, the message body of the HTTP response MUST be empty.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-5066" class="component" name="HTTPBindingOperation-5066">
<synopsis>It MUST contain an absolute or a relative IRI, i.e. it MUST NOT include a fragment identifier in the IRI.</synopsis>
<test id="HTTPBinding-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-5B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-2606001" class="component" name="HTTPHeader-2606001">
<synopsis>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:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-2606002" class="component" name="HTTPHeader-2606002">
<synopsis>If the value of an HTTP Header component's required property is true, the inclusion of this HTTP header field is REQUIRED</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5063" class="component" name="HTTPHeader-5063">
<synopsis>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.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5068" class="component" name="HTTPHeader-5068">
<synopsis>A Binding Message Reference or a Binding Fault component's http headers property MUST NOT contain multiple HTTP Header components with the same name property.</synopsis>
<test id="HTTPBinding-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-6B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5069" class="component" name="HTTPHeader-5069">
<synopsis>This type MUST be a simple type.</synopsis>
<test id="HTTPBinding-7B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-7B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5070" class="component" name="HTTPHeader-5070">
<synopsis>If the value is true, then the HTTP header field MUST be included in the message.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPQueryString-5074" class="component" name="HTTPQueryString-5074">
<synopsis>The instance data MUST NOT contain elements with an xs:nil attribute whose value is true.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2607010" class="message" name="HTTPSerialization-2607010">
<synopsis>This element MUST NOT carry an xs:nil attribute whose value is true</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2607011" class="component" name="HTTPSerialization-2607011">
<synopsis>If this format is used then the style property of Interface Operation component being bound MUST contain a value of http://www.w3.org/@@@@/@@/wsdl/style/iri as defined in , i.e. this serialization format may only be used to serialize the HTTP request corresponding to the initial message of an interface operation.</synopsis>
<test id="HTTPBinding-8B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-8B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608001" class="component" name="HTTPSerialization-2608001">
<synopsis>If the style property of the Interface Operation bound has a value of http://www.w3.org/@@@@/@@/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>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608002" class="component" name="HTTPSerialization-2608002">
<synopsis>For the HTTP binding defined in this section (), application/x-www-form-urlencoded MAY be used as a serialization format for an input message (HTTP Request), but MUST NOT be used as a serialization format for an output or fault message (HTTP Response).</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608003" class="component" name="HTTPSerialization-2608003">
<synopsis>If not all elements from the instance data are cited in the http location property, or if the property is not present on the Binding Operation component, then additional serialization rules apply.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608004" class="component" name="HTTPSerialization-2608004">
<synopsis>For elements of the instance data not cited in the http location property, a query string is constructed as follows.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608005" class="component" name="HTTPSerialization-2608005">
<synopsis>If the HTTP request method used does not allow HTTP message body (e.g. GET and DELETE), and if the value of the http location ignore uncited property is false, then the following rules apply.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608007" class="component" name="HTTPSerialization-2608007">
<synopsis>If the HTTP request method used does allow an HTTP message body (e.g. POST and PUT), then the following rules apply.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608008" class="component" name="HTTPSerialization-2608008">
<synopsis>The Content-Type HTTP header field must have the value application/x-www-form-urlencoded.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608009" class="component" name="HTTPSerialization-2608009">
<synopsis>this serialization format may only be used to serialize the HTTP request corresponding to the initial message of an interface operation.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5067" class="component" name="HTTPSerialization-5067">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5071" class="component" name="HTTPSerialization-5071">
<synopsis>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 .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5073" class="component" name="HTTPSerialization-5073">
<synopsis>Strings enclosed within single curly braces MUST be element names from the instance data of the input message.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5075" class="component" name="HTTPSerialization-5075">
<synopsis>The Content-Type HTTP header MUST have the value application/xml, or a media type compatible with application/xml as specified in section .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5076" class="component" name="HTTPSerialization-5076">
<synopsis>Specifically, for the HTTP binding defined in this section (), multipart/form-data MAY be used as a serialization format for an input message (HTTP Request), but MUST NOT be used as a serialization format for an output or fault message (HTTP Response).</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5077" class="component" name="HTTPSerialization-5077">
<synopsis>The Content-Disposition header MUST have the value form-data, and its name parameter is the local name of the element.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5078" class="component" name="HTTPSerialization-5078">
<synopsis>The Content-Type header MUST have the value:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5079" class="component" name="HTTPSerialization-5079">
<synopsis>The instance data MUST NOT contain elements with an xs:nil attribute whose value is true.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0001" class="document" name="Import-0001">
<synopsis>However, any WSDL 2.0 document that contains component definitions that refer by QName to WSDL 2.0 components that belong to a different namespace MUST contain a wsdl:importelement information item for that namespace (see ).</synopsis>
<test id="Description-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Description-1B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0003" class="document" name="Import-0003">
<synopsis>Imported components have different target namespace values from the WSDL 2.0 document that is importing them.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0070" class="document" name="Import-0070">
<synopsis>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).</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0071" class="document" name="Import-0071">
<synopsis>This value MUST NOT match the actual value of targetNamespaceattribute information item in the enclosing WSDL 2.0 document.</synopsis>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0072" class="document" name="Import-0072">
<synopsis>If the location attribute in the importelement information item is dereferencible then it MUST reference a WSDL 2.0 document and 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>
<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"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1400001" class="document" name="Import-1400001">
<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>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#ImportInclude-1400002" class="component" name="ImportInclude-1400002">
<synopsis>The semantics of an extension MUST NOT depend on how components are brought into a component model instance via <import> or <include>.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Include-0069" class="document" name="Include-0069">
<synopsis>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.</synopsis>
<test id="Include-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Include-1B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Include-1400000" class="document" name="Include-1400000">
<synopsis>The IRI indicated by location MUST resolve to a WSDL 2.0 document.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOnlyComposition-2200501" class="component" name="InOnlyComposition-2200501">
<synopsis>The in-only message exchange pattern consists of exactly one message as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOnlyFaults-2200502" class="exchange" name="InOnlyFaults-2200502">
<synopsis>The in-only message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOptOutComposition-2200801" class="component" name="InOptOutComposition-2200801">
<synopsis>The in-optional-out message exchange pattern consists of one or two messages, in order, as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOptOutFaults-2200802" class="exchange" name="InOptOutFaults-2200802">
<synopsis>The in-optional-out message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOutComposition-2200701" class="component" name="InOutComposition-2200701">
<synopsis>The in-out message exchange pattern consists of exactly two messages, in order, as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOutFaults-2200702" class="exchange" name="InOutFaults-2200702">
<synopsis>The in-out message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0027" class="component" name="Interface-0027">
<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"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0028" class="component" name="Interface-0028">
<synopsis>The list of xs:QName in an extendsattribute information item MUST NOT contain duplicates.</synopsis>
<test id="Interface-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-4B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0030" class="component" name="Interface-0030">
<synopsis>For each Interface component in the interfaces property of a Description component, the name property MUST be unique.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0031" class="document" name="Interface-0031">
<synopsis>Its value, if present, MUST contain absolute IRIs (see ).</synopsis>
<test id="Interface-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-1B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-0032" class="component" name="InterfaceFault-0032">
<synopsis>For each Interface Fault component in the interface faults property of an Interface component, the name property must be unique.</synopsis>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-0033" class="component" name="InterfaceFault-0033">
<synopsis>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 ).</synopsis>
<test id="InterfaceFault-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-2B"/>
<test id="InterfaceFault-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-3B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1203000" class="document" name="InterfaceFault-1203000">
<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>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1203001" class="component" name="InterfaceFault-1203001">
<synopsis>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.</synopsis>
<test id="InterfaceFault-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-3B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-0043" class="component" name="InterfaceFaultReference-0043">
<synopsis>The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-0044" class="component" name="InterfaceFaultReference-0044">
<synopsis>The direction MUST be consistent with the direction implied by the fault propagation ruleset used in the message exchange pattern of the operation.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-0045" class="component" name="InterfaceFaultReference-0045">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-1206000" class="document" name="InterfaceFaultReference-1206000">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-0040" class="component" name="InterfaceMessageReference-0040">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-0041" class="component" name="InterfaceMessageReference-0041">
<synopsis>When the message content model property has the value #any or #none the element declaration property MUST be empty.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-0042" class="component" name="InterfaceMessageReference-0042">
<synopsis>For each Interface Message Reference component in the interface message references property of an Interface Operation component, its message label property MUST be unique.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205000" class="component" name="InterfaceMessageReference-1205000">
<synopsis>An xs:token with one of the values in or out, indicating whether the message is coming to the service or going from the service, respectively.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205001" class="component" name="InterfaceMessageReference-1205001">
<synopsis>An xs:token with one of the values #any, #none, #other, or #element.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205002" class="document" name="InterfaceMessageReference-1205002">
<synopsis>The type of the elementattribute information item is a union of xs:QName and xs:token where the allowed token values are #any, #none, or #other.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205003" class="document" name="InterfaceMessageReference-1205003">
<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>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-0035" class="component" name="InterfaceOperation-0035">
<synopsis>For each Interface Operation component in the interface operations property of an Interface component, the name property MUST be unique.</synopsis>
<test id="InterfaceOperation-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-2B"/>
</assertion>
<assertion count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-0036" class="component" name="InterfaceOperation-0036">
<synopsis>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 ).</synopsis>
<test id="InterfaceOperation-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-1B"/>
<test id="InterfaceOperation-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-5B"/>
<test id="InterfaceOperation-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-6B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-0038" class="component" name="InterfaceOperation-0038">
<synopsis>An Interface Operation component MUST satisfy the specification defined by each operation style identified by its style property.</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204000" class="component" name="InterfaceOperation-1204000">
<synopsis>This xs:anyURI MUST be an absolute IRI (see ).</synopsis>
<test id="InterfaceOperation-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-3B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204001" class="component" name="InterfaceOperation-1204001">
<synopsis>These xs:anyURIs MUST be absolute IRIs (see ).</synopsis>
<test id="InterfaceOperation-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-4B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204002" class="document" name="InterfaceOperation-1204002">
<synopsis>Its value MUST be an absolute IRI (see ).</synopsis>
<test id="InterfaceOperation-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-3B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204003" class="document" name="InterfaceOperation-1204003">
<synopsis>Its value MUST be an absolute IRI (see ).</synopsis>
<test id="InterfaceOperation-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-4B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204005" class="component" name="InterfaceOperation-1204005">
<synopsis>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.</synopsis>
<test id="InterfaceOperation-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-5B"/>
</assertion>
<assertion count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5028" class="component" name="IRIStyle-5028">
<synopsis>When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</synopsis>
<test id="IRI-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-1B"/>
<test id="IRI-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-2B"/>
<test id="IRI-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-3B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5029" class="component" name="IRIStyle-5029">
<synopsis>The sequence MUST only contain elements.</synopsis>
<test id="IRI-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-4B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5030" class="component" name="IRIStyle-5030">
<synopsis>The sequence MUST contain only local element children.</synopsis>
<test id="IRI-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-4B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5031" class="component" name="IRIStyle-5031">
<synopsis>The localPart of the element's QName MUST be the same as the Interface Operation component's name.</synopsis>
<test id="IRI-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-6B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5032" class="component" name="IRIStyle-5032">
<synopsis>The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</synopsis>
<test id="IRI-7B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-7B"/>
</assertion>
<assertion count="9" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5034" class="component" name="IRIStyle-5034">
<synopsis>The children elements of the sequence MUST derive from xs:simpleType, and MUST NOT be of the type or derive from xs:QName, xs:NOTATION, xs:hexBinary or xs:base64Binary.</synopsis>
<test id="IRI-8B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-8B"/>
<test id="IRI-9B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-9B"/>
<test id="IRI-10B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-10B"/>
<test id="IRI-11B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-11B"/>
<test id="IRI-12B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-12B"/>
<test id="IRI-13B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-13B"/>
<test id="IRI-14B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-14B"/>
<test id="IRI-15B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-15B"/>
<test id="IRI-16B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-16B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-0076" class="document" name="Location-0076">
<synopsis>It MUST NOT appear on a wsdl:description element or any of its children/descendants.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-0077" class="component" name="Location-0077">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-1700000" class="document" name="Location-1700000">
<synopsis>For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MEP-0037" class="component" name="MEP-0037">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPDescriptiveness-2200001" class="exchange" name="MEPDescriptiveness-2200001">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPTermination-2200104" class="exchange" name="MEPTermination-2200104">
<synopsis>Generation of a fault, regardless of ruleset, terminates the exchange.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0004" class="document" name="MessageLabel-0004">
<synopsis>The messageLabelattribute information item of an interface message 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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0005" class="document" name="MessageLabel-0005">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0006" class="document" name="MessageLabel-0006">
<synopsis>The messageLabelattribute information item of a binding message 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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0007" class="document" name="MessageLabel-0007">
<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>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0008" class="document" name="MessageLabel-0008">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0009" class="document" name="MessageLabel-0009">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0010" class="document" name="MessageLabel-0010">
<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>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0011" class="document" name="MessageLabel-0011">
<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>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0012" class="document" name="MessageLabel-0012">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0013" class="document" name="MessageLabel-0013">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0014" class="document" name="MessageLabel-0014">
<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>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0015" class="document" name="MessageLabel-0015">
<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>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0039" class="component" name="MessageLabel-0039">
<synopsis>The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MessageTriggersFault-2200301" class="exchange" name="MessageTriggersFault-2200301">
<synopsis>When the Message Triggers Fault propagation rule is in effet, any message, including the first in the pattern, MAY trigger a fault message, which MUST have opposite direction.</synopsis>
</assertion>
<assertion count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5035" class="component" name="MultipartStyle-5035">
<synopsis>When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</synopsis>
<test id="Multipart-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-1B"/>
<test id="Multipart-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-2B"/>
<test id="Multipart-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-3B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5036" class="component" name="MultipartStyle-5036">
<synopsis>The sequence MUST only contain elements.</synopsis>
<test id="Multipart-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-4B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5037" class="component" name="MultipartStyle-5037">
<synopsis>The localPart of the element's QName MUST be the same as the Interface Operation component's name.</synopsis>
<test id="Multipart-8B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-8B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5038" class="component" name="MultipartStyle-5038">
<synopsis>The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</synopsis>
<test id="Multipart-9B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-9B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5039" class="component" name="MultipartStyle-5039">
<synopsis>The sequence MUST NOT contain multiple children element declared with the same local name.</synopsis>
<test id="Multipart-10B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-10B"/>
</assertion>
<assertion count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5081" class="component" name="MultipartStyle-5081">
<synopsis>The sequence MUST contain only local element children.</synopsis>
<test id="Multipart-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-5B"/>
<test id="Multipart-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-6B"/>
<test id="Multipart-7B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-7B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5082" class="component" name="MultipartStyle-5082">
<synopsis>The attributes minOccurs and maxOccurs for these child elements MUST have a value 1.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#NodeIdentity-2200000" class="exchange" name="NodeIdentity-2200000">
<synopsis>A node MAY be accessible via more than one physical address or transport.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#NoFaults-2200401" class="exchange" name="NoFaults-2200401">
<synopsis>When the No Faults propagation rule is in effect, faults MUST NOT be propagated.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OperationSafety-2300001" class="component" name="OperationSafety-2300001">
<synopsis>However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.4 of .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OperationSafety-2300002" class="document" name="OperationSafety-2300002">
<synopsis>An OPTIONAL safeattribute information item with the following Infoset properties:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutInComposition-2201101" class="component" name="OutInComposition-2201101">
<synopsis>The out-in message exchange pattern consists of exactly two messages, in order, as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutInFaults-2201102" class="exchange" name="OutInFaults-2201102">
<synopsis>The out-in message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOnlyComposition-2200901" class="component" name="OutOnlyComposition-2200901">
<synopsis>The out-only message exchange pattern consists of exactly one message as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOnlyFaults-2200902" class="exchange" name="OutOnlyFaults-2200902">
<synopsis>The out-only message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOptInComposition-2201201" class="component" name="OutOptInComposition-2201201">
<synopsis>The out-optional-in message exchange pattern consists of one or two messages, in order, as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOptInFaults-2201202" class="exchange" name="OutOptInFaults-2201202">
<synopsis>The out-optional-in message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-0049" class="component" name="Property-0049">
<synopsis>A reference to a Type Definition component in the type definitions property of the Description component constraining the value of the Property, or the token #value if the value property is not empty.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-0050" class="component" name="Property-0050">
<synopsis>The ref property of a Property component MUST be unique within the properties property of an Interface, Interface Fault, Interface Operation, Interface Message Reference, Interface Fault Reference, Binding, Binding Fault, Binding Operation, Binding Message Reference, Binding Fault Reference, Service, or Endpoint component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-0051" class="component" name="Property-0051">
<synopsis>All specified values MUST be equal and belong to each specified value set.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-1208001" class="component" name="Property-1208001">
<synopsis>This IRI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Property that it identifies.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#PropertyRef-0048" class="component" name="PropertyRef-0048">
<synopsis>This xs:anyURI MUST be an absolute IRI as defined by .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#QName-0002" class="component" name="QName-0002">
<synopsis>Furthermore, all QName references, whether to the same or to different namespaces MUST resolve to components (see ).</synopsis>
</assertion>
<assertion count="6" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#QName-resolution-1219000" class="document" name="QName-resolution-1219000">
<synopsis>A Description component MUST NOT have such broken references.</synopsis>
<test id="Service-12B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-12B"/>
<test id="Service-13B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-13B"/>
<test id="Service-12B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-12B"/>
<test id="Service-13B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-13B"/>
<test id="Service-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-1B"/>
<test id="Service-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-2B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustInOnlyComposition-2200601" class="component" name="RobustInOnlyComposition-2200601">
<synopsis>The robust in-only message exchange pattern consists of exactly one message as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustInOnlyFaults-2200602" class="exchange" name="RobustInOnlyFaults-2200602">
<synopsis>The robust in-only message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustOutOnlyComposition-2201001" class="component" name="RobustOutOnlyComposition-2201001">
<synopsis>The robust out-only message exchange pattern consists of exactly one message as follows:</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustOutOnlyFaults-2201002" class="exchange" name="RobustOutOnlyFaults-2201002">
<synopsis>The robust out-only message exchange pattern uses the rule .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5007" class="component" name="RPCStyle-5007">
<synopsis>If the RPC style is used by an Interface Operation component then its message exchange pattern property MUST have the value either http://www.w3.org/@@@@/@@/wsdl/in-only or http://www.w3.org/@@@@/@@/wsdl/in-out.</synopsis>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5008" class="component" name="RPCStyle-5008">
<synopsis>The value of the message content model property for the Interface Message Reference components of the interface message references property MUST be #element.</synopsis>
<test id="RPC-1B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-1B"/>
<test id="RPC-2B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-2B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5009" class="component" name="RPCStyle-5009">
<synopsis>The content model of input and output element declaration elements MUST be defined using a complex type that contains a sequence from XML Schema.</synopsis>
<test id="RPC-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-3B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5010" class="component" name="RPCStyle-5010">
<synopsis>The input sequence MUST only contain elements and element wildcards.</synopsis>
<test id="RPC-4B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-4B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5011" class="component" name="RPCStyle-5011">
<synopsis>The input sequence MUST NOT contain more than one element wildcard.</synopsis>
<test id="RPC-5B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-5B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5012" class="component" name="RPCStyle-5012">
<synopsis>The element wildcard, if present, MUST appear after any elements.</synopsis>
<test id="RPC-6B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-6B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5013" class="component" name="RPCStyle-5013">
<synopsis>The output sequence MUST only contain elements.</synopsis>
<test id="RPC-7B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-7B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5014" class="component" name="RPCStyle-5014">
<synopsis>Both the input and output sequences MUST contain only local element children.</synopsis>
<test id="RPC-8B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-8B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5015" class="component" name="RPCStyle-5015">
<synopsis>The local name of input element's QName MUST be the same as the Interface Operation component's name.</synopsis>
<test id="RPC-9B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-9B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5016" class="component" name="RPCStyle-5016">
<synopsis>Input and output elements MUST both be in the same namespace.</synopsis>
<test id="RPC-14B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-14B"/>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5017" class="component" name="RPCStyle-5017">
<synopsis>The complex type that defines the body of an input or an output element MUST NOT contain any local attributes.</synopsis>
<test id="RPC-10B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-10B"/>
<test id="RPC-11B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-11B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5018" class="component" name="RPCStyle-5018">
<synopsis>If elements with the same qualified name appear as children of both the input and output elements, then they MUST both be declared using the same named type.</synopsis>
<test id="RPC-15B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-15B"/>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5019" class="component" name="RPCStyle-5019">
<synopsis>The input or output sequence MUST NOT contain multiple children elements declared with the same name.</synopsis>
<test id="RPC-12B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-12B"/>
<test id="RPC-13B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-13B"/>
</assertion>
<assertion count="3" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0016" class="document" name="Schema-0016">
<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"/>
<test id="Import-3B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-3B"/>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0017" class="document" name="Schema-0017">
<synopsis>The referenced schema MUST contain a targetNamespaceattribute information item on its xs:schemaelement information item.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0018" class="document" name="Schema-0018">
<synopsis>A WSDL 2.0 document MUST NOT define the same element or type in more than one inlined schema.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0021" class="document" name="Schema-0021">
<synopsis>A specification of extension syntax for an alternative schema language MUST use a namespace that is different than the namespace of XML Schema.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0022" class="document" name="Schema-0022">
<synopsis>If wsdlx:interface and wsdlx:binding are used together then they MUST satisfy the same consistency rules that apply to the interface property of a Service component and the binding property of a nested Endpoint component, that is either the binding refers the interface of the service or the binding refers to no interface.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0052" class="document" name="Schema-0052">
<synopsis>The value of the targetNamespaceattribute information item of the xs:schemaelement information item of an imported schema MUST equal the value of the namespace of the importelement information item in the importing WSDL 2.0 document.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0053" class="document" name="Schema-0053">
<synopsis>The namespace used for an alternate schema language MUST be an absolute IRI.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Service-0063" class="component" name="Service-0063">
<synopsis>For each Service component in the services property of a Description component, the name property MUST be unique.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPAction-5048" class="component" name="SOAPAction-5048">
<synopsis>A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2503001" class="message" name="SOAPBinding-2503001">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5040" class="component" name="SOAPBinding-5040">
<synopsis>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.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5041" class="message" name="SOAPBinding-5041">
<synopsis>If the value is #none then the payload MUST be empty.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5042" class="component" name="SOAPBinding-5042">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5043" class="component" name="SOAPBinding-5043">
<synopsis>Every SOAP binding MUST indicate what version of SOAP is in use for the operations of the interface that this binding applies to.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5044" class="component" name="SOAPBinding-5044">
<synopsis>Every SOAP binding MUST indicate what underlying protocol is in use.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBindingFault-5045" class="component" name="SOAPBindingFault-5045">
<synopsis>For every Interface Fault component contained in an Interface component, a mapping to a SOAP Fault MUST be described.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHeaderBlock-5050" class="component" name="SOAPHeaderBlock-5050">
<synopsis>When its value is true, the SOAP header block MUST be decorated with a SOAP mustUnderstandattribute information item with a value of true; if so, the XML element declaration referenced by the element declaration property MUST allow this SOAP mustUnderstandattribute information item.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHeaderBlock-5051" class="component" name="SOAPHeaderBlock-5051">
<synopsis>If the value is true, then the SOAP header block MUST be included in the message.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHeaderBlock-5052" class="component" name="SOAPHeaderBlock-5052">
<synopsis>The value of the elementattribute information item MUST resolve to a global element declaration from the element declarations property of the Description component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHTTPGeneration-5055" class="component" name="SOAPHTTPGeneration-5055">
<synopsis>If the SOAP MEP selected is http://www.w3.org/2003/05/soap/mep/soap-response/ then the value of the SOAP http://www.w3.org/2003/05/soap/mep/ImmediateDestination property MUST be generated using the HTTP binding extension's rules for generating an IRI for HTTP GET (see ).</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHTTPSelection-5054" class="component" name="SOAPHTTPSelection-5054">
<synopsis>This default binding rule is applicable when the value of the soap underlying protocol property of the Binding component is http://www.w3.org/2003/05/soap/bindings/HTTP/. If the SOAP MEP selected as specified above has the value http://www.w3.org/2003/05/soap/mep/request-response/ then the HTTP method used is POST. If the SOAP MEP selected has the value http://www.w3.org/2003/05/soap/mep/soap-response/ then the HTTP method used is GET.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPMEP-5047" class="component" name="SOAPMEP-5047">
<synopsis>A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPMEPDefault-5046" class="component" name="SOAPMEPDefault-5046">
<synopsis>A xs:anyURI, which is an absolute IRI as defined by , to the Binding component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPMEPSelection-5053" class="component" name="SOAPMEPSelection-5053">
<synopsis>For a given Interface Operation component, if there is a Binding Operation component whose interface operation property matches the component in question and its soap mep property has a value, then the SOAP MEP is the value of the soap mep property. Otherwise, the SOAP MEP is the value of the Binding component's soap mep default, if any. Otherwise, the Interface Operation component's message exchange pattern property MUST have the value http://www.w3.org/@@@@/@@/wsdl/in-out, and the SOAP MEP is the URI http://www.w3.org/2003/05/soap/mep/request-response/ identifying the SOAP Request-Response Message Exchange Pattern as defined in .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPModule-5049" class="component" name="SOAPModule-5049">
<synopsis>A xs:anyURI, which is an absolute IRI as defined by .</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-0023" class="document" name="Types-0023">
<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 count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-0026" class="component" name="Types-0026">
<synopsis>Each XML Schema type definition MUST have a unique QName.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1201006" class="component" name="Types-1201006">
<synopsis>Each XML Schema element declaration MUST have a unique QName.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300000" class="document" name="Types-1300000">
<synopsis>Every QName reference MUST resolve (see ).</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300001" class="document" name="Types-1300001">
<synopsis>When resolving QNames references for schema definitions, the namespace MUST be imported by the referring WSDL 2.0 document.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300002" class="document" name="Types-1300002">
<synopsis>Specifically components that the schema imports via xs:import are NOT referenceable.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300003" class="document" name="Types-1300003">
<synopsis>Similarly, components defined in an inlined XML schema are NOT automatically referenceable within WSDL 2.0 document that imported (using wsdl:import) the WSDL 2.0 document that inlines the schema (see for more details).</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300005" class="document" name="Types-1300005">
<synopsis>The type of the wsdlx:interfaceattribute information item is an xs:QName that specifies the name property of an Interface component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300006" class="document" name="Types-1300006">
<synopsis>The type of the wsdlx:bindingattribute information item is an xs:QName that specifies the name property of a Binding component.</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5019" class="component" name="WRPC-5019">
<synopsis>OPTIONAL, but MUST be present when the style is RPC</synopsis>
</assertion>
<assertion count="0" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5020" class="component" name="WRPC-5020">
<synopsis>Values for the second component MUST be chosen among the following four: "#in", "#out", "#inout" "#return".</synopsis>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5021" class="component" name="WRPC-5021">
<synopsis>The value of the first component of each pair (q, t) MUST be unique within the list.</synopsis>
<test id="RPC-17B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-17B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5022" class="component" name="WRPC-5022">
<synopsis>For each child element of the input and output messages of the operation, a pair (q, t), whose first component q is equal to the qualified name of that element, MUST be present in the list, with the caveat that elements that appear with cardinality greater than one MUST be treated as a single element.</synopsis>
<test id="RPC-18B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-18B"/>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5023" class="component" name="WRPC-5023">
<synopsis>For each pair (q, #in), there MUST be a child element of the input element with a name of q. There MUST NOT be a child element of the output element with the name of q.</synopsis>
<test id="RPC-19B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-19B"/>
<test id="RPC-20B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-20B"/>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5024" class="component" name="WRPC-5024">
<synopsis>For each pair (q, #out), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.</synopsis>
<test id="RPC-21B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-21B"/>
<test id="RPC-22B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-22B"/>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5025" class="component" name="WRPC-5025">
<synopsis>For each pair (q, #inout), there MUST be a child element of the input element with a name of q. There MUST also be a child element of the output element with the name of q.</synopsis>
<test id="RPC-23B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-23B"/>
<test id="RPC-24B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-24B"/>
</assertion>
<assertion count="2" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5026" class="component" name="WRPC-5026">
<synopsis>For each pair (q, #return), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.</synopsis>
<test id="RPC-25B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-25B"/>
<test id="RPC-26B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-26B"/>
</assertion>
<assertion count="1" href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5027" class="document" name="WRPC-5027">
<synopsis>Additionally, each even-numbered item (0, 2, 4, ...) in the list MUST be of type xs:QName and each odd-numbered item (1, 3, 5, ...) in the list MUST be of the subtype of xs:token described in the previous paragraph.</synopsis>
<test id="RPC-27B" href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-27B"/>
</assertion>
</assertions>
--- NEW FILE: dashboard.xsl ---
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="dashboard.xsl"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
xmlns:report="http://www.w3.org/2006/06/wsdl/ValidationReport" >
<xsl:import href="results/interchange.xsl"/>
<xsl:import href="results/validation.xsl"/>
<xsl:import href="assertion-coverage.xsl"/>
<xsl:import href="coverage.xsl"/>
<xsl:param name="DSTAMP" />
<xsl:param name="TSTAMP" />
<xsl:param name="TODAY" />
<xsl:output method="html" encoding="UTF-8" indent="no"/>
<xsl:template match="/">
<html>
<head>
<title>Test Suite Health Dashboard</title>
<style type="text/css">
body {font-family:sans-serif}
td {border:1px solid #DDDDDD}
.passed {background-color:green}
.failed {background-color:orange}
.disaster {background-color:red}
.border th, .border td { border: 1px solid black; padding: 0.5ex }
.border th { background: #ccc }
.good { background: green }
.bad { background: red }
</style>
</head>
<body>
<h2>Test Suite Health Dashboard</h2>
<xsl:if test="$TODAY">
<address>
<xsl:text>Generated </xsl:text>
<xsl:value-of select="$TODAY" />,
<xsl:value-of select="$TSTAMP" />
</address>
</xsl:if>
<p>Assertion Coverage (<a href="Assertion-coverage.html">details</a>)</p>
<xsl:for-each select="document('assertion-coverage.xml')">
<xsl:call-template name="assertion-summary"/>
</xsl:for-each>
<p>Test Case Coverage (<a href="test-suite-coverage-summary.xml">details</a>)</p>
<xsl:for-each select="document('test-suite-coverage-summary.xml')/coverage">
<xsl:call-template name="test-coverage-summary"/>
</xsl:for-each>
<p/>
<hr/>
<h2>Implementation Health</h2>
<p>Component Model Test Results (<a href="results/Interchange.html">details</a>)</p>
<xsl:for-each select="document('results/interchange.xml')">
<xsl:call-template name="interchange-results-summary"/>
</xsl:for-each>
<p>Validation Test Results (<a href="results/Validation.html">details</a>)</p>
<table>
<xsl:for-each select="document('results/validation.xml')">
<thead>
<tr>
<xsl:for-each select="summary/vendors/vendor">
<td><strong><xsl:value-of select="@name"/></strong></td>
</xsl:for-each>
</tr>
</thead>
<tbody>
<tr>
<xsl:call-template name="validation-summaries"/>
</tr>
</tbody>
</xsl:for-each>
</table>
<p>Message Exchange Test Results (<a href="tbd">details</a>)</p>
<p>tbd</p>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
--- NEW FILE: assertions-extractor.xsl ---
<?xml version="1.0" encoding="UTF-8"?>
<!--
This stylesheet has not been automatically generated. Do
edit it!
-->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:strip-space elements="*" />
<xsl:output method="xml" indent="yes" />
<xsl:template match="/">
<assertions>
<xsl:for-each select='specs/spec'>
<xsl:variable name='file'
select='concat("../wsdl20/", @src)' />
<xsl:variable name='uri' select='@uri' />
<xsl:for-each
select="document($file)/spec/body/div1//assert">
<assertion class='{@class}' id='{@id}'
required='{@required}' origin="{$uri}">
<xsl:attribute name='part'>
<xsl:choose>
<xsl:when
test='contains($uri, "adjuncts")'>
<xsl:text>2</xsl:text>
</xsl:when>
<xsl:otherwise>
<xsl:text>1</xsl:text>
</xsl:otherwise>
</xsl:choose>
</xsl:attribute>
<xsl:attribute name='section'>
<xsl:value-of
select='count(ancestor::div1/preceding-sibling::div1)+1' />
</xsl:attribute>
<xsl:attribute name='subsection'>
<xsl:choose>
<xsl:when test='ancestor::div2'>
<xsl:variable name='count'
select='count(ancestor::div2/preceding-sibling::div2)+1' />
<xsl:choose>
<xsl:when
test='$count < 10'>
<xsl:text>0</xsl:text>
<xsl:value-of
select='$count' />
</xsl:when>
<xsl:otherwise>
<xsl:value-of
select='$count' />
</xsl:otherwise>
</xsl:choose>
</xsl:when>
<xsl:otherwise>
<xsl:text>00</xsl:text>
</xsl:otherwise>
</xsl:choose>
</xsl:attribute>
<!-- <xsl:apply-templates select='*|text()' /> -->
<xsl:value-of select='normalize-space(.)' />
</assertion>
</xsl:for-each>
</xsl:for-each>
</assertions>
</xsl:template>
<xsl:template match="@*|*">
<xsl:apply-templates select="@*|node()" />
</xsl:template>
<xsl:template match="text()">
<xsl:copy></xsl:copy>
</xsl:template>
</xsl:stylesheet>
Index: assertions-report.xsl
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/assertions-report.xsl,v
retrieving revision 1.7
retrieving revision 1.8
diff -C 2 -d -r1.7 -r1.8
*** assertions-report.xsl 7 Jul 2006 18:53:24 -0000 1.7
--- assertions-report.xsl 16 Nov 2006 14:22:06 -0000 1.8
***************
*** 1,131 ****
<?xml version="1.0" encoding="UTF-8"?>
! <!--
! This stylesheet has not been automatically generated. Do
! edit it!
! -->
! <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
! version="1.0">
- <xsl:strip-space elements="*" />
<xsl:output method="xml" indent="yes" />
<xsl:template match="/">
! <xsl:variable name='ViolatesAssertions'
! select='/ViolatesAssertions' />
!
! <html lang='en-us'>
! <head>
! <title>Assertion Coverage Report</title>
! <link rel="stylesheet" type="text/css"
! href="http://www.w3.org/StyleSheets/TR/base.css" />
! <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
! <style type='text/css'>
! .border th, .border td { border: 1px solid black; padding: 0.5ex }
! .border th { background: #ccc }
! .good { background: green }
! .bad { background: red }
! .class, .count { text-align: center }
! .bar { font-weight: bold; }
! .synopsis { font-size: small }
! </style>
! </head>
! <body>
! <h1>Assertion Coverage Report</h1>
! <xsl:variable name='assertions'
! select='document("assertions.xml")/assertions/assertion'/>
! <xsl:variable name='count'
! select='count($assertions)'/>
! <xsl:variable name='count_component'
! select='count($assertions[@class="component"])'/>
! <xsl:variable name='count_document'
! select='count($assertions[@class="document"])'/>
! <xsl:variable name='count_exchange'
! select='count($assertions[@class="exchange"])'/>
! <xsl:variable name='count_message'
! select='count($assertions[@class="message"])'/>
! <xsl:variable name="unique_violations"
! select="$ViolatesAssertions//ViolateAssertion[not(@assertion=following::ViolateAssertion/@assertion)]" />
! <table>
! <tbody>
! <tr>
! <th width='200px' style='text-align: left'><xsl:value-of select='$count'/> Assertions</th>
! <td>
! <table class='bar' width='{$count}px' cellspacing='0' cellpadding='0'>
! <tbody>
! <tr>
! <td width='{count($unique_violations)}px' class='good'>
! <xsl:value-of select='count($unique_violations)'/>
! </td>
! <td width='{$count - count($unique_violations)}px' style='text-align: right' class='bad'>
! <xsl:value-of select='$count - count($unique_violations)'/>
! </td>
! </tr>
! </tbody>
! </table>
! </td>
! </tr>
! </tbody>
! </table>
! <p><xsl:value-of select='$count'/> assertions
! (<xsl:value-of select='$count_component'/> component,
! <xsl:value-of select='$count_document'/> document,
! <xsl:value-of select='$count_exchange'/> exchange,
! <xsl:value-of select='$count_message'/> message).
! <xsl:value-of select='count($assertions[@part="1"])'/> for part 1,
! <xsl:value-of select='count($assertions[@part="2"])'/> for part 2.</p>
! <table class='border'>
! <thead>
! <tr>
! <th>Status</th>
! <th>Count</th>
! <th>Assertion</th>
! <th>Synopsis</th>
! <th>Class</th>
! <th>Tests</th>
! </tr>
! </thead>
! <tbody>
! <xsl:for-each
! select='$assertions'>
! <xsl:sort select='@id'/>
! <xsl:variable name='id' select='@id'/>
! <xsl:variable name='violations'
! select='$ViolatesAssertions/ViolateAssertion[@assertion=$id]'/>
! <xsl:variable name='count_violations_2'
! select='count($violations)'/>
!
! <tr>
! <td>
! <xsl:attribute name="class">
! <xsl:choose>
! <xsl:when test="$count_violations_2 = 0">bad</xsl:when>
! <xsl:otherwise>good</xsl:otherwise>
! </xsl:choose>
! </xsl:attribute>
! <xsl:text> </xsl:text>
! </td>
! <td class='count'><xsl:value-of select='$count_violations_2'/></td>
! <td>
! <a href='{concat(@origin, "/#", @id)}'><xsl:value-of select='$id' /></a>
! </td>
! <td class='synopsis'>
! <xsl:value-of select='.'/>
! </td>
! <td class='class'><xsl:value-of select='@class' /></td>
! <td>
! <xsl:for-each select='$violations'>
! <xsl:text>[</xsl:text><a href='{@origin}'><xsl:value-of select='@test-id'/></a><xsl:text>] </xsl:text>
! </xsl:for-each>
! </td>
! </tr>
! </xsl:for-each>
! </tbody>
! </table>
! </body>
! </html>
</xsl:template>
-
- <xsl:template match='assertion'></xsl:template>
</xsl:stylesheet>
--- 1,42 ----
<?xml version="1.0" encoding="UTF-8"?>
! <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="xml" indent="yes" />
<xsl:template match="/">
! <xsl:processing-instruction name="xml-stylesheet">type="text/xsl" href="assertion-coverage.xsl"</xsl:processing-instruction>
! <xsl:variable name="ViolatesAssertions" select="ViolatesAssertions" />
! <xsl:variable name="assertions"
! select="document('assertions.xml')/assertions/assertion"/>
! <xsl:variable name="count"
! select="count($assertions)"/>
! <xsl:variable name="count_component"
! select="count($assertions[@class='component'])"/>
! <xsl:variable name="count_document"
! select="count($assertions[@class='document'])"/>
! <xsl:variable name="count_exchange"
! select="count($assertions[@class='exchange'])"/>
! <xsl:variable name="count_message"
! select="count($assertions[@class='message'])"/>
! <xsl:variable name="unique_violations" select="$ViolatesAssertions//ViolateAssertion[not(@assertion=following::ViolateAssertion/@assertion)]" />
! <assertions component="{$count_component}" document="{$count_document}"
! exchange="{$count_exchange}" message="{$count_message}"
! part1="{count($assertions[@part=1])}" part2="{count($assertions[@part=2])}">
! <xsl:for-each select="$assertions">
! <xsl:sort select="@id"/>
! <xsl:variable name="id" select="@id"/>
! <xsl:variable name="violations" select="$ViolatesAssertions/ViolateAssertion[@assertion=$id]"/>
! <xsl:variable name="count_violations_2" select="count($violations)"/>
!
! <assertion name="{$id}" class="{@class}" href="{concat(@origin, '/#', @id)}" count="{$count_violations_2}">
! <synopsis><xsl:copy-of select="node()"/></synopsis>
! <xsl:for-each select="$violations">
! <test href="{@origin}" id="{@test-id}"/>
! </xsl:for-each>
! </assertion>
! </xsl:for-each>
! </assertions>
</xsl:template>
</xsl:stylesheet>
Index: build.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/build.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -C 2 -d -r1.28 -r1.29
*** build.xml 14 Nov 2006 08:18:20 -0000 1.28
--- build.xml 16 Nov 2006 14:22:06 -0000 1.29
***************
*** 166,169 ****
--- 166,173 ----
</target>
+ <target name="test-suite-coverage-summary-report" depends="test-suite-coverage-summary" description="Generates HTML version of summary of coverage reports.">
+ <xslt style="coverage.xsl" in="test-suite-coverage-summary.xml" out="test-suite-coverage-summary.html" force="yes" />
+ </target>
+
<target name="dtd" description="Generates a DTD for the defined Ant tasks.">
<antstructure output="project.dtd" />
***************
*** 171,183 ****
<target name="extract-assertions" description="Extract assertions from the specifications">
! <xslt style="extract-assertions.xsl" in="../wsdl20/wsdl20-specs.xml" out="assertions.xml" />
</target>
<target name="test-suite-assertions-coverage" depends="extract-assertions" description="Generates a coverage report for assertions">
! <xslt style="violate-assertions.xsl" in="test-suite.xml" out="violate-assertions.xml" />
! <xslt style="assertions-report.xsl" in="violate-assertions.xml" out="assertions-report.html" />
! <delete file='violate-assertions.xml' />
</target>
<target name='test-suite-convert-messages' description='Convert WS-I Log messages into test suite format'>
<xslt style='messages/ws-i.xsl' basedir='messages' destdir='messages'>
--- 175,202 ----
<target name="extract-assertions" description="Extract assertions from the specifications">
! <xslt style="assertions-extractor.xsl" in="../wsdl20/wsdl20-specs.xml" out="assertions.xml" />
</target>
<target name="test-suite-assertions-coverage" depends="extract-assertions" description="Generates a coverage report for assertions">
! <xslt style="assertions-collect-results.xsl" in="test-suite.xml" out="assertions-violated.temp.xml" />
! <xslt style="assertions-report.xsl" in="assertions-violated.temp.xml" out="assertion-coverage.xml" />
! <delete file="assertions-violated.temp.xml" />
! <tstamp />
! <xslt style="assertion-coverage.xsl" in="assertion-coverage.xml" out="Assertion-coverage.html" >
! <param name="DSTAMP" expression="${DSTAMP}"/>
! <param name="TSTAMP" expression="${TSTAMP}"/>
! <param name="TODAY" expression="${TODAY}"/>
! </xslt>
</target>
+ <target name="Dashboard.html" depends="" description="generate Dashboard summary in XML">
+ <tstamp />
+ <xslt style="dashboard.xsl" in="dashboard.xsl" out="Dashboard.html" force="yes">
+ <param name="DSTAMP" expression="${DSTAMP}"/>
+ <param name="TSTAMP" expression="${TSTAMP}"/>
+ <param name="TODAY" expression="${TODAY}"/>
+ </xslt>
+ </target>
+
<target name='test-suite-convert-messages' description='Convert WS-I Log messages into test suite format'>
<xslt style='messages/ws-i.xsl' basedir='messages' destdir='messages'>
--- NEW FILE: Assertion-coverage.html ---
<html lang="en-us">
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Assertion Coverage Report</title>
<link href="http://www.w3.org/StyleSheets/TR/base.css" type="text/css" rel="stylesheet">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<style type="text/css"> .border th, .border td { border: 1px solid black; padding:
0.5ex } .border th { background: #ccc } .good { background: green } .bad {
background: red } .class, .count { text-align: center } .bar { font-weight:
bold; } .synopsis { font-size: small } </style>
</head>
<body>
<h1>Assertion Coverage Report</h1>
<div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold">
<span style="position:absolute">62</span><img alt="27% have coverage" width="54" height="16" src="green.gif"><span style="position:absolute">166</span><img alt="73% have no coverage" width="146" height="16" src="red.gif"></div>
<p>228 assertions
(157 component,
50 document,
18 exchange,
3 message).
106 for part 1,
122 for part 2.
</p>
<table class="border">
<thead>
<tr>
<th>Status</th><th>Count</th><th>Assertion</th><th>Synopsis</th><th>Class</th><th>Tests</th>
</tr>
</thead>
<tbody>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0054">Binding-0054</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/Chat-1B">Chat-1B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0055">Binding-0055</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/Chat-2B">Chat-2B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0056">Binding-0056</a></td><td class="synopsis">This xs:anyURI MUST be an absolute IRI as defined by .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Binding-0057">Binding-0057</a></td><td class="synopsis">For each Binding component in the bindings property of a Description component, the name property MUST be unique.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-3B">Binding-3B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingFault-0058">BindingFault-0058</a></td><td class="synopsis">For each Binding Fault component in the binding faults property of a Binding component, the interface fault property MUST be unique.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Binding-2B">Binding-2B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingFaultReference-0061">BindingFaultReference-0061</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingFaultReference-0062">BindingFaultReference-0062</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingMessageReference-0060">BindingMessageReference-0060</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#BindingOperation-0059">BindingOperation-0059</a></td><td class="synopsis">For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Compare-URI-IRI-0068">Compare-URI-IRI-0068</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-0024">Description-0024</a></td><td class="synopsis">Each WSDL 2.0 or type system component of the same kind MUST be uniquely identified by its qualified name.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-0025">Description-0025</a></td><td class="synopsis">Its value MUST be an absolute IRI (see ) and should be dereferenceable.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Description-2B">Description-2B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201000">Description-1201000</a></td><td class="synopsis">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0 Information Sets (Infosets), that is one or more descriptionelement information items.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201001">Description-1201001</a></td><td class="synopsis">The value of the targetNamespaceattribute information item SHOULD be dereferenceable.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201002">Description-1201002</a></td><td class="synopsis">It SHOULD resolve to a human or machine processable document that directly or indirectly defines the intended semantics of those components.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201003">Description-1201003</a></td><td class="synopsis">It MAY resolve to a WSDL 2.0 document that provides service description information for that namespace.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201004">Description-1201004</a></td><td class="synopsis">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents (which may be combined as needed via ), then the targetNamespaceattribute information item SHOULD resolve to a master WSDL 2.0 document that includes all the WSDL 2.0 documents needed for that service description.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Description-1201005">Description-1201005</a></td><td class="synopsis">Zero or more element information items amongst its [children], in order as follows:</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/TicketAgent-1B">TicketAgent-1B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">4</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Endpoint-0064">Endpoint-0064</a></td><td class="synopsis">This xs:anyURI MUST be an absolute IRI as defined by .</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-14B">Service-14B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-15B">Service-15B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-14B">Service-14B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-15B">Service-15B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Endpoint-0065">Endpoint-0065</a></td><td class="synopsis">For each Endpoint component in the endpoints property of a Service component, the name property MUST be unique.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Endpoint-0066">Endpoint-0066</a></td><td class="synopsis">For each Endpoint component in the endpoints property of a Service component, the binding property MUST either be a Binding component with an unspecified interface property or a Binding component with an interface property equal to the interface property of the Service component.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Equivalence-0067">Equivalence-0067</a></td><td class="synopsis">Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0073">Extensibility-0073</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0074">Extensibility-0074</a></td><td class="synopsis">If a WSDL 2.0 document declares an extension, Feature or Property as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension, Feature or Property, unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension, Feature or Property.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0075">Extensibility-0075</a></td><td class="synopsis">Therefore, the Web service MUST support every extension, Feature or Property that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension, Feature or Property that is declared as mandatory.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extension-1600000">Extension-1600000</a></td><td class="synopsis">The meaning of an extension SHOULD be defined (directly or indirectly) in a document that is available at its namespace IRI.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2200202">FaultDelivery-2200202</a></td><td class="synopsis">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.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultDelivery-2200302">FaultDelivery-2200302</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagation-2200101">FaultPropagation-2200101</a></td><td class="synopsis">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.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagation-2200102">FaultPropagation-2200102</a></td><td class="synopsis">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.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultPropagationModification-2200103">FaultPropagationModification-2200103</a></td><td class="synopsis">However, extensions or binding extensions MAY modify these rulesets.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#FaultReplacesMessage-2200201">FaultReplacesMessage-2200201</a></td><td class="synopsis">When the Fault Replaces Message propagation rule is in effect, any message after the first in the pattern MAY be replaced with a fault message, which MUST have identical direction.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Feature-1207001">Feature-1207001</a></td><td class="synopsis">This IRI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Feature that it identifies.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#FeatureRef-0046">FeatureRef-0046</a></td><td class="synopsis">This xs:anyURI MUST be an absolute IRI as defined by .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#FeatureRef-0047">FeatureRef-0047</a></td><td class="synopsis">The ref property of a Feature component MUST be unique within the features property of an Interface, Interface Fault, Interface Operation, Interface Message Reference, Interface Fault Reference, Binding, Binding Fault, Binding Operation, Binding Message Reference, Binding Fault Reference, Service, or Endpoint component.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPAccessAuthentication-5080">HTTPAccessAuthentication-5080</a></td><td class="synopsis">If the http authentication scheme property is present, then this property MUST be present.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-2603001">HTTPBinding-2603001</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5056">HTTPBinding-5056</a></td><td class="synopsis">When formulating the HTTP message to be transmitted, the HTTP request method used MUST be selected using one of the following:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5057">HTTPBinding-5057</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5058">HTTPBinding-5058</a></td><td class="synopsis">When formulating the HTTP message to be transmitted, the HTTP transfer coding used MUST be selected using one of the following:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5059">HTTPBinding-5059</a></td><td class="synopsis">When formulating the HTTP fault message to be transmitted, the HTTP transfer coding used MUST be selected using one of the following:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5061">HTTPBinding-5061</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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBinding-5062">HTTPBinding-5062</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="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingFault-2606003">HTTPBindingFault-2606003</a></td><td class="synopsis">The fault definition SHOULD agree with the definition of the HTTP error codes, as specified in section 8 of .</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-2B">HTTPBinding-2B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingFault-2607002">HTTPBindingFault-2607002</a></td><td class="synopsis">An integer value of this property identifies the error Status-Code as defined by that the service will use in case the fault is returned.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2604001">HTTPBindingOperation-2604001</a></td><td class="synopsis">Wild cards (for example, application/*) SHOULD NOT be used in this attribute information item since they may lead to interoperability problems.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-3B">HTTPBinding-3B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-4B">HTTPBinding-4B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2605001">HTTPBindingOperation-2605001</a></td><td class="synopsis">The first is transmitted using an HTTP request, and the second is transmitted using the corresponding HTTP response.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2605002">HTTPBindingOperation-2605002</a></td><td class="synopsis">This IRI is combined with the base IRI specified in the address property of the Endpoint component to form the full IRI for the HTTP request to invoke the operation.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-2605003">HTTPBindingOperation-2605003</a></td><td class="synopsis">The value of the serialization format used for a message is a media type which MUST be covered by this range.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-5065">HTTPBindingOperation-5065</a></td><td class="synopsis">In cases where only one message is being sent, the message body of the HTTP response MUST be empty.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPBindingOperation-5066">HTTPBindingOperation-5066</a></td><td class="synopsis">It MUST contain an absolute or a relative IRI, i.e. it MUST NOT include a fragment identifier in the IRI.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-5B">HTTPBinding-5B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-2606001">HTTPHeader-2606001</a></td><td class="synopsis">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:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-2606002">HTTPHeader-2606002</a></td><td class="synopsis">If the value of an HTTP Header component's required property is true, the inclusion of this HTTP header field is REQUIRED</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5063">HTTPHeader-5063</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5068">HTTPHeader-5068</a></td><td class="synopsis">A Binding Message Reference or a Binding Fault component's http headers property MUST NOT contain multiple HTTP Header components with the same name property.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-6B">HTTPBinding-6B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5069">HTTPHeader-5069</a></td><td class="synopsis">This type MUST be a simple type.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-7B">HTTPBinding-7B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPHeader-5070">HTTPHeader-5070</a></td><td class="synopsis">If the value is true, then the HTTP header field MUST be included in the message.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPQueryString-5074">HTTPQueryString-5074</a></td><td class="synopsis">The instance data MUST NOT contain elements with an xs:nil attribute whose value is true.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2607010">HTTPSerialization-2607010</a></td><td class="synopsis">This element MUST NOT carry an xs:nil attribute whose value is true</td><td class="class">message</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2607011">HTTPSerialization-2607011</a></td><td class="synopsis">If this format is used then the style property of Interface Operation component being bound MUST contain a value of http://www.w3.org/@@@@/@@/wsdl/style/iri as defined in , i.e. this serialization format may only be used to serialize the HTTP request corresponding to the initial message of an interface operation.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/HTTPBinding-8B">HTTPBinding-8B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608001">HTTPSerialization-2608001</a></td><td class="synopsis">If the style property of the Interface Operation bound has a value of http://www.w3.org/@@@@/@@/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>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608002">HTTPSerialization-2608002</a></td><td class="synopsis">For the HTTP binding defined in this section (), application/x-www-form-urlencoded MAY be used as a serialization format for an input message (HTTP Request), but MUST NOT be used as a serialization format for an output or fault message (HTTP Response).</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608003">HTTPSerialization-2608003</a></td><td class="synopsis">If not all elements from the instance data are cited in the http location property, or if the property is not present on the Binding Operation component, then additional serialization rules apply.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608004">HTTPSerialization-2608004</a></td><td class="synopsis">For elements of the instance data not cited in the http location property, a query string is constructed as follows.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608005">HTTPSerialization-2608005</a></td><td class="synopsis">If the HTTP request method used does not allow HTTP message body (e.g. GET and DELETE), and if the value of the http location ignore uncited property is false, then the following rules apply.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608007">HTTPSerialization-2608007</a></td><td class="synopsis">If the HTTP request method used does allow an HTTP message body (e.g. POST and PUT), then the following rules apply.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608008">HTTPSerialization-2608008</a></td><td class="synopsis">The Content-Type HTTP header field must have the value application/x-www-form-urlencoded.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-2608009">HTTPSerialization-2608009</a></td><td class="synopsis">this serialization format may only be used to serialize the HTTP request corresponding to the initial message of an interface operation.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5067">HTTPSerialization-5067</a></td><td class="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:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5071">HTTPSerialization-5071</a></td><td class="synopsis">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 .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5073">HTTPSerialization-5073</a></td><td class="synopsis">Strings enclosed within single curly braces MUST be element names from the instance data of the input message.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5075">HTTPSerialization-5075</a></td><td class="synopsis">The Content-Type HTTP header MUST have the value application/xml, or a media type compatible with application/xml as specified in section .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5076">HTTPSerialization-5076</a></td><td class="synopsis">Specifically, for the HTTP binding defined in this section (), multipart/form-data MAY be used as a serialization format for an input message (HTTP Request), but MUST NOT be used as a serialization format for an output or fault message (HTTP Response).</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5077">HTTPSerialization-5077</a></td><td class="synopsis">The Content-Disposition header MUST have the value form-data, and its name parameter is the local name of the element.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5078">HTTPSerialization-5078</a></td><td class="synopsis">The Content-Type header MUST have the value:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#HTTPSerialization-5079">HTTPSerialization-5079</a></td><td class="synopsis">The instance data MUST NOT contain elements with an xs:nil attribute whose value is true.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0001">Import-0001</a></td><td class="synopsis">However, any WSDL 2.0 document that contains component definitions that refer by QName to WSDL 2.0 components that belong to a different namespace MUST contain a wsdl:importelement information item for that namespace (see ).</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Description-1B">Description-1B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0003">Import-0003</a></td><td class="synopsis">Imported components have different target namespace values from the WSDL 2.0 document that is importing them.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0070">Import-0070</a></td><td class="synopsis">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).</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0071">Import-0071</a></td><td class="synopsis">This value MUST NOT match the actual value of targetNamespaceattribute information item in the enclosing WSDL 2.0 document.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-0072">Import-0072</a></td><td class="synopsis">If the location attribute in the importelement information item is dereferencible then it MUST reference a WSDL 2.0 document and 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>[<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>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Import-1400001">Import-1400001</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></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#ImportInclude-1400002">ImportInclude-1400002</a></td><td class="synopsis">The semantics of an extension MUST NOT depend on how components are brought into a component model instance via <import> or <include>.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Include-0069">Include-0069</a></td><td class="synopsis">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.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Include-1B">Include-1B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Include-1400000">Include-1400000</a></td><td class="synopsis">The IRI indicated by location MUST resolve to a WSDL 2.0 document.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOnlyComposition-2200501">InOnlyComposition-2200501</a></td><td class="synopsis">The in-only message exchange pattern consists of exactly one message as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOnlyFaults-2200502">InOnlyFaults-2200502</a></td><td class="synopsis">The in-only message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOptOutComposition-2200801">InOptOutComposition-2200801</a></td><td class="synopsis">The in-optional-out message exchange pattern consists of one or two messages, in order, as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOptOutFaults-2200802">InOptOutFaults-2200802</a></td><td class="synopsis">The in-optional-out message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOutComposition-2200701">InOutComposition-2200701</a></td><td class="synopsis">The in-out message exchange pattern consists of exactly two messages, in order, as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#InOutFaults-2200702">InOutFaults-2200702</a></td><td class="synopsis">The in-out message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0027">Interface-0027</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>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0028">Interface-0028</a></td><td class="synopsis">The list of xs:QName in an extendsattribute information item MUST NOT contain duplicates.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-4B">Interface-4B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0030">Interface-0030</a></td><td class="synopsis">For each Interface component in the interfaces property of a Description component, the name property MUST be unique.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Interface-0031">Interface-0031</a></td><td class="synopsis">Its value, if present, MUST contain absolute IRIs (see ).</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Interface-1B">Interface-1B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-0032">InterfaceFault-0032</a></td><td class="synopsis">For each Interface Fault component in the interface faults property of an Interface component, the name property must be unique.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-0033">InterfaceFault-0033</a></td><td class="synopsis">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 ).</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-2B">InterfaceFault-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-3B">InterfaceFault-3B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1203000">InterfaceFault-1203000</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>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFault-1203001">InterfaceFault-1203001</a></td><td class="synopsis">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.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceFault-3B">InterfaceFault-3B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-0043">InterfaceFaultReference-0043</a></td><td class="synopsis">The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-0044">InterfaceFaultReference-0044</a></td><td class="synopsis">The direction MUST be consistent with the direction implied by the fault propagation ruleset used in the message exchange pattern of the operation.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-0045">InterfaceFaultReference-0045</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceFaultReference-1206000">InterfaceFaultReference-1206000</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-0040">InterfaceMessageReference-0040</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-0041">InterfaceMessageReference-0041</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-0042">InterfaceMessageReference-0042</a></td><td class="synopsis">For each Interface Message Reference component in the interface message references property of an Interface Operation component, its message label property MUST be unique.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205000">InterfaceMessageReference-1205000</a></td><td class="synopsis">An xs:token with one of the values in or out, indicating whether the message is coming to the service or going from the service, respectively.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205001">InterfaceMessageReference-1205001</a></td><td class="synopsis">An xs:token with one of the values #any, #none, #other, or #element.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205002">InterfaceMessageReference-1205002</a></td><td class="synopsis">The type of the elementattribute information item is a union of xs:QName and xs:token where the allowed token values are #any, #none, or #other.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceMessageReference-1205003">InterfaceMessageReference-1205003</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></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-0035">InterfaceOperation-0035</a></td><td class="synopsis">For each Interface Operation component in the interface operations property of an Interface component, the name property MUST be unique.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-2B">InterfaceOperation-2B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-0036">InterfaceOperation-0036</a></td><td class="synopsis">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 ).</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-1B">InterfaceOperation-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-5B">InterfaceOperation-5B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-6B">InterfaceOperation-6B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-0038">InterfaceOperation-0038</a></td><td class="synopsis">An Interface Operation component MUST satisfy the specification defined by each operation style identified by its style property.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204000">InterfaceOperation-1204000</a></td><td class="synopsis">This xs:anyURI MUST be an absolute IRI (see ).</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-3B">InterfaceOperation-3B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204001">InterfaceOperation-1204001</a></td><td class="synopsis">These xs:anyURIs MUST be absolute IRIs (see ).</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-4B">InterfaceOperation-4B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204002">InterfaceOperation-1204002</a></td><td class="synopsis">Its value MUST be an absolute IRI (see ).</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-3B">InterfaceOperation-3B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204003">InterfaceOperation-1204003</a></td><td class="synopsis">Its value MUST be an absolute IRI (see ).</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-4B">InterfaceOperation-4B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#InterfaceOperation-1204005">InterfaceOperation-1204005</a></td><td class="synopsis">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.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/InterfaceOperation-5B">InterfaceOperation-5B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5028">IRIStyle-5028</a></td><td class="synopsis">When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-1B">IRI-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-2B">IRI-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-3B">IRI-3B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5029">IRIStyle-5029</a></td><td class="synopsis">The sequence MUST only contain elements.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-4B">IRI-4B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5030">IRIStyle-5030</a></td><td class="synopsis">The sequence MUST contain only local element children.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-4B">IRI-5B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5031">IRIStyle-5031</a></td><td class="synopsis">The localPart of the element's QName MUST be the same as the Interface Operation component's name.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-6B">IRI-6B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5032">IRIStyle-5032</a></td><td class="synopsis">The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-7B">IRI-7B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">9</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#IRIStyle-5034">IRIStyle-5034</a></td><td class="synopsis">The children elements of the sequence MUST derive from xs:simpleType, and MUST NOT be of the type or derive from xs:QName, xs:NOTATION, xs:hexBinary or xs:base64Binary.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-8B">IRI-8B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-9B">IRI-9B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-10B">IRI-10B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-11B">IRI-11B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-12B">IRI-12B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-13B">IRI-13B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/ad/IRI-14B">IRI-14B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-15B">IRI-15B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/IRI-16B">IRI-16B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-0076">Location-0076</a></td><td class="synopsis">It MUST NOT appear on a wsdl:description element or any of its children/descendants.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-0077">Location-0077</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Location-1700000">Location-1700000</a></td><td class="synopsis">For each pair of IRIs, if the location IRI of the pair is dereferencible 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></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MEP-0037">MEP-0037</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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPDescriptiveness-2200001">MEPDescriptiveness-2200001</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MEPTermination-2200104">MEPTermination-2200104</a></td><td class="synopsis">Generation of a fault, regardless of ruleset, terminates the exchange.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0004">MessageLabel-0004</a></td><td class="synopsis">The messageLabelattribute information item of an interface message 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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0005">MessageLabel-0005</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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0006">MessageLabel-0006</a></td><td class="synopsis">The messageLabelattribute information item of a binding message 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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0007">MessageLabel-0007</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></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0008">MessageLabel-0008</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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0009">MessageLabel-0009</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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0010">MessageLabel-0010</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></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0011">MessageLabel-0011</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></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0012">MessageLabel-0012</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0013">MessageLabel-0013</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="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0014">MessageLabel-0014</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></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0015">MessageLabel-0015</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></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#MessageLabel-0039">MessageLabel-0039</a></td><td class="synopsis">The value of this property MUST match the name of a placeholder message defined by the message exchange pattern.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MessageTriggersFault-2200301">MessageTriggersFault-2200301</a></td><td class="synopsis">When the Message Triggers Fault propagation rule is in effet, any message, including the first in the pattern, MAY trigger a fault message, which MUST have opposite direction.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5035">MultipartStyle-5035</a></td><td class="synopsis">When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be #element.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-1B">Multipart-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-2B">Multipart-2B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-3B">Multipart-3B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5036">MultipartStyle-5036</a></td><td class="synopsis">The sequence MUST only contain elements.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-4B">Multipart-4B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5037">MultipartStyle-5037</a></td><td class="synopsis">The localPart of the element's QName MUST be the same as the Interface Operation component's name.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-8B">Multipart-8B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5038">MultipartStyle-5038</a></td><td class="synopsis">The complex type that defines the body of the element or its children elements MUST NOT contain any attributes.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-9B">Multipart-9B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5039">MultipartStyle-5039</a></td><td class="synopsis">The sequence MUST NOT contain multiple children element declared with the same local name.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-10B">Multipart-10B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5081">MultipartStyle-5081</a></td><td class="synopsis">The sequence MUST contain only local element children.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-5B">Multipart-5B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-6B">Multipart-6B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Multipart-7B">Multipart-7B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#MultipartStyle-5082">MultipartStyle-5082</a></td><td class="synopsis">The attributes minOccurs and maxOccurs for these child elements MUST have a value 1.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#NodeIdentity-2200000">NodeIdentity-2200000</a></td><td class="synopsis">A node MAY be accessible via more than one physical address or transport.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#NoFaults-2200401">NoFaults-2200401</a></td><td class="synopsis">When the No Faults propagation rule is in effect, faults MUST NOT be propagated.</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OperationSafety-2300001">OperationSafety-2300001</a></td><td class="synopsis">However, an operation SHOULD be marked safe if it meets the criteria for a safe interaction defined in Section 3.4 of .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OperationSafety-2300002">OperationSafety-2300002</a></td><td class="synopsis">An OPTIONAL safeattribute information item with the following Infoset properties:</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutInComposition-2201101">OutInComposition-2201101</a></td><td class="synopsis">The out-in message exchange pattern consists of exactly two messages, in order, as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutInFaults-2201102">OutInFaults-2201102</a></td><td class="synopsis">The out-in message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOnlyComposition-2200901">OutOnlyComposition-2200901</a></td><td class="synopsis">The out-only message exchange pattern consists of exactly one message as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOnlyFaults-2200902">OutOnlyFaults-2200902</a></td><td class="synopsis">The out-only message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOptInComposition-2201201">OutOptInComposition-2201201</a></td><td class="synopsis">The out-optional-in message exchange pattern consists of one or two messages, in order, as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#OutOptInFaults-2201202">OutOptInFaults-2201202</a></td><td class="synopsis">The out-optional-in message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-0049">Property-0049</a></td><td class="synopsis">A reference to a Type Definition component in the type definitions property of the Description component constraining the value of the Property, or the token #value if the value property is not empty.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-0050">Property-0050</a></td><td class="synopsis">The ref property of a Property component MUST be unique within the properties property of an Interface, Interface Fault, Interface Operation, Interface Message Reference, Interface Fault Reference, Binding, Binding Fault, Binding Operation, Binding Message Reference, Binding Fault Reference, Service, or Endpoint component.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-0051">Property-0051</a></td><td class="synopsis">All specified values MUST be equal and belong to each specified value set.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Property-1208001">Property-1208001</a></td><td class="synopsis">This IRI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Property that it identifies.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#PropertyRef-0048">PropertyRef-0048</a></td><td class="synopsis">This xs:anyURI MUST be an absolute IRI as defined by .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#QName-0002">QName-0002</a></td><td class="synopsis">Furthermore, all QName references, whether to the same or to different namespaces MUST resolve to components (see ).</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">6</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#QName-resolution-1219000">QName-resolution-1219000</a></td><td class="synopsis">A Description component MUST NOT have such broken references.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-12B">Service-12B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-13B">Service-13B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-12B">Service-12B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-13B">Service-13B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-1B">Service-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Service-2B">Service-2B</a>] </td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustInOnlyComposition-2200601">RobustInOnlyComposition-2200601</a></td><td class="synopsis">The robust in-only message exchange pattern consists of exactly one message as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustInOnlyFaults-2200602">RobustInOnlyFaults-2200602</a></td><td class="synopsis">The robust in-only message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustOutOnlyComposition-2201001">RobustOutOnlyComposition-2201001</a></td><td class="synopsis">The robust out-only message exchange pattern consists of exactly one message as follows:</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RobustOutOnlyFaults-2201002">RobustOutOnlyFaults-2201002</a></td><td class="synopsis">The robust out-only message exchange pattern uses the rule .</td><td class="class">exchange</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5007">RPCStyle-5007</a></td><td class="synopsis">If the RPC style is used by an Interface Operation component then its message exchange pattern property MUST have the value either http://www.w3.org/@@@@/@@/wsdl/in-only or http://www.w3.org/@@@@/@@/wsdl/in-out.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5008">RPCStyle-5008</a></td><td class="synopsis">The value of the message content model property for the Interface Message Reference components of the interface message references property MUST be #element.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-1B">RPC-1B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-2B">RPC-2B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5009">RPCStyle-5009</a></td><td class="synopsis">The content model of input and output element declaration elements MUST be defined using a complex type that contains a sequence from XML Schema.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-3B">RPC-3B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5010">RPCStyle-5010</a></td><td class="synopsis">The input sequence MUST only contain elements and element wildcards.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-4B">RPC-4B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5011">RPCStyle-5011</a></td><td class="synopsis">The input sequence MUST NOT contain more than one element wildcard.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-5B">RPC-5B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5012">RPCStyle-5012</a></td><td class="synopsis">The element wildcard, if present, MUST appear after any elements.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-6B">RPC-6B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5013">RPCStyle-5013</a></td><td class="synopsis">The output sequence MUST only contain elements.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-7B">RPC-7B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5014">RPCStyle-5014</a></td><td class="synopsis">Both the input and output sequences MUST contain only local element children.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-8B">RPC-8B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5015">RPCStyle-5015</a></td><td class="synopsis">The local name of input element's QName MUST be the same as the Interface Operation component's name.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-9B">RPC-9B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5016">RPCStyle-5016</a></td><td class="synopsis">Input and output elements MUST both be in the same namespace.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-14B">RPC-14B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5017">RPCStyle-5017</a></td><td class="synopsis">The complex type that defines the body of an input or an output element MUST NOT contain any local attributes.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-10B">RPC-10B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-11B">RPC-11B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5018">RPCStyle-5018</a></td><td class="synopsis">If elements with the same qualified name appear as children of both the input and output elements, then they MUST both be declared using the same named type.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-15B">RPC-15B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#RPCStyle-5019">RPCStyle-5019</a></td><td class="synopsis">The input or output sequence MUST NOT contain multiple children elements declared with the same name.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-12B">RPC-12B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-13B">RPC-13B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">3</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0016">Schema-0016</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0017">Schema-0017</a></td><td class="synopsis">The referenced schema MUST contain a targetNamespaceattribute information item on its xs:schemaelement information item.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0018">Schema-0018</a></td><td class="synopsis">A WSDL 2.0 document MUST NOT define the same element or type in more than one inlined schema.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0021">Schema-0021</a></td><td class="synopsis">A specification of extension syntax for an alternative schema language MUST use a namespace that is different than the namespace of XML Schema.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0022">Schema-0022</a></td><td class="synopsis">If wsdlx:interface and wsdlx:binding are used together then they MUST satisfy the same consistency rules that apply to the interface property of a Service component and the binding property of a nested Endpoint component, that is either the binding refers the interface of the service or the binding refers to no interface.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0052">Schema-0052</a></td><td class="synopsis">The value of the targetNamespaceattribute information item of the xs:schemaelement information item of an imported schema MUST equal the value of the namespace of the importelement information item in the importing WSDL 2.0 document.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Schema-0053">Schema-0053</a></td><td class="synopsis">The namespace used for an alternate schema language MUST be an absolute IRI.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Service-0063">Service-0063</a></td><td class="synopsis">For each Service component in the services property of a Description component, the name property MUST be unique.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPAction-5048">SOAPAction-5048</a></td><td class="synopsis">A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-2503001">SOAPBinding-2503001</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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5040">SOAPBinding-5040</a></td><td class="synopsis">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.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5041">SOAPBinding-5041</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"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5042">SOAPBinding-5042</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>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5043">SOAPBinding-5043</a></td><td class="synopsis">Every SOAP binding MUST indicate what version of SOAP is in use for the operations of the interface that this binding applies to.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBinding-5044">SOAPBinding-5044</a></td><td class="synopsis">Every SOAP binding MUST indicate what underlying protocol is in use.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPBindingFault-5045">SOAPBindingFault-5045</a></td><td class="synopsis">For every Interface Fault component contained in an Interface component, a mapping to a SOAP Fault MUST be described.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHeaderBlock-5050">SOAPHeaderBlock-5050</a></td><td class="synopsis">When its value is true, the SOAP header block MUST be decorated with a SOAP mustUnderstandattribute information item with a value of true; if so, the XML element declaration referenced by the element declaration property MUST allow this SOAP mustUnderstandattribute information item.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHeaderBlock-5051">SOAPHeaderBlock-5051</a></td><td class="synopsis">If the value is true, then the SOAP header block MUST be included in the message.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHeaderBlock-5052">SOAPHeaderBlock-5052</a></td><td class="synopsis">The value of the elementattribute information item MUST resolve to a global element declaration from the element declarations property of the Description component.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHTTPGeneration-5055">SOAPHTTPGeneration-5055</a></td><td class="synopsis">If the SOAP MEP selected is http://www.w3.org/2003/05/soap/mep/soap-response/ then the value of the SOAP http://www.w3.org/2003/05/soap/mep/ImmediateDestination property MUST be generated using the HTTP binding extension's rules for generating an IRI for HTTP GET (see ).</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHTTPSelection-5054">SOAPHTTPSelection-5054</a></td><td class="synopsis">This default binding rule is applicable when the value of the soap underlying protocol property of the Binding component is http://www.w3.org/2003/05/soap/bindings/HTTP/. If the SOAP MEP selected as specified above has the value http://www.w3.org/2003/05/soap/mep/request-response/ then the HTTP method used is POST. If the SOAP MEP selected has the value http://www.w3.org/2003/05/soap/mep/soap-response/ then the HTTP method used is GET.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPMEP-5047">SOAPMEP-5047</a></td><td class="synopsis">A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPMEPDefault-5046">SOAPMEPDefault-5046</a></td><td class="synopsis">A xs:anyURI, which is an absolute IRI as defined by , to the Binding component.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPMEPSelection-5053">SOAPMEPSelection-5053</a></td><td class="synopsis">For a given Interface Operation component, if there is a Binding Operation component whose interface operation property matches the component in question and its soap mep property has a value, then the SOAP MEP is the value of the soap mep property. Otherwise, the SOAP MEP is the value of the Binding component's soap mep default, if any. Otherwise, the Interface Operation component's message exchange pattern property MUST have the value http://www.w3.org/@@@@/@@/wsdl/in-out, and the SOAP MEP is the URI http://www.w3.org/2003/05/soap/mep/request-response/ identifying the SOAP Request-Response Message Exchange Pattern as defined in .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPModule-5049">SOAPModule-5049</a></td><td class="synopsis">A xs:anyURI, which is an absolute IRI as defined by .</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-0023">Types-0023</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 “import” element information item).</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-0026">Types-0026</a></td><td class="synopsis">Each XML Schema type definition MUST have a unique QName.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1201006">Types-1201006</a></td><td class="synopsis">Each XML Schema element declaration MUST have a unique QName.</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300000">Types-1300000</a></td><td class="synopsis">Every QName reference MUST resolve (see ).</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300001">Types-1300001</a></td><td class="synopsis">When resolving QNames references for schema definitions, the namespace MUST be imported by the referring WSDL 2.0 document.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300002">Types-1300002</a></td><td class="synopsis">Specifically components that the schema imports via xs:import are NOT referenceable.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300003">Types-1300003</a></td><td class="synopsis">Similarly, components defined in an inlined XML schema are NOT automatically referenceable within WSDL 2.0 document that imported (using wsdl:import) the WSDL 2.0 document that inlines the schema (see for more details).</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300005">Types-1300005</a></td><td class="synopsis">The type of the wsdlx:interfaceattribute information item is an xs:QName that specifies the name property of an Interface component.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Types-1300006">Types-1300006</a></td><td class="synopsis">The type of the wsdlx:bindingattribute information item is an xs:QName that specifies the name property of a Binding component.</td><td class="class">document</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5019">WRPC-5019</a></td><td class="synopsis">OPTIONAL, but MUST be present when the style is RPC</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="bad"> </td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5020">WRPC-5020</a></td><td class="synopsis">Values for the second component MUST be chosen among the following four: "#in", "#out", "#inout" "#return".</td><td class="class">component</td><td></td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5021">WRPC-5021</a></td><td class="synopsis">The value of the first component of each pair (q, t) MUST be unique within the list.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-17B">RPC-17B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5022">WRPC-5022</a></td><td class="synopsis">For each child element of the input and output messages of the operation, a pair (q, t), whose first component q is equal to the qualified name of that element, MUST be present in the list, with the caveat that elements that appear with cardinality greater than one MUST be treated as a single element.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-18B">RPC-18B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5023">WRPC-5023</a></td><td class="synopsis">For each pair (q, #in), there MUST be a child element of the input element with a name of q. There MUST NOT be a child element of the output element with the name of q.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-19B">RPC-19B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-20B">RPC-20B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5024">WRPC-5024</a></td><td class="synopsis">For each pair (q, #out), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-21B">RPC-21B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-22B">RPC-22B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5025">WRPC-5025</a></td><td class="synopsis">For each pair (q, #inout), there MUST be a child element of the input element with a name of q. There MUST also be a child element of the output element with the name of q.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-23B">RPC-23B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-24B">RPC-24B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">2</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5026">WRPC-5026</a></td><td class="synopsis">For each pair (q, #return), there MUST be a child element of the output element with a name of q. There MUST NOT be a child element of the input element with the name of q.</td><td class="class">component</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-25B">RPC-25B</a>] [<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-26B">RPC-26B</a>] </td>
</tr>
<tr>
<td class="good"> </td><td class="count">1</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#WRPC-5027">WRPC-5027</a></td><td class="synopsis">Additionally, each even-numbered item (0, 2, 4, ...) in the list MUST be of type xs:QName and each odd-numbered item (1, 3, 5, ...) in the list MUST be of the subtype of xs:token described in the previous paragraph.</td><td class="class">document</td><td>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-27B">RPC-27B</a>] </td>
</tr>
</tbody>
</table>
</body>
</html>
Index: coverage.xsl
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/coverage.xsl,v
retrieving revision 1.5
retrieving revision 1.6
diff -C 2 -d -r1.5 -r1.6
*** coverage.xsl 29 Jul 2006 20:46:25 -0000 1.5
--- coverage.xsl 16 Nov 2006 14:22:06 -0000 1.6
***************
*** 17,25 ****
version="1.0">
! <xsl:output method="html" indent="yes" />
<xsl:template match="/coverage">
<html>
<head>
<title>
WSDL 2.0 Document Test Case Coverage Report
--- 17,26 ----
version="1.0">
! <xsl:output method="xml" encoding="UTF-8" indent="yes" />
<xsl:template match="/coverage">
<html>
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>
WSDL 2.0 Document Test Case Coverage Report
***************
*** 32,40 ****
WSDL 2.0 Document Test Case Coverage Report
</h1>
! <address>
! <xsl:text>Generated</xsl:text>
! <xsl:value-of select="' '" />
! <xsl:value-of select="TODAY" />
! </address>
<p>
This reports measures the coverage of WSDL 2.0
--- 33,43 ----
WSDL 2.0 Document Test Case Coverage Report
</h1>
! <xsl:if test="TODAY">
! <address>
! <xsl:text>Generated </xsl:text>
! <xsl:value-of select="TODAY" />,
! <xsl:value-of select="TSTAMP" />
! </address>
! </xsl:if>
<p>
This reports measures the coverage of WSDL 2.0
***************
*** 46,50 ****
<tr>
<th align="right">Good Documents:</th>
! <td align="right">
<xsl:value-of select="good" />
</td>
--- 49,53 ----
<tr>
<th align="right">Good Documents:</th>
! <td align="left">
<xsl:value-of select="good" />
</td>
***************
*** 52,56 ****
<tr>
<th align="right">Bad Documents:</th>
! <td align="right">
<xsl:value-of select="bad" />
</td>
--- 55,59 ----
<tr>
<th align="right">Bad Documents:</th>
! <td align="left">
<xsl:value-of select="bad" />
</td>
***************
*** 58,65 ****
<tr>
<th align="right">Total Documents:</th>
! <td align="right">
<xsl:value-of select="total" />
</td>
</tr>
</table>
<br />
--- 61,74 ----
<tr>
<th align="right">Total Documents:</th>
! <td align="left">
<xsl:value-of select="total" />
</td>
</tr>
+ <tr>
+ <th align="right">Coverage Summary:</th>
+ <td>
+ <xsl:call-template name="test-coverage-summary"/>
+ </td>
+ </tr>
</table>
<br />
***************
*** 85,89 ****
<xsl:template match="item">
<tr>
! <td>
<xsl:attribute name="bgcolor">
<xsl:choose>
--- 94,98 ----
<xsl:template match="item">
<tr>
! <td count="{@count}">
<xsl:attribute name="bgcolor">
<xsl:choose>
***************
*** 103,106 ****
</tr>
</xsl:template>
!
</xsl:stylesheet>
\ No newline at end of file
--- 112,128 ----
</tr>
</xsl:template>
! <xsl:template name="test-coverage-summary">
! <div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold; margin:0px">
! <xsl:variable name="total" select="count(item)"/>
! <xsl:variable name="none" select="count(item[@count = 0])"/>
! <xsl:variable name="some" select="count(item[@count > 0 and @count < 4])"/>
! <xsl:variable name="many" select="count(item[@count > 3])"/>
! <xsl:variable name="percentage-none" select="$none div $total"/>
! <xsl:variable name="percentage-some" select="$some div $total"/>
! <xsl:variable name="percentage-many" select="$many div $total"/>
! <xsl:if test="$percentage-many > .01"><span style="position:absolute"><xsl:value-of select="$many"/></span><img src="green.gif" height="16" width="{round(200*$percentage-many)}" alt="{round($percentage-many * 100)}% have good coverage"/></xsl:if>
! <xsl:if test="$percentage-some > .01"><span style="position:absolute"><xsl:value-of select="$some"/></span><img src="yellow.gif" height="16" width="{round(200*$percentage-some)}" alt="{round($percentage-some* 100)}% have minimal coverage"/></xsl:if>
! <xsl:if test="$percentage-none > .01"><span style="position:absolute"><xsl:value-of select="$none"/></span><img src="red.gif" height="16" width="{round(200*$percentage-none)}" alt="{round($percentage-none* 100)}% have no coverage"/></xsl:if>
! </div>
! </xsl:template>
</xsl:stylesheet>
\ No newline at end of file
--- NEW FILE: yellow.gif ---
(This appears to be a binary file; contents omitted.)
--- NEW FILE: Dashboard.html ---
<html xmlns:report="http://www.w3.org/2006/06/wsdl/ValidationReport"><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Test Suite Health Dashboard</title><style type="text/css">
body {font-family:sans-serif}
td {border:1px solid #DDDDDD}
.passed {background-color:green}
.failed {background-color:orange}
.disaster {background-color:red}
.border th, .border td { border: 1px solid black; padding: 0.5ex }
.border th { background: #ccc }
.good { background: green }
.bad { background: red }
</style></head><body><h2>Test Suite Health Dashboard</h2><address>Generated November 16 2006,
0621</address><p>Assertion Coverage (<a href="Assertion-coverage.html">details</a>)</p><div style="border:1px solid black; padding:0px; width:202px; height:18px; font-size:x-small; font-weight:bold"><span style="position:absolute">62</span><img alt="27% have coverage" width="54" height="16" src="green.gif"><span style="position:absolute">166</span><img alt="73% have no coverage" width="146" height="16" src="red.gif"></div><p>Test Case Coverage (<a href="test-suite-coverage-summary.xml">details</a>)</p><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">60</span><img alt="54% have good coverage" width="108" height="16" src="green.gif"><span style="position:absolute">30</span><img alt="27% have minimal coverage" width="54" height="16" src="yellow.gif"><span style="position:absolute">21</span><img alt="19% have no coverage" width="38" height="16" src="red.gif"></div><p></p><hr><h2>Implementation Health/h2><p>Component Model Test Results (<a href="results/Interchange.html">details</a>)</p><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">43</span><img alt="64% passed" width="128" height="16" src="green.gif"><span style="position:absolute">24</span><img alt="36% failed" width="72" height="16" src="red.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">66</span><img alt="99% passed" width="197" 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">43</span><img alt="64% passed" width="128" height="16" src="green.gif"><span style="position:absolute">20</span><img alt="30% failed" with="60" height="16" src="red.gif"></td></tr></table><p>Validation Test Results (<a href="results/Validation.html">details</a>)</p><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">2</span><img alt="1.1627906976744187% passed" width="2.3255813953488373" height="16" src="green.gif"><span style="position:absolute"> (170)</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">19</span><img alt="11.046511627906977% passed" width="22.093023255813954" height="16" src="green.gif"><span style="position:absolute">91</span><img alt="52.90697674418605% passed" width="105.8139534883721" height="16" src="yellow.gif"><span style="position:absolute">50</span><img alt="29.069767441860467% failed" width="58.139534883720934" height="16" src"red.gif"><span style="position:absolute"> (12)</span></div></td></tr></tbody></table><p>Message Exchange Test Results (<a href="tbd">details</a>)</p><p>tbd</p></body></html>
Received on Thursday, 16 November 2006 14:25:02 UTC