The Relationship Between Open Standards and Open Source Software
Tues-945-Johnson.pdf
We've invited the experts to explore ODF and PDF and how they relate to open source software. What are the open source implementations of each?
The degree to which ODF and PDF meet the Bruce Perens tests of open standards will be explored:
- 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 in to 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.
- Predatory Practices: Open Standards may employ license terms that protect against subversion of the standard by 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.
Jim King will also discuss how PDF become so predominant when the specification was controlled by Adobe and not a standards organization.
Program note: this session replaces the earlier offering "The Top Five Mistakes" by Andy Astor.
Back to Sessions