- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Wed, 10 Apr 2013 15:13:58 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv32710/TR-version
Modified Files:
Overview.html
Log Message:
publication preparation
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/04/09 20:57:09 1.75
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/04/10 15:13:58 1.76
@@ -35,11 +35,11 @@
Group</a> as an updated working draft. The publication reflects changes made since the
<a href="http://www.w3.org/TR/2012/WD-its20-20121206/">Last Call</a> publication 6 November 2012. The Working Group expects to advance this
Working Draft to Recommendation status (see <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
- maturity levels</a>).</p><p id="open-issues">All <a href="http://tinyurl.com/its20-comments-handling">last call issues</a> in the normative sections (from <a class="section-ref" href="#notation-terminology">Section 3: Notation and Terminology</a> to
+ maturity levels</a>).</p><p id="open-issues">All <a href="http://services.w3.org/xslt?xslfile=http%3A%2F%2Fwww.w3.org%2FInternational%2Fmultilingualweb%2Flt%2Fdrafts%2Fits20%2Ftools%2Fxslt%2Fdisco-for-its20.xsl&xmlfile=https%3A%2F%2Fwww.w3.org%2FInternational%2Fmultilingualweb%2Flt%2Ftrack%2Fapi%2Fdump%3Ffull&content-type=&submit=transform">last call issues</a> in the normative sections (from <a class="section-ref" href="#notation-terminology">Section 3: Notation and Terminology</a> to
<a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a> and <a class="section-ref" href="#normative-references">Appendix A: References</a> to
- <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a>) have been resolved, with 4 exceptions: @@@@. The other, non-normative sections contain only
+ <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a>) have been resolved, with <a href="#unresolved-issues">four exceptions</a>. The other, non-normative sections contain only
explanatory material and will be updated in a later working draft. The Working Group
- encourages feedback until end of April 2013 on the @@@ open issues: @@@@ sections.</p><p>To give feedback send your comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
+ encourages feedback until end of April 2013 on the <a href="#unresolved-issues">unresolved issues</a>.</p><p>To give feedback send your comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives
for this list</a> are publicly available. See also <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed
within the Working Group</a> and the <a href="#changelog-since-20121023">list of
@@ -89,9 +89,9 @@
<div class="toc3">5.2.2 <a href="#selection-local">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2065">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2071">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2310">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2316">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules">Link to External Rules</a></div>
@@ -678,7 +678,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">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">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1143" id="d0e1143"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1149" id="d0e1149"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">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
@@ -945,9 +945,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"><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="d0e2065" id="d0e2065"></a>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"><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="d0e2071" id="d0e2071"></a>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="d0e2076" id="d0e2076"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
+<h5><a name="d0e2082" id="d0e2082"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">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">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
AbsoluteLocationPath</a>s as described in <a href="#xpath">XPath 1.0</a>.
@@ -992,14 +992,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="d0e2287" id="d0e2287"></a>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
+<h5><a name="d0e2293" id="d0e2293"></a>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors">[Selectors Level 3]</a>. Both simple selectors
and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2297" id="d0e2297"></a>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
+<h5><a name="d0e2303" id="d0e2303"></a>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors">[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"><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="d0e2310" id="d0e2310"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional query
+<h4><a href="#contents"><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="d0e2316" id="d0e2316"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords">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>,
@@ -1175,20 +1175,18 @@
process and its corresponding external rules file.</p></li></ul></div><div class="div2">
<h3><a href="#contents"><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="conversion-to-nif" id="conversion-to-nif"></a>5.7 Conversion to NIF</h3><p>This section 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">[NIF]</a>. The conversion results in RDF triples.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP
- tool and can produce a lot of "<span class="quote">phantom</span>" predicates from excessive
+ tool. It can produce a lot of "<span class="quote">phantom</span>" predicates from excessive
whitespace, which 1) increases the size of the intermediate mapping and 2) extracts
- this whitespace as text. This might decrease NLP performance. It is recommended to
+ this whitespace as text, and therefore might decrease NLP performance. It is strongly recommended to
normalize whitespace in the input XML/HTML/DOM in order to minimize such phantom
- predicates. A normalized example is given below. The whitespace normalization
- algorithm itself is format dependent, e.g. it differs for HTML compared to general
- XML. Hence no normative algorithm for whitespace normalization is given as part of
- this specification.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-HTML-whitespace-normalization" id="EX-HTML-whitespace-normalization"></a>Example 25: Example of an HTML document with whitespace normalized as preparation for
- conversion to NIF</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><html></strong><strong class="hl-tag" style="color: #000096"><body></strong><strong class="hl-tag" style="color: #000096"><h2</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Welcome to <strong class="hl-tag" style="color: #000096"><span</strong>
+ predicates. A normalized example is given below. Since the whitespace normalization
+ algorithm itself is format dependent, for example, it differs for HTML compared to general
+ XML, no normative algorithm for whitespace normalization is given as part of
+ this specification.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-HTML-whitespace-normalization" id="EX-HTML-whitespace-normalization"></a>Example 25: Example of an HTML document with whitespace character normalization as preparation for the conversion to NIF</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><html></strong><strong class="hl-tag" style="color: #000096"><body></strong><strong class="hl-tag" style="color: #000096"><h2</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Welcome to <strong class="hl-tag" style="color: #000096"><span</strong>
<span class="hl-attribute" style="color: #F5844C">its-ta-ident-ref</span>=<span class="hl-value" style="color: #993300">"http://dbpedia.org/resource/Dublin"</span> <span class="hl-attribute" style="color: #F5844C">its-within-text</span>=<span class="hl-value" style="color: #993300">"yes"</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>Dublin<strong class="hl-tag" style="color: #000096"></span></strong> in <strong class="hl-tag" style="color: #000096"><b</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">its-within-text</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Ireland<strong class="hl-tag" style="color: #000096"></b></strong>!<strong class="hl-tag" style="color: #000096"></h2></strong><strong class="hl-tag" style="color: #000096"></body></strong><strong class="hl-tag" style="color: #000096"></html></strong></pre></div></div><p id="its2nif-algorithm">The conversion algorithm to generate NIF consists of seven
steps.</p><ul><li><p id="its2nif-algorithm-step1">STEP 1: Get an ordered list of all text nodes
- of the document.</p></li><li><p id="its2nif-algorithm-step2">STEP 2: Generate an XPath expression for each
- non-empty text node of all leaf elements and remember them.</p></li><li><p id="its2nif-algorithm-step3">STEP 3: Get the text for each node and make a
+ of the document.</p></li><li><p id="its2nif-algorithm-step2">STEP 2: Generate an XPath expression for each non-empty text node of all leaf elements and memorize them.</p></li><li><p id="its2nif-algorithm-step3">STEP 3: Get the text for each node and make a
tuple with the XPath expressions (X,T). Since the text nodes have a certain order we
now have a list of ordered tuples ((x0,t0), (x1,t1), ..., (xn,tn)).</p></li><li><p id="its2nif-algorithm-step4">STEP 4 (optional): Serialize as XML or as RDF.
The list with the XPath-to-text mapping can also be kept in memory. Part of a
@@ -1239,31 +1237,27 @@
<mapping x="xpath(/html/body[1]/h2[1]/text()[3])" b="28" e="29" />
<mapping x="xpath(/html/body[1]/h2[1])" b="0" e="29" />
</mappings></pre></div></div><ul><li><p id="its2nif-algorithm-step5">STEP 5: Create a context URI and attach the
- whole concatenated text of the document as reference.</p></li><li><p id="its2nif-algorithm-step6">STEP 6: Now attach any ITS metadata items from
- the XML/HTML/DOM input to respective NIF URIs.</p></li><li><p id="its2nif-algorithm-step7">STEP 7: Omit all irrelevant URIs (those that
- do not carry annotations, they will just bloat the data).</p></li></ul><div class="exampleInner"><div class="exampleOuter"><pre>@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> .
+ whole concatenated text of the document as reference.</p></li><li><p id="its2nif-algorithm-step6">STEP 6: Attach any ITS metadata annotations from the XML/HTML/DOM input to the respective NIF URIs.</p></li><li><p id="its2nif-algorithm-step7">STEP 7: Omit all URIs that do not carry annotations (they will just bloat the data).</p></li></ul><div class="exampleInner"><div class="exampleOuter"><pre>@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> .
+@prefix nif: <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#>
<http://example.com/exampledoc.html#char=0,29>
- rdf:type str:Context ;
- rdf:type str:OffsetBasedString ;
+ rdf:type nif:Context ;
+ rdf:type nif:RFC5147String ;
# concatenate the whole text
- str:isString "$(t0+t1+t2+...+tn)" ;
+ nif:isString "$(t0+t1+t2+...+tn)" ;
itsrdf:translate "yes";
- str:occursIn <http://example.com/exampledoc.html> .
+ nif:occursIn <http://example.com/exampledoc.html> .
<http://example.com/exampledoc.html#char=11,17>
- rdf:type str:String ;
- rdf:type str:OffsetBasedString ;
+ rdf:type nif:RFC5147String;
+ rdf:type nif:RFC5147String ;
itsrdf:translate "no";
itsrdf:taIdentRef <http://dbpedia.org/resource/Dublin> ;
- str:referenceContext <http://example.com/exampledoc.html#char=0,29> .
+ nif:referenceContext <http://example.com/exampledoc.html#char=0,29> .
<http://example.com/exampledoc.html#char=21,28>
- rdf:type str:String ;
- rdf:type str:OffsetBasedString ;
+ rdf:type nif:RFC5147String;
+ rdf:type nif:RFC5147String ;
itsrdf:translate "no";
- str:referenceContext <http://example.com/exampledoc.html#char=0,29> .
-</pre></div></div><p>A complete sample output in RDF/XML format after step 7, given the input document <a href="#EX-HTML-whitespace-normalization">Example 25</a>, is available at <a href="examples/nif/EX-nif-conversion-output.xml">examples/nif/EX-nif-conversion-output.xml</a>.</p><span class="editor-note">[Ed. note: above example needs to be updated with regards to "text analysis" output.]</span><div class="note"><p class="prefix"><b>Note:</b></p><p>The conversion to NIF is the basis for natural language processing (NLP)
- applications, creating for example named entity annotations. A non-normative algorithm
- to integrate these annotations into the original input document is given in <a class="section-ref" href="#nif-backconversion">Appendix F: Conversion NIF2ITS</a>. The algorithm in that appendix is
- non-normative since many choices depend on the actual NLP application.</p></div></div><div class="div2">
+ nif:referenceContext <http://example.com/exampledoc.html#char=0,29> .
+</pre></div></div><p>A complete sample output in RDF/XML format after step 7, given the input document <a href="#EX-HTML-whitespace-normalization">Example 25</a>, is available at <a href="examples/nif/EX-nif-conversion-output.xml">examples/nif/EX-nif-conversion-output.xml</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The conversion to NIF is a possible basis for a natural language processing (NLP) application that creates, for example, named entity annotations. A non-normative algorithm to integrate these annotations into the original input document is given in <a class="section-ref" href="#nif-backconversion">Appendix F: Conversion NIF2ITS</a>. This algorithm is non-normative because many decisions depend on the actually employed NLP application.</p></div></div><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="its-tool-annotation" id="its-tool-annotation"></a>5.8 ITS Tools Annotation</h3><p>In some cases, it may be important for instances of data categories to be associated
with information about the processor that generated them. For example, the score of the
<a href="#mtconfidence">MT Confidence</a> data category (provided via the
@@ -1471,7 +1465,7 @@
make use just of the string value of <code>p</code>. Nevertheless the id provided
via <a href="#idvalue">ID value</a> pertains only to the <code>p</code>
element. It cannot be used to identify nested elements or attributes.</p></li><li><p>Using <a href="#target-pointer">target pointer</a>, selected
- <code>source</code> element have the ITS information that their translation is
+ <code>source</code> element have the ITS information that their translation is
available in a <code>target</code> element; see <a href="#EX-target-pointer-global-1">Example 70</a>. This information does not
inherit to child elements of <code>target pointer</code>. E.g., the translation of a
<code>span</code> element nested in <code>source</code> is not available in a
@@ -3410,8 +3404,7 @@
http://www.w3.org/TR/html401.</dd><dt class="label"><a name="html5" id="html5"/>HTML5</dt><dd>Robin Berjon et al. <a href="http://www.w3.org/TR/2012/CR-html5-20121217/"><cite>HTML5</cite></a>. W3C Candidate Recommendation 17 December 2012. Available at <a href="http://www.w3.org/TR/2012/CR-html5-20121217/">
http://www.w3.org/TR/1999/REC-html401-19991224</a>. The latest version of <a href="http://www.w3.org/TR/html5/">HTML5</a> is available at
http://www.w3.org/TR/html5/.</dd><dt class="label"><a name="ianacharsets" id="ianacharsets"/>IANA Character Sets</dt><dd>
- <a href="http://www.iana.org/assignments/character-sets"><cite>Character Sets</cite></a> Available at <a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>.</dd><dt class="label"><a name="NIF" id="NIF"/>NIF</dt><dd>NIF Placeholder at
- http://persistence.uni-leipzig.org/nlp2rdf/</dd><dt class="label"><a name="qa-framework" id="qa-framework"/>QAFRAMEWORK</dt><dd>Karl Dubost, Lynne Rosental, Dominique
+ <a href="http://www.iana.org/assignments/character-sets"><cite>Character Sets</cite></a> Available at <a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>.</dd><dt class="label"><a name="NIF" id="NIF"/>NIF</dt><dd>Hellmann, S. (ed.). <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core">NIF 2.0 Core Ontology Version 1.0</a>, version April 2013. Available at http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core under CC-BY 2.0 license. </dd><dt class="label"><a name="qa-framework" id="qa-framework"/>QAFRAMEWORK</dt><dd>Karl Dubost, Lynne Rosental, Dominique
Hazaël-Massieux, Lofton Henderson. <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/"><cite>QA Framework:
Specification Guidelines</cite></a>. W3C Recommendation 17 August 2005. Available at <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">
http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/</a>. The latest version of <a href="http://www.w3.org/TR/qaframe-spec/">QAFRAMEWORK</a> is available at
@@ -5805,7 +5798,7 @@
algorithm</a>.</p><p>As a natural language processing (NLP) tool, we choose <a href="https://github.com/dbpedia-spotlight/dbpedia-spotlight#readme">DBpedia
Spotlight</a>. For this example let's assume DBpedia Spotlight linked "Ireland" to
DBpedia:</p><div class="exampleInner"><div class="exampleOuter"><pre><http://example.com/exampledoc.html#char=21,28>
- rdf:type str:String ;
+ rdf:type nif:RFC5147String;
itsrdf:taIdentRef <http://dbpedia.org/resource/Ireland> .
<http://dbpedia.org/resource/Ireland>
rdf:type <http:/nerd.eurecom.fr/ontology#Country> .
@@ -6017,12 +6010,11 @@
<code class="its-attr-markup">lineBreakType</code>?</td><td>
<code class="its-attr-markup">its-storage-size</code>, <code class="its-attr-markup">its-storage-encoding</code>?,
<code class="its-attr-markup">lits-line-break-type</code>?</td></tr></tbody></table></div><div class="div1">
-<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="revisionlog" id="revisionlog"></a>H Revision Log (Non-Normative)</h2><p id="changelog-since-20121206">The following log records major changes that have been
+<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="revisionlog" id="revisionlog"></a>H Revision Log (Non-Normative)</h2><p id="unresolved-issues">The following four issues have not been resolved since the publication of the last call <a href="http://www.w3.org/TR/2012/WD-its20-20121206/">ITS 2.0 Working Draft 6 December 2012</a>:</p><ul><li><p><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/67">issue-67: Change definition of regular expression for allowed characters</a></p></li><li><p><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/91">issue-91: Parts of Ruby section should be removed</a>. The Working Group decided to remove the Ruby section but seeks feedback before finalizing this decision.</p></li><li><p><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/97">issue-97: HTML translate</a></p></li><li><p><ahref="https://www.w3.org/International/multilingualweb/lt/track/issues/118">issue-118: HTML ITS default behaviour</a></p></li></ul><p>The Working Group especially encourages feedback on these issues by end of April 2013.</p><p id="changelog-since-20121206">The following log records major changes that have been
made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121206/">ITS 2.0 Working Draft 6 December 2012</a>.</p><ol class="depth1"><li><p>Added optional version attribute to standoff elements, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/122">issue-122</a>.</p></li><li><p>Fixed <a href="#EX-its-tool-annotation-1">Example 26</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/58">issue-58</a>.</p></li><li><p>Clarified text in <a class="section-ref" href="#basic-concepts-addingpointing">Section 2.3: Adding Information or Pointing to Existing Information</a> and
<a class="section-ref" href="#selection-global">Section 5.2.1: Global, Rule-based Selection</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/59">issue-59</a>.</p></li><li><p>Clarified the definition of <code>uncategorized</code> in <a class="section-ref" href="#lqissue-typevalues">Appendix C: Values for the Localization Quality Issue Type</a>, and (see <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2012Dec/0031.html">related mail</a>) used "<span class="quote">value</span>" consistently instead of
"<span class="quote">category</span>" to refer to the value types. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/60">issue-60</a>.</p></li><li><p>Clarified definition of <a href="#lqissue-global">Localization Quality
- Issue</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/62">issue-62</a>.</p></li><li><p>Removed <code>disambigClassPointer</code> attribute, see <a class="section-ref" href="#textanalysis-implementation">Section 8.10.2: Implementation</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/64">issue-64</a>.</p></li><li><p>Clarified that <code class="its-attr-markup">provenanceRecordsRefPointer</code> cannot be used in HTML, see
- <a class="section-ref" href="#provenance-implementation">Section 8.12.2: Implementation</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/65">issue-65</a>.</p></li><li><p>Changed the allowed location of the <code class="its-attr-markup">version</code> attribute in <a class="section-ref" href="#its-version-attribute">Section 5.1: Indicating the Version of ITS</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/66">issue-66</a>.</p></li><li><p>Clarified links to external rules, see <a class="section-ref" href="#link-external-rules">Section 5.4: Link to External Rules</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/69">issue-69</a>.</p></li><li><p>Clarified in <a class="section-ref" href="#html5-selection-precedence">Section 6.4: Precedence between Selections</a> that in HTML
+ Issue</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/62">issue-62</a>.</p></li><li><p>Removed <code>disambigClassPointer</code> attribute, see <a class="section-ref" href="#textanalysis-implementation">Section 8.10.2: Implementation</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/64">issue-64</a>.</p></li><li><p>Clarified that <code class="its-attr-markup">provenanceRecordsRefPointer</code> cannot be used in HTML, see<a class="section-ref" href="#provenance-implementation">Section 8.12.2: Implementation</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/65">issue-65</a>.</p></li><li><p>Changed the allowed location of the <code class="its-attr-markup">version</code> attribute in <a class="section-ref" href="#its-version-attribute">Section 5.1: Indicating the Version of ITS</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/66">issue-66</a>.</p></li><li><p>Clarfied links to external rules, see <a class="section-ref" href="#link-external-rules">Section 5.4: Link to External Rules</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/69">issue-69</a>.</p></li><li><p>Clarified in <a class="section-ref" href="#html5-selection-precedence">Section 6.4: Precedence between Selections</a> that in HTML
(like in XML) global rules are to be read in document order, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/77">issue-77</a>.</p></li><li><p>Clarified how the filter in <a class="section-ref" href="#LocaleFilter">Section 8.11: Locale Filter</a> works, see
<a href="https://www.w3.org/International/multilingualweb/lt/track/issues/92">issue-92</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/103">issue-103</a>.</p></li><li><p>Clarified in <a class="section-ref" href="#html5-markup">Section 6: Using ITS Markup in HTML</a> that values of attributes
in HTML with a pre-defined set of values match ASCII-case-insensitively, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/93">issue-93</a>.</p></li><li><p>Changed representation of decimal numbers from xs:decimal to xs:double, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/94">issue-94</a>.</p></li><li><p>Added statement about HTML5 <code>translate</code> attribute in <a href="#trans-datacat">Translate</a> data category, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/97">issue-97</a></p></li><li><p>Removed case-insensitivity from the algorithm of the <a href="#domain">Domain</a> data category, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/102">issue-102</a>.</p></li><li><p>Clarified <a class="section-ref" href="#xhtml5-markup">Section 7: Using ITS Markup in XHTML</a> and a related <a href="#note-html-rules-location">note</a> in <a class="section-ref" href="#html5-markup">Sction 6: Using ITS Markup in HTML</a> in response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/115">issue-115</a>.</p></li><li><p>Clarified when to use HTML-like and when XML-like ITS markup in XHTML as a response
Received on Wednesday, 10 April 2013 15:14:01 UTC