Re: [ogpx] URI schema for virtual world locations?

Kari Lippert <kari.lippert@gmail.com> Sun, 24 January 2010 14:53 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 1C7343A689A for <ogpx@core3.amsl.com>; Sun, 24 Jan 2010 06:53:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 oafaldcsRqFA for <ogpx@core3.amsl.com>; Sun, 24 Jan 2010 06:53:35 -0800 (PST)
Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by core3.amsl.com (Postfix) with ESMTP id 392AB3A6892 for <ogpx@ietf.org>; Sun, 24 Jan 2010 06:53:34 -0800 (PST)
Received: by ewy26 with SMTP id 26so1236785ewy.28 for <ogpx@ietf.org>; Sun, 24 Jan 2010 06:53:32 -0800 (PST)
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=FxuBUlzaKt19ML757p2K/cdhtKs84NIoQFPPXontic4=; b=ltGzrnGQVAMyIrONI16FQ/T/Pf6NzABS01ndXXh87BZWQQW1h/b09j3N5oAyZ0CUz1 Ega3uwlXiemqtPgUcuCIX/OGdcN3GD4TkiLtEm8/+MGVmBYGlohp5nTSw2ffD2/gFuUt YgijqN4LdYX4WQWIfhNH5UD2luv0E3RjGp23g=
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=kEMSeO6O+IJIoshsKm4tLzYEnnYs44pqhNzJ4D1WmaEe3anvptqRP+OHd4OODI+TnG 93VZIHwMjBHBhdWHROriuqgalweP+beMXQ/A+TUo8L5myWUY/+VxDlbtT7GextkV5eEA yIcUvv8HDDiKP9o4sSOTZxdIFScYUSju3Yst0=
MIME-Version: 1.0
Received: by 10.216.171.207 with SMTP id r57mr2099617wel.146.1264344812506; Sun, 24 Jan 2010 06:53:32 -0800 (PST)
In-Reply-To: <20100124135955.GA30394@alinoe.com>
References: <b8ef0a221001211132i1a76b959k6f5768f15c5aa03c@mail.gmail.com> <b8ef0a221001211310k11e87a57gda827e6dc2458c77@mail.gmail.com> <7765f2c61001220625h25580faexe0a20dca1f74a58b@mail.gmail.com> <0DF3EFDA-FDB3-45E4-91D1-051B1288E27C@bbn.com> <b8ef0a221001220802l4307cdc7m14b05426876afa66@mail.gmail.com> <f72742de1001220835s783eb958o11e5deac9b7ea9b4@mail.gmail.com> <b8ef0a221001221113o7a337fc1y45ec86d300140fa@mail.gmail.com> <20100123003637.GA23071@alinoe.com> <3a880e2c1001221818s11796ce9kd2e22153cdacd57b@mail.gmail.com> <20100124135955.GA30394@alinoe.com>
Date: Sun, 24 Jan 2010 09:53:32 -0500
Message-ID: <382d73da1001240653t210c4b9fv25ed126029cfe300@mail.gmail.com>
From: Kari Lippert <kari.lippert@gmail.com>
To: Carlo Wood <carlo@alinoe.com>
Content-Type: multipart/alternative; boundary="0016367fa8f56c504a047dea370a"
Cc: "Infinity Linden (Meadhbh Hamrick)" <infinity@lindenlab.com>, Meadhbh Hamrick <meadhbh.siobhan@gmail.com>, ogpx@ietf.org
Subject: Re: [ogpx] URI schema for virtual world locations?
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: Sun, 24 Jan 2010 14:53:37 -0000

When modeling information with disparate groups, this kind of discussion is
healthy. There is still an issue here with what each currently known service
requires, and what the science fiction types in the group think they might
require in future yet-to-be-built worlds. There have been a few proposals
for how to handle that but it's not clear to me that the solution
(require cartesian coordinates) will satisfy all comers. I'd like to propose
a very simple stating, by those who know, of how current worlds specify a
location of an avatar or object in their world. There may be another
solution (along the lines of a transformation service mentioned previously)
hiding out there. Certainly in the information I suggested initially there
needs to be added which world!  Can we get world-specific definition for
"location" from this list? Are there others that are not represented by
membership?

I'd also like to continue this discussion in the conceptual space - figuring
out implementation is a good exercise to test a solution but if done prior
to arrival at a solution it can hamper an exploration of the possible.

Kari


On Sun, Jan 24, 2010 at 8:59 AM, Carlo Wood <carlo@alinoe.com> wrote:

> I pressed the 'send' button too soon, but almost immediately followed
> up with a reply to myself (where I more or less took back the first
> part, that you comment on ;).
>
> My point was, there is only a need for a 3 dimensional cartesian coordinate
> system really, relative to a region.
>
> In order to be able to show map, it should be possible map regions
> to some 2 dimensional coordinate system.
>
> By using a global 3 dimensional *cartesian* coordinate system,
> and do the latter mapping by projecting along the z-axis, we'd
> force every world to be flat.
>
> If that is what we decide for, so be it. But if we want to avoid
> getting only flat worlds for some reason then we have two options:
>
> * Either add support for other coordinate systems (cylindrical, polar...)
>
> or
>
> * Let go of the "simple" way that local 3D coordinates are mapped
>  to the 2D 'map' coordinates.
>
> If on top of that we want to accommodate the fact that some regions
> are not connected at all (you can't fly or walk from one to the
> other: they do not have any intuitional or logical relative position),
> we need to add the notions of 'spaces' (mathematical word), or
> maybe call it 'map' as that is what it will boil down to: separate
> maps of connected regions (I recall having posted a proposed word
> for that for communication purposes: continents).
>
> Hence my proposal for points 1.3 and 1.4:
>
> 1.3. there may be two forms of location representation:
> map position (longitude/latitude) that give regions in a
> given space, a place on a map, and cartesian coordinates
> relative to the origin of a region (x,y,z).
>
> 1.4. the statement above (1.3) implies there is a public service
> available to map between the {space, longitude, latitude}
> "map coordinates" and points relative to a given region:
>
> {space/map, longitude, latitude} <---> {region name, x, y}
>
>
> I have no objection, not too strong anyway ;), against
> continents being flat on the map, only allowing curved
> land through special browsers. The reason for that is
> that I think that otherwise it's just too hard to create
> and show a map, something not worth the effort at this
> point, not even during the design of this standard :/
>
> Note that by setting "space/map" to a constant, this
> extended proposal is completely consistent with how
> SL currently works (one big map, and {longitude, latitude}
> being the global coordinates). Yet, it would discourage
> using {x, y, z} for global coordinates, but shows that
> it's needed / better to use {region, x, y, z} for
> locations, or alternatively {space/map, longitude, latitude, z}.
>
> --
> Carlo Wood <carlo@alinoe.com>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>



-- 


http://kjlippert.wordpress.com/
http://community.webshots.com/user/MissGnomer