www-ws-desc@w3.org from June 2002 by date

Sunday, 30 June 2002

• Re: service name as local part of a qname Steve Tuecke
• Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])) Sanjiva Weerawarana
• Re: service name as local part of a qname Sanjiva Weerawarana
• WSDL 1.2: Updated draft (June 30) Sanjiva Weerawarana

Saturday, 29 June 2002

• Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])) Steve Tuecke
• service name as local part of a qname Steve Tuecke
• Re: Draft agenda: 24 June TAG teleconference (Arch document, WSA update) Paul Prescod
• Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])) Sanjiva Weerawarana
• Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])) Sanjiva Weerawarana

Friday, 28 June 2002

• Re: elementFormDefault="qualified" in WSDL Schema.. David Booth
• Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])) Prasad Yendluri
• Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])) Prasad Yendluri
• Re: Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]) Sanjiva Weerawarana
• RE: Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]) Martin Gudgin
• Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon] Jean-Jacques Moreau
• Re: Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]) Jean-Jacques Moreau
• Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon] sggraham@us.ibm.com
• Re: Minutes, 27 June 2002 Web Service Description Telcon Jean-Jacques Moreau

Thursday, 27 June 2002

• RE: issue 43: Does order matter for the child elements of "defini tions"? Jeff Mischkinsky

Friday, 28 June 2002

• Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]) Sanjiva Weerawarana
• Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon] Sanjiva Weerawarana
• Resolved issues, 27 June 2002 Jonathan Marsh

Thursday, 27 June 2002

• Re: elementFormDefault="qualified" in WSDL Schema.. Prasad Yendluri
• Re: elementFormDefault="qualified" in WSDL Schema.. Prasad Yendluri
• ＊。。連鎖超商邀你加盟。。＊ kk@w3.org
• Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon] Jonathan Marsh
• ACTION: All wg members to review part 1 and part 2 by July 4 Jonathan Marsh
• Re: elementFormDefault="qualified" in WSDL Schema.. Prasad Yendluri
• ACTION: All wg members to review editorial issues by July 11 Jonathan Marsh
• Minutes, 27 June 2002 Web Service Description Telcon Jonathan Marsh
• updated draft of WSDL 1.2 (Part 1) ready for review Sanjiva Weerawarana
• RE: elementFormDefault="qualified" in WSDL Schema.. Martin Gudgin
• Re: elementFormDefault="qualified" in WSDL Schema.. Prasad Yendluri
• RE: elementFormDefault="qualified" in WSDL Schema.. David Cleary
• Re: Issue 17: support for SOAP role attribute Christopher B Ferris
• Re: Issue 4: Use of namespace attribute on soap:body Prasad Yendluri
• RE: issue: optional "name" attribute of <definition> Liu, Kevin
• RE: Target namespace in WSDL Liu, Kevin
• RE: Proposal to Resolve encodingStyle Issues #5 and #30 Jeffrey Schlimmer
• Re: Proposal to Resolve encodingStyle Issues #5 and #30 Jean-Jacques Moreau
• Re: Issue 17: support for SOAP role attribute Jean-Jacques Moreau
• Re: Proposal to Resolve encodingStyle Issues #5 and #30 ryman@ca.ibm.com
• Re: Issue 17: support for SOAP role attribute Christopher B Ferris
• updated draft Sanjiva Weerawarana
• Re: WSDL SOAP Binding schema does not reflect the spec Jean-Jacques Moreau
• Re: Proposal to Resolve encodingStyle Issues #5 and #30 Jean-Jacques Moreau
• Re: W3C WSDL WG Issues: Non-SOAP HTTP Binding Jean-Jacques Moreau
• Re: Issue: SOAP binding violates separation of abstract definitions concrete bindings Jean-Jacques Moreau
• Re: Issue 17: support for SOAP role attribute Jean-Jacques Moreau
• RE: issue 43: Does order matter for the child elements of "defini tions"? Martin Gudgin
• Re: issue 43: Does order matter for the child elements of "defini tions"? Sanjiva Weerawarana
• RE: issue 43: Does order matter for the child elements of "defini tions"? Martin Gudgin
• Re: issue 43: Does order matter for the child elements of "defini tions"? Sanjiva Weerawarana
• RE: elementFormDefault="qualified" in WSDL Schema.. Martin Gudgin
• Re: issue 43: Does order matter for the child elements of "defini tions"? Sanjiva Weerawarana
• RE: issue 43: Does order matter for the child elements of "defini tions"? Liu, Kevin
• Re: Target namespace in WSDL Prasad Yendluri
• elementFormDefault="qualified" in WSDL Schema.. Prasad Yendluri

Wednesday, 26 June 2002

• RE: Draft agenda: 24 June TAG teleconference (Arch document, WSA update) Jeffrey Schlimmer
• WSDL SOAP Binding schema does not reflect the spec Prasad Yendluri
• Re: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body ) Prasad Yendluri
• Re: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body ) Prasad Yendluri
• RE: Target namespace in WSDL Dave Hollander
• Agenda for 27 June 2002 WS Description WG Jonathan Marsh
• Minutes, Wed Afternoon 12 June 2002 FTF Jonathan Marsh
• RE: Issue 17: support for SOAP role attribute Martin Gudgin
• Re: issue: optional "name" attribute of <definition> Prasad Yendluri
• RE: Target namespace in WSDL Tom Jordahl
• RE: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body ) Jonathan Marsh
• RE: Target namespace in WSDL Martin Gudgin
• RE: Target namespace in WSDL Jonathan Marsh
• RE: Issue 17: support for SOAP role attribute Jonathan Marsh
• RE: Issue 17: support for SOAP role attribute Martin Gudgin
• Re: Issue 17: support for SOAP role attribute Jean-Jacques Moreau
• Re: Issue 17: support for SOAP role attribute Jean-Jacques Moreau
• RE: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body ) Martin Gudgin
• Re: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body ) Sanjiva Weerawarana
• Re: issue: optional "name" attribute of <definition> Joyce Yang
• Re: Issue 17: support for SOAP role attribute Bob Cunnings
• RE: Issue 17: support for SOAP role attribute Martin Gudgin
• RE: Issue 17: support for SOAP role attribute Martin Gudgin
• Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body ) Martin Gudgin
• Issue 17: support for SOAP role attribute Jean-Jacques Moreau
• Re: Target namespace in WSDL Jacek Kopecky
• Re: Target namespace in WSDL Jean-Jacques Moreau
• Re: Issue: SOAP binding violates separation of abstract definitions concrete bindings Prasad Yendluri
• Issue 25: Interaction between W3C XML Schema and SOAP Data Model Martin Gudgin
• Re: issue: optional "name" attribute of <definition> Sanjiva Weerawarana

Tuesday, 25 June 2002

• Re: Proposal for dealing with solicit/response and notification Prasad Yendluri
• Re: issue 57: Should Operations permit alternate and multiple responses? Prasad Yendluri
• Re: issue 60: Text in the WSDL spec inconsistency about optional parts Prasad Yendluri
• Re: issue: optional "name" attribute of <definition> Joyce Yang
• Re: Proposal to Resolve encodingStyle Issues #5 and #30 Jacek Kopecky
• Re: issue: optional "name" attribute of <definition> Jacek Kopecky
• Proposal to Resolve encodingStyle Issues #5 and #30 ryman@ca.ibm.com
• Re: issue: optional "name" attribute of <definition> sggraham@us.ibm.com
• Re: Target namespace in WSDL sggraham@us.ibm.com
• issue: optional "name" attribute of <definition> Sanjiva Weerawarana
• Re: Target namespace in WSDL Sanjiva Weerawarana
• Re: Ports, Names, Symbol Spaces and targetNamespace Sanjiva Weerawarana
• Re: Abstract model ednote? Sanjiva Weerawarana
• Re: Minutes 20 June 2002 WS Desc telcon Jean-Jacques Moreau
• Minutes 20 June 2002 WS Desc telcon michael.mahan@nokia.com
• Re: SOAP Binding Faults Jean-Jacques Moreau
• Issue 4: Use of namespace attribute on soap:body Martin Gudgin
• Target namespace in WSDL Martin Gudgin
• Abstract model ednote? Jean-Jacques Moreau
• Ports, Names, Symbol Spaces and targetNamespace Martin Gudgin
• Fw: Draft agenda: 24 June TAG teleconference (Arch document, WSA update) Sanjiva Weerawarana

Monday, 24 June 2002

• RE: updated editor's copy of WSDL 1.2 spec Jonathan Marsh
• Re: updated editor's copy of WSDL 1.2 spec Sanjiva Weerawarana
• RE: updated editor's copy of WSDL 1.2 spec Martin Gudgin
• Re: updated editor's copy of WSDL 1.2 spec Sanjiva Weerawarana
• RE: updated editor's copy of WSDL 1.2 spec Martin Gudgin
• RE: Rationale to close the operation overloading issue Jochen.Ruetschlin@DaimlerChrysler.com
• Re: updated editor's copy of WSDL 1.2 spec Sanjiva Weerawarana
• Re: Rationale to close the operation overloading issue Jochen.Ruetschlin@DaimlerChrysler.com
• RE: updated editor's copy of WSDL 1.2 spec Martin Gudgin
• Re: updated editor's copy of WSDL 1.2 spec Jean-Jacques Moreau

Friday, 21 June 2002

• RE: Rationale to close the operation overloading issue ryman@ca.ibm.com
• Re: updated editor's copy of WSDL 1.2 spec Sanjiva Weerawarana
• RE: Proposal for dealing with solicit/response and notification Dale Moberg
• RE: Rationale to close the operation overloading issue Tom Jordahl
• Re: updated editor's copy of WSDL 1.2 spec Jean-Jacques Moreau
• updated editor's copy of WSDL 1.2 Part 2: Bindings Jean-Jacques Moreau
• RE: Rationale to close the operation overloading issue Jochen.Ruetschlin@DaimlerChrysler.com
• Re: Rationale to close the operation overloading issue mario.jeckle@daimlerchrysler.com
• RE: issue 43: Does order matter for the child elements of "definitions"? Martin Gudgin

Thursday, 20 June 2002

• ACTION: All WG members to review redundancy issues by next week Jonathan Marsh
• Re: Rationale to close the operation overloading issue David Booth
• RE: Rationale to close the operation overloading issue ryman@ca.ibm.com
• RE: Rationale to close the operation overloading issue Jeff Mischkinsky
• RE: Rationale to close the operation overloading issue ryman@ca.ibm.com
• late regrets jpauhlsson@echangeur.fr
• Re: issue 34: Should portTypes be extensible? Jean-Jacques Moreau
• Re: issue 26: transmission primitives Jean-Jacques Moreau
• Re: issue 57: Should Operations permit alternate and multiple responses? Jean-Jacques Moreau
• Re: issue 57: Should Operations permit alternate and multiple responses? Jean-Jacques Moreau
• Re: Issues 35, 36, 37 Jean-Jacques Moreau
• Re: issue 38: Clarify the what kinds of extensibility elements go where Jean-Jacques Moreau
• RE: issue 60: Text in the WSDL spec inconsistency about optional parts Jeffrey Schlimmer
• RE: issue 57: Should Operations permit alternate and multiple responses? Jeffrey Schlimmer
• RE: issue 26: transmission primitives Jeffrey Schlimmer
• RE: issue 38: Clarify the what kinds of extensibility elements go where Jeffrey Schlimmer
• RE: Rationale to close the operation overloading issue Jochen.Ruetschlin@DaimlerChrysler.com
• RE: issue 34: Should portTypes be extensible? Jeffrey Schlimmer
• RE: Issues 35, 36, 37 Jeffrey Schlimmer
• RE: Text for extensibility section Sedukhin, Igor
• Issues 35, 36, 37 Glen Daniels
• RE: issue 38: Clarify the what kinds of extensibility elements go where Glen Daniels
• RE: issue 43: Does order matter for the child elements of "defini tions"? Glen Daniels
• issue 42: Shall "element" attribute of "part" only refer to elements defined in schema? Sanjiva Weerawarana
• issue "issue-clarify elements" Sanjiva Weerawarana
• updated editor's copy of WSDL 1.2 spec Sanjiva Weerawarana
• issue 26: transmission primitives Sanjiva Weerawarana
• issue 34: Should portTypes be extensible? Sanjiva Weerawarana
• issues 35 & 36 Sanjiva Weerawarana
• issue 37: Should we remove parameter order? Sanjiva Weerawarana
• issue 38: Clarify the what kinds of extensibility elements go where Sanjiva Weerawarana
• issue 43: Does order matter for the child elements of "definitions"? Sanjiva Weerawarana
• issue 57: Should Operations permit alternate and multiple responses? Sanjiva Weerawarana
• issue 60: Text in the WSDL spec inconsistency about optional parts Sanjiva Weerawarana
• Re: WSDL Version 1.2 Part 2: Bindings, date 2002/4/11 Jean-Jacques Moreau
• Proposal for dealing with solicit/response and notification Jacek Kopecky

Wednesday, 19 June 2002

• Agenda for 20 June 2002 WS Description WG Jonathan Marsh
• RE: issue: service type ryman@ca.ibm.com
• RE: WSDL Version 1.2 Part 2: Bindings, date 2002/4/11 Jeffrey Schlimmer
• WSDL Version 1.2 Part 2: Bindings, date 2002/4/11 Carl Binding
• Regrets for 6-20 call Liu, Kevin
• Re: MEP and Operations FABLET Youenn
• RE: W3C WSDL WG Issues: Non-SOAP HTTP Binding Jeffrey Schlimmer

Tuesday, 18 June 2002

• RE: Text for extensibility section Sedukhin, Igor
• RE: Text for extensibility section Jeffrey Schlimmer
• RE: Text for extensibility section Sedukhin, Igor
• RE: issue: service type Jeffrey Schlimmer
• RE: Text for extensibility section Jeffrey Schlimmer
• RE: Text for extensibility section Jeffrey Schlimmer
• RE: proposal for resolving service type issues Jeffrey Schlimmer
• RE: proposal for resolving service type issues Jeffrey Schlimmer
• RE: MEP and Operations Jeffrey Schlimmer

Monday, 17 June 2002

• RE: Rationale to close the operation overloading issue Jonathan Marsh
• RE: Rationale to close the operation overloading issue Gaertner, Dietmar
• Re: Rationale to close the operation overloading issue butek@us.ibm.com
• Re: Rationale to close the operation overloading issue Sanjiva Weerawarana
• Re: Rationale to close the operation overloading issue Jochen.Ruetschlin@DaimlerChrysler.com
• Re: MEP and Operations FABLET Youenn

Sunday, 16 June 2002

• Re: Rationale to close the operation overloading issue Sanjiva Weerawarana

Friday, 14 June 2002

• Re: Rationale to close the operation overloading issue Jochen.Ruetschlin@DaimlerChrysler.com
• Re: Rationale to close the operation overloading issue Jean-Jacques Moreau
• Re: MEP and Operations Jean-Jacques Moreau
• Re: Rationale to close the operation overloading issue Jochen.Ruetschlin@DaimlerChrysler.com

Thursday, 13 June 2002

• Raw Minutes from 6-11 AM Lind, Steven D, ALASO
• Rationale to close the operation overloading issue Joyce Yang
• RE: MEP and Operations Dale Moberg
• Re: I will not be able to attend the today's conference call Jean-Jacques Moreau
• Re: Regrets Sanjiva Weerawarana
• Regrets don@lexmark.com
• operation overloading issue Sanjiva Weerawarana
• I will not be able to attend the today's conference call Sadiq, Waqar
• Re: proposal for resolving service type issues Jean-Jacques Moreau
• MEP and Operations FABLET Youenn

Wednesday, 12 June 2002

• RE: Text for extensibility section Sedukhin, Igor
• Architecture WG Requirements vis-a-vis WSDL WG Requirements Jeffrey Schlimmer
• Raw minutes for Tuesday afternoon Roberto Chinnici
• Fwd: Analysis of WSD Requirements by WS Arch Philippe Le Hegaret
• Analysis of WSD Requirements by WS Arch Christopher Ferris
• RE: an image processing use case for wsdl ryman@ca.ibm.com

Tuesday, 11 June 2002

• Re: Text for extensibility section Jean-Jacques Moreau
• Notes on the flip chart Hao He
• Re: proposal for resolving service type issues sggraham@us.ibm.com
• RE: an image processing use case for wsdl Hao He
• Re: an image processing use case for wsdl ryman@ca.ibm.com
• an image processing use case for wsdl Hao He
• RE: Second draft June FTF Agenda - issues to be discussed Liu, Kevin
• Draft primer outline David Booth
• raw minutes from Monday AM Sanjiva Weerawarana
• raw minutes from 2002-06-10 afternoon Philippe Le Hegaret
• Re: Fw: [soapbuilders] NMTokens, NCNames, PortTypes, and Bindings. Prasad Yendluri
• Re: proposal for resolving service type issues Sanjiva Weerawarana
• Re: proposal for resolving service type issues Steve Tuecke
• Text for extensibility section Glen Daniels
• Fw: [soapbuilders] NMTokens, NCNames, PortTypes, and Bindings. Sanjiva Weerawarana

Monday, 10 June 2002

• Re: proposal for resolving service type issues Sanjiva Weerawarana
• Re: proposal for resolving service type issues Jean-Jacques Moreau
• SOAP Binding Faults James M Snell
• Re: Fw: issue: service type ryman@ca.ibm.com

Saturday, 8 June 2002

• proposal for resolving service type issues Sanjiva Weerawarana

Friday, 7 June 2002

• Second draft June FTF Agenda Jonathan Marsh
• Minutes, 6 June 2002 WS Description telcon Jonathan Marsh

Thursday, 6 June 2002

• RE: SOAP Binding: Is body/@use required? Jeffrey Schlimmer
• Extensibility proposal from today Roberto Chinnici
• Re: issue: service type Jacek Kopecky
• RE: issue: service type Jacek Kopecky
• RE: Editorial issue - Terminology for Operation types David Booth
• RE: FTF meeting questions food Dilber, Ayse, ALASO
• Re: ISSUE : Extensible message exchange patterns Christopher Ferris
• Re: ISSUE : Extensible message exchange patterns Glen Daniels
• Re: [amtf] my view of what the Abstract model should do and why FABLET Youenn
• Re: issue: service type Sanjiva Weerawarana
• RE: issue: service type Jeffrey Schlimmer
• Re: ISSUE : Extensible message exchange patterns Jean-Jacques Moreau
• Re: ISSUE : Extensible message exchange patterns Christopher Ferris
• RE: issue: service type David Booth
• RE: ISSUE : Extensible message exchange patterns Jeffrey Schlimmer
• Re: ISSUE : Extensible message exchange patterns Sanjiva Weerawarana
• Re: Doubly revised extensibility proposal Roberto Chinnici
• RE: Doubly revised extensibility proposal Jeffrey Schlimmer
• RE: ISSUE : Extensible message exchange patterns Jeffrey Schlimmer
• SOAP Binding: Is body/@use required? Jeffrey Schlimmer
• Re: Doubly revised extensibility proposal Roberto Chinnici

Wednesday, 5 June 2002

• RE: Reminder: WS Desc telcon Thursday 6 June 2002 Swearingen Sandra Civ AFCA/ITCM
• Agenda for 6 June 2002 WS Description WG Jonathan Marsh
• WS Desc WG Usage Scenarios published David Booth
• Re: Issue: Text in the WSDL spec inconsistency about optional parts Jean-Jacques Moreau
• RE: issue: service type Jacek Kopecky
• Re: Fw: issue: service type Jacek Kopecky
• Re: Issue: Text in the WSDL spec inconsistency about optional parts Prasad Yendluri
• [amtf] my view of what the Abstract model should do and why Jacek Kopecky
• Re: Issue: Text in the WSDL spec inconsistency about optional parts Jean-Jacques Moreau
• Re: New issue: Representing safe operations (was: [TAG] how to use GET to make resources addressable) Jean-Jacques Moreau
• Re: issue: service type Sanjiva Weerawarana

Tuesday, 4 June 2002

• Issue: Text in the WSDL spec inconsistency about optional parts Prasad Yendluri
• Re: Issue: SOAP binding violates separation of abstract definitionsconcrete bindings Prasad Yendluri
• RE: Issue: SOAP binding violates separation of abstract definitions concrete bindings David Cleary
• Re: Issue: SOAP binding violates separation of abstract definitions concrete bindings Prasad Yendluri
• RE: issue: service type Matt Long
• Issue: SOAP binding violates separation of abstract definitions concrete bindings Prasad Yendluri
• RE: Doubly revised extensibility proposal Jonathan Marsh
• RE: New issue: Representing safe operations (was: [TAG] how to use GET to make resources addressable) Paul Cotton
• Re: New issue: Representing safe operations (was: [TAG] how to use GET to make resources addressable) Sanjiva Weerawarana
• Fw: issue: service type Sanjiva Weerawarana

Monday, 3 June 2002

• RE: Doubly revised extensibility proposal Sedukhin, Igor
• Re: Doubly revised extensibility proposal Roberto Chinnici

Last message date: Sunday, 30 June 2002 15:05:21 UTC