deprecation and 1st version [was Re: answer to TAG issue on positive statements for non applicability]

[...Changing list to QAWG...]

At 06:21 PM 5/3/2005 +0200, Chris Lilley wrote:
>On Tuesday, May 3, 2005, 5:03:49 PM, Karl wrote:
>[...]
>KD> The QA Working Group agrees that for deprecated, obsolete, optional
>KD> features and subdivisions, it was not clear how a specification could
>KD> match the requirements if none of these were present in the
>KD> specification. To clarify this, the Good Practices and Requirements have
>KD> been amended. For instance, the "Identify deprecated features" now reads
>KD> in "What does it mean?":
>KD>     If the specified technology has already been published in a previous
>KD>     version of the specification, indicate the features from the
>KD>     previous version now deprecated or state in the conformance section
>KD>     that no features were deprecated.
>KD> http://www.w3.org/TR/2005/WD-qaframe-spec-20050428/#deprecated-
>KD> feature-principle
>
>Thank you for the response. It partially satisfies the concerns I
>raised.
>
>A first publication of a specification can still have deprecated
>features, if there was a previous poorly documented, undocumented, or
>defined-by-implementation version.

Jeremy Carroll also mentioned this odd case, that the first version of a 
spec might deprecate features from a mature technology or W3C Submission 
upon which the spec was based.

Perhaps it deserves a note.

-Lofton.