- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Sat, 11 Aug 2012 14:29:29 -0600
- To: "'Felix Sasaki'" <fsasaki@w3.org>
- CC: <public-multilingualweb-lt@w3.org>
Hi Felix, >> The table entry looks ok, except possibly for Overriding: >> I think it should be Yes. > > Shouldn't it be rather not applicable? Also, the inheritance > should be none, I think. Otherwise, for an input like this > ... > We have an output like this: > <node path="/doc/msg[1]/desc[1]" outputType="new-value-global"> > <output>settingsMissing_d</output> > </node> > <node path="/doc/msg[1]/desc[1]/em[1]" outputType="inherited"> > <output>settingsMissing_d</output> > </node> > That is, the id inherits from "desc" to the child element "em". > > So we should probably change > "The information applies to the textual content of the element, > including child elements, but excluding attributes." > to > "There is no inheritance." > What do you think? Mmm... I guess I need to refresher on our two concepts of inheritance and overriding. For Overriding: If I have: its:idValueRule selector="//text" idValue="concat(../@name, '_t')"/> its:idValueRule selector="//text/quote" idValue="../@id"/> Shouldn't the second rule override the first one? I think it should. For inheritance: I think I see what you mean: the ID is only valid for the whole content and cannot be applied *just* to a specific child element. But at the same time it's true that the information does apply to the child elements. So the original statement is not wrong, is it? But I'm probably missing something. Cheers, -ys
Received on Saturday, 11 August 2012 20:30:01 UTC