Users need to easily identify whether a given feature is stable (i.e., all browsers support it, such as the <p> tag), part of a draft standard, or proprietary.
We do document the different states of a spec feature here:
But we need to make these categories more actionable for the frontend designer/developer.
Our discussions are summarized in the email to email@example.com, subject: "Standards status categories" Date: Fri, 07 Dec 2012 18:00:50 -0600,
Additional discussion: http://lists.w3.org/Archives/Public/public-webplatform/2012Dec/0179.html
(In reply to comment #0)
> Users need to easily identify whether a given feature is stable (i.e., all
> browsers support it, such as the <p> tag), part of a draft standard, or
Certainly "stable", "draft" and "proprietary" aren’t sufficient. There are many features in Rec-level specs and not all browsers support them. Are those stable? They’re certainly not drafts ;)
I think this is trying to mix browser support with standardization status in a single label, and I have my doubts about whether that is useful or even feasible. Sure, they are correlated, but they are different data.
Perhaps summarizing browser support next to the standardization status would be more useful and developers would get the information they need from these two pieces of info very quickly.
New location: http://project.webplatform.org/ia/issues/11