From 86715b004ad0f2067ec5c2cd7a85cc89912c2bd6 Mon Sep 17 00:00:00 2001
From: stpeter <stpeter@stpeter.im>
Date: Wed, 29 Jun 2011 09:28:55 -0600
Subject: [PATCH] 0.14

---
 xep-0234.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/xep-0234.xml b/xep-0234.xml
index 4045a936..08c38cae 100644
--- a/xep-0234.xml
+++ b/xep-0234.xml
@@ -25,14 +25,14 @@
   <shortname>NOT_YET_ASSIGNED</shortname>
   &stpeter;
   <revision>
-    <version>0.14rc2</version>
-    <date>2011-06-24</date>
+    <version>0.14</version>
+    <date>2011-06-29</date>
     <initials>psa</initials>
     <remark>
       <ul>
         <li>Defined file description format separate from XEP-0096</li>
-        <li>Modified the checksum format to reuse the &lt;hashes/&gt; element from incoming proposal</li>
-        <li>Described the process of aborting a file transfer.</li>
+        <li>Modified the checksum format to reuse the &lt;hashes/&gt; element from XEP-0300</li>
+        <li>Described the process of aborting a file transfer</li>
         <li>Clarified the order of events (Jingle, then transport) when the session is terminated</li>
         <li>Added section on determining spport, including service discovery feature for multi-file support</li>
         <li>Removed the 'urn:xmpp:jingle:apps:file-transfer:info:2' namespace by putting all elements into the 'urn:xmpp:jingle:apps:file-transfer:3' namespace</li>
@@ -160,7 +160,7 @@
   <ul>
     <li>Use the session negotiation semantics from <cite>XEP-0166</cite>.</li>
     <li>Use &xep0260; and &xep0261;.</li>
-    <li>Define a file description format that enables hash agility (unlike <cite>XEP-0096</cite>).</li>
+    <li>Define a file description format that, unlike <cite>XEP-0096</cite> enables hash agility (via &xep0300;).</li>
     <li>Define a clear upgrade path from SI File Transfer to Jingle File Transfer.</li>
   </ul>
   <p>Jingle file transfer is only as reliable as the transports on which it depends. In particular, SOCKS5 Bytestreams ("S5B") does not always result in NAT or firewall traversal. To work around that problem, this specification requires all implementations to support as a fallback mechanism In-Band Bytestreams ("IBB"), which usually results in a successful (if slow) file transfer.</p>