- From: CVS User jkosek <cvsmail@w3.org>
- Date: Sat, 01 Jun 2013 11:39:35 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv10611
Modified Files:
its20.odd
Log Message:
Edits from Arle for section 4
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/01 11:29:00 1.433
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/01 11:39:34 1.434
@@ -986,7 +986,7 @@
the markup in XML documents. Such markup is subject to the conformance clauses in <ptr
target="#conformance-product-processing-expectations" type="specref"/>.</p>
<p><emph>Definitions related to this conformance type:</emph> ITS markup declarations are
- defined in various subsections in
+ defined in various subsections
<!-- <ptr
target="#its-processing" type="specref"/> and <ptr
target="#datacategory-description" type="specref"/> (e.g. <ptr
@@ -1006,12 +1006,11 @@
<item>one of the local ITS attributes</item>
<item><gi>span</gi> element</item>
</list></item>
- <item><p xml:id="its-conformance-1-2"><emph>1-2:</emph> If the <gi>rules</gi> element is
- used, it <ref target="#rfc-keywords">MUST</ref> be part of the content model of at
- least one element declared in the schema. It <ref target="#rfc-keywords"
- >SHOULD</ref> be in a content model for meta information, if this is available in
- that schema (e.g. the <code>head</code> element in <ptr target="#xhtml10"
- type="bibref"/>).</p></item>
+ <item><p xml:id="its-conformance-1-2"><emph>1-2:</emph> If the <gi>rules</gi> element is used, it <ref
+ target="#rfc-keywords">MUST</ref> be part of the content model of at least one
+ element declared in the schema. It <ref target="#rfc-keywords">SHOULD</ref> be in a
+ content model for meta information, if this is available in that schema (e.g., the
+ <code>head</code> element in <ptr target="#xhtml10" type="bibref"/>).</p></item>
<!-- <item diff="del"><emph>1-2: </emph> The
<gi>schemaRule</gi> element <ref
target="#rfc2119">MAY</ref> be used as part of a <ref
@@ -1046,7 +1045,7 @@
target="#def-selection">selection mechanism</ref>, <ref
target="#datacategories-defaults-etc">defaults / inheritance / overriding
characteristics</ref>, and <ref target="#selection-precedence">precedence</ref>. The
- markup <ref target="#rfc-keywords">MAY</ref> be valid against a schema which conforms to
+ markup <ref target="#rfc-keywords">MAY</ref> be valid against a schema that conforms to
the clauses in <ptr target="#conformance-product-schema" type="specref"/>.</p>
<p><emph>Definitions related to this conformance type:</emph> The processing expectations
for ITS markup make use of selection mechanisms defined in <ptr target="#its-processing"
@@ -1063,9 +1062,9 @@
process.</p>
<note>
<p> Application-specific processing (that is processing that goes beyond the computation
- of ITS information for a node) such as automated filtering of translatable content
- based on the <ref target="#trans-datacat">Translate</ref> data category is not covered
- by the conformance clauses below.</p>
+ of ITS information for a node), such as automated filtering of translatable content
+ based on the <ref target="#trans-datacat">Translate</ref> data category, is not
+ covered by the conformance clauses below.</p>
</note>
<p>
<emph>Conformance clauses:</emph>
@@ -1087,10 +1086,9 @@
type="specref"/>, for the type of selections it processes.</p></item>
</list></item>
- <item><p xml:id="its-conformance-2-2"><emph>2-2:</emph> If an application claims to
- process ITS markup for the global selection mechanism, it <ref
- target="#rfc-keywords">MUST</ref> process an XLink <att>href</att> attribute found
- on a <gi>rules</gi> elements.</p></item>
+ <item><p xml:id="its-conformance-2-2"><emph>2-2:</emph> If an application claims to process ITS markup for
+ 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
target="#rfc-keywords">MUST</ref> process that markup with XML
@@ -1122,16 +1120,15 @@
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). Implementors 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>
+ 2-4). 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">
<head>Conformance Type 3: Processing Expectations for ITS Markup in HTML</head>
<p><emph>Description:</emph> Processors need to compute the ITS information that pertains
- to a node in a HTML document. The ITS processing expectations define how the computation
- has to be carried out. Correct computation involves support for <ref
+ to a node in an HTML document. The ITS processing expectations define how the
+ computation has to be carried out. Correct computation involves support for <ref
target="#def-selection">selection mechanism</ref>, <ref
target="#datacategories-defaults-etc">defaults / inheritance / overriding
characteristics</ref>, and <ref target="#html5-selection-precedence"
@@ -1147,9 +1144,8 @@
target="#html5-inline-global-rules">inline global</ref>).</p>
<p><emph>Who uses this conformance type:</emph> Applications that need to process the
nodes captured by a data category for internationalization or localization. Examples of
- this type of application are: ITS markup-aware editors, or translation tools that make
- use of ITS markup to filter translatable text as an input to the localization
- process.</p>
+ this type of application are ITS markup-aware editors or translation tools that make use
+ of ITS markup to filter translatable text as an input to the localization process.</p>
<note>
<p> Application-specific processing (that is processing that goes beyond the computation
of ITS information for a node) such as automated filtering of translatable content
@@ -1176,11 +1172,10 @@
type="specref"/>, for the type of selections it processes.</p></item>
</list></item>
- <item><p xml:id="its-conformance-3-2"><emph>3-2:</emph> If an application claims to
- process ITS markup for the global selection mechanism, it <ref
- target="#rfc-keywords">MUST</ref> process a <att>href</att> attribute found on a
- <code>link</code> elements which has a <code>rel</code> attribute with the value
- <code>its-rules</code>.</p></item>
+ <item><p xml:id="its-conformance-3-2"><emph>3-2:</emph> If an application claims to process ITS markup for
+ the global selection mechanism, it <ref target="#rfc-keywords">MUST</ref> process a
+ <att>href</att> attribute found on a <code>link</code> element that has a
+ <code>rel</code> attribute with the value <code>its-rules</code>.</p></item>
<item><p xml:id="its-conformance-3-3"><emph>3-3:</emph> If an application claims to
process ITS markup implementing the conformance clauses 3-1 and 3-2, it <ref
target="#rfc-keywords">MUST</ref> process that markup within HTML
@@ -1188,8 +1183,8 @@
</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>
+ 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>
@@ -1198,7 +1193,7 @@
exception:</p>
<list>
<item><ref target="http://dev.w3.org/html5/spec/single-page.html#global-attributes"
- >Global attributes</ref> which can be used on all HTML elements are extended by
+ >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>
</list>
Received on Saturday, 1 June 2013 11:39:36 UTC