It remains a closed, a one-way system.
Certification is a legal process between two parties.
The struggle to get people to learn the DTD notation continued, but at least folks were willing to try out the feedback loop. How can users determine these qualities?
Let's try and clarify a few points.
They might not address exactly the same public: User agents versus servers. We think there should be a tool to gather observations made on a single document by various validators and quality checkers, and summarize all of that neatly for the user. Think of it an aggregator of observations made by a number of different tools.
Mobile Best Practices might be one canditate, and ERT WG with EARL might be another possible implementation of this language.
Could you also help me with my homework?
php plus hiding the 'php' part in the previous example hides the technology in use and enhance a bit security.
It should be done in coordination with one or two Working Groups and in the context of a practical use.
That would be a rare sight, but it's not a fantasy.
As the history of CSS shows, we do a lot better when we add test suites to the mix.
These questions take on additional weight when considered with respect to the security or the safety of the product in question.
html sent back, giving the hint to the editing software that the PUT has to be done at this specific URI, to avoid any ambiguity.
This leads to several issues for editing clients, but also for servers.
We published it quickly.
The document defines a minimal set of metadata elements that can usefully be applied to tests that are intended for publication within a test suite.
Whether or not you're able to help, please join our mailing list and read our blog. Often the chosen criteria will be to have two interoperable implementations of each feature.