SOAP-JMS Binding Working Group Teleconference

08 Feb 2011

See also: IRC log


+1.512.286.aaaa, +1.708.246.aabb, padams, Derek, +44.196.287.aacc, +1.209.474.aadd, Mark, eric, +1.919.663.aaee


<trackbot> Date: 08 February 2011

Appointment of the scribe

<scribe> scribe: Mark

Approval of prior meeting minutes

Minutes are approved without amendment

Review the agenda

No changes

Administrative items

Eric: Propose we skip next week's call - will decide later in the call
... Introducing Matthew

Review action items

Eric: 146 to follow up with Oracle, no progress
... 202 and 242 - both related moving to PR - propose we close

close action-202

<trackbot> ACTION-202 Investigate the necessary steps for completing CR and moving to PR closed

close action-242

<trackbot> ACTION-242 Clarify with Yves the criteria needed for PR vs. Rec closed

Phil: No progress on 223
... No progress on 223

Derek: No progress on 222

Phil: Does WebSphere Message Broker test with WebSphere App. Server?

Matthew: Yes - tested with WAS 7

Phil: Would interpos between two IBM products count towards compliance?

Eric: We'll come back to that question
... 243 still investigating TIBCO testing with WAS

Moving to PR (via CR? & LC)

Eric: If Message Broker can declare compliance, then the fact that it also works with WAS would be a bonus but not essential
... We need to show that each feature in the spec has been implemented

<eric> http://lists.w3.org/Archives/Public/public-soap-jms/2011Feb/0002.html

Eric: We do not currently have an implementation which includes WSDL support

Matthew: Message Broker has implemented the IRI part of the spec. (and can pull the IRI from WSDL) but WSDL properties are not implemented

action matthew to investigate whether CXF supports WSDL

<trackbot> Created ACTION-244 - Investigate whether CXF supports WSDL [on Matthew Golby-Kirk - due 2011-02-15].

Eric: Phil and Matthew to look into compatibility between IBM products
... 2 interoperable IBM products may be enough to move to PR, but probably not to reach W3C recommendation

Specification Issues:

Eric: No new issues

URI Scheme

Eric: Draft is in RFC editors queue, IANA have registered the URI scheme
... See:


Eric: and the registry has been created http://www.iana.org/assignments/jms-uri-variants/jms-uri-variants.xhtml
... Now chasing up the timeline for completion


Eric: Should we meet next week ?

RESOLUTION: We will skip the next meeting

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2011/02/08 17:32:30 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/222/223/
No ScribeNick specified.  Guessing ScribeNick: mphillip
Found Scribe: Mark
Default Present: +1.512.286.aaaa, +1.708.246.aabb, padams, Derek, +44.196.287.aacc, +1.209.474.aadd, Mark, eric, +1.919.663.aaee
Present: +1.512.286.aaaa +1.708.246.aabb padams Derek +44.196.287.aacc +1.209.474.aadd Mark eric +1.919.663.aaee
Found Date: 08 Feb 2011
Guessing minutes URL: http://www.w3.org/2011/02/08-soap-jms-minutes.html
People with action items: 

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

[End of scribe.perl diagnostic output]