Re: [mmox] OGP scalability concerns
"Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com> Thu, 02 April 2009 01:49 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 0315E3A6A61 for <mmox@core3.amsl.com>; Wed, 1 Apr 2009 18:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.526
X-Spam-Level:
X-Spam-Status: No, score=-3.526 tagged_above=-999 required=5 tests=[AWL=0.073, 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 SRgDs7d61lRx for <mmox@core3.amsl.com>; Wed, 1 Apr 2009 18:49:30 -0700 (PDT)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id 0B9B23A685D for <mmox@ietf.org>; Wed, 1 Apr 2009 18:49:30 -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 114E13DBC464; Wed, 1 Apr 2009 18:50:31 -0700 (PDT)
Message-Id: <8D793BD8-6AA2-49C7-96EF-435A5B449AA6@lindenlab.com>
From: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
To: Jon Watte <jwatte@gmail.com>
In-Reply-To: <49D40A06.7030708@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 01 Apr 2009 18:50:30 -0700
References: <62BFE5680C037E4DA0B0A08946C0933D7B692E1B@rrsmsx506.amr.corp.intel.com> <CD02023C-3E7B-4E76-8429-11035C827E53@lindenlab.com> <f0b9e3410904011701i2ccb03d4r1b48d33cfe3988ea@mail.gmail.com> <49D40A06.7030708@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 01:49:31 -0000
Okay... if we want to get pedantic, then let's get pedantic. * 47 CFR 51.3 defines interoperability as "the ability of two or more facilities, or networks, to be connected, to exchange information, and to use the information that has been exchanged." * 17 USCS § 1201 describes interoperability as "means the ability of computer programs to exchange information, and of such programs mutually to use the information which has been exchanged." * 44 USCS § 3601 describes interoperability as "the ability of different operating and software systems, applications, and services to communicate and exchange data in an accurate, effective, and consistent manner." * The IEEE has used "the ability of two or more systems or components to exchange information and to use the information that has been exchanged." as the definition of the term. I would suggest that we all might be using the term incorrectly as the definitions above imply an exchange of information; that is, information flows between two facilities, networks, computer programs, operating systems, applications, services, systems or components. Perhaps it is more appropriate to say: * "Second Life (as a service) has demonstrated interoperability with an instance of OpenSim using a version of the OGP protocol." or * "sim3078.aditi.lindenlab.com has demonstrated interoperability with ec2-XXX-XXX-XXX-XXX.compute-1.amazonaws.com using a version of the OGP protocol." or * "Second Life server version 1.22 (as a software system) has demonstrated interoperability with a version of OpenSim." But I would defend our previous usage of the term to describe OGP as an "interoperability protocol" because, in fact, there are software systems (Second Life and OpenSim) which use it to exchange information which is used by either system. I believe the term you're looking for, given your usage is "universality." And no, OGP does not provide universality. OGP does not allow WoW to talk with Star Wars Galaxies or There.Com or a Forterra simulation. It also doesn't solve world hunger or global warming. But then again, OGP was not intended to provide that kind of universality (or to solve world hunger.) And I would suggest that neither LESS nor DIS nor HLA were designed for universality either. I further believe that universality is not a feature of a protocol, but of markets, products and possibly networks. -cheers -meadhbh On Apr 1, 2009, at 5:42 PM, Jon Watte wrote: > Charles Krinke wrote: >> To me, interop implies a full handoff of an avatar from one virtual >> world to another. > > Is it "virtual worlds interop" if there aren't multiple virtual > worlds interoperating involved on an ongoing basis? > It sounds like you're describing something like "avatar interop," to > me. > > 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. > > Sincerely, > > jw >
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Lawson English
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Jason Giglio
- Re: [mmox] OGP scalability concerns Rob Lanphier
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Christian Scholz