Cart
[Home] [By Thread] [By Date] [Recent Entries]
At 10:10 AM 09/22/99 +1000, Marcus Carr wrote: >The two options that come to mind are either: > ><chapter> > <security>u</security> > <title>Wheeled Armoured Toys</title> > <para0> > <security>u</security> > <para>WATs are your friend...</para> > <security>u</security> (I think this line is superfluous...) > </para0> ></chapter> > >... which requires the evaluation of a child element before the >application is able to >understand how to deal with an elements such as para0 or para, (presumably >the values are >inherited) Whether you evaluate the security level first because it's an attribute or whether you evaluate it first because it's the first child element, you're still going to evaluate it before you evaluate the (other) child elements. Why/how is it worse to deal with it first as a child element rather than dealing with it first as an attribute? -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Mark Nutter, <mnutter@f...> Internet Applications Developer FORE Systems Some people are atheists 'til the day they die. xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
