Browse Prior Art Database

Method for enabling changes in chat history

IP.com Disclosure Number: IPCOM000201614D
Publication Date: 2010-Nov-16
Document File: 4 page(s) / 89K

Publishing Venue

The IP.com Prior Art Database

Abstract

In today's communication via information technology, the role of chat software systems is increasing. However, the full potential of this highly interactive medium is not completely exploited in current chat systems: for example, prior art chat systems do not allow to correct errors easily that have occurred in the chat conversation. In this article, a method is proposed to allow changes to the already exchanged pieces of a chat; in particular, this method takes care that changes in the already exchanged text are not be missed by one of the chat partners.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 46% of the total text.

Page 01 of 4

Method for enabling changes in chat history

In today's communication via information technology, the role of chat software systems is increasing as it allows fast cycles between questions and answers, and thereby communication via chat systems is replacing communication via eMail systems. However, the full potential of this highly interactive medium is not completely exploited in current chat systems: for example, prior art chat systems do not allow to correct errors easily that have occurred in the chat conversation.

In this article, a method is proposed to allow changes to the already sent pieces of a chat. In particular, the problem is handled that changes in the already exchanged text could be missed by one of the chat partners. At the same time, overflooding chat participants with unnecessary warnings is avoided.

To illustrate the problem solved by this method, let us consider the following portion of a chat:

Fig. 1: Chat with spelling error

(This page contains 00 pictures or other non-text object)

Here, the word "today" is considered to be accidentally misspelled as "tomay".

In prior art chat systems, a correction of the already sent parts is not possible; thus, occasionally an attempt is made to repair those errors otherwise, two examples are shown in Figure 2.

Fig. 2: Correction approach by additional text

1


Page 02 of 4

(This page contains 00 pictures or other non-text object)

Here, you can see a common correction by the additional conversation "tomay -> today" ... "np".

In the lower right corner, a more verbose alternative is shown as well.

Classifying Changes by Relevance

The method proposed here allows to change the history of a chat conversation. Doing so, the risk is introduced that one of the chat partners might miss a change done in the already exchanged text, which then can cause misunderstandings. The proposed method takes this into account and allows a multi-level approach to avoid this problem, thereby using different strategies depending on the relevance of a change.

Relevances of changes can be classified like this:
changes with low relevance.

1.

For example, correcting a spelling error that did not affect the meaning of a sentence.
changes with some relevance

2.

For example, replacing a word by a different one with slightly different meaning, without intention to change the meaning of the text but with the risk for changing the meaning of the text.
changes with high relevance

3.

Changes that intentionally change the meaning, compared to the meaning of the original message. This could be, for example, a removed or inserted "not", or a corrected URL, or a corrected date/time info.

Rendering Changes by Relevance

Preferably, the rendering of changes for the chat partners takes into account the actual relevance of a change.

For example, for a change with low relevance, the previous (obsoleted) text can be made completely invisible; or it can be made visible on demand as shown in Figure
3.

Fig. 3: Example for render...