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

Re: [ACTION-256]: Compile and circulate itsTool examples togehter with proposal text

From: Dave Lewis <dave.lewis@cs.tcd.ie>
Date: Tue, 06 Nov 2012 15:44:42 +0000
Message-ID: <5099306A.6040007@cs.tcd.ie>
To: Yves Savourel <ysavourel@enlaso.com>
CC: public-multilingualweb-lt@w3.org
hi Yves,

On 05/11/2012 15:29, Yves Savourel wrote:
> --1) It seems we still have the data category defined in toolsRef. So technically is it necessary to declare it in <toolInfo>? I suppose having it there allows to know what the data is about without looking at the toolsRef attribute. But it's also duplicated data and could possibly (but improbably) end up with different values.

It is redundant as a toolInfo attribute. not sure ifits useful, but if 
we keep it we need to add a note that the binding in the ITS:toolRefs 
take precendence if they are different

>
> --2) I would name toolName, toolVersion and toolInfo just name, version and info: they are always inside <toolInfo> so can't be mis-interpreted.--3) How would we use <processInfo> in HTML5. We can't really embed that in <script> because the reference is to <toolInfo> not a single ID we could place in ,script> as well (unlike the stand-off annotation).
Seem reasonable, but note we aren't proposing this schema as a normative 
feature, just as an exmaple. We could make that more concrete as best 
practice, but yes lets makes the example as sensible as possible in the 
spec.

--3) How would we use <processInfo> in HTML5. We can't really embed that in <script> because the reference is to <toolInfo> not a single ID we could place in ,script> as well (unlike the stand-off annotation).

You are right that as we have multiple ID (per toolInfo element) we want 
to refer to in the <script> we can't use the same solution as we 
discussed in the tc on monday.

Two option occur to me:
a) enforce that each toolInfo element is  in a different script, with 
the script id reflecting the toolInfo element id

b) [a hack] , allow multiple toolInfo elements in a single processInfo 
element in a script and make the script xml:id be the line separated 
concatenation of all the toolInfo elements in the script, i.e.:

<script id="T3|T4|T5" type=application/xml>
<its:processInfo>

   <its:toolInfo xml:id="T3" dataCategory="MTConfidence">
   <its:toolName>Bing Translator</its:toolName>
   <its:toolValue>en-t-cs</its:toolValue>
  </its:toolInfo>
<its:toolInfo xml:id="T4" dataCategory="MTConfidence">
   <its:toolName>vanilla Moses</its:toolName>
   <its:toolValue>medical:EN-ES_LA</its:toolValue>
  </its:toolInfo>
<its:toolInfo>
<its:toolInfo xml:id="T5" dataCategory="Text Analysis Confidence">
   <its:toolName> http://enrycher.ijs.si </its:toolName>
  </its:toolInfo>
</its:processInfo>
</script>

any thoughts?
cheers,
Dave
Received on Tuesday, 6 November 2012 15:39:55 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:25:03 UTC