RE: [ISSUE 34] Quality error category proposal

Hi Felix, all,

We’re painfully aware of the drawbacks of “overlap” solutions in XML. But there is no way around having them in XLIFF. So, as you say, the solution would be to reference some kind of ‘holder’ element and have the ITS info there.

The main problem with using the same attributes both in the "inline" and in the "referenced" notation is that the same ITS attributes would need to have two different semantics.

- In the inline case the information applies to the content of the element where the attribute is. That's the normal and expected behavior:

<span its:term="yes" its:locNoteType="alert" its:locNoteDescription="...">...</span>

- but in your converted notation, the information applies instead to the content of the element that references the element where the attributes are:

<metadata id="itsinfo" its:term="yes" its:locNoteType="alert" its:locNoteDescription="...">

Currently we can't have it both ways.
We would need to specify that difference explicitly somehow. And I'm not sure it would be a good solution.


Another problem is that if ITS doesn't define some 'holder' element for the QA-errors (I guess there is always <its:span>, but it doesn't feel right to use for this. So I suppose one could be provided, but that's a rather awkward solution.

This drives me to think one may as well define the whole data category in an XLIFF module.
I suppose that's fine. It would be something like this:

<unit>
 <segment>
  <source>...</source>
  <target>Insert the <mrk id='m1' type='x-xlfQA' ref="#qa1">Pen Drive</mrk> in the USB port</target>
 </segment>
 <xlfQA:qaItem id="qa1"
  error????="URI to machine readable information">Should be USB key</xlfQA:qaitem>
</unit>

It's a bit sad to have to use a namespace and structure that's not 'natively' ITS.

But there is something worst:

This means we would have to define global rules to allow ITS processor to map such data back to the qaError data category. Maybe that is something we were planning to have anyway? But I haven't seen it in any example so far.

Cheers,
-ys

Received on Wednesday, 11 July 2012 12:09:40 UTC