<?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: Practical ePub metadata: Authorship</title>
	<atom:link href="http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/</link>
	<description>Threepress creates software for publishers, educators and authors.</description>
	<lastBuildDate>Tue, 07 Feb 2012 13:57:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Liza Daly</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-3471</link>
		<dc:creator>Liza Daly</dc:creator>
		<pubDate>Tue, 27 Jul 2010 13:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-3471</guid>
		<description>They would just be expressed by multiple elements:

&lt;dc:creator opf:role=&quot;aut&quot;&gt;person&lt;/dc:creator&gt;

&lt;dc:creator opf:role=&quot;edt&quot;&gt;person&lt;/dc:creator&gt;</description>
		<content:encoded><![CDATA[<p>They would just be expressed by multiple elements:</p>
<p>&lt;dc:creator opf:role=&#8221;aut&#8221;&gt;person&lt;/dc:creator&gt;</p>
<p>&lt;dc:creator opf:role=&#8221;edt&#8221;&gt;person&lt;/dc:creator&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: elmimmo</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-3465</link>
		<dc:creator>elmimmo</dc:creator>
		<pubDate>Sun, 25 Jul 2010 15:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-3465</guid>
		<description>How about one creator with several roles? Say, author and illustrator are the same person, but then there are also other creators with their own role.</description>
		<content:encoded><![CDATA[<p>How about one creator with several roles? Say, author and illustrator are the same person, but then there are also other creators with their own role.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nic Gibson</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-2167</link>
		<dc:creator>Nic Gibson</dc:creator>
		<pubDate>Fri, 19 Feb 2010 08:05:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-2167</guid>
		<description>I&#039;m terribly late to comment here but I was the person who required Dave Cramer to abuse the mechanism. I totally agree that we should never have to work around bugs in the reader but the editorial staff at the  major  trade publisher I worked for at that time were absolutely opposed to any ebook being released that didn&#039;t show all authors on the author line. We raised this with Adobe who accepted that is was a bug but that didn&#039;t resolve the commercial issue. 

I&#039;m currently writing an ePub conversion spec for another major trade publisher (they currently require simply that their conversion partners work to the IDPF specs and the output is too variable with that wide a specification). I&#039;ve found myself in exactly the same situation. As a result I may have to create the same requirement again.</description>
		<content:encoded><![CDATA[<p>I&#8217;m terribly late to comment here but I was the person who required Dave Cramer to abuse the mechanism. I totally agree that we should never have to work around bugs in the reader but the editorial staff at the  major  trade publisher I worked for at that time were absolutely opposed to any ebook being released that didn&#8217;t show all authors on the author line. We raised this with Adobe who accepted that is was a bug but that didn&#8217;t resolve the commercial issue. </p>
<p>I&#8217;m currently writing an ePub conversion spec for another major trade publisher (they currently require simply that their conversion partners work to the IDPF specs and the output is too variable with that wide a specification). I&#8217;ve found myself in exactly the same situation. As a result I may have to create the same requirement again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liza Daly</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-2016</link>
		<dc:creator>Liza Daly</dc:creator>
		<pubDate>Mon, 11 Jan 2010 15:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-2016</guid>
		<description>Personally I hate working around bugs in readers when composing an ebook. The ebook file will long outlast the bugs, and should be written with that in mind.</description>
		<content:encoded><![CDATA[<p>Personally I hate working around bugs in readers when composing an ebook. The ebook file will long outlast the bugs, and should be written with that in mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cook</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-2014</link>
		<dc:creator>Mike Cook</dc:creator>
		<pubDate>Sun, 10 Jan 2010 13:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-2014</guid>
		<description>How would you handle something such as Andrew Lang&#039;s Fairy Books in the NCX file?

Various
Andrew Lang

As many reading systems will assign the first dc:creator it encounters as the author. Because I always place &quot;aut&quot; first this will be shown as &quot;Various&quot; (this is how Adobe DE works), though it would probably be more useful to have the author shown as &quot;Andrew Lang&quot;.

In these situations would you recommend I put the &quot;edt&quot; first, or stay with my current hierarchy (below) and live with the fact that the author will be shown as &quot;Various&quot;?

dc:creator opf:role=&quot;aut&quot;
dc:creator opf:role=&quot;edt&quot;
dc:creator opf:role=&quot;ill&quot;
etc.</description>
		<content:encoded><![CDATA[<p>How would you handle something such as Andrew Lang&#8217;s Fairy Books in the NCX file?</p>
<p>Various<br />
Andrew Lang</p>
<p>As many reading systems will assign the first dc:creator it encounters as the author. Because I always place &#8220;aut&#8221; first this will be shown as &#8220;Various&#8221; (this is how Adobe DE works), though it would probably be more useful to have the author shown as &#8220;Andrew Lang&#8221;.</p>
<p>In these situations would you recommend I put the &#8220;edt&#8221; first, or stay with my current hierarchy (below) and live with the fact that the author will be shown as &#8220;Various&#8221;?</p>
<p>dc:creator opf:role=&#8221;aut&#8221;<br />
dc:creator opf:role=&#8221;edt&#8221;<br />
dc:creator opf:role=&#8221;ill&#8221;<br />
etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xelle</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-1537</link>
		<dc:creator>Xelle</dc:creator>
		<pubDate>Thu, 03 Dec 2009 19:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-1537</guid>
		<description>In our digital publishing process, we also choose to put all the main authors in one element, to comply with ADE... All our publishers currently want to have DRM, so ADE is not one reader among the others, it&#039;s the only reader we have to work with.
They don&#039;t understand yet all the consequences of this choice on their ebooks&#039; quality...</description>
		<content:encoded><![CDATA[<p>In our digital publishing process, we also choose to put all the main authors in one element, to comply with ADE&#8230; All our publishers currently want to have DRM, so ADE is not one reader among the others, it&#8217;s the only reader we have to work with.<br />
They don&#8217;t understand yet all the consequences of this choice on their ebooks&#8217; quality&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-1403</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Sat, 28 Nov 2009 07:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-1403</guid>
		<description>the other guy&#039;s bugs are always trivial.

except, of course, when they&#039;re not...

-bowerbird</description>
		<content:encoded><![CDATA[<p>the other guy&#8217;s bugs are always trivial.</p>
<p>except, of course, when they&#8217;re not&#8230;</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stuart yeates</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-1389</link>
		<dc:creator>stuart yeates</dc:creator>
		<pubDate>Fri, 27 Nov 2009 21:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-1389</guid>
		<description>I&#039;m with Liza on this. We do lots of things in our ePubs that are beyond the capability of an particular reader to display.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with Liza on this. We do lots of things in our ePubs that are beyond the capability of an particular reader to display.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liza Daly</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-1385</link>
		<dc:creator>Liza Daly</dc:creator>
		<pubDate>Fri, 27 Nov 2009 17:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-1385</guid>
		<description>That&#039;s unfortunate but I don&#039;t believe that publishers who are making significant investments in digitization projects should be working around bugs in ADE that are trivial to fix.</description>
		<content:encoded><![CDATA[<p>That&#8217;s unfortunate but I don&#8217;t believe that publishers who are making significant investments in digitization projects should be working around bugs in ADE that are trivial to fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Cramer</title>
		<link>http://blog.threepress.org/2009/11/27/practical-epub-metadata-authorship/comment-page-1/#comment-1384</link>
		<dc:creator>Dave Cramer</dc:creator>
		<pubDate>Fri, 27 Nov 2009 15:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1001#comment-1384</guid>
		<description>Unfortunately, ADE will only display the contents of the first dc:creator element above the NCX display. So some customers have required us to put all authors in a single dc:creator, wrong as that is.</description>
		<content:encoded><![CDATA[<p>Unfortunately, ADE will only display the contents of the first dc:creator element above the NCX display. So some customers have required us to put all authors in a single dc:creator, wrong as that is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

