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

Carlo Wood <carlo@alinoe.com> Sat, 23 January 2010 00:36 UTC

Return-Path: <carlo@alinoe.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 E0FDB3A659B for <ogpx@core3.amsl.com>; Fri, 22 Jan 2010 16:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.047
X-Spam-Level:
X-Spam-Status: No, score=0.047 tagged_above=-999 required=5 tests=[AWL=-0.937, BAYES_40=-0.185, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 VizSotYJODnk for <ogpx@core3.amsl.com>; Fri, 22 Jan 2010 16:36:48 -0800 (PST)
Received: from viefep15-int.chello.at (viefep15-int.chello.at [62.179.121.35]) by core3.amsl.com (Postfix) with ESMTP id 3DE1028C0D8 for <ogpx@ietf.org>; Fri, 22 Jan 2010 16:36:48 -0800 (PST)
Received: from edge05.upcmail.net ([192.168.13.212]) by viefep15-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20100123003640.NVNE10247.viefep15-int.chello.at@edge05.upcmail.net>; Sat, 23 Jan 2010 01:36:40 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge05.upcmail.net with edge id Yocd1d01Z0FlQed05ocesE; Sat, 23 Jan 2010 01:36:40 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.71) (envelope-from <carlo@alinoe.com>) id 1NYTzR-0006bE-2A; Sat, 23 Jan 2010 01:36:37 +0100
Date: Sat, 23 Jan 2010 01:36:37 +0100
From: Carlo Wood <carlo@alinoe.com>
To: Meadhbh Hamrick <meadhbh.siobhan@gmail.com>
Message-ID: <20100123003637.GA23071@alinoe.com>
References: <a768bcd91001211023h7e502394y9a65b399f1ee4b56@mail.gmail.com> <8FB8EE72-4938-4DA2-8134-6496DBF6ADE5@gmail.com> <b8ef0a221001211132i1a76b959k6f5768f15c5aa03c@mail.gmail.com> <BD24FA22-060C-44F8-8897-9D2808CC1769@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <b8ef0a221001221113o7a337fc1y45ec86d300140fa@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: 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: Sat, 23 Jan 2010 00:36:50 -0000

On Fri, Jan 22, 2010 at 11:13:46AM -0800, Meadhbh Hamrick wrote:
> 1.3. there may be two forms of location representation: absolute
> position within the virtual world (as denoted by a single point in
> space) or relative to the origin of a region.
> 
> 1.4. the statement above (1.3) implies there is a public service
> available to map between points in the absolute space of the virtual
> world and points relative to a region.

It is not true that the relative position of any two arbitrary
regions is known. For example, some world could consist of
of planets in solar systems and some would simply be too far
apart to use coordinates in meters. Another example are
the islands of private sims in SL.

Hence, it makes more sense to limit coordinates to a Cartesian
coordinate system relative to a given region, and be have
a public service that maps region name pairs to a relative
position vector v(name1,name2), or returning nil if they are
not in the same space.

The distance between {name1, v1}, where v1 = {x1,y1,z1},
and {name2, v2} is then v(name1, name2) + v2 - v1.

That way a world is not obliged to have one single space
where in every region must have a place.

Also, putting every region in one region will likely
lead to this 2D plane with regions and a z-coordinate
with a range equal to that of each region: a flat world
(like SL). I hope everyone knows that ANY example that
breaks a protocol is prove that the protocol is wrong ;),
so here it goes: someone might want to create "ring world"
(http://en.wikipedia.org/wiki/Ringworld), where the
rings exists of square regions, and the diameter of the
ring is too large to really want to use it. Such a world
could not very easily map it's world positions to a
flat one (or even x/y/z, without getting really large
and seemingly random numbers).

A better approach therefore seems to be:

A Cartesian coordinate system for one region at a time.
A map from region names to a 2-dimensional *map* coordinates,
where the map coordinates might have any arbitrary relationship
to world coordinates (being irrelevant), including the
notion that two regions might not be in the same space.

This would allow painting a map on a 2D surface (which can
be used to explore and retrieve LM's from), but it would
NOT allow to calculate the (real 3-D space) distance between
points.

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, longitude, latitude} <---> {region name, x, y}

-- 
Carlo Wood <carlo@alinoe.com>