aboutsummaryrefslogtreecommitdiff
path: root/xep-0247.xml
diff options
context:
space:
mode:
authorEmmanuel Gil Peyrot <linkmauve@linkmauve.fr>2017-02-14 22:08:49 +0000
committerSam Whited <sam@samwhited.com>2017-02-16 19:37:21 -0600
commit7a64b7b1ed8869d54cf4c9fe4fd4ada06bc328ee (patch)
treeb31de9ecf749ef6913834de99be394158f107e27 /xep-0247.xml
parentfe9d3969fd125e71b47b04b4b8c9c6ced609997c (diff)
Remove spaces at the end of CDATA blocks in all XEPs.
sed -i 's/^\s\+]]>/]]>/g' xep-*.xml
Diffstat (limited to 'xep-0247.xml')
-rw-r--r--xep-0247.xml38
1 files changed, 19 insertions, 19 deletions
diff --git a/xep-0247.xml b/xep-0247.xml
index d512cd6..f54cc0f 100644
--- a/xep-0247.xml
+++ b/xep-0247.xml
@@ -85,7 +85,7 @@
| ack |
|------------------------------>|
| |
- ]]></code>
+]]></code>
<p>First the initiator sends a Jingle session-initiate.</p>
<example caption="Initiator sends session-initiate"><![CDATA[
<iq from='romeo@montague.lit/orchard'
@@ -104,14 +104,14 @@
</content>
</jingle>
</iq>
- ]]></example>
+]]></example>
<p>The responder immediately acknowledges receipt of the Jingle session-initiate.</p>
<example caption="Responder acknowledges session-initiate"><![CDATA[
<iq from='juliet@capulet.lit/balcony'
id='ty1bf726'
to='romeo@montague.lit/orchard'
type='result'/>
- ]]></example>
+]]></example>
<p>If the responding user accepts the session then her client sends a session-accept.</p>
<example caption="Responder sends session-accept"><![CDATA[
<iq from='juliet@capulet.lit/balcony'
@@ -130,14 +130,14 @@
</content>
</jingle>
</iq>
- ]]></example>
+]]></example>
<p>The initiator acknowledges receipt.</p>
<example caption="Initiator acknowledges session-accept"><![CDATA[
<iq from='romeo@montague.lit/orchard'
id='hwd987h'
to='juliet@capulet.lit/balcony'
type='result'/>
- ]]></example>
+]]></example>
<p>The clients can then begin to exchange XMPP data over the in-band bytestream. Because the transport is an in-band bytestream, the XMPP data is prepared as described in &xep0047; (i.e., Base64-encoded).</p>
<p>First the initiator sends an initial stream header to the responder.</p>
<example caption="Initial stream header (unencoded)"><![CDATA[
@@ -147,7 +147,7 @@
from='romeo@montague.lit/orchard'
to='juliet@capulet.lit/balcony'
version='1.0'>
- ]]></example>
+]]></example>
<p>Note: In accordance with &xmppim;, the initial stream header SHOULD include the 'to' and 'from' attributes, which SHOULD specify the full JIDs of the clients. If the initiator supports stream features and the other stream-related aspects of XMPP 1.0 as specified in <cite>RFC 3920</cite>, then it SHOULD include the version='1.0' flag as shown in the previous example.</p>
<example caption="Initial stream header (encoded in IBB) and IQ-result"><![CDATA[
<iq from='romeo@montague.net/orchard'
@@ -166,7 +166,7 @@
id='ur73n153'
to='romeo@montague.net/orchard'
type='result'/>
- ]]></example>
+]]></example>
<p>The responder then sends a response stream header back to the initiator (because this stream header is sent in the other direction, the IBB 'seq' attribute has a value of zero, not 1).</p>
<example caption="Response stream header"><![CDATA[
<stream:stream
@@ -176,7 +176,7 @@
id='hs91gh1836d8s717'
to='romeo@montague.lit/orchard'
version='1.0'>
- ]]></example>
+]]></example>
<example caption="Response stream header (encoded in IBB) and IQ-result"><![CDATA[
<iq from='juliet@capulet.com/balcony'
id='pd61g397'
@@ -194,13 +194,13 @@
id='pd61g397'
to='juliet@capulet.com/balcony'
type='result'/>
- ]]></example>
+]]></example>
<p>Once the streams are established, either entity then can send XMPP message, presence, and IQ stanzas, with or without 'to' and 'from' addresses.</p>
<example caption="A message (unencoded)"><![CDATA[
<message from='romeo@montague.lit/orchard' to='juliet@capulet.lit/balcony'>
<body>M&apos;lady, I would be pleased to make your acquaintance.</body>
</message>
- ]]></example>
+]]></example>
<example caption="A message (encoded in IBB) and IQ-result"><![CDATA[
<iq from='romeo@montague.net/orchard'
id='iq7dh294'
@@ -218,13 +218,13 @@
id='iq7dh294'
to='romeo@montague.net/orchard'
type='result'/>
- ]]></example>
+]]></example>
<p>The responder could then send a reply.</p>
<example caption="A reply (unencoded)"><![CDATA[
<message from='juliet@capulet.lit/balcony' to='romeo@montague.lit/orchard'>
<body>Art thou not Romeo, and a Montague?</body>
</message>
- ]]></example>
+]]></example>
<example caption="A reply (encoded in IBB) and IQ-result"><![CDATA[
<iq from='juliet@capulet.com/balcony'
id='hr91hd63'
@@ -241,11 +241,11 @@
id='kr91n475'
to='juliet@capulet.com/balcony'
type='result'/>
- ]]></example>
+]]></example>
<p>To end the XML stream, either party sends a closing &lt;/stream:stream&gt; element.</p>
<example caption="Stream close (unencoded)"><![CDATA[
</stream:stream>
- ]]></example>
+]]></example>
<example caption="Stream close (encoded in IBB) and IQ-result"><![CDATA[
<iq from='juliet@capulet.com/balcony'
id='kr91n475'
@@ -260,7 +260,7 @@
id='kr91n475'
to='juliet@capulet.com/balcony'
type='result'/>
- ]]></example>
+]]></example>
<p>However, even after the application-level XML stream is terminated, the negotiated Jingle transport (here in-band bytestream) continues and could be re-used. To completely terminate the Jingle session, the terminating party would then also send a Jingle session-terminate message.</p>
<example caption="Responder terminates the stream and session"><![CDATA[
<iq from='juliet@capulet.lit/balcony'
@@ -272,14 +272,14 @@
initiator='romeo@montague.lit/orchard'
sid='851ba2'/>
</iq>
- ]]></example>
+]]></example>
<p>The other party then acknowledges the Jingle session-terminate.</p>
<example caption="Initiator acks session-terminate"><![CDATA[
<iq from='romeo@montague.lit/orchard'
id='psy617r4'
to='juliet@capulet.lit/balcony'
type='result'/>
- ]]></example>
+]]></example>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
@@ -315,7 +315,7 @@
<transport>streaming</transport>
<doc>XEP-0247</doc>
</application>
- ]]></code>
+]]></code>
</section2>
</section1>
@@ -338,7 +338,7 @@
</xs:simpleType>
</xs:schema>
- ]]></code>
+]]></code>
</section1>
</xep>