RE: Tool info specification (Re: action-221 summary of overriding discussion)

Hi Jirka, Felix, all,

> But it is really necessary to have such fidelity about tools used?
> Is there some use-case for annotating each piece of ITS markup 
> with a tool info? Wouldn't it be just sufficient to list tools used,
> maybe with some flag saying which data categories has been touched
> by each tool.

There are use cases where annotation of the same data category is done by different tools.
For example:

<xliff version="1.2"
 xmlns="urn:oasis:names:tc:xliff:document:1.2" 
 xmlns:its="http://www.w3.org/2005/11/its">
<file original="/Example-XML.xml" source-language="en"
 target-language="fr" datatype="xml">
<body>
<trans-unit id="1">
 <source xml:lang="en-us">This is the text of the message.</source>
 <alt-trans match-quality="100">
  <target xml:lang="fr-fr" its:mtConfidenceScore="98.67">Ceci est le texte du message.</target>
 </alt-trans>
 <alt-trans match-quality="100" its:mtConfidenceScore="0.9876">
  <target xml:lang="fr-fr">C'est le texte du message.</target>
 </alt-trans>
</trans-unit>
</file>
</xliff>

The two translation proposals are from different engines.

- A reference to the tool at the document level will not work.
- A global reference to tool that generated the annotation for the MT Confidence data category will not work either.

As far as can see, the only way to properly associate the score with the tool that generated it is with something that goes along with the score itself.

But at the same time, we'd want also cater for Declan and Tadej's use cases that don't require to repeat over and over such link information.

Hence, the discussion about the list of IDs for Felix's proposal.


I think Felix' proposal may be close to a solution, but it seems to me that making the ITS Tool Information thing a data category itself is the problem, because we're then bound to all the same issues and restrictions we have with data categories.

Maybe the link between the tool information and the instance of the data category could be done by something which would not be part of a data category? Some lone attribute that could be use anywhere.

I also think the information such link needs to carry is both the ID of the tool description element but also an identifier of the data category targeted, otherwise we can't resolve the multi-tools/same data category use case.


I'll think on it in the long flight to the City of Hundred Spires
-yves

Received on Saturday, 22 September 2012 20:31:32 UTC