<?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"
	>
<channel>
	<title>Comments for inkdroid</title>
	<atom:link href="http://inkdroid.org/journal/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://inkdroid.org/journal</link>
	<description>beep beep</description>
	<pubDate>Sat, 05 Jul 2008 19:12:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Content-MD5 considered helpful by ed</title>
		<link>http://inkdroid.org/journal/2008/06/23/content-md5-considered-helpful/#comment-65729</link>
		<dc:creator>ed</dc:creator>
		<pubDate>Mon, 30 Jun 2008 13:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=205#comment-65729</guid>
		<description>No I hadn't seen that &lt;a href="http://gigaom.com/2008/06/27/storage-outages-can-todays-hardware-handle-the-cloud/" rel="nofollow"&gt;article&lt;/a&gt;, thanks Andy! So is the benefit of using the Content-MD5 HTTP header in addition to the checks built in to TCP? It allows you to check the integrity of the transfer explicitly rather than implicitly by just using TCP? The header does seem redundant somehow--it would be interesting to know the history of why it was added.</description>
		<content:encoded><![CDATA[<p>No I hadn&#8217;t seen that <a href="http://gigaom.com/2008/06/27/storage-outages-can-todays-hardware-handle-the-cloud/" rel="nofollow">article</a>, thanks Andy! So is the benefit of using the Content-MD5 HTTP header in addition to the checks built in to TCP? It allows you to check the integrity of the transfer explicitly rather than implicitly by just using TCP? The header does seem redundant somehow&#8211;it would be interesting to know the history of why it was added.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content-MD5 considered helpful by Andy Boyko</title>
		<link>http://inkdroid.org/journal/2008/06/23/content-md5-considered-helpful/#comment-65560</link>
		<dc:creator>Andy Boyko</dc:creator>
		<pubDate>Fri, 27 Jun 2008 20:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=205#comment-65560</guid>
		<description>Did you see where they traced the corruption to a faulty load balancer?  (Via &lt;a href="http://gigaom.com/2008/06/27/storage-outages-can-todays-hardware-handle-the-cloud/" rel="nofollow"&gt;GigaOm&lt;/a&gt;)</description>
		<content:encoded><![CDATA[<p>Did you see where they traced the corruption to a faulty load balancer?  (Via <a href="http://gigaom.com/2008/06/27/storage-outages-can-todays-hardware-handle-the-cloud/" rel="nofollow">GigaOm</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BagIt by Jim</title>
		<link>http://inkdroid.org/journal/2008/06/06/bagit/#comment-65445</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 24 Jun 2008 17:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=203#comment-65445</guid>
		<description>I was pretty pleased when LC suggested we use the spec to deliver NDIIPP content to them.  Super low cost and easy to validate.  

Addressing Peter's comment regarding 'best before' dates, it's my suspicion that LC isn't in a position to fast-track data acquisition presently.  That doesn't mean that the spec, as implemented by others, wouldn't benefit from a data associated with data.</description>
		<content:encoded><![CDATA[<p>I was pretty pleased when LC suggested we use the spec to deliver NDIIPP content to them.  Super low cost and easy to validate.  </p>
<p>Addressing Peter&#8217;s comment regarding &#8216;best before&#8217; dates, it&#8217;s my suspicion that LC isn&#8217;t in a position to fast-track data acquisition presently.  That doesn&#8217;t mean that the spec, as implemented by others, wouldn&#8217;t benefit from a data associated with data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content-MD5 considered helpful by Peter Murray</title>
		<link>http://inkdroid.org/journal/2008/06/23/content-md5-considered-helpful/#comment-65401</link>
		<dc:creator>Peter Murray</dc:creator>
		<pubDate>Mon, 23 Jun 2008 20:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=205#comment-65401</guid>
		<description>Very interesting, indeed!  I would have thought that the reliable transport of "TCP" was enough.  Page 207 (section 13.14 "TCP Checksum Computation") of my trusty third edition of Comer's Internetworking with TCP/IP says "TCP uses 16-bit arithmetic and takes the one's complement of the one's complement sum.  At the receiving site, TCP software performs the same computation to verify that the segment [headers plus playload] arrived intact."</description>
		<content:encoded><![CDATA[<p>Very interesting, indeed!  I would have thought that the reliable transport of &#8220;TCP&#8221; was enough.  Page 207 (section 13.14 &#8220;TCP Checksum Computation&#8221;) of my trusty third edition of Comer&#8217;s Internetworking with TCP/IP says &#8220;TCP uses 16-bit arithmetic and takes the one&#8217;s complement of the one&#8217;s complement sum.  At the receiving site, TCP software performs the same computation to verify that the segment [headers plus playload] arrived intact.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on provide and enable by RDFa &#187; Blog Archive &#187; UK National Archive Uses RDFa</title>
		<link>http://inkdroid.org/journal/2008/06/18/provide-and-enable/#comment-65398</link>
		<dc:creator>RDFa &#187; Blog Archive &#187; UK National Archive Uses RDFa</dc:creator>
		<pubDate>Mon, 23 Jun 2008 17:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=204#comment-65398</guid>
		<description>[...] Gazette (published since 1665), which we have already reported on, the next UK Government site reported to use RDFa is the UK National [...]</description>
		<content:encoded><![CDATA[<p>[...] Gazette (published since 1665), which we have already reported on, the next UK Government site reported to use RDFa is the UK National [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on following your nose to the web of data by Lost in Knowledge</title>
		<link>http://inkdroid.org/journal/2008/01/04/following-your-nose-to-the-web-of-data/#comment-64893</link>
		<dc:creator>Lost in Knowledge</dc:creator>
		<pubDate>Thu, 12 Jun 2008 17:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.inkdroid.org/journal/2008/01/04/following-your-nose-to-the-web-of-data/#comment-64893</guid>
		<description>&lt;strong&gt;Interesting overview about how it works&#8230;...&lt;/strong&gt;

Semantic Web, Linked data, RDF, Web 3.0 and the like are now buzz. A lot is being written about them but sometimes it&#8217;s hard for the newbie to fully understand how this data is to be related and how any software could navigate through it.
At inkd...</description>
		<content:encoded><![CDATA[<p><strong>Interesting overview about how it works&#8230;&#8230;</strong></p>
<p>Semantic Web, Linked data, RDF, Web 3.0 and the like are now buzz. A lot is being written about them but sometimes it&#8217;s hard for the newbie to fully understand how this data is to be related and how any software could navigate through it.<br />
At inkd&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BagIt by Peter Binkley</title>
		<link>http://inkdroid.org/journal/2008/06/06/bagit/#comment-64650</link>
		<dc:creator>Peter Binkley</dc:creator>
		<pubDate>Fri, 06 Jun 2008 21:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=203#comment-64650</guid>
		<description>We heard about this at the PASIG meeting in San Francisco last week - it looks very handy. I didn't pick up on the possibility of holey bags there, though. Given that this is intended for delivery rather than persistence, it might be helpful to allow a best-before date in fetch.txt (maybe per line). Since this will often be used to share ingestion-friendly files, which I may not want to leave lying around in web-accessible space, the date would let me say "get it by Friday cuz it may not be there next week".</description>
		<content:encoded><![CDATA[<p>We heard about this at the PASIG meeting in San Francisco last week - it looks very handy. I didn&#8217;t pick up on the possibility of holey bags there, though. Given that this is intended for delivery rather than persistence, it might be helpful to allow a best-before date in fetch.txt (maybe per line). Since this will often be used to share ingestion-friendly files, which I may not want to leave lying around in web-accessible space, the date would let me say &#8220;get it by Friday cuz it may not be there next week&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BagIt by Michael J. Giarlo</title>
		<link>http://inkdroid.org/journal/2008/06/06/bagit/#comment-64645</link>
		<dc:creator>Michael J. Giarlo</dc:creator>
		<pubDate>Fri, 06 Jun 2008 16:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=203#comment-64645</guid>
		<description>One quick response to gsf's query about fetch.txt, "one question: why aren’t URLs in the fetch.txt preceded by a checksum?"

The checksums for files listed in fetch.txt are already listed in the manifest.  I'm not sure how useful the length param is since the checksum is already recorded elsewhere, but I suppose it's a good way to -quickly- check if the content from a URL is what you're looking for.</description>
		<content:encoded><![CDATA[<p>One quick response to gsf&#8217;s query about fetch.txt, &#8220;one question: why aren’t URLs in the fetch.txt preceded by a checksum?&#8221;</p>
<p>The checksums for files listed in fetch.txt are already listed in the manifest.  I&#8217;m not sure how useful the length param is since the checksum is already recorded elsewhere, but I suppose it&#8217;s a good way to -quickly- check if the content from a URL is what you&#8217;re looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BagIt by Gabriel Sean Farrell</title>
		<link>http://inkdroid.org/journal/2008/06/06/bagit/#comment-64642</link>
		<dc:creator>Gabriel Sean Farrell</dc:creator>
		<pubDate>Fri, 06 Jun 2008 13:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=203#comment-64642</guid>
		<description>One thing I'm struck by right away is the similarity of of BagIt to the DSpace Simple Archive Format, which I'll call SAF even though the DSpace docs fail to employ such a lovely acronym.  The unfortunate URL for that section of the docs is http://www.dspace.org/index.php?option=com_content&#38;task=view&#38;id=144#itemimporter.  Anyway, as you can see there, SAF consists of an archive directory with item subdirectories.  Each item directory contains a dublin_core.xml describing the item and a "contents" file similar to the BagIt "manifest", but without the checksums.  

BagIt is obviously more flexible, and the fetch.txt is a banging idea (one question: why aren't URLs in the fetch.txt preceded by a checksum?).  It occurs to me now that it would be simple to send an SAF item or bunch of items within a Bag, though I'm not sure what the gain there would be.  In any case, that part of SWORD (i.e. converting from BagIt to something DSpace/Fedora/etc. can ingest) should be pretty simple, so you're probably right that the retrieval of "holey bags" will be the kicker.</description>
		<content:encoded><![CDATA[<p>One thing I&#8217;m struck by right away is the similarity of of BagIt to the DSpace Simple Archive Format, which I&#8217;ll call SAF even though the DSpace docs fail to employ such a lovely acronym.  The unfortunate URL for that section of the docs is <a href="http://www.dspace.org/index.php?option=com_content&amp;task=view&amp;id=144#itemimporter" rel="nofollow">http://www.dspace.org/index.php?option=com_content&amp;task=view&amp;id=144#itemimporter</a>.  Anyway, as you can see there, SAF consists of an archive directory with item subdirectories.  Each item directory contains a dublin_core.xml describing the item and a &#8220;contents&#8221; file similar to the BagIt &#8220;manifest&#8221;, but without the checksums.  </p>
<p>BagIt is obviously more flexible, and the fetch.txt is a banging idea (one question: why aren&#8217;t URLs in the fetch.txt preceded by a checksum?).  It occurs to me now that it would be simple to send an SAF item or bunch of items within a Bag, though I&#8217;m not sure what the gain there would be.  In any case, that part of SWORD (i.e. converting from BagIt to something DSpace/Fedora/etc. can ingest) should be pretty simple, so you&#8217;re probably right that the retrieval of &#8220;holey bags&#8221; will be the kicker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SKOS in the Context of Semantic Web Deployment by Presentation at the Library of Congress: Simple Knowledge Organization System (SKOS) in the context of Semantic Web Deployment &#171; Alistair Miles</title>
		<link>http://inkdroid.org/journal/2008/04/30/skos-in-the-context-of-semantic-web-deployment/#comment-62071</link>
		<dc:creator>Presentation at the Library of Congress: Simple Knowledge Organization System (SKOS) in the context of Semantic Web Deployment &#171; Alistair Miles</dc:creator>
		<pubDate>Tue, 13 May 2008 16:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=196#comment-62071</guid>
		<description>[...] presentation on SKOS and Semantic Web Deployment last week at the Library of Congress. Here&#8217;s the blurb.. Links are valuable. Links between documents, between people, between ideas, between data. Data is [...]</description>
		<content:encoded><![CDATA[<p>[...] presentation on SKOS and Semantic Web Deployment last week at the Library of Congress. Here&#8217;s the blurb.. Links are valuable. Links between documents, between people, between ideas, between data. Data is [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
