On Aug 17, 2009, at 11:43 PM, Anne van Kesteren wrote:
> 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.
The parts of HTML5 defining things like the Window object and origins
could in theory be factored out, but it's decidedly nontrivial to do so.
Regards,
Maciej