Monday, 31 January 2005
- Action item on changing processor conformance to document conformance
- Re: Proposal for Simplifications to the Component Model
- Re: SOAP Header Blocks in WSDL (was RE: First Class Headers - Propose d Resolution for LC76d
- Re: Proposal for Simplifications to the Component Model
- Re: What Happens if 2 Inline Schemas Define the Same Element?
- SOAP Header Blocks in WSDL (was RE: First Class Headers - Propose d Resolution for LC76d
Sunday, 30 January 2005
Saturday, 29 January 2005
Friday, 28 January 2005
- Minutes [+ summary]: 19-20 January 2005 WS Description FTF
- Re: Proposal for Simplifications to the Component Model
- Re: Proposed Changes to the Interface Component, Features and Properties
- Re: Two logical WSDL documents describing the same service
- Re: Proposal for Simplifications to the Component Model
- Re: Proposed Changes to the Interface Component, Features and Properties
- RE: Two logical WSDL documents describing the same service
- Re: What Happens if 2 Inline Schemas Define the Same Element?
- RE: First Class Headers - Proposed Resolution for LC76d
- Re: First Class Headers - Proposed Resolution for LC76d
- Re: Proposed Changes to the Interface Component, Features and Properties
- Re: Proposal for Simplifications to the Component Model
- RE: Two logical WSDL documents describing the same service
- Re: First Class Headers - Proposed Resolution for LC76d
- Re: What Happens if 2 Inline Schemas Define the Same Element?
- RE: First Class Headers - Proposed Resolution for LC76d
- Re: What Happens if 2 Inline Schemas Define the Same Element?
Thursday, 27 January 2005
- RE: What Happens if 2 Inline Schemas Define the Same Element?
- RE: What Happens if 2 Inline Schemas Define the Same Element?
- RE: What Happens if 2 Inline Schemas Define the Same Element?
- RE: What Happens if 2 Inline Schemas Define the Same Element?
- Re: First Class Headers - Proposed Resolution for LC76d
- RE: What Happens if 2 Inline Schemas Define the Same Element?
- What Happens if 2 Inline Schemas Define the Same Element?
- Re: First Class Headers - Proposed Resolution for LC76d
- Re: Proposal for Simplifications to the Component Model
- RE: First Class Headers - Proposed Resolution for LC76d
- Proposed Resolution for LC52a
- Proposed Resolution for LC52a
- Re: Proposal for Simplifications to the Component Model
- [Fwd: FW: Proposed Resolution for LC52a]
- Proposed Changes to the Interface Component, Features and Properties
- Proposed Resolution for LC75t and LC92
- Proposed Resolution for LC75s and LC91
- Meeting records list still in 2004...
- Proposal for Simplifications to the Component Model
Wednesday, 26 January 2005
- Agenda, 27 January 2004 WS Desc telcon
- Re: First Class Headers - Proposed Resolution for LC76d
- Re: Comments on Primer
- RE: First Class Headers - Proposed Resolution for LC76d
- RE: Comments on Primer
- RE: Choice of response message in WSDL
- RE: Choice of response message in WSDL
- RE: Choice of response message in WSDL
- Re: First Class Headers - Proposed Resolution for LC76d
Monday, 24 January 2005
- Re: Choice of response message in WSDL
- Choice of response message in WSDL
- RE: First Class Headers - Proposed Resolution for LC76d
- First Class Headers - Proposed Resolution for LC76d
- Comments on Primer
Saturday, 22 January 2005
Friday, 21 January 2005
- Headers Proposal V1.2
- RE: Headers proposal V 1.1 (compatible with V1.0)
- Headers proposal V 1.1 (compatible with V1.0)
- XML 1.1 Dropped, XSD 1.0 Simple Types Used
Thursday, 20 January 2005
- Headers proposal revisited
- Re: Initial PDF Version of WSDL 2.0 Part 1 Available
- apparent bug on the operation name mapping requirement text
Wednesday, 19 January 2005
- Initial PDF Version of WSDL 2.0 Part 1 Available
- [revised] Agenda, 20-21 January 2005 WS Desc FTF, Melbourne AUS
Monday, 17 January 2005
- Agenda, 19 Jan 2005 joint WS Description, WS Addressing FTF meeting
- RE: What is the SOAP MEP for In-only
Sunday, 16 January 2005
Saturday, 15 January 2005
Friday, 14 January 2005
Thursday, 13 January 2005
- Re: Meaning of a WSDL document
- Minutes, 13 Jan 2005 WS Description telcon
- ACTION 2005-01-06 Umit to respond to Henry
Wednesday, 12 January 2005
Tuesday, 11 January 2005
Monday, 10 January 2005
Thursday, 6 January 2005
- RE: Last Call issue: How does the Operation Name Mapping Requirement (Part 1, section 2.2.1.1) relate to interface inheritance?
- RE: Issue 259 Some alternatives, proposals
- Workshop on Business Services Networks (BSN)
- Re: Issue 259 Some alternatives, proposals
- Issue 263 (Lexical and value space of the attributes and XML Schema Decl) Proposed Resolution
- Issue 262 (Value of contentType and the range specified by expectedMediaType) Proposed Resolution
- Issue 261 (Allow expecteMediaType to contain '*') Proposed Resolution
- Issue 268 (Interop Problems with Accept header) Proposed Resolution
Wednesday, 5 January 2005
- Issue 266 Differentiating the type of binary Content when no schema is present
- Re: New Twisty Alternate Versions of WSDL 2.0 Part 1
- Issue 259 Some alternatives, proposals
- Issue 260 Some alternatives
- Issue 258 Proposed Resolution
- Re: New Twisty Alternate Versions of WSDL 2.0 Part 1
- Re: New Twisty Alternate Versions of WSDL 2.0 Part 1
- Re: New Twisty Alternate Versions of WSDL 2.0 Part 1
- New Twisty Alternate Versions of WSDL 2.0 Part 1
- RE: Agenda, 6 January 2004 WS Desc telcon [Media Type Description]