moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 18:22:24 -05:00
Code Issues Releases Wiki Activity

RFC 4227 obsoletes RFC 3288

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@812 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-05-07 17:03:54 +00:00
parent 292fcd2f7f
commit 8b7a844d58
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0072.xml
View File

@ -353,7 +353,7 @@
</tr>
<tr>
<td>Alternate Transports</td>
<td>Send SOAP XML plus binary data over alternate transports such as <cite>WS-Attachments</cite> <note>WS-Attachments &lt;<link url="http://www.watersprings.org/pub/id/draft-nielsen-dime-soap-01.txt">http://www.watersprings.org/pub/id/draft-nielsen-dime-soap-01.txt</link>&gt; (work in progress).</note> or SOAP-over-BEEP as defined in &rfc3288;.</td>
<td>Send SOAP XML plus binary data over alternate transports such as <cite>WS-Attachments</cite> <note>WS-Attachments &lt;<link url="http://www.watersprings.org/pub/id/draft-nielsen-dime-soap-01.txt">http://www.watersprings.org/pub/id/draft-nielsen-dime-soap-01.txt</link>&gt; (work in progress).</note> or SOAP-over-BEEP as defined in &rfc4227;.</td>
<td>SHOULD NOT</td>
<td>These methods are just other transport protocols and would needlessly complicate implementations of SOAP over XMPP.</td>
</tr>
@ -624,7 +624,7 @@
</section1>
<section1 topic="SOAP XMPP Binding" anchor='binding'>
<p>Section 4 of &w3soap1; defines a SOAP Protocol Binding Framework; two instantiations of that framework are the SOAP HTTP Binding (specified in Section 7 of &w3soap2;) and the &w3soapemail;. (Additionally, a binding to BEEP is described in <cite>RFC 3288</cite>.) As an alternative to the HTTP and Email bindings, this section formally defines the SOAP XMPP Binding in accordance with the SOAP Protocol Binding Framework.</p>
<p>Section 4 of &w3soap1; defines a SOAP Protocol Binding Framework; two instantiations of that framework are the SOAP HTTP Binding (specified in Section 7 of &w3soap2;) and the &w3soapemail;. (Additionally, a binding to BEEP is described in <cite>RFC 4227</cite>.) As an alternative to the HTTP and Email bindings, this section formally defines the SOAP XMPP Binding in accordance with the SOAP Protocol Binding Framework.</p>
<p>Note: The SOAP XMPP Binding is optional, and SOAP nodes are not required to implement it. A SOAP node that correctly and completely implements the SOAP XMPP Binding as described herein may be said to "conform to the SOAP 1.2 XMPP Binding".</p>
<section2 topic="Binding Name" anchor='binding-name'>
<p>The SOAP XMPP Binding is identified by the following URI:</p>

1
xep.ent
View File

@ -396,6 +396,7 @@
<!ENTITY rfc4032 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4032'>RFC 4032</link></span> <note>RFC 4032: Update to the Session Initiation Protocol (SIP) Preconditions Framework &lt;<link url='http://tools.ietf.org/html/rfc4032'>http://tools.ietf.org/html/rfc4032</link>&gt;.</note>" >
<!ENTITY rfc4119 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4119'>RFC 4119</link></span> <note>RFC 4119: A Presence-based GEOPRIV Location Object Format &lt;<link url='http://tools.ietf.org/html/rfc4119'>http://tools.ietf.org/html/rfc4119</link>&gt;.</note>" >
<!ENTITY rfc4122 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4122'>RFC 4122</link></span> <note>RFC 4122: A Universally Unique IDentifier (UUID) URN Namespace &lt;<link url='http://tools.ietf.org/html/rfc4122'>http://tools.ietf.org/html/rfc4122</link>&gt;.</note>" >
<!ENTITY rfc4227 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4227'>RFC 4227</link></span> <note>RFC 4227: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) &lt;<link url='http://tools.ietf.org/html/rfc4227'>http://tools.ietf.org/html/rfc4227</link>&gt;.</note>" >
<!ENTITY rfc4251 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4251'>RFC 4251</link></span> <note>RFC 4251: The Secure Shell (SSH) Protocol Architecture &lt;<link url='http://tools.ietf.org/html/rfc4251'>http://tools.ietf.org/html/rfc4251</link>&gt;.</note>" >
<!ENTITY rfc4252 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4252'>RFC 4252</link></span> <note>RFC 4252: The Secure Shell (SHS) Authentication Protocol &lt;<link url='http://tools.ietf.org/html/rfc4252'>http://tools.ietf.org/html/rfc4252</link>&gt;.</note>" >
<!ENTITY rfc4253 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4253'>RFC 4253</link></span> <note>RFC 4253: The Secure Shell (SSH) Transport Layer Protocol &lt;<link url='http://tools.ietf.org/html/rfc4253'>http://tools.ietf.org/html/rfc4253</link>&gt;.</note>" >