public-ws-addressing@w3.org from November 2004 by date

Tuesday, 30 November 2004

• RE: i0001: EPRs as identifiers David Booth
• RE: NEW ISSUE: Marking RefProps/RefParams using attributes Srinivas, Davanum M
• NEW ISSUE: Marking RefProps/RefParams using attributes Srinivas, Davanum M

Monday, 29 November 2004

• RE: Issues i034: Action defaults (was Re: Issue 019: WSDL Version Neutrality) Jonathan Marsh
• Re: Agenda: WS-A telcon 2004-11-29 Rich Salz
• RE: Agenda: WS-A telcon 2004-11-29 paul.downey@bt.com
• Re: Agenda: WS-A telcon 2004-11-29 Hugo Haas
• RE: Using attributes to mark RefProp's and RefParam's Glen Daniels
• Re: Using attributes to mark RefProp's and RefParam's Marc Hadley
• Re: i038: Scope of message addressing properties [i038] Marc Hadley
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Steve Graham

Sunday, 28 November 2004

• RE: Agenda: WS-A telcon 2004-11-29 David Orchard
• Agenda: WS-A telcon 2004-11-29 Mark Nottingham
• Re: i0001: EPRs as identifiers Mark Baker

Friday, 26 November 2004

• Re: NEW ISSUE: Securing EPRs Marc Hadley
• Re: Using attributes to mark RefProp's and RefParam's Tom Rutt

Thursday, 25 November 2004

• RE: Using attributes to mark RefProp's and RefParam's Christopher B Ferris
• RE: Using attributes to mark RefProp's and RefParam's Rich Salz
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: Using attributes to mark RefProp's and RefParam's Martin Gudgin
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• Addresses, identifiers, and cookie semantics Mark Baker
• RE: Using attributes to mark RefProp's and RefParam's Christopher B Ferris
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: i0001: EPRs as identifiers Martin Gudgin
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Christopher B Ferris
• RE: Using attributes to mark RefProp's and RefParam's Christopher B Ferris
• RE: Using attributes to mark RefProp's and RefParam's Martin Gudgin
• Re: Composibility problems with refps Mark Baker
• Re: Using attributes to mark RefProp's and RefParam's Mark Baker
• RE: Composibility problems with refps Rich Salz
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: Composibility problems with refps Christopher B Ferris
• RE: Using attributes to mark RefProp's and RefParam's Christopher B Ferris
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: Using attributes to mark RefProp's and RefParam's Christopher B Ferris
• RE: i0001: EPRs as identifiers David Booth
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• Re: NEW ISSUE: Securing EPRs Mark Nottingham
• Re: NEW ISSUE: Replace QName's with anyURI [i037] Mark Nottingham
• Re: NEW ISSUE: WS-Addressing MIME Media Type [i036] Mark Nottingham
• Re: NEW ISSUE: Scope of message addressing properties [i038] Mark Nottingham
• Re: NEW ISSUE: Spec name versioning (editorial) [i039] Mark Nottingham
• RE: Composibility problems with refps Rich Salz

Wednesday, 24 November 2004

• RE: Composibility problems with refps Christopher B Ferris
• RE: Using attributes to mark RefProp's and RefParam's Christopher B Ferris
• RE: Composibility problems with refps Rich Salz
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: Using attributes to mark RefProp's and RefParam's Christopher B Ferris
• RE: Composibility problems with refps David Orchard
• RE: Composibility problems with refps Rich Salz
• RE: Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: Composibility problems with refps Christopher B Ferris
• RE: Composibility problems with refps David Orchard
• RE: Composibility problems with refps Martin Gudgin
• RE: Composibility problems with refps David Orchard
• RE: Composibility problems with refps Martin Gudgin
• RE: i0001: EPRs as identifiers Martin Gudgin
• RE: Composibility problems with refps Martin Gudgin
• RE: i0001: EPRs as identifiers David Booth
• RE: i0001: EPRs as identifiers (implementation model) paul.downey@bt.com
• RE: Composibility problems with refps David Orchard
• Security and self-description (was Re: Composibility problems with refps Mark Baker
• Re: Composibility problems with refps Rich Salz
• Using attributes to mark RefProp's and RefParam's Srinivas, Davanum M
• RE: Composibility problems with refps Christopher B Ferris
• RE: Composibility problems with refps Martin Gudgin
• RE: Composibility problems with refps David Orchard
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Mark Baker
• RE: i0001: EPRs as identifiers (implementation model) David Booth
• NEW ISSUE: Spec name versioning (editorial) Hugo Haas
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Marc Hadley
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Mark Little
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) John Fuller
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Christopher B Ferris
• NEW ISSUE: Securing EPRs Marc Hadley
• Re: Composibility problems with refps Rich Salz
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Mark Baker
• RE: Composibility problems with refps Francisco Curbera
• Issue i021 detailed proposal (was Re: Issue 021: WSDL Extension for Addressing) Hugo Haas
• RE: i0001: EPRs as identifiers (why XML?) Rich Salz
• RE: i0001: EPRs as identifiers (why XML?) Vinoski, Stephen
• Re: i0001: EPRs as identifiers (why XML?) John Fuller
• RE: i0001: EPRs as identifiers (why XML?) Jim Webber
• RE: i0001: EPRs as identifiers (why XML?) paul.downey@bt.com
• RE: i0001: EPRs as identifiers (why XML?) Jim Webber
• Re: ACTION: Rich to begin work on schema Rich Salz
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) David Orchard
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Savas Parastatidis
• Minutes of the 2004-11-22 teleconference Mark Nottingham
• RE: i0001: EPRs as identifiers (why XML?) Rich Salz

Tuesday, 23 November 2004

• RE: i0001: EPRs as identifiers (why XML?) Vinoski, Stephen
• RE: i0001: EPRs as identifiers (why XML?) Vinoski, Stephen
• RE: NEW ISSUE: Scope of message addressing properties David Orchard
• Re: NEW ISSUE: Scope of message addressing properties Tom Rutt
• NEW ISSUE: Scope of message addressing properties Marc Hadley
• Re: Composibility problems with refps Marc Hadley
• Re: Composibility problems with refps Rich Salz
• RE: NEW ISSUE: Replace QName's with anyURI David Orchard
• RE: Composibility problems with refps David Orchard
• Re: NEW ISSUE: Replace QName's with anyURI Marc Hadley
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• NEW ISSUE: Replace QName's with anyURI Rich Salz
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Christopher B Ferris
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Rich Salz
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Savas Parastatidis
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Martin Gudgin
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Rich Salz
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Savas Parastatidis
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Christopher B Ferris
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Christopher B Ferris
• Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Rich Salz
• Issues i034: Action defaults (was Re: Issue 019: WSDL Version Neutrality) Hugo Haas
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Martin Gudgin
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Martin Gudgin
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Martin Gudgin
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Christopher B Ferris
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Martin Gudgin
• RE: Composibility problems with refps Rich Salz
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Composibility problems with refps Francisco Curbera
• RE: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Glen Daniels

Monday, 22 November 2004

• NEW ISSUE: WS-Addressing MIME Media Type James Snell

Tuesday, 23 November 2004

• Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!) Srinivas, Davanum M
• RE: Composibility problems with refps Christopher B Ferris
• RE: Composibility problems with refps Christopher B Ferris
• RE: Composibility problems with refps David Orchard
• RE: Composibility problems with refps Vambenepe, William N
• RE: Composibility problems with refps Christopher B Ferris
• RE: ISSUE 8 : "Clarity and Safety" Christopher B Ferris

Monday, 22 November 2004

• RE: i0001: EPRs as identifiers (why XML?) Jim Webber
• RE: Composibility problems with refps David Orchard
• RE: Composibility problems with refps Srinivas, Davanum M
• Re: Composibility problems with refps Rich Salz
• RE: Composibility problems with refps Srinivas, Davanum M
• RE: ISSUE 8 : "Clarity and Safety" David Orchard
• Re: Composibility problems with refps Christopher B Ferris
• Re: ISSUE 8 : "Clarity and Safety" Marc Hadley
• WD CHANGE Anish Karmarkar
• RE: Issue 0001: Use cases for Reference Properties? paul.downey@bt.com
• RE: ISSUE 8 : "Clarity and Safety" Martin Gudgin
• i023: Requried properties in EPR -- email to kick off the discussion Anish Karmarkar
• RE: ISSUE 8 : "Clarity and Safety" Martin Gudgin
• Re: Issue 0001: Use cases for Reference Properties? Marc Hadley
• Re: ISSUE 8 : "Clarity and Safety" Marc Hadley
• Re: Composibility problems with refps Anish Karmarkar
• i034: scope of action defaults Anish Karmarkar
• Re: Composibility problems with refps Tom Rutt
• i001: EPRs as identifiers: Use cases for RefProps/Params David Orchard
• RE: Issue 0001: Use cases for Reference Properties? paul.downey@bt.com
• Re: Composibility problems with refps Anish Karmarkar
• RE: i0001: EPRs as identifiers Francisco Curbera
• Re: ISSUE 8 : "Clarity and Safety" Hugo Haas
• RE: ISSUE 8 : "Clarity and Safety" Francisco Curbera
• RE: Composibility problems with refps Jonathan Marsh
• RE: i0001: EPRs as identifiers (why XML?) Francisco Curbera
• RE: New Issue: use XSD to describe the syntax [i032] David Orchard
• RE: i0001: EPRs as identifiers (implementation model) Martin Gudgin
• RE: ISSUE 8 : "Clarity and Safety" Martin Gudgin
• RE: i0001: EPRs as identifiers (why XML?) michael.eder@nokia.com
• Re: New Issue: use XSD to describe the syntax [i032] Rich Salz
• Re: New Issue: use XSD to describe the syntax [i032] Sanjiva Weerawarana
• RE: New Issue: use XSD to describe the syntax [i032] Rich Salz
• RE: New Issue: use XSD to describe the syntax [i032] paul.downey@bt.com
• WD CHANGE: Mention schema, XML 1.0 decisions Rich Salz
• RE: i0001: EPRs as identifiers (why XML?) David Booth
• RE: i0001: EPRs as identifiers (implementation model) David Booth

Sunday, 21 November 2004

• RE: i0001: EPRs as identifiers (why XML?) Srinivas, Davanum M
• RE: i0001: EPRs as identifiers (why XML?) Savas Parastatidis
• RE: i0001: EPRs as identifiers (why XML?) Rich Salz
• RE: New Issue: use XSD to describe the syntax [i032] Jonathan Marsh
• RE: i0001: EPRs as identifiers (why XML?) Jonathan Marsh

Saturday, 20 November 2004

• Agenda: WS-A telcon 2004-11-22 Mark Nottingham

Friday, 19 November 2004

• RE: i0001: EPRs as identifiers David Booth
• ACTION: Rich to begin work on schema Rich Salz
• RE: i0001: EPRs as identifiers David Orchard
• RE: i0001: EPRs as identifiers (why XML?) David Orchard
• Re: ISSUE 8 : "Clarity and Safety" Hugo Haas
• I034: Re: Issue 019: WSDL Version Neutrality Hugo Haas
• Re: i034: computing default Action value for WSDL 2.0 Hugo Haas
• RE: i0001: EPRs as identifiers David Orchard

Thursday, 18 November 2004

• RE: i0001: EPRs as identifiers (why XML?) David Booth
• Agenda: 2004-12-07 F2F, Redmond, WA US [DRAFT] Mark Nottingham
• Minutes of the 2004-11-15 teleconference Mark Nottingham
• RE: i0001: EPRs as identifiers David Booth
• Re: i0001: EPRs as identifiers (why XML?) Steve Maine
• RE: i034: computing default Action value for WSDL 2.0 Rich Salz
• RE: i034: computing default Action value for WSDL 2.0 Jonathan Marsh

Wednesday, 17 November 2004

• Re: i0001: EPRs as identifiers (why XML?) Mark Baker
• Re: i034: computing default Action value for WSDL 2.0 Rich Salz
• RE: i0001: EPRs as identifiers Savas Parastatidis
• i034: computing default Action value for WSDL 2.0 Jonathan Marsh
• RE: ISSUE 8 : "Clarity and Safety" Jonathan Marsh
• Re: Issue 019: WSDL Version Neutrality Marc Hadley
• RE: i0001: EPRs as identifiers (why XML?) Jonathan Marsh
• RE: Issue 019: WSDL Version Neutrality Jonathan Marsh
• RE: Issue 019: WSDL Version Neutrality Jonathan Marsh
• RE: i0001: EPRs as identifiers Martin Gudgin
• RE: i0001: EPRs as identifiers David Orchard
• RE: ISSUE 8 : "Clarity and Safety" Martin Gudgin
• Issue 0001: Use cases for Reference Properties? David Booth
• Re: i0001: EPRs as identifiers David Booth
• Re: i0001: EPRs as identifiers David Booth
• Re: i0001: EPRs as identifiers Hugo Haas
• Re: Issue 019: WSDL Version Neutrality Hugo Haas
• Re: Issue 019: WSDL Version Neutrality [i034] Mark Nottingham
• Re: NEW ISSUE: Fixed action URI for faults [i035] Mark Nottingham
• Re: Issue 019: WSDL Version Neutrality Rich Salz

Tuesday, 16 November 2004

• Re: Issue 019: WSDL Version Neutrality Hugo Haas
• RE: i0001: EPRs as identifiers David Orchard
• Re: i0001: EPRs as identifiers Mark Nottingham

Monday, 15 November 2004

• Re: i003: WSDL 1.1/2.0 MEPs. Initial proposal (long) Anish Karmarkar
• WS-Reliability specification submitted for OASIS Standard Garfield Green
• RE: Issue 019: WSDL Version Neutrality Jonathan Marsh
• RE: Agenda: WS-A telcon 2004-11-15 Martin Gudgin
• Re: i003: WSDL 1.1/2.0 MEPs. Initial proposal (long) Hugo Haas
• Re: i0001: EPRs as identifiers Anish Karmarkar
• RE: Issue 021: WSDL Extension for Addressing Jonathan Marsh
• Re: Issue numbers Mark Nottingham
• Re: i026: Supporting Multiple Ports in EPRs: Initial proposal Tom Rutt
• i017: Purpose of Action property Anish Karmarkar
• RE: Issue numbers Glen Daniels
• i0016: Distinguishing RefProperty headers Glen Daniels
• Composibility problems with refps Anish Karmarkar
• Re: ISSUE 8 : "Clarity and Safety" Tom Rutt
• Re: i0001: EPRs as identifiers Hugo Haas
• i0018: Protocol-specific markup in RefP's Glen Daniels
• Re: i0001: EPRs as identifiers Tom Rutt
• RE: ISSUE 8 : "Clarity and Safety" Martin Gudgin
• NEW ISSUE: Fixed action URI for faults Marc Hadley
• Re: i0001: EPRs as identifiers Hugo Haas
• i0031: Making wsa:Action Optional David Orchard
• RE: i0001: EPRs as identifiers Martin Gudgin
• RE: Issue 012: Recapitulation and proposal draft 1 Martin Gudgin
• RE: why Service QName is required if client has WSDL + engaged in conversation? Martin Gudgin
• RE: New Issue: use XSD to describe the syntax [i032] paul.downey@bt.com
• Re: Agenda: WS-A telcon 2004-11-15 Mark Little

Sunday, 14 November 2004

• RE: Agenda: WS-A telcon 2004-11-15 David Orchard
• RE: i0001: EPRs as identifiers Mark Baker
• Agenda: WS-A telcon 2004-11-15 Mark Nottingham

Saturday, 13 November 2004

• RE: i0001: EPRs as identifiers Srinivas, Davanum M
• RE: i0001: EPRs as identifiers David Orchard
• RE: i0001: EPRs as identifiers Savas Parastatidis
• RE: i0001: EPRs as identifiers David Orchard
• RE: i0001: EPRs as identifiers David Orchard
• Re: i0001: EPRs as identifiers Francisco Curbera
• Re: New Issue: use XSD to describe the syntax [i032] Rich Salz
• Re: i0001: EPRs as identifiers Mark Baker
• RE: i028: Implications of the presence of ReplyTo Rich Salz
• i0001: EPRs as identifiers David Orchard
• Re: New Issue: use XSD to describe the syntax [i032] Sanjiva Weerawarana
• Re: New Issue: use XSD to describe the syntax [i032] Rich Salz
• Re: New Issue: use XSD to describe the syntax [i032] Sanjiva Weerawarana
• i026: Supporting Multiple Ports in EPRs: Initial proposal Vinoski, Stephen

Friday, 12 November 2004

• RE: New Issue: use XSD to describe the syntax [i032] Martin Gudgin
• RE: i028: Implications of the presence of ReplyTo Jim Webber
• RE: New Issue: use XSD to describe the syntax [i032] David Orchard
• RE: New Issue: use XSD to describe the syntax [i032] paul.downey@bt.com
• Re: New Issue: use XSD to describe the syntax [i032] Rich Salz
• Re: i028: Implications of the presence of ReplyTo Tom Rutt
• RE: i028: Implications of the presence of ReplyTo (and also i003: ) Jacques Durand
• Re: i028: Implications of the presence of ReplyTo Francisco Curbera
• RE: i028: Implications of the presence of ReplyTo Martin Gudgin
• Re: i028: Implications of the presence of ReplyTo Tom Rutt
• Re: i028: Implications of the presence of ReplyTo Tom Rutt
• RE: i028: Implications of the presence of ReplyTo Martin Gudgin
• Re: i028: Implications of the presence of ReplyTo Tom Rutt
• Re: i028: Implications of the presence of ReplyTo Tom Rutt
• Re: i028: Implications of the presence of ReplyTo Tom Rutt
• RE: i028: Implications of the presence of ReplyTo paul.downey@bt.com
• i009 Cardinality of properties and their values paul.downey@bt.com
• RE: i028: Implications of the presence of ReplyTo Francisco Curbera
• Re: i028: Implications of the presence of ReplyTo Marc Hadley
• RE: i029 Disallowing Faults paul.downey@bt.com
• RE: i028: Implications of the presence of ReplyTo Brinild
• Re: i028: Implications of the presence of ReplyTo Brinild
• Re: i028: Implications of the presence of ReplyTo Sanjiva Weerawarana
• Re: i029 Disallowing Faults Sanjiva Weerawarana
• RE: i028: Implications of the presence of ReplyTo Martin Gudgin
• RE: i028: Implications of the presence of ReplyTo Martin Gudgin
• RE: i028: Implications of the presence of ReplyTo Savas Parastatidis
• RE: Why FaultTo? Rich Salz
• Re: i028: Implications of the presence of ReplyTo Marc Hadley
• i028: RE: i028: Implications of the presence of ReplyTo Jacques Durand
• RE: i028: Implications of the presence of ReplyTo Brinild
• Re: i029 Disallowing Faults Mark Peel

Thursday, 11 November 2004

• Re: i029 Disallowing Faults Doug Davis
• i029 Disallowing Faults Harris Reynolds
• Re: Why FaultTo? Mark Baker
• Re: Why FaultTo? Mark Little
• Re: Why FaultTo? Sanjiva Weerawarana
• RE: Why FaultTo? Martin Gudgin
• Re: Why FaultTo? Mark Baker
• i003: WSDL 1.1/2.0 MEPs. Initial proposal (long) Martin Gudgin
• RE: Why FaultTo? Martin Gudgin
• RE: i028: Implications of the presence of ReplyTo Martin Gudgin
• Why FaultTo? Mark Baker
• Re: i028: Implications of the presence of ReplyTo Marc Hadley
• RE: i028: Implications of the presence of ReplyTo Martin Gudgin
• Re: NEW Issue - Reference to WSDL definition in an EPR [i033] Mark Nottingham
• RE: NEW Issue - Reference to WSDL definition in an EPR Bergersen, Rebecca
• Re: NEW Issue - Reference to WSDL definition in an EPR Mark Nottingham
• RE: NEW Issue - Reference to WSDL definition in an EPR Bergersen, Rebecca
• NEW Issue - Reference to WSDL definition in an EPR Bergersen, Rebecca

Wednesday, 10 November 2004

• Re: New Issue: use XSD to describe the syntax [i032] Mark Nottingham
• i028: Implications of the presence of ReplyTo Marc Hadley
• Re: WS-A Issue 28 - Multiple ports Tom Rutt
• Re: schema / component model for addressing structures? Rich Salz
• schema / component model for addressing structures? paul.downey@bt.com
• RE: WS-A Issue 28 - Multiple ports Brinild
• Re: Sanjiva Weerawarana

Tuesday, 9 November 2004

• RE: WS-A Issue 28 - Multiple ports needed in an EPR brinild
• RE: ISSUE 8 : "Clarity and Safety" George Datuashvili

Wednesday, 10 November 2004

• RE: Issue 019: WSDL Version Neutrality Savas Parastatidis

Tuesday, 9 November 2004

• RE: Issue 019: WSDL Version Neutrality Yalcinalp, Umit
• Re: Issue 019: WSDL Version Neutrality Hugo Haas
• RE: WS-A Issue 27 - Reference to WSDL definition in an EPR Bergersen, Rebecca
• Re: ISSUE 8 : "Clarity and Safety" Tom Rutt
• Re: Issue 012: Recapitulation and proposal draft 1 Francisco Curbera
• ISSUE 8 : "Clarity and Safety" Glen Daniels
• RE: Issue 019: WSDL Version Neutrality Yalcinalp, Umit
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• Issue 019: WSDL Version Neutrality Hugo Haas
• Issues and e-mail discussion Mark Nottingham

Monday, 8 November 2004

• Minutes of the 2004-11-08 teleconference Mark Nottingham
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Savas Parastatidis
• AI: why Service QName is required if client has WSDL + engaged in conversation? Anish Karmarkar
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Jonathan Marsh
• Re: IOR Questions Tom Rutt
• Re: WS-A Issue 28 - Multiple ports needed in an EPR Anish Karmarkar
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• Issue 6 (Message Property Optionality) Marc Hadley
• IOR Questions David Orchard
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Savas Parastatidis
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Marc Hadley
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Francisco Curbera
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Rich Salz
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Baker
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• RE: WS-A Issue 28 - Multiple ports needed in an EPR paul.downey@bt.com
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• RE: WS-A Issue 28 - Multiple ports needed in an EPR David Orchard
• RE: WS-A Issue 28 - Multiple ports needed in an EPR paul.downey@bt.com
• foo wsa:action (was WS-Addr issues) paul.downey@bt.com
• Re: WS-A Issue 28 - Multiple ports needed in an EPR Tom Rutt
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Martin Gudgin
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Martin Gudgin
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Martin Gudgin
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: NEW ISSUE: making wsa:Action optional Mark Little
• Re: NEW ISSUE: making wsa:Action optional Mark Little

Sunday, 7 November 2004

• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• Agenda: WS-A telcon 2004-11-08 Mark Nottingham
• Re: NEW ISSUE: making wsa:Action optional Mark Nottingham
• Re: URIs vs EPRs Mark Baker
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Savas Parastatidis
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Rich Salz
• Re: WS-Addr issues Mark Baker
• URIs vs EPRs Mark Baker
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• Re: NEW ISSUE: making wsa:Action optional Francisco Curbera
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Francisco Curbera
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Rich Salz
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• Re: WS-A Issue 28 - Multiple ports needed in an EPR Sanjiva Weerawarana
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Francisco Curbera
• RE: WS-Addr issues Francisco Curbera

Saturday, 6 November 2004

• RE: WS-Addr issues Francisco Curbera

Sunday, 7 November 2004

• Re: Mandator wsa:Action (was Re: WS-Addr issues) Francisco Curbera

Saturday, 6 November 2004

• RE: Mandator wsa:Action (was Re: WS-Addr issues) Francisco Curbera

Sunday, 7 November 2004

• RE: WS-A Issue 28 - Multiple ports needed in an EPR Rich Salz
• RE: WS-A Issue 28 - Multiple ports needed in an EPR David Orchard

Saturday, 6 November 2004

• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• RE: WS-A Issue 28 - Multiple ports needed in an EPR David Orchard
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• RE: WS-Addr issues David Orchard
• RE: WS-Addr issues Doug Davis
• RE: WS-Addr issues Doug Davis
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Martin Gudgin
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Martin Gudgin
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Martin Gudgin
• RE: WS-Addr issues Martin Gudgin
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: Issue 021: WSDL Extension for Addressing Hugo Haas
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Martin Gudgin
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Martin Gudgin
• NEW ISSUE: making wsa:Action optional Mark Little
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Martin Gudgin
• RE: WS-Addr issues Martin Gudgin
• RE: Issue 011 Martin Gudgin
• Re: WS-Addr issues Mark Little
• RE: Issue 011 Martin Gudgin
• Re: WS-Addr issues Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: WS-Addr issues Mark Little
• Re: Action and scope (was: WS-Addr issues) Mark Little
• Re: WS-Addr issues Mark Little
• Re: WS-Addr issues Sanjiva Weerawarana
• Re: WS-Addr issues Jeff Mischkinsky
• Re: WS-Addr issues Jeff Mischkinsky
• Re: Action and scope (was: WS-Addr issues) Jeff Mischkinsky
• Re: WS-A Issue 28 - Multiple ports needed in an EPR Jeff Mischkinsky
• Re: WS-A Issue 28 - Multiple ports needed in an EPR Sanjiva Weerawarana

Friday, 5 November 2004

• Re: WS-Addr issues Tom Rutt

Saturday, 6 November 2004

• Re: WS-Addr issues Sanjiva Weerawarana

Friday, 5 November 2004

• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Rich Salz
• RE: Issue #1: Proposed text and resolution Srinivas, Davanum M
• Re: Issue 021: WSDL Extension for Addressing Hugo Haas
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Vinoski, Stephen
• Re: Issue #1: Proposed text and resolution Mark Baker
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Savas Parastatidis
• RE: WS-Addr issues David Orchard
• RE: WS-Addr issues paul.downey@bt.com
• Re: WS-Addr issues Doug Davis
• Issue #1: Proposed text and resolution David Orchard
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• RE: WS-Addr issues David Orchard
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• Action optionality (was: WS-Addr issues) Mark Nottingham
• RE: WS-Addr issues paul.downey@bt.com
• Action and scope (was: WS-Addr issues) Mark Nottingham
• Re: WS-Addr issues Mark Little
• Re: NEW ISSUE Mark Little
• RE: WS-Addr issues Savas Parastatidis
• Re: WS-Addr issues Mark Baker
• RE: WS-Addr issues paul.downey@bt.com
• Re: NEW ISSUE Mark Nottingham
• [public-ws-addressing] <none> Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: NEW ISSUE Mark Little
• Re: WS-Addr issues Sanjiva Weerawarana
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Marc Hadley
• Re: WS-Addr issues Mark Baker
• RE: WS-Addr issues Jim Webber
• New Issue: use XSD to describe the syntax Rich Salz
• Minutes of the 2004-11-03 teleconference Hugo Haas
• Re: Raising issues Mark Nottingham
• Re: NEW ISSUE Mark Nottingham
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Tom Rutt
• Re: WS-Addr issues Francisco Curbera
• RE: WS-Addr issues Harm Smit
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Harm Smit
• Re: NEW ISSUE Mark Little
• Re: WS-Addr issues Mark Little
• RE: WS-Addr issues paul.downey@bt.com
• RE: NEW ISSUE paul.downey@bt.com
• RE: WS-Addr issues paul.downey@bt.com
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: WS-Addr issues Mark Little
• Re: WS-Addr issues Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: WS-Addr issues Mark Little
• NEW ISSUE Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: WS-Addr issues Mark Little
• Re: WS-Addr issues Tom Rutt
• Re: WS-Addr issues Tom Rutt
• Re: WS-Addr issues Tom Rutt
• Re: WS-Addr issues Tom Rutt
• Re: WS-Addr issues Tom Rutt
• RE: WS-Addr issues Francisco Curbera
• RE: WS-Addr issues Francisco Curbera
• RE: WS-Addr issues Jim Webber
• RE: WS-Addr issues Francisco Curbera
• RE: WS-Addr issues Savas Parastatidis
• Re: WS-Addr issues Anish Karmarkar
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Anish Karmarkar
• Re: WS-Addr issues Anish Karmarkar
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Anish Karmarkar

Thursday, 4 November 2004

• RE: WS-Addr issues Doug Davis
• Re: WS-Addr issues Anish Karmarkar
• Issue 012: Recapitulation and proposal draft 1 Bob Freund
• RE: WS-Addr issues Jim Webber
• Re: Issue 012: EPR Lifetime Anish Karmarkar
• Re: WS-Addr issues Mark Nottingham
• Re: WS-Addr issues Mark Nottingham
• RE: WS-Addr issues David Orchard
• i023 status Mark Nottingham
• Cardinality / Optionality issues Mark Nottingham
• Re: WS-A Issue 28 - Multiple ports needed in an EPR Mark Nottingham
• Raising issues Mark Nottingham
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• Re: WS-Addr issues Francisco Curbera
• RE: Mandator wsa:Action (was Re: WS-Addr issues) Jim Webber
• Re: WS-Addr issues Doug Davis
• RE: WS-Addr issues Jim Webber
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• RE: WS-Addr issues Jim Webber
• Re: Issue 012: EPR Lifetime Mark Nottingham
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Francisco Curbera
• Re: Action item: embedded policy requirements/use case Mark Nottingham
• RE: Issue 011 Glen Daniels
• Re: Issue 011 Anish Karmarkar
• Re: Issue 011 Anish Karmarkar
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Marc Hadley
• RE: WS-A Issue 28 - Multiple ports needed in an EPR Martin Gudgin
• RE: WS-Addr issues Martin Gudgin
• RE: WS-Addr issues Savas Parastatidis
• RE: WS-Addr issues Savas Parastatidis
• RE: WS-Addr issues Martin Gudgin
• RE: WS-Addr issues Harm Smit
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: Mandator wsa:Action (was Re: WS-Addr issues) Rich Salz
• Re: get metadata (was RE: WS-Addr issues Mark Baker
• RE: Mandator wsa:Action (was Re: WS-Addr issues) David Orchard
• Re: WS-Addr issues Mark Little
• Mandator wsa:Action (was Re: WS-Addr issues) Mark Little
• Re: WS-Addr issues Mark Little
• RE: get metadata (was RE: WS-Addr issues David Orchard
• RE: WS-A Issue 27 - Reference to WSDL definition in an EPR David Orchard
• Re: WS-Addr issues Francisco Curbera
• WS-A Issue 28 - Multiple ports needed in an EPR Bergersen, Rebecca
• WS-A Issue 27 - Reference to WSDL definition in an EPR Bergersen, Rebecca
• RE: WS-Addr issues David Orchard
• RE: WS-Addr issues David Orchard
• RE: WS-Addr issues Harm Smit
• Re: WS-Addr issues Marc Hadley
• Re: WS-Addr issues Marc Hadley
• RE: WS-Addr issues Vinoski, Stephen
• RE: WS-Addr issues Harm Smit
• Re: get metadata (was RE: WS-Addr issues Mark Baker
• Re: WS-Addr issues Francisco Curbera
• RE: WS-Addr issues David Orchard
• Re: WS-Addr issues Mark Little
• Re: WS-Addr issues Mark Little
• Re: WS-Addr issues Marc Hadley
• RE: get metadata (was RE: WS-Addr issues Ashok Malhotra
• RE: WS-Addr issues Savas Parastatidis
• get metadata (was RE: WS-Addr issues Mark Baker
• Re: WS-Addr issues Marc Hadley
• Re: WS-Addr issues Francisco Curbera
• Re: WS-Addr issues Mark Little
• RE: WS-Addr issues Savas Parastatidis
• Re: WS-Addr issues Mark Little
• Re: Issue 012: EPR Lifetime Mark Little
• Re: WS-Addr issues Mark Little
• RE: WS-Addr issues paul.downey@bt.com
• RE: Issue 012: EPR Lifetime David Orchard
• RE: EPRs and URIs prezo at F2F David Orchard
• RE: EPRs and URIs prezo at F2F Srinivas, Davanum M

Wednesday, 3 November 2004

• EPRs and URIs prezo at F2F David Orchard
• RE: WS-Addr issues David Orchard
• RE: WS-Addr issues Ashok Malhotra
• RE: WS-Addr issues David Orchard
• RE: WS-Addr issues Ashok Malhotra
• RE: WS-Addr issues Vinoski, Stephen
• RE: WS-Addr issues David Orchard
• RE: WS-Addr issues Jim Webber
• RE: WS-Addr issues Vinoski, Stephen
• Re: Issue 011 Marc Hadley
• RE: WS-Addr issues Jim Webber
• RE: Issue 011 Martin Gudgin
• Re: Issue 011 Marc Hadley
• RE: Action item: embedded policy requirements/use case Ashok Malhotra
• Minutes of the NYC F2F Hugo Haas
• Re: Action item: embedded policy requirements/use case Sanjiva Weerawarana
• Re: WS-Addr issues Sanjiva Weerawarana
• Fw: Issue 011 Greg Truty
• RE: Issue 011 Martin Gudgin
• Action item: embedded policy requirements/use case Francisco Curbera
• Re: WS-Addr issues Marc Hadley
• Re: Issue 011 Marc Hadley
• Re: WS-Addr issues Rich Salz
• RE: WS-Addr issues Vinoski, Stephen
• RE: Issue 012: EPR Lifetime michael.eder@nokia.com
• Re: WS-Addr issues Doug Davis
• Issue 021: WSDL Extension for Addressing Hugo Haas
• Re: WS-Addr issues Rich Salz
• RE: Issue 012: EPR Lifetime Martin Gudgin
• Re: Issue 012: EPR Lifetime Francisco Curbera
• WS-Addr issues Doug Davis
• RE: Issue 011 Martin Gudgin
• Re: Issue 011 Marc Hadley
• Issue 012: EPR Lifetime Bob Freund
• Re: Issue 011 Anish Karmarkar
• Re: Issue 011 Anish Karmarkar
• RE: Issue 011 Martin Gudgin

Tuesday, 2 November 2004

• RE: Issue 011 Glen Daniels
• RE: Issue 011 David Orchard
• RE: Issue 011 Martin Gudgin
• RE: Issue 011 David Orchard
• WS-Addressing presentation from the NYC F2F Mark Nottingham
• Agenda: WS-A WG telcon 2004-11-03 Mark Nottingham
• RE: Issue 011 Martin Gudgin
• Issue 011 Harris Reynolds
• Implication of the publication of the first public Working Draft with regards to the Patent Policy Hugo Haas

Last message date: Tuesday, 30 November 2004 22:43:19 UTC