- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Fri, 30 Aug 2013 11:03:38 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv27386
Modified Files:
its20.html its20.odd
Log Message:
spelling mistakes noted by Ivan
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/08/19 12:55:35 1.488
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/08/30 11:03:37 1.489
@@ -512,7 +512,7 @@
and <code class="its-elem-markup">textarea</code> are interpreted as <code>withinText="nested"</code>.</p></li><li><p id="translate-in-html5">The <a href="#trans-datacat" shape="rect">Translate</a> data category has a direct counterpart in
<a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, namely the <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>
<code>translate</code> attribute. ITS 2.0 does not define its own behavior for <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>
- <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute" shape="rect">the HTML5 definition</a>. That definition also applies to nodes selected via global rules. That is, a <code class="its-elem-markup">translateRule</code> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-and-existing-HTML5-markup" id="EX-its-and-existing-HTML5-markup" shape="rect"/>Example 9: The <a href="#language-information" shape="rect">Language Information</a>, <a href="#idvalue" shape="rect">Id Value</a>,
+ <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute" shape="rect">the HTML5 definition</a>. That definition also applies to nodes selected via global rules. That is, a <code class="its-elem-markup">translateRule</code> like <code><its:translateRule selector="//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-and-existing-HTML5-markup" id="EX-its-and-existing-HTML5-markup" shape="rect"/>Example 9: The <a href="#language-information" shape="rect">Language Information</a>, <a href="#idvalue" shape="rect">Id Value</a>,
<a href="#elements-within-text" shape="rect">Elements within Text</a> and <a href="#trans-datacat" shape="rect">Translate</a>
ITS 2.0 data categories expressed by native HTML markup.</div><p>The <code>lang</code> attribute of the <code>html</code> element conveys the
<a href="#language-information" shape="rect">Language Information</a> value "en".
@@ -759,7 +759,7 @@
elements</a> for each data category. Each rule element has a <code class="its-attr-markup">selector</code>
attribute and possibly other attributes. The <code class="its-attr-markup">selector</code> attribute contains an
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>
+ 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">
<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
@@ -810,7 +810,7 @@
</pre></div><p>[Source file: <a href="examples/xml/EX-selection-local-1.xml" shape="rect">examples/xml/EX-selection-local-1.xml</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code class="its-attr-markup">dir</code> and <code class="its-attr-markup">translate</code> attributes are not listed in the
ITS attributes to be used in HTML. The reason is that these two attributes are
available in HTML natively, so there is no need to provide them as <code>its-</code>
- attributes. The definition of the two attributes in HTML is compatibly, that is it
+ attributes. The definition of the two attributes in HTML is compatible, that is it
provides the same values and interpretation, as the definition for the two data
categories <a href="#trans-datacat" shape="rect">Translate</a> and <a href="#directionality" shape="rect">Directionality</a>.</p></div></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="selectors" id="selectors" shape="rect"/>5.3 Query Language of Selectors</h3><div class="div3">
@@ -5588,9 +5588,9 @@
</dd><dt class="label"><a name="nif-reference" id="nif-reference" shape="rect"/>NIF</dt><dd>Hellmann, S. et al. (ed.). <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#" shape="rect">NIF 2.0 Core Ontology</a>, as of August 2013. Available at <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#" shape="rect">http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#</a> under CC-BY 3.0 license maintained by the <a href="http://nlp2rdf.org" shape="rect">NLP2RDF project</a>.</dd><dt class="label"><a name="nvdl" id="nvdl" shape="rect"/>NVDL</dt><dd>Information technology – Document Schema Definition
Languages (DSDL) – Part 4: <cite>Namespace-based Validation Dispatching Language
(NVDL)</cite>. International Organization for Standardization (ISO) ISO/IEC
- 19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument" shape="rect"/>OpenDocument</dt><dd>Michael Brauer et al. <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect"><cite>OASIS Open Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
+ 19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument" shape="rect"/>OpenDocument</dt><dd>Michael Brauer et al. <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect"><cite>OASIS Open Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>. The latest
- version of <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
+ version of <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
OpenDocument</a> is available at
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="prov-dm" id="prov-dm" shape="rect"/>PROV-DM</dt><dd>Moreau, Luc and Paolo Missier (eds.). <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/" shape="rect">Provenance data model</a>.
W3C Recommendation 30 April 2013. Available at <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/" shape="rect">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>.
@@ -6021,5 +6021,5 @@
declarations for the Terminology data category and the summary for local data categories
in <a class="section-ref" href="#selection-local" shape="rect">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" shape="rect">Example 40</a></p></li><li><p>Added placeholders for new data categories to <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>Added a placeholder section <a class="section-ref" href="#conversion-to-nif" shape="rect">Appendix F: Conversion to NIF</a></p></li></ol></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="acknowledgements" id="acknowledgements" shape="rect"/>J Acknowledgements (Non-Normative)</h2><p>This document has been developed with contributions by the
- <a href="http://www.w3.org/International/multilingualweb/lt/" shape="rect">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 CollegeDublin), Matthias 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 & Telecommunications (IIT), NCSR), Mārcis Pinnis (Tilde), Prashant Verma Prashant (Department of Information Technology, Govrnment of India), 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/" shape="rect">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 CollegeDublin), Matthias 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 & Telecommunications (IIT), NCSR), Mārcis Pinnis (Tilde), Prashant Verma Prashant (Department of Information Technology, Govrnment of India), 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:
</p><ul><li><p>Sebastian Hellmann for introducing us to <a title="" href="#nif-reference" shape="rect">[NIF]</a> and for contributing to the creation of the <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS 2.0 ontology</a> and NIF testing.</p></li><li><p>Daniel Naber for introducing us to <a href="http://languagetool.org" shape="rect">LanguageTool</a> and for implementing <a href="#lqissue-typevalues" shape="rect">Localization Quality Issue Type</a> functionality in language tool.</p></li></ul></div></div></body></html>
\ No newline at end of file
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/08/20 13:46:40 1.503
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/08/30 11:03:38 1.504
@@ -728,7 +728,7 @@
and <gi>textarea</gi> are interpreted as <code>withinText="nested"</code>.</p></item>
<item><p xml:id="translate-in-html5">The <ref target="#trans-datacat">Translate</ref> data category has a direct counterpart in
<ptr target="#html5" type="bibref"/>, namely the <ptr target="#html5" type="bibref"/>
- <code>translate</code> attribute. ITS 2.0 does not define its own behavior for <ptr target="#html5" type="bibref"/> <code>translate</code>, but just refers to <ref target="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">the HTML5 definition</ref>. That definition also applies to nodes selected via global rules. That is, a <gi>translateRule</gi> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to <val>yes</val>.</p></item>
+ <code>translate</code> attribute. ITS 2.0 does not define its own behavior for <ptr target="#html5" type="bibref"/> <code>translate</code>, but just refers to <ref target="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">the HTML5 definition</ref>. That definition also applies to nodes selected via global rules. That is, a <gi>translateRule</gi> like <code><its:translateRule selector="//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to <val>yes</val>.</p></item>
</list>
<exemplum xml:id="EX-its-and-existing-HTML5-markup">
<head>The <ref target="#language-information">Language Information</ref>, <ref target="#idvalue">Id Value</ref>,
@@ -1194,8 +1194,7 @@
attribute and possibly other attributes. The <att>selector</att> attribute contains an
absolute selector as defined in <ptr target="#selectors" type="specref"/>.</item>
<item><ref target="#selection-local">Locally in a document</ref>: the selection is
- realized using ITS local attributes, which are attached to an element node, or the
- <gi>span</gi> element. There is no additional <att>selector</att>
+ realized using ITS local attributes, which are attached to an element node, or the <gi>span</gi> element. There is no additional <att>selector</att>
attribute. The default selection for each data category defines whether the selection
covers attributes and child elements. See <ptr target="#datacategories-defaults-etc"
type="specref"/>.</item>
@@ -1267,7 +1266,7 @@
<note><p>The <att>dir</att> and <att>translate</att> attributes are not listed in the
ITS attributes to be used in HTML. The reason is that these two attributes are
available in HTML natively, so there is no need to provide them as <code>its-</code>
- attributes. The definition of the two attributes in HTML is compatibly, that is it
+ attributes. The definition of the two attributes in HTML is compatible, that is it
provides the same values and interpretation, as the definition for the two data
categories <ref target="#trans-datacat">Translate</ref> and <ref
target="#directionality">Directionality</ref>.</p></note>
Received on Friday, 30 August 2013 11:03:40 UTC