Editing Open standard (section)

==== Bruce Perens' definition ====
One of the most popular definitions of the term "open standard", as measured by Google ranking, is the one developed by [[Bruce Perens]].<ref>{{cite web|url=http://www.dwheeler.com/essays/opendocument-open.html|title=Is OpenDocument an Open Standard? Yes!|website=www.dwheeler.com|access-date=18 March 2018|archive-date=22 March 2009|archive-url=https://web.archive.org/web/20090322043712/http://www.dwheeler.com/essays/opendocument-open.html|url-status=dead}}</ref>
His definition lists a set of principles that he believes must be met by an open standard:<ref name=parens>{{cite web|url=http://perens.com/OpenStandards/Definition.html|url-status=dead|archive-url=https://web.archive.org/web/20060101010742/http://perens.com/OpenStandards/Definition.html|archive-date=2006-01-01|access-date=2020-02-22|title=Open Standards: Principles and Practice|publisher=Bruce Perens}}</ref>

#Availability: Open Standards are available for all to read and implement.
#Maximize End-User Choice: Open Standards create a fair, competitive market for implementations of the standard. They do not lock the customer into a particular vendor or group.
#No Royalty: Open Standards are free for all to ''implement'', with no royalty or fee. ''Certification'' of compliance by the standards organization may involve a fee.
#No Discrimination: Open Standards and the organizations that administer them do not favor one implementor over another for any reason other than the technical standards compliance of a vendor's implementation. Certification organizations must provide a path for low and zero-cost implementations to be validated, but may also provide enhanced certification services.
#Extension or Subset: Implementations of Open Standards may be extended, or offered in subset form. However, certification organizations may decline to certify subset implementations, and may place requirements upon extensions (see ''Predatory Practices'').
#Predatory Practices: Open Standards may employ license terms that protect against subversion of the standard by ''[[Embrace, extend and extinguish|embrace-and-extend]]'' tactics. The licenses attached to the standard may require the publication of reference information for extensions, and a license for all others to create, distribute, and sell software that is compatible with the extensions. An Open Standard may not otherwise prohibit extensions.

Bruce Perens goes on to explain further the points in the standard in practice. With regard to availability, he states that "any software project should be able to afford a copy without undue hardship. The cost should not far exceed the cost of a college textbook".<ref name=parens/>