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

Friday, 31 January 2003

• [MTF] Definition of management terms Heather Kreger

Thursday, 30 January 2003

• RE: Summary of WSA January F2F meeting Champion, Mike
• Re: Summary of WSA January F2F meeting Mark Baker
• RE: Whither MEP and Feature discussions? Don Mullen
• RE: [MTF] Virtual Face to Face Cutler, Roger (RogerCutler)
• Summary of WSA January F2F meeting Mike Champion

Tuesday, 28 January 2003

• [MTF} Deliverables and Dates Heather Kreger

Sunday, 26 January 2003

• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: RM and Intermediaries Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• RE: RM and Intermediaries Ricky Ho
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• RE: RM and Intermediaries Burdett, David
• RE: RM and Intermediaries Assaf Arkin
• RE: RM and Intermediaries Ugo Corda

Saturday, 25 January 2003

• RE: RM and Intermediaries Champion, Mike
• RM and Intermediaries Ricky Ho

Friday, 24 January 2003

• Re: Whither MEP and Feature discussions? Amelia A. Lewis
• Whither MEP and Feature discussions? David Orchard

Thursday, 23 January 2003

• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• MEP text from break-out session M. Jones
• MEPs Don Mullen
• FW: Some notes on the Request-Response MEP, prompted by asynchron icity Don Mullen
• RE: Proposed text on reliability in the web services architecture Jean-Jacques Dubray
• OWL overview Daniel_Austin@grainger.com

Wednesday, 22 January 2003

• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Miles Sabin
• Re: Proposed text on reliability in the web services architecture Bill de hÓra
• RE: Proposed text on reliability in the web services architecture Assaf Arkin

Tuesday, 21 January 2003

• Re: Proposed text on reliability in the web services architecture Miles Sabin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Miles Sabin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Miles Sabin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Miles Sabin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Cutler, Roger (RogerCutler)
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Miles Sabin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Cutler, Roger (RogerCutler)
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Peter Furniss
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Miles Sabin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Miles Sabin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Bill de hÓra
• Re: The Web Services Architecture WG position on XML profiling/subset ting noah_mendelsohn@us.ibm.com
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Cutler, Roger (RogerCutler)

Monday, 20 January 2003

• RE: Proposed text on reliability in the web services architecture Champion, Mike
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• [MTF] Management Face to Face at the Face to Face? Heather Kreger

Sunday, 19 January 2003

• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Walden Mathews

Friday, 17 January 2003

• Re: Proposed text on reliability in the web services architecture Doug Bunting
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• Re: The Web Services Architecture WG position on XML profiling/subsetting Paul Grosso
• Re: The Web Services Architecture WG position on XML profiling/subset ting noah_mendelsohn@us.ibm.com
• The Web Services Architecture WG position on XML profiling/subset ting Champion, Mike
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Hao He

Thursday, 16 January 2003

• RE: Proposed text on reliability in the web services architecture Hao He
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Toward a more precise and accurate discussion of Discovery David Booth
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• [MTF] Can MTF Meet Friday? Heather Kreger
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• Web Services Choreography WG established by W3C Champion, Mike
• Re: Proposed text on reliability in the web services architecture Bill de hÓra
• Re: Loose coupling is like pornography Doug Kaye
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Proposed text on reliability in the web services architecture S. Mike Dierken
• RE: Proposed text on reliability in the web services architecture Hao He
• Re: Proposed text on reliability in the web services architecture Walden Mathews

Wednesday, 15 January 2003

• RE: programming model for document-style SOAP Hao He
• RE: programming model for document-style SOAP Anne Thomas Manes
• RE: programming model for document-style SOAP Ugo Corda
• RE: programming model for document-style SOAP Assaf Arkin
• RE: programming model for document-style SOAP Assaf Arkin
• RE: programming model for document-style SOAP Anne Thomas Manes
• RE: programming model for document-style SOAP Anne Thomas Manes
• RE: programming model for document-style SOAP Anne Thomas Manes
• RE: programming model for document-style SOAP Sunit
• RE: programming model for document-style SOAP Assaf Arkin
• RE: programming model for document-style SOAP Hao He
• RE: Summing up on visibility(?) Assaf Arkin
• RE: programming model for document-style SOAP Assaf Arkin
• RE: Myth of loose coupling Assaf Arkin
• RE: Myth of loose coupling Assaf Arkin
• RE: programming model for document-style SOAP Hao He
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: programming model for document-style SOAP Anne Thomas Manes
• RE: Summing up on visibility(?) Assaf Arkin

Tuesday, 14 January 2003

• RE: programming model for document-style SOAP Hao He
• RE: programming model for document-style SOAP Christian Hoertnagl
• Oops - Nevermind. Richard Katz

Monday, 13 January 2003

• WS-Reliability - in tune with S010? Richard Katz
• Re: [Fwd: Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices] Duane Nickull
• RE: Summing up on visibility(?) (really, I mean it this time 8-) Champion, Mike
• Re: [Fwd: Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices] Mark Baker

Sunday, 12 January 2003

• Re: Summing up on visibility(?) Mark Baker
• RE: Summing up on visibility(?) Anne Thomas Manes
• Re: Summing up on visibility(?) Mark Baker
• Re: Generic URI things Mark Baker
• Re: Summing up on visibility(?) (really, I mean it this time 8-) Mark Baker

Saturday, 11 January 2003

• Re: Proposed text on reliability in the web services architecture Walden Mathews
• Re: Proposed text on reliability in the web services architecture Paul Prescod

Friday, 10 January 2003

• Re: Summing up on visibility(?) S. Mike Dierken
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Summing up on visibility(?) Walden Mathews

Thursday, 9 January 2003

• Re: Proposed text on reliability in the web services architecture Walden Mathews

Friday, 10 January 2003

• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: The other concensus problem Assaf Arkin
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• RE: Summing up on visibility(?) Assaf Arkin
• RE: Generic URI things Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: The other concensus problem Assaf Arkin
• RE: The other concensus problem Assaf Arkin
• Re: Can anyone point us to information on WS-Reliability Fred Carter
• RE: Proposed text on reliability in the web services architecture Jean-Jacques Dubray
• RE: Loose coupling is like pornography Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Generic URI things S. Mike Dierken
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Generic URI things Christopher B Ferris
• RE: Can anyone point us to information on WS-Reliability Assaf Arkin
• RE: Summing up on visibility(?) (really, I mean it this time 8-) Christopher B Ferris
• RE: Summing up on visibility(?) (really, I mean it this time 8-) Champion, Mike
• RE: Can anyone point us to information on WS-Reliability Ricky Ho
• Re: Summing up on visibility(?) (really, I mean it this time 8-) Mark Baker
• RE: Summing up on visibility(?) Champion, Mike
• Re: Summing up on visibility(?) Miles Sabin
• Re: Summing up on visibility(?) Mark Baker
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• RE: Proposed text on reliability in the web services architecture Jean-Jacques Dubray
• Re: Summing up on visibility(?) Miles Sabin
• RE: Loose coupling is like pornography Edwin Khodabakchian
• RE: Loose coupling is like pornography Assaf Arkin
• RE: Can anyone point us to information on WS-Reliability Assaf Arkin
• RE: Loose coupling is like pornography Hao He
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Summing up on visibility(?) Assaf Arkin
• RE: Summing up on visibility(?) Assaf Arkin
• Re: Summing up on visibility(?) Walden Mathews
• RE: Summing up on visibility(?) Assaf Arkin
• RE: Loose coupling is like pornography Assaf Arkin
• RE: Summing up on visibility(?) Edwin Khodabakchian
• RE: Can anyone point us to information on WS-Reliability Hao He
• RE: Summing up on visibility(?) Champion, Mike
• RE: Can anyone point us to information on WS-Reliability Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• Re: Summing up on visibility(?) Christopher B Ferris
• Re: Summing up on visibility(?) S. Mike Dierken
• The other concensus problem Mark Baker
• RE: Loose coupling is like pornography Hao He
• Re: Summing up on visibility(?) Walden Mathews
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• Re: Loose coupling is like pornography Walden Mathews
• Re: Summing up on visibility(?) Mark Baker
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Loose coupling is like pornography Assaf Arkin

Thursday, 9 January 2003

• Loose coupling is like pornography Hao He
• RE: Proposed text on reliability in the web services architecture David Orchard
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• RE: Proposed text on reliability in the web services architecture [long] Assaf Arkin
• RE: Proposed text on reliability in the web services architecture Assaf Arkin
• Re: Summing up on visibility(?) Christopher B Ferris
• Link to Microsoft third party ebXML info Duane Nickull
• RE: Summing up on visibility(?) Assaf Arkin
• RE: Summing up on visibility(?) Assaf Arkin
• [Fwd: [ebxml-msg] about Web Services Reliability and ebMS] Duane Nickull
• Re: Proposed text on reliability in the web services architecture [long] Walden Mathews
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• RE: [MTF] Call Reminder for today ECKERT,ZULAH (HP-Cupertino,ex1)
• RE: Proposed text on reliability in the web services architecture Jean-Jacques Dubray
• Partial regrets for 1-9-03 call Zimek, Sinisa
• Regrets for telecon. Sadiq, Waqar
• RE: Summing up on visibility(?) Champion, Mike
• RE: Proposed text on reliability in the web services architecture Cutler, Roger (RogerCutler)
• RE: Proposed text on reliability in the web services architecture [lo ng] Champion, Mike
• RE: Proposed text on reliability in the web services architecture [lo ng] Cutler, Roger (RogerCutler)
• Re: Summing up on visibility(?) Mark Baker
• Re: Summing up on visibility(?) Miles Sabin
• [Fwd: Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices] Duane Nickull
• RE: [MTF] Call Reminder for today Sedukhin, Igor
• Web Services I18N Usage Scenarios published Champion, Mike
• RE: Summing up on visibility(?) Champion, Mike
• possible regrets for today's call Abbie Barbir
• Re: Summing up on visibility(?) Mark Baker
• RE: Overhauling the discovery part of the architecture document David Booth
• Re: Summing up on visibility(?) Miles Sabin
• Re: Proposed text on reliability in the web services architecture Mark Baker
• RE: Overhauling the discovery part of the architecture document Ugo Corda
• Re: Summing up on visibility(?) Mark Baker
• Re: Summing up on visibility(?) Mark Baker
• Re: Summing up on visibility(?) Miles Sabin
• RE: Summing up on visibility(?) Champion, Mike
• RE: Proposed text on reliability in the web services architecture bhaugen
• RE: Proposed text on reliability in the web services architecture Jean-Jacques Dubray
• Re: Summing up on visibility(?) Mark Baker
• RE: Summing up on visibility(?) Ugo Corda
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• RE: Proposed text on reliability in the web services architecture bhaugen
• Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices Duane Nickull
• RE: Proposed text on reliability in the web services architecture bhaugen
• RE: Proposed text on reliability in the web services architecture [long] Peter Furniss
• RE: Proposed text on reliability in the web services architecture Xu, Jenny
• Re: Proposed text on reliability in the web services architecture Mark Baker
• RE: Proposed text on reliability in the web services architecture Jean-Jacques Dubray
• RE: Proposed text on reliability in the web services architecture Jean-Jacques Dubray
• Re: Summing up on visibility(?) Miles Sabin
• RE: Summing up on visibility(?) Champion, Mike
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• Re: Proposed text on reliability in the web services architecture [long] Walden Mathews
• RE: Overhauling the discovery part of the architecture document Cutler, Roger (RogerCutler)
• RE: Proposed text on reliability in the web services architecture bhaugen
• Re: Summing up on visibility(?) Mark Baker
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• Re: Proposed text on reliability in the web services architecture Mark Baker
• RE: Proposed text on reliability in the web services architecture bhaugen
• RE: Proposed text on reliability in the web services architecture Peter Furniss
• RE: Proposed text on reliability in the web services architecture [lo ng] Peter Furniss
• Re: REST and agents Mark Baker
• RE: Proposed text on reliability in the web services architecture Champion, Mike
• Re: Proposed text on reliability in the web services architecture Walden Mathews
• RE: Myth of loose coupling Jean-Jacques Dubray
• Overhauling the discovery part of the architecture document Hugo Haas
• Re: Summing up on visibility(?) Miles Sabin
• Re: REST and agents Miles Sabin
• Re: Can anyone point us to information on WS-Reliability Jeff Mischkinsky
• Can anyone point us to information on WS-Reliability Champion, Mike
• Re: Summing up on visibility(?) Mark Baker
• RE: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices Champion, Mike
• Re: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices Sanjiva Weerawarana
• RE: Myth of loose coupling Newcomer, Eric
• RE: InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices David Orchard
• RE: Myth of loose coupling David Orchard
• RE: Myth of loose coupling Assaf Arkin
• RE: Incorporating the REST and Loose Coupling threads into the WS A document (was RE: Myth of loose coupling) Hao He
• RE: Myth of loose coupling Assaf Arkin
• InfoWorld: OASIS seeks URI scheme that accommodates XML, Web serv ices Champion, Mike
• Proposed text on reliability in the web services architecture [lo ng] Champion, Mike
• RE: programming model for document-style SOAP Hao He

Wednesday, 8 January 2003

• Re: Generic URI things Mark Baker
• Re: Generic URI things Mark Baker
• RE: Summing up on visibility(?) Ugo Corda
• Summing up on visibility(?) Mark Baker
• Re: REST and agents bhaugen
• Re: Dynamic invocation vs. late/dynamic binding James M Snell
• REST and agents Francis McCabe
• Re: Generic URI things Christopher B Ferris
• [MTF] Call Reminder for today Heather Kreger
• Re: Myth of loose coupling Walden Mathews
• Re: Myth of loose coupling Walden Mathews
• Re: Myth of loose coupling Walden Mathews
• Re: Myth of loose coupling Walden Mathews
• RE: Generic URI things Abbie Barbir
• Re: Generic URI things Miles Sabin
• Re: Generic URI things Mark Baker
• Re: Generic URI things Miles Sabin
• RE: programming model for document-style SOAP Champion, Mike
• RE: Myth of loose coupling Champion, Mike
• RE: Myth of loose coupling Jean-Jacques Dubray
• Incorporating the REST and Loose Coupling threads into the WSA do cument (was RE: Myth of loose coupling) Champion, Mike
• Re: Binding Christopher B Ferris
• RE: Myth of loose coupling Champion, Mike
• Generic URI things Mark Baker
• RE: Myth of loose coupling Abbie Barbir
• RE: Myth of loose coupling Champion, Mike
• Re: Myth of loose coupling Mark Baker
• Re: Myth of loose coupling Walden Mathews
• Re: Binding Walden Mathews
• RE: programming model for document-style SOAP Anne Thomas Manes
• programming model for document-style SOAP Christian Hoertnagl
• Re: Myth of loose coupling Walden Mathews
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) Sanjiva Weerawarana
• Re: Binding Miles Sabin
• RE: Semantic Web needed for RESTful Web services? (RE: Binding) Peter Furniss
• Re: Dynamic invocation vs. late/dynamic binding Mark Baker
• RE: Myth of loose coupling David Orchard
• RE: Myth of loose coupling Hao He
• Re: Binding Mark Baker
• RE: Dynamic invocation vs. late/dynamic binding Edwin Khodabakchian
• Re: Dynamic invocation vs. late/dynamic binding Mark Baker
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) Sanjiva Weerawarana
• RE: Myth of loose coupling David Orchard
• Re: Dynamic invocation vs. late/dynamic binding Sanjiva Weerawarana
• Re: Dynamic invocation vs. late/dynamic binding Walden Mathews
• Re: Myth of loose coupling Walden Mathews
• RE: Binding Champion, Mike
• Re: Binding Mark Baker
• Re: Myth of loose coupling Walden Mathews

Tuesday, 7 January 2003

• Re: Binding Christopher B Ferris
• Re: Binding Miles Sabin
• Re: Myth of loose coupling David Jacobs
• Re: Binding Mark Baker
• Re: Dynamic invocation vs. late/dynamic binding James M Snell
• Re: Dynamic invocation vs. late/dynamic binding Walden Mathews
• Re: Binding Miles Sabin
• RE: Myth of loose coupling David Orchard
• RE: Myth of loose coupling David Orchard
• RE: Myth of loose coupling David Orchard
• Re: Dynamic invocation vs. late/dynamic binding James M Snell
• Re: Dynamic invocation vs. late/dynamic binding Mark Baker
• RE: Semantic Web needed for RESTful Web services? (RE: Binding) Edwin Khodabakchian
• Re: Dynamic invocation vs. late/dynamic binding Sanjiva Weerawarana
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) Sanjiva Weerawarana
• Re: Myth of loose coupling David Jacobs
• RE: Semantic Web needed for RESTful Web services? (RE: Binding) Edwin Khodabakchian
• RE: Myth of loose coupling Ugo Corda
• Re: [xml-dist-app] <none> Joseph Reagle
• Dynamic invocation vs. late/dynamic binding Mark Baker
• Re: Myth of loose coupling David Jacobs
• RE: Binding James M Snell
• Re: Myth of loose coupling David Jacobs
• RE: Binding Abbie Barbir
• RE: Myth of loose coupling Ugo Corda
• Re: Myth of loose coupling Francis McCabe
• RE: Binding James M Snell
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) Sanjiva Weerawarana
• Re: Myth of loose coupling Jacobs,David B.
• Re: Semantic Web needed for RESTful Web services? (RE: Binding) Mark Baker
• RE: Binding Abbie Barbir
• Re: Binding Walden Mathews
• RE: Myth of loose coupling Jean-Jacques Dubray
• RE: BTP without RM scenario Peter Furniss
• RE: Binding Abbie Barbir
• Re: Binding Christopher B Ferris
• Semantic Web needed for RESTful Web services? (RE: Binding) Champion, Mike
• Re: Binding Miles Sabin
• RE: Myth of loose coupling Assaf Arkin
• RE: Myth of loose coupling Assaf Arkin
• Re: Myth of loose coupling Jacobs,David B.
• Re: Myth of loose coupling Jacobs,David B.
• RE: Myth of loose coupling Assaf Arkin
• RE: Myth of loose coupling Assaf Arkin
• Re: Myth of loose coupling David Jacobs
• Re: Binding Mark Baker
• RE: Myth of loose coupling Edwin Khodabakchian
• RE: Myth of loose coupling Assaf Arkin
• WS-friendly XML profile? Champion, Mike
• Re: Binding Mark Baker
• RE: A different binding example (was RE: Binding) Edwin Khodabakchian
• Re: Binding Christopher B Ferris
• RE: Myth of loose coupling Edwin Khodabakchian
• RE: A different binding example (was RE: Binding) Champion, Mike
• Re: Binding Walden Mathews
• Re: REST; good for humans and machines Mark Baker
• RE: Myth of loose coupling Edwin Khodabakchian
• RE: Myth of loose coupling Ugo Corda
• Re: Binding Mark Baker
• RE: Myth of loose coupling Champion, Mike
• RE: A different binding example (was RE: Binding) Ugo Corda
• Re: A Modest Proposal (was RE: Binding) Walden Mathews
• RE: A different binding example (was RE: Binding) Champion, Mike
• RE: A Modest Proposal (was RE: Binding) Champion, Mike
• Re: Terminology (was RE: Issue 5 and "webarch") Walden Mathews

Monday, 6 January 2003

• RE: A different binding example (was RE: Binding) Ugo Corda
• Re: [xml-dist-app] <none> noah_mendelsohn@us.ibm.com
• RE: REST; good for humans and machines Peter Furniss
• RE: A different binding example (was RE: Binding) Edwin Khodabakchian
• RE: A different binding example (was RE: Binding) Ugo Corda
• Re: Binding James M Snell
• RE: A different binding example (was RE: Binding) Edwin Khodabakchian
• Re: Binding Miles Sabin
• RE: Binding Ugo Corda
• Re: Binding Miles Sabin
• RE: Binding Peter Furniss
• RE: A Modest Proposal (was RE: Binding) David Orchard
• Re: Binding Francis McCabe
• Re: A Modest Proposal (was RE: Binding) Mark Baker
• Re: A different binding example (was RE: Binding) Mark Baker
• RE: Myth of loose coupling David Orchard
• A different binding example (was RE: Binding) Champion, Mike
• Re: Binding Mark Baker
• RE: Myth of loose coupling Edwin Khodabakchian
• Re: Binding Mark Baker
• RE: A Modest Proposal (was RE: Binding) Champion, Mike
• RE: Binding David Orchard
• Re: Binding Miles Sabin
• RE: A Modest Proposal (was RE: Binding) David Orchard
• RE: Binding David Orchard
• Myth of loose coupling David Orchard
• RE: Binding David Orchard
• RE: Issue 5; GET vs GetLastTradePrice Christopher B Ferris
• RE: WS-I and RPC Burdett, David
• RE: WS-I and RPC Burdett, David
• Re: Binding Geoff Arnold
• Re: Binding Miles Sabin
• RE: A Modest Proposal (was RE: Binding) David Orchard
• Re: Binding Mark Baker
• Re: A Modest Proposal (was RE: Binding) Mark Baker
• RE: Binding Jean-Jacques Dubray
• RE: A Modest Proposal (was RE: Binding) Abbie Barbir
• Re: Binding Miles Sabin
• A Modest Proposal (was RE: Binding) Champion, Mike
• Re: Binding Mark Baker
• Re: Binding Miles Sabin
• Re: Binding Mark Baker
• Re: REST; good for humans and machines Christopher B Ferris
• Re: REST; good for humans and machines Walden Mathews
• RE: WS-I and RPC Assaf Arkin
• RE: WS-I and RPC Assaf Arkin
• Re: Binding Miles Sabin
• RE: WS-I and RPC Edwin Khodabakchian
• Re: WS-I and RPC Mark Baker
• Terminology (was RE: Issue 5 and "webarch") Champion, Mike
• RE: WS-I and RPC Assaf Arkin
• Re: Binding Mark Baker
• RE: REST; good for humans and machines Assaf Arkin
• Re: REST; good for humans and machines Walden Mathews
• WS-I and RPC Mark Baker
• RE: Binding Champion, Mike
• RE: REST; good for humans and machines Assaf Arkin
• RE: Binding Ugo Corda
• Re: REST; good for humans and machines Walden Mathews
• Re: Issue 5 and "webarch" Mark Baker
• Re: Issue 5 and "webarch" Walden Mathews
• Re: Issue 5 and "webarch" Walden Mathews
• RE: REST; good for humans and machines Assaf Arkin

Sunday, 5 January 2003

• Re: REST; good for humans and machines Mark Baker
• RE: Issue 5 and "webarch" David Orchard
• RE: Binding Champion, Mike
• Re: Binding Miles Sabin
• RE: REST; good for humans and machines Champion, Mike
• Re: Binding Mark Baker
• RE: REST; good for humans and machines Assaf Arkin
• RE: Issue 5 and "webarch" Assaf Arkin
• RE: Binding Champion, Mike
• Re: REST; good for humans and machines Mark Baker
• RE: REST; good for humans and machines Assaf Arkin
• Re: Binding Miles Sabin
• Re: REST; good for humans and machines Mark Baker
• Binding Mark Baker
• RE: REST; good for humans and machines Newcomer, Eric
• Re: REST; good for humans and machines Geoff Arnold
• Re: REST; good for humans and machines Mark Baker
• Re: REST; good for humans and machines Geoff Arnold
• Re: REST; good for humans and machines Miles Sabin
• RE: Issue 5 and "webarch" David Orchard
• RE: Issue 5 and "webarch" Ugo Corda
• Re: REST; good for humans and machines Mark Baker
• RE: Issue 5 and "webarch" Newcomer, Eric
• Re: Issue 5 and "webarch" Mark Baker
• RE: REST; good for humans and machines Champion, Mike
• RE: Issue 5 and "webarch" Champion, Mike
• RE: Issue 5 and "webarch" Newcomer, Eric
• RE: REST; good for humans and machines Newcomer, Eric
• Re: Issue 5 and "webarch" Mark Baker
• Re: REST; good for humans and machines Mark Baker
• RE: Issue 5 and "webarch" Champion, Mike

Saturday, 4 January 2003

• RE: REST; good for humans and machines Champion, Mike
• REST; good for humans and machines Mark Baker
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews

Friday, 3 January 2003

• RE: Issue 5; GET vs GetLastTradePrice Champion, Mike
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews
• RE: Issue 5; GET vs GetLastTradePrice Katia Sycara
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews
• Re: [xml-dist-app] <none> Rich Salz
• Re: Issue 5; GET vs GetLastTradePrice Roy T. Fielding
• Issue 5 and "webarch" Mark Baker

Thursday, 2 January 2003

• [www-ws-arch] <none> David Orchard
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews
• RE: Issue 5; GET vs GetLastTradePrice David Orchard
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews
• RE: Issue 5; GET vs GetLastTradePrice Abbie Barbir
• RE: Issue 5; GET vs GetLastTradePrice Katia Sycara
• RE: Useful article on WS Choreography Jean-Jacques Dubray
• HTTP authentication & timeouts Mark Baker
• RE: Issue 5; GET vs GetLastTradePrice Assaf Arkin
• RE: Issue 5; GET vs GetLastTradePrice Champion, Mike
• Useful article on WS Choreography Champion, Mike
• RE: Issue 5; GET vs GetLastTradePrice David Orchard
• RE: Issue 5; GET vs GetLastTradePrice Champion, Mike
• RE: Issue 5; GET vs GetLastTradePrice David Orchard
• GET vs GetLastTradePrice...Is a unified interface bad? Edwin Khodabakchian
• Re: Issue 5; GET vs GetLastTradePrice Mark Baker
• Re: Issue 5; GET vs GetLastTradePrice Mark Baker
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews
• RE: Issue 5; GET vs GetLastTradePrice David Orchard
• Re: Issue 5; GET vs GetLastTradePrice Francis McCabe
• RE: Issue 5; GET vs GetLastTradePrice David Orchard
• RE: Issue 5; GET vs GetLastTradePrice Champion, Mike
• RE: Issue 5; GET vs GetLastTradePrice Newcomer, Eric
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews
• RE: Issue 5; GET vs GetLastTradePrice Champion, Mike
• RE: Issue 5; GET vs GetLastTradePrice Newcomer, Eric
• RE: Issue 5; GET vs GetLastTradePrice Champion, Mike
• Re: Issue 5; GET vs GetLastTradePrice Walden Mathews
• RE: Issue 5; GET vs GetLastTradePrice Newcomer, Eric
• Issue 5; GET vs GetLastTradePrice Mark Baker
• Issue 5; GET vs GetLastTradePrice Mark Baker

Wednesday, 1 January 2003

• RE: Hypermedia vs. data (long) Assaf Arkin
• Re: Hypermedia vs. data (long) bhaugen
• Re: Hypermedia vs. data (long) Miles Sabin
• RE: Hypermedia vs. data (long) Champion, Mike
• RE: Hypermedia vs. data (long) Newcomer, Eric
• Re: Hypermedia vs. data (long) bhaugen

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