- From: Arle Lommel <arle.lommel@dfki.de>
- Date: Mon, 1 Jul 2013 13:53:23 +0200
- To: David Lewis <dave.lewis@cs.tcd.ie>, Christian Lieske <christian.lieske@sap.com>, "public-i18n-its-ig@w3.org" <public-i18n-its-ig@w3.org>, Aljoscha Burchardt <aljoscha.burchardt@dfki.de>
- Message-Id: <744EF883-BE9B-4485-975D-D8DAFE07396F@dfki.de>
Hi all,
In discussion with Felix today about using the profileRef as a mechanism for pointing to the MQM issue types in ITS 2.0, I found that one of his objections (he may have others, but we didn't get to discuss in details), was that we don't have defined what is on the other end of that Ref, so it isn't clear how one is to interpret that. He felt that it was simply to vague. From this conversation it became apparent that I had neglected to state one core assumption on my part: an MQM profile would be well-defined in a machine-readable format. It wouldn't be a prose description or something else unintelligible.
As an example, I'm including a snapshot from an internal development document that shows an XML profile for the ITS 2.0 types cast as MQM issue types. It needs some work, but this shows something of what might be on the other end as a profile.
Felix, would knowing that something *like* this (I know it needs some work) is on the other end for MQM resolve your concern, or do you have other issues with using the profileRef for that purpose?
Best,
-Arle
<?xml version="1.0" encoding="UTF-8"?>
<mqm xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="file:/Users/fenevad/Dropbox/dfki/qt-launchpad/schemas/mqmMetric.xsd">
<head>
<mqmversion>2.0</mqmversion>
<metricname>Sample metric</metricname>
</head>
<issues>
<issue type="Accuracy" active="no" weight="0">
<issue type="Terminology" displayname="terminology" active="yes" weight="1.0"/>
<issue type="Mistranslation" displayname="mistranslation" active="yes" weight="1.0">
<issue type="Number" displayname="numbers" weight="1.0"/>
<issue type="Entity (such as name or place)" displayname="inconsistent-entities"
weight="1.0"/>
</issue>
<issue type="Omission" displayname="omission" weight="1.0"/>
<issue type="Addition" displayname="addition" weight="1.0"/>
<issue type="Untranslated" displayname="untranslated" weight="1.0"/>
</issue>
<issue type="Design" displayname="formatting" weight="1.0">
<issue type="Markup" displayname="markup" weight="1.0"/>
<issue type="Whitespace" displayname="whitespace" weight="1.0"/>
<issue type="Length" displayname="length" weight="1.0"/>
</issue>
<issue type="Internationalization" displayname="internationalization" weight="1.0"/>
<issue type="Other" displayname="other" weight="1.0"/>
<issue type="Fluency" active="no" weight="0">
<issue type="Content" active="no" weight="0">
<issue type="Register" displayname="register" weight="1.0"/>
<issue type="Style" displayname="style" weight="1.0"/>
<issue type="Inconsistency" displayname="inconsistency" weight="1.0"/>
<issue type="Duplication" displayname="duplication" weight="1.0"/>
</issue>
<issue type="Mechanical" active="no" weight="0">
<issue type="Spelling" displayname="misspelling" weight="1.0"/>
<issue type="Typography" displayname="typographical" weight="1.0"/>
<issue type="Grammar" displayname="grammar" weight="1.0"/>
<issue type="Locale violation" displayname="locale-violation" weight="1.0"/>
<issue type="Nonallowed characters" displayname="characters" weight="1.0"/>
<issue type="Pattern problem" displayname="pattern-problem" weight="1.0"/>
<issue type="Corpus conformance" displayname="non-conformance" weight="1.0"/>
</issue>
<issue type="Unintelligible" displayname="uncategorized" weight="1.0"/>
</issue>
<issue type="Verity" active="no" weight="0">
<issue type="Legal requirements" displayname="legal" weight="1.0"/>
<issue type="Locale applicability" displayname="locale-specific-content" weight="1.0"/>
</issue>
</issues>
</mqm>
Received on Monday, 1 July 2013 11:53:54 UTC