You could build a hash for each doc, where the key is the node's content, and the value is a reference to a list of ids. 
my %text1 = (
   "is"                       => [ "1" ],
   "example that I just made" => [ "2" ],
   "I"                        => [ "3" ],
);

my %text2 = (
   "Here is"                  => [ "7" ],
   "example that I just made" => [ "8" ],
);

foreach my $content (keys %text2) {
   next if not exists $text1{$content};

   my @ids = (
      (map { "text1.$_" } @{$text1{$content}}),
      (map { "text2.$_" } @{$text2{$content}}),
   );

   print("\"$content\" found at ", join(', ', @ids), "\n");
}

[download]

Building the hashes is an exercise left to the user (since it's dependant on the parser you're using).

In reply to Re: Matching up XML tags in 2 arrays by ikegami
in thread Matching up XML tags in 2 arrays by bwgoudey

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.