<?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: With Bankruptcy on Our Minds: The Structure of Title 11 U.S.C.</title>
	<atom:link href="http://computationallegalstudies.com/2009/04/01/with-bankruptcy-on-our-minds-the-structure-of-title-11-usc/feed/" rel="self" type="application/rss+xml" />
	<link>http://computationallegalstudies.com/2009/04/01/with-bankruptcy-on-our-minds-the-structure-of-title-11-usc/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 19:15:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Visualizing 26 U.S.C., Take 2: Capital Gains &#38; Losses - Full Depth &#124; Computational Legal Studies</title>
		<link>http://computationallegalstudies.com/2009/04/01/with-bankruptcy-on-our-minds-the-structure-of-title-11-usc/#comment-171</link>
		<dc:creator>Visualizing 26 U.S.C., Take 2: Capital Gains &#38; Losses - Full Depth &#124; Computational Legal Studies</dc:creator>
		<pubDate>Wed, 15 Apr 2009 02:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://computationallegalstudies.com/?p=325#comment-171</guid>
		<description>[...] For details on the coloring of the visual, see our previous post visualizing the Bankruptcy Code 11 U.S.C here. [...] </description>
		<content:encoded><![CDATA[<p>[...] For details on the coloring of the visual, see our previous post visualizing the Bankruptcy Code 11 U.S.C here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Visualizing 26 U.S.C ___ : At the &#8220;Section Depth&#8221; &#124; Computational Legal Studies</title>
		<link>http://computationallegalstudies.com/2009/04/01/with-bankruptcy-on-our-minds-the-structure-of-title-11-usc/#comment-170</link>
		<dc:creator>Visualizing 26 U.S.C ___ : At the &#8220;Section Depth&#8221; &#124; Computational Legal Studies</dc:creator>
		<pubDate>Mon, 13 Apr 2009 10:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://computationallegalstudies.com/?p=325#comment-170</guid>
		<description>[...] representation would include a mapping beyond Sec. 501 to its (c) and (3) subcomponents.  In our previous post highlighting 11 U.S.C. __ (the Bankruptcy Code), we presented a traversable &#8220;full depth&#8221; representation for its [...] </description>
		<content:encoded><![CDATA[<p>[...] representation would include a mapping beyond Sec. 501 to its (c) and (3) subcomponents.  In our previous post highlighting 11 U.S.C. __ (the Bankruptcy Code), we presented a traversable &#8220;full depth&#8221; representation for its [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Katz</title>
		<link>http://computationallegalstudies.com/2009/04/01/with-bankruptcy-on-our-minds-the-structure-of-title-11-usc/#comment-169</link>
		<dc:creator>Daniel Katz</dc:creator>
		<pubDate>Wed, 08 Apr 2009 15:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://computationallegalstudies.com/?p=325#comment-169</guid>
		<description>There are several issues which you might be the culprit.    Screen resolution, machine configuration and/or software.  Screen resolution is often the issue.  It is a large image to render.

However, it might also be a function of specific configuration of your machine and/or software.  Without sitting at your work station, it is difficult to know precisely what to say.  

We have heard from lots of folks who had no difficulty.  Thus, perhaps you can use an alternative machine?

Anyway...  best of luck,  Dan</description>
		<content:encoded><![CDATA[<p>There are several issues which you might be the culprit.    Screen resolution, machine configuration and/or software.  Screen resolution is often the issue.  It is a large image to render.</p>
<p>However, it might also be a function of specific configuration of your machine and/or software.  Without sitting at your work station, it is difficult to know precisely what to say.  </p>
<p>We have heard from lots of folks who had no difficulty.  Thus, perhaps you can use an alternative machine?</p>
<p>Anyway&#8230;  best of luck,  Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Lawless</title>
		<link>http://computationallegalstudies.com/2009/04/01/with-bankruptcy-on-our-minds-the-structure-of-title-11-usc/#comment-168</link>
		<dc:creator>Bob Lawless</dc:creator>
		<pubDate>Wed, 08 Apr 2009 13:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://computationallegalstudies.com/?p=325#comment-168</guid>
		<description>Ditto with same software. It also did not work for me on Internet Explorer.</description>
		<content:encoded><![CDATA[<p>Ditto with same software. It also did not work for me on Internet Explorer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Weinstein</title>
		<link>http://computationallegalstudies.com/2009/04/01/with-bankruptcy-on-our-minds-the-structure-of-title-11-usc/#comment-167</link>
		<dc:creator>Jesse Weinstein</dc:creator>
		<pubDate>Fri, 03 Apr 2009 23:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://computationallegalstudies.com/?p=325#comment-167</guid>
		<description>The text does not seem to be visible, at least on Firefox 3.0.8 on WinXP, with Flash 10.0 r12.  The terminal nodes just are little white squarish shapes.</description>
		<content:encoded><![CDATA[<p>The text does not seem to be visible, at least on Firefox 3.0.8 on WinXP, with Flash 10.0 r12.  The terminal nodes just are little white squarish shapes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc
Database Caching 1/4 queries in 0.001 seconds using apc
Object Caching 259/262 objects using apc

Served from: computationallegalstudies.com @ 2012-02-08 14:56:43 -->
