See also: IRC log
<trackbot> Date: 05 October 2010
<scribe> Scribe: Mark
Minutes approved with no amendments
http://lists.w3.org/Archives/Public/public-soap-jms/2010Sep/0022.html
Link to minor issue
To be discuss under "Raised spec issues"
No other modifications
Eric: Apologies for cancellation last week
Eric: Progress on 213 (prepare
disposition of comments document ) but more work to do
... Suggest we close 213 and raise new actions based on
feedback
... Rseponded to question about whitespace in URI per 215
close action-215
<trackbot> ACTION-215 Respond to question about encoding of white space in parameters closed
http://lists.w3.org/Archives/Public/public-soap-jms/2010Sep/0022.html
Mark: Issue is the paragraph describing encoding is too specific - suggest we broaden it to all characters in the URI instead of just parameter values
Eric: Doesn't affect normative text - could be considered an editorial change
<eric> http://www.w3.org/2002/ws/soapjms/tracker/issues/64
RESOLUTION: No objections to opening this issue
No comments on proposed resolution
RESOLUTION: The proposal for issue 64 is accepted as written
action mark to apply the proposal for issue 64
<trackbot> Created ACTION-216 - Apply the proposal for issue 64 [on Mark Phillips - due 2010-10-12].
None
Eric: Has the action to change
the status of the document to reflect new status
... Need to make a copy of the document so that the editors
draft does not show new status
... ...and make associated build changes. The run the pubrules
checker over the document, and add the "status of the document"
section
... ...other last call working draft documents can be used for
reference
... Yves will be able to help chek the document
... Still need the 2 working implementations to move to PR
Mark: Will have a go at updating the document with those changes
Eric: Action 212 reassigned to Mark
<eric> http://lists.w3.org/Archives/Public/public-soap-jms/2010Oct/0002.html
Eric: Disposition of comments at
above link
... About to check this document into CVS so oher people can
edit
... Other examples of Disposition of Comments documents have
more complex status sections, but most of the SOAP/JMS issues
have been raised and resolved by the workgroup without the
resolutions being rejected, so we should be able to have a
relatively simple set of tables
Mark: What is the section "Issues Agreed In Specification"?
Eric: "Issues Agreed In
Specification" will be issues raised by people outside
workgroup.
... Question for workgroup - what to put in commentary
section?
... e.g. a link to the minutes where the resolution was
discussed
Mark: A link to the email which describes the application should be sufficient
Eric: ...and a link to the
minutes where we approved the proposed resolution - or modified
the proposal to come up with a resolution
... OK - will commit the current version to CVS and start to
fill in the Commentary.
... (Using OpenOffice to edit HTML if anyone else wants to help
editing)
Mark Nottingham is the reviewer - we owe him a response to his comments so far
Eric: (e.g. comment on the suggestion for a registry of JMS variants)
None
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.919.663.aaaa, alewis, +1.708.246.aabb, +1.650.846.aacc, eric, Derek, +1.512.286.aadd, padams, +44.196.287.aaee, mphillip, +1.617.519.aaff Present: +1.919.663.aaaa alewis +1.708.246.aabb +1.650.846.aacc eric Derek +1.512.286.aadd padams +44.196.287.aaee mphillip +1.617.519.aaff Found Date: 05 Oct 2010 Guessing minutes URL: http://www.w3.org/2010/10/05-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]