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 12:54:58 -0800
Cc: HTML WG <public-html@w3.org>
Message-Id: <E6004DBE-82D3-45F1-91E0-EC637EB0B752@oracle.com>
To: Ian Hickson <ian@hixie.ch>


On Nov 18, 2008, at 7:24 PM, Ian Hickson wrote:

> On Tue, 18 Nov 2008, Nikunj Mehta wrote:
>> On Nov 17, 2008, at 5:36 PM, Ian Hickson wrote:
>>> On Mon, 17 Nov 2008, Nikunj Mehta wrote:
>>>>
>>>> What Ian considers Platform core [1] as listed in [2] includes a
>>>> wide variety of things that don't have much to do with HTML at all.
>>>> SQL (5.10.2) and unstructured storage (5.10.1) are good examples.
>>>> The only reasons for keeping these parts in the HTML5 spec that I
>>>> have seen are that these pieces are stable and the same editor  
>>>> would
>>>> be working on these sections as the Platform Core. Neither sound
>>>> good enough reasons to me.
>>>
>>> They're not particularily good reasons, but splitting those two  
>>> parts
>>> up would delay progress by a year or more, and that is unacceptable
>>> IMHO.
>>
>> Sorry but Hixie's opinion is not what decides the matter here.
>
> Well, it decides it as much as yours, right?

Seeing what is flying around here, my opinion or for that matter that  
of anyone not agreeing with you seems to have very little impact on  
decisions.  Also, if you were not being satirical when you said "a  
decade  or more out from the core parts of the spec being  
interoperably implemented" [1], then how does an extra year (assuming  
you are actually right) make any difference?

<snip>Will address separately</snip>

>
>
>>>> 2. Current features of browsers are sometimes being standardized in
>>>> other specs. As an example, XMLHttpRequest is not a part of HTML5
>>>> even though that is part of most current browsers and is core to  
>>>> the
>>>> browser platform.
>>>
>>> XHR was part of HTML5. It was extracted because someone  
>>> volunteered to
>>> edit it. That's really all it takes.
>>
>> I am sure there are some in this WG and outside who would be  
>> willing to
>> help edit parts of this spec (even though they may get carved out of
>> this HTML5 spec). Seemingly random scope definitions and section  
>> splits,
>> decisions about what is in and what is not, and ownership decisions  
>> are
>> turning them off. I know that the number is non-zero, because I am  
>> one
>> of them.
>
> Please, if you are willing to take over editing one of the sections
> described in this mail:
>
>   http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html
>
> ...then let us know. I would be more than happy to spread the workload
> and work with you on this.

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. If you really are serious about  
spreading the workload, then you must consider alternatives to the  
splits identified in your original email. Your response to [2] in [3]  
indicates you are open. The onus is really on /you/ (HTML WG nodding)  
to allow other editors in this henhouse.

[1] http://lists.w3.org/Archives/Public/public-html/2008Nov/0282.html
[2] http://lists.w3.org/Archives/Public/public-html/2008Oct/0273.html
[3] http://lists.w3.org/Archives/Public/public-html/2008Oct/0274.html
Received on Thursday, 20 November 2008 20:56:01 UTC

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