[big-snip]
> > In all of those situations, I believe the desire was for the Source to > > override the default. So in each of your examples (numbered 1-5) the > > results are listed: > > > > 1. <a><b/></a> > > 2. <a><b/></a> > > 3. <a><b x="1"/></a> > > 4. <a><b x="1" y="2"/></a> > > 5. <a><b x="1" y="2"/></a> > > > > So the Default provides base values, and the Source will override those > > values when provided. > > Thats how I would expect it to behave but thats not how Stephen > expects it to behave :) Ouch! Actually, that is what I expect if your merging for the purpose of attribute resolution. If you merging for the purpose of contained element aggrigation that isn't what I expect. It is important to understand that these are two distinclty different policies. The aggregation case deals with progressive ADDITION of elements. > And I didn't even comment on the potential more painful example > > Source: <a><b x="1"/></a> > Default: <a><b/><a/><b x="2" y="2"/></a> > > Result == ? Syntax error! Can you rephrase the default declaration. Steve. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
