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