W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2005

[ESW Wiki] Update of "its0503ReqTermIdentification" by MasakiItagaki

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 07 Jun 2005 07:33:23 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050607073323.2591.14090@localhost.localdomain>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by MasakiItagaki:
http://esw.w3.org/topic/its0503ReqTermIdentification


------------------------------------------------------------------------------
  == Challenge/Issue ==
  The capability of specifying terms within the source content is important for terminology management that is beneficial to translation/localization quality. Terms to be identified include any domain-specific words and abbribiations for which translators need additional information in order to find appropriate concepts in their target langauges. Term identification also facilitates the creation of glossaries and allows validation of terminology usage in the source and target documents.
  
- '''[[CL]] How about refering to the usage scenario here?]]'''
- '''[[MI]] Yes, we need it. How about the format of links to usage scenarios? If we don't need a specific format, I'll put some reference in here.]]''' '''[[YS-'''No special format needed, for now just point to the wiki page, we'll fix it to point to the correct section in the final document.''']]'''
- 
  Meanwhile, identified terms could be used for indexing that may require some language specific information. For example, Japanse words are sorted not by script characters, but by phonetic characters. Therefore when a Japanese index item should be accompanied with a phonetic string, called Yomigana.
  
  As a result, terms may require various attributes, such as part of speech, gender, number, term types, definitions, notes on usage, etc. To avoid such a large attribute data is repeated within a document, it should be possible for identified terms to link to externalized attribute data, such as glossary documents and terminology database (See Quick Guideline Thoughs below).  
  
  == Notes ==
  For more details, please see discussions on term links at OASIS/XLIFF [http://lists.w3.org/Archives/Public/public-i18n-its/2005JanMar/0069.html] for more details. The OSCAR/TBX working group is currently working on drafting the TBX Link sepcification [http://www.lisa.org/oscar/tbxlink/].
+ 
+ == Related Usage Scenario ==
+ Terminology Creation and Translation [http://esw.w3.org/topic/its0504ReqTermCreationTrans]
  
  == Quick Guideline Thoughts ==
  An example of externalization of term attributes:
Received on Tuesday, 7 June 2005 08:30:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:45 GMT