Jump to content

Uniform Computer Information Transactions Act

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Yobot (talk | contribs) at 18:30, 5 December 2012 (clean up, References after punctuation per WP:REFPUNC and WP:PAIC using AWB (8748)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Uniform Computer Information Transactions Act (UCITA) was an attempt to introduce a Uniform Act for US States to follow. As a model law, it only specifies a set of guidelines, and each of the States should decide if to pass it or not, separately. UCITA has been drafted by National Conference of Commissioners on Uniform State Laws (NCCUSL).[1]

UCITA has been designed to clarify issues which were not addressed by existing Uniform Commercial Code. "Few disagree that the current Uniform Commercial Code is ill-suited for use with licensing and other intangible transactions," said practicing attorney Alan Fisch.[2]

UCITA has faced severe opposition from various groups.[3] [4] .[5]

UCITA has only been passed in two states, Virginia and Maryland. The law did not pass in other states.[2] Nevertheless, legal scholars, such as noted commercial law professor Jean Braucher, believe that the UCITA offers academic value.[2]

A resolution recommending approval of UCITA by the American Bar Association (ABA) has been withdrawn by the NCCUSL in 2003, indicating that UCITA lacks the consensus which is necessary for it to become an uniform law.[6]

Provisions

UCITA focuses on adapting current commercial trade laws to the modern software era. It is particularly controversial in terms of computer software. The code would automatically make a software maker liable for defects and errors in the program. However, it allows a shrinkwrap license to override any of UCITA's provisions. As a result, commercial software makers can include such a license in the box and not be liable for errors in the software. Free software that is normally distributed through downloads, however, would not be able to force a shrinkwrap license and would therefore be liable for errors. Small software makers without legal knowledge would also be at risk.[3]

UCITA would explicitly allow software makers to make any legal restrictions they want on their software by calling the software a license in the EULA, rather than a sale. This would therefore take away purchasers right to resell used software under the first sale doctrine. Without UCITA, courts have often ruled that despite the EULA claiming a license, the actual actions by the software company and purchaser clearly shows it was a purchase, meaning that the purchaser has the right to resell the software to anyone.

History

UCITA has started as an attempt to modify Uniform Commercial Code, by introducing new article (Article 2B), also known as UCC2B.[1] Committee for drafting UCC2B consisted of both members from NCCUSL and members of American Law Institute (ALI). At certain stage of the process, ALI has withdrawn from the drafting process, effectively killing UCC2B. Afterwards, NCCUSL has renamed UCC2B into UCITA and proceeded on its own.[1]

Passage Record

Before ratification, each state may amend its practices, thus specific effects may be somewhat different in each state. This means that the final "as read" UCITA document is what is actually passed and signed into law by each state governor. The passage record typically indicates each version of UCITA submitted for ratification.

References

See also