- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Thu, 22 Jan 2004 11:37:15 -0800
- To: "WS Description List" <www-ws-desc@w3.org>
[Second draft]
Logistics [1], dial-in numbers [2] (members only).
[1] http://www.w3.org/2002/ws/desc/4/04-01-f2f.htm
[2] http://www.w3.org/2002/ws/desc/4/04-01-f2f.htm#Bridge
--------------------------------------------------------
Wednesday 28 January
--------------------------------------------------------
13:00 Introductions and logistics
- Assignment of scribes
(Igor Sedukhin), Adi Sakala, Arthur Ryman, (Prasad Yendluri),
(Dietmar Gaertner), Tom Jordahl, (Jeffrey Schlimmer),
Philippe Le Hegaret, William Vambenepe, Umit Yalcinalp
- Agenda bashing
13:10 Publication plan
Survey of remaining work
Part 1: Open issues:
misc (16)
editorial (2)
Part 2: Open issues:
misc (1)
editorial (1)
Primer: ?
13:30 Faults
- Issue 105: Abstract Faults [3]
Work through some WSDL examples to verify that Paul's
fault proposal [4] doesn't negatively impact bindings.
- Issue fault-name-uniqueness [5]: Should faults be named with
QNames? In WSDL 1.1 fault names are NCNames which are not unique
within portType even. This leads to a cumbersome mechanism to
uniquely identify a fault.
- Issue 89: Binding message references in component model [6]
[3] http://tinyurl.com/ysgl#x105
[4] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0064.html
[5] http://tinyurl.com/ysgl#xissue%20fault%20name%20uniqueness
[6] http://tinyurl.com/ysgl#x89
15:00 Break
15:20 Faults (cont.)
16:30 Joint Session with Arch WG
- Summary of Arch deliverables and areas WSDesc should be aware of
- Use Cases document disposition
- Issue 90: Synchronize terminology [7]
- Issue 75: Incoherence between WSA and WSD MEPs [8]
[7] http://tinyurl.com/ysgl#x90
[8] http://tinyurl.com/ysgl#x75
17:30 Adjourn
-------------------------------------------------------
Thursday 29 January
-------------------------------------------------------
09:00 Attribute styles "at risk?"
- Word from GGF that they don't want attribute styles [10].
- Issue 103: Proposal for combining the two attribute operation
styles to one [11, 12]
[10] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0086.html
[11] http://tinyurl.com/ysgl#x103
[12] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0164.html
10:30 Break
10:50 Features and properties "at risk?"
- WSChor statement [13]
- Issue 108: properties and schema languages other than XSD [14, 15]
If properties remain, we need to discuss requirements for a
solution to this issue and recruit a champion.
[13] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0066.html
[14] http://tinyurl.com/ysgl#x108
[15] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0006.html
12:30 Lunch
13:30 WSDL structure issues
- Issue X: BEA Simplified Syntax Proposal [16]
Overview and initial thoughts.
- Issue X: Headers/Body [17]
- Issue 102: Schemas in imported WSDL [18]
Review Glen's specese [19]
- Issue 95: service/@name required? [20]
Options:
a) No: remove service/@name
b) Yes: close issue.
- Issue 79: How much validation? [21]
Options:
a) In scope: need volunteer to write up a proposal.
b) Out of scope: close issue
[16] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0071.html
[17] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0069.html
[18] http://tinyurl.com/ysgl#x102
[19] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0017.html
[20] http://tinyurl.com/ysgl#x95
[21] http://tinyurl.com/ysgl#x79
15:00 Break
15:20 Structural issues (cont.)
16:00 Inheritance issues:
- Issue 76: Pointing at derived interfaces [22]
Options:
a) Yes: need volunteer to write up a proposal.
b) No: close issue
- Issue 81: Account for interface inheritance [23]
Options:
a) Yes: come up with an alternative.
b) No: close issue
[22] http://tinyurl.com/ysgl#x76
[23] http://tinyurl.com/ysgl#x81
17:30 Adjourn
-------------------------------------------------------
Friday 30 January
-------------------------------------------------------
09:00 Binding issues:
- Issue 80: Inappropriate binding component name [30]
Options:
a) Yes: come up with an alternative name.
b) No: close issue
- Issue 82: Relax binding syntax [31]
Need proposal to understand the scope of this issue.
- Issue 83: Interaction between binding extensions [32]
Options:
a) In scope: come up with a proposal.
b) Out of scope: close issue.
[30] http://tinyurl.com/ysgl#x80
[31] http://tinyurl.com/ysgl#x82
[32] http://tinyurl.com/ysgl#x83
10:30 Break
10:50 Issue 109: Versioning [33]
- Required reading (DavidO) [34]
- Use Cases (DavidO) [35]
- Requirements (PaulD) [36]
[33] http://tinyurl.com/ysgl#x109
[34] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0098.html
[35] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0070.html
[36] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0076.html
12:30 Lunch
13:30 Issue 96: Support for SOAP intermediaries [37]
Need an analysis on whether there are issues here.
[37] http://tinyurl.com/ysgl#x96
14:30 Issue 87: Redundant direction information [38]
Options:
a) Drop direction property.
b) Retain direction property.
[38] http://tinyurl.com/ysgl#x87
15:00 Break
15:20 Style issues
- Issue 98: > 1 style per interface [39]
Options:
a) Yes: Make @style an (unordered?) list of URIs.
b) No: Close issue.
- Issue X: Jacek's proposal to remove style attribute
and handle this using normal extensibility. [40]
[39] http://tinyurl.com/ysgl#x98
[40] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0054.html
16:00 Media type TF report (preliminary) [41]
[41]
http://lists.w3.org/Archives/Public/public-ws-media-types/2004Jan/0001.h
tml
16:30 Planning for remaining Part 1 issues.
- Issue 97: Schema language for SOAP encoding [42]
If such a language appears, what status would we give it?
- Issue 104: Appendix E cleanup [43]
- Issue 106: Using RDF in WSDL [44, 45]
[42] http://tinyurl.com/ysgl#x97
[43] http://tinyurl.com/ysgl#x104
[44] http://tinyurl.com/ysgl#x106
[45] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0076.html
17:00 Adjourn
Received on Thursday, 22 January 2004 14:37:17 UTC