- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 28 Jan 2006 00:33:29 +0000
- To: public-i18n-its@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2761 ------- Additional Comments From fsasaki@w3.org 2006-01-28 00:33 ------- (In reply to comment #4) > Not allowing selector in situ is certainly an interesting proposal. > > This would make things more difficult for any datacat applied to attributes, > but since we don't encourage translatable attribute, and this would affect > only the cases when we override a defined datacat this may not be to big of an > issue. > for a user of ITS, it would be more difficult in the sense that each time you want to express s.t. about a specific, singular attribute, you would need an <its:documentRule> element with at least two attributes: the data category attribute and the selector attribute. But the attributes would be necessary in the in situ application as well. And it would be no problem to express s.t. about attributes *in general* dislocated: <its:documentRule its:translate="yes" its:translateSelector="//img/@alt"/> for an ITS processor, I think it would make things slightly easier to have no in situ selector attributes, and the expressive power of selection would be the same.
Received on Saturday, 28 January 2006 00:33:38 UTC