Digital Publishing and Copyright Infringement

I don’t have any deep and meaningful thoughts on this myself, but I’ve been wondering for a while why we don’t hear more about copyright infringement and DMCA infringement in the digital publishing industry.  The music, movie and gaming industries seem to have led the charge in protecting their copyrights in the digital world and being extremely vocal about it in the process. But not so the publishing industry. I’ve heard a couple of different explanations for this none of which I find completely satisfying. One is that publishers have different relationships with their customers than other industries – perhaps less adversarial in some senses, and publishers are thus more concerned than some industries about alienating customers by threatening copyright infringement suits. Another explanation has been that the publishing industry has somehow been better at using technological protection measures to protect its content. Again, I don’t know how much truth there is to that. I did correspond with one self-published author who told me that she sends out DMCA notices all the time to folks who illegally copy her work and that when she works with publishers, they also end up sending a lot of DMCA notices on her behalf. This author also mentioned to me that copyright infringement in the book industry is potentially more damaging to content creators (and distributors) because people tend to only read a book once while they go back to other digital copyrighted works – music, movies, games – multiple times and may ultimately decide it’s easier to just get a legal copy at the end of the day.  I’m not sure that makes sense either. If people download games, music and movies illegally, I can’t imagine that their ongoing enjoyment of that content would lead them to want to make legal purchases down the track unless there are other incentives.

I’d be interested in whether others have thoughts on these issues. I’ve been trying to puzzle them out for a while.

What’s a “Document”?

1370556_lots_of_files I’m under an edit deadline right now, but Orin Kerr’s post over at Volokh Conspiracy on the Verizon FISA order contains this fascinating bit:

If the order is what it appears to be, then the order points to a problem in Section 1861 that has not been appreciated. Section 1861 says that the “things” that are collected must be relevant to a national security investigation or threat assessment, but it says nothing about the scope of the things obtained. When dealing with a physical object, we naturally treat relevance on an object-by-object basis. Sets of records are different. If Verizon has a database containing records of billions of phone calls made by millions of customers, is that database a single thing, millions of things, or billions of things? Is relevance measured by each record, each customer, or the relevance of the entire database as a whole? If the entire massive database has a single record that is relevant, does that make the entire database relevant, too? The statute doesn’t directly answer that, it seems to me. But certainly it’s surprising — and troubling — if the Section 1861 relevance standard is being interpreted at the database-by-database level.

I’ve wondered about this sort of question before, in a different context. At the tail end of this article, in trying to come up with an explanation for why so many judges were taking the (to me) extreme step of ordering civil litigants to provide social networking login information to their opponents, I offered the following:

It is also possible that courts and lawyers are having difficulty in applying the rules of discovery to social-networking sites for a much more prosaic reason: confusion over what exactly constitutes a “document” on a social-networking site. That is, the problem may simply be one of translation from new technology to more familiar forms of media. It is possible that some courts and lawyers are conceiving of the information visible on a social-networking site as akin to an ordinary website, in which a “document” is typically defined as a single webpage. Once it has been shown that relevant information exists in a document, typically the entire document must be produced, absent redactions for privileged information, so that the relevant information maintains its context. In ordering access to entire sites, courts may be thinking of social-networking accounts as in essence single documents, or a small number of documents.

This was in the conclusion, not the body of the article, so I didn’t go much further. But it can’t be right that all of the messages that appear in someone’s Facebook account are a single “document” for discovery purposes — even though they may all display on a single, very long screen. That is, what constitutes a “document” may be separating from the physical or virtual characteristics of document-ness relied on previously — presence within a single container or file — and may have more to do with how they are constructed, or used. Cf. Mike Madison on “things.” But once again, I’ll have to leave further exploration of this idea for some other time.

Some Takeaways from “When Patents Attack! – Part 2″

I listened to This American Life’s new show on patents today; it’s a followup to the original, widely heralded show from two years ago. I think it was well reported, and worth a listen. Despite concerns about NPEs being worse now than two years ago, I thought the show was oddly more balanced than the last time (even though nearly half the show is just a replay of a portion of the original). The part of the show I want to focus on is a patent granted to Crawford based on a 1993 filing date, which claims a large part of the online backup business model/technology (depending on how you look at it).

In the original show, it was revealed that Intellectual Ventures (IV) purchased the patent in 2007, sold it to a shell company in Marshall, Texas, called Oasis in 2010, but retained a “back end” percentage of any settlements/litigation winnings. Oasis sued a bunch of online backup companies, settled with most, and then lost against the holdouts when a jury found that Crawford actually co-invented the patent but failed to include the other inventor on the patent application. In this part, we learn that IV’s back end percentage is 90%, and that Crawford got about 18% of IV’s take. In short, Oasis got 10% as an enforcement agent. I have a lot to say about this topic, but only a short amount of time now, due to deadlines on three different papers (who says professors take the summer off). I did want to note three takeaways:

1. The Intellectual Ventures part of the story is actually the least surprising/interesting part of the story. I think it’s a great piece of reporting; IV made a real gaffe by pointing to Crawford as its model inventor, and This American Life dug and found some answers. But the answer isn’t all that new if you’ve been following this area. At the time Oasis filed its suit, the conventional wisdom was that IV was mounting several lawsuits through shell companies. Maybe this was due to earlier IV statements that they preferred not to litigate, much like people never die at Disneyland.

It appears that the Oasis lawsuit featured in the show is one of those shell lawsuits, though I have no idea whether IV ceded control when it transferred the patent or retained control about who pursue. To this, I ask the same question I asked in my Wired op-ed: does it matter? Would we view this lawsuit or the patent differently if it were brought by IV? If IV had a 10% backend instead of 90%? If Crawford brought the suit? If Crawford’s company survived to bring suit? My answer is generally not, other than having concerns about misinformation and secrecy. Perhaps others feel differently.

2. Many software patents are too broad. This is nothing new, of course, but the show illustrates it nicely. I’ll discuss the Crawford patent below, but the first part of the show nicely illustrates this point with a segment on the podcasting patent. The show argues that the inventors never could make podcasting work, and resorted to audiocassette distribution; the argument is that the inventor merely invented the “idea” of podcasting.

This type of attack on the patent falls under a few different legal rules: written description (claiming more than the inventor actually invented), enablement (claiming more than the inventor actually taught), and functional claiming (claiming the function divorced from the way it was implemented). Further, in Life After Bilski we argue that an idea that is so broad that it is unmoored from any specific application might be an unpatentable abstract idea.

I don’t know where the podcasting patent stands, but my first read of it makes me think it’s pretty broad.

3. My favorite part of the show was the story about how Crawford obtained the patent. While the ending is not so great (invalidity due to non-joinder of inventor), the story itself is one that is rarely told in today’s patent bashing news cycle.  It turns out that Crawford and friends came up with the idea for online backup with passwords back in 1991, as part of a failed business venture to solve a very real problem that consumers faced – an easy way to back up data offsite. The story describes how the friends swapped floppy disks, but remember that 1991 was before writeable CDs, and floppy drives were 1.44MB. The average 20MB hard drive (can you imagine? how did we live like that?) would take many floppy disks.

Thus, they came up with a solution. Was it obvious? I don’t know. The first When Patents Attack show implied as much, but the patent survived whatever challenges the litigants brought on that front. For all the talk about many other patents in the same area, it might just be that those patents were improvements on this pioneering patent. It wouldn’t be the first time, but I don’t really have any idea.

The point I want to make, though, is that this is patent law working exactly as it was supposed to. It was people getting together to solve a problem, coming up with a solution, and attempting to protect it. (Well, there was one hiccup, which is that the inventors didn’t get together and file, apparently – but it was invalidated for that reason. This isn’t the case most of the time.) Indeed, the show confirms a key point that IV has always maintained, that a significant amount of money was paid to the inventor. That money might stimulate further investment in the invention in the future.

But another thing happened that often happens; the inventors were too early. They came up with a solution that wasn’t commercially viable yet. The world of 2400 baud modems where users pay for bandwidth by the minute was simply not ready for the online solution, and the business failed to materialize. Indeed, my own firm tried something similar in 1997 working with a Sparcstation and a client who was a Sun engineer; it was still too slow to use in-house, let alone online. Technology needed to catch up.

This is one reason why we often see patent assertions much later in a patent’s life, especially in software. Many really great software solutions–both in patents and in research–implement ideas nobody ever thought of on equipment that’s just barely ready to handle it. It’s not until years later that the solutions seem obvious because the enabling technology makes it commercially feasible.

The question is, what do we do about this? In other areas of patent law, we tolerate long delays. We would prefer not to have them, of course. Indeed, one side benefit of the current assertion trend is that patentees are getting more savvy about commercializing earlier. For example, Crawford and friends could have approached folks with fast networks and computers – universities – with their solution back in the early 1990s. Maybe today they would have, and might have found some early adopters.

But even if patents are not exploited, other patent areas treat this as a feature of the system; most calls to reform the system to avoid this problem have been to commercialize earlier, not to kill off  the patents (so long as the patent is not hidden for too long). Software patents seem to be different, though. The collective wisdom seems to be less tolerant of this delay for software. I think the reason for this stems from my second point, above. Because software patents can be so broad, the concern is that a single broad patent –even a valid one– can render an entire industry infringers. Furthermore, patents filed in the early 1990s expire seventeen years after grant, not 20 years after filing. This effectively extended their life, perhaps for too long.

I’ll end by saying that I share these concerns about software patents, but I’m not so sure that they are so different from the rest of the patent world. There have been plenty of broad overarching patents in a variety of industries over time. Some had poor outcomes that stunted industries, and some fueled industries. People disagree about the software industry, I think.

These were my primary takeaways. I wish I had a clever solution, but I don’t; the show is worth listening to, however, with an open mind.

Believing, then Seeing

“[S]ecular Americans …  think that belief precedes action and explains choice. That’s part of our folk model of the mind: that belief comes first.”  from @tanyaluhrmann in this NYTimes op-ed about the roles of faith and belief in evangelical communities.

I sometimes see intellectual property law and policy discussions through a similar lens:  People want to believe that IP does all of the things that it is said that IP does, so they proceed (law, policy, scholarship) accordingly.

But there is much more to all of this than what might appear to be simply willing suspension of dis-belief, or some obvious circular reasoning.  The reasoning metaphor, and the presumption that we reason first, are out of place.  Luhrmann, still in the Times, writes:

I saw that people went to church to experience joy and to learn how to have more of it. These days I find that it is more helpful to think about faith as the questions people choose to focus on, rather than the propositions observers think they must hold.

If you can sidestep the problem of belief — and the related politics, which can be so distracting — it is easier to see that the evangelical view of the world is full of joy. God is good. The world is good. Things will be good, even if they don’t seem good now. That’s what draws people to church. It is understandably hard for secular observers to sidestep the problem of belief. But it is worth appreciating that in belief is the reach for joy, and the reason many people go to church in the first place.

Talk among IP circles of motivations and incentives that drives creativity and innovation — even talk that focuses, as it should on non-monetary or non-financial incentives — misses, I think, at least a good chunk of this.   The “reach for joy” resonates as an ideal far beyond evangelical or even more generally spiritual settings.  Artists and scientists are, too, engaged in a kind of reach for joy — and all the more so when we expand the frame to think not only in terms of internal rewards (“I feel joy”) but external ones as well (“I share joy”).

(Post title borrowed from @dewittjones and his “Celebrate What’s Right” video, though the sentiment doesn’t originate with him.)