See also: IRC log
<trackbot> Date: 27 July 2010
Eric: Chair will be absent for meeting during week of Aug. 9-13 - shall we skip the meeting?
Mark: I'll be out too - happy to skip
Phil: +1
Amy: (Will be out next week )
RESOLUTION: We will skip the meeting from 9-13 August
<scribe> Scribe: Mark
The minutes are approved
Agenda approved without modification
Eric: Sent updated draft of URI scheme to the list. Main changes are to make it a provisional draft, and to make the JMS reference a normative reference
Mark: A number of RFC2119 words are lower case, but I'm happy with that
Eric: Could take a run at changing
Phil: Agree with Mark - doesn't seem very important - using the words without capitalisation is clear enough
Eric: OK - will submit as a provisional scheme today.
http://www.w3.org/2002/ws/soapjms/tracker/actions/146 - Eric - no action
http://www.w3.org/2002/ws/soapjms/tracker/actions/181 - Eric - can't close (this is the issue of moving to CR)
http://www.w3.org/2002/ws/soapjms/tracker/actions/189 - Eric - done resolution for issue 40
close action-189
<trackbot> ACTION-189 Apply resolution for issue 40 closed
http://www.w3.org/2002/ws/soapjms/tracker/actions/190 - Eric - done - issue 59 raised
close action-190
<trackbot> ACTION-190 Review the test cases once the changes for issue 39 have been applied closed
http://www.w3.org/2002/ws/soapjms/tracker/actions/191 - Derek - no progress
http://www.w3.org/2002/ws/soapjms/tracker/actions/192 - Mark - done
close action-192
<trackbot> ACTION-192 Send list of known JMS URI formats to the SOAP/JMS list closed
http://www.w3.org/2002/ws/soapjms/tracker/actions/193 - Eric - investigate provisional URI process - still needs further investigation
http://www.w3.org/2002/ws/soapjms/tracker/actions/194 - Eric
<scribe> done
close action-194
<trackbot> ACTION-194 Apply the resolutions to Issues 41-46 closed
http://www.w3.org/2002/ws/soapjms/tracker/issues/47 -
Eric: topicReplyToName has two unflagged RFC2119 assertions, some inappropriate
Mark: Proposal looks good
Phil: Fine with rewording like this
RESOLUTION: Issue 47 is opened
Eric: proposal is to rewrite the text to eliminate the keywords
RESOLUTION: The proposal to resolve Issue 47 is accepted as written
http://www.w3.org/2002/ws/soapjms/tracker/issues/48
Eric: Four unflagged 2119 assertions about message body and content type - more appropriate to move to definition of contentType
RESOLUTION: Issue 48 is opened
http://www.w3.org/2002/ws/soapjms/tracker/issues/49
Eric: Section 2.4.1: Another MUST statement without an assertion - describing the intended behaviour of XML parser
RESOLUTION: Issue 49 is opened
Eric: XML parsers will already ignore the encoding
Discussion on whether the bullet is required at all
RESOLUTION: The proposal to resolve Issue 49 is accepted as written
http://www.w3.org/2002/ws/soapjms/tracker/issues/50
Eric: The first paragraph in Section 2.5 does not make it clear that SOAP 1.1 must follow the patterns defined in this document
RESOLUTION: Issue 50 is opened
Mark: Suggest the proposal is
modified to make it clear that the MEP is specified in this
document
... Moving the third paragraph up above the SOAP 1.2
statement
Phil: Agreed - merging the first and 3rd paragraphs
Eric: OK - we need an action for an alternative proposal
action mark to propose an alternative resolution to issue 50
<trackbot> Created ACTION-195 - Propose an alternative resolution to issue 50 [on Mark Phillips - due 2010-08-03].
http://www.w3.org/2002/ws/soapjms/tracker/issues/51
Eric: normative statements are redundant in 2.4 (assertion 2027) and 2.6.1.1 (assertion 2034) and 2.7.1 (assertion 2040)
RESOLUTION: Issue 51 is opened
Eric: Propose rewording and removing assertions 2034 and 2040
RESOLUTION: The proposal to resolve Issue 51 is accepted as written
http://www.w3.org/2002/ws/soapjms/tracker/issues/52
Eric: Lower case RFC2119 "must" keyword for JMSReplyTo in 2.6.1.1
RESOLUTION: Issue
52 is opened
... The proposal to resolve Issue 52 is accepted as written
http://www.w3.org/2002/ws/soapjms/tracker/issues/53
Eric: Missing description for failure behaviour in 2.6.1.3
RESOLUTION: Issue 53 is opened
Phil: Suggest we revise the proposal to spell the word fail as "Fail"
RESOLUTION: The proposal to resolve Issue 53 is accepted with the amendment to the word fail as suggested by Phil
http://www.w3.org/2002/ws/soapjms/tracker/issues/54
Eric: In 2.6.2.3 JMSDeliveryMode has an unflagged SHOULD
RESOLUTION: Issue 54 is opened
Eric: Proposal is that SHOULD changes to "ought to"
RESOLUTION: The proposal to resolve Issue 54 is accepted as stated in the issue text
Out of time
<scribe> ACTION: Eric to To apply resolutions for the resolved issues above [recorded in http://www.w3.org/2010/07/27-soap-jms-minutes.html#action01]
<trackbot> Created ACTION-196 - Apply resolutions for the resolved issues above [on Eric Johnson - due 2010-08-03].
Phil: Do we have outstanding changes that will affect the test cases?
Eric: The test cases will be simplified by removal of normation assertions and Issue 59 will add test cases for Correlation ID
Phil: Would be good to get the test cases sorted as soon as we can
Eric: Agreed
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: [IBM-Hursley], alewis, +1.512.286.aaaa, +1.209.474.aabb, +1.708.246.aacc Present: [IBM-Hursley] alewis +1.512.286.aaaa +1.209.474.aabb +1.708.246.aacc Found Date: 27 Jul 2010 Guessing minutes URL: http://www.w3.org/2010/07/27-soap-jms-minutes.html People with action items: eric WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]