W3C home > Mailing lists > Public > public-ws-addressing-tests@w3.org > March 2006

RE: Next Steps

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 27 Mar 2006 12:17:03 -0800
Message-ID: <37D0366A39A9044286B2783EB4C3C4E8020A823C@RED-MSG-10.redmond.corp.microsoft.com>
To: <paul.downey@bt.com>, <gdaniels@sonicsoftware.com>
Cc: <public-ws-addressing-tests@w3.org>

What's the difference between status="REQUIRED" and cr="REQUIRED"?

> -----Original Message-----
> From: public-ws-addressing-tests-request@w3.org [mailto:public-ws-
> addressing-tests-request@w3.org] On Behalf Of paul.downey@bt.com
> Sent: Wednesday, March 22, 2006 1:04 PM
> To: gdaniels@sonicsoftware.com
> Cc: public-ws-addressing-tests@w3.org
> Subject: Next Steps
> 
> 
> I've been thinking about Glen's concern about REQUIRED|OPTIONAL|
> INFORMATIONAL wrt the testsuite.
> 
> Now the testsuite has done its job and helped demonstrate
> interoperability of the CR versions of the Core and SOAP binding
> specifications, and we have a snapshot of the CR report,
> I suggest adding a new attribute to each testcase,
> 
>    status='REQUIRED|OPTIONAL|INFORMATIONAL'
> 
> to indicate if the testcase exhibits a required, optional
> or informational feature, irrespective of our 'CR' report.
> 
> I guess we could also contemplate continuing to accept new
> testcases if they were submitted in the form of a testcases.xml
> snippit and an example document and reused the notify and
> echo 'operations'. There would be no expectation that our
> existing endpoints would send such tests, but chances are
> they'd work with them if they fell within the remit of our
> PR specs.
> 
> And as for WSDL CR testing, well that's another story,
> and one probably layered upon the current suite, and something
> I have to confess to being mostly clueless about what
> it would demonstrate, exactly ;-)
> 
> Paul
> 
> 
Received on Monday, 27 March 2006 20:17:24 GMT

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