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

RE: [ISSUE-42] Wording for the tool information markup

From: Yves Savourel <ysavourel@enlaso.com>
Date: Wed, 3 Oct 2012 07:50:47 -0600
To: <public-multilingualweb-lt@w3.org>
Message-ID: <assp.0623e82bc6.assp.0623d84d2c.007e01cda16e$17cd56e0$476804a0$@com>
> Could we get away with simply toolRefs, with the URI pointing 
> to some non-ITS resource or being just an identifier?

Let me expend on this:

It seems all data categories that could use a common way to refer to a tool do not have additional ITS-specific information at the local level related to the tool, except for mtConfidence.

For example (for new still using / as the separator):

<span its:textAnalysisScore="11" its:toolRefs="textAnalysis/http://enrycher.ijs.si/">text</span>

<doc its:locQualityPrecisScore="22" its:toolRefs="locQualityPrecis/http://example.org/qaModel/v13">...</doc>

<span its:locQualityIssueType="grammar" its:toolrefs="locQualityIssue/http://example.org/qaMovel/v1">...<span>

So the only one left seems to be mtConfidence. But maybe the URI could be the engine identifier:

<span its:mtConfidenceScore="33" its:toolRefs="mtConfidence/https://hub.microsofttranslator.com/user/en-t-fr">...</span>

I realize putting two information (the tool identifier and the engine identifier) in a single URI may not be easy in this last case, and may lead to non-browsable URI, but it may be simpler than trying to come up with a complex toolInfo element.

Just a thought.
-yves
Received on Wednesday, 3 October 2012 13:51:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:55 UTC