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

Re: Why "Platform Core" and "HTML5" are in the same spec

From: Nikunj Mehta <nikunj.mehta@oracle.com>
Date: Thu, 20 Nov 2008 14:05:13 -0800
To: Jonas Sicking <jonas@sicking.cc>
Message-Id: <C190BE1F-31D1-4A2B-91DF-5F1D9E2FEFD7@oracle.com>
Cc: Ian Hickson <ian@hixie.ch>, HTML WG <public-html@w3.org>

Feedback from implementors *must* be taken in to account. However, I  
did not know that there is a requirement that HTML5 cannot break  
itself /yet/. Of course, care must be taken that any damage is  
controlled, but I would like to clarify what the W3C process around  
editing the draft is.

I would need to fully understand the process being followed by Ian in  
editing the HTML5 spec before making any commitments about the process.

By the way, Oracle has joined both the HTML and Web apps working  
groups, and I am the Oracle nominee on both.

Nikunj
On Nov 20, 2008, at 1:54 PM, Jonas Sicking wrote:

>> I do not agree the proposed split of the sections currently in  
>> HTML5 and my previous communication [2] puts that on record. I am  
>> willing to edit SQL, offline application cache as well as server  
>> sent events, but you would not separate them from other parts of  
>> the "Platform Core" in which I have little experience.
>
> For the record I think it'd be great to get those parts split out.  
> The one caveat is that offline application cache depends on browsing  
> context spec which currently lives in HTML5. I don't think that is a  
> unsolvable problem though, we just have to be ok with having a  
> dependence on the HTML5 spec (something which has caused controversy  
> in the past).
>
> I'd also say that a separate SQL interface belongs more more in the  
> webapps WG, so ideally you would have to join that WG.
>
> If you truly are serious about taking these parts on, and the group  
> is ok with it, I'd love to see some drafts. However an absolute  
> requirement for me is that some of the process that Hixie is using  
> is followed. Such as keeping editor drafts open, ensuring that the  
> specs don't break existing deployed code (which now exists for the  
> offline app cache), and that feedback from implementors are taken  
> into account.
>
> / Jonas
>
>
Received on Thursday, 20 November 2008 22:06:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:59 UTC