- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Wed, 19 Jun 2002 15:35:30 -0700
- To: <www-ws-desc@w3.org>
Dial in information (members only): http://lists.w3.org/Archives/Member/w3c-ws-desc/2002Jun/0024.html See the public WG page [1] for pointers to current documents and other information, and the private page [2] for administrative matters. If you have additions to the agenda, please email them to the WG list before the start of the telcon. -------------------------------------------------------------------- Agenda 1. Assign scribe. Lucky minute taker for this week is: Mario Jeckle (fallback Michael Mahan, Mike McHugh, Don Mullen, Jochen Ruetschlin, Waqar Sadiq, Adi Sakala) 2. Approval of minutes. 2a. 6 June telcon [6]. 2b. Minutes from FTF - allow one more week for review. See [7], [8], [9], [10], [11]. Where are minutes from Wed? 3. Review of Action items. DONE 2002.06.06: Joyce to write up rationale for dropping operation overloading. DONE 2002.06.06: GlenD to write up his proposed extensibility spec DONE 2002.06.06: GlenD and JJ will prepare a Soap MEP presentation for F2F RETIRED 2002.06.06: Jeffrey to write solicit-response proposal to discuss at f2f 2002.06.10: Martin to provide component descriptions for July 12. [in time for July 20 teleconf] ? 2002.06.11: Jacek to write a concrete proposal for solicit-response ? 2002.06.11: Jeffrey to write up his two requirements for solicit-response ? 2002.06.11: Martin is to follow up with Eric Prud'hommeux to see what he means by this requirement 4. Publication progress: 4a. Spec. Is there a new copy to review? At FTF we planned to approve publication next week. 4b. Requirements. 4c. Editors. 5. No telcon July 4th - US Independence Day. 6. Issues Main focus for today is to jumpstart discussion and proposals on new issues, especially by taking a survey of those marked as Editorial, and those related to the SOAP binding which have so far been neglected. 6a: Issue: Overloading operations. Joyce's rationale: [12] Is there any new information? [13] 6b. Issue(s): Non-SOAP HTTP Binding Jeffrey refactored up the non-SOAP HTTP binding issues [25] and proposed a solution for some of them in [26], [27], and [28]. See also [29]. SOAP Binding issues: 6c. Issue: SOAPAction1 #1 [30] 6d. Issue: SOAPAction2 #2 [31] 6e. Issue: Namespaces #4 [32] 6f. Issue: Encoding Style #5 [33] 6g. Issue: nowhere to specify actor URI in WSDL? #17 [34] 6h. Issue: Default for transport of <soap:binding> #18 [35] 6i. Issue: SOAP 1.2 support? #23 [36] 6j. Issue: Real difference between literal vs. encoded? #24 [37] 6k. Issue: Unclear relationship between XML Schemas and SOAP data model #25 [38] 6l. Issue: style="rpc|document" #27 [39] 6m. Issue: transport="uri" #28 [40] 6n. Issue: soap:body parts #29 [41] 6o. Issue: soap:body encodingStyle #30 [42] 6p. Issue: soap:address #31 [43] 6q. Issue: SOAP 1.1 backward compatibility support? #32 [44] 6r. Issue: Distinction between RPC style and document style #33 [45] 6s. Issue: The binding extension for SOAP is defined in terms of features that interact in a complex way #40 [46] 6t. Issue: Asymmetry between soap:body and soap:header #51 [47] - Jonathan -------------------------------------------------------------------- [1] http://www.w3.org/2002/ws/desc/ [2] http://www.w3.org/2002/ws/desc/admin [3] http://lists.w3.org/Archives/Member/w3c-ws-desc/ [4] http://lists.w3.org/Archives/Public/www-ws-desc/ [5] http://www.w3.org/2002/01/ws-desc-charter [6] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0044.html [7] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0057.html [8] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0056.html [9] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0081.html [10] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0069.html [11] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0064.html [12] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0080.html [13] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0092.html [25] http://lists.w3.org/Archives/Public/www-ws-desc/2002Apr/0182.html [26] http://lists.w3.org/Archives/Public/www-ws-desc/2002Apr/0183.html [27] http://lists.w3.org/Archives/Public/www-ws-desc/2002Apr/0204.html [28] http://lists.w3.org/Archives/Public/www-ws-desc/2002May/0009.html [29] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0102.html [30] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x1 [31] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x2 [32] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x4 [33] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x5 [34] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x17 [35] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x18 [36] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x23 [37] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x24 [38] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x25 [39] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x27 [40] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x28 [41] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x29 [42] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x30 [43] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x31 [44] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x32 [45] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x33 [46] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x40 [47] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html# x51 [48] --------------------------------------------------------------------
Received on Wednesday, 19 June 2002 18:36:03 UTC