W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > May 2012

RE: targetPointer Requirement update

From: Yves Savourel <ysavourel@enlaso.com>
Date: Fri, 4 May 2012 09:00:25 -0600
To: "'Dave Lewis'" <dave.lewis@cs.tcd.ie>, <public-multilingualweb-lt@w3.org>
Message-ID: <assp.0471406173.assp.0471fdd9a5.000301cd2a06$a2bc9250$e835b6f0$@com>
Hi Dave, all,

> However, this explanation does make me think the 
> use case is out of scope for ITS 2.0.  because:
> ... 
> ii) There are already standard file formats, i.e. XLIFF,
> TMX, that support this.
> ... not using these is not best practice. 
> So it doesn't seem in scope to develop a standard 
> solution for something that isn't best practice or 
> in general is needed solely to support issues in 
> proprietary formats.

XLIFF and TMX are precisely why something like targetPointer is needed.
ITS is not meant just for translation. As applications like Tadej's Enrycher show, one may want to perform other linguistic-related tasks (e.g. semantic tagging, spell-checking, data-mining, alignment, creation of an MT-generated TM, etc).

I think we should expect any XML tool that ITS2-aware to be able to read a document in format XYZ only knowing its ITS properties. It shouldn't need to know about XLIFF or TMX to process XLIFF or TMX documents. Currently such application cannot read an XLIFF document properly.

Received on Friday, 4 May 2012 15:00:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:44 UTC