- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Wed, 17 Sep 2003 13:57:35 -0700
- To: <www-ws-desc@w3.org>
[Rearranged to accommodate requests (90% successful). Added additional
topics.]
Logistics [1], dial-in numbers [2] (members only).
[1] http://www.w3.org/2002/ws/arch/3/07/f2fSeptLogistics.html
[2] http://www.w3.org/2002/ws/arch/3/07/f2fSeptLogistics.html#Bridge
--------------------------------------------------------
Monday 22 September
--------------------------------------------------------
09:00 Introductions and logistics
- Assignment of scribes
@@@
- Agenda fine-tuning
09:15 Removing message. New Draft [3], schema [4]
- Countdown to close the following issues [5].
* Issue 27: Remove 'style' attribute [6]
* Issue 39: Binding extensions depend on structure of
portType [7]
* Issue 40: Binding extensions for SOAP interact in a
complex way [8]
* Issue 45: fault/@use should be optional [9]
* Issue 48: soap:body/@use should be optional [10]
* Issue 63: soap binding violates separation of abstract
and concrete [11]
- Rules for @encodingStyle [12, slide 18]
* No default value
* If not given then no information about the "style" of
the operation's elements is available.
- @encodingStyle="http://www.w3.org/2003/ws/desc/rpc" [12, slide 19]
* The input and output elements have been defined according to
a pattern indicated by these rules.
* Input/output elements contain only local element children
(i.e., no global elements allowed). (No <choice> etc.
allowed? Not sure but probably should say so.)
* Input element's name's localPart and operation/@name are the
same.
* Output element's name's localPart is
concat(operation/@name,"Response")
* Input and output elements are both in the same namespace.
* The child elements of input and output represent input and
output parameters of the operation. ("<part>" in WSDL 1.1)
* If there exists foo such that there are child elements named
foo in both input and output elements, then that represents
an in/out parameter.
* If there does not exist any such foo in both elements then
all the parameters are input-only and/or output-only as
appropriate (depending on whether they're in the input or
output element).
[3] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.xml
[4] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.xsd
[5] http://lists.w3.org/Archives/Public/www-ws-desc/2003Aug/0004.html
[6] http://tinyurl.com/mwuy#x27
[7] http://tinyurl.com/mwuy#x39
[8] http://tinyurl.com/mwuy#x40
[9] http://tinyurl.com/mwuy#x45
[10] http://tinyurl.com/mwuy#x48
[11] http://tinyurl.com/mwuy#x63
[12] http://lists.w3.org/Archives/Public/www-ws-desc/2003Jul/0161.html
10:30 Break
10:50 Binding enhancements. New draft [13, 14]
- Unresolved proposal: Drop <soap:binding>: drop @protocol, change
<soap:address>: add @protocol.
- Issue #80: Inappropriate name for binding component [15].
- Issue #81: Match between binding/@interface and
service/@interface should account for interface
inheritance. [16]
- Issue #82: Relax binding syntax constraints in favor of
semantic constraints [17]
- Issue #83: Specify interaction between binding extensions [18]
- Issue #84: Are SOAP header faults needed? [19]
- Issue #85: HTTP (non-SOAP) binding depends on message/part [20]
Philippe to make proposal.
- Issue #86: Should we define a new binding element for
default rule for wsoap:operation/@soapActionURI.
Proposal = interfaceTNS#operation-name. [21]
[13]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.xml#Bindi
ng
[14]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.xml#Endpo
int
[15] http://tinyurl.com/mwuy#x80
[16] http://tinyurl.com/mwuy#x81
[17] http://tinyurl.com/mwuy#x82
[18] http://tinyurl.com/mwuy#x83
[19] http://tinyurl.com/mwuy#x84
[20] http://tinyurl.com/mwuy#x85
[21] http://tinyurl.com/mwuy#x86
12:00 Lunch
13:00 Binding Enhancements (cont.)
14:00 Patterns. New draft [20]
- Choose specific patterns for the standard [21]:
1. TF recommendation: drop request-response and multicast-
solicit-response patterns, as subsumed by others [22].
2. Sanjiva's proposal: drop any pattern not used in a
normative binding in our spec.
3. Tom's proposal: drop the "multi" patterns.
4. Amy's proposal: at least the patterns in WSDL 1.1.
[20]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12-patterns.
xml
[21] http://lists.w3.org/Archives/Public/www-ws-desc/2003Aug/0010.html
[22]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/meps-vs-iops/rec
ommendations_clean.htm
15:00 Break
15:20 Patterns (cont.)
16:30 WSDL Validator demo (Arthur)
17:30 Adjourn
-------------------------------------------------------
Tuesday 23 September
-------------------------------------------------------
09:00 R085 Describing endpoint references. [30]
- General agreement to add such capability to WSDL, but
not agreement on the precise form of the annotations and
where in the WSDL they should reside. Proposal
from Umit [31], response from Arthur [32].
- Related issue (?) dynamic discovery of a service [33].
- Arthur to work with Umit to unify approaches.
[30]
http://lists.w3.org/Archives/Public/www-ws-desc/2003Apr/att-0088/R085-20
03-04-22.html
[31]
http://lists.w3.org/Archives/Public/www-ws-desc/2003Jun/att-0024/umit_pr
oposal.html__charset_ISO-8859-1
[32] http://lists.w3.org/Archives/Public/www-ws-desc/2003Jun/0142.html
[33] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0004.html
10:30 Break
10:50 Endpoint references (cont.)
12:00 Lunch
13:00 Attributes
- TF revised proposal [34]
[34] TBD
15:00 Break
15:20 Attributes (cont.)
17:30 Adjourn
-------------------------------------------------------
Wednesday 23 September
-------------------------------------------------------
09:00 [Attributes | Endpoint References as needed, otherwise:]
Issue 2: SOAPAction has been deprecated, as of SOAP 1.2 [40].
- Arthur's proposal to unify property URIs and QName URIs. [41]
Alternatives include using property markup, or a QNamed
attribute.
- Proposal for advertising QoS features of a Web service in WSDL
[42].
[40] http://tinyurl.com/mwuy#x2
[41] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0047.html
[42] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0020.html
09:45 Media type handling in WSDL 1.2 (Philippe) [43, 44, 45]
[43] http://lists.w3.org/Archives/Public/www-ws-desc/2003Mar/0028.html
[44] http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0088.html
[45] http://www.w3.org/2003/09/0912-media-types.html
10:30 Break
10:50 WSDL Component Designators [46]
Draft TAG finding [47]
[46] http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0075.html
[47] http://lists.w3.org/Archives/Public/www-tag/2003Jun/0054.html
12:00 Adjourn [48]
[48] http://www.cdsusa.com/
Received on Wednesday, 17 September 2003 16:57:46 UTC