changed nbsp to #160

xep-0352-v0.2
Peter Saint-Andre 10 years ago
parent c1d2f0ee51
commit 496018222b

@ -5,7 +5,7 @@
<!--#include virtual="/includes/head.txt" -->
<h2>XMPP Extensions</h2>
<p><a class='standardsButton' href='atom.xml'>ATOM</a>&nbsp;&nbsp;<a class='standardsButton' href='rss.xml'>RSS</a></p>
<p><a class='standardsButton' href='atom.xml'>ATOM</a>&#160;&#160;<a class='standardsButton' href='rss.xml'>RSS</a></p>
<p>This page lists all <a href='/extensions/'>XMPP Extension Protocols</a> published by the XMPP Standards Foundation, including specifications that have been retracted, rejected, deprecated, and obsoleted.</p>

@ -5,7 +5,7 @@
<!--#include virtual="/includes/head.txt" -->
<h2>XMPP Extensions</h2>
<p><a class="standardsButton" href="atom.xml">ATOM</a>&nbsp;&nbsp;<a class="standardsButton" href="rss.xml">RSS</a></p>
<p><a class="standardsButton" href="atom.xml">ATOM</a>&#160;&#160;<a class="standardsButton" href="rss.xml">RSS</a></p>
<p>XMPP is the Extensible Messaging and Presence Protocol, a set of open <a href='/tech/'>technologies</a> for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.</p>
<p>The <a href='/xsf/'>XMPP Standards Foundation</a> (XSF) develops extensions to <a href="/">XMPP</a> through a standards process centered around XMPP Extension Protocols (XEPs). The <a href="xep-0001.html">process</a> is managed by the <a href="editor.shtml">XMPP Extensions Editor</a> and involves intensive discussion on the <a href="http://mail.jabber.org/mailman/listinfo/standards/">Standards mailing list</a>, formal review and <a href="/council/votes.shtml">voting</a> by the <a href="/council/">XMPP Council</a>, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal <a href="ipr-policy.shtml">IPR Policy</a> for wide implementation. Submissions are <a href='submit.shtml'>welcome</a> (see also the <a href="/extensions/inbox/">&quot;inbox&quot;</a>). All XEPs and related files are under <a href="/xsf/sourcecontrol.shtml">source control</a>, <a href="/extensions/attic/">old versions</a> are available, and IETF-style <a href="/extensions/refs/">XML reference files</a> are provided. A compressed archive of all current XEPs can be downloaded <a href="/extensions/xepbundle.tar.bz2">here</a>. You can view and submit XEP-related bugs and feature requests at the <a href='http://tracker.xmpp.org/browse/SPEC'>issue tracker</a>.</p>

@ -178,7 +178,7 @@
<td>bearing</td>
<td>xs:decimal</td>
<td>GPS bearing (direction in which the entity is heading to reach its next waypoint), measured in decimal degrees relative to true north <note>It is the responsibility of the receiver to translate bearing into decimal degrees relative to magnetic north, if desired.</note></td>
<td>&nbsp;</td>
<td>&#160;</td>
</tr>
<tr>
<td>building</td>
@ -202,7 +202,7 @@
<td>datum</td>
<td>xs:string</td>
<td>GPS datum <note>If datum is not included, receiver MUST assume WGS84; receivers MUST implement WGS84; senders MAY use another datum, but it is not recommended.</note></td>
<td>&nbsp;</td>
<td>&#160;</td>
</tr>
<tr>
<td>description</td>

@ -368,14 +368,14 @@
<p>Two identities: "client/pc/Psi" and "client/pc/&#936;"</p>
</li>
<li>
<p>S = 'client/pc/el/&#936;&nbsp;0.11&lt;client/pc/en/Psi&nbsp;0.11&lt;'</p>
<p>S = 'client/pc/el/&#936;&#160;0.11&lt;client/pc/en/Psi&#160;0.11&lt;'</p>
</li>
<li>
<p>Sort the features: "http://jabber.org/protocol/caps", http://jabber.org/protocol/disco#info", "http://jabber.org/protocol/disco#items", "http://jabber.org/protocol/muc".</p>
</li>
<li>
<p>
S = 'client/pc/el/&#936;&nbsp;0.11&lt;client/pc/en/Psi&nbsp;0.11&lt;http://jabber.org/protocol/caps&lt;http://jabber.org/protocol/disco#info&lt;
S = 'client/pc/el/&#936;&#160;0.11&lt;client/pc/en/Psi&#160;0.11&lt;http://jabber.org/protocol/caps&lt;http://jabber.org/protocol/disco#info&lt;
<br />http://jabber.org/protocol/disco#items&lt;http://jabber.org/protocol/muc&lt;'.
</p>
</li>
@ -383,14 +383,14 @@
<p>Sort the extended service discovery forms by FORM_TYPE (there is only one: "urn:xmpp:dataforms:softwareinfo").</p>
</li>
<li>
<p>S = 'client/pc/el/&#936;&nbsp;0.11&lt;client/pc/en/Psi&nbsp;0.11&lt;http://jabber.org/protocol/caps&lt;http://jabber.org/protocol/disco#info&lt;
<p>S = 'client/pc/el/&#936;&#160;0.11&lt;client/pc/en/Psi&#160;0.11&lt;http://jabber.org/protocol/caps&lt;http://jabber.org/protocol/disco#info&lt;
<br />http://jabber.org/protocol/disco#items&lt;http://jabber.org/protocol/muc&lt;urn:xmpp:dataforms:softwareinfo&lt;'</p>
</li>
<li>
<p>Sort the fields by var and append the value(s): "ip_version&lt;ipv4&lt;ipv6", "os&lt;Mac", "os_version&lt;10.5.1", "software&lt;Psi", "software_version&lt;0.11".</p>
</li>
<li>
<p>S = 'client/pc/el/&#936;&nbsp;0.11&lt;client/pc/en/Psi&nbsp;0.11&lt;http://jabber.org/protocol/caps&lt;http://jabber.org/protocol/disco#info&lt;
<p>S = 'client/pc/el/&#936;&#160;0.11&lt;client/pc/en/Psi&#160;0.11&lt;http://jabber.org/protocol/caps&lt;http://jabber.org/protocol/disco#info&lt;
<br />http://jabber.org/protocol/disco#items&lt;http://jabber.org/protocol/muc&lt;urn:xmpp:dataforms:softwareinfo&lt;
<br />ip_version&lt;ipv4&lt;ipv6&lt;os&lt;Mac&lt;os_version&lt;10.5.1&lt;software&lt;Psi&lt;software_version&lt;0.11&lt;'</p>
</li>

@ -243,9 +243,9 @@
<tr>
<th>event</th>
<th>Description</th>
<th>Action&nbsp;Elements</th>
<th>Sender&nbsp;Support</th>
<th>Recipient&nbsp;Support</th>
<th>Action&#160;Elements</th>
<th>Sender&#160;Support</th>
<th>Recipient&#160;Support</th>
</tr>
<tr>
<td>new</td>
@ -333,26 +333,26 @@
<th>Action</th>
<th>Element</th>
<th>Description</th>
<th>Sender&nbsp;Support</th>
<th>Recipient&nbsp;Support</th>
<th>Sender&#160;Support</th>
<th>Recipient&#160;Support</th>
</tr>
<tr>
<td>Insert&nbsp;Text</td>
<td>&lt;t&nbsp;p='#'&gt;text&lt;/t&gt;</td>
<td>Insert&#160;Text</td>
<td>&lt;t&#160;p='#'&gt;text&lt;/t&gt;</td>
<td>Insert specified <strong>text</strong> at position 'p' in message.</td>
<td><strong>REQUIRED</strong></td>
<td><strong>REQUIRED</strong></td>
</tr>
<tr>
<td>Erase&nbsp;Text</td>
<td>&lt;e&nbsp;p='#'&nbsp;n='#'/&gt;</td>
<td>Erase&#160;Text</td>
<td>&lt;e&#160;p='#'&#160;n='#'/&gt;</td>
<td>Remove 'n' characters before position 'p' in message<em>.</em></td>
<td>RECOMMENDED</td>
<td><strong>REQUIRED</strong></td>
</tr>
<tr>
<td>Wait&nbsp;Interval</td>
<td>&lt;w&nbsp;n='#'/&gt;</td>
<td>Wait&#160;Interval</td>
<td>&lt;w&#160;n='#'/&gt;</td>
<td>Wait 'n' milliseconds.</td>
<td>RECOMMENDED</td>
<td>RECOMMENDED</td>
@ -633,7 +633,7 @@
</section3>
<section3 topic="Usage with Chat States" anchor="usage_with_chat_states">
<p>Real-time text can be used in conjunction with <strong>Chat State Notifications</strong>. It is best to handle <strong>XEP-0301</strong> and <strong>XEP-0085</strong> transmissions in separate &lt;message/&gt; stanzas. Chat states such as &lt;composing/&gt; or &lt;active/&gt; are sent separately from &lt;rtt/&gt; elements.</p>
<p>Chat states are handled as specified by <strong>XEP-0085</strong>. The continuous transmission of real-time text corresponds to a &lt;composing/&gt; chat state. Therefore, the timing of the &lt;composing/&gt; chat state coincides with the beginning of continuous &lt;rtt/&gt; transmission.&nbsp;</p>
<p>Chat states are handled as specified by <strong>XEP-0085</strong>. The continuous transmission of real-time text corresponds to a &lt;composing/&gt; chat state. Therefore, the timing of the &lt;composing/&gt; chat state coincides with the beginning of continuous &lt;rtt/&gt; transmission.</p>
</section3>
<section3 topic="Usage with Last Message Correction" anchor="usage_with_last_message_correction">
<p>It is possible to use <strong>Last Message Correction</strong> with real-time text. If <strong>XEP-0308</strong> is implemented in concert with this specification, the following rules apply:</p>
@ -841,49 +841,49 @@
<tr>
<th>Element</th>
<th>Action</th>
<th>Real -Time&nbsp;Message</th>
<th>Cursor&nbsp;Position*</th>
<th>Real -Time&#160;Message</th>
<th>Cursor&#160;Position*</th>
</tr>
<tr>
<td>&lt;t&gt;Helo&lt;/t&gt;</td>
<td>Output&nbsp;"Helo"</td>
<td>Output&#160;"Helo"</td>
<td>Helo</td>
<td>4</td>
</tr>
<tr>
<td>&lt;e/&gt;</td>
<td>Erase&nbsp;1&nbsp;character&nbsp;from&nbsp;end&nbsp;of&nbsp;line.</td>
<td>Erase&#160;1&#160;character&#160;from&#160;end&#160;of&#160;line.</td>
<td>Hel</td>
<td>3</td>
</tr>
<tr>
<td>&lt;t&gt;lo...planet&lt;/t&gt;</td>
<td>Output&nbsp;"lo...planet"&nbsp;at&nbsp;end&nbsp;of&nbsp;line.</td>
<td>Output&#160;"lo...planet"&#160;at&#160;end&#160;of&#160;line.</td>
<td>Hello...planet</td>
<td>14</td>
</tr>
<tr>
<td>&lt;e&nbsp;n='6'/&gt;</td>
<td>Erase&nbsp;6&nbsp;characters&nbsp;from&nbsp;end&nbsp;of&nbsp;line</td>
<td>&lt;e&#160;n='6'/&gt;</td>
<td>Erase&#160;6&#160;characters&#160;from&#160;end&#160;of&#160;line</td>
<td>Hello...</td>
<td>8</td>
</tr>
<tr>
<td>&lt;t&gt;&nbsp;World&lt;/t&gt;</td>
<td>Output&nbsp;"&nbsp;World"&nbsp;at&nbsp;end&nbsp;of&nbsp;line.</td>
<td>Hello...&nbsp;World</td>
<td>&lt;t&gt;&#160;World&lt;/t&gt;</td>
<td>Output&#160;"&#160;World"&#160;at&#160;end&#160;of&#160;line.</td>
<td>Hello...&#160;World</td>
<td>14</td>
</tr>
<tr>
<td>&lt;e&nbsp;n='3'&nbsp;p='8'/&gt;</td>
<td>Erase&nbsp;3&nbsp;characters&nbsp;before&nbsp;position&nbsp;8</td>
<td>Hello&nbsp;World</td>
<td>&lt;e&#160;n='3'&#160;p='8'/&gt;</td>
<td>Erase&#160;3&#160;characters&#160;before&#160;position&#160;8</td>
<td>Hello&#160;World</td>
<td>5</td>
</tr>
<tr>
<td>&lt;t&nbsp;p='5'&gt;&nbsp;there,&lt;/t&gt;</td>
<td>Output&nbsp;"&nbsp;there,"&nbsp;at&nbsp;position&nbsp;5</td>
<td>Hello&nbsp;there,&nbsp;World</td>
<td>&lt;t&#160;p='5'&gt;&#160;there,&lt;/t&gt;</td>
<td>Output&#160;"&#160;there,"&#160;at&#160;position&#160;5</td>
<td>Hello&#160;there,&#160;World</td>
<td>12</td>
</tr>
</table>

@ -3751,37 +3751,37 @@
<tr>
<td>id</td>
<td>required</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>The ID of the node in the data source.</td>
</tr>
<tr>
<td>displayName</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>If provided, a string presentable to users. If localization is supported and a correct language attribute was provided, this string will be localized.</td>
</tr>
<tr>
<td>nodeType</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>A string representing the type of the node.</td>
</tr>
<tr>
<td>localId</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>If provided, an ID for the node, but unique locally between siblings.</td>
</tr>
<tr>
<td>logId</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>If provided, an ID for the node, as it would appear or be used in system logs.</td>
</tr>
<tr>
<td>cacheType</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>Used to uniquely identify the node in sources where the ID of the node is not sufficient. Example: In a spatial ordering different nodes may represent
countries, regions, cities, areas, streets, buildings and apartments in the same source. However, the ID of each node would depend on what type of node it
represents. It might be valid to have a region, city and/or area with the same ID. So, to these circumstances, a Cache Type of Country, Region, City, Area,
@ -3790,13 +3790,13 @@
<tr>
<td>state</td>
<td>required</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>Current overall state of the node.</td>
</tr>
<tr>
<td>hasChildren</td>
<td>required</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>If the node has children or not.</td>
</tr>
<tr>
@ -3830,19 +3830,19 @@
<tr>
<td>parentId</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>The node ID of the parent node. If not available, the node is considered a root node.</td>
</tr>
<tr>
<td>parentCacheType</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>The Cache Type of the parent node.</td>
</tr>
<tr>
<td>lastChanged</td>
<td>optional</td>
<td>&nbsp;</td>
<td>&#160;</td>
<td>When the node was last changed. Can be used by clients to synchronize content between the concentrator and itself.</td>
</tr>
</table>

Loading…
Cancel
Save