W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > April to June 2005

2004/ws/addressing Makefile.testsuite,NONE,1.1 ws-addr-testsuite.xml,NONE,1.1 ws-addr-testsuite.html,NONE,1.1 Makefile,1.3,1.4 entitieswd.dtd,1.6,1.7 entities.dtd,1.6,1.7

From: Paul Downey via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 20 Apr 2005 21:43:00 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DOMyL-0002wx-0k@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv11319

Modified Files:
	Makefile entitieswd.dtd entities.dtd 
Added Files:
	Makefile.testsuite ws-addr-testsuite.xml 
	ws-addr-testsuite.html 
Log Message:
added testsuite overview document

Index: entitieswd.dtd
===================================================================
RCS file: /sources/public/2004/ws/addressing/entitieswd.dtd,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** entitieswd.dtd	22 Mar 2005 14:35:57 -0000	1.6
--- entitieswd.dtd	20 Apr 2005 21:42:58 -0000	1.7
***************
*** 17,20 ****
--- 17,21 ----
  <!ENTITY wsa-soap.prefix "ws-addr-soap">
  <!ENTITY wsa-wsdl.prefix "ws-addr-wsdl">
+ <!ENTITY wsa-testsuite.prefix "ws-addr-testsuite">
  
  <!ENTITY w3c.tr.latest  "http://www.w3.org/TR">	
***************
*** 32,35 ****
--- 33,38 ----
  <!ENTITY w3c-designation-wsa-wsdl
    "&w3c.tr.latest;/&draft.year;/WD-&wsa-wsdl.prefix;-&draft.date;">
+ <!ENTITY w3c-designation-wsa-testsuite
+   "&w3c.tr.latest;/&draft.year;/WD-&wsa-testsuite.prefix;-&draft.date;">
  <!ENTITY w3c-designation-generic
    "&w3c.tr.latest;/&draft.year;/WD-&prefix;-&draft.date;">

--- NEW FILE: Makefile.testsuite ---
# -*-makefile-*-
# $Id: Makefile.testsuite,v 1.1 2005/04/20 21:42:57 pdowney Exp $

PREFIX=ws-addr-testsuite

SCHEMAS=ws-addr.xsd

IMAGES=

FILES=\
$(IMAGES) \
xmlspec.dtd \
entitiesedcopy.dtd \
entitieswd.dtd \
entities.dtd \
xmlspec.xsl \
xmlspec-addressing.xsl

include Makefile.base

Index: Makefile
===================================================================
RCS file: /sources/public/2004/ws/addressing/Makefile,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** Makefile	22 Mar 2005 11:43:13 -0000	1.3
--- Makefile	20 Apr 2005 21:42:58 -0000	1.4
***************
*** 2,5 ****
--- 2,6 ----
  SOAP=Makefile.soap
  WSDL=Makefile.wsdl
+ TESTSUITE=Makefile.testsuite
  
  default:
***************
*** 9,15 ****
  	echo "	core";\
  	echo "	soap";\
! 	echo "	wsdl"
  
! all: core soap wsdl
  
  core:
--- 10,17 ----
  	echo "	core";\
  	echo "	soap";\
! 	echo "	wsdl";\
! 	echo "	testsuite"
  
! all: core soap wsdl 
  
  core:
***************
*** 22,30 ****
  	make -f $(WSDL)
  
  clean:
! 	@for m in $(CORE) $(SOAP) $(WSDL); do\
  	make -f $$m clean; done
  
! .PHONY: default all core soap wsdl clean
  
  # Used for nxml-mode in Emacs
--- 24,35 ----
  	make -f $(WSDL)
  
+ testsuite:
+ 	make -f $(TESTSUITE)
+ 
  clean:
! 	@for m in $(CORE) $(SOAP) $(WSDL) $(TESTSUITE); do\
  	make -f $$m clean; done
  
! .PHONY: default all core soap wsdl testsuite clean
  
  # Used for nxml-mode in Emacs

--- NEW FILE: ws-addr-testsuite.xml ---
<?xml version="1.0"?>
<!-- $Id: ws-addr-testsuite.xml,v 1.1 2005/04/20 21:42:58 pdowney Exp $ -->
<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.1//EN" "xmlspec.dtd" [
<!ENTITY prefix "ws-addr-testsuite">
<!ENTITY % entities SYSTEM "entities.dtd" >
%entities;
<!ENTITY status SYSTEM "status.xml">
<!ENTITY document.status "Editors' copy $Date: 2005/04/20 21:42:58 $">
<!ENTITY wsa-title "&wsa-testsuite.title;">
<!ENTITY prevloc "">
]>
<?xml-stylesheet type='text/xsl' href='xmlspec-addressing.xsl'?>
<spec w3c-doctype="wd" role="&document.role;">
    <header>
        <title>&wsa-testsuite.title;</title>
        <w3c-designation>&w3c-designation-wsa-testsuite;</w3c-designation>
        <w3c-doctype>&document.status;</w3c-doctype>
        <pubdate>
            <day>&draft.day;</day>
            <month>&draft.month;</month>
            <year>&draft.year;</year>
        </pubdate>
        <publoc>
            <loc href="&w3c-designation-wsa-testsuite;">&w3c-designation-wsa-testsuite;</loc>
        </publoc> &altlocs; <prevlocs>
            <loc href="&prevloc;">&prevloc;</loc>
        </prevlocs>
        <latestloc>
            <loc href="&wsa-testsuite.latest;">&wsa-testsuite.latest;</loc>
        </latestloc>
        <authlist>
            <author>
                <name>Paul Downey</name>
                <affiliation>BT</affiliation>
            </author>
        </authlist>
        <abstract>
            <p>This document describes the Test Suite deliverable for the 
		<loc href='http://www.w3.org/2002/ws/addr/'>Web Services Addressing Working Group</loc>
 as defined by the Working Group's 
		    <loc href="http://www.w3.org/2004/09/wsa-charter.html">Charter</loc>. </p>
        </abstract> &status; <langusage>
            <language id="en-US">English</language>
        </langusage>
        <revisiondesc>
            <p>Last Modified: $Date: 2005/04/20 21:42:58 $</p>
        </revisiondesc>
    </header>
    <body>
        <div1 id="tocRange">
            <head>Introduction</head>
            <p>One of the deliverables specified in the Charter of the Web Services Addressing
		Working Group is 
		<emph>a test suite intended to promote implementation of the 
		Candidate Recommendation, and to assess interoperability between these 
		implementations.</emph>
	    </p>
	    <p>The Working Group Charter also states that <emph>the Working Group is expected to demonstrate four 
		interoperable implementations during the Call for Implementations step.</emph> 
		It is anticipated that some, but not all of the test cases held within the test suite 
		will be used to practially test implementations during an interoperability 
		Workshop and thereby satisfy the entrance 
		criteria for the Web Service Addressing 
		specifications to enter the 
		<loc href='http://www.w3.org/Consortium/Process-20010719/tr.html#RecsPR'>Proposed Recommendation stage</loc>.</p>
		<p>The test suite will be maintained by the Working Group and remain available for
		regression testing beyond publication of the Web Addressing Recommendation, however
		it is not expected that the test suite will form a part of the Web Addressing 
		Recommendation; the status of this document will remain as a Working Group note.
		</p>

            <div2 id="conformance">
                <head>Conformance Claims</head>
		<p>
		A Web Services Addressing implementation that passes all of the tests specified
		in this document may claim conformance to the Web Services Addressing Test
		Suite $Date: 2005/04/20 21:42:58 $.
		</p>
		<p>
		Conformance to the Web services Addressing Test Suite does not by itself enable a 
		party to claim conformance with the Web Services Addressing specification.
		Not passing an individual test may be used as an indication that an implementation 
		is likely not to conform to the Web Services Addressing specification.
		</p>
	    </div2>

            <div2 id="notation">
                <head>Notational Conventions</head>
                <p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
                    "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
                    interpreted as described in RFC 2119 [<bibref ref="RFC2119"/>].</p>
                <p>When describing abstract data models, this specification uses the notational
                    convention used by the XML Infoset [<bibref ref="XMLInfoSet"/>]. Specifically,
                    abstract property names always appear in square brackets (e.g., [some
                    property]).</p>
                <p>When describing concrete XML schemas [<bibref ref="XMLSchemaP1"/>, <bibref
                        ref="XMLSchemaP2"/>], this specification uses the notational convention of
                    WS-Security [<bibref ref="WS-Security"/>]. Specifically, each member of an
                    element's [children] or [attributes] property is described using an XPath-like
                    notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates
                    the presence of an element wildcard (&lt;xs:any/&gt;). The use of @{any}
                    indicates the presence of an attribute wildcard
                    (&lt;xs:anyAttribute/&gt;).</p>
            </div2>
            <div2 id="namespaces">
                <head>Namespaces</head>
                <p> This specification uses a number of namespace prefixes throughout; they are
                    listed in <specref ref="nsprefix"/>. Note that the choice of any namespace
                    prefix is arbitrary and not semantically significant (see [<bibref ref="XMLNS"/>
                    ]).</p>
                <table summary="Namespace prefixes usage in this specification" id="nsprefix"
                    border="1">
                    <caption>Prefixes and Namespaces used in this specification</caption>
                    <tbody>
                        <tr>
                            <th align="left">Prefix</th>
                            <th align="left">Namespace</th>
                        </tr>
                        <tr>
                            <td>S</td>
                            <td>http://www.w3.org/2003/05/soap-envelope</td>
                        </tr>
                        <tr>
                            <td>S11</td>
                            <td>http://schemas.xmlsoap.org/soap/envelope</td>
                        </tr>
                        <tr>
                            <td>wsa</td>
                            <td>&nsuri;</td>
                        </tr>
                        <tr>
                            <td>xs</td>
                            <td>http://www.w3.org/2001/XMLSchema</td>
                        </tr>
                    </tbody>
                </table>
                <p>WS-Addressing may be used with SOAP [<bibref ref="SOAP12-PART1"/>] as described
                    in &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]. WS-Addressing may be used
                    with WSDL [<bibref ref="WSDL20"/>] described services as described in
                        &wsa-wsdl.title;[<bibref ref="WSADDR-WSDL"/>]. Examples in this
                    specification use an XML 1.0 [<bibref ref="XML10"/>] representation but this is
                    not a requirement.</p>
                <p>All information items defined by this specification are identified by the XML
                    namespace URI [<bibref ref="XMLNS"/>] "&nsuri;". A normative XML Schema
                        [<bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>] document can be
                    obtained by dereferencing the XML namespace URI.</p>
            </div2>
        </div1>

        <div1 id="testScenarios">
            <head>Test Scenarios</head>

            <div2 id="messagePassingScenarios">
                <head>Message Passing Scenarios</head>

            <div3 id="OneWayScenarios">
                <head>One Way Binding</head>
		<p>Message passing scenarios using an underlying protocol to exchange
		 messages which has no natural return path for messages, e.g. UDP.
		</p>

<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inonly.png?rev=1.1&amp;content-type=image/png"/>
<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-robustinonly.png?rev=1.1&amp;content-type=image/png"/>
<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inout.png?rev=1.1&amp;content-type=image/png"/>
<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-outonly.png?rev=1.1&amp;content-type=image/png"/>

	    </div3>

            <div3 id="TwoWayScenarios">
                <head>Two Way Binding</head>
		<p>Message passing scenarios using an underlying protocol to exchange
		 messages which has a 'back-channel', e.g. HTTP.
		</p>

<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inonly.png?rev=1.1&amp;content-type=image/png"/>
<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-a.png?rev=1.1&amp;content-type=image/png"/>
<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-b.png?rev=1.1&amp;content-type=image/png"/>
<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-a.png?rev=1.1&amp;content-type=image/png"/>
<graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-b.png?rev=1.1&amp;content-type=image/png"/>

		    <ednote>
			<name>P Downey</name>
			<edtext>
			 Scenarios taken from a whiteboard discussion
			 of the Async Task Force, 18-4-2005.
			</edtext>
		    </ednote>
	    </div3>
	    </div2>

            <div2 id="otherScenarios">
                <head>Other Scenarios</head>

		    <ednote>
			<name>P Downey</name>
			<edtext>
			 There may be other types of scenario we would use to 
			 catalogue tests, such as "security", which may be used in conjuction
			 with the message passing scenarios.
			</edtext>
		    </ednote>
	    </div2>

        </div1>

        <div1 id="testAssertions">
            <head>Test Assertions</head>
		    <p>
		    Assertions to be defined in a separate assertions document.
		    </p>
		    <ednote>
			<name>P Downey</name>
			<edtext>
			The SOAP 1.2 assertions document made it to Recommended.
			Should we afford our assertion document the  same status
			given it is likely to remain stable with the specfication?
			</edtext>
		    </ednote>
        </div1>

        <div1 id="testCases">
            <head>Test Cases</head>

		    <ednote>
			<name>P Downey</name>
			<edtext>
			The test cases from the Microsoft submitted
			scenarios reference a version of WS-Addressing.
		        dated 2004/03 and possibly not the Member Submission.
			Is this an issue from the IP perspective?
			</edtext>
		    </ednote>
        </div1>

        <div1 id="testDocuments">
            <head>Test Documents</head>

		    <ednote>
			<name>P Downey</name>
			<edtext>
			Test from the Microsoft submitted
			scenarios reference a version of WS-Addressing.
		        dated 2004/03 and possibly not the Member Submission.
			Is this an issue from the IP perspective?
			</edtext>
		    </ednote>
        </div1>

        <div1 id="references">
            <head>References</head>
            <blist>
                <bibl key="WS-Addressing-Core" id="WSADDR-CORE"
                    href="&w3c-designation-wsa-core;">
                    <titleref>&wsa-core.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
                <bibl key="WS-Addressing-SOAP" id="WSADDR-SOAP"
                    href="&w3c-designation-wsa-soap;">
                    <titleref>&wsa-soap.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
                <bibl key="WS-Addressing-WSDL" id="WSADDR-WSDL"
                    href="&w3c-designation-wsa-wsdl;">
                    <titleref>&wsa-wsdl.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
                <bibl key="WSDL 2.0" id="WSDL20" href="http://www.w3.org/TR/2004/WD-wsdl20-20040803">
                    <titleref>Web Services Description Language 2.0</titleref>, R. Chinnici, M.
                    Gudgin, J. J. Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web
                    Consortium, 3 August 2004. This version of the WSDL 2.0 specification is
                    http://www.w3.org/TR/2004/WD-wsdl20-20040803. The <loc
                        href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</loc> is
                    available at http://www.w3.org/TR/wsdl20.</bibl>

                <bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
                    <titleref>Key words for use in RFCs to Indicate Requirement Levels</titleref>,
                    S. Bradner. Internet Engineering Task Force, June 1999. Available at
                    http://www.ietf.org/rfc/rfc2119.txt. </bibl>
                <bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt"> M.
                    Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)", January
                    2005.</bibl>

                <bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204">
                    <titleref>Extensible Markup Language (XML) 1.0 (Third Edition)</titleref>, T.
                    Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
                    Consortium, 4 February 2004. This version of the XML
                    1.0 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The <loc
                        href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</loc> is
                    available at http://www.w3.org/TR/REC-xml. </bibl>
                <bibl id="XMLNS" key="XML Namespaces"
                    href="http://www.w3.org/TR/1999/REC-xml-names-19990114">
                    <titleref>Namespaces in XML</titleref>, T. Bray, D. Hollander, and A. Layman,
                    Editors. World Wide Web Consortium, 14 January 1999. This version of the XML
                    Information Set Recommendation is
                    http://www.w3.org/TR/1999/REC-xml-names-19990114. The <loc
                        href="http://www.w3.org/TR/REC-xml-names">latest version of Namespaces in
                        XML</loc> is available at http://www.w3.org/TR/REC-xml-names. </bibl>
                <bibl id="XMLInfoSet" key="XML Information Set"
                    href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024">
                    <titleref>XML Information Set</titleref>, J. Cowan and R. Tobin, Editors. World
                    Wide Web Consortium, 24 October 2001. This version of the XML Information Set
                    Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The <loc
                        href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
                        Set</loc> is available at http://www.w3.org/TR/xml-infoset. </bibl>

                <bibl id="XMLSchemaP1" key="XML Schema Structures"
                    href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
                    <titleref>XML Schema Part 1: Structures Second Edition</titleref>, H. Thompson, D. Beech, M.
                    Maloney, and N. Mendelsohn, Editors. World Wide
		    Web Consortium, 28 October 2004. This
                    version of the XML Schema Part 1 Recommendation is
                    http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc
                        href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
                    1</loc> is available at http://www.w3.org/TR/xmlschema-1. </bibl>
                <bibl key="XML Schema Datatypes" id="XMLSchemaP2"
                    href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
                    <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron and A. Malhotra,
                    Editors. World Wide Web Consortium, 28 October 2004. This version of the XML Schema
                    Part 2 Recommendation is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The
                        <loc href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
                        Part 2</loc> is available at http://www.w3.org/TR/xmlschema-2. </bibl>
                <bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework"
                    href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
                    <titleref>SOAP Version 1.2 Part 1: Messaging Framework</titleref>, M. Gudgin, M.
                    Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web
                    Consortium, 24 June 2003. This version of the "SOAP Version 1.2 Part 1:
                    Messaging Framework" Recommendation is
                    http://www.w3.org/TR/2003/REC-soap12-part1-20030624/. The <loc
                        href="http://www.w3.org/TR/soap12-part1/">latest version of "SOAP Version
                        1.2 Part 1: Messaging Framework"</loc> is available at
                    http://www.w3.org/TR/soap12-part1/. </bibl>
                <bibl id="WS-Security" key="WS-Security"
                    href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"
                    > OASIS, <titleref>Web Services Security: SOAP Message Security</titleref>,
                    March 2004.</bibl>
            </blist>
        </div1>
    </body>
    <back> &acknowledgements; <inform-div1 id="changelog">
            <head>Change Log</head>
        </inform-div1>
    </back>
</spec>

--- NEW FILE: ws-addr-testsuite.html ---
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang=
"en-US">
<head>
<meta name="generator" content=
"HTML Tidy for Mac OS X (vers 12 April 2005), see www.w3.org" />
<meta http-equiv="Content-Type" content=
"text/html; charset=utf-8" />
<title>Web Services Addressing 1.0 - Test Suite</title>

<style type="text/css">
/*<![CDATA[*/
code           { font-family: monospace; }

div.constraint,
div.issue,
div.note,
div.notice     { margin-left: 2em; }

dt.label       { display: run-in; }

li, p           { margin-top: 0.3em;
                 margin-bottom: 0.3em; }

.diff-chg       { background-color: yellow; }
.diff-del       { background-color: red; text-decoration: line-through;}
.diff-add       { background-color: lime; }

table          { empty-cells: show; }

table caption {
        font-weight: normal;
        font-style: italic;
        text-align: left;
        margin-bottom: .5em;
}

div.issue {
  color: red;
}

div.exampleInner pre { margin-left: 1em;
                       margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
                  margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
                   border-top-width: 4px;
                   border-top-style: double;
                   border-top-color: #d3d3d3;
                   border-bottom-width: 4px;
                   border-bottom-style: double;
                   border-bottom-color: #d3d3d3;
                   padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
                    margin: 4px}
/*]]>*/
</style>
<link rel="stylesheet" type="text/css" href=
"http://www.w3.org/StyleSheets/TR/base.css" />
<link rel="alternate" title="" href="" type="" />
<link rel="contents" href="#contents" />
</head>
<body>
<div class="head">
<h1>Web Services Addressing 1.0 - Test Suite</h1>
<h2>Editors' copy $Date: 2005/04/20 21:42:58 $ @@ @@@@ @@@@</h2>
<dl>
<dt>This version:</dt>
<dd><a href="ws-addr-wsdl.html">ws-addr-wsdl.html</a></dd>
<dt>Latest version:</dt>
<dd><a href=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl">
http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl</a></dd>
<dt>Previous versions:</dt>
<dd><a href=""></a></dd>
<dt>Editor:</dt>
<dd>Paul Downey, BT</dd>
</dl>
<p>This document is also available in these non-normative formats:
<a href=""></a>.</p>
<p class="copyright"><a href=
"http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup>
(<a href="http://www.csail.mit.edu/"><acronym title=
"Massachusetts Institute of Technology">MIT</acronym></a>, <a href=
"http://www.ercim.org/"><acronym title=
"European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
W3C <a href=
"http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href=
"http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
and <a href=
"http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> rules apply.</p>
</div>
<hr />
<div>
<h2><a name="abstract" id="abstract">Abstract</a></h2>
<p>This document describes the Test Suite deliverable for the
<a href="http://www.w3.org/2002/ws/addr/">Web Services Addressing
Working Group</a> as defined by the Working Group's <a href=
"http://www.w3.org/2004/09/wsa-charter.html">Charter</a>.</p>
</div>
<div>
<h2><a name="status" id="status">Status of this Document</a></h2>
<p><strong>This document is an editors' copy that has no official
standing.</strong></p>
</div>
<hr />
<div class="toc">
<h2><a name="contents" id="contents">Table of Contents</a></h2>
<p class="toc">1. <a href="#tocRange">Introduction</a><br />
&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#conformance">Conformance
Claims</a><br />
&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#notation">Notational
Conventions</a><br />
&nbsp;&nbsp;&nbsp;&nbsp;1.3 <a href=
"#namespaces">Namespaces</a><br />
2. <a href="#testScenarios">Test Scenarios</a><br />
&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href=
"#messagePassingScenarios">Message Passing Scenarios</a><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.1 <a href=
"#OneWayScenarios">One Way Binding</a><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2 <a href=
"#TwoWayScenarios">Two Way Binding</a><br />
&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#otherScenarios">Other
Scenarios</a><br />
3. <a href="#testAssertions">Test Assertions</a><br />
4. <a href="#testCases">Test Cases</a><br />
5. <a href="#testDocuments">Test Documents</a><br />
6. <a href="#references">References</a><br /></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3>
<p class="toc">A. <a href="#acknowledgments">Acknowledgements</a>
(Non-Normative)<br />
B. <a href="#changelog">Change Log</a> (Non-Normative)<br /></p>
</div>
<hr />
<div class="body">
<div class="div1">
<h2><a name="tocRange" id="tocRange"></a>1. Introduction</h2>
<p>One of the deliverables specified in the Charter of the Web
Services Addressing Working Group is <em>a test suite intended to
promote implementation of the Candidate Recommendation, and to
assess interoperability between these implementations.</em></p>
<p>The Working Group Charter also states that <em>the Working Group
is expected to demonstrate four interoperable implementations
during the Call for Implementations step.</em> It is anticipated
that some, but not all of the test cases held within the test suite
will be used to practially test implementations during an
interoperability Workshop and thereby satisfy the entrance criteria
for the Web Service Addressing specifications to enter the <a href=
"http://www.w3.org/Consortium/Process-20010719/tr.html#RecsPR">Proposed
Recommendation stage</a>.</p>
<p>The test suite will be maintained by the Working Group and
remain available for regression testing beyond publication of the
Web Addressing Recommendation, however it is not expected that the
test suite will form a part of the Web Addressing Recommendation;
the status of this document will remain as a Working Group
note.</p>
<div class="div2">
<h3><a name="conformance" id="conformance"></a>1.1 Conformance
Claims</h3>
<p>A Web Services Addressing implementation that passes all of the
tests specified in this document may claim conformance to the Web
Services Addressing Test Suite $Date: 2005/04/20 21:42:58 $.</p>
<p>Conformance to the Web services Addressing Test Suite does not
by itself enable a party to claim conformance with the Web Services
Addressing specification. Not passing an individual test may be
used as an indication that an implementation is likely not to
conform to the Web Services Addressing specification.</p>
</div>
<div class="div2">
<h3><a name="notation" id="notation"></a>1.2 Notational
Conventions</h3>
<p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in RFC 2119
[<cite><a href="#RFC2119">IETF RFC 2119</a></cite>].</p>
<p>When describing abstract data models, this specification uses
the notational convention used by the XML Infoset [<cite><a href=
"#XMLInfoSet">XML Information Set</a></cite>]. Specifically,
abstract property names always appear in square brackets (e.g.,
[some property]).</p>
<p>When describing concrete XML schemas [<cite><a href=
"#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href=
"#XMLSchemaP2">XML Schema Datatypes</a></cite>], this specification
uses the notational convention of WS-Security [<cite><a href=
"#WS-Security">WS-Security</a></cite>]. Specifically, each member
of an element's [children] or [attributes] property is described
using an XPath-like notation (e.g.,
/x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates the
presence of an element wildcard (&lt;xs:any/&gt;). The use of
@{any} indicates the presence of an attribute wildcard
(&lt;xs:anyAttribute/&gt;).</p>
</div>
<div class="div2">
<h3><a name="namespaces" id="namespaces"></a>1.3 Namespaces</h3>
<p>This specification uses a number of namespace prefixes
throughout; they are listed in <a href="#nsprefix">Table 1-1</a>.
Note that the choice of any namespace prefix is arbitrary and not
semantically significant (see [<cite><a href="#XMLNS">XML
Namespaces</a></cite> ]).</p>
<a name="nsprefix" id="nsprefix"></a>
<table summary="Namespace prefixes usage in this specification"
border="1">
<caption>Table 1-1. Prefixes and Namespaces used in this
specification</caption>
<tbody>
<tr>
<th align="left" rowspan="1" colspan="1">Prefix</th>
<th align="left" rowspan="1" colspan="1">Namespace</th>
</tr>
<tr>
<td rowspan="1" colspan="1">S</td>
<td rowspan="1" colspan="1">
http://www.w3.org/2003/05/soap-envelope</td>
</tr>
<tr>
<td rowspan="1" colspan="1">S11</td>
<td rowspan="1" colspan="1">
http://schemas.xmlsoap.org/soap/envelope</td>
</tr>
<tr>
<td rowspan="1" colspan="1">wsa</td>
<td rowspan="1" colspan="1">
http://www.w3.org/@@@@/@@/addressing</td>
</tr>
<tr>
<td rowspan="1" colspan="1">xs</td>
<td rowspan="1" colspan="1">http://www.w3.org/2001/XMLSchema</td>
</tr>
</tbody>
</table>
<br />
<p>WS-Addressing may be used with SOAP [<cite><a href=
"#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>] as
described in Web Services Addressing 1.0 - SOAP
Binding[<cite><a href=
"#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. WS-Addressing may be
used with WSDL [<cite><a href="#WSDL20">WSDL 2.0</a></cite>]
described services as described in Web Services Addressing 1.0 -
WSDL Binding[<cite><a href=
"#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>]. Examples in this
specification use an XML 1.0 [<cite><a href="#XML10">XML
1.0</a></cite>] representation but this is not a requirement.</p>
<p>All information items defined by this specification are
identified by the XML namespace URI [<cite><a href="#XMLNS">XML
Namespaces</a></cite>] "http://www.w3.org/@@@@/@@/addressing". A
normative XML Schema [<cite><a href="#XMLSchemaP1">XML Schema
Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema
Datatypes</a></cite>] document can be obtained by dereferencing the
XML namespace URI.</p>
</div>
</div>
<div class="div1">
<h2><a name="testScenarios" id="testScenarios"></a>2. Test
Scenarios</h2>
<div class="div2">
<h3><a name="messagePassingScenarios" id=
"messagePassingScenarios"></a>2.1 Message Passing Scenarios</h3>
<div class="div3">
<h4><a name="OneWayScenarios" id="OneWayScenarios"></a>2.1.1 One
Way Binding</h4>
<p>Message passing scenarios using an underlying protocol to
exchange messages which has no natural return path for messages,
e.g. UDP.</p>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inonly.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-1.</span></i></p>
<br /></div>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-robustinonly.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-2.</span></i></p>
<br /></div>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inout.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-3.</span></i></p>
<br /></div>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-outonly.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-4.</span></i></p>
<br /></div>
</div>
<div class="div3">
<h4><a name="TwoWayScenarios" id="TwoWayScenarios"></a>2.1.2 Two
Way Binding</h4>
<p>Message passing scenarios using an underlying protocol to
exchange messages which has a 'back-channel', e.g. HTTP.</p>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inonly.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-5.</span></i></p>
<br /></div>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-a.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-6.</span></i></p>
<br /></div>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-b.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-7.</span></i></p>
<br /></div>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-a.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-8.</span></i></p>
<br /></div>
<div class="figure" style="text-align: center"><br />
<img src=
"http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-b.png?rev=1.1&amp;content-type=image/png" />
<p style="text-align:left"><i><span>Figure 2-9.</span></i></p>
<br /></div>
<table border="1" summary="Editorial note: P Downey">
<tr>
<td align="left" valign="top" width="50%"><b>Editorial note: P
Downey</b></td>
<td align="right" valign="top" width="50%">&nbsp;</td>
</tr>
<tr>
<td colspan="2" align="left" valign="top">Scenarios taken from a
whiteboard discussion of the Async Task Force, 18-4-2005.</td>
</tr>
</table>
</div>
</div>
<div class="div2">
<h3><a name="otherScenarios" id="otherScenarios"></a>2.2 Other
Scenarios</h3>
<table border="1" summary="Editorial note: P Downey">
<tr>
<td align="left" valign="top" width="50%"><b>Editorial note: P
Downey</b></td>
<td align="right" valign="top" width="50%">&nbsp;</td>
</tr>
<tr>
<td colspan="2" align="left" valign="top">There may be other types
of scenario we would use to catalogue tests, such as "security",
which may be used in conjuction with the message passing
scenarios.</td>
</tr>
</table>
</div>
</div>
<div class="div1">
<h2><a name="testAssertions" id="testAssertions"></a>3. Test
Assertions</h2>
<p>Assertions to be defined in a separate assertions document.</p>
<table border="1" summary="Editorial note: P Downey">
<tr>
<td align="left" valign="top" width="50%"><b>Editorial note: P
Downey</b></td>
<td align="right" valign="top" width="50%">&nbsp;</td>
</tr>
<tr>
<td colspan="2" align="left" valign="top">The SOAP 1.2 assertions
document made it to Recommended. Should we afford our assertion
document the same status given it is likely to remain stable with
the specfication?</td>
</tr>
</table>
</div>
<div class="div1">
<h2><a name="testCases" id="testCases"></a>4. Test Cases</h2>
<table border="1" summary="Editorial note: P Downey">
<tr>
<td align="left" valign="top" width="50%"><b>Editorial note: P
Downey</b></td>
<td align="right" valign="top" width="50%">&nbsp;</td>
</tr>
<tr>
<td colspan="2" align="left" valign="top">The test cases from the
Microsoft submitted scenarios reference a version of WS-Addressing.
dated 2004/03 and possibly not the Member Submission. Is this an
issue from the IP perspective?</td>
</tr>
</table>
</div>
<div class="div1">
<h2><a name="testDocuments" id="testDocuments"></a>5. Test
Documents</h2>
<table border="1" summary="Editorial note: P Downey">
<tr>
<td align="left" valign="top" width="50%"><b>Editorial note: P
Downey</b></td>
<td align="right" valign="top" width="50%">&nbsp;</td>
</tr>
<tr>
<td colspan="2" align="left" valign="top">Test from the Microsoft
submitted scenarios reference a version of WS-Addressing. dated
2004/03 and possibly not the Member Submission. Is this an issue
from the IP perspective?</td>
</tr>
</table>
</div>
<div class="div1">
<h2><a name="references" id="references"></a>6. References</h2>
<dl>
<dt class="label"><a name="WSADDR-CORE" id=
"WSADDR-CORE"></a>[WS-Addressing-Core]</dt>
<dd><cite><a href="ws-addr-core.html">Web Services Addressing 1.0 -
Core</a></cite>, M. Gudgin, M. Hadley, Editors.</dd>
<dt class="label"><a name="WSADDR-SOAP" id=
"WSADDR-SOAP"></a>[WS-Addressing-SOAP]</dt>
<dd><cite><a href="ws-addr-soap.html">Web Services Addressing 1.0 -
SOAP Binding</a></cite>, M. Gudgin, M. Hadley, Editors.</dd>
<dt class="label"><a name="WSADDR-WSDL" id=
"WSADDR-WSDL"></a>[WS-Addressing-WSDL]</dt>
<dd><cite><a href="ws-addr-wsdl.html">Web Services Addressing 1.0 -
WSDL Binding</a></cite>, M. Gudgin, M. Hadley, Editors.</dd>
<dt class="label"><a name="WSDL20" id="WSDL20"></a>[WSDL 2.0]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2004/WD-wsdl20-20040803">Web Services
Description Language 2.0</a></cite>, R. Chinnici, M. Gudgin, J. J.
Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web
Consortium, 3 August 2004. This version of the WSDL 2.0
specification is http://www.w3.org/TR/2004/WD-wsdl20-20040803. The
<a href="http://www.w3.org/TR/wsdl20">latest version of WSDL
2.0</a> is available at http://www.w3.org/TR/wsdl20.</dd>
<dt class="label"><a name="RFC2119" id="RFC2119"></a>[IETF RFC
2119]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
Bradner. Internet Engineering Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC3987" id="RFC3987"></a>[IETF RFC
3987]</dt>
<dd>M. Duerst, M. Suignard, "Internationalized Resource Identifiers
(IRIs)", January 2005. (See <cite><a href=
"http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a></cite>.)</dd>
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup
Language (XML) 1.0 (Third Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
Consortium, 4 February 2004. This version of the XML 1.0
Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The
<a href="http://www.w3.org/TR/REC-xml">latest version of XML
1.0</a> is available at http://www.w3.org/TR/REC-xml.</dd>
<dt class="label"><a name="XMLNS" id="XMLNS"></a>[XML
Namespaces]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in
XML</a></cite>, T. Bray, D. Hollander, and A. Layman, Editors.
World Wide Web Consortium, 14 January 1999. This version of the XML
Information Set Recommendation is
http://www.w3.org/TR/1999/REC-xml-names-19990114. The <a href=
"http://www.w3.org/TR/REC-xml-names">latest version of Namespaces
in XML</a> is available at http://www.w3.org/TR/REC-xml-names.</dd>
<dt class="label"><a name="XMLInfoSet" id="XMLInfoSet"></a>[XML
Information Set]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2001/REC-xml-infoset-20011024">XML
Information Set</a></cite>, J. Cowan and R. Tobin, Editors. World
Wide Web Consortium, 24 October 2001. This version of the XML
Information Set Recommendation is
http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The <a href=
"http://www.w3.org/TR/xml-infoset">latest version of XML
Information Set</a> is available at
http://www.w3.org/TR/xml-infoset.</dd>
<dt class="label"><a name="XMLSchemaP1" id="XMLSchemaP1"></a>[XML
Schema Structures]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema
Part 1: Structures Second Edition</a></cite>, H. Thompson, D.
Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web
Consortium, 28 October 2004. This version of the XML Schema Part 1
Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema
Part 1</a> is available at http://www.w3.org/TR/xmlschema-1.</dd>
<dt class="label"><a name="XMLSchemaP2" id="XMLSchemaP2"></a>[XML
Schema Datatypes]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema
Part 2: Datatypes Second Edition</a></cite>, P. Byron and A.
Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This
version of the XML Schema Part 2 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
Part 2</a> is available at http://www.w3.org/TR/xmlschema-2.</dd>
<dt class="label"><a name="SOAP12-PART1" id=
"SOAP12-PART1"></a>[SOAP 1.2 Part 1: Messaging Framework]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">SOAP Version
1.2 Part 1: Messaging Framework</a></cite>, M. Gudgin, M. Hadley,
N. Mendelsohn, J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide
Web Consortium, 24 June 2003. This version of the "SOAP Version 1.2
Part 1: Messaging Framework" Recommendation is
http://www.w3.org/TR/2003/REC-soap12-part1-20030624/. The <a href=
"http://www.w3.org/TR/soap12-part1/">latest version of "SOAP
Version 1.2 Part 1: Messaging Framework"</a> is available at
http://www.w3.org/TR/soap12-part1/.</dd>
<dt class="label"><a name="WS-Security" id=
"WS-Security"></a>[WS-Security]</dt>
<dd>OASIS, <cite><a href=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">
Web Services Security: SOAP Message Security</a></cite>, March
2004.</dd>
</dl>
</div>
</div>
<div class="back">
<div class="div1">
<h2><a name="acknowledgments" id="acknowledgments"></a>A.
Acknowledgements (Non-Normative)</h2>
<p>This document is the work of the <a href=
"http://www.w3.org/2002/ws/addr/">W3C Web Service Addressing
Working Group</a>.</p>
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order): Abbie Barbir (Nortel Networks), Rebecca
Bergersen (IONA Technologies, Inc.), Andreas Bjärlestam (ERICSSON),
Ugo Corda (SeeBeyond Technology Corporation), Francisco Curbera
(IBM Corporation), Glen Daniels (Sonic Software), Paul Downey (BT),
Jacques Durand (Fujitsu Limited), Michael Eder (Nokia), Robert
Freund (Hitachi, Ltd.), Yaron Goland (BEA Systems, Inc.), Martin
Gudgin (Microsoft Corporation), Arun Gupta (Sun Microsystems,
Inc.), Hugo Haas (W3C/ERCIM), Marc Hadley (Sun Microsystems, Inc.),
David Hull (TIBCO Software, Inc.), Yin-Leng Husband (HP), Anish
Karmarkar (Oracle Corporation), Paul Knight (Nortel Networks),
Philippe Le Hégaret (W3C/MIT), Mark Little (Arjuna Technologies
Ltd.), Jonathan Marsh (Microsoft Corporation), Jeff Mischkinsky
(Oracle Corporation), Nilo Mitra (ERICSSON), Eisaku Nishiyama
(Hitachi, Ltd.), Mark Nottingham (BEA Systems, Inc.), Ales Novy
(Systinet Inc.), David Orchard (BEA Systems, Inc.), Mark Peel
(Novell, Inc.), Tony Rogers (Computer Associates), Tom Rutt
(Fujitsu Limited), Rich Salz (DataPower Technology, Inc.), Davanum
Srinivas (Computer Associates), Jiri Tejkl (Systinet Inc.), Greg
Truty (IBM Corporation), Steve Vinoski (IONA Technologies, Inc.),
Pete Wenzel (SeeBeyond Technology Corporation), Steve Winkler (SAP
AG), Ümit Yalçınalp (SAP AG), Prasad Yendluri (webMethods,
Inc.).</p>
<p>Previous members of the Working Group were: Lisa Bahler (SAIC -
Telcordia Technologies), Marc Goodner (SAP AG), Harris Reynolds
(webMethods, Inc.).</p>
<p>The people who have contributed to <a href=
"http://lists.w3.org/Archives/Public/public-ws-addressing/">discussions
on public-ws-addressing@w3.org</a> are also gratefully
acknowledged.</p>
</div>
<div class="div1">
<h2><a name="changelog" id="changelog"></a>B. Change Log
(Non-Normative)</h2>
</div>
</div>
</body>
</html>

Index: entities.dtd
===================================================================
RCS file: /sources/public/2004/ws/addressing/entities.dtd,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** entities.dtd	10 Feb 2005 11:09:24 -0000	1.6
--- entities.dtd	20 Apr 2005 21:42:58 -0000	1.7
***************
*** 16,19 ****
--- 16,20 ----
  <!ENTITY wsa-soap.title "Web Services Addressing 1.0 - SOAP Binding">
  <!ENTITY wsa-wsdl.title "Web Services Addressing 1.0 - WSDL Binding">
+ <!ENTITY wsa-testsuite.title "Web Services Addressing 1.0 - Test Suite">
  
  <!-- Latest version links. don't touch -->
***************
*** 21,24 ****
--- 22,26 ----
  <!ENTITY wsa-soap.latest "&w3c.tr.latest;/&wsa-soap.prefix;">
  <!ENTITY wsa-wsdl.latest "&w3c.tr.latest;/&wsa-wsdl.prefix;">
+ <!ENTITY wsa-testsuite.latest "&w3c.tr.latest;/&wsa-testsuite.prefix;">
  
  <!-- XML Namespaces used in the drafts -->
Received on Wednesday, 20 April 2005 21:43:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:40 GMT