Anish Karmarkar
- WS-Addressing 1.0 Core -- XML infoset representation of EPR > Information model (Thursday, 12 May)
- WS-Addressing 1.0 Core - what is a 'request' and what is a 'reply'? (Thursday, 12 May)
- WS-Addressing 1.0 Core -- immutability of MAPs (Thursday, 12 May)
- WS-Addressing 1.0 Core -- How does one extend the abstract properties of an endpoint reference (Thursday, 12 May)
- WS-Addressing 1.0 Core - section 2.1 -- unclear wording regarding conflicts between metadata (editorial) (Thursday, 12 May)
- WS-Addressing 1.0 Core - section 2.1 -- what does 'each of the EPRs' refer to (Thursday, 12 May)
- WS-Addressing 1.0 Core -- Notational conventions not explained (Thursday, 12 May)
- WS-Addressing 1.0 Core, inconsistent use of 'Endpoint Reference' (ed nit) (Thursday, 12 May)
- WS-Addressing 1.0 Core -- requirement of XML 1.0 (Thursday, 12 May)
- WS-Addressing 1.0 Core - ed nit - section 1.2 (references) (Thursday, 12 May)
- WS-Addressing Core, section 1.1 editorial nit (Thursday, 12 May)
- Editorial nit regd Example 1-1 in Core (Thursday, 12 May)
- Editorial nit - WS-Addressing Core (Thursday, 12 May)
Arun Gupta
Bergersen, Rebecca
Davanum Srinivas
David Hull
- LC Comment: (editorial) Security implications of [message id] in re-transmissions (Wednesday, 11 May)
- [message id] should be optional (Tuesday, 10 May)
- LC Comment: (editorial) Processors unconstrained in the face of non-compliant messages. (Thursday, 5 May)
- LC Comment: Message compliance (Thursday, 5 May)
- LC Comment: When is a fault/reply expected? (Thursday, 5 May)
- LC Comment: "... the processor MUST fault" in section 3.2 is vacuous. (Thursday, 5 May)
- LC Comment:(editorial) Use of mustUnderstand=1 in example (Thursday, 5 May)
- LC Comment: (editorial) Definitions of MAPs in core section 3 should have their own subsection (Thursday, 5 May)
- LC Comment: Rewriting by intermediaries (Thursday, 5 May)
- LC Comment: Multiple reply relationships (Thursday, 5 May)
- LC Comment: MAPs in EPR reference params (Thursday, 5 May)
- LC Comment: Supported faults (Thursday, 5 May)
- LC Comment: Uniqueness of [message id] (Thursday, 5 May)
- What does core section 3 actually require? (Tuesday, 3 May)
David Orchard
Glen Daniels
Hugo Haas
Jacek Kopecky
- Re: WS-Addressing Last Call issue 64 closed (Tuesday, 10 May)
- nonNegativeInteger or duration for RetryAfter (Tuesday, 3 May)
- content of fault detail (Tuesday, 3 May)
- mandatory fault reason (Tuesday, 3 May)
- mandatory action (Tuesday, 3 May)
- mandatory ReplyTo, handling replies in WS-Addressing (Tuesday, 3 May)
- no mustUnderstand extensibility (Tuesday, 3 May)
- dereferencing namespace URI - but no link (editorial) (Tuesday, 3 May)
- presentation of typing information in element descriptions (Tuesday, 3 May)
- use of IRIs in WS-Addressing (Tuesday, 3 May)
- ws-addressing LC review editorial comments (Tuesday, 3 May)
Jeff Mischkinsky
Jonathan Marsh
Katy Warr
Marc Hadley
Mark Nottingham
Martin Gudgin
michael.eder@nokia.com
Nilo Mitra (TX/EUS)
Paul Downey
paul.downey@bt.com
Prasad Yendluri
Rimas Rekasius
Robert Freund
Tim Ewald
Vikas Deolaliker
Winkler, Steve
Yalcinalp, Umit
Last message date: Tuesday, 24 May 2005 17:19:58 UTC