This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: need help explaining one data structure over another


I guess I am just trying to figure out why DocBook went to such trouble to
have a whole bunch of index terms -- they must have had some reason for
using primary, secondary, indexdiv, etc., right?

> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Hunsberger,
> Peter
> Sent: Monday, August 05, 2002 9:57 AM
> To: 'xsl-list@lists.mulberrytech.com'
> Subject: RE: [xsl] need help explaining one data structure over another
>
>
>
> > Help me out [...] an please give me [...] a good argument for
> why system 2
> > is advantageous over system 1.
>
> Sorry, I'm going to also vote for system 1.  Having done a lot of generic
> XSLT I definitely prefer an XML input stream that a) does not make any
> assumptions about how it will be processed; and b) uses XML structure to
> indicate hierarchy and not element names.
>
> In your case, argument d) would seem to be particularly relevant; you've
> already got a perfectly reasonable way to indicate the
> relationship of each
> item to each other (the XML hierarchy) why would you also want to
> invent an
> artificial naming convention to duplicate the same information?
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]