<?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: Phones and Food</title>
	<atom:link href="http://madisonian.net/2007/07/09/phones-and-food/feed/" rel="self" type="application/rss+xml" />
	<link>http://madisonian.net/2007/07/09/phones-and-food/</link>
	<description>a blog about law, tech, culture, and related things</description>
	<lastBuildDate>Sat, 11 Feb 2012 02:59:42 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Buccafusco</title>
		<link>http://madisonian.net/2007/07/09/phones-and-food/comment-page-1/#comment-224090</link>
		<dc:creator>Chris Buccafusco</dc:creator>
		<pubDate>Mon, 16 Jul 2007 17:58:46 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/archives/2007/07/09/phones-and-food/#comment-224090</guid>
		<description>Thanks for the post on food and IP.  There is some interesting cultural history behind the development of chefs as creative artists.  For any number of reasons, as musicians, painters, and poets were responding to the calls of the Romantic revolution, chefs remained in their kitchens toiling away unseen.  With the eruption of public restaurants in the early 19th century, chefs had an opportunity to claim their place alongside these other newly minted geniuses.  I believe that one reason they missed the chance is that the most popular and influential chefs of the day - men like Careme and Escoffier - thought of themselves as systematizers.  Great cooking in the 19th century had more to do with correct reproductions of canonical dishes than it did with creating original masterpieces (although there was a place for this).  It really wasn&#039;t until the establishment of Nouvelle Cuisine in the 1970s that classic haute cuisine was even questioned.  Nouvelle Cuisine, and the king-makers at Michelin and Gault-Millau, established a culinary discourse that prized creativity and originality above all else and set the stage for the recognition of chefs as artists.  Of course, my suggestion raises as many questions as it answers (why were Careme and Escoffier canonizers?  what role does gender play?  what about philosophical and aesthetic ideas about the sense of taste?), but perhaps it helps explain why chefs have been so late to the IP party and why they seem to be coming on so strongly.</description>
		<content:encoded><![CDATA[<p>Thanks for the post on food and IP.  There is some interesting cultural history behind the development of chefs as creative artists.  For any number of reasons, as musicians, painters, and poets were responding to the calls of the Romantic revolution, chefs remained in their kitchens toiling away unseen.  With the eruption of public restaurants in the early 19th century, chefs had an opportunity to claim their place alongside these other newly minted geniuses.  I believe that one reason they missed the chance is that the most popular and influential chefs of the day &#8211; men like Careme and Escoffier &#8211; thought of themselves as systematizers.  Great cooking in the 19th century had more to do with correct reproductions of canonical dishes than it did with creating original masterpieces (although there was a place for this).  It really wasn&#8217;t until the establishment of Nouvelle Cuisine in the 1970s that classic haute cuisine was even questioned.  Nouvelle Cuisine, and the king-makers at Michelin and Gault-Millau, established a culinary discourse that prized creativity and originality above all else and set the stage for the recognition of chefs as artists.  Of course, my suggestion raises as many questions as it answers (why were Careme and Escoffier canonizers?  what role does gender play?  what about philosophical and aesthetic ideas about the sense of taste?), but perhaps it helps explain why chefs have been so late to the IP party and why they seem to be coming on so strongly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Madison</title>
		<link>http://madisonian.net/2007/07/09/phones-and-food/comment-page-1/#comment-224085</link>
		<dc:creator>Mike Madison</dc:creator>
		<pubDate>Thu, 12 Jul 2007 18:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/archives/2007/07/09/phones-and-food/#comment-224085</guid>
		<description>See, e.g., the dissent in Lion Oil Co. v. Marsh, 220 Ark. 678, 249 S.W.2d 569 (1952), but I&#039;m not sure that the case applies here.  It deals with state labor laws.</description>
		<content:encoded><![CDATA[<p>See, e.g., the dissent in Lion Oil Co. v. Marsh, 220 Ark. 678, 249 S.W.2d 569 (1952), but I&#8217;m not sure that the case applies here.  It deals with state labor laws.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Boyden</title>
		<link>http://madisonian.net/2007/07/09/phones-and-food/comment-page-1/#comment-224082</link>
		<dc:creator>Bruce Boyden</dc:creator>
		<pubDate>Wed, 11 Jul 2007 18:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/archives/2007/07/09/phones-and-food/#comment-224082</guid>
		<description>Hmm, good points. On &quot;lawfully,&quot; first, it&#039;s modifying &quot;connecting,&quot; meaning that the connection has to be lawful (i.e., no phone phreaking), rather than the circumvention itself (obviously, since that&#039;s the whole point of the exception). I haven&#039;t seen the iPhone terms, but I bet they flat-out ban RE, not using the phone to connect to some other service per se. Of course, even if that&#039;s true, Apple could just re-word its terms.

Which leads to my second point, which is that somewhere in the dim recesses of my brain, I recall seeing cases that stand for the proposition that &quot;unlawful&quot; in statutes typically does not mean &quot;in breach of a contract,&quot; but rather in violation of public law. Breaching a contract is not illegal; it just subjects you to damages (and maybe other remedies).</description>
		<content:encoded><![CDATA[<p>Hmm, good points. On &#8220;lawfully,&#8221; first, it&#8217;s modifying &#8220;connecting,&#8221; meaning that the connection has to be lawful (i.e., no phone phreaking), rather than the circumvention itself (obviously, since that&#8217;s the whole point of the exception). I haven&#8217;t seen the iPhone terms, but I bet they flat-out ban RE, not using the phone to connect to some other service per se. Of course, even if that&#8217;s true, Apple could just re-word its terms.</p>
<p>Which leads to my second point, which is that somewhere in the dim recesses of my brain, I recall seeing cases that stand for the proposition that &#8220;unlawful&#8221; in statutes typically does not mean &#8220;in breach of a contract,&#8221; but rather in violation of public law. Breaching a contract is not illegal; it just subjects you to damages (and maybe other remedies).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Madison</title>
		<link>http://madisonian.net/2007/07/09/phones-and-food/comment-page-1/#comment-224081</link>
		<dc:creator>Mike Madison</dc:creator>
		<pubDate>Wed, 11 Jul 2007 16:01:02 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/archives/2007/07/09/phones-and-food/#comment-224081</guid>
		<description>Bruce,
I hope that you&#039;re right, and I also hope that we never have to test the proposition.
The word &quot;lawfully&quot; in the regulation is curious, however.  Does &quot;lawfully&quot; have a &quot;telecommunications law&quot; meaning, that is, no one is hacking into the network; the subscriber has paid for access, and so on?  I imagine that this is what the Copyright Office intended.  But might &quot;lawfully&quot; have a broader meaning, so that connecting to a non-AT&amp;T network with the iPhone might not be &quot;lawful&quot; because doing so violates the &quot;no reverse engineering&quot; covenant that the user agreed to? And what if the circumvention is not for the purpose of connecting to a wireless phone network, but for disabling the iPhone&#039;s connection to AT&amp;T&#039;s network, without intending to adopt a new phone connection?
Just wondering.  Of course, even if the exception doesn&#039;t apply then there may be no 1201 liability because, as you note, there is no underlying work to be protected.  But courts (.e.g, Blizzard) haven&#039;t been resolute in applying 1201 that way.
Mike</description>
		<content:encoded><![CDATA[<p>Bruce,<br />
I hope that you&#8217;re right, and I also hope that we never have to test the proposition.<br />
The word &#8220;lawfully&#8221; in the regulation is curious, however.  Does &#8220;lawfully&#8221; have a &#8220;telecommunications law&#8221; meaning, that is, no one is hacking into the network; the subscriber has paid for access, and so on?  I imagine that this is what the Copyright Office intended.  But might &#8220;lawfully&#8221; have a broader meaning, so that connecting to a non-AT&#038;T network with the iPhone might not be &#8220;lawful&#8221; because doing so violates the &#8220;no reverse engineering&#8221; covenant that the user agreed to? And what if the circumvention is not for the purpose of connecting to a wireless phone network, but for disabling the iPhone&#8217;s connection to AT&#038;T&#8217;s network, without intending to adopt a new phone connection?<br />
Just wondering.  Of course, even if the exception doesn&#8217;t apply then there may be no 1201 liability because, as you note, there is no underlying work to be protected.  But courts (.e.g, Blizzard) haven&#8217;t been resolute in applying 1201 that way.<br />
Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Boyden</title>
		<link>http://madisonian.net/2007/07/09/phones-and-food/comment-page-1/#comment-224078</link>
		<dc:creator>Bruce Boyden</dc:creator>
		<pubDate>Mon, 09 Jul 2007 18:11:27 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/archives/2007/07/09/phones-and-food/#comment-224078</guid>
		<description>Interesting. I don&#039;t think a &quot;no reverse engineering&quot; clause can create 1201 liability where there otherwise isn&#039;t any (e.g., no copyrighted work being protected; or an exception applies). It can create *contractual* liability, but that&#039;s a whole different box of remedies.

On the exception, this may be an example of the open texture of law, but the text of the regulation that was actually adopted is broader than what Peters implied in her recommendation:

&quot;Computer programs in the form of firmware that enable wireless telephone handsets to connect to a wireless telephone communication network, when circumvention is accomplished for the sole purpose of lawfully connecting to a wireless telephone communication network.&quot;

That seems to cover iPhone hacking, no matter what Apple intended for the iPhone, so long as the circumvention is limited to connecting to a different network. (I&#039;m presuming that, e.g., opening the case is not &quot;circumvention.&quot;) Even beyond that, Chamberlain and Lexmark would seem to stand in the way of a 1201 suit challenging circumvention of protections on the operation of software code where reproduction of the code was not reasonably at issue.</description>
		<content:encoded><![CDATA[<p>Interesting. I don&#8217;t think a &#8220;no reverse engineering&#8221; clause can create 1201 liability where there otherwise isn&#8217;t any (e.g., no copyrighted work being protected; or an exception applies). It can create *contractual* liability, but that&#8217;s a whole different box of remedies.</p>
<p>On the exception, this may be an example of the open texture of law, but the text of the regulation that was actually adopted is broader than what Peters implied in her recommendation:</p>
<p>&#8220;Computer programs in the form of firmware that enable wireless telephone handsets to connect to a wireless telephone communication network, when circumvention is accomplished for the sole purpose of lawfully connecting to a wireless telephone communication network.&#8221;</p>
<p>That seems to cover iPhone hacking, no matter what Apple intended for the iPhone, so long as the circumvention is limited to connecting to a different network. (I&#8217;m presuming that, e.g., opening the case is not &#8220;circumvention.&#8221;) Even beyond that, Chamberlain and Lexmark would seem to stand in the way of a 1201 suit challenging circumvention of protections on the operation of software code where reproduction of the code was not reasonably at issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://madisonian.net/2007/07/09/phones-and-food/comment-page-1/#comment-224077</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Mon, 09 Jul 2007 17:04:33 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/archives/2007/07/09/phones-and-food/#comment-224077</guid>
		<description>re the Chef as romantic author: Those who find the cultivation of expensive tastes morally problematic can only hope that series like &quot;My Super Sweet 16&quot; cultivate a counternarrative: food snobs as spoiled villains, and their &quot;courtier-chefs&quot; overweening enablers of a decadent elite.  

Perhaps they could use this book for ideas: David Rakoff, 
Don&#039;t Get Too Comfortable: The Indignities of Coach Class, The Torments of Low Thread Count, The Never-Ending Quest for Artisanal Olive Oil, and Other First World Problems.

at http://www.amazon.com/Dont-Get-Too-Comfortable-Indignities/dp/0385510365</description>
		<content:encoded><![CDATA[<p>re the Chef as romantic author: Those who find the cultivation of expensive tastes morally problematic can only hope that series like &#8220;My Super Sweet 16&#8243; cultivate a counternarrative: food snobs as spoiled villains, and their &#8220;courtier-chefs&#8221; overweening enablers of a decadent elite.  </p>
<p>Perhaps they could use this book for ideas: David Rakoff,<br />
Don&#8217;t Get Too Comfortable: The Indignities of Coach Class, The Torments of Low Thread Count, The Never-Ending Quest for Artisanal Olive Oil, and Other First World Problems.</p>
<p>at <a href="http://www.amazon.com/Dont-Get-Too-Comfortable-Indignities/dp/0385510365" rel="nofollow">http://www.amazon.com/Dont-Get-Too-Comfortable-Indignities/dp/0385510365</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

