Four questions in government software policy
Government software policy joins purchasing decisions to questions about rights and information. A license determines permitted uses of code, a standard describes shared technical rules, and a procurement policy governs the process of choosing a system. The subjects interact, but their terms are not interchangeable. The Initiative for Software Choice’s principle headings provide a way into these questions when their campaign origin is made explicit and the policy arguments are kept separate from the definitions.
The Open Data Format Initiative’s comparison records the coalition’s four headings quoted below. They are presented as the coalition’s words, not recommendations. The topics lead to more detailed accounts of purchasing, publicly funded software, interoperability and intellectual property. In each case, the legal arrangement or policy actually adopted is distinct from the reason that a campaign, institution or government offered for it.
Procure software on its merits, not through categorical preferences
The purchasing question concerns how a public buyer defines an acceptable solution and compares alternatives. The Center for Strategic and International Studies’ policy survey distinguishes mandatory actions from preferences, advisory measures and research and development programs. A rule requiring a licensing model has a different effect from guidance that places it among the options. The survey also distinguishes approved actions from proposals and failed bills; a proposed rule was not an adopted purchasing requirement.
The survey records reasons offered for open-source policies, including costs, local skills and independence from proprietary systems. It also records policies emphasizing fitness for purpose and value for money without promoting a particular development model. GOV.UK’s guidance asks public buyers to give open source equal consideration and assess initial and ongoing costs, staff skills, support, maintenance and compatibility. These accounts show the competing concerns without resolving which policy a different institution would adopt.
The procurement policy page explains the distinction between neutrality, preferences and mandates. It also separates a policy category from the practical evaluation of a system. A statement that purchasing is based on merit still leaves questions about which costs, functions and license rights enter that assessment.
Promote broad availability of government funded research
Public funding does not describe a single ownership arrangement. Wikipedia’s account of the Bayh–Dole Act explains the retention of certain federally funded inventions by contractors. Cornell’s Legal Information Institute presents the federal rule that copyright protection is generally unavailable for a work of the United States Government, while the government can receive copyrights transferred to it. Patent ownership and copyright in a work are different questions, so a rule about one cannot simply be substituted for the other.
Licensing then addresses the rights a recipient obtains in code. A license can permit distribution and modification while attaching conditions to those activities. Wikipedia describes the European Union Public Licence as a free-software license written and approved by the European Commission. The publicly funded software page considers these arrangements and the distinction between public-domain code, copyleft and permissive terms. Broad access and the conditions of subsequent use remain separate parts of the licensing discussion.
Promote interoperability through platform-neutral standards
Interoperability concerns systems working with one another; openness concerns the conditions of a standard’s availability and implementation. Wikipedia’s overview of open standards describes different definitions centered on the specification, the drafting process and the rights attached to a standard. A specification can therefore be available for reading while its implementation terms still need separate description. RAND and FRAND concern reasonable and nondiscriminatory licensing terms; royalty-free terms concern the absence of royalty payments.
The interoperability and standards page explains these distinctions, the organizations that develop standards and the frameworks used by public administrations. Open source describes software rights and development; an open standard describes rules that different implementations can follow. The terms can occur in the same policy while continuing to refer to different things.
Maintain a choice of strong intellectual property protections
Copyright, trade secrets and patents concern different forms of protection. Software licenses describe what recipients may do with protected material. Wikipedia’s software-copyright and software-patent overviews discuss these separate subjects; copyright in code does not itself settle whether an invention is eligible for a patent. The intellectual-property page distinguishes the rights and license terms, while the patent pages examine particular rules and decisions in Europe and the United States.
In a 2002 opinion column in The Register, Bruce Perens objected that the coalition’s principles could constrain user choice through their approach to procurement and interoperability. That was his published argument. The headings and the objection frame a policy disagreement; neither supplies a verdict for this reference.