Wednesday, 31 March 2004
Monday, 29 March 2004
- Re: HTTP chunk-encoding
- HTTPS support
- HTTP chunk-encoding
- ANN: 2nd International Conf. on Service-Oriented Computing (ICSOC '04)
Thursday, 25 March 2004
Friday, 26 March 2004
Wednesday, 24 March 2004
Thursday, 25 March 2004
- Re: Proposed resolutions for issues 146 and 150
- RE: Proposed resolutions for issues 146 and 150
- Minutes, 25 March 2004 WS Description telcon
- Strawman SOAP 1.2 Binding pseudo-schema
- Re: component designators spec - where art thou?
- Re: component designators spec - where art thou?
- Re: Agenda, 25 March 2004 WS Desc telcon (regrets)
- Re: Agenda, 25 March 2004 WS Desc telcon
Wednesday, 24 March 2004
- RE: Proposed resolutions for issues 146 and 150
- Re: Proposed resolutions for issues 146 and 150
- Re: component designators spec - where art thou?
- RE: Proposed resolutions for issues 146 and 150
- [Fwd: [OASIS members] public review of OASIS WSRM TC spec]
- Re: Proposed resolutions for issues 146 and 150
- Re: Agenda, 25 March 2004 WS Desc telcon
- Re: Processor conformance: fault on non-conformant input
- updating the component designators appendix
Tuesday, 23 March 2004
- RE: Proposed resolutions for issues 146 and 150
- RE: regrets to 18 March, 2000 WS description telcon
- Invitation to give a WS talk
- Agenda, 25 March 2004 WS Desc telcon
- Re: Processor conformance: fault on non-conformant input
- RE: Proposed resolutions for issues 146 and 150
- Re: Processor conformance: fault on non-conformant input
- Re: Proposed resolutions for issues 146 and 150
- RE: regrets to 18 March, 2000 WS description telcon
- RE: regrets to 18 March, 2000 WS description telcon
- Re: Processor conformance: fault on non-conformant input
- Re: Processor conformance: fault on non-conformant input
- Re: WSDL 1.1 to WSDL 2.0 mapping
- Re: Proposed resolutions for issues 146 and 150
- Re: Processor conformance: fault on non-conformant input
- RE: Proposed resolutions for issues 146 and 150
- Re: Processor conformance: fault on non-conformant input
- Re: Processor conformance: fault on non-conformant input
- RE: WSDL 1.1 to WSDL 2.0 mapping
- Re: Processor conformance: fault on non-conformant input
- Re: Proposed resolutions for issues 146 and 150
- Re: Proposed resolutions for issues 146 and 150
- Re: Proposed resolutions for issues 146 and 150
- Re: Processor conformance: fault on non-conformant input
- Re: wsdli:wsdlLocation attribute
- Re: wsdli:wsdlLocation attribute
- Re: Processor conformance: fault on non-conformant input
- Re: WSDL 1.1 to WSDL 2.0 mapping
- Re: Proposed resolutions for issues 146 and 150
Monday, 22 March 2004
- Re: Proposed resolutions for issues 146 and 150
- Re: Proposed resolutions for issues 146 and 150
- Re: Processor conformance: fault on non-conformant input
- RE: WSDL 1.1 to WSDL 2.0 mapping
- RE: Proposed resolutions for issues 146 and 150
- Re: Proposed resolutions for issues 146 and 150
- Re: WSDL 1.1 to WSDL 2.0 mapping
- RE: WSDL 1.1 to WSDL 2.0 mapping
- Re: Proposed resolutions for issues 146 and 150
- Re: wsdli:wsdlLocation attribute
- Re: write a schema for the wsdli namespace
- Re: WSDL 1.1 to WSDL 2.0 mapping
- Re: wsdli:wsdlLocation attribute
- remaining editorial tasks for part1?
- write a schema for the wsdli namespace
- Re: Properties text today?
- Re: Properties text today?
- WSDL 1.1 to WSDL 2.0 mapping
- Re: Wording on targetNamespace document
- wsdli:wsdlLocation attribute
- Re: Wording on targetNamespace document
- Re: Properties text today?
- Re: cvs server down??
- Re: cvs server down??
- Re: Processor conformance: fault on non-conformant input
- cvs server down??
Saturday, 20 March 2004
Friday, 19 March 2004
- Wording on targetNamespace document
- Re: Processor conformance: fault on non-conformant input
- Re: Processor conformance: fault on non-conformant input
- RE: Processor conformance: fault on non-conformant input
- Re: Processor conformance: fault on non-conformant input
- Re: Processor conformance: fault on non-conformant input
- Re: Processor conformance: fault on non-conformant input
- Re: Issue 115
- Re: regrets to 18 March, 2000 WS description telcon
- Re: Properties text today?
- RE: WSDL Import/Include Locations
- RE: regrets to 18 March, 2000 WS description telcon
- Re: Resolution to issue 139
- Re: Processor conformance: fault on non-conformant input
- Re: Properties text today?
- Re: Issue 115
- Re: features and requiredness
- Re: Issue 115
- Re: [revised] Proposed resolutions for issues 146 and 150
- Re: Processor conformance: fault on non-conformant input
- Re: Resolution to issue 139
Thursday, 18 March 2004
- FW: request for review: XML Schema Second Edition PER
- Re: Resolution to issue 139
- regrets to 18 March, 2000 WS description telcon
- RE: features and requiredness
- Re: Processor conformance: fault on non-conformant input
- Minutes 18 March, 2000 WS description telcon
- Re: Issue 115
- Re: features and requiredness
- Re: component designators spec - where art thou?
- Re: [revised] Proposed resolutions for issues 146 and 150
- Re: Processor conformance: fault on non-conformant input
- Re: Issue 115
- Re: Issue 115
- Processor conformance: fault on non-conformant input
- Re: Issue 115
- Re: features and requiredness
- Re: Normative vs Non-normative Notes (was Re: Other suggested editorial changes)
- Re: features and requiredness
- Re: features and requiredness
- Re: Properties text today?
- RE: proposal: make binding/operation/(input|output)/@messageLabel optional
- Re: Normative vs Non-normative Notes (was Re: Other suggested editorial changes)
- Re: proposal: make binding/operation/(input|output)/@messageLabel optional
- Re: proposal: make binding/operation/(input|output)/@messageLabel optional
- Re: proposal: make binding/operation/(input|output)/@messageLabel optional
- Re: Normative vs Non-normative Notes (was Re: Other suggested editorial changes)
- RE: proposal: make binding/operation/(input|output)/@messageLabel optional
- Re: Normative vs Non-normative Notes (was Re: Other suggested editorial changes)
- Properties text today?
- RE: proposal: make binding/operation/(input|output)/@messageLabel optional
- Re: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- Re: features and requiredness
- Re: features and requiredness
- Re: ADD Feature Proposal
- proposal: make binding/operation/(input|output)/@messageLabel optional
- Re: WSDL Import/Include Locations
- ADD Feature Proposal
- Re: Other suggested editorial changes
- Re: Agenda, 18 March 2004 WS Desc telcon
- Re: Other suggested editorial changes
Wednesday, 17 March 2004
- Re: Normative vs Non-normative Notes (was Re: Other suggested editorial changes)
- Effort to simplifying our spec
- Normative vs Non-normative Notes (itemized list)
- Normative vs Non-normative Notes (was Re: Other suggested editorial changes)
- Re: Another try at HTTP binding
- Agenda, 18 March 2004 WS Desc telcon
- [re-corrected] Minutes 11 March, 2000 WS description telcon
- Re: Other suggested editorial changes
- Re: Other suggested editorial changes
- Re: [corrected] Minutes 11 March, 2000 WS description telcon
- Re: Other suggested editorial changes
- Re: Spec wording for operation safety
- [corrected] Minutes 11 March, 2000 WS description telcon
- Re: features and requiredness
- Re: Other suggested editorial changes
- Re: features and requiredness
- Re: Another try at HTTP binding
- Re: Issue 115
- Re: Issue 32: Will SOAP 1.1 still be supported?
- more EDTODOs from 20040311 telecon completed
- Re: features and requiredness
- RE: completed more EDTODOs from 20040311 telecon
- Re: features & properties: anywhere or only selected places??
- RE: Issue 32: Will SOAP 1.1 still be supported?
- Re: Issue 32: Will SOAP 1.1 still be supported?
- Re: Issue 32: Will SOAP 1.1 still be supported?
- Re: features and requiredness
- Re: Issues 58 and 59: MIME binding
- Re: Issue 32: Will SOAP 1.1 still be supported?
- Re: features & properties: anywhere or only selected places??
- completed more EDTODOs from 20040311 telecon
- Re: Issue 115
- Re: issue 79 is dealt with
- Re: Minutes 11 March, 2000 WS description telcon
- Re: Proposed resolutions for issues 146 and 150
- Re: issue 79 is dealt with
- Re: Issue 115
Tuesday, 16 March 2004
- Re: component designators spec - where art thou?
- RE: Proposed resolutions for issues 146 and 150
- RE: Proposed resolution to issue 143
- RE: Proposed resolutions for issues 146 and 150
- Re: Minutes 11 March, 2000 WS description telcon
- Re: component designators spec - where art thou?
- RE: Proposed resolutions for issues 146 and 150
- Re: features and requiredness
- RE: Proposed resolutions for issues 146 and 150
- proposing to close issue 152
Monday, 15 March 2004
- Resolution to issue 139
- RE: component designators spec - where art thou?
- RE: Proposed resolutions for issues 146 and 150
- Re: Proposed resolutions for issues 146 and 150
- Re: component designators spec - where art thou?
- RE: Change to the RPC signature extension (Was: [revised] Proposed resolutions for issues 146 and 150)
- Change to the RPC signature extension (Was: [revised] Proposed resolutions for issues 146 and 150)
- RE: [revised] Proposed resolutions for issues 146 and 150
- RE: component designators spec - where art thou?
- Re: features and requiredness
- Issue 115
- moved to edtodo
- old EDTODOs in the 20040311 telecon minutes
- Re: Issue 32: Will SOAP 1.1 still be supported?
- Re: Broken resolution of NCNAME or QNAME
- features and requiredness
- issue 79 is dealt with
- Re: WSDL Import/Include Locations
- component designators spec - where art thou?
- issue 122 is dealt with
- issue 142 is dealt with
- Re: Proposed resolution to issue 143
- clarification on why operations and faults are not qname referencible
- RE: WSDL Import/Include Locations
- Re: WSDL Import/Include Locations
Sunday, 14 March 2004
Friday, 12 March 2004
- Re: Issue 66: How to represent the equivalent of hypertext links?
- Re: WSDL Import/Include Locations
- Re: features & properties: anywhere or only selected places??
- Issue 66: How to represent the equivalent of hypertext links?
- Issues 58 and 59: MIME binding
- Issue 32: Will SOAP 1.1 still be supported?
- Re: WSDL Import/Include Locations
- RE: features & properties: anywhere or only selected places??
- Minutes 11 March, 2000 WS description telcon
- Re: WSDL Import/Include Locations
- Re: features & properties: anywhere or only selected places??
- Introduction
- Re: Proposed resolutions for issues 146 and 150
- Re: features & properties: anywhere or only selected places??
- RE: WSDL Import/Include Locations
- RE: [revised] Proposed resolutions for issues 146 and 150
- [revised] Proposed resolutions for issues 146 and 150
- Re: WSDL Import/Include Locations
Thursday, 11 March 2004
- RE: features & properties: anywhere or only selected places??
- RE: features & properties: anywhere or only selected places??
- Re: features & properties: anywhere or only selected places??
- Re: features & properties: anywhere or only selected places??
- proposal for consistifying @name attrs
- Re: Proposed Resolution for Issue 135
- Re: Proposed resolutions for issues 146 and 150
- WSDL Language/Processor clarifications
- RE: features & properties: anywhere or only selected places??
Wednesday, 10 March 2004
- Re: features & properties: anywhere or only selected places??
- Re: Proposed Resolution for Issue 135
- Re: Proposed Resolution for Issue 135
- Proposed Resolution for Issue 135
- Proposed resolutions for issues 146 and 150
- Re: working on fault changes
- RE: working on fault changes
- RE: Spec wording for operation safety
- Re: Spec wording for operation safety
- RE: Spec wording for operation safety
- Re: Suggested editorial changes to 2.6.1 The Feature Component
- features & properties: anywhere or only selected places??
- Re: Suggested editorial changes to 2.6.1 The Feature Component
- Re: Spec wording for operation safety
- working on fault changes
- Other suggested editorial changes
- Re: Suggested editorial changes to 2.6.1 The Feature Component
- Re: Suggested editorial changes to 2.6.1 The Feature Component
- Suggested editorial changes to 2.6.1 The Feature Component
- Agenda, 11 March 2004 WS Desc telcon
- SOAP 1.2 security requirements...
Tuesday, 9 March 2004
- Spec wording for operation safety
- Summary, 4-5 March 2004 WS Description WG FTF
- Minutes, 5 March 2004 WS Description WG FTF
- Minutes, 4 March 2004 WS Description WG FTF
- Re: Another try at HTTP binding
- RE: WSDL Import/Include Locations
- Re: WSDL Import/Include Locations
Monday, 8 March 2004
- RE: renaming operation/{input,output}/@messageReference
- RE: WSDL Import/Include Locations
- Re: WSDL Import/Include Locations
- renaming operation/{input,output}/@messageReference
- Re: question about interface/operation/@style and interface/@styl eDefault
- Re: Rough text per resolution of issue 127 (Behavior if import/ include fails)
- Re: WSDL Import/Include Locations
- Re: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- Review: SOAP Data Model Schema Language
Friday, 5 March 2004
- Re: WSDL Import/Include Locations
- RE: Rough text per resolution of issue 127 (Behavior if import/ include fails)
- Re: question about interface/operation/@style and interface/@styl eDefault
- Rough text per resolution of issue 127 (Behavior if import/include fails)
- RE: question about interface/operation/@style and interface/@styl eDefault
- URI identifier comparison
Thursday, 4 March 2004
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- Re: WSDL Import/Include Locations
- synthesis of versioning discussion
- F2F presentation on WSDL language versus processor
- RE: WSDL Import/Include Locations
Wednesday, 3 March 2004
- Re: WSDL Import/Include Locations
- Re: Out Of Body Experiences (application header feature)
- RE: Validation, Versioning and RDF [Was Re: WSDL WG request for adding multiple version extensibility into Schema 1.1]
- Re: Validation, Versioning and RDF [Was Re: WSDL WG request for adding multiple version extensibility into Schema 1.1]
- Re: Marking operations safe
- Re: Correction for the f2f Minutes (Also action 2004-01-30 for Jonathan)
- Re: Correction for the f2f Minutes (Also action 2004-01-30 for Jonathan)
- Re: Another try at HTTP binding
- Agenda for joint meeting with XMLP Noon 3 March