The __DATA__ method seems to definitely be the right way here (w/purely static string data), but it in the interest of plugging a module i find handy (and preparing for more complicated scenarios, keep in mind something like this should work as well, using IO::Scalar: 
my $data = <<EOF;
<?xml version='1.0' standalone='yes'?>
<RULE output_format="pdf" lsog_version="lsog5">
  <SERVICE_REQUEST>
    <SOMETAG min_length="25" max_length="60">Some value</SOMETAG>
    <ANOTHER_TAG min_length="0" max_length="8">another value</ANOTHER_
+TAG>
  </SERVICE_REQUEST>
</RULE>
EOF
use IO::Scalar;
my $SH = new IO::Scalar \$data;
my $template = $xs->XMLin( $SH );

[download]

In reply to Re: Inline XML by davidrw
in thread Inline XML by heathen

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.