Re: [vwrap] Status and future of the VWRAP working group

Boroondas Gupte <sllists@boroon.dasgupta.ch> Tue, 29 March 2011 01:40 UTC

Return-Path: <sllists@boroon.dasgupta.ch>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B83028C13E for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 18:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, 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 19EAyk0TR8JV for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 18:40:16 -0700 (PDT)
Received: from datendelphin.net (india288.server4you.de [85.25.150.202]) by core3.amsl.com (Postfix) with ESMTP id 188233A6833 for <vwrap@ietf.org>; Mon, 28 Mar 2011 18:40:15 -0700 (PDT)
Received: from [192.168.1.101] (adsl-62-167-25-70.adslplus.ch [62.167.25.70]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by datendelphin.net (Postfix) with ESMTPSA id DE4782E047; Tue, 29 Mar 2011 03:44:38 +0200 (CEST)
Message-ID: <4D9138E0.6090807@boroon.dasgupta.ch>
Date: Tue, 29 Mar 2011 03:41:52 +0200
From: Boroondas Gupte <sllists@boroon.dasgupta.ch>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110313 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: Meadhbh Hamrick <ohmeadhbh@gmail.com>, Morgaine <morgaine.dinova@googlemail.com>
References: <AANLkTim=tpngqs8gt=sjCeOQgtUATVRXXKe11qUaNJFw@mail.gmail.com> <BLU159-ds1192252375D420BE8C7C9EDCB90@phx.gbl> <956AEC85-F919-4C64-96BA-277B620CAB18@gmail.com> <AANLkTimLHwMb9u5Ok-44-JgHaL_EydeSHyHUQybvNpMp@mail.gmail.com> <20110326135320.GC29908@alinoe.com> <AANLkTin=9a35pzm9QkGt6v5PgWAgsqomkYCBG8eSa4Xg@mail.gmail.com> <AANLkTinp2+skkPP0L1sWtTn1-OU=Q6_YXk_W1+QdL-8Q@mail.gmail.com> <AANLkTin25vWxk9Wd1U3ne_4DedU4Cz5JhMHTzt9gDyfA@mail.gmail.com> <AANLkTimM=ERx_WctgAzHhgm_GE_cVYM0j6FXp6xMthds@mail.gmail.com> <AANLkTi=aghMKoOusjwbC7wyh=kzZwEY7a3_VCiw93ZYB@mail.gmail.com> <4D9116A4.8010602@boroon.dasgupta.ch> <AANLkTim_wpu3_a7doRDPafQEahgAZV6X+z5H-=7_GQAU@mail.gmail.com>
In-Reply-To: <AANLkTim_wpu3_a7doRDPafQEahgAZV6X+z5H-=7_GQAU@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030401000502030407010506"
Cc: vwrap@ietf.org
Subject: Re: [vwrap] Status and future of the VWRAP working group
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 01:40:17 -0000

On 03/29/2011 02:00 AM, Morgaine wrote:
> On Tue, Mar 29, 2011 at 12:15 AM, Boroondas Gupte
> <sllists@boroon.dasgupta.ch <mailto:sllists@boroon.dasgupta.ch>> wrote:
>
>
>     d. interoperability between (instances of) any two virtual world
>     systems
>     conforming to the (to be defined) VWRAP standard.
>
>
>
> Exactly as Boroondas says.  Indeed, that is the interoperability goal
> sought by the majority of contributors here over the years, so this is
> nothing new. It's the feature that virtual worlds don't yet have, and
> that's why it's worthwhile to work on it.

On 03/29/2011 02:25 AM, Meadhbh Hamrick wrote:
> i think that's the same thing as "service level interop" with the
> added requirement that participants implement all services.

Let me get this straight. If we

    * take this "interoperability between VW systems" (as propagated by
      Morgaine),
    * assume these systems are composed from separable services and
    * drop the requirement that each service provider (I'd like to avoid
      the term "participant" here, as that could also refer to end users
      or their user-agents) provides a complete set of services (i.e. a
      "whole" virtual world, that could function on its own), but
      instead allow them to offer single services that only form a
      virtual world when combined with other services from other
      compliant providers

we end up with "service level interoperability" (as propagated by Meadhbh)?

(Please speak up if I'm misreading any of you.)

If that is actually the case, most of the differences within the group
might be merely in nomenclature. Or maybe the difference isn't mainly in
the entities we want to interoperate, but instead in what we mean by
interoperation? Or have we ended up at a formulation abstract enough
that people can agree with it even when they actually have different
goals from each other?

Slightly confused,
Boroondas