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 consistently across independent implementations
📈 Indicators
- Number of Web features whose implementation coverage support their adoption
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 are deployed seamlessly across hardware, OS boundaries, deployment environment
📈 Indicators
- Number of Web features that are not available in widely deployed platforms
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: Test suites that verify whether and how well Web technologies run across a variety of platforms
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
Output: Systematic monitoring of features that don't get deployed or aren't usable across platforms
🎯 Outcome: Interoperable Web technologies are deployed seamlessly across the globe.
A user can expect to experience a given piece of Web content no matter their location.
📈 Indicators
- Known regulatory or technical obstacles that limit adoption of 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.