Friday, 30 July 2004
- WSDL 2.0 part two last call last call
- Re: Proposed revised abstract
- Re: Minutes: 29 July 2004 telcon
- RE: Proposed revised abstract
- Re: Edits to part 2
- RE: Proposed revised abstract
- Proposed revised abstract
- Re: Edits to part 2
- RE: Edits to part 2
- Re: Edits to part 2
- Re: Minutes: 29 July 2004 telcon
- Re: Minority objection to features and properties
Thursday, 29 July 2004
- RE: Minutes: 29 July 2004 telcon
- Re: Minutes: 29 July 2004 telcon
- RE: Minutes: 29 July 2004 telcon
- Re: Minutes: 29 July 2004 telcon
- Minutes: 29 July 2004 telcon
- Web page
- RE: 'ad:mustUnderstand', Schema Annotation Element? (was RE: Few more (significant) edits
- RE: 'ad:mustUnderstand', Schema Annotation Element? (was RE: Few more (significant) edits
- RE: 'ad:mustUnderstand', Schema Annotation Element? (was RE: Few more (significant) edits
- Re: 'ad:mustUnderstand', Schema Annotation Element? (was RE: Few more (significant) edits
- Re: pls review text added for what "required" means
- RE: Few more (significant) edits
- on "binding" the AD feature: where does the text go?
- Re: Few more (significant) edits
- RE: Few more (significant) edits
- Re: Few more (significant) edits
- FW: Issue 189 proposals:
- Re: Part 2 Features stuff
- Minority objection to requiring unique GEDs or required feature to distinguish operations
- Minority objection to features and properties
- Re: pls review text added for what "required" means
- Re: pls review text added for what "required" means
- Re: pls review text added for what "required" means
- Minority Opinon re: Compositors [IONA, Oracle, Sonic, Sun]
- Part 3: Added Application Feature; pending questions (was Re: Review LC drafts now!)
- Re: Intermediaries?
- [1st draft] Agenda: 2-4 August 2004 WS Description WG FTF
Wednesday, 28 July 2004
- Re: pls review text added for what "required" means
- Intermediaries?
- RE: help with incorporating operation name v3 proposal (issue 168)
- Re: help with incorporating operation name v3 proposal (issue 168)
- Re: help with incorporating operation name v3 proposal (issue 168)
- Re: Review LC drafts now!
- 'ad:mustUnderstand', Schema Annotation Element? (was RE: Few more (significant) edits
- RE: Review LC drafts now!
- Re: Issue 189 proposals:
- Re: help with incorporating operation name v3 proposal (issue 168)
- Few more (significant) edits
Tuesday, 27 July 2004
- RE: help with incorporating operation name v3 proposal (issue 168)
- Re: help with incorporating operation name v3 proposal (issue 168)
- Part 2 Features stuff
- RE: Issue 189 proposals:
- RE: Issue 189 proposals:
- Re: Describing which blobs are to be optimized.
- Re: Issue 189 proposals:
- RE: Issue 189 proposals:
- RE: Issue 189 proposals:
- RE: Issue 189 proposals:
- Review LC drafts now!
- [final] Agenda, 29 July 2004 WS Desc telcon
- RE: [Issue 165] Re: What happened about HTTPS in the HTTP binding?
- Re: help with incorporating operation name v3 proposal (issue 168)
- RE: Issue 189 proposals:
- Re: Issue 189 proposals:
Monday, 26 July 2004
- Re: Describing which blobs are to be optimized.
- RE: Requiredness (two issues)
- Re: Requiredness (two issues)
- Re: Requiredness (two issues)
- RE: help with incorporating operation name v3 proposal (issue 168)
- RE: Issue 189 proposals:
- RE: help with incorporating operation name v3 proposal (issue 168)
- pls review text added for what "required" means
- RE: Issue 189 proposals:
- Fw: request for clarification on closing issue 211
- Re: Issue 189 proposals:
- RE: Issue 189 proposals:
- help with incorporating operation name v3 proposal (issue 168)
- Re: Issue 189 proposals:
- no SOAP binding for in-only operations? :-(
- Re: Describing which blobs are to be optimized.
- Re: Composition model
- Composition model
- Re: Some new text
- Re: Requiredness (two issues)
- Some new text
- Requiredness (two issues)
- Re: Issue 189 proposals:
- Re: Issue 189 proposals:
Friday, 23 July 2004
- Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Re: [Issue 165] Re: What happened about HTTPS in the HTTP binding?
- [Issue 165] Re: What happened about HTTPS in the HTTP binding?
- RE: Minutes, 22 July 2004 Web Services Description WG telcon
- What happened about HTTPS in the HTTP binding?
Thursday, 22 July 2004
- [draft] Agenda, 29 July 2004 WS Desc telcon
- RE: Minutes, 22 July 2004 Web Services Description WG telcon
- Minutes, 22 July 2004 Web Services Description WG telcon
- FW: [corrected] Minutes, 15 July 2004 WS Desc telcon
- Re: Resolution of issue 168
- SOAP 11 Binding: Strawman Proposal B
- Schemas for SOAP and HTTP Binding
- RE: [Issue 226] Re: Cross-binding HTTP Features
- Editorial Issue: Part 3 SOAP Binding
- Re: [final] Agenda, 22 July 2004 WS Desc telcon
- HTTP binding: unknown editorial note
- Re: Resolution of issue 168
- [final] Agenda, 22 July 2004 WS Desc telcon
- Proposed resolution for Issue 206
- Proposed Resolution for Issue 205
- Proposed resolution for Issue 201
- CORRECTION Proposed Resolution for Issue 162
- Proposed Resolution for Issue 161:
- Re: Issue 162:
- Issue 162:
Wednesday, 21 July 2004
- Re: Property component's dependency on XML Schema
- Re: HTTP binding mismatch and identification missing
- Re: HTTP binding mismatch and identification missing
- [Issue 226] Re: Cross-binding HTTP Features
- RE: HTTP binding mismatch and identification missing
- HTTP binding mismatch and identification missing
- Re: Part 1: Component reference vs. QName
Tuesday, 20 July 2004
- Property component's dependency on XML Schema
- Which came first, the function or the binding?
- Re: Resolution of issue 168
- Resolution of issue 168
- HTTP binding and interface operation MEP
- RE: FW: Action Item 2004-07-01 Solution to 168/R114
- RE: Part 1: Component reference vs. QName
Monday, 19 July 2004
- Issue 189 proposals:
- Re: Part 1: Component reference vs. QName
- Re: Part 1: Component reference vs. QName
- Re: Part 1: Component reference vs. QName
- XMLP Issue 468 closed
- Re: Part 1: Component reference vs. QName
Saturday, 17 July 2004
Friday, 16 July 2004
- Re: Part 1: Component reference vs. QName
- RE: Decouple SOAP Version from SOAP Binding ?
- Re: Minutes, 15 July 2004 WS Desc telcon
- [draft] Agenda, 15 July 2004 WS Desc telcon
- Re: Minutes, 8 July 2004 WS Desc telcon
- Re: Action item: HTTP binding for accepts header and output Serialization.
- Re: Editorial comments on Part 3
- Re: Action item: HTTP binding for accepts header and output Serialization.
- Re: Decouple SOAP Version from SOAP Binding ?
- RE: Part 1: Component reference vs. QName
- RE: Decouple SOAP Version from SOAP Binding ?
Thursday, 15 July 2004
- Minutes, 15 July 2004 WS Desc telcon
- Issue 166 - Binding of Faults in HTTP Binding
- Re: FW: Action Item 2004-07-01 Solution to 168/R114
- Re: FW: Action Item 2004-07-01 Solution to 168/R114
- RE: issue 235: definition of Fault
- issue 235: definition of Fault
- RE: Decouple SOAP Version from SOAP Binding ?
- RE: Part 1: Component reference vs. QName
- Decouple SOAP Version from SOAP Binding ?
- Part 1: Component reference vs. QName
- RE: FW: Action Item 2004-07-01 Solution to 168/R114
- RE: FW: Action Item 2004-07-01 Solution to 168/R114
- RE: FW: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: FW: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: [final] Agenda, 15 July 2004 WS Desc telcon
- RE: Action Item 2004-07-01 Solution to 168/R114
Wednesday, 14 July 2004
- Re: Describing which blobs are to be optimized.
- [final] Agenda, 15 July 2004 WS Desc telcon
- RE: Minutes, 8 July 2004 WS Desc telcon
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: FW: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- FW: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Some notes on Part 1
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
Tuesday, 13 July 2004
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Part 1: Editorial Issues
- Re: Part 1: Editorial Issues
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: AD Feature: HTTP header conflicts
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- updating/verifying the URI refs section (appendix C)
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Revised Asynch Binding
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: AD Feature: HTTP header conflicts
Monday, 12 July 2004
Tuesday, 13 July 2004
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- discussion style (was: Re: Revised Asynch Binding)
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
Monday, 12 July 2004
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Revised Asynch Binding
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Minutes, 8 July 2004 WS Desc telcon
- Re: AD Feature: HTTP header conflicts
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Part 1: Editorial Issues
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Revised Asynch Binding
- RE: Revised Asynch Binding
- RE: updated draft to put F&P in more places
- RE: Revised Asynch Binding
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Revised Asynch Binding
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Revised Asynch Binding
- Re: "operation name" .. an alternate proposal
Friday, 9 July 2004
- [draft] Agenda, 15 July 2004 WS Desc telcon
- Re: "operation name" .. an alternate proposal
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- AD Feature: HTTP header conflicts
- Re: "operation name" .. an alternate proposal
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: "operation name" .. an alternate proposal
- RE: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- Re: Issue 177: XML 1.1 support
- Re: Issue 177: XML 1.1 support
- Re: Action Item 2004-07-01 Solution to 168/R114
Thursday, 8 July 2004
- Re: "operation name" .. an alternate proposal
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- Part 1: Editorial Issues
- Minutes, 8 July 2004 WS Desc telcon
- Re: "operation name" .. an alternate proposal
- Re: "operation name" .. an alternate proposal
- Re: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: "operation name" .. an alternate proposal
- RE: Revised Asynch Binding
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Revised Asynch Binding
- RE: Revised Asynch Binding
- Re: Revised Asynch Binding
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: "operation name" .. an alternate proposal
- RE: Issue 177: XML 1.1 support
- RE: Issue 177: XML 1.1 support
- "operation name" .. an alternate proposal
- RE: Atom API in WSDL 2.0
- Re: Revised Asynch Binding
- RE: Revised Asynch Binding
- Fw: Revised Asynch Binding
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Revised Asynch Binding
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Issue 177: XML 1.1 support
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Issue 177: XML 1.1 support
- Re: Revised Asynch Binding
- Re: Revised Asynch Binding
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Action Item 2004-07-01 Solution to 168/R114
Wednesday, 7 July 2004
- Re: Revised Asynch Binding
- RE: Revised Asynch Binding
- Re: Revised Asynch Binding
- RE: Action Item 2004-07-01 Solution to 168/R114
- input serialization flexibility
- RE: Revised Asynch Binding
- Re: Revised Asynch Binding
- Re: Action Item 2004-07-01 Solution to 168/R114
- Re: Allowable content in the types element
- RE: Revised Asynch Binding
- RE: Action Item 2004-07-01 Solution to 168/R114
- Re: Revised Asynch Binding
- Agenda, 8 July 2004 WS Desc telcon
- RE: Application Data Feature and related stuff
- RE: Action Item 2004-07-01 Solution to 168/R114
- RE: Action Item 2004-07-01 Solution to 168/R114
Tuesday, 6 July 2004
- Issue 189: Binding message content to URI
- 169 Syntax for webMethod - property or attribute?
- Re: [Draft] Agenda, 8 July 2004 WS Desc telcon
- RE: Revised Asynch Binding
- RE: Revised Asynch Binding
- Re: Revised Asynch Binding
- Re: Revised Asynch Binding
Monday, 5 July 2004
- Atom API in WSDL 2.0
- RE: Revised Asynch Binding
- Issue 233: Dynamically Override Fault Destinations (proposal)
- Issue 230: {message label} vs {label}
- Allowable content in the types element
- Issue 220: Document interface extension semantics
- RE: Revised Asynch Binding
- Re: Issue 211: Omitting interface messages in bindings
- Re: Revised Asynch Binding
- Re: which async binding/operation? (was Revised Asynch Binding)
- Re: Revised Asynch Binding
- which async binding/operation? (was Revised Asynch Binding)
- RE: Revised Asynch Binding
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
Sunday, 4 July 2004
Saturday, 3 July 2004
- Re: Issue 228 [was RE: updated draft to put F&P in more places]
- New Issue: MTOM/XOP support, probably editorial
- Action Item 2004-07-01 Solution to 168/R114
Friday, 2 July 2004
- Issue 488 closed
- [Draft] Agenda, 8 July 2004 WS Desc telcon
- Issue 228 [was RE: updated draft to put F&P in more places]
- Re: Issue 232 [was RE: Issues 227, 231, 234, 235 plus 226, 227, 232]
- Re: Agenda, 1 July 2004 WS Desc telcon
- Re: Issue 232 [was RE: Issues 227, 231, 234, 235 plus 226, 227, 232]
- Issue 232 [was RE: Issues 227, 231, 234, 235 plus 226, 227, 232]
- Re: absolute vs. relative URIs?
- RE: absolute vs. relative URIs?
- RE: absolute vs. relative URIs?
- Fw: Minutes, 24 June 2004 WS Desc telcon
- absolute vs. relative URIs?
- Re: Issues 227, 231, 234, 235 plus 226, 227, 232
- RE: Issues 227, 231, 234, 235 plus 226, 227, 232
Thursday, 1 July 2004
- Issue 195 [was RE: Features and Properties versus Extensions]
- Issues 227, 231, 234, 235
- Minutes: 1 July 2004 WS Desc telcon
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- How to add links to other documents using xmlspec
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Agenda, 1 July 2004 WS Desc telcon
- Re: Issue 168 (Which Operation?) / Requirement R114
- Re: Issue 168 (Which Operation?) / Requirement R114
- Editorial comments on Part 3
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 168 (Which Operation?) / Requirement R114
- Resolution of Issue 489
- Re: Action item: HTTP binding for accepts header and output Serialization.
- Re: Issue 168 (Which Operation?) / Requirement R114
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.