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