Editorial: Wording clarifications in Core Section 4
Fwd: Rationalize URI vs. IRI (Core, clarification)
Fwd: Last call issue with ReplyTo and security
Fwd: Last call issue with section 3.0: why does this spec mandate a dispatching model?
WS-Addressing - Closing Last Call Issue 12
entire route in ws-addressing
Missing xml namespace prefix declaration (SOAP, editorial)
Allowance of Migration Contracts for WS-addressing conformant endpoints
Re: Allow dispatch on more than [destination] and [action] (Core, clarification)
Intermediary Processing
LC31 wsa:IsReferenceParameter clashes
Resolution of LC27
RE: Rationalize URI vs. IRI (Core, clarification) lc23
Re: Typographical nits (SOAP, editorial) (correction)
Re: Clarify Anonymous URI and for the case of HTTP responses (Core substantive)
lc21: Anonymous and [destination] over-constrained
Resolution for WS-Addressing LC issue 18 - proposal accepted
Resolution of issue LC19
LC10 - EIIs have QNames
Fw: LC9 - Reinforce absolute IRIs
[Arun.Gupta@Sun.COM: [Fwd: Last call comment (soap): Normative text for fault properties binding]]
[Arun.Gupta@Sun.COM: [Fwd: Last Call Comment (soap) - Binding fault [detail] in SOAP 1.1 envelope]]
Last call issue with ReplyTo and security
Last call issue with section 3.0: why does this spec mandate a dispatching model?
introduction of MAP and MEP terms
Fwd: [Editorial][SOAP] MessageId vs MessageID
Fwd: [Editorial][SOAP] order of items in section 2.3
Fwd: [Editorial][SOAP] IRI for SOAP 1.2 Module and SOAP 1.1 Extension
Fwd: [Editorial][SOAP] Section 5
Fwd: [Editorial][xsd] typo in xsd
Fwd: [Editorial][SOAP] Bad URL's
[Editorial][Core] Section 3.2
[Editorial][Core] Bad URL's
[Editorial][Core] S11 in Table 1-1
[Editorial][Core] Section 4
[Editorial][Core] Order of items in section 3 and 3.1
[Editorial][Core] Table 3-1
[Editorial][Core] Example 3-1
Question regarding cardinality of [destination]
Feedback on xs:nonNegativeInteger (SOAP, clarification)
More Security Considerations (SOAP, substantive)
Clarify Invalid Message Addressing Property and Message Property Required Faults (SOAP, substantive)
Clarify conformance requirements (SOAP, substantive)
Duplicate headers at the ultimate receiver (SOAP, substantive)
Binding rules don't appear to allow optional headers (SOAP, clarification)
Note effect of wsa:IsReferenceParameter on validation (SOAP, clarification)
wsa:IsReferenceParameter clashes (SOAP, substantive)
Formal definition of wsa:isReferenceParameter (SOAP, clarification)
wsa:isReferenceParameter inconsistent casing (SOAP, clarification)
Mixed notation and indirect terminology for MAPs (SOAP, clarification)
Clarify distinction between XML Infoset representation and SOAP headers (SOAP, clarification)
Clarify which fault if SOAP Action and wsa:Action don't match (SOAP, substantive)
Merge Core and SOAP Binding specs (SOAP, substantive)
Typographical nits (SOAP, editorial)
Header extensibility processing model (Core, substantive)
Anonymous and [destination] over-constrained (Core, substantive)
Clarify Anonymous URI and for the case of HTTP responses (Core substantive)
Clarify [destination] comparison (Core, clarification)
[children] inconsistency (Core, editorial)
Anonymous not limited to replies (Core, editorial)
Allow dispatch on more than [destination] and [action] (Core, clarification)
Disallow multiple "reply" relationships (Core, clarification)
Clearer wording for Table 3-1 (Core, editorial)
Clearer wording for Section 2.1 (Core, editorial)
Ref param data encoding (Core, clarification)
Ref param opacity (Core, clarification)
EIIs have QNames? (Core, editorial)
Reinforce absolute IRIs (Core, clarification)
Rationalize URI vs. IRI (Core, clarification)
- RE: Rationalize URI vs. IRI (Core, clarification)
- Re: Rationalize URI vs. IRI (Core, clarification)
- RE: Rationalize URI vs. IRI (Core, clarification)