Thursday, 1 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.
Wednesday, 30 June 2004
- Re: Issue 168 (Which Operation?) / Requirement R114
- RE: Issue 169: Propose http method in the operation interface to simplify http binding.
- Agenda, 1 July 2004 WS Desc telcon
- RE: Action item: HTTP binding for accepts header and output Serialization.
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Issue 168 (Which Operation?) / Requirement R114
- RE: updated draft to put F&P in more places
- RE: Issue 177: XML 1.1 support
- Issue 197 action: proposed text
- 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.
Tuesday, 29 June 2004
- Re: Issue 169: Propose http method in the operation interface to simplify http binding.
- Namespacing component properties
- 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.
- Issue 169: Propose http method in the operation interface to simplify http binding.
- Revised Asynch Binding
- RE: Application Data Feature and related stuff
- RE: Application Data Feature and related stuff
- RE: Application Data Feature and related stuff
- RE: Application Data Feature and related stuff
- Re: Application Data Feature and related stuff
- RE: Application Data Feature and related stuff
- RE: Application Data Feature and related stuff
- RE: Application Data Feature and related stuff
Monday, 28 June 2004
- Re: Issue 177: XML 1.1 support
- RE: Application Data Feature and related stuff
- Re: Issue 218 - Justify Interface Faults
- Re: updated draft to put F&P in more places
- Re: updated draft to put F&P in more places
- Re: Issue 218 - Justify Interface Faults
- Re: updated draft to put F&P in more places
Sunday, 27 June 2004
Friday, 25 June 2004
- Re: Issue 214: Refine "properties" terminology
- RE: Minutes, 24 June 2004 WS Desc telcon
- Re: Minutes, 24 June 2004 WS Desc telcon
- updated draft to put F&P in more places
- Re: Issue 130: Asynch request/response HTTP binding needed
- RE: Issue 130: Asynch request/response HTTP binding needed
- Re: Action item: HTTP binding for accepts header and output Serialization.
- Re: expectedMediaType and Accept header syntax (was Re: Action it em: HTTP binding for accepts header and output Serialization.)
- RE: Issue 130: Asynch request/response HTTP binding needed
- WS-Description WG's LC comments on XMLP specs
- Re: Issue 130: Asynch request/response HTTP binding needed
- Re: Issue 130: Asynch request/response HTTP binding needed
- Issue 177: XML 1.1 support
Thursday, 24 June 2004
- Minutes, 24 June 2004 WS Desc telcon
- Re: expectedMediaType and Accept header syntax (was Re: Action it em: HTTP binding for accepts header and output Serialization.)
- Re: Issue 130: Asynch request/response HTTP binding needed
- Re: Issue 130: Asynch request/response HTTP binding needed
- Re: Issue 130: Asynch request/response HTTP binding needed
- RE: Issue 130: Asynch request/response HTTP binding needed
- RE: Application Data Feature and related stuff
- RE: Application Data Feature and related stuff
- Re: Issue 169: Syntax for webMethod - property or attribute?
- RE: expectedMediaType and Accept header syntax (was Re: Action it em: HTTP binding for accepts header and output Serialization.)
- expectedMediaType and Accept header syntax (was Re: Action item: HTTP binding for accepts header and output Serialization.)
- Type of expectedMediaType element ??
- RE: Action item: HTTP binding for accepts header and output Serialization.
- Part 3: Relating serializations to operation styles
- RE: Issue 130: Asynch request/response HTTP binding needed
- Re: Action item: HTTP binding for accepts header and output Serialization.
- RE: Issue 169: Syntax for webMethod - property or attribute?
- Re: Issue 169: Syntax for webMethod - property or attribute?
- Re: Issue 130: Asynch request/response HTTP binding needed
- Action item: HTTP binding for accepts header and output Serialization.
Wednesday, 23 June 2004
- [final] Agenda, 24 June 2004 WS Desc telcon
- RE: Issue 214: Refine "properties" terminology
- RE: Issue 214: Refine "properties" terminology
- Issue 214: Refine "properties" terminology
- RE: Issue 157: Formalize processing model
- RE: Issue 130: Asynch request/response HTTP binding needed
- Issue 169: Syntax for webMethod - property or attribute?
- RE: Issue 130: Asynch request/response HTTP binding needed
- Re: [Draft] Agenda, 24 June 2004 WS Desc telcon
- RE: Issue 157: Formalize processing model
- RE: Issue 160 [was 157]: Formalize processing model
- RE: Issue 130: Asynch request/response HTTP binding needed
- Application Data Feature and related stuff
- Re: Issue 130: Asynch request/response HTTP binding needed
- RE: Issue 210: component equivalence
- RE: Issue 130: Asynch request/response HTTP binding needed
- Re: Issue 212: binding defaulting clarification
- Re: Issue 210: component equivalence
- Issue 218 - Justify Interface Faults
- RE: Issue 212: binding defaulting clarification
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- RE: Issue 210: component equivalence
- Re: Issue 157: Formalize processing model
- Re: Issue 157: Formalize processing model
Tuesday, 22 June 2004
- Re: Issue 157: Formalize processing model
- [Draft] Agenda, 24 June 2004 WS Desc telcon
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- RE: Issue 130: Asynch request/response HTTP binding needed
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- Issue 167: Synchronize pseudo-schema
- Issue 157: Formalize processing model
- Issue 130: Asynch request/response HTTP binding needed
- Re: Issue 210: component equivalence
- Re: Issue 210: component equivalence
- Re: Issue 210: component equivalence
- RE: Issue 212: binding defaulting clarification
- part 1: description of Binding Operation component [editorial]
- Re: Issue 210: component equivalence
- Issue 212: binding defaulting clarification
Monday, 21 June 2004
- Re: Issue 210: component equivalence
- Re: Issues 225: new proposals
- Issue 210: component equivalence
- Issue 211: Omitting interface messages in bindings
Saturday, 19 June 2004
Friday, 18 June 2004
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Agenda, 17 June 2004 WS Desc telcon
- review of LC drafts of XMLP specs
- Re: Sample Application described in WSDL using HTTP binding and s howing messages
Thursday, 17 June 2004
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- Re: Sample Application described in WSDL using HTTP binding and s howing messages
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Sample Application described in WSDL using HTTP binding and s howing messages
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- Paradies Bundesrepublik - Rente fuer die Welt - #Key:1356#
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Sample Application described in WSDL using HTTP binding and s howing messages
Wednesday, 16 June 2004
- Issues 225: new proposals
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Issue 225: accommodating non-XML data models (proposal)
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Agenda, 17 June 2004 WS Desc telcon
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Comments - WSDL 2.0 Message Exchange Patterns
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Issue 225: accommodating non-XML data models (proposal)
- Re: Which operation?
- RE: Which operation?
Tuesday, 15 June 2004
- RE: Describing which blobs are to be optimized.
- Agenda, 17 June 2004 WS Desc telcon
- RE: Describing which blobs are to be optimized.
- Comments - WSDL 2.0 Message Exchange Patterns
- Re: Which operation?
- RE: Sample Application described in WSDL using HTTP binding and s howing messages
- Re: Which operation?
- RE: Which operation?
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Which operation?
- Re: Issue 225: accommodating non-XML data models (proposal)
- RE: Which operation?
- Re: Which operation?
- [corrected] Minutes, 10 June 2004 WS Desc telcon
- RE: WSDL 2.0 Last Call Schedule
- Re: Issue 225: accommodating non-XML data models (proposal)
- Re: Which operation?
- RE: documenting pseudo schema lang
- Re: Which operation?
- RE: Which operation?
- documenting pseudo schema lang
- Re: Which operation?
- WSDL 2.0 Last Call Schedule (Regrets for July 1)
- RE: WSDL 2.0 Last Call Schedule (Regrets for July 1)
- RE: Which operation?
- Re: Which operation?
- Re: Which operation?
- Issue 225: accommodating non-XML data models (proposal)
Monday, 14 June 2004
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- Re: Which operation?
- RE: WSDL 2.0 Last Call Schedule
- Re: Sample Application described in WSDL using HTTP binding and showing messages
- WSDL Issues champions
- WSDL 2.0 Last Call Schedule
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- RE: Describing which blobs are to be optimized.
- RE: Describing which blobs are to be optimized.
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Call For Participation: 2004 IEEE International Conference on Web Services (ICWS 2004)
Saturday, 12 June 2004
Friday, 11 June 2004
- Issue 213: appropriate expression of property constraints
- Re: Issues 223, 224: Component Model definition (proposal)
- RE: Re: Describing which blobs are to be optimized.
- Fwd: Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Optimization hints based on expected media types
- RE: Issue 216: RPC and Schema dependency
- Re: Minutes, 10 June 2004 WS Desc telcon
- Re: Issue 217: Syntax for multiple styles
Thursday, 10 June 2004
- Issues 223, 224: Component Model definition (proposal)
- RE: Issue 217: Syntax for multiple styles
- Minutes, 10 June 2004 WS Desc telcon
- RE: Cross-binding HTTP Features
- RE: Cross-binding HTTP Features
- Cross-binding HTTP Features
- Action Item fulfillment: issue 155
- Re: Issue 212: Generic operations (proposal)
- RE: Issue 217: Syntax for multiple styles
- RE: Issue 217: Syntax for multiple styles
- RE: Issue 217: Syntax for multiple styles
- RE: Issue 217: Syntax for multiple styles
- Re: Agenda, 10 June 2004 WS Desc telcon
- Re: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- Re: Issue 216: RPC and Schema dependency
- Re: Issue 217: Syntax for multiple styles
- Re: Issue 212: Generic operations (proposal)
- Re: June 10, likely regrets
- June 10, likely regrets
- RE: Sample Application described in WSDL using HTTP binding and showing messages
- Re: Sample Application described in WSDL using HTTP binding and showing messages
- Issue 216: RPC and Schema dependency
- Sample Application described in WSDL using HTTP binding and showing messages
Wednesday, 9 June 2004
- Issue 212: Generic operations (proposal)
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- Issue 217: Syntax for multiple styles
- RE: XML 1.1 support proposals
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- Re: Comments - WSDL 2.0 Core
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- RE: Comments - WSDL 2.0 Core
- Agenda, 10 June 2004 WS Desc telcon
- FW: Last Call for SOAP Message Optimization related specs
- RE: trying to execute editorial action item to incorporate Jacek's text
- RE: XML 1.1 support proposals
Tuesday, 8 June 2004
- XML 1.1 support proposals
- trying to execute editorial action item to incorporate Jacek's text
- Re: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- RE: Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
- Features: required implementation and use (was Re: Describing which blobs are to be optimized.)
Monday, 7 June 2004
- [corrected] Minutes, 3 June 2004 WS Description teslcon
- RE: Describing which blobs are to be optimized.
- ** deadline extended **: Call for Papers for ICSOC '04
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- should WSDL be used to describe existing HTTP resources?
- CFP: The International Journal of Web Services Research (JWSR)
- CFP: International Journal of Business Process Integration and Management (IJBPIM)
Saturday, 5 June 2004
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- RE: Describing which blobs are to be optimized.
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
Friday, 4 June 2004
- RE: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Re: Describing which blobs are to be optimized.
- Describing which blobs are to be optimized.
Thursday, 3 June 2004
- Minutes, 3 June 2004 WS Description teslcon
- Re: Indicating element nodes that must be optimized with XOP
- RE: Indicating element nodes that must be optimized with XOP
- Re: Proposal: map HTTP fault codes to interface faults
- RE: Proposal: map HTTP fault codes to interface faults
- RE: Indicating element nodes that must be optimized with XOP
- Re: Indicating element nodes that must be optimized with XOP
- Re: Indicating element nodes that must be optimized with XOP
Wednesday, 2 June 2004
- RE: Agenda, 3 June 2004 WS Desc telcon
- Agenda, 3 June 2004 WS Desc telcon
- RE: Indicating element nodes that must be optimized with XOP
- Re: Indicating element nodes that must be optimized with XOP
- Re: Indicating element nodes that must be optimized with XOP
- RE: Expressing MTOM/XOP using feature syntax
- Re: Expressing MTOM/XOP using feature syntax
- Re: Indicating element nodes that must be optimized with XOP