20386 2012-12-14 00:25:05 +0000 Finalize categories of "Standardization Status": stable, proprietary, draft 2013-03-14 17:22:05 +0000 1 1 1 Unclassified webplatform.org info architecture unspecified All All RESOLVED MOVED P2 major --- 20387 1 julee schepers jonathan lea public-webplatform-bugs oldest_to_newest 80153 0 julee 2012-12-14 00:25:05 +0000 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: http://docs.webplatform.org/wiki/Property:Standardization_Status But we need to make these categories more actionable for the frontend designer/developer. Our discussions are summarized in the email to public-webplatform@w3.org, subject: "Standards status categories" Date: Fri, 07 Dec 2012 18:00:50 -0600, Message-ID: <50C28332.5030809@mozilla.com>: http://lists.w3.org/Archives/Public/public-webplatform/2012Dec/0161.html 80154 1 julee 2012-12-14 00:27:06 +0000 Additional discussion: http://lists.w3.org/Archives/Public/public-webplatform/2012Dec/0179.html 80277 2 lea 2012-12-17 16:17:01 +0000 (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 > proprietary. 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. 84435 3 jonathan 2013-03-14 17:22:05 +0000 New location: http://project.webplatform.org/ia/issues/11