15:58:13 RRSAgent has joined #soap-jms 15:58:13 logging to http://www.w3.org/2009/07/14-soap-jms-irc 15:58:15 RRSAgent, make logs public 15:58:15 Zakim has joined #soap-jms 15:58:17 Zakim, this will be SJMS 15:58:17 I do not see a conference matching that name scheduled within the next hour, trackbot 15:58:18 Meeting: SOAP-JMS Binding Working Group Teleconference 15:58:18 Date: 14 July 2009 15:58:27 trackbot, start telcon 15:58:29 RRSAgent, make logs public 15:58:31 Zakim, this will be SJMS 15:58:31 I do not see a conference matching that name scheduled within the next hour, trackbot 15:58:32 Meeting: SOAP-JMS Binding Working Group Teleconference 15:58:32 Date: 14 July 2009 15:58:54 RRSAgent, make logs public 15:59:33 chair: Eric 15:59:41 Phil has joined #soap-jms 15:59:45 we have a problem. 15:59:53 zakim doesn't have us scheduled on the bridge. 16:00:14 does that mean we won't get access ? 16:00:17 zakim, what conferences? 16:00:17 I see XML_ET-TF()11:00AM, Styl_XSLWG(F2F)4:00AM active 16:00:18 also scheduled at this time is SW_RIF()11:00AM 16:00:21 eric has joined #soap-jms 16:00:31 it means we can't dial in. 16:00:44 right... it doesn't recognize the usual passcode 16:01:12 i'm trying to find out if there's a way to schedule on the fly. 16:01:20 http://www.w3.org/2001/12/zakim-irc-bot 16:01:31 agenda: http://lists.w3.org/Archives/Public/public-soap-jms/2009Jul/0003.html 16:01:57 Derek has joined #soap-jms 16:02:12 peaston has joined #soap-jms 16:02:22 unfortunately, yves is on holiday, so he prolly can't help us. 16:02:55 http://www.w3.org/Guide/1998/08/TeleconferenceHowTo.htm 16:03:17 looks like a manual process 16:03:33 That also indicates two days notice. 16:03:40 yes :-( 16:03:44 umm. eric, do you have a teleconference number that we could resort to? 16:03:54 ok, Yves; conference Team_(soap-jms)16:03Z scheduled with code 26632 (CONF2) for 60 minutes until 1703Z 16:03:55 or ... anyone else have a bridge? 16:04:09 ah, yves! 16:04:13 happy bastille day! 16:04:19 thanks ;) 16:04:20 I have a call-in # that we could use if we need to 16:04:33 I'll check what happenned tomorrow wrt phone number 16:04:37 well conf code 16:05:11 Team_(soap-jms)16:03Z has now started 16:05:18 + +1.650.846.aaaa 16:05:20 That number worked for me. 16:05:30 + +1.708.246.aabb 16:05:34 + +1.919.663.aacc 16:05:35 Zakim, aaaa is eric. 16:05:36 + +0196287aadd 16:05:36 +eric; got it 16:05:49 Zakim, aadd is mark 16:05:49 +mark; got it 16:06:19 zakim, aabb is Derek 16:06:19 +Derek; got it 16:06:22 thanks Yves! 16:06:29 Indeed! 16:06:38 + +1.512.286.aaee 16:06:44 viva la revolution! 16:06:49 Zakim, aaee is Phil 16:06:49 +Phil; got it 16:07:15 TOPIC: 1) Appointment of the scribe 16:07:19 scribe: mark 16:07:40 +Peter_Easton 16:07:52 TOPIC: 2) Minutes 16:07:58 zakim, Peter_Easton is peaston 16:07:58 +peaston; got it 16:08:07 all: No problems 16:08:18 TOPIC: 3) Review the agenda 16:08:38 http://lists.w3.org/Archives/Public/public-soap-jms/2009Jul/0003.html 16:09:10 TOPIC: 4) Review action items 16:09:17 http://www.w3.org/2002/ws/soapjms/tracker/actions/open 16:09:32 Eric: No progress on 32 16:09:46 Derek: No progress on 68 16:10:50 Eric: Action 89 is done 16:10:56 http://lists.w3.org/Archives/Public/public-soap-jms/2009Jun/0013.html 16:11:11 email to be discussed in agenda item 6 16:11:55 Peter: Made contact with CXF team re: action 90 16:12:17 http://wiki.apache.org/general/soapjms4cxf 16:12:21 Peter: Some SOAP/JMS changes checked into CXF - no work done on WSDL 16:12:45 Peter: Will add details into email 16:13:06 close action-89 16:13:06 ACTION-89 Review the test assertion IDs to see which ones we _really_ need to test closed 16:13:13 close action-90 16:13:13 ACTION-90 Follow up contacts with CXF to find out timeframes etc. closed 16:13:42 TOPIC: 5) URI specification - updated submission: 16:14:06 Eric: No feedback / objections to updated submission 16:14:12 https://datatracker.ietf.org/drafts/draft-merrick-jms-uri/ 16:14:28 Eric: Need to assess what we need to do to get this to RFC 16:15:58 Eric: Have contacted all contributors to check contact details and get signoff for 200902trust IP Language - waiting for IBM, Progress, and Oracle 16:16:20 TOPIC: 6) Specification items: 16:16:39 a) Updates to the FAQ... 16:16:53 http://www.w3.org/2002/ws/soapjms/wiki/2008-09_FAQ 16:17:43 Eric: Seems like we should address some additional questions 16:18:30 Eric: e.g. How does this compare with SOAP/HPP 16:18:43 s/HPP/HTTP/ 16:19:20 Eric: Could do with links to definitions 16:19:40 Mark: Maybe something about reliable messaging 16:20:49 Eric: Should be reserve some time next call to brainstorm questions 16:20:56 s/be/we/ 16:21:19 b) Specification inconsistency: 16:21:44 Eric: Bug in spec identified: http://lists.w3.org/Archives/Public/public-soap-jms/2009Jul/0001.html 16:23:51 ACTION: Eric to propose a change to Spec. wording to remedy inconsistency in MIME example vs. Protocol-2029 assertion 16:23:51 Created ACTION-91 - Propose a change to Spec. wording to remedy inconsistency in MIME example vs. Protocol-2029 assertion [on Eric Johnson - due 2009-07-21]. 16:24:05 c) Unnecessary normative statements: 16:24:21 http://lists.w3.org/Archives/Public/public-soap-jms/2009Jun/0013.html 16:24:38 http://www.w3.org/TR/2009/CR-soapjms-20090604/#binding-examples 16:26:19 Eric Proposal to merge Protocol-2012 and 2013 16:26:35 Mark: Makes sense 16:28:19 Eric: Similarly propose to drop Protocol-2020 and include fault subcode in Protocol-2019 16:30:29 Eric: and collapse Protocol-2023 and 2024 into a single assertion 16:30:56 s/2024/2022/ 16:32:43 Eric: Propose reworking the table for 2024 http://www.w3.org/TR/2009/CR-soapjms-20090604/#Protocol-2024 16:34:55 Eric: Have the table specifiy the behaviour without assertions, and the repeat the assertions about which properties must be included "As-is", "SHOULD exclude", and "MUST exclude" in three bullets following the table 16:35:25 Eric: Each bullet would describe a set of properties with common behaviour, and would be a separate normative statement 16:37:00 Mark: Agree, it would be easier to test with 3 separate assertions 16:38:02 ACTION: Mark to propose the wording for the change to split 2024 into three testable assertions 16:38:02 Sorry, amibiguous username (more than one match) - Mark 16:38:02 Try using a different identifier, such as family name or username (eg. mhapner, mphillip) 16:38:19 ACTION: mphillip to propose the wording for the change to split 2024 into three testable assertions 16:38:19 Created ACTION-92 - Propose the wording for the change to split 2024 into three testable assertions [on Mark Phillips - due 2009-07-21]. 16:39:41 Eric: Protocol-2035 is redundant - all assertions in the table are made elsewhere 16:39:51 Phil: Agreed - we can remove this 16:46:04 Eric: Propose removing Protocol-2039 - must normative statements are covered elsewhere apart from the statement on the request URI. 16:49:06 Mark: We had early use cases which were based on the request_URI being used for routing. Having this value in the reply would help correlate requests and replies but I don't have a strong opinion that ths should be kept in 16:50:04 Eric: When removing Protocol-2035, we should also remove the requirement to copy the SOAPJMS_requestURI from the request 16:50:34 Eric: i.e. remove the requestURI line from the table 16:52:23 ACTION Eric to propose the revised table to the list 16:52:23 Created ACTION-93 - Propose the revised table to the list [on Eric Johnson - due 2009-07-21]. 16:53:35 Eric Protocol-2041 is also a collection of redundant assertions. Could change the table title to 'Examples of values set by Conforming Client' 16:53:46 Phil: Would be sufficient to just remove the assertion 16:54:20 TOPIC: 7. Testing 16:54:23 No progress 16:54:27 TOPIC: 8) Implementations 16:55:28 Eric: Some progress on CXF, we know IBM has an implementation in WAS, so we are working towards the two implementations we need 16:55:57 Eric: Next question is what is the timeline for having these implementations done? 16:56:16 Derek: Still working with product management 16:57:26 Phil: May be possible for IBM and CXF to collaborate on test cases 16:57:31 Pete: Will check into that 16:57:35 TOPIC: 9) AOB 16:58:09 None 16:58:11 -Phil 16:58:12 -eric 16:58:12 -Derek 16:58:13 -mark 16:58:22 -peaston 16:58:28 rrsagent, generate minutes 16:58:28 I have made the request to generate http://www.w3.org/2009/07/14-soap-jms-minutes.html mphillip 16:58:33 -alewis 16:58:34 Team_(soap-jms)16:03Z has ended 16:58:35 Attendees were +1.650.846.aaaa, +1.708.246.aabb, +1.919.663.aacc, +0196287aadd, eric, mark, alewis, Derek, +1.512.286.aaee, Phil, peaston 17:02:38 eric has left #soap-jms 19:00:06 Zakim has left #soap-jms