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: Thu, 14 Apr 2005 07:57:45 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050414075745.30955.37977@swada.w3.org>
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


------------------------------------------------------------------------------
  
  == Description: ==
  
+ It should be possible to identify terms inside an element or a span. Terms should be either associated with attributes for related term information or linked to external terminology data. 
- It should be possible to identify terms inside an element or a span together
- with related attributes. 
- 
   
  
  == Background: ==
  
+ The capability to specify terms within the source content is important for terminology management that is beneficial to translation/localization quality. It facilitates, for example, the creation of glossaries and indexes, and also allows terminology validation between source and target documents.
- The capability to specify terms within the source content is important for
- terminology management and index creation. It facilitates, for example, the
- creation of glossaries and indexes, and also allows terminology validation
- between source and target documents.
  
+ 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.  
- Each term should be accompanied by term attributes depending on
- identification purposes. If it's for glossary data, term attributes may be
- part-of-speech and a term type, while index terms may have a sorting string.
  
+ [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>
+ 	<its:info>
+ 		<its:def>Group of island<its:def>
+ 		<its:pronunciation>"är-k&-'pe-l&-"gO, "är-ch&-<its:pronunciation>
+ 	</its:info>
+ </its:termEntry>
+ 
  
  == Notes: ==
  
+ Reference to discussions on term links: http://www.oasis-open.org/apps/org/workgroup/xliff/email/archives/200407/msg00026.html

- Members discussed TMX-Link and TBX-Link as references (see Minutes
- 2005-03-03: ITS teleconference), and the both standards should be reviewed
- when the solution for this requirement is reviewed. 
  
- 
- '''[CL] Great. Some feedback:
- 
-  1. I am not sure that sth. like TMX-Link exists.
-  2. Possibly, we can reuse some of the thoughts from http://www.oasis-open.org/apps/org/workgroup/xliff/email/archives/200407/msg00026.html '''
- 
Received on Thursday, 14 April 2005 07:58:01 GMT

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