|
There are several processes by which we trim weeds from the specifications. • On a regular basis, especially around explicit call-for-comments, we go through every section and mark areas as being considered for removal. This happened early in 2008 with the data templates, repetition blocks, and DFN-element cross references, for example. If no feedback is received to give us strong reasons to keep such features, then they eventually are removed altogether. • Anyone can ask for a feature to be removed; such feedback is considered like all other feedback and is based on the merits of the arguments put forward. • If browsers don't widely implement a feature, or if authors don't use a feature, or if the uses of the feature are inconsequential of fundamentally wrong or damaging, then, after due consideration, features will be removed. Removing features is a critical part of spec development.
more
|
Is there a process for removing bad ideas from the spec?
Related Questions
- Some of the benchmarks in CPU2006 and MPI2007 derive from the same source codes. CPU2006 benchmarks are ...
- A SPEC/CPU benchmark is intended to run on a single processor core. On multiprocessor systems, a "rate" run ...
- Briefly, you need an SMP or cluster system, running Unix, Linux or Microsoft Windows with compilers; a ...
- SPEC MPI2007 focuses on performance of compute intensive applications using the Message-Passing Interface ( ...
- SPEC uses a reference machine to normalize the performance metrics used in the MPI2007 suites. Each benchmark ...