Wednesday, 29 June 2005
Tuesday, 28 June 2005
Monday, 27 June 2005
- Re: Issue LC90
- RE: Issue LC90
- Re: Issue LC90
- Re: Issue LC90
- RE: LC68 - Use-cases
- Re: Issue LC90
- Re: Issue LC90
- Re: Issue LC90
- Re: Issue LC90
- Re: Issue LC90
- Re: Issue LC90
- Re: LC68 - Use-cases
- Re: Issue LC90
- Re: Issue LC90
- LC103
- Issue LC90
- Proposal for i050 : introduction of EPR to indicate 'noReply'
- LC68 - Use-cases
Saturday, 25 June 2005
Wednesday, 22 June 2005
Thursday, 23 June 2005
Wednesday, 22 June 2005
Friday, 17 June 2005
Wednesday, 22 June 2005
Tuesday, 21 June 2005
- Self-describing Messages wrt MEPs
- Re: Requirements for one-way MEP
- Re: Requirements for one-way MEP
- Minutes of the 2005-06-20 teleconference
- Re: Requirements for one-way MEP
- Re: Proposal for lc75/lc88
- Re: Why is [message id] required for requests but not for other messages?
Monday, 20 June 2005
- In the spirit of real-time editing
- Proposal for lc87 and lc55
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Proposal for lc75/lc88
- Re: Agenda: WS-A telcon 2005-06-20
- Regrets for 6/20
Friday, 17 June 2005
Sunday, 19 June 2005
Friday, 17 June 2005
Thursday, 16 June 2005
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- NEW DEADLINE: Third European Conference on Web Services - ECOWS 2005
- Re: Why is [message id] required for requests but not for other messages?
Wednesday, 15 June 2005
Tuesday, 14 June 2005
- Re: Proposal for lc75/lc88
- Email glitch
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- RE: Why is [message id] required for requests but not for other messages?
- Re: How does Message ID coordinate with existing message ID facilities?
- RE: Why is [message id] required for requests but not for other messages?
- RE: How does Message ID coordinate with existing message ID facilities?
- RE: Proposal for lc75/lc88
- RE: Proposal for lc75/lc88
- Re: Proposal for lc75/lc88
- Re: Proposal for lc75/lc88
- Re: content of fault detail
- Re: Proposal for lc75/lc88
- Re: content of fault detail
- RE: Proposal for lc75/lc88
- RE: How does Message ID coordinate with existing message ID facilities?
Monday, 13 June 2005
- Re: Why is [message id] required for requests but not for other messages?
- Re: Why is [message id] required for requests but not for other messages?
- RE: Why is [message id] required for requests but not for other messages?
- Why is [message id] required for requests but not for other messages?
- Proposal for lc75/lc88
- How does Message ID coordinate with existing message ID facilities?
- Re: content of fault detail
- Re: wsa:FaultTo unusable for SOAP mustUnderstand faults
- Re: content of fault detail
- Message ID use cases:
- Re: content of fault detail
Sunday, 12 June 2005
- Regrets for WS-A telcon 2005-06-13
- Re: Minutes of the Berlin F2F
- Minutes of the Berlin F2F
- Agenda: WS-A telcon 2005-06-13
- Re: content of fault detail
Thursday, 9 June 2005
- RE: wsa:FaultTo unusable for SOAP mustUnderstand faults
- Re: wsa:FaultTo unusable for SOAP mustUnderstand faults
- RE: wsa:FaultTo unusable for SOAP mustUnderstand faults
- Re: wsa:FaultTo unusable for SOAP mustUnderstand faults
Wednesday, 8 June 2005
- RE: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: [soapbuilders] current best practice for using WS-Addressing in WSDL 1.1?
- RE: [soapbuilders] current best practice for using WS-Addressing in WSDL 1.1?
- current best practice for using WS-Addressing in WSDL 1.1?
- Re: Another go at lc75 and lc88 language (correction)
- RE: Another go at lc75 and lc88 language (correction)
- RE: Another go at lc75 and lc88 language (correction)
- RE: Another go at lc75 and lc88 language (correction)
- RE: Another go at lc75 and lc88 language (correction)
Tuesday, 7 June 2005
- 2nd CFP: European Conference on Web Services (ECOWS 2005)
- RE: Another go at lc75 and lc88 language (correction)
Monday, 6 June 2005
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- RE: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: Another go at lc75 and lc88 language (correction)
- Re: on LC75
- Re: Another go at lc75 and lc88 language
- RE: Another go at lc75 and lc88 language (correction)
- Another go at lc75 and lc88 language