Re: Inheritence and Overriding (Was RE: Sanity check)

Yves Savourel wrote:
> Hi Felix, all,
> 
>>> So it seems logical that any global translate rule on <code> should be 
>>> overriden by the local its:translate on its parent element.
>> I would agree with Sebastian that this should not be the case. 
>> Take a look at CSS: a global rule like em { color: blue ; } is 
>> overridden by <em style ="color: blue;"> , but it is for the <em> 
>> element *not* overridden by a local rule like <p style ="color: blue;"> 
>> ...<em> ...
> 
> I need to think more about this...

Just as an example, here is an CSS example (bad HTML, don't look at it)
which creates the result:

<html>
<head>
<title>ITS inheritance</title>
<style type="text/css">
em { color: blue;}</style>
</head>
<body>
<h1>Umlaute</h1>
<p style="color:
red;"><em>&auml;</em>&uuml;&ouml;&Auml;&Uuml;&Uuml;&szlig;</p>
<p>&#x30A2;</p>
</body>
</html>

> But regardless the "right" interpretation we need to make it much clearer in the specification.

agree.

> 
> 
>> actually http://www.w3.org/TR/2006/WD-its-20060518/#selection-precedence
>> is not clear about this:
>> [[1. Implicit local selection in documents (ITS local attributes on a specific element)
>>   2. Global selections in documents (using a rules element)
>>   3. Global selections in an external file (using a rules element), 
>> linked via the XLink href attribute or a different mechanism
>>   4. Selections via defaults for data categories, see Section 6.1:
>> Position and Default Selections of Data Categories]] this list does not 
>> talk about inherited values.
> 
> By the way, I'm seeing something wrong in this list I didn't noticed before: #3 includes linked rules, I would think they should be
> in #2 because we treat they are processed when we go through the embedded rules no? That is there is no difference between an
> embedded its:rules that has the rules inside <its:rules> or one that has the same rules in a linked file. (And obviously, if an
> embedded its:rules has both, the linked rules are processed first).

yes, the example at
http://www.w3.org/TR/2006/CR-its-20061102/#link-external-rules is also
like that. But I read the list 1-4 also like that: 2 has higher
precedence than 3, so 3 (the external rules) are processed first ...

Cheer,

Felix

> 
> The way #3 and #2 are described here it looks like we have to process the external rules, then the linked rules, then the embedded
> rules, so if you have this:
> 
> <head>
>  <its:rules>
>   <some rules...>
>  </its:rules>
>  <its:rules xlink:href="file.its"/>
> </head>
> 
> The content of file.its would be treated before <some rules...> while I would expect the reverse.
> 
> Cheers,
> -yves
> 
>

Received on Monday, 4 December 2006 02:45:07 UTC