What do you think of this data structure for specifying how to produce XML: 

[ tag_name, \%attr, $inner ]

[download]
where $inner is
  1. plain text - representing content
  2. an array ref - representing another tag(s)
This would not allow for mixed content. But for data-oriented XML production, that does not matter?

example

    <family name="Kawasaki">
        <father>Yasuhisa</father>
        <mother>Chizuko</mother>
        <children>
            <girl>Shiori</girl>
            <boy>Yusuke</boy>
            <boy>Kairi</boy>
        </children>
    </family>

[download]
[ family => { name => 'Kawasaki' },
  [
    [father => {} => 'Yasushisa' ],
    [mother => {} => 'Chizuko' ],
    [children
        [
          [girl => {} => 'Shiori'],
          [boy  => {} => 'Yasuke'],
          [boy  => {} => 'Kairi']
        ]
     ]
   ]
]

[download]

why another data to xml producer?

Here are the reasons I can think of:
  1. not easy/possible to specify when something is an attribute versus an element using XML::Simple. Ditto with XML::Smart
  2. cumbersome to specify exact ordering of XML with XML::TreePP
  3. data structure changes in XML::TreePP based on whether there are attributes or attributes and text as shown here

In reply to A data structure for XML generation by metaperl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.