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

Meadhbh Siobhan <meadhbh.siobhan@gmail.com> Thu, 20 August 2009 23:09 UTC

Return-Path: <meadhbh.siobhan@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 325B93A6A59 for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 16:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 WoHefoIlZIcP for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 16:09:35 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by core3.amsl.com (Postfix) with ESMTP id 1778F3A6916 for <ogpx@ietf.org>; Thu, 20 Aug 2009 16:09:35 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 5so201480qwi.31 for <ogpx@ietf.org>; Thu, 20 Aug 2009 16:09:38 -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:cc:content-type :content-transfer-encoding; bh=tSTYB5p9SGoYAbaJU7Q5/dQ9Gr/6U38efnB81w+ALBI=; b=E6Fh5RT4y40w/1vI2e8dtx++UdV8XAf5zdJiEQE1GgnbJZ4sd4KvliX4WTJJxq7Bho fCHnLlhWB+s2PPCwtD12sqakjtffJTfvpP3oRdneuv0Qn++C+2xdj/BCODhAXQjZ2u5p 1yjMDpgYjaL/idrQwCxXXdICJi669Izn5oU0Q=
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 :cc:content-type:content-transfer-encoding; b=al4wtIEqu40l8jpDR7t2FJ3GAJmWGEOhIxoj1Vt1hG7Bc95qe08c4vjg+bTgyj9dLA aW3WUPYD0bEhqFQGuxYoWN6R1s04knIlCyKPmSZZWDxUieuwM1e7MiMvYeyxL0aNrpA/ M8PcqMkW8uIkPibQfLJ1RfvaMsdZ8AAS2czoE=
MIME-Version: 1.0
Received: by 10.229.34.143 with SMTP id l15mr71027qcd.80.1250809778631; Thu, 20 Aug 2009 16:09:38 -0700 (PDT)
In-Reply-To: <f72742de0908201600y46311454la8db52c4be1b18dc@mail.gmail.com>
References: <f72742de0908191206m2a5b3e2fm4efcf0eaf471a758@mail.gmail.com> <e0b04bba0908191914h4837045ct777d2c63a30ddaf0@mail.gmail.com> <3a880e2c0908191925p506de284w5ebb5cab7d893256@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>
Date: Thu, 20 Aug 2009 16:09:38 -0700
Message-ID: <b8ef0a220908201609m1c77be2n3d499b7da20fec5a@mail.gmail.com>
From: Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
To: Joshua Bell <josh@lindenlab.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ogpx@ietf.org
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: Thu, 20 Aug 2009 23:09:36 -0000

the charter already says "Such virtual worlds may consist of regions
administered by distinct organizations."

i think we used the term "virtual world(s)" to help contextualize the
effort. if the term is confusing, we could use "region" and "region
domain" and "region host / simulator" in the body of the charter.

though i would argue that the term "virtual world" should appear
somewhere early in the description of the working group so people
reading the charter will have some context. (Dave C. and others have
argued persuasively out that peeps from outside the VW/OGP community
won't automatically know that "OGP" means "virtual worlds protocol."
consequently, i think "region domain" won't automatically translate to
"part of a virtual world" unless explicitly mentioned.)

-cheers
-meadhbh


On Thu, Aug 20, 2009 at 4:00 PM, Joshua Bell<josh@lindenlab.com> wrote:
> Ugh, I just realized that my last several posts were private replies, not
> reply-all messages. D'oh. Resending, but some context may be lost.
>
>
> On Thu, Aug 20, 2009 at 1:42 PM, Morgaine <morgaine.dinova@googlemail.com>
> wrote:
>>
>> On Thu, Aug 20, 2009 at 7:01 PM, Meadhbh Siobhan
>> <meadhbh.siobhan@gmail.com> wrote, in answer to Carlo Wood:
>>
>>> and to your point about landmarks and teleport.
>>>
>>> teleporting between points in the virtual world, even if the origin
>>> and destination are managed by different administrative domains has
>>> always been part of the protocol proposal. we're not taking that out.
>>
>>
>> That was not Carlo's point.  Carlo asked about landmarks and teleports
>> between  virtual worlds, so stating that you're not taking them out from
>> within a single world is not answering his question.
>>
>> The question being asked is a very simple one.  I do not understand why a
>> clear answer is not being given.
>
> I think we all agree (ahem, have rough consensus) on this statement:
>
> * OGP should support teleports between regions that are part of different
> administrative domains, when policy permits.
>
> I think the hard part is that "world" is not a well defined concept in OGP.
> We can't say "OGP should support teleports between different worlds" when we
> can't define "world". I maintain that "world" is not a technical term, just
> as the HTTP RFCs do not define "web". (The term is used in the preamble, but
> not defined.) Personally, I think the term "world" will come to mean
> something I'll hand-wavily call policy-clusters-of-agent/region-domains,
> meaning groups of places avatars can easily (not necessarily freely)
> traverse; some "worlds" will span multiple administrative domains, some
> won't. But I don't want to try and define that now!
>
>> This is a matter of huge importance to the large number of SL-compatible
>> open grids that already exist, with more appearing regularly.  It needs to
>> be clearly stated whether mechanisms for interop between SL-compatible
>> worlds will be within the scope of the OGPX group, or not.
>
> Would it help if we added a parenthetical "(which may be described as one or
> more virtual worlds)" or something somewhere in the charter? IMHO, it does
> not add technical detail to the charter, but if it makes it more appealing
> or comprehensible to those not embedded in the process, it's worthwhile.
>
>>
>> Defining our scope is our primary task at this time.  This question cannot
>> be dodged.
>
> Agreed. And it may be that we're being too precise/pedantic in the charter
> text.
>
>
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>