[ACTION-320]: Localization Quality Précis Retain in Spec.

All

Arle and I spoke this morning.

VistaTEC definitely sees a requirement for Localisation Quality Précis - 
that is, a data category to contain document level, quality related 
metadata. The locQualityIssue metadata has much more meaning when it is 
referenced back to an overall score and pass/fail threshold and optionally 
point to other non-normative information (contained in the rating).

There is a current proposal for a change of name to "Localization Quality 
Rating" at 
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Nov/0151.html
. I have no objection to this.

Implementations: VistaTEC would be an implementer of this category. Arle 
thinks that he could provide a second implementation but cannot commit to 
having it ready until March 2013.

Later today/tomorrow I will revise section 8.18 to reflect the naming 
change and amend the description and post back to the group.

The only questions I have having re-read the Loc. Quality sections are 
about capturing the "agent" and "tool". Given that the Translation Agent 
Provenance data category can be used freely in combination with 
Localization Quality Issue and Localization Quality Rating then I see no 
problem with the former and if we have a data category independent 
mechanism for "tool" then I'm happy there also. Given these two 
assumptions I see no need to change any of the Localization Quality Rating 
attributes.

Jirka, is this enough information that you can proceed with the schema's?

Phil.


************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail.

www.vistatec.com
************************************************************