<?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: MARC-Hash: a proposed format for JSON/YAML/Whatever-compatible MARC records</title>
	<atom:link href="http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/feed/" rel="self" type="application/rss+xml" />
	<link>http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/</link>
	<description>Disclaimer: I'm not actually a robot.</description>
	<lastBuildDate>Thu, 08 Jul 2010 20:37:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bill</title>
		<link>http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/comment-page-1/#comment-78</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Mon, 13 Apr 2009 23:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/#comment-78</guid>
		<description>&lt;p&gt;Meh. I agree -- and hence the disclaimers --- that it&#039;s nothing special. But &quot;nothing special that everyone agrees on&quot; is better than no agreement at all, and for some people XML processing is a barrier they don&#039;t want to have to deal with. For all its seeming ubiquity, lots of folks never have to deal with XML in their programming.&lt;/p&gt;

&lt;p&gt;I guess my thing is, &quot;IF we&#039;re going to serialize MARC as JSON/YAML/Whatnot, let&#039;s all do it the same way.&quot;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Meh. I agree &#8212; and hence the disclaimers &#8212; that it&#8217;s nothing special. But &#8220;nothing special that everyone agrees on&#8221; is better than no agreement at all, and for some people <acronym title="Extensible Markup Language">XML</acronym> processing is a barrier they don&#8217;t want to have to deal with. For all its seeming ubiquity, lots of folks never have to deal with <acronym title="Extensible Markup Language">XML</acronym> in their programming.</p>

<p>I guess my thing is, &#8220;IF we&#8217;re going to serialize <acronym title="MAchine Readable Cataloging">MARC</acronym> as JSON/YAML/Whatnot, let&#8217;s all do it the same way.&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/comment-page-1/#comment-77</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Mon, 13 Apr 2009 22:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/#comment-77</guid>
		<description>&lt;p&gt;This is basically just MARC-XML translated to JSON, yes?&lt;/p&gt;

&lt;p&gt;Do you really find it easier to work with than MARC-XML?  I guess if you&#039;re doing your work in javascript, maybe.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is basically just <acronym title="MAchine Readable Cataloging">MARC</acronym>-<acronym title="Extensible Markup Language">XML</acronym> translated to JSON, yes?</p>

<p>Do you really find it easier to work with than <acronym title="MAchine Readable Cataloging">MARC</acronym>-<acronym title="Extensible Markup Language">XML</acronym>?  I guess if you&#8217;re doing your work in javascript, maybe.</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.467 seconds -->
