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 1051 - "Identify depreacted features" too strong
Summary: "Identify depreacted features" too strong
Status: RESOLVED REMIND
Alias: None
Product: QA
Classification: Unclassified
Component: QASpec-GL (show other bugs)
Version: LC-2004-11-22
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Karl Dubost
QA Contact: Karl Dubost
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-21 09:51 UTC by Dominique Hazael-Massieux
Modified: 2005-04-28 11:53 UTC (History)
0 users

See Also:


Attachments

Description Dominique Hazael-Massieux 2005-01-21 09:51:36 UTC
http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#deprecated-feature-principle

  "Identify deprecated features."

is slightly too strong, since the informative text below starts " When a 
technology evolves,".

What to do with a first version of a technology is usually "N/A", and 
admittedly the simple step of "This is a first version, so we have no 
deprecated featues, and don't need to document it at all" does fulfil 
this requirement.

Although, for example OWL, in its first version, does provide:
http://www.w3.org/TR/2004/REC-owl-ref-20040210/#appD
"Changes from DAML+OIL"
which does identify features deprecated from the member submission 
DAML+OIL from which OWL evolved.

I think this comment could be addressed by a sentence early in the 
section, maybe the very first sentence, like "Not normally applicable to 
first versions of a specification."
Comment 1 Dominique Hazael-Massieux 2005-03-04 02:18:51 UTC
The WG agreed with the comment, and will incorporate the proposed wording or a
slight modification of it.
Comment 2 Dominique Hazael-Massieux 2005-04-28 11:53:52 UTC
setting version to LC in case of future use