SOAP-JMS Binding Working Group Teleconference

11 Aug 2009


See also: IRC log






<trackbot> Date: 11 August 2009

1) Appointment of the scribe

<scribe> Scribe: mphillip

2) Minutes

Minutes of last call: http://www.w3.org/2009/08/04-soap-jms-minutes.html

No objections

3) Review the agenda

2 additional issues raised since the agenda was posted

No other comments on agenda

4) Review action items

Actions: http://www.w3.org/2002/ws/soapjms/tracker/actions/open

Derek: No progress on action 68

Eric: Proposal submitted for #91

close action-91

<trackbot> ACTION-91 Propose a change to Spec. wording to remedy inconsistency in MIME example vs. Protocol-2029 assertion closed

Eric: No progress on actions 93 and 97

Phil: Have posted changes for issues related to actions 100 and 101

close action-100

<trackbot> ACTION-100 Apply Issue-7 resolution to spec CVS commit is acceptable closed

close action-101

5) URI specification:

Eric: No response from Dongbo (Oracle) or Progress)

6) Raised issues:

<eric> Raised issues: http://www.w3.org/2002/ws/soapjms/tracker/issues/raised

<eric> http://www.w3.org/2002/ws/soapjms/tracker/issues/9

Phil: Issues 1-7 discussed last week and normative wording agreed for faults
... Some of the wording in the spec. is still inconsistent with the newly agreed wording
... In issue 9 - propose editorial change to standardise the wording of fault descriptions

<trackbot> ACTION-101 Apply 1,2,3,5,6 issue resolutions to spec CVS commit is acceptable closed

No objections to opening this issue

<eric> http://www.w3.org/2002/ws/soapjms/tracker/issues/10

RESOLUTION: Open Issue 9

<eric> http://www.w3.org/TR/2009/CR-soapjms-20090604/#Protocol-2016

Phil: Issue 10 describes two assertions (2016 and 2017) which should be collapsed into one (section 2.2.3)

All agree to open issue-10

7) Accepting proposals to close open issues

<eric> http://lists.w3.org/Archives/Public/public-soap-jms/2009Aug/0003.html

<Phil> latest copy of binding spec: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8

RESOLUTION: All accept that Eric's proposal resolves this issue

Action Phil to update the spec with Eric's proposal for issue 8

<trackbot> Created ACTION-102 - Update the spec with Eric's proposal for issue 8 [on Phil Adams - due 2009-08-18].

8) Accepting applied resolutions:

Issue-1 -

<eric> http://lists.w3.org/Archives/Public/public-soap-jms/2009Aug/0007.html

Discussion about overcoming problem that a termdef element is not allowed in an assertion in the SpecXML document

Eric: Could cross-reference to the assertion later in section 2.8 (instead of to the term)

<Phil> "<p><termdef id="contentTypeMismatch" term="contentTypeMismatch"><assert class="document" id="Protocol-2012" cr-id="" preamble="(contentType)">

<Phil> If the <code>charset</code> parameter is specified, it is checked to ensure that it matches the encoding value from the supplied XML.

<Phil> A fault <rfc2119>MUST</rfc2119> be generated with subcode <term>contentTypeMismatch</term> if the encoding values do not match.</assert></termdef>

<Phil> </p>"

Phil: Propose the above solution - to put entire assert element inside termdef

<eric> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.58&content-type=text/html&f=h

<eric> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.58&content-type=text/html&f=h#Protocol-2012

No objections to this

RESOLUTION: Accept the applied resolution of Issue-1

Issue 2:



This is not consistent with the Issue-1 pattern

Action Phil to make the Issue-2 changes consistent with Issue-1

<trackbot> Created ACTION-103 - Make the Issue-2 changes consistent with Issue-1 [on Phil Adams - due 2009-08-18].

Issue 3



Assertion 2022 is also inconsistent with the style used for issue 1

Leave Issue 3 open for same corrections as Issue 2

Issue 5


<eric> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.58&content-type=text/html&f=h#Protocol-2034

RESOLUTION: All approve the application of resolution for Issue-5

<eric> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.58&content-type=text/html&f=h#Protocol-2038

Issue 6 http://www.w3.org/2002/ws/soapjms/tracker/issues/6

Eric: Our accepted resolution of this also included removing JMSPriority from the table

Action Phil to reapply the resolution for issue 6 (remove JMS Priority)

<trackbot> Created ACTION-104 - reapply the resolution for issue 6 (remove JMS Priority) [on Phil Adams - due 2009-08-18].

Out of time...

12). AOB

mphillip: I will be out of the office for the next two weeks

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/08/11 16:59:13 $

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/progress/Progress/
Found Scribe: mphillip
Inferring ScribeNick: mphillip

WARNING: No "Present: ... " found!
Possibly Present: Actions Derek Phil Yves alewis eric joined mphillip soap-jms trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Regrets: Peter
Agenda: http://lists.w3.org/Archives/Public/public-soap-jms/2009Aug/0010.html
Found Date: 11 Aug 2009
Guessing minutes URL: http://www.w3.org/2009/08/11-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]