Chris Sloan’s Blog

VC Seth Levine has posted a nice article highlighting some very practical and effective user registration features that every web app developer needs to consider. Having attempted to sign up for many a web service myself and been frustrated by these things, I would echo all of them, and I would add another one: make sure the sign up process works! I attempted to submit a request to participate in a public beta of a highly-touted new web service, and I got stuck because the “submit” button appeared not to be active! I haven’t gone back since.

Remember, you only get one chance to make a good first impression, and if you don’t make it count (and quickly) you may not get a second impression.

Great article here on why many doctors are reluctant to adopt electronic medical records.

In yesterday’s post, I talked about why, if you are the customer, a knowledge qualifier in an intellectual property representation/warranty is inappropriate. Today, I’ll tell you what you should REALLY care about, and why the knowledge qualifier may not be that big of a deal.

What you should really care about is having an unqualified, uncapped indemnification obligation covering third party IP infringement claims involving the software or services that the vendor is providing (including embedded third party software, but that is a topic for another day).

What’s the difference between an IP rep/warranty and an IP indemnity? The remedy. If there is a third party IP claim, and the vendor defends and indemnifies the customer, then the vendor has satisfied its obligation to the customer. If there is also an IP infringement rep/warranty, then, regardless of whether the vendor defends the claim, the customer also has a claim that the vendor breached the agreement.

So, if you are the customer, your top priority is the unqualified, uncapped indemnity. The IP rep/warranty is also nice to have, but in most cases, it’s of secondary importance.

I review a lot of IT agreements (as well as traditional IP license agreements). I’m constantly surprised at the creative ways that IT vendors try to shift risks inappropriately to their customers; I call these “weasel” provisions. One of the standard ones involves the relatively common intellectual property non-infringement representation.

Often, the vendor agreement includes language like this (taken from an actual agreement that I reviewed recently):

4.4 “Vendor warrants that to its knowledge, the Licensed Software does not infringe or violate the patent, trademark, copyright, trade secret or any other intellectual property right of any entity not a party to this Agreement.”

When I review one of these for a client, I always strike the knowledge qualifier. Sometimes I get the following argument (quoting the vendor from the contract I quoted above):

We will not be able to remove “to its knowledge” in paragraph 4.4. We only know, and can warranty, what we know today.

At first blush that sounds like a convincing argument, but it completely misses the crux of the problem. Knowledge qualifiers are risk-shifting provisions. By adding the knowledge qualifier, the vendor is shifting the risk to the customer that the vendor’s software unknowlingly infringes someone’s intellectual property. Of course, it’s true (at least with respect to patent infringement) that the vendor may not know that it is infringing, but neither does the customer, and the vendor is in a much better position to control the risk. Put another way, the risk of the unknown must be borne by one party or the other; in this case, the vendor should bear it, and the knowledge qualifier should come out.

You can analogize this to buying a car. If your car’s warranty were limited to “reasonable efforts”, and you took it in for a warranty repair and the dealer said “We tried but we couldn’t fix it. Tough luck,” you’d be pretty upset, right? The knowledge qualifier described above is really the same issue.

In part 2 tomorrow, I will explain why this may not matter very much, if you have a strong indemnification provision.

Jason Hoida (in-house attorney at Opera) emailed me the link to the new Opera Turbo browser (available here). It runs all the traffic (other than SSL traffic) through a compression algorithm so that web pages load up significantly faster. Mostly it just compresses images; as a result the images look grainier, but you can turn the turbo feature off with one click if you need the full image resolution. I downloaded Opera Turbo over the weekend and played around with it; it works as advertised and I was impressed with the simple, clean interface.

While I’m not ready to give up my beloved Firefox for everyday browser usage (love those plugins), Opera Turbo will come in very handy when I’m using a Blackberry modem or otherwise working off of a slow internet connection.