- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Tue, 27 Nov 2012 17:00:14 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv20133
Modified Files:
its20.html its20.odd
Log Message:
more edits
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/27 14:53:17 1.266
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/27 17:00:14 1.267
@@ -1042,8 +1042,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="selection-precedence" id="selection-precedence" shape="rect"/>5.5 Precedence between Selections</h3><p>The following precedence order is defined for selections of ITS information in various
positions (the first item in the list has the highest precedence):</p><ol class="depth1"><li><p>Selection via explicit (that is, not inherited) local ITS markup in documents (<a href="#local-attributes" shape="rect">ITS local attributes</a> on a specific element)</p></li><li><p>Global selections in documents (using a
<code class="its-elem-markup">rules</code> element)</p><p>Inside each <code class="its-elem-markup">rules</code> 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 <code class="its-attr-markup">href</code> attribute</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
+ </p><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 8.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 provided via lower precedence is overriden by the higher precedence.
@@ -1204,17 +1203,17 @@
applications, creating for example named entity annotations. A non-normative algorithm
to integrate these annotations into the original input document is given in <a class="section-ref" href="#nif-backconversion" shape="rect">Appendix H: Conversion NIF2ITS</a>. The algorithm in that appendix is
non-normative since many choices depend on the actual NLP application.</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="its-tool-annotation" id="its-tool-annotation" shape="rect"/>5.8 ITS Tools Annotation</h3><p>In some cases, it may be important for instances of data categories to be associated with information about the processor that generated them. For example, the score of the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category (provided via the <code class="its-attr-markup">mtConfidence</code> attribute) is meaningful only when the consumer of the information also knows what MT engine produced it, because the score provides the relative confidence of translations from the same MT engine but does not provide a score that can be reliably compared between MT engines. The same is true for confidence provided for the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category, providing confidence informaton via the <code class="its-attr-markup">disambigConfidence</code> attribute, or the <a href="#terminology" shape="rect">Terminology</a> data category, providing confidence information via the <code class="its-attr-markup">termConfidence</code> attribute.</p><p>ITS 2.0 provides a mechanism to associate such processor information with the use of individual data categories in a document, independently from data category annotations themselves.</p><p>The attribute <code class="its-attr-markup">toolsRef</code> provides a way to associates all the annotations of a given data category within the element with information about the processor that generated those data category annotations.</p><p>The value of <code class="its-attr-markup">toolsRef</code> is a space-separated list of references where each reference is composed of two parts: a data category identifier and an IRI. These two parts are separated by a character <code>|</code> VERTICAL LINE (U+007C).</p><ul><li><p>The data category identifier <a href="#rfc219" shape="rect">MUST</a> be one of the following identifiers: <code>allowed-characters</code>, <code>directionality</code>, <code>disambiguation</code>, <code>domain</code>, <code>elements-within-text</code>, <code>external-resource</code>, <code>id-value</code>, <code>language-information</code>, <code>locale-filter</code>, <code>localization-note</code>, <code>lq-issues</code>, <code>lq-precis</code>, <code>mt-confidence</code>, <code>provenance</code>, <code>ruby</code>, <code>storage-size</code>, <code>target-pointer</code>, <code>terminology</code>, <code>translate</code>.</p></li><li><p>The IRI indicates information about the processor used to generate the data category annotation. No single means is specified for how this IRI should be used to indicate processor information. Possible mechanisms are: to encode information directly in the IRI, e.g. as parameters; to reference an external resource that provides such information, e.g. an XML file or an RDF declaration; or to reference another part of th document that provides such information.</p></li></ul><p>In HTML5 documents, the mechanism is implemented with the <code class="its-attr-markup">its-tools-ref</code> attribute.</p><p>The attribute applies to the content of the element where it is declared (including its children elements) and to the attributes of that element.</p><p>On any given node, the information provided by this mechanism is a space-separated list of the accumulated references found it the <code class="its-attr-markup">toolsRef</code> attributes
+<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="its-tool-annotation" id="its-tool-annotation" shape="rect"/>5.8 ITS Tools Annotation</h3><p>In some cases, it may be important for instances of data categories to be associated with information about the processor that generated them. For example, the score of the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category (provided via the <code class="its-attr-markup">mtConfidence</code> attribute) is meaningful only when the consumer of the information also knows what MT engine produced it, because the score provides the relative confidence of translations from the same MT engine but does not provide a score that can be reliably compared between MT engines. The same is true for confidence provided for the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category, providing confidence informaton via the <code class="its-attr-markup">disambigConfidence</code> attribute, or the <a href="#terminology" shape="rect">Terminology</a> data category, providing confidence information via the <code class="its-attr-markup">termConfidence</code> attribute.</p><p>ITS 2.0 provides a mechanism to associate such processor information with the use of individual data categories in a document, independently from data category annotations themselves.</p><p>The attribute <code class="its-attr-markup">toolsRef</code> provides a way to associate all the annotations of a given data category within the element with information about the processor that generated those data category annotations.</p><p>The value of <code class="its-attr-markup">toolsRef</code> is a space-separated list of references where each reference is composed of two parts: a data category identifier and an IRI. These two parts are separated by a character <code>|</code> VERTICAL LINE (U+007C).</p><ul><li><p>The data category identifier <a href="#rfc219" shape="rect">MUST</a> be one of the following identifiers: <code>allowed-characters</code>, <code>directionality</code>, <code>disambiguation</code>, <code>domain</code>, <code>elements-within-text</code>, <code>external-resource</code>, <code>id-value</code>, <code>language-information</code>, <code>locale-filter</code>, <code>localization-note</code>, <code>lq-issue</code>, <code>lq-precis</code>, <code>mt-confidence</code>, <code>provenance</code>, <code>ruby</code>, <code>storage-size</code>, <code>target-pointer</code>, <code>terminology</code>, <code>translate</code>.</p></li><li><p>The IRI indicates information about the processor used to generate the data category annotation. No single means is specified for how this IRI should be used to indicate processor information. Possible mechanisms are: to encode information directly in the IRI, e.g. as parameters; to reference an external resource that provides such information, e.g. an XML file or an RDF declaration; or to reference another part of the ocument that provides such information.</p></li></ul><p>In HTML5 documents, the mechanism is implemented with the <code class="its-attr-markup">its-tools-ref</code> attribute.</p><p>The attribute applies to the content of the element where it is declared (including its children elements) and to the attributes of that element.</p><p>On any given node, the information provided by this mechanism is a space-separated list of the accumulated references found it the <code class="its-attr-markup">toolsRef</code> attributes
declared in the enclosing elements and sorted by data category identifiers. For each data category, the IRI part is the one of the inner-most declarartion.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-tool-annotation-1" id="EX-its-tool-annotation-1" shape="rect"/>Example 25: Accumulation and Overriding of the <code class="its-attr-markup">toolsRef</code> Values</div><p>In this example, the text shows the computed tools reference information for the given node. Note that the references are ordered alphabetically and
that the IRI values are always the ones of the inner-most declaration.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><doc</strong> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
<span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|MT1"</span><strong class="hl-tag" style="color: #000096">
></strong>doc node: "mt-confidence|MT1"
- <strong class="hl-tag" style="color: #000096"><group</strong> <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"lq-issues|ABC"</span><strong class="hl-tag" style="color: #000096">
+ <strong class="hl-tag" style="color: #000096"><group</strong> <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"lq-issue|ABC"</span><strong class="hl-tag" style="color: #000096">
></strong>group node: "lq-issues|ABC mt-confidence|MT1"
<strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"disambiguation|Tool3"</span><strong class="hl-tag" style="color: #000096">
- ></strong>This p node: "disambiguation|Tool3 lq-issues|ABC mt-confidence|MT1"<strong class="hl-tag" style="color: #000096"></p></strong>
+ ></strong>This p node: "disambiguation|Tool3 lq-issue|ABC mt-confidence|MT1"<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|MT123"</span><strong class="hl-tag" style="color: #000096">
- ></strong>This p node: "disambiguation|Tool3 lq-issues|ABC mt-confidence|MT123"<strong class="hl-tag" style="color: #000096"></p></strong>
+ ></strong>This p node: "disambiguation|Tool3 lq-issue|ABC mt-confidence|MT123"<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></group></strong>
<strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"disambiguation|XYZ"</span><strong class="hl-tag" style="color: #000096">
></strong>This p node: "disambiguation|XYZ mt-confidence|MT1"<strong class="hl-tag" style="color: #000096"></p></strong>
@@ -1223,7 +1222,7 @@
for the first two <code>p</code> elements are found in element with <code>id="T1"</code> in the external document tools.xml, while that information for the
third <code>p</code> element is found in the element with <code>id="T2"</code> in the same document. In addition, <code class="its-attr-markup">toolsRef</code> is used to identify a Web
resource with information about the QA tool used to generate the <a href="#lqissue" shape="rect">Localization Quality Issue</a> annotation in the document.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><doc</strong> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span>
- <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|file:///tools.xml#T1 lq-issues|http://www.qalsp-ex.com/qatools/transcheckv1.3"</span>
+ <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|file:///tools.xml#T1 lq-issue|http://www.qalsp-ex.com/qatools/transcheckv1.3"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">its:mt-confidence</span>=<span class="hl-value" style="color: #993300">"0.78"</span><strong class="hl-tag" style="color: #000096">></strong>Text translated with tool T1<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">its:mt-confidence</span>=<span class="hl-value" style="color: #993300">"0.55"</span> <span class="hl-attribute" style="color: #F5844C">its:locQualityIssueType</span>=<span class="hl-value" style="color: #993300">"typographical"</span>
@@ -1258,7 +1257,7 @@
following rules:</p><ol class="depth1"><li><p>Attribute name is prefixed with <code>its-</code></p></li><li><p>Each uppercase letter in the attribute name is replaced by <code>-</code>
(U+002D) followed by a lowercase variant of the letter.</p></li></ol><p>
</p><p>Values of attributes which corresponds to data categories with a predefined set of
- values MUST be matched case-insensitively. </p><div class="note"><p class="prefix"><b>Note:</b></p><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in
+ values <a href="#rfc2119" shape="rect">MUST</a> be matched case-insensitively. </p><div class="note"><p class="prefix"><b>Note:</b></p><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in
HTML terminology data category can be stored as <code class="its-attr-markup">its-term</code>,
<code>ITS-TERM</code>, <code>its-Term</code> etc. All those attributes are treated as
equivalent and will gets normalized upon DOM construction.</p></div></div><div class="div2">
@@ -1270,22 +1269,21 @@
take this into account.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Using XPath in global rules linked from HTML5 documents does not create an additional
burden to implementers. Parsing HTML5 content produces a DOM tree that can be directly
queried using XPath, functionality supported by all major browsers.</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="html5-inline-global-rules" id="html5-inline-global-rules" shape="rect"/>6.3 Inline Global Rules in HTML5</h3><p>Inline global rules MUST be specified inside <code>script</code> which has <code>type</code>
- attribute with the value <code>application/xml</code> or
- <code>application/its+xml</code>. The <code>script</code> element itself MUST be child of
- <code>head</code> element. Comments MUST NOT be used inside global rules. Each
- <code>script</code> element MUST NOT contain more then one <code class="its-elem-markup">rules</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is preferred to use external global rules linked using <code>link</code>
+<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="html5-inline-global-rules" id="html5-inline-global-rules" shape="rect"/>6.3 Inline Global Rules in HTML5</h3><p>Inline global rules <a href="#rfc2119" shape="rect">MUST</a> be specified inside <code>script</code> which has <code>type</code>
+ attribute with the value <code>application/its+xml</code>. The <code>script</code> element itself <a href="#rfc2119" shape="rect">SHOULD</a> be child of
+ <code>head</code> element. Comments <a href="#rfc2119" shape="rect">MUST NOT</a> be used inside global rules. Each
+ <code>script</code> element <a href="#rfc2119" shape="rect">MUST NOT</a> contain more then one <code class="its-elem-markup">rules</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is preferred to use external global rules linked using <code>link</code>
element.</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="html5-standoff-markup" id="html5-standoff-markup" shape="rect"/>6.4 Standoff Markup in HTML5</h3><p>The constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff markup in HTML5</a> and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issues markup in HTML5</a>
<a href="#rfc2119" shape="rect">MUST</a> be followed.</p></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="html5-selection-precedence" id="html5-selection-precedence" shape="rect"/>6.5 Precedence between Selections</h3><p>The following precedence order is defined for selections of ITS information in various
positions of HTML document (the first item in the list has the highest precedence):</p><ol class="depth1"><li><p>Implicit local selection in documents (<a href="#html5-local-attributes" shape="rect">ITS
- local attributes</a> on a specific element)</p></li><li><p>Global selections in documents (using mechanism described in <a class="section-ref" href="#html5-external-global-rules" shape="rect">Section 6.2: External Rules</a> or <a class="section-ref" href="#html5-inline-global-rules" shape="rect">Section 6.3: Inline Global Rules in HTML5</a>)</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></li><li><p>Selections via defaults for data categories, see <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.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
+ local attributes</a> on a specific element)</p></li><li><p>Global selections in documents (using mechanism described in <a class="section-ref" href="#html5-external-global-rules" shape="rect">Section 6.2: External Rules</a> or <a class="section-ref" href="#html5-inline-global-rules" shape="rect">Section 6.3: Inline Global Rules in HTML5</a>)</p><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 8.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></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="xhtml5-markup" id="xhtml5-markup" shape="rect"/>7 Using ITS Markup in XHTML</h2><p>XHTML documents aimed at public consumption by Web browsers SHOULD use syntax for local
- attributes described in <a class="section-ref" href="#html5-local-attributes" shape="rect">Section 6.1: Mapping of Local Data Categories to HTML5</a> and SHOULD
- NOT use <a href="#html5-inline-global-rules" shape="rect">inline global rules</a> in order to
+<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="xhtml5-markup" id="xhtml5-markup" shape="rect"/>7 Using ITS Markup in XHTML</h2><p>XHTML documents aimed at public consumption by Web browsers <a href="#rfc2119" shape="rect">SHOULD</a> use syntax for local
+ attributes described in <a class="section-ref" href="#html5-local-attributes" shape="rect">Section 6.1: Mapping of Local Data Categories to HTML5</a> and <a href="#rfc2119" shape="rect">SHOULD
+ NOT</a> use <a href="#html5-inline-global-rules" shape="rect">inline global rules</a> in order to
adhere to <a href="http://www.w3.org/TR/html-design-principles/#dom-consistency" shape="rect">DOM
Consistency HTML Design Principle</a>.</p></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="datacategory-description" id="datacategory-description" shape="rect"/>8 Description of Data Categories</h2><p>
@@ -2269,7 +2267,7 @@
their equivalent representations) are used in a standoff manner, the
information they carry pertains to the content of the element that refers to the
standoff annotation, not to the content of the element <code class="its-elem-markup">provenanceRecord</code> where they are
- declared.</p><p id="provenance-records-in-html5-constraint">In HTML5 the standoff markup <a href="#rfc-keywords" shape="rect">MUST</a> be stored inside a <code>script</code> element with its <code>id</code> attribute that <a href="#rfc-keywords" shape="rect">MUST</a> be set to the same value as the <code>xml:id</code>
+ declared.</p><p id="provenance-records-in-html5-constraint">In HTML5 the standoff markup <a href="#rfc-keywords" shape="rect">MUST</a> be stored inside a <code>script</code> element. It <a href="#rfc-keywords" shape="rect">MUST</a> have a <code>type</code> attribute with the value <code>application/its+xml</code>. Its <code>id</code> attribute <a href="#rfc-keywords" shape="rect">MUST</a> be set to the same value as the <code>xml:id</code>
attribute of the <code class="its-elem-markup">provenanceRecords</code> element it contains.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-provenance-local-1" id="EX-provenance-local-1" shape="rect"/>Example 63: Annotating provenance information in XML with local inline markup</div><p>The provenance related attributes at the <code>par</code> and
<code>legalnotice</code> elements are used to associate the provenance information
directly with the content of theses elements.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:dc</span>=<span class="hl-value" style="color: #993300">"http://purl.org/dc/elements/1.1/"</span>
@@ -2685,8 +2683,7 @@
<code class="its-attr-markup">locQualityIssueProfileRef</code> and <code class="its-attr-markup">locQualityIssueEnabled</code> are used
in a standoff manner, the information they carry pertains to the content of the
element that refers to the standoff annotation, not to the content of the element
- <code class="its-elem-markup">locQualityIssue</code> where they are declared.</p><p id="loc-quality-issues-in-html5-constraint">In HTML5 the standoff markup <a href="#rfc-keywords" shape="rect">MUST</a> be stored inside a <code>script</code> element with
- its <code>id</code> attribute that <a href="#rfc-keywords" shape="rect">MUST</a> be set to the same value as the <code>xml:id</code>
+ <code class="its-elem-markup">locQualityIssue</code> where they are declared.</p><p id="loc-quality-issues-in-html5-constraint">In HTML5 the standoff markup <a href="#rfc-keywords" shape="rect">MUST</a> be stored inside a <code>script</code> element. It <a href="#rfc-keywords" shape="rect">MUST</a> have a <code>type</code> attribute with the value <code>application/its+xml</code>. Its <code>id</code> attribute <a href="#rfc-keywords" shape="rect">MUST</a> be set to the same value as the <code>xml:id</code>
attribute of the <code class="its-elem-markup">locQualityIssues</code> element it contains.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-1" id="EX-locQualityIssue-local-1" shape="rect"/>Example 77: Annotating an issue in XML with local inline markup</div><p>The attributes <code class="its-attr-markup">locQualityIssueType</code>, <code class="its-attr-markup">locQualityIssueComment</code>
and <code class="its-attr-markup">locQualityIssueSeverity</code> are used to associate the issue information
directly with a selected span of content.</p><div class="exampleInner"><pre xml:space="preserve"><span class="hl-directive" style="color: maroon"><?xml version="1.0"?></span>
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/27 14:53:17 1.263
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/27 17:00:14 1.264
@@ -1495,8 +1495,6 @@
<item>Any rule linked via the XLink <att>href</att> attribute</item>
</list>
</p>
- <note><p>If identical selections are defined in different rules elements within one
- document, the selection defined by the last takes precedence.</p></note>
<note><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></note>
</item>
@@ -1712,12 +1710,12 @@
<p>ITS 2.0 provides a mechanism to associate such processor information with the use of individual data categories in a document, independently from data category annotations themselves.</p>
- <p>The attribute <att>toolsRef</att> provides a way to associates all the annotations of a given data category within the element with information about the processor that generated those data category annotations.</p>
+ <p>The attribute <att>toolsRef</att> provides a way to associate all the annotations of a given data category within the element with information about the processor that generated those data category annotations.</p>
<p>The value of <att>toolsRef</att> is a space-separated list of references where each reference is composed of two parts: a data category identifier and an IRI. These two parts are separated by a character <code>|</code> VERTICAL LINE (U+007C).</p>
<list>
- <item><p>The data category identifier <ref target="#rfc2119">MUST</ref> be one of the following identifiers: <code>allowed-characters</code>, <code>directionality</code>, <code>disambiguation</code>, <code>domain</code>, <code>elements-within-text</code>, <code>external-resource</code>, <code>id-value</code>, <code>language-information</code>, <code>locale-filter</code>, <code>localization-note</code>, <code>lq-issues</code>, <code>lq-precis</code>, <code>mt-confidence</code>, <code>provenance</code>, <code>ruby</code>, <code>storage-size</code>, <code>target-pointer</code>, <code>terminology</code>, <code>translate</code>.</p></item>
+ <item><p>The data category identifier <ref target="#rfc2119">MUST</ref> be one of the following identifiers: <code>allowed-characters</code>, <code>directionality</code>, <code>disambiguation</code>, <code>domain</code>, <code>elements-within-text</code>, <code>external-resource</code>, <code>id-value</code>, <code>language-information</code>, <code>locale-filter</code>, <code>localization-note</code>, <code>lq-issue</code>, <code>lq-precis</code>, <code>mt-confidence</code>, <code>provenance</code>, <code>ruby</code>, <code>storage-size</code>, <code>target-pointer</code>, <code>terminology</code>, <code>translate</code>.</p></item>
<item><p>The IRI indicates information about the processor used to generate the data category annotation. No single means is specified for how this IRI should be used to indicate processor information. Possible mechanisms are: to encode information directly in the IRI, e.g. as parameters; to reference an external resource that provides such information, e.g. an XML file or an RDF declaration; or to reference another part of the document that provides such information.</p></item>
</list>
@@ -1773,7 +1771,7 @@
(U+002D) followed by a lowercase variant of the letter.</item>
</list></p>
<p>Values of attributes which corresponds to data categories with a predefined set of
- values MUST be matched case-insensitively. </p>
+ values <ref target="#rfc2119">MUST</ref> be matched case-insensitively. </p>
<note><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in
HTML terminology data category can be stored as <att>its-term</att>,
<code>ITS-TERM</code>, <code>its-Term</code> etc. All those attributes are treated as
@@ -1804,11 +1802,10 @@
<div xml:id="html5-inline-global-rules">
<head>Inline Global Rules in HTML5</head>
- <p>Inline global rules MUST be specified inside <code>script</code> which has <code>type</code>
- attribute with the value <code>application/xml</code> or
- <code>application/its+xml</code>. The <code>script</code> element itself MUST be child of
- <code>head</code> element. Comments MUST NOT be used inside global rules. Each
- <code>script</code> element MUST NOT contain more then one <gi>rules</gi> element.</p>
+ <p>Inline global rules <ref target="#rfc2119">MUST</ref> be specified inside <code>script</code> which has <code>type</code>
+ attribute with the value <code>application/its+xml</code>. The <code>script</code> element itself <ref target="#rfc2119">SHOULD</ref> be child of
+ <code>head</code> element. Comments <ref target="#rfc2119">MUST NOT</ref> be used inside global rules. Each
+ <code>script</code> element <ref target="#rfc2119">MUST NOT</ref> contain more then one <gi>rules</gi> element.</p>
<note><p>It is preferred to use external global rules linked using <code>link</code>
element.</p></note>
</div>
@@ -1825,8 +1822,8 @@
<item><p>Global selections in documents (using mechanism described in <ptr
target="#html5-external-global-rules" type="specref"/> or <ptr
target="#html5-inline-global-rules" type="specref"/>)</p>
- <note><p>If identical selections are defined in different rules elements within one
- document, the selection defined by the last takes precedence.</p></note>
+ <note><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></note>
</item>
<item>Selections via defaults for data categories, see <ptr
target="#datacategories-defaults-etc" type="specref"/></item>
@@ -1839,9 +1836,9 @@
<div xml:id="xhtml5-markup">
<head>Using ITS Markup in XHTML</head>
- <p>XHTML documents aimed at public consumption by Web browsers SHOULD use syntax for local
- attributes described in <ptr target="#html5-local-attributes" type="specref"/> and SHOULD
- NOT use <ref target="#html5-inline-global-rules">inline global rules</ref> in order to
+ <p>XHTML documents aimed at public consumption by Web browsers <ref target="#rfc2119">SHOULD</ref> use syntax for local
+ attributes described in <ptr target="#html5-local-attributes" type="specref"/> and <ref target="#rfc2119">SHOULD
+ NOT</ref> use <ref target="#html5-inline-global-rules">inline global rules</ref> in order to
adhere to <ref target="http://www.w3.org/TR/html-design-principles/#dom-consistency">DOM
Consistency HTML Design Principle</ref>.</p>
</div>
@@ -3474,7 +3471,7 @@
information they carry pertains to the content of the element that refers to the
standoff annotation, not to the content of the element <gi>provenanceRecord</gi> where they are
declared.</p>
- <p xml:id="provenance-records-in-html5-constraint">In HTML5 the standoff markup <ref target="#rfc-keywords">MUST</ref> be stored inside a <code>script</code> element with its <code>id</code> attribute that <ref target="#rfc-keywords">MUST</ref> be set to the same value as the <code>xml:id</code>
+ <p xml:id="provenance-records-in-html5-constraint">In HTML5 the standoff markup <ref target="#rfc-keywords">MUST</ref> be stored inside a <code>script</code> element. It <ref target="#rfc-keywords">MUST</ref> have a <code>type</code> attribute with the value <code>application/its+xml</code>. Its <code>id</code> attribute <ref target="#rfc-keywords">MUST</ref> be set to the same value as the <code>xml:id</code>
attribute of the <gi>provenanceRecords</gi> element it contains.</p>
<exemplum xml:id="EX-provenance-local-1">
<head>Annotating provenance information in XML with local inline markup</head>
@@ -3984,8 +3981,7 @@
in a standoff manner, the information they carry pertains to the content of the
element that refers to the standoff annotation, not to the content of the element
<gi>locQualityIssue</gi> where they are declared.</p>
- <p xml:id="loc-quality-issues-in-html5-constraint">In HTML5 the standoff markup <ref target="#rfc-keywords">MUST</ref> be stored inside a <code>script</code> element with
- its <code>id</code> attribute that <ref target="#rfc-keywords">MUST</ref> be set to the same value as the <code>xml:id</code>
+ <p xml:id="loc-quality-issues-in-html5-constraint">In HTML5 the standoff markup <ref target="#rfc-keywords">MUST</ref> be stored inside a <code>script</code> element. It <ref target="#rfc-keywords">MUST</ref> have a <code>type</code> attribute with the value <code>application/its+xml</code>. Its <code>id</code> attribute <ref target="#rfc-keywords">MUST</ref> be set to the same value as the <code>xml:id</code>
attribute of the <gi>locQualityIssues</gi> element it contains.</p>
</item>
</list>
Received on Tuesday, 27 November 2012 17:00:22 UTC