XLIFF 1.1 Terminology Integration Best Practices Recommendation

Draft Best Practices Recommendation, 13 June 2004

Editors:

Yves Savourel: <ysavourel@translate.com>
John Reid: <jreid@novell.com>
Andrzej Zydron: <azydron@xml-intl.com>

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Abstract

This draft document defines the prefered best practices methodology for integrating inline terminology resolution within an XLIFF document.

Status of this Document

This is a Draft Committee Best Practices Recommendation. Comments may be sent to xliff-comment@lists.oasis-open.org.

1. Introduction
2. Detailed Specification

1. Introduction

The purposes of this document is to define the preferred methodology when integrating inline terminology resolution with an XLIFF document. This can be done within the <source> and <target> elements.

2. Detailed Specification

The XLIFF <mrk> element has a mtype attribute that can take values from ISO-12620 2.1.11, one of them is "term". The <mrk> also allows extension attributes so additional information can be added as required.

For the purposes of terminology the following namespace should be declared:

  xmlns:term="urn:xliff-term-extensions"

The extension attribute term:pos can be used to denote part of spech identification. The extension attribute term:tgt can be used to provide target term identification.

Example:

  <trans-unit id="1.0">
   <source>Remove the left-handed widget from the subassembly</source>
   <target><mrk mtype="term" term:pos="VB" term:tgt="odlacz">Remove</mrk> 
              <mrk mtype="term" term:pos="NN" term:tgt="leworeczna lydzetka">the left-handed widget</mrk> from 
			  <mrk mtype="term" term:pos="NN" term:tgt="podzespol">subassembly</mrk></target>
  </trans-unit>

2.1 Elements

The The requirements for the inline resolution of target terminology is met by use of the <mrk> element along with the use of namespace extension attributes.

2.1.1 Mark Element

The full specification of the <mrk> element is available from the main XLIFF 1.1 specification document.

2.2. Attributes

term: attributes term:tgt, term:pos

2.2.1. Terminology Namespace Attributes

term:tgt

Target language term - The target language term.

Value description:

The term in the target language.

Default value:

Undefined..

Used in:

<mrk>,

term:pos

Part of Speach - The part of speach of the identified term.