Wikiality – Part II

There was some traffic on the ULC E-Comm Listserv (on which I surreptitiously lurk – and if you don’t know what it is and are interested in e-commerce law, highly recommended) about courts citing Wikipedia with a couple of links to some other stuff, including an article on Slaw as well as an article in the New York Times about the concerns raised by some regarding court decisions citing Wikipedia. Some excerpts and notes to expand on my previous post:

From the con side:

In a recent letter to The New York Law Journal, Kenneth H. Ryesky, a tax lawyer who teaches at Queens College and Yeshiva University, took exception to the practice, writing that “citation of an inherently unstable source such as Wikipedia can undermine the foundation not only of the judicial opinion in which Wikipedia is cited, but of the future briefs and judicial opinions which in turn use that judicial opinion as authority.”

This raises a good point that I didn’t mention in my previous post. I certainly think Wikipedia is fine to note certain things, but I really, definitely, positively, do not think that it should be cited as judicial authority. In my previous article I thought this was so self-evident I didn’t bother mentioning, but the quote above illustrates that it might not be all that clear. Court decisions, as most of you know, are written by judges who take into account the facts and apply the law to the facts of the case, along with other facts and information that may have a bearing on the case. The source of the law includes statutes and of course previously decided cases, which enunciate rules or principles that the court either applies, distinguishes based on the facts as being inapplicable, or, in some cases, overturns (for any number of reasons). Court decisions are not, of course, published on Wikipedia and are not subject to the collective editing process of Wikipedia, nor should they be. Rather, references to Wikipedia in court cases are to provide additional or ancillary context or facts to a case. They do not and should not derogate from principles of law that are set forth in court decisions. But, contrary to what Mr. Ryesky, Esq., indicates above, I don’t think referring to Wikipedia for context or facts will suddenly undermine the foundations of law, since the legal reasoning itself still will and must be based on sources of law, not facts and not context.

Hence the following end to the NTY article:

Stephen Gillers, a professor at New York University Law School, saw this as crucial: “The most critical fact is public acceptance, including the litigants,” he said. “A judge should not use Wikipedia when the public is not prepared to accept it as authority.”

For now, Professor Gillers said, Wikipedia is best used for “soft facts” that are not central to the reasoning of a decision. All of which leads to the question, if a fact isn’t central to a judge’s ruling, why include it?

“Because you want your opinion to be readable,” said Professor Gillers. “You want to apply context. Judges will try to set the stage. There are background facts. You don’t have to include them. They are not determinitive. But they help the reader appreciate the context.”

He added, “The higher the court the more you want to do it. Why do judges cite Shakespeare or Kafka?”

Exactly.

Patent Lawsuits Catch-Up

A nice summary of the 2006 e-comm lititation in the E-Commerce Times. Not surprisingly, they call 2006 the “Year of the Tech Patent Lawsuits”. An excerpt on one of my favourites:

For better or worse, patent attorneys can thank the NTP v. Research In Motion case for introducing the word ‘patent troll’ into the general lexicon and more fundamentally, highlighting how easy it is for an upstart to challenge an established company. In short, it made patent law sexy.

This and many other recent cases in with which an e-commerce patent has been challenged by a small company has led to a steady call for reform by the software industry, he said.

“At every opportunity, today’s software market-leaders have called for reductions in the power of patents, increases in the difficulty of obtaining patents, and an enforcement bias toward companies that practice the patent.

Some see the proposed reforms as improving ‘patent quality’ while others see them as a way to squeeze out upstart competitors,” he explained

Wow. I never thought I’d live to see the words “patent law” and “sexy” used in the same sentence, much less using the latter to describe the former. I’ve already ruminated about this topic previously so will keep this one short. Links to the articles below.

Part 1 Part 2

The Virtues and Evils of Open Source

Yes, I know, I’ve been behind lately. A ton of very interesting things to catch up on. But I’d like to put in one quick note about open source code. I recently came across an article, written last year by a lawyer, generally advising development companies not to use open source. I don’t quite recall where it was (if I did I’d link to it) but I do remember it being quite clear in stating that using open source is A Bad Thing and to avoid it altogether – not just to be careful, but rather to treat it as one would radioactive waste.

With respect, I don’t quite agree. I certainly advise my clients to take a great deal of caution in using open source code, particularly the GPL variety, and very particularly if they have a desire to keep some or all of their own secret, proprietary code secret and proprietary. That being said, I do have many, many clients who have used open source code to great advantage in various ways. Some have simply used existing open source code to avoid reinventing the wheel (and saving on costs), while taking care to keep viral elements out of their proprietary code. Others have been more aggressive with the open source model and have intentionally decided to use open source as the basis for their business model and making their very own code, or parts of it, either open source or subject to a dual-licensing model. As the Red Hats, JBosses, Sleepycats, MySQLs etc. etc. of the world have demonstrated, you can go open source and still have a pretty viable business. And, of course, there are the “old world” companies like IBM who have decided to go open source (in some limited ways – e.g. IBM’s DB2 Express-C thing).

Of course, this is not to suggest that anyone through caution to the wind and just start pulling down stuff from Sourceforge and whacking it into your product. Use of open source definitely requires some planning ahead and consideration of what the business model and value proposition of your business will be. Optimally, enlist the help of a lawyer who’s familiar with open source licenses to discuss what you plan to do and the packages you plan to use. Or, if that’s not feasible, try at least to read the applicable licenses yourself and ensure you comply with them, because if you don’t think that anyone will notice, or that no one will actually sue you, you may want to pay a visit to the GPL Violations Site and reconsider, in addition to the questions that will be asked of you when the due diligence starts on your next round of financing or, even worse, your (aborted) exit event. Can badly managed open source usage (and I emphasize badly managed, not simply open source usage) kill a deal? Definitely.

In short – I don’t think open source is necessarily a bad thing. In fact, it can be a pretty good thing, not just in the social good sense and all that, but also as a business. But it need to be used taking into account its terms of use and ensuring that its consistent with the strategy you plan to take.

If perhaps there’s one thing I’d recommend it would be for shops to make absolutely sure they have a disciplined approach in tracking where code comes from and the terms under which its being used and why its being used. That applies not only to open source stuff, but also, for example, your programmers taking neat snippets of code from Dr. Dobbs or something else, or coming across a nice little script somewhere on the Web and saying “Gee, that’s neat, let’s use it in our product”.

Anyway, if I remember where the article was I’ll update this to include a link.

D-Wave’s Quantum Computing Demo

As I mentioned earlier, there was a Canadian company that announced it would demonstrate a working quantum computer this week. And demonstrate they did. Yesterday. In California. Then they released this press release, which is frustratingly short on details.

There was some other minor press coverage, including a short article in Scientific American. The nub:

For the demonstration, he says D-Wave operators remotely controlled the quantum computer, housed in Burnaby, British Columbia, from a laptop in California. The quantum computer was given three problems to solve: searching for molecular structures that match a target molecule, creating a complicated seating plan, and filling in Sudoku puzzles.

But experts say the announcement may be a bit – er – premature. Even if the computer were to work as advertised, it still would be nearly 1,000 times too small to solve problems that stump ordinary computers. Moreover, researchers do not know whether it will work at bigger sizes.

A similar tone was in most other articles that didn’t parrot the press release – namely, that the demo was not very impressive. That part is rather unfortunate, although not wholly unexpected – the company did indicate (somewhere) that this was intended to be a proof of concept to gain interest.

So I guess at least for the foreseeable future, the cryptography industry will still be around.

A Real Quantum Computer – This Week!

Sorry, been off sick. One very quick entry from Techworld, about a BC company, D-Wave, that will be debuting a real Quantum computer this week!!

Twenty years before most scientists expected it, a commercial company has announceda quantum computer that promises to massively speed up searches and optimisation calculations.

D-Wave of British Columbia has promised to demonstrate a quantum computer next Tuesday, that can carry out 64,000 calculations simultaneously (in parallel “universes”), thanks to a new technique which rethinks the already-uncanny world of quantum computing. But the academic world is taking a wait-and-see approach.

If it turns out to be true, this will be revolutionary news. I mean, truly revolutionary. If it works, well, say goodbye to most of the cryptography industry, as a quantum computer should easily be able to defeat the most sophisticated encryption methods currently known by simple brute strength. Amongst other things. This is nearly unlimited computing power in a box. Stunning. Assuming, of course, it actually works.