I think that you may want to change the operational definition of the
working group such that HTML 2.0 represents a set of features we
think should be in it; thse corresponded roughly to our perception of
current practice as of the time when we made the recommendation.
Individuals may then want to argue for additional features in HTML 2.0
anyway, but whether or not someone has implemented it in a browser
shouldn't be the leading term; whether or not there are a large number
of servers and documents out already that use the feature is probably
of higher importance, for example.