<?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: Apple &amp; eReader insist every eReader book download site use their new non-standard URL format</title>
	<atom:link href="http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Sat, 21 Nov 2009 16:13:16 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steve Jordan</title>
		<link>http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/comment-page-1/#comment-1055415</link>
		<dc:creator>Steve Jordan</dc:creator>
		<pubDate>Mon, 11 May 2009 12:41:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/#comment-1055415</guid>
		<description>I wouldn&#039;t consider it worth the trouble... especially as I offer my books in 5 other formats already... that&#039;s enough links.  And I don&#039;t support the idea of setting up specialized links for specific devices... that&#039;s the opposite of standardization, and this industry needs standardization more than anything else.</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t consider it worth the trouble&#8230; especially as I offer my books in 5 other formats already&#8230; that&#8217;s enough links.  And I don&#8217;t support the idea of setting up specialized links for specific devices&#8230; that&#8217;s the opposite of standardization, and this industry needs standardization more than anything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Meadows</title>
		<link>http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/comment-page-1/#comment-1054466</link>
		<dc:creator>Chris Meadows</dc:creator>
		<pubDate>Sun, 10 May 2009 02:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/#comment-1054466</guid>
		<description>I imagine that you could probably edit the Bookshelf bookmarklet to work by changing the extensions and the prefixes that it changes.</description>
		<content:encoded><![CDATA[<p>I imagine that you could probably edit the Bookshelf bookmarklet to work by changing the extensions and the prefixes that it changes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ Valente</title>
		<link>http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/comment-page-1/#comment-1054368</link>
		<dc:creator>MJ Valente</dc:creator>
		<pubDate>Sat, 09 May 2009 22:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/#comment-1054368</guid>
		<description>I agree that now (2.1) the process to upload a .pdb file to eBook Reader is a pain. Either you need to send the files to your personal space in eReader.com or you need to know the *exact* URL of the file, which — of course — most of the times is not easily obtained in Safari Mobile. 

Having a bookmarklet could indeed work around this. Something Fictionwise should consider.

I&#039;m still wishing I hadn&#039;t upgraded from 2.0.1.</description>
		<content:encoded><![CDATA[<p>I agree that now (2.1) the process to upload a .pdb file to eBook Reader is a pain. Either you need to send the files to your personal space in eReader.com or you need to know the *exact* URL of the file, which — of course — most of the times is not easily obtained in Safari Mobile. </p>
<p>Having a bookmarklet could indeed work around this. Something Fictionwise should consider.</p>
<p>I&#8217;m still wishing I hadn&#8217;t upgraded from 2.0.1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Meadows</title>
		<link>http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/comment-page-1/#comment-1054213</link>
		<dc:creator>Chris Meadows</dc:creator>
		<pubDate>Sat, 09 May 2009 15:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/#comment-1054213</guid>
		<description>All right, fair enough. I thought that all URLs (or URIs?) were supposed to be approved by some standards body, the same way that domain name suffixes do. But I guess it&#039;s more open than that.

Anyway, that still doesn&#039;t change the central point that asking &lt;i&gt;everyone else&lt;/i&gt; to change the way they do things for the sake of convenience to &lt;i&gt;them&lt;/i&gt; seems a little backward to me.</description>
		<content:encoded><![CDATA[<p>All right, fair enough. I thought that all URLs (or URIs?) were supposed to be approved by some standards body, the same way that domain name suffixes do. But I guess it&#8217;s more open than that.</p>
<p>Anyway, that still doesn&#8217;t change the central point that asking <i>everyone else</i> to change the way they do things for the sake of convenience to <i>them</i> seems a little backward to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry Melton</title>
		<link>http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/comment-page-1/#comment-1054210</link>
		<dc:creator>Henry Melton</dc:creator>
		<pubDate>Sat, 09 May 2009 15:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/2009/05/08/ereaders-nonstandard-url/#comment-1054210</guid>
		<description>Chris, custom URN&#039;s are fairly common.  Take a look at http://www.rfc-editor.org/rfc/rfc3305.txt which is a standards based look at the whole issue.  Just off the cuff, I think this ereader: urn is a method to get around the fact that the iPhone&#039;s mobile Safari doesn&#039;t download to a file system like desktop versions do.  By putting a custom URN on the URL, the browser can route the download to the proper handler application.  Its the same thing that happens with iTune Store URL&#039;s to apps, with the itunes: urn.  

Of course, everyone should double-check my old memories, because I&#039;m not really on top of these issues anymore.</description>
		<content:encoded><![CDATA[<p>Chris, custom URN&#8217;s are fairly common.  Take a look at <a href="http://www.rfc-editor.org/rfc/rfc3305.txt" rel="nofollow">http://www.rfc-editor.org/rfc/rfc3305.txt</a> which is a standards based look at the whole issue.  Just off the cuff, I think this ereader: urn is a method to get around the fact that the iPhone&#8217;s mobile Safari doesn&#8217;t download to a file system like desktop versions do.  By putting a custom URN on the URL, the browser can route the download to the proper handler application.  Its the same thing that happens with iTune Store URL&#8217;s to apps, with the itunes: urn.  </p>
<p>Of course, everyone should double-check my old memories, because I&#8217;m not really on top of these issues anymore.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
