in reply to (jeffa) Re: Picking an XML Module
in thread Picking an XML Module

First off, i really think you should change the structure of your XML to something like: def.xml

Why? Why would you pervert a perfectly logical, not to mention practical, document structure, in order for your code to be easier to write? The original format makes sense, why add extra tags everywhere to avoid having to deal with mixed content? Mixed content exists, it's there for a good reason: that's how you write documents.

What happens if you have more than one definition in the section? Would you have this:

<part id="1">
      <info>infoinfostuffhere</info>
      <def word="someword">some definition of the word</def>
      <extra>more info and notes</extra>
      <extradef word="someword">some definition of an other word</extr
+adef>
      <doubleextra>even more info and notes</doubleextra>
   </part>

[download]

I don't think it would make sense either!

Replies are listed 'Best First'.
(jeffa) 3Re: Picking an XML Module
by jeffa (Bishop) on Aug 03, 2003 at 16:47 UTC
    Because i am still a newbie at XML. :P

    Seriously, because i didn't know any better ... i see now why the mixed content is OK to have. ninja-joe ... my apologies. If you do take my advice, feel free to ask more questions ... i personally find XSLT and XPath to be somewhat hard to work with until you get the hang of them. While i was developing hacking out the above code, i found it 'easier' (falsely, of course) to wrap everything instead of dealing with mixed content. mirod++ yet again. ;)

    jeffa

    L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
[reply]

In Section Seekers of Perl Wisdom