Thanks a lot for so many kind suggestions.

By the way, and if you don't care a little naïf Mediation here, while I started to use Twig, I thought it would be useful to the CPAN users a competition between the modules that eventually perform similar tasks. Although CPAN (somewhere) recommends the user should only submit modules which aims are not yet covered by other even accepted module, I think people tends by several reasons to bypass the procedure of sending suggestions to older authors. I think this is not bad, but an objective weighting method could do the job of choosing the better one easier.
Kwalitee cares only about - let’s say - formal requirements, or syntactic as opposed to semantic behaviors. The *.t framework only guarantees the module will not fail in your machine. So, we don’t have a real rating system. (If I’m totally wrong, please let me know).
A simplistic approach to such semantic competition between modules able to do the “same” job could be to make a bench mark for each module on the same tasks. Several input sizes could be used to accomplish a detailed description. Some kind of metadata like w3c OWL would need to be attached to the doc of the modules for making possible the automatic creation of input and scripts. Etc. What do you think?

In reply to Re: Choosing the best XML module for a toy system by fernandes
in thread Choosing the best XML module for a toy system by fernandes

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.