Re: [ogpx] where does VWRAP fit?
Kari Lippert <kari.lippert@gmail.com> Fri, 11 September 2009 17:02 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 CCAF63A689B for <ogpx@core3.amsl.com>; Fri, 11 Sep 2009 10:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level:
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[AWL=0.231, 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 EbqnHNqLNprn for <ogpx@core3.amsl.com>; Fri, 11 Sep 2009 10:02:14 -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 756AC3A692B for <ogpx@ietf.org>; Fri, 11 Sep 2009 10:02:14 -0700 (PDT)
Received: by ewy3 with SMTP id 3so348364ewy.42 for <ogpx@ietf.org>; Fri, 11 Sep 2009 10:02:49 -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; bh=bdKbUr5oFA5GWsS/b0d06OGcpgt16KwAzsUg1luguok=; b=iV0hnzZ546gcGUpMcJOWuWUuxQvQM1E21ALdKG5+d9JyypnmY075pqW2/jE5Nkjm2s //Y72Mj5e/qQrXaX0+0ritCoFa+vHTSlpKksT5a0LM9X3LIka+29UEtVZ15Sp7418hMp mXXTj96gqG40eKXEkOelh2+O1sNLCibFba634=
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; b=myWA50IXJcl28hcKb3rl6LMops1Ia0+BcDXyX/eYiv/1QkkYciIBDFuwWfwbWVZJrC ng3OW2oI/E3Oj1D3tE52tR2gnvzn7U8abszMjkIrl7cxIRrRSlVE0P5iSuFmpNVL77el DHgHLhG4NNWq7FOZYnVcUqwNBC9iP1+kTcfRA=
MIME-Version: 1.0
Received: by 10.216.86.73 with SMTP id v51mr794011wee.89.1252688568683; Fri, 11 Sep 2009 10:02:48 -0700 (PDT)
In-Reply-To: <f72742de0909110915q61e051a8yeb623787a2ddd719@mail.gmail.com>
References: <382d73da0909060904h7b666bdqc40ce151ce0d241a@mail.gmail.com> <e0b04bba0909110036r3337f945tb93955fbac0c5798@mail.gmail.com> <f72742de0909110915q61e051a8yeb623787a2ddd719@mail.gmail.com>
Date: Fri, 11 Sep 2009 13:02:48 -0400
Message-ID: <382d73da0909111002g15e6720bgeae34b6843719e0e@mail.gmail.com>
From: Kari Lippert <kari.lippert@gmail.com>
To: Joshua Bell <josh@lindenlab.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: ogpx@ietf.org
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 17:02:15 -0000
> > 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. > Awesome - this clarifies what a region is. It also states that one region can exist 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. > Are you referring to "you personally" as the user perspective? If so, then this is consistent with what I understand. > 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. > If you are abstracting this definition from the start of my question regarding "virtual place" then you didn't quite understand. I take the blame for not properly describing it. What I was trying to say is that a "virtual place" is somewhere (not everywhere) the "virtual representation" (as opposed to the meat-body) can go. This statement was only made to clarify the term "virtual place" as I had intended to use it in place of the highly contested "virtual world". The "user community" currently associates the term "virtual world" with an application/service provider pairing. They can move around inside most of the "virtual place"s within that application/service provider pairing seamlessly. (Take as an example the difference between moving around different user-content-spaces in Second Life vs. user-content-spaces in Gogofrog. Both 3D, both user-content-spaces, one seamless and the other not.) I believe the desire of the "user community" is to move their "virtual representation" between one application/service provider set of "virtual place"s (which they call a "virual world") to another (e.g., OpenSim to Second Life) in a seamless fashion. I do not believe that the "user community" desires all of those "virtual place"s to be a single application/service provider pairing. I also believe the "user community" would abandon the whole thing if it all looked like it came from a cookie cutter! The future is what this protocol is to support, yes? I believe that future includes the ability to "walk through a door" (teleport, click a street sign or ad, etc.) to another "virtual place" -- from your island on Second Life to her room in Gogofrog to his place in Habbo. Yes, yes, I know, we're not talking about those sorts of places but I think they will factor in in the future. If Second Life, OSGrid, Reaction Grid and Science Sim are the countries, then these places will become the islands. We want to make sure we don't preclude travel to islands as we establish travel between countries, but rather define for the island (and the countries) what has to be in place to allow such travel. I thank you for the country travel analogy - as Charles says, it fits quite well when you consider all of the things involved in a border crossing. Kari
- [ogpx] where does VWRAP fit? Kari Lippert
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Joshua Bell
- Re: [ogpx] where does VWRAP fit? Charles Krinke
- Re: [ogpx] where does VWRAP fit? Kari Lippert
- Re: [ogpx] where does VWRAP fit? Meadhbh Siobhan
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Carlo Wood
- Re: [ogpx] where does VWRAP fit? Charles Krinke
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Charles Krinke
- Re: [ogpx] where does VWRAP fit? Marshall Eubanks
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Charles Krinke
- Re: [ogpx] where does VWRAP fit? Kari Lippert
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Joshua Bell
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Morgaine
- Re: [ogpx] where does VWRAP fit? Charles Krinke