Re: [ogpx] Next Steps for OGPX WG Charter

David W Levine <dwl@us.ibm.com> Mon, 03 August 2009 19:56 UTC

Return-Path: <dwl@us.ibm.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 211BA3A6EC0; Mon, 3 Aug 2009 12:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.574
X-Spam-Level:
X-Spam-Status: No, score=-3.574 tagged_above=-999 required=5 tests=[AWL=-0.976, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 m3b-U-c4hFSZ; Mon, 3 Aug 2009 12:56:02 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by core3.amsl.com (Postfix) with ESMTP id EEE213A6EB9; Mon, 3 Aug 2009 12:56:01 -0700 (PDT)
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e7.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id n73JtLAb007553; Mon, 3 Aug 2009 15:55:21 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n73Jtjec220208; Mon, 3 Aug 2009 15:55:50 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n73JtiYO027491; Mon, 3 Aug 2009 15:55:44 -0400
Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n73JtiAs027484; Mon, 3 Aug 2009 15:55:44 -0400
In-Reply-To: <e0b04bba0907312144t35216648ka192e1f3a6ee5c17@mail.gmail.com>
References: <F0487BF6-FBBB-481A-A25E-DE777AC274E2@lindenlab.com> <e0b04bba0907312144t35216648ka192e1f3a6ee5c17@mail.gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>
MIME-Version: 1.0
X-KeepSent: 5C64A22F:91BA9F9D-85257607:006B1DFF; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009
Message-ID: <OF5C64A22F.91BA9F9D-ON85257607.006B1DFF-85257607.006D794B@us.ibm.com>
From: David W Levine <dwl@us.ibm.com>
Date: Mon, 3 Aug 2009 15:55:44 -0400
X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Build V851_07072009|July 07, 2009) at 08/03/2009 15:55:44, Serialize complete at 08/03/2009 15:55:44
Content-Type: multipart/alternative; boundary="=_alternative 006D794885257607_="
Cc: ogpx-bounces@ietf.org, ogpx@ietf.org
Subject: Re: [ogpx] Next Steps for OGPX WG Charter
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2009 19:56:03 -0000

ogpx-bounces@ietf.org wrote on 08/01/2009 12:44:14 AM:

> Morgaine <morgaine.dinova@googlemail.com> 
> Sent by: ogpx-bounces@ietf.org
>
> One of the best ways of tackling this is to directly ask who it 
> actually applies to.  What kinds of worlds could interoperate through 
OGP?
> 
> This question is often answered in an informal way:  "OGP allows 
> interoperation between SL-like worlds."  That answer is fair enough 
> when given loosely and informally, but it is not good enough for an 
> IETF spec, for obvious reasons.  We may know what we mean, 
> informally, but we need a more objective way of expressing it, so 
> that people without any background in Second Life can still find it 
> precise and informative.
> 
> I would like to propose that a different informal answer is 
> appropriate here, an answer which, while equally simple, is 
> enormously more embracing while still being just as concise and 
> specific and inherently implementable:

> "OGP allows interoperation between any virtual worlds that implement
> the protocol."
> 
> This almost sounds recursive, but it is not:  it makes it clear that
> it doesn't matter how different and divergent the worlds may be, 
> they can still interoperate through OGP as long as they implement 
> that common protocol.  It no longer mentions Second Life.  It does 
> not refer to a totally fictitious unit of "the world".  It does not 
> require interoperating worlds to be clones, either implicitly or 
> explicitly.  It clearly states that the ONLY requirement for interop
> is implementing this one protocol, or suite.
> 
> In other words, it avoids being prescriptive about worlds, and it 
> lets adherence to the protocol define the universe of interop.
> 

> 
> 
> Morgaine.
> 
Please note that the "constraint" language in the charter is about the 
the requirements the specifications address.  If you look at the 
constraint
language in the most recent draft, while it suffers from requiring 
understanding
a lot of terms in the space, it does permit a pretty  easy decision as to 
whether
a requirement is within the remit of the working group. The feedback from 
the 
BOF was not that the constraints are wrong, but that they are hard to 
understand. 

We're looking for edits and new language which can be more readily 
understood, but does not
change the basic nature of the constraints. 


- David Levine
~ Zha Ewry ISL