- From: <bugzilla@jessica.w3.org>
- Date: Wed, 09 Nov 2011 02:12:33 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12510
Glenn Adams <glenn@skynav.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #12 from Glenn Adams <glenn@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.
Received on Wednesday, 9 November 2011 02:12:41 UTC