W3C

- DRAFT -

SOAP-JMS Binding Working Group Teleconference

22 Jul 2008

Agenda

See also: IRC log

Attendees

Present
alewis, Roland_Merrick, Phil, Eric, Derek, Yves, markphillips, GlenD
Regrets
Chair
Roland
Scribe
markphillips

Contents


 

 

<scribe> scribeNick: markphillips

Actions

Eric's action (clarifying what we mean by "MUST fully support the JMS IRI")

Eric: Looking at other URI schemes to see how this is handled

Mark's action to look at XML schema - still outstanding

<Yves> http://dev.w3.org/2008/ws/soapjms/soapjms.html#binding-properties

Roland's action to look at how we indicate normative and non-normative sections of the code

<Yves> http://dev.w3.org/2008/ws/soapjms/soapjms.html#binding-header-props

Roland: action still outstanding - but a code example is included in section 2.2.2 (see the link above)

<gdaniels> (hey folks, Glen joined a couple mins ago - sorry to be late!)

Eric: This draws a lot of attention to a non-normative section

Roland will try some different styles to simplify the presentation - possibly a sub-section which bounds the non-normative examples

(just for sections 2.2.2 and 2.2.3)

Testing

Phil: No testing strategy has been agreed yet

Glen: A test suite does not need to be a full SOAP stack - it can be build onto JMS

Eric: tests don't need to be code - could have written instructions - tests need to show interoperability

Glen: We need 2 interoperable implementations for every MUST constraint

Eric: Proposal: We need to identify test scenarios in textual form
... e.g. Outlined One-way and request-response message exchanges, and some WSDL

Roland: Need to also identify which assertions are addressed by these test scenarios

Glen: WS-Addressing test cases may provide a useful template

<gdaniels> http://www.w3.org/2002/ws/addr/testsuite/testcases/

<scribe> ACTION: Phil to write up one or two initial test scenarios - a one-way and request-response [recorded in http://www.w3.org/2008/07/22-soap-jms-minutes.html#action01]

<trackbot> Created ACTION-16 - Write up one or two initial test scenarios - a one-way and request-response [on Phil Adams - due 2008-07-29].

Glen: WS-Addressing template looks suitable. It uses XPath for the assertions - see http://www.w3.org/2002/ws/addr/testsuite/testcases/#test1238

Eric: For XPath to work we'd need a syntax to represent the JMS messages

Summary of Action Items

[NEW] ACTION: Phil to write up one or two initial test scenarios - a one-way and request-response [recorded in http://www.w3.org/2008/07/22-soap-jms-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2008/07/22 17:18:53 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: markphillips
Inferring Scribes: markphillips
Default Present: alewis, Roland_Merrick, Phil, Eric, Derek, Yves, markphillips, GlenD
Present: alewis Roland_Merrick Phil Eric Derek Yves markphillips GlenD
Agenda: http://lists.w3.org/Archives/Public/public-soap-jms/2008Jul/0014.html
Got date from IRC log name: 22 Jul 2008
Guessing minutes URL: http://www.w3.org/2008/07/22-soap-jms-minutes.html
People with action items: phil

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]