WWW/International/multilingualweb/lt/drafts/its20 its20.html,1.122,1.123 its20.odd,1.122,1.123

Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv8964

Modified Files:
	its20.html its20.odd 
Log Message:
Continued implementation of loc quality.

Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -d -r1.122 -r1.123
--- its20.odd	22 Aug 2012 02:52:40 -0000	1.122
+++ its20.odd	22 Aug 2012 11:00:09 -0000	1.123
@@ -4552,15 +4552,198 @@
 								<cell></cell>
 							</row>
 							<row>
-								<cell><code></code></cell>
+								<cell><code>legal</code></cell>
+								<cell>The text is legally problematic (e.g., it is specific to the wrong legal system).</cell>
+								<cell><list>
+									<item>The localized text is intended for use in Thailand but includes U.S. regulatory notices.</item>
+									<item>A text translated into German contains comparative advertising claims that are not allowed by German law.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>register</code></cell>
+								<cell>The text is written in the wrong linguistic register of uses slang or other language variants
+									inappropriate to the text.</cell>
+								<cell><list>
+									<item>A financia text in U.S. English refers to dollars as "bucks".</item>
+								</list></cell>
+								<cell>S+T</cell>
 								<cell></cell>
+							</row>
+							<row>
+								<cell><code>locale-specific-content</code></cell>
+								<cell>The localization contains content that does not apply to the locale for which it was prepared.</cell>
 								<cell><list>
+									<item>A text translated for the Japanese market contains call center numbers in Texas and refers
+										to special offers available only in the U.S.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell>Legally inappropriate material should be classified as <code>legal</code>.</cell>
+							</row>
+							<row>
+								<cell><code>locale-violation</code></cell>
+								<cell>Text violates norms for the intended locale.</cell>
+								<cell><list>
+									<item>A text localized into German has dates in YYYY-MM-DD format instead of in DD.MM.YYYY.</item>
+									<item>A text for the Irish market uses American-style foot and inch measurements instead of centimeters.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>style</code></cell>
+								<cell>The text contains stylistic errors.</cell>
+								<cell><list>
+									<item>Company style guidelines dictates that all individuals be referred to as Mr. or Ms. with 
+										a family name, but the text refers to “Jack Smith”.</item>
 									<item></item>
-									<item></item>
 								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>characters</code></cell>
+								<cell>The text contains characters that are garbled or incorrect or that are not used in the language 
+									in which the content appears.</cell>
+								<cell><list>
+									<item>A text should have a '•' but instead has a '¥' sign.</item>
+									<item>A text translated into German omits the umlauts over 'ü', 'ö', and 'ä'.</item>
+								</list></cell>
+								<cell>S+T</cell>
 								<cell></cell>
+							</row>
+							<row>
+								<cell><code>misspelling</code></cell>
+								<cell>The text contains a misspelling.</cell>
+								<cell><list>
+									<item>A German text misspells the word "Zustellung" as "Zustellüng".</item>
+								</list></cell>
+								<cell>S+T</cell>
 								<cell></cell>
 							</row>
+							<row>
+								<cell><code>typographical</code></cell>
+								<cell>The text has typographical errors such as omitted/incorrect punctuation, incorrect
+									capitalization, etc.</cell>
+								<cell><list>
+									<item>An English text has the following sentence: "The man whom, we saw, was in the Military and carried it's insignias".</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>formatting</code></cell>
+								<cell>The text is formatted incorrectly.</cell>
+								<cell><list>
+									<item>Warnings in the text are supposed to be set in italic face, but instead appear in bold face.</item>
+									<item>Margins of the text are narrower than specified.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>inconsistent-entities</code></cell>
+								<cell>The source and target text contain different named entities (dates, times, place names, individual names, etc.)</cell>
+								<cell><list>
+									<item>The name "Thaddeus Cahill" appears in an English source but is rendered as "Tamaš Cahill" in the Czech version.</item>
+									<item>The date "February 9, 2007" appears in the source but the translated text has "2. September 2007".</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>numbers</code></cell>
+								<cell>Numbers are inconsistent between source and target.</cell>
+								<cell><list>
+									<item>A source text states that an object is 120 cm long, but the target text says it is 129 cm. long.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell>Some tools may correct for differences in units of measurement to reduce false positives.</cell>
+							</row>
+							<row>
+								<cell><code>markup</code></cell>
+								<cell>There is an issue related to markup or a mismatch in markup between source and target.</cell>
+								<cell><list>
+									<item>The source segment has five markup tags but the target has only two.</item>
+									<item>An opening tag in the text is missing a closing tag.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>pattern-problem</code></cell>
+								<cell>The text fails to match a pattern that defines allowable content (or matches one that defines
+									non-allowable content).</cell>
+								<cell><list>
+									<item>The tool disallows the regular expression pattern ['"”’][\.,] but the translated text contains "A leading “expert”, a political hack, claimed otherwise."</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>whitespace</code></cell>
+								<cell>There is a mismatch in whitespace between source and target content.</cell>
+								<cell><list>
+									<item>A source segment starts with six space characters but the corresponding target segment has two non-breaking spaces at the start.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell></cell>
+							</row>
+							<row>
+								<cell><code>internationalization</code></cell>
+								<cell>There is an issue related to the internationalization of content.</cell>
+								<cell><list>
+									<item>A line of programming code has embedded language-specific strings.</item>
+									<item>A user interface element leaves no room for text expansion.</item>
+									<item>A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell>There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to.</cell>
+							</row>
+							<row>
+								<cell><code>length</code></cell>
+								<cell>There is a significant difference in source and target length.</cell>
+								<cell><list>
+									<item>The translation of a segment is five times as long as the source.</item>
+								</list></cell>
+								<cell>T</cell>
+								<cell>What constitutes a "significant" difference in length is determined by the model 
+									referred to in the <att>locQualityIssueProfileRef</att>.</cell>
+							</row>
+							<row>
+								<cell><code>uncategorized</code></cell>
+								<cell>The issue has not been categorized.</cell>
+								<cell><list>
+									<item>A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified.</item>
+								</list></cell>
+								<cell>S+T</cell>
+								<cell>This category has two uses:
+									<list type="ordered">
+										<item>A tool can use it to pass through quality data from another tool
+									in cases where the issues from the other tool are not classified (for example, a localization 
+									quality assurance tool interfaces with a third-party grammar checker).</item>
+										<item>A tool's issues are not yet assigned to categories, and, until an updated assignment is made,
+									they may be listed as <code>uncategorized</code>. In this case it is recommended that issues be assigned 
+									to appropriate categories as soon as possible since uncategorized does not foster interoperability.</item>
+									</list>
+								</cell>
+							</row>
+							<row>
+								<cell><code>other</code></cell>
+								<cell>Any issue that cannot be assigned to any values listed above.</cell>
+								<cell></cell>
+								<cell>S+T</cell>
+								<cell><list type="unordered">
+									<item>This category 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>
+									<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" category, 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 category.</item>
+								</list></cell>
+							</row>
 						</table>
 					</div>
 					<div xml:id="lqissue-markup">

Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -d -r1.122 -r1.123
--- its20.html	22 Aug 2012 02:52:40 -0000	1.122
+++ its20.html	22 Aug 2012 11:00:08 -0000	1.123
@@ -2395,10 +2395,95 @@
                         </td><td rowspan="1" colspan="1">The text contains a grammatical error (including errors of syntax and morphology).</td><td rowspan="1" colspan="1">
                            <ul><li><p>The text reads "The guidelines says that users should use a static grounding strap."</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/>
-                        </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">
+                           <code>legal</code>
+                        </td><td rowspan="1" colspan="1">The text is legally problematic (e.g., it is specific to the wrong legal system).</td><td rowspan="1" colspan="1">
+                           <ul><li><p>The localized text is intended for use in Thailand but includes U.S. regulatory notices.</p></li><li><p>A text translated into German contains comparative advertising claims that are not allowed by German law.</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>register</code>
+                        </td><td rowspan="1" colspan="1">The text is written in the wrong linguistic register of uses slang or other language variants
+									inappropriate to the text.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A financia text in U.S. English refers to dollars as "bucks".</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>locale-specific-content</code>
+                        </td><td rowspan="1" colspan="1">The localization contains content that does not apply to the locale for which it was prepared.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A text translated for the Japanese market contains call center numbers in Texas and refers
+										to special offers available only in the U.S.</p></li></ul>
+                        </td><td rowspan="1" colspan="1">S+T</td><td rowspan="1" colspan="1">Legally inappropriate material should be classified as <code>legal</code>.</td></tr><tr><td rowspan="1" colspan="1">
+                           <code>locale-violation</code>
+                        </td><td rowspan="1" colspan="1">Text violates norms for the intended locale.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A text localized into German has dates in YYYY-MM-DD format instead of in DD.MM.YYYY.</p></li><li><p>A text for the Irish market uses American-style foot and inch measurements instead of centimeters.</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>style</code>
+                        </td><td rowspan="1" colspan="1">The text contains stylistic errors.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>Company style guidelines dictates that all individuals be referred to as Mr. or Ms. with 
+										a family name, but the text refers to “Jack Smith”.</p></li><li><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>characters</code>
+                        </td><td rowspan="1" colspan="1">The text contains characters that are garbled or incorrect or that are not used in the language 
+									in which the content appears.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A text should have a '•' but instead has a '¥' sign.</p></li><li><p>A text translated into German omits the umlauts over 'ü', 'ö', and 'ä'.</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>misspelling</code>
+                        </td><td rowspan="1" colspan="1">The text contains a misspelling.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A German text misspells the word "Zustellung" as "Zustellüng".</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>typographical</code>
+                        </td><td rowspan="1" colspan="1">The text has typographical errors such as omitted/incorrect punctuation, incorrect
+									capitalization, etc.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>An English text has the following sentence: "The man whom, we saw, was in the Military and carried it's insignias".</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>formatting</code>
+                        </td><td rowspan="1" colspan="1">The text is formatted incorrectly.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>Warnings in the text are supposed to be set in italic face, but instead appear in bold face.</p></li><li><p>Margins of the text are narrower than specified.</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>inconsistent-entities</code>
+                        </td><td rowspan="1" colspan="1">The source and target text contain different named entities (dates, times, place names, individual names, etc.)</td><td rowspan="1" colspan="1">
+                           <ul><li><p>The name "Thaddeus Cahill" appears in an English source but is rendered as "Tamaš Cahill" in the Czech version.</p></li><li><p>The date "February 9, 2007" appears in the source but the translated text has "2. September 2007".</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>numbers</code>
+                        </td><td rowspan="1" colspan="1">Numbers are inconsistent between source and target.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A source text states that an object is 120 cm long, but the target text says it is 129 cm. long.</p></li></ul>
+                        </td><td rowspan="1" colspan="1">S+T</td><td rowspan="1" colspan="1">Some tools may correct for differences in units of measurement to reduce false positives.</td></tr><tr><td rowspan="1" colspan="1">
+                           <code>markup</code>
+                        </td><td rowspan="1" colspan="1">There is an issue related to markup or a mismatch in markup between source and target.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>The source segment has five markup tags but the target has only two.</p></li><li><p>An opening tag in the text is missing a closing tag.</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>pattern-problem</code>
+                        </td><td rowspan="1" colspan="1">The text fails to match a pattern that defines allowable content (or matches one that defines
+									non-allowable content).</td><td rowspan="1" colspan="1">
+                           <ul><li><p>The tool disallows the regular expression pattern ['"”’][\.,] but the translated text contains "A leading “expert”, a political hack, claimed otherwise."</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>whitespace</code>
+                        </td><td rowspan="1" colspan="1">There is a mismatch in whitespace between source and target content.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A source segment starts with six space characters but the corresponding target segment has two non-breaking spaces at the start.</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>internationalization</code>
+                        </td><td rowspan="1" colspan="1">There is an issue related to the internationalization of content.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A line of programming code has embedded language-specific strings.</p></li><li><p>A user interface element leaves no room for text expansion.</p></li><li><p>A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes.</p></li></ul>
+                        </td><td rowspan="1" colspan="1">S+T</td><td rowspan="1" colspan="1">There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to.</td></tr><tr><td rowspan="1" colspan="1">
+                           <code>length</code>
+                        </td><td rowspan="1" colspan="1">There is a significant difference in source and target length.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>The translation of a segment is five times as long as the source.</p></li></ul>
+                        </td><td rowspan="1" colspan="1">T</td><td rowspan="1" colspan="1">What constitutes a "significant" difference in length is determined by the model 
+									referred to in the <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueProfileRef</a>.</td></tr><tr><td rowspan="1" colspan="1">
+                           <code>uncategorized</code>
+                        </td><td rowspan="1" colspan="1">The issue has not been categorized.</td><td rowspan="1" colspan="1">
+                           <ul><li><p>A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified.</p></li></ul>
+                        </td><td rowspan="1" colspan="1">S+T</td><td rowspan="1" colspan="1">This category has two uses:
+									<ol class="depth1"><li><p>A tool can use it to pass through quality data from another tool
+									in cases where the issues from the other tool are not classified (for example, a localization 
+									quality assurance tool interfaces with a third-party grammar checker).</p></li><li><p>A tool's issues are not yet assigned to categories, and, until an updated assignment is made,
+									they may be listed as <code>uncategorized</code>. In this case it is recommended that issues be assigned 
+									to appropriate categories as soon as possible since uncategorized does not foster interoperability.</p></li></ol>
+                        </td></tr><tr><td rowspan="1" colspan="1">
+                           <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+T</td><td rowspan="1" colspan="1">
+                           <ul><li><p>This category 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 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" category, 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 category.</p></li></ul>
+                        </td></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
    {
@@ -2691,7 +2776,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="d3e8539" id="d3e8539" 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="d3e8915" id="d3e8915" shape="rect"/>Example 69: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
 &lt;sch:schema
   xmlns:sch="http://www.ascc.net/xml/schematron" &gt;
 &lt;!-- Schematron document to test constraints for global and local ITS markup.
@@ -2758,7 +2843,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="d3e8561" id="d3e8561" shape="rect"/>Example 70: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve">&lt;rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"&gt; &lt;namespace
+					attributes of host language are ignored during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8937" id="d3e8937" shape="rect"/>Example 70: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve">&lt;rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"&gt; &lt;namespace
 						ns="http://www.w3.org/2005/11/its"&gt; &lt;validate schema="its-elements.rng"/&gt;
 						&lt;/namespace&gt; &lt;namespace ns="http://www.w3.org/2005/11/its" match="attributes"&gt;
 						&lt;validate schema="its-attributes.rng"/&gt; &lt;/namespace&gt; &lt;anyNamespace&gt;

Received on Wednesday, 22 August 2012 11:00:17 UTC