Hacker News new | past | comments | ask | show | jobs | submit login

Let's take the 'on a computer' portion out of it.

If I specify that my company takes orders that only have certain header columns and must have specific format in certain fields on the bill of goods, is that /specification/ (not the full text I wrote, but the facts of the specification itself) copyrightable? Why? I don't see that the abstract facts of a specification of interoperability should receive any kind of copyright.




As a matter of public policy, I agree that the specification should not receive protection, but under the law as written by Congress, it does. Thomas's dissent is correct.

My comment is about process, not policy.


Under the law, they do not receive protection.

See Baker v. Selden, which despite it's age is still good law.

https://en.wikipedia.org/wiki/Baker_v._Selden


No. Baker v. Selden does not settle the question of APIs and fair use. That is why the Google v Oracle case made it to the Supreme Court.


It does say that the facts of a traditional print formatting specification (ie. the specific subtopic we're talking about) is not granted copyright protections.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: