Re: TAUS TML proposal

Actually, looking at the proposal in more detail, I see that it has some real problems in that it exposes metadata in ways that would totally break in non-aware processes. Because it is relying on native HTML mechanisms that only work if tools are aware of the “kludge” used to hide the data, it would end up blowing up word counts for other tools, result in content being accidentally translated (since <span> tags are not, by default protected), etc. I really do not like the overloading of existing mechanisms in this way when they serve fundamentally different purposes. It would take only one tool in the chain that processed the content in an intelligent way that does not match the expectation for things to break.

There is a real advantage to using ITS in these contexts because then tools that don't understand it also know that they don't understand it. The proposed TML in the article however, would be problematic because there is nothing in it to tell the tools (a) that they don't know what to do with it and (b) what they should do with it. It is thus entirely opaque in a bad way.

-Arle


 
Sic scripsit Dave Lewis ad "public-i18n-its-ig@w3.org" die Wed Apr 08 2015 14:50:31:
 
> Guys,
> did anyone see the article in TAUS Review #3 on 'translation mark-up' language?
> http://issuu.com/tausreview/docs/tausreview-dataissue-april2015/14
> 
> It suggests an annotation mark-up that seems to replicate ITS2.0 terminology and text analysis tag functionality.
> 
> Dave