mirror of
https://github.com/moparisthebest/xeps
synced 2025-01-08 12:27:59 -05:00
Remove spaces at the end of CDATA blocks in all XEPs.
sed -i 's/^\s\+]]>/]]>/g' xep-*.xml
This commit is contained in:
parent
fe9d3969fd
commit
7a64b7b1ed
@ -128,9 +128,7 @@
|
||||
|
||||
<section2 topic='Record Format' anchor='dnsformat'>
|
||||
<p>The following format for DNS TXT resource records is specified in <cite>RFC 1464</cite>:</p>
|
||||
<code><![CDATA[
|
||||
<owner> <class> <ttl> <TXT> <"attribute name=attribute value">
|
||||
]]></code>
|
||||
<code><![CDATA[<owner> <class> <ttl> <TXT> <"attribute name=attribute value">]]></code>
|
||||
<p>This document specifies that the following additional rules apply for DNS TXT resource records used to specify alternative connection methods:</p>
|
||||
<ol>
|
||||
<li>It is RECOMMENDED for the owner to be "_xmppconnect".</li>
|
||||
|
@ -156,8 +156,8 @@
|
||||
[ ... ]
|
||||
</user>
|
||||
</host>
|
||||
</server-data> ]]>
|
||||
</example>
|
||||
</server-data>
|
||||
]]></example>
|
||||
</section2>
|
||||
|
||||
<section2 topic='Rosters' anchor='rosters'>
|
||||
|
@ -140,7 +140,8 @@
|
||||
<feature var='http://jabber.org/protocol/pubsub#multi-collections'/>
|
||||
...
|
||||
</query>
|
||||
</iq> ]]></example>
|
||||
</iq>
|
||||
]]></example>
|
||||
</section2>
|
||||
|
||||
<section2 topic='Discover Nodes' anchor='disco-nodes'>
|
||||
|
12
xep-0278.xml
12
xep-0278.xml
@ -117,7 +117,8 @@ All signalling, request, response and publishing is done via XMPP, not requiring
|
||||
<tracker policy='public' address='capulet.lit' protocol='udp'/>
|
||||
<stun policy='public' address='200.111.111.111' port='3857' protocol='udp'/>
|
||||
</services>
|
||||
</iq> ]]></example>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p><em>In this example 'montague.lit' XMPP Domain a Relay Service and a Tracker Service. The Relay Service can be contacted in order to retrieve Relay Channels. The Tracker Service can be contacted in order to retrieve its known services.</em></p>
|
||||
</section2>
|
||||
<section2 topic="Jingle Client Searches for Services on a Retrieved Tracker Service" anchor="clientcheckownserver">
|
||||
@ -136,7 +137,8 @@ All signalling, request, response and publishing is done via XMPP, not requiring
|
||||
to='romeo@montague.lit/orchard'
|
||||
type='result'>
|
||||
<services xmlns='http://jabber.org/protocol/jinglenodes'/>
|
||||
</iq> ]]></example>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p><em>In this example 'capulet.lit' returned an empty service list, meaning that it does NOT known ANY Relay or Tracker Services.</em></p>
|
||||
</section2>
|
||||
<section2 topic="Jingle Client Searches for Services on online Roster Entries" anchor="clientcheckownserver">
|
||||
@ -157,7 +159,8 @@ All signalling, request, response and publishing is done via XMPP, not requiring
|
||||
<services xmlns='http://jabber.org/protocol/jinglenodes'>
|
||||
<relay policy='roster' address='juliet@capulet.lit/balcony' protocol='udp'/>
|
||||
</services>
|
||||
</iq>]]></example>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p>In this example 'juliet@capulet.lit/balcony' returned a Relay Service entry that is restricted to its roster. This Service is usable as the requester has 'juliet@capulet.lit/balcony' on its roster. Although, services with policy 'roster' MUST NOT be listed in Tracker Responses expects in Tracker Responses that comes from the Service Entity itself, in this case 'juliet@capulet.lit/balcony'.</p>
|
||||
<p><em>In the presented example 'romeo@montague.lit/orchard' knows that 'juliet@capulet.lit/balcony' provides Relay Service, but if another entity requests 'romeo@montague.lit/orchard' its known services, it MUST NOT include 'juliet@capulet.lit/balcony' as it is a roster restricted entry.</em></p>
|
||||
</section2>
|
||||
@ -187,7 +190,8 @@ All signalling, request, response and publishing is done via XMPP, not requiring
|
||||
protocol='udp'
|
||||
maxkbps='120'
|
||||
expire='60'/>
|
||||
</iq> ]]></example>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p><em>After receiving the &CHANNEL; the requester MUST send his stream to 'host' and 'localport' pair and send a &CANDIDATE; containing the 'host' and 'remoteport' values.</em></p>
|
||||
</section2>
|
||||
</section1>
|
||||
|
Loading…
Reference in New Issue
Block a user