<?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: On the Trident Project: Part 1 &#8211; Architecture</title>
	<atom:link href="http://library.duke.edu/blogs/digital-collections/2009/02/13/on-the-trident-project-part-1-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://library.duke.edu/blogs/digital-collections/2009/02/13/on-the-trident-project-part-1-architecture/</link>
	<description>Notes from the Digital Collections Team at Duke</description>
	<lastBuildDate>Fri, 20 Nov 2009 17:24:38 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Will Sexton</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/02/13/on-the-trident-project-part-1-architecture/comment-page-1/#comment-5601</link>
		<dc:creator>Will Sexton</dc:creator>
		<pubDate>Tue, 17 Feb 2009 20:40:06 +0000</pubDate>
		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=561#comment-5601</guid>
		<description>Thanks, Tito.  Yes, the index should work with the front end for digital collections.  I do expect the front end to use the repository API to access the contents of digital collections.  In fact, I hope that implementation of the repository will open up the digital collections to a wider variety of publishing possibilities than we have now.</description>
		<content:encoded><![CDATA[<p>Thanks, Tito.  Yes, the index should work with the front end for digital collections.  I do expect the front end to use the repository API to access the contents of digital collections.  In fact, I hope that implementation of the repository will open up the digital collections to a wider variety of publishing possibilities than we have now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tito Sierra</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/02/13/on-the-trident-project-part-1-architecture/comment-page-1/#comment-5591</link>
		<dc:creator>Tito Sierra</dc:creator>
		<pubDate>Tue, 17 Feb 2009 20:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=561#comment-5591</guid>
		<description>Nice work, Will.  One question... is the indexing component of Trident meant to only address metadata management and administration needs (i.e., to help metadata creators find existing records and avoid duplication), or will also power front-end digital collection searching? To put it a different way, how do you expect your front-end digital collection apps will interface with Trident?</description>
		<content:encoded><![CDATA[<p>Nice work, Will.  One question&#8230; is the indexing component of Trident meant to only address metadata management and administration needs (i.e., to help metadata creators find existing records and avoid duplication), or will also power front-end digital collection searching? To put it a different way, how do you expect your front-end digital collection apps will interface with Trident?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
