- From: Yves Savourel <ysavourel@translate.com>
- Date: Tue, 28 Mar 2006 13:56:25 -0700
- To: <public-i18n-its@w3.org>
Hi Felix, all, Looking at http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0301.html For tomorrow item #4 of the agenda. Here are some comments: > #About rubyRule: > ... > <its:rubyRule its:selector="//span[class='ruby']" > its:rubyBaseMap="span[class='rubyBase']" > its:rubyTextMap="span[class='rubyText']"/> Just a reminder: Don't forget the <rp> element that exists in the W3C ruby module. (And what about complex ruby constructs?) > #About langRule: The element langRule is used to express > that a given piece of content (selected by the attribute langMap) > is used to express language information as defined by RFC 3066 > or its successor. Example: > <its:langRule its:selector="//p" its:langMap="@mylangattribute"/> > ... > #About localeRule: The element localeRule is used to express that > a given piece of content (selected by the attribute localeMap) is > used to express locale information. Example: <its:localeRule > its:selector="//p" its:langMap="@mylocaleattribute"/>. Mmmm... I guess langMap and localeMap stay named like this while the other change to xyzPointer/PassThrough/Etc. One question: if the content of langMap is always an attribute, why the '@'? Is the value an XPath expression or the name of the equivalent attribute/element? Something tells me involving 'locale' before there is a clear consensus in the XML world on what is it and have a RFC3066-like reference for the values, is a bad idea. When you say "The value of @mylocaleattribute might be compliant to RFC 3066 bis, but this is not mandatory." then it means basically "use whatever value you want", and that makes it non-interoperable. I can understand <langRule> because it maps to XML/ITS-recommended way to specify language and there is value set define for it. But what is the use case for mapping a user-defined locale to ...nothing interoperable. Knowing the name of the attribute used for specifying the locale is not enough: one needs a defined set of values. To me, having localeMap may raise the false hope that ITS provides some kind of interoperable locale concept. Cheers, -yves
Received on Tuesday, 28 March 2006 20:56:39 UTC