- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Thu, 30 May 2013 15:56:44 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv28906
Modified Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd
Log Message:
sec 1-2 editing, implementing changes from http://www.w3.org/2013/05/29-mlw-lt-minutes.html#item07 until modifications: dropped ruby
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/05/30 07:53:26 1.1
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/05/30 15:56:44 1.2
@@ -53,9 +53,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors" shape="rect">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage" shape="rect">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e1913" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2017" shape="rect">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2158" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2262" shape="rect">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param" shape="rect">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules" shape="rect">Link to External Rules</a></div>
@@ -512,17 +512,20 @@
<code>its-*</code> attributes introduced for <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> in older versions of HTML (such
as 3.2 or 4.01) and pages using these attributes will work without any problems,
<code>its-*</code> attributes will be marked as invalid in validators.</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="additional-data-categories" id="additional-data-categories" shape="rect"/>1.4.2 Additional data categories</h4><p>tbd</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="modified-datacategories" id="modified-datacategories" shape="rect"/>1.4.3 Modified data categories</h4><p>tbd</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="additional-data-categories" id="additional-data-categories" shape="rect"/>1.4.2 Additional data categories</h4><p>The following new data categories have been introduced in ITS 2.0</p><ul><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of a given content by passing domain identifiers from the content to applications and potentially mapping to application specific identifiers.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate the results of text analysis to be annotated in content.</p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that have been involved in the translaion of the content or the revision of the translated content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: identify a value that can be used as unique identifier for a given part of the content.
+ </p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a>: indicate how whitespace should be handled in content.</p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a>: describe the nature and severity of an error detected during a language-oriented quality assurance (QA) process.</p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a>: express an overall measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a>: indicate the confidence that MT systems provide about their translation.
+ </p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a>: specify the characters that are permitted in a given piece of content.</p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a>: specify the maximum storage size of a given content.</p></li></ul></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="modified-datacategories" id="modified-datacategories" shape="rect"/>1.4.3 Modified data categories</h4><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 since at the time of writing, a stable model for ruby was not available. There are ongoing discussions about the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a>. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p><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 enancements 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></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="additional-mechanisms" id="additional-mechanisms" shape="rect"/>1.4.4 Additional or modified mechanisms</h4><div class="div4">
<h5><a name="query-language-on-rules-element" id="query-language-on-rules-element" shape="rect"/>1.4.4.1 Query language on rules element</h5><p>tbd</p></div><div class="div4">
<h5><a name="modified-selectors" id="modified-selectors" shape="rect"/>1.4.4.2 Modified selectors</h5><p>tbd</p></div><div class="div4">
<h5><a name="parameters-in-selectors" id="parameters-in-selectors" shape="rect"/>1.4.4.3 Parameters in selectors</h5><p>tbd</p></div><div class="div4">
<h5><a name="traceability" id="traceability" shape="rect"/>1.4.4.4 Traceability</h5><p>tbd</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="mappings" id="mappings" shape="rect"/>1.4.5 Mappings</h4><div class="div4">
-<h5><a name="mapping-NIF" id="mapping-NIF" shape="rect"/>1.4.5.1 NIF</h5><p>tbd</p></div><div class="div4">
-<h5><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>1.4.5.2 XLIFF</h5><p>tbd</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="unicode-normalization" id="unicode-normalization" shape="rect"/>1.4.6 Unicode normalization</h4><p>tbd</p></div><div class="div3">
+<h5><a name="mapping-NIF" id="mapping-NIF" shape="rect"/>1.4.5.1 ITS and RDF/NIF</h5><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
+ representations) that contain ITS metadata to the RDF-based format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. The conversion results in RDF triples.</p><p>NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations. The conversion <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> is defined normatively. The backconversion <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div><div class="div4">
+<h5><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>1.4.5.2 ITS and XLIFF</h5><p>The XML Localization Interchange File Format <a title="" href="#xliff" shape="rect">[XLIFF]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.0 usage scenarios <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a>. These usage scenarios involve: 1) the mapping of ITS meta-data in a source document into XLIFF and ITS meta-data of the translatable content in XLIFF file; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS eta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rect">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="unicode-normalization" id="unicode-normalization" shape="rect"/>1.4.6 Unicode normalization</h4><p>As a general guidance, implementations of ITS 2.0 should use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. Further information on the topic of Unicode normalization is provided by <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</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="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.4.7 Extended implementation hints</h4><p>tbd</p></div></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
<em>This section is informative.</em>
@@ -669,7 +672,7 @@
and localization of XML schemas and documents.] The concept of a data
category is independent of its implementation in an XML and HTML environment (e.g. using
an element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "implementation" subsections in
- <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1002" id="d0e1002" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1106" id="d0e1106" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
to whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language independent
level is a <code class="its-attr-markup">translate</code> attribute with two possible values:
"yes" and "no". An implementation on a schema language specific
@@ -934,9 +937,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</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="d0e1913" id="d0e1913" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<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="d0e2017" id="d0e2017" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e1924" id="d0e1924" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2028" id="d0e2028" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
which starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
@@ -981,14 +984,14 @@
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 <code>css</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2135" id="d0e2135" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2239" id="d0e2239" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Both simple selectors
and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2145" id="d0e2145" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2249" id="d0e2249" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Selector is not
evaluated against the complete document tree but only against subtrees rooted at
nodes selected by selector in the <code class="its-attr-markup">selector</code> attribute.</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="d0e2158" id="d0e2158" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
+<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="d0e2262" id="d0e2262" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords" shape="rect">MUST</a> define:</p><ul><li><p>identifier of query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating absolute selector to collection of nodes;</p></li><li><p>rules for evaluating relative selector to collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/05/30 07:53:26 1.3
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/05/30 15:56:44 1.4
@@ -573,9 +573,60 @@
-->
<div xml:id="additional-data-categories"><head>Additional data categories</head>
- <p>tbd</p></div>
+ <p>The following new data categories have been introduced in ITS 2.0</p>
+
+ <list type="unordered">
+ <item><ref target="#domain">Domain</ref>: identify the topic or subject of a given content by passing domain identifiers from the content to applications and potentially mapping to application specific identifiers.</item>
+
+
+
+ <item><ref target="#textanalysis">Text Analysis</ref>: annotate the results of text analysis to be annotated in content.</item>
+
+
+
+ <item><ref target="#LocaleFilter">Locale Filter</ref>: specify that a piece of content is only applicable to certain locales. </item>
+
+
+
+ <item><ref target="#provenance">Provenance</ref>: communicate the identity of agents that have been involved in the translation of the content or the revision of the translated content.</item>
+
+
+
+ <item><ref target="#externalresource">External Resource</ref>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</item>
+
+
+
+ <item><ref target="#target-pointer">Target Pointer</ref>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</item>
+
+
+
+ <item><ref target="#idvalue">Id Value</ref>: identify a value that can be used as unique identifier for a given part of the content.
+ </item>
+
+
+ <item><ref target="#preservespace">Preserve Space</ref>: indicate how whitespace should be handled in content.</item>
+
+
+ <item><ref target="#lqissue">Localization Quality Issue</ref>: describe the nature and severity of an error detected during a language-oriented quality assurance (QA) process.</item>
+
+
+ <item><ref target="#lqrating">Localization Quality Rating</ref>: express an overall measurement of the localization quality of a document or an item in a document.</item>
+
+
+ <item><ref target="#mtconfidence">MT Confidence</ref>: indicate the confidence that MT systems provide about their translation.
+ </item>
+
+
+ <item> <ref target="#allowedchars">Allowed Characters</ref>: specify the characters that are permitted in a given piece of content.</item>
+
+ <item><ref target="#storagesize">Storage Size</ref>: specify the maximum storage size of a given content.</item></list>
+ </div>
- <div xml:id="modified-datacategories"><head>Modified data categories</head> <p>tbd</p>
+ <div xml:id="modified-datacategories"><head>Modified data categories</head>
+
+ <p xml:id="ruby-in-its2">ITS 1.0 provided the <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation">Ruby data category</ref>. ITS 2.0 does not provide ruby since at the time of writing, a stable model for ruby was not available. There are ongoing discussions about the <ref target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</ref>. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p>
+
+ <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>
</div>
@@ -595,13 +646,21 @@
<div xml:id="mappings"><head>Mappings</head>
- <div xml:id="mapping-NIF"><head>NIF</head> <p>tbd</p></div>
-
- <div xml:id="mapping-XLIFF"><head>XLIFF</head> <p>tbd</p></div>
+ <div xml:id="mapping-NIF"><head>ITS and RDF/NIF</head>
+ <p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
+ representations) that contain ITS metadata to the RDF-based format based on <ptr
+ target="#nif-reference" type="bibref"/>. The conversion results in RDF triples.</p>
+ <p>NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations. The conversion <ref target="#conversion-to-nif">ITS 2.0 to NIF</ref> is defined normatively. The backconversion <ref target="#nif-backconversion">NIF to ITS 2.0</ref> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div>
+
+ <div xml:id="mapping-XLIFF"><head>ITS and XLIFF</head>
+ <p>The XML Localization Interchange File Format <ptr target="#xliff" type="bibref"/> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.0 usage scenarios <ptr target="#mlw-metadata-us-impl" type="bibref"/>. These usage scenarios involve: 1) the mapping of ITS meta-data in a source document into XLIFF and ITS meta-data of the translatable content in XLIFF file; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <ref target="http://www.w3.orgInternational/its/wiki/XLIFF_Mapping">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</ref> is being defined within the <ref target="http://www.w3.org/International/its/ig/">Internationalization Tag Set Interest Group</ref>.</p>
+ </div>
</div>
- <div xml:id="unicode-normalization"><head>Unicode normalization</head> <p>tbd</p></div>
+ <div xml:id="unicode-normalization"><head>Unicode normalization</head>
+ <p>As a general guidance, implementations of ITS 2.0 should use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. Further information on the topic of Unicode normalization is provided by <ptr target="#charmod-norm" type="bibref"/>.</p>
+ </div>
<div xml:id="extended-implementation-hints"><head>Extended implementation hints</head> <p>tbd</p></div>
Received on Thursday, 30 May 2013 15:56:51 UTC