- From: Anne van Kesteren <annevk@opera.com>
- Date: Tue, 18 Aug 2009 08:43:44 +0200
- To: "Doug Schepers" <schepers@w3.org>, public-canvas-api@w3.org
- Cc: "public-html@w3.org WG" <public-html@w3.org>
On Tue, 18 Aug 2009 05:46:37 +0200, Doug Schepers <schepers@w3.org> wrote: > It's not really the spin-off aspect that is the issue, it's the maturity > along the Recommendation Track. The same situation applies to the > XmlHttpRequest (XHR) spec, which was never part of HTML5, but which has > a normative dependency on aspects of the HTML5 spec (that is, XHR > references HTML5 for an essential part of its functionality). XMLHttpRequest was part of HTML5. (Though it was taken out before the W3C published an HTML5 draft.) The reason XMLHttpRequest references HTML5 by the way is because HTML5 defines some essential bits of the Web platform that are not defined anywhere else. Pretty much any specification that defines an API in detail needs to reference HTML5. -- Anne van Kesteren http://annevankesteren.nl/
Received on Tuesday, 18 August 2009 06:44:29 UTC