- From: Bob Freund-Hitachi <bob.freund@hitachisoftware.com>
- Date: Thu, 02 Mar 2006 00:37:27 -0500
- To: "[WS-A]" <public-ws-addressing@w3.org>
- Message-id: <7D5D3FDA429F4D469ADF210408D6245A0390BD@jeeves.freunds.com>
W3C Web Services Addressing Working Group - Face to Face meeting agenda Mar 2-3 2006 Dial-in information on WG Admin page http://www.w3.org/2002/ws/addr/admin Meeting Room Iles B March 2 All times Central European Time 09:00 Call to order 1. Roll call, select scribe for both days (see scribe list below) 2. Agenda review, AOB 3. Call for corrections to the minutes - 2006-02-20: http://www.w3.org/2002/ws/addr/6/02/20-ws-addr-minutes.html 4. Progression Plan -Core - cleaned up pub for final WG review by March 13 -SOAP - cleaned up pub for final WG review By March 13 -WSDL - LC closes March end, get to CR by April 17 4. Review action items http://www.w3.org/2002/ws/addr/admin#actionitems 2006-01-19: David Orchard to draft SOAP 1.1 one-way binding WG Note. DONE 2006-02-20: Katy Warr to Propose text and drive issue cr23 DONE 5. Proposed CR Issues Proposed 1: Use SOAP 1.2 properties where possible in describing SOAP 1.2 behavior. http://www.w3.org/mid/43EA49FF.70603@tibco.com Proposed 2: Use of predefined fault actions for application faults [was FW: Action in 1133, 1134] http://www.w3.org/mid/37D0366A39A9044286B2783EB4C3C4E801B6775A@RED-MSG-1 0.redmond.corp.microsoft.com 10:00 Break 10:30 6. Conclusion and completion of "one paragraph" out-optional-in note 7. CR Issues <http://www.w3.org/2002/ws/addr/cr-issues/> * cr23 - cr15 resolution nullified cr4 resolution Owner: Katy Warr 12:00 Lunch 14:00 * cr21 - Resolution of CR17 introduced contradiction 15:00 break 16:00 Test status and report Redaction of features as indicated by test experience * wsa:ProblemHeader - testcases 1145 and 1245 * wsa:UnreachableDestination - testcase 1260 Adjourn at 17:30 March 3 09:00 Resume 1. Disposition of features at risk 10:00 break 11:00 obstacles to rec status Closure of remaining CR issues Instruction to prepare PR documents for Core and SOAP 12:00 Lunch 14:00 LC issues as received <http://www.w3.org/2002/ws/addr/lc-issues/> * lc109 - Should [fault endpoint] be required for robust in-only message? * lc110 - Should [fault endpoint] be prohibited in Robust in-only fault messages? * lc111 - Section 3.1.1 clarity * lc112 - Three states in two * lc113 - Section 3.3 clarity Proposal 1: In WSDL 2.0, a SOAP Module component may be used to declare the use of the WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a SOAP Module component is semantically equivalent to the {addressing required} property defined in section 3.1.1. Note that this module is only meaningful when used on WSDL components where the {addressing required} property is allowed, i.e. as a member of the {soap modules} property of a Binding component. * cr114 - Typos in section 2.1 * cr115 - Example 4-1 is wrong * cr116 - use of wsa:ReferenceParameters 15:00 break 17:30 close ----------------------------------------------------------- Scribe list A participant from the Member at the top of the list is expected to scribe the meeting. If no participant from that Member is able to scribe, a participant from the next Member on the list is expected to scribe, and so forth. After one participant from a Member scribes, that Member's name goes to the bottom of the list. Systinet Sonoa Hitachi HP Oracle ERICSSON IONA Nortel Sun Microsoft webMethods WSO2 JBoss Fujitsu TIBCO Sonic W3C SAP BT BEA CA IBM See <http://www.w3.org/2002/ws/addr/minutes.html> for more information about taking minutes.
Received on Thursday, 2 March 2006 05:37:37 UTC