Thursday, 31 March 2005
- Re: Last Call for Web Services Addressing Core and SOAP Binding
- Last Call for Web Services Addressing Core and SOAP Binding
- Minutes for the 2005-03-28 teleconference
Wednesday, 30 March 2005
Monday, 28 March 2005
- Test Case Form Try-out
- Action item for issue i021
- Re: Compromise Proposal [was -- Re: TIBCO objects to last call]
Sunday, 27 March 2005
- Re: Agenda: WS-A telcon 2005-03-28 [NOTE CHANGED TIMES]
- Agenda: WS-A telcon 2005-03-28
- Re: Compromise Proposal [was -- Re: TIBCO objects to last call]
Saturday, 26 March 2005
- Compromise Proposal [was -- Re: TIBCO objects to last call]
- Re: TIBCO objects to last call
- NEW ISSUE: Editorial: bad WSDL 1.1 namespace URI in Example 2.3
- NEW ISSUE: Editorial: WSDL Binding prefix table
Friday, 25 March 2005
- Re: TIBCO objects to last call
- RE: TIBCO objects to last call
- Re: TIBCO objects to last call
- Re: NEW ISSUE: Dependencies with other groups
- Re: TIBCO objects to last call
- RE: TIBCO objects to last call
- RE: TIBCO objects to last call (resend)
Thursday, 24 March 2005
- NEW ISSUE: Dependencies with other groups
- Re: TIBCO objects to last call (resend)
- NEW ISSUE: Should MAPs be divorced from the rest of the specification?
- RE: TIBCO objects to last call (resend)
- Re: TIBCO objects to last call (resend)
- RE: TIBCO objects to last call (resend)
- Re: TIBCO objects to last call (resend)
- Re: TIBCO objects to last call
- RE: TIBCO objects to last call (resend)
- Re: TIBCO objects to last call (resend)
- Re: TIBCO objects to last call
- RE: TIBCO objects to last call (resend)
- RE: TIBCO objects to last call (resend)
- Re: TIBCO objects to last call (resend)
- RE: TIBCO objects to last call (resend)
- RE: TIBCO objects to last call (resend)
Wednesday, 23 March 2005
Thursday, 24 March 2005
Wednesday, 23 March 2005
Tuesday, 22 March 2005
- RE: Demonstrating the obvious
- Use of WSA in other specs.
- Demonstrating the obvious
- Questions about the current draft.
Monday, 21 March 2005
- Who depends on us?
- Re: Agenda: WS-A telcon 2005-03-21
- Re: Agenda: WS-A telcon 2005-03-21
- RE: Agenda: WS-A telcon 2005-03-21
- Re: MAPs and SOAP
- WS_Addressing_Scenarios contribution from Microsoft
- Stepping back a bit ...
- RE: MAPs and SOAP
- Re: MAPs and SOAP
- RE: wsa:Action in responses
- Re: wsa:Action in responses
Sunday, 20 March 2005
- CFP: International Conference on Service-Oriented Computing 2005 (ICSOC' 05)
- Agenda: WS-A telcon 2005-03-21
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints [i054]
Saturday, 19 March 2005
Friday, 18 March 2005
- RE: A minor question
- RE: What does it mean for a MAP to be "mandatory"?
- Re: MAPs and SOAP
- RE: wsa:Action in responses
- RE: MAPs and SOAP
- Re: A minor question
- RE: A minor question
- RE: A minor question
- What does it mean for a MAP to be "mandatory"?
- RE: A minor question
- Re: A minor question
- Re: wsa:Action in responses
- Re: wsa:Action in responses
- RE: A minor question
- RE: A minor question
- Re: A minor question
- Re: MAPs and SOAP
- RE: A minor question
- RE: A minor question
- Re: MAPs and SOAP
Thursday, 17 March 2005
Friday, 18 March 2005
Thursday, 17 March 2005
- RE: MAPs and SOAP
- RE: A minor question
- Re: A minor question
- Re: A minor question
- RE: A minor question
- Which properties are optional depends on the protocol
- Reply-to and in-reply-to are orthogonal
- Re: MAPs and SOAP
- Special treatment for well-known endpoints
- Sketch for request/reply/alternate
- RE: MAPs and SOAP
- Re: MAPs and SOAP
- Re: MAPs and SOAP
Wednesday, 16 March 2005
- RE: wsa:Action in responses
- Re: MAPs and SOAP
- Re: MAPs and SOAP
- RE: MAPs and SOAP
- Re: MAPs and SOAP
- Re: MAPs and SOAP
- Re: MAPs and SOAP
- Re: MAPs and SOAP
- Re: Charter requirements [was: Process requirements for going to Last Call]
- Re: MAPs and SOAP
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints
- Re: Charter requirements [was: Process requirements for going to Last Call]
- Minutes of the 2005-03-14 teleconference
- Re: MAPs and SOAP
Tuesday, 15 March 2005
- Re: Charter requirements [was: Process requirements for going to Last Call]
- Charter requirements [was: Process requirements for going to Last Call]
- RE: NEW ISSUE: Handling arbitrary sets of associated endpoints
- RE: wsa:Action in responses
- SOAP properties in non request/reply interactions
- Re: wsa:Action in responses
- Re: wsa:Action in responses
- Re: wsa:Action in responses
- i050: Characterization of underlying issues and of proposals seen so far
- MAPs and SOAP
- RE: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- Re: Proposing a wsa:Security element
Monday, 14 March 2005
- Re: i050: FaultTo fallback to ReplyTo rule
- i050: FaultTo fallback to ReplyTo rule
- Re: Proposing a wsa:Security element
- Re: Full text for Issue 50 Proposal
- RE: Proposing a wsa:Security element
- Full text for Issue 50 Proposal
- Re: Proposing a wsa:Security element
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints
- Re: Proposing a wsa:Security element
- Re: Why is [destination] defined as an IRI?
- Re: Help on ws-addressing
- Re: Proposing a wsa:Security element
- Re: Proposing a wsa:Security element
- RE: Proposing a wsa:Security element
- Re: Proposing a wsa:Security element
- Re: Proposing a wsa:Security element
- RE: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- Help on ws-addressing
- Section 2.3 - examples
Sunday, 13 March 2005
Saturday, 12 March 2005
- RE: trust model and epr security
- Re: WSA SOAP Binding minor editorial issues
- trust model and epr security
- Proposing a wsa:Security element
- Agenda: WS-A telcon 2005-03-14
Friday, 11 March 2005
- RE: NEW ISSUE: Handling arbitrary sets of associated endpoints
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints
- wsa:Action in responses
- Re: What, if anything, comes back on the HTTP reply if fault is non-default?
- Re: NEW ISSUE: Handling arbitrary sets of associated endpoints
- RE: What, if anything, comes back on the HTTP reply if fault is non-default?
- RE: NEW ISSUE: Handling arbitrary sets of associated endpoints
Thursday, 10 March 2005
- RE: WSA SOAP Binding minor editorial issues
- RE: WSA SOAP Binding minor editorial issues
- NEW ISSUE: Handling arbitrary sets of associated endpoints
- Re: Minutes for the 2005-02-27 F2F
- What, if anything, comes back on the HTTP reply if fault is non-default?
- Lack of layering in WS (Was: RFC 2616 (rfc2616) - Hypertext Transfer Protocol ...)
- Re: Minutes for the 2005-02-27 F2F
- RE: Why is [destination] defined as an IRI?
- RE: Why is [destination] defined as an IRI?
- Why is [destination] defined as an IRI?
- Re: WSA Core minor editorial issues
- Re: WSA SOAP Binding minor editorial issues
- Re: WSA SOAP Binding minor editorial issues
Wednesday, 9 March 2005
- Re: Minutes for the 2005-02-27 F2F
- WSA SOAP Binding minor editorial issues
- RE: Editorial work on issue 53 complete
- Re: Minutes for the 2005-02-27 F2F
- Re: wsa:Type still around?
- Re: New issue: Notification relationship IRI
- RE: Editorial work on issue 53 complete
Tuesday, 8 March 2005
- Re: Editorial work on issue 53 complete
- RE: Editorial work on issue 53 complete
- Minutes of the 2005-03-07 teleconference
- Editorial work on issue 53 complete
- What to do about MAP extensibility, if we need to
- Re: NEW ISSUE: Schema tweaks [i053]
- A minor question
- Request/reply/reply
- Issue 50 and points west
- WSA Core minor editorial issues
- RE: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- RE: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- RE: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- Re: Additional Proposals for Resolving Issue 50
- Additional Proposals for Resolving Issue 50
Monday, 7 March 2005
- RE: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- Minimal Proposed Changes to Resolve Issue 50
- Re: i050: Misalignment of treatment of reply messages and fault messages
- Re: Minutes of the Web Services Addressing / TAG joint meeting
- RE: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- Re: Minutes of the Web Services Addressing / TAG joint meeting
- i050: Misalignment of treatment of reply messages and fault messages
- Re: Minutes of the Web Services Addressing / TAG joint meeting
- Re: Minutes of the Web Services Addressing / TAG joint meeting
- Re: RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- wsa:Type still around?
- RFC 2616 (rfc2616) - Hypertext Transfer Protocol -- HTTP/1.1Re: Minutes of the Web Services Addressing / TAG joint meeting
- Re: Minutes of the Web Services Addressing / TAG joint meeting
Saturday, 5 March 2005
Friday, 4 March 2005
- Minutes for the 2005-02-27 [resend]
- Re: Minutes of the Web Services Addressing / TAG joint meeting
- Re: Minutes of the Web Services Addressing / TAG joint meeting
- Fw: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Minutes of the Web Services Addressing / TAG joint meeting
Thursday, 3 March 2005
- Minutes for the 2005-02-27 F2F
- RE: NEW ISSUE: Schema tweaks
- Apologies for next meeting
- Minutes of the Web Services Addressing / TAG joint meeting
- Re: Summary of decision tree for Addr/Desc groups
- RE: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Fw: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: New issue: Notification relationship IRI
- RE: NEW ISSUE: Schema tweaks
- RE: NEW ISSUE: Schema tweaks
- Re: New issue: Notification relationship IRI
- Re: NEW ISSUE: Schema tweaks
Wednesday, 2 March 2005
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Updated Ed Drafts Available
- RE: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- RE: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- RE: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- New issue: Notification relationship IRI
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: NEW ISSUE: Schema tweaks
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: NEW ISSUE: Schema tweaks
Tuesday, 1 March 2005
- Re: Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: NEW ISSUE: Schema tweaks
- Proposed resolution for Issue 50 (Misallignment of faut to and reply to )
- Re: NEW ISSUE: Schema tweaks
- Can ReferenceParameters contain message addressing properties defined in WS-Addresing core
- Re: i004: Text for reorganization of security sections
- Re: NEW ISSUE: Schema tweaks
- RE: NEW ISSUE: Schema tweaks
- Re: NEW ISSUE: Schema tweaks
- Re: NEW ISSUE: Schema tweaks
- Re: NEW ISSUE: Definition of SOAP 1.2 (and 1.1) modules [i022]
- Relationship in in/out/request/reply
- Re: i004: Text for reorganization of security sections
- Re: i007: new proposal for discussion (was Re: Issue 7 convo from Melbourne)
- i007: new proposal for discussion (was Re: Issue 7 convo from Melbourne)
- FW: Summary of decision tree for Addr/Desc groups
- RE: New ed drafts available.