<?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: R.I.P.ositories</title>
	<atom:link href="http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/</link>
	<description>Ideas linking Libraries, Computing, E-learning, and anything else that springs to mind.</description>
	<lastBuildDate>Tue, 27 Dec 2011 12:03:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Owen Stephens</title>
		<link>http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/comment-page-1/#comment-110</link>
		<dc:creator>Owen Stephens</dc:creator>
		<pubDate>Tue, 22 Apr 2008 16:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.meanboyfriend.com/overdue_ideas/?p=175#comment-110</guid>
		<description>Thanks for leaving the comment Rachel. I guess I meant that the IE diagram isn&#039;t explicit enough in how the IE engages with the wider web.
I agree with much of your comment. However, I think as a community we often are a bit inward looking. To take a couple of examples:
Many library catalogues have been available on the web for 10+ years - but most output as unstructured html. How many output RSS as a standard results format? How many provide a publicly accessible RESTful API? While most catalogues support z39.50, few have adopted SRU/W.
JSR168 - I theory this is a great idea - but try to integrate any HE based service with Netvibes, Pageflakes, iGoogle etc. We are talking a different language to them.
It is perhaps too easy to be negative about the situation, and I argue in my post that things are actually more positive than others portray. However, I worry that OAI-PMH is the z39.50 of the repository world - a great idea, but never going to be adopted by the majority.
</description>
		<content:encoded><![CDATA[<p>Thanks for leaving the comment Rachel. I guess I meant that the IE diagram isn&#8217;t explicit enough in how the IE engages with the wider web.<br />
I agree with much of your comment. However, I think as a community we often are a bit inward looking. To take a couple of examples:<br />
Many library catalogues have been available on the web for 10+ years &#8211; but most output as unstructured html. How many output RSS as a standard results format? How many provide a publicly accessible RESTful API? While most catalogues support z39.50, few have adopted SRU/W.<br />
JSR168 &#8211; I theory this is a great idea &#8211; but try to integrate any HE based service with Netvibes, Pageflakes, iGoogle etc. We are talking a different language to them.<br />
It is perhaps too easy to be negative about the situation, and I argue in my post that things are actually more positive than others portray. However, I worry that OAI-PMH is the z39.50 of the repository world &#8211; a great idea, but never going to be adopted by the majority.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen Stephens</title>
		<link>http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/comment-page-1/#comment-111</link>
		<dc:creator>Owen Stephens</dc:creator>
		<pubDate>Tue, 22 Apr 2008 16:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.meanboyfriend.com/overdue_ideas/?p=175#comment-111</guid>
		<description>Thanks for leaving the comment Rachel. I guess I meant that the IE diagram isn&#039;t explicit enough in how the IE engages with the wider web.
I agree with much of your comment. However, I think as a community we often are a bit inward looking. To take a couple of examples:
Many library catalogues have been available on the web for 10+ years - but most output as unstructured html. How many output RSS as a standard results format? How many provide a publicly accessible RESTful API? While most catalogues support z39.50, few have adopted SRU/W.
JSR168 - I theory this is a great idea - but try to integrate any HE based service with Netvibes, Pageflakes, iGoogle etc. We are talking a different language to them.
It is perhaps too easy to be negative about the situation, and I argue in my post that things are actually more positive than others portray. However, I worry that OAI-PMH is the z39.50 of the repository world - a great idea, but never going to be adopted by the majority.
</description>
		<content:encoded><![CDATA[<p>Thanks for leaving the comment Rachel. I guess I meant that the IE diagram isn&#8217;t explicit enough in how the IE engages with the wider web.<br />
I agree with much of your comment. However, I think as a community we often are a bit inward looking. To take a couple of examples:<br />
Many library catalogues have been available on the web for 10+ years &#8211; but most output as unstructured html. How many output RSS as a standard results format? How many provide a publicly accessible RESTful API? While most catalogues support z39.50, few have adopted SRU/W.<br />
JSR168 &#8211; I theory this is a great idea &#8211; but try to integrate any HE based service with Netvibes, Pageflakes, iGoogle etc. We are talking a different language to them.<br />
It is perhaps too easy to be negative about the situation, and I argue in my post that things are actually more positive than others portray. However, I worry that OAI-PMH is the z39.50 of the repository world &#8211; a great idea, but never going to be adopted by the majority.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rachel Bruce</title>
		<link>http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/comment-page-1/#comment-108</link>
		<dc:creator>Rachel Bruce</dc:creator>
		<pubDate>Tue, 22 Apr 2008 02:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.meanboyfriend.com/overdue_ideas/?p=175#comment-108</guid>
		<description>I&#039;ve just come across this post. I have to comment on the issue of the IE being closed. Your comment:&quot;the IE encourages the idea of a closed community rather than integrating with the wider world&quot;. I have always interpreted the IE diagram as a pretty high level representation of different sets of services within an infrastructure ( that should work with the wider web ). The boundaries between the different layers have always been blurred (I think they are even more so now we see web service approaches). The presentation layer in my view has always been about all different types of views on to the content and services. So subject portal, web search engine, library management system, personal learning environment. The &#039;portal&#039; type services that have been developed through JISC IE funding have always been encouraged to make their services available in flexible ways so a few years back JSR168, SRU/W and then WSRP, REST.
I guess you do say &#039;encourages the idea&#039;; I concede that. We needed [need] to make the more open nature clearer.
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just come across this post. I have to comment on the issue of the IE being closed. Your comment:&#8221;the IE encourages the idea of a closed community rather than integrating with the wider world&#8221;. I have always interpreted the IE diagram as a pretty high level representation of different sets of services within an infrastructure ( that should work with the wider web ). The boundaries between the different layers have always been blurred (I think they are even more so now we see web service approaches). The presentation layer in my view has always been about all different types of views on to the content and services. So subject portal, web search engine, library management system, personal learning environment. The &#8216;portal&#8217; type services that have been developed through JISC IE funding have always been encouraged to make their services available in flexible ways so a few years back JSR168, SRU/W and then WSRP, REST.<br />
I guess you do say &#8216;encourages the idea&#8217;; I concede that. We needed [need] to make the more open nature clearer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rachel Bruce</title>
		<link>http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/comment-page-1/#comment-109</link>
		<dc:creator>Rachel Bruce</dc:creator>
		<pubDate>Tue, 22 Apr 2008 02:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.meanboyfriend.com/overdue_ideas/?p=175#comment-109</guid>
		<description>I&#039;ve just come across this post. I have to comment on the issue of the IE being closed. Your comment:&quot;the IE encourages the idea of a closed community rather than integrating with the wider world&quot;. I have always interpreted the IE diagram as a pretty high level representation of different sets of services within an infrastructure ( that should work with the wider web ). The boundaries between the different layers have always been blurred (I think they are even more so now we see web service approaches). The presentation layer in my view has always been about all different types of views on to the content and services. So subject portal, web search engine, library management system, personal learning environment. The &#039;portal&#039; type services that have been developed through JISC IE funding have always been encouraged to make their services available in flexible ways so a few years back JSR168, SRU/W and then WSRP, REST.
I guess you do say &#039;encourages the idea&#039;; I concede that. We needed [need] to make the more open nature clearer.
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just come across this post. I have to comment on the issue of the IE being closed. Your comment:&#8221;the IE encourages the idea of a closed community rather than integrating with the wider world&#8221;. I have always interpreted the IE diagram as a pretty high level representation of different sets of services within an infrastructure ( that should work with the wider web ). The boundaries between the different layers have always been blurred (I think they are even more so now we see web service approaches). The presentation layer in my view has always been about all different types of views on to the content and services. So subject portal, web search engine, library management system, personal learning environment. The &#8216;portal&#8217; type services that have been developed through JISC IE funding have always been encouraged to make their services available in flexible ways so a few years back JSR168, SRU/W and then WSRP, REST.<br />
I guess you do say &#8216;encourages the idea&#8217;; I concede that. We needed [need] to make the more open nature clearer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rachel Bruce</title>
		<link>http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/comment-page-1/#comment-107</link>
		<dc:creator>Rachel Bruce</dc:creator>
		<pubDate>Tue, 22 Apr 2008 02:28:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.meanboyfriend.com/overdue_ideas/?p=175#comment-107</guid>
		<description>I&#039;ve just come across this post. I have to comment on the issue of the IE being closed. Your comment:&quot;the IE encourages the idea of a closed community rather than integrating with the wider world&quot;. I have always interpreted the IE diagram as a pretty high level representation of different sets of services within an infrastructure ( that should work with the wider web ). The boundaries between the different layers have always been blurred (I think they are even more so now we see web service approaches). The presentation layer in my view has always been about all different types of views on to the content and services. So subject portal, web search engine, library management system, personal learning environment. The &#039;portal&#039; type services that have been developed through JISC IE funding have always been encouraged to make their services available in flexible ways so a few years back JSR168, SRU/W and then WSRP, REST.
I guess you do say &#039;encourages the idea&#039;; I concede that. We needed [need] to make the more open nature clearer.
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just come across this post. I have to comment on the issue of the IE being closed. Your comment:&#8221;the IE encourages the idea of a closed community rather than integrating with the wider world&#8221;. I have always interpreted the IE diagram as a pretty high level representation of different sets of services within an infrastructure ( that should work with the wider web ). The boundaries between the different layers have always been blurred (I think they are even more so now we see web service approaches). The presentation layer in my view has always been about all different types of views on to the content and services. So subject portal, web search engine, library management system, personal learning environment. The &#8216;portal&#8217; type services that have been developed through JISC IE funding have always been encouraged to make their services available in flexible ways so a few years back JSR168, SRU/W and then WSRP, REST.<br />
I guess you do say &#8216;encourages the idea&#8217;; I concede that. We needed [need] to make the more open nature clearer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roddy MacLeod</title>
		<link>http://www.meanboyfriend.com/overdue_ideas/2008/02/ripositories/comment-page-1/#comment-106</link>
		<dc:creator>Roddy MacLeod</dc:creator>
		<pubDate>Sun, 24 Feb 2008 19:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.meanboyfriend.com/overdue_ideas/?p=175#comment-106</guid>
		<description>Some of the PerX reports may be of interest WRT your R.I.P.ositories posy:
http://www.icbl.hw.ac.uk/perx/deliverables.htm
</description>
		<content:encoded><![CDATA[<p>Some of the PerX reports may be of interest WRT your R.I.P.ositories posy:<br />
<a href="http://www.icbl.hw.ac.uk/perx/deliverables.htm" rel="nofollow">http://www.icbl.hw.ac.uk/perx/deliverables.htm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

