This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1143 - positive statements for non applicability
Summary: positive statements for non applicability
Status: RESOLVED REMIND
Alias: None
Product: QA
Classification: Unclassified
Component: QASpec-GL (show other bugs)
Version: LC-2004-11-22
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Karl Dubost
QA Contact: Karl Dubost
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords: needsAction
Depends on:
Blocks:
 
Reported: 2005-03-04 02:41 UTC by Dominique Hazael-Massieux
Modified: 2005-04-28 11:53 UTC (History)
0 users

See Also:

Attachments

Description Dominique Hazael-Massieux 2005-03-04 02:41:13 UTC 
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.
Comment 1 Dominique Hazael-Massieux 2005-03-04 02:43:03 UTC 
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.
Comment 2 Dominique Hazael-Massieux 2005-04-28 11:53:49 UTC 
setting version to LC in case of future use