<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0">
<channel>
<title>William L. Reynolds</title>
<copyright>Copyright (c) 2011  All rights reserved.</copyright>
<link>http://works.bepress.com/william_reynolds</link>
<description>Recent documents in William L. Reynolds</description>
<language>en-us</language>
<lastBuildDate>Fri, 15 Jul 2011 07:26:26 PDT</lastBuildDate>
<ttl>3600</ttl>








<item>
<title>The Supreme Court Rules for the Reporting of Opinions: A Critique</title>
<link>http://works.bepress.com/william_reynolds/46</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/46</guid>
<pubDate>Wed, 02 Mar 2011 12:17:59 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William M. Richman et al.</author>


<category>Judicial Process</category>

</item>






<item>
<title>Elitism, Expediency, and the New Certiorari: Requiem for the Learned Hand Tradition</title>
<link>http://works.bepress.com/william_reynolds/45</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/45</guid>
<pubDate>Tue, 22 Feb 2011 08:43:02 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William M. Richman et al.</author>


<category>Judicial Process</category>

</item>






<item>
<title>Robert Leflar, Judicial Process, and Choice of Law</title>
<link>http://works.bepress.com/william_reynolds/44</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/44</guid>
<pubDate>Tue, 22 Feb 2011 08:43:01 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds et al.</author>


<category>Conflict of Laws</category>

</item>






<item>
<title>Studying Deck Chairs on the Titanic</title>
<link>http://works.bepress.com/william_reynolds/43</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/43</guid>
<pubDate>Tue, 22 Feb 2011 08:42:59 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds et al.</author>


<category>Judicial Process</category>

</item>






<item>
<title>Why Teach International Family Law in Conflicts?</title>
<link>http://works.bepress.com/william_reynolds/42</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/42</guid>
<pubDate>Thu, 17 Feb 2011 05:12:37 PST</pubDate>
<description>
	<![CDATA[
	<p>[The author] sets forth a challenge to conflicts professors: to teach international family law in their conflict of laws classes.  At present, many conflicts professors avoid teaching international family law, in part because the study of this subject is complicated by several statutes addressing particularly difficult issues.  Ignorning international family law is unwise, because many United States citizens and lawyers are likely to confront such problems.</p>

	]]>
</description>

<author>William L. Reynolds</author>


<category>Conflict of Laws</category>

<category>Foreign Law</category>

</item>






<item>
<title>Limited Publication in the Fourth and Sixth Circuits</title>
<link>http://works.bepress.com/william_reynolds/41</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/41</guid>
<pubDate>Tue, 15 Feb 2011 13:00:41 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds et al.</author>


<category>Constitutional Law</category>

<category>Judicial Process</category>

</item>






<item>
<title>Juridical Cripples: Plurality Opinions in the Supreme Court</title>
<link>http://works.bepress.com/william_reynolds/40</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/40</guid>
<pubDate>Tue, 15 Feb 2011 13:00:40 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>John F. Davis et al.</author>


<category>Constitutional Law</category>

<category>Judicial Process</category>

</item>






<item>
<title>The Non-Precedential Precedent - Limited Publication and No-Citation Rules in the United States Courts of Appeals</title>
<link>http://works.bepress.com/william_reynolds/39</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/39</guid>
<pubDate>Mon, 14 Feb 2011 10:49:12 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds et al.</author>


<category>Judicial Process</category>

</item>






<item>
<title>The Proper Forum for a Suit: Transnational Forum Non Conveniens and Counter-Suit Injunctions in the Federal Courts</title>
<link>http://works.bepress.com/william_reynolds/38</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/38</guid>
<pubDate>Mon, 14 Feb 2011 07:41:28 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds</author>


<category>Judicial Process</category>

</item>






<item>
<title>What Happens When Parties Fail to Prove Foreign Law?</title>
<link>http://works.bepress.com/william_reynolds/37</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/37</guid>
<pubDate>Mon, 14 Feb 2011 07:41:27 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds</author>


<category>Foreign Law</category>

</item>






<item>
<title>An Evaluation of Limited Publication in the United States Courts of Appeals: The Price of Reform</title>
<link>http://works.bepress.com/william_reynolds/36</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/36</guid>
<pubDate>Mon, 14 Feb 2011 07:41:26 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds et al.</author>


<category>Judicial Process</category>

</item>






<item>
<title>Appellate Justice Bureaucracy and Scholarship</title>
<link>http://works.bepress.com/william_reynolds/35</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/35</guid>
<pubDate>Fri, 11 Feb 2011 11:46:37 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William M. Richman et al.</author>


<category>Constitutional Law</category>

</item>






<item>
<title>Electronic Contracting Cases 2009-2010</title>
<link>http://works.bepress.com/william_reynolds/34</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/34</guid>
<pubDate>Thu, 10 Feb 2011 10:28:10 PST</pubDate>
<description>
	<![CDATA[
	<p>This article, our sixth annual survey of electronic contracting cases, discusses the significant electronic contracting cases decided between June 15, 2009 and June 15, 2010. Over the past six years, the law of electronic contracts has matured, and the cases we discuss in this article show this maturation. The survey covers contract formation by the use of shrinkwrap, clickwrap and browsewrap terms, and contract formation by the exchange of e-mail messages.</p>

	]]>
</description>

<author>Juliet M. Moringiello et al.</author>


<category>Contracts</category>

<category>Cyberspace Law</category>

</item>






<item>
<title>What’s Software Got to Do with it? The ALI Principles of the Law of Software Contracts</title>
<link>http://works.bepress.com/william_reynolds/33</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/33</guid>
<pubDate>Thu, 10 Feb 2011 10:28:08 PST</pubDate>
<description>
	<![CDATA[
	<p>In May, 2009, the American Law Institute (“ALI”) approved its Principles of the Law of Software Contracts (“Principles”). The attempt to codify, or at least unify, the law of software contracts has a long and contentious history, the roots of which can be found in the attempt to add an Article 2B to the Uniform Commercial Code (“UCC”) in the mid-1990s. Article 2B became the Uniform Computer Information Transactions Act (“UCITA”) when the ALI withdrew from the project in 1999, and UCITA became the law in only two states, Virginia and Maryland. UCITA became a dirty word, with several states enacting “bomb shelter” provisions to ensure that UCITA would never enter those states by way of a choice of law clause. Although the Principles were conceived, in part, as a counterweight to UCITA, the latter was dead in the water by the time the Principles project became active. Nevertheless, the Principles project proceeded apace. This Article examines the results of that decision.</p>
<p>The proponents of efforts to formulate a body of law for software contracts tend to insist that such a body of law is necessary because software transfers, as transfers of copies of information, are different from transfers of goods, and these differences make the common law of contracts and Article 2 of the UCC inappropriate bodies of law to govern software contracts. The ALI Principles constitute the latest attempt at such unification, and in this article, we argue that there is little in the Principles that addresses any unique characteristics of software. Neither one of us was involved in the Article 2B/UCITA project, so we approach this problem by looking at the law as it existed at the time the Principles project started instead of looking at the law at the time Article 2B was conceived.</p>

	]]>
</description>

<author>Juliet M. Moringiello et al.</author>


<category>Contracts</category>

</item>






<item>
<title>Tributes to Professor Alan Hornstein</title>
<link>http://works.bepress.com/william_reynolds/32</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/32</guid>
<pubDate>Thu, 10 Feb 2011 10:28:07 PST</pubDate>
<description>
	<![CDATA[
	<p>Tributes to Professor Alan Hornstein upon his retirement from the University of Maryland School of Law.</p>

	]]>
</description>

<author>David S. Bogen et al.</author>


<category>Tribute</category>

</item>






<item>
<title>The Straight-Line Method of Determining Personal Jurisdiction</title>
<link>http://works.bepress.com/william_reynolds/31</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/31</guid>
<pubDate>Thu, 10 Feb 2011 10:28:06 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>John M. Brumbaugh et al.</author>


<category>Judicial Process</category>

</item>






<item>
<title>Legal Process and the Past of Antitrust</title>
<link>http://works.bepress.com/william_reynolds/30</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/30</guid>
<pubDate>Thu, 10 Feb 2011 10:28:04 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds et al.</author>


<category>Antitrust Law</category>

</item>






<item>
<title>Prologomenon to an Empirical Restatement of Conflicts</title>
<link>http://works.bepress.com/william_reynolds/29</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/29</guid>
<pubDate>Thu, 10 Feb 2011 10:28:02 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William M. Richman et al.</author>


<category>Conflict of Laws</category>

</item>






<item>
<title>Back to the Future in Law Schools</title>
<link>http://works.bepress.com/william_reynolds/28</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/28</guid>
<pubDate>Wed, 02 Feb 2011 13:12:01 PST</pubDate>
<description>
	<![CDATA[
	
	]]>
</description>

<author>William L. Reynolds</author>


<category>Legal Education</category>

</item>






<item>
<title>What&apos;s Software Got To Do With It?  The ALI Principles of the Law of Software Contracting</title>
<link>http://works.bepress.com/william_reynolds/26</link>
<guid isPermaLink="true">http://works.bepress.com/william_reynolds/26</guid>
<pubDate>Mon, 15 Mar 2010 06:47:16 PDT</pubDate>
<description>
	<![CDATA[
	<p>In May, 2009, the American Law Institute (“ALI”) approved its Principles of the Law of Software Contracts (“Principles”). The attempt to codify, or at least unify, the law of software contracts has a long and contentious history, the roots of which can be found in the attempt to add an Article 2B to the Uniform Commercial Code (“UCC”) in the mid-1990s. Article 2B became the Uniform Computer Information Transactions Act (“UCITA”) when the ALI withdrew from the project in 1999, and UCITA became the law in only two states, Virginia and Maryland. UCITA became a dirty word, with several states enacting “bomb shelter” provisions to ensure that UCITA would never enter those states by way of a choice of law clause. Although the Principles were conceived, in part, as a counterweight to UCITA, the latter was dead in the water by the time the Principles project became active. Nevertheless, the Principles project proceeded apace. This Article examines the results of that decision.</p>
<p>The proponents of efforts to formulate a body of law for software contracts tend to insist that such a body of law is necessary because software transfers, as transfers of copies of information, are different from transfers of goods, and these differences make the common law of contracts and Article 2 of the UCC inappropriate bodies of law to govern software contracts. The ALI Principles constitute the latest attempt at such unification, and in this article, we argue that there is little in the Principles that addresses any unique characteristics of software. Neither one of us was involved in the Article 2B/UCITA project, so we approach this problem by looking at the law as it existed at the time the Principles project started instead of looking at the law at the time Article 2B was conceived</p>

	]]>
</description>

<author>Juliet M. Moringiello et al.</author>


<category>Cyberspace Law</category>

</item>





</channel>
</rss>

