- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 10 Jun 2013 16:48:54 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv32549
Modified Files:
its20.html its20.odd
Log Message:
see http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0035.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/07 08:36:43 1.442
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/10 16:48:53 1.443
@@ -54,16 +54,16 @@
<div class="toc1">4 <a href="#conformance" shape="rect">Conformance</a><div class="toc2">4.1 <a href="#conformance-product-schema" shape="rect">Conformance Type 1: ITS Markup Declarations</a></div>
<div class="toc2">4.2 <a href="#conformance-product-processing-expectations" shape="rect">Conformance Type 2: The Processing Expectations for ITS Markup</a></div>
<div class="toc2">4.3 <a href="#conformance-product-html-processing-expectations" shape="rect">Conformance Type 3: Processing Expectations for ITS Markup in HTML</a></div>
-<div class="toc2">4.4 <a href="#conformance-class-html5-its" shape="rect">Conformance Class for HTML5+ITS documents</a></div>
+<div class="toc2">4.4 <a href="#conformance-type-html5-its" shape="rect">Conformance Type 4: Markup conformance for HTML5+ITS documents</a></div>
</div>
<div class="toc1">5 <a href="#its-processing" shape="rect">Processing of ITS information</a><div class="toc2">5.1 <a href="#its-version-attribute" shape="rect">Indicating the Version of ITS</a></div>
<div class="toc2">5.2 <a href="#datacategory-locations" shape="rect">Locations of Data Categories</a><div class="toc3">5.2.1 <a href="#selection-global" shape="rect">Global, Rule-based Selection</a></div>
<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="#d0e2368" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2426" 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="#d0e2613" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2671" 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>
@@ -307,7 +307,7 @@
management and integration of unstructured data in knowledge management systems.</p></div><div class="div4">
<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7 Localization Workflow Managers</h5><p>These types of users are concerned with localization workflows in which content
goes through certain steps: preparation for localization, start of the localization
- process by e.g. a conversion into a bitext (aligned parallel text) format like <a title="" href="#xliff" shape="rect">[XLIFF]</a>, the actual localization by human translators or
+ process by e.g. a conversion into a bitext (aligned parallel text) format like <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> or <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>, the actual localization by human translators or
machine translation and other adaptations of content, and finally the integration of
the localized content into the original format. That format is often based on XML or
HTML; (Web) content management systems are widely used for content creation, and
@@ -497,7 +497,7 @@
<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="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="its-and-xliff" id="its-and-xliff" shape="rect"/>1.5 ITS and XLIFF</h3><p>ITS 2.0 has no normative dependency on <a title="" href="#xliff" shape="rect">[XLIFF]</a> (XML Interchange File format). Nevertheless, important usage scenarios for ITS 2.0 are 1) XLIFF generation with e.g. HTML as an input file containing ITS 2.0 metadata, and 2) Direct representation of ITS 2.0 data categories within XLIFF files. See <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> for more information on these and other usage scenarios for ITS 2.0. For both scenarios, 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 beig defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>. Readers of this specification are encouraged to evaluate whether that mapping fulfills their needs and to provide comments in the <a href="http://lists.w3.org/Archives/Public/public-i18n-its-ig" shape="rect">ITS IG mailing list (public archive)</a>.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="its-and-xliff" id="its-and-xliff" shape="rect"/>1.5 ITS and XLIFF</h3><p>ITS 2.0 has no normative dependency on XLIFF (XML Interchange File format) <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> or <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>. Nevertheless, important usage scenarios for ITS 2.0 are 1) XLIFF generation with e.g. HTML as an input file containing ITS 2.0 metadata, and 2) Direct representation of ITS 2.0 data categories within XLIFF files. See <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> for more information on these and other usage scenarios for ITS 2.0. For both scenarios, a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rec">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>. Readers of this specification are encouraged to evaluate whether that mapping fulfills their needs and to provide comments in the <a href="http://lists.w3.org/Archives/Public/public-i18n-its-ig" shape="rect">ITS IG mailing list (public archive)</a>.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="out-of-scope" id="out-of-scope" shape="rect"/>1.6 Out of Scope</h3><p>The definition of what a localization process or localization parameters must address
is outside the scope of this standard and it does not address all of the mechanisms or
data formats (sometimes called localization project parameters) that may be needed to
@@ -691,7 +691,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="d0e1453" id="d0e1453" shape="rect"/>Example 14: 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="d0e1457" id="d0e1457" shape="rect"/>Example 14: 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
@@ -748,10 +748,11 @@
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conformance" id="conformance" shape="rect"/>4 Conformance</h2><p>
<em>This section is normative.</em>
</p><p>The usage of the term <em>conformance clause</em> in this section is in compliance
- with <a title="QA Framework:
 Specification Guidelines" href="#qa-framework" shape="rect">[QAFRAMEWORK]</a>.</p><p>This specification defines three types of conformance: conformance of <a href="#conformance-product-schema" shape="rect">1) ITS markup declarations</a> , conformance of
+ with <a title="QA Framework:
 Specification Guidelines" href="#qa-framework" shape="rect">[QAFRAMEWORK]</a>.</p><p>This specification defines four types of conformance: conformance of <a href="#conformance-product-schema" shape="rect">1) ITS markup declarations</a> , conformance of
<a href="#conformance-product-processing-expectations" shape="rect">2) processing expectations
- for ITS Markup</a> and conformance of <a href="#conformance-product-html-processing-expectations" shape="rect">3) processing expectations
- for ITS Markup in HTML</a>. Also special <a href="#conformance-class-html5-its" shape="rect">conformance class</a> is defined for using ITS markup in HTML5 documents, HTML5+ITS,
+ for ITS Markup</a>, conformance of <a href="#conformance-product-html-processing-expectations" shape="rect">3) processing expectations
+ for ITS Markup in HTML</a>, and <a href="#conformance-type-html5-its" shape="rect">Conformance Type 4: Markup conformance for HTML5+ITS documents</a>.
+ The conformance type 4 is defined for using ITS markup in HTML5 documents, HTML5+ITS,
which serves as an <em>applicable specification</em> in the sense specified in the
<a href="http://www.w3.org/TR/html5/infrastructure.html#extensibility" shape="rect">Extensibility
section</a> of <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. These conformance types and
@@ -776,7 +777,7 @@
element declared in the schema. It <a href="#rfc-keywords" shape="rect">SHOULD</a> be in a
content model for meta information, if this is available in that schema (e.g., the
<code>head</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>).</p></li><li><p id="its-conformance-1-3">
- <em>1-4:</em> If the <code class="its-elem-markup">span</code> element is
+ <em>1-3:</em> If the <code class="its-elem-markup">span</code> element is
used, it <a href="#rfc-keywords" shape="rect">SHOULD</a> be declared as an inline
element.</p></li></ul><span class="editor-note">[Ed. note: Above numbering is wrong.]</span><p id="its-markup-conformance-claims">Full implementations of this conformance type
will implement all markup declarations for ITS. Statements related to this conformance
@@ -816,13 +817,13 @@
the global selection mechanism, it <a href="#rfc-keywords" shape="rect">MUST</a> process an
XLink <code class="its-attr-markup">href</code> attribute found on a <code class="its-elem-markup">rules</code> element.</p></li><li><p id="its-conformance-2-3">
<em>2-3:</em> If an application claims to
- process ITS markup implementing the conformance clauses 2-1, 2-2 and 2-3, it <a href="#rfc-keywords" shape="rect">MUST</a> process that markup with XML
+ process ITS markup implementing the conformance clauses 2-2 and 2-3, it <a href="#rfc-keywords" shape="rect">MUST</a> process that markup with XML
documents.</p></li><li><p id="its-conformance-2-4">
<em>2-4:</em> After processing ITS information
- on the basis of conformance clauses <a href="#its-conformance-2-1" shape="rect">2-1</a> and
- <a href="#its-conformance-2-2" shape="rect">2-2</a>, an application <a href="#rfc-keywords" shape="rect">MAY</a> convert an XML document to NIF, using the
+ on the basis of conformance clauses <a href="#its-conformance-2-1" shape="rect">2-1</a>,
+ <a href="#its-conformance-2-2" shape="rect">2-2</a> and <a href="#its-conformance-2-3" shape="rect">2-3</a>, an application <a href="#rfc-keywords" shape="rect">MAY</a> convert an XML document to <a title="" href="#nif-reference" shape="rect">[NIF]</a>, using the
algorithm described in <a class="section-ref" href="#conversion-to-nif" shape="rect">Section 5.7: Conversion to NIF</a>.</p></li><li><p id="its-conformance-2-5">
- <em>2-5:</em> Non-ITS elements and attributes found in ITS elements <a href="#rfc2119" shape="rect">MAY</a> be ignored.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a> essentially
+ <em>2-5:</em> Non-ITS elements and attributes found in ITS elements <a href="#rfc2119" shape="rect">MAY</a> be ignored.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="nif-optional-feature">The conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a> essentially
means that the conversion to NIF is an optional feature of ITS 2.0, and that the
conversion is independent of whether ITS information has been made available via the
global or local selection mechanisms, see conformance clause <a href="#its-conformance-2-1-1" shape="rect">2-1-1</a>.</p></div><p id="its-processing-conformance-claims">Statements related to this conformance type
@@ -830,13 +831,14 @@
categories</a> they implement, and for each <a href="#def-datacat" shape="rect">data
category</a> which type of selection they support, whether they support processing
of XML. If the implementation provides the conversion to NIF (see conformance clause
- <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="https://github.com/finnle/ITS-2.0-Testsuite/" shape="rect">ITS 2.0 test suite</a>. All
- tests specify which data category is processed (clause 2-1); they are relevant for
- (clause 2-1-1) global or local selection, or both; they require the processing of
- defaults and precedence of selections (clauses 2-1-2 and 2-1-3); for each data
- category there are tests with linked rules (2-2); and all types of tests are given for
- XML (clause 2-3). In addition, there are test cases for conversion to NIF (clause
- 2-4). Implementers are encouraged to organize their documentation in a similar way, so
+ <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="http://tbd:update" shape="rect">ITS 2.0 test suite</a>. All
+ tests specify which data category is processed (clause <a href="#its-conformance-2-1" shape="rect">2-1</a>); they are relevant for
+ (clause <a href="#its-conformance-2-1-1" shape="rect">2-1-1</a>) global or local selection, or both; they require the processing of
+ defaults and precedence of selections (clauses <a href="#its-conformance-2-1-2" shape="rect">2-1-2</a> and
+ <a href="#its-conformance-2-1-3" shape="rect">2-1-3</a>); for each data
+ category there are tests with linked rules (<a href="#its-conformance-2-2" shape="rect">2-2</a>); and all types of tests are given for
+ XML (clause <a href="#its-conformance-2-3" shape="rect">2-3</a>). In addition, there are test cases for conversion to NIF (clause
+ <a href="#its-conformance-2-4" shape="rect">2-4</a>). Implementers are encouraged to organize their documentation in a similar way, so
that users of ITS 2.0 easily can understand the processing capabilities available.</p></div></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conformance-product-html-processing-expectations" id="conformance-product-html-processing-expectations" shape="rect"/>4.3 Conformance Type 3: Processing Expectations for ITS Markup in HTML</h3><p>
<em>Description:</em> Processors need to compute the ITS information that pertains
@@ -869,13 +871,20 @@
<code>rel</code> attribute with the value <code>its-rules</code>.</p></li><li><p id="its-conformance-3-3">
<em>3-3:</em> If an application claims to
process ITS markup implementing the conformance clauses 3-1 and 3-2, it <a href="#rfc-keywords" shape="rect">MUST</a> process that markup within HTML
- documents.</p></li></ul><p id="its-html-processing-conformance-claims">Statements related to this conformance
+ documents.</p></li><li><p id="its-conformance-3-4">
+ <em>3-4:</em> After processing ITS information
+ on the basis of conformance clauses <a href="#its-conformance-3-1" shape="rect">3-1</a>,
+ <a href="#its-conformance-3-2" shape="rect">3-2</a> and
+ <a href="#its-conformance-3-3" shape="rect">3-3</a>, an application <a href="#rfc-keywords" shape="rect">MAY</a> convert an <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> document to
+ <a title="" href="#nif-reference" shape="rect">[NIF]</a>, using the
+ algorithm described in <a class="section-ref" href="#conversion-to-nif" shape="rect">Section 5.7: Conversion to NIF</a>.</p></li></ul><p id="its-html-processing-conformance-claims">Statements related to this conformance
type <a href="#rfc-keywords" shape="rect">MUST</a> list all <a href="#def-datacat" shape="rect">data
categories</a> they implement and, for each <a href="#def-datacat" shape="rect">data
category</a>, which type of selection they support.</p></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conformance-class-html5-its" id="conformance-class-html5-its" shape="rect"/>4.4 Conformance Class for HTML5+ITS documents</h3><p>Conforming HTML5+ITS documents are those that comply with all the conformance criteria
+<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="conformance-type-html5-its" id="conformance-type-html5-its" shape="rect"/>4.4 Conformance Type 4: Markup conformance for HTML5+ITS documents</h3><p>Conforming HTML5+ITS documents are those that comply with all the conformance criteria
for documents as defined in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> with the following
- exception:</p><ul><li><p><a href="http://dev.w3.org/html5/spec/single-page.html#global-attributes" shape="rect">Global attributes</a> that can be used on all HTML elements are extended by
+ exception:</p><ul><li><p id="its-conformance-4-1">Conformance clause <em>4-1:</em>
+ <a href="http://dev.w3.org/html5/spec/single-page.html#global-attributes" shape="rect">Global attributes</a> that can be used on all HTML elements are extended by
attributes for local data categories as defined in <a class="section-ref" href="#html5-local-attributes" shape="rect">Section 6.1: Mapping of Local Data Categories to HTML</a>.</p></li></ul></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="its-processing" id="its-processing" shape="rect"/>5 Processing of ITS information</h2><p>
<em>This section is normative.</em>
@@ -954,9 +963,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="d0e2368" id="d0e2368" 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="d0e2426" id="d0e2426" 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="d0e2379" id="d0e2379" 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="d0e2437" id="d0e2437" 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
that 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>.
@@ -1001,14 +1010,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="d0e2590" id="d0e2590" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2648" id="d0e2648" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
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="d0e2600" id="d0e2600" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2658" id="d0e2658" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[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" 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="d0e2613" id="d0e2613" 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="d0e2671" id="d0e2671" 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>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>,
@@ -3108,7 +3117,8 @@
expressed locally in HTML</div><p>The <code class="its-attr-markup">its-loc-quality-rating-score</code>,
<code class="its-attr-markup">its-loc-quality-rating-score-threshold</code> and
<code class="its-attr-markup">its-loc-quality-rating-profile-ref</code> are used to score the quality of the
- document.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">fr</span>
+ document.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">fr</span>
<span class="hl-attribute" style="color: #F5844C">its-loc-quality-rating-profile-ref</span>=<span class="hl-value" style="color: #993300">http://example.org/qaModel/v13</span>
<span class="hl-attribute" style="color: #F5844C">its-loc-quality-rating-score</span>=<span class="hl-value" style="color: #993300">90</span>
<span class="hl-attribute" style="color: #F5844C">its-loc-quality-rating-score-threshold</span>=<span class="hl-value" style="color: #993300">80</span><strong class="hl-tag" style="color: #000096">
@@ -5837,7 +5847,8 @@
Princeton University. 2010, available at: <a href="http://wordnet.princeton.edu" shape="rect">http://wordnet.princeton.edu</a>.</dd><dt class="label"><a name="xhtml10" id="xhtml10" shape="rect"/>XHTML 1.0</dt><dd>Steven Pemberton et al. <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect"><cite>XHTML™ 1.0 The Extensible
HyperText Markup Language (Second Edition)</cite></a>. W3C Recommendation 26 January 2000, revised 1 August 2002. Available at <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect">
http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>. The latest version of <a href="http://www.w3.org/TR/xhtml1/" shape="rect">XHTML 1.0</a> is available at
- http://www.w3.org/TR/xhtml1/.</dd><dt class="label"><a name="xliff" id="xliff" shape="rect"/>XLIFF</dt><dd>XLIFF reference - tbd.</dd><dt class="label"><a name="xml-i18n-bp" id="xml-i18n-bp" shape="rect"/>XML i18n BP</dt><dd>Yves Savourel, Jirka Kosek, Richard Ishida.
+ http://www.w3.org/TR/xhtml1/.</dd><dt class="label"><a name="xliff1.2" id="xliff1.2" shape="rect"/>XLIFF 1.2</dt><dd>Savourel, Yves, John Reid, Tony Jewtushenko and Rodolfo M. Raya. <a href="http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html" shape="rect"><cite>XLIFF Version 1.2</cite></a>. OASIS Standard 1 February 2008.
+ Available at <a href="http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html" shape="rect">http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html</a>.</dd><dt class="label"><a name="xliff2.0" id="xliff2.0" shape="rect"/>XLIFF 2.0</dt><dd>Comerford, Tom, David Filip, Rodolfo M. Raya and Yves Savourel. <a href="http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/xliff-core-v2.0-csprd01.html" shape="rect"><cite>XLIFF Version 2.0</cite></a>. Committee Specification Draft 01 / Public Review Draft 01. Available at <a href="http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/xliff-core-v2.0-csprd01.html" shape="rect">http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/xliff-core-v2.0-csprd01.html</a>. The latest version of <a href="http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html" shape="rect">XLIFF 2.0</a> is available at http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html</dd><dt class="label"><a name="xml-i18n-bp" id="xml-i18n-bp" shape="rec"/>XML i18n BP</dt><dd>Yves Savourel, Jirka Kosek, Richard Ishida.
<a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/" shape="rect"><cite>Best
Practices for XML Internationalization</cite></a>. Available at <a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/" shape="rect">http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/</a>. The latest version of
<a href="http://www.w3.org/TR/xml-i18n-bp/" shape="rect">xml-i18n-bp</a> is available at
@@ -6136,12 +6147,11 @@
Selectors integration.</p></li><li><p>Added examples to <a class="section-ref" href="#externalresource" shape="rect">Section 8.12: External Resource</a>.</p></li><li><p>Simplified <a class="section-ref" href="#LocaleFilter" shape="rect">Section 8.10: Locale Filter</a>.</p></li><li><p>Added a note about HTML and the attributes <code class="its-attr-markup">dir</code> and <code class="its-attr-markup">translate</code>
to <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.2: Local Selection in an XML Document</a>.</p></li><li><p>Added definition of <code class="its-elem-markup">param</code> element to <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>.</p></li><li><p>Added <a class="section-ref" href="#target-pointer" shape="rect">Section 8.13: Target Pointer</a>.</p></li><li><p>Original Ruby markup model changed to HTML5 Ruby model.</p></li><li><p>Updated references.</p></li><li><p>Added <a class="section-ref" href="#preservespace" shape="rect">Section 8.15: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#lqissue" shape="rect">Section 8.16: Localization Quality Issue</a> and the related <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a>.</p></li><li><p>Added <a class="section-ref" href="#lqrating" shape="rect">Section 8.17: Loclization Quality Rating</a>.</p></li><li><p>Added a placeholder <a class="section-ref" href="#mtconfidence" shape="rect">Section 8.18: MT Confidence</a>.</p></li></ol><p id="changelog-since-20120626">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-20120626/" shape="rect">ITS 2.0 Working Draft 26 June 2012</a>.</p><ol class="depth1"><li><p>Various editorial changes (non-normative references update, style & grammar
- fixes).</p></li><li><p>Made clarifications to <a class="section-ref" href="#out-of-scope" shape="rect">Section 1.6: Out of Scope</a>, <a class="section-ref" href="#design-decisions" shape="rect">Section 1.7: Important Design Principles</a>.</p></li><li><p>Added explanatory note on precedence and overriding in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a>.</p></li><li><p>Reordered some components in <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>.</p></li><li><p>Restructured <a class="section-ref" href="#relation-to-its10-and-new-principles" shape="rect">Section 1.1: Relation to ITS 1.0 and New Principles</a>.</p></li><li><p>Added <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a> as a stub.</p></li><li><p>Added <a class="section-ref" href="#LocaleFilter" shape="rect">Section 8.10: Locale Filter</a>.</p></li><li><p>Added <a class="sectionref" href="#domain" shape="rect">Section 8.8: Domain</a>.</p></li><li><p>Added <a class="section-ref" href="#usage-in-legacy-html" shape="rect">Section 1.4.5: Version of HTML</a>.</p></li><li><p>Added local markup in <a class="section-ref" href="#elements-within-text" shape="rect">Section 8.7: Elements Within Text</a>.</p></li><li><p>Added <a class="section-ref" href="#externalresource" shape="rect">Section 8.12: External Resource</a>.</p></li><li><p>Updated examples to use the <code class="its-attr-markup">version</code> attribute with the value
- <code>2.0</code>.</p></li></ol><p id="changelog-since-20070403">The following log records major changes that have been
+ fixes).</p></li><li><p>Made clarifications to <a class="section-ref" href="#out-of-scope" shape="rect">Section 1.6: Out of Scope</a>, <a class="section-ref" href="#design-decisions" shape="rect">Section 1.7: Important Design Principles</a>.</p></li><li><p>Added explanatory note on precedence and overriding in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a>.</p></li><li><p>Reordered some components in <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>.</p></li><li><p>Restructured <a class="section-ref" href="#relation-to-its10-and-new-principles" shape="rect">Section 1.1: Relation to ITS 1.0 and New Principles</a>.</p></li><li><p>Added <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a> as a stub.</p></li><li><p>Added <a class="section-ref" href="#LocaleFilter" shape="rect">Section 8.10: Locale Filter</a>.</p></li><li><p>Added <a class="sectionref" href="#domain" shape="rect">Section 8.8: Domain</a>.</p></li><li><p>Added <a class="section-ref" href="#usage-in-legacy-html" shape="rect">Section 1.4.5: Version of HTML</a>.</p></li><li><p>Added local markup in <a class="section-ref" href="#elements-within-text" shape="rect">Section 8.7: Elements Within Text</a>.</p></li><li><p>Added <a class="section-ref" href="#externalresource" shape="rect">Section 8.12: External Resource</a>.</p></li><li><p>Updated examples to use the <code class="its-attr-markup">version</code> attribute with the value<code>2.0</code>.</p></li></ol><p id="changelog-since-20070403">The following log records major changes that have been
made to this document between the <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0 Recommendation</a> and
this document.</p><ol class="depth1"><li><p>Clarified <a href="#introduction" shape="rect">introduction</a> to cover ITS 2.0</p></li><li><p>Added a subsection on the relation to ITS 1.0 to the introduction, see <a class="section-ref" href="#relation-to-its10" shape="rect">Section 1.1.1: Relation to ITS 1.0</a></p></li><li><p>Created HTML based declarations for various data categories, see e.g., HTML
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 45</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">Section 5.7: 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"/>I Acknowledgements (Non-Normative)</h2><p>This document has been developed with contributions by the
MultilingualWeb-LT Working Group: 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), 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), Daniel Grasmick (Lucy Software and Services GmbH), Declan Groves (Centre for Next Generation Localisation), Manuel Honegger (University of Limerick), Dominic Jones (Trinity College Dublin), Milan Karásek (Moravia Worldwide), Jirka Kosek (University of Economics, Prague), Michael Kruppa (Cocomore AG), Alejandro Leiva (Cocomore AG), David Lewis (Trinity College Dublin), Fredrik Lden (ENLASO Corporation), Christian Lieske (SAP AG), Arle Lommel (German Research Center for Artificial Intelligence (DFKI) Gmbh), Shaun McCance ((public) Invited expert), Sean Mooney (University of Limerick), Jan Nelson (Microsoft Corporation), Pablo Nieto Caride (Linguaserve), Naoto Nishio (University of Limerick), Philip O'Duffy (University of Limerick), Des Oates (Adobe Systems Inc.), Carina Pellar (Cocomore AG), Georgios Petasis (Institute of Informatics & Telecommunications (IIT), NCSR), 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 (W3C Fellow on behalf of DFKI), Yves Savourel (ENLASO Corporation), Jörg Schütz (W3C Invited Experts), Ankit Srivastava (Centre for Next Generation Localisation), Tadej Štajner (Jozef Stefan Institute), Olaf-Michael Stefanov ((public) Invited expert), Najib Tounsi (Ecoe Mohammadia d'Ingenieurs Rabat (EMI)), 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 href="#conversion-to-nif" 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>.</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
+ </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/06/07 18:04:26 1.443
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/10 16:48:54 1.444
@@ -375,7 +375,7 @@
<p>These types of users are concerned with localization workflows in which content
goes through certain steps: preparation for localization, start of the localization
process by e.g. a conversion into a bitext (aligned parallel text) format like <ptr
- target="#xliff" type="bibref"/>, the actual localization by human translators or
+ target="#xliff1.2" type="bibref"/> or <ptr target="#xliff2.0" type="bibref"/>, the actual localization by human translators or
machine translation and other adaptations of content, and finally the integration of
the localized content into the original format. That format is often based on XML or
HTML; (Web) content management systems are widely used for content creation, and
@@ -572,7 +572,8 @@
<div xml:id="its-and-xliff">
<head>ITS and XLIFF</head>
- <p>ITS 2.0 has no normative dependency on <ptr target="#xliff" type="bibref"/> (XML Interchange File format). Nevertheless, important usage scenarios for ITS 2.0 are 1) XLIFF generation with e.g. HTML as an input file containing ITS 2.0 metadata, and 2) Direct representation of ITS 2.0 data categories within XLIFF files. See <ptr target="#mlw-metadata-us-impl" type="bibref"/> for more information on these and other usage scenarios for ITS 2.0. For both scenarios, a <ref target="http://www.w3.org/International/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>. Readers of this specification are encouraged to evaluate whether that mapping fulfills their needs and to provide comments in the <ref target="http://lists.w3.org/Archives/Public/public-i18n-its-ig">ITS IG mailing list (public archive)</rf>.</p>
+ <p>ITS 2.0 has no normative dependency on XLIFF (XML Interchange File format) <ptr
+ target="#xliff1.2" type="bibref"/> or <ptr target="#xliff2.0" type="bibref"/>. Nevertheless, important usage scenarios for ITS 2.0 are 1) XLIFF generation with e.g. HTML as an input file containing ITS 2.0 metadata, and 2) Direct representation of ITS 2.0 data categories within XLIFF files. See <ptr target="#mlw-metadata-us-impl" type="bibref"/> for more information on these and other usage scenarios for ITS 2.0. For both scenarios, a <ref target="http://www.w3.org/International/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>. Readers of this specification are encouraged to evaluate whether that mapping fulfills their needs and to provide comments in the <ref target="http://lists.w3.org/Archives/Public/public-i18n-its-ig">ITS IG mailing list (public archive)</ref>.</p>
</div>
<div xml:id="out-of-scope">
<head>Out of Scope</head>
@@ -968,13 +969,14 @@
</p>
<p>The usage of the term <emph>conformance clause</emph> in this section is in compliance
with <ptr target="#qa-framework" type="bibref"/>.</p>
- <p>This specification defines three types of conformance: conformance of <ref
+ <p>This specification defines four types of conformance: conformance of <ref
target="#conformance-product-schema">1) ITS markup declarations</ref> , conformance of
<ref target="#conformance-product-processing-expectations">2) processing expectations
- for ITS Markup</ref> and conformance of <ref
+ for ITS Markup</ref>, conformance of <ref
target="#conformance-product-html-processing-expectations">3) processing expectations
- for ITS Markup in HTML</ref>. Also special <ref target="#conformance-class-html5-its"
- >conformance class</ref> is defined for using ITS markup in HTML5 documents, HTML5+ITS,
+ for ITS Markup in HTML</ref>, and <ref target="#conformance-type-html5-its"
+ >Conformance Type 4: Markup conformance for HTML5+ITS documents</ref>.
+ The conformance type 4 is defined for using ITS markup in HTML5 documents, HTML5+ITS,
which serves as an <emph>applicable specification</emph> in the sense specified in the
<ref target="http://www.w3.org/TR/html5/infrastructure.html#extensibility">Extensibility
section</ref> of <ptr target="#html5" type="bibref"/>. These conformance types and
@@ -1024,7 +1026,7 @@
target="#rfc2119">SHOULD</ref> be declared at all
elements which are part of the<hi diff="del">
existing or new</hi> schema.</item>-->
- <item><p xml:id="its-conformance-1-3"><emph>1-4:</emph> If the <gi>span</gi> element is
+ <item><p xml:id="its-conformance-1-3"><emph>1-3:</emph> If the <gi>span</gi> element is
used, it <ref target="#rfc-keywords">SHOULD</ref> be declared as an inline
element.</p></item>
@@ -1092,17 +1094,17 @@
the global selection mechanism, it <ref target="#rfc-keywords">MUST</ref> process an
XLink <att>href</att> attribute found on a <gi>rules</gi> element.</p></item>
<item><p xml:id="its-conformance-2-3"><emph>2-3:</emph> If an application claims to
- process ITS markup implementing the conformance clauses 2-1, 2-2 and 2-3, it <ref
+ process ITS markup implementing the conformance clauses 2-2 and 2-3, it <ref
target="#rfc-keywords">MUST</ref> process that markup with XML
documents.</p></item>
<item><p xml:id="its-conformance-2-4"><emph>2-4:</emph> After processing ITS information
- on the basis of conformance clauses <ref target="#its-conformance-2-1">2-1</ref> and
- <ref target="#its-conformance-2-2">2-2</ref>, an application <ref
- target="#rfc-keywords">MAY</ref> convert an XML document to NIF, using the
+ on the basis of conformance clauses <ref target="#its-conformance-2-1">2-1</ref>,
+ <ref target="#its-conformance-2-2">2-2</ref> and <ref target="#its-conformance-2-3">2-3</ref>, an application <ref
+ target="#rfc-keywords">MAY</ref> convert an XML document to <ptr target="#nif-reference" type="bibref"/>, using the
algorithm described in <ptr target="#conversion-to-nif" type="specref"/>.</p></item>
<item><p xml:id="its-conformance-2-5"><emph>2-5:</emph> Non-ITS elements and attributes found in ITS elements <ref target="#rfc2119">MAY</ref> be ignored.</p></item>
</list>
- <note><p>The conformance clause <ref target="#its-conformance-2-4">2-4</ref> essentially
+ <note><p xml:id="nif-optional-feature">The conformance clause <ref target="#its-conformance-2-4">2-4</ref> essentially
means that the conversion to NIF is an optional feature of ITS 2.0, and that the
conversion is independent of whether ITS information has been made available via the
global or local selection mechanisms, see conformance clause <ref
@@ -1116,13 +1118,14 @@
>MUST</ref> be stated.</p>
<note><p>The above conformance clauses are directly reflected in the <ref
- target="https://github.com/finnle/ITS-2.0-Testsuite/">ITS 2.0 test suite</ref>. All
- tests specify which data category is processed (clause 2-1); they are relevant for
- (clause 2-1-1) global or local selection, or both; they require the processing of
- defaults and precedence of selections (clauses 2-1-2 and 2-1-3); for each data
- category there are tests with linked rules (2-2); and all types of tests are given for
- XML (clause 2-3). In addition, there are test cases for conversion to NIF (clause
- 2-4). Implementers are encouraged to organize their documentation in a similar way, so
+ target="http://tbd:update">ITS 2.0 test suite</ref>. All
+ tests specify which data category is processed (clause <ref target="#its-conformance-2-1">2-1</ref>); they are relevant for
+ (clause <ref target="#its-conformance-2-1-1">2-1-1</ref>) global or local selection, or both; they require the processing of
+ defaults and precedence of selections (clauses <ref target="#its-conformance-2-1-2">2-1-2</ref> and
+ <ref target="#its-conformance-2-1-3">2-1-3</ref>); for each data
+ category there are tests with linked rules (<ref target="#its-conformance-2-2">2-2</ref>); and all types of tests are given for
+ XML (clause <ref target="#its-conformance-2-3">2-3</ref>). In addition, there are test cases for conversion to NIF (clause
+ <ref target="#its-conformance-2-4">2-4</ref>). Implementers are encouraged to organize their documentation in a similar way, so
that users of ITS 2.0 easily can understand the processing capabilities available.</p></note>
</div>
<div xml:id="conformance-product-html-processing-expectations">
@@ -1182,22 +1185,29 @@
process ITS markup implementing the conformance clauses 3-1 and 3-2, it <ref
target="#rfc-keywords">MUST</ref> process that markup within HTML
documents.</p></item>
+ <item><p xml:id="its-conformance-3-4"><emph>3-4:</emph> After processing ITS information
+ on the basis of conformance clauses <ref target="#its-conformance-3-1">3-1</ref>,
+ <ref target="#its-conformance-3-2">3-2</ref> and
+ <ref target="#its-conformance-3-3">3-3</ref>, an application <ref
+ target="#rfc-keywords">MAY</ref> convert an <ptr target="#html5" type="bibref"/> document to
+ <ptr target="#nif-reference" type="bibref"/>, using the
+ algorithm described in <ptr target="#conversion-to-nif" type="specref"/>.</p></item>
</list>
<p xml:id="its-html-processing-conformance-claims">Statements related to this conformance
type <ref target="#rfc-keywords">MUST</ref> list all <ref target="#def-datacat">data
categories</ref> they implement and, for each <ref target="#def-datacat">data
category</ref>, which type of selection they support.</p>
</div>
- <div xml:id="conformance-class-html5-its">
- <head>Conformance Class for HTML5+ITS documents</head>
+ <div xml:id="conformance-type-html5-its">
+ <head>Conformance Type 4: Markup conformance for HTML5+ITS documents</head>
<p>Conforming HTML5+ITS documents are those that comply with all the conformance criteria
for documents as defined in <ptr target="#html5" type="bibref"/> with the following
exception:</p>
<list>
- <item><ref target="http://dev.w3.org/html5/spec/single-page.html#global-attributes"
+ <item><p xml:id="its-conformance-4-1">Conformance clause <emph>4-1:</emph> <ref target="http://dev.w3.org/html5/spec/single-page.html#global-attributes"
>Global attributes</ref> that can be used on all HTML elements are extended by
attributes for local data categories as defined in <ptr
- target="#html5-local-attributes" type="specref"/>.</item>
+ target="#html5-local-attributes" type="specref"/>.</p></item>
</list>
</div>
</div>
@@ -5717,7 +5727,9 @@
http://www.w3.org/TR/2002/REC-xhtml1-20020801/</ref>. The latest version of <ref
target="http://www.w3.org/TR/xhtml1/">XHTML 1.0</ref> is available at
http://www.w3.org/TR/xhtml1/.</bibl>
- <bibl xml:id="xliff" n="XLIFF">XLIFF reference - tbd.</bibl>
+ <bibl xml:id="xliff1.2" n="XLIFF 1.2">Savourel, Yves, John Reid, Tony Jewtushenko and Rodolfo M. Raya. <title><ref target="http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html">XLIFF Version 1.2</ref></title>. OASIS Standard 1 February 2008.
+ Available at <ref target="http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html">http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html</ref>.</bibl>
+ <bibl xml:id="xliff2.0" n="XLIFF 2.0">Comerford, Tom, David Filip, Rodolfo M. Raya and Yves Savourel. <title><ref target="http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/xliff-core-v2.0-csprd01.html">XLIFF Version 2.0</ref></title>. Committee Specification Draft 01 / Public Review Draft 01. Available at <ref target="http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/xliff-core-v2.0-csprd01.html">http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/xliff-core-v2.0-csprd01.html</ref>. The latest version of <ref target="http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html">XLIFF 2.0</ref> is available at http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html</bibl>
<bibl n="XML i18n BP" xml:id="xml-i18n-bp">Yves Savourel, Jirka Kosek, Richard Ishida.
<title><ref target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/">Best
Practices for XML Internationalization</ref></title>. Available at <ref
@@ -6470,7 +6482,6 @@
<item>Daniel Naber for introducing us to <ref
target="http://languagetool.org">LanguageTool</ref> and for implementing <ref
target="#lqissue-typevalues">Localization Quality Issue Type</ref> functionality in language tool.</item>
- add: Shaun, Tilde, ]init[.
</list>
</div>
</back>
Received on Monday, 10 June 2013 16:48:57 UTC