RSS と Atom の情報を XQuery を使って集約する

                
<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  >

<channel>
  <title>MCslp</title>
  <link>http://mcslp.com</link>
  <description>News from the desk of Martin MC Brown</description>
  <pubDate>Wed, 07 Nov 2007 23:25:53 +0000</pubDate>
  <generator>http://wordpress.org/?v=2.0.4</generator>
  <language>en</language>
      <item>
    <title>System Administration Toolkit: Testing system validity</title>
    <link>http://mcslp.com/?p=269</link>
    <comments>http://mcslp.com/?p=269#comments</comments>
    <pubDate>Wed, 07 Nov 2007 23:25:48 +0000</pubDate>
    <dc:creator>Martin MC Brown</dc:creator>
    
  <category>Articles</category>
  <category>IBM developerWorks</category>
  <category>Open Source</category>
  <category>System Administration</category>
    <guid isPermaLink="false">http://mcslp.com/?p=269</guid>
    <description><![CDATA[Have you ever wondered whether the system you are 
	using is the same as the one that you originally configured? 
Making sure that the configuration and setting information that you configured is the 
same as when you configured it should be a basic part of any security procedure. 
After all, if an unscrupulous person has [...]]]></description>
      <content:encoded><![CDATA[<p>Have you ever wondered whether the 
	  system you are using is the same as the one that you originally configured? 
	  </p>
<p>Making sure that the configuration and setting information that you configured 
is the same as when you configured it should be a basic part of any security procedure. 
After all, if an unscrupulous person has changed the configuration of your system, you 
want to know about it. </p>
<p>Tracking that information though can be difficult. You can't expect to 
check the contents of every single file. Even if you automated the process, the 
potential quantity of information to be checked could be enormous and often what you 
want first is a quick indication of where to start looking. </p>
<p>In my new article, System Administration Toolkit: Testing system validity I 
show you a number of techniques for recording and verifying this information, and 
include sample scripts that will automate the process for you. </p>
<p>Read: <a href="http://www.ibm.com/developerworks/aix/library/
 au-satsystemvalidity/index.html?ca=drs-">Systems Administration Toolkit: 
 Testing system validity</a>
</p>
]]></content:encoded>
      <wfw:commentRSS>http://mcslp.com/?feed=rss2&p=269</wfw:commentRSS>
    </item>
...
</rss>

                
<?xml version="1.0" encoding="UTF-8"?>
<feed version="0.3" xmlns="http://purl.org/atom/ns#"
  xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en">
  <title>MCslp</title>
  <link rel="alternate" type="text/html" href="http://mcslp.com"/>
  <tagline>News from the desk of Martin MC Brown</tagline>
  <modified>2007-11-07T23:25:53Z</modified>
  <copyright>Copyright 2007</copyright>
  <generator url="http://wordpress.org/" 
           version="2.0.4">WordPress</generator>
  <entry>
    <author>
      <name>Martin MC Brown</name>
    </author>
    <title type="text/html" mode="escaped"
      ><![CDATA[System Administration Toolkit: 
	           Testing system validity]]></title>
    <link rel="alternate" type="text/html" href="http://mcslp.com/?p=269"/>
    <id>http://mcslp.com/?p=269</id>
    <modified>2007-11-07T23:25:48Z</modified>
    <issued>2007-11-07T23:25:48Z</issued>

    <dc:subject>Articles</dc:subject>
    <dc:subject>IBM developerWorks</dc:subject>
    <dc:subject>Open Source</dc:subject>
    <dc:subject>System Administration</dc:subject>
    <summary type="text/plain" mode="escaped"><![CDATA[Have you ever 
	wondered whether the system you are using is the same as the one that you 
	originally configured? 
	Making sure that the configuration and setting information that you configured 
	is the same as when you configured it should be a basic part of any security 
	procedure. After all, if an unscrupulous person has [...]]]></summary>
    <content type="text/html" mode="escaped"
          xml:base="http://mcslp.com/?p=269"><![CDATA[...]]></content>
  </entry>

                
use XML::FeedPP;

my $source = 'http://planet.mcslp.com/wp-rss2.php';

my $feed = XML::FeedPP->new( $source );

print <<EOF;
<html>
<body>
<b>All the news that's fit to print</b>
<hr/>
EOF

foreach my $item ($feed->get_item()) 
{
    my ($title,$link) = ($item->link(),$item->title());

    print <<EOF;
<div>
   RSS item <b>$title</b> is located at <b>$link</b>
</div>
EOF

}

print <<EOF
  </body>
</html>
EOF

                
<html>
<body>
<b>All the news that's fit to print</b>
<hr/>
<div>
   RSS item <b>http://feeds.computerworld.com/~r/Computerworld/MartinMCBrown/
   ~3/188475547/six_months_with_two_skype_phones</b> is located at <b>Six 
   months with two Skype phones</b>
</div>
<div>
   RSS item <b>http://feeds.computerworld.com/~r/Computerworld/MartinMCBrown/
   ~3/187849420/what_to_do_with_the_old_computing_bits_and_pieces</b> is located 
   at <b>What to do with the old computing bits and pieces</b>
</div>
...
</div>
  </body>
</html>

                
<?xml version="1.0" encoding="utf-8" ?> 
<xsl:stylesheet
     version="1.0"
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:output method="xml" />
     <xsl:template match="rss/channel">
     <html>
          <body>
               <xsl:apply-templates select="item" />
          </body>
     </html>
     </xsl:template>
     <xsl:template match="item">
       <div>
         RSS item <b><xsl:value-of select="title"/></b> is located 
              at <b><xsl:value-of select="link"/></b>
       </div>
     </xsl:template>
</xsl:stylesheet>

                
declare function local:rss-row ($link, $title)
{
<div>
  RSS item <b>{$title}</b> is located at <b>{$link}</b>
</div>
};

declare function local:rss-summary ($url)
{
 for $b in doc($url)/rss/channel/item
 return local:rss-row($b/link/text(), $b/title/text())
};

<html>
<body>
<b>All the news that's fit to print</b>
<hr/>

 {local:rss-summary("planet.rss2.xml")}

  </body>
</html>

                
declare function local:rss-summary ($url)
{
 for $b in doc($url)/rss/channel/item
 order by $b/pubDate 
 return local:rss-row($b/link/text(), $b/title/text())
};

                
declare function local:rss-summary ($url)
{
 for $b in doc($url)/rss/channel/item
 order by $b/pubDate descending
 return local:rss-row($b/link/text(), $b/title/text())
};

                
declare function local:rss-row ($doctitle, $link, $title)
{
<li><a href="{$link}">{$doctitle}: {$title}</a></li>
};

declare function local:rss-summary ($url)
{
 let $feeddoc := doc($url)

 for $b in $feeddoc/rss/channel/item
 order by $b/pubDate descending
 return local:rss-row($feeddoc/rss/channel/title/text(), $b/link/text(), $b/title/text())

};

<html>
<body>
<b>All the news that's fit to print</b>
<hr/>

<ul>
 {local:rss-summary("http://coalface.mcslp.com/wp-rss2.php")}
 {local:rss-summary("http://www.mcslp.com/wp-rss2.php")}
</ul>
  </body>
</html>

                
declare function local:buildmergerow ($doctitle, $item)
{
<item>
<doctitle>{$doctitle}</doctitle>
<title>{$item/title/text()}</title>
<link>{$item/link/text()}</link>
<pubdate>{$item/pubDate/text()}</pubdate>
</item>
};

declare function local:rss-row ($item)
{
<li><a href="{$item/link/text()}">{$item/doctitle/text()}: 
               {$item/title/text()}</a></li>
};

declare function local:rss-summary ($url)
{
 let $feeddoc := doc($url)

 for $b in $feeddoc/rss/channel/item
         return local:buildmergerow($feeddoc/rss/channel/title/text(), $b)
};

<html>
<body>
<b>All the news that's fit to print</b>
<hr/>

<ul>

{ 
let $feedlist := ("http://coalface.mcslp.com/wp-rss2.php",
                  "http://www.mcslp.com/wp-rss2.php")

let $merged := for $url in $feedlist
        return local:rss-summary($url)

return for $item in $merged
        order by $item/pubdate descending
        return local:rss-row($item)

}

 </ul>
  </body>
</html>

                
if (count($feeddoc/atom:feed/atom:entry) > 0)
        then
              local:parse-atom($feeddoc)
        else
              local:parse-rss($feeddoc)

                
declare namespace atom = "http://purl.org/atom/ns#";

declare function local:atombuildmergerow ($doctitle, $item)
{
<item>
<doctitle>{$doctitle}</doctitle>
<title>{ $item/atom:title/text() }</title>
<link>{$item/atom:id/text()}</link>
<pubdate>{$item/atom:modified/text()}</pubdate>
</item>
};

declare function local:rssbuildmergerow ($doctitle, $item)
{
<item>
<doctitle>{$doctitle}</doctitle>
<title>{$item/title/text()}</title>
<link>{$item/link/text()}</link>
<pubdate>{$item/pubDate/text()}</pubdate>
</item>
};

declare function local:rss-row ($item)
{
<li><a href="{$item/link/text()}">{$item/doctitle/text()}: 
                            {$item/title/text()}</a></li>
};

declare function local:parse-rss($feeddoc)
{
    for $b in $feeddoc/rss/channel/item
         return local:rssbuildmergerow($feeddoc/rss/channel/title/text(), $b)
};

declare function local:parse-atom($feeddoc)
{
    for $b in $feeddoc/atom:feed/atom:entry
         return local:atombuildmergerow($feeddoc/atom:feed/atom:title/text(), $b)
};

<html>
<body>
<b>All the news that's fit to print</b>
<hr/>

<ul>

{
let $feedlist := ("coalface.rss2.xml",
                  "mcslp.atom.xml")

let $merged := for $url in $feedlist
        let $feeddoc := doc($url)
        return if (count($feeddoc/atom:feed/atom:entry) > 0)
        then
              local:parse-atom($feeddoc)
        else
              local:parse-rss($feeddoc)

return for $item in $merged
        order by $item/title
        return local:rss-row($item)

}

 </ul>
  </body>
</html>