RE: Term Identification: Requirement

Hi everyone,

Sorry for sending a pointer to an inaccessible link.

I include the text below ...

Best regards,
Hi there, 

Since the discussion for intra-source/intra-target extension points revolves around terminology-/linguistics related examples, and since we are touching this area also in other contexts, here a couple of thoughts about the representation of terminology-/linguistics related information ...

I would favor an approach which some might term 'normalized' (in the sense of database theory), others 'single source-oriented/non-redundant'. It boils down to the following:

If you have chunks of information (e.g. all information related to a terminology concept) than don't repeat it, rather link to it. Accordingly, Yves' example would be become:

<source>Our guests can appease their spirit of adventure and itchy 
feet by exploring the various islands of our small  <xyz:term cID="1234ABE34FE">>archipelago</xyz:term></source>.

'cID' abbreviates 'concept identifier'.

The identifier would be related to terminological database which is identified by the URN to which the namespace prefix belongs.

An XML serialization of the concept identified by 'cID' would look like the following:

<xyz:termEntry cID="1234ABE34FE">
  <xyz:def>Group of island<xyz:def>
  <xyz:pronunciation>"är-k&-'pe-l&-"gO, "är-ch&-<xyz:pronunciation>

Using the Open Lexicon Interchange Format (OLIF; see as the representation for the XML serialization, you could end up with XLIFF which looks like the following:

<xliff version="1.1" xmlns="urn:oasis:names:tc:xliff:document:1.1" xmlns:xyz="urn:appInfo:Items" xmlns:xsi="" xmlns:olf="">
 <file original="island.txt" source-language="en" target-language="fr" datatype="plaintext">
     <olif OlifVersion="2.0, February 2002">
      <header CreaTool="CoolTerm" CreatToolVersion="1.4.3" OrigFormat="internal" AdminLang="EN" CreaDate="20031119091301Z" CreaId="X">
        <subjFieldDCS DCSType="replacement">CompLingCompany</subjFieldDCS>
        <quotMarkInfo QuotMarkRet="some"/>
       <entry ConceptUserId="2312">
        <mono MonoUserId="1232">
           <definition>Group of islands</definition>
          <note>pron:"är-k&amp;-'pe-l&amp;-"gO, "är-ch&amp;-</note>
   <trans-unit id="x">
    <source>Our guests can appease their spirit of adventure and itchy feet by exploring the various islands of our small  <olf:term cID="2312">archipelago</olf:term>
   <target>Notre visiteurs ...</target>

The benefits of this 'link-only' approach would clearly start to show if you for example would have the term 'archipelago' 1000 times in your document ... 

Best regards,
-----Original Message-----
From: [] On Behalf Of Masaki Itagaki
Sent: Thursday, March 31, 2005 4:47 PM
Subject: RE: Term Identification: Requirement

Hi Christian

Thank you for your feedback. Yves was talking about TMX-link in a previous
teleconference. Let's discuss that today. I would like to look at the
contents in the Oasis link, but it asks ID and PW. Would you mind posting
the page itself here (if it's not too long).


-----Original Message-----
From: Lieske, Christian [] 
Sent: Thursday, March 31, 2005 2:18 AM
Cc: Masaki Itagaki
Subject: RE: Term Identification: Requirement

Hi Masaki,

Great. Some feedback:

1. I am not sure that sth. like TMX-Link exists.
2. Possibly, we can reuse some of the thoughts from

Best regards,

Received on Thursday, 31 March 2005 15:05:22 UTC