Ian Hickson wrote:
On Sat, 31 Oct 2009, SM wrote:Joint responsibility increases the chances of failure as two working groups do not work the same way.How do you define "success"? I think the more people are involved the more likely we are to get interoperable implementations.It should be noted that the WHATWG's work is based on technical merit and not on consensus. If even just one person raises a valid technical issue in the WHATWG, they cannot be overridden by the rest of the group having complete agreement that they should just ignore the technical issue. There is also a firm philosophy that the specs match interoperable deployed implementations, and that the specs not leave things undefined.The IETF process is based on consensus. An IETF Working Group cannot change that. The philosophical questions can be addressed in the charter if the group reaches a consensus about that.My comments are as an individual. The proposed WG will be part of the IETF. It is not the IETF. The entire IETF community will be asked to comment on the proposal submitted for publication. The IETF does not constrain the solution. It is up to the IETF participants to determine what problem will be solved and how it will be solved. There's the BoF and this mailing to discuss about all that and come up with a proposed charter. People from the W3C WebApps and WHATWG are not excluded. Ask them to join this mailing list and participate.Sure. And people from the IETF are not excluded from the WHATWG, and are welcome to join the mailing list and participate there also.
My comment as individual.I am in the WHATWG ml, but I have to say that I haven't seen any discussion, at least lately, on the WebSocket spec.
at least in the specification mailing list.Actually I'd like also see more people from WHATWG community become involved the technical discussion that at the moment
is happening in the HyBi mailing list. cheers Sal
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.