Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revision

Kari Lippert <kari.lippert@gmail.com> Mon, 31 August 2009 11:52 UTC

Return-Path: <kari.lippert@gmail.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 5A7C33A6BB8 for <ogpx@core3.amsl.com>; Mon, 31 Aug 2009 04:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level:
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74]
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 HIyH-X6c+lYx for <ogpx@core3.amsl.com>; Mon, 31 Aug 2009 04:52:45 -0700 (PDT)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id F15153A6BC9 for <ogpx@ietf.org>; Mon, 31 Aug 2009 04:52:44 -0700 (PDT)
Received: by ewy3 with SMTP id 3so446985ewy.42 for <ogpx@ietf.org>; Mon, 31 Aug 2009 04:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=0C+HfVdfpZhcQm6+Jkmj1Q5PIcEJs4Sk1s2ByjYfxnM=; b=xXAvvMsKiapDik1w0UDjGZj5qlagh9wrot+1R3om4lCZv4O7c1BzWifPlvI4CnviA8 yCnHMzK9Kfp1M/Gh2Y2OxuvAFqt5YYGHMvp4VDbDUDIa97TEzmQ6EHHcD3DCqUVZ+MQ+ 1q3InfxKOey+y5CU/ijAWczBbLpjHNdGXqg+Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=S/KdizSGbcTG3Ww+v/PtkrerRU4Qt/sldqzvMkJiFcjbzEf5OCnwHLkquxNlB+3v1w qI7XdprPUeQTEuhwoKhWepXmjQX9z7EeC2eBWR3G22NzZNNhw7z7eAiBhdmtVKOLuGlX mm8DZxb/lbM0c0tPUqlAiIbwvDj4ecYoSZ084=
MIME-Version: 1.0
Received: by 10.216.28.66 with SMTP id f44mr1131080wea.28.1251719569838; Mon, 31 Aug 2009 04:52:49 -0700 (PDT)
In-Reply-To: <e0b04bba0908302127u4f36b98fp81e766c2cbc6526a@mail.gmail.com>
References: <3a880e2c0908281127h6965f332na493007b032e5e93@mail.gmail.com> <20090830003055.GD22756@alinoe.com> <4A9A8F7D.6070501@dcrocker.net> <b8ef0a220908301013t29821ac5q8d03d97002bdfdb1@mail.gmail.com> <20090830230832.GB25364@alinoe.com> <e0b04bba0908302127u4f36b98fp81e766c2cbc6526a@mail.gmail.com>
Date: Mon, 31 Aug 2009 07:52:49 -0400
Message-ID: <382d73da0908310452s50afa853qb2950cc26cfa30cb@mail.gmail.com>
From: Kari Lippert <kari.lippert@gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>, ogpx@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revision
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 11:52:46 -0000

This sounds like a good plan.

Kari


On Mon, Aug 31, 2009 at 12:27 AM,
Morgaine<morgaine.dinova@googlemail.com> wrote:
> I support Carlo's request that we define the terms that we use before we use
> them.
>
> As Carlo's says, undefined terms should not be used in the charter or in the
> group name --- it introduces uncertainty and confusion.  I would add that
> even less should undefined terms appear in our protocol specifications,
> which are relatively precise documents of interest to implementors.  If we
> don't know what a virtual world is, the term should be abandoned in favour
> of one that we do understand.
>
> Carlo offers one way of defining the topological entities in our problem
> space, based on size and administration, which sounds quite viable.  A
> meaning of virtual world might be agreed in this way.
>
> As an alternative, I propose a simpler and much more flexible approach:
> define virtual worlds as anything that implements the required endpoints of
> the VWRAP protocol.  We do not need to know anything else about them.  This
> lets the people who actually design the virtual worlds decide what
> constitutes a virtual world.  The only thing that interests us is that these
> "virtual worlds" implement the VWRAP endpoints.
>
> This is highly workable in practice.  After all, Linden Lab knows that SL is
> a virtual world, they don't need it defined.  Likewise, the owners of OSgrid
> know that OSgrid is a virtual world too, they don't need it defined.  As a
> result, a definition of "virtual world" by an IETF workgroup will have
> little practical effect outside of the specifications, because the
> implementors will design their worlds as it suits them.  If they are to
> interoperate through VWRAP however, then both LL and OSgrid will ensure that
> they implement the protocol correctly, no matter their internal differences.
>
> Note that this is the approach taken in a large number of IETF protocols:
> the implementation behind the endpoint is just an implementation detail, and
> is of no consequence as long as it implements the protocol correctly.
> Precedent suggests that this is the right approach.
>
> I believe that this is simpler, more powerful, and much more flexible than
> defining "virtual world" on the basis of topology.  All we need to know is
> that VWRAP endpoints are available, and not what kind of entity actually
> implements them.
>
> Morgaine.
>
>
>
>
>
>
>
>
> ===================================
>
> On Mon, Aug 31, 2009 at 12:08 AM, Carlo Wood <carlo@alinoe.com> wrote:
>>
>> I think that any effort to work on the final wording
>> should be stopped until we finally agree on what "virtual world" means...
>>
>> I understand that you don't want to define what virtual world means,
>> in which case you shouldn't use it at all in the charter and also
>> not in the protocol name (VWrap).
>>
>> There are several levels of 'locations' in an SL-like whatever:
>>
>> First, the words that are already in use by the community:
>>
>> 1) simulator
>> 2) estate
>> 3) region
>> 4) land
>> 5) island
>> 6) virtual world
>>
>> Then the locations that we need terms for to be able to even
>> TALK about them:
>>
>> A) A smallest partition
>> B) A collection of adjacent A's run by a single administration
>> C) A collection of adjecent B's run by different administrations (which
>> very likely use the same TOS etc)
>> D) A collection of C's that are not adjacent but still fall under the same
>> TOS etc.
>> E) A collection of D's that have totally different administrations and
>> possibly different TOS etc, but which interoperate.
>> F) The whole of all E's that do not interoperate, but still use VWRAP.
>> G) The rest that use the term "virtual world", but do not use VWRAP.
>>
>> MMOX and WoW is part of G. I consider that not relevant as it should be
>> clear by now what is part of G and what not.
>>
>> Meadhbh, do you disagree with my list(s)?
>> Anything you want to add, or change my rough definitions of things?
>>
>> Please don't reply with "we don't want to define this" :p
>> We NEED to define this, or we can't TALK about this!
>>
>> --
>> Carlo Wood <carlo@alinoe.com>
>>
>> PS I hope it should be clear by now: the problem we are having
>>   is that you call 'E' "a virtual world", while Morgaine, Kari,
>>   me and others want to call 'D' "virtual world". Moreover,
>>   you do as if D or E do not exist, so that we will not
>>   be able to talk about them separately later on :/
>>
>>   You might convince me to call 'E' "virtual world", but
>>   then we need a well defined term for 'D' in order to
>>   communicate about D, too.
>>
>>   In my previous post I proposed to use "Galaxy" for E.
>>
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>