OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (XLIFF-8) mtc:matchQuality cannot be interpreted as ITS MT confidence by ITS processors


    [ https://issues.oasis-open.org/browse/XLIFF-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66200#comment-66200 ] 

David Filip commented on XLIFF-8:
---------------------------------

This has been reopened because of a new finding by Yves
http://markmail.org/thread/6kvjlbuuo3vczkfe

It seems to me the relationship between the 3 attributes matchQuality, its:locQualityRatingScore and its:mtConfidence is a bit confusing.
 
-     According the specification both matchQuality can be used to represent its:locQualityRatingScore and its:mtConfidence.
One question that comes to mind is: What if you have both data categories set for a given <mtc:match>? How can matchQuality takes both values? (maybe the answer the third bullet?).
 
-     There is a “[WIP]” marker (Work In Progress” I assume) that is at the end of this paragraph:
“The attribute locQualityRatingScore MUST NOT be used on <mtc:match>, where it maps to and from mtc:matchQuality unless in scope of mt-confidence annotatorRef [WIP].”
 
-     I’m not sure I understand the constraint above: It seems to say matchQuality maps to mtConfidence if it’s within the scope of an annotatorRef for mt-confidence (and then we have to use locQualityRatingScore for locQualityRatingScore), otherwise matchQuality maps to locQualityRatingScore. Is that correct?
If so, it seems a recipe for a lot of problems: Some implementations may not support both MT Confidence and Localization Quality Scope.
I’m also not quite sure why two different ITS data categories values can map to the same XLIFF value: Is that means mtConfidence and locQualityRatingScore represent the same thing in ITS?

> mtc:matchQuality cannot be interpreted as ITS MT confidence by ITS processors 
> ------------------------------------------------------------------------------
>
>                 Key: XLIFF-8
>                 URL: https://issues.oasis-open.org/browse/XLIFF-8
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Sub-task
>          Components: ITS Module
>    Affects Versions: 2.1_csprd01
>         Environment: https://lists.oasis-open.org/archives/xliff-comment/201610/msg00019.html
>            Reporter: Yves Savourel
>            Assignee: David Filip
>              Labels: ready-for-vote
>             Fix For: 2.1_csprd02
>
>
> I'm not sure how we can say that MT Confidence is supported in XLIFF:
> The ITS specification does not have global pointer for that data category in ITS.
> Isn't this a case similar to Localization Note where we can easily transfer the data into XLIFF, but technically, a ITS processor
> cannot get the same result?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]