Re: [ogpx] one virtual world, or many?

Joshua Bell <josh@lindenlab.com> Mon, 31 August 2009 23:38 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 65CF028C27F for <ogpx@core3.amsl.com>; Mon, 31 Aug 2009 16:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.672
X-Spam-Level:
X-Spam-Status: No, score=-1.672 tagged_above=-999 required=5 tests=[AWL=0.304, BAYES_00=-2.599, 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 6Sxc2BKuVqpv for <ogpx@core3.amsl.com>; Mon, 31 Aug 2009 16:38:27 -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 8FB1F3A6C00 for <ogpx@ietf.org>; Mon, 31 Aug 2009 16:38:27 -0700 (PDT)
Received: by pzk38 with SMTP id 38so4310095pzk.5 for <ogpx@ietf.org>; Mon, 31 Aug 2009 16:38:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.22.2 with SMTP id z2mr1306964rvi.122.1251761914893; Mon, 31 Aug 2009 16:38:34 -0700 (PDT)
In-Reply-To: <4A9BE0B0.5010508@dcrocker.net>
References: <3a880e2c0908281127h6965f332na493007b032e5e93@mail.gmail.com> <20090830003055.GD22756@alinoe.com> <b8ef0a220908291754x31f24ea7x702100d6aa9810ef@mail.gmail.com> <e0b04bba0908300225l34ec9f35x465d46f34313b60c@mail.gmail.com> <382d73da0908300505t3f804865h629bec91ad59954a@mail.gmail.com> <4A9A9D5A.9020400@dcrocker.net> <b8ef0a220908301134l7046cca7geb8ee9af26436b@mail.gmail.com> <4A9BE0B0.5010508@dcrocker.net>
Date: Mon, 31 Aug 2009 16:38:34 -0700
Message-ID: <f72742de0908311638h4f17c987t2b3e828f23b901ed@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd1a59047d7a504727888f6
Subject: Re: [ogpx] one virtual world, or many?
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, 31 Aug 2009 23:38:28 -0000

On Mon, Aug 31, 2009 at 7:39 AM, Dave CROCKER <dhc@dcrocker.net> wrote:

>
>
> Meadhbh Siobhan wrote:
>
>> so. this is an interesting one.
>>
>> those of us who called for the OGPX BoF are in agreement that the term
>> "virtual world" is informational only.
>>
>
>
> This calls for an alternative that hadn't occurred to me.
>
> The charter currently has the string "virtual world" thirteen times.  And
> it is used heavily in discussions on this list.
>
> That level use of use essentially guarantees that the string is not merely
> informative.  It really does have to have specific technical meaning that
> folks agree on.
>

I agree that this is problematic. We should alter uses of "virtual world" in
the charter are not necessary. I'll work on this tomorrow with Meadhbh.

One is particularly interesting, on review:

"Within a single virtual world, avatars exist in at most one location in a
shared virtual space."

This line actually points at the loose working consensus we seem to share
about what a "virtual world" really is - the set of places "you" can "go" as
"yourself". This includes both the technological aspects (i.e. services
adhering to common protocols; network access) and policy aspects (i.e.
permission to access, trust agreements).

Again, it seems like we agree on what we're talking about, even if we're
loathe to define it precisely.


    My suggest is to remove all occurrences of the term from the charter,
>     except for the two in the first sentence of the draft charters
> Description
>     section.
>
> In other words, say that vwrap provides a service in virtual world
> simulation, but then make all other references be in terms of vwrap-specific
> technical constructs.  regions, agents, etc.
>

Agreed. We'll probably retain "virtual world" where the description is
entirely to evoke the problem space, but avoid it elsewhere.

We should have a new draft charter out tomorrow.