W3C home > Mailing lists > Public > public-html@w3.org > November 2007

Re: Why splitting HTML5 into several specs has failed to work (Was: Request for clarification on HTML 5 publication status)

From: Adam Roben <aroben@apple.com>
Date: Fri, 30 Nov 2007 10:26:25 -0800
Message-ID: <475055D1.80509@apple.com>
To: Sam Ruby <rubys@us.ibm.com>
CC: Ian Hickson <ian@hixie.ch>, "public-html@w3.org WG" <public-html@w3.org>

Sam Ruby wrote:
> Ian Hickson wrote:
>> On Thu, 29 Nov 2007, Sam Ruby wrote:
>>> Why is "the" (as in one and only) specification the only document in 
>>> which this information can make it onto a W3C site?  I've seen 
>>> several specifications which are spread across volumes.  Can't 
>>> different volume in a series be in different states at any given time?
>> There are a few reasons, but primarily the parts are too 
>> interconnected. (For example, the offline stuff has to integrate with 
>> the navigation stuff and the parsing stuff, which has to integrate 
>> with the scripting stuff, and soon enough you've brought in most of 
>> the current spec.)
> Care to elaborate?
> From a quick scan of the current draft, the only occurrences of the 
> word "offline" are in section 4.6.  I have no problem believing that 
> that section would depend on navigation, parsing, and scripting stuff; 
> what I am curious to see to what extent the reverse is true.

One example is in the Navigation section 
<http://dev.w3.org/html5/spec/#navigate>. Step 7 describes how to behave 
in the presence of opportunistic caching namespaces from application 
cache manifests, which are defined in the Offline Web Applications 
section <http://dev.w3.org/html5/spec/#offline>.

Received on Friday, 30 November 2007 18:28:39 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:24 UTC