Re: [mmox] OGP scalability concerns

"Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com> Thu, 02 April 2009 03:00 UTC

Return-Path: <infinity@lindenlab.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E44213A6957 for <mmox@core3.amsl.com>; Wed, 1 Apr 2009 20:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.527
X-Spam-Level:
X-Spam-Status: No, score=-3.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, 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 kQM-j63xjk+F for <mmox@core3.amsl.com>; Wed, 1 Apr 2009 20:00:10 -0700 (PDT)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id 3044F3A6821 for <mmox@ietf.org>; Wed, 1 Apr 2009 20:00:10 -0700 (PDT)
Received: from regression.lindenlab.com (regression.lindenlab.com [10.1.16.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tammy.lindenlab.com (Postfix) with ESMTP id 59AB03DBC446; Wed, 1 Apr 2009 20:01:11 -0700 (PDT)
Message-Id: <52A129B8-3FC6-486A-99A5-C00BED8BDE08@lindenlab.com>
From: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
To: Jon Watte <jwatte@gmail.com>
In-Reply-To: <49D4295C.2020502@gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 01 Apr 2009 20:01:11 -0700
References: <62BFE5680C037E4DA0B0A08946C0933D7B692E1B@rrsmsx506.amr.corp.intel.com> <CD02023C-3E7B-4E76-8429-11035C827E53@lindenlab.com> <f0b9e3410904011701i2ccb03d4r1b48d33cfe3988ea@mail.gmail.com> <49D40A06.7030708@gmail.com> <8D793BD8-6AA2-49C7-96EF-435A5B449AA6@lindenlab.com> <49D4295C.2020502@gmail.com>
X-Mailer: Apple Mail (2.930.3)
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] OGP scalability concerns
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2009 03:00:11 -0000

so maybe we might say "virtual world avatar interop" or "virtual world  
event stream interop"?

but not say "virtual world interop" 'cause it's too vague?

On Apr 1, 2009, at 7:56 PM, Jon Watte wrote:

> Meadhbh Hamrick (Infinity) wrote:
>> I believe the term you're looking for, given your usage is  
>> "universality." And no, OGP does not provide universality. OGP
>
>>>
>>> It may sound pedantic, but I do think it's important to put as  
>>> unambiguous labels on what we discuss as possible, so that we  
>>> don't end up making different assumptions without realizing it,  
>>> and ending up in confusion and discord.
>
> I'm sorry: I think you misunderstood what I was saying and took it  
> the wrong way. The word "interop" is clearly correct, and I am not  
> arguing against that. My argument is against labeling anything and  
> everything as "virtual world interop." As we've seen, it's a term  
> that is so broad as to be almost meaningless. I'm merely arguing for  
> specificity.
>
> The proposal is to be more detailed about what kind of interop we're  
> talking about in any particular case. For example, there might be  
> VoIP interop, or avatar interop, or authentication interop, or  
> simulation interop, or service brokerage interop, or online status  
> interop, or text chat interop. Those are all forms of interop  
> necessary to accomplish "full virtual world interop." The confusion  
> arises when someone talks about "virtual worlds interop" but is  
> actually only discussing one piece. In my opinion, it would be more  
> accurate, and help everybody, to clearly specify the piece you're  
> talking about.
>
> Sincerely,
>
> jw
>