--- # ora-canonical-source: Projects/Ora/Paper — Public Domain Over Open Source.md title: Public Domain Over Open Source section: Ora — Foundation arguments status: review description: Open source has been the public domain's working substitute for thirty-five years. Why they are not the same, and why Ora chooses the public domain. authors: - The Ora Knowledge Foundation (initiative in formation) downloads: md: /papers/white/public-domain-over-open-source.md license: https://creativecommons.org/publicdomain/zero/1.0/ --- # Public Domain Over Open Source Open source has been the public domain's working substitute for thirty-five years. The two are not the same thing. The Ora Knowledge Foundation is an initiative in formation. It is not incorporated and is not accepting donations. Existing Ora project artifacts are publicly released under CC0 where stated; the Foundation stewardship, trademark, contribution-review, and legal-partnership mechanisms discussed below are proposed and do not currently operate. ## The substitute Free and open-source licenses — GPL, AGPL, MIT, BSD, Apache — operate by using copyright as a lever. The licensor holds copyright. The license grants permissions on conditions. Compliance with the conditions is enforced through the same legal apparatus that would otherwise be used to enforce a proprietary copyright claim. Copyleft licenses preserve openness by requiring derivatives to remain open. Permissive licenses preserve attribution by requiring it on derivatives. Both are tools that depend on copyright being real. This has worked well, mostly, for thirty-five years. The Free Software Foundation built the GPL. The Open Source Initiative shepherded a constellation of compatible licenses. The Apache Software Foundation, the Linux Foundation, Software Freedom Conservancy, Software Freedom Law Center, the Electronic Frontier Foundation — a stack of institutions exists to defend the licenses' force when they are challenged. The result has been a working substitute for what an actual public domain would have been if jurisdictions and institutions and the legal system had supported it directly. But it is a substitute. The mechanism it works through — copyright enforcement on conditions — is exactly the mechanism that proprietary software uses against users. The defenders of free software wield copyright as a tool of openness; the same tool is wielded against openness in other hands. The licenses are conditional grants of permission, and conditions can be challenged, disputes can become enclosure pressure, and the compliance apparatus has to be tended continuously. ## What CC0 is Creative Commons CC0 1.0 Universal is the strongest public-domain dedication available. Where other Creative Commons licenses grant permissions on conditions (BY for attribution, NC for non-commercial use, ND for no derivatives, SA for share-alike), CC0 dedicates the work to the public domain to the maximum extent permitted by law. There are no permissions to grant because there are no rights left to grant permissions over. Anyone can use, modify, distribute, build upon, fork, or republish a CC0 work, for any purpose, on the same terms. Commercial use. Modification. Redistribution. Inclusion in derivative works. Use in jurisdictions hostile to public-domain dedication, to the extent local law allows. The dedicator releases all rights to the maximum extent permitted, including the right to be attributed. Existing Ora artifacts released under CC0 are available for anyone to use on the terms of that dedication. A future Foundation would serve as steward rather than owner: it would not claim copyright in public-domain artifacts, and it could not relicense work after dedicating it to the public domain. ## Why this is structurally different Three structural differences from open source matter to the proposed Foundation's approach. **No condition can be challenged because there are no conditions.** A copyleft license can be defied — by a commercial actor who wants to use the code without complying with the openness condition. The defiance has to be answered through copyright enforcement, which means litigation and cost for a steward or rights holder. CC0 has no condition. There is nothing to defy and nothing to enforce. **Public-domain dedication is irreversible.** A copyleft license can be revoked by the licensor as to future works, and compliance disputes can lead to difficult questions about which versions remain open. A CC0 dedication, once made, is intended to be permanent. No future steward or successor could re-enclose what had already been dedicated. **The licensing apparatus does not need defending.** A copyleft license requires institutional infrastructure to remain effective: the licenses need to keep up with changes in copyright law; enforcement organizations need funding; test cases must establish the licenses' force; and a defense bar must handle disputes. CC0 takes that compliance apparatus off the table. A future Foundation would not need to create a license-enforcement capacity for artifacts already dedicated to the public domain. These differences accumulate. They are not equivalent in some narrow technical sense; they are different commitments at the legal-architectural level. ## The cost CC0 has costs that copyleft licenses avoid. Anyone can use the artifacts in proprietary products without contributing back. A commercial actor that took a future Foundation-stewarded framework, wrapped it in a closed product, and sold access would be doing something that copyleft might prohibit and CC0 permits. The Ora project accepts this cost for its CC0 releases because the alternative cost — maintaining a copyleft enforcement apparatus and risking disputes over license conditions — is higher. The proposed Foundation would continue that policy if it is incorporated and begins stewardship work. The cost is also less load-bearing than it appears. A commercial actor that wraps a published CC0 framework in a closed product competes against the same framework in the public catalog. The closed product's value proposition has to come from something the framework alone does not provide — service, integration, support, or brand. If the closed product is just the framework with a fee gate, users can get the source material for free. The market disciplines this. The cost would be more load-bearing if future Foundation-stewarded artifacts were the kind of thing where commercial enclosure adds substantial value. Software libraries that get bundled into proprietary products at scale benefit from copyleft because the bundling is an enclosure that copyleft prevents. Frameworks released as natural-language specifications cannot be bundled the same way; the framework is its own delivery surface, and a closed product that includes a CC0 framework still has to deliver the framework's value to compete. ## What this is not CC0 is not anti-copyleft. The Free Software Foundation, the GPL, and the institutions that defend copyleft have produced enormous value over decades. Ora's choice, and the policy proposed for a future Foundation, does not entail a critique of copyleft as a strategy; it is a different strategy chosen for different reasons. CC0 is not naïve about source confusion. A future incorporated Foundation could pursue trademarks on its name or certification marks used to identify authentic releases. No such Foundation trademark or certification program currently operates. If rights were established, they would be used only to prevent confusion about the source of artifacts — not to restrict use, modification, or redistribution of public-domain content. Anyone could state truthfully that their work was derived from or compatible with Foundation-stewarded artifacts; trademark rights would constrain only a false implication of endorsement. CC0 is not the same thing as everything-goes. The proposed Foundation could eventually steward a reference framework library and review submissions against public specifications. No Foundation contribution intake, specification standard, review process, or distribution system currently operates. The design would welcome forks, modifications, and alternative collections while applying a published standard to material accepted into a future Foundation-stewarded catalog. ## Why this matters The proposed Foundation's rationale depends on the artifacts it might steward remaining free. Open-source licenses are a working substitute for that, but they require continuous defense and depend on institutions, jurisdictions, and enforcement capacity. CC0 dedicates artifacts to the public domain without requiring that licensing apparatus to keep functioning. The choice is structural. Ora uses CC0 because it makes enclosure attempts pointless in advance: there is nothing to acquire that is not already free. The proposed Foundation would follow the same policy. Conditions on use — even conditions as light as attribution — can become disputes and enclosure pressure. A public-domain dedication has no condition to challenge. A future Foundation's leverage would not be control over the artifacts. It could come from source-identifying trademarks if obtained, partnerships if formed, defensive publication, and a contributor community if one develops. No Foundation trademarks, standing legal-defense partnerships, contribution system, or active contributor community currently exists. None of those future mechanisms would require copyleft licensing; each could operate alongside public-domain dedication. That is the rationale.