i068 proposal: separate one-way binding document

A new one-way bidning document might look like:

 


Abstract


Web Services Addressing provides transport-neutral mechanisms to address
Web services and messages.  Web Services Addressing 1.0 - SOAP 1.1
One-way Binding (this document) defines modification to the SOAP 1.1
HTTP Binding to support sending a one-way message.


Status of this Document


This document is an editors' copy that has no official standing.

________________________________


Table of Contents


1. Introduction
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#tocRange#tocRange> 
    1.1 Notational Conventions
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#notation#notation> 
    1.2 Namespaces
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#namespaces#namespaces> 
6. References
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#references#references> 


Appendices


A. Acknowledgements
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#acknowledgments#acknowledgments
>  (Non-Normative)



________________________________


1. Introduction


Web Services Addressing 1.0 - Core[WS-Addressing-Core
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#WSADDR-CORE#WSADDR-CORE> ]
defines a set of abstract properties and an XML Infoset [XML Information
Set
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLInfoSet#XMLInfoSet> ]
representation thereof to reference Web service endpoints and to
facilitate end-to-end addressing of endpoints in messages. Web Services
Addressing 1.0 - SOAP 1.1 One-way Binding (this document) defines
modification to the SOAP 1.1 HTTP Binding to support sending a one-way
message..


1.1 Notational Conventions


The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [IETF RFC 2119
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#RFC2119#RFC2119> ].

When describing abstract data models, this specification uses the
notational convention used by the XML Infoset [XML Information Set
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLInfoSet#XMLInfoSet> ].
Specifically, abstract property names always appear in square brackets
(e.g., [some property]).

When describing concrete XML schemas [XML Schema Structures
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLSchemaP1#XMLSchemaP1> , XML
Schema Datatypes
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLSchemaP2#XMLSchemaP2> ],
this specification uses the notational convention of WS-Security
[WS-Security
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#WS-Security#WS-Security> ].
Specifically, each member of an element's [children] or [attributes]
property is described using an XPath-like notation (e.g.,
/x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates the
presence of an element wildcard (<xs:any/>). The use of @{any} indicates
the presence of an attribute wildcard (<xs:anyAttribute/>).


1.2 Namespaces


This specification uses a number of namespace prefixes throughout; they
are listed in Table 1-1
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#nsprefs#nsprefs> . Note that
the choice of any namespace prefix is arbitrary and not semantically
significant (see [XML Namespaces
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLNS#XMLNS> ]).

Table 1-1. Prefixes and Namespaces used in this specification

Prefix

Namespace

S

http://www.w3.org/2003/05/soap-envelope

S11

http://schemas.xmlsoap.org/soap/envelope

wsa

http://www.w3.org/@@@@/@@/addressing 

wsaw

http://www.w3.org/@@@@/@@/addressing/wsdl 

xs

http://www.w3.org/2001/XMLSchema

wsdl

Either http://www.w3.org/2005/08/wsdl or
http://schemas.xmlsoap.org/wsdl/ depending on context

wsdl20

http://www.w3.org/2005/08/wsdl

wsdl11

http://schemas.xmlsoap.org/wsdl/

soap11

http://schemas.xmlsoap.org/wsdl/soap/

 

The working group intends to update the value of the Web Services
Addressing 1.0 - WSDL Binding namespace URI each time a new version of
this document is published until such time that the document reaches
Candidate Recommendation status. Once it has reached Candidate
Recommendation status, the working group intends to maintain the value
of the Web Services Addressing 1.0 - WSDL Binding namespace URI that was
assigned in the Candidate Recommendation unless significant changes are
made that impact the implementation of the specification.

WS-Addressing is defined in terms of the XML Information Set [XML
Information Set
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLInfoSet#XMLInfoSet> ].
WS-Addressing may be used with SOAP [SOAP 1.2 Part 1: Messaging
Framework
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#SOAP12-PART1#SOAP12-PART1> ] as
described in Web Services Addressing 1.0 - SOAP
Binding[WS-Addressing-SOAP
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#WSADDR-SOAP#WSADDR-SOAP> ]. The
examples in this specification use an XML 1.0 [XML 1.0
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XML10#XML10> ] representation
but this is not a requirement.

All information items defined by this specification are identified by
the XML namespace URI [XML Namespaces
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLNS#XMLNS> ]
"http://www.w3.org/@@@@/@@/addressing/wsdl". A normative XML Schema [XML
Schema Structures
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLSchemaP1#XMLSchemaP1> , XML
Schema Datatypes
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-wsdlProposedRevision1.62.html#XMLSchemaP2#XMLSchemaP2> ]
document can be obtained by dereferencing the XML namespace URI.


2. SOAP 1.1 One-way HTTP Binding


The SOAP 1.1/HTTP binding can be used for one-way messages.  For such
messages, the receiver of a message MUST respond with a 202 status code
and an empty HTTP body, aka no SOAP envelope.  Any SOAP Envelope that is
a reply MUST be sent using a separate HTTP connection.

 


3. References


[WS-Addressing-Core] 

Web Services Addressing 1.0 - Core
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-core.html> , M. Gudgin, M. Hadley, Editors.

[WS-Addressing-SOAP] 

Web Services Addressing 1.0 - SOAP Binding
<http://lists.w3.org/Archives/Public/public-ws-addressing/2005Dec/att-00
80/ws-addr-soap.html> , M. Gudgin, M. Hadley, Editors.

 

Add soap 1.1, etc..