F.A.Q.
1) What is Real-Time Text?
Real-Time Text is a feature that allows users to see text as it is typed into a text interface. It differs from Internet instant messaging (IM) and mobile texting (SMS) in that the characters appear in near real-time as they are typed, not as a block of text after it is written. Real-Time Text is communicating using text that is the closest to voice communication.
2) What can Real-Time Text be used for?
Real-Time Text can be used on its own to enable conversations using text. It can also be used where voice is impractical (such as in noisy environments or meetings), or as an adjunct to voice and video conversations to transfer text information with the audio or video feed. Real-time transcription of a video or audio conference is an example.
Real-Time Text is part of a concept called “Total Conversation” which provides bi-directional real-time exchange of video, text and voice between users in two or more locations.
3) What is Total Conversation?
Total Conversation is a service allowing an audiovisual conversation with bidirectional full-duplex real-time transfer of Real-Time Text, Video and Voice between 2 or more users.
Total Conversation allows people with a disability (deaf or hard of hearing or blind for example) and people who find themselves in a situation where
the complementing streaming media Real-Time Text, video and Voice together fulfills the conversation needs much
better than only Voice (background noise, being in a library etc).
Total Conversation is an ITU service description in
ITU-T Rec. F.703.
4) Why is Real Time Text important to people who are deaf or hard of hearing?
In addition to its many applications for fully hearing people, Real-Time Text is important as an alternative to voice communications for people who are deaf and hard of hearing. It allows a more natural, bi-directional flow of text based conversation to take place compared with the “type-enter-wait-read-response-reply” technology of IM and SMS.
In fact: when Real-Time Text is fully mainstream, it will be solving one of the biggest accessibility problems of Internet communications for people who are deaf or hard of hearing!
5) What is the technology behind Real-Time Text?
At the core of the framework for Real-Time Text over Internet Protocol (IP) networks is the Session Initiation Protocol (SIP) and the Real-Time Text transport standard as currently described in IETF RFC 4103.
This framework is designed to be compatible with voice over IP (VoIP) and Video over IP environments. It also builds upon, and is compatible with, the high-level user requirements of deaf, hard of hearing, and speech-impaired users, as described in RFC 3351.
6) What is the Real-Time Text Taskforce?
The R3TF is a centre for advocacy and knowledge exchange in the field of real-time text. It will contribute to the promotion, design and implementation of interoperable RTT solutions and encourage adoption of RTT in mainstream products and services.
The R3TF is also an Accessibility organisation for people who are Deaf, Hard of Hearing or have a speech impairment, since RTT will make Telephony over Internet fully accessible for everybody and this fits in the "Design for All" approach. The R3TF has as goal to make Real-Time Text mainstream and part of universal design, so that all people can communicate with each other without difficulty or limitations or having to use expensive assistive telecom equipment like a text telephone.
7) How can I participate in the Real-Time Text Taskforce?
All active work, standardization, writing of documents and building and other projects will be done in dedicated Task-Groups.
To participate directly in the R3TF, you can join one or more Task-Groups. Or it can be indirect by helping the R3TF with resources or funding.
8) What can the R3TF Participants do?
The short answer: everything that helps the R3TF to do her tasks and goals.
The most direct way is participating in the Task-Groups, or even after approval from the Operational Board, form a new Task-Group and become the task-Group leader.
9) What is the relationship between Internet Society and the Real-Time Text Taskforce?
ISOC has launched an Enabling Access initiative which aims to address some of the fundamental impediments to Internet growth and usability.
One aspect of the initiative focuses on advancing the development of technologies, the business case, and policy environment for facilitating the use of the Internet by people with disabilities. As part of this effort, ISOC has served as an “incubator” of the R3TF by providing coordination assistance, technical expertise, and implementation support for the Taskforce. Now that the R3TF is an independent foundation. The R3TF and ISOC will work together to archive the goals of the R3TF.
10) What is the difference between ToIP and Real-Time Text?
ToIP is RFC4103, which is Real-Time Text on IP networks using SIP. Real-Time Text is streaming text that is send and recieved on a character by character basis and that is also possible using different standards and protocols.
11) How can we donate funds/sponsor the R3TF?
We will publish very soon the details how companies and organisations can sponsor the R3TF.
Please contact arnoud [at] realtimetext.org or via the contact form for sponsor and partner information in the meantime.
12) Is the R3TF affiliated to the IETF?
No, while Real-Time Text has been documented within the IETF processes, the R3TF is an independent Foundation.
