Re: [vwrap] Status and future of the VWRAP working group
Morgaine <morgaine.dinova@googlemail.com> Tue, 29 March 2011 06:37 UTC
Return-Path: <morgaine.dinova@googlemail.com>
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 75CFB3A6826 for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 23:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.914
X-Spam-Level:
X-Spam-Status: No, score=-2.914 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 xu9nZ9YoP0iS for <vwrap@core3.amsl.com>; Mon, 28 Mar 2011 23:37:03 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 361DF3A67EF for <vwrap@ietf.org>; Mon, 28 Mar 2011 23:37:03 -0700 (PDT)
Received: by qwg5 with SMTP id 5so2805099qwg.31 for <vwrap@ietf.org>; Mon, 28 Mar 2011 23:38:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=MgEaBhmbDFmM0RHCVxECp9esyjYzY8SBxtVTL+bg/GE=; b=AvNACMJxwB0f4jf3LKjiCWbijMLjdAweEGj50Cdaa+ygR/JcgP98wAJnwfsxT4Hzep ZOOFTC3/GBAYFOfzJzZMBfHNBh8P2ex8PvDWGwZnj2b6SK7HHgFAarNnD8M+tmkxoNr6 bwF4+JLUGV+hEpP6gGJXqDwa+277PxVy/erVs=
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=AHXtDZnun5cfE+7c6v/XkwzALNtogo4FQ7trNfJGNK6kjyzJFYX93hwVXD21JvPZ4H ARkB2CKx9q4gTM6uGW09XrDFwKWKS+2wVlcWvAaUqTKnp/61YlXAWpIOea2TKQbRrATk q9Nsin0Vyq3VxW7sWFrwaG4qcwWHXCN2Z90nE=
MIME-Version: 1.0
Received: by 10.229.78.228 with SMTP id m36mr3259528qck.109.1301380720848; Mon, 28 Mar 2011 23:38:40 -0700 (PDT)
Received: by 10.229.211.84 with HTTP; Mon, 28 Mar 2011 23:38:40 -0700 (PDT)
In-Reply-To: <4D9138E0.6090807@boroon.dasgupta.ch>
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> <4D9138E0.6090807@boroon.dasgupta.ch>
Date: Tue, 29 Mar 2011 07:38:40 +0100
Message-ID: <AANLkTimKVsTUKMQ6ctMAXofMnBtq0Eoyv_rTG2o0+2PR@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary="00235429d3569570d2049f994fd4"
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 06:37:06 -0000
On Tue, Mar 29, 2011 at 2:41 AM, Boroondas Gupte <sllists@boroon.dasgupta.ch > wrote:Let me get this straight. If we > > - 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)? > Boroondas, there has never been any requirement that a party provide a complete set of services. Any party can provide as many or as few types as services as they want, so that has never been an issue. The interoperability that we're talking about here is the one that every ordinary user of multiple worlds understands perfectly well when they discover to their dismay that each world is an isolated walled garden, and wish it were otherwise. The introduction of "service level interoperability" into the discussion is just an attempt to avoid that most important requirement. We either have interoperability between worlds, in which an inhabitant can travel from one world to another and take their avatar and/or possessions with them, or else we don't have that. It's black and white, and no amount of fudging about "service level interoperability" is going to overcome the lack of VW interoperability as a user would understand it. This is *NOT* a matter of terminology, as some are trying to portray. On the one hand we gain interoperability between worlds, and on the other hand we don't. Morgaine. ======================= On Tue, Mar 29, 2011 at 2:41 AM, Boroondas Gupte <sllists@boroon.dasgupta.ch > wrote: > On 03/29/2011 02:00 AM, Morgaine wrote: > > On Tue, Mar 29, 2011 at 12:15 AM, Boroondas Gupte < > 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 >
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- [vwrap] Status and future of the VWRAP working gr… Katherine Mancuso
- [vwrap] Status and future of the VWRAP working gr… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Cristina Videira Lopes
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Fleep Tuque
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Mark Bannon
- Re: [vwrap] Status and future of the VWRAP workin… peter host
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Peter Saint-Andre
- Re: [vwrap] Status and future of the VWRAP workin… Peter Saint-Andre
- Re: [vwrap] Status and future of the VWRAP workin… Patnad Babii
- Re: [vwrap] Status and future of the VWRAP workin… Lawson English
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Fleep Tuque
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- [vwrap] Relevant panel at the IEFT: the role of s… Cristina Videira Lopes
- Re: [vwrap] Status and future of the VWRAP workin… Peter Saint-Andre
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Nexii Malthus
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Patnad Babii
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… mysticaldemina
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Carlo Wood
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Fleep Tuque
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Vaughn Deluca
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Boroondas Gupte
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick
- Re: [vwrap] Status and future of the VWRAP workin… Boroondas Gupte
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Dickson, Mike (ISS Software)
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Izzy Alanis
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Barry Leiba
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Morgaine
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Dzonatas Sol
- Re: [vwrap] Status and future of the VWRAP workin… Meadhbh Hamrick