- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Thu, 05 Sep 2013 15:47:59 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv13675
Modified Files:
its20.html its20.odd
Log Message:
implemented lqi edits, see attachment at http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Sep/0017.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/09/05 15:08:16 1.490
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/09/05 15:47:58 1.491
@@ -2602,35 +2602,14 @@
<h3><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" id="lqissue" shape="rect"/>8.16 Localization Quality Issue</h3><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-definition" id="lqissue-definition" shape="rect"/>8.16.1 Definition</h4><p>The <a href="#lqissue" shape="rect">Localization Quality Issue</a> data category is used to
express information related to localization quality assessment tasks. Such tasks can
- be conducted on the translation of some source text into a target language or on the
- source text itself where its quality may impact on the localization process.</p><p>This data category can be used in a number of ways, including the following example
- scenarios:</p><ul><li><p>An automatic quality checking tool flags a number of potential quality issues
- in an XML or HTML file and marks them up using ITS 2.0 markup. Other tools in the
- workflow then examine this markup and decide whether the file needs to be reviewed
- manually or passed on for further processing without a manual review
- stage.</p></li><li><p>A quality assessment process identifies a number of issues and adds the ITS
- markup to a rendered 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><div class="note"><p class="prefix"><b>Note:</b></p><p id="selecting-issues">What issues are considered in quality
- assessment tasks depends on the nature of the project and tools used. For more
- information on setting translation project specifications and determining quality
- expectations, implementers are encouraged to consult <a title="Translation projects – General guidance" href="#isots11669" shape="rect">[ISO/TS 11669:2002]</a>. Details about translation specifications are available at <a title="Structured Specifications and Translation Parameters" href="#structuredspecs" shape="rect">[Structured Specifications]</a>. While these documents do not directly
- address the definition of quality metrics, they provide useful guidance for
- implementers interested in determining which localization quality issue values
- are best for specific scenarios.</p></div><p>The data category defines five pieces of information:</p><a name="lqissueDefs" id="lqissueDefs" shape="rect"/><table border="1" width="100%"><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
+ be conducted on the translation of some source content (such as a text or an image) into a target language or on the
+ source content itself where its quality may impact on the localization process.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Automated or manual quality assessment is one area of quality management for translational and localization. An example of existing quality assessment is in-country review (e.g., as part of a language acceptance test for software). An important part of quality assessment is the list of issue types that are being used. Very often, simple issue categories like "correct/incorrect" or "like/dislike" are inadequate; instead, more specific ones such as "terminology" or "grammar" are more helpful in identifying concrete reasons for quality problems and for obtaining a more objective picture of quality levels.</p><p>Non-normative terminology related to localization quality as used in this section is provided in Appendix @@@TBD@@@.</p></div><p>This data category can be used in a number of ways, including the following example
+ scenarios:</p><ul><li><p>A human reviewer working with a web-based tool adds quality markup manually in a text editor, including comments and suggestions, to localized content as part of the review process. A subsequent process examines this markup to ensure that changes were made.</p></li><li><p>A fully automatic quality checking tool flags a number of potential quality issues in an XML or HTML file and marks them up using ITS 2.0 markup. A human reviewer then uses another tool to examine this markup and decide whether the file needs to receive more extensive review or be passed on for further processing without a further manual review stage.</p></li><li><p>A quality assessment process identifies a number of issues and adds the ITS markup to a rendered 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></ul><div class="note"><p class="prefix"><b>Note:</b></><p id="selecting-issues">What issues should be considered in quality assessment tasks depends on the nature of the project and tools used. Further guidance is beyond the scope of this specification, but implementers may wish to consult the references cited in Appendix @@@TBD@@@.</p></div><p>The data category defines five pieces of information:</p><a name="lqissueDefs" id="lqissueDefs" shape="rect"/><table border="1" width="100%"><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 classifier that groups similar issues into categories (for example to differentiate spelling errors from grammar errors).</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 types <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">A decimal value representing the severity of the issue, as defined by the
- model generating the metadata.</td><td rowspan="1" colspan="1">A rational number in the interval 0 to 100 (inclusive). The value follows the
+ 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 a specific instance of a quality issue.</td><td rowspan="1" colspan="1">Text</td><td rowspan="1" colspan="1">Comments can be used to explain an issue or provide guidance in addressing an issue. For example, a note about a Terminology issue might specify what term should be used.</td></tr><tr><td rowspan="1" colspan="1">Severity</td><td rowspan="1" colspan="1">A classifier for the seriousness of an issue. The seriousness depends on the Quality Model that is being applied. The Quality Model should be made explicit via the Profile Reference.</td><td rowspan="1" colspan="1">A rational number in the interval 0 to 100 (inclusive). The value follows the
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double" shape="rect">XML
Schema double data type</a> with the constraining facets <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#rf-minInclusive" shape="rect">minInclusive</a> set to 0 and <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#rf-maxInclusive" shape="rect">maxInclusive</a> set to 100. The higher values represent 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 original value can be passed along using a custom namespace for
- XML, or a <code>data-</code> attribute for HTML.</td></tr><tr><td rowspan="1" colspan="1">Profile Reference</td><td rowspan="1" colspan="1">A reference to a document describing the quality assessment model used for the
- issue.</td><td rowspan="1" colspan="1">An IRI pointing to the reference document.</td><td rowspan="1" colspan="1">The use of resolvable IRI is strongly recommended as it provides a way for
+ severity.</td><td rowspan="1" colspan="1">It is up to tools to map the values allowed by ITS 2.0 to their own system’s scale. If needed, the original value can be passed along using a custom namespace for XML, or a <code>data-</code> attribute for HTML.</td></tr><tr><td rowspan="1" colspan="1">Profile Reference</td><td rowspan="1" colspan="1">A reference to a description of the quality assessment model (or a specific profile (customization/instantiation) of a model, where relevant) used for the issue.</td><td rowspan="1" colspan="1">An IRI pointing to the reference document.</td><td rowspan="1" colspan="1">The use of resolvable IRIs is strongly recommended as it provides a way for
human evaluators to learn more about the quality issues in use.</td></tr><tr><td rowspan="1" colspan="1">Enabled</td><td rowspan="1" colspan="1">A flag indicating whether the issue is enabled or not.</td><td rowspan="1" colspan="1">A value <code>yes</code> or <code>no</code>, with the default value being
<code>yes</code>.</td><td rowspan="1" colspan="1">This flag is used to activate or deactivate issues. There is no prescribed
behavior associated with activated or deactivated issues. One example of usage is
@@ -3232,16 +3211,15 @@
<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="lqissue-typevalues" id="lqissue-typevalues" shape="rect"/>C Values for the Localization Quality Issue Type</h2><p>
<em>This section is normative.</em>
</p><p>The <code class="its-attr-markup">locQualityIssueType</code> 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
+ between different localization quality assurance tools. It offers a list of high-level
+ quality issue types common in fully automatic and manual localization quality assessment. Tools
can map their internal types to these types 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 scope column in the following table identifies whether the issue type applies to the
- source text (“S”), target text (“T”) or both (“S or T”).</p><p>The values listed in the following table are allowed for <code class="its-attr-markup">locQualityIssueType</code>.
+ know the specific issues identified by the generating tool.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Note: The values of locQualityIssueType were derived from an early version of the QTLaunchPad project's Multidimensional Quality Metrics (MQM) framework. MQM is based on a careful analysis of existing translation quality assessment tools and models, such as the LISA QA Model, SAE J2450 @@@tbd - add reference?@@@, and various commercial tools. The values represent common issue types found in those models and are designed to provide interoperability between models. Differences in granularity and in issue types may prevent full interoperability, but using the shared values will maximize interoperability where possible.</p></div><p>The scope column in the following table identifies whether the issue type applies to the
+ source content (“S”), target content (“T”) or both (“S or T”).</p><p>The values listed in the following table are allowed for <code class="its-attr-markup">locQualityIssueType</code>.
Ideally the values a tool implementing the data category produces for the attribute matches one
- of the values provided in this table and are as semantically accurate as possible. Tools are encouraged to
- map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-mappings">The <a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> maintains an
- <a href="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings" shape="rect">informative mapping</a> between ITS 2.0 quality issue types and other types used to specify quality issues: types produced by quality check tools, defined in other specifications etc. The purpose of these mappings is to document how tool internal information relates to the ITS 2.0 quality types. To foster interoperability, implementers are strongly encouraged not to rely on these mappings and to implement the ITS 2.0 quality types natively.</p></div><a name="lqissue-typevalues-table" id="lqissue-typevalues-table" shape="rect"/><table border="1" width="100%"><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">
+ of the values provided in this table and are as semantically accurate as possible. For example, marking the phrase “These man is” as a <code>terminology</code> issue, rather than as a <code>grammar</code> issue would be semantically inaccurate. Tools are encouraged to
+ map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>For tools <em>generating</em> ITS 2.0 Localization Quality Issue markup, if one internal issue type can be categorized as multiple ITS 2.0 issue types, <em>the first applicable one from the following table should be used</em>. The list is ordered with more specific types first. For example, if a terminology database specifies that the term “USB memory stick” should be used instead of “USB pen drive” but the translated content has “Insert a USB pen drive into any available USB port”, <code>terminology</code> would be used instead of <code>mistranslation</code> because <code>terminology</code> occurs earlier in the list and is more specific than a (general) <code>mistranslation</code>. In the case where multiple separate issues must be marked on a single span (e.g., it contains both a <code>mistranslation<code> and a <code>grammar</code> issue), implementers may wish to use standoff annotation, as shown in <a href="#EX-locQualityIssue-local-2" shape="rect">Example 75</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 76</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-mappings">The <a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> maintains informative <a href="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings" shape="rect">mappings of tool-specific quality issue types and ITS 2.0 localization quality types</a>. The ITS IG Wiki provides information on how to update that list. The purpose of these mappings is to document how tool internal information relates to the ITS 2.0 quality types. To foster interoperability, implementers are strongly encouraged to implement the ITS 2.0 quality types natively.</p></div><a name="lqissue-typevalues-table" id="lqissue-typevalues-table" shape="rect"/><able border="1" width="100%"><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">
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/09/05 15:08:17 1.505
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/09/05 15:47:59 1.506
@@ -3926,34 +3926,20 @@
<head>Definition</head>
<p>The <ref target="#lqissue">Localization Quality Issue</ref> data category is used to
express information related to localization quality assessment tasks. Such tasks can
- be conducted on the translation of some source text into a target language or on the
- source text itself where its quality may impact on the localization process.</p>
+ be conducted on the translation of some source content (such as a text or an image) into a target language or on the
+ source content itself where its quality may impact on the localization process.</p>
+ <note>
+ <p>Automated or manual quality assessment is one area of quality management for translational and localization. An example of existing quality assessment is in-country review (e.g., as part of a language acceptance test for software). An important part of quality assessment is the list of issue types that are being used. Very often, simple issue categories like "correct/incorrect" or "like/dislike" are inadequate; instead, more specific ones such as "terminology" or "grammar" are more helpful in identifying concrete reasons for quality problems and for obtaining a more objective picture of quality levels.</p>
+ <p>Non-normative terminology related to localization quality as used in this section is provided in Appendix @@@TBD@@@.</p>
+ </note>
<p>This data category can be used in a number of ways, including the following example
scenarios:</p>
<list type="unordered">
- <item><p>An automatic quality checking tool flags a number of potential quality issues
- in an XML or HTML file and marks them up using ITS 2.0 markup. Other tools in the
- workflow then examine this markup and decide whether the file needs to be reviewed
- manually or passed on for further processing without a manual review
- stage.</p></item>
- <item><p>A quality assessment process identifies a number of issues and adds the ITS
- markup to a rendered 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></item>
- <item><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></item>
- </list>
- <note><p xml:id="selecting-issues">What issues are considered in quality
- assessment tasks depends on the nature of the project and tools used. For more
- information on setting translation project specifications and determining quality
- expectations, implementers are encouraged to consult <ptr target="#isots11669"
- type="bibref"/>. Details about translation specifications are available at <ptr
- target="#structuredspecs" type="bibref"/>. While these documents do not directly
- address the definition of quality metrics, they provide useful guidance for
- implementers interested in determining which localization quality issue values
- are best for specific scenarios.</p></note>
+ <item>A human reviewer working with a web-based tool adds quality markup manually in a text editor, including comments and suggestions, to localized content as part of the review process. A subsequent process examines this markup to ensure that changes were made.</item>
+ <item>A fully automatic quality checking tool flags a number of potential quality issues in an XML or HTML file and marks them up using ITS 2.0 markup. A human reviewer then uses another tool to examine this markup and decide whether the file needs to receive more extensive review or be passed on for further processing without a further manual review stage.</item>
+ <item>A quality assessment process identifies a number of issues and adds the ITS markup to a rendered 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.</item>
+ </list>
+ <note><p xml:id="selecting-issues">What issues should be considered in quality assessment tasks depends on the nature of the project and tools used. Further guidance is beyond the scope of this specification, but implementers may wish to consult the references cited in Appendix @@@TBD@@@.</p></note>
<p>The data category defines five pieces of information:</p>
<table border="1" xml:id="lqissueDefs" width="100%">
<row role="head">
@@ -3964,8 +3950,7 @@
</row>
<row>
<cell>Type</cell>
- <cell>A set of broad types of issues into which tool-specific issues can be
- categorized.</cell>
+ <cell>A classifier that groups similar issues into categories (for example to differentiate spelling errors from grammar errors).</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 types <ref target="#rfc-keywords"
@@ -3975,14 +3960,13 @@
</row>
<row>
<cell>Comment</cell>
- <cell>A human-readable description of the quality issue.</cell>
+ <cell>A human-readable description of a specific instance of a quality issue.</cell>
<cell>Text</cell>
- <cell/>
+ <cell>Comments can be used to explain an issue or provide guidance in addressing an issue. For example, a note about a Terminology issue might specify what term should be used.</cell>
</row>
<row>
<cell>Severity</cell>
- <cell>A decimal value representing the severity of the issue, as defined by the
- model generating the metadata.</cell>
+ <cell>A classifier for the seriousness of an issue. The seriousness depends on the Quality Model that is being applied. The Quality Model should be made explicit via the Profile Reference.</cell>
<cell>A rational number in the interval 0 to 100 (inclusive). The value follows the
<ref target="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double">XML
Schema double data type</ref> with the constraining facets <ref
@@ -3991,16 +3975,13 @@
target="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#rf-maxInclusive"
>maxInclusive</ref> set to 100. The higher values represent greater
severity.</cell>
- <cell>It is up to tools to map the values of this to their own system to this scale.
- If needed, the original value can be passed along using a custom namespace for
- XML, or a <code>data-</code> attribute for HTML.</cell>
+ <cell>It is up to tools to map the values allowed by ITS 2.0 to their own system’s scale. If needed, the original value can be passed along using a custom namespace for XML, or a <code>data-</code> attribute for HTML.</cell>
</row>
<row>
<cell>Profile Reference</cell>
- <cell>A reference to a document describing the quality assessment model used for the
- issue.</cell>
+ <cell>A reference to a description of the quality assessment model (or a specific profile (customization/instantiation) of a model, where relevant) used for the issue.</cell>
<cell>An IRI pointing to the reference document.</cell>
- <cell>The use of resolvable IRI is strongly recommended as it provides a way for
+ <cell>The use of resolvable IRIs is strongly recommended as it provides a way for
human evaluators to learn more about the quality issues in use.</cell>
</row>
<row>
@@ -4878,21 +4859,21 @@
<emph>This section is normative.</emph>
</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
+ between different localization quality assurance tools. It offers a list of high-level
+ quality issue types common in fully automatic and manual localization quality assessment. Tools
can map their internal types to these types 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>
+ <note><p>Note: The values of locQualityIssueType were derived from an early version of the QTLaunchPad project's Multidimensional Quality Metrics (MQM) framework. MQM is based on a careful analysis of existing translation quality assessment tools and models, such as the LISA QA Model, SAE J2450 @@@tbd - add reference?@@@, and various commercial tools. The values represent common issue types found in those models and are designed to provide interoperability between models. Differences in granularity and in issue types may prevent full interoperability, but using the shared values will maximize interoperability where possible.</p></note>
<p>The scope column in the following table identifies whether the issue type applies to the
- source text (“S”), target text (“T”) or both (“S or T”).</p>
+ source content (“S”), target content (“T”) or both (“S or T”).</p>
<p>The values listed in the following table are allowed for <att>locQualityIssueType</att>.
Ideally the values a tool implementing the data category produces for the attribute matches one
- of the values provided in this table and are as semantically accurate as possible. Tools are encouraged to
+ of the values provided in this table and are as semantically accurate as possible. For example, marking the phrase “These man is” as a <code>terminology</code> issue, rather than as a <code>grammar</code> issue would be semantically inaccurate. Tools are encouraged to
map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p>
+ <note><p>For tools <emph>generating</emph> ITS 2.0 Localization Quality Issue markup, if one internal issue type can be categorized as multiple ITS 2.0 issue types, <emph>the first applicable one from the following table should be used</emph>. The list is ordered with more specific types first. For example, if a terminology database specifies that the term “USB memory stick” should be used instead of “USB pen drive” but the translated content has “Insert a USB pen drive into any available USB port”, <code>terminology</code> would be used instead of <code>mistranslation</code> because <code>terminology</code> occurs earlier in the list and is more specific than a (general) <code>mistranslation</code>. In the case where multiple separate issues must be marked on a single span (e.g., it contains both a <code>mistranslation</code> and a <code>grammar</code> issue), implementers may wish to use standoff annotation, as shown in <ptr target="#EX-locQualityIssue-local-2" type="exref"/> and <pt target="#EX-locQualityIssue-html5-local-2" type="exref"/>.</p></note>
<note>
- <p xml:id="qa-issue-types-mappings">The <ref
- target="http://www.w3.org/International/its/ig/">ITS Interest Group</ref> maintains an
- <ref target="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings">informative mapping</ref> between ITS 2.0 quality issue types and other types used to specify quality issues: types produced by quality check tools, defined in other specifications etc. The purpose of these mappings is to document how tool internal information relates to the ITS 2.0 quality types. To foster interoperability, implementers are strongly encouraged not to rely on these mappings and to implement the ITS 2.0 quality types natively.</p>
+ <p xml:id="qa-issue-types-mappings">The <ref target="http://www.w3.org/International/its/ig/">ITS Interest Group</ref> maintains informative <ref target="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings">mappings of tool-specific quality issue types and ITS 2.0 localization quality types</ref>. The ITS IG Wiki provides information on how to update that list. The purpose of these mappings is to document how tool internal information relates to the ITS 2.0 quality types. To foster interoperability, implementers are strongly encouraged to implement the ITS 2.0 quality types natively.</p>
</note>
<table border="1" xml:id="lqissue-typevalues-table" width="100%">
<row role="head">
Received on Thursday, 5 September 2013 15:48:04 UTC