[ESW Wiki] Update of "its0503ReqTermIdentification" by MasakiItagaki

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


------------------------------------------------------------------------------
  
  = Term Identification =
  
+ == Summary ==
- == Description: ==
- 
  It should be possible to identify terms inside an element or a span and to provide data for terminology management and index generation. Terms should be either associated with attributes for related term information or linked to external terminology data. 
   
  
+ == Challenge/Issue ==
- == Background: ==
- 
  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.
  
  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.  
+ 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 '''LINKS TO BE ADDED WHEN AVAILABLE'''.
+ 
+ == Quick Guideline Thoughts ==
+ An example of externalization of term attributes:
+ 
- [Example]
+ [Example] 
-  
  <source>Our guests can appease their spirit of adventure and itchy feet by exploring the various islands of our small  '''<its:term cID="1234">archipelago</its:term>'''</source>.
  
  The term, '''archipelago,''' could link to the following external data:
  
  [Example]
-  
  <its:termEntry cID="1234ABE34FE">
   '''<its:term>archipelago</its:term>'''
   <its:pos>noun</its:pos>
@@ -46, +48 @@

   </its:info>
  </its:termEntry>
  
- == 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 '''LINKS TO BE ADDED WHEN AVAILABLE'''.
-

Received on Thursday, 19 May 2005 05:54:43 UTC