Independent
This article is a stub. You can help the W3C wiki by expanding it.
The goal of this page is to collect, curate, and distill information about what does independent mean in a W3C context in general, and as it applies to the W3C Process, and the Success Criteria of (most) Working Group Charters.
This is part of the 2024 AB Priority Project: Interoperability and the Role of Independent Implementations ("3Is project").
Articles
Articles and blog posts on the topic of independent (implementations) in standards:
- ...
[Qing An] Some articles or reports I find relevant:
- 1996-10 RFC2026 The Internet Standards Process -- Revision 3
- "In general, an Internet Standard is a specification that is stable and well-understood, is technically competent, has multiple, independent, and interoperable implementations with substantial operational experience, enjoys significant public support, and is recognizably useful in some or all parts of the Internet."
- "Thus, a candidate specification must be implemented and tested for correct operation and interoperability by multiple independent parties and utilized in increasingly demanding environments, before it can be adopted as an Internet Standard."
- 2009-09 RFC5657 Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard
- "Independent implementations should be written by different people at different organizations using different code and protocol libraries. If it's necessary to relax this definition, it can be relaxed as long as there is evidence to show that success is due more to the quality of the protocol than to out-of-band understandings or common code. If there are only two implementations of an undeployed protocol, the report SHOULD identify the implementations and their "genealogy" (which libraries were used or where the codebase came from)."