From f96c2870c35bf7e6598547dc8c513c57c737241f Mon Sep 17 00:00:00 2001 From: Russell Ballestrini Date: Sun, 19 Oct 2025 07:40:11 -0400 Subject: [PATCH] Add explanation that state machines are public domain mathematics Compare state machines to mathematical formulas like Pythagorean theorem. Explain that expressing state logic in YAML describes mathematical relationships. Assert these are fundamental CS concepts taught for decades, not proprietary innovations. --- content/2025-10-18-who-owns-yaml.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/2025-10-18-who-owns-yaml.rst b/content/2025-10-18-who-owns-yaml.rst index b910666..3759d49 100644 --- a/content/2025-10-18-who-owns-yaml.rst +++ b/content/2025-10-18-who-owns-yaml.rst @@ -18,6 +18,8 @@ who owns yaml? **YAML is data, & data is not code.** Even when YAML expresses configuration logic, workflow definitions, or infrastructure-as-code, it remains a data serialization format. Data structures & formats are not patentable subject matter under established legal precedent - raw data, database schemas, & file formats are considered abstract ideas that lack the technical novelty required for patent protection. Attempting to patent data schemas or configuration formats creates barriers to interoperability & harms the open ecosystem that makes modern software development possible. +**State machines are mathematics, not inventions.** Finite state machines, state transitions, & graph-based logic are fundamental computer science concepts - like algorithms & mathematical formulas - that exist in the public domain. You cannot patent the concept of a state machine any more than you can patent addition or the Pythagorean theorem. When you express state machine logic in YAML (defining states, transitions, & rules), you're describing mathematical relationships using a data format. The underlying concepts have been taught in computer science curricula for decades & represent shared human knowledge, not proprietary innovations. + Let's find out what licenses actually govern the implementations. the question