Re: [hybi] Proposed Charter for HyBi WG (rev.3)

SM <sm@resistor.net> Sat, 31 October 2009 16:36 UTC

Return-Path: <sm@resistor.net>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C33C63A6831 for <hybi@core3.amsl.com>; Sat, 31 Oct 2009 09:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level:
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2u+kdofK7WNJ for <hybi@core3.amsl.com>; Sat, 31 Oct 2009 09:36:14 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id E3FD23A6783 for <hybi@ietf.org>; Sat, 31 Oct 2009 09:36:14 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4.Beta0/8.14.4.Beta0) with ESMTP id n9VGaJq8011247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Oct 2009 09:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1257006988; x=1257093388; bh=gzVYetV6KSYAtKrwIdEtevb5NF5R8pfdEAECSFSkvkU=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=mq6XzMLtK+SaEu8uzsu4Vwm1QusiMkJ/S4uYS7uAtflpaijXT83cWs0cg/RxwKyVR iKQ+3KbCzGpj9DMSN8HweTFNMUmdCpLYAxRdanrD/Zz9SYvUjOZWkPB6+RjjWW037O wl6DUicjnx7QtOz4yqmaLKw2ugpzjN6Q8pWQxBAE=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=aFFm6Ie/Txpb7BPAYnaSa1hMYSgXx14XkazHfFg8SVv4z6e2WniXO3dnnmvNTIrR1 3KA8gB74eVQZFCaSaLRrZtGMDeXzB6mpPlOv3mj01UeZ8rFhSM1uTg20aMdmBycn/HF BSfxxqFwK+bU71dRvP2cTpr3nbrezShMEHUwe5g=
Message-Id: <6.2.5.6.2.20091031080527.040fe028@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 31 Oct 2009 09:35:59 -0700
To: Ian Hickson <ian@hixie.ch>, Salvatore Loreto <salvatore.loreto@ericsson.com>
From: SM <sm@resistor.net>
In-Reply-To: <Pine.LNX.4.62.0910310335580.25616@hixie.dreamhostps.com>
References: <4AE966CA.9090907@ericsson.com> <Pine.LNX.4.62.0910300047310.25608@hixie.dreamhostps.com> <4AEABDBF.80705@ericsson.com> <6.2.5.6.2.20091030120030.043cff78@resistor.net> <Pine.LNX.4.62.0910310335580.25616@hixie.dreamhostps.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: hybi@ietf.org
Subject: Re: [hybi] Proposed Charter for HyBi WG (rev.3)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2009 16:36:15 -0000

At 20:59 30-10-2009, Ian Hickson wrote:
>The WHATWG is happy to work with anyone. I don't understand what you mean
>by "liason with" juxtaposed by "take on prime responsibility", though. In
>what sense is it a liason if the other group no longer has responsibility?
>Surely a joint effort implies joint responsibility.

Editorial comment:  That should have been "the working group will 
liaise with the ...".

Joint responsibility increases the chances of failure as two working 
groups do not work the same way.

>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.

Regards,
-sm