This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
* How do we check that a section is not in a "Umbrella specification" because of not applicability or lack of it? * Should we have sections with non applicable.
http://lists.w3.org/Archives/Public/www-qa/2004Dec/0007.html Suggestion: * Fill the SpecGL ICS and put a link to it in your specification. Inside the ICS, explain your choices.
in http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0056.html Mark Skall wrote:" I was assigned an action item to define a best practice to address the problem I identified during my review of XINCLUDE for conformance to SpecGL. The problem had to do with not knowing if various features, like deprecated features, were present and thus not being able to determine if the absence of the identification of these features, as required by SpecGL, was non-conformance or non applicability. After careful review, I decided that there was already a best practice that solves this problem - it is the best practice for providing an ICS. The existing ICS best practice asks for implementations to indicate which capabilities and optional features have been implemented. In our telcon discussion we agreed that this would be a possible solution to the problem but that we would need some way to make the ICS accessible from the spec. However, the existing best practice specifically says that "This Good Practice suggests that the specification itself include an ICS proforma." It seems to me that following this best practice would take care of this problem. Thus, there is no need for a new best practice. "
After further discussion during its Boston F2F meeting (Mar 3rd PM), the Working Group agreed to explicitely requires a positive statement when it is asked to identify one of the DoV and that there is no such a DoV in the given specification.
setting version to LC in case of future use