%ents; ]>
Language Translation This document defines an XMPP protocol extension for providing language translation facilities over XMPP. It supports human, machine, client-based, and server-based translations. &LEGALNOTICE; 0171 Experimental Standards Track Standards Council XMPP Core XMPP IM XEP-0030 langtrans Boyd Fletcher boyd@spawar.navy.mil Daniel LaPrade dlaprade@echostorm.net Keith Lirette keith.lirette@gd-ais.com Brian Raymond braymond@echostorm.net 0.3 2008-02-01 kl/bf Modified semantics to use IQ stanzas for communication with servers; changed dst_lang to destination_lang and src_lang to source_lang. 0.2 2006-04-24 psa Added text about use of Thread IDs. 0.1 2006-01-24 psa Initial version. 0.0.4 2006-01-17 psa Converted to XML format, cleaned up text, modified examples, changed pivotable and reviewed attributes to xs:boolean, corrected schema. 0.0.3 2006-01-16 bf Changed xml:lang to destination, derived to derived_from; added service discovery identity. 0.0.2 2005-12-28 bf Miscellaneous edits. 0.0.1 2005-12-21 bf First draft.

There currently exists no standard for describing language translations over a text chat protocol. While numerous products and services exist to provide translation of text, there exists no standardized protocol extension for requesting a translation and expressing the details of the translation XMPP (see &rfc3920;). This document describes how to express a translation and its components in an XMPP message as well as a method to request translation.

Direct translation can be realized by either client-side translation before sending or transparent components translating messages on the fly. Discovering XMPP entities capable of translation allows for clients to request translation from them based on their capabilities. The remote XMPP entity could be either an automated translation service or a human providing translation.
TermDefinition
Original TextThis is the message text that was originally created by the sender. This is the text that is translated.
Translated TextThis is the message text that has been translated by the language translation engines. This also called the destination text. For any given message there can be multiple destination text message bodies.
Pivot LanguagePivoting is the process of using one or more intermediate languages to translate from a given source language to a specific destination language. For example, if you needed to translate from English to Russian but only had translators that went from English to French and French to Russian then you could use French as a pivot language.
Pivot TextThis is the translated text of the original message in a pivot language. For any given destination language, there can be zero or more pivot text bodies. The ordering of pivoting is required to be specified for the destination language.
Language Translation EngineSince not all language translation engines are the same quality it is important to some classes of users that they know what translation engine was used. It is equally important to also be able to select a specific translation engine for a given language pairing if more than one engine is available.
Language Translation Character SetSome language translation engines can only translate text between languages if certain character sets (or code pages) are used.
Language Translation Dictionary In order to enhance the accuracy of translation engines most support the concept of mission specific dictionaries.

The protocol defined herein addresses the following requirements:

  1. Enable an XMPP entity to request a translation from a remote XMPP entity.

  2. Enable an XMPP entity to express the following mandatory elements of a translation for any receiving entities.

    1. Identification of Original Text
    2. Identification of Translated Text
    3. Identification of any Pivot Language(s) and Text
    4. Identification of the method and order of translation

  3. Enable an XMPP entity to express the following optional elements of a translation for any receiving entities.

    1. Identification of Language Translation Engines used.
    2. Identification of Location of the translation.
    3. Identification of Sender and Destination language of choice.
    4. Discovery of Server support for translation including which language pair, dictionaries, and engines are available.
    5. Identification of desire to text to be translated or not to be translated.

The following methods of translation are supported:

  1. Manual or Human
  2. Machine or Automated
  3. Machine with Human Review

The following use cases simple scenarios for expression translation as well as requesting them from remote entities.

A message directly translated by the originating XMPP entity or a transparent XMPP entity delivered to a remote entity with only the required elements of source and destination language; this is the simplest case for a translation from one language to another. The source language is known because there is no <translation/> tag describing it. Three translation methods are supported by doing the following:

  1. If no 'engine' attribute is present, then manual (or human) translation was performed.
  2. If an 'engine' attribute is present then machine (or automated) translation was performed, where the translation engine is identified by the value of the 'engine' attribute. If the 'engine' attribute is present its value is an empty string, then the name of the translation engine was not available.
  3. If the 'engine' attribute and the 'reviewed' attribute are present, then machine translation was performed but the message text was reviewed and possibly modified by a human.
Hello Bonjour How are you? comment allez-vous? ]]>

A message translated by the originating XMPP entity or a transparent XMPP entity delivered to a remote entity with the pivot languages used to accomplish the translation. The source language is known because there is no translation tag describing it. When a translation is done via a pivot language, the pivot languages and their order of use MUST be specified.

Bonjour Hello x443;лте comment allez-vous? How are you? Как вы? ]]>

A message translated by the originating XMPP entity or a transparent XMPP entity delivered to a remote entity using pivot languages and machine translation. The source language is known because there is no &X; translation tag describing it.

Bonjour Hello x443;лте comment allez-vous? How are you? Как вы? ]]>

When connected to a server, a XMPP entity can locate translation providers by asking a server which translation providers are attached to the server; this MUST be done using &xep0030;. The server SHOULD return the availability of of translation providers and language pairings for which the user has rights to use.

]]> ... ... ]]>

Service Discovery is used to determine if a JID provides translation services. The JID can also be a bot (e.g., <towerofbabel@shakespeare.lit>) or a server component (e.g., <translation.shakespeare.lit>).

]]> ... ... ]]>

The supported languages and other details for the service must be known to use it. It is permissible for a translation service to provide multiple translation engines for the same language pairing -- if this is done, then a separate <item/> tag MUST be used for each pairing. A 'dictionary' attribute MAY be used to specify the dictionary for a specific <item/>. In order to specify more than one dictionary for a given language pairing then a separate <item/> tag MUST be used for each dictionary specification for that language pairing.

]]> ]]>

To request service from a translation provider you can send a message to a provider requesting translations. The lack of a 'derived_from' attribute in the <translation/> element indicates a request for a translation.

How are you? ]]> hello, how are you? comment allez-vous? ]]> How are you? ]]> How are you? Come siete? Wie geht es Ihnen? ]]>

If a specific dictionary is required you MAY request a dictionary. This SHOULD have been returned when discoing the server although a dictionary MAY be requested which was not. The dictionaries are translation engine specific and are free form text.

How are you? ]]> hello, how are you? comment allez-vous? ]]>

If the translation service cannot complete the translation it SHOULD return a error indicating some part of the translation request was problematic, unless doing so would violate the privacy and security considerations in XMPP Core and XMPP IM, or local security and privacy policies.

How are you? ]]>

If privacy or security considerations make returning an error not feasible it SHOULD return a error.

How are you? ]]>

In order to reduce user confusion and misunderstanding of a translated message body, it is RECOMMENDED that implementations of langtran implement the following user interface features.

  1. Translated messages should be clearly identified as being a translation.
  2. The display of translated message should clearly show how (automated, manual, automated with human review) a messaged was translated.
  3. The display of a message should clearly show if the translation is the destination, original or pivot language.
  4. If pivoting is used, the destination message text should be marked in such a way as to indicate that it was translated on one or more pivot languages, what those language are, in what order they were used, and the actual pivot language text should be accessible to the user.
  5. It is recommended that only one level of pivoting be used as quality of the destination translation degrades significantly after each pivot.

Note: The 'reviewed' and 'pivotable' attributes are of type "boolean" and MUST be handled accordingly. &BOOLEANNOTE;

In order to properly process multi-language messages, clients MUST implement support for multiple message bodies differentiated by the 'xml:lang' attribute as described in RFC 3920.

Potential attacks may be easier against services that implement translation because of the potential disclosure of information regarding language pairings, engines, and dictionaries used however no specific vulnerabilities are introduced.

This possible weakness can be mitigated by not returning specifics to requesting entities and the responding entity MAY perform authorization checks in order to determine how to respond.

This document requires no interaction with &IANA;.

The ®ISTRAR; shall include 'http://jabber.org/protocol/langtrans' and 'http://jabber.org/protocol/langtrans#items' in its registry of protocol namespaces.

The XMPP Registrar shall add a type of "translation" to the "automation" category in its registry of service discovery identities.

 ]]> ]]>