www-ws-arch@w3.org from January 2003 by author

Abbie Barbir

• possible regrets for today's call (Thursday, 9 January)
• RE: Generic URI things (Wednesday, 8 January)
• RE: Myth of loose coupling (Wednesday, 8 January)
• RE: Binding (Tuesday, 7 January)
• RE: Binding (Tuesday, 7 January)
• RE: Binding (Tuesday, 7 January)
• RE: A Modest Proposal (was RE: Binding) (Monday, 6 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)

Amelia A. Lewis

• Re: Whither MEP and Feature discussions? (Friday, 24 January)

Anne Thomas Manes

• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: Summing up on visibility(?) (Sunday, 12 January)
• RE: programming model for document-style SOAP (Wednesday, 8 January)

Assaf Arkin

• RE: Proposed text on reliability in the web services architecture (Sunday, 26 January)
• RE: RM and Intermediaries (Sunday, 26 January)
• RE: Proposed text on reliability in the web services architecture (Sunday, 26 January)
• RE: RM and Intermediaries (Sunday, 26 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 23 January)
• RE: Proposed text on reliability in the web services architecture (Wednesday, 22 January)
• RE: Proposed text on reliability in the web services architecture (Wednesday, 22 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Sunday, 19 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 17 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 17 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: Summing up on visibility(?) (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: Myth of loose coupling (Wednesday, 15 January)
• RE: Myth of loose coupling (Wednesday, 15 January)
• RE: Proposed text on reliability in the web services architecture (Wednesday, 15 January)
• RE: Proposed text on reliability in the web services architecture (Wednesday, 15 January)
• RE: Summing up on visibility(?) (Wednesday, 15 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: The other concensus problem (Friday, 10 January)
• RE: Summing up on visibility(?) (Friday, 10 January)
• RE: Generic URI things (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: The other concensus problem (Friday, 10 January)
• RE: The other concensus problem (Friday, 10 January)
• RE: Loose coupling is like pornography (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Can anyone point us to information on WS-Reliability (Friday, 10 January)
• RE: Loose coupling is like pornography (Friday, 10 January)
• RE: Can anyone point us to information on WS-Reliability (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Summing up on visibility(?) (Friday, 10 January)
• RE: Summing up on visibility(?) (Friday, 10 January)
• RE: Summing up on visibility(?) (Friday, 10 January)
• RE: Loose coupling is like pornography (Friday, 10 January)
• RE: Can anyone point us to information on WS-Reliability (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Loose coupling is like pornography (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture [long] (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Summing up on visibility(?) (Thursday, 9 January)
• RE: Summing up on visibility(?) (Thursday, 9 January)
• RE: Myth of loose coupling (Thursday, 9 January)
• RE: Myth of loose coupling (Thursday, 9 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: WS-I and RPC (Monday, 6 January)
• RE: WS-I and RPC (Monday, 6 January)
• RE: WS-I and RPC (Monday, 6 January)
• RE: REST; good for humans and machines (Monday, 6 January)
• RE: REST; good for humans and machines (Monday, 6 January)
• RE: REST; good for humans and machines (Monday, 6 January)
• RE: REST; good for humans and machines (Sunday, 5 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)
• RE: REST; good for humans and machines (Sunday, 5 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Hypermedia vs. data (long) (Wednesday, 1 January)

bhaugen

• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Re: REST and agents (Wednesday, 8 January)
• Re: Hypermedia vs. data (long) (Wednesday, 1 January)
• Re: Hypermedia vs. data (long) (Wednesday, 1 January)

Bill de hÓra

• Re: Proposed text on reliability in the web services architecture (Wednesday, 22 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 16 January)

Burdett, David

• RE: RM and Intermediaries (Sunday, 26 January)
• RE: WS-I and RPC (Monday, 6 January)
• RE: WS-I and RPC (Monday, 6 January)

Champion, Mike

• RE: Summary of WSA January F2F meeting (Thursday, 30 January)
• RE: Proposed text on reliability in the web services architecture (Sunday, 26 January)
• RE: RM and Intermediaries (Saturday, 25 January)
• RE: Proposed text on reliability in the web services architecture (Monday, 20 January)
• The Web Services Architecture WG position on XML profiling/subset ting (Friday, 17 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• Web Services Choreography WG established by W3C (Thursday, 16 January)
• RE: Summing up on visibility(?) (really, I mean it this time 8-) (Monday, 13 January)
• RE: Summing up on visibility(?) (really, I mean it this time 8-) (Friday, 10 January)
• RE: Summing up on visibility(?) (Friday, 10 January)
• RE: Summing up on visibility(?) (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Summing up on visibility(?) (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture [lo ng] (Thursday, 9 January)
• Web Services I18N Usage Scenarios published (Thursday, 9 January)
• RE: Summing up on visibility(?) (Thursday, 9 January)
• RE: Summing up on visibility(?) (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Summing up on visibility(?) (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Can anyone point us to information on WS-Reliability (Thursday, 9 January)
• RE: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices (Thursday, 9 January)
• InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices (Thursday, 9 January)
• Proposed text on reliability in the web services architecture [lo ng] (Thursday, 9 January)
• RE: programming model for document-style SOAP (Wednesday, 8 January)
• RE: Myth of loose coupling (Wednesday, 8 January)
• Incorporating the REST and Loose Coupling threads into the WSA do cument (was RE: Myth of loose coupling) (Wednesday, 8 January)
• RE: Myth of loose coupling (Wednesday, 8 January)
• RE: Myth of loose coupling (Wednesday, 8 January)
• RE: Binding (Wednesday, 8 January)
• Semantic Web needed for RESTful Web services? (RE: Binding) (Tuesday, 7 January)
• WS-friendly XML profile? (Tuesday, 7 January)
• RE: A different binding example (was RE: Binding) (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: A different binding example (was RE: Binding) (Tuesday, 7 January)
• RE: A Modest Proposal (was RE: Binding) (Tuesday, 7 January)
• A different binding example (was RE: Binding) (Monday, 6 January)
• RE: A Modest Proposal (was RE: Binding) (Monday, 6 January)
• A Modest Proposal (was RE: Binding) (Monday, 6 January)
• Terminology (was RE: Issue 5 and "webarch") (Monday, 6 January)
• RE: Binding (Monday, 6 January)
• RE: Binding (Sunday, 5 January)
• RE: REST; good for humans and machines (Sunday, 5 January)
• RE: Binding (Sunday, 5 January)
• RE: REST; good for humans and machines (Sunday, 5 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)
• RE: REST; good for humans and machines (Saturday, 4 January)
• RE: Issue 5; GET vs GetLastTradePrice (Friday, 3 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Useful article on WS Choreography (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Hypermedia vs. data (long) (Wednesday, 1 January)

Christian Hoertnagl

• RE: programming model for document-style SOAP (Tuesday, 14 January)
• programming model for document-style SOAP (Wednesday, 8 January)

Christopher B Ferris

• Re: Generic URI things (Friday, 10 January)
• RE: Summing up on visibility(?) (really, I mean it this time 8-) (Friday, 10 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Generic URI things (Wednesday, 8 January)
• Re: Binding (Wednesday, 8 January)
• Re: Binding (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• RE: Issue 5; GET vs GetLastTradePrice (Monday, 6 January)
• Re: REST; good for humans and machines (Monday, 6 January)

Cutler, Roger (RogerCutler)

• RE: [MTF] Virtual Face to Face (Thursday, 30 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture [lo ng] (Thursday, 9 January)
• RE: Overhauling the discovery part of the architecture document (Thursday, 9 January)

Daniel_Austin@grainger.com

• OWL overview (Thursday, 23 January)

David Booth

• Toward a more precise and accurate discussion of Discovery (Thursday, 16 January)
• RE: Overhauling the discovery part of the architecture document (Thursday, 9 January)

David Jacobs

• Re: Myth of loose coupling (Tuesday, 7 January)
• Re: Myth of loose coupling (Tuesday, 7 January)
• Re: Myth of loose coupling (Tuesday, 7 January)
• Re: Myth of loose coupling (Tuesday, 7 January)
• Re: Myth of loose coupling (Tuesday, 7 January)

David Orchard

• Whither MEP and Feature discussions? (Friday, 24 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices (Thursday, 9 January)
• RE: Myth of loose coupling (Thursday, 9 January)
• RE: Myth of loose coupling (Wednesday, 8 January)
• RE: Myth of loose coupling (Wednesday, 8 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: A Modest Proposal (was RE: Binding) (Monday, 6 January)
• RE: Myth of loose coupling (Monday, 6 January)
• RE: Binding (Monday, 6 January)
• RE: A Modest Proposal (was RE: Binding) (Monday, 6 January)
• RE: Binding (Monday, 6 January)
• Myth of loose coupling (Monday, 6 January)
• RE: Binding (Monday, 6 January)
• RE: A Modest Proposal (was RE: Binding) (Monday, 6 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)
• [www-ws-arch] <none> (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)

Don Mullen

• RE: Whither MEP and Feature discussions? (Thursday, 30 January)
• MEPs (Thursday, 23 January)
• FW: Some notes on the Request-Response MEP, prompted by asynchron icity (Thursday, 23 January)

Doug Bunting

• Re: Proposed text on reliability in the web services architecture (Friday, 17 January)

Doug Kaye

• Re: Loose coupling is like pornography (Thursday, 16 January)

Duane Nickull

• Re: [Fwd: Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices] (Monday, 13 January)
• Link to Microsoft third party ebXML info (Thursday, 9 January)
• [Fwd: [ebxml-msg] about Web Services Reliability and ebMS] (Thursday, 9 January)
• [Fwd: Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices] (Thursday, 9 January)
• Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices (Thursday, 9 January)

ECKERT,ZULAH (HP-Cupertino,ex1)

• RE: [MTF] Call Reminder for today (Thursday, 9 January)

Edwin Khodabakchian

• RE: Loose coupling is like pornography (Friday, 10 January)
• RE: Summing up on visibility(?) (Friday, 10 January)
• RE: Dynamic invocation vs. late/dynamic binding (Wednesday, 8 January)
• RE: Semantic Web needed for RESTful Web services? (RE: Binding) (Tuesday, 7 January)
• RE: Semantic Web needed for RESTful Web services? (RE: Binding) (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: A different binding example (was RE: Binding) (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: A different binding example (was RE: Binding) (Monday, 6 January)
• RE: A different binding example (was RE: Binding) (Monday, 6 January)
• RE: Myth of loose coupling (Monday, 6 January)
• RE: WS-I and RPC (Monday, 6 January)
• GET vs GetLastTradePrice...Is a unified interface bad? (Thursday, 2 January)

Francis McCabe

• REST and agents (Wednesday, 8 January)
• Re: Myth of loose coupling (Tuesday, 7 January)
• Re: Binding (Monday, 6 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)

Fred Carter

• Re: Can anyone point us to information on WS-Reliability (Friday, 10 January)

Geoff Arnold

• Re: Binding (Monday, 6 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• Re: REST; good for humans and machines (Sunday, 5 January)

Hao He

• RE: Proposed text on reliability in the web services architecture (Friday, 17 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: programming model for document-style SOAP (Tuesday, 14 January)
• RE: Loose coupling is like pornography (Friday, 10 January)
• RE: Can anyone point us to information on WS-Reliability (Friday, 10 January)
• RE: Loose coupling is like pornography (Friday, 10 January)
• Loose coupling is like pornography (Thursday, 9 January)
• RE: Incorporating the REST and Loose Coupling threads into the WS A document (was RE: Myth of loose coupling) (Thursday, 9 January)
• RE: programming model for document-style SOAP (Thursday, 9 January)
• RE: Myth of loose coupling (Wednesday, 8 January)

Heather Kreger

• [MTF] Definition of management terms (Friday, 31 January)
• [MTF} Deliverables and Dates (Tuesday, 28 January)
• [MTF] Management Face to Face at the Face to Face? (Monday, 20 January)
• [MTF] Can MTF Meet Friday? (Thursday, 16 January)
• [MTF] Call Reminder for today (Wednesday, 8 January)

Hugo Haas

• Overhauling the discovery part of the architecture document (Thursday, 9 January)

Jacobs,David B.

• Re: Myth of loose coupling (Tuesday, 7 January)
• Re: Myth of loose coupling (Tuesday, 7 January)
• Re: Myth of loose coupling (Tuesday, 7 January)

James M Snell

• Re: Dynamic invocation vs. late/dynamic binding (Wednesday, 8 January)
• Re: Dynamic invocation vs. late/dynamic binding (Tuesday, 7 January)
• Re: Dynamic invocation vs. late/dynamic binding (Tuesday, 7 January)
• RE: Binding (Tuesday, 7 January)
• RE: Binding (Tuesday, 7 January)
• Re: Binding (Monday, 6 January)

Jean-Jacques Dubray

• RE: Proposed text on reliability in the web services architecture (Thursday, 23 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Friday, 10 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Myth of loose coupling (Thursday, 9 January)
• RE: Myth of loose coupling (Wednesday, 8 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Binding (Monday, 6 January)
• RE: Useful article on WS Choreography (Thursday, 2 January)

Jeff Mischkinsky

• Re: Can anyone point us to information on WS-Reliability (Thursday, 9 January)

Joseph Reagle

• Re: [xml-dist-app] <none> (Tuesday, 7 January)

Katia Sycara

• RE: Issue 5; GET vs GetLastTradePrice (Friday, 3 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)

M. Jones

• MEP text from break-out session (Thursday, 23 January)

Mark Baker

• Re: Summary of WSA January F2F meeting (Thursday, 30 January)
• Re: [Fwd: Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices] (Monday, 13 January)
• Re: Summing up on visibility(?) (Sunday, 12 January)
• Re: Summing up on visibility(?) (Sunday, 12 January)
• Re: Generic URI things (Sunday, 12 January)
• Re: Summing up on visibility(?) (really, I mean it this time 8-) (Sunday, 12 January)
• Re: Summing up on visibility(?) (really, I mean it this time 8-) (Friday, 10 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• The other concensus problem (Friday, 10 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Re: REST and agents (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Generic URI things (Wednesday, 8 January)
• Re: Generic URI things (Wednesday, 8 January)
• Summing up on visibility(?) (Wednesday, 8 January)
• Re: Generic URI things (Wednesday, 8 January)
• Generic URI things (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Dynamic invocation vs. late/dynamic binding (Wednesday, 8 January)
• Re: Binding (Wednesday, 8 January)
• Re: Dynamic invocation vs. late/dynamic binding (Wednesday, 8 January)
• Re: Binding (Wednesday, 8 January)
• Re: Binding (Tuesday, 7 January)
• Re: Dynamic invocation vs. late/dynamic binding (Tuesday, 7 January)
• Dynamic invocation vs. late/dynamic binding (Tuesday, 7 January)
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: REST; good for humans and machines (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: A Modest Proposal (was RE: Binding) (Monday, 6 January)
• Re: A different binding example (was RE: Binding) (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: A Modest Proposal (was RE: Binding) (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: WS-I and RPC (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• WS-I and RPC (Monday, 6 January)
• Re: Issue 5 and "webarch" (Monday, 6 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• Re: Binding (Sunday, 5 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• Binding (Sunday, 5 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• Re: Issue 5 and "webarch" (Sunday, 5 January)
• Re: Issue 5 and "webarch" (Sunday, 5 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• REST; good for humans and machines (Saturday, 4 January)
• Issue 5 and "webarch" (Friday, 3 January)
• HTTP authentication & timeouts (Thursday, 2 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)

Mike Champion

• Summary of WSA January F2F meeting (Thursday, 30 January)

Miles Sabin

• Re: Proposed text on reliability in the web services architecture (Wednesday, 22 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: Summing up on visibility(?) (Thursday, 9 January)
• Re: REST and agents (Thursday, 9 January)
• Re: Generic URI things (Wednesday, 8 January)
• Re: Generic URI things (Wednesday, 8 January)
• Re: Binding (Wednesday, 8 January)
• Re: Binding (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Monday, 6 January)
• Re: Binding (Sunday, 5 January)
• Re: Binding (Sunday, 5 January)
• Re: REST; good for humans and machines (Sunday, 5 January)
• Re: Hypermedia vs. data (long) (Wednesday, 1 January)

Newcomer, Eric

• RE: Myth of loose coupling (Thursday, 9 January)
• RE: REST; good for humans and machines (Sunday, 5 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)
• RE: REST; good for humans and machines (Sunday, 5 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• RE: Hypermedia vs. data (long) (Wednesday, 1 January)

noah_mendelsohn@us.ibm.com

• Re: The Web Services Architecture WG position on XML profiling/subset ting (Tuesday, 21 January)
• Re: The Web Services Architecture WG position on XML profiling/subset ting (Friday, 17 January)
• Re: [xml-dist-app] <none> (Monday, 6 January)

Paul Grosso

• Re: The Web Services Architecture WG position on XML profiling/subsetting (Friday, 17 January)

Paul Prescod

• Re: Proposed text on reliability in the web services architecture (Saturday, 11 January)

Peter Furniss

• RE: Proposed text on reliability in the web services architecture (Tuesday, 21 January)
• RE: Proposed text on reliability in the web services architecture [long] (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• RE: Proposed text on reliability in the web services architecture [lo ng] (Thursday, 9 January)
• RE: Semantic Web needed for RESTful Web services? (RE: Binding) (Wednesday, 8 January)
• RE: BTP without RM scenario (Tuesday, 7 January)
• RE: REST; good for humans and machines (Monday, 6 January)
• RE: Binding (Monday, 6 January)

Rich Salz

• Re: [xml-dist-app] <none> (Friday, 3 January)

Richard Katz

• Oops - Nevermind. (Tuesday, 14 January)
• WS-Reliability - in tune with S010? (Monday, 13 January)

Ricky Ho

• RE: RM and Intermediaries (Sunday, 26 January)
• RM and Intermediaries (Saturday, 25 January)
• RE: Can anyone point us to information on WS-Reliability (Friday, 10 January)

Roy T. Fielding

• Re: Issue 5; GET vs GetLastTradePrice (Friday, 3 January)

S. Mike Dierken

• Re: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Generic URI things (Friday, 10 January)
• Re: Summing up on visibility(?) (Friday, 10 January)

Sadiq, Waqar

• Regrets for telecon. (Thursday, 9 January)

Sanjiva Weerawarana

• Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices (Thursday, 9 January)
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) (Wednesday, 8 January)
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) (Wednesday, 8 January)
• Re: Dynamic invocation vs. late/dynamic binding (Wednesday, 8 January)
• Re: Dynamic invocation vs. late/dynamic binding (Tuesday, 7 January)
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) (Tuesday, 7 January)
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) (Tuesday, 7 January)

Sedukhin, Igor

• RE: [MTF] Call Reminder for today (Thursday, 9 January)

Sunit

• RE: programming model for document-style SOAP (Wednesday, 15 January)

Ugo Corda

• RE: RM and Intermediaries (Sunday, 26 January)
• RE: programming model for document-style SOAP (Wednesday, 15 January)
• RE: Overhauling the discovery part of the architecture document (Thursday, 9 January)
• RE: Summing up on visibility(?) (Thursday, 9 January)
• RE: Summing up on visibility(?) (Wednesday, 8 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: Myth of loose coupling (Tuesday, 7 January)
• RE: A different binding example (was RE: Binding) (Tuesday, 7 January)
• RE: A different binding example (was RE: Binding) (Monday, 6 January)
• RE: A different binding example (was RE: Binding) (Monday, 6 January)
• RE: Binding (Monday, 6 January)
• RE: Binding (Monday, 6 January)
• RE: Issue 5 and "webarch" (Sunday, 5 January)

Walden Mathews

• Re: Proposed text on reliability in the web services architecture (Sunday, 26 January)
• Re: Proposed text on reliability in the web services architecture (Monday, 20 January)
• Re: Proposed text on reliability in the web services architecture (Sunday, 19 January)
• Re: Proposed text on reliability in the web services architecture (Friday, 17 January)
• Re: Proposed text on reliability in the web services architecture (Friday, 17 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 16 January)
• Re: Proposed text on reliability in the web services architecture (Saturday, 11 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Re: Proposed text on reliability in the web services architecture (Friday, 10 January)
• Re: Proposed text on reliability in the web services architecture (Friday, 10 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Summing up on visibility(?) (Friday, 10 January)
• Re: Proposed text on reliability in the web services architecture (Friday, 10 January)
• Re: Loose coupling is like pornography (Friday, 10 January)
• Re: Proposed text on reliability in the web services architecture (Friday, 10 January)
• Re: Proposed text on reliability in the web services architecture [long] (Thursday, 9 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Re: Proposed text on reliability in the web services architecture [long] (Thursday, 9 January)
• Re: Proposed text on reliability in the web services architecture (Thursday, 9 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Binding (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Dynamic invocation vs. late/dynamic binding (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Myth of loose coupling (Wednesday, 8 January)
• Re: Dynamic invocation vs. late/dynamic binding (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: Binding (Tuesday, 7 January)
• Re: A Modest Proposal (was RE: Binding) (Tuesday, 7 January)
• Re: Terminology (was RE: Issue 5 and "webarch") (Tuesday, 7 January)
• Re: REST; good for humans and machines (Monday, 6 January)
• Re: REST; good for humans and machines (Monday, 6 January)
• Re: REST; good for humans and machines (Monday, 6 January)
• Re: Issue 5 and "webarch" (Monday, 6 January)
• Re: Issue 5 and "webarch" (Monday, 6 January)
• Re: Issue 5; GET vs GetLastTradePrice (Saturday, 4 January)
• Re: Issue 5; GET vs GetLastTradePrice (Friday, 3 January)
• Re: Issue 5; GET vs GetLastTradePrice (Friday, 3 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)
• Re: Issue 5; GET vs GetLastTradePrice (Thursday, 2 January)

Xu, Jenny

• RE: Proposed text on reliability in the web services architecture (Thursday, 9 January)

Zimek, Sinisa

• Partial regrets for 1-9-03 call (Thursday, 9 January)

Last message date: Friday, 31 January 2003 14:21:14 UTC