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

RE: targetPointer Requirement update

From: Yves Savourel <ysavourel@enlaso.com>
Date: Sun, 6 May 2012 05:33:18 -0600
To: "'Arle Lommel'" <arle.lommel@dfki.de>, "'Dave Lewis'" <dave.lewis@cs.tcd.ie>
CC: <public-multilingualweb-lt@w3.org>
Message-ID: <assp.04731d690b.assp.0473d986b6.000f01cd2b7c$090712d0$1b153870$@com>
Hello Arle, Dave, all,

> ... But we really need to know how common this need is.
> If it is not common, I would agree with Dave. 
> If it is common, however, I'd like to consider targetPointer.
> Dave's point about scope creep is important to keep in mind,
> so perhaps we need a clearer use case to see how difficult
> it would be.

To me targetPointer completes the part of the requirement R019 (http://www.w3.org/TR/itsreq/#multilang) not addressed through best practices. Multilingual XML documents do exist and currently they can't be processed efficiently by ITS1-aware tools.

I think XLIFF or TMX or TS are good enough use cases (XLIFF and TMX are also mentioned in R019). A tool implementing ITS2 should be able to work with such formats.

Note also that this is an enhancement of the translateRule rather than a new data category. It is something identified by the ITS Interest Group after ITS1 was released. I think addressing those issues falls into the first goal listed in our charter: "To develop the successor of ITS 1.0". Whether or not targetPointer makes it into an implemented feature and the final ITS2 specification is another matter, but in my opinion there is no doubt it deserves to be in our requirements list.

Received on Sunday, 6 May 2012 11:33:45 UTC

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