Hacker News new | ask | show | jobs
by atlanta90210 163 days ago
The state of Georgia tried to copyright its public written laws. They lost.

https://www.bfvlaw.com/supreme-court-rules-georgia-cannot-cl...

2 comments

I'm not sure what point you're trying to make?

First, laws cannot be copyrighted. They're in the public domain.

Second, the case you link to was not about laws, but annotated law. The annotated version (OCGA) was written by LexisNexis, and all that work paid for by LexisNexis. Obviously, normally that would mean LexisNexis has the copyright on the annotations. This is unproblematic.

Another organization (Public.Resource.Org) posted the OCGA online. Georgia sued, arguing the annotations were the work of LexisNexis and therefore obviously copyrighted. But the problem was that Georgia had declared the annotations to be official.

The Supreme Court found this act of making them official made them essentially the law itself, and therefore uncopyrightable. Which meant LexisNexis had done all that expensive work for free, whoops.

So it's a weird edge case where Georgia should either not have accorded any special status to the annotations, or should have paid for annotations themselves if they wanted "official" ones, and made them public domain.

It’s not a weird edge case at all. For many specific areas like building codes, states have long delegated publication and “annotation” (essentially, writing down critical elements of the law that must be known to folks who want to obey the law) to private publishers. This isn’t literally “Georgia tried to copyright its laws” but it’s close enough to be morally the same. I remember being incensed about this in the late 1990s and I’m glad the wheel of justice (finally) turned.

ETA: A critical tell here are the words “The State of Georgia sued.” Georgia essentially tried to copyright its laws by having a private firm do the copyrighting, and they didn’t even make much effort to hide behind this fiction, since they were the plaintiff. Kudos to the courts for seeing past this low-effort obfuscation.

I’d guess Lexis did that to itself. Usually the “deal” is that West or Lexis provides codification and reporting services for zero dollars, if they are named the official printer.

So the Legislature doesn’t have to maintain and oversee their own nest of troublesome legal pedants, and picks up a few contributions from legal publishing “entrepreneurs.”

By making the Annotated code official, it meant that anyone looking to prove what a particular law says in court would have to get it from the expensive, $412 hardback book, not the free version. I’d guess Lexis asked for that provision as part of its deal with Georgia.

How does one decide what should be in the public domain for the good of society and what should be commercialized? These are a couple of examples that I learned recently

1. In the UK, Royal Mail owns the postal addresses data. I was looking at UK's open datasets - apparently lot of datasets that have addresses can't be used without paying Royal Mail. There are some exceptions - but I am no lawyer. It is depressing to learn that Royal Mail is no longer a public institution, it was sold against public will by the UK government to a private entity, and sold again and as of last year it is owned by a Czech billionaire. Similarly, Canadian postal code database is also not free.

2. CPT code descriptions are owned by AMA (apparently they're super litigious?). Sure they took the time to write them, they should be compensated - but imagine how many interesting projects can be built if this data was freely available

On one hand, multi Billion dollar companies like Bloomberg exist, thanks to free and open data. But also things that should be free (dictionaries, postal codes etc) aren't.

It's not a question of "how do you decide which public standards should be freely accessible". That's easy: all of them. The public benefits more from freely accessible standards whether they're building codes, legal codes, ISO standards, or HDMI. The effect of not having them publicly available is that people make-do without having read the standard and the public has no way to validate things against the standard afterwards.

The question we don't have an easy answer for is how to incentivise the people behind these things without locking their work behind paywalls? Compliance marks, homologation regimes, copyright, and other strategies all have their own downsides.

Do you think it’s good for UpToDate that OpenEvidence scrapes and paraphrases UpToDate and sells the same information in a GPT wrapper to make big investor bucks? I don’t know what the answer is. Go for it, tell me.