A scenario investigating questions of conformance and scoping
Presentation for Compositors
Part 1, section 2.4.1, {message}
WSDL Specification readability: formulaic text
Proposal for adding Compositors to WSDL 2.0
RE: Suggest TAG/WSD WG liaison meeting at tech plenary
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
- Re: Optional Extensions
- Re: Optional Extensions
- Re: Optional Extensions
- RE: Optional Extensions
- RE: Optional Extensions
- RE: Optional Extensions
- RE: Optional Extensions
- RE: Optional Extensions
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: optional messageReference attribute on interface definition elements
Your Ship Has Come In! This Time You Are Not At The Airport!
WSD charter goal: Simplicity
WSDL 1.1 XML Schemas Legal Issue
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
[ rev 1] Agenda: 28-30 Jan 2004 WS Description WG FTF
Charter comments: SOAP 1.1
Compatible evolution of schemas
RE: Another try at HTTP binding
Attributes
Action item 2003-11-03 OperationName feature
Agenda, 22 January 2004 WS Desc telcon
Versioning and Web Service Description
Simplified WSDL Syntax
- Re: Simplified WSDL Syntax
- RE: Simplified WSDL Syntax
- RE: Simplified WSDL Syntax
- Re: Simplified WSDL Syntax
Versioning Use Cases
Header/Body Style Proposal
- RE: Header/Body Style Proposal
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
- FW: Issue 32: SOAP 1.1 support
Agenda: 28-30 Jan 2004 WS Description WG FTF
Features and Properties
Please Join My Superb Yahoo Forums!
RE: Proposal: abstract faults (amendment)
Proposal: abstract faults (amended)
Alternate approach to indicating operation styles
bugs in WSDL1.1 specs but no reference to issues list?
Minutes, 15 January 2004 Web Services Description Working Group teleconference
Deadline Reminder: 2004 IEEE International Conference on Web Serv ices (ICWS 2004)
Incorporating Service References in Part1
Followup: multiple services sharing a name
Agenda, 15 January 2004 WS Desc telcon
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
Draft minutes of 08-Jan-2004 telcon
RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
- RE: encodingStyle
Re: Another try at HTTP binding
A swing at schema import text
Extending the functionality of an existing Web Service
- Re: Extending the functionality of an existing Web Service
- RE: Extending the functionality of an existing Web Service
WS-I review drafts of Basic Profile Attachements work now available
Likely regrets for Jan 8th telecon
[rev] Agenda, 8 January 2004 WS Desc telcon
RE: Fuflillment of action item: language for circular includes
Agenda, 8 January 2004 WS Desc telcon
Issue: properties and schema languages other than XSD
Minutes of WS Description call 2003-12-18
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
- Re: Two logical WSDL documents describing the same service
- Re: Two logical WSDL documents describing the same service