OpenStreetMap identifies catastrophic effect of Brexit on database right

The Guardian today reports that the open-source mapping project OpenStreetMap, described as "Wikipedia-for-maps", is contemplating relocating from the UK to somewhere that is still in the EU. Although there seem to be manifold reasons, one of them (and I should have thought a pretty important one) is the fact that databases of UK origin will no longer enjoy protection in EU27.

What we know (and possibly love) as database right in the UK is, of course, a creature of EU law. Actually, it's old enough to be EC law: Directive of the European Parliament and of the Council 96/9/EC on the legal protection of databases, implemented by the Copyright and Rights in Databases Regulations 1997, SI 1997 No 3032. Those regulations were amended in 2003 and further amended in the blizzard of secondary legislation that was caused by Brexit, by the Intellectual Property (Copyright and Related Rights) (Amendment) (EU Exit) Regulations 2019, SI 2019 No 605 (Regulation 28 is the place to look, if you are interested). I wrote about all this not long ago, here, but it bears repeating in this new context.

The amendments are not complicated, although it takes a lot of legislative verbiage to convey what they are doing: where the original legislation mentioned the EEA, it now refers to the UK. This means that where previously a connection with the EEA (being a national of an EEA Member State, or incorporated in one, or habitually resident in one - I am going from memory here, so please check the legislation if it's important for you) meant your database qualified for protection in the UK, from now on (for databases created after IP completion day, as 11pm on 31 December 2020 is called - "completion" being a form of Newspeak and actually denoting something very different) you have to show the same connection with the UK. For databases created before IP completion day, protection continues on the old basis and for the original term, but I imagine that will cause all kinds of interesting problems when the proprietor finds it convenient to argue that there has been a substantial change in the database such that protection can start running again - only to find that it potentially means the database no longer qualifies for protection.

Anyway, that's the other side of the OpenStreetMap coin. What OSM are worried about is the treatment of databases of UK origin in the EEA, and of course with the UK no longer being in the EEA, UK databases (if I may call them that) no longer enjoy the protection of the sui generis right created by the Directive. Pre-existing databases will still be protected, by virtue of Article 58 of the Withdrawal Agreement, but given the nature of databases that is a wasting asset. Arguably, the OSM database is a pre-existing one and (the OpenStreetMap Foundation being incorporated in England) it therefore enjoys continuing protection, but the term is only 15 years: the saving grace, for database makers, is that a substantial change to the database "which would result in the database being considered to be a substantial new investment" qualifies the resulting database for protection. Never having had to think about it particularly before, I had reduced that rule to "a substantial new investment in the database keeps the 15 term running", but clearly that is too simplistic: in fact, a substantial new investment means you have a new database which is protected for 15 years, and that makes it abundantly clear why OpenStreetMap are unhappy.

'Internal' distribution does not mean GPL is not invoked

Chicago software licensing attorney Evan Brown  notes an interesting case, XimpleWare Corp. v. Versata Software, Inc., 2014 WL 490940 (N.D.Cal. February 4, 2014), one of very few which address the workings of the General Public Licence (in suit, GPLv2) - a document which becomes more and more important every day.
The plaintiff (as they still call them over there - how quaint! Oh, sorry, I forgot that British irony would be completely lost on any American readers) wrote an XML parser and made it available under GPL v2. The defendant acquired software from another vendor that included the code, and allegedly distributed that software to parties outside the organization. The plaintiff argued that the defendant did not comply with the conditions of the GPL (no attribution, no copyright notice, no reference to the plaintiff's source code, no offer to 'convey' as the GPL puts it the source code), and sued for copyright infringement.
The defendant's argument was that its 'distribution' of the software was merely internal, mainly to its own financial advisers, so the GPL's requirements were not triggered. The court rejected defendant’s argument, looking to the allegations in the complaint that defendant distributed the software to vendors in India, as well as providing it to 'thousands of non-employee financial advisers.'

Python

"You learn from a conglomeration of the incredible past - whatever experience gotten in any way whatsoever", according to Bob Dylan, quotes by whom I found myself searching out this morning in the hope of finding something inspirational - something as inspirational and uplifting as the rendition of My Back Pages from his 40th anniversary concert. Well, that seemed like a useful quote to remember, and when I found myself doing some more research this evening, into the Python programming language, I got some experience which I thought might be worth sharing. After all, the second most popular posting on my personal blog shares my experience of how to replace a Nissan Micra K11 water pump drive belt (the most-read one is about an Achilles heel injury, although it might be the Dylan song title I used for it that draws in the visitors).

If you want to know about the Python language itself, Wikipedia has what looks like a good article on it - though with Wikipedia, who knows? No warranties. What interested me was the licence: the original Python was incompatible with the GPL, apparently for the sole reason that it was governed by the laws of the State of Virginia. I assume that doesn't reflect at all on the laws of that particular state: merely that the GPL doesn't permit stipulations about governing law. In any event, the licence was modified to overcome this and the replacement, the Python Software Foundation License is compatible with it. The PSFL as it is familiarly known is a BSD-style, permissive free software license. What I found interesting is that it is not a copyleft licence: it permits modifications to the source code, as well as the construction of derivative works, without making the code open-source. So a program written in Python (of which Wikipedia lists many) isn't necessarily going to be open source just because it was created with open source tools.