See also: IRC log
<trackbot> Date: 16 November 2010
<scribe> Scribe: Mark
http://www.w3.org/2010/11/09-soap-jms-minutes.html
Minutes are approved
Agenda accepted without modification
Eric: 224 - issue 66 has been
raised
... 226 Issue 65 has been raised
close action-224
<trackbot> ACTION-224 Raise issue on items 2 and 3 of Peter's testing action-219 closed
close action-226
<trackbot> ACTION-226 Open issue on EXI mail exchange closed
Derek: No progress on 222
Phil: No progress on 223 or 227
Peter: Still progressing 225
Eric: Any suggestions for moving this along?
Need to find time to test conformance for IBM WAS and/or Software AG
Other implementations...
Phil: Axis2 does not conform to SOAP/JMS at the moment
Eric: Should we open Issue 65 -
characterisation of EXI in payload?
... Raised by Jean-Baptiste Bugeaud who proposed declaring that
the content is encoded (with a ContentEncoding header), and
adding a Fault to identify unsupported encodings
... Would provide a standard mechanism for declaring encoding -
e.g. content compressed with gzip
Amy: Might need to differentiate between content-encoding and transfer-encoding
Eric: That was not included in
Jean-Baptiste's proposal but it did come up in discussion
... If we open the issue, then the minimum required changes
will be to add support for a new JMS property, and to add a
fault that the service provider can throw if the encoding is
not supported
... We *could* simultaneously define two versions of the spec.
and say that version 1.0 of the specification does not support
the new header and version 1.1 does
Amy: Makes sense to open the issue to have further discussion
Peter: Agreed - we should acknowledge the use-case - would be interesting to hear what support there is in otherJMS implementations for compression
Eric: TIBCO has a special (non-standard) JMS header which tells TIBCO EMS to compress the message in-flight
<eric> Mark, we lost you on the phone - you calling back in?
apologies - line dropped - dialling back in
Mark: +1 for opening the issue
Phil +1
RESOLUTION: Issue 65 will be opened
Issue 66
Eric: Missing test cases as found by Peter
RESOLUTION: Issue 66 will be opened
Eric: Need someone to come up with proposal(s) for Issue-65
<scribe> ACTION: Eric to come up with a proposal for Issue-65 [recorded in http://www.w3.org/2010/11/16-soap-jms-minutes.html#action01]
<trackbot> Created ACTION-228 - Come up with a proposal for Issue-65 [on Eric Johnson - due 2010-11-23].
<scribe> ACTION: Phil to come up with a proposal for Issue-65 [recorded in http://www.w3.org/2010/11/16-soap-jms-minutes.html#action02]
<trackbot> Created ACTION-229 - Come up with a proposal for Issue-65 [on Phil Adams - due 2010-11-23].
3 people at the IETF are looking at the URI scheme
Eric: Hope we will hear something
this week - will pos an update to the list
... and update the Draft on IETF
... One comment we have had is that the Sun URIs for JMS and
JNDI might not be the most current (given Oracle's acquisition
of Sun)
Eric: Suggest we skip next week's call - please endeavour to progress actions in the meantime
<padams> +1
RESOLUTION: No call next week
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) No ScribeNick specified. Guessing ScribeNick: mphillip Found Scribe: Mark Default Present: +1.512.286.aaaa, padams, +1.708.246.aabb, +1.650.846.aacc, +44.196.287.aadd, Mark, eric, +1.781.280.aaee, Derek, +1.919.663.aaff Present: +1.512.286.aaaa padams +1.708.246.aabb +1.650.846.aacc +44.196.287.aadd Mark eric +1.781.280.aaee Derek +1.919.663.aaff Found Date: 16 Nov 2010 Guessing minutes URL: http://www.w3.org/2010/11/16-soap-jms-minutes.html People with action items: eric phil WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]