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

Re: targetPointer Requirement update

From: David Lewis <dave.lewis@cs.tcd.ie>
Date: Mon, 07 May 2012 18:04:15 +0100
Message-ID: <4FA8008F.3080408@cs.tcd.ie>
To: public-multilingualweb-lt@w3.org
Hi Yves,
If this is to deal with XLIFF and TMX file specifically, then I'm afraid 
I still don't understand the use case very well.

Where there is already an element structure in the host document that 
indicates source and target content, what is the use case where the 
implementer wouldn't read the relevant XLIFF or TMX schema document to 
figure out how to parse this themselves. This seems simpler than 
defining a new standard tag in ITS to essentially explain the schema of 

Is there some class of useage of XLIFF and TMX that makes the 
interpretation of their source-target binding difficult to parse 
directly in practice?

Also, consideration non-translation use cases such as semantic tagging 
or parallel text extraction , it doesn't seem likely that you'd do these 
without needing either to write to the file or understand say the 
distinction between translation and an alt-trans - in which case you'd 
need a working understanding of XLIFF/TMX anyway.


On 04/05/2012 16:00, Yves Savourel wrote:
> 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.
> Cheers,
> -yves
Received on Monday, 7 May 2012 17:04:37 UTC

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