See also: IRC log
<trackbot> Date: 14 April 2009
<scribe> Scribe: mphillip
<Roland> trackbot, start telcon
<Yves> trackbot, start telcon
trackbot-ng, start telcon
trackbot, start telcon
<trackbot> Getting data for channel #soap-jms at http://www.w3.org/2002/ws/soapjms/tracker//api/users failed - alert sysreq of a possible bug
<trackbot> Meeting: SOAP-JMS Binding Working Group Teleconference
<trackbot> Date: 14 April 2009
Open actions: http://www.w3.org/2002/ws/soapjms/tracker/actions/open
<trackbot> Getting data for channel #soap-jms at http://www.w3.org/2002/ws/soapjms/tracker//api/users failed - alert sysreq of a possible bug
<trackbot> Meeting: SOAP-JMS Binding Working Group Teleconference
<trackbot> Date: 14 April 2009
<trackbot> Getting data for channel #soap-jms at http://www.w3.org/2002/ws/soapjms/tracker//api/users failed - alert sysreq of a possible bug
<trackbot> Meeting: SOAP-JMS Binding Working Group Teleconference
<trackbot> Date: 14 April 2009
<trackbot> Getting data for channel #soap-jms at http://www.w3.org/2002/ws/soapjms/tracker//api/users failed - alert sysreq of a possible bug
<trackbot> Meeting: SOAP-JMS Binding Working Group Teleconference
<trackbot> Date: 14 April 2009
Eric: no progress on Action
32
... (action 73) updating URI scheme
... Has responded to two comments from Harald and Mark Baker on
the IETF apps working group - waiting for confirmation from
Harald that are updates make sense
Roland: ...and Harald has responded
Eric: No comments from Harald on
jndi- prefix - suggest we make the change next week if we have
not heard
... Have comments on action 70 (Phil's contentType
changes)
... Roland has commented to the list on Eric's comments
Roland: Phil has submitted a proposal on the error if an implementation does not support a URI variant
http://lists.w3.org/Archives/Public/public-soap-jms/2009Apr/0014.html
Roland's comments: http://lists.w3.org/Archives/Public/public-soap-jms/2009Apr/0022.html
Phil: Proposes new fault subcode "unsupportedLookupVariant"
Roland: This is a new assertion & associated test case
Phil: There is an assertion to
say that the JNDI variant must be supported - but we need a new
one to test the fault. Phil will update the spec. with the
suggested changes, plus the fault in 2.8, and the assertion,
and we will review the changes next week
... Will update action 75 with this
Roland: Amy has made a proposal on the precedence rules and Roland has updated spec.
close action-77
<trackbot> ACTION-77 Clarify precedence of URI etc in WSDL 3.4.5 closed
Roland: Derek has completed action to Review the SOAP-JMS Binding spec to see if any changes are required for new jndi naming scheme
close action-79
<trackbot> ACTION-79 Review the SOAP-JMS Binding spec to see if any changes are required for new jndi naming scheme closed
<scribe> ACTION: Roland to update the spec. with jndi- prefix changes (when get confirmation from Harald) [recorded in http://www.w3.org/2009/04/14-soap-jms-minutes.html#action01]
<trackbot> Sorry, couldn't find user - Roland
<Roland> http://www.w3.org/2002/ws/soapjms/tracker/actions/pendingreview
Eric: Action 70 is closed
Roland: Agreed
close action-70
<trackbot> ACTION-70 Take another pass of the Content Type wording closed
Actions pending review
Roland: Has updated the spec.
with the changes to precedence rules
... Per action 80 - will check this with Dongbo to ensure it
addresses her last call comments
Phil: Happy with Eric's comments
on contentType, other than the 2 sentences which needed the
word "first"
... Has to leave the call
close action-80
<trackbot> ACTION-80 Remove point 3 (properties come from JMS URI) from section 2.2 closed
http://lists.w3.org/Archives/Public/public-soap-jms/2009Apr/0024.html
Eric: Walk through contentType changes referenced in email above
<eric> Note also that if the payload is formatted as a MIME multipart message, then the byte or character encountered in the JMS Message body MUST be the start of the MIME boundary for the start of the first part ? what MIME Part One [IETF RFC 2045] section 2.5 calls a "Body Part". Likewise, if the message is formatted as "text/xml" or "application/soap+xml", then the first byte or character of the JMS Message body MUST be the start of a conforming XML document.
<eric> Note also that if the payload is formatted as a MIME multipart message, then the first byte or character encountered in the JMS Message body MUST be the start of the MIME boundary for the start of the first part ? what MIME Part One [IETF RFC 2045] section 2.5 calls a "Body Part". Likewise, if the message is formatted as "text/xml" or "application/soap+xml", then the first byte or character of the JMS Message body MUST be the start of a conforming XML document.
Roland: What are the implications on examples?
Eric: Believe there are none
mphillip: Agreed
Roland: I'm happy with these changes
mphillip: +1
<scribe> ACTION: Roland to update the spec. with Phil and Eric's changes [recorded in http://www.w3.org/2009/04/14-soap-jms-minutes.html#action02]
<trackbot> Sorry, couldn't find user - Roland
<scribe> ACTION: Roland to update the spec. with jndi- prefix changes (when get confirmation from Harald) [recorded in http://www.w3.org/2009/04/14-soap-jms-minutes.html#action03]
<trackbot> Sorry, couldn't find user - Roland
<scribe> ACTION: Roland_Merrick to update the spec. with jndi- prefix changes (when get confirmation from Harald) [recorded in http://www.w3.org/2009/04/14-soap-jms-minutes.html#action04]
<trackbot> Sorry, couldn't find user - Roland_Merrick
<Yves> ACTION: rmerric to update the spec. with jndi- prefix changes (when get confirmation from Harald) [recorded in http://www.w3.org/2009/04/14-soap-jms-minutes.html#action05]
<trackbot> Sorry, couldn't find user - rmerric
mphillip: Will raise actions manually
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/undocumented action/action 73/ Found Scribe: mphillip Inferring ScribeNick: mphillip Default Present: +1.650.846.aaaa, +1.512.286.aabb, +962.7.0.aacc, +1.617.324.aadd, Yves, Roland, eric, mphillip Present: +1.650.846.aaaa +1.512.286.aabb +962.7.0.aacc +1.617.324.aadd Yves Roland eric mphillip Regrets: Derek Amy Peter Agenda: http://lists.w3.org/Archives/Public/public-soap-jms/2009Apr/0020.html Found Date: 14 Apr 2009 Guessing minutes URL: http://www.w3.org/2009/04/14-soap-jms-minutes.html People with action items: rmerric roland roland_merrick WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]