- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Wed, 26 Jun 2002 13:46:30 -0700
- To: <www-ws-desc@w3.org>
Dial in information (members only):
http://lists.w3.org/Archives/Member/w3c-ws-desc/2002Jun/0049.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 Mike McHugh, Don Mullen, Jochen Ruetschlin,
Waqar Sadiq, Adi Sakala)
2. Approval of minutes.
2a. 20 June telcon [6].
2b. Minutes from FTF - allow one more week for review.
See [7], [8], [9], [10], [11], [12].
3. Review of Action items.
DONE 2002-06-20: JM. Converging issues list for single view
DONE 2002-06-20: JJM. add to issues list - specifying soap bindings
fault codes
2002-06-20: Sanjiva. Champion for 6c. Issue: SOAPAction1 #1
2002-06-20: Jean-J. Analyze whether WSD should gneralize a
mechanism
to provide protocol headers. This was discussed as part
of 6d. Issue: SOAPAction2 #2
DONE 2002-06-20: Gudge. Champion for 6e: Issue Namespaces #4
DONE 2002-06-20: Arthur: Champion for 6f. Issue: Encoding Style #5
DONE 2002-06-20: Jean-J Champion for 6g. Issue: nowhere to specify
actor URI in WSDL? #17
2002-06-20: JeffS Champion for 6h. Issue: Default for transport
of <soap:binding> #18
2002-06-20: Jean-J, Glen, Mike, Dietmar create TF. 3 weeks for
findings on 6i. Issue: SOAP 1.2 support? #23
2002-06-20: JonathanM will help with telecon logictics for 6i.
Issue: SOAP 1.2 support? #23
2002-06-20: JonathanM. Postpone 6j. Issue: Real difference
between literal vs. encoded? #24
DONE 2002-06-20: Gudge. Champion for 6k. Issue: Unclear relationship
between XML Schemas and SOAP data model #25
DONE 2002-06-20: Arthur. Champion for 6o. Issue: soap:body encodingStyle
#30.
2002-06-20: Issue Editor. Jean-J identifies dup issue: 6q. Issue:
SOAP 1.1 backward compatibility support? #32
4. SOAP TF meeting - Monday 8AM PDT?
5. Representation change: Cisco.
6. Requirements document:
Seeking approval to publish. [13]
New draft requirements at [19]
7. WSDL 1.2 (parts 1 [14] and 2 [15])
Seeking approval to publish on June 30 (?) barring any showstoppers.
AM note at [20]
8. Duplicate/redundant issues identified by Sanjiva. Call for
objections at [38].
No controversy:
- Issue 57: Should Operations permit alternate and multiple
responses? [22]
- Issue 43: Does order matter for the child elements of
"definitions"? [23]
- Issue 38: Clarify the what kinds of extensibility elements go
where [24]
- Issue 37: Should we remove parameter order? [25]
- Issue 36: Should we remove notification operations? [26]
- Issue 35: Should we remove solicit-response operations? [26]
- Issue 34: Should portTypes be extensible? [27]
- Issue "issue-clarify elements" [29]
- Issue 42: Shall "element" attribute of "part" only refer to
elements defined in schema? [30]
Some discussion:
- Issue 26: Transmission primitives [28], [31]
- Issue 60: Text in the WSDL spec inconsistency about optional
parts [21], [40]
9. New Issues
- Issue: Clarification of the meaning of soap:operation/@style [16]
- Issue: SOAP binding violates separation of abstract definitions
and concrete bindings [37]
- Issue: Ports, Names, Symbol Spaces and targetNamespace [43]
10. Editorial Issues
Proposal: Delegate responsibility to editors for all issues marked
as "Editorial" in the issues list [42]. WG members would have 2 weeks
to review this list and verify that no issues marked "Editorial" have
substantive content that needs to be discussed.
11. Issue: Overloading operations.
Joyce's rationale: [17]
Vote:
- Remove overloaded operations
- Keep overloaded operations
12. Issue 17: support for SOAP role attribute.
JJM's proposal thread starts at [32].
13. Issue issue-require-targetnamespace:
Gudge's proposal thread starts at [33].
14. Issue: optional "name" attribute of <definition>
Sanjiva's proposal to remove this attribute [34].
15. Issue 4: Namespaces
Gudge's proposal [35], musings at [39]
16. Issue issue-multiple-services.
Sanjiva's proposal at [44].
17. Issue 5: EncodingStyle.
Arthur recommends closing as a dupe of Issue #30. [41]
18. Issue 25: Interaction between W3C XML Schema and SOAP Data Model
Gudge's explains at [36]
19. Issue 30: soap:body encodingStyle
Arthur's proposal [41]
20. Issue service-type: [46] OK to wait on Abstract Component work to
provide a more concrete proposal?
21. Issue remove-solicit-response-operations: Removing solicit-response
and notifications. [45] OK to schedule for FTF?
22. HTTP Binding Issues (6a, 41)
Jeffrey recommends no change [18].
- 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/0170.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/0208.html
[13]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/requirements/ws-desc-re
qs.html
[14] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/part1/part1.html
[15]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/part2/wsdl12-part2.html
[16] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0110.html
[17] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0080.html
[18] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0102.html
[19] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0164.html
[20] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0166.html
[21] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0111.html
[22] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0112.html
[23] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0113.html
[24] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0114.html
[25] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0115.html
[26] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0116.html
[27] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0117.html
[28] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0118.html
[29] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0120.html
[30] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0121.html
[31] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0137.html
[32] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0190.html
[33] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0167.html
[34] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0175.html
[35] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0168.html
[36] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0186.html
[37] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0187.html
[38] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0144.html
[39] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0191.html
[40] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0182.html
[41] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0178.html
[42] http://www.w3.org/2002/ws/desc/2/06/issues.html
[43] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0165.html
[44] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0046.html
[45] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0109.html
[46] http://lists.w3.org/Archives/Public/www-ws-desc/2002Jun/0002.html
--------------------------------------------------------------------
Received on Wednesday, 26 June 2002 16:47:02 UTC