W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2006

Re: locInfo

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 27 Jan 2006 13:13:33 +0900
To: "Yves Savourel" <yves@opentag.com>, public-i18n-its@w3.org
Message-ID: <op.s30rcvm6x1753t@ibm-60d333fc0ec>

Hi Yves,

On Fri, 27 Jan 2006 09:46:17 +0900, Yves Savourel <yves@opentag.com> wrote:

>
> Hi Felix, and all,
>
> Some notes the locInfo datacat:
>
> - locInfoType is defined as xs:token in the XSD for ITS, but as CDATA in  
> the DTD. Shouldn't we enumerate the values in the DTD?

That would be a possibiliyt. We discussed at some point to have two  
attributes instead of one: "@locInfoDesc" and "@lofInfoAlert". In that  
way, we would not need "type". What do you think?

>
> - If locInfoType is not present, do we have a default value for it? If  
> so, is it description or alert?

The solution with two attributes would solve that problem

>
> - In the description of datacat table (section 4): The default selection  
> in instance document for locInfo is: "Textual content of
> element, including content of child elements, but excluding attributes."  
> This imply that every single inline code within a paragraph
> that has a locInfo should also have the locInfo applied, is this making  
> sense?
> I can see the inheritence interest in some case (for non-inline  
> elements), but if the ITS processor uses some "tree-decoration"
> method to propagate the note, this can end up in a huge amount of extra  
> nodes not really necessary. Mmmm... I guess it's a processor
> problem...

Did you see what I wrote at  
http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0051.html  
about the inheritance problem with @locInfo? The general question is: how  
to handle inheritance if we don't have *alternative* values, that is s.t.  
different from its:translate, its:dir etc.
We *could* leave that to the implemenation, which could decide if  
inheritance should be turned of or not. We could also add a new feature to  
ITS, e.g. an @inheritance attribute with values "yes" or "no". I'm not  
sure what is more feasible.

Cheers,
Felix
Received on Friday, 27 January 2006 04:13:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC