<?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"
	>
<channel>
	<title>Comments on: Creative Commons NonCommercial</title>
	<atom:link href="http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/feed/" rel="self" type="application/rss+xml" />
	<link>http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/</link>
	<description>relatively irrelevant</description>
	<pubDate>Fri, 05 Sep 2008 13:38:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Jacques FROISSANT Altaïde</title>
		<link>http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/#comment-2825</link>
		<dc:creator>Jacques FROISSANT Altaïde</dc:creator>
		<pubDate>Wed, 22 Mar 2006 17:38:40 +0000</pubDate>
		<guid isPermaLink="false">http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/#comment-2825</guid>
		<description>&lt;p&gt;&lt;strong&gt;Schmap le guide touristique 2.0 ...&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Schmap c'est vraiment le guide touristique 2.0 ! : un contenu mis à jour en temps réel, customisable, consultable à volonté, proposant des excursions virtuelles modifiables pour préparer les votres selon vos envies, des cartes agissant de manièr...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>Schmap le guide touristique 2.0 &#8230;</strong></p>
<p>Schmap c&#8217;est vraiment le guide touristique 2.0 ! : un contenu mis à jour en temps réel, customisable, consultable à volonté, proposant des excursions virtuelles modifiables pour préparer les votres selon vos envies, des cartes agissant de manièr&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Pittman</title>
		<link>http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/#comment-2802</link>
		<dc:creator>David Pittman</dc:creator>
		<pubDate>Tue, 07 Mar 2006 01:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/#comment-2802</guid>
		<description>&lt;p&gt;My feeling is that Schmap does intend to make a profit.  If not immediately, then later on.  Use of the creative commons photos is a cost saving measure during their startup. Their contract seems to supersede the standard creative commons license in that it allows them to use the photos at any time in the future, regardless of the extent of ad revenue or change in download policy.  This certainly seems to be a wise business approach given the extensive database of travel photographs on the Flickr site, although not all are CC.  I wonder how many all rights reserved photos are short listed?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>My feeling is that Schmap does intend to make a profit.  If not immediately, then later on.  Use of the creative commons photos is a cost saving measure during their startup. Their contract seems to supersede the standard creative commons license in that it allows them to use the photos at any time in the future, regardless of the extent of ad revenue or change in download policy.  This certainly seems to be a wise business approach given the extensive database of travel photographs on the Flickr site, although not all are CC.  I wonder how many all rights reserved photos are short listed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Whyndham</title>
		<link>http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/#comment-2793</link>
		<dc:creator>Matt Whyndham</dc:creator>
		<pubDate>Fri, 03 Mar 2006 09:34:20 +0000</pubDate>
		<guid isPermaLink="false">http://jasonpearce.com/blog/2006/03/01/creative-commons-noncommercial/#comment-2793</guid>
		<description>&lt;p&gt;Having read the draft CC guidelines on non-commercial use (you have to click through until you get to the PDF), it still seems a bit grey. What does "in connection with" mean?&lt;/p&gt;

&lt;p&gt;I'm taking the scope of that to be "pertaining to the whole project". Others may confine themselves to the particular "supplier" transaction revolving around the CC-licenced work itself, or to the transaction involving the end-user. I think the latter is what Schmap are hoping.&lt;/p&gt;

&lt;p&gt;Photographers providing elements of a guidebook don't always get paid highly. Thousands queue up to get into Lonely Planet books, and I think all you get is another guidebook, and none of your image rights.&lt;/p&gt;

&lt;p&gt;In the commercial world, suppliers of many OEM components don't always benefit from the whole-product value chain either, or influence it very much (unless you are Intel), so it's on the face of it a bold posture to expect all the terms of your contract to be exactly duplicated further along the chain, and for this to propagate to the entire product.&lt;/p&gt;

&lt;p&gt;Like GPL components of Sun's software, you can require, if you choose, that your OEM component (i.e. your photo) be incorporated in another work without your work being inaccessible as a result. But you would have to be Intel-strength-critical to the success of that product to require that the whole product be placed in the commons.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Having read the draft CC guidelines on non-commercial use (you have to click through until you get to the PDF), it still seems a bit grey. What does &#8220;in connection with&#8221; mean?</p>
<p>I&#8217;m taking the scope of that to be &#8220;pertaining to the whole project&#8221;. Others may confine themselves to the particular &#8220;supplier&#8221; transaction revolving around the CC-licenced work itself, or to the transaction involving the end-user. I think the latter is what Schmap are hoping.</p>
<p>Photographers providing elements of a guidebook don&#8217;t always get paid highly. Thousands queue up to get into Lonely Planet books, and I think all you get is another guidebook, and none of your image rights.</p>
<p>In the commercial world, suppliers of many OEM components don&#8217;t always benefit from the whole-product value chain either, or influence it very much (unless you are Intel), so it&#8217;s on the face of it a bold posture to expect all the terms of your contract to be exactly duplicated further along the chain, and for this to propagate to the entire product.</p>
<p>Like GPL components of Sun&#8217;s software, you can require, if you choose, that your OEM component (i.e. your photo) be incorporated in another work without your work being inaccessible as a result. But you would have to be Intel-strength-critical to the success of that product to require that the whole product be placed in the commons.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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