Re: [ogpx] OGPX WG draft charter, 2009-08-19 revision

Joshua Bell <josh@lindenlab.com> Fri, 21 August 2009 00:16 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 6D1073A6D30 for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 17:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.671
X-Spam-Level:
X-Spam-Status: No, score=-1.671 tagged_above=-999 required=5 tests=[AWL=0.305, 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 0BBj3QRXYfPE for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 17:16:08 -0700 (PDT)
Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by core3.amsl.com (Postfix) with ESMTP id B90203A6EFF for <ogpx@ietf.org>; Thu, 20 Aug 2009 17:16:03 -0700 (PDT)
Received: by gxk17 with SMTP id 17so438681gxk.19 for <ogpx@ietf.org>; Thu, 20 Aug 2009 17:16:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.91.143.18 with SMTP id v18mr378317agn.71.1250813766776; Thu, 20 Aug 2009 17:16:06 -0700 (PDT)
In-Reply-To: <20090820235657.GB21280@alinoe.com>
References: <e0b04bba0908191914h4837045ct777d2c63a30ddaf0@mail.gmail.com> <e0b04bba0908192003p34a367f2q4b99be3cf916cd72@mail.gmail.com> <20090820141835.GB28751@alinoe.com> <b8ef0a220908201101g3b448d8ck7b406fc481c56f8d@mail.gmail.com> <e0b04bba0908201342hd17ce91qac0136124cd3a444@mail.gmail.com> <f72742de0908201426m6b8feac9v57e9ef1cd73e5c06@mail.gmail.com> <f72742de0908201600y46311454la8db52c4be1b18dc@mail.gmail.com> <b8ef0a220908201609m1c77be2n3d499b7da20fec5a@mail.gmail.com> <20090820235051.GA21280@alinoe.com> <20090820235657.GB21280@alinoe.com>
Date: Thu, 20 Aug 2009 17:16:06 -0700
Message-ID: <f72742de0908201716i6f5adc29o18313a6e55318a7f@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e643559a3fb67204719bc69d
Subject: Re: [ogpx] OGPX WG draft charter, 2009-08-19 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: Fri, 21 Aug 2009 00:16:09 -0000

On Thu, Aug 20, 2009 at 4:56 PM, Carlo Wood <carlo@alinoe.com> wrote:

> On Fri, Aug 21, 2009 at 01:50:51AM +0200, Carlo Wood wrote:
> > As a result, an agent domain shouldn't care less where someone
> > wants to go, because they are never responsible, and therefore
> > it should NOT be a matter of policy where someone can or cannot
> > teleport while keeping their inventory: it should simply be
> > possible, because the address is given in the LandMark.
>
> What I guess is my main point, is that I think that we can
> keep using "virtual world" (or just world in short) and
> that that should refer to a (group of) region(s) under
> one administration, and not to the agent domain; where
> the world can (therefore) have a different TOS, has
> world-wide bans issued by said administration, deals with
> every Abuse Report against avatars in their region,
> and which even could run on machines in a country with
> different laws than the worlds of other administrations.
>

I'm a fan of that loose definition of "world" myself. I think I alluded to
something similar earlier, but to try and rephrase to cover our shared
thinking: the boundaries of a "world" are where a user notices (or should
notice) a difference due to policy or behavior.

Like "web site" it isn't clear that that's a technical term; it shouldn't
keep us from using the term (since we have roughly shared understanding of
the meaning) but on the other hand we shouldn't fixate on a rigorous
technical definition since it doesn't seem to be a first-class entity within
the drafts we're focusing on right now.

Huzzah, convergence!