Warnings for old DOM specifications
Hi all, A while ago I proposed adding warnings to a number of specifications to alert readers that those documents are no longer being maintained. [1] As there seemed to be general agreement this would be good to do, I've written up some proposed wording; see the attachment. Please let me know if you have any comments. Thanks Ms2ger [1] http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0245.html Title: Warnings for old DOM specifications Warnings for old DOM specifications Specifications with a replacement DOM 2 Core DOM 2 Traversal and Range Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the DOM4 specification, which is intended to eventually supersede this document, is currently ongoing in the Web Applications (WebApps) Working Group. DOM 3 Core Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the DOM4 specification, which is intended to eventually supersede this document, is currently ongoing in the Web Applications (WebApps) Working Group. DOM 2 Events Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the Document Object Model Level 3 Events specification, which is intended to eventually supersede this document, is currently ongoing in the Web Applications (WebApps) Working Group. DOM 2 Style Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the CSS Object Model specification, which is intended to eventually supersede this document, is currently ongoing in the Cascading Style Sheets (CSS) Working Group. DOM 2 HTML Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the HTML5 specification, which is intended to eventually supersede this document, is currently ongoing in the HTML Working Group. Specifications without a replacement DOM 3 Load and Save DOM 3 Validation Document Status Update 2012-##-##. This paragraph is informative. The concepts this document defines have not seen adoption in web browsers and are obsolete. The Web Applications (WebApps) Working Group does not recommend its implementation. Readers who wish to pursue the use cases addressed by this specification, are encouraged to send email to public-webapps (archives).
Re: Warnings for old DOM specifications
Thanks Ms2ger! I will start a CfC and include the HTML WG and CSS WG chairs since those WGs are explicitly mentioned in your proposed text. -Art On Apr 4, 2012, at 7:53 AM, ext Ms2ger wrote: Hi all, A while ago I proposed adding warnings to a number of specifications to alert readers that those documents are no longer being maintained. [1] As there seemed to be general agreement this would be good to do, I've written up some proposed wording; see the attachment. Please let me know if you have any comments. Thanks Ms2ger [1] http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0245.html warnings.html
CfC: Add warnings to old DOM specifications; deadline April 18
In September 2011, an obsolescence message was added to the November 2000 DOM 2 Views specs [D2V]. As WebApps previously discussed (link below), we would like to add a similar message to additional (old) DOM Recommendations.Msger's (Mozilla) proposed text is in the following document and this is a Call for Consensus to agree on this text. If this CfC passes, the text will be added to the top of the Recommendations as was done with [D2V]: http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/att-0044/warnings.htmlDaniel, Peter - please note the CSS WG is mentioned in the proposed text for DOM 2 Style http://www.w3.org/TR/DOM-Level-2-Style/Maciej, Sam, Paul - please note the HTML WG is mentioned in the proposed text for DOM 2 HTML http://www.w3.org/TR/DOM-Level-2-HTML/All -If you have any comments or concerns about this proposal, please send them to public-webapps@w3.org by April 2 at the latest.-Thanks, Art Barstow[D2V]http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113/Begin forwarded message:Resent-From: public-webapps@w3.orgFrom: ext Ms2ger ms2...@gmail.comDate: April 4, 2012 7:53:44 AM EDTTo: "public-webapps@w3.org" public-webapps@w3.orgSubject: Warnings for old DOM specificationsarchived-at: http://www.w3.org/mid/4f7c3648.1000...@gmail.comHi all,A while ago I proposed adding warnings to a number of specifications to alert readers that those documents are no longer being maintained. [1]As there seemed to be general agreement this would be good to do, I've written up some proposed wording; see the attachment.Please let me know if you have any comments.ThanksMs2ger[1] http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0245.htmlTitle: Warnings for old DOM specifications Warnings for old DOM specifications Specifications with a replacement DOM 2 Core DOM 2 Traversal and Range Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the DOM4 specification, which is intended to eventually supersede this document, is currently ongoing in the Web Applications (WebApps) Working Group. DOM 3 Core Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the DOM4 specification, which is intended to eventually supersede this document, is currently ongoing in the Web Applications (WebApps) Working Group. DOM 2 Events Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the Document Object Model Level 3 Events specification, which is intended to eventually supersede this document, is currently ongoing in the Web Applications (WebApps) Working Group. DOM 2 Style Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the CSS Object Model specification, which is intended to eventually supersede this document, is currently ongoing in the Cascading Style Sheets (CSS) Working Group. DOM 2 HTML Document Status Update 2012-##-##. This paragraph is informative. This document is not currently being actively maintained. Readers should not expect corrections and clarifications for the text to appear here or in the associated errata document. Work on the HTML5 specification, which is intended to eventually supersede this document, is currently ongoing in the HTML Working Group. Specifications without a replacement DOM 3 Load and Save DOM 3 Validation Document Status Update 2012-##-##. This paragraph is informative. The concepts this document defines have not seen adoption in web browsers and are obsolete. The Web Applications (WebApps) Working Group does not recommend its implementation. Readers who wish to pursue the use cases addressed by this specification, are encouraged to send email to public-webapps (archives).
Re: CfC: Add warnings to old DOM specifications; deadline April 18
Arthur Barstow: All - If you have any comments or concerns about this proposal, please send them to public-webapps@w3.org mailto:public-webapps@w3.org by April 2 at the latest. April 18? +1 to the warnings, I think they're worded well and useful.
Re: CfC: Add warnings to old DOM specifications; deadline April 18
On Apr 4, 2012, at 8:00 PM, ext Cameron McCormack wrote: Arthur Barstow: All - If you have any comments or concerns about this proposal, please send them to public-webapps@w3.org mailto:public-webapps@w3.org by April 2 at the latest. April 18? Ooops - yes, April 18!
Re: CfC: Add warnings to old DOM specifications; deadline April 18
* Arthur Barstow wrote: Msger's (Mozilla) proposed text is in the following document and this is a Call for Consensus to agree on this text. If this CfC passes, the text will be added to the top of the Recommendations as was done with [D2V]: http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/att-0044/warnings.html DOM Level 3 Core essentially replaced DOM Level 2 Core for the features relevant to both specifications, especially as far as unversioned imple- mentations are concerned. Since making such status update edits is not currently a widely adopted W3C practise, the pointer should go to the DOM Level 3 Core specification, to avoid that people make assumptions a- bout the absence of such notices in other specifications. At least this would have to be explained in the note. It does not seem like the people interested in DOM4 actually mean to make a specification that could meaningfully supersede DOM Level 3 Core for all its current users; there are no Java bindings for instance. As such I would regard the note as proposed as rather misleading. For DOM Level 3 Load and Save the statement have not seen adoption in web browsers is misleading, and Working Groups cannot declare certain Recommendations as obsolete and no longer recommended. The Process for that is to formally Rescind them, and that is what the group should do if it wants to communicate anything more than that the specifications are no longer being maintained. I note, again, that there are legal pro- blems with rescinding Recommendations informally as proposed. All the notes should reference formal publications of the W3C, not un- published documents. The reason for that should be quite obvious, you want to be able to counter any criticism of things in the editor drafts by pointing out they are just that. That defense will not work very well if referencing editor drafts becomes ubiquitous, even in formal settings like the SotD. The press for instance might feel justified to report on bad proposals in editors' drafts, and report them as the real deal with support by member organizations if the formally published documents are hard to find or are often out of date. Similarily, courts may find that promoting informal documents in this manner is a form of deception. If X, Y, and Z are in the Working Group, X puts something into an editor's draft, Y implements it and Z sues Y over it, Y might argue they assumed Z will commit to RF licensing, and Z might argue they never knew about what X put into the draft because it was never formally published. Who will win the argument if there is confusion about the standing of these editor drafts? And who will pay for the damages to the W3C's reputation this might cause, whatever the outcome? We avoid this kind of stuff by simply accepting that referencing the formally published works is the right, normal, proper, expected thing to do. If people want to change that, they will have to talk to whoever will suffer the consequences. As that is not the Working Group as such, it's the wrong forum to propose this kind of change. Hence the first sentence of this paragraph. -- Björn Höhrmann · mailto:bjo...@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
