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

Morgaine <morgaine.dinova@googlemail.com> Thu, 20 August 2009 20:43 UTC

Return-Path: <morgaine.dinova@googlemail.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 AB2083A6F77 for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 13:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.826
X-Spam-Level:
X-Spam-Status: No, score=-1.826 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 E7wnt+Eigrqf for <ogpx@core3.amsl.com>; Thu, 20 Aug 2009 13:42:57 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by core3.amsl.com (Postfix) with ESMTP id E0CEC3A6F6B for <ogpx@ietf.org>; Thu, 20 Aug 2009 13:42:51 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 22so85134eye.31 for <ogpx@ietf.org>; Thu, 20 Aug 2009 13:42:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=WmqObAjo3TbrLMRGEr6HrmQGPmDd7jRjRKNPKA6XozE=; b=lF6nsXmroOxCNsouuQc0lzhA+IzoIeYcy+LWPkXTNGwwcwEp9L8aT78ZhZWVrSBo04 h751Xh96x/NpAnwb3cmWlJdBWDxqlyKdRHwuJxE+jg4jLb97dmVXdkxOgTsouzVRtqdf 7KdC095q4FhYxpjvSnkiE6bx+Zh9qlaRPq8KM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=k+I+oZ6H/YssD8f2F20pJw9/8F+HHhL10iztmuT/T33oFk6bx6mN/in54riAy38kj6 gj9UX1/waP+2iUoeepl7OQmIL69YgZHpb06nZH8pJxzznXzcJSmICMKSOScW8AhNj1dm +NMA5+cbiL/FVl6mFTCjvgIWL7G3iRHXSCZrk=
MIME-Version: 1.0
Received: by 10.210.11.17 with SMTP id 17mr237877ebk.96.1250800973752; Thu, 20 Aug 2009 13:42:53 -0700 (PDT)
In-Reply-To: <b8ef0a220908201101g3b448d8ck7b406fc481c56f8d@mail.gmail.com>
References: <f72742de0908191206m2a5b3e2fm4efcf0eaf471a758@mail.gmail.com> <3a880e2c0908191738x69235df3t4a42cdd5193ef5f7@mail.gmail.com> <e0b04bba0908191914h4837045ct777d2c63a30ddaf0@mail.gmail.com> <3a880e2c0908191925p506de284w5ebb5cab7d893256@mail.gmail.com> <e0b04bba0908192003p34a367f2q4b99be3cf916cd72@mail.gmail.com> <20090820141835.GB28751@alinoe.com> <b8ef0a220908201101g3b448d8ck7b406fc481c56f8d@mail.gmail.com>
Date: Thu, 20 Aug 2009 21:42:53 +0100
Message-ID: <e0b04bba0908201342hd17ce91qac0136124cd3a444@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0015174be630b9a95b047198cb21
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 20:43:01 -0000

On Thu, Aug 20, 2009 at 7:01 PM, Meadhbh Siobhan
<meadhbh.siobhan@gmail.com>wrote;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.

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.

Defining our scope is our primary task at this time.  This question cannot
be dodged.


Morgaine.







On Thu, Aug 20, 2009 at 7:01 PM, Meadhbh Siobhan
<meadhbh.siobhan@gmail.com>wrote;wrote:

> 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.
>
> sharable landmarks haven't been explicitly mentioned, but we do
> require a way to uniquely address locations in a virtual world
> (otherwise how do you represent where you're teleporting too?) there's
> been a lot of discussion about using URLs to uniquely identify
> regions. If you added an offset from the middle of the region to the
> region's URL, that would be the beginning of a landmark.
>
> hmm... i don't think we've explicitly mentioned that regions have a
> bounding surface and an origin, but lemme put that on the list of
> things to add to the spec.
>
> -cheers
> -meadhbh
>
> On Thu, Aug 20, 2009 at 7:18 AM, Carlo Wood<carlo@alinoe.com> wrote:
> >
> > I think that what Morgaine is trying to say is that
> > if Linden Lab's official (or hidden) policy is to NOT
> > interop with other virtual worlds, then they are not
> > the right party to trust when it comes to defining
> > a protocol that most, if not all, other parties DO
> > want to support interop.
> >
> > Since it seems, at this point, that the policy of
> > LL will prohibit interop in the future between
> > SL and other grids, there is a lack of trust right now;
> > and as a result of that lack of trust, a very clear
> > statement about the intent of the OGPX (as opposed to LL)
> > about interop MUST be part of this draft.
> >
> > Personally, I will reject any protocol that doesn't
> > make it a priority to concentrate on interoperability
> > (such as sharing LM's and teleporting). So, instead
> > of adding a paragraph that clearly states that the
> > objective of OGPX is to not support interop, I'd rather
> > see a paragraph added that clearly states that it
> > IS to support interop.
> >
> > The keyword here being "clearly". That is certainly
> > not the case at the moment.
> >
> > --
> > Carlo Wood <carlo@alinoe.com>
> > _______________________________________________
> > ogpx mailing list
> > ogpx@ietf.org
> > https://www.ietf.org/mailman/listinfo/ogpx
> >
>