Explanation of relation between HTML and ITS 2.0

Hi all,

I have written some text to explain the relation between HTLM and ITS 
2.0. The aim is to replace the content of section 1.4 with that text.

Please provide comments by Monday evening. I will then make the replacement.

Best,

Felix

================
1.4 Usage in HTML
For applying ITS 2.0 data categories to HTML, four aspects need to be 
taken into account: linkage of global rules, the HTML specific approach 
to insert local ITS 2.0 markup into HTML, the relation between HTML 
markup and ITS 2.0 data categories, and the version of HTML.

1.4.1 Linkage of global rules
For the so-called “global approach” in HTML, this specification defines 
a link type for referring to files with global rules in Section 6.2: 
Global rules.
[Ed. Note: add here example 8 and example 9]

1.4.2 Approach to insert local ITS 2.0 markup into HTML
In HTML, ITS local markup is realized with a dedicated prefix its-*. The 
mapping of the XML specific ITS attributes to their HTML its-* 
counterparts is defined in section 6.1.

1.4.3 Relation between HTML markup and ITS 2.0 data categories
There are three ITS 2.0 data categories, which have direct counterparts 
in HTML markup. For theses data categories, ITS 2.0 defines specific 
behaviour.
• For the “Language Information” data category there is the HTML “lang” 
attribute or in XHTML the “xml:lang” attribute. These attributes act as 
local markup for the “Language Information” data category in HTML and 
take precedence over language information conveyed via a global langRule.
• For the “Id Value” data category there is the HTML “id” or in XHTML 
the “xml:id” attribute. These attributes act as local markup for the “Id 
Value” data category in HTML and take precedence over id information 
conveyed via a global idValueRule.
• For the “Elements within Text” data category there is the set of HTML 
elements defined as inline attributes (tbd: add link). In the absence of 
“Elements within Text” local markup or global rules selecting the 
element in question, by default these elements are interpreted as 
withinText=”yes”.
The “Translate” data category has a counterpart in HTML5: the HTML5s 
“translate” attribute. The definition of that attribute is similar, but 
not identical to ITS 2.0, in terms of defaults and the relation between 
attribute and elements translatability. Also, as of writing this 
document, the definition of the “translate” attribute in HTML5 is not 
stable. Users of ITS 2.0 are strongly encouraged to set “Translate” 
behaviour in HTML5 explicitly via global rules, and to process local 
“translate” attributes in HTML5 with dedicated ITS 2.0 processors, to 
avoid unexpected behaviour.

Example 10 (number tbc): The “Language Information, “Id Value”, 
“Elements within Text” and “Translate” ITS 2.0 data categories used with 
HTML native markup. The “html” element is interpreted to convey the 
“Language Information” value “en”. The “p” element is interpreted to 
convey the “Id Value” of “p1”. The “em” element is interpreted to be 
withinText=”yes”.
<!DOCTYPE html>
<html lang=en>
<head>
<meta charset=utf-8>
<title>HTML native markup expressing four ITS 2.0 data categories</title>
</head>
<body>
<p id="p1">This is a <em motherboard</em>.</p>
</body>
</html>

Some HTLM markup has similar, but not always identical roles for 
specific ITS 2.0 data categories. For example, the HTML “dfn” element 
can be used to identify a term in the sense of the “Terminology” data 
category. But this is not always the case and it depends on the 
intentions of the content authors. To accomodate this situation, users 
of ITS 2.0 are encouraged to specifiy the association of existing HTML 
markup with a dedicated global rules file. For an example see (link to 
XML i18n BP document example for XHTML rules).

1.4.4 Version of HTML
ITS 2.0 does not define how to use ITS in HTML versions prior version 5. 
Users are encouraged to migrate their content to HTML5 or XHTML. While 
it is possible to use its-* attributes introduced for HTML5 in older 
versions of HTML (such as 3.2 or 4.01) and pages using these attributes 
will work without any problems, its-* attributes will be marked as 
invalid in validators.
================

Received on Friday, 26 April 2013 09:24:42 UTC