ITS in <mrk>

[Yves Savourel <ysavourel@enlaso.com>]

Hi all,

I had an action item from the Face-to-face meeting to look at the possibilities to use directly the ITS namespace in the <mrk> elements to implement comments, translate and term.

Here it is:

Because <sm/> and <em/> used in the overlapping cases are empty elements, the ITS attribute semantic does not work for them. That is, for example, if you have its:term in <sm/> the scope is the content of <sm> (always empty) and not the content from <sm/> to <em/>.

So for <sm/> and <em/> we have to define our own attributes.

While the semantic works for <mrk> (the scope is the content of <mrk>), I feel that it would be confusing to have to use two different attributes to express the same information depending on what annotation element is used.

So, to me, that eliminate using directly the its:translate, its:term, etc. attributes. This does not mean we don't support the corresponding ITS data categories. They are just implemented using the XLIFF markup and can be mapped using ITS rules if needed.

-ys