- From: CVS User alommel <cvsmail@w3.org>
- Date: Fri, 30 Nov 2012 13:09:04 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv17659
Modified Files:
its20.odd
Log Message:
possible reflow prior to editing. No content change
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/30 11:30:07 1.285
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/30 13:09:04 1.286
@@ -19,12 +19,16 @@
<altlocs>
<loc href="its20.odd">ODD/XML document</loc>
<loc href="itstagset20.zip">self-contained zipped archive</loc>
- <loc href="diffs/diff-wd20120626-its10-20070403.html">XHTML Diff markup between publication 2012-06-26 and ITS 1.0
- Recommendation 2007-04-03</loc>
- <loc href="diffs/diff-wd20120731-wd20120626.html">XHTML Diff markup publication 2012-07-31 and publication 2012-06-26</loc>
- <loc href="diffs/diff-wd20120829-wd20120731.html">XHTML Diff markup publication 2012-08-29 and publication 2012-07-31</loc>
- <loc href="diffs/diff-wd20121023-wd20120829.html">XHTML Diff markup publication 2012-10-23 and publication 2012-08-29</loc>
- <loc href="diffs/diff-wd20121206-wd20121023.html">XHTML Diff markup publication 2012-12-06 and publication 2012-10-23</loc>
+ <loc href="diffs/diff-wd20120626-its10-20070403.html">XHTML Diff markup between publication
+ 2012-06-26 and ITS 1.0 Recommendation 2007-04-03</loc>
+ <loc href="diffs/diff-wd20120731-wd20120626.html">XHTML Diff markup publication 2012-07-31 and
+ publication 2012-06-26</loc>
+ <loc href="diffs/diff-wd20120829-wd20120731.html">XHTML Diff markup publication 2012-08-29 and
+ publication 2012-07-31</loc>
+ <loc href="diffs/diff-wd20121023-wd20120829.html">XHTML Diff markup publication 2012-10-23 and
+ publication 2012-08-29</loc>
+ <loc href="diffs/diff-wd20121206-wd20121023.html">XHTML Diff markup publication 2012-12-06 and
+ publication 2012-10-23</loc>
</altlocs>
<prevlocs>
<loc href="http://www.w3.org/TR/2012/WD-its20-20121023/">
@@ -87,12 +91,17 @@
<p>This document was published by the <loc
href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
- Group</loc> as a Last Call Working Draft. The Working Group expects to advance this Working
- Draft to Recommendation status (see <loc
+ Group</loc> as a Last Call Working Draft. The Working Group expects to advance this
+ Working Draft to Recommendation status (see <loc
href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
maturity levels</loc>). The Last Call period ends 10 January 2013.</p>
-<p>The normative sections of this document (from <specref ref="notation-terminology"/> to <specref ref="datacategory-description"/> and <specref ref="normative-references"/> to <specref ref="its-schemas"/>) are stable. The other, non-normative sections contain only explanatory material and will be updated in a later working draft. Hence, the Working Group especially encourages feedback on the normative sections. The goal is to move out of last call without any substantive changes to these sections.</p>
+ <p>The normative sections of this document (from <specref ref="notation-terminology"/> to
+ <specref ref="datacategory-description"/> and <specref ref="normative-references"/> to
+ <specref ref="its-schemas"/>) are stable. The other, non-normative sections contain only
+ explanatory material and will be updated in a later working draft. Hence, the Working Group
+ especially encourages feedback on the normative sections. The goal is to move out of last
+ call without any substantive changes to these sections.</p>
<p>To give feedback send your comments to <loc
href="mailto:public-multilingualweb-lt-comments@w3.org"
@@ -100,10 +109,10 @@
WD" in the subject line of your email. The <loc
href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives
for this list</loc> are publicly available. See also <loc
- href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed
- within the Working Group</loc> and the <loc href="#changelog-since-20121023">list of changes since
- the previous publication</loc>.</p>
-
+ href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed
+ within the Working Group</loc> and the <loc href="#changelog-since-20121023">list of
+ changes since the previous publication</loc>.</p>
+
<p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a
draft document and may be updated, replaced or obsoleted by other documents at any time. It
is inappropriate to cite this document as other than work in progress.</p>
@@ -182,8 +191,8 @@
<p>ITS 2.0 also adds the following principles and features not found in ITS 1.0:</p>
<list type="unorderd">
<item>ITS 2.0 data categories are intended to be format neutral, with support for XML,
- HTML, and NIF: a data category implementation only needs to support a single
- content format mapping in order to support a claim of ITS 2.0 conformance.</item>
+ HTML, and NIF: a data category implementation only needs to support a single content
+ format mapping in order to support a claim of ITS 2.0 conformance.</item>
<item>ITS 2.0 provides algorithms to generate NIF out of HTML or XML with ITS 2.0
metadata.</item>
<item>A global implementation of ITS 2.0 requires at least the XPath version 1.0.
@@ -191,7 +200,8 @@
expressed via a dedicated <ref target="#queryLanguage">queryLanguage</ref>
attribute.</item>
</list>
- <p xml:id="its20-new-data-categories">The new data categories included in ITS 2.0 are:</p>
+ <p xml:id="its20-new-data-categories">The new data categories included in ITS 2.0
+ are:</p>
<list type="unorderd">
<item><ref target="#domain">Domain</ref></item>
<item><ref target="#Disambiguation">Disambiguation</ref></item>
@@ -329,7 +339,13 @@
manner (see <ref target="#selection-global">global, rule-based approach</ref>). This
global work, however, may fall to information architects, rather than the content
producers themselves.</p>
- <p xml:id="cms-plain-text-fields">Content producers often work with content management systems (CMS). In various CMS, some of the CMS fields only allow to store plain text. For these fields, the current ITS 2.0 data categories can only be applied globally and not with local attributes. This issue should be addressed in another way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields if possible, or using an extra field which allows HTML input and save the plain text of this extra field in the plain text field.</p>
+ <p xml:id="cms-plain-text-fields">Content producers often work with content management
+ systems (CMS). In various CMS, some of the CMS fields only allow to store plain
+ text. For these fields, the current ITS 2.0 data categories can only be applied
+ globally and not with local attributes. This issue should be addressed in another
+ way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields
+ if possible, or using an extra field which allows HTML input and save the plain text
+ of this extra field in the plain text field.</p>
</div>
<div xml:id="users_machine-translation">
<head>Machine Translation Systems</head>
@@ -396,8 +412,8 @@
</list>
<exemplum xml:id="EX-ways-to-use-its-1">
<head>Use of ITS by content author</head>
- <p>The <code>its:translate="no"</code> attributes indicate that the <code>path</code> and
- the <code>cmd</code> elements should not be translated.</p>
+ <p>The <code>its:translate="no"</code> attributes indicate that the <code>path</code>
+ and the <code>cmd</code> elements should not be translated.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-ways-to-use-its-1.xml"/>
</exemplum>
@@ -458,8 +474,8 @@
<p>The first two approaches above can be likened to the use of CSS in <ptr
target="#xhtml10" type="bibref"/>. Using a <code>style</code> attribute, an XHTML
content author may assign a color to a particular paragraph. That author could also
- have used the <code>style</code> element at the top of the page to say that all paragraphs
- of a particular class or in a particular context would be colored red.</p>
+ have used the <code>style</code> element at the top of the page to say that all
+ paragraphs of a particular class or in a particular context would be colored red.</p>
</div>
</div>
@@ -468,8 +484,7 @@
<p>ITS 2.0 adds support for usage in HTML. In HTML, ITS local selection is realized via
dedicated, <ref target="#html5-local-attributes">data category specific
attributes</ref>.</p>
- <note type="ed">Add example of HTML with local attributes for illustration
- purposes</note>
+ <note type="ed">Add example of HTML with local attributes for illustration purposes</note>
<p>For the so-called “<ref target="#basic-concepts-selection-global">global
approach</ref>” in HTML, this specification defines a link type for referring to files
with global rules in <ptr target="#html5-global-rules" type="specref"/>.</p>
@@ -537,8 +552,8 @@
on the other hand, need an efficient way to manage translations of large document sets
based on the same schema. These needs could by realized by a specification of defaults
for the <ref target="#trans-datacat">Translate</ref> data category along with exceptions
- to those defaults (e.g. all <code>p</code> elements should be translated, but not <code>p</code>
- elements inside of an <code>index</code> element).</p>
+ to those defaults (e.g. all <code>p</code> elements should be translated, but not
+ <code>p</code> elements inside of an <code>index</code> element).</p>
<p>To meet these requirements this specification introduces mechanisms that add ITS
information to XML documents, see <ptr target="#its-processing" type="specref"/>. These
mechanisms also provide a means for specifying ITS information for attributes (a task
@@ -614,9 +629,9 @@
<p>The document in <ptr target="#EX-basic-concepts-1" type="exref"/> shows how a content
author may use the ITS <att type="class">translate</att> attribute to indicate that
- all content inside the <code>author</code> element should be protected from translation.
- Translation tools that are aware of the meaning of this attribute can then screen the
- relevant content from the translation process.</p>
+ all content inside the <code>author</code> element should be protected from
+ translation. Translation tools that are aware of the meaning of this attribute can
+ then screen the relevant content from the translation process.</p>
<exemplum xml:id="EX-basic-concepts-1">
<head>ITS markup on elements in an XML document (local approach) </head>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
@@ -652,10 +667,10 @@
<p>myElement/descendant-or-self::*/@*</p>
<p>Unfortunately, values like this cause trouble when they are used in XSLT-based
processing of ITS where the values of the ITS <att>selector</att> attributes are
- used as values of <code>match</code> attributes of XSLT templates. The reason for this
- is the following: <code>match</code> attributes may only contain a restriction/subset
- of XPath expressions, so-called <ref target="http://www.w3.org/TR/xslt#patterns"
- >patterns</ref>.</p>
+ used as values of <code>match</code> attributes of XSLT templates. The reason for
+ this is the following: <code>match</code> attributes may only contain a
+ restriction/subset of XPath expressions, so-called <ref
+ target="http://www.w3.org/TR/xslt#patterns">patterns</ref>.</p>
<p>Basically the following restrictions hold for patterns: </p>
<list>
<item>only axes "child" or "attribute" allowed</item>
@@ -694,7 +709,8 @@
local markup throughout a document (or documents, if the <gi>rules</gi> element is
stored as an external entity)</item>
<item>ITS data categories can designate attribute values as well as elements.</item>
- <item>It is possible to associate ITS markup with existing markup (for example the <code>term</code> element in DITA)</item>
+ <item>It is possible to associate ITS markup with existing markup (for example the
+ <code>term</code> element in DITA)</item>
</list>
@@ -746,13 +762,13 @@
<p>The document in <ptr target="#EX-basic-concepts-3" type="exref"/> shows how inheritance
and overriding work for the <ref target="#trans-datacat">Translate</ref> data category.
By default elements are translatable. Here, the <gi>translateRule</gi> element declared
- in the header overrides the default for the <code>head</code> element inside <code>text</code>
- and for all its children. Because the <code>title</code> element is actually translatable,
- the global rule needs to be overridden by a local <code>its:translate="yes"</code>. Note
- that the global rule is processed first, regardless of its position inside the document.
- In the main body of the document, the default applies, and here it is
- <code>its:translate="no"</code> that is used to set “faux pas” as
- non-translatable.</p>
+ in the header overrides the default for the <code>head</code> element inside
+ <code>text</code> and for all its children. Because the <code>title</code> element is
+ actually translatable, the global rule needs to be overridden by a local
+ <code>its:translate="yes"</code>. Note that the global rule is processed first,
+ regardless of its position inside the document. In the main body of the document, the
+ default applies, and here it is <code>its:translate="no"</code> that is used to set
+ “faux pas” as non-translatable.</p>
<exemplum xml:id="EX-basic-concepts-3">
<head>Overriding and Inheritance</head>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
@@ -811,8 +827,8 @@
<p><termStruct term="data category" xml:id="t002">ITS defines <term>data category</term>
as an abstract concept for a particular type of information for internationalization
and localization of XML schemas and documents.</termStruct> 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>
+ 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>
<list type="unordered">
<item>the prose description, see <ptr target="#datacategory-description" type="specref"
@@ -825,7 +841,7 @@
type="specref"/>
</item>
</list>
- <exemplum >
+ <exemplum>
<head>A data category and its implementation</head>
<p>The <ref target="#trans-datacat">Translate</ref> data category conveys information as
to whether a piece of content should be translated or not.</p>
@@ -853,13 +869,13 @@
<note>
<p xml:id="note-object-selection">The selection of the ITS data categories applies to
textual values contained within element or attribute nodes. In some cases these nodes
- form pointers to other resources; a well-known example is the <code>src</code> attribute
- on the <code>img</code> element in HTML. The ITS <ref target="#trans-datacat"
- >Translate</ref> data category applies to the text of the pointer itself, not the
- object to which it points. Thus in the following example, the translation information
- specified via the <gi>translateRule</gi> element applies to the filename
- <val>instructions.jpg</val>, and is not an instruction to open the graphic and
- change the words therein.</p>
+ form pointers to other resources; a well-known example is the <code>src</code>
+ attribute on the <code>img</code> element in HTML. The ITS <ref
+ target="#trans-datacat">Translate</ref> data category applies to the text of the
+ pointer itself, not the object to which it points. Thus in the following example, the
+ translation information specified via the <gi>translateRule</gi> element applies to
+ the filename <val>instructions.jpg</val>, and is not an instruction to open the
+ graphic and change the words therein.</p>
<exemplum xml:id="EX-notation-terminology-1">
<head>Selecting the text of a pointer to an external object</head>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
@@ -884,13 +900,16 @@
</div>
<div xml:id="iri-usage">
<head>Usage of Internationalized Resource Identifiers in ITS</head>
- <p>All attributes that have the type <code>anyURI</code> in the normative RELAX NG schema in <ptr target="#its-schemas" type="specref"/> <ref
- target="#rfc-keywords">MUST</ref> allow the usage of Internationalized Resource
+ <p>All attributes that have the type <code>anyURI</code> in the normative RELAX NG schema
+ in <ptr target="#its-schemas" type="specref"/>
+ <ref target="#rfc-keywords">MUST</ref> allow the usage of Internationalized Resource
Identifiers (IRIs, <ptr target="#rfc3987" type="bibref"/> or its successor) to ease the
adoption of ITS in international application scenarios.</p>
</div>
- <div xml:id="def-html"><head>The Term HTML</head>
- <p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor <ptr target="#html5" type="bibref"/>.</p>
+ <div xml:id="def-html">
+ <head>The Term HTML</head>
+ <p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor
+ <ptr target="#html5" type="bibref"/>.</p>
</div>
</div>
<div xml:id="conformance">
@@ -943,8 +962,8 @@
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>
+ 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
@@ -977,8 +996,8 @@
<div xml:id="conformance-product-processing-expectations">
<head>Conformance Type 2: The Processing Expectations for ITS Markup</head>
<p><emph>Description:</emph> Processors need to compute the ITS information that pertains
- to a node in an XML 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 XML 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="#selection-precedence">precedence</ref>. The
@@ -1030,12 +1049,12 @@
<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
- documents.</p></item>
+ 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 algorithm described in <ptr
- target="#conversion-to-nif" type="specref"/>.</p></item>
+ target="#rfc-keywords">MAY</ref> convert an XML document to NIF, using the
+ algorithm described in <ptr target="#conversion-to-nif" type="specref"/>.</p></item>
</list>
<note><p>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
@@ -1046,27 +1065,27 @@
<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, whether they support processing
- of XML. If the implementation provides the conversion to NIF (see
- conformance clause <ref target="#its-conformance-2-4">2-4</ref>), this <ref
- target="#rfc-keywords">MUST</ref> be stated.</p>
+ of XML. If the implementation provides the conversion to NIF (see conformance clause
+ <ref target="#its-conformance-2-4">2-4</ref>), this <ref target="#rfc-keywords"
+ >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). 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>
+ 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). 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>
</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 a 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"
@@ -1077,7 +1096,8 @@
target="#datacategory-description" type="specref"/> have <ref
target="#datacategories-defaults-etc">defaults / inheritance / overriding
characteristics</ref>, and allow for using ITS markup in various positions (<ref
- target="#html5-local-attributes">local</ref>, <ref target="#html5-external-global-rules">external global</ref> and <ref
+ target="#html5-local-attributes">local</ref>, <ref
+ target="#html5-external-global-rules">external global</ref> and <ref
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
@@ -1146,8 +1166,9 @@
<emph>This section is normative.</emph>
</p>
-<note><p>Additional definitions about processing of HTML are given in <ptr type="specref" target="#html5-markup"/>.</p></note>
-
+ <note><p>Additional definitions about processing of HTML are given in <ptr type="specref"
+ target="#html5-markup"/>.</p></note>
+
<div xml:id="its-version-attribute">
<head>Indicating the Version of ITS</head>
@@ -1173,7 +1194,8 @@
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> or <gi>ruby</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> or <gi>ruby</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>
@@ -1220,8 +1242,8 @@
<div xml:id="selection-local">
<head>Local Selection in an XML Document</head>
<p>Local selection in XML documents is realized with <ref target="#local-attributes">ITS
- local attributes</ref> or the <gi>span</gi> element.
- <gi>span</gi> serves just as a carrier for the local ITS attributes.</p>
+ local attributes</ref> or the <gi>span</gi> element. <gi>span</gi> serves just as a
+ carrier for the local ITS attributes.</p>
<p>The data category determines what is being selected. The necessary data category
specific defaults are described in <ptr target="#datacategories-defaults-etc"
@@ -1233,8 +1255,8 @@
<p>By default the content of all elements in a document is translatable. The attribute
<code>its:translate="no"</code> in the <code>head</code> element means that the
content of this element, including child elements, should not be translated. The
- attribute <code>its:translate="yes"</code> in the <code>title</code> element means that
- the content of this element, should be translated (overriding the
+ attribute <code>its:translate="yes"</code> in the <code>title</code> element means
+ that the content of this element, should be translated (overriding the
<code>its:translate="no"</code> in <code>head</code>). Attribute values of the
selected elements or their children are not affected by local <att type="class"
>translate</att> attributes. By default they are not translatable.</p>
@@ -1248,11 +1270,11 @@
</exemplum>
<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
[1992 lines skipped]
Received on Friday, 30 November 2012 13:09:09 UTC