[Bug 12510] Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12510 Ian 'Hixie' Hickson i...@hixie.ch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #19 from Ian 'Hixie' Hickson i...@hixie.ch --- That patch is unhelpful since it is to a dynamically generated file. Hence my comment 17. I'm marking this WONTFIX, since I view the WHATWG version as canonical and don't really think it's a problem for people to use the WHATWG version. The W3C version is only useful for the patent policy, and thus doesn't need the hyperlinks. However, I wouldn't object to someone finding a solution to this. If anyone does want to actually work with me to fix this, please reopen the bug, assign it to yourself, and e-mail me, as per comment 17. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 12510] Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12510 Glenn Adams gl...@skynav.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX |--- --- Comment #20 from Glenn Adams gl...@skynav.com --- I'm unable to accept this resolution, in part because this is a W3C venue and, as a consequence, the W3C version of HTML5 is canonical, not WHATWG. It is the responsibility of the spec writer to define or referenced external definition of formal terms, and that responsibility applies here. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 12510] Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12510 Ian 'Hixie' Hickson i...@hixie.ch changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||LATER --- Comment #13 from Ian 'Hixie' Hickson i...@hixie.ch 2011-12-02 16:48:33 UTC --- I understand what you're asking for. I'm saying that if you want it any time soon, you need to provide the script to set it up. Failing that, it'll have to wait until I get around to it, which may not be for some time as I don't really have a good idea for how to do it. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug 12510] Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12510 Julian Reschke julian.resc...@gmx.de changed: What|Removed |Added Status|RESOLVED|REOPENED CC||julian.resc...@gmx.de Resolution|LATER | --- Comment #14 from Julian Reschke julian.resc...@gmx.de 2011-12-02 17:19:16 UTC --- This is indeed a problem. The W3C version is incomplete/underspecified without these terms being properly linked (note that a similar issue has been raised by me with respect to URL parsing during WGLC). -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug 12510] Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12510 Glenn Adams gl...@skynav.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Comment #12 from Glenn Adams gl...@skynav.com 2011-11-09 02:12:32 UTC --- (In reply to comment #11) I have no intention of adding cross-spec cross-references to the WebSocket spec. If someone is interested in providing patches to the spec splitter to do this, please contact me directly. How you create your spec products for use in the W3C is your business, not mine. I am asking that each reference or use of a fundamental concept as described in 2.1: Many fundamental concepts from HTML are used by this specification. [HTML] be made explicit by using a link (anchor) to the relevant defining clause/section in [HTML]. For example, the following phrases should link to the defining sections of [HTML]: 1. queue a task = http://dev.w3.org/html5/spec/Overview.html#queue-a-task 2. dispatch [an] event = http://dev.w3.org/html5/spec/Overview.html#concept-event-dispatch 3. task source = http://dev.w3.org/html5/spec/Overview.html#task-source 4. event loop = http://dev.w3.org/html5/spec/Overview.html#event-loop 5. task (otherwise unqualified) = http://dev.w3.org/html5/spec/Overview.html#concept-task If these (and any other concepts from HTML I don't list above) are used normatively, then it should be made clear that the HTML definition applies (and not some other random implied definition). I don't care if it is done by links at each usage, or by listing the concepts in one place (e.g., under dependencies) and placing the links there. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug 12510] Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12510 Ian 'Hixie' Hickson i...@hixie.ch changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WONTFIX --- Comment #11 from Ian 'Hixie' Hickson i...@hixie.ch 2011-10-31 22:47:58 UTC --- I have no intention of adding cross-spec cross-references to the WebSocket spec. If someone is interested in providing patches to the spec splitter to do this, please contact me directly. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
