[ Main | List
of Articles | Bad Software | UCITA | Law of Software
Quality | Digital Signatures | Bookstore | Court Cases
| Links | Press
Releases | About Us | What's
New ]
UCITA
main document. See also
recent amendments to UCITA. See also NCCUSL's
comments on UCITA.
UCITA is a proposed law that will govern all contracts for
the development, sale, licensing, support and maintenance of computer
software and for many other contracts involving information. It
also extends easily (vendor's choice) to sales of computers and
computer peripherals and probably extends to many types of embedded
software, such as the fuel injectors in your car.
UCITA was initially proposed as an amendment to the Uniform
Commercial Code, which is co-authored by NCCUSL
(the National Conference of Commissioners on Uniform State Laws)
and the ALI (American Law Institute). That project (UCC Article
2B) ended when ALI walked out, after repeatedly calling for fundamental
revisions over a three year period (objecting primarily that UCITA's
approach takes away key customer rights, limits competition, and
conflicts with federal policies on innovation and fair use of
copyrighted materials.) NCCUSL renamed the bill, adopted it in
July 1999, primarily with the support of software and information
publishers. UCITA recently passed in Virginia and Maryland. It
will be under consideration in many additional state legislatures
this year.
This page links you to our analyses and to a few analyses by
other writers that we think are particularly helpful. For the
vendors' / proponents side, see Carol Kunze's sites. www.ucitaonline.com
for current news and www.2bguide.com
for archival materials, including some of the customer-side documents.
The primary opposition organization to UCITA is now the 4CITE
coalition. Additional information is available at the National Consumer Law Center page
(there's no direct link to the page, go to www.nclc.org, then
to Special Initiatives, then to UCITA.). James
Huggins' site, and the
IEEE-USA site are also pretty useful.
Articles
You probably can't read all of these. We have italicized the
ones we think are the best ones.
Gentle Introductions
Detailed Analyses
- Software Engineering & UCITA.
(J. Computer Law, Winter 1999) A thorough analysis of
UCITA from the software engineer's viewpoint rather than from
a consumer viewpoint.This is my (Kaner's) primary research document.
100 pages, 325 footnotes.
- Analysis for the Federal Trade
Commission by Kaner & Pels. (Septemer, 2000).
UCITA will pull software out of the scope of several consumer
protection laws including the Magnuson Moss Act. The FTC is investigating
the desirability of this. This paper raises new issues involving
embedded software.
- Why You Should Oppose UCITA,
(Computer Lawyer, 2000) an outline of reasons the
legal community should oppose UCITA.
- DUELING ARTICLES in Software Quality Professional. Kaner
(original), Brennan
(response and 2nd article combined), Kaner
(response).
- Article
2B: Report from the November 13-15, 1998 Meeting
(Kaner, UCC Bulletin, Jan 1999 & Feb 1999) The results
of this meeting strikingly show the bias of the drafting committee.
- Comments
on Article 2B: (Kaner, memo to Article 2B drafting
committee, October 1998) Detailed section-by-section analysis
of the problems of 2B in response to a request from the Chair
for detailed, specific proposals.Written from the perspective
of customers and writers.
- Bad Software: Who
is Liable. (Kaner, Invited / keynote address to Quality
Assurance Institute and to American Society for Quality, May
/ June 1998). In-depth background and analysis of quality-related
effects of Article 2B.
- Article 2B is Fundamentally
Unfair to Mass-Market Software Customers (Kaner, memo to
American Law Institute, October, 1997) Analysis for ALI executive
meeting.
- Proposed
Article 2B: Problems from the Customer's View. Part 2: List of
Key Issues, (Kaner, UCC Bulletin February 1997.)
- Proposed
Article 2B: Problems from the Customer's View. Part 1: Underlying
Issues, (Kaner, UCC Bulletin January 1997.) This article
was written for the Article 2B Drafting Committee at its meeting
on September 27-29, 1996. It examines several fundamental issues
in the Draft, using them to show the extent to which the Draft
is biased against customers.
Consumer Issues
- Analysis for the Federal Trade
Commission by Kaner & Pels. (Septemer, 2000).
UCITA will pull software out of the scope of several consumer
protection laws including the Magnuson Moss Act. The FTC is investigating
the desirability of this. This paper raises new issues involving
embedded software.
- Nondisclosure
and UCITA. (Kaner, NCCUSL Annual Meeting, July 1999). Despite
claims to the contrary, the current wording of UCITA will make
it riskier for journalists and customers to write comparative
reviews or criticisms of software products.
- Comments
on Article 2B: (Kaner, memo to Article 2B drafting
committee, October 1998) Detailed section-by-section analysis
of the problems of 2B in response to a request from the Chair
for detailed, specific proposals.Written from the perspective
of customers and writers.
- Consumer Concerns About
Article 2B (Kaner, ABA Convention, August 1998)
- A Bad Law
for Bad Software. (Kaner, UC Berkeley Conference on the Impact
of Article 2B of the UCC on the Future of Transactions in Information
and Electronic Commerce. Spring, 1998.)
- Consumer Issues and Article
2B (Kaner, Paglia, memo to American Law Institute, December,
1997). Top 10 list of issues.
- Article 2B is Fundamentally
Unfair to Mass-Market Software Customers (Kaner, memo to
American Law Institute, October, 1997) Analysis for ALI executive
meeting.
- Software
Customer Dissatisfaction (Kaner &
Pels, memo to Article 2B drafting committee March, 1997) A thorough
collection of statistics on customer dissatisfaction in the mass
market.
- Liability
for Bad Software and Support (Kaner, Executive Briefing,
Software Support Professionals Assoc, March 1999)
Writers' Issues
- Nondisclosure
and UCITA. (Kaner, NCCUSL Annual Meeting, July 1999). Despite
claims to the contrary, the current wording of UCITA will make
it riskier for journalists and customers to write comparative
reviews or criticisms of software products.
- Why Writers Should
Actively Oppose The Uniform Computer Information Transactions
Act. (Kaner, National Writers Union Annual Delegates Assembly,
June 19, 1999)
- Comments
on Article 2B: (Kaner, memo to Article 2B drafting
committee, October 1998) Detailed section-by-section analysis
of the problems of 2B in response to a request from the Chair
for detailed, specific proposals.Written from the perspective
of customers and writers.
Software Developers' Issues
- Software Engineering & UCITA.
(J. Computer Law, Winter 1999) A thorough analysis of
UCITA from the software engineer's viewpoint rather than from
a consumer viewpoint.This is my (Kaner's) primary research document.
100 pages, 325 footnotes.
- DUELING ARTICLES in Software Quality Professional. Kaner
(original), Brennan
(response and 2nd article combined), Kaner
(response).
- Article
2B and Reverse Engineering. (Kaner,
Uniform Commerical Code Bulletin, November, 1998.) (Legal audience)
Explains the nature of reverse engineering and why people do
it. Article 2B continues (February 1999) to make it easy for
publishers to ban reverse engineering. The court challenge to
such a ban would be expensive, fact specific, and very uncertain
of success. This reflect bad underlying policy, a mistake that
will seriously harm the industry.
- The Problem
of Reverse Engineering. Software QA Magazine, 1998 (Engineering
audience.)
- Restricting
Competition in the Software Industry: Impact of the Pending Revisions
to the Uniform Commercial Code. (Kaner, Ralph Nader's
Microsoft conference, November, 1997.)Some of the details are
out of date, but the main problems are all still there. This
has been a useful introduction / summary for (especially) software
engineers.
- Uniform Commercial
Code Article 2B: A New Law of Software Quality, (Kaner, Software
QA magazine, April 1996) Overview for software developers.
Large Customer Issues
Defects, Software Quality
- Software Engineering & UCITA.
(J. Computer Law, Winter 1999) A thorough analysis of
UCITA from the software engineer's viewpoint rather than from
a consumer viewpoint.This is my (Kaner's) primary research document.
100 pages, 325 footnotes.
- Nondisclosure
and UCITA. (Kaner, NCCUSL Annual Meeting, July 1999). Despite
claims to the contrary, the current wording of UCITA will make
it riskier for journalists and customers to write comparative
reviews or criticisms of software products.
- Letter to NCCUSL
from Software Engineering Institute (July, 1999)
- Letter to NCCUSL from software-test-discuss (this is the
Nets largest e-mail discussion forum on software quality
control www.badsoftware.com/swtest.htm)
- Nondisclosure
and UCITA. (Kaner, NCCUSL Annual Meeting, July 1999). Despite
claims to the contrary, the current wording of UCITA will make
it riskier for journalists and customers to write comparative
reviews or criticisms of software products.
- Bad Software: Who
is Liable.(Kaner, Invited / keynote address to Quality
Assurance Institute and to American Society for Quality, May
/ June 1998). In-depth background and analysis of quality-related
effects of Article 2B.
- SPLAT! Requirements
Bugs on the Information Superhighway (Kaner, Lawrence, Johnson,
Software QA, 1998).
- Legal
Issues and Software Quality: (Kaner, Keynote address to annual
meeting of the Software Division of the American Society for
Quality, October 1997). Background on commercial law, software
contract law.
- Impossibility of Complete
Testing, (Kaner, prepared for annual
NCCUSL meeting, August 1997; Published in Software QA magazine.)
Be cautious about demanding perfection as a legal standard because
it is impossible to tell, at time of release, whether the product
is defect-free.
- Software
Customer Dissatisfaction (Kaner &
Pels, memo to Article 2B drafting committee March, 1997) A thorough
collection of statistics on customer dissatisfaction in the mass
market.
- Not Quite Terrible
Enough Software: (Kaner: Remarks at the 1997 Software Engineering
Process Group Conference, March 1997). This paper accompanied
a joint presentation with Ray Nimmer. It reviews the issues from
the perspective of the quality-conscious software engineer, and
looks at the issue of quality-related tradeoffs. Article 2B provides
no disincentives for selling products with serious, known errors.
- What
is a Serious Bug? Defining a "Material Breach" of a
Software License Agreement, (Kaner,
Software QA magazine, January 1997)
- Watts
Humphrey writes about Article 2B. July, 1997.
Electronic Commerce
and Digital Signatures
- E-Commerce Provisions in
the UCITA and UETA (Kaner, July 1999) Compares the two draft
laws.
- Analysis
of E-Commerce Issues for the FTC (Kaner, April 1999) Digital
signatures, e-mail receipt, other issues.
- SPLAT!
Requirements Bugs on the Information Superhighway
(Kaner, Lawrence, Johnson, Software QA, 1998).
- Notes on E-Mail Receipt
(Kaner, Johnson, analysis for Uniform Electronic Transactions
Act committee, January 1998) Looks at where a message can be
lost or corrupted in the flow from sender to receiver. The underlying
question is, at what point do we say, "If it has reached
here, it should be legally considered to have been received by
the person it was sent to?"
- The Insecurity of Digital
Signatures (Kaner, e-mail report, September 1997).
First look at the problem of user identify fraud using digital
signatures, and the problems in UETA (since corrected) and UCC
Article 2B.
- Privacy
Problems in Article 2B (Kaner, Drafting Committee November
1996)
Self Help (Vendor's ability to unilaterally
shut down a customer, without court review)
Drafting Process
- Article
2B and Consumers. (Kaner, Annual Meeting of NCCUSL, July,
1998). Top 10 list of consumer-side proposals circulated at 1998
NCCUSL meeting.
- Letter to
Connie Ring Regarding Publicity and Negotiations in Article 2B,
(Kaner, letter, March 1997). The claims that critics of UCITA
(Article 2B) were misrepresenting the facts and were unfairly
using publicity started in early 1997, with a nasty series of
personal attacks on Todd Paglia (Ralph Nader's lawyer, who has
since left the project). I was not yet being personally attacked
this way. I stepped in, on the phone and in this memo, trying
to restore the amicable style that is most fruitful for negotiation.
General Background
- Software Engineering & UCITA.
(J. Computer Law, Winter 1999) A thorough analysis of UCITA from
the software engineer's viewpoint rather than from a consumer
viewpoint.This is my (Kaner's) primary research document. 100
pages, 325 footnotes.
- Analysis for the Federal Trade
Commission by Kaner & Pels. (Septemer, 2000).
UCITA will pull software out of the scope of several consumer
protection laws including the Magnuson Moss Act. The FTC is investigating
the desirability of this. This paper raises new issues involving
embedded software.
- Why You Should Oppose UCITA,
(Computer Lawyer, 2000) an outline of reasons the
legal community should oppose UCITA.
- Bad Software: Who
is Liable. (Kaner, Invited / keynote addresses to
Quality Assurance Institute and to American Society for Quality,
May / June 1998). In-depth background and analysis of quality-related
effects of Article 2B.
- Restricting
Competition in the Software Industry: Impact of the Pending Revisions
to the Uniform Commercial Code. (Kaner, Ralph Nader's
Microsoft conference, November, 1997.) Some of the details
are out of date, but the main problems are all still there. This
has been a useful introduction / summary for (especially) software
engineers.
- Legal
Issues and Software Quality: (Kaner, Keynote, annual meeting
of the Software Division of the American Society for Quality,
October 1997) Background on commercial law, software contract
law.
- Software
Liability. (Kaner,
Pacific Northwest Software Quality Conference, October, 1997.)
The unique piece to get out of this paper is the look
at legislative drafting as product development. Drafts of laws
are products, with conflicting requirements, constraints on what
can be achieved, and bugs.
- Uniform Commercial
Code Article 2B: A New Law of Software Quality, (Kaner, Software
QA magazine, April 1996) Overview for software developers.
Background on UCITA (Kaner
& Pels, July 1999)
The Uniform Computer Information Transactions Act (UCITA) is
a long, complex law that will govern all contracts for the development,
sale, licensing, maintenance, and support of computer software,
plus most contracts for information (such as books) in digital
form. Vendors of other products that contain software, such as
computers, can also bring their products within the scope of UCITA,
rather than Article 2 of the Uniform Commercial Code, a law that
is much friendlier to consumers and small businesses.
In various forms, UCITA has been under development for about
12 years. For the last four years, it was called Article 2B and
was drafted as a proposed amendment to the Uniform Commercial
Code.
The strength of UCITA is that it creates a uniform law governing
a wide range of transactions. It unifies the laws across the states
and it resolves some differences in legal treatment of computer-related
services and sales/licensing of packaged software.
The problem with UCITA is that the drafting has been dominated
by lobbyists for software publishers. The drafting committee is
independent of these companies and is trying in good faith to
write a decent bill. But committee members (and its chair) have
repeatedly expressed the belief that the bill cannot pass without
the support of The Industry, and The Industry (trade associations
lobbyists) has repeatedly threatened to withdraw its support if
this or that position was not written into (or kept in) the draft
law.
Dont get us wrong about this. Weve worked in the
software industry (usually as managers) for most of our adult
lives. We appreciate NCCUSL's enthusiasm for protecting America's
fastest growing industry. But when a legislative drafting committee
lets itself be too heavily influenced by a single industrys
lawyers, the result is a law that is just too imbalanced. Over
the past four years, we (and many others) repeatedly proposed
compromises or alternatives that we believed were win-win solutions.
The results were negligible. Look at our detailed analyses of
September 1996 (part
1, part
2), October 1997,
December 1997,
August 1998,
October 1998
and November,
1998. The same issues came up year after year, with no genuine
progress, year after year.
There are many analyses in the articles, and we encourage you
to read them. But to give you a taste, here are just a few examples
of the rules under UCITA:
- Suppose you buy a computer game. When you've finished playing
it, suppose that you want to take it off of your computer and
give it to your sister. Under the law today, this is just like
buying a book or a record--you can't make a copy to keep for
yourself, but you can give away the one that you bought or you
can lend it to a friend or sell it used. Under UCITA, the publisher
can say you can't sell the software used, lend it or give it
away. Book publishers tried to restrict post-sale reselling of
books a century ago. A feisty little retailer called Macy's took
them on, and the United States Supreme Court invalidated these
restrictions. UCITA's grant of new intellectual property rights
to mass-market sellers is one of many reasons that the main American
library associations oppose UCITA.
- Suppose your new computer game doesn't work. You call for
help. The software company charges $3 per minute to talk to you.
After half an hour ($90), you realize the company won't help
you. You ask for a refund and return the product. Under UCITA,
the company can send you the $40 you paid for the game but keep
the $90 you spent on the phone call. You'd have been better off
throwing the game away. This is one of many ways in which UCITA
lets software companies avoid responsibility for their defects,
even for defects they know about when they sell the product.
Even for defects that they know about and choose not to tell
the customer about. Many software developers believe that this
rule threatens the professionalism of their work. It is one of
the reasons that the main developers' professional societies
(including the Association for Computing Machinery and the Institute
for Electrical and Electronic Engineers) oppose UCITA or have
expressed serious concerns about it. Similar opposition comes
from quality control professionals.
- Suppose that a software company demonstrates a product at
a trade show. You order the product at the show. The product
you receive has different screens, is harder to use and less
capable. Today, when a software company demonstrates a product,
it creates a warranty that the product you get will be the same,
work the same, and have the same capabilities as the one demonstrated.
UCITA eliminates this warranty for the display layout and commands)
and cuts it back for functionality.
Backers of UCITA insist that it leaves consumers and small
businesses with our existing rights, and gives us new ones. But
it doesn't. That's why every consumer advocate we know (including
Consumers Union and Ralph Nader's Consumer Project on Technology)
has called for termination of the UCITA project. A July
9, 1999 analysis by the Federal Trade Commission points out
that UCITA allows software companies to place "restrictions
on a consumers right to sue for a product defect, to use
the product, or even to publicly discuss or criticize the product."
The analysis concludes, "we question whether it is appropriate
to depart from these consumer protection and competition policy
principles in a state commercial law statute."
Please write a letter to your governor and state legislators.
Your input will be noticed.
The articles at this web site are not legal advice. They do
not establish a lawyer/client relationship between me and you.
I took care to ensure that they were well researched at the time
that I wrote them, but the law changes quickly. By the time you
read this material, it may be out of date. Also, the laws of the
different States are not the same. These discussions might not
apply to your circumstances. Please do not take legal action on
the basis of what you read here without consulting your own attorney.
Please direct questions or problems regarding this web site
to Cem Kaner, Professor,
Department of Computer Sciences, Florida Institute of Technology,
150 West University Blvd., Melbourne, FL 32901-6975.
Last modified: September 16, 2000. Copyright ©
1997-2000, Cem Kaner.
All rights reserved.