{"data":{"id":"us-ok/okla.-stat.-tit.-62-62-34.31.1","jurisdiction":"us-ok","citation":"Okla. Stat. tit. 62, § 62-34.31.1","heading":"Software acquisition requests","body":"A. For the purposes of this section, \"open source software\"\n\nmeans software that guarantees the user of the software use of the\n\nsoftware for any purpose, allows unrestricted access to the\n\nrespective source code, enables the use of the internal mechanisms\n\nand arbitrary portions of the software with the ability to adapt\n\nthem to the needs of the user, provides the freedom to make and\n\ndistribute copies of the software, and guarantees the right to\n\nmodify the software with the freedom to distribute modifications of\n\nthe new resulting software under the same license as the original\n\nsoftware. \"Open standards\" means specifications for the encoding\n\nand transfer of computer data that is free for all to implement and\n\nuse in perpetuity, with no royalty or fee, has no restrictions on\n\nthe use of data stored in the format, has no restrictions on the\n\ncreation of software that stores, transmits, receives, or accesses\n\ndata codified in such way, has a specification available for all to\n\nread, in a human-readable format, written in commonly accepted\n\ntechnical language, is documented, so that anyone can write software\n\nthat can read and interpret the complete semantics of any data file\n\nstored in the data format, allows any file written in that format to\n\nbe identified as adhering or not adhering to the format, and\n\nprovides that any encryption or obfuscation algorithms are usable in\n\na royalty-free, nondiscriminatory manner in perpetuity, and are\n\ndocumented so that anyone in possession of the appropriate\n\nencryption key or keys or other data necessary to recover the\n\noriginal data is able to write software to access the data.\n\n\"Proprietary software\" means software that does not fulfill all of\n\nthe guarantees provided by open source software.\n\nB. Prior to approving software acquisition requests, the\n\npurchasing entity shall consider whether proprietary or open source\n\nsoftware offers the most cost-effective software solution for the\n\nagency, based on consideration of all associated acquisition,\n\nsupport, maintenance, and training costs.\n\nC. Whenever possible the Chief Information Officer or\n\npurchasing entity shall avoid approving requests for the acquisition\n\nof products that do not comply with open standards for\n\ninteroperability or data storage.","path":["OK Code","Title 62"],"source_url":"https://www.oklegislature.gov/OK_Statutes/CompleteTitles/os62.pdf","current_through":"2026-08-14","vintage":"open-us-law v2026.08, retrieved 2026-09-14","retrieved_at":"2026-09-14T18:32:36Z","sha256":"cbe02ffd1fb0e33ef0e3931f7a9528c9852d976636129c3177852ebaacc76adb","source_id":"us-ok","stale":false,"prev":"us-ok/okla.-stat.-tit.-62-62-34.31","next":"us-ok/okla.-stat.-tit.-62-62-34.31.2"},"notice":"GroundRules: Original legal text. Not legal advice."}
