Re: Term="yes|no"

Hi Yves,

Sorry for being late in this discussion. I have some concerns in this
change:

- It disconnects the global usage of the terminology data category with
the local one. In the latter, we have only term="yes".
- It introduces a new functionality for global rules of overriding a
"this is a term" rule, which again is not available locally.
- I think the comparison to xml:lang regarding overrides, which Martin
introduced, is not appropriate, since xml:lang is only used locally.
- You wrote "One should be able to override a previous rule that says a
given element is a term.", but I'm not sure if this is absolutely
necessary. Translatability, directionality and elements within text use
overrides, but the other data categories don't.

I'm also concerned that this change, esp. the disconnection between
global and local, is rather substantive and not appropriate during last
call.

Again, sorry for being late and my concerns.

Felix

Yves Savourel wrote:
> Hi all,
> 
> I have an action item to list the changes needed in the WD to add term="yes|no"
> http://www.w3.org/2006/08/23-i18nits-minutes.html#action01
> 
> Here they are:
> 
> A) Add term="yes" in <its:termRule> in the examples 12, 13, 15, 17, 19 and 27.
> 
> 
> B) In section 6.4.2: "is realized with a termRule element with a mandatory selector attribute."
> 
> Would become:
> 
> "is realized with a termRule element with a mandatory selector attribute and a mandatory term attribute with a value 'yes' or 'no'."
> 
> (or whatever more consistent formulation matches the one Christian has come up with during the last edit of the data cat
> definitions)
> 
> 
> C) In section 6.4.3: The addition of term="yes|no" in the termRule's attributes list ODD definition.
> 
> 
> I think that is all.
> -yves
> 
> 
> 
> 
>