Friday, 31 May 2002
- RE: FTF meeting questions food
- RE: MEPs: Hardcoded or not? (was: Re: Minutes of teleconference02-05-23)
- RE: Doubly revised extensibility proposal
- Re: ISSUE : Extensible message exchange patterns
- Re: MEPs: Hardcoded or not? (was: Re: Minutes of teleconference02-05-23)
- RE: ISSUE : Extensible message exchange patterns
- Re: MEPs: Hardcoded or not? (was: Re: Minutes of teleconference02-05-23)
- Re: ISSUE : Extensible message exchange patterns
- Re: ISSUE : Extensible message exchange patterns
- Re: Minutes 30 May 2002 WS Desc telcon (plain text)
Thursday, 30 May 2002
- Minutes 30 May 2002 WS Desc telcon (plain text)
- Minutes 30 May 2002 WS Desc telcon
- FTF meeting questions food
- RE: ISSUE : Extensible message exchange patterns
- RE: Editorial issue - Terminology for Operation types
- Regarding your upcoming proposal for requiredness in extensions
- RE: Regarding your upcoming proposal for requiredness in extensio ns
- resolving issue-message-parts
- RE: Doubly revised extensibility proposal
- Re: Doubly revised extensibility proposal
- Re: Doubly revised extensibility proposal
- Re: Doubly revised extensibility proposal
- RE: Doubly revised extensibility proposal
- RE: Doubly revised extensibility proposal
- ISSUE : Extensible message exchange patterns
- Re: Doubly revised extensibility proposal
- RE: Doubly revised extensibility proposal
- Re: [amtf] Thought on the abstractness and modelness of my proposal
- Re: MEPs: Hardcoded or not? (was: Re: Minutes of teleconference02-05-23)
- Re: Doubly revised extensibility proposal
- RE: Doubly revised extensibility proposal
- RE: Doubly revised extensibility proposal
- RE: Doubly revised extensibility proposal
- Re: Draft wording for <import>
- Re: Doubly revised extensibility proposal
- RE: Doubly revised extensibility proposal
Wednesday, 29 May 2002
- Agenda for 30 May 2002 WS Description WG
- Re: [amtf] Thought on the abstractness and modelness of my proposal
- Re: [amtf] Thought on the abstractness and modelness of my proposal
Thursday, 30 May 2002
Wednesday, 29 May 2002
Tuesday, 28 May 2002
- RE: Draft wording for <import>
- RE: Doubly revised extensibility proposal
- RE: Extensions
- Doubly revised extensibility proposal
- Re: Extensions
- RE: Extensions
- Re: Extensions
- RE: Extensions
- Re: MEPs: Hardcoded or not? (was: Re: Minutes of teleconference 02-05-23)
- Re: Draft wording for <import>
- Re: WSDL 1.2: be infoset based on not? (was: Re: Draft wording for <import>)
- RE: [amtf] 2002/5/23 telcon summary
- Re: Extensions
- RE: Editorial issue - Terminology for Operation types
- RE: Fw: [wsdl] Charact-set encoding - how to specify in WSDL?
Monday, 27 May 2002
- RE: WSDL 1.2: be infoset based on not? (was: Re: Draft wording for <import>)
- Re: Draft wording for <import>
- WSDL 1.2: be infoset based on not? (was: Re: Draft wording for <import>)
- [amtf] 2002/5/23 telcon summary
- RE: Issue: should WSDL allow overloaded methods?
- Draft wording for <import>
Friday, 24 May 2002
- Issue: (recast) Notification of Failures Only MEP (Negative Acks?)
- RE: Issue: should WSDL allow overloaded methods?
- Re: Issue: should WSDL allow overloaded methods?
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: Can One-Way operations return faults?
- MEPs: Hardcoded or not? (was: Re: Minutes of teleconference 02-05-23)
- Re: Fw: [wsdl] Charact-set encoding - how to specify in WSDL?
Thursday, 23 May 2002
- Extensions
- RE: Issue: Can One-Way operations return faults?
- Minutes of teleconference 02-05-23
- Re: Issue: should WSDL allow overloaded methods?
- RE: Fw: [wsdl] Charact-set encoding - how to specify in WSDL?
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: should WSDL allow overloaded methods?
- RE: Issue: Can One-Way operations return faults?
- RE: Issue: Can One-Way operations return faults?
- RE: Revised extensibility proposal
- RE: Revised extensibility proposal
- RE: Revised extensibility proposal
- RE: Revised extensibility proposal
- Re: Issue:soap:body binding description confusing when use is "literal"
- RE: Issue: should WSDL allow overloaded methods?
- Re: proposed issue: Support for non-named-operation oriented portTypes
- Re: Issue: Can One-Way operations return faults?
- (CfP) Web Services -- Research, Standardization, and Deployment
- Re: Issue: should WSDL allow overloaded methods?
- Re: Issue: should WSDL allow overloaded methods?
- Re: Issue: should WSDL allow overloaded methods?
- Re: Issue:soap:body binding description confusing when use is "literal"
- Re: Revised extensibility proposal
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: should WSDL allow overloaded methods?
- RE: Issue: Can One-Way operations return faults?
- RE: Revised extensibility proposal
- Re: Issue: should WSDL allow overloaded methods?
Wednesday, 22 May 2002
- Re: Revised extensibility proposal
- Re: [amtf] Multiple responses? (was: Re: First shot at Abstract Model)
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: should WSDL allow overloaded methods?
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: Can One-Way operations return faults?
- Agenda for 23 May 2002 WS Description WG
- RE: Revised extensibility proposal
- Re: Issue: Can One-Way operations return faults?
- Re: Issue: Can One-Way operations return faults?
- RE: Revised extensibility proposal
- Re: Revised extensibility proposal
- RE: Revised extensibility proposal
- RE: Revised extensibility proposal
- Re: Revised extensibility proposal
- Re: Issue: should inout parameters be of the same type?
- Re: Issue: Can One-Way operations return faults?
- Re: proposed issue: Support for non-named-operation oriented portTypes
- [amtf] ServiceType? Service with multiple interfaces? (was: Re: First shot at Abstract Model)
- [amtf] incoming and outgoing operations? (was: Re: First shot at AbstractModel)
- Re: Issue: Can One-Way operations return faults?
- [amtf] Multiple responses? (was: Re: First shot at Abstract Model)
- Re: [amtf] First shot at Abstract Model
- Re: Issue: should WSDL allow overloaded methods?
- Re: Fw: [wsdl] Charact-set encoding - how to specify in WSDL?
- Re: WSDL Spec - SOAP Examples
- Re: Issue: should WSDL allow overloaded methods?
Tuesday, 21 May 2002
- Re: [amtf] First shot at Abstract Model
- Issue: Can One-Way operations return faults?
- Re: Revised extensibility proposal
- Re: proposed issue: Support for non-named-operation oriented portTypes
- RE: Revised extensibility proposal
- Re: Revised extensibility proposal
- RE: Revised extensibility proposal
- RE: Revised extensibility proposal
- Re: Extending port types (AKA a scenario for UPnP)
- New issue: Representing safe operations (was: [TAG] how to use GET to make resources addressable)
- Re: Revised extensibility proposal
Monday, 20 May 2002
Tuesday, 21 May 2002
Monday, 20 May 2002
Sunday, 19 May 2002
Saturday, 18 May 2002
Friday, 17 May 2002
- proposed issue: Support for non-named-operation oriented portTypes
- Revised extensibility proposal
- Re: W3C WSDL WG: 6b. Define encoding for non-ASCII characters in request URL
- RE: update part1 docs (editors' drafts) .. - issue with wsdl vers ioning and service identity
- Re: Issues 6a, 6d, 41. Define encoding into a request URL
- RE: update part1 docs (editors' drafts) .. - issue with name scop e of top elements
Thursday, 16 May 2002
- update part1 docs (editors' drafts) ..
- Re: Issue: should inout parameters be of the same type?
- Re: Issue: should inout parameters be of the same type?
- Re: Issue: should inout parameters be of the same type?
- proposed issue and resolution: eliminate <message> construct
- Re: Issue: should inout parameters be of the same type?
- Use case for Publish/Subscribe - Push Model
- Raw telconf minutes, 20020516
- Issue: should inout parameters be of the same type?
- Regrets for today's teleconference
- Regrets for today's telcon
- Usecase document
- Minutes of the 09 May 2002 WS Description WG telcon
- RE: issue: optional parts in <message>?
Wednesday, 15 May 2002
- Agenda for 16 May 2002 WS Description WG
- Re: issue: optional parts in <message>?
- Minutes 9 May 2002 Telcon
Tuesday, 14 May 2002
Saturday, 11 May 2002
- Re: issue: optional parts in <message>?
- Re: Random thoughts on the Abstract Model Task Force (AMTF)
- Random thoughts on the Abstract Model Task Force (AMTF)
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
Thursday, 9 May 2002
- Re: Issue:soap:body binding description confusing when use is "literal"
- RE: Extensibility proposal
- RE: Extensibility proposal
- RE: Extending port types (AKA a scenario for UPnP)
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- RE: W3C WSDL WG: 6b. Define encoding for non-ASCII characters in request URL
Wednesday, 8 May 2002
- Re: Extensibility proposal
- Agenda for 9 May 2002 WS Description WG
- RE: Extensibility proposal
- RE: Extensibility proposal
- Re: issue: optional parts in <message>?
- Re: Conflicts of WSDL schemas
- Re: Extensibility proposal
- Issue: WSDL must import schemas if types from them are used
Tuesday, 7 May 2002
- Re: Issues 6a, 6d, 41. Define encoding into a request URL
- Issue:soap:body binding description confusing when use is "literal"
- RE: Extensibility proposal
- Re: issue: optional parts in <message>?
- Extensibility proposal
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: language extensibility [was: updated part1 draft's (editor's copy)]
- RE: language extensibility [was: updated part1 draft's (editor's copy)]
- RE: extensions [was: updated part1 docs (editor's drafts)]
- Re: issue: optional parts in <message>?
- Regrets Conf call 9/5
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: import/include issue
- Re: import/include issue
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- updated part1 draft's (editor's copy)
- issue: service type
- issue: portType extensibility
- import/include issue
Monday, 6 May 2002
- Re: issue: optional parts in <message>?
- Issue: should WSDL allow overloaded methods?
- RE: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: W3C WSDL WG: 6b. Define encoding for non-ASCII characters in request URL
- Re: Extending port types (AKA a scenario for UPnP)
Sunday, 5 May 2002
Saturday, 4 May 2002
- Re: Issue: Should Operations permit alternate and multiple responses
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
Friday, 3 May 2002
Saturday, 4 May 2002
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
Friday, 3 May 2002
- RE: issue: optional parts in <message>?
- Re: Issue: Should Operations permit alternate and multiple responses
- RE: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- RE: comment: documentation scenario and requirement
- RE: extensions [was: updated part1 docs (editor's drafts)]
- comment: documentation scenario and requirement
- Re: Final one for me RE: Issue: Should Operations permit alternate and multiple responses
Thursday, 2 May 2002
- RE: Minutes of teleconference 2002-05-02
- Minutes of teleconference 2002-05-02
- Re: Web Service Architecture Usage Scenarios editors copy available
- Re: Web Service Architecture Usage Scenarios editors copy available
- Final one for me RE: Issue: Should Operations permit alternate and multiple responses
- Comments on Web Service Usage Scenarios 23 April 2002
- Re: Web Service Architecture Usage Scenarios editors copy available
- RE: extensions [was: updated part1 docs (editor's drafts)]
- RE: extensions [was: updated part1 docs (editor's drafts)]
- RE: extensions [was: updated part1 docs (editor's drafts)]
- RE: Web Services Description Conference call minutes for April 18 , 20 02
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- Re: Issue: Should Operations permit alternate and multiple responses
- RE: events (was: Re: Draft minutes of 2002/04/25 telcon)
- RE: issue: optional parts in <message>?
- RE: More on extensibility
- RE: events (was: Re: Draft minutes of 2002/04/25 telcon)
- Re: issue: optional parts in <message>?
- Re: Issue: Should Operations permit alternate and multiple responses
- Re: issue: optional parts in <message>?
- Re: issue: optional parts in <message>?
- More on extensibility
- RE: Issue: Should Operations permit alternate and multiple responses
- Re: issue: optional parts in <message>?
- events (was: Re: Draft minutes of 2002/04/25 telcon)
- Re: Issue: Should Operations permit alternate and multiple responses
- RE: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- Web Service Architecture Usage Scenarios editors copy available
- Incorporation of WSD Usage Scenarios into WS Arch usage scenarios
Wednesday, 1 May 2002
- RE: Issue: Should Operations permit alternate and multiple responses
- RE: issue: optional parts in <message>?
- Agenda for 2 May 2002 WS Description WG
- Re: issue: optional parts in <message>?
- RE: issue: optional parts in <message>?
- W3C WSDL WG Issue: 6e. Define behavior for missing search pattern part
- RE: issue: optional parts in <message>?
- Re: import / include issue
- Re: issue: optional parts in <message>?
- Re: Issue: Should Operations permit alternate and multiple responses
- issue: optional parts in <message>?
- RE: import / include issue
- Re: import / include issue
- RE: import / include issue
- Re: import / include issue