- From: Felix Sasaki <fsasaki@w3.org>
- Date: Mon, 7 May 2012 06:20:41 +0200
- To: Yves Savourel <ysavourel@enlaso.com>
- Cc: Dave Lewis <dave.lewis@cs.tcd.ie>, public-multilingualweb-lt@w3.org
Received on Monday, 7 May 2012 04:21:08 UTC
2012/5/4 Yves Savourel <ysavourel@enlaso.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. A big +1. Felix > Currently such application cannot read an XLIFF document properly. > > Cheers, > -yves > > > > > > -- Felix Sasaki DFKI / W3C Fellow
Received on Monday, 7 May 2012 04:21:08 UTC