<?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 for Rights and Royalties News</title>
	<atom:link href="http://www.rightsandroyalties.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rightsandroyalties.com</link>
	<description>Your Source for News Affecting Rights, Royalties and the Future of Publishing</description>
	<lastBuildDate>Tue, 31 Aug 2010 18:26:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on e-Books: Promo Potential Outweighs Piracy Peril by Bobson</title>
		<link>http://www.rightsandroyalties.com/2010/08/e-books-promo-potential-outweighs-piracy-peril/comment-page-1/#comment-226</link>
		<dc:creator>Bobson</dc:creator>
		<pubDate>Tue, 31 Aug 2010 18:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.rightsandroyalties.com/?p=330#comment-226</guid>
		<description>DRM is a miracle to anybody who wants to keep they&#039;re work secure. It&#039;s every writers dream to know that no scoundrel is extracting he/she&#039;s work. It&#039;s a wonder to know that technology is always around to have our backs.

&lt;a href=&quot;http://www.goldenagenovel.com&quot; rel=&quot;nofollow&quot;&gt;Ebook and Novella &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>DRM is a miracle to anybody who wants to keep they&#8217;re work secure. It&#8217;s every writers dream to know that no scoundrel is extracting he/she&#8217;s work. It&#8217;s a wonder to know that technology is always around to have our backs.</p>
<p><a href="http://www.goldenagenovel.com" rel="nofollow">Ebook and Novella </a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating Standards for the Book Rights Registry:  Using Existing Standards Part 3 &#8211; ONIX for RRO&#8217;s by admin</title>
		<link>http://www.rightsandroyalties.com/2009/08/onix_for_rros/comment-page-1/#comment-14</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 13 Aug 2009 15:42:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.rightsandroyalties.com/?p=76#comment-14</guid>
		<description>Mark,

Thanks so much!  This is great.  I misunderstood the intended semantics of &quot;distribution&quot; - so thanks for clarifying.  Makes much more sense now.

My thinking on DSR is that it requires an identifier.  Does that identifier represent the content, or the implementation of that content?  If it represents the implementation of that content, then somewhere there must be a link between the implementation and the content/book/work.  If that is the case, then we would have duplication of data and the potential challenges that come with that.

If the identifier in DSR refers to the content/book/work, then DSR is insufficient for the purpose, and ONIX-DS would be required.

Would love to get your thoughts on that.

Finally, thanks for clarifying the usage.  I had not realized that the implementation now underway was a production environment - that&#039;s great news.

Thanks again!</description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>Thanks so much!  This is great.  I misunderstood the intended semantics of &#8220;distribution&#8221; &#8211; so thanks for clarifying.  Makes much more sense now.</p>
<p>My thinking on DSR is that it requires an identifier.  Does that identifier represent the content, or the implementation of that content?  If it represents the implementation of that content, then somewhere there must be a link between the implementation and the content/book/work.  If that is the case, then we would have duplication of data and the potential challenges that come with that.</p>
<p>If the identifier in DSR refers to the content/book/work, then DSR is insufficient for the purpose, and ONIX-DS would be required.</p>
<p>Would love to get your thoughts on that.</p>
<p>Finally, thanks for clarifying the usage.  I had not realized that the implementation now underway was a production environment &#8211; that&#8217;s great news.</p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating Standards for the Book Rights Registry:  Using Existing Standards Part 3 &#8211; ONIX for RRO&#8217;s by Mark Bide</title>
		<link>http://www.rightsandroyalties.com/2009/08/onix_for_rros/comment-page-1/#comment-13</link>
		<dc:creator>Mark Bide</dc:creator>
		<pubDate>Thu, 13 Aug 2009 07:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.rightsandroyalties.com/?p=76#comment-13</guid>
		<description>David, thank you for your very helpful post about the &quot;ONIX for RROs&quot; standards. I have a small number of comments on your posting which I hope will be helpful in deepening the understanding of the two messages.

Your description of ONIX for Repertoire as &quot;a way for a rights holder to identify rights for a body of works, rather than just an individual work&quot; is correct, although I might be inclined to describe it as &quot;a way for a rights holder to communicate rights and permissions for a body of works, rather than just an individual work&quot;. It is also true that ONIX for Repertoire in use can (and is) used to communicate messages about single works where this is appropriate. 

What I am not less sure about is your description of a Repertoire as a &quot;specific collection of Distributions&quot;. A &quot;Distribution&quot; in RRO terms is the process whereby money collected from licensees is allocated to individual titles and their rightsholders. A Distribution message is therefore the message that documents a payment, explaining to the rightsholder the individual sums which go to make up a complete payment.

Why not use DSR for this purpose? Essentially because DSR is lacking in detail -- it can describe the allocation of funds to a list of identified works, but does not carry the detail of how those funds were calculated. Within the RRO community, the ability to describe not only what is being paid but also why is essential. Does the same thing apply to the distribution of funds from the Book Rights Registry? My assumption (on the basis of what I know in other contexts) is that some rightsholders will both expect and make use of this data, while others will find a simple listing of allocations a title level sufficient. This is certainly worth more careful exploration. 

Finally, as far as implementation is concerned, yes these standards are new. But both are now in use in a very rigorous &quot;production&quot; environment in the UK, with literally hundreds of ONIX-RP messages being processed every week. The nature of ONIX-DS is that there are not so many messages involved (one a month) but that has now been &quot;in production&quot; for a year and is working very smoothly.

Mark</description>
		<content:encoded><![CDATA[<p>David, thank you for your very helpful post about the &#8220;ONIX for RROs&#8221; standards. I have a small number of comments on your posting which I hope will be helpful in deepening the understanding of the two messages.</p>
<p>Your description of ONIX for Repertoire as &#8220;a way for a rights holder to identify rights for a body of works, rather than just an individual work&#8221; is correct, although I might be inclined to describe it as &#8220;a way for a rights holder to communicate rights and permissions for a body of works, rather than just an individual work&#8221;. It is also true that ONIX for Repertoire in use can (and is) used to communicate messages about single works where this is appropriate. </p>
<p>What I am not less sure about is your description of a Repertoire as a &#8220;specific collection of Distributions&#8221;. A &#8220;Distribution&#8221; in RRO terms is the process whereby money collected from licensees is allocated to individual titles and their rightsholders. A Distribution message is therefore the message that documents a payment, explaining to the rightsholder the individual sums which go to make up a complete payment.</p>
<p>Why not use DSR for this purpose? Essentially because DSR is lacking in detail &#8212; it can describe the allocation of funds to a list of identified works, but does not carry the detail of how those funds were calculated. Within the RRO community, the ability to describe not only what is being paid but also why is essential. Does the same thing apply to the distribution of funds from the Book Rights Registry? My assumption (on the basis of what I know in other contexts) is that some rightsholders will both expect and make use of this data, while others will find a simple listing of allocations a title level sufficient. This is certainly worth more careful exploration. </p>
<p>Finally, as far as implementation is concerned, yes these standards are new. But both are now in use in a very rigorous &#8220;production&#8221; environment in the UK, with literally hundreds of ONIX-RP messages being processed every week. The nature of ONIX-DS is that there are not so many messages involved (one a month) but that has now been &#8220;in production&#8221; for a year and is working very smoothly.</p>
<p>Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tech Watch Article:  Should Google Be Allowed to Monopolize &#8220;Orphan&#8221; Books? by dmarlin</title>
		<link>http://www.rightsandroyalties.com/2009/07/tech-watch-article-should-google-be-allowed-to-monopolize-orphan-books/comment-page-1/#comment-2</link>
		<dc:creator>dmarlin</dc:creator>
		<pubDate>Thu, 09 Jul 2009 21:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rightsandroyalties.com/2009/07/09/tech-watch-article-should-google-be-allowed-to-monopolize-orphan-books/#comment-2</guid>
		<description>Not sure about the facts of this dollar amount - I think the author may be confusing the BRR with the publishers settlement.</description>
		<content:encoded><![CDATA[<p>Not sure about the facts of this dollar amount &#8211; I think the author may be confusing the BRR with the publishers settlement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
