W3C home > Mailing lists > Public > public-multilingualweb-lt-commits@w3.org > March 2013

CVS WWW/International/multilingualweb/lt/drafts/its20

From: CVS User alommel <cvsmail@w3.org>
Date: Thu, 28 Mar 2013 10:26:24 +0000
Message-Id: <E1ULA2K-00080c-J8@gil.w3.org>
To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv30786

Modified Files:
	its20.html its20.odd 
Log Message:
fixed issues 76 and 124

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/03/27 22:16:52	1.358
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/03/28 10:26:24	1.359
@@ -3292,10 +3292,11 @@
           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 values listed in the following table are allowed for <code class="its-attr-markup">locQualityIssueType</code>.
-          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 types 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><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-tool-specific-mappings">The <a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> maintains an
+          The values a tool implementing the data category produces for the attribute must
+          match one of the values provided in this table and must be semantically accurate. If a
+          tool can map its internal values to these types it must do so and must use the value
+          <code>other</code>, which is reserved strictly for values that cannot be mapped to these
+          values.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-tool-specific-mappings">The <a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> maintains an
             informative mappings of tools to localization quality issue types. <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings" shape="rect">The ITS IG
               Wiki</a> provides information on <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings#Update_of_this_page" shape="rect">how to update that list</a>.</p></div><a name="lqissue-typevalues-table" id="lqissue-typevalues-table" shape="rect"/><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>
@@ -3306,13 +3307,13 @@
                   English to translate (a literal translation), but the term used in English should
                   be “wedge block,” as specified in a terminology list supplied to the
                   translator.</p></li></ul>
-                  </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This value <a href="#rfc-keywords" shape="rect">MUST NOT</a> be used for simple
-              typographical errors or word choice not related to defined terminologies. For example,
-              a mistyping of “pin” as “pen” or the use of “imply” instead of “infer” (mistaking two
-              commonly confused words) would not count as terminology issues and should be
-              categorized as either spelling errors or mistranslations, depending on the nature of
-              the issue. Terminology refers <em>only</em> to cases where incorrect choices about
-              terms (either formal or commonly defined in a domain) are involved.</td></tr><tr><td rowspan="1" colspan="1">
+                  </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This value must not be used for simple typographical errors or word choice not
+              related to defined terminologies. For example, a mistyping of “pin” as “pen” or the
+              use of “imply” instead of “infer” (mistaking two commonly confused words) would not
+              count as terminology issues and should be categorized as either spelling errors or
+              mistranslations, depending on the nature of the issue. Terminology refers
+              <em>only</em> to cases where incorrect choices about terms (either formal or
+              commonly defined in a domain) are involved.</td></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
@@ -3349,10 +3350,11 @@
                   paste operation.</p></li></ul>
                   </td><td rowspan="1" colspan="1">T</td><td rowspan="1" colspan="1"/></tr><tr><td rowspan="1" colspan="1">
                      <code>inconsistency</code>
-                  </td><td rowspan="1" colspan="1">The text is inconsistent with itself (NB: not for use with terminology
+                  </td><td rowspan="1" colspan="1">The text is inconsistent with itself or is translated inconsistency (NB: not for use with terminology
               inconsistency).</td><td rowspan="1" colspan="1">
                      <ul><li><p>The text states that an event happened in 1912 in one location but in another
-                  states that it happened in 1812.</p></li></ul>
+                  states that it happened in 1812.</p></li><li><p>The translated text uses different wording for multiple instances of a single
+                regulatory notice that occurs in multiple locations in a series of manuals.</p></li></ul>
                   </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1"/></tr><tr><td rowspan="1" colspan="1">
                      <code>grammar</code>
                   </td><td rowspan="1" colspan="1">The text contains a grammatical error (including errors of syntax and
@@ -3485,12 +3487,12 @@
                      <code>other</code>
                   </td><td rowspan="1" colspan="1">Any issue that cannot be assigned to any values listed above.</td><td rowspan="1" colspan="1"/><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">
                      <ul><li><p>This value allows for the inclusion of any issues not included in the
-                  previously listed values. This value <a href="#rfc-keywords" shape="rect">MUST NOT</a> be
-                  used for any tool- or model-specific issues that can be mapped to the values
-                  listed above.</p></li><li><p>In addition, this value is not synonymous with <code>uncategorized</code> in
+                  previously listed values. This value must not be used for any tool- or
+                  model-specific issues that can be mapped to the values listed above.</p></li><li><p>In addition, this value is not synonymous with <code>uncategorized</code> in
                   that <code>uncategorized</code> issues may be assigned to another precise value,
-                  while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" value, it <a href="#rfc-keywords" shape="rect">MUST</a> be mapped to this value even if the specific
-                  instance of the issue might be mapped to another value.</p></li></ul>
+                  while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" value, it must be mapped to
+                  this value even if the specific instance of the issue might be mapped to another
+                  value.</p></li></ul>
                   </td></tr></tbody></table></div><div class="div1">
 <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-schemas" id="its-schemas" shape="rect"/>D Schemas for ITS</h2><p>The following schemas define ITS elements and attributes and can be used as building
           blocks when you want to integrate ITS markup into your own XML vocabulary. You can see
@@ -5797,7 +5799,7 @@
             see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/79" shape="rect">issue-79</a>.</p></li><li><p>Edits to resolve <a href="#directionality" shape="rect">Directionality</a> issues, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/86" shape="rect">issue-86</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/90" shape="rect">issue-90</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/101" shape="rect">issue-101</a> and <a href="http://lists.w3.org/Archives/Public/www-international/2013JanMar/0238.html" shape="rect">edits summary mail</a>.</p></li><li><p>Added a <code>non-conformance</code> value to the <a href="#lqissue-typevalues-table" shape="rect">Localization Quality Issue Type table</a>, see
               <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/63" shape="rect">issue-63</a>.</p></li><li><p>Revised abstract as part of rewrite of sections 1 and 2, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/377" shape="rect">action-377</a>.</p></li><li><p>Added note related to "domainMapping" in "multi-engine" scenarios, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/75" shape="rect">issue-75</a>.</p></li><li><p>Implemented minor editiorial changes from
             <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/113" shape="rect">Issue-113</a>.</p></li><li><p>Added the attribute <code class="its-attr-markup">type</code> to the <a href="#LocaleFilter" shape="rect">Locale
-            Filter</a> data category and updated the corresponding examples. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/121" shape="rect">issue-121</a>.</p></li><li><p>In <a class="section-ref" href="#provenance-implementation" shape="rect">Section 8.12.2: Implementation</a> removed untrue statement that the attribute <code class="its-attr-markup">provenanceRecordsRefPointer</code> does not apply to HTML, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/123" shape="rect">issue-123</a>.</p></li><li><p>Put <a href="#css-selectors-and-attributes" shape="rect">a note</a> in <a class="section-ref" href="#css-selectors" shape="rect">Section 5.3.3: CSS Selectors</a> about CSS selectors and attributes, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/99" shape="rect">issue-99</a>.</p></li></ol><p id="changelog-since-20121023">The following log records major changes that have been
+            Filter</a> data category and updated the corresponding examples. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/121" shape="rect">issue-121</a>.</p></li><li><p>In <a class="section-ref" href="#provenance-implementation" shape="rect">Section 8.12.2: Implementation</a> removed untrue statement that the attribute <code class="its-attr-markup">provenanceRecordsRefPointer</code> does not apply to HTML, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/123" shape="rect">issue-123</a>.</p></li><li><p>Put <a href="#css-selectors-and-attributes" shape="rect">a note</a> in <a class="section-ref" href="#css-selectors" shape="rect">Section 5.3.3: CSS Selectors</a> about CSS selectors and attributes, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/99" shape="rect">issue-99</a>.</p></li><li><p>Updated <a href="#lqissue-typevalues" shape="rect">the table of Localization Quality Issue Type values</a> to clarify the valueof “inconsistency,” see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/76" shape="rect">issue-76</a>.</p></li><li><p>Updated <a href="#lqissue-typevalues" shape="rect">the table of Localization Quality Issue Type values</a> to properly use RFC2119 values. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/124" shape="rect">issue-124</a>.</p></li></ol><p id="changelog-since-20121023">The following log records major changes that have been
           made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121023/" shape="rect">ITS 2.0 Working Draft 23 October 2012</a>.</p><ol class="depth1"><li><p>Clarified usage of <a href="#domain" shape="rect">Domain</a> data category in HTML in
             response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/56" shape="rect">issue-56</a>.</p></li><li><p>Added the <a href="#lqissueDefs" shape="rect">enabled information</a> in <a class="section-ref" href="#lqissue" shape="rect">Section 8.17: Localization Quality Issue</a>.</p></li><li><p>Updated the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category.</p></li><li><p>Fine tuned the algorithm to compute the result values of the <a href="#domain" shape="rect">Domain</a> data category.</p></li><li><p>Fix on <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 81</a>:
               <code>id</code> attribute of <code>script</code> element now the same as of containing
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/03/27 22:16:53	1.351
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/03/28 10:26:24	1.352
@@ -4819,12 +4819,11 @@
           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 types 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>
+          The values a tool implementing the data category produces for the attribute must
+          match one of the values provided in this table and must be semantically accurate. If a
+          tool can map its internal values to these types it must do so and must use the value
+          <code>other</code>, which is reserved strictly for values that cannot be mapped to these
+          values.</p>
         <note>
           <p xml:id="qa-issue-types-tool-specific-mappings">The <ref
               target="http://www.w3.org/International/its/ig/">ITS Interest Group</ref> maintains an
@@ -4858,13 +4857,13 @@
               </list>
             </cell>
             <cell>S or T</cell>
-            <cell>This value <ref target="#rfc-keywords">MUST NOT</ref> be used for simple
-              typographical errors or word choice not related to defined terminologies. For example,
-              a mistyping of “pin” as “pen” or the use of “imply” instead of “infer” (mistaking two
-              commonly confused words) would not count as terminology issues and should be
-              categorized as either spelling errors or mistranslations, depending on the nature of
-              the issue. Terminology refers <emph>only</emph> to cases where incorrect choices about
-              terms (either formal or commonly defined in a domain) are involved.</cell>
+            <cell>This value must not be used for simple typographical errors or word choice not
+              related to defined terminologies. For example, a mistyping of “pin” as “pen” or the
+              use of “imply” instead of “infer” (mistaking two commonly confused words) would not
+              count as terminology issues and should be categorized as either spelling errors or
+              mistranslations, depending on the nature of the issue. Terminology refers
+              <emph>only</emph> to cases where incorrect choices about terms (either formal or
+              commonly defined in a domain) are involved.</cell>
           </row>
           <row>
             <cell><code>mistranslation</code></cell>
@@ -4937,12 +4936,14 @@
           </row>
           <row>
             <cell><code>inconsistency</code></cell>
-            <cell>The text is inconsistent with itself (NB: not for use with terminology
+            <cell>The text is inconsistent with itself or is translated inconsistency (NB: not for use with terminology
               inconsistency).</cell>
             <cell>
               <list>
                 <item>The text states that an event happened in 1912 in one location but in another
                   states that it happened in 1812.</item>
+                <item>The translated text uses different wording for multiple instances of a single
+                regulatory notice that occurs in multiple locations in a series of manuals.</item>
               </list>
             </cell>
             <cell>S or T</cell>
@@ -5231,15 +5232,14 @@
             <cell>
               <list type="unordered">
                 <item>This value allows for the inclusion of any issues not included in the
-                  previously listed values. This value <ref target="#rfc-keywords">MUST NOT</ref> be
-                  used for any tool- or model-specific issues that can be mapped to the values
-                  listed above.</item>
+                  previously listed values. This value must not be used for any tool- or
+                  model-specific issues that can be mapped to the values listed above.</item>
                 <item>In addition, this value is not synonymous with <code>uncategorized</code> in
                   that <code>uncategorized</code> issues may be assigned to another precise value,
                   while other issues cannot.</item>
-                <item>If a system has an "miscellaneous" or "other" value, it <ref
-                    target="#rfc-keywords">MUST</ref> be mapped to this value even if the specific
-                  instance of the issue might be mapped to another value.</item>
+                <item>If a system has an "miscellaneous" or "other" value, it must be mapped to
+                  this value even if the specific instance of the issue might be mapped to another
+                  value.</item>
               </list>
             </cell>
           </row>
@@ -5845,6 +5845,8 @@
               >issue-121</ref>.</item>
           <item>In <ptr target="#provenance-implementation" type="specref"/> removed untrue statement that the attribute <att>provenanceRecordsRefPointer</att> does not apply to HTML, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/123">issue-123</ref>.</item>
           <item>Put <ref target="#css-selectors-and-attributes">a note</ref> in <ptr target="#css-selectors" type="specref"/> about CSS selectors and attributes, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/99">issue-99</ref>.</item>
+          <item>Updated <ref target="#lqissue-typevalues">the table of Localization Quality Issue Type values</ref> to clarify the value of “inconsistency,” see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/76">issue-76</ref>.</item>
+          <item>Updated <ref target="#lqissue-typevalues">the table of Localization Quality Issue Type values</ref> to properly use RFC2119 values. See <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/124">issue-124</ref>.</item>
         </list>
         <p xml:id="changelog-since-20121023">The following log records major changes that have been
           made to this document since the <ref target="http://www.w3.org/TR/2012/WD-its20-20121023/"
Received on Thursday, 28 March 2013 10:26:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:40 UTC