From 496018222bc61d68983793dc48c9edd7e678b0aa Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 19 Nov 2013 14:47:32 -0700 Subject: [PATCH] changed nbsp to #160 --- all.shtml | 2 +- index.shtml | 2 +- xep-0080.xml | 4 ++-- xep-0115.xml | 8 ++++---- xep-0301.xml | 56 ++++++++++++++++++++++++++-------------------------- xep-0326.xml | 22 ++++++++++----------- 6 files changed, 47 insertions(+), 47 deletions(-) diff --git a/all.shtml b/all.shtml index c0ab5916..97c61d23 100755 --- a/all.shtml +++ b/all.shtml @@ -5,7 +5,7 @@

XMPP Extensions

-

ATOM  RSS

+

ATOM  RSS

This page lists all XMPP Extension Protocols published by the XMPP Standards Foundation, including specifications that have been retracted, rejected, deprecated, and obsoleted.

diff --git a/index.shtml b/index.shtml index 5d6b913a..20cfdfda 100755 --- a/index.shtml +++ b/index.shtml @@ -5,7 +5,7 @@

XMPP Extensions

-

ATOM  RSS

+

ATOM  RSS

XMPP is the Extensible Messaging and Presence Protocol, a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.

The XMPP Standards Foundation (XSF) develops extensions to XMPP through a standards process centered around XMPP Extension Protocols (XEPs). The process is managed by the XMPP Extensions Editor and involves intensive discussion on the Standards mailing list, formal review and voting by the XMPP Council, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal IPR Policy for wide implementation. Submissions are welcome (see also the "inbox"). All XEPs and related files are under source control, old versions are available, and IETF-style XML reference files are provided. A compressed archive of all current XEPs can be downloaded here. You can view and submit XEP-related bugs and feature requests at the issue tracker.

diff --git a/xep-0080.xml b/xep-0080.xml index cdf41315..2a6b0ebb 100644 --- a/xep-0080.xml +++ b/xep-0080.xml @@ -178,7 +178,7 @@ bearing xs:decimal GPS bearing (direction in which the entity is heading to reach its next waypoint), measured in decimal degrees relative to true north It is the responsibility of the receiver to translate bearing into decimal degrees relative to magnetic north, if desired. -   +   building @@ -202,7 +202,7 @@ datum xs:string GPS datum If datum is not included, receiver MUST assume WGS84; receivers MUST implement WGS84; senders MAY use another datum, but it is not recommended. -   +   description diff --git a/xep-0115.xml b/xep-0115.xml index 68992862..bb6c280e 100644 --- a/xep-0115.xml +++ b/xep-0115.xml @@ -368,14 +368,14 @@

Two identities: "client/pc/Psi" and "client/pc/Ψ"

  • -

    S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<'

    +

    S = 'client/pc/el/Ψ 0.11<client/pc/en/Psi 0.11<'

  • 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".

  • - 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<
    http://jabber.org/protocol/disco#items<http://jabber.org/protocol/muc<'.

    • @@ -383,14 +383,14 @@

    Sort the extended service discovery forms by FORM_TYPE (there is only one: "urn:xmpp:dataforms:softwareinfo").

  • -

    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<
    http://jabber.org/protocol/disco#items<http://jabber.org/protocol/muc<urn:xmpp:dataforms:softwareinfo<'

  • 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".

  • -

    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<
    http://jabber.org/protocol/disco#items<http://jabber.org/protocol/muc<urn:xmpp:dataforms:softwareinfo<
    ip_version<ipv4<ipv6<os<Mac<os_version<10.5.1<software<Psi<software_version<0.11<'

    • diff --git a/xep-0301.xml b/xep-0301.xml index 3554e9a6..9c9e6abc 100644 --- a/xep-0301.xml +++ b/xep-0301.xml @@ -243,9 +243,9 @@ event Description - Action Elements - Sender Support - Recipient Support + Action Elements + Sender Support + Recipient Support new @@ -333,26 +333,26 @@ Action Element Description - Sender Support - Recipient Support + Sender Support + Recipient Support - Insert Text - <t p='#'>text</t> + Insert Text + <t p='#'>text</t> Insert specified text at position 'p' in message. REQUIRED REQUIRED - Erase Text - <e p='#' n='#'/> + Erase Text + <e p='#' n='#'/> Remove 'n' characters before position 'p' in message. RECOMMENDED REQUIRED - Wait Interval - <w n='#'/> + Wait Interval + <w n='#'/> Wait 'n' milliseconds. RECOMMENDED RECOMMENDED @@ -633,7 +633,7 @@

    Real-time text can be used in conjunction with Chat State Notifications. It is best to handle XEP-0301 and XEP-0085 transmissions in separate <message/> stanzas. Chat states such as <composing/> or <active/> are sent separately from <rtt/> elements.

    -

    Chat states are handled as specified by XEP-0085. 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. 

    +

    Chat states are handled as specified by XEP-0085. 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.

    It is possible to use Last Message Correction with real-time text. If XEP-0308 is implemented in concert with this specification, the following rules apply:

    @@ -841,49 +841,49 @@ Element Action - Real -Time Message - Cursor Position* + Real -Time Message + Cursor Position* <t>Helo</t> - Output "Helo" + Output "Helo" Helo 4 <e/> - Erase 1 character from end of line. + Erase 1 character from end of line. Hel 3 <t>lo...planet</t> - Output "lo...planet" at end of line. + Output "lo...planet" at end of line. Hello...planet 14 - <e n='6'/> - Erase 6 characters from end of line + <e n='6'/> + Erase 6 characters from end of line Hello... 8 - <t> World</t> - Output " World" at end of line. - Hello... World + <t> World</t> + Output " World" at end of line. + Hello... World 14 - <e n='3' p='8'/> - Erase 3 characters before position 8 - Hello World + <e n='3' p='8'/> + Erase 3 characters before position 8 + Hello World 5 - <t p='5'> there,</t> - Output " there," at position 5 - Hello there, World + <t p='5'> there,</t> + Output " there," at position 5 + Hello there, World 12 diff --git a/xep-0326.xml b/xep-0326.xml index a63eedd1..6387fd4c 100644 --- a/xep-0326.xml +++ b/xep-0326.xml @@ -3751,37 +3751,37 @@ id required -   +   The ID of the node in the data source. displayName optional -   +   If provided, a string presentable to users. If localization is supported and a correct language attribute was provided, this string will be localized. nodeType optional -   +   A string representing the type of the node. localId optional -   +   If provided, an ID for the node, but unique locally between siblings. logId optional -   +   If provided, an ID for the node, as it would appear or be used in system logs. cacheType optional -   +   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 @@ state required -   +   Current overall state of the node. hasChildren required -   +   If the node has children or not. @@ -3830,19 +3830,19 @@ parentId optional -   +   The node ID of the parent node. If not available, the node is considered a root node. parentCacheType optional -   +   The Cache Type of the parent node. lastChanged optional -   +   When the node was last changed. Can be used by clients to synchronize content between the concentrator and itself.