Sunday, June 26, 2011

Garbage-in, Quality-out

The common think expression “garbage-in, garbage-out” is often thrown out without any vigorous thought. Proponents believe it just has to be true.

First, I have to agree with Charles Babbage who famously said: "On two occasions, I have been asked [by members of Parliament], 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able to rightly apprehend the kind of confusion of ideas that could provoke such a question."

Second, if we do try to make some sense of the concept, the expression can hold true only if all the source materials are completely rubbish. I believe there is much to be learned from all sources of information. If there are any gems in the collection, then there is the possibility that “good” material can be identified. Indeed, we are all exposed to an enormous amount of data. How well we process this information depends on the sophistication of our filters. And, machines can also develop filters. IBM’s Watson, the Jeopardy playing computer, deduced mostly correct answers from unwashed Internet resources—and it trounced its human competitors.

Third, while the expression has been applied to legal agreements, such as those filed on EDGAR, for my part, I do not think of any of them as garbage. They are precedents. They are expressions of real transactions.

Fourth, common thinkers tend to fixate on language, sometimes debating the difference between ‘will’, ‘shall’ and ‘must’. While this is important, there are many other dimensions to legal agreements, including—and most importantly—the application of legal terms to business transactions. In fact, it is not uncommon for those focusing on the words to miss some key clause or accidentally duplicate clause language. Without a broader view—a checklist—we cannot see the forest for the trees.”

Fifth, and most importantly, we can now see the power of aggregation and filters in practice. Contract analysis reviews a set of agreements and determines how the document is organized, what clauses it contains, and the range of standard and non-standard language. The first task of contract analysis is to aggregate all the source documents into one common outline, creating the agreement checklist. Next, the analysis finds all the matching clause elements, and for each branch of the outline, it constructs a clause library. Finally, algorithms examine all the clauses and identify the core (non-negotiated or deal neutral) language for each provision, together with the full range of deal-specific or alternative terms.

When creating a new model form, the process will sometimes start by identifying the most conforming document in the set: the one containing the most common clause elements and the most standard language. This is done for reasons of expediency. If we start with single conforming document, then we can spend less time normalizing the clause language, and particularly the definitions. (See The Fastest Way to Create a Form).

However, situations arise where we do not find a good (or conforming) document containing all the standard elements of a transaction. These situations are quite apparent from the software analysis. The software shows the source agreements are highly divergent in structure and content. If there are no good examples, then we can assume that we face a situation of sub-optimal source documents. In this case we can use contract analysis to identify the most common deal elements and for each provision find the most conforming clause. The remarkable result is that while no one document represents best practice, the aggregate of all documents does. Or, to end with another bumper-sticker expression: we are smarter than me.”

In conclusion, part of reason for a shift from wordsmithing to transactional analysis is an expanding world view. When our world is limited to handful of precedents that we personally drafted or gathered from trusted colleagues, this tiny universe can be carefully dissected word-by-word. In the last few years, our universe has massively expanded to include all documents filed on EDGAR, enormous volumes financial transactions, and vast collections of agreements generated from an interconnected global marketplace.

We cannot be masters of the digital universe based solely on our personal reading experiences.

Friday, June 24, 2011

Intellectual Property Rep

The Intellectual Property Representation (on ContractStandards) appears to have been built over time, incrementally adding more and more language. All clauses example share common elements, such as the disclosure of registered IP, declaration of rights of ownership and representations regarding non-infringement. However, with respect to less frequently appearing clause elements there is a very wide range of optional provisions and little consistency in their occurrence. The result is a listing of overlapping representations, without a clear reference to what technology platforms they apply, other than a generic concept of “intellectual property” that spans everything from inchoate ideas to commercial software packages.

The proposed organizing theme (a work in progress) builds the clause components from a business framework, offering a matrix of configurable clause components that can be inserted if applicable to the representing party.


Disclosure
Ownership
Warranties
Sufficiency
IP Protection
Compliance
Proprietary IP






Registered IP
ü
ü

ü
ü
ü
Commercial IP
ü
ü
ü
ü
ü
ü
Proprietary Operational IP
ü
ü
ü
ü
ü
ü
Conceptual IP




ü
ü
Licensed IP






Licensed Operational IP
ü

ü
ü
ü
ü

Registered IP: patents, trademarks, copyrights, and domain names protected by registration.
Commercial IP: intellectual property products and services sold or licensed.
Operational IP: intellectual products, services and content developed, commissioned, acquired or customized used to manage business operations, separated into commercially available technology and customized technology. Operational IP may be owned or licensed.
Conceptual IP: inventions, ideas, concepts and trade secrets.

(Note: optional clause language should be added whether the representing party has re-seller or distribution rights to IP owned by a third party).

Using the framework, the IP representations can be applied to each definitional category, adjusting the reps appropriately based on proprietary rights. For example, in the case of an acquisition agreement, warranties given for commercial IP (out-bound license agreements) should mirror the warranties in the party’s software license agreements. However, there are frequently significant differences between the warranties offered by a business to its licensees (typically very limited) and the warranties given by the same company to a buyer of the business (often including performance and error-free warranties). On the hand, warranties given for licensed software used to run a business (in-bound license agreements) and customized technology may require that the technology is substantially error-free.