Agenda, 1 April 2004 WS Desc telcon
HTTPS support
HTTP chunk-encoding
ANN: 2nd International Conf. on Service-Oriented Computing (ICSOC '04)
Minutes, 25 March 2004 WS Description telcon
Strawman SOAP 1.2 Binding pseudo-schema
[Fwd: [OASIS members] public review of OASIS WSRM TC spec]
updating the component designators appendix
Invitation to give a WS talk
Agenda, 25 March 2004 WS Desc telcon
- Re: Agenda, 25 March 2004 WS Desc telcon
- Re: Agenda, 25 March 2004 WS Desc telcon
- Re: Agenda, 25 March 2004 WS Desc telcon (regrets)
remaining editorial tasks for part1?
write a schema for the wsdli namespace
WSDL 1.1 to WSDL 2.0 mapping
- Re: WSDL 1.1 to WSDL 2.0 mapping
- RE: WSDL 1.1 to WSDL 2.0 mapping
- RE: WSDL 1.1 to WSDL 2.0 mapping
- RE: WSDL 1.1 to WSDL 2.0 mapping
wsdli:wsdlLocation attribute
cvs server down??
Wording on targetNamespace document
FW: request for review: XML Schema Second Edition PER
regrets to 18 March, 2000 WS description telcon
- RE: regrets to 18 March, 2000 WS description telcon
- RE: regrets to 18 March, 2000 WS description telcon
- RE: regrets to 18 March, 2000 WS description telcon
- RE: regrets to 18 March, 2000 WS description telcon
Minutes 18 March, 2000 WS description telcon
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: 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: 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: Processor conformance: fault on non-conformant input
- Re: Processor conformance: fault on non-conformant input
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
proposal: make binding/operation/(input|output)/@messageLabel optional
ADD Feature Proposal
Effort to simplifying our spec
Agenda, 18 March 2004 WS Desc telcon
[re-corrected] Minutes 11 March, 2000 WS description telcon
[corrected] Minutes 11 March, 2000 WS description telcon
more EDTODOs from 20040311 telecon completed
completed more EDTODOs from 20040311 telecon
RE: Proposed resolution to issue 143
proposing to close issue 152
Resolution to issue 139
RE: Change to the RPC signature extension (Was: [revised] Proposed resolutions for issues 146 and 150)
Issue 115
moved to edtodo
old EDTODOs in the 20040311 telecon minutes
Re: Broken resolution of NCNAME or QNAME
features and requiredness
- Re: features and requiredness
issue 79 is dealt with
component designators spec - where art thou?
- RE: component designators spec - where art thou?
- Re: component designators spec - where art thou?
- RE: 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
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: 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?
Minutes 11 March, 2000 WS description telcon
Introduction
[revised] Proposed resolutions for issues 146 and 150
- RE: [revised] Proposed resolutions for issues 146 and 150
- RE: [revised] Proposed resolutions for issues 146 and 150
- RE: [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
proposal for consistifying @name attrs
WSDL Language/Processor clarifications
Proposed resolutions for issues 146 and 150
- 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: Proposed resolutions for issues 146 and 150
- 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: Proposed resolutions for issues 146 and 150
- RE: Proposed resolutions for issues 146 and 150
- RE: Proposed resolutions for issues 146 and 150
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??
- RE: features & properties: anywhere or only selected places??
- RE: features & properties: anywhere or only selected places??
working on fault changes
Other suggested editorial changes
- Re: Other suggested editorial changes
- Re: Other suggested editorial changes
- Re: Other suggested editorial changes
- Re: Other suggested editorial changes
- Normative vs Non-normative Notes (was Re: Other suggested editorial changes)
- Normative vs Non-normative Notes (itemized list)
- Re: Other suggested editorial changes
- Re: Other suggested editorial changes
Suggested editorial changes to 2.6.1 The Feature Component
Agenda, 11 March 2004 WS Desc telcon
SOAP 1.2 security requirements...
Spec wording for operation safety
- Re: Spec wording for operation safety
- RE: Spec wording for operation safety
- RE: Spec wording for operation safety
- Re: 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
renaming operation/{input,output}/@messageReference
Review: SOAP Data Model Schema Language
RE: Rough text per resolution of issue 127 (Behavior if import/ include fails)
Rough text per resolution of issue 127 (Behavior if import/include fails)
RE: question about interface/operation/@style and interface/@styl eDefault
- Re: question about interface/operation/@style and interface/@styl eDefault
- Re: question about interface/operation/@style and interface/@styl eDefault
URI identifier comparison
synthesis of versioning discussion
F2F presentation on WSDL language versus processor
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: Another try at HTTP binding
Agenda for joint meeting with XMLP Noon 3 March
RE: WSDL Import/Include Locations
- Re: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations
- RE: WSDL Import/Include Locations