RE: ISSUE-118: HTML ITS default behaviour - starting point, ACTION-452 => idValue

Hi Fredrik,

The rule is in the defaults (and the strict) fprm because that's how ITSEngine is getting its defaults behavior currently.
Directionality is also set that way.
(in other words: currently we don't hard-code all the default. Some of them are done through the global rules.


-----Original Message-----
From: Fredrik Liden [] 
Sent: Wednesday, February 27, 2013 11:14 AM
To: Yves Savourel;
Subject: RE: ISSUE-118: HTML ITS default behaviour - starting point, ACTION-452 => idValue

Hi Yves, all,

I'm wondering about idValue. Is this rule required for html id? The test files seems to have the rule but reading the spec, to me, it reads as not required.
I was searching the mailing list and it coincidentally I found that I had asked the same question back in November.


"The recommended way to specify a unique identifier is to use xml:id or id in HTML (See the best practice “Defining markup for unique identifiers” from [XML i18n BP]). The idValueRule element is intended only as a fall-back mechanism for documents where unique identifiers are available with another construct."

* The Id Value data category only provides for rules to be expressed at a global level. Locally, users are able to use xml:id (which is defined by XML) or id in HTML, or an attribute specific to the format in question (as in Example 73).

*Applying the Id Value data category to xml:id (in XML) or id (in HTML) attributes in global rules is not necessary, since these attributes are the recommended way to specify an identifier.

All those three paragraphs seem to indicate that the rule is not needed or am I missing something? Fyi, there's no html example with id on the spec page.


-----Original Message-----
From: Yves Savourel 
Sent: Wednesday, February 27, 2013 5:50 AM
Subject: ISSUE-118: HTML ITS default behaviour - starting point, ACTION-452

Hi everyone,

Attached and copied below is the set of global rules corresponding to what we think would be a start for the defaults.
This is likely not covering all that needs to be covered.
And obviously some of these are likely controversial.

The wiki page for listing the defaults is here:


<?xml version="1.0" encoding="UTF-8"?>
<its:rules xmlns:its="" version="2.0"
 <!-- Inline elements -->
 <its:withinTextRule withinText="yes"
  selector="//h:abbr | //h:acronym | //h:br | //h:cite | //h:code | //h:dfn
  | //h:kbd | //h:q | //h:samp | //h:span | //h:strong | //h:var | //h:b | //h:em
  | //h:big | //h:hr | //h:i | //h:small | //h:sub | //h:sup | //h:tt | //h:del
  | //h:ins | //h:bdo | //h:img | //h:a | //h:font | //h:center | //h:s | //h:strike
  | //h:u | //h:isindex" />
 <!-- Non-translatable elements -->
 <its:translateRule selector="//h:script|//h:style" translate="no"/>
 <its:translateRule selector="//h:del" translate="no"/>  <its:translateRule selector="//h:del/descendant-or-self::*/@*" translate="no"/>
 <!-- Translatable attribute -->
 <its:translateRule selector="//h:*/@abbr|//h:*/@alt|//h:*/@prompt|//h:*/@standby|//h:*/@summary|//h:*/@title" translate="yes"/>
 <its:translateRule selector="//h:meta[@name='keywords']/@content" translate="yes"/>  <its:translateRule selector="//h:meta[@name='description']/@content" translate="yes"/>
 <!-- Attributes for the input element -->  <its:translateRule selector="//h:input/@value" translate="yes"/>  <its:translateRule selector="//h:input[@type='hidden']/@value" translate="no"/>
 <!-- Bidirectional information. Note: No direct support for 'auto' value -->  <its:dirRule selector="//h:*[@dir='ltr']" dir="ltr"/>  <its:dirRule selector="//h:*[@dir='rtl']" dir="rtl"/>  <its:dirRule selector="//h:bdo[@dir='ltr']" dir="lro"/>  <its:dirRule selector="//h:bdo[@dir='rtl']" dir="rlo"/>

 <!-- Note: dfn and dt don't match exactly the Terminology data category -->
 <!-- Id Value -->
 <its:idValueRule selector="//h:*[@id]" idValue="@id"/>
 <!-- Note: Preserve space is not handled by ITS -->
 <!-- Domain -->
 <its:domainRule selector="/h:html"
  domainPointer="/h:html/h:head/h:meta[@name='dcterms.subject' or @name='keywords']/@content"/>


Received on Wednesday, 27 February 2013 18:29:19 UTC