<?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/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	> <channel><title>Comments on: What&#8217;s the Deal with NCIP?</title> <atom:link href="http://dltj.org/article/whats-the-deal-with-ncip/feed/" rel="self" type="application/rss+xml" /><link>http://dltj.org/article/whats-the-deal-with-ncip/</link> <description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description> <lastBuildDate>Wed, 08 Feb 2012 17:48:39 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Peter Murray</title><link>http://dltj.org/article/whats-the-deal-with-ncip/comment-page-1/#comment-153210</link> <dc:creator>Peter Murray</dc:creator> <pubDate>Wed, 29 Jun 2011 17:24:38 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2008/01/whats-the-deal-with-ncip/#comment-153210</guid> <description>Thanks for the pointer, Cat.  Since I wrote that post in early 2008, NISO has beefed up its collaboration capabilities with the &lt;a href=&quot;http://www.kavi.com/&quot; rel=&quot;nofollow&quot;&gt;KAVI&lt;/a&gt; software.</description> <content:encoded><![CDATA[<p>Thanks for the pointer, Cat.  Since I wrote that post in early 2008, NISO has beefed up its collaboration capabilities with the <a href="http://www.kavi.com/" rel="nofollow">KAVI</a> software.</p> ]]></content:encoded> </item> <item><title>By: Cat Aloger</title><link>http://dltj.org/article/whats-the-deal-with-ncip/comment-page-1/#comment-153208</link> <dc:creator>Cat Aloger</dc:creator> <pubDate>Wed, 29 Jun 2011 17:18:49 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2008/01/whats-the-deal-with-ncip/#comment-153208</guid> <description>The discussion group link on the envisionware site is working as of the end of June 2011.http://www.niso.org/lists/ncipinfo/</description> <content:encoded><![CDATA[<p>The discussion group link on the envisionware site is working as of the end of June 2011.</p><p><a href="http://www.niso.org/lists/ncipinfo/" rel="nofollow">http://www.niso.org/lists/ncipinfo/</a></p> ]]></content:encoded> </item> <item><title>By: the jester</title><link>http://dltj.org/article/whats-the-deal-with-ncip/comment-page-1/#comment-29771</link> <dc:creator>the jester</dc:creator> <pubDate>Fri, 25 Jan 2008 02:10:00 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2008/01/whats-the-deal-with-ncip/#comment-29771</guid> <description>Hmmm.  I, too, had certainly envisioned a more free-flowing model, not a hub-and-spoke model (no matter who was in the center).  Thanks for the reply, David.</description> <content:encoded><![CDATA[<p>Hmmm.  I, too, had certainly envisioned a more free-flowing model, not a hub-and-spoke model (no matter who was in the center).  Thanks for the reply, David.</p> ]]></content:encoded> </item> <item><title>By: David F</title><link>http://dltj.org/article/whats-the-deal-with-ncip/comment-page-1/#comment-29767</link> <dc:creator>David F</dc:creator> <pubDate>Fri, 25 Jan 2008 01:20:11 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2008/01/whats-the-deal-with-ncip/#comment-29767</guid> <description>&lt;blockquote&gt; &lt;i&gt;Does “NCIP Compliant” actually mean anything?&lt;/i&gt; &lt;/blockquote&gt;No. When I first started reading the specs, I thought that it might allow a given library to connect to another, arbitrary, library that was known to have the desired item. But that&#039;s not how it works at core. A library can only send requests to libraries with which it has negotiated a trust relationship outside of the NCIP world. This is why, at LITA Forum &#039;06 in Nashville, OCLC kept talking up their &quot;star&quot; model: everybody trusts OCLC, so you send requests to us, and we&#039;ll broker between library systems.&quot;</description> <content:encoded><![CDATA[<blockquote><p> <i>Does “NCIP Compliant” actually mean anything?</i></p></blockquote><p>No. When I first started reading the specs, I thought<br /> that it might allow a given library to connect to another,<br /> arbitrary, library that was known to have the desired item. But<br /> that&#8217;s not how it works at core. A library can only send requests<br /> to libraries with which it has negotiated a trust relationship<br /> outside of the NCIP world. This is why, at LITA Forum &#8217;06 in<br /> Nashville, OCLC kept talking up their &#8220;star&#8221; model: everybody<br /> trusts OCLC, so you send requests to us, and we&#8217;ll broker between<br /> library systems.&#8221;</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: dltj.org @ 2012-02-11 15:38:46 by W3 Total Cache -->
