W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > November 2006

2002/ws/desc/test-suite build.xml,1.37,1.38 assertion-coverage.xml,1.3,1.4 Assertion-coverage.html,1.3,1.4 assertions.xml,1.3,1.4

From: Jonathan Marsh via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 27 Nov 2006 18:14:14 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1Gokze-0003CR-Lh@lionel-hutz.w3.org>

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

Modified Files:
	build.xml assertion-coverage.xml Assertion-coverage.html 
	assertions.xml 
Log Message:
Rebuild assertion coverage report and dashboard.

Index: assertions.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/assertions.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C 2 -d -r1.3 -r1.4
*** assertions.xml	16 Nov 2006 14:22:06 -0000	1.3
--- assertions.xml	27 Nov 2006 18:14:12 -0000	1.4
***************
*** 49,82 ****
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0009" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0013" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="FeatureRef-0046" class="component" part="1" section="2" subsection="07">This xs:anyURI MUST be an absolute IRI as defined by .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="false" id="Feature-1207001" class="component" part="1" section="2" subsection="07">This IRI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Feature that it identifies.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="FeatureRef-0047" class="component" part="1" section="2" subsection="07">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="PropertyRef-0048" class="component" part="1" section="2" subsection="08">This xs:anyURI MUST be an absolute IRI as defined by .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Property-1208001" class="component" part="1" section="2" subsection="08">This IRI SHOULD be dereferenceable to a document that directly or indirectly defines the meaning and use of the Property that it identifies.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Property-0049" class="component" part="1" section="2" subsection="08">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Property-0050" class="component" part="1" section="2" subsection="08">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Property-0051" class="component" part="1" section="2" subsection="08">All specified values MUST be equal and belong to each specified value set.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0054" class="component" part="1" section="2" subsection="09">If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components) then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0055" class="component" part="1" section="2" subsection="09">A Binding component that defines bindings for an Interface component MUST define bindings for all the operations of that Interface component.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0056" class="component" part="1" section="2" subsection="09">This xs:anyURI MUST be an absolute IRI as defined by .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0057" class="component" part="1" section="2" subsection="09">For each Binding component in the bindings 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="BindingFault-0058" class="component" part="1" section="2" subsection="10">For each Binding Fault component in the binding faults property of a Binding component, the interface fault property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingOperation-0059" class="component" part="1" section="2" subsection="11">For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingMessageReference-0060" class="component" part="1" section="2" subsection="12">For each Binding Message Reference component in the binding message references property of a Binding Operation component, the interface message reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0006" class="document" part="1" section="2" subsection="12">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0010" class="document" part="1" section="2" subsection="12">If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0014" class="document" part="1" section="2" subsection="12">If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-0061" class="component" part="1" section="2" subsection="13">For each Binding Fault Reference component in the binding fault references property of a Binding Operation component, the interface fault reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0007" class="document" part="1" section="2" subsection="13">The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0011" class="document" part="1" section="2" subsection="13">If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0015" class="document" part="1" section="2" subsection="13">If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-0062" class="component" part="1" section="2" subsection="13">There MUST be an Interface Fault Reference component in the interface fault references of the Interface Operation being bound with message label equal to the effective message label and with interface fault equal to an Interface Fault component with name equal to the actual value of the refattribute information item.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Service-0063" class="component" part="1" section="2" subsection="14">For each Service component in the services 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="Endpoint-0064" class="component" part="1" section="2" subsection="15">This xs:anyURI MUST be an absolute IRI as defined by .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Endpoint-0065" class="component" part="1" section="2" subsection="15">For each Endpoint component in the endpoints property of a Service component, the name property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Endpoint-0066" class="component" part="1" section="2" subsection="15">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Equivalence-0067" class="component" part="1" section="2" subsection="17">Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="QName-resolution-1219000" class="document" part="1" section="2" subsection="19">A Description component MUST NOT have such broken references.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Compare-URI-IRI-0068" class="component" part="1" section="2" subsection="20">When such absolute URIs and IRIs are being compared to determine equivalence (see ) they MUST be compared character-by-character as indicated in .</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-0016" class="document" part="1" section="3" subsection="01">A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace unless an xs:import or xs:schemaelement information item for that namespace is present or the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-0017" class="document" part="1" section="3" subsection="01">The referenced schema MUST contain a targetNamespaceattribute information item on its xs:schemaelement information item.</assertion>
--- 49,74 ----
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0009" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0013" class="document" part="1" section="2" subsection="06">If the messageLabelattribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0054" class="component" part="1" section="2" subsection="07">If a Binding component specifies any operation-specific binding details (by including Binding Operation components) or any fault binding details (by including Binding Fault components) then it MUST specify an interface the Binding component applies to, so as to indicate which interface the operations come from.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0055" class="component" part="1" section="2" subsection="07">A Binding component that defines bindings for an Interface component MUST define bindings for all the operations of that Interface component.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0056" class="component" part="1" section="2" subsection="07">This xs:anyURI MUST be an absolute IRI as defined by .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Binding-0057" class="component" part="1" section="2" subsection="07">For each Binding component in the bindings 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="BindingFault-0058" class="component" part="1" section="2" subsection="08">For each Binding Fault component in the binding faults property of a Binding component, the interface fault property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingOperation-0059" class="component" part="1" section="2" subsection="09">For each Binding Operation component in the binding operations property of a Binding component, the interface operation property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingMessageReference-0060" class="component" part="1" section="2" subsection="10">For each Binding Message Reference component in the binding message references property of a Binding Operation component, the interface message reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0006" class="document" part="1" section="2" subsection="10">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0010" class="document" part="1" section="2" subsection="10">If the messageLabelattribute information item of a binding message reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0014" class="document" part="1" section="2" subsection="10">If the messageLabelattribute information item of a binding message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-0061" class="component" part="1" section="2" subsection="11">For each Binding Fault Reference component in the binding fault references property of a Binding Operation component, the interface fault reference property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0007" class="document" part="1" section="2" subsection="11">The messageLabelattribute information item of a binding fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0011" class="document" part="1" section="2" subsection="11">If the messageLabelattribute information item of a binding fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="MessageLabel-0015" class="document" part="1" section="2" subsection="11">If the messageLabelattribute information item of a binding fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="BindingFaultReference-0062" class="component" part="1" section="2" subsection="11">There MUST be an Interface Fault Reference component in the interface fault references of the Interface Operation being bound with message label equal to the effective message label and with interface fault equal to an Interface Fault component with name equal to the actual value of the refattribute information item.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Service-0063" class="component" part="1" section="2" subsection="12">For each Service component in the services property of a Description component, the name property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Endpoint-0064" class="component" part="1" section="2" subsection="13">This xs:anyURI MUST be an absolute IRI as defined by .</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Endpoint-0065" class="component" part="1" section="2" subsection="13">For each Endpoint component in the endpoints property of a Service component, the name property MUST be unique.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Endpoint-0066" class="component" part="1" section="2" subsection="13">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Equivalence-0067" class="component" part="1" section="2" subsection="15">Extension properties which are not string values, sets of strings or references MUST describe their values' equivalence rules.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="QName-resolution-1219000" class="document" part="1" section="2" subsection="17">A Description component MUST NOT have such broken references.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Compare-URI-IRI-0068" class="component" part="1" section="2" subsection="18">When such absolute URIs and IRIs are being compared to determine equivalence (see ) they MUST be compared character-by-character as indicated in .</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-0016" class="document" part="1" section="3" subsection="01">A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace unless an xs:import or xs:schemaelement information item for that namespace is present or the namespace is the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition .</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Schema-0017" class="document" part="1" section="3" subsection="01">The referenced schema MUST contain a targetNamespaceattribute information item on its xs:schemaelement information item.</assertion>
***************
*** 102,107 ****
  <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>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-0074" class="component" part="1" section="6" subsection="01">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.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-0075" class="component" part="1" section="6" subsection="01">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.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-0076" class="document" part="1" section="7" subsection="00">It MUST NOT appear on a wsdl:description element or any of its children/descendants.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-0077" class="component" part="1" section="7" subsection="01">Its actual value MUST be a list of pairs of IRIs; where the first IRI of a pair, which MUST be an absolute IRI as defined in , indicates a WSDL 2.0 (or 1.1) namespace name, and, the second a hint as to the location of a WSDL 2.0 document defining WSDL 2.0 components (or WSDL 1.1 elements ) for that namespace name.</assertion>
--- 94,99 ----
  <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>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-0074" class="component" part="1" section="6" subsection="01">If a WSDL 2.0 document declares an extension as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension.</assertion>
! <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Extensibility-0075" class="component" part="1" section="6" subsection="01">Therefore, the Web service MUST support every extension that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension that is declared as mandatory.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-0076" class="document" part="1" section="7" subsection="00">It MUST NOT appear on a wsdl:description element or any of its children/descendants.</assertion>
  <assertion origin="http://www.w3.org/TR/2006/CR-wsdl20-20060327" required="true" id="Location-0077" class="component" part="1" section="7" subsection="01">Its actual value MUST be a list of pairs of IRIs; where the first IRI of a pair, which MUST be an absolute IRI as defined in , indicates a WSDL 2.0 (or 1.1) namespace name, and, the second a hint as to the location of a WSDL 2.0 document defining WSDL 2.0 components (or WSDL 1.1 elements ) for that namespace name.</assertion>
***************
*** 124,137 ****
  <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>
--- 116,119 ----

Index: assertion-coverage.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/assertion-coverage.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C 2 -d -r1.3 -r1.4
*** assertion-coverage.xml	18 Nov 2006 00:06:52 -0000	1.3
--- assertion-coverage.xml	27 Nov 2006 18:14:12 -0000	1.4
***************
*** 2,6 ****
  <?xml-stylesheet type="text/xsl" href="assertion-coverage.xsl"?>
  
! <assertions part2="122" part1="106" message="3" exchange="18" document="50" component="157">
  <assertion count="3" 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>
--- 2,6 ----
  <?xml-stylesheet type="text/xsl" href="assertion-coverage.xsl"?>
  
! <assertions part2="112" part1="98" message="3" exchange="13" document="50" component="144">
  <assertion count="3" 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>
***************
*** 100,107 ****
  </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">
--- 100,107 ----
  </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 as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension.</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 that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension 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">
***************
*** 126,138 ****
  <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>
--- 126,129 ----
***************
*** 309,318 ****
  <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>
--- 300,303 ----
***************
*** 576,612 ****
  <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>
--- 561,564 ----
***************
*** 625,634 ****
  <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="1" 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>
--- 577,580 ----

Index: Assertion-coverage.html
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/Assertion-coverage.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C 2 -d -r1.3 -r1.4
*** Assertion-coverage.html	18 Nov 2006 00:06:52 -0000	1.3
--- Assertion-coverage.html	27 Nov 2006 18:14:12 -0000	1.4
***************
*** 13,24 ****
  <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">105</span><img alt="46% have coverage" width="92" height="16" src="green.gif"><span style="position:absolute">123</span><img alt="54% have no coverage" width="108" 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">
--- 13,24 ----
  <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">105</span><img alt="50% have coverage" width="100" height="16" src="green.gif"><span style="position:absolute">105</span><img alt="50% have no coverage" width="100" height="16" src="red.gif"></div>
! <p>210 assertions
! 					(144 component, 
  					50 document, 
! 					13 exchange, 
  					3 message). 
! 					98 for part 1,
! 					112 for part 2.
  				</p>
  <table class="border">
***************
*** 99,106 ****
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-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">&nbsp;</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>
--- 99,106 ----
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0074">Extensibility-0074</a></td><td class="synopsis">If a WSDL 2.0 document declares an extension as optional (i.e., NON-mandatory), then the Web service MUST NOT assume that the client supports that extension unless the Web service knows (through some other means) that the client has in fact elected to engage and support that extension.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
! <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/#Extensibility-0075">Extensibility-0075</a></td><td class="synopsis">Therefore, the Web service MUST support every extension that is declared as optional in the WSDL 2.0 document, in addition to supporting every extension that is declared as mandatory.</td><td class="class">component</td><td></td>
  </tr>
  <tr>
***************
*** 126,138 ****
  </tr>
  <tr>
- <td class="bad">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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>
--- 126,129 ----
***************
*** 291,300 ****
  </tr>
  <tr>
- <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#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">&nbsp;</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">&nbsp;</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>
--- 282,285 ----
***************
*** 495,531 ****
  </tr>
  <tr>
- <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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">&nbsp;</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>
--- 480,483 ----
***************
*** 540,549 ****
  </tr>
  <tr>
- <td class="bad">&nbsp;</td><td class="count">0</td><td><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#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">&nbsp;</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="good">&nbsp;</td><td class="count">1</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>[<a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/RPC-28B">RPC-28B</a>] </td>
  </tr>
--- 492,495 ----

Index: build.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/build.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -C 2 -d -r1.37 -r1.38
*** build.xml	20 Nov 2006 02:32:22 -0000	1.37
--- build.xml	27 Nov 2006 18:14:12 -0000	1.38
***************
*** 202,206 ****
  
  	<target name="extract-assertions" description="Extract assertions from the specifications">
! 		<xslt style="assertions-extractor.xsl" in="../wsdl20/wsdl20-specs.xml" out="assertions.xml" />
  	</target>
  
--- 202,206 ----
  
  	<target name="extract-assertions" description="Extract assertions from the specifications">
! 		<xslt style="assertions-extractor.xsl" in="../wsdl20/wsdl20-specs.xml" out="assertions.xml" force="yes"/>
  	</target>
  
Received on Monday, 27 November 2006 18:15:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:24 UTC