Back | WP 6.1 Version | ASCII Version | PDF Version
To: Uniform Electronic Transactions Act Drafting Committee and Observers.
From: Ben Beard, Reporter.
Date: September 18, 1998.
Re: Fifth Draft of The Uniform Electronic Transactions Act - General Comments and Issues.
Enclosed is the fifth draft (including the Annual Meeting Draft) of the Uniform Electronic Transactions Act (the "Act"). This draft has been revised from the March 23, 1998 Draft discussed at the April, 1998 meeting of the Drafting Committee in Washington D.C., and also includes some changes from the 1998 Annual Meeting Draft.
Following the Annual Meeting, Chair Fry and I discussed the content of the draft to be presented in Rapid City. Since the Drafting Committee had not reviewed and commented on the changes made in the Annual Meeting draft, and it appeared that we would not have full attendance by all members of the Committee for all or part of the meeting in Rapid City, we initially considered simply presenting the Annual Meeting draft for discussion in Rapid City. However, certain provisions required obvious redrafting in light of the Committee's directions at the April meeting (e.g., Sections 202, 203 and 302). Further, drafts of the Report of the Task Force on Scope have been available in time to consider addressing some of its recommendations in this Draft. Finally, the intention to have this Act ready for final reading next summer, suggested that some changes and alternatives be presented to the Drafting Committee in Rapid City, in order to move the process along.
The enclosed draft has been marked to show changes from the March 23, 1998 draft. Changes from, and alternatives to, the Annual Meeting Draft are also reflected in this draft. These changes or alternatives have been discussed in the "Reporter's Note to this Draft" following the affected sections. I have done everything possible to present the changes in the clearest manner possible. To the extent any changes were missed in the marking, it was inadvertent and entirely my responsibility.
PRINCIPAL ISSUES IN THIS DRAFT.
Although the Drafting Committee deleted presumptions from this Act in April, there remain advocates of the need for presumptions, on the ground that the law needs to provide direct legal incentives to use and implement reasonable security procedures. The concern over deletion of presumptions is that parties will be less motivated to implement good security procedures without the benefit of legal presumptions.
On the other hand there are those who assert that, in the absence of legally created presumptions, parties will have even greater incentives to implement reasonable, reliable, robust procedures at the lowest cost commensurate with the types of risk inherent in the particular type of transaction. From a legal perspective, these incentives are indirect, based on evidentiary considerations relating to the ability to prove the source and content of an electronic record or signature. Without such procedures, those seeking to enforce electronic records and signatures will have difficulty establishing for a finder of fact that a given electronic record or signature is in fact that of the other party, or accurately presents the information conveyed.
Moreover, the existence of a presumption does not necessarily permit early resolution of litigation through summary judgment. In the face of a denial by the party to be bound, a bursting bubble presumption is exploded and of no aid to the proponent. If a stronger presumption which shifts the burden of persuasion is adopted, the party to be bound can avoid summary judgment by denying the reasonableness of the procedure, thereby creating a question of fact as to the predicate for obtaining the benefit of the presumption. Finally, once the reasonableness of the procedure is established, the need for the presumption largely evaporates, since the inference to be drawn from a reasonable procedure will be that the record or signature is that of the party to be bound.
Finally it is important to remember that there are also self-interested, business reasons for parties to implement strong procedures. Parties using electronic commerce have a natural desire to avoid fraudulent transactions which can be prevented by reasonable means. Particularly when dealing with customers unfamiliar with, and perhaps wary of, electronic media, it is in business' interest to develop reasonable procedures to assure and convince people that electronic commerce is safe and reliable. Creation of legal presumptions may have the unintended consequence of skewing the natural development of technology which best addresses these needs based on reasonable decisions weighing the cost of the technology against the goals the technology is intended to accomplish.
Although the Drafting Committee has expressed its view on presumptions, this remains a critical issue in light of the continued existence of presumptions in the electronic contracting provisions of Article 2B.
This reorganization was not implemented in this draft to prevent confusion. This draft reflects changes from the March 23 draft through the Annual Meeting Draft and from the Annual Meeting Draft to this draft. Adding a major reorganization was viewed as too much at this time. I will implement the reorganization in the next draft.
Aside from the foregoing, the "Reporter's Note to this Draft" following several sections, highlight issues new to this draft. In addition, there are a number of minor issues (e.g., the standard of reliability in Section 205) which can be addressed at the meeting with, hopefully, a minimum of controversy.
I look forward to our meeting October 9-11 and moving the project forward.
SECTION 101. SHORT TITLE.
SECTION 102. DEFINITIONS.
SECTION 103. SCOPE.
SECTION 104. SCOPE - EXCLUSIONS AND LIMITATIONS.
SECTION 105. VARIATION BY AGREEMENT.
SECTION 106. APPLICATION AND CONSTRUCTION.
SECTION 107. MANIFESTING ASSENT.
SECTION 108. OPPORTUNITY TO REVIEW.
SECTION 109. DETERMINATION OF REASONABLE SECURITY PROCEDURE.
SECTION 110. EFFECT OF REQUIRING UNREASONABLE SECURITY PROCEDURE.
SECTION 111. LEGAL RECOGNITION OF ELECTRONIC RECORDS, ELECTRONIC SIGNATURES AND ELECTRONIC CONTRACTS (Combines Sections 201, 301 and 401(c)).
SECTION 112. ATTRIBUTION OF ELECTRONIC RECORD TO PARTY.
SECTION 113. DETECTION OF CHANGES AND ERRORS.
SECTION 114. INADVERTENT ERROR.
SECTION 115. EFFECT OF ELECTRONIC SIGNATURES (formerly 302).
SECTION 116. OPERATIONS OF ELECTRONIC DEVICES. (Formerly 303)
SECTION 117. NOTARIZATION AND ACKNOWLEDGMENT (formerly 304).
SECTION 118. ORIGINALS - INFORMATION ACCURACY.
SECTION 119. RETENTION OF ELECTRONIC RECORDS.
SECTION 120. ADMISSIBILITY INTO EVIDENCE (formerly 404).
SECTION 121. CONTRACT FORMATION AND VALIDITY.
SECTION 122. TIME AND PLACE OF SENDING AND RECEIPT.
SECTION 123. ELECTRONIC ACKNOWLEDGMENT OF RECEIPT.
SECTION 124. TRANSFERABLE RECORDS.
SECTION 201. CREATION AND RETENTION OF ELECTRONIC RECORDS AND CONVERSION OF WRITTEN RECORDS BY GOVERNMENTAL AGENCIES.
SECTION 202. RECEIPT AND DISTRIBUTION OF ELECTRONIC RECORDS BY GOVERNMENTAL AGENCIES.
SECTION 203. [DESIGNATED STATE OFFICER] TO ADOPT STATE STANDARDS.
SECTION 204. INTEROPERABILITY.
SECTION 301. SEVERABILITY.
SECTION 302. EFFECTIVE DATE.
SECTION 303. SAVINGS AND TRANSITIONAL PROVISIONS.