- From: Yves Savourel via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 22 Aug 2012 17:54:18 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv30033
Modified Files:
its20.html its20.odd
Log Message:
Moved locqualityissuetype values to appendix; shorten html example.
Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -d -r1.127 -r1.128
--- its20.odd 22 Aug 2012 13:41:49 -0000 1.127
+++ its20.odd 22 Aug 2012 17:54:15 -0000 1.128
@@ -4421,9 +4421,8 @@
<p xml:id="lqissue-local">LOCAL: Using the inline markup to represent the data category locally is limited to a single
occurrence for a given content (e.g. one cannot have different <att>locQualityIssueType</att> attributes applied
- to the same span of text because the inner-most one would override the others). Because there may be several
- instances of a localization quality issue for a given ontent, a local <emph>standoff markup</emph> allowing
- such cases is also provided.</p>
+ to the same span of text because the inner-most one would override the others).
+ A local <emph>standoff markup</emph> is provided to allow such cases.</p>
<p>The following local markup is available for the Localization Quality Issue data category:</p>
<list type="unordered">
<item><p>Either (inline markup):</p>
@@ -4485,7 +4484,7 @@
</exemplum>
<exemplum xml:id="EX-locQualityIssue-html5-local-1">
<head>Annotating an issue in HTML with local inline markup</head>
- <p>In this example several spans of content are assocaited with a quality issue.</p>
+ <p>In this example several spans of content are associated with a quality issue.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/html5/EX-locQualityIssue-html5-local-1.html" />
</exemplum>
@@ -4518,301 +4517,6 @@
target="examples/html5/EX-locQualityIssue-html5-local-2.html" />
</exemplum>
<note type="ed">TODO for above: Finalize how HTML its-loc-quality-issues and its-loc-quality-issue should be defined.</note>
-
- <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>untranslated</code></cell>
- <cell>Content that should have been translated was left untranslated.</cell>
- <cell><list>
- <item>The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian
- localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer."</item>
- </list></cell>
- <cell>T</cell>
- <cell><code>omission</code> takes precedence over <code>untranslated</code>. Omissions are distinct in
- that they address cases where text is not present, while <code>untranslated</code> addresses cases
- where text has been carried from the source untranslated.</cell>
- </row>
- <row>
- <cell><code>addition</code></cell>
- <cell>The translated text contains inappropriate additions.</cell>
- <cell><list>
- <item>The translated text contains a note from the translator to himself to look up a term; the note should have
- been deleted but was not.</item>
- </list></cell>
- <cell>T</cell>
- <cell></cell>
- </row>
- <row>
- <cell><code>duplication</code></cell>
- <cell>Content has been duplicated improperly.</cell>
- <cell><list>
- <item>A section of the target text was inadvertently copied twice in a copy and paste operation.</item>
- </list></cell>
- <cell>T</cell>
- <cell></cell>
- </row>
- <row>
- <cell><code>inconsistency</code></cell>
- <cell>The text is inconsistent with itself (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>
- </list></cell>
- <cell>S+T</cell>
- <cell></cell>
- </row>
- <row>
- <cell><code>grammar</code></cell>
- <cell>The text contains a grammatical error (including errors of syntax and morphology).</cell>
- <cell><list>
- <item>The text reads "The guidelines says that users should use a static grounding strap."</item>
- </list></cell>
- <cell>S+T</cell>
- <cell></cell>
- </row>
- <row>
- <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>
- </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">
<head>Markup Declarations for Localization Quality Issue</head>
@@ -5229,55 +4933,352 @@
http://www.w3.org/TR/xpath/ .</bibl>
</listBibl>
</div>
+ <div xml:id="lqissue-typevalues">
+ <head>Values for the Localization Quality Issue Type</head>
+ <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>untranslated</code></cell>
+ <cell>Content that should have been translated was left untranslated.</cell>
+ <cell><list>
+ <item>The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian
+ localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer."</item>
+ </list></cell>
+ <cell>T</cell>
+ <cell><code>omission</code> takes precedence over <code>untranslated</code>. Omissions are distinct in
+ that they address cases where text is not present, while <code>untranslated</code> addresses cases
+ where text has been carried from the source untranslated.</cell>
+ </row>
+ <row>
+ <cell><code>addition</code></cell>
+ <cell>The translated text contains inappropriate additions.</cell>
+ <cell><list>
+ <item>The translated text contains a note from the translator to himself to look up a term; the note should have
+ been deleted but was not.</item>
+ </list></cell>
+ <cell>T</cell>
+ <cell></cell>
+ </row>
+ <row>
+ <cell><code>duplication</code></cell>
+ <cell>Content has been duplicated improperly.</cell>
+ <cell><list>
+ <item>A section of the target text was inadvertently copied twice in a copy and paste operation.</item>
+ </list></cell>
+ <cell>T</cell>
+ <cell></cell>
+ </row>
+ <row>
+ <cell><code>inconsistency</code></cell>
+ <cell>The text is inconsistent with itself (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>
+ </list></cell>
+ <cell>S+T</cell>
+ <cell></cell>
+ </row>
+ <row>
+ <cell><code>grammar</code></cell>
+ <cell>The text contains a grammatical error (including errors of syntax and morphology).</cell>
+ <cell><list>
+ <item>The text reads "The guidelines says that users should use a static grounding strap."</item>
+ </list></cell>
+ <cell>S+T</cell>
+ <cell></cell>
+ </row>
+ <row>
+ <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>
+ </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 type="inform" xml:id="informative-references">
<head>References</head>
<listBibl>
<bibl xml:id="bidiarticle" n="Bidi Article">Richard Ishida. <title>
- <ref target="http://www.w3.org/International/articles/inline-bidi-markup/">What you need to
- know about the bidi algorithm and inline markup</ref></title>. Article of the <ref
- target="http://www.w3.org/International/">W3C Internationalization Activity</ref>, June
+ <ref target="http://www.w3.org/International/articles/inline-bidi-markup/">What you need to
+ know about the bidi algorithm and inline markup</ref></title>. Article of the <ref
+ target="http://www.w3.org/International/">W3C Internationalization Activity</ref>, June
2005.</bibl>
<bibl xml:id="css2-1" n="CSS 2.1"> Bert Bos, Tantek Çelik, Ian Hickson Håkon Wium Lie. <title>
- <ref target="http://www.w3.org/TR/2011/REC-CSS2-20110607/">Cascading Style Sheets, level 2
- revision 1 CSS 2.1 Specification</ref>
- </title>. W3C Recommendation 7 June 2011. Available at <ref
- target="http://www.w3.org/TR/2011/REC-CSS2-20110607/">
- http://www.w3.org/TR/2011/REC-CSS2-20110607/</ref>. The latest version of <ref
+ <ref target="http://www.w3.org/TR/2011/REC-CSS2-20110607/">Cascading Style Sheets, level 2
+ revision 1 CSS 2.1 Specification</ref>
+ </title>. W3C Recommendation 7 June 2011. Available at <ref
+ target="http://www.w3.org/TR/2011/REC-CSS2-20110607/">
+ http://www.w3.org/TR/2011/REC-CSS2-20110607/</ref>. The latest version of <ref
target="http://www.w3.org/TR/CSS21/">CSS2</ref> is available at
http://www.w3.org/TR/CSS21/.</bibl>
<bibl xml:id="dita10" n="DITA 1.0">Michael Priestley, JoAnn Hackos, et. al., editors. <title><ref
- target=" https://www.oasis-open.org/committees/download.php/15316/dita10.zip">OASIS
- Darwin Information Typing Architecture (DITA) Language Specification v1.0</ref></title>.
+ target=" https://www.oasis-open.org/committees/download.php/15316/dita10.zip">OASIS
+ Darwin Information Typing Architecture (DITA) Language Specification v1.0</ref></title>.
OASIS Standard 9 May 2005. Available at <ref
target=" https://www.oasis-open.org/committees/download.php/15316/dita10.zip">
https://www.oasis-open.org/committees/download.php/15316/dita10.zip</ref>.</bibl>
<bibl xml:id="docbook" n="DocBook">Norman Walsh and Leonard Muellner. <title>
- <ref target="http://www.docbook.org/">DocBook: The Definitive Guide</ref>
- </title>. Available at <ref target="http://www.docbook.org/">
+ <ref target="http://www.docbook.org/">DocBook: The Definitive Guide</ref>
+ </title>. Available at <ref target="http://www.docbook.org/">
http://www.docbook.org/</ref>.</bibl>
<bibl xml:id="geo-i18n-l10n" n="l10n i18n">Richard Ishida, Susan Miller. <ref
- target="http://www.w3.org/International/questions/qa-i18n">Localization vs.
- Internationalization</ref>. Article of the <ref target="http://www.w3.org/International/"
+ target="http://www.w3.org/International/questions/qa-i18n">Localization vs.
+ Internationalization</ref>. Article of the <ref target="http://www.w3.org/International/"
>W3C Internationalization Activity</ref>, January 2006.</bibl>
<bibl xml:id="html5" n="HTML5">Ian Hickson <title>
- <ref target="http://www.w3.org/TR/html5/">HTML5 – A vocabulary and associated APIs for HTML
- and XHTML</ref>
- </title>. W3C Working Draft 29 March 2012. Available at <ref
- target="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</ref>. </bibl>
+ <ref target="http://www.w3.org/TR/html5/">HTML5 – A vocabulary and associated APIs for HTML
+ and XHTML</ref>
+ </title>. W3C Working Draft 29 March 2012. Available at <ref
+ target="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</ref>. </bibl>
<bibl xml:id="iso30042" n="ISO 30042">(International Organization for Standardization).
- <title>TermBase eXchange (TBX)</title>. [Geneva]: International Organization for
+ <title>TermBase eXchange (TBX)</title>. [Geneva]: International Organization for
Standardization, 2008.</bibl>
<bibl xml:id="itsreq" n="ITS REQ">Yves Savourel. <title>
- <ref target="http://www.w3.org/TR/2006/WD-itsreq-20060518/">Internationalization and
- Localization Markup Requirements</ref>
- </title>. W3C Working Draft 18 May 2006. Available at <ref
- target="http://www.w3.org/TR/2006/WD-itsreq-20060518/">
- http://www.w3.org/TR/2006/WD-itsreq-20060518/</ref>. The latest version of <ref
+ <ref target="http://www.w3.org/TR/2006/WD-itsreq-20060518/">Internationalization and
+ Localization Markup Requirements</ref>
+ </title>. W3C Working Draft 18 May 2006. Available at <ref
+ target="http://www.w3.org/TR/2006/WD-itsreq-20060518/">
+ http://www.w3.org/TR/2006/WD-itsreq-20060518/</ref>. The latest version of <ref
target="http://www.w3.org/TR/itsreq/">ITS REQ</ref> is available at
http://www.w3.org/TR/itsreq/.</bibl>
<bibl xml:id="reqlocdtd" n="Localizable DTDs">Richard Ishida, Yves Savourel <title><ref
- target="http://people.w3.org/rishida/localizable-dtds/">Requirements for Localizable DTD
- Design</ref></title>. Working Draft 7 July 2003. Available at <ref
+ target="http://people.w3.org/rishida/localizable-dtds/">Requirements for Localizable DTD
+ Design</ref></title>. Working Draft 7 July 2003. Available at <ref
target="http://people.w3.org/rishida/localizable-dtds/"
>http://people.w3.org/rishida/localizable-dtds/</ref>. </bibl>
<bibl xml:id="css3-selectors" n="CSS Selectors Level 3">Tantek Çelik, Elika J. Etemad, Daniel
@@ -5285,71 +5286,71 @@
<ref target="http://www.w3.org/TR/css3-selectors/">Selectors Level 3</ref>
</title>. W3C Recommendation 29 September 2011. Available at <ref
target="http://www.w3.org/TR/css3-selectors/"
- >http://www.w3.org/TR/css3-selectors/</ref>.</bibl>
+ >http://www.w3.org/TR/css3-selectors/</ref>.</bibl>
<bibl xml:id="nvdl" n="NVDL">Information technology -- Document Schema Definition Languages (DSDL)
-- Part 4: <title>Namespace-based Validation Dispatching Language (NVDL)</title>. International
Organization for Standardization (ISO) ISO/IEC 19757-4:2003.</bibl>
<bibl xml:id="opendocument" n="OpenDocument">Michael Brauer et al. <title>
- <ref target=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS Open
- Document Format for Office Applications (OpenDocument).</ref>
- </title>. Oasis Standard 1 May 2005. Available at <ref
- target=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
- https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</ref>. The latest version
+ <ref target=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS Open
+ Document Format for Office Applications (OpenDocument).</ref>
+ </title>. Oasis Standard 1 May 2005. Available at <ref
+ target=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
+ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</ref>. The latest version
of <ref target=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
OpenDocument</ref> is available at
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</bibl>
<bibl xml:id="rfc3066" n="RFC 3066">Harald Alvestrand. <title><ref
- target="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of
- Languages</ref></title>. RFC 3066, January 2001. Available at <ref
+ target="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of
+ Languages</ref></title>. RFC 3066, January 2001. Available at <ref
target="http://www.ietf.org/rfc/rfc3066.txt"
- >http://www.ietf.org/rfc/rfc3066.txt</ref>.</bibl>
+ >http://www.ietf.org/rfc/rfc3066.txt</ref>.</bibl>
<bibl xml:id="ruby-tr" n="Ruby-TR">Marcin Sawicki (until 10 October, 1999), Michel Suignard,
Masayasu Ishikawa (石川 雅康), Martin Dürst, Tex Texin, <title>
<ref target="http://www.w3.org/TR/ruby/">Ruby Annotation</ref>
</title>. W3C Recommendation 31 May 2001. Available at <ref
target="http://www.w3.org/TR/2001/REC-ruby-20010531/">
http://www.w3.org/TR/2001/REC-ruby-20010531/ </ref>. The latest version of <ref
- target="http://www.w3.org/TR/ruby/">Ruby Annotation</ref> is available at
+ target="http://www.w3.org/TR/ruby/">Ruby Annotation</ref> is available at
http://www.w3.org/TR/ruby/.</bibl>
<bibl xml:id="schematron" n="Schematron">Information technology -- Document Schema Definition
Languages (DSDL) -- Part 3: <title>Rule-based validation -- Schematron</title>. International
Organization for Standardization (ISO) ISO/IEC 19757-3:2003.</bibl>
<bibl xml:id="tei" n="TEI">Lou Burnard and Syd Bauman (eds). <title>
- <ref target="http://www.tei-c.org/Guidelines/P5/">Text Encoding Initiative Guidelines
- development version (P5)</ref>
- </title>. TEI Consortium, Charlottesville, Virginia, USA, Text Encoding Initiative.</bibl>
+ <ref target="http://www.tei-c.org/Guidelines/P5/">Text Encoding Initiative Guidelines
+ development version (P5)</ref>
+ </title>. TEI Consortium, Charlottesville, Virginia, USA, Text Encoding Initiative.</bibl>
<bibl xml:id="xhtml10" n="XHTML 1.0">Steven Pemberton et al. <title>
- <ref target="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">XHTML™ 1.0 The Extensible
- HyperText Markup Language (Second Edition)</ref>
- </title>. W3C Recommendation 26 January 2000, revised 1 August 2002. Available at <ref
- target="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">
- http://www.w3.org/TR/2002/REC-xhtml1-20020801/</ref>. The latest version of <ref
+ <ref target="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">XHTML™ 1.0 The Extensible
+ HyperText Markup Language (Second Edition)</ref>
+ </title>. W3C Recommendation 26 January 2000, revised 1 August 2002. Available at <ref
+ target="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">
+ http://www.w3.org/TR/2002/REC-xhtml1-20020801/</ref>. The latest version of <ref
target="http://www.w3.org/TR/xhtml1/">XHTML 1.0</ref> is available at
http://www.w3.org/TR/xhtml1/.</bibl>
-
+
<bibl n="XML i18n BP" xml:id="xml-i18n-bp">Yves Savourel, Jirka Kosek, Richard Ishida. <title><ref
- target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/">Best Practices for XML
- Internationalization</ref></title>. Available at <ref
+ target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/">Best Practices for XML
+ Internationalization</ref></title>. Available at <ref
target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/"
>http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/</ref>. The latest version of <ref
- target="http://www.w3.org/TR/xml-i18n-bp/">xml-i18n-bp</ref> is available at
+ target="http://www.w3.org/TR/xml-i18n-bp/">xml-i18n-bp</ref> is available at
http://www.w3.org/TR/xml-i18n-bp/.</bibl>
-
+
<bibl xml:id="xmlspecbib" n="XMLSPEC"><title>
- <ref target="http://www.w3.org/2002/xmlspec/">The XML Spec Schema and Stylesheets</ref>
- </title>. Available at <ref target="http://www.w3.org/2002/xmlspec/">
- http://www.w3.org/2002/xmlspec/</ref>.</bibl>
+ <ref target="http://www.w3.org/2002/xmlspec/">The XML Spec Schema and Stylesheets</ref>
+ </title>. Available at <ref target="http://www.w3.org/2002/xmlspec/">
+ http://www.w3.org/2002/xmlspec/</ref>.</bibl>
<bibl xml:id="xslt10" n="XSLT 1.0"> James Clark. <title>
- <ref target="http://www.w3.org/TR/1999/REC-xslt-19991116">XSL Transformations (XSLT) Version
- 1.0</ref>
- </title>. W3C Recommendation 16 November 1999. Available at <ref
- target="http://www.w3.org/TR/1999/REC-xslt-19991116">
- http://www.w3.org/TR/1999/REC-xslt-19991116</ref>. The latest version of <ref
+ <ref target="http://www.w3.org/TR/1999/REC-xslt-19991116">XSL Transformations (XSLT) Version
+ 1.0</ref>
+ </title>. W3C Recommendation 16 November 1999. Available at <ref
+ target="http://www.w3.org/TR/1999/REC-xslt-19991116">
+ http://www.w3.org/TR/1999/REC-xslt-19991116</ref>. The latest version of <ref
target="http://www.w3.org/TR/xslt">XSLT 1.0</ref> is available at
http://www.w3.org/TR/xslt.</bibl>
<bibl xml:id="xul" n="XUL"><title>
- <ref target="http://www.xulplanet.com/">exTensible User Interface Language</ref>
- </title>. Available at <ref target="http://www.xulplanet.com/">
+ <ref target="http://www.xulplanet.com/">exTensible User Interface Language</ref>
+ </title>. Available at <ref target="http://www.xulplanet.com/">
http://www.xulplanet.com/</ref>.</bibl>
</listBibl>
</div>
Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -d -r1.127 -r1.128
--- its20.html 22 Aug 2012 13:41:49 -0000 1.127
+++ its20.html 22 Aug 2012 17:54:15 -0000 1.128
@@ -125,13 +125,14 @@
</div>
</div>
<h3><a name="appendices" id="appendices" shape="rect"/>Appendices</h3><div class="toc1">A <a href="#normative-references" shape="rect">References</a></div>
-<div class="toc1">B <a href="#informative-references" shape="rect">References</a> (Non-Normative)</div>
-<div class="toc1">C <a href="#its-markup-summary" shape="rect">Summary of ITS Markup</a> (Non-Normative)</div>
-<div class="toc1">D <a href="#its-schemas" shape="rect">Schemas for ITS</a> (Non-Normative)</div>
-<div class="toc1">E <a href="#its-schematron-constraints" shape="rect">Checking ITS Markup Constraints With Schematron</a> (Non-Normative)</div>
-<div class="toc1">F <a href="#its-nvdl-schema" shape="rect">Checking ITS Markup with NVDL</a> (Non-Normative)</div>
-<div class="toc1">G <a href="#revisionlog" shape="rect">Revision Log</a> (Non-Normative)</div>
-<div class="toc1">H <a href="#acknowledgements" shape="rect">Acknowledgements</a> (Non-Normative)</div>
+<div class="toc1">B <a href="#lqissue-typevalues" shape="rect">Values for the Localization Quality Issue Type</a></div>
+<div class="toc1">C <a href="#informative-references" shape="rect">References</a> (Non-Normative)</div>
+<div class="toc1">D <a href="#its-markup-summary" shape="rect">Summary of ITS Markup</a> (Non-Normative)</div>
+<div class="toc1">E <a href="#its-schemas" shape="rect">Schemas for ITS</a> (Non-Normative)</div>
+<div class="toc1">F <a href="#its-schematron-constraints" shape="rect">Checking ITS Markup Constraints With Schematron</a> (Non-Normative)</div>
+<div class="toc1">G <a href="#its-nvdl-schema" shape="rect">Checking ITS Markup with NVDL</a> (Non-Normative)</div>
+<div class="toc1">H <a href="#revisionlog" shape="rect">Revision Log</a> (Non-Normative)</div>
+<div class="toc1">I <a href="#acknowledgements" shape="rect">Acknowledgements</a> (Non-Normative)</div>
</div><hr/><div class="body"><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="introduction" id="introduction" shape="rect"/>1 Introduction</h2><p>
<em>This section is informative.</em>
@@ -143,8 +144,8 @@
for HTML5, serializations in <a href="http://www.w3.org/TR/xhtml-rdfa-primer/" shape="rect">RDFa</a> and
<a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF</a>, and the schema languages XML DTD <a title="Extensible Markup Language (XML)
								1.0 (Fourth Edition)" href="#xml10spec" shape="rect">[XML 1.0]</a>, XML Schema <a title="XML Schema Part 1:
								Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and
RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements document</a>, in
- <a title="Internationalization and
								Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a> and <a title="Requirements for Localizable DTD
								Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.</p><p>Not all requirements listed there are addressed in this document. Those which are not addressed here
- are either covered in <a title="Best Practices for XML
								Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a> (potentially in an as yet
+ <a title="Internationalization and
							Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a> and <a title="Requirements for Localizable DTD
						Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.</p><p>Not all requirements listed there are addressed in this document. Those which are not addressed here
+ are either covered in <a title="Best Practices for XML
						Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a> (potentially in an as yet
unwritten best practice document on multilingual Web content), or may be addressed in a future
version of this specification.</p><div class="div2">
<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="relation-to-its10-and-new-principles" id="relation-to-its10-and-new-principles" shape="rect"/>1.1 Relation to ITS 1.0 and New Principles</h3><div class="div3">
@@ -226,7 +227,7 @@
localization of content. The following paragraphs sketch these different types of users, and
their usage of ITS. In order to support all of these users, the information about what
markup should be supported to enable worldwide use and effective localization of content is
- provided in this specification in two ways:</p><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="div4">
+ provided in this specification in two ways:</p><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="div4">
<h5><a name="schema-dev-new" id="schema-dev-new" shape="rect"/>1.3.1.1Schema developers starting a schema from the ground up</h5><p>This type of user will find proposals for attribute and element names to be included in
their new schema (also called "host vocabulary"). Using the attribute and element names
proposed in the ITS specification may be helpful because it leads to easier recognition
@@ -238,7 +239,7 @@
<h5><a name="schema-dev-existing" id="schema-dev-existing" shape="rect"/>1.3.1.2Schema developers working with an existing schema</h5><p>This type of user will be working with schemas such as DocBook, DITA, or perhaps a
proprietary schema. The ITS Working Group has sought input from experts developing
widely used formats such as the ones mentioned.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The question "How to use ITS with existing popular markup schemes?" is covered in
- more details (including examples) in a separate document: <a title="Best Practices for XML
								Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p></div><p>Developers working on existing schemas should check whether their schemas support the
+ more details (including examples) in a separate document: <a title="Best Practices for XML
						Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p></div><p>Developers working on existing schemas should check whether their schemas support the
markup proposed in this specification, and, where appropriate, add the markup proposed
here to their schema.</p><p>In some cases, an existing schema may already contain markup equivalent to that
recommended in ITS. In this case it is not necessary to add duplicate markup since ITS
@@ -372,7 +373,7 @@
<xs:attributeGroup ref="commonAtts"/>
</xs:complexType>
</xs:element>
-</xs:schema></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-5.xsd" shape="rect">examples/xml/EX-ways-to-use-its-5.xsd</a>]</p></div><p>The first two approaches above can be likened to the use of CSS in <a title="XHTML™ 1.0 The Extensible
								HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>. Using a <code>style</code> attribute, an XHTML content author may assign
+</xs:schema></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-5.xsd" shape="rect">examples/xml/EX-ways-to-use-its-5.xsd</a>]</p></div><p>The first two approaches above can be likened to the use of CSS in <a title="XHTML™ 1.0 The Extensible
							HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>. Using a <code>style</code> attribute, an XHTML content author may assign
a color to a particular paragraph. That author could also have used the <code>style</code>
element at the top of the page to say that all paragraphs of a particular class or in a
particular context would be colored red.</p></div></div><div class="div2">
@@ -418,7 +419,7 @@
XML nodes the ITS-related information pertains to must be clearly defined. Thus, ITS defines
<a href="#termdef-selection" shape="rect">selection</a> mechanisms to specify to what parts of an
XML document an ITS data category and its values should be applied. Selection relies on the
- information which is given in the XML Information Set <a title="XML Information Set
								(Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>. ITS applications may implement inclusion mechanisms such as XInclude or DITA's <a title="OASIS
								Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> conref.</p><p>Content authors, for example, need a simple way to work with the <a href="#trans-datacat" shape="rect">Translate</a> data category in order to express whether the content of an element or
+ information which is given in the XML Information Set <a title="XML Information Set
								(Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>. ITS applications may implement inclusion mechanisms such as XInclude or DITA's <a title="OASIS
						Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> conref.</p><p>Content authors, for example, need a simple way to work with the <a href="#trans-datacat" shape="rect">Translate</a> data category in order to express whether the content of an element or
attribute should be translated or not. Localization managers, on the other hand, need an
efficient way to manage translations of large document sets based on the same schema. These
needs could by realized by a specification of defaults for the <a href="#trans-datacat" shape="rect">Translate</a> data category along with exceptions to those defaults (e.g. all <code>p</code>
@@ -435,11 +436,11 @@
<em>Ease of integration</em>:</p><ul><li><p> ITS follows the example from <a href="http://www.w3.org/TR/2001/REC-xlink-20010627/#att-method" shape="rect">section 4</a> of
<a title="XML Linking Language 1.1" href="#xlink1" shape="rect">[XLink 1.1]</a>, by providing mostly global attributes for the
implementation of ITS data categories. Avoiding elements for ITS purposes as much as
- possible ensures ease of integration into existing markup schemes, see <a href="http://www.w3.org/TR/itsreq/#impact" shape="rect">section 3.14</a> in <a title="Internationalization and
								Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a>. Only for some requirements do additional child elements have to be
+ possible ensures ease of integration into existing markup schemes, see <a href="http://www.w3.org/TR/itsreq/#impact" shape="rect">section 3.14</a> in <a title="Internationalization and
							Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a>. Only for some requirements do additional child elements have to be
used, see for example <a class="section-ref" href="#ruby-annotation" shape="rect">Section 6.6: Ruby</a>.</p></li><li><p>ITS has no dependency on technologies which are still under
development.</p></li><li><p>ITS fits with existing work in the W3C architecture (e.g. use of <a title="XML Path Language (XPath)
								Version 1.0" href="#xpath" shape="rect">[XPath 1.0]</a> for the selection mechanism).</p></li></ul></div><div class="div2">
<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="spec-development" id="spec-development" shape="rect"/>1.7 Development of this Specification</h3><p>This specification has been developed using the ODD (<em>One Document Does it all</em>)
- language of the Text Encoding Initiative (<a title="Text Encoding Initiative Guidelines
								development version (P5)" href="#tei" shape="rect">[TEI]</a>). This is a
+ language of the Text Encoding Initiative (<a title="Text Encoding Initiative Guidelines
							development version (P5)" href="#tei" shape="rect">[TEI]</a>). This is a
literate programming language for writing XML schemas, with three characteristics:</p><ol class="depth1"><li><p>The element and attribute set is specified using an XML vocabulary which includes support
for macros (like DTD entities, or schema patterns), a hierarchical class system for
attributes and elements, and creation of modules.</p></li><li><p>The content models for elements and attributes are written using embedded RELAX NG XML
@@ -455,7 +456,7 @@
<code>its:translate='yes'</code>) always pertains to one or more XML or HTML nodes (primarily
element and attribute nodes). In a sense, ITS markup “selects” the relevant node(s). Selection
may be explicit or implicit. ITS distinguishes two approaches to selection: (1) local, and (2)
- using global rules.</p><p>The mechanisms defined for ITS selection resemble those defined in <a title="Cascading Style Sheets, level 2
								revision 1 CSS 2.1 Specification" href="#css2-1" shape="rect">[CSS 2.1]</a>. The local approach can be compared to the <code>style</code> attribute in
+ using global rules.</p><p>The mechanisms defined for ITS selection resemble those defined in <a title="Cascading Style Sheets, level 2
							revision 1 CSS 2.1 Specification" href="#css2-1" shape="rect">[CSS 2.1]</a>. The local approach can be compared to the <code>style</code> attribute in
HTML/XHTML, and the approach with global rules is similar to the <code>style</code> element in
HTML/XHTML. ITS usually uses XPath for identifying nodes although CSS and other query languages
can be used if supported by application. Thus,</p><ul><li><p>the local approach puts ITS markup in the relevant element of the host vocabulary (e.g.
@@ -496,7 +497,7 @@
process this content for translation will need to implement the expected inheritance.</p></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="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.1.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 11</a> shows a different approach
to identifying non-translatable content, similar to that used with a <code>style</code> element
- in <a title="XHTML™ 1.0 The Extensible
								HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an ITS-defined element called
+ in <a title="XHTML™ 1.0 The Extensible
							HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an ITS-defined element called
<a class="itsmarkup" href="#rules" shape="rect">rules</a>. It works as follows: A document can contain a <a class="itsmarkup" href="#rules" shape="rect">rules</a> element
(placed where it does not impact the structure of the document, e.g., in a “head” section).
It contains one or more ITS rule elements (for example <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a>). Each of
@@ -613,7 +614,7 @@
localization of XML schemas and documents.] The concept of a data category is
independent of its implementation in an XML environment (e.g. using an element or
attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "markup declarations" subsections in
- <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1159" id="d3e1159" shape="rect"/>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as to
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1159" id="d3e1159" shape="rect"/>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as to
whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language independent level
is a <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute with two possible values: "yes"
and "no". An implementation on a schema language specific level would be the
@@ -628,7 +629,7 @@
<a href="#def-adding-pointing" shape="rect">added</a> to the selected nodes, or it can <a href="#def-adding-pointing" shape="rect">point to existing information</a> which is related to
selected nodes. </p><p id="selection-and-inclusion-mechanisms">Selection relies on the information that is given in
the XML Information Set <a title="XML Information Set
								(Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>. ITS applications <a href="#rfc-keywords" shape="rect">MAY</a> implement inclusion mechanisms such as XInclude or DITA's
- <a title="OASIS
								Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> conref.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="note-object-selection">The selection of the ITS data categories applies to textual
+ <a title="OASIS
						Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> conref.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="note-object-selection">The selection of the ITS data categories applies to textual
values contained within element or attribute nodes. In some cases these nodes form pointers
to other resources; a well-known example is the <code>src</code> attribute on the <code>img</code>
element in HTML. The ITS <a href="#trans-datacat" shape="rect">Translate</a> data category applies
@@ -647,7 +648,7 @@
</text></pre></div><p>[Source file: <a href="examples/xml/EX-notation-terminology-1.xml" shape="rect">examples/xml/EX-notation-terminology-1.xml</a>]</p></div></div></div><div class="div2">
<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="iri-usage" id="iri-usage" shape="rect"/>3.5 Usage of Internationalized Resource Identifiers in ITS</h3><p>The attributes <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a>, <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNoteRef</a> and <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoRef</a> which contain resource identifiers <a href="#rfc-keywords" shape="rect">MUST</a>
allow the usage of Internationalized Resource Identifiers (IRIs, <a title="Internationalized Resource Identifiers
								(IRIs)" href="#rfc3987" shape="rect">[RFC 3987]</a> or its successor) to ease the adoption of ITS in international application
- scenarios.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The ITS schemas in <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a> are not normative. Hence
+ scenarios.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The ITS schemas in <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a> are not normative. Hence
this specification defines no validation requirements for IRI values in ITS markup. For
processing of these values, relying on IRIs imposes no specific requirements. The reason is
that the processing happens on the info set level <a title="XML Information Set
								(Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>, where no difference between IRIs and URIs exists.</p></div></div></div><div class="div1">
@@ -674,7 +675,7 @@
it <a href="#rfc-keywords" shape="rect">MUST</a> be part of the content model of at least one
element declared in the schema. It <a href="#rfc-keywords" shape="rect">SHOULD</a> be in a
content model for meta information, if this is available in that schema (e.g. the
- <code>head</code> element in <a title="XHTML™ 1.0 The Extensible
								HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>).</p></li><li><p id="its-conformance-1-3">
+ <code>head</code> element in <a title="XHTML™ 1.0 The Extensible
							HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>).</p></li><li><p id="its-conformance-1-3">
<em>1-3:</em> If the <a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element is used, it
<a href="#rfc-keywords" shape="rect">SHOULD</a> be declared as an inline
element.</p></li><li><p id="its-conformance-1-4">
@@ -683,13 +684,13 @@
element.</p></li></ul><p id="its-markup-conformance-claims">Full implementations of this conformance type will
implement all markup declarations for ITS. Statements related to this conformance type <a href="#rfc-keywords" shape="rect">MUST</a> list all markup declarations they implement.</p><p>
<em>Examples: </em> Examples of the usage of ITS markup declarations in various existing
- schemas are given in a separate document <a title="Best Practices for XML
								Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Since the ITS markup declarations are schema language independent, each schema language can
+ schemas are given in a separate document <a title="Best Practices for XML
						Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Since the ITS markup declarations are schema language independent, each schema language can
use its own, possibly multiple, mechanisms to implement the conformance clauses for ITS
markup declarations. For example, an XML DTD can use parameter entities to encapsulate the
<a href="#span.attributes" shape="rect">ITS local attributes</a>, or declare them directly for
each element. The appropriate steps to integrate ITS into a schema depend on the design of
this schema (e.g. whether it already has a customization layer that uses parameter
- entities). The ITS schemas in the format of XML DTD, XML Schema and RELAX NG in <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a> are only informative examples.</p></div></div><div class="div2">
+ entities). The ITS schemas in the format of XML DTD, XML Schema and RELAX NG in <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a> are only informative examples.</p></div></div><div class="div2">
<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="conformance-product-processing-expectations" id="conformance-product-processing-expectations" shape="rect"/>4.2 Conformance Type 2: The Processing Expectations for ITS Markup</h3><p>
<em>Description:</em> Processors need to compute the ITS information that pertains to a node
in an XML document. The ITS processing expectations define how the computation has to be carried
@@ -1028,7 +1029,7 @@
<a class="itsmarkup" href="#rules" shape="rect">rules</a> element)</p><p>Inside each <a class="itsmarkup" href="#rules" shape="rect">rules</a> element the precedence order is: </p><ol class="depth2"><li><p>Any rule inside the rules element</p></li><li><p>Any rule linked via the XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute</p></li><li><p><span class="editor-note">[Ed. note: Define how HTML5 link works with precedence.]</span></p></li></ol><p>
</p><div class="note"><p class="prefix"><b>Note:</b></p><p>If identical selections are defined in different rules elements within one
document, the selection defined by the last takes precedence.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>ITS does not define precedence related to rules defined or linked based on non-ITS
- mechanisms (such as processing instructions for linking rules).</p></div></li><li><p>Selections via defaults for data categories, see <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a></p></li></ol><p>In case of conflicts between global selections via multiple <a href="#selection-global" shape="rect">rules</a> elements, the last rule has higher precedence.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The precedence order fulfills the same purpose as the built-in template rules of <a title="XSL Transformations (XSLT) Version
								1.0" href="#xslt10" shape="rect">[XSLT 1.0]</a>. Override semantics are always complete, that is all
+ mechanisms (such as processing instructions for linking rules).</p></div></li><li><p>Selections via defaults for data categories, see <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a></p></li></ol><p>In case of conflicts between global selections via multiple <a href="#selection-global" shape="rect">rules</a> elements, the last rule has higher precedence.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The precedence order fulfills the same purpose as the built-in template rules of <a title="XSL Transformations (XSLT) Version
							1.0" href="#xslt10" shape="rect">[XSLT 1.0]</a>. Override semantics are always complete, that is all
information that is specified in one rule element is overridden by the next one.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2838" id="d3e2838" shape="rect"/>Example 22: Conflicts between selections of ITS information which are resolved using the precedence
order</div><p>The two elements <code>title</code> and <code>author</code> of this document should be treated as
separate content when inside a <code>prolog</code> element, but as part of the content of their
@@ -1058,7 +1059,7 @@
categories can be associated with such existing markup, using the global selection mechanism
described in <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>.</p><p>Associating existing markup with ITS data categories can be done only if the processing
expectations of the host markup are the same as, or greater than, those of ITS. For example, the
- <a title="OASIS
								Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> format can use its translate attribute to apply to
+ <a title="OASIS
						Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> format can use its translate attribute to apply to
“transcluded” content, going beyond the ITS 2.0 local selection mechanism, but not contradicting
it.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-associating-its-with-existing-markup-1" id="EX-associating-its-with-existing-markup-1" shape="rect"/>Example 23: Association of the ITS data categories <a href="#trans-datacat" shape="rect"> Translate</a> and
<a href="#terminology" shape="rect">Terminology</a> with DITA 1.0 markup</div><p>In this example, there is an existing <code>translate</code> attribute in DITA, and it is
@@ -1501,7 +1502,7 @@
</p></li><li><p>Data category value: "rlo" (right-to-left text)</p><p>CSS rule:
<code>*[dir="rlo"] { unicode-bidi: bidi-override; direction:
rtl}</code>
- </p></li></ul><p>More information about how to use this data category is provided by <a title="What you need to
								know about the bidi algorithm and inline markup" href="#bidiarticle" shape="rect">[Bidi Article]</a>.</p></div></div><div class="div3">
+ </p></li></ul><p>More information about how to use this data category is provided by <a title="What you need to
							know about the bidi algorithm and inline markup" href="#bidiarticle" shape="rect">[Bidi Article]</a>.</p></div></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="directionality-implementation" id="directionality-implementation" shape="rect"/>6.5.2 Implementation</h4><span class="editor-note">[Ed. note: Examples for HTML5 need to be added; some values need to added to <code>dir</code>
to reflect HTML5.]</span><p>The <a href="#directionality" shape="rect">Directionality</a> data category can be expressed with
global rules, or locally on an individual element. The information applies to the textual
@@ -1597,7 +1598,7 @@
</its:ruby>の歴史を説明するものです。</p>
</body>
</text></pre></div><p>[Source file: <a href="examples/xml/EX-ruby-implementation-1.xml" shape="rect">examples/xml/EX-ruby-implementation-1.xml</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The structure of the content model for the <a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element is identical with the
- structure of ruby markup as defined in <a title="HTML5 – A vocabulary and associated APIs for HTML
								and XHTML" href="#html5" shape="rect">[HTML5]</a>.</p><p>The structure of ruby defined in section 5.4 of <a title="OASIS Open
								Document Format for Office Applications (OpenDocument)." href="#opendocument" shape="rect">[OpenDocument]</a> is also compliant with ruby defined in this specification.</p></div><span class="editor-note">[Ed. note: Need to reevaluate above statement related to ODF.]</span></div><div class="div3">
+ structure of ruby markup as defined in <a title="HTML5 – A vocabulary and associated APIs for HTML
							and XHTML" href="#html5" shape="rect">[HTML5]</a>.</p><p>The structure of ruby defined in section 5.4 of <a title="OASIS Open
							Document Format for Office Applications (OpenDocument)." href="#opendocument" shape="rect">[OpenDocument]</a> is also compliant with ruby defined in this specification.</p></div><span class="editor-note">[Ed. note: Need to reevaluate above statement related to ODF.]</span></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="ruby-markup" id="ruby-markup" shape="rect"/>6.6.3 Markup Declarations for Ruby</h4><dl><dt class="label">rubyRule</dt><dd><table class="scrap" summary="Scrap"><tbody><tr valign="baseline"><td rowspan="1" colspan="1"><a name="rubyRule" id="rubyRule" shape="rect"/>[79] </td><td rowspan="1" colspan="1"><code>rubyRule</code></td><td rowspan="1" colspan="1"> ::= </td><td rowspan="1" colspan="1"><code> element its:rubyRule { rubyRule.content, <a href="#rubyRule.attributes" shape="rect">rubyRule.attributes</a> }</code></td></tr></tbody><tbody><tr valign="baseline"><td rowspan="1" colspan="1"><a name="rubyRule.content" id="rubyRule.content" shape="rect"/>[80] </td><td rowspan="1" colspan="1"><code>rubyRule.content</code></td><td rowspan="1" colspan="1"> ::= </td><td rowspan="1" colspan="1"><code>
<a href="#rubyText" shape="rect">rubyText</a>?</code></td></tr></tbody><tbody><tr valign="baseline"><td rowspan="1" colspan="1"><a name="rubyRule.attributes" id="rubyRule.attributes" shape="rect"/>[81] </td><td rowspan="1" colspan="1"><code>rubyRule.attributes</code></td><td rowspan="1" colspan="1"> ::= </td><td rowspan="1" colspan="1"><code>
@@ -1640,7 +1641,7 @@
<code>xml:lang</code> is the standard way to specify language information in XML.
<code>xml:lang</code> is defined in terms of <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#sec-lang-tag" shape="rect">RFC 3066 or its
successor</a> (<a title="Tags for Identifying
								Languages" href="#bcp47" shape="rect">[BCP47]</a> is the "Best Common Practice"
- for language identification and encompasses <a title="Tags for the Identification of
								Languages" href="#rfc3066" shape="rect">[RFC 3066]</a> and
+ for language identification and encompasses <a title="Tags for the Identification of
						Languages" href="#rfc3066" shape="rect">[RFC 3066]</a> and
its successors.)</p></div><span class="editor-note">[Ed. note: Add something about HTML5 lang]</span></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="langinfo-implementation" id="langinfo-implementation" shape="rect"/>6.7.2 Implementation</h4><p>The <a href="#language-information" shape="rect">Language Information</a> data category can be
expressed only with global rules. The information applies to the textual content of the
@@ -1654,11 +1655,11 @@
information is for example relevant to provide basic text segmentation hints for tools such
as translation memory systems. The values associated with this data category are:</p><ul><li><p>
"yes" : The element and its content are part of the flow of its parent
- element. For example the element <code>strong</code> in <a title="XHTML™ 1.0 The Extensible
								HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>:</p><p>
+ element. For example the element <code>strong</code> in <a title="XHTML™ 1.0 The Extensible
							HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>:</p><p>
<code><strong>Appaloosa horses</strong> have spotted coats.</code>
</p></li><li><p>
"nested" : The element is part of the flow of its parent element, its
- content is an independent flow. For example the element <code>fn</code> in <a title="OASIS
								Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a>:</p><p>
+ content is an independent flow. For example the element <code>fn</code> in <a title="OASIS
						Darwin Information Typing Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a>:</p><p>
<code>Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn>
have spotted coats.</code>
</p></li><li><p>
@@ -2147,7 +2148,7 @@
translation engines.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>In general, it is recommended to avoid developing formats where the same content is
stored in different languages in the same document, unless for very specific use cases.
See the best practices “<a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#DevMLDoc" shape="rect">Working
- with multilingual documents</a>” from <a title="Best Practices for XML
								Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a> for further guidance.</p></div></div><div class="div3">
+ with multilingual documents</a>” from <a title="Best Practices for XML
						Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a> for further guidance.</p></div></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="target-pointer-implementation" id="target-pointer-implementation" shape="rect"/>6.15.2 Implementation</h4><p>The <a href="#target-pointer" shape="rect">Target Pointer</a> data category can be expressed only
with global rules. The information applies to the textual content of the element. There is
no inheritance. There is no default.</p><p id="targetpointer-global">GLOBAL: The <a class="itsmarkup" href="#targetPointerRule" shape="rect">targetPointerRule</a> element contains the following:</p><ul><li><p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> which selects the nodes to which this rule applies.</p></li><li><p>A required <a class="itsmarkup" href="#targetPointerRule.attributes" shape="rect">targetPointer</a> attribute. It contains a <a href="#selectors" shape="rect">relative selector</a> that points to the node for the target content
@@ -2183,7 +2184,7 @@
<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="idvalue" id="idvalue" shape="rect"/>6.16 Id Value</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="idvalue-definition" id="idvalue-definition" shape="rect"/>6.16.1 Definition</h4><p>The <a href="#idvalue" shape="rect">Id Value</a> data category indicates a value that can be used as
unique identifier for a given part of the content.</p><p>The recommended way to specify a unique identifier is to use <code>xml:id</code> (See the best
- practice “<a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#DevUniqueID" shape="rect">Defining markup for unique identifiers</a>” from <a title="Best Practices for XML
								Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>). The <a class="itsmarkup" href="#idValueRule" shape="rect">idValueRule</a> element is intended only as a fall-back
+ practice “<a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#DevUniqueID" shape="rect">Defining markup for unique identifiers</a>” from <a title="Best Practices for XML
						Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>). The <a class="itsmarkup" href="#idValueRule" shape="rect">idValueRule</a> element is intended only as a fall-back
mechanism for documents where unique identifiers are available with another construct.</p><p>Providing a unique identifier that is maintained in the original document can be use for
several purposes, for example:</p><ul><li><p>Allow automated alignment between different versions of the source document, or
between source and translated documents.</p></li><li><p>Improve the confidence in leveraged translation for exact matches.</p></li><li><p>Provide back-tracking information between displayed text and source material when
@@ -2387,9 +2388,8 @@
locQualityIssueSeverity="50"/>
</its:rules></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssueRule-html5-global.xml" shape="rect">examples/html5/EX-locQualityIssueRule-html5-global.xml</a>]</p></div><p id="lqissue-local">LOCAL: Using the inline markup to represent the data category locally is limited to a single
occurrence for a given content (e.g. one cannot have different <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueType" shape="rect">locQualityIssueType</a> attributes applied
- to the same span of text because the inner-most one would override the others). Because there may be several
- instances of a localization quality issue for a given ontent, a local <em>standoff markup</em> allowing
- such cases is also provided.</p><p>The following local markup is available for the Localization Quality Issue data category:</p><ul><li><p>Either (inline markup):</p><ul><li><p>At least one of the following attributes:</p><ul><li><p>A <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueType" shape="rect">locQualityIssueType</a> attribute that implements the
+ to the same span of text because the inner-most one would override the others).
+ A local <em>standoff markup</em> is provided to allow such cases.</p><p>The following local markup is available for the Localization Quality Issue data category:</p><ul><li><p>Either (inline markup):</p><ul><li><p>At least one of the following attributes:</p><ul><li><p>A <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueType" shape="rect">locQualityIssueType</a> attribute that implements the
<a href="#lqissueDefs" shape="rect">type information</a>.</p></li><li><p>A <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueComment" shape="rect">locQualityIssueComment</a> attribute that implements the
<a href="#lqissueDefs" shape="rect">comment information</a>.</p></li></ul></li><li><p>An optional <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueSeverity" shape="rect">locQualityIssueSeverity</a> attribute that implements the
<a href="#lqissueDefs" shape="rect">severity information</a>.</p></li><li><p>An optional <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueProfileRef" shape="rect">locQualityIssueProfileRef</a> attribute that implements the
@@ -2413,82 +2413,38 @@
its:locQualityIssueType="typographical"
its:locQualityIssueComment="Sentence without capitalization"
its:locQualityIssueSeverity="50">this</span> is an example</para>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-1.xml" shape="rect">examples/xml/EX-locQualityIssue-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-local-1" id="EX-locQualityIssue-html5-local-1" shape="rect"/>Example 72: Annotating an issue in HTML with local inline markup</div><p>In this example several spans of content are assocaited with a quality issue.</p><div class="exampleInner"><pre xml:space="preserve">
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-1.xml" shape="rect">examples/xml/EX-locQualityIssue-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-local-1" id="EX-locQualityIssue-html5-local-1" shape="rect"/>Example 72: Annotating an issue in HTML with local inline markup</div><p>In this example several spans of content are associated with a quality issue.</p><div class="exampleInner"><pre xml:space="preserve">
<html lang="en">
<head>
<title>Telharmonium 1897</title>
<style type="text/css">
- [its-loc-quality-type]{
- border:1px solid green;
- margin:2px;
- }
- [its-loc-quality-issue-type = untranslated]{
- background-color:red;
- }
- [its-loc-quality-issue-type = whitespace]{
+ [its-loc-quality-issue-type]{
background-color:yellow;
- }
- [its-loc-quality-issue-type = inconsistent-entities]{
- background-color:#9DFFE1;
- }
- [its-loc-quality-issue-type = spelling]{
- background-color:#FFE2F7;
+ margin:2px;
}
[its-loc-quality-issue-severity = "100"]{
- border: 6px solid red;
- }
- [its-loc-quality-issue-profile-ref = "abc"]:before{
- content:"⇛";
- }
- [its-loc-quality-issue-profile-ref = "abc"]:after{
- content:"⇚";
- }
- [its-loc-quality-issue-profile-ref = "grammar"]:before{
- content:"❮";
- }
- [its-loc-quality-issue-profile-ref = "grammar"]:after{
- content:"❯";
+ border: 2px solid red;
}
</style>
</head>
<body>
- <h1
- id="h0001"
- its-loc-quality-issue-profile-ref="abc"
- its-loc-quality-issue-type="untranslated"
- data-mytool-qacode="target_equals_source">Telharmonium (1897)</h1>
- <p id="p0001">
- <span class="segment" id="s0001">
- <span
- its-loc-quality-issue-profile-ref="abc"
- its-loc-quality-issue-type="inconsistent-entities"
- its-loc-quality-issue-comment="Should be Thomas Cahill. Why is Batman in the picture?"
- its-loc-quality-issue-severity="100"
- data-mytool-qacode="named_entity_not_found">Christian Bale</span>
- <span
- its-loc-quality-issue-profile-pointer="abc"
- its-loc-quality-issue-type="whitespace"
- its-loc-quality-issue-severity="10"
- data-mytool-qacode="extra_space_around_punctuation">(1867 – 1934)</span>
- conceived of an instrument that could transmit its
- sound from a power plant for hundreds of miles to
- listeners over telegraph wiring.
- </span>
- <span class="segment" id="s0002">Beginning in 1889 the sound
- quality of regular telephone concerts was very poor on
- account of the buzzing generated by carbon-granule
- microphones. As a result Cahill decided to set a new
- standard in perfection of sound
- <span
- its-loc-quality-issue-profile-ref="grammar"
- its-loc-quality-issue-type="spelling"
- its-loc-quality-issue-severity="50"
- its-loc-quality-issue-comment="should be "quality"">qulaity</span>
- with his instrument, a standard that would not only satisfy
- listeners but that would overcome all the flaws of traditional
- instruments.
- </span>
- </p>
+ <h1>Telharmonium (1897)</h1>
+ <p>
+ <span
+ its-loc-quality-issue-profile-ref="http://example.org/qaMovel/v1"
+ its-loc-quality-issue-type="inconsistent-entities"
+ its-loc-quality-issue-comment="Should be Thomas Cahill."
+ its-loc-quality-issue-severity="100"
+ data-mytool-qacode="named_entity_not_found">Christian Bale</span>(1867–1934) conceived of an instrument that could transmit its sound
+ from a power plant for hundreds of miles to listeners over telegraph wiring. Beginning in
+ 1889 the sound quality of regular telephone concerts was very poor on account of the buzzing
+ generated by carbon-granule microphones. As a result Cahill decided to set a new standard in
+ perfection of sound <span
+ its-loc-quality-issue-profile-ref="grammar"
+ its-loc-quality-issue-type="spelling"
+ its-loc-quality-issue-severity="50"
+ its-loc-quality-issue-comment="should be "quality"">qulaity</span> with his instrument, a standard that would not only satisfy listeners but that
+ would overcome all the flaws of traditional instruments.</p>
</body>
</html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-local-1.html" shape="rect">examples/html5/EX-locQualityIssue-html5-local-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-2" id="EX-locQualityIssue-local-2" shape="rect"/>Example 73: Annotating an issue in XML with local standoff markup</div><p>The following example shows a document using local standoff markup to encode several issues.
The <code>mrk</code> element delimits the content to markup and holds a <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssuesRef" shape="rect">locQualityIssuesRef</a>
@@ -2562,145 +2518,7 @@
its-loc-quality-issue-severity="30"/>
</span>
</body>
-</html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-local-2.html" shape="rect">examples/html5/EX-locQualityIssue-html5-local-2.html</a>]</p></div><span class="editor-note">[Ed. note: TODO for above: Finalize how HTML its-loc-quality-issues and its-loc-quality-issue should be defined.]</span><p id="lqissue-typevalues">Values for the Localization Quality Issue Type:</p><p>The <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueType" 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="#att.locqualityissue.attribute.locQualityIssueType" 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>untranslated</code>
- </td><td rowspan="1" colspan="1">Content that should have been translated was left untranslated.</td><td rowspan="1" colspan="1">
- <ul><li><p>The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian
- localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer."</p></li></ul>
- </td><td rowspan="1" colspan="1">T</td><td rowspan="1" colspan="1">
- <code>omission</code> takes precedence over <code>untranslated</code>. Omissions are distinct in
- that they address cases where text is not present, while <code>untranslated</code> addresses cases
- where text has been carried from the source untranslated.</td></tr><tr><td rowspan="1" colspan="1">
- <code>addition</code>
- </td><td rowspan="1" colspan="1">The translated text contains inappropriate additions.</td><td rowspan="1" colspan="1">
- <ul><li><p>The translated text contains a note from the translator to himself to look up a term; the note should have
- been deleted but was not.</p></li></ul>
- </td><td rowspan="1" colspan="1">T</td><td rowspan="1" colspan="1"/></tr><tr><td rowspan="1" colspan="1">
- <code>duplication</code>
- </td><td rowspan="1" colspan="1">Content has been duplicated improperly.</td><td rowspan="1" colspan="1">
- <ul><li><p>A section of the target text was inadvertently copied twice in a copy and 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 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>
- </td><td rowspan="1" colspan="1">S+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 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>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="#att.locqualityissue.attribute.locQualityIssueProfileRef" 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">
+</html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-local-2.html" shape="rect">examples/html5/EX-locQualityIssue-html5-local-2.html</a>]</p></div><span class="editor-note">[Ed. note: TODO for above: Finalize how HTML its-loc-quality-issues and its-loc-quality-issue should be defined.]</span></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><span class="editor-note">[Ed. note: TODO: update to proper declaration and add markup for HTML.]</span><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
{
@@ -2894,52 +2712,191 @@
Version 1.0</cite></a>. W3C Recommendation 16 November 1999. Available at <a href="http://www.w3.org/TR/1999/REC-xpath-19991116/" shape="rect">
http://www.w3.org/TR/1999/REC-xpath-19991116/</a>. The latest version of <a href="http://www.w3.org/TR/xpath/" shape="rect">XPath 1.0</a> is available at
http://www.w3.org/TR/xpath/ .</dd></dl></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="informative-references" id="informative-references" shape="rect"/>B References (Non-Normative)</h2><dl><dt class="label"><a name="bidiarticle" id="bidiarticle" shape="rect"/>Bidi Article</dt><dd>Richard Ishida. <a href="http://www.w3.org/International/articles/inline-bidi-markup/" shape="rect"><cite>What you need to
- know about the bidi algorithm and inline markup</cite></a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>, June
+<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"/>B Values for the Localization Quality Issue Type</h2><p>The <a class="itsmarkup" href="#att.locqualityissue.attribute.locQualityIssueType" 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="#att.locqualityissue.attribute.locQualityIssueType" 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>untranslated</code>
+ </td><td rowspan="1" colspan="1">Content that should have been translated was left untranslated.</td><td rowspan="1" colspan="1">
+ <ul><li><p>The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian
+ localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer."</p></li></ul>
+ </td><td rowspan="1" colspan="1">T</td><td rowspan="1" colspan="1">
+ <code>omission</code> takes precedence over <code>untranslated</code>. Omissions are distinct in
+ that they address cases where text is not present, while <code>untranslated</code> addresses cases
+ where text has been carried from the source untranslated.</td></tr><tr><td rowspan="1" colspan="1">
+ <code>addition</code>
+ </td><td rowspan="1" colspan="1">The translated text contains inappropriate additions.</td><td rowspan="1" colspan="1">
+ <ul><li><p>The translated text contains a note from the translator to himself to look up a term; the note should have
+ been deleted but was not.</p></li></ul>
+ </td><td rowspan="1" colspan="1">T</td><td rowspan="1" colspan="1"/></tr><tr><td rowspan="1" colspan="1">
+ <code>duplication</code>
+ </td><td rowspan="1" colspan="1">Content has been duplicated improperly.</td><td rowspan="1" colspan="1">
+ <ul><li><p>A section of the target text was inadvertently copied twice in a copy and 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 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>
+ </td><td rowspan="1" colspan="1">S+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 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>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="#att.locqualityissue.attribute.locQualityIssueProfileRef" 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="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="informative-references" id="informative-references" shape="rect"/>C References (Non-Normative)</h2><dl><dt class="label"><a name="bidiarticle" id="bidiarticle" shape="rect"/>Bidi Article</dt><dd>Richard Ishida. <a href="http://www.w3.org/International/articles/inline-bidi-markup/" shape="rect"><cite>What you need to
+ know about the bidi algorithm and inline markup</cite></a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>, June
2005.</dd><dt class="label"><a name="css2-1" id="css2-1" shape="rect"/>CSS 2.1</dt><dd> Bert Bos, Tantek Çelik, Ian Hickson Håkon Wium Lie. <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/" shape="rect"><cite>Cascading Style Sheets, level 2
- revision 1 CSS 2.1 Specification</cite></a>. W3C Recommendation 7 June 2011. Available at <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/" shape="rect">
- http://www.w3.org/TR/2011/REC-CSS2-20110607/</a>. The latest version of <a href="http://www.w3.org/TR/CSS21/" shape="rect">CSS2</a> is available at
+ revision 1 CSS 2.1 Specification</cite></a>. W3C Recommendation 7 June 2011. Available at <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/" shape="rect">
+ http://www.w3.org/TR/2011/REC-CSS2-20110607/</a>. The latest version of <a href="http://www.w3.org/TR/CSS21/" shape="rect">CSS2</a> is available at
http://www.w3.org/TR/CSS21/.</dd><dt class="label"><a name="dita10" id="dita10" shape="rect"/>DITA 1.0</dt><dd>Michael Priestley, JoAnn Hackos, et. al., editors. <a href=" https://www.oasis-open.org/committees/download.php/15316/dita10.zip" shape="rect"><cite>OASIS
- Darwin Information Typing Architecture (DITA) Language Specification v1.0</cite></a>.
+ Darwin Information Typing Architecture (DITA) Language Specification v1.0</cite></a>.
OASIS Standard 9 May 2005. Available at <a href=" https://www.oasis-open.org/committees/download.php/15316/dita10.zip" shape="rect">
https://www.oasis-open.org/committees/download.php/15316/dita10.zip</a>.</dd><dt class="label"><a name="docbook" id="docbook" shape="rect"/>DocBook</dt><dd>Norman Walsh and Leonard Muellner. <a href="http://www.docbook.org/" shape="rect"><cite>DocBook: The Definitive Guide</cite></a>. Available at <a href="http://www.docbook.org/" shape="rect">
http://www.docbook.org/</a>.</dd><dt class="label"><a name="geo-i18n-l10n" id="geo-i18n-l10n" shape="rect"/>l10n i18n</dt><dd>Richard Ishida, Susan Miller. <a href="http://www.w3.org/International/questions/qa-i18n" shape="rect">Localization vs.
- Internationalization</a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>, January 2006.</dd><dt class="label"><a name="html5" id="html5" shape="rect"/>HTML5</dt><dd>Ian Hickson <a href="http://www.w3.org/TR/html5/" shape="rect"><cite>HTML5 – A vocabulary and associated APIs for HTML
- and XHTML</cite></a>. W3C Working Draft 29 March 2012. Available at <a href="http://www.w3.org/TR/html5/" shape="rect">http://www.w3.org/TR/html5/</a>. </dd><dt class="label"><a name="iso30042" id="iso30042" shape="rect"/>ISO 30042</dt><dd>(International Organization for Standardization).
- <cite>TermBase eXchange (TBX)</cite>. [Geneva]: International Organization for
+ Internationalization</a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>, January 2006.</dd><dt class="label"><a name="html5" id="html5" shape="rect"/>HTML5</dt><dd>Ian Hickson <a href="http://www.w3.org/TR/html5/" shape="rect"><cite>HTML5 – A vocabulary and associated APIs for HTML
+ and XHTML</cite></a>. W3C Working Draft 29 March 2012. Available at <a href="http://www.w3.org/TR/html5/" shape="rect">http://www.w3.org/TR/html5/</a>. </dd><dt class="label"><a name="iso30042" id="iso30042" shape="rect"/>ISO 30042</dt><dd>(International Organization for Standardization).
+ <cite>TermBase eXchange (TBX)</cite>. [Geneva]: International Organization for
Standardization, 2008.</dd><dt class="label"><a name="itsreq" id="itsreq" shape="rect"/>ITS REQ</dt><dd>Yves Savourel. <a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/" shape="rect"><cite>Internationalization and
- Localization Markup Requirements</cite></a>. W3C Working Draft 18 May 2006. Available at <a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/" shape="rect">
- http://www.w3.org/TR/2006/WD-itsreq-20060518/</a>. The latest version of <a href="http://www.w3.org/TR/itsreq/" shape="rect">ITS REQ</a> is available at
+ Localization Markup Requirements</cite></a>. W3C Working Draft 18 May 2006. Available at <a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/" shape="rect">
+ http://www.w3.org/TR/2006/WD-itsreq-20060518/</a>. The latest version of <a href="http://www.w3.org/TR/itsreq/" shape="rect">ITS REQ</a> is available at
http://www.w3.org/TR/itsreq/.</dd><dt class="label"><a name="reqlocdtd" id="reqlocdtd" shape="rect"/>Localizable DTDs</dt><dd>Richard Ishida, Yves Savourel <a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect"><cite>Requirements for Localizable DTD
- Design</cite></a>. Working Draft 7 July 2003. Available at <a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="css3-selectors" id="css3-selectors" shape="rect"/>CSS Selectors Level 3</dt><dd>Tantek Çelik, Elika J. Etemad, Daniel
+ Design</cite></a>. Working Draft 7 July 2003. Available at <a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="css3-selectors" id="css3-selectors" shape="rect"/>CSS Selectors Level 3</dt><dd>Tantek Çelik, Elika J. Etemad, Daniel
Glazman, Ian Hickson, Peter Linss, John Williams <a href="http://www.w3.org/TR/css3-selectors/" shape="rect"><cite>Selectors Level 3</cite></a>. W3C Recommendation 29 September 2011. Available at <a href="http://www.w3.org/TR/css3-selectors/" shape="rect">http://www.w3.org/TR/css3-selectors/</a>.</dd><dt class="label"><a name="nvdl" id="nvdl" shape="rect"/>NVDL</dt><dd>Information technology -- Document Schema Definition Languages (DSDL)
-- Part 4: <cite>Namespace-based Validation Dispatching Language (NVDL)</cite>. International
Organization for Standardization (ISO) ISO/IEC 19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument" shape="rect"/>OpenDocument</dt><dd>Michael Brauer et al. <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect"><cite>OASIS Open
- Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
- https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>. The latest version
+ Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
+ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>. The latest version
of <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
OpenDocument</a> is available at
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="rfc3066" id="rfc3066" shape="rect"/>RFC 3066</dt><dd>Harald Alvestrand. <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect"><cite>Tags for the Identification of
- Languages</cite></a>. RFC 3066, January 2001. Available at <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect">http://www.ietf.org/rfc/rfc3066.txt</a>.</dd><dt class="label"><a name="ruby-tr" id="ruby-tr" shape="rect"/>Ruby-TR</dt><dd>Marcin Sawicki (until 10 October, 1999), Michel Suignard,
+ Languages</cite></a>. RFC 3066, January 2001. Available at <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect">http://www.ietf.org/rfc/rfc3066.txt</a>.</dd><dt class="label"><a name="ruby-tr" id="ruby-tr" shape="rect"/>Ruby-TR</dt><dd>Marcin Sawicki (until 10 October, 1999), Michel Suignard,
Masayasu Ishikawa (石川 雅康), Martin Dürst, Tex Texin, <a href="http://www.w3.org/TR/ruby/" shape="rect"><cite>Ruby Annotation</cite></a>. W3C Recommendation 31 May 2001. Available at <a href="http://www.w3.org/TR/2001/REC-ruby-20010531/" shape="rect">
http://www.w3.org/TR/2001/REC-ruby-20010531/ </a>. The latest version of <a href="http://www.w3.org/TR/ruby/" shape="rect">Ruby Annotation</a> is available at
http://www.w3.org/TR/ruby/.</dd><dt class="label"><a name="schematron" id="schematron" shape="rect"/>Schematron</dt><dd>Information technology -- Document Schema Definition
Languages (DSDL) -- Part 3: <cite>Rule-based validation -- Schematron</cite>. International
Organization for Standardization (ISO) ISO/IEC 19757-3:2003.</dd><dt class="label"><a name="tei" id="tei" shape="rect"/>TEI</dt><dd>Lou Burnard and Syd Bauman (eds). <a href="http://www.tei-c.org/Guidelines/P5/" shape="rect"><cite>Text Encoding Initiative Guidelines
- development version (P5)</cite></a>. TEI Consortium, Charlottesville, Virginia, USA, Text Encoding Initiative.</dd><dt class="label"><a name="xhtml10" id="xhtml10" shape="rect"/>XHTML 1.0</dt><dd>Steven Pemberton et al. <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect"><cite>XHTML™ 1.0 The Extensible
- HyperText Markup Language (Second Edition)</cite></a>. W3C Recommendation 26 January 2000, revised 1 August 2002. Available at <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect">
- http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>. The latest version of <a href="http://www.w3.org/TR/xhtml1/" shape="rect">XHTML 1.0</a> is available at
+ development version (P5)</cite></a>. TEI Consortium, Charlottesville, Virginia, USA, Text Encoding Initiative.</dd><dt class="label"><a name="xhtml10" id="xhtml10" shape="rect"/>XHTML 1.0</dt><dd>Steven Pemberton et al. <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect"><cite>XHTML™ 1.0 The Extensible
+ HyperText Markup Language (Second Edition)</cite></a>. W3C Recommendation 26 January 2000, revised 1 August 2002. Available at <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect">
+ http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>. The latest version of <a href="http://www.w3.org/TR/xhtml1/" shape="rect">XHTML 1.0</a> is available at
http://www.w3.org/TR/xhtml1/.</dd><dt class="label"><a name="xml-i18n-bp" id="xml-i18n-bp" shape="rect"/>XML i18n BP</dt><dd>Yves Savourel, Jirka Kosek, Richard Ishida. <a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/" shape="rect"><cite>Best Practices for XML
- Internationalization</cite></a>. Available at <a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/" shape="rect">http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/</a>. The latest version of <a href="http://www.w3.org/TR/xml-i18n-bp/" shape="rect">xml-i18n-bp</a> is available at
+ Internationalization</cite></a>. Available at <a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/" shape="rect">http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/</a>. The latest version of <a href="http://www.w3.org/TR/xml-i18n-bp/" shape="rect">xml-i18n-bp</a> is available at
http://www.w3.org/TR/xml-i18n-bp/.</dd><dt class="label"><a name="xmlspecbib" id="xmlspecbib" shape="rect"/>XMLSPEC</dt><dd>
<a href="http://www.w3.org/2002/xmlspec/" shape="rect"><cite>The XML Spec Schema and Stylesheets</cite></a>. Available at <a href="http://www.w3.org/2002/xmlspec/" shape="rect">
- http://www.w3.org/2002/xmlspec/</a>.</dd><dt class="label"><a name="xslt10" id="xslt10" shape="rect"/>XSLT 1.0</dt><dd> James Clark. <a href="http://www.w3.org/TR/1999/REC-xslt-19991116" shape="rect"><cite>XSL Transformations (XSLT) Version
- 1.0</cite></a>. W3C Recommendation 16 November 1999. Available at <a href="http://www.w3.org/TR/1999/REC-xslt-19991116" shape="rect">
- http://www.w3.org/TR/1999/REC-xslt-19991116</a>. The latest version of <a href="http://www.w3.org/TR/xslt" shape="rect">XSLT 1.0</a> is available at
+ http://www.w3.org/2002/xmlspec/</a>.</dd><dt class="label"><a name="xslt10" id="xslt10" shape="rect"/>XSLT 1.0</dt><dd> James Clark. <a href="http://www.w3.org/TR/1999/REC-xslt-19991116" shape="rect"><cite>XSL Transformations (XSLT) Version
+ 1.0</cite></a>. W3C Recommendation 16 November 1999. Available at <a href="http://www.w3.org/TR/1999/REC-xslt-19991116" shape="rect">
+ http://www.w3.org/TR/1999/REC-xslt-19991116</a>. The latest version of <a href="http://www.w3.org/TR/xslt" shape="rect">XSLT 1.0</a> is available at
http://www.w3.org/TR/xslt.</dd><dt class="label"><a name="xul" id="xul" shape="rect"/>XUL</dt><dd>
<a href="http://www.xulplanet.com/" shape="rect"><cite>exTensible User Interface Language</cite></a>. Available at <a href="http://www.xulplanet.com/" shape="rect">
http://www.xulplanet.com/</a>.</dd></dl></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-markup-summary" id="its-markup-summary" shape="rect"/>C Summary of ITS Markup (Non-Normative)</h2><p>
+<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-markup-summary" id="its-markup-summary" shape="rect"/>D Summary of ITS Markup (Non-Normative)</h2><p>
<em>This section is informative.</em>
</p><span class="editor-note">[Ed. note: Needs to be updated with the additional data categories, once available.]</span><p>The following list summarizes elements relating to global rules and their attributes:</p><ul><li><p>
<span class="new-term"><rules></span> Container for global rules.</p><ul><li><p>
@@ -3110,7 +3067,7 @@
</p><p>Indicates a term locally.</p></li></ul><p/><ul><li><p>
<span class="new-term">dir</span>
</p><p>The text direction for the context.</p></li></ul></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 (Non-Normative)</h2><p>
+<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"/>E Schemas for ITS (Non-Normative)</h2><p>
<em>This section is informative.</em>
</p><span class="editor-note">[Ed. note: This section needs to be written with a schema for HTML5; the existing schemas need to
be updated with the data categories new in ITS 2.0.]</span><p>The following schemas define ITS elements and attributes and could be used as building blocks when
@@ -3126,7 +3083,7 @@
</p></li><li><p>
<a href="schemas/its.rng" shape="rect">RELAX NG XML syntax document for ITS</a>
</p></li></ul></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-schematron-constraints" id="its-schematron-constraints" shape="rect"/>E Checking ITS Markup Constraints With Schematron (Non-Normative)</h2><p>
+<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"/>F 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="d3e9212" id="d3e9212" shape="rect"/>Example 76: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
@@ -3192,7 +3149,7 @@
</sch:rule>
</sch:pattern>
</sch:schema></pre></div><p>[Source file: <a href="examples/xml/its-constraints-check-schematron.xml" shape="rect">examples/xml/its-constraints-check-schematron.xml</a>]</p></div></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-nvdl-schema" id="its-nvdl-schema" shape="rect"/>F Checking ITS Markup with NVDL (Non-Normative)</h2><p>
+<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-nvdl-schema" id="its-nvdl-schema" shape="rect"/>G Checking ITS Markup with NVDL (Non-Normative)</h2><p>
<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
@@ -3201,7 +3158,7 @@
</namespace> <namespace ns="http://www.w3.org/2005/11/its" match="attributes">
<validate schema="its-attributes.rng"/> </namespace> <anyNamespace>
<allow/> </anyNamespace> </rules></pre></div><p> [Source file: <a href="schemas/its.nvdl" shape="rect">its.nvdl</a>]</p></div><p>The NVDL schema depends on the following two schemas:</p><span class="editor-note">[Ed. note: These schemas need to be provided in an updated draft.]</span><ul><li><p>RELAX NG schema for ITS elements</p></li><li><p>RELAX NG schema for ITS attributes</p></li></ul></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="revisionlog" id="revisionlog" shape="rect"/>G Revision Log (Non-Normative)</h2><p id="changelog-since-20120731">The following log records major changes that have been made to this
+<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="revisionlog" id="revisionlog" shape="rect"/>H Revision Log (Non-Normative)</h2><p id="changelog-since-20120731">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-20120731/" shape="rect">ITS 2.0 Working Draft
31 July 2012</a>.</p><ol class="depth1"><li><p>Added <a class="section-ref" href="#Disambiguation" shape="rect">Section 6.10: Disambiguation</a>.</p></li><li><p>Added <a class="section-ref" href="#preservespace" shape="rect">Section 6.17: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#idvalue" shape="rect">Section 6.16: Id Value</a>.</p></li><li><p>Added support for different query language and reworked whole XPath and CSS Selectors
integration.</p></li><li><p>Added a note about HTML5 and the attributes <a class="itsmarkup" href="#att.local.no-ns.attribute.dir" shape="rect">dir</a> and <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> to <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.3: Local Selection in an XML Document</a>.</p></li><li><p>Added definition of <a class="itsmarkup" href="#param" shape="rect">param</a> element to <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>.</p></li><li><p>Added <a class="section-ref" href="#target-pointer" shape="rect">Section 6.15: Target Pointer</a>.</p></li><li><p>Original Ruby markup model changed to HTML5 Ruby model.</p></li><li><p>Added <a class="section-ref" href="#preservespace" shape="rect">Section 6.17: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#lqissue" shape="rect">Section 6.18: Localization Quality Issue</a>.</p></li></ol>p id="changelog-since-20120626">The following log records major changes that have been made to this
@@ -3211,7 +3168,7 @@
document between the <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0
Recommendation</a> and this document.</p><ol class="depth1"><li><p>Clarified <a href="#introduction" shape="rect">introduction</a> to cover ITS 2.0</p></li><li><p>Added a subsection on the relation to ITS 1.0 to the introduction, see <a class="section-ref" href="#relation-to-its10" shape="rect">Section 1.1.1: Relation to ITS 1.0</a></p></li><li><p>Created HTML5 based declarations for various data categories, see e.g. <a href="#att.term.html5" shape="rect">HTML5 declarations for the Terminology data category</a> and the
<a href="#att.local.html5" shape="rect">summary for local data categories</a> in <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.3: Local Selection in an XML Document</a></p></li><li><p>Created examples for these declarations, see e.g. <a href="#EX-term-local-html-1" shape="rect">Example 38</a></p></li><li><p>Added placeholders for new data categories to <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>Added a placeholder section <a class="section-ref" href="#conversion-to-nif-and-RDFa" shape="rect">Section 5.7: Conversion to NIF and RDFa</a></p></li></ol></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="acknowledgements" id="acknowledgements" shape="rect"/>H Acknowledgements (Non-Normative)</h2><span class="editor-note">[Ed. note: Need to update this.]</span><p>This document has been developed with contributions by the MultilingualWeb-LT Working Group: Mihael
+<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="acknowledgements" id="acknowledgements" shape="rect"/>I Acknowledgements (Non-Normative)</h2><span class="editor-note">[Ed. note: Need to update this.]</span><p>This document has been developed with contributions by the MultilingualWeb-LT Working Group: Mihael
Arcan (DERI Galway at the National University of Ireland, Galway, Ireland), Pablo Badía
(Linguaserve), Aaron Beaton (Opera Software), Luis Bellido (Universidad Politécnica de Madrid),
Aljoscha Burchardt (German Research Center for Artificial Intelligence (DFKI) Gmbh), Nicoletta
Received on Wednesday, 22 August 2012 17:54:46 UTC