- From: Yves Savourel via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 21 Aug 2012 22:42:19 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv11835
Modified Files:
its20.html its20.odd
Log Message:
Continued implementing loc quality.
Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.120
retrieving revision 1.121
diff -u -d -r1.120 -r1.121
--- its20.odd 21 Aug 2012 20:28:22 -0000 1.120
+++ its20.odd 21 Aug 2012 22:42:17 -0000 1.121
@@ -4306,7 +4306,7 @@
<row>
<cell>Type</cell>
<cell>A set of broad types of issues into which tool-specific issues can be categorized.</cell>
- <cell>One of the values defined in list of type values.</cell>
+ <cell>One of the values defined in <ref target="#lqissue-typevalues">list of type values</ref>.</cell>
<cell>ITS 2.0-compliant tools that use these categories <ref target="#rfc-keywords">MUST</ref>
map their internal values to these types.
If the type of the issue is set to <code>uncategorized</code>, a comment <ref target="#rfc-keywords">MUST</ref>
@@ -4444,11 +4444,72 @@
and <att>locQualityIssueProfileRef</att> (or their equivalent representations) are used in in a standoff manner, the information
they carry pertains to the content of the element that refers to the standoff annotation, not to the content of the element
<gi>locQualityIssue</gi> (or <code><span loc-quality-issue></code>in HTML) where they are declared.</p>
-
<exemplum xml:id="EX-locQualityNote-local-1">
<head>TODO</head>
<p>TODO</p>
</exemplum>
+
+ <p xml:id="lqissue-typevalues">Values for the Localization Quality Issue Type:</p>
+ <p>The <att>locQualityIssueType</att> attribute provides a basic level of interoperability between different localization quality
+ assurance systems. It offers a list of high-level quality issue types common in automatic and human localization quality assessment.
+ Tools can map their internal categories to these categories in order to exchange information about the kinds of issues they
+ identify and take appropriate action even if another tool does not know the specific issues identified by the generating tool.</p>
+ <p>The values listed in the following table are allowed for <att>locQualityIssueType</att>. The values a tool implementing the data category
+ produces for the attribute <ref target="#rfc-keywords">MUST</ref> match one of the values provided in this table and
+ <ref target="#rfc-keywords">MUST</ref> be semantically accurate. If a tool can map its internal values to these categories it
+ <ref target="#rfc-keywords">MUST</ref> do so and <ref target="#rfc-keywords">MUST NOT</ref> use the value <code>other</code>,
+ which is reserved strictly for values that cannot be mapped to these values.</p>
+ <table border="1">
+ <row role="head">
+ <cell>Value</cell>
+ <cell>Description</cell>
+ <cell>Example</cell>
+ <cell>Scope</cell>
+ <cell>Notes</cell>
+ </row>
+ <row>
+ <cell><code>terminology</code></cell>
+ <cell>An incorrect term or a term from the wrong domain was used or terms are used inconsistently.</cell>
+ <cell><list>
+ <item>The localization had “Pen Drive” when corporate terminology specified that “USB Stick” was to be used.</item>
+ <item>The localization text inconsistently used "Start" and "Begin".</item>
+ </list></cell>
+ <cell>S+T</cell>
+ <cell></cell>
+ </row>
+ <row>
+ <cell><code>mistranslation</code></cell>
+ <cell>The content of the target mistranslates the content of the source.</cell>
+ <cell><list>
+ <item>The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick"
+ but the Italian translation reads "l'ape riuscì a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone"
+ ("A bee succeeded...")</item>
+ </list></cell>
+ <cell>T</cell>
+ <cell>Issues related to translation of specific terms related to the domain or task-specific language should be categorized as
+ <code>terminology</code> issues.</cell>
+ </row>
+ <row>
+ <cell><code>omission</code></cell>
+ <cell>Necessary text has been omitted from the localization or source.</cell>
+ <cell><list>
+ <item>One or more segments found in the source that should have been translated are missing in the target.</item>
+ </list></cell>
+ <cell>S+T</cell>
+ <cell>This type should not be used for missing whitespace or formatting codes, but instead should be reserved
+ for linguistic content.</cell>
+ </row>
+ <row>
+ <cell><code></code></cell>
+ <cell></cell>
+ <cell><list>
+ <item></item>
+ <item></item>
+ </list></cell>
+ <cell></cell>
+ <cell></cell>
+ </row>
+ </table>
</div>
<div xml:id="lqissue-markup">
<head>Markup Declarations for Localization Quality Issue</head>
Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.120
retrieving revision 1.121
diff -u -d -r1.120 -r1.121
--- its20.html 21 Aug 2012 20:28:22 -0000 1.120
+++ its20.html 21 Aug 2012 22:42:16 -0000 1.121
@@ -2312,7 +2312,7 @@
HTML preview of an XML file along with CSS styling that highlights these issues. The resulting HTML
file is then sent back to the translator to assist his or her revision efforts.</p></li><li><p>A human reviewer working with a web-based tool adds quality markup, including comments and
suggestions, to a localized text as part of the review process. A subsequent process examines this
- markup to ensure that changes were made.</p></li></ul><p>The data category defines four pieces of information:</p><span class="editor-note">[Ed. note: TODO: Table]</span><a name="lqissueDefs" id="lqissueDefs" shape="rect"/><table border="1"><thead><tr><td rowspan="1" colspan="1">Information</td><td rowspan="1" colspan="1">Description</td><td rowspan="1" colspan="1">Value</td><td rowspan="1" colspan="1">Notes</td></tr></thead><tbody><tr><td rowspan="1" colspan="1">Type</td><td rowspan="1" colspan="1">A set of broad types of issues into which tool-specific issues can be categorized.</td><td rowspan="1" colspan="1">One of the values defined in list of type values.</td><td rowspan="1" colspan="1">ITS 2.0-compliant tools that use these categories <a href="#rfc-keywords" shape="rect">MUST</a>
+ markup to ensure that changes were made.</p></li></ul><p>The data category defines four pieces of information:</p><span class="editor-note">[Ed. note: TODO: Table]</span><a name="lqissueDefs" id="lqissueDefs" shape="rect"/><table border="1"><thead><tr><td rowspan="1" colspan="1">Information</td><td rowspan="1" colspan="1">Description</td><td rowspan="1" colspan="1">Value</td><td rowspan="1" colspan="1">Notes</td></tr></thead><tbody><tr><td rowspan="1" colspan="1">Type</td><td rowspan="1" colspan="1">A set of broad types of issues into which tool-specific issues can be categorized.</td><td rowspan="1" colspan="1">One of the values defined in <a href="#lqissue-typevalues" shape="rect">list of type values</a>.</td><td rowspan="1" colspan="1">ITS 2.0-compliant tools that use these categories <a href="#rfc-keywords" shape="rect">MUST</a>
map their internal values to these types.
If the type of the issue is set to <code>uncategorized</code>, a comment <a href="#rfc-keywords" shape="rect">MUST</a>
be specified as well.</td></tr><tr><td rowspan="1" colspan="1">Comment</td><td rowspan="1" colspan="1">A human-readable description of the quality issue.</td><td rowspan="1" colspan="1">Text</td><td rowspan="1" colspan="1"/></tr><tr><td rowspan="1" colspan="1">Severity</td><td rowspan="1" colspan="1">An decimal value representing the severity of the issue, as defined by the model generating the metadata.</td><td rowspan="1" colspan="1">A decimal between 0.0 to 100.0 (included), with higher values indicating greater severity.</td><td rowspan="1" colspan="1">It is up to tools to map the values of this to their own system to this scale. If needed, the
@@ -2343,7 +2343,34 @@
<a href="#lqissueDefs" shape="rect">profile reference information</a>.</p></li></ul></li></ul></li></ul></li></ul><p>Important: When the attributes <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a>, <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueComment</a>, <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueSeverity</a>
and <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueProfileRef</a> (or their equivalent representations) are used in in a standoff manner, the information
they carry pertains to the content of the element that refers to the standoff annotation, not to the content of the element
- <a class="itsmarkup" href="#locQualityIssue" shape="rect">locQualityIssue</a> (or <code><span loc-quality-issue></code>in HTML) where they are declared.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityNote-local-1" id="EX-locQualityNote-local-1" shape="rect"/>Example 68: TODO</div><p>TODO</p></div></div><div class="div3">
+ <a class="itsmarkup" href="#locQualityIssue" shape="rect">locQualityIssue</a> (or <code><span loc-quality-issue></code>in HTML) where they are declared.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityNote-local-1" id="EX-locQualityNote-local-1" shape="rect"/>Example 68: TODO</div><p>TODO</p></div><p id="lqissue-typevalues">Values for the Localization Quality Issue Type:</p><p>The <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a> attribute provides a basic level of interoperability between different localization quality
+ assurance systems. It offers a list of high-level quality issue types common in automatic and human localization quality assessment.
+ Tools can map their internal categories to these categories in order to exchange information about the kinds of issues they
+ identify and take appropriate action even if another tool does not know the specific issues identified by the generating tool.</p><p>The values listed in the following table are allowed for <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a>. The values a tool implementing the data category
+ produces for the attribute <a href="#rfc-keywords" shape="rect">MUST</a> match one of the values provided in this table and
+ <a href="#rfc-keywords" shape="rect">MUST</a> be semantically accurate. If a tool can map its internal values to these categories it
+ <a href="#rfc-keywords" shape="rect">MUST</a> do so and <a href="#rfc-keywords" shape="rect">MUST NOT</a> use the value <code>other</code>,
+ which is reserved strictly for values that cannot be mapped to these values.</p><table border="1"><thead><tr><td rowspan="1" colspan="1">Value</td><td rowspan="1" colspan="1">Description</td><td rowspan="1" colspan="1">Example</td><td rowspan="1" colspan="1">Scope</td><td rowspan="1" colspan="1">Notes</td></tr></thead><tbody><tr><td rowspan="1" colspan="1">
+ <code>terminology</code>
+ </td><td rowspan="1" colspan="1">An incorrect term or a term from the wrong domain was used or terms are used inconsistently.</td><td rowspan="1" colspan="1">
+ <ul><li><p>The localization had “Pen Drive” when corporate terminology specified that “USB Stick” was to be used.</p></li><li><p>The localization text inconsistently used "Start" and "Begin".</p></li></ul>
+ </td><td rowspan="1" colspan="1">S+T</td><td rowspan="1" colspan="1"/></tr><tr><td rowspan="1" colspan="1">
+ <code>mistranslation</code>
+ </td><td rowspan="1" colspan="1">The content of the target mistranslates the content of the source.</td><td rowspan="1" colspan="1">
+ <ul><li><p>The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick"
+ but the Italian translation reads "l'ape riuscì a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone"
+ ("A bee succeeded...")</p></li></ul>
+ </td><td rowspan="1" colspan="1">T</td><td rowspan="1" colspan="1">Issues related to translation of specific terms related to the domain or task-specific language should be categorized as
+ <code>terminology</code> issues.</td></tr><tr><td rowspan="1" colspan="1">
+ <code>omission</code>
+ </td><td rowspan="1" colspan="1">Necessary text has been omitted from the localization or source.</td><td rowspan="1" colspan="1">
+ <ul><li><p>One or more segments found in the source that should have been translated are missing in the target.</p></li></ul>
+ </td><td rowspan="1" colspan="1">S+T</td><td rowspan="1" colspan="1">This type should not be used for missing whitespace or formatting codes, but instead should be reserved
+ for linguistic content.</td></tr><tr><td rowspan="1" colspan="1">
+ <code/>
+ </td><td rowspan="1" colspan="1"/><td rowspan="1" colspan="1">
+ <ul><li><p/></li><li><p/></li></ul>
+ </td><td rowspan="1" colspan="1"/><td rowspan="1" colspan="1"/></tr></tbody></table></div><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="lqissue-markup" id="lqissue-markup" shape="rect"/>6.18.3 Markup Declarations for Localization Quality Issue</h4><dl><dt class="label">locQualityIssueRule</dt><dd><table class="scrap" summary="Scrap"><tbody><tr valign="baseline"><td rowspan="1" colspan="1"><a name="locQualityIssueRule" id="locQualityIssueRule" shape="rect"/>[139] </td><td rowspan="1" colspan="1"><code>locQualityIssueRule</code></td><td rowspan="1" colspan="1"> ::= </td><td rowspan="1" colspan="1"><code>
element its:locQualityIssueRule
{
@@ -2636,7 +2663,7 @@
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="its-schematron-constraints" id="its-schematron-constraints" shape="rect"/>E Checking ITS Markup Constraints With Schematron (Non-Normative)</h2><p>
<em>This section is informative.</em>
</p><p>Several constraints of ITS markup cannot be validated with ITS schemas. The following <a title="Rule-based validation -- Schematron" href="#schematron" shape="rect">[Schematron]</a> document allows for validating some of these
- constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8315" id="d3e8315" shape="rect"/>Example 69: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
+ constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8439" id="d3e8439" shape="rect"/>Example 69: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
<sch:schema
xmlns:sch="http://www.ascc.net/xml/schematron" >
<!-- Schematron document to test constraints for global and local ITS markup.
@@ -2703,7 +2730,7 @@
<em>This section is informative.</em>
</p><p>The following <a title="Namespace-based Validation Dispatching Language (NVDL)" href="#nvdl" shape="rect">[NVDL]</a> document allows validation of ITS markup which has
been added to a host vocabulary. Only ITS elements and attributes are checked. Elements and
- attributes of host language are ignored during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8337" id="d3e8337" shape="rect"/>Example 70: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve"><rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"> <namespace
+ attributes of host language are ignored during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8461" id="d3e8461" shape="rect"/>Example 70: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve"><rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"> <namespace
ns="http://www.w3.org/2005/11/its"> <validate schema="its-elements.rng"/>
</namespace> <namespace ns="http://www.w3.org/2005/11/its" match="attributes">
<validate schema="its-attributes.rng"/> </namespace> <anyNamespace>
Received on Tuesday, 21 August 2012 22:42:21 UTC