“Various nifty functions”

Further to the code-literate judge in Oracle v Google, via Groklaw we now have his ruling that the Java APIs are not copyrightable.

It’s an exceptionally clear piece of work and a good introduction to the subject. I certainly couldn’t have written a better technical summary, although I’m sure there are bits that a non-programmer would still struggle with—for example, the judge uses the term “subroutine” without explanation.

I like the jaunty language:

After Java’s introduction in 1996, Sun [...] wrote hundreds more programs to carry out various nifty functions

And he is certainly decisive. The section describing the code at issue (rangeCheck) is introduced thus:

Oracle has made much of nine lines of code that crept into both Android and Java. This circumstance is so innocuous and overblown by Oracle that the actual facts, as found herein by the judge, will be set forth below for the benefit of the court of appeals.

And in the closing remark,

[It] is important to step back and take in the breadth of Oracle’s claim. Of the 166 Java packages, 129 were not violated in any way. Of the 37 accused, 97 percent of the Android lines were new from Google and the remaining three percent were freely replicable under the merger and names doctrines. Oracle must resort, therefore, to claiming that it owns, by copyright, the exclusive right to any and all possible implementations of the taxonomy-like command structure for the 166 packages and/or any subpart thereof — even though it copyrighted only one implementation. To accept Oracle’s claim would be to allow anyone to copyright one version of code to carry out a system of commands and thereby bar all others from writing their own different versions to carry out all or part of the same commands. No holding has ever endorsed such a sweeping proposition.

As an aside, nice to see our old friend Sega v Accolade cited again. I haven’t read all that many US legal opinions on software copyright, but I think pretty much all the ones I have seen have referred to Sega v Accolade.

You can read the whole thing on Groklaw.

Speaking of learning to code

Dialogue in Oracle vs Google, between Judge Alsup and Oracle’s lead counsel David Boies:

Judge: We heard the testimony of Mr. Bloch. I couldn’t have told you the first thing about Java before this problem. I have done, and still do, a significant amount of programming in other languages. I’ve written blocks of code like rangeCheck a hundred times before. I could do it, you could do it. The idea that someone would copy that when they could do it themselves just as fast, it was an accident. There’s no way you could say that was speeding them along to the marketplace. You’re one of the best lawyers in America, how could you even make that kind of argument?

Oracle: I want to come back to rangeCheck.

Judge: rangeCheck! All it does is make sure the numbers you’re inputting are within a range, and gives them some sort of exceptional treatment.

(via Groklaw)

A dot com is an American domain

Verisign seizes .com domain registered via foreign Registrar on behalf of US Authorities” (via Daring Fireball) — a gambling site based outside the US, using a .com domain registered by a non-US registrar, has had its domain seized by US authorities after prosecutors in Maryland asked Verisign, who control the top-level .com nameservers, to hand it over.

The prosecutor noted that “sports betting is illegal in Maryland, and federal law prohibits bookmakers from flouting that law simply because they are located outside the country”. It’s not clear whether the site was doing anything that would be considered illegal outside the US, but I can’t see anything in the story to suggest so. It looks like a legal business in the country it operated in.

In my earlier post about the now-postponed SOPA regulations in the US (Why the proposed US copyright regulations should worry UK citizens) I wrote

The definition of a “domestic” site [in the draft legislation] is brief, but not without ambiguity: it’s a site with a domain name registered or assigned by a US registrar, or (if it has no domain name) a site hosted in the US.

I can’t tell whether that means names whose top-level domains have US-based sponsoring registrars, including all .org, .com and .net domains, or only those whose registration was carried out by a US-based registrar.

This case shows that US authorities may be inclined to treat any .org, .com or .net domain as being under US jurisdiction, no matter where its registrar was based.

Here in the UK, I think we’ve become too used to thinking of .com or .org domains as meaning simply “of the Internet” rather than of any specific country. That will have to change.

I’m not going to suggest we should rush to replace all our .org domains with .org.uk ones—chances are many of them are hosted in the US in any case—but it’s time to forget the old ideal of an Internet domain rather than a national one. A dot com is an American domain.

Why the proposed US copyright regulations should worry UK citizens

Referring to today’s 24-hour Wikipedia blackout in protest against proposed US copyright regulations, a colleague at work asks:

Could someone explain to me why wikipedia et al wouldn’t just move hosting to a different country if they have issue with US regulations… this blackout kind of implies that US law regulates the whole internet

A site like Wikipedia is unlikely to be in any position to relocate, given that it’s run in the US by a US-based foundation and has many US editors, but for those of us in the UK with more modest sites this is a legitimate question. Why worry?

You may in fact fall under US regulation

The proposed regulations divide the Internet into “domestic” sites, which are considered to be US-based and so to fall under US regulation, and “foreign” sites, which are all the others.

The definition of a “domestic” site is brief, but not without ambiguity: it’s a site with a domain name  registered or assigned by a US registrar, or (if it has no domain name) a site hosted in the US.

I can’t tell whether that means names whose top-level domains have US-based sponsoring registrars, including all .org, .com and .net domains, or only those whose registration was carried out by a US-based registrar. Either way it will cover quite a high proportion of sites being run outside the US at present. I’m also unsure whether non-US domains such as .co.uk might be considered domestic if they were registered through a US registrar.

Even if you don’t, these laws are intended to affect you

One of the “selling points” of this legislation is that it imposes effective controls on foreign sites as well as domestic ones.

Provisions are included to require infrastructure sites within the US, such as search engines, payment processors, or ad networks, to remove access to or stop working with any foreign sites deemed infringing. The US still operates much of the Internet’s infrastructure and is the biggest market for many of its services. This could be a big problem for many sites even in places that don’t formally consider the US to be the centre of the world.

There’s no effective comeback

The question of whether a foreign site is “infringing” or not would be determined in US courts, and the only way to argue it would be in US courts. That might not be something anyone outside the US would wish to do.

The US has a record of targeting small-scale infringers

It’s tempting to think that none of this would apply to any of us unless we start running sites that intentionally host pirated material. Unfortunately, the US has a track record of aggressively pursuing action against individuals for relatively minor infringements (see 1, 2, 3, etc). It’s not unreasonable to fear that a general blog-hosting site in the UK, or any site that permits comments, or a research site that refers to audio or video media, could end up being harshly punished for something it never intended.

Afraid, or just concerned?

It’s possible that none of this would affect any of us, in practice.

But it’s also possible that these regulations might be more of a headache for people outside the US than for anyone within it, given their explicit provisions to deal with foreign sites and lack of recourse for foreign site operators, and the concentration of Internet resources and facilities inside the US. If Americans are worried, we should at very least be keeping a wary eye open as well.

See also

Update: I had missed this article on The Verge which answers and clarifies several of the things I had wondered about, and also makes the situation look even worse from a UK perspective.