Re: [ogpx] Definitions of terms to be used in my (our?) communication
Meadhbh Siobhan <meadhbh.siobhan@gmail.com> Mon, 31 August 2009 18:08 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 9418328C448 for <ogpx@core3.amsl.com>;
Mon, 31 Aug 2009 11:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038,
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 XcCcrP1+JaIR for
<ogpx@core3.amsl.com>; Mon, 31 Aug 2009 11:08:05 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com
[209.85.146.181]) by core3.amsl.com (Postfix) with ESMTP id 7D47228C446 for
<ogpx@ietf.org>; Mon, 31 Aug 2009 11:08:05 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id v27so578344wah.5 for
<ogpx@ietf.org>; Mon, 31 Aug 2009 11:08:13 -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=1DymnKFj5JvHJHFmGPXLimPyFeDVKygofMzViYwt3Xw=;
b=krQGYpPOcdojJztBIGc0sBDXldo3SZ9qEz50CmmbESGUrJriIXz1wD2/9owgGcBccJ
vrrHUQUofIT26IHc/ZgxyQXACiI/L4n8lUj8Cctquyc3h+/yVIfYq7Yh63/qTHwNcFof
nmxpzcOiIBC0cDl7MKoRwqrhctz5EPtRY3lwE=
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=kLOQuIZG0/JDjOKd1ioCeLRxj2PMlzB0de8QPziMEckdATbPaS1xx5L+v+mhlQEthr
lpGJsTv39rreQLftlY0SqEStr5TyzVoAAN9HvKh0at/4ltM4RCM6O/FySF8pPgMdI031
9vFbNsPDrnUCrGzieP6qQ/Ipz9VlAuF46s0tI=
MIME-Version: 1.0
Received: by 10.115.51.16 with SMTP id d16mr2955441wak.165.1251742093767;
Mon, 31 Aug 2009 11:08:13 -0700 (PDT)
In-Reply-To: <20090831170006.GB15637@alinoe.com>
References: <20090831170006.GB15637@alinoe.com>
Date: Mon, 31 Aug 2009 11:08:13 -0700
Message-ID: <b8ef0a220908311108v5d8a2b72v45c759c6bf421971@mail.gmail.com>
From: Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
To: Carlo Wood <carlo@alinoe.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Definitions of terms to be used in my (our?) communication
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 18:08:06 -0000
hey carlo, just as a fyi, we have some _slightly_ different terms/definitions in OGP/VWRAP than in SL. just a reminder, OGP/VWRAP is decidedly not legacy SL protocol. (sorry if i sound like a broken record about that) but before i comment on these terms, let me point out that while this discussion is interesting and germane to the subject of virtual worlds, it is a bit out of scope for a discussion about the charter. so, can we just for right now, just use the terms that have been defined in the way that they're defined and get through the charter bashing? i PROMISE you, that we'll get back to terms in more detail, and honestly, i like your use of the term "universe." in the current OGP/VWRAP documents, the term "island" and "galaxy" aren't used. your use of the term "region" is different than the way it's described in the intro doc. what you call a "region" below, we would call a "region domain." what we call a "region" is the set of data used to represent a collection of adjacent points in the virtual world. i'm hoping that the verbiage in the draft charter makes it clear that services that export information about the region or provide an interface to modify the region's state go through a single region specific URI. the "simulator" is the server process that maintains the region's state and processes service requests. the "simulator host" or "region host" is the machine itself that the simulator process runs on. further, a "domain" is a collection of resources administered by a single entity. thus a "region domain" is a collection of regions that are run by the same entity, and presumably _could_ be governed by the same terms of service, or more importantly to us, could potentially be considered a single end entity in the trust model. we haven't put the term "adjacent region" into the doc, and now that i see you talking about it, i think it was an oversight not to. or rather, maybe just to talk about "adjacency" in general. for people who are unfamiliar with SL, adjacent regions are simply regions that are next to each other in the geometry of the virtual world. in second life, a region communicates with adjacent regions so the original region can tell the client the state of assets it's managing, if the client needs to know about it and policy says the client can access that information. *whew* in SL, the term "island" sometimes means regions that have no adjacent regions (i.e. - they're out in the virtual ocean, all by themselves) or about a virtual landscape that looks like an island. (obviously, the former is more interesting to this group than the latter at this moment.) the terms "land" and "continent" are not defined in the spec. SL uses "continents" for administrative and (some) billing purposes. we are not trying to foist this aspect of SL off on the unsuspecting public. that is, it works well for us to divide things into continents, and if someone other than Linden wants to do this, good on ya. but, requiring that this be a part of the specification is not harmonious with our objective of not having people say bad things about us. "galaxy" is also not defined in the spec, or by any of implementors who worked on OGP over the last 2 years. "virtual world" is defined informally as discussed earlier on this list. i know morgaine frequently uses the term "region domain" to describe what we would call a "virtual world." "VWRAP Universe" is not defined now, and i'm generally loathe to introduce new terms, but i have to admit, i kinda like this one. but let's talk about it more later. about "MMOX Universe.." as far as i can tell, no one is working on MMOX currently, so we might want to say "non-VWRAP universe" to describe universes that are not VWRAPish. On Mon, Aug 31, 2009 at 10:00 AM, Carlo Wood<carlo@alinoe.com> wrote: > A) A smallest partition > > REGION > > B) A collection of adjacent regions run by a single administration > > ISLAND or ADJACENT REGIONS > > C) A collection of adjacent regions's run by different administrations > (which very likely use the same TOS etc) > > LAND, or CONTINENT when larger. > > D) A collection of continent's that are not adjacent but still fall > under the same TOS, likely use the same inter-world protocols > and organisation-specific extensions etc (likely, they will > have their own website and their own Abuse Report team etc). > > VIRTUAL WORLD > > E) A collection of Virtual World's that have totally different > administrations and possibly different TOS etc, but which > interoperate (ie, you can pass on a Landmark of one VW to > a person you meet in another VW). > > GALAXY > > F) The whole of all Galaxies that do not interoperate, but still use VWRAP. > > VWRAP UNIVERSE > > G) The rest that use the term "virtual world", but do not use VWRAP. > > MMOX UNIVERSE > > > Please state if > * you have problem with me going to use these terms consistently in my posts > * you will use these terms with the same meaning > * you wish to give these terms a different meaning > > I understand there is also something called "REGION DOMAIN", but > I have no idea which of the above that would be as it's not my > term and it was never discussed. > > -- > Carlo Wood <carlo@alinoe.com> > _______________________________________________ > ogpx mailing list > ogpx@ietf.org > https://www.ietf.org/mailman/listinfo/ogpx >
- [ogpx] Definitions of terms to be used in my (our… Carlo Wood
- Re: [ogpx] Definitions of terms to be used in my … Kari Lippert
- Re: [ogpx] Definitions of terms to be used in my … Meadhbh Siobhan
- Re: [ogpx] Definitions of terms to be used in my … Meadhbh Siobhan
- Re: [ogpx] Definitions of terms to be used in my … Carlo Wood
- Re: [ogpx] Definitions of terms to be used in my … Carlo Wood
- Re: [ogpx] Definitions of terms to be used in my … Infinity Linden
- Re: [ogpx] Definitions of terms to be used in my … Infinity Linden
- Re: [ogpx] Definitions of terms to be used in my … Infinity Linden
- Re: [ogpx] Definitions of terms to be used in my … Carlo Wood
- Re: [ogpx] Definitions of terms to be used in my … Meadhbh Siobhan
- Re: [ogpx] Definitions of terms to be used in my … Carlo Wood
- Re: [ogpx] Definitions of terms to be used in my … Dave CROCKER