- From: Karl Dubost <karl@la-grange.net>
- Date: Mon, 28 Jun 2004 17:44:09 -0400
- To: www-qa@w3.org
- Message-Id: <499D0A45-C94C-11D8-8A27-000A95718F82@la-grange.net>
Hi, We don't have a definition in the "QA glossary" [1] for Deprecate and Obsolete The "HTML 4.01" [2] Specification has the most complete definition of them, I think. Lynne has given for "addition to the QA glossary" [3]: ======= * Deprecated Feature An existing feature that has become outdated by a newer construct and is no longer viable. * Obsolete Feature that is no longer defined in the specification. ======= What do we mean by viable. HTML 4.01 says that the developer should support it, which is very dependent on the class of product For Obsolete, I would say: Feature from a previous version of the technology which is no longer defined in the speficiation. * Do we agree with the definition there? * We definitely have to define a short definition for the QA Glossary, which will be more general. * Do we create specific topic on the wiki for it? Quick understanding: Deprecated: * New feature exists that covers the old feature * Should not be used anymore by producer tools. * Must be supported by consumer tools. Use case scenarios with techno FooML 1.0 to FooML 2.0 read save A Doc FooML 1.0 -------> Producer -------> Doc FooML ? B Doc FooML 1.0 -------> Reader What's happening? - in the cases A and B - for obsolete and for deprecated? - With Producer/Reader supporting and/or not 1.0/2.0 ------------------------------------------------ * "Deprecated" [3] A deprecated element or attribute is one that has been outdated by newer constructs. Deprecated elements are defined in the reference manual in appropriate locations, but are clearly marked as deprecated. Deprecated elements may become obsolete in future versions of HTML. User agents should continue to support deprecated elements for reasons of backward compatibility. Definitions of elements and attributes clearly indicate which are deprecated. This specification includes examples that illustrate how to avoid using deprecated elements. In most cases these depend on user agent support for style sheets. In general, authors should use style sheets to achieve stylistic and formatting effects rather than HTML presentational attributes. HTML presentational attributes have been deprecated when style sheet alternatives exist (see, for example, [CSS1]). ------------------------------------------------ ------------------------------------------------ * "Obsolete" [4] An obsolete element or attribute is one for which there is no guarantee of support by a user agent. Obsolete elements are no longer defined in the specification, but are listed for historical purposes in the changes section of the reference manual. ------------------------------------------------ [1] http://www.w3.org/QA/glossary [2] http://www.w3.org/TR/1999/REC-html401-19991224/ [3] http://www.w3.org/TR/1999/REC-html401-19991224/conform.html#deprecated [4] http://www.w3.org/TR/1999/REC-html401-19991224/conform.html#obsolete [5] http://www.w3.org/mid/ 5.1.0.14.2.20040628080853.01e7bbc0@mailserver.nist.gov -- Karl Dubost - http://www.w3.org/People/karl/ W3C Conformance Manager *** Be Strict To Be Cool ***
Received on Monday, 28 June 2004 19:25:18 UTC