Re: [ogpx] resolving the name issue

Joshua Bell <josh@lindenlab.com> Fri, 28 August 2009 15:48 UTC

Return-Path: <josh@lindenlab.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 EA75528C3F4 for <ogpx@core3.amsl.com>; Fri, 28 Aug 2009 08:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.885
X-Spam-Level:
X-Spam-Status: No, score=-0.885 tagged_above=-999 required=5 tests=[AWL=-0.398, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, 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 w1CfggNiLqZz for <ogpx@core3.amsl.com>; Fri, 28 Aug 2009 08:48:36 -0700 (PDT)
Received: from mail-pz0-f200.google.com (mail-pz0-f200.google.com [209.85.222.200]) by core3.amsl.com (Postfix) with ESMTP id 3597328C409 for <ogpx@ietf.org>; Fri, 28 Aug 2009 08:48:30 -0700 (PDT)
Received: by pzk38 with SMTP id 38so2048022pzk.5 for <ogpx@ietf.org>; Fri, 28 Aug 2009 08:48:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.20.19 with SMTP id x19mr555881rvi.66.1251474513132; Fri, 28 Aug 2009 08:48:33 -0700 (PDT)
In-Reply-To: <e0b04bba0908280416w60e9c7cdre7e3eaef3e244cb1@mail.gmail.com>
References: <3a880e2c0908211129l7d9defa5od81261e3e5805714@mail.gmail.com> <479011.65903.qm@web111210.mail.gq1.yahoo.com> <f72742de0908270926o6991317cw8d140a7f371e7245@mail.gmail.com> <e0b04bba0908280416w60e9c7cdre7e3eaef3e244cb1@mail.gmail.com>
Date: Fri, 28 Aug 2009 08:48:33 -0700
Message-ID: <f72742de0908280848q62e21c54q2b2b2bc72b33f891@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd1a8fcccfe1f0472359d9e
Subject: Re: [ogpx] resolving the name issue
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: Fri, 28 Aug 2009 15:48:37 -0000

On Fri, Aug 28, 2009 at 4:16 AM, Morgaine <morgaine.dinova@googlemail.com>wrote;wrote:

> On Thu, Aug 27, 2009 at 5:26 PM, Joshua Bell <josh@lindenlab.com> wrote:
>
>>
>> 1. Agent Based Open Virtual Environments Working Group - ABOVE ("above")
>> 2. Virtual World Region/Agent Protocol Working Group - VWRAP ("v-wrap")
>>
>
> I support the *Region/Agent* part of #2 because it refers to  the central
> idea in this proposal that makes it distinct from other interop protocols.
> In particular, it distinguishes this work from other proposals that would be
> in the scope of MMOX.
>
> In contrast, the *Virtual World* part of #2 just adds fuel to the problems
> that have been highlighted here about the redefinition of this phrase in OGP
> compared to its use by everyone else in this sphere.  That issue isn't going
> away, and will become ever harder as we begin to focus on use cases for
> cross-world interop.
>

That's a healthy concern, but I think we need to bite the bullet and risk
the dreaded "Virtual World" phrase in the name. It is *so* evocative to
anyone inside and outside the space and leaves little ambiguity about the
problem domain. No, it isn't specific enough, hence the qualifiers.

MMOX suffered from being far too broad a name (MMO = WoW to most of the
planet). VW is still broad, but I think we can handle it. After all, while
we're focused on the subset of VWs that share Region/Agent concepts, the
protocols may appeal to others. (And it's not limited to the domain, of
course; I was trying to evangelize LLSD in Stockholm.)

Dropping "World" leaves phrases that only make sense to people in the know.
I would expect "Virtual Region" or more so "Virtual Domain" to invite
queries from far afield within the IETF ("Virtual domain? is that like DDNS
kicked up a notch?")

So... like others, I guess I'm putting my voice behind "VWRAP" - kudos to
Carlo for the suggestion.

Can list participants agree to VWRAP as "not perfect, but good enough" and
move past the name issue to real interop work?