Contributions > Service Genres > Translate 1.1 Login
  Minimize
 
 
  Print  Minimize
Name
 
  • Name: Translate
  • Alternate Name: Translation
Rationale
 

This Service Genre has been developed to describe the behaviours required of a Translation Service. A Translation Service is confined to natural langauges (e.g. French), and alters a source document from one natural langauge to a different natural language, whilst preserving the semantics of the source document.

Version
 
  • e-Framework Service Genre Version: v1.1
Description
 

This Service Genre interprets the meaning of a source text in one natural language, and produces the equivalent text in a different natural language.

It is important to note that it is meanings that are translated, rather than individual words. Translation services can be bilingual (two languages only), or multi lingual. Translations can be in one direction only, or bi directional. Often an intermediate form is used between the different languages.

Translation services can be configured by domain. This allows the translator to use a smaller set of substitutions, and thus a better translation can be generated. Translations of conversations or ‘non standard’ text are much more difficult than translations of legal documents or weather reports.

There are broadly three algorithmic approaches used by translators:

  • Direct: where a word is translated directly, usually without an intermediate into the target language. Typically meaning is lost.
  • Interlingua: where the text is analysed in a representation form from which the final text is subsequently generated. The intermediate language can then (theoretically) be used by any number of generator modules to create the target text. The intermediate language is a machine representation – it is probably not something that a human could read.
  • Transfer: where the text is translated into a language dependent intermediary. A specific translation module needs to exist for each translation language pair. Whilst this approach creates a lot more work if new languages are to be added, the programming of the intermediary is much easier – as there are only two languages to be involved.

Commonly, human intervention is required for a successful translation, however, the literature does contain some examples where machine translated documents can be used directly. It is further noted within the literature that translation software is typically used as an aide by human translators.

NOTE: specifications exist for defining a service where human translation can be requested and managed. Such specifications are NOT part of this service genre.

As defined the Translate Service Genre is not access controlled. Any client may attempt to contact a translate service end point. There are no authentication controls. The service end point is responsible for determining which clients can make translations.

Functionality
 

The Translate Service Genre supports one function:

  • Translate Content - where the requester provides source text in one natural language, for translation into another natural language.

No other functionality is defined. The functionality that is defined MAY be extended.

Usage Scenarios
 

 

Applicability
 

Translation Services SHOULD be used for the translation of formal documents from within a specific domain.

Translation Services SHOULD NOT be used for general translations of informal content.

Requests & Behaviours
 

Translate Content SHALL meet the following conditions:

  • The Request SHOULD specify:
    • The source language of the text.
    • The destination language into which the text is to be translated
    • The text to be translated
  • The Request MAY specify:
    • A specific domain based vocabulary to use
  • The Response SHOULD:
    • Include the translated text.
    • Indicate any error conditions (such as the message not being accepted for delivery).
Use & Interactions
 

Individual Service Expressions SHOULD provide models showing how clients interact with service interfaces.

Structure
 

 

Applicable Standards
 

None

Design Decisions and Tradeoffs
 

Translate Services MAY require authentication and authorisation mechanisms.

Translate Services MAT contain functionality to manage the range of languages and domain vocabularies to use.

Implementation Guidance and Dependencies
 

 

Known Uses
 

SysTran

Related Service Usage Models (SUMs)
 

 

Related CORE SUMs
 

 

Classification
 
Domain(s) [ ] Learning & Teaching [ ] Research
[ ] Libraries
[ ] Administration
[ ] IT Services
[X] Common
Maturity [ ] Immature [X] Mature
Development Scale [ ] Isolated [X] Ubiquitous
Status [X] Approved [ ] Placeholder
[ ] Unapproved
[ ] Superseded
[ ] Withdrawn
Confidence Level [ ] High [X] Medium [ ] Low
Version History
 
Version Date Author Description Organisation / Project
v1.1 2007-03-06 Phil Nicholls Draft approved by eFIG JISC 
Intellectual Property
 

© Copyright, e-Framework Partners 2007

Attribute this work as:
Translate Genre, The e-Framework Partners, 2007. Derived from...

Attribution History:

  1. Derived from Translate Genre authored and submitted by Phil Nicholls on behalf of the JISC (e-Framework Partner), 2007

Last updated 14 October 2008

 
 
  Minimize
Unless otherwise noted material from the e-Framework website can be downloaded for your own use under a Creative Commons Attribution-ShareAlike 2.5 Australia License
CreativeCommons-by-sa.png
 
Friday, March 19, 2010
Copyright e-Framework Partners 2006 - 2009

Terms and Conditions

Privacy Statement