Another method is to form queries targeting the item of interest, parse, then use "findvalue":
my $xquery = '//metadata/audience/@name';# find the first <audience n +ame="xyz"> my $xquery2 = "//othermeta[\@name = 'plugin.id']/\@content";# find an +othermeta with a name = plugin.id and @content my $xquery3 = '//@xml:lang'; # find first @xml:lang my $xparser = XML::LibXML->new(); # create new parser object eval { $xmldoc = $xparser->parse_file($file) }; # trap parsing errors + that can't be suppressed normally, like &nbsp; entities if ($@){ print "Problems! \n The error(s):\n$@\n"; } if ($pluginname = $xmldoc->findvalue( $xquery2 )){ # returns value +of plugin name print " Plugin name found: $pluginname\n"; }
ETC...
SC

In reply to Re: Finding node with attribute XML::LibXML by stylechief
in thread Finding node with attribute XML::LibXML by jjap

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.