Re: [ogpx] VWRAP Draft Charter: 2009 08 28 revision

Kari Lippert <kari.lippert@gmail.com> Sun, 30 August 2009 12:05 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 11F1C28C0F2 for <ogpx@core3.amsl.com>; Sun, 30 Aug 2009 05:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 UJTCWXbld0Jj for <ogpx@core3.amsl.com>; Sun, 30 Aug 2009 05:05:28 -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 C04B728C0EB for <ogpx@ietf.org>; Sun, 30 Aug 2009 05:05:27 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 22so676991eye.51 for <ogpx@ietf.org>; Sun, 30 Aug 2009 05:05:32 -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:content-type; bh=A0uDWpZGR8n3xqAVU+fYFC1hCzz4AIIzpFlyngo7c5g=; b=cG2sCcWzpPVIXIZR2v5CrqhvrnIBitqzn9CZg/Bx0lMluHMgJ6fwCG5QCLzbZPy8Fl SDrupTI+RmMZ14RVHsGjzA4oCOA+4ZpbaRYbEkEnr6DUiK83BSOx8MKVrA7DD9YCA4zt IJW72yi0b9qtY1D9DtQJmkRgBQZkQlxlcxUhs=
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 :content-type; b=kxfP3H+70FpUsuzHOfy1B6mupiVATl008O0sk0xIPoaAO5iJ14HDE/DPrPdnYNQgxh jXw+DUOf/e/MUCj57evVhEPuaRtYkYSOJIr1CCFhanunb/A00C3UCS9alRHkiwXbX95l nMOPeo/tXctP1prt0PaYnNoqD5hYrvO4t8q60=
MIME-Version: 1.0
Received: by 10.216.55.201 with SMTP id k51mr791852wec.184.1251633932729; Sun, 30 Aug 2009 05:05:32 -0700 (PDT)
In-Reply-To: <e0b04bba0908300225l34ec9f35x465d46f34313b60c@mail.gmail.com>
References: <3a880e2c0908281127h6965f332na493007b032e5e93@mail.gmail.com> <20090830003055.GD22756@alinoe.com> <b8ef0a220908291754x31f24ea7x702100d6aa9810ef@mail.gmail.com> <e0b04bba0908300225l34ec9f35x465d46f34313b60c@mail.gmail.com>
Date: Sun, 30 Aug 2009 08:05:32 -0400
Message-ID: <382d73da0908300505t3f804865h629bec91ad59954a@mail.gmail.com>
From: Kari Lippert <kari.lippert@gmail.com>
To: ogpx@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [ogpx] VWRAP Draft Charter: 2009 08 28 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: Sun, 30 Aug 2009 12:05:29 -0000

My two cents....

The first paragraph (where the purpose is being laid out) says:

Conforming  client  applications use  the protocol  to manipulate and
move the  user's avatar, create  objects in  a virtual world, interact
 with other users  and their surroundings  and consume and create
media and information from sources inside and outside their virtual
world.

I normally lurk in this group but I have to say this surprised me.
This statement says that I will use this protocol within my virtual
world, not that I will use this protocol to interface with different
virtual worlds. This doesn't speak to what I thought the thrust was -
interoperability of worlds for transportability of avatars. While once
could argue that the use of the same protocol intra-world would help
in the inter-world communication, this is not the case and should not
be assumed to be so. I'm actually saddened that you're all thinking of
interoperability as achievable only if everyone uses the same
intra-world protocol.

"Enforcing" the use of a standard intra-world for every world will be
impossible and quite possibly viewed as some by an intrusion into
their IP, not to mention that it would kill innovation. Transfer
between worlds will be lossy: existing worlds are not the same, nor do
they have the same types of virtual property associated with them.
This standard is going to either have to address the bare minimum, or
become obsolete prior to completion with the introduction of a novel
virtual world into the virtual universe.

I concur with many of the discussions that have been put forth
regarding this draft and have the following suggestions:

Infinity Linden - good rewording to include OGP history; too confusing
to leave in the main body (a reader will think it a typo)

Morgaine - agree to remove sentence that begins "To support the
exegesis  of the specifications..."

meadhbh - deployment patterns are very different from models of
protocols; deployment patterns may be useful but should not replace a
good model

Morgaine - agree with the addition of the Foundation Component but
argue that it should also be the focus in the first paragraph of the
description

meadhbh/Morgaine/Carlo - redefinition of virtual world is a bad idea
but what you are really talking about is the virtual universe as
composed by a variety of virtual worlds - and I like the plain English
of Region 1 in VW 1 to Region 2 in VW 2 expression put forth as it is
very clear, easily understood, not easily misunderstood,  and I
believe captures the intent of the standard to be developed

Once we figure out the focus (which I take to be inter-world, or
cross-world, transfer) then we can begin capturing the requirements
for a "successful transfer". From that the model, the deployment
pattern(s), the conformance guidelines, and other associated parts of
the standard will come. So I ask, what is the focus (purpose) of the
working group? Why are you making all this effort? Is it to bring the
multitudes of virtual worlds to one protocol or to make transfer
between them possible? I posit those are two different standards and
only the latter is worth standardization.

<step off soapbox>
My two cents anyway....

Kari