mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-21 15:18:51 -05:00
changed nbsp to #160
This commit is contained in:
Peter Saint-Andre
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> <a class='standardsButton' href='rss.xml'>RSS</a></p>
|
||||
<p><a class='standardsButton' href='atom.xml'>ATOM</a>  <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> <a class="standardsButton" href="rss.xml">RSS</a></p>
|
||||
<p><a class="standardsButton" href="atom.xml">ATOM</a>  <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/">"inbox"</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> </td>
|
||||
<td> </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> </td>
|
||||
<td> </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>description</td>
|
||||
|
||||
@ -368,14 +368,14 @@
|
||||
<p>Two identities: "client/pc/Psi" and "client/pc/Ψ"</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<'</p>
|
||||
<p>S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<'</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/Ψ 0.11<client/pc/en/Psi 0.11<http://jabber.org/protocol/caps<http://jabber.org/protocol/disco#info<
|
||||
S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<http://jabber.org/protocol/caps<http://jabber.org/protocol/disco#info<
|
||||
<br />http://jabber.org/protocol/disco#items<http://jabber.org/protocol/muc<'.
|
||||
</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/Ψ 0.11<client/pc/en/Psi 0.11<http://jabber.org/protocol/caps<http://jabber.org/protocol/disco#info<
|
||||
<p>S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<http://jabber.org/protocol/caps<http://jabber.org/protocol/disco#info<
|
||||
<br />http://jabber.org/protocol/disco#items<http://jabber.org/protocol/muc<urn:xmpp:dataforms:softwareinfo<'</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Sort the fields by var and append the value(s): "ip_version<ipv4<ipv6", "os<Mac", "os_version<10.5.1", "software<Psi", "software_version<0.11".</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<http://jabber.org/protocol/caps<http://jabber.org/protocol/disco#info<
|
||||
<p>S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<http://jabber.org/protocol/caps<http://jabber.org/protocol/disco#info<
|
||||
<br />http://jabber.org/protocol/disco#items<http://jabber.org/protocol/muc<urn:xmpp:dataforms:softwareinfo<
|
||||
<br />ip_version<ipv4<ipv6<os<Mac<os_version<10.5.1<software<Psi<software_version<0.11<'</p>
|
||||
</li>
|
||||
|
||||
56
xep-0301.xml
56
xep-0301.xml
@ -243,9 +243,9 @@
|
||||
<tr>
|
||||
<th>event</th>
|
||||
<th>Description</th>
|
||||
<th>Action Elements</th>
|
||||
<th>Sender Support</th>
|
||||
<th>Recipient Support</th>
|
||||
<th>Action Elements</th>
|
||||
<th>Sender Support</th>
|
||||
<th>Recipient Support</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>new</td>
|
||||
@ -333,26 +333,26 @@
|
||||
<th>Action</th>
|
||||
<th>Element</th>
|
||||
<th>Description</th>
|
||||
<th>Sender Support</th>
|
||||
<th>Recipient Support</th>
|
||||
<th>Sender Support</th>
|
||||
<th>Recipient Support</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Insert Text</td>
|
||||
<td><t p='#'>text</t></td>
|
||||
<td>Insert Text</td>
|
||||
<td><t p='#'>text</t></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 Text</td>
|
||||
<td><e p='#' n='#'/></td>
|
||||
<td>Erase Text</td>
|
||||
<td><e p='#' n='#'/></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 Interval</td>
|
||||
<td><w n='#'/></td>
|
||||
<td>Wait Interval</td>
|
||||
<td><w n='#'/></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 <message/> stanzas. Chat states such as <composing/> or <active/> are sent separately from <rtt/> elements.</p>
|
||||
<p>Chat states are handled as specified by <strong>XEP-0085</strong>. The continuous transmission of real-time text corresponds to a <composing/> chat state. Therefore, the timing of the <composing/> chat state coincides with the beginning of continuous <rtt/> transmission. </p>
|
||||
<p>Chat states are handled as specified by <strong>XEP-0085</strong>. The continuous transmission of real-time text corresponds to a <composing/> chat state. Therefore, the timing of the <composing/> chat state coincides with the beginning of continuous <rtt/> 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 Message</th>
|
||||
<th>Cursor Position*</th>
|
||||
<th>Real -Time Message</th>
|
||||
<th>Cursor Position*</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><t>Helo</t></td>
|
||||
<td>Output "Helo"</td>
|
||||
<td>Output "Helo"</td>
|
||||
<td>Helo</td>
|
||||
<td>4</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><e/></td>
|
||||
<td>Erase 1 character from end of line.</td>
|
||||
<td>Erase 1 character from end of line.</td>
|
||||
<td>Hel</td>
|
||||
<td>3</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><t>lo...planet</t></td>
|
||||
<td>Output "lo...planet" at end of line.</td>
|
||||
<td>Output "lo...planet" at end of line.</td>
|
||||
<td>Hello...planet</td>
|
||||
<td>14</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><e n='6'/></td>
|
||||
<td>Erase 6 characters from end of line</td>
|
||||
<td><e n='6'/></td>
|
||||
<td>Erase 6 characters from end of line</td>
|
||||
<td>Hello...</td>
|
||||
<td>8</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><t> World</t></td>
|
||||
<td>Output " World" at end of line.</td>
|
||||
<td>Hello... World</td>
|
||||
<td><t> World</t></td>
|
||||
<td>Output " World" at end of line.</td>
|
||||
<td>Hello... World</td>
|
||||
<td>14</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><e n='3' p='8'/></td>
|
||||
<td>Erase 3 characters before position 8</td>
|
||||
<td>Hello World</td>
|
||||
<td><e n='3' p='8'/></td>
|
||||
<td>Erase 3 characters before position 8</td>
|
||||
<td>Hello World</td>
|
||||
<td>5</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><t p='5'> there,</t></td>
|
||||
<td>Output " there," at position 5</td>
|
||||
<td>Hello there, World</td>
|
||||
<td><t p='5'> there,</t></td>
|
||||
<td>Output " there," at position 5</td>
|
||||
<td>Hello there, World</td>
|
||||
<td>12</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
22
xep-0326.xml
22
xep-0326.xml
@ -3751,37 +3751,37 @@
|
||||
<tr>
|
||||
<td>id</td>
|
||||
<td>required</td>
|
||||
<td> </td>
|
||||
<td> </td>
|
||||
<td>The ID of the node in the data source.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>displayName</td>
|
||||
<td>optional</td>
|
||||
<td> </td>
|
||||
<td> </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> </td>
|
||||
<td> </td>
|
||||
<td>A string representing the type of the node.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>localId</td>
|
||||
<td>optional</td>
|
||||
<td> </td>
|
||||
<td> </td>
|
||||
<td>If provided, an ID for the node, but unique locally between siblings.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>logId</td>
|
||||
<td>optional</td>
|
||||
<td> </td>
|
||||
<td> </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> </td>
|
||||
<td> </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> </td>
|
||||
<td> </td>
|
||||
<td>Current overall state of the node.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>hasChildren</td>
|
||||
<td>required</td>
|
||||
<td> </td>
|
||||
<td> </td>
|
||||
<td>If the node has children or not.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -3830,19 +3830,19 @@
|
||||
<tr>
|
||||
<td>parentId</td>
|
||||
<td>optional</td>
|
||||
<td> </td>
|
||||
<td> </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> </td>
|
||||
<td> </td>
|
||||
<td>The Cache Type of the parent node.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>lastChanged</td>
|
||||
<td>optional</td>
|
||||
<td> </td>
|
||||
<td> </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…
Reference in New Issue
Block a user