This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Several places where a specification might have some option (deprecated, extended, subsetted, profiled, etc) there is no requirement to make a positive statement that the spec has no (deprecated elements, extensions, subsets, profiles, etc). It is therefore hard to tell specs that conform (because they don't have these things) from ones that do not conform (because they have these things and don't clearly identify them). The QA Specification Guidelines is an example of a spec that does not clearly state that it does not have several items in this category. Thus, its not easy to tell if it conforms to itself or not.
The QA Working Group agreed that positive statements are needed to distinguish cases of non-applicability from cases of non-conformance, and will amend the relevant requirements and good practices accordingly. We will also fix our own document in that respect.
setting version to LC in case of future use