Re: [ogpx] where does VWRAP fit?

Joshua Bell <josh@lindenlab.com> Fri, 11 September 2009 16:15 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 405183A6AC2 for <ogpx@core3.amsl.com>; Fri, 11 Sep 2009 09:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.529
X-Spam-Level:
X-Spam-Status: No, score=-0.529 tagged_above=-999 required=5 tests=[AWL=-0.967, BAYES_40=-0.185, 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 RromEn1zvvh1 for <ogpx@core3.amsl.com>; Fri, 11 Sep 2009 09:15:18 -0700 (PDT)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id AFBBB3A682E for <ogpx@ietf.org>; Fri, 11 Sep 2009 09:15:17 -0700 (PDT)
Received: by bwz19 with SMTP id 19so891120bwz.37 for <ogpx@ietf.org>; Fri, 11 Sep 2009 09:15:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.14.131 with SMTP id g3mr1455151faa.68.1252685748623; Fri, 11 Sep 2009 09:15:48 -0700 (PDT)
In-Reply-To: <e0b04bba0909110036r3337f945tb93955fbac0c5798@mail.gmail.com>
References: <382d73da0909060904h7b666bdqc40ce151ce0d241a@mail.gmail.com> <e0b04bba0909110036r3337f945tb93955fbac0c5798@mail.gmail.com>
Date: Fri, 11 Sep 2009 09:15:48 -0700
Message-ID: <f72742de0909110915q61e051a8yeb623787a2ddd719@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary="00151747af9a0fdb1e04734fa1ff"
Subject: Re: [ogpx] where does VWRAP fit?
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, 11 Sep 2009 16:15:19 -0000

On Fri, Sep 11, 2009 at 12:36 AM, Morgaine
<morgaine.dinova@googlemail.com>wrote:

> *Users* of *virtual worlds* know exactly what the term means, in the same
> way that they can distinguish one country from another when they go on
> holiday.  People have been living with the concept of different places ever
> since they started travelling beyond their village boundary, and nowadays
> the popularity of tourism embodies that concept most vividly in the form of
> *countries*.  Different countries tend to look different and have
> different cultures and different rules (local policies).  This is entirely
> natural and instinctive to us.
>

And yet, from a formal/legal perspective, things are far more complicated
than this, which is why "countries" is a non-technical term and those
seeking to be precise use lovely terms like "nation-states". Check out
http://en.wikipedia.org/wiki/Nation for some discussion about the
terminology, or think about examples like England which is a country by yet
not a sovereign state; it is part of the United Kingdom of Great Britain and
Northern Ireland, which in turn is a sovereign member state of the European
Union (Hopefully I got that right...). Or think of microstates - contested
and otherwise. It's not our job as technology implementers and spec writers
to dictate policy, or disenfranchise the world-view of others.


> That concept doesn't disappear when "places" become digital.  Instead the
> concept blossoms, because without the constraints of the physical world,
> virtual places can be so dramatically different.


Agreed. Just as the real world is not simply partitioned into "countries",
virtual places will express far more organizational variety than we can
currently imagine. I don't feel anointed to define terminology for the
future users of such technology.

Having removed it, we can then address how VWRAP implements the
> user-oriented requirement of interop between multiple virtual worlds, since
> removing the "single VW" will allow us to refer to more than one VW.  We've
> already been told authoritatively that, as it stands, the protocol will only
> connect single regions or a region domain of regions to one single virtual
> world, and not interop with a whole other VW.


There is no such authority that could make such a statement. The draft
charter does not speak in a normative fashion about virtual worlds,
precisely to avoid such claims - based on your feedback!

VWRAP as a protocol suite should provide the framework for moving agents
between regions. Regions are represented as sets of services, which can be
provided by multiple service providers, and within multiple trust domains.

Given that, if you personally define "virtual world" as a set of regions
that are provided by a single service provider, then VWRAP should indeed
provide the framework for agents to traverse those multiple virtual worlds,
policy permitting.

If you personally define "virtual world" as the set of all regions that an
agent can visit (provided by one or more providers), then no, VWRAP would
not allow traversing multiple worlds because, by that definition, that agent
can only experience one such world.

Again, the draft charter text explicitly avoids talking about social
constructs like "virtual worlds" precisely for this reason, based on
feedback from you and others.