- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Sun, 23 Jun 2013 08:54:47 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv32320
Modified Files:
its20.html its20.odd
Log Message:
updated change log, spell etc. checks
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/21 17:38:26 1.465
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/23 08:54:46 1.466
@@ -76,7 +76,7 @@
<div class="toc2">6.4 <a href="#html5-selection-precedence" shape="rect">Precedence between Selections</a></div>
</div>
<div class="toc1">7 <a href="#xhtml5-markup" shape="rect">Using ITS Markup in XHTML</a></div>
-<div class="toc1">8 <a href="#datacategory-description" shape="rect">Description of Data Categories</a><div class="toc2">8.1 <a href="#datacategories-defaults-etc" shape="rect">Position, Defaults, Inheritance and Overriding of Data Categories</a></div>
+<div class="toc1">8 <a href="#datacategory-description" shape="rect">Description of Data Categories</a><div class="toc2">8.1 <a href="#datacategories-defaults-etc" shape="rect">Position, Defaults, Inheritance, and Overriding of Data Categories</a></div>
<div class="toc2">8.2 <a href="#trans-datacat" shape="rect">Translate</a><div class="toc3">8.2.1 <a href="#translatability-definition" shape="rect">Definition</a></div>
<div class="toc3">8.2.2 <a href="#translatability-implementation" shape="rect">Implementation</a></div>
</div>
@@ -246,7 +246,7 @@
<strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
<strong class="hl-tag" style="color: #000096"></section></strong>
<strong class="hl-tag" style="color: #000096"></resources></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><p>ITS proposes several mechanisms, which differ amongst others in terms of the usage scenario/user types for which the mechanism is most suitable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 2: Document that uses two different ITS mechanisms to indicate that some parts have to be left untranslated.</div><p>ITS provides two mechanisms to explicitly associate metadata with one
+</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><p>ITS proposes several mechanisms, which differ among others in terms of the usage scenario/user types for which the mechanism is most suitable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 2: Document that uses two different ITS mechanisms to indicate that some parts have to be left untranslated.</div><p>ITS provides two mechanisms to explicitly associate metadata with one
or more pieces of content (e.g. XML nodes): a <a href="#basic-concepts-selection-global" shape="rect">global</a>, rule-based
approach as well as a <a href="#basic-concepts-selection-local" shape="rect">local</a>, attribute-based approached. Here, for
instance, a <code class="its-elem-markup">translateRule</code> first specifies that only every second element inside
@@ -278,7 +278,7 @@
<strong class="hl-tag" style="color: #000096"></section></strong>
<strong class="hl-tag" style="color: #000096"></resources></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">examples/xml/EX-motivation-its-2.xml</a>]</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="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 are simple:</p><ol class="depth1"><li><p>Provide metadata (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global appraoch</a>) to associate metadata with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the metadata straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of metadata categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing metadata (e.g. terms aleady marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
+<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="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 are simple:</p><ol class="depth1"><li><p>Provide metadata (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global approach</a>) to associate metadata with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the metadata straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of metadata categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing metadata (e.g. terms aleady marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
identify additional metadata categories for internationalization-related processes. The
<a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> for
example compiled a list of additional data categories (see this <a href="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf" shape="rect">related summary</a>). Some of these were then defined in ITS 2.0: <a href="#idvalue" shape="rect">ID Value</a>, local <a href="#elements-within-text" shape="rect">Elements
@@ -291,10 +291,10 @@
metadata in localization workflows</p></li></ul><p>One example outcome of the resulting synergies is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the
provenance-related requirement by allowing ITS processors to leave a trace: ITS
processors can basically say “It is me that generated this bit of
- information”. Another example are the <a title="" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0 which help to couple Natural Language
+ information”. Another example are the <a title="" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0, which help to couple Natural Language
Processing with concepts of the Semantic Web.</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="usage-scenarios" id="usage-scenarios" shape="rect"/>1.3 Usage Scenarios</h3><p>The <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a>
- <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “ITS is a technology to easily create XML which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multilingual production.</p><ul><li><p>Static mono-lingual (for example, the area of content authors): This part of the
+ <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “ITS is a technology to easily create XML, which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multilingual production.</p><ul><li><p>Static mono-lingual (for example, the area of content authors): This part of the
content has the directionality “right-to-left”.</p></li><li><p>Dynamic multilingual: (for example, the area of machine translation systems): This
part of the content has to be left untranslated.</p></li></ul><p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production
process chain, it was slanted towards a simple three phase
@@ -309,8 +309,8 @@
the time were conceived as being closely tied to human actors such as content authors or
information architects. ITS 2.0 raises non-human actors such as word processors/editors,
content management systems, machine translation systems, term candidate generators,
- entity identifiers/disambiguators to the same level. This change amongst others is
- reflected by the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a> which
+ entity identifiers/disambiguators to the same level. This change among others is
+ reflected by the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a>, which
allows systems to record that they have processed a certain part of content.</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="high-level-differences-between-1.0-and-2.0" id="high-level-differences-between-1.0-and-2.0" shape="rect"/>1.4 High-level differences between ITS 1.0 and ITS 2.0</h3><p>The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.</p><p>
<em>Coverage of <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>: </em>ITS 1.0 can be applied to XML content. ITS 2.0 extends the coverage to <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. Explanatory details about ITS 2.0 and <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> are given in <a class="section-ref" href="#specific-HTML-support" shape="rect">Section 2.5: Specific HTML support</a>.</p><p>
@@ -319,9 +319,9 @@
<em>Modification of data categories</em>:</p><ul><li><p id="ruby-in-its2">ITS 1.0 provided the <a href="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation" shape="rect">Ruby data
category</a>. ITS 2.0 does not provide ruby because at the time of writing the
<a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a> was still under development. Once these discussions are
- settled, the Ruby data category possibly will be re-introduced, in a subsequent
+ settled, the Ruby data category possibly will be reintroduced, in a subsequent
version of ITS.</p></li><li><p>The <a href="#directionality" shape="rect">Directionality</a> data category reflects directionality markup in <a title="HTML 4.01" href="#html4" shape="rect">[HTML 4.01]</a>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</p></li></ul><p>
- <em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param" shape="rect">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has a <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="sectio-ref" href="#traceability" shape="rect">Section 2.6: Traceability</a> for details.</p></li></ul><p>
+ <em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param" shape="rect">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has an <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="sectin-ref" href="#traceability" shape="rect">Section 2.6: Traceability</a> for details.</p></li></ul><p>
<em>Mappings:</em> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about how to relate ITS 2.0 to XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.7: Mapping and conversion</a> for details.</p><p>
<em>Changes to the conformance section</em>: The <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <a title="" href="#nif-reference" shape="rect">[NIF]</a> has been added. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.</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="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.5 Extended implementation hints</h3><p id="unicode-normalization">As a general guidance, implementations of ITS 2.0 are encouraged to use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</a>.</p></div></div><div class="div1">
@@ -341,7 +341,7 @@
base.</p></li><li><p><a href="#directionality" shape="rect">Directionality</a>: specifies the base writing
direction of blocks, embeddings and overrides for the Unicode bidirectional
algorithm.</p></li><li><p><a href="#language-information" shape="rect">Language Information</a>: expresses the
- language of a given piece of content.</p></li><li><p><a href="#elements-within-text" shape="rect">Elements Witin Text:</a> expresses how
+ language of a given piece of content.</p></li><li><p><a href="#elements-within-text" shape="rect">Elements Within Text:</a> expresses how
content of an element is related to the text flow (constitutes its own segment like
paragraphs, is part of a segment like emphasis marker etc.).</p></li><li><p><a href="#domain" shape="rect">Domain</a>: identifies the topic or subject of the
annotated content for translation-related applications.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotates content with lexical or
@@ -393,7 +393,7 @@
<strong class="hl-tag" style="color: #000096"></info></strong>
<strong class="hl-tag" style="color: #000096"><para></strong>This is a short article.<strong class="hl-tag" style="color: #000096"></para></strong>
<strong class="hl-tag" style="color: #000096"></article></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-1.xml" shape="rect">examples/xml/EX-basic-concepts-1.xml</a>]</p></div><p>For the local approach (and <a href="#EX-basic-concepts-1" shape="rect">Example 3</a>) to work for a whole markup vocabulary, a schema developer would need to add the <code class="its-attr-markup">translate</code> attribute to the schema as a common attribute or on all the relevant element definitions. The example indicates that <a href="#basic-concepts-overinher" shape="rect">inheritance</a> plays a part in identifying which content does have to be translated and which does not: Although only the <code>author</code> element is marked as “do not translate”, its descendants (<code>personname</code>, <code>firstname</code>, <code>surname</code>) are considered to be implicitly marked as well. Tools that process this content for translation need to implement the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">For XML content, the local pproach cannot be applied to a particular attribute. If ITS needs to be applied to a particular attribute, the global approach has to be used. The local approach applies to content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>. For the <a href="#trans-datacat" shape="rect">Translate</a> data category used in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, this is different, see the explanation of the <a href="#translate-in-html5" shape="rect">HTML5 definition of Translate</a>.</p></div><div class="div3">
+</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-1.xml" shape="rect">examples/xml/EX-basic-concepts-1.xml</a>]</p></div><p>For the local approach (and <a href="#EX-basic-concepts-1" shape="rect">Example 3</a>) to work for a whole markup vocabulary, a schema developer would need to add the <code class="its-attr-markup">translate</code> attribute to the schema as a common attribute or on all the relevant element definitions. The example indicates that <a href="#basic-concepts-overinher" shape="rect">inheritance</a> plays a part in identifying which content does have to be translated and which does not: Although only the <code>author</code> element is marked as “do not translate”, its descendants (<code>personname</code>, <code>firstname</code>, <code>surname</code>) are considered to be implicitly marked as well. Tools that process this content for translation need to implement the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">For XML content, the local pproach cannot be applied to a particular attribute. If ITS needs to be applied to a particular attribute, the global approach has to be used. The local approach applies to content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>. For the <a href="#trans-datacat" shape="rect">Translate</a> data category used in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, this is different, see the explanation of the <a href="#translate-in-html5" shape="rect">HTML5 definition of Translate</a>.</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.2.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 4</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 <code class="its-elem-markup">rules</code>. It works as follows: A document can contain a <code class="its-elem-markup">rules</code> element (placed where it does not impact the structure of the document, e.g., in a “head” section, or even outside of the document itself). The <code class="its-elem-markup">rules</code> elemnt contains one or more ITS children/rule elements (for example <code class="its-elem-markup">translateRule</code>). Each of these children elements contains a <code class="its-attr-markup">selector</code> attribute. As its name suggests, this attribute selects the node or nodes to which the corresponding ITS information pertains. The values of ITS <code class="its-attr-markup">selector</code> attributes are XPath absolute location paths (or CSS Selectors if queryLanguage is set to "css"). Via the <code class="its-elem-markup">param</code> element variables can be provided and used in selectors.
</p><p>Information for the handling of namespaces in XPath expressions is taken from namespace declarations
<a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> in the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 4: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -437,11 +437,11 @@
<strong class="hl-tag" style="color: #000096"></div></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></text></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div><p>For XML content, <a href="#datacategories-overview" shape="rect">data category specific defaults</a> are provided. These are independent of the actual XML markup vocabulary. Example for the <a href="#trans-datacat" shape="rect">Translate</a> data category: <code>translate="yes"</code> for elements, and <code>translate="no"</code> for attributes.</p><p>For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence, that HTML markup is normatively interpreted as ITS 2.0 data category information (see <a class="section-ref" href="#html5-existing-markup-versus-its" shape="rect">Section 2.5.3: HTML markup with ITS 2.0 counterparts</a> for more information).</p></div><div class="div2">
+</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div><p>For XML content, <a href="#datacategories-overview" shape="rect">data category specific defaults</a> are provided. These are independent of the actual XML markup vocabulary. Example for the <a href="#trans-datacat" shape="rect">Translate</a> data category: <code>translate="yes"</code> for elements, and <code>translate="no"</code> for attributes.</p><p>For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence that HTML markup is normatively interpreted as ITS 2.0 data category information (see <a class="section-ref" href="#html5-existing-markup-versus-its" shape="rect">Section 2.5.3: HTML markup with ITS 2.0 counterparts</a> for more information).</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="basic-concepts-addingpointing" id="basic-concepts-addingpointing" shape="rect"/>2.4 Adding Information or Pointing to Existing Information</h3><p>Data categories can add information or point to information for the selected nodes. For example, the <a href="#locNote-datacat" shape="rect">Localization Note</a>
data category can add information to selected nodes (using a <code class="its-elem-markup">locNote</code> element),
or point to existing information elsewhere in the document (using a
- <code class="its-attr-markup">locNotePointer</code> attribute).</p><p>The <a href="#datacategories-overview" shape="rect">data category overview table</a>, in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>, provides an overview of which
+ <code class="its-attr-markup">locNotePointer</code> attribute).</p><p>The <a href="#datacategories-overview" shape="rect">data category overview table</a>, in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>, provides an overview of which
data categories allow the addition of information and which allow to point to existing
information.</p><p>Adding information and pointing to existing information are <em>mutually
exclusive</em>; attributes for adding information and attributes for pointing to the
@@ -524,7 +524,7 @@
<strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"p1"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>This is a <strong class="hl-tag" style="color: #000096"><em></strong>motherboard<strong class="hl-tag" style="color: #000096"></em></strong> and image:
<strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"http://example.com/myimg.png"</span> <span class="hl-attribute" style="color: #F5844C">alt</span>=<span class="hl-value" style="color: #993300">"My image"</span><strong class="hl-tag" style="color: #000096">/></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-its-and-existing-HTML5-markup.html" shape="rect">examples/html5/EX-its-and-existing-HTML5-markup.html</a>]</p></div><p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behaviors as certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <a href="#terminology" shape="rect">Terminology</a> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. For example, a rule can be used to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes"</code>. For additional examples see the <a href="http://www.w3.org/TR2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml" shape="rect">XML I18N Best Practices</a> document.</p></div><div class="div3">
+<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-its-and-existing-HTML5-markup.html" shape="rect">examples/html5/EX-its-and-existing-HTML5-markup.html</a>]</p></div><p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behaviors as certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <a href="#terminology" shape="rect">Terminology</a> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. For example, a rule can be used to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes"</code>. For additional examples, see the <a href="http://www.w3.org/T/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml" shape="rect">XML I18N Best Practices</a> document.</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="html5-standoff-markup-explanation" id="html5-standoff-markup-explanation" shape="rect"/>2.5.4 Standoff markup in HTML5</h4><p>The <a href="#provenance" shape="rect">Provenance</a> and the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data categories allow for using so-called standoff markup, see the XML <a href="#EX-provenance-global-1" shape="rect">Example 59</a>. In HTML such standoff markup is placed into a <code>script</code> element. If this is done, the constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff</a> markup in HTML and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issue</a> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <a href="#EX-proveance-html5-local-2" shape="rect">Example 62</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 77</a>.</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="usage-in-legacy-html" id="usage-in-legacy-html" shape="rect"/>2.5.5 Version of HTML</h4><p>ITS 2.0 does not define how to use ITS in HTML versions prior to version 5. Users are
thus encouraged to migrate their content to <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> or XHTML. While it is possible to use
@@ -616,10 +616,10 @@
<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="conformance" id="conformance" shape="rect"/>4 Conformance</h2><p>
<em>This section is normative.</em>
</p><p>The usage of the term <em>conformance clause</em> in this section is in compliance
- with <a title="QA Framework:
 Specification Guidelines" href="#qa-framework" shape="rect">[QAFRAMEWORK]</a>.</p><p>This specification defines four types of conformance: conformance of <a href="#conformance-product-schema" shape="rect">1) ITS markup declarations</a> , conformance of
+ with <a title="QA Framework:
 Specification Guidelines" href="#qa-framework" shape="rect">[QAFRAMEWORK]</a>.</p><p>This specification defines four types of conformance: conformance of <a href="#conformance-product-schema" shape="rect">1) ITS markup declarations</a>, conformance of
<a href="#conformance-product-processing-expectations" shape="rect">2) processing expectations
for ITS Markup</a>, conformance of <a href="#conformance-product-html-processing-expectations" shape="rect">3) processing expectations
- for ITS Markup in HTML</a>, and <a href="#conformance-product-html5-its" shape="rect">Conformance Type 4: Markup conformance for HTML5+ITS documents</a>.
+ for ITS Markup in HTML</a>, and <a href="#conformance-product-html5-its" shape="rect">4) markup conformance for HTML5+ITS documents</a>.
The conformance type 4 is defined for using ITS markup in HTML5 documents, HTML5+ITS,
which serves as an <em>applicable specification</em> in the sense specified in the
<a href="http://www.w3.org/TR/html5/infrastructure.html#extensibility" shape="rect">Extensibility
@@ -697,7 +697,7 @@
global or local selection mechanisms, see conformance clause <a href="#its-conformance-2-1-1" shape="rect">2-1-1</a>.</p></div><p id="its-processing-conformance-claims">Statements related to this conformance type
<a href="#rfc-keywords" shape="rect">MUST</a> list all <a href="#def-datacat" shape="rect">data
categories</a> they implement, and for each <a href="#def-datacat" shape="rect">data
- category</a> which type of selection they support, whether they support processing
+ category</a>, which type of selection they support, whether they support processing
of XML. If the implementation provides the conversion to NIF (see conformance clause
<a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="http://tbd:update" shape="rect">ITS 2.0 test suite</a>. All
tests specify which data category is processed (clause <a href="#its-conformance-2-1" shape="rect">2-1</a>); they are relevant for
@@ -772,7 +772,7 @@
absolute selector as defined in <a class="section-ref" href="#selectors" shape="rect">Section 5.3: Query Language of Selectors</a>.</p></li><li><p><a href="#selection-local" shape="rect">Locally in a document</a>: the selection is
realized using ITS local attributes, which are attached to an element node, or the<code class="its-elem-markup">span</code> element. There is no additional <code class="its-attr-markup">selector</code>
attribute. The default selection for each data category defines whether the selection
- covers attributes and child elements. 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></ul><p>The two locations are described in detail below.</p><div class="div3">
+ covers attributes and child elements. 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></ul><p>The two locations are described in detail below.</p><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="selection-global" id="selection-global" shape="rect"/>5.2.1 Global, Rule-based Selection</h4><p>Global, rule-based selection is implemented using the <code class="its-elem-markup">rules</code> element. The
<code class="its-elem-markup">rules</code> element contains zero or more <a href="#rule-elements" shape="rect">rule
elements</a>. Each <a href="#rule-elements" shape="rect">rule element</a> has a mandatory
@@ -787,7 +787,7 @@
nodes, or for pointing to existing notes in the document. For the former purpose, a
<code class="its-elem-markup">locNote</code> element can be used. For the latter purpose, a
<code class="its-attr-markup">locNotePointer</code> attribute can be used.</p><p>The <a href="#datacategories-overview" shape="rect">data category overview table</a>, in
- <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>, provides an overview of
+ <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>, provides an overview of
what data categories allow to point to existing information or to add information.</p><p>The functionalities of adding information and pointing to existing information are
<em>mutually exclusive</em>. That is: markup for pointing and adding the same
information <a href="#rfc-keywords" shape="rect">MUST NOT</a> appear in the same rule
@@ -797,7 +797,7 @@
<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="selection-local" id="selection-local" shape="rect"/>5.2.2 Local Selection in an XML Document</h4><p>Local selection in XML documents is realized with <a href="#local-attributes" shape="rect">ITS
local attributes</a> or the <code class="its-elem-markup">span</code> element. <code class="its-elem-markup">span</code> serves just as a
carrier for the local ITS attributes.</p><p>The data category determines what is being selected. The necessary data category
- specific defaults are described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-local-1" id="EX-selection-local-1" shape="rect"/>Example 12: Defaults for various data categories</div><p>By default the content of all elements in a document is translatable. The attribute
+ specific defaults are described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-local-1" id="EX-selection-local-1" shape="rect"/>Example 12: Defaults for various data categories</div><p>By default the content of all elements in a document is translatable. The attribute
<code>its:translate="no"</code> in the <code>head</code> element means that the
content of this element, including child elements, is not intended for translation. The
attribute <code>its:translate="yes"</code> in the <code>title</code> element means
@@ -873,7 +873,7 @@
<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="css-selectors" id="css-selectors" shape="rect"/>5.3.3 CSS Selectors</h4><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <code>CSS Selectors</code> is used throughout the specification in the
sense of <code>Selectors</code> as specified in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a> to prevent confusion with the generic use of the word "selector".
See <a href="#css-selectors" shape="rect">The term CSS Selector</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-implementations">The working group will not provide a CSS Selectors-based
- implementation; nevertheless there are several existing libraries, that can
+ implementation; nevertheless there are several existing libraries that can
translate CSS Selectors to XPath so that XPath selectors-based implementations can
be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by the value <code>css</code> in the
@@ -989,12 +989,12 @@
<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>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>Selection via inherited values. This applies only
- to element nodes. The inheritance rules are laid out in a dedicated <a href="#datacategories-overview" shape="rect">datacategory overview table</a>: see the column
+ to element nodes. The inheritance rules are laid out in a dedicated <a href="#datacategories-overview" shape="rect">data category overview table</a>: see the column
"<span class="quote">Inheritance for element nodes</span>". Selection via inheritance takes
- precedence over default values, see below item.</p></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 over default values, see below item.</p></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.
- E.g. defaults are overridden by inherited values and these are overriden by nodes
+ all information provided via lower precedence is overridden by the higher precedence.
+ E.g. defaults are overridden by inherited values and these are overridden by nodes
selected via global rules, which are in turn overridden by local markup.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-precedence-1" id="EX-selection-precedence-1" shape="rect"/>Example 20: Conflicts between selections of ITS information resolved using the precedence
order</div><p>The two elements <code>title</code> and <code>author</code> of this document are intended as separate content when inside a <code>prolog</code> element, but in other
contexts as part of the content of their parent element. In order to make this
@@ -1280,8 +1280,8 @@
</p><p>
<a href="#EX-within-text-local-1" shape="rect">Example 49</a> demonstrates the <a href="#elements-within-text" shape="rect">Elements Within Text</a> data category with the local
XML attribute <code class="its-attr-markup">withinText</code>. <a href="#EX-within-text-local-html5-1" shape="rect">Example 50</a> demonstrates the counterpart in HTML, i.e.,
- the local attribute <code class="its-attr-markup">its-within-text</code>.</p><p>Values of attributes which corresponds to data categories with a predefined set of
- values <a href="#rfc2119" shape="rect">MUST</a> be matched ASCII-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 the <a href="#terminology" shape="rect">terminology data category</a> can be stored as
+ the local attribute <code class="its-attr-markup">its-within-text</code>.</p><p>Values of attributes, which corresponds to data categories with a predefined set of
+ values, <a href="#rfc2119" shape="rect">MUST</a> be matched ASCII-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 the <a href="#terminology" shape="rect">terminology data category</a> can be stored as
<code class="its-attr-markup">its-term</code>, <code>ITS-TERM</code>, <code>its-Term</code> etc. All of those
attributes are treated as equivalent and will be normalized upon DOM construction.</p></div><p>Values of attributes that correspond to data categories that use <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double" shape="rect">XML Schema double
data type</a>
@@ -1317,9 +1317,9 @@
details.</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). Selection
via inheritance takes precedence over default values (see below).</p></div></li><li><p>Selection via inherited values. This applies only to element nodes. The
- inheritance rules are laid out in a dedicated <a href="#datacategories-overview" shape="rect">datacategory overview table</a> (see the column "<span class="quote">Inheritance for element
+ inheritance rules are laid out in a dedicated <a href="#datacategories-overview" shape="rect">data category overview table</a> (see the column "<span class="quote">Inheritance for element
nodes). Selection via inheritance takes precedence over default values (see
- below).</span>"</p></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
+ below).</span>"</p></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><p>
<a href="#EX-translate-html5-global-1" shape="rect">Example 6</a>, previously discussed,
demonstrates the precedence: the <code>code</code> element with the <code class="its-attr-markup">translate</code>
@@ -1329,7 +1329,7 @@
<em>This section is normative.</em>
</p><p>XHTML documents aimed at public consumption by Web browsers, including HTML5 documents in
XHTML syntax, <a href="#rfc2119" shape="rect">SHOULD</a> use the syntax described in <a class="section-ref" href="#html5-markup" shape="rect">Section 6: Using ITS Markup in HTML</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 class="exampleOuter"><div class="exampleHeader"><a name="EX-xhtml-markup-1" id="EX-xhtml-markup-1" shape="rect"/>Example 26: Using ITS 2.0 markup in XHTML</div><p>This examples illustrates the use of ITS 2.0 local markup in XHTML.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"></strong>
+ HTML Design Principle</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-xhtml-markup-1" id="EX-xhtml-markup-1" shape="rect"/>Example 26: Using ITS 2.0 markup in XHTML</div><p>This example illustrates the use of ITS 2.0 local markup in XHTML.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"></strong>
<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>XHTML and ITS2.0<strong class="hl-tag" style="color: #000096"></title></strong>
@@ -1349,7 +1349,7 @@
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="datacategory-description" id="datacategory-description" shape="rect"/>8 Description of Data Categories</h2><p>
<em>This section is normative.</em>
</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="datacategories-defaults-etc" id="datacategories-defaults-etc" shape="rect"/>8.1 Position, Defaults, Inheritance and Overriding of Data Categories</h3><p>The following table summarizes for each data category which selection, default value,
+<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="datacategories-defaults-etc" id="datacategories-defaults-etc" shape="rect"/>8.1 Position, Defaults, Inheritance, and Overriding of Data Categories</h3><p>The following table summarizes for each data category which selection, default value,
and inheritance and overriding behavior apply. It also provides data category
identifiers used in <a class="section-ref" href="#its-tool-annotation" shape="rect">Section 5.8: ITS Tools Annotation</a>.</p><p>Foreign elements can be used only inside <code class="its-elem-markup">rules</code>. Foreign attributes can be used on any element defined in ITS.</p><ul><li><p id="def-default-values">
<em>Default values</em> apply if both local and global selection
@@ -1360,7 +1360,7 @@
to child elements of nodes and attributes related to these nodes or their child
notes. The inheritance for the <a href="#trans-datacat" shape="rect">Translate</a> data
category, for example, mandates that all child elements of nodes are translatable
- whereas all attributes related to these the nodes or their child notes are not
+ whereas all attributes related to these nodes or their child notes are not
translatable.</p></li><li><p id="def-overriding">For ITS data categories with inheritance, the
information conveyed by the data category can be overridden. For example, a local
<code class="its-attr-markup">translate</code> attribute overrides the <a href="#trans-datacat" shape="rect">Translate</a> information conveyed by a global
@@ -1528,7 +1528,7 @@
data category settings of attributes using local markup. This limitation is
consistent with the advised practice of not using translatable attributes. If
attributes need to be translatable, then
- this has to be declared globally. Note that this restriciption does not apply to <a href="#html5-translate-handling" shape="rect">HTML5</a>.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-2" id="EX-translate-selector-2" shape="rect"/>Example 29: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed
+ this has to be declared globally. Note that this restriction does not apply to <a href="#html5-translate-handling" shape="rect">HTML5</a>.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-2" id="EX-translate-selector-2" shape="rect"/>Example 29: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed
locally</div><p>The local <code>its:translate="no"</code> specifies that the content of
<code>panelmsg</code> is not to be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><messages</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><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><msg</strong> <span class="hl-attribute" style="color: #F5844C">num</span>=<span class="hl-value" style="color: #993300">"123"</span><strong class="hl-tag" style="color: #000096">></strong>Click Resume Button on Status Display or <strong class="hl-tag" style="color: #000096"><panelmsg</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">
@@ -1838,7 +1838,7 @@
namespace.</p><p>Applying the <a href="#language-information" shape="rect">Language Information</a> data
category to <code>xml:lang</code> attributes using global rules is not necessary,
since <code>xml:lang</code> is the standard way to specify language information in
- <a title="Extensible Markup Language
 (XML) 1.0 (Fifth Edition)" href="#xml10spec" shape="rect">[XML 1.0]</a> .</p><p>In HTML <code>lang</code> is the mandated means of language identification.</p></div></div><div class="div3">
+ <a title="Extensible Markup Language
 (XML) 1.0 (Fifth Edition)" href="#xml10spec" shape="rect">[XML 1.0]</a>.</p><p>In HTML <code>lang</code> is the mandated means of language identification.</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="langinfo-implementation" id="langinfo-implementation" shape="rect"/>8.6.2 Implementation</h4><p>The <a href="#language-information" shape="rect">Language Information</a> data category can
be expressed only with global rules. For elements, the data category information <a href="#def-inheritance" shape="rect">inherits</a> to the textual content of the element,
<em>including</em> child elements and attributes. There is no default.</p><p id="languageinformation-global">GLOBAL: The <code class="its-elem-markup">langRule</code> element contains
@@ -1853,18 +1853,18 @@
viewpoint. This 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
+ "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>
<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,
+ "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>
<code>Palouse horses<fn>A Palouse horse is the same as an
Appaloosa.</fn> have spotted coats.</code>
</p></li><li><p>
- "no" : The element splits the text flow of its parent element and
+ "no": The element splits the text flow of its parent element and
its content is an independent text flow. For example the element <code>p</code>
when inside the element <code>li</code> in DITA or XHTML:</p><p>
<code><li>Palouse horses: <p>They have spotted coats.</p>
@@ -1928,7 +1928,7 @@
subject of content. Such information allows for more relevant linguistic choices
during various processes.</p><p>Examples of usage include:</p><ul><li><p>Allowing machine translation systems to select the most appropriate engine and
rules to translate the content.</p></li><li><p>Providing a general indication of what terminology collection is most suitable for use by
- translators.</p></li></ul><p>This data category addresses various challenges:</p><ul><li><p>Often domain-related information already exist in the document (e.g., keywords
+ translators.</p></li></ul><p>This data category addresses various challenges:</p><ul><li><p>Often domain-related information already exists in the document (e.g., keywords
in the HTML <code>meta</code> element). The <a href="#domain" shape="rect">Domain</a> data
category provides a mechanism to point to this information.</p></li><li><p>There are many flat or structured lists of domain related values, keywords, key
phrases, classification codes, ontologies, etc. The <a href="#domain" shape="rect">Domain</a> data category does not propose its own given list. Instead it
@@ -1974,7 +1974,7 @@
context of the <a href="#domain" shape="rect">Domain</a> data category) can accommodate
""workflow/multi engine" scenarios.</p><p>Example:</p><ul><li><p>A scenario involves Machine Translation (MT) engines A and B. The domain
labels used by engine A follow the naming scheme A_123, the one for engine B
- follow the naming scheme B_456.</p></li><li><p>A <code class="its-attr-markup">domainMapping</code> like the following is in place:
+ follow the naming scheme B_456.</p></li><li><p>A <code class="its-attr-markup">domainMapping</code> as follows is in place:
domainMapping="'sports law' Legal, 'property law' Legal"</p></li><li><p>Engine A maps 'Legal' to A_4711, Engine B maps 'Legal' to B_42.</p></li></ul><p>Thus, ITS does not encode a process or workflow (like "Use MT engine A with domain
A_4711, and use MT engine B with domain A_42"). Rather, it encodes information that
can be used in workflows.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-domain-1" id="EX-domain-1" shape="rect"/>Example 51: The <code class="its-elem-markup">domainRule</code> element</div><p>The <code class="its-elem-markup">domainRule</code> element expresses that the content of the HTML
@@ -2096,7 +2096,7 @@
<code class="its-attr-markup">taClassRefPointer</code>
attribute that contains a
<a href="#selectors" shape="rect">relative selector</a>
- pointing to a node that holds an IRI which implements the
+ pointing to a node that holds an IRI, which implements the
<a href="#textAnalysis-info-pieces" shape="rect">entity type / concept class
</a>
information.</p></li><li><p>Exactly one of the following:</p><ul><li><p>
@@ -2158,7 +2158,7 @@
<code class="its-attr-markup">its-annotators-ref</code>) attribute specified for the
<a href="#textanalysis" shape="rect">Text Analysis</a>
data category. For more information, see
- <a class="section-ref" href="#its-tool-annotation" shape="rect">Section 5.8: ITS Tools Annotation</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-text-analysis-html5-local-1" id="EX-text-analysis-html5-local-1" shape="rect"/>Example 53: Local mixed usage of Usage of <code class="its-attr-markup">taClassRef</code>, and <code class="its-attr-markup">taIdentRef</code> in HTML. </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+ <a class="section-ref" href="#its-tool-annotation" shape="rect">Section 5.8: ITS Tools Annotation</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-text-analysis-html5-local-1" id="EX-text-analysis-html5-local-1" shape="rect"/>Example 53: Local mixed usage of <code class="its-attr-markup">taClassRef</code>, and <code class="its-attr-markup">taIdentRef</code> in HTML.</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">"en"</span> <span class="hl-attribute" style="color: #F5844C">its-annotators-ref</span>=<span class="hl-value" style="color: #993300">"text-analysis|http://enrycher.ijs.si"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">"utf-8"</span><strong class="hl-tag" style="color: #000096"> /></strong>
@@ -2177,11 +2177,10 @@
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-text-analysis-html5-local-1.html" shape="rect">examples/html5/EX-text-analysis-html5-local-1.html</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p> For expressing <a href="#textAnalysis-info-pieces" shape="rect">Entity type / concept class </a>
information, implementers are encouraged to use an existing repository of entity
- types such as the Named Entity Recognition and Disambiguation <a title="" href="#nerd" shape="rect">[NERD]</a> ontology. Of course this requires that the repository satisfy the
- constraints imposed by the text analysis data category (e.g., use of IRIs). </p><p>
+ types such as the Named Entity Recognition and Disambiguation <a title="" href="#nerd" shape="rect">[NERD]</a> ontology. Of course this requires that the repository satisfies the
+ constraints imposed by the text analysis data category (e.g., use of IRIs).</p><p>
Various target types can be expressed via
- <a href="#textAnalysis-info-pieces" shape="rect">Entity type / concept class
- </a>: types of entities, types of lexical concepts, or ontology
+ <a href="#textAnalysis-info-pieces" shape="rect">Entity type / concept class</a>: types of entities, types of lexical concepts, or ontology
concepts. While a relationship between these types may exist, this
specification does not prescribe a way of automatically inferring a
one target type from another.
@@ -2193,9 +2192,9 @@
to consume these formats. For other usage scenarios (e.g., adding text annotation to
feed into a subsequent terminology process), using native ITS Text Analysis data
category markup is preferred. In this way, the markup easily can be stripped out
- again later.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-text-analysis-html5-rdfa" id="EX-text-analysis-html5-rdfa" shape="rect"/>Example 54: Local mixed usage of <code class="its-attr-markup">taClassRefPointer</code>, and
+ again later.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-text-analysis-html5-rdfa" id="EX-text-analysis-html5-rdfa" shape="rect"/>Example 54: Local mixed usage of <code class="its-attr-markup">taClassRefPointer</code>, and
<code class="its-attr-markup">taIdentRefPointer</code>, in HTML+RDFa Lite. </div><p> See <a href="#EX-text-analysis-html5-rdfa-companion-document" shape="rect">Example 55</a>
- for the companion document with the mapping data. </p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+ for the companion document with the mapping data.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -2208,7 +2207,7 @@
<span class="hl-attribute" style="color: #F5844C">typeof</span>=<span class="hl-value" style="color: #993300">"http:/nerd.eurecom.fr/ontology#Location"</span><strong class="hl-tag" style="color: #000096">></strong>Dublin<strong class="hl-tag" style="color: #000096"></span></strong> is
the capital of Ireland.<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-text-analysis-html5-rdfa.html" shape="rect">examples/html5/EX-text-analysis-html5-rdfa.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-text-analysis-html5-rdfa-companion-document" id="EX-text-analysis-html5-rdfa-companion-document" shape="rect"/>Example 55: Companion document, having the mapping data for <a href="#EX-text-analysis-html5-rdfa" shape="rect">Example 54</a> . </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <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">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
+<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-text-analysis-html5-rdfa.html" shape="rect">examples/html5/EX-text-analysis-html5-rdfa.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-text-analysis-html5-rdfa-companion-document" id="EX-text-analysis-html5-rdfa-companion-document" shape="rect"/>Example 55: Companion document, having the mapping data for <a href="#EX-text-analysis-html5-rdfa" shape="rect">Example 54</a>.</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <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">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:textAnalysisRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//*[@typeof and @about]"</span>
<span class="hl-attribute" style="color: #F5844C">taClassRefPointer</span>=<span class="hl-value" style="color: #993300">"@typeof"</span> <span class="hl-attribute" style="color: #F5844C">taIdentRefPointer</span>=<span class="hl-value" style="color: #993300">"@about"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
@@ -2312,8 +2311,8 @@
computer assisted translation tools, may offer an easy way to create this information.
Translation tools can then present this information to post-editors or translation
workflow managers. Web applications may to present such information to consumers of
- translated documents.</p><p>The data category defines seven pieces of information:</p><a name="provenanceDefs" id="provenanceDefs" shape="rect"/><table border="1" width="100%"><thead><tr><td rowspan="1" colspan="1">Information</td><td rowspan="1" colspan="1">Description</td><td rowspan="1" colspan="1">Value</td></tr></thead><tbody><tr><td rowspan="1" colspan="1">Human provenance information</td><td rowspan="1" colspan="1">Identification of a human translation agent</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Organisational provenance information</td><td rowspan="1" colspan="1">Identification of an organization acting as a translation agent</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Tool-related provenance information</td><td rowspan="1" colspan="1">Identification of a software tool that was used in translating th selected
- content</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Human revision provenance information</td><td rowspan="1" colspan="1">Identification of a human translation revision agent</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Organisational revision provenance information</td><td rowspan="1" colspan="1">Identification of an organization acting as a translation revision
+ translated documents.</p><p>The data category defines seven pieces of information:</p><a name="provenanceDefs" id="provenanceDefs" shape="rect"/><table border="1" width="100%"><thead><tr><td rowspan="1" colspan="1">Information</td><td rowspan="1" colspan="1">Description</td><td rowspan="1" colspan="1">Value</td></tr></thead><tbody><tr><td rowspan="1" colspan="1">Human provenance information</td><td rowspan="1" colspan="1">Identification of a human translation agent</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Organizational provenance information</td><td rowspan="1" colspan="1">Identification of an organization acting as a translation agent</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Tool-related provenance information</td><td rowspan="1" colspan="1">Identification of a software tool that was used in translating th selected
+ content</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Human revision provenance information</td><td rowspan="1" colspan="1">Identification of a human translation revision agent</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Organizational revision provenance information</td><td rowspan="1" colspan="1">Identification of an organization acting as a translation revision
agent</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Tool-related revision provenance information</td><td rowspan="1" colspan="1">Identification of a software tool that was used in revising the translation of
the selected content</td><td rowspan="1" colspan="1">A string or an IRI (only for the <code>Ref</code> attributes)</td></tr><tr><td rowspan="1" colspan="1">Reference to external provenance information</td><td rowspan="1" colspan="1">A reference to external provenance information</td><td rowspan="1" colspan="1">A space (U+0020) separated list of IRIs</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The tool related provenance and tool related revision provenance pieces of
information are not meant to express information about tools used for creating ITS
@@ -2331,8 +2330,8 @@
related to the content selected via the <code class="its-attr-markup">selector</code> attribute.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-provenance-global-1" id="EX-provenance-global-1" shape="rect"/>Example 59: The <a href="#provenance" shape="rect">Provenance</a> data category used globally with
standoff provenance records.</div><p>This example expresses provenance information in a standoff manner using
<code>provenanceRecords</code> elements. The <code class="its-elem-markup">provRule</code> element specifies
- that for any element with a <code>ref</code> attribute, that <code>ref</code>
- attribute hold a reference to an associated <code class="its-elem-markup">provenanceRecords</code> element where
+ that for any element with a <code>ref</code> attribute that <code>ref</code>
+ attribute holds a reference to an associated <code class="its-elem-markup">provenanceRecords</code> element where
the provenance information is listed. The <code>legalnotice</code> element has been
revised two times. Hence, the related <code class="its-elem-markup">provenanceRecords</code> element contains
two <code class="its-elem-markup">provenanceRecord</code> child 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>
@@ -2370,7 +2369,7 @@
category locally is limited to a single occurrence for a given content (e.g., one
cannot have different <code class="its-attr-markup">toolRef</code> attributes applied 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 <a href="#provenance" shape="rect">Provenance</a> data category:</p><ul><li><p>Either (inline markup): at least one of the following attributes:</p><ul><li><p>A <code class="its-attr-markup">person</code> or <code class="its-attr-markup">personRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">human provenance information</a>.</p></li><li><p>An <code class="its-attr-markup">org</code> or <code class="its-attr-markup">orgRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">organisational provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">tool</code> or <code class="its-attr-markup">toolRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">tool-related provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">revPerson</code> or <code class="its-attr-markup">revPersonRef</coe> attribute that implements the <a href="#provenanceDefs" shape="rect">human revision provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">revOrg</code> or <code class="its-attr-markup">revOrgRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">organisational revision provenance
+ markup</em> is provided to allow such cases.</p><p>The following local markup is available for the <a href="#provenance" shape="rect">Provenance</a> data category:</p><ul><li><p>Either (inline markup): at least one of the following attributes:</p><ul><li><p>A <code class="its-attr-markup">person</code> or <code class="its-attr-markup">personRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">human provenance information</a>.</p></li><li><p>An <code class="its-attr-markup">org</code> or <code class="its-attr-markup">orgRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">organizational provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">tool</code> or <code class="its-attr-markup">toolRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">tool-related provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">revPerson</code> or <code class="its-attr-markup">revPersonRef</coe> attribute that implements the <a href="#provenanceDefs" shape="rect">human revision provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">revOrg</code> or <code class="its-attr-markup">revOrgRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">organizational revision provenance
information</a>.</p></li><li><p>A <code class="its-attr-markup">revTool</code> or <code class="its-attr-markup">revToolRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">tool-related revision provenance
information</a>.</p></li><li><p>A <code class="its-attr-markup">provRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">reference to external provenance
descriptions</a>.</p></li></ul></li><li><p>Or (standoff markup):</p><ul><li><p>A <code class="its-attr-markup">provenanceRecordsRef</code> attribute. Its value is an IRI pointing to
@@ -2380,13 +2379,13 @@
least one of the following attributes:</p><ul><li><p>A <code class="its-attr-markup">person</code> or <code class="its-attr-markup">personRef</code> attribute that implements
the <a href="#provenanceDefs" shape="rect">human provenance
information</a>.</p></li><li><p>An <code class="its-attr-markup">org</code> or <code class="its-attr-markup">orgRef</code> attribute that implements the
- <a href="#provenanceDefs" shape="rect">organisational provenance
+ <a href="#provenanceDefs" shape="rect">organizational provenance
information</a>.</p></li><li><p>A <code class="its-attr-markup">tool</code> or <code class="its-attr-markup">toolRef</code> attribute that implements the
<a href="#provenanceDefs" shape="rect">tool-related provenance
information</a>.</p></li><li><p>A <code class="its-attr-markup">revPerson</code> or <code class="its-attr-markup">revPersonRef</code> attribute that
implements the <a href="#provenanceDefs" shape="rect">human revision provenance
information</a>.</p></li><li><p>A <code class="its-attr-markup">revOrg</code> or <code class="its-attr-markup">revOrgRef</code> attribute that implements
- the <a href="#provenanceDefs" shape="rect">organisational revision provenance
+ the <a href="#provenanceDefs" shape="rect">organizational revision provenance
information</a>.</p></li><li><p>A <code class="its-attr-markup">revTool</code> or <code class="its-attr-markup">revToolRef</code> attribute that
implements the <a href="#provenanceDefs" shape="rect">tool-related revision
provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">provRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">reference to external provenance
@@ -2402,7 +2401,7 @@
<code class="its-elem-markup">provenanceRecord</code> where they are declared.</p><p id="provenance-records-in-html5-constraint"> In HTML the standoff markup <a href="#rfc-keywords" shape="rect">MUST</a> either be stored inside a <code>script</code>
element in the same HTML document, or be linked from any
<code class="its-attr-markup">provenanceRecordsRef</code> to an external XML or HTML file with the
- standoff inside. If standoff is inside a <code>script</code> element, that element
+ standoff inside. If standoff is inside a <code>script</code> element that element
<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
@@ -2561,7 +2560,7 @@
[138 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/21 17:38:26 1.472
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/23 08:54:47 1.473
@@ -2,7 +2,7 @@
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rng="http://relaxng.org/ns/structure/1.0"
xmlns:spec="http://example.com/xmlspec" xmlns:xlink="http://www.w3.org/1999/xlink"
- xmlns:xi="http://www.w3.org/2001/XInclude" xml:lang="en">
+ xmlns:xi="http://www.w3.org/2001/XInclude" xml:lang="en-US">
<header xmlns="http://example.com/xmlspec">
<title>Internationalization Tag Set (ITS) Version 2.0</title>
<w3c-designation>ITS20</w3c-designation>
@@ -237,7 +237,7 @@
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-motivation-its-1.xml"/>
</exemplum>
- <p>ITS proposes several mechanisms, which differ amongst others in terms of the usage scenario/user types for which the mechanism is most suitable.</p>
+ <p>ITS proposes several mechanisms, which differ among others in terms of the usage scenario/user types for which the mechanism is most suitable.</p>
<exemplum xml:id="EX-motivation-its-2">
<head>Document that uses two different ITS mechanisms to indicate that some parts have to be left untranslated.</head>
@@ -261,7 +261,7 @@
<list type="ordered">
<item>Provide metadata (e.g. <q>Do not translate</q>) to assist internationalization-related processes</item>
- <item>Use XPath (so-called <ref target="#selection-global">global appraoch</ref>) to associate metadata with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the metadata straight onto the XML nodes themselves (so-called <ref target="#def-local-attributes">local approach</ref>)</item>
+ <item>Use XPath (so-called <ref target="#selection-global">global approach</ref>) to associate metadata with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the metadata straight onto the XML nodes themselves (so-called <ref target="#def-local-attributes">local approach</ref>)</item>
<item>Work with a well-defined set of metadata categories or values (e.g. only the values <val>yes</val> and <val>no</val> for certain data categories)</item>
@@ -324,7 +324,7 @@
provenance-related requirement by allowing ITS processors to leave a trace: ITS
processors can basically say <q>It is me that generated this bit of
information</q>. Another example are the <ptr target="#nif-reference"
- type="bibref"/> related details of ITS 2.0 which help to couple Natural Language
+ type="bibref"/> related details of ITS 2.0, which help to couple Natural Language
Processing with concepts of the Semantic Web.</p>
</div>
@@ -332,7 +332,7 @@
- <p>The <ptr target="#its10" type="bibref"/> <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#introduction">introduction</ref> states: <q>ITS is a technology to easily create XML which is internationalized and can be localized effectively</q>. In order to make this tangible, ITS 1.0 provided examples for <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage">users and usages</ref>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multilingual production.</p>
+ <p>The <ptr target="#its10" type="bibref"/> <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#introduction">introduction</ref> states: <q>ITS is a technology to easily create XML, which is internationalized and can be localized effectively</q>. In order to make this tangible, ITS 1.0 provided examples for <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage">users and usages</ref>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multilingual production.</p>
@@ -388,8 +388,8 @@
the time were conceived as being closely tied to human actors such as content authors or
information architects. ITS 2.0 raises non-human actors such as word processors/editors,
content management systems, machine translation systems, term candidate generators,
- entity identifiers/disambiguators to the same level. This change amongst others is
- reflected by the ITS 2.0 <ref target="#its-tool-annotation">Tool Annotation</ref> which
+ entity identifiers/disambiguators to the same level. This change among others is
+ reflected by the ITS 2.0 <ref target="#its-tool-annotation">Tool Annotation</ref>, which
allows systems to record that they have processed a certain part of content.</p>
@@ -411,7 +411,7 @@
<ref
target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element"
>ruby model in HTML5</ref> was still under development. Once these discussions are
- settled, the Ruby data category possibly will be re-introduced, in a subsequent
+ settled, the Ruby data category possibly will be reintroduced, in a subsequent
version of ITS.</p></item>
<item> <p>The <ref target="#directionality">Directionality</ref> data category reflects directionality markup in <ptr target="#html4" type="bibref"/>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</p></item></list>
@@ -420,7 +420,7 @@
<list>
<item><p xml:id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <ref target="#basic-concepts-selection-global">global rules</ref>. ITS 2.0 allows for choosing the <ref target="#selectors">query language of selectors</ref>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></item>
<item><p xml:id="parameters-in-selector">In global rules it is now possible to set <ref target="#its-param">variables for the selectors</ref> (XPath expression). The <gi>param</gi> element serves this purpose.</p></item>
- <item>ITS 2.0 has a <ref target="#its-tool-annotation">ITS Tools Annotation</ref> mechanism to associate processor information with the use of individual data categories. See <ptr target="#traceability" type="specref"/> for details.</item>
+ <item>ITS 2.0 has an <ref target="#its-tool-annotation">ITS Tools Annotation</ref> mechanism to associate processor information with the use of individual data categories. See <ptr target="#traceability" type="specref"/> for details.</item>
</list>
<p><emph>Mappings:</emph> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <ptr target="#nif-reference" type="bibref"/> and links to guidance about how to relate ITS 2.0 to XLIFF. See <ptr target="#mapping-conversion" type="specref"/> for details.</p>
@@ -474,7 +474,7 @@
algorithm.</item>
<item><ref target="#language-information">Language Information</ref>: expresses the
language of a given piece of content.</item>
- <item><ref target="#elements-within-text">Elements Witin Text:</ref> expresses how
+ <item><ref target="#elements-within-text">Elements Within Text:</ref> expresses how
content of an element is related to the text flow (constitutes its own segment like
paragraphs, is part of a segment like emphasis marker etc.).</item>
<item><ref target="#domain">Domain</ref>: identifies the topic or subject of the
@@ -649,7 +649,7 @@
target="examples/xml/EX-basic-concepts-3.xml"/>
</exemplum>
<p>For XML content, <ref target="#datacategories-overview">data category specific defaults</ref> are provided. These are independent of the actual XML markup vocabulary. Example for the <ref target="#trans-datacat">Translate</ref> data category: <code>translate="yes"</code> for elements, and <code>translate="no"</code> for attributes.</p>
- <p>For <ptr target="#html5" type="bibref"/>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence, that HTML markup is normatively interpreted as ITS 2.0 data category information (see <ptr target="#html5-existing-markup-versus-its" type="specref"/> for more information).</p>
+ <p>For <ptr target="#html5" type="bibref"/>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence that HTML markup is normatively interpreted as ITS 2.0 data category information (see <ptr target="#html5-existing-markup-versus-its" type="specref"/> for more information).</p>
</div>
<div xml:id="basic-concepts-addingpointing">
<head>Adding Information or Pointing to Existing Information</head>
@@ -751,7 +751,7 @@
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/html5/EX-its-and-existing-HTML5-markup.html"/>
</exemplum>
- <p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behaviors as certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <ref target="#terminology">Terminology</ref> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. For example, a rule can be used to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes"</code>. For additional examples see the <ref target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml">XML I18N Best Practices</ref> document.</p>
+ <p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behaviors as certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <ref target="#terminology">Terminology</ref> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. For example, a rule can be used to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes"</code>. For additional examples, see the <ref target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml">XML I18N Best Practices</ref> document.</p>
</div>
<div xml:id="html5-standoff-markup-explanation"><head>Standoff markup in HTML5</head>
@@ -944,12 +944,12 @@
<p>The usage of the term <emph>conformance clause</emph> in this section is in compliance
with <ptr target="#qa-framework" type="bibref"/>.</p>
<p>This specification defines four types of conformance: conformance of <ref
- target="#conformance-product-schema">1) ITS markup declarations</ref> , conformance of
+ target="#conformance-product-schema">1) ITS markup declarations</ref>, conformance of
<ref target="#conformance-product-processing-expectations">2) processing expectations
for ITS Markup</ref>, conformance of <ref
target="#conformance-product-html-processing-expectations">3) processing expectations
for ITS Markup in HTML</ref>, and <ref target="#conformance-product-html5-its"
- >Conformance Type 4: Markup conformance for HTML5+ITS documents</ref>.
+ >4) markup conformance for HTML5+ITS documents</ref>.
The conformance type 4 is defined for using ITS markup in HTML5 documents, HTML5+ITS,
which serves as an <emph>applicable specification</emph> in the sense specified in the
<ref target="http://www.w3.org/TR/html5/infrastructure.html#extensibility">Extensibility
@@ -1085,7 +1085,7 @@
<p xml:id="its-processing-conformance-claims">Statements related to this conformance type
<ref target="#rfc-keywords">MUST</ref> list all <ref target="#def-datacat">data
categories</ref> they implement, and for each <ref target="#def-datacat">data
- category</ref> which type of selection they support, whether they support processing
+ category</ref>, which type of selection they support, whether they support processing
of XML. If the implementation provides the conversion to NIF (see conformance clause
<ref target="#its-conformance-2-4">2-4</ref>), this <ref target="#rfc-keywords"
>MUST</ref> be stated.</p>
@@ -1416,7 +1416,7 @@
type="bibref"/> to prevent confusion with the generic use of the word "selector".
See <ref target="#css-selectors">The term CSS Selector</ref>.</p></note>
<note><p xml:id="css-selectors-implementations">The working group will not provide a CSS Selectors-based
- implementation; nevertheless there are several existing libraries, that can
+ implementation; nevertheless there are several existing libraries that can
translate CSS Selectors to XPath so that XPath selectors-based implementations can
be used.</p></note>
<note><p xml:id="css-selectors-and-attributes">CSS selectors have no ability to point to
@@ -1558,7 +1558,7 @@
</item>
<item xml:id="precedence-inheritance">Selection via inherited values. This applies only
to element nodes. The inheritance rules are laid out in a dedicated <ref
- target="#datacategories-overview">datacategory overview table</ref>: see the column
+ target="#datacategories-overview">data category overview table</ref>: see the column
<quote>Inheritance for element nodes</quote>. Selection via inheritance takes
precedence over default values, see below item.</item>
<item xml:id="precedence-defaults">Selections via defaults for data categories, see <ptr
@@ -1570,8 +1570,8 @@
<note>
<p>The precedence order fulfills the same purpose as the built-in template rules of <ptr
target="#xslt10" type="bibref"/>. Override semantics are always complete, that is
- all information provided via lower precedence is overriden by the higher precedence.
- E.g. defaults are overridden by inherited values and these are overriden by nodes
+ all information provided via lower precedence is overridden by the higher precedence.
+ E.g. defaults are overridden by inherited values and these are overridden by nodes
selected via global rules, which are in turn overridden by local markup.</p>
</note>
<exemplum xml:id="EX-selection-precedence-1">
@@ -1919,8 +1919,8 @@
XML attribute <att>withinText</att>. <ptr type="exref"
target="#EX-within-text-local-html5-1"/> demonstrates the counterpart in HTML, i.e.,
the local attribute <att>its-within-text</att>.</p>
- <p>Values of attributes which corresponds to data categories with a predefined set of
- values <ref target="#rfc2119">MUST</ref> be matched ASCII-case-insensitively. </p>
+ <p>Values of attributes, which corresponds to data categories with a predefined set of
+ values, <ref target="#rfc2119">MUST</ref> be matched ASCII-case-insensitively. </p>
<note><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in HTML the <ref
target="#terminology">terminology data category</ref> can be stored as
<att>its-term</att>, <code>ITS-TERM</code>, <code>its-Term</code> etc. All of those
@@ -1997,7 +1997,7 @@
</item>
<item>Selection via inherited values. This applies only to element nodes. The
inheritance rules are laid out in a dedicated <ref target="#datacategories-overview"
- >datacategory overview table</ref> (see the column <quote>Inheritance for element
+ >data category overview table</ref> (see the column <quote>Inheritance for element
nodes). Selection via inheritance takes precedence over default values (see
below).</quote></item>
<item>Selections via defaults for data categories, see <ptr
@@ -2023,7 +2023,7 @@
HTML Design Principle</ref>.</p>
<exemplum xml:id="EX-xhtml-markup-1">
<head>Using ITS 2.0 markup in XHTML</head>
- <p>This examples illustrates the use of ITS 2.0 local markup in XHTML.</p>
+ <p>This example illustrates the use of ITS 2.0 local markup in XHTML.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/html5/EX-xhtml-markup-1.html" type="html5"/>
</exemplum>
@@ -2072,7 +2072,7 @@
</schemaSpec>
<div xml:id="datacategories-defaults-etc">
- <head>Position, Defaults, Inheritance and Overriding of Data Categories</head>
+ <head>Position, Defaults, Inheritance, and Overriding of Data Categories</head>
<p>The following table summarizes for each data category which selection, default value,
and inheritance and overriding behavior apply. It also provides data category
@@ -2088,7 +2088,7 @@
to child elements of nodes and attributes related to these nodes or their child
notes. The inheritance for the <ref target="#trans-datacat">Translate</ref> data
category, for example, mandates that all child elements of nodes are translatable
- whereas all attributes related to these the nodes or their child notes are not
+ whereas all attributes related to these nodes or their child notes are not
translatable.</p></item>
<item><p xml:id="def-overriding">For ITS data categories with inheritance, the
information conveyed by the data category can be overridden. For example, a local
@@ -2451,7 +2451,7 @@
data category settings of attributes using local markup. This limitation is
consistent with the advised practice of not using translatable attributes. If
attributes need to be translatable, then
- this has to be declared globally. Note that this restriciption does not apply to <ref target="#html5-translate-handling">HTML5</ref>.</p></note>
+ this has to be declared globally. Note that this restriction does not apply to <ref target="#html5-translate-handling">HTML5</ref>.</p></note>
<exemplum xml:id="EX-translate-selector-2">
<head>The <ref target="#trans-datacat">Translate</ref> data category expressed
locally</head>
@@ -2845,7 +2845,7 @@
<p>Applying the <ref target="#language-information">Language Information</ref> data
category to <code>xml:lang</code> attributes using global rules is not necessary,
since <code>xml:lang</code> is the standard way to specify language information in
- <ptr target="#xml10spec" type="bibref"/> .</p>
+ <ptr target="#xml10spec" type="bibref"/>.</p>
<p>In HTML <code>lang</code> is the mandated means of language identification.</p>
</note>
</div>
@@ -2882,19 +2882,19 @@
hints for tools such as translation memory systems. The values associated with this
data category are:</p>
<list type="unordered">
- <item><p><val>yes</val> : The element and its content are part of the flow of its
+ <item><p><val>yes</val>: The element and its content are part of the flow of its
parent element. For example the element <code>strong</code> in <ptr type="bibref"
target="#xhtml10"/>:</p>
<p><code><strong>Appaloosa horses</strong> have spotted
coats.</code></p>
</item>
- <item><p><val>nested</val> : The element is part of the flow of its parent element,
+ <item><p><val>nested</val>: 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
<ptr target="#dita10" type="bibref"/>:</p>
<p><code>Palouse horses<fn>A Palouse horse is the same as an
Appaloosa.</fn> have spotted coats.</code></p>
</item>
- <item><p><val>no</val> : The element splits the text flow of its parent element and
+ <item><p><val>no</val>: The element splits the text flow of its parent element and
its content is an independent text flow. For example the element <code>p</code>
when inside the element <code>li</code> in DITA or XHTML:</p>
<p><code><li>Palouse horses: <p>They have spotted coats.</p>
@@ -2982,7 +2982,7 @@
</list>
<p>This data category addresses various challenges:</p>
<list type="unordered">
- <item>Often domain-related information already exist in the document (e.g., keywords
+ <item>Often domain-related information already exists in the document (e.g., keywords
in the HTML <code>meta</code> element). The <ref target="#domain">Domain</ref> data
category provides a mechanism to point to this information.</item>
<item>There are many flat or structured lists of domain related values, keywords, key
@@ -3101,7 +3101,7 @@
<item><p>A scenario involves Machine Translation (MT) engines A and B. The domain
labels used by engine A follow the naming scheme A_123, the one for engine B
follow the naming scheme B_456.</p></item>
- <item><p>A <att>domainMapping</att> like the following is in place:
+ <item><p>A <att>domainMapping</att> as follows is in place:
domainMapping="'sports law' Legal, 'property law' Legal"</p></item>
<item><p>Engine A maps 'Legal' to A_4711, Engine B maps 'Legal' to B_42.</p></item>
</list>
@@ -3328,7 +3328,7 @@
<att>taClassRefPointer</att>
attribute that contains a
<ref target="#selectors">relative selector</ref>
- pointing to a node that holds an IRI which implements the
+ pointing to a node that holds an IRI, which implements the
<ref target="#textAnalysis-info-pieces">entity type / concept class
</ref>
information.</p>
@@ -3434,7 +3434,7 @@
data category. For more information, see
<ptr target="#its-tool-annotation" type="specref" />.</p>
<exemplum xml:id="EX-text-analysis-html5-local-1">
- <head> Local mixed usage of Usage of <att>taClassRef</att>, and <att>taIdentRef</att> in HTML. </head>
+ <head>Local mixed usage of <att>taClassRef</att>, and <att>taIdentRef</att> in HTML.</head>
<egXML xmlns="http://www.tei-c.org/ns/Examples" type="html5"
target="examples/html5/EX-text-analysis-html5-local-1.html" />
</exemplum>
@@ -3442,12 +3442,11 @@
<p> For expressing <ref target="#textAnalysis-info-pieces">Entity type / concept class </ref>
information, implementers are encouraged to use an existing repository of entity
types such as the Named Entity Recognition and Disambiguation <ptr type="bibref"
- target="#nerd"/> ontology. Of course this requires that the repository satisfy the
- constraints imposed by the text analysis data category (e.g., use of IRIs). </p>
+ target="#nerd"/> ontology. Of course this requires that the repository satisfies the
+ constraints imposed by the text analysis data category (e.g., use of IRIs).</p>
<p>
Various target types can be expressed via
- <ref target="#textAnalysis-info-pieces">Entity type / concept class
- </ref>: types of entities, types of lexical concepts, or ontology
+ <ref target="#textAnalysis-info-pieces">Entity type / concept class</ref>: types of entities, types of lexical concepts, or ontology
concepts. While a relationship between these types may exist, this
specification does not prescribe a way of automatically inferring a
one target type from another.
@@ -3465,16 +3464,16 @@
category markup is preferred. In this way, the markup easily can be stripped out
again later.</p>
<exemplum xml:id="EX-text-analysis-html5-rdfa">
- <head> Local mixed usage of <att>taClassRefPointer</att>, and
+ <head>Local mixed usage of <att>taClassRefPointer</att>, and
<att>taIdentRefPointer</att>, in HTML+RDFa Lite. </head>
<p> See <ptr target="#EX-text-analysis-html5-rdfa-companion-document" type="exref"/>
- for the companion document with the mapping data. </p>
+ for the companion document with the mapping data.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples" type="html5"
target="examples/html5/EX-text-analysis-html5-rdfa.html"/>
</exemplum>
<exemplum xml:id="EX-text-analysis-html5-rdfa-companion-document">
<head> Companion document, having the mapping data for <ptr
- target="#EX-text-analysis-html5-rdfa" type="exref"/> . </head>
+ target="#EX-text-analysis-html5-rdfa" type="exref"/>.</head>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/html5/EX-text-analysis-html5-rdfa.xml"/>
</exemplum>
@@ -3616,7 +3615,7 @@
<cell>A string or an IRI (only for the <code>Ref</code> attributes)</cell>
</row>
<row>
- <cell>Organisational provenance information</cell>
+ <cell>Organizational provenance information</cell>
<cell>Identification of an organization acting as a translation agent</cell>
<cell>A string or an IRI (only for the <code>Ref</code> attributes)</cell>
</row>
@@ -3632,7 +3631,7 @@
<cell>A string or an IRI (only for the <code>Ref</code> attributes)</cell>
</row>
<row>
- <cell>Organisational revision provenance information</cell>
+ <cell>Organizational revision provenance information</cell>
<cell>Identification of an organization acting as a translation revision
agent</cell>
<cell>A string or an IRI (only for the <code>Ref</code> attributes)</cell>
@@ -3679,8 +3678,8 @@
standoff provenance records.</head>
<p>This example expresses provenance information in a standoff manner using
<code>provenanceRecords</code> elements. The <gi>provRule</gi> element specifies
- that for any element with a <code>ref</code> attribute, that <code>ref</code>
- attribute hold a reference to an associated <gi>provenanceRecords</gi> element where
+ that for any element with a <code>ref</code> attribute that <code>ref</code>
+ attribute holds a reference to an associated <gi>provenanceRecords</gi> element where
the provenance information is listed. The <code>legalnotice</code> element has been
revised two times. Hence, the related <gi>provenanceRecords</gi> element contains
two <gi>provenanceRecord</gi> child elements.</p>
@@ -3700,13 +3699,13 @@
<item><p>A <att>person</att> or <att>personRef</att> attribute that implements the <ref
target="#provenanceDefs">human provenance information</ref>.</p></item>
<item><p>An <att>org</att> or <att>orgRef</att> attribute that implements the <ref
- target="#provenanceDefs">organisational provenance information</ref>.</p></item>
+ target="#provenanceDefs">organizational provenance information</ref>.</p></item>
<item><p>A <att>tool</att> or <att>toolRef</att> attribute that implements the <ref
target="#provenanceDefs">tool-related provenance information</ref>.</p></item>
<item><p>A <att>revPerson</att> or <att>revPersonRef</att> attribute that implements the <ref
target="#provenanceDefs">human revision provenance information</ref>.</p></item>
<item><p>A <att>revOrg</att> or <att>revOrgRef</att> attribute that implements the <ref
- target="#provenanceDefs">organisational revision provenance
+ target="#provenanceDefs">organizational revision provenance
information</ref>.</p></item>
<item><p>A <att>revTool</att> or <att>revToolRef</att> attribute that implements the <ref
target="#provenanceDefs">tool-related revision provenance
@@ -3738,7 +3737,7 @@
</item>
<item>
<p>An <att>org</att> or <att>orgRef</att> attribute that implements the
- <ref target="#provenanceDefs">organisational provenance
+ <ref target="#provenanceDefs">organizational provenance
information</ref>.</p>
</item>
<item>
@@ -3753,7 +3752,7 @@
</item>
<item>
<p>A <att>revOrg</att> or <att>revOrgRef</att> attribute that implements
- the <ref target="#provenanceDefs">organisational revision provenance
+ the <ref target="#provenanceDefs">organizational revision provenance
information</ref>.</p>
</item>
<item>
@@ -3788,7 +3787,7 @@
target="#rfc-keywords">MUST</ref> either be stored inside a <code>script</code>
element in the same HTML document, or be linked from any
<att>provenanceRecordsRef</att> to an external XML or HTML file with the
- standoff inside. If standoff is inside a <code>script</code> element, that element
+ standoff inside. If standoff is inside a <code>script</code> element that element
<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
@@ -3903,7 +3902,7 @@
<item><p>Compare source and target content for quality verification.</p></item>
- <item><p>Re-use existing translations when localizing the new version of an existing
+ <item><p>Reuse existing translations when localizing the new version of an existing
document.</p></item>
<item><p>Access aligned bi-lingual content to build memories, or to train machine
@@ -4248,7 +4247,7 @@
allow attributes from another namespace we cannot use <att>locQualityIssuesRef</att>
directly. Instead, a global rule is used to map the function of
[139 lines skipped]
Received on Sunday, 23 June 2013 08:54:52 UTC