From 05fb4901a26ccf6bfb9ee8553a21c53574951c81 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 9 Aug 2012 08:58:36 -0600 Subject: [PATCH] 0.7 --- xep-0301.xml | 138 ++++++++++++++++++++++++--------------------------- 1 file changed, 66 insertions(+), 72 deletions(-) diff --git a/xep-0301.xml b/xep-0301.xml index 28af6d92..b959b4eb 100644 --- a/xep-0301.xml +++ b/xep-0301.xml @@ -28,10 +28,16 @@ markybox@gmail.com http://www.realjabber.org + + 0.7 + 2012-08-08 + MDR +

Simplifications and grammatical corrections. Some sections (1, 6.2, 6.4) shortened with simpler language.

 + 0.6 2012-07-28 - MDR + MDR

Changes and improvements in preparation for advance to Draft. Unified <e/> element (Erase Text) to handle all possible text deletions. Clarify the Unicode terminology used in this specification, and move @@ -92,20 +98,18 @@

This document defines a specification for real-time text transmitted in-band over an XMPP network.

-

Real-time text is text transmitted instantly while it is being typed or created. The recipient can immediately read the sender's text as it is written, without waiting. Text can be used conversationally, similar to a telephone conversation, where one listens while the other is speaking. It eliminates waiting times found in messaging, and is favored by deaf and hard of hearing individuals who prefer text conversation.

-

Real-time text has been around for decades in various implementations:

+

Real-time text is text transmitted instantly while it is being typed or created. The recipient can immediately read the sender's text as it is written, without waiting. Text can be used conversationally, similar to a telephone conversation, where one listens while the other is speaking. It eliminates waiting times found in messaging. Real-time text has been around for decades in various implementations:

  • The 'talk' command on UNIX systems since the 1970's.
    • -
  • ICQ had a peer-to-peer split screen mode from 1996-1999.
    • -
  • TTY and text telephones for the deaf and hard of hearing.
    • +
  • TTY and text telephones.
  • For SIP, real-time text is sent using IETF RFC 4103 RFC 4103: RTP Payload for Text Conversation. <http://tools.ietf.org/html/rfc4103>. with ITU-T T.140 ITU-T T.140: Protocol for multimedia application text conversation. <http://www.itu.int/rec/T-REC-T.140>. presentation coding.
    • -
  • In 2008, AOL AIM 6.8 gained the AOL Real-Time IM AOL AIM Real Time Text: <http://help.aol.com/help/microsites/microsite.do?cmd=displayKC&externalId=223568>. feature.
    • +
  • The Real-Time IM AOL AIM Real Time Text: <http://help.aol.com/help/microsites/microsite.do?cmd=displayKC&externalId=223568>. feature found in AOL Instant Messenger.
  • A component within Total Conversation, used by Reach112 Reach112: European emergency service with real-time text. <http://www.reach112.eu>. in Europe, an accessible emergency service with real-time text.
-

Real-time text is suitable for smooth and rapid mainstream communication in text, as an all-inclusive technology to complement instant messaging. It can also allow immediate conversation in situations where speech cannot be used (e.g. quiet environments, privacy, deaf and hard of hearing). Real-time text is also beneficial in emergency situations, due to its immediacy. For a visual animation of real-time text, see Real-Time Text Taskforce +

Real-time text allows continuous and rapid communication in text, to complement general-purpose instant messaging. It can also allow immediate conversation in situations where speech cannot be used (e.g. quiet environments, privacy, deaf and hard of hearing). Real-time text is also beneficial in emergency situations, due to its immediacy. For a visual animation of real-time text, see Real-Time Text Taskforce Real-Time Text Taskforce, a foundation for real-time text standardization <http://www.realtimetext.org>..

@@ -136,22 +140,23 @@
  1. Allow XMPP to follow the ITU-T Rec. F.703 ITU-T Rec. F.703: Multimedia conversational services. <http://www.itu.int/rec/T-REC-F.703>. Total Conversation standard for simultaneous voice, video, and real-time text.
    2. -
  2. Be a candidate technology for use with Next Generation 9-1-1 / 1-1-2 emergency services.
    3. +
  3. Be a candidate technology for use with next generation emergency services (e.g. 9-1-1 and 1-1-2).
  4. Be suitable for transcription services and (when coupled with voice at user's choice) for TTY/text telephone alternatives, relay services, and captioned telephone systems.
  5. Allow immediate conversational text through mobile phone text messaging and mainstream instant messaging.
 +

action element – An XML element that represents a single real-time message edit, such as text insertion or deletion.

+

character - A single Unicode code point. See Unicode Character Counting.

real-time – A conversational latency of less than 1 second, as defined by ITU-T Rec. F.700 ITU-T Rec. F.700: Framework Recommendation for multimedia services <http://www.itu.int/rec/T-REC-F.700>., section 2.1.2.1.

real-time text – Text transmitted instantly while it is being typed or created.

real-time message – Recipient's real-time view of the sender's message still being typed or created.

-

action element – An XML element that represents a single real-time message edit, such as text insertion or deletion.

RTT – Acronym for real-time text.

 -

Real-time text is transmitted via an <rtt/> child element of a <message/> stanza. The <rtt/> element is transmitted at regular intervals by the sender client while a message is being composed, to allow the recipient to see the latest message text, without waiting for the full message sent in a <body/> element.

+

Real-time text is transmitted via an <rtt/> child element of a <message/> stanza. The <rtt/> element is transmitted at regular intervals by the sender client while a message is being composed, to allow the recipient to see the latest message text from the sender, without waiting for the full message sent in a <body/> element.

This is a basic example of a real-time message "Hello, my Juliet!” transmitted in real-time while it is being typed, before a final message delivery in a <body/> element (to remain Backwards Compatible):

Example 1: Introductory Example

@@ -212,40 +217,40 @@ init - Initiate a real-time text session. + Signals the start of real-time text. OPTIONAL RECOMMENDED cancel - End a real-time text session. + Signals the end of real-time text. OPTIONAL RECOMMENDED

event='new'
- Senders MUST use this value when transmitting the first <rtt/> element containing Action Elements (i.e. the first character(s) of a new message). Recipient clients MUST initialize a new real-time message for display, and then process action elements within the <rtt/> element. If a real-time message already exists in the same chat session, its content MUST be replaced (i.e. cleared prior to processing action elements). Senders MAY send subsequent <rtt/> elements that do not contain an event attribute.

+ Senders MUST use this value when transmitting the first <rtt/> element containing Action Elements (i.e. when sending the first character(s) of a new message). Recipient clients MUST initialize a new real-time message for display, and then process action elements within the <rtt/> element. If a real-time message already exists, from the same sender in the same chat session, its content MUST be replaced (i.e. cleared prior to processing action elements). Senders MAY send subsequent <rtt/> elements that do not contain an event attribute.

event='reset'
- For recipients, both 'new' and 'reset' are logically identical, and differ only for implementation purposes (e.g. highlighting newly-started messages). Recipient clients MUST initialize a new real-time message for display, and then process action elements within the <rtt/> element. If a real-time message already exists in the same chat session, its content MUST be replaced (i.e. cleared prior to processing action elements). Senders MAY send subsequent <rtt/> elements that do not contain an event attribute. Recipients MUST be able to process 'reset' without first receiving 'new'. See Message Reset, used for Keeping Real-Time Text Synchronized and Basic Real-Time Text.

+ For recipients, both 'new' and 'reset' are logically identical, and differ only for implementation purposes (e.g. highlighting newly-started messages). Recipient clients MUST initialize a new real-time message for display, and then process action elements within the <rtt/> element. If a real-time message already exists, from the same sender in the same chat session, its content MUST be replaced (i.e. cleared prior to processing action elements). Senders MAY send subsequent <rtt/> elements that do not contain an event attribute. Recipients MUST be able to process 'reset' without first receiving 'new'. See Message Reset, used for Keeping Real-Time Text Synchronized and Basic Real-Time Text.

event='init'
- Clients MAY use this value to signal the other end that real-time text is being activated. It can be used to signal activation of real-time text before starting a new real-time message. If used, this <rtt/> element MUST be empty with no action elements. See Activating and Deactivating Real-Time Text.

+ Clients MAY use this value to signal the other end that real-time text is being activated. It can be used to signal activation of real-time text before starting a new real-time message (since it may take a while before the sender starts composing). If used, this <rtt/> element MUST be empty with no action elements. See Activating and Deactivating Real-Time Text.

event='cancel'
Clients MAY use this value to signal the other end to stop transmitting real-time text. If used, this <rtt/> element MUST be empty with no action elements. Recipients SHOULD discontinue sending back <rtt/> elements for the remainder of the same chat session (or unless 'init' is used again). See Activating and Deactivating Real-Time Text.

-

This attribute is used only if &xep0308; (XEP-0308) is implemented at the same time as this specification. If a client supports both XEP-0301 and XEP-0308, clients SHOULD use this attribute to allow recipient clients to have improved presentation of real-time text during message correction (e.g. shown as in-place editing of previous message).

-

This id attribute refers to the <message/> stanza containing the <body/> that is being edited (See 'Business Rules' in XEP-0308). When used, id MUST be included in all <rtt/> elements transmitted during message correction of the previous message. A Message Reset MUST be used when switching between messages being edited (i.e. switching between editing the new partially-composed message versus editing of the previously delivered message).

+

This attribute is used only if &xep0308; (XEP-0308) is implemented at the same time as this specification. If a client supports both XEP-0301 and XEP-0308, clients MUST use this attribute if real-time text is used during editing of the previously delivered message.

+

This id attribute refers to the <message/> stanza containing the <body/> that is being edited (See 'Business Rules' in XEP-0308). When used, id MUST be included in all <rtt/> elements transmitted during message correction of the previous message. The whole message MUST be retransmitted via <rtt event='reset'/> (Message Reset) when beginning to edit the previous message, or when switching between messages (e.g. editing the new partially-composed message versus editing of the previously delivered message).

 -

The real-time message is considered complete upon receipt of a <body/> element in a <message/> stanza. The delivered text in the <body/> element is considered the final message text, and supersedes the real-time message. In the ideal case, the text from <body/> is redundant since this delivered text is identical to the final contents of the real-time message.

-

Senders MUST include an event attribute in the next <rtt/> element that is transmitted after a message stanza containing a <body/> element.

+

The real-time message is considered complete upon receipt of a <body/> element in a <message/> stanza. The delivered text in the <body/> element is considered the final message text, and supersedes the real-time message. In the ideal case, the text from the <body/> element is redundant since this delivered text is identical to the final contents of the real-time message.

+

Senders MAY transmit the <body/> element in the same or separate message stanza as the one containing the <rtt/> element. Senders MUST include an event attribute in the next <rtt/> element that is transmitted after a message stanza containing a <body/> element.

The real-time text standard simply provides early delivery of text before the <body/> element. The <body/> element continues to follow the &xmppcore; specification. In particular, XMPP implementations need to ignore XML elements they do not understand. Clients, that do not support real-time text, will continue to behave normally, displaying complete lines of messages as they are delivered.

 -

For the best balance between interoperability and usability, the default transmission interval of <rtt/> elements for a continuously-changing message SHOULD be approximately 0.7 second. This interval meets ITU-T Rec. F.700 Section A.3.2.1 for good quality real-time conversation. If a different transmission interval needs to be used, the interval SHOULD be between 0.3 second and 1 second.

+

For the best balance between interoperability and usability, the default transmission interval of <rtt/> elements for a continuously-changing message SHOULD be approximately 0.7 seconds. This interval meets ITU-T Rec. F.700 Section A.3.2.1 for good quality real-time conversation. If a different transmission interval needs to be used, the interval SHOULD be between 0.3 seconds and 1 second.

A longer interval will lead to a less optimal user experience in most network conditions. Conversely, a much shorter interval can lead to Congestion Considerations. To provide fluid real-time text, one or more of the following methods can be used:

  • Preserving Key Press Intervals for natural typing display, independently of the transmission interval.
    • @@ -283,7 +288,7 @@ Wait Interval <w n='#'/> - Wait n thousandths of a second. + Wait n milliseconds. RECOMMENDED RECOMMENDED @@ -296,13 +301,13 @@

  • For Element <t/> – Insert Text and Element <e/> – Erase Text:
    The p attribute is an absolute position value, as a character position index into the real-time message, where 0 represents the beginning of the message. If p is omitted, the default value of p MUST point to the end of the message (i.e. p is set to the current length of the real-time message).

  • For the purpose of this specification, the word "character" represents a single Unicode code point. See Unicode Character Counting.

    • -

  • Senders MUST NOT use negative values for any attribute, nor use p values beyond the current message length. However, recipients receiving such p values MUST clip negative values to 0, and clip excessively high p values to the current length of the real-time message. Modifications only occur within the boundaries of the current real-time message.

    • +

  • Senders MUST NOT use negative values for any attribute, nor use p values beyond the current message length. However, recipients receiving such values MUST clip negative values to 0, and clip excessively high p values to the current length of the real-time message. Modifications only occur within the boundaries of the current real-time message.

Recipients MUST be able to process all <t/> and <e/> action elements for incoming <rtt/> transmissions, even if senders do not use all of these for outgoing <rtt/> transmissions (e.g. Basic Real-Time Text). Support for <w/> is RECOMMENDED for both senders and recipients, in order to accommodate Preserving Key Press Intervals. Recipients MUST ignore unexpected or unsupported elements within <rtt/>, while continuing to process subsequent action elements (Compatibility is ensured via Namespace Versioning). Action elements are immediate child elements of the <rtt/> element, and are never nested. See examples in Use Cases.

-

Support the transmission of text, including key presses, and text block inserts.
+

Supports the transmission of text, including key presses, and text block inserts.
Note: Text can be any subset of text allowed in the <body/> element of a <message/>. If <t/> is empty, no text modification takes place.

text]]>

Append specified text at the end of message. (p defaults to message length).
@@ -314,7 +319,7 @@ -

Support the behavior of Backspace key presses. Text is removed towards beginning of the message. This element is also used for all delete operations, including the Delete key, and text block deletes.
+

Supports the behavior of backspace key presses. Text is removed towards beginning of the message. This element is also used for all delete operations, including the delete key, and text block deletes.
Note: Excess backspaces MUST be ignored. Thus, text is backspaced only to the beginning of the message, in situations where the value of p is excessively large.

]]>

Remove 1 character from end of message. (n defaults to 1, and p defaults to message length)

@@ -326,9 +331,9 @@

Remove n characters before character position p in message.

 -

Allow the transmission of intervals, between real-time text actions, to support the pauses between key presses. See Preserving Key Press Intervals.

+

Allow for the transmission of intervals, between real-time text actions, to recreate the pauses between key presses. See Preserving Key Press Intervals.

]]>

-

Wait n thousandths of a second before processing the next action element. This pause MAY be approximate, and not necessarily be of millisecond precision. The n value SHOULD NOT exceed the Transmission Interval. Also, if a Body Element arrives, pauses SHOULD be interrupted to prevent a delay in message delivery.

+

Wait n milliseconds before processing the next action element. This pause MAY be approximate, and not necessarily be of millisecond precision. The n value SHOULD NOT exceed the Transmission Interval. Also, if a Body Element arrives, pauses SHOULD be interrupted to prevent a delay in message delivery.

 @@ -368,7 +373,7 @@
  • When the recipient starts sending messages from a different full JID (e.g. switched systems);
  • When the recipient sends a presence update (e.g. from offline to online);
    • -
  • When the sender resumes composing after an extended pause (e.g. recovery from Stale Messages handling);
    • +
  • When the sender resumes composing after an extended pause (e.g. recipient may have cleared Stale Messages);
  • When the conversation is unlocked (e.g. section 5.1 of &xmppim;);

A message reset is done using the <rtt/> attribute event value of 'reset' (see RTT Attributes).

@@ -381,7 +386,7 @@

Real-time text is generated based on text normally allowed to be transmitted within the <body/> element.

Incorrectly generated Action Elements and Attribute Values can lead to inconsistencies between the sender and recipient during real-time editing. The Unicode characters of the real-time text needs to make it transparently from the sender to the recipient, without unexpected modifications after sender pre-processing. This is the chain between the sender's creation of real-time text, to the recipient's processing of real-time text. Transparent transmission of Unicode characters is possible with sender pre-processing, as long as the transmission from the sender to the recipient remains standards-compliant, including compliant XML processors and compliant XMPP servers.

-

Any inconsistencies that occur during real-time message editing (e.g. non-compliant servers that modifies messages, incorrect Unicode Character Counting) will recover upon delivery of the Body Element, upon the next Message Reset, and/or during Basic Real-Time Text.

+

Any inconsistencies that occur during real-time message editing (e.g. non-compliant servers that modify messages, incorrect Unicode Character Counting) will recover upon delivery of the Body Element, upon the next Message Reset, and/or during Basic Real-Time Text.

For this specification, a "character" represents a single Unicode code point. This is the same definition used in section 1.1 of IETF RFC 5198 RFC 5198: Unicode Format for Network Interchange. <http://tools.ietf.org/html/rfc5198>.. For platform-independent interoperability of Action Elements, calculations on Attribute Values (p and n) MUST be based on counts of Unicode code points.

Many platforms use different internal encodings (i.e. string formats) that are different from the transmission encoding (UTF-8). These factors need to be considered:

@@ -398,7 +403,7 @@

Sender clients MUST generate real-time text (Action Elements and Attribute Values) based on the plain text version of the sender's message with pre-processing completed. This is separate and concurrent to any displayed presentation of the same message (e.g. formatting, emoticon graphics, &xep0071;).

Pre-processing before generating real-time text, include Unicode normalization, conversion of emoticons graphics to text, removal of illegal characters, line-break conversion, and any other necessary text modifications. For Unicode normalization, sender clients SHOULD ensure the message is in Unicode Normalization Form C ("NFC"), specified by section 3 of RFC 5198, and within many other standards such as Canonical XML 1.0.

If Unicode combining character sequences (e.g. letter with multiple accents) are used for Element <t/> – Insert Text, then complete combining character sequences SHOULD be sent. In situations where modifications are required to an existing combining character sequence (e.g. adding an additional accent), an Element <e/> – Erase Text SHOULD be used to delete the existing combining character sequence, before transmitting a complete replacement sequence via the <t/> element. (However, recipients SHOULD NOT assume this behavior from sending clients. See Guidelines for Recipients).

-

For the purpose of calculating Attribute Values, line breaks MUST be treated as a single character, if line breaks are used within real-time text. Conversion of line breaks into a single LINE FEED U+000A is REQUIRED for XML processors, according to section 2.11 of XML XML: Extensible Markup Language 1.0 (Fifth Edition). <http://www.w3.org/TR/xml/>.. In addition, XML character entities are counted as a single character.

+

For the purpose of calculating Attribute Values, any line breaks MUST be treated as a single character. Conversion of line breaks into a single LINE FEED U+000A is REQUIRED for XML processors, according to section 2.11 of XML XML: Extensible Markup Language 1.0 (Fifth Edition). <http://www.w3.org/TR/xml/>.. In addition, XML character entities are counted as a single character.

For Element <t/> – Insert Text, text MUST be obtained using compliant XML processing (including entities converted to characters). Recipient clients SHOULD ensure that the received text is in Unicode Normalization Form C ("NFC"). After this, recipient clients MUST NOT do any other modifications to resulting real-time messages. This is to allow accurate processing of subsequent Action Elements and Attribute Values (The recipient client can separately process/modify a copy of the same real-time message text, if necessary for the purpose of display presentation).

@@ -449,38 +454,28 @@ -

Implementers can choose a preferred activation method for real-time text. For example, clients in the assistive market can choose to do immediate activation of real-time text. Mainstream clients might do user-initiated activation/confirmation of real-time text. The confirmation process could be similar to common activation methods used for audio/video. It is also beneficial for senders and recipients to easily synchronize the enabling/disabling of real-time text.

- -

Activation of real-time text in a chat session (immediate or user-initiated) can be done by:

+

There are many possible ways to implement turning on/off real-time text. Clients can send outgoing real-time text by default. Other clients might choose to do user-initiated activation (e.g. via a button).

+ +

Sender clients can simply begin transmitting real-time text (i.e. send <rtt/> elements), either immediately or upon user-initiated activation.

+

For one-on-one chats, it can be beneficial for clients to easily synchronize the enabling/disabling of real-time text. Upon receiving incoming real-time text, recipient clients can automatically do an appropriate response, such as:

    -
  • Begin transmitting real-time text (by sending any valid <rtt/> elements); or
    • -
  • Signaling first (by transmitting <rtt event='init'/> as the first <rtt/> element).
    • +
  • Activate immediately (begin transmitting <rtt/> elements too); or
    • +
  • Activate after user confirmation prompt (for Privacy considerations); or
    • +
  • Deny (transmit <rtt event='cancel'/>); or
    • +
  • Ignore (discard incoming <rtt/> elements); or
    • +
  • Display only incoming real-time text (e.g. Multi-User Chat participants control their own outgoing real-time text).
-

Recipient clients can respond to any incoming <rtt/> with appropriate response(s), such as any of:

-
    -
  • Accepting immediately (by activating in response); or
    • -
  • Accepting after recipient confirmation (by activating in response, after a user confirmation prompt); or
    • -
  • Deny (by transmitting <rtt event='cancel'/> which is used in Deactivation Methods); or
    • -
  • Ignoring (by discarding incoming <rtt/> as a last resort, without using Deactivation Methods).
    • -
  • Other appropriate responses (e.g. only display incoming real-time text during Multi-User Chat).
    • -
-

Before transmitting <rtt/> elements, it is preferable for a sender client to explicitly discover whether the recipient client supports the protocol defined herein (using Determining Support). Once confirmed, it is useful for sender clients to signal activation using <rtt event=’init’/>, since it may be a while before the user starts to compose a new message.

-

In the absence of explicit discovery or negotiation, the sender client can implicitly request and discover the use of real-time text, by sending <rtt event='init'/> upon activation. It is inappropriate to send any further <rtt/> elements, until the recipient client responds with incoming <rtt/> elements during the same chat session. Implicit discovery allows usage of real-time text as an enhancement to &xep0085; (XEP-0085 Section 5.1), during all situations where it can be used. See Usage with Chat States.

-

It can be acceptable for software to display incoming real-time text without activating outgoing real-time text. Displaying incoming real-time text, while waiting for user confirmation, can be educational to users unfamiliar with real-time text. Care needs to be taken to prevent this situation from becoming confusing to the user. Implementers can add other additional behaviors that are appropriate, such as an introductory note upon first activation, for Privacy considerations.

+

For any client, the preferred first <rtt/> element to send is <rtt event='init'/> as it can quickly signal activation of real-time text, without waiting for the sender to begin composing a new message, and since it is usable regardless of discovery.

+

Before sending real-time text, it is preferable for a sender client to explicitly discover whether the recipient client supports the protocol defined herein (using Determining Support). In the absence of explicit discovery or negotiation, the sender client can implicitly request and discover the use of real-time text, by sending <rtt event='init'/> upon activation. It is inappropriate to send any further <rtt/> elements, until support is confirmed either by incoming <rtt/> elements or via discovery. Implicit discovery allows usage of real-time text as an enhancement to &xep0085; (XEP-0085 Section 5.1), during all situations where it can be used. See Usage with Chat States.

 - -

Real-time text can be deactivated by any of:

+ +

Real-time text can be deactivated by transmitting <rtt event='cancel'/>, or simply by ending the chat session. Recipient clients can respond to deactivation with appropriate response(s), including:

    -
  • Sending a signal (using <rtt event='cancel'/> upon deactivation, deny, or end of chat session); or
    • -
  • Simply ending the chat session (without transmitting any further <rtt/> elements).
    • -
-

Recipient clients can respond to deactivation with appropriate response(s), including:

-
    -
  • Discontinue transmission of <rtt/> elements as well (not applicable to Multi-User Chat); and
    • +
  • Stop transmitting <rtt/> elements as well (not applicable to Multi-User Chat); and
  • Handle the sender's unfinished incoming real-time message (such as clearing it and/or saving it); and
  • Inform the recipient user that sender ended real-time text (or denied/cancelled, if no real-time text was received).
-

Sending an <rtt event='cancel'/> is useful in situations where the user closes a chat window, and ends the chat session. It is useful when the user wants to deactivate real-time text, while still continuing the chat session. After deactivation, any client can reactivate real-time text again in accordance to Activation Methods.

+

Sending an <rtt event='cancel'/> is also useful in situations where the user closes a chat window, and ends the chat session. It is also useful when the user wants to deactivate or deny real-time text, while still continuing the chat session. After <rtt event='cancel'/>, any client can reactivate real-time text again using <rtt event='init'/>.

 @@ -492,7 +487,7 @@

  • After Element <t/> – Insert Text, the cursor position is the p attribute plus the length of the text being inserted. The cursor position is put at the end of the inserted text.
    This is the normal forward cursor movement during text insertion.

  • After Element <e/> – Erase Text, the cursor position is the p attribute minus the n attribute.
    - This is the normal backwards cursor movement to a Backspace key.

    • + This is the normal backwards cursor movement to a backspace key.

  • After an empty Element <t/> – Insert Text (in the format of <t p='#'/> with no text to insert), the cursor position is the p attribute, and no text modification is done.
    This allows cursor response to arrow keys and/or mouse repositioning the cursor.

    • @@ -521,10 +516,13 @@ -

    Real-time text can be generated via monitoring key presses. However, this does not have the advantages of Monitoring Message Changes Instead Of Key Presses. Care needs be taken with automatic changes to the message, generated by means other than key presses. This includes spell check auto-correct, copy and pastes, transcription, input method editors, and multiple key presses required to compose a character (i.e. accents). Key press events do not capture these text changes, and this can cause real-time text to go out of sync between the sender and the recipient.

    +

    Real-time text can be generated via monitoring key presses. However, this does not have the advantages of Monitoring Message Changes Instead Of Key Presses. Care needs be taken with automatic changes to the message, generated by means other than key presses. This includes spell check auto-correct, copy and pastes, transcription, input method editors, and multiple key presses required to compose a character (i.e. accents). Key press events can miss these text changes, and this can potentially cause incorrect real-time text to be transmitted.

    +     + +

    The use of Element <t/> – Insert Text without any attributes, simply appends text to the end of a message, while the use of Element <e/> – Erase Text without any attributes, simply erases text from the end of the message. This sending method can also be useful for special-purpose clients where mid-message editing capabilities are not used (e.g. simple transcription, news tickers, relay services, captioned telephone).

     -

    It is possible for sender clients to implement Message Reset as the only method of transmitting changes to a real-time message. This method of sending real-time text is generally discouraged in most general-use clients. The entire message is simply retransmitted every Transmission Interval whenever there are any text changes. The below is a transmission of the real-time message “Hello there!” at regular intervals while the sender is typing.

    +

    It is possible for sender clients to use Message Reset to retransmit the whole real-time message, whenever there are text changes. The advantage is very simple implementation. Disadvantages can include the lack of Preserving Key Press Intervals, and extra bandwidth consumption that can occur with longer messages, unless stream compression is used. The below illustrates transmission of the real-time message “Hello there!” at a regular Transmission Interval while the sender is typing.

    Hel @@ -542,11 +540,6 @@ Hello there! ]]>

    -

    The advantage is very simple implementation. However, major disadvantages include the lack of Preserving Key Press Intervals, and extra bandwidth consumption that can occur with longer messages, unless stream compression is used.

    -     - -

    The use of Element <t/> – Insert Text without any attributes, simply appends text to the end of a message, while the use of Element <e/> – Erase Text without any attributes, simply erases text from the end of the message. This sending method is unsuitable for most general-purpose clients, but is useful if mid-message editing capabilities are not used (e.g. simple transcription, news tickers, relay services, captioned telephone).

    -

    If editing is needed in the middle of a message, without adding sender support for other Action Elements, the use of Message Reset supports situations where mid-message editing takes place. In this situation, the disadvantages are the same as Basic Real-Time Text, including the lack of Preserving Key Press Intervals, and extra bandwidth consumption that can occur with longer messages, unless stream compression is used.

         @@ -576,7 +569,7 @@

    The in-band nature of this real-time text standard allows one-to-many situations. Thus, real-time text is appropriate for use with &xep0045; (MUC), as well as concurrent simultaneous logins.

    For simplicity, clients can implement real-time text only for one-on-one chat, and not for MUC. However, it can be appropriate to support <rtt/> elements in MUC, even if not all participants support real-time text. Participants that enable real-time text during group chat need to keep track of multiple concurrent real-time messages on a per-participant basis. Participants, with real-time text, will see real-time text coming from each participant that has real-time text enabled. Participant clients without real-time text (whether unsupported or turned off) will simply see group chat function normally on a line-by-line basis, since it is Backwards Compatible.

    -

    Participants that turn off real-time text for themselves, can simply ignore incoming <rtt/> and not transmit outgoing <rtt/>. Participant clients in MUC receiving an incoming <rtt event=’cancel’/> needs to keep outgoing transmission unaffected during Deactivation Methods (otherwise, one participant could deny real-time text between other willing participants).

    +

    Participants that turn off real-time text for themselves, can simply ignore incoming <rtt/> and not transmit outgoing <rtt/>. Participant clients in MUC receiving an incoming <rtt event=’cancel’/> needs to keep outgoing transmission unaffected during Deactivation Guidelines (otherwise, one participant could deny real-time text between other willing participants).

    To minimize on-screen clutter of multiple idle real-time messages, clients can hide idle messages, clear old Stale Messages, and/or prioritize the display of the most useful real-time messages. Prominent visibility of real-time text can be assigned to recent typists and/or moderators (e.g. classroom teacher, convention speaker). For the same participant logged in multiple times in the same room, see Simultaneous Logins. In situations of simultaneous typing by a large number of participants, see Congestion Considerations.

     @@ -651,7 +644,7 @@ Hello - + @@ -659,7 +652,7 @@ Alice Hello Alice - + @@ -667,7 +660,7 @@ This i - + @@ -675,7 +668,7 @@ s Bob This is Bob - + @@ -683,14 +676,14 @@ How a - + re yo - + @@ -698,7 +691,7 @@ u? How are you? - + ]]>

    @@ -965,7 +958,7 @@

    The nature of real-time text can result in more frequent transmission of <message/> stanzas than would otherwise happen in a non-real-time text conversation. This can lead to increased network and server loading of XMPP networks.

    -

    Transmission of real-time text can be throttled temporarily during poor network conditions. It is appropriate to use latency monitoring mechanisms (e.g. &xep0184; or &xep0198;) in order to temporarily adjust the Transmission Interval of real-time text beyond the recommended range. This results in lagged text (less real-time) but is better than failure during poor network conditions. The use of Message Reset can also retransmit real-time text lost by poor network conditions, including stanzas dropped during a network issue or server error. These techniques are useful for mission-critical applications such as Next Generation 9-1-1 emergency services.

    +

    Transmission of real-time text can be throttled temporarily during poor network conditions. It is appropriate to use latency monitoring mechanisms (e.g. &xep0184; or &xep0198;) in order to temporarily adjust the Transmission Interval of real-time text beyond the recommended range. This results in lagged text (less real-time) but is better than failure during poor network conditions. The use of Message Reset can also retransmit real-time text lost by poor network conditions, including stanzas dropped during a network issue or server error. These techniques are useful for mission-critical applications such as next generation emergency services (e.g. text to 9-1-1).

    Excess numbers of real-time messages (e.g. during DoS scenario in Multi-User Chat) might cause local resource-consumption issues, which can be mitigated by accelerated time-out of Stale Messages.

    According to multiple university studies worldwide, the average length of instant messages is under 40 characters. The additional incremental bandwidth overhead of real-time text can be very low for an existing XMPP client, especially one already using many extensions. Bandwidth can also be further mitigated using stream compression, to benefit bandwidth-constrained networks (e.g. GPRS, 3G, satellite).

     @@ -1005,6 +998,7 @@ + @@ -1046,7 +1040,7 @@ ]]>

     -

    The members of the Real-Time Text Taskforce (R3TF), www.realtimetext.org, has contributed greatly specification. Mark Rejhon leads the Jabber/XMPP Taskgroup at R3TF. Members of R3TF who have contributed to this specification include Gunnar Hellstrom, Paul E. Jones, Gregg Vanderheiden, Barry Dingle, and Arnoud van Wijk. Others contributors include Bernard Aboba, Mark Grady, Darren Sturman, Christian Vogler, Norm Williams, and several members from the XMPP Standards Mailing List, including Kevin Smith, Peter Saint Andre and many others.

    +

    The members of the Real-Time Text Taskforce (R3TF), www.realtimetext.org, made significant contributions to this specification. Mark Rejhon leads the Jabber/XMPP Taskgroup at R3TF. Members of R3TF who have contributed to this specification include Gunnar Hellstrom, Paul E. Jones, Gregg Vanderheiden, Barry Dingle, and Arnoud van Wijk. Others contributors include Bernard Aboba, Mark Grady, Darren Sturman, Christian Vogler, Norm Williams, and several members from the XMPP Standards Mailing List, including Kevin Smith, Peter Saint Andre and many others.

    The technique of Preserving Key Press Intervals, otherwise called "natural typing", was created by Mark Rejhon, who is deaf. It is incorporated into this specification in compliance of the XSF's Intellectual Property Rights Policy at http://xmpp.org/extensions/ipr-policy.shtml.