<?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: Analysis: Some revelations on Day Two</title>
	<atom:link href="http://www.scotusblog.com/2005/09/analysis-some-revelations-on-day-two/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.scotusblog.com/2005/09/analysis-some-revelations-on-day-two/</link>
	<description>The Supreme Court of the United States blog</description>
	<lastBuildDate>Mon, 23 Jan 2012 22:38:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Chris</title>
		<link>http://www.scotusblog.com/2005/09/analysis-some-revelations-on-day-two/#comment-7948</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 14 Sep 2005 15:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.scotusblog.com/wp/uncategorized/analysis-some-revelations-on-day-two/#comment-7948</guid>
		<description>&quot;Both [Scalia and Thomas] consider quite illegitimate the thought that the Constitutionâ€™s words should be given up-to-date meanings, as times change. Roberts drew a distinction between original motivation and the breadth of language actually chosen by constitutional draftsmen. One can accept why a provision was put into the Constitution, he suggested, but then see breadth -- and some fluidity -- in the concepts written into the document.&quot;
&lt;p&gt;Our understanding of the legitimacy of &quot;up-to-date meanings&quot; would be much clearer, I think, if we used distinctions from the philosophy of language to mark a difference between changed meanings, on the one hand, and changed constitutional outcomes, on the other.  Using the philosophy of language would help, I think.    For what it&#039;s worth, &lt;a href=&quot;http://papers.ssrn.com/sol3/papers.cfm?abstract_id=798466&quot; rel=&quot;nofollow&quot;&gt;here&#039;s my attempt to do that&lt;/a&gt;, defending a half-dead, half-living Constitution.  In Fregean language, we can have an up-to-date Bedeutung without an up-to-date Sinn.
&lt;p&gt;I&#039;m not sure if I&#039;m the same sort of &quot;interesting combination of a constitutional &#039;originalist&#039; and a believer that the Constitution changes over time â€“ that it is in some ways a living document&quot; that Roberts may seem to be, but I agree that there is plenty of unexplored space there.&lt;/p&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&#8220;Both [Scalia and Thomas] consider quite illegitimate the thought that the Constitutionâ€™s words should be given up-to-date meanings, as times change. Roberts drew a distinction between original motivation and the breadth of language actually chosen by constitutional draftsmen. One can accept why a provision was put into the Constitution, he suggested, but then see breadth &#8212; and some fluidity &#8212; in the concepts written into the document.&#8221;</p>
<p>Our understanding of the legitimacy of &#8220;up-to-date meanings&#8221; would be much clearer, I think, if we used distinctions from the philosophy of language to mark a difference between changed meanings, on the one hand, and changed constitutional outcomes, on the other.  Using the philosophy of language would help, I think.    For what it&#8217;s worth, <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=798466" rel="nofollow">here&#8217;s my attempt to do that</a>, defending a half-dead, half-living Constitution.  In Fregean language, we can have an up-to-date Bedeutung without an up-to-date Sinn.</p>
<p>I&#8217;m not sure if I&#8217;m the same sort of &#8220;interesting combination of a constitutional &#8216;originalist&#8217; and a believer that the Constitution changes over time â€“ that it is in some ways a living document&#8221; that Roberts may seem to be, but I agree that there is plenty of unexplored space there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

