<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: O&#8217;Reilly to Amazon: Open the Kindle!</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2009/07/07/oreilly-calls-for-amazon-to-open-the-kindle/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2009/07/07/oreilly-calls-for-amazon-to-open-the-kindle/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Wed, 15 Feb 2012 17:25:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: New Technologies and the Need for Standards &#171; The Scholarly Kitchen</title>
		<link>http://scholarlykitchen.sspnet.org/2009/07/07/oreilly-calls-for-amazon-to-open-the-kindle/#comment-4585</link>
		<dc:creator><![CDATA[New Technologies and the Need for Standards &#171; The Scholarly Kitchen]]></dc:creator>
		<pubDate>Fri, 11 Sep 2009 14:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=4884#comment-4585</guid>
		<description><![CDATA[[...] argued that one essential way to move the e-book market forward is to settle on a standard file format, the most likely being ePub, despite its many obvious [...]]]></description>
		<content:encoded><![CDATA[<p>[...] argued that one essential way to move the e-book market forward is to settle on a standard file format, the most likely being ePub, despite its many obvious [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thorn</title>
		<link>http://scholarlykitchen.sspnet.org/2009/07/07/oreilly-calls-for-amazon-to-open-the-kindle/#comment-3793</link>
		<dc:creator><![CDATA[thorn]]></dc:creator>
		<pubDate>Tue, 07 Jul 2009 16:58:13 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=4884#comment-3793</guid>
		<description><![CDATA[yep. note to amazon: open the kindle!

and - note 2 to amazon: open your dang e-book format! why shouldn&#039;t sony reader owners be able to purchase their content directly from amazon, rather than (possibly) having to purchase from other sources, where content is far more expensive? i&#039;m thinking their $ is as good as anyone&#039;s..]]></description>
		<content:encoded><![CDATA[<p>yep. note to amazon: open the kindle!</p>
<p>and &#8211; note 2 to amazon: open your dang e-book format! why shouldn&#8217;t sony reader owners be able to purchase their content directly from amazon, rather than (possibly) having to purchase from other sources, where content is far more expensive? i&#8217;m thinking their $ is as good as anyone&#8217;s..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaveh</title>
		<link>http://scholarlykitchen.sspnet.org/2009/07/07/oreilly-calls-for-amazon-to-open-the-kindle/#comment-3791</link>
		<dc:creator><![CDATA[Kaveh]]></dc:creator>
		<pubDate>Tue, 07 Jul 2009 15:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=4884#comment-3791</guid>
		<description><![CDATA[I fully agree with Tim O&#039;Reilly. And there is another reason to use open specifications for eBooks, namely to allow complex STM content, like tables and math, to be used in eBooks. Presently there is no solution for complex STM content, save a dumb PDF.]]></description>
		<content:encoded><![CDATA[<p>I fully agree with Tim O&#8217;Reilly. And there is another reason to use open specifications for eBooks, namely to allow complex STM content, like tables and math, to be used in eBooks. Presently there is no solution for complex STM content, save a dumb PDF.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

