See also: IRC log
<trackbot> Date: 24 February 2009
<scribe> Scribe:peaston
<Roland> http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0019.html
<scribe> Chair:Roland
<Roland> http://www.w3.org/2002/ws/soapjms/tracker/actions/open
<Derek> http://dev.w3.org/2008/ws/soapjms/testcases/
<Roland> http://dev.w3.org/2008/ws/soapjms/testcases/assertions/assertions.html
Close: Action-53
close action-53
<trackbot> ACTION-53 Provide testcase(s) in properties area closed
<Roland> http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0017.html
<Roland> http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0020.html
phil: this is a corner case perhaps not specify
<Phil> I think that was eric, not phil :)
: Re:ACTION-62 Make a proposal to clarify the wording and scope of the (221) jndiContext Parameter property)
: Re:ACTION-62 Make a proposal to clarify the wording and scope of the (221) jndiContext Parameter property)
this is a corner case perhaps not specify
roland: we should specify the
jndi case
... if you use jndi ignore topicReplyTo
<Roland> Dongbo question: http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0008.html
eric: hesitant to add topicReplyTo to wsdl
derek: could we just use it in
the URI
... could have a reply to type
eric: do we have a conflict if
wsdl and URI are inconsistent
... we could leave this in the URI spec
roland: what about error conditions
mphillips: just take the first one in the URI is there are conflicts
eric: there are a bunch of error cases
derek: make statements about what is ignored versus errors if the URI has conflicting R2 specs
<scribe> ACTION: derek to redraft words re replyTo and topicReplyTO [recorded in http://www.w3.org/2009/02/24-soap-jms-minutes.html#action01]
<trackbot> Created ACTION-67 - Redraft words re replyTo and topicReplyTO [on Derek Rokicki - due 2009-03-03].
<Roland> http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0022.html
roland the security principal may be contraversial otherwise ok
peter will pick another property
<Roland> http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0018.html
<Roland> http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0021.html
amy: Robust In-Only designed with JMS in mind
I muted
roland: we could fully specify it or specify it as other meps like RIO are not prohibited
eric: or do nothing note that we have to consider security concerns of NOT being rebust
amy roland etc: additional MEPS allowable is good
roland: do we state this in the spec i.e. other MEPS ok
derek: if we don't define RIO fully could be interpop issues
eric: is RIO a SOAP MEP ? should check
amy: SOAP WG only defined
SOAP/HTTP perhaps SOAP/email
... RIO is being implemented getting traction
roland: this is a significant
addition i.e. time spec tests etc
... adding an MEP may reset the W3C process
phil: what about next rev
eric: how about a non-normative
appendix ?
... RIO has JMS QOS implications
... non-normative section(appendix) would be a step in the
right direction
roland: Q1 do we want a normative section ?
all: no
roland: any volunteers for a non-normative section ?
all: generally restrained response
<scribe> ACTION: derek to draft words on what you can do with non-normative MEPs like RIO [recorded in http://www.w3.org/2009/02/24-soap-jms-minutes.html#action02]
<trackbot> Created ACTION-68 - Draft words on what you can do with non-normative MEPs like RIO [on Derek Rokicki - due 2009-03-03].
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 Scribe: peaston Inferring ScribeNick: peaston Default Present: alewis, Roland, +1.708.246.aaaa, Phil, Derek, peaston, eric, mphillip Present: alewis Roland +1.708.246.aaaa Phil Derek peaston eric mphillip Agenda: http://lists.w3.org/Archives/Public/public-soap-jms/2009Feb/0019.html Found Date: 24 Feb 2009 Guessing minutes URL: http://www.w3.org/2009/02/24-soap-jms-minutes.html People with action items: derek WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]