[vwrap] Cautionary thought...

David W Levine <dwl@us.ibm.com> Thu, 23 September 2010 21:12 UTC

Return-Path: <dwl@us.ibm.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5EDE3A6AA4; Thu, 23 Sep 2010 14:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.942
X-Spam-Level:
X-Spam-Status: No, score=-5.942 tagged_above=-999 required=5 tests=[AWL=0.656, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 ZrvbvJ0ZKubl; Thu, 23 Sep 2010 14:12:50 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by core3.amsl.com (Postfix) with ESMTP id 2A85E3A69D0; Thu, 23 Sep 2010 14:12:50 -0700 (PDT)
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by e8.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id o8NKsQcW013370; Thu, 23 Sep 2010 16:54:26 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o8NLDJhl353810; Thu, 23 Sep 2010 17:13:19 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id o8NLDJjp001108; Thu, 23 Sep 2010 18:13:19 -0300
Received: from d01mc605.pok.ibm.com (d01mc605.pok.ibm.com [9.63.9.192]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id o8NLDImm001101; Thu, 23 Sep 2010 18:13:18 -0300
In-Reply-To: <AANLkTinaghw0KwwvCQn8sEE5787C5zvdvt0Mos_qvByA@mail.gmail.com>
References: <4C9AB1BB.2010008@ics.uci.edu> <AANLkTi=fz6LhpRaTJr7Bu4KsXS93-B0B7SzjH4PwDGuc@mail.gmail.com> <4C9B7041.50908@ics.uci.edu> <AANLkTim-BvM-z90DjRcXD1r1bvZ1doSxzq6-Ou4jg-V7@mail.gmail.com> <B404AC53EB6E4A90A58B2C606CF66045@TWEEDY64> <AANLkTim98XGBrUQOVs0a1iyJD5AOq9nBPhcbZYgU6tro@mail.gmail.com> <4C9BAFF4.5010702@ics.uci.edu> <AANLkTinaghw0KwwvCQn8sEE5787C5zvdvt0Mos_qvByA@mail.gmail.com>
X-KeepSent: 6A9EEFC7:2F6ECF5E-852577A7:00739733; type=4; name=$KeepSent
To: Morgaine <morgaine.dinova@googlemail.com>
X-Mailer: Lotus Notes Release 8.5.1FP1 SHF20 February 10, 2010
Message-ID: <OF6A9EEFC7.2F6ECF5E-ON852577A7.00739733-852577A7.007492B5@us.ibm.com>
From: David W Levine <dwl@us.ibm.com>
Date: Thu, 23 Sep 2010 17:13:17 -0400
X-MIMETrack: Serialize by Router on D01MC605/01/M/IBM(Release 8.0.2FP4|December 10, 2009) at 09/23/2010 17:13:18
MIME-Version: 1.0
Content-type: multipart/alternative; Boundary="0__=0ABBFD34DFE011A38f9e8a93df938690918c0ABBFD34DFE011A3"
Content-Disposition: inline
Cc: vwrap@ietf.org, vwrap-bounces@ietf.org
Subject: [vwrap] Cautionary thought...
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 21:12:52 -0000

As we bash around terms and flexibility and scope, once again. I want to
very gently raise one important cautionary thought, one I think very much
in line with
John's desire to start simple. There is an inherent tension between
flexibility and utility. The more things which can be negotiated and built
in ways which allow
parallel implementations of the same function, the greater the possibility
of creating two totally compliant implementations which can't interoperate
in any useful fashion.

Given the fact that virtual words are, at the end of the day about multiple
people seeing as close the same experience as possible, I think this is an
important point to keep in mind. We all share a desire to build a flexible,
extensible standard. But there are plenty of standards which don't actually
produce interoperability because so much is optional. No specific thing
being discussed here seems bad or out of place, but I do think it useful to
remind ourselves that there are traps at both ends of the spectrum.
Standards which are too narrow fail because they don't meet people's need
for features. Standards which are too broad fail because they don't
actually define enough things to ensure that complaint implementations can
do useful things. For virtual worlds, I strongly believe this trap lurks
more in "what we can display" then in how we move it, but it still does
matter.

Food for thought.

- David
~ Zha