CVS WWW/International/multilingualweb/lt/drafts/its20/TR-version

Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv7431/TR-version

Modified Files:
	Overview.html 
Log Message:
connectivity again - hopefully final fixes before PR pub

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html	2013/09/15 15:49:53	1.121
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html	2013/09/17 17:16:57	1.122
@@ -34,7 +34,7 @@
         Natural Language Processing Interchange Format (NIF).</p><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
         Group</a> as a Proposed Recommendation. Comments submitted against the <a href="http://www.w3.org/TR/2013/WD-its20-20130820/">previous Last Call specification</a> are consolidated in a <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-3rd-last-call.html">comment tracking document</a>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <a href="https://github.com/w3c/its-2.0-testsuite/">Test Suite</a> and created an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</a> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
         document 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> The W3C Membership and other interested parties are invited to review the document and send 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
+          maturity levels</a>).</p><p>The ITS 2.0 specification has a normative dependency on the HTML5 specification: it relies on the <a href="http://www.w3.org/TR/2013/CR-html5-20130806/dom.html#the-translate-attribute">HTML5 Translate attribute</a>. By publishing this ITS 2.0 Proposed Recommendation, W3C expects that the functionality specified in ITS 2.0 will not be affected by changes to HTML5 as HTML5 proceeds to Recommendation.</p><p> The W3C Membership and other interested parties are invited to review the document and send 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. Advisory Committee Representatives should consult their <a href="https://www.w3.org/2002/09/wbs/myQuestionnaires">WBS questionnaires</a>.  The deadline for review and comments is 15 October 2013.  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-20130820">list of
@@ -82,9 +82,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="#d0e2515">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2520">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="#d0e2763">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2768">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>
@@ -587,7 +587,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="d0e1613" id="d0e1613"></a>Example 10: 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="d0e1618" id="d0e1618"></a>Example 10: 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 is intended for translation 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
@@ -844,9 +844,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="d0e2515" id="d0e2515"></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="d0e2520" id="d0e2520"></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="d0e2526" id="d0e2526"></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="d0e2531" id="d0e2531"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
                 that starts with "<code>/</code>". That is, it <a href="#rfc-keywords">MUST</a> 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>.
@@ -891,14 +891,14 @@
                 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
                 <code class="its-attr-markup">queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d0e2740" id="d0e2740"></a>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as a
+<h5><a name="d0e2745" id="d0e2745"></a>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as a
                 selector as defined in <a title="Selectors Level&#xA;                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="d0e2750" id="d0e2750"></a>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords">MUST</a> be interpreted as a
+<h5><a name="d0e2755" id="d0e2755"></a>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords">MUST</a> be interpreted as a
                 selector as defined in <a title="Selectors Level&#xA;                3" href="#css3-selectors">[Selectors Level 3]</a>. A selector is
                 not evaluated against the complete document tree but only against subtrees rooted at
                 nodes selected by the 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="d0e2763" id="d0e2763"></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="d0e2768" id="d0e2768"></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>the identifier of the query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating an absolute selector to a collection of nodes;</p></li><li><p>rules for evaluating a relative selector to a 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>,
@@ -1784,7 +1784,7 @@
                      </p></li></ul></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="within-text-implementation" id="within-text-implementation"></a>8.7.2 Implementation</h4><p>The <a href="#elements-within-text">Elements Within Text</a> data category can
               be expressed with global rules, or locally on an individual element. There is no
-              inheritance.</p><p>For XML: The default is that elements are not within text.</p><p id="html5-withintext-handling">For HTML: The default is that elements are not within text, with the following exceptions:</p><ul><li><p>For the elements that are part of the <a href="http://www.w3.org/TR/2012/CR-html5-20121217/dom.html#phrasing-content-1">HTML5 phrasing content</a> the 
+              inheritance.</p><p>For XML: The default is that elements are not within text.</p><p id="html5-withintext-handling">For HTML: The default is that elements are not within text, with the following exceptions:</p><ul><li><p>For the elements that are part of the <a href="http://www.w3.org/TR/2012/CR-html5-20130806/dom.html#phrasing-content-1">HTML5 phrasing content</a> the 
                   default is <code>withinText="yes"</code>, with the following exceptions:</p><ul><li><p>For the elements <code class="its-elem-markup">iframe</code>, <code class="its-elem-markup">noscript</code>, <code class="its-elem-markup">script</code> and <code class="its-elem-markup">textarea</code> the default is <code>withinText="nested"</code>.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-within-text-defaults-html5-1" id="EX-within-text-defaults-html5-1"></a>Example 46: Illustrates the defaults for the <a href="#elements-within-text">Elements Within Text</a> data category in HTML.</div><p>In this document the different flows of text are the following (brackets indicating inline or nested elements):<br/><code><br/>
                  - "Elements within Text defaults for HTML5"<br/>
                  - "The element p is not within text. But [the element em is]."<br/>
@@ -6045,5 +6045,5 @@
             declarations for the Terminology data category and the summary for local data categories
             in <a class="section-ref" href="#selection-local">Section 5.2.2: Local Selection in an XML Document</a></p></li><li><p>Created examples for these declarations, see e.g., <a href="#EX-term-local-html-1">Example 40</a></p></li><li><p>Added placeholders for new data categories to <a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a></p></li><li><p>Added a placeholder section <a class="section-ref" href="#conversion-to-nif">Appendix F: Conversion to NIF</a></p></li></ol></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="acknowledgements" id="acknowledgements"></a>K Acknowledgements</h2><p>This document has been developed with contributions by the
-          <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working Group</a> and collaborators:  Mihael Arcan (DERI Galway at the National University of Ireland, Galway, Ireland), Pablo Badía (Linguaserve), Aaron Beaton (Opera Software), Renat Bikmatov (Logrus Plus LLC), Aljoscha Burchardt (German Research Center for Artificial Intelligence (DFKI GmbH)), Nicoletta CalzolarI (CNR--Consiglio Nazionale delle Ricerche), Somnath Chandra (Department of Information Technology, Government of India), John Colosi (Verisign, Inc.), Mauricio del Olmo (Linguaserve), Giuseppe Deriard (Linguaserve), Pedro Luis Díez Orzas (Linguaserve), David Filip (University of Limerick), Leroy Finn (Trinity College Dublin), Karl Fritsche (Cocomore AG), Serge Gladkoff (Logrus Plus LLC), Tatiana Gornostay (Tilde), Daniel Grasmick (Lucy Software and Services GmbH), Declan Groves (Centre for Next Generation Localisation), Manuel Honegger (University of Limerick), Dominic Jones (Trinity College Dublin), Mathias Kandora (]init[), Milan Karásek (Moravia Worldwide), Jirka Kosek (University of Economics, Prague), Michael Kruppa (Cocomore AG), Alejandro Leiva (Cocomore AG), Swaran Lata (Department of Information Technology, Government of India), David Lewis (Trinity College Dublin), Fredrik Liden (ENLASO Corporation), Christian Lieske (SAP AG), Qun Liu (Centre for Next Generation Localisation), Arle Lommel (German Research Center for Artificial Intelligence (DFKI GmbH)), Priyanka Malik (Department of Information Technology, Government of India), Shaun McCance ((public) Invited expert), Sean Mooney (University of Limerick), Jan Nelson (Microsoft Corporation), Pablo Nieto Caride (Linguaserve), Pēteris Ņikiforovs (Tilde), Naoto Nishio (University of Limerick), Philip O'Duffy (University of Limerick), Des Oates (Adobe Systems Inc.), Georgios Petasis (Institute of Informatics &amp; Telecommunications (IIT), NCSR), Mārcis Pinnis (Tilde), Prashant Verma Prashant (Department of Information Technology, Government of Inia), Georg Rehm (German Research Center for Artificial Intelligence (DFKI GmbH)), Phil Ritchie (VistaTEC), Thomas Rüdesheim (Lucy Software and Services GmbH), Nieves Sande (German Research Center for Artificial Intelligence (DFKI GmbH)), Felix Sasaki (DFKI / W3C Fellow), Yves Savourel (ENLASO Corporation), Jörg Schütz (W3C Invited Experts), Sebastian Sklarß (]init[), Ankit Srivastava (Centre for Next Generation Localisation), Tadej Štajner (Jozef Stefan Institute), Olaf-Michael Stefanov ((public) Invited expert), Najib Tounsi (Ecole Mohammadia d'Ingenieurs Rabat (EMI)), Naitik Tyagi Tyagi (Department of Information Technology, Government of India), Ronny Unger (Cocomore AG), Clemens Weins (Cocomore AG).</p><p>A special thanks goes to the following persons:
+          <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working Group</a> and collaborators:  Mihael Arcan (DERI Galway at the National University of Ireland, Galway, Ireland), Pablo Badía (Linguaserve), Aaron Beaton (Opera Software), Renat Bikmatov (Logrus Plus LLC), Aljoscha Burchardt (German Research Center for Artificial Intelligence (DFKI GmbH)), Nicoletta Calzolari (CNR--Consiglio Nazionale delle Ricerche), Somnath Chandra (Department of Information Technology, Government of India), John Colosi (Verisign, Inc.), Mauricio del Olmo (Linguaserve), Giuseppe Deriard (Linguaserve), Pedro Luis Díez Orzas (Linguaserve), David Filip (University of Limerick), Leroy Finn (Trinity College Dublin), Karl Fritsche (Cocomore AG), Serge Gladkoff (Logrus Plus LLC), Tatiana Gornostay (Tilde), Daniel Grasmick (Lucy Software and Services GmbH), Declan Groves (Centre for Next Generation Localisation), Manuel Honegger (University of Limerick), Dominic Jones (Trinity College Dublin), Mathias Kandora (]init[), Milan Karásek (Moravia Worldwide), Jirka Kosek (University of Economics, Prague), Michael Kruppa (Cocomore AG), Alejandro Leiva (Cocomore AG), Swaran Lata (Department of Information Technology, Government of India), David Lewis (Trinity College Dublin), Fredrik Liden (ENLASO Corporation), Christian Lieske (SAP AG), Qun Liu (Centre for Next Generation Localisation), Arle Lommel (German Research Center for Artificial Intelligence (DFKI GmbH)), Priyanka Malik (Department of Information Technology, Government of India), Shaun McCance ((public) Invited expert), Sean Mooney (University of Limerick), Jan Nelson (Microsoft Corporation), Pablo Nieto Caride (Linguaserve), Pēteris Ņikiforovs (Tilde), Naoto Nishio (University of Limerick), Philip O'Duffy (University of Limerick), Des Oates (Adobe Systems Inc.), Georgios Petasis (Institute of Informatics &amp; Telecommunications (IIT), NCSR), Mārcis Pinnis (Tilde), Prashant Verma Prashant (Department of Information Technology, Government of Inia), Georg Rehm (German Research Center for Artificial Intelligence (DFKI GmbH)), Phil Ritchie (VistaTEC), Thomas Rüdesheim (Lucy Software and Services GmbH), Nieves Sande (German Research Center for Artificial Intelligence (DFKI GmbH)), Felix Sasaki (DFKI / W3C Fellow), Yves Savourel (ENLASO Corporation), Jörg Schütz (W3C Invited Experts), Sebastian Sklarß (]init[), Ankit Srivastava (Centre for Next Generation Localisation), Tadej Štajner (Jozef Stefan Institute), Olaf-Michael Stefanov ((public) Invited expert), Najib Tounsi (Ecole Mohammadia d'Ingenieurs Rabat (EMI)), Naitik Tyagi Tyagi (Department of Information Technology, Government of India), Stephan Walter (Cocomore AG), Clemens Weins (Cocomore AG).</p><p>A special thanks goes to the following persons:
           </p><ul><li><p>Sebastian Hellmann for introducing us to <a title="" href="#nif-reference">[NIF]</a> and for contributing to the creation of the <a href="http://www.w3.org/2005/11/its/rdf#">ITS 2.0 ontology</a> and NIF testing.</p></li><li><p>Daniel Naber for introducing us to <a href="http://languagetool.org">LanguageTool</a> and for implementing <a href="#lqissue-typevalues">Localization Quality Issue Type</a> functionality in language tool.</p></li></ul></div></div></body></html>
\ No newline at end of file

Received on Tuesday, 17 September 2013 17:17:00 UTC