<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Converting the III XML Server into an SRU/SRW Server</title>
	<atom:link href="http://scriblio.net/scribbles/124/converting-the-iii-xml-server-into-an-srusrw-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://scriblio.net/scribbles/124/converting-the-iii-xml-server-into-an-srusrw-server/</link>
	<description>open source software for libraries</description>
	<lastBuildDate>Sat, 21 Jan 2012 14:35:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: dwalker</title>
		<link>http://scriblio.net/scribbles/124/converting-the-iii-xml-server-into-an-srusrw-server/#comment-1631</link>
		<dc:creator>dwalker</dc:creator>
		<pubDate>Thu, 18 Aug 2005 20:16:48 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=12#comment-1631</guid>
		<description>Just got our III XML Server back up and running today, and started using the above style sheets.

Boy is it fast!

I was testing the XSLT previously against Plymouth State and Michigan State&#039;s catalogs, but firewalls and network latency slowed it down a bit.

When using it against our own catalog, it&#039;s sub-second fast.  The initial XSLT transformation of the III output to SRU / MARC XML or Dublin Core is not even noticeable.

I think this really ultimately removes any problems I had in using the III XML Server.  It would be nice if Innovative actually made the XML Server SRU and MARC-XML compliant from the beginning.   But this work-around is so straight forward and in no way a hack that I&#039;m as happy as can be with the whole purchase now.</description>
		<content:encoded><![CDATA[<p>Just got our III XML Server back up and running today, and started using the above style sheets.</p>
<p>Boy is it fast!</p>
<p>I was testing the XSLT previously against Plymouth State and Michigan State&#8217;s catalogs, but firewalls and network latency slowed it down a bit.</p>
<p>When using it against our own catalog, it&#8217;s sub-second fast.  The initial XSLT transformation of the III output to SRU / MARC XML or Dublin Core is not even noticeable.</p>
<p>I think this really ultimately removes any problems I had in using the III XML Server.  It would be nice if Innovative actually made the XML Server SRU and MARC-XML compliant from the beginning.   But this work-around is so straight forward and in no way a hack that I&#8217;m as happy as can be with the whole purchase now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
