13640 2011-08-03 21:11:53 +0000 Stable references in reference section 2011-08-05 15:30:08 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Linux RESOLVED NEEDSINFO P3 normal --- 1 plh ian annevk eoconnor ian julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52252 0 plh 2011-08-03 21:11:53 +0000 The specification references many unstable drafts, some of them are editor's drafts at best that are always on the move. The specification should reference stable documents when they exist and update those references along the way. 52253 1 plh 2011-08-03 21:13:09 +0000 See also http://www.w3.org/Bugs/Public/show_bug.cgi?id=12930 52261 2 annevk 2011-08-03 21:33:34 +0000 Why is this a good use of our time? 52267 3 plh 2011-08-03 21:53:15 +0000 Unless you can point me to a different way for handling this, I don't know how else to approach it. 52268 4 annevk 2011-08-03 21:58:27 +0000 The different way would be to handle it as we handle it now. Other than a few people from ye old guard, nobody complained. 52269 5 ian 2011-08-03 22:00:48 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: What do you mean by "unstable"? 52270 6 plh 2011-08-03 22:08:26 +0000 (In reply to comment #4) > The different way would be to handle it as we handle it now. Other than a few > people from ye old guard, nobody complained. The current way turns the specification into a never stable document. HTML5 should have a clear definition, not a vague sense of one. As recently as last week, I've got comments that HTML5 shouldn't be turned into an unstable technology. So, I consider my feedback as a good use of my time at least, especially if it leads to resolve that question once and for all. 52271 7 plh 2011-08-03 22:12:29 +0000 (In reply to comment #5) > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are > satisfied with this response, please change the state of this bug to CLOSED. If > you have additional information and would like the editor to reconsider, please > reopen this bug. If you would like to escalate the issue to the full HTML > Working Group, please add the TrackerRequest keyword to this bug, and suggest > title and text for the tracker issue; or you may create a tracker issue > yourself, if you are able to do so. For more details, see this document: > http://dev.w3.org/html5/decision-policy/decision-policy.html > > Status: Did Not Understand Request > Change Description: no spec change > Rationale: What do you mean by "unstable"? I'm surprised that I need to spell this out, especially given the recent exchange on the Web Performance mailing list and the link to bug 12930. Linking to an ever changing editor's draft DOES NOT give a stable reference. There is no guarantee of stability on all of the references to dev.w3.org for example. 52275 8 ian 2011-08-03 22:36:46 +0000 You mean the discussions on the web-perf list that you never replied to? http://lists.w3.org/Archives/Public/public-web-perf/2011Apr/0013.html http://lists.w3.org/Archives/Public/public-web-perf/2011Jul/0090.html What do you mean by "stable"? 53779 9 mike 2011-08-04 05:17:16 +0000 mass-move component to LC1 54241 10 ian 2011-08-05 15:24:43 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: No new information since comment 5. 54243 11 julian.reschke 2011-08-05 15:30:08 +0000 I think "did not understand request" isn't entirely accurate. The request sounds pretty clear to me.