NB: The Theory of Change described in this document is a work in progress that has received only limited input and review from the community.
🎯 Outcome: Interoperable Web technologies are implemented in a diverse set of products offering meaningful difference choices to users
📈 Indicators
- Share of indepedent implementations that implement Web features
Output: Royalty-free consensus-based standards that enable interoperable ecosystems
Output: Maintained test suites that new and existing implementation can easily integrate in their development process
e.g. Web Platform Tests
At the moment, outside of WPT, test suites tend to be developed to "exit Candidate Recommendation" and don't have a clear maintenance plan, nor active work in easing their integration in implementation development toolchains.
Output: Automatically obtained and published test results of implementations of Web technologies
e.g. wpt.fyi
At the moment, outside of WPT, test results are normally collected only at precise time of the development of technologies.
Output: Tools that facilitate and accelerate the adoption of Web technologies
For instance, validators and checkers, documentation, polyfills, data about feature support across implementations.
Output: Reference or baseline implementations of Web technologies
🎯 Outcome: Interoperable Web technologies provide a credible alternative to proprietary platforms for content and service providers
📈 Indicators
- Number of popular online services that are only available through proprietary platforms
Output: Systematic gap analysis of the features the Web provides compared to other platforms
Output: Systematic collection of use cases to guide the development of new Web technologies
While some groups take more or less formal and systematic approaches to develop use cases, and while explainers (which the W3C TAG strongly encourages as part of developing technologies) are expected to be anchored in end-user's need, the work on use cases remains ad-hoc and uncoordinated across groups.
Output: Tools that facilitate and accelerate the adoption of Web technologies
For instance, validators and checkers, documentation, polyfills, data about feature support across implementations.