Sunday, 1 February 2004
Saturday, 31 January 2004
- Re: Asynch request/response HTTP binding needed
- Re: Asynch request/response HTTP binding needed
- RE: Asynch request/response HTTP binding needed
- Re: Asynch request/response HTTP binding needed
- RE: Asynch request/response HTTP binding needed
- Re: Second level xs:import
- Re: Asynch request/response HTTP binding needed
Friday, 30 January 2004
- A scenario investigating questions of conformance and scoping
- RE: Second level xs:import
- RE: Asynch request/response HTTP binding needed
- Re: Another try at HTTP binding
Thursday, 29 January 2004
Wednesday, 28 January 2004
- RE: Optional Extensions
- RE: WSDL Specification readability: formulaic text
- Re: Optional Extensions
- RE: Optional Extensions
- Re: Optional Extensions
- Re: Optional Extensions
- Part 1, section 2.4.1, {message}
- Re: Optional Extensions
- Re: Optional Extensions
- RE: Optional Extensions
- Re: Optional Extensions
- RE: Optional Extensions
- RE: WSD charter goal: Simplicity
- Re: Action item 2003-11-03 OperationName feature
- Re: WSD charter goal: Simplicity
- Re: Action item 2003-11-03 OperationName feature
Tuesday, 27 January 2004
- RE: WSD charter goal: Simplicity
- RE: Optional Extensions
- RE: Optional Extensions
- Re: Optional Extensions
- Re: in-optional-out?
- RE: Optional Extensions
- RE: in-optional-out?
- Re: WSDL Specification readability: formulaic text
- Re: Simplified WSDL Syntax
- Re: Why aren't two input/output elements allowed to share the same messageReference value?
- Re: Optional Extensions
- Re: in-optional-out?
- WSDL Specification readability: formulaic text
Monday, 26 January 2004
- RE: Simplified WSDL Syntax
- RE: Why aren't two input/output elements allowed to share the same messageReference value?
- RE: Second level xs:import
- RE: Optional Extensions
- Re: Asynch request/response HTTP binding needed
- Re: Optional Extensions
- Proposal for adding Compositors to WSDL 2.0
- RE: Optional Extensions
- RE: Optional Extensions
- Re: Simplified WSDL Syntax
- Re: Optional Extensions
- RE: Optional Extensions
- Re: Optional Extensions
- Re: Asynch request/response HTTP binding needed
- RE: Suggest TAG/WSD WG liaison meeting at tech plenary
- Re: in-optional-out?
- Re: Why aren't two input/output elements allowed to share the same messageReference value?
- Re: Second level xs:import
- in-optional-out?
- re-use faults by ref
- Why aren't two input/output elements allowed to share the same messageReference value?
- Message attribute optional
- Second level xs:import
- Optional Extensions
- Asynch request/response HTTP binding needed
- RE: optional messageReference attribute on interface definition elements
Sunday, 25 January 2004
Monday, 26 January 2004
Saturday, 24 January 2004
- RE: WSDL Import/Include Locations
- RE: optional messageReference attribute on interface definition elements
Friday, 23 January 2004
- RE: Header/Body Style Proposal
- RE: Simplified WSDL Syntax
- Re: WSDL Import/Include Locations
- Re: optional messageReference attribute on interface definition elements
- Re: Header/Body Style Proposal
- WSD charter goal: Simplicity
- WSDL 1.1 XML Schemas Legal Issue
Thursday, 22 January 2004
- FW: Issue 32: SOAP 1.1 support
- RE: Header/Body Style Proposal
- Re: Requiring all operations to be bound
- WSDL Import/Include Locations
- Confusion between binding and element names
- optional messageReference attribute on interface definition elements
- The semantics of mandatory properties and features
- Requiring all operations to be bound
- messageReference semantics on binding
- Broken resolution of NCNAME or QNAME
- A & B in MEPs
- RE: Simplified WSDL Syntax
- Re: Header/Body Style Proposal
- RE: Header/Body Style Proposal
Friday, 23 January 2004
Thursday, 22 January 2004
Friday, 23 January 2004
Thursday, 22 January 2004
- Re: Simplified WSDL Syntax
- Re: Header/Body Style Proposal
- Re: Action item 2003-11-03 OperationName feature
- RE: Simplified WSDL Syntax
- RE: Header/Body Style Proposal
Friday, 23 January 2004
Thursday, 22 January 2004
- Charter comments: SOAP 1.1
- Compatible evolution of schemas
- Re: Another try at HTTP binding
- RE: Issue 32: SOAP 1.1 support
- Re: Simplified WSDL Syntax
- Re: Action item 2003-11-03 OperationName feature
- Re: Another try at HTTP binding
- Re: Simplified WSDL Syntax
- Re: Header/Body Style Proposal
- RE: Action item 2003-11-03 OperationName feature
- RE: Another try at HTTP binding
- Re: Action item 2003-11-03 OperationName feature
- Re: Another try at HTTP binding
- Attributes
Wednesday, 21 January 2004
- RE: Header/Body Style Proposal
- Re: Another try at HTTP binding
- RE: Header/Body Style Proposal
- Action item 2003-11-03 OperationName feature
- Agenda, 22 January 2004 WS Desc telcon
- RE: Header/Body Style Proposal
- RE: Issue 32: SOAP 1.1 support
- RE: Versioning and Web Service Description
- RE: Issue 32: SOAP 1.1 support
- Versioning and Web Service Description
- RE: Issue 32: SOAP 1.1 support
- RE: Issue 32: SOAP 1.1 support
- RE: Issue 32: SOAP 1.1 support
- Re: Issue 32: SOAP 1.1 support
- Simplified WSDL Syntax
- Versioning Use Cases
- Header/Body Style Proposal
- Issue 32: SOAP 1.1 support
Tuesday, 20 January 2004
- Agenda: 28-30 Jan 2004 WS Description WG FTF
- Features and Properties
- Please Join My Superb Yahoo Forums!
- RE: Proposal: abstract faults (amendment)
- RE: Proposal: abstract faults (amended)
- Re: Proposal: abstract faults (amended)
Monday, 19 January 2004
- RE: Incorporating Service References in Part1
- Proposal: abstract faults (amended)
- Re: Another try at HTTP binding
- Re: Another try at HTTP binding
- Re: Another try at HTTP binding
- Re: Another try at HTTP binding
- Re: Followup: multiple services sharing a name
- Alternate approach to indicating operation styles
Friday, 16 January 2004
Thursday, 15 January 2004
- bugs in WSDL1.1 specs but no reference to issues list?
- Minutes, 15 January 2004 Web Services Description Working Group teleconference
- Re: Followup: multiple services sharing a name
- RE: Extending the functionality of an existing Web Service
- Re: Followup: multiple services sharing a name
- Deadline Reminder: 2004 IEEE International Conference on Web Serv ices (ICWS 2004)
- Re: Incorporating Service References in Part1
- Incorporating Service References in Part1
Wednesday, 14 January 2004
Tuesday, 13 January 2004
Monday, 12 January 2004
- RE: encodingStyle
- RE: Two logical WSDL documents describing the same service
- Re: Two logical WSDL documents describing the same service
- RE: Two logical WSDL documents describing the same service
Friday, 9 January 2004
- Re: Two logical WSDL documents describing the same service
- Re: Two logical WSDL documents describing the same service
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
Thursday, 8 January 2004
- RE: Extending the functionality of an existing Web Service
- RE: Extending the functionality of an existing Web Service
- Draft minutes of 08-Jan-2004 telcon
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- Re: Two logical WSDL documents describing the same service
- Re: Another try at HTTP binding
- Re: [rev] Agenda, 8 January 2004 WS Desc telcon
- Re: Another try at HTTP binding
- Re: Another try at HTTP binding
- Re: Issue: properties and schema languages other than XSD
- Re: Extending the functionality of an existing Web Service
- A swing at schema import text
- Extending the functionality of an existing Web Service
- Re: Two logical WSDL documents describing the same service
- Re: Two logical WSDL documents describing the same service
- Re: Two logical WSDL documents describing the same service
- WS-I review drafts of Basic Profile Attachements work now available
- Likely regrets for Jan 8th telecon
Wednesday, 7 January 2004
Tuesday, 6 January 2004
- RE: Fuflillment of action item: language for circular includes
- Agenda, 8 January 2004 WS Desc telcon
- RE: Issue: properties and schema languages other than XSD
- Issue: properties and schema languages other than XSD
Monday, 5 January 2004
- Minutes of WS Description call 2003-12-18
- Re: Two logical WSDL documents describing the same service
Sunday, 4 January 2004
- Re: encodingStyle
- Re: Two logical WSDL documents describing the same service
- Re: Two logical WSDL documents describing the same service