- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Wed, 9 Jun 2004 10:41:12 -0700
- To: <www-ws-desc@w3.org>
0. Dial in information (members only) [.1]:
See the public WG page [.2] for pointers to current documents and other
information, and the private page [.3] for administrative matters.
If you have additions to the agenda, please email them to the WG list
before the start of the telcon.
[.1] http://lists.w3.org/Archives/Member/w3c-ws-desc/2004Jun/0011.html
[.2] http://www.w3.org/2002/ws/desc/
[.3] http://www.w3.org/2002/ws/desc/admin
--------------------------------------------------------------------
Agenda
1. Assign scribe. Lucky minute taker for this week is one of:
Erik Ackerman, Adi Sakala, Tom Jordahl, William Vambenepe,
Prasad Yendluri, Jean-Jacques Moreau, Umit Yalcinalp,
Igor Sedukhin, Dale Moberg, Paul Downey, Hugo Haas
--------------------------------------------------------------------
2. Approval of minutes:
- June 3 (corrected) [.1]
[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0041.html
--------------------------------------------------------------------
3. Review of Action items [.1].
? 2004-04-01: Marsh will get schema tf going.
?ED 2004-04-29: Part 1 editors to adopt Jacek's "purpose of the
binding" text, without "interchangeable"
endpoints, and using "confidentiality" (or
similar) instead of TLS.
?ED 2004-05-19: Editors to include in the primer an example
that uses MTOM. (Issue 72)
?ED 2004-05-19: Editors to make propogation of modules and f&p
use the nearing enclosing scope. (Issue 180)
?ED 2004-05-19: Editors to fix component model to remove
default* properties, use mapping from syntax
instead. (Issue 182)
?ED 2004-05-20: Editors to incorporate Hugo's full potato
proposal. (Issue 54)
?ED 2004-05-20: David Orchard to update HTTP binding to
include discussion of how to generate an
accepts header from schema annotations
conformant to the media types extension
document, and to use outputSerialization
based on that information.
?ED 2004-05-20: Editors to incorporate http:{properties} into
binding.
?ED 2004-05-21: Sanjiva to implement the resolution that
@soapaction not there means no soapaction.
(Issue 1)
? 2004-05-21: Part 2 Editors to add such a statement.
(Issue 191)
?ED 2004-05-21: Part 3 Editors to add a statement to relate
each of the two soap meps to wsdl meps.
(Issue 191)
?ED 2004-05-21: Editors to add ednotes to the spec to
indicate areas that had contention. (Issue
190)
?ED 2004-05-21: Editors to remove @separator from HTTP
binding. (Issue 190)
? 2004-05-21: DaveO to write up a scenario to motivate path
creation on a per-operation basis. (Issue
190)
?ED 2004-05-21: Editors to write up that we allow
http:version etc. in the soap binding when
the protocol is http. (Issue 190)
?ED 2004-05-21: Editors to update part 3 to say that for SOAP
Response MEPs the URI will be generated
following the HTTP binding rules for
generating a URI (for GET). (Issue 61)
?ED 2004-05-21: Editors to update soap binding default rules
to allow use of MTOM. (Issue 184)
? 2004-05-21: Amy to provide wording to go into spec to say
that our bindings only support the identified
MEPs but others can be handled if appropriate
rules are defined elsewhere. (Issue 155)
?ED 2004-05-27: Editors to add http:faultSerialization
attribute.
? 2004-05-27: DaveO will write up better description of
this issue (189).
[.1] http://www.w3.org/2002/ws/desc/#actions
---------------------------------------------------------------------
4. Administrivia
a. New members:
- Mark Nottingham replacing Yaron Goland for BEA
- Jacek Kopecky returns, representing DERI
- Peter Madziak, Helen Chen join from Agfa-Gevaert N. V.
b. Upcoming FTFs
- August 2-4 (London)
Logistics [.1], registration [.2].
- September 14-16 (Toronto) [.3]
- November (West Coast) volunteers needed
[.1] http://www.w3.org/2002/ws/desc/4/04-08-f2f.htm
[.2] http://lists.w3.org/Archives/Member/w3c-ws-desc/2004Mar/0064.html
[.3] http://lists.w3.org/Archives/Member/w3c-ws-desc/2004May/0000.html
------------------------------------------------------------------
5. Task Force Status.
a. Media type description
- 1st Working Draft Published [.1]
b. MTOM/XOP
- Last Call Published [.2]
c. QA & Testing
- Suggested QA plan [.3]
- More details from Arthur [.4]
- Interop bake-off
d. Schema versioning
- Waiting to hear back from Schema on my draft "charter."
- Henry's validate-twice write-up [.5]
[.1] http://www.w3.org/TR/2004/WD-xml-media-types-20040608/
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0052.html
[.3]
http://lists.w3.org/Archives/Public/www-ws-desc/2004Apr/att-0029/QA_Oper
ational_Checklist.htm
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2004Apr/0037.html
[.5] http://lists.w3.org/Archives/Public/www-ws-desc/2004Apr/0019.html
------------------------------------------------------------------
6. New Issues. Issues list [.1].
- Mark N's: See issues 207-225.
- 208, 213, 215 are editorial - refer directly to editors?
[.1] http://www.w3.org/2002/ws/desc/2/06/issues.html
------------------------------------------------------------------
7. Issue 207: Binding message content to URI [.1]
- How to mark which elements to optimize
- See thread starting at [.2]
- Related issue on F&P? [.3]
[.1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x207
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0020.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0042.html
------------------------------------------------------------------
8. XML 1.1 issues (time permitting)
- Issue 174: Tie WSDL conformance to XML conformance? [.1]
- Issue 175: Is it valid for a XML 1.1 document to import or
include a XML 1.0 document (and vice versa)? [.2]
- Issue 176: Can a WSDL 2.0 XML 1.1 document contain (or
reference), a XML Schema 1.0 type description? [.3]
- Issue 177: Normative dependence on XML Schema 1.0 precludes
XML 1.1 [.4]
- Proposed resolutions [.5]
[.1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x174
[.2] http://www.w3.org/2002/ws/desc/2/06/issues.html#x175
[.3] http://www.w3.org/2002/ws/desc/2/06/issues.html#x176
[.4] http://www.w3.org/2002/ws/desc/2/06/issues.html#x177
[.5] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0049.html
------------------------------------------------------------------
9. Issue 189: Binding message content to URI [.1]
- Awaiting issue description from DaveO
[.1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x189
------------------------------------------------------------------
10. Issue 158: Setting HTTP headers in the HTTP binding [.1]
- ADD related.
[.1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x158
------------------------------------------------------------------
11. Issue 112: New headers/body style? [.1]
- ADD proposal [.2]
- friendly amendment [.3]
[.1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x112
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2004Mar/0167.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2004Mar/0170.html
------------------------------------------------------------------
12. Issue 130: Need async request/response HTTP binding [.1]
- David Orchard's Async proposal [.2]
[.1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x130
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2004May/0029.html
------------------------------------------------------------------
Scheduled for future telcons
------------------------------------------------------------------
13. Effort to simplify our spec.
- DavidB [.1] and Jonathan [.2] have provided some data points.
- Arthur's suggestion [.3]
[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2004Mar/0162.html
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2004Apr/0006.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2004Apr/0028.html
Received on Wednesday, 9 June 2004 13:41:43 UTC