SSRN Home Search and Download Papers Browse Abstract and Paper Submission Subscribe to Networks View Briefcase Top Papers Top Authors Top Institutions

 

Abstract

 
 

Footnotes (238)

Beta

 


 



Patterns of Drafting Errors in the Uniform Commercial Code and How Courts Should Respond to Them

Gregory E. Maggs
George Washington University Law School



University of Illinois Law Review, Vol. 81, 2002
GWU Law School Public Law Research Paper No. 379
GWU Legal Studies Research Paper No. 379

Abstract:     
This article identifies eight recurring patterns of drafting in the Uniform Commercial Code (UCC). For each of these patterns, and for other idiosyncratic errors, the article recommends specific judicial responses. These responses take advantage of many of the UCC's unique characteristics. While the problem of drafting errors in the UCC may seem minor in light of the model code's high overall quality, the suggested responses can lead to a more efficient and effective application of the statute.

Keywords: UCC, U.C.C., Uniform Commercial Code, legislative drafting, drafting errors, statutory interpretation

JEL Classifications: K12

Accepted Paper Series

Date posted: June 15, 2005 ; Last revised: November 28, 2007

Suggested Citation

Maggs, Gregory E., Patterns of Drafting Errors in the Uniform Commercial Code and How Courts Should Respond to Them. University of Illinois Law Review, Vol. 81, 2002; GWU Law School Public Law Research Paper No. 379; GWU Legal Studies Research Paper No. 379. Available at SSRN: http://ssrn.com/abstract=742713


Export to: Export Citation What's this?

Contact Information

Gregory E. Maggs (Contact Author)
George Washington University Law School ( email )
2000 H Street, N.W.
Washington, DC 20052
United States
Feedback to SSRN (Beta)


Paper statistics
Abstract Views: 988
Downloads: 113
Download Rank: 75,462
Footnotes: 238

© 2010 Social Science Electronic Publishing, Inc. All Rights Reserved.  FAQ   Terms of Use   Privacy Policy   Copyright
This page was served by apollo6 in 0.140 seconds.