Software and intellectual property: copyright, trade secrets, patents and licenses
Intellectual-property rules protect different aspects of software. Copyright concerns protected expression, trade-secret rules concern qualifying information kept confidential, and patent law concerns claimed inventions that meet its requirements. A software license sets permissions and conditions for activities such as use or redistribution. These concepts overlap in a program's legal setting, but they do not describe the same rights.
Copyright protects expression
The U.S. Copyright Office’s copyright explanation includes computer programs among protected works of authorship. It describes protection arising when an original work is fixed in a tangible form. It also distinguishes expression from ideas, procedures, methods, systems and discoveries. That distinction matters for software: copyright in code is not a general ownership claim over every idea the program implements.
The Copyright Office explains that ownership can arise through employment arrangements and transfers as well as authorship. It lists reproduction, preparation of derivative works and distribution among exclusive rights, subject to statutory limits. A recipient's permission to exercise a right and the identity of the copyright owner are consequently separate questions. Receiving a copy does not describe all the permissions attached to it.
Wikipedia’s software-copyright article explains that free and open-source licenses also rely on copyright to enforce their conditions. Copyright is therefore not confined to proprietary distribution. A copyleft condition can use the copyright holder's permissions to require preservation of specified rights when code is shared. The legal foundation and the licensing choice remain distinct.
Software as a literary work
Wikipedia’s account of the TRIPS Agreement records protection of computer programs in source or object-code form as literary works. In this legal usage, literary work is a category of protected expression, rather than a claim that code resembles a novel. Treating a program as a literary work also differs from considering whether an invention involving software is eligible for a patent.
The Computer Programs Directive reference article describes the European Union's copyright framework for computer programs. It records rights concerning copying, alteration and distribution, together with limitations. Its account links harmonization of copyright law with the problem of interoperability. This addresses the legal protection of programs rather than creating an unrestricted entitlement to use or alter any program.
Decompilation and interoperability
The directive article describes decompilation where necessary for a program to operate with another program or device. It also states that the results cannot be used for other purposes without infringing the program's copyright. The exception has a purpose and limits; describing it as interoperability-related does not make every form of reverse engineering permissible in every circumstance.
The same source describes copies necessary to use a program, alteration within its intended purpose and personal backup copies in its account of limitations on exclusive rights. Permissions arising through a license and limitations arising through law are related ways an activity can be authorized. They have different foundations and cannot be treated as interchangeable descriptions of a user's rights.
Confidential information and trade secrets
Wikipedia’s trade-secret explanation describes information that has commercial value because it is not generally known or readily ascertainable, and that is subject to reasonable steps to keep it secret. The source notes that exact definitions vary by country. Confidentiality by itself does not state every requirement of trade-secret status; the value and protective measures are also relevant.
Trade-secret protection normally does not depend on formal registration, according to the article. It describes non-disclosure agreements as one means of maintaining secrecy and notes that trade secrets can be licensed or sold. Source access under a restricted agreement can therefore coexist with confidentiality. Making information available to an authorized recipient is different from making it available for unrestricted redistribution.
Patents concern claimed inventions
Wikipedia’s software-patent overview describes patents as territorial exclusionary rights granted in exchange for disclosure of inventions. It also explains that jurisdictions use different eligibility standards for software-related claims. The category is consequently not defined by the simple presence of code: the claimed invention and the applicable legal requirements matter.
The patent-law background page compares European and U.S. eligibility rules. The EU computer-implemented-inventions page describes a proposed directive and its outcome. These subjects concern patentability and legal policy, which remain separate from the copyright conditions on distributing a program's code.
From rights to license terms
Wikipedia’s software-license article describes a license as a legal instrument governing use or redistribution. Its proprietary-software article distinguishes closed-source software from source-available software with restrictive permissions. Its copyleft account describes conditions intended to preserve rights in redistributed derivatives. Inspecting source, modifying it and distributing changes are therefore distinct activities in a licensing arrangement.
Wikipedia’s Shared Source Initiative account describes Microsoft's source-available licensing scheme. It records access for reference, review and development under different terms, with some licenses meeting open-source definitions and others retaining proprietary restrictions. The program name alone does not identify the permissions in every offering. This example illustrates source access with differing conditions, rather than a recommendation of a supplier or product.
The license-family comparison explains those distinctions in more detail. The publicly funded software page adds the separate issues of ownership, government works and publication. Together, these categories describe the rights and permissions that a software policy can address without assuming a single model for every program.