- From: CVS User jkosek <cvsmail@w3.org>
- Date: Sat, 01 Jun 2013 15:43:13 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv27934
Modified Files:
its20.odd
Log Message:
Edits from Arle for section 6 and 7
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/01 14:35:49 1.435
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/01 15:43:13 1.436
@@ -1911,33 +1911,33 @@
<div xml:id="html5-local-attributes">
<head>Mapping of Local Data Categories to HTML</head>
<p>All data categories defined in <ptr target="#datacategory-description" type="specref"/>
- and having local implementation might be used in HTML with the exception of <ref
+ and having local implementation may be used in HTML with the exception of the <ref
target="#trans-datacat" type="specref">Translate</ref>, <ref target="#directionality"
- type="specref">Directionality</ref> and <ref target="#language-information" type="specref">Language
- Information</ref> data categories.</p>
+ type="specref">Directionality</ref> and <ref target="#language-information"
+ type="specref">Language Information</ref> data categories.</p>
<note>
- <p>The above mentioned data categories are excluded because HTML has native markup for
+ <p>The above-mentioned data categories are excluded because HTML has native markup for
them.</p>
</note>
- <p>In HTML data categories are implemented as attributes. Name of the HTML attribute is
- derived from the name of the attribute defined in the local implementation by using the
- following rules:<list type="ordered">
- <item>Attribute name is prefixed with <code>its-</code></item>
+ <p>In HTML data categories are implemented as attributes. The name of the HTML attribute
+ is derived from the name of the attribute defined in the local implementation by using
+ the following rules:<list type="ordered">
+ <item>The attribute name is prefixed with <code>its-</code></item>
<item>Each uppercase letter in the attribute name is replaced by <code>-</code>
(U+002D) followed by a lowercase variant of the letter.</item>
</list></p>
<p><ptr type="exref" target="#EX-within-text-local-1"/> demonstrates the <ref
target="#elements-within-text">Elements Within Text</ref> data category with the local
XML attribute <att>withinText</att>. <ptr type="exref"
- target="#EX-within-text-local-html5-1"/> demonstrates the counterpart in HTML, that is
+ target="#EX-within-text-local-html5-1"/> demonstrates the counterpart in HTML, i.e.,
the local attribute <att>its-within-text</att>.</p>
<p>Values of attributes which corresponds to data categories with a predefined set of
values <ref target="#rfc2119">MUST</ref> be matched ASCII-case-insensitively. </p>
- <note><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in
- HTML terminology data category can be stored as <att>its-term</att>,
- <code>ITS-TERM</code>, <code>its-Term</code> etc. All those attributes are treated
- as equivalent and will get normalized upon DOM construction.</p></note>
- <p>Values of attributes which corresponds to data categories which use <ref
+ <note><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in HTML the <ref
+ target="#terminology">terminology data category</ref> can be stored as
+ <att>its-term</att>, <code>ITS-TERM</code>, <code>its-Term</code> etc. All of those
+ attributes are treated as equivalent and will be normalized upon DOM construction.</p></note>
+ <p>Values of attributes that correspond to data categories that use <ref
target="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double">XML Schema double
data type</ref>
<ref target="#rfc2119">MUST</ref> be also valid floating-point numbers as defined in
@@ -1946,23 +1946,23 @@
<div xml:id="html5-global-rules">
<head>Global rules</head>
- <p>Various aspects for global rules in general, external global rules or inline global
+ <p>Various aspects for global rules in general, external global rules, or inline global
rules need to be taken into account. An example of an HTML5 document using global rules
is <ptr target="#EX-translate-html5-global-1" type="exref"/>. The corresponding rules
file is <ptr target="#EX-translate-html5-global-1-rules-file" type="exref"/>.</p>
<note>
- <p>By default XPath 1.0 will be used for selection in global rules. If users prefer
+ <p>By default XPath 1.0 will be used for selection in global rules. If users prefer an
easier selection mechanism, they can switch query language to CSS selectors by using
the <att>queryLanguage</att> attribute, see <ptr target="#queryLanguage"
type="specref"/>.</p>
</note>
<note>
- <p>HTML5 parsing algorithm automatically puts all HTML elements into XHTML namespace
- (<code>http://www.w3.org/1999/xhtml</code>). Selectors used in global rules must
- take this into account.</p>
+ <p>The HTML5 parsing algorithm automatically puts all HTML elements into the XHTML
+ namespace (<code>http://www.w3.org/1999/xhtml</code>). Selectors used in global rules
+ must take this into account.</p>
</note>
- <p xml:id="html5-external-global-rules">Link to external global rules is specified in
- <att>href</att> attribute of <code>link</code> element, with the link relation
+ <p xml:id="html5-external-global-rules">Linking to external global rules is specified in
+ the <att>href</att> attribute of <code>link</code> elements, with the link relation
<code>its-rules</code>.</p>
<note>
<p>Using XPath in global rules linked from HTML documents does not create an additional
@@ -1970,12 +1970,12 @@
queried using XPath, functionality supported by all major browsers.</p>
</note>
<p xml:id="html5-inline-global-rules">Inline global rules <ref target="#rfc2119"
- >MUST</ref> be specified inside <code>script</code> which has <code>type</code>
- attribute with the value <code>application/its+xml</code>. The <code>script</code>
- element itself <ref target="#rfc2119">SHOULD</ref> be child of <code>head</code>
- element. Comments <ref target="#rfc2119">MUST NOT</ref> be used inside global rules.
- Each <code>script</code> element <ref target="#rfc2119">MUST NOT</ref> contain more than
- one <gi>rules</gi> element.</p>
+ >MUST</ref> be specified inside a <code>script</code> element that has a
+ <code>type</code> attribute with the value <code>application/its+xml</code>. The
+ <code>script</code> element itself <ref target="#rfc2119">SHOULD</ref> be a child of
+ the <code>head</code> element. Comments <ref target="#rfc2119">MUST NOT</ref> be used
+ inside global rules. Each <code>script</code> element <ref target="#rfc2119">MUST
+ NOT</ref> contain more than one <gi>rules</gi> element.</p>
<note><p xml:id="note-html-rules-location">It is preferred to use external global rules
linked using the <code>link</code> element than to have global rules embedded in the
document.</p></note>
@@ -1996,27 +1996,29 @@
<list type="ordered">
<item>Implicit local selection in documents (<ref target="#html5-local-attributes">ITS
local attributes</ref> on a specific element)</item>
- <item><p>Global selections in documents (using mechanism of <ref
+ <item><p>Global selections in documents (using the mechanism of <ref
target="#html5-external-global-rules">external global rules</ref> or <ref
target="#html5-inline-global-rules">inline global rules</ref>), to be processed in
a document order, see <ptr type="specref" target="#selection-global"/> for
details.</p>
- <note><p>ITS does not define precedence related to rules defined or linked based on
+ <note>
+ <p>ITS does not define precedence related to rules defined or linked based on
non-ITS mechanisms (such as processing instructions for linking rules). Selection
- via inheritance takes precedence over default values, see below item.</p></note>
+ via inheritance takes precedence over default values (see below).</p>
+ </note>
</item>
<item>Selection via inherited values. This applies only to element nodes. The
inheritance rules are laid out in a dedicated <ref target="#datacategories-overview"
- >datacategory overview table</ref>, see column <quote>Inheritance for element
- nodes</quote>. Selection via inheritance takes precedence over default values, see
- below item.</item>
+ >datacategory overview table</ref> (see the column <quote>Inheritance for element
+ nodes). Selection via inheritance takes precedence over default values (see
+ below).</quote></item>
<item>Selections via defaults for data categories, see <ptr
target="#datacategories-defaults-etc" type="specref"/>.</item>
</list>
<p>In case of conflicts between global selections via multiple <ref
target="#selection-global">rules</ref> elements, the last rule has higher
precedence.</p>
- <p>The forehand mentioned <ptr target="#EX-translate-html5-global-1" type="exref"/>
+ <p><ptr target="#EX-translate-html5-global-1" type="exref"/>, previously discussed,
demonstrates the precedence: the <code>code</code> element with the <att>translate</att>
attribute set to yes has precedence over the global rule setting all <code>code</code>
elements as untranslatable.</p>
@@ -2027,7 +2029,7 @@
<head>Using ITS Markup in XHTML</head>
<p><emph>This section is normative.</emph></p>
<p>XHTML documents aimed at public consumption by Web browsers, including HTML5 documents in
- XHTML synatx, <ref target="#rfc2119">SHOULD</ref> use the syntax described in <ptr
+ XHTML syntax, <ref target="#rfc2119">SHOULD</ref> use the syntax described in <ptr
target="#html5-markup" type="specref"/> in order to adhere to <ref
target="http://www.w3.org/TR/html-design-principles/#dom-consistency">DOM Consistency
HTML Design Principle</ref>.</p>
@@ -2038,12 +2040,12 @@
target="examples/html5/EX-xhtml-markup-1.html" type="html5"/>
</exemplum>
<note>
- <p>Please note that this section defines how to use ITS in XHTML content which is directly
- served to Web browsers. Such XHTML is very often sent with a wrong media type and parsed
- as HTML not as XML in Web browsers. In such case it is more robust and safer to use
- HTML-like syntax for ITS metadata.</p>
+ <p>Please note that this section defines how to use ITS in XHTML content that is directly
+ served to Web browsers. Such XHTML is very often sent with an incorrect media type and
+ parsed as HTML rather than XML in Web browsers. In such case it is more robust and safer
+ to use HTML-like syntax for ITS metadata.</p>
<p>However when XHTML is not used as a delivery but rather as an exchange or storage
- format all XML features can be used in XHTML and it's advised to use XML syntax for ITS
+ format all XML features can be used in XHTML and it is advised to use XML syntax for ITS
metadata.</p>
</note>
</div>
Received on Saturday, 1 June 2013 15:43:14 UTC