Description
|
The term “open standard” may be seen from these three perspectives:
- The recognized SSOs, as organizations representing the standards creators, considers a standard
to be open if the creation of the standard follows the tenets of open meeting, consensus and due
process.
- An implementer of an existing standard would call the standard open when it serves the market
they wish, it is without cost to them, does not preclude further innovation (by them), does not
obsolete their prior implementations, and does not favor a competitor.
- The user of an implementation of the standard would call a standard open when multiple
implementations of the standard from different sources are available, when the implementation
functions in all locations needed, when the implementation is supported over the user-planned
service life, and when new implementations desired by the user are backward compatible to
previously purchased implementations.
Open Standards Requirements:
This clarifies the very different views of the creators, implementers and users of standards on what is
an open standard. Their combined, reasonable, but not simple, expectations translate into the ten
requirements that enable open standards:
- Open Meeting - all may participate in the standards development process.
- Consensus - all interests are discussed and agreement found, no domination.
- Due Process - balloting and an appeals process may be used to find resolution.
- Open IPR - how holders of IPR related to the standard make available their IPR.
- One World - same standard for the same capability, world-wide.
- Open Change - all changes are presented and agreed in a forum supporting the five requirements
above.
- Open Documents - committee drafts and completed standards documents are easily available for
implementation and use.
- Open Interface - supports proprietary advantage (implementation); each interface is not hidden or
controlled (implementation); each interface of the implementation supports migration (use).
- Open Access - objective conformance mechanisms for implementation testing and user evaluation.
- On-going Support - standards are supported until user interest ceases rather than when
implementer interest declines.
|