Dropping unused features

On 2007-05-08, Arnt Gulbrandsen wrote:

> Hm. I reread 1602 now and can't find any text saying that 
> standards-track progression should drop unused features. Isn't there 
> any?

1602 has long been obsoleted by 2026 (October 1996).  Quoting 2026:

"  The requirement for at least two independent and interoperable
   implementations applies to all of the options and features of the
   specification.  In cases in which one or more options or features
   have not been demonstrated in at least two interoperable
   implementations, the specification may advance to the Draft Standard
   level only if those options or features are removed.
"

That (as worded) is quite a bit stronger than "should drop".  It's
more like "must drop".

If a feature is in fact unused, it's going to be awfully difficult to
find two implementations...  In theory, even if a feature is used by
only one implementation, it must be removed in order for the
specification to advance to Draft.  In practice, there is an abundant
supply of loopholes; for one thing, "feature" is not defined in 2026.