Re: [ogpx] resolving the name issue

Morgaine <morgaine.dinova@googlemail.com> Sat, 22 August 2009 03:22 UTC

Return-Path: <morgaine.dinova@googlemail.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 21FB53A682B for <ogpx@core3.amsl.com>; Fri, 21 Aug 2009 20:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 kjbNQeWIhUu1 for <ogpx@core3.amsl.com>; Fri, 21 Aug 2009 20:22:58 -0700 (PDT)
Received: from mail-ew0-f206.google.com (mail-ew0-f206.google.com [209.85.219.206]) by core3.amsl.com (Postfix) with ESMTP id 92A493A68EF for <ogpx@ietf.org>; Fri, 21 Aug 2009 20:22:57 -0700 (PDT)
Received: by ewy2 with SMTP id 2so1263294ewy.43 for <ogpx@ietf.org>; Fri, 21 Aug 2009 20:22:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=o07u5RXojPkxrr/5RKnk3HsTYTjDOgrVJrBxAmeSHZc=; b=KU8Ad6RZOci/lRC9dBuAr0KLYUmpkx1G0emAmSRwUOlJI4KTDFGbJ51QdTUnjdrl+x +S4A4Ow1PvtbfylC3U78rPpT79OIYPIMxBtHzbxsGwIn14XgYv5SrLeFqIUaTu69NbJw GbF701dnA/eojEG1xLHeD6h3Iel1zImP1fXbs=
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=M81zeIwB3aIZ9/kCim2fSRaVOlr303Ul9xeA2J/Qbyg5VgluZxLkC/L+du2S5EyiYb GDcR2MZOKGjfZszImbuxf59nkojPWRQ85AwmaKZ9vDu3dtce1XIA9JSSRNT/YfYwNc/H 6KWncYF77EF7tiTHBPMxPg3A9wfnCm0yoCppQ=
MIME-Version: 1.0
Received: by 10.210.10.4 with SMTP id 4mr2313434ebj.36.1250911376918; Fri, 21 Aug 2009 20:22:56 -0700 (PDT)
In-Reply-To: <3a880e2c0908211129l7d9defa5od81261e3e5805714@mail.gmail.com>
References: <3a880e2c0908211129l7d9defa5od81261e3e5805714@mail.gmail.com>
Date: Sat, 22 Aug 2009 04:22:56 +0100
Message-ID: <e0b04bba0908212022w6e24b4awb0e9cbb6d66ad4d9@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0015174be0544449020471b280ba
Subject: Re: [ogpx] resolving the name issue
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: Sat, 22 Aug 2009 03:22:59 -0000

As a general rule, I would recommend *against* using common words such as
ABOVE or OVER for the name of the group or protocol, for several reasons:


   - Not everyone will capitalize ABOVE or OVER when using them in this
   technical context, so ambiguities will arise in common usage outside of this
   group.
   - Discussions about the protocol *held in voice* will incur vocal
   ambiguity with the corresponding English words, and of course capitalization
   is not possible in this medium.
   - Sometimes the words "above" or "over" in their normal English meaning
   will get CAPITALIZED FOR EMPHASIS, adding yet more confusion to the mix.
   - New names like SMTP or HTTP extend natural language easily through
   popular use, but overloaded terms create conflict rather than smooth
   language extension.
   - ABOVE or OVER may be cute constructions, but cuteness doesn't help
   anyone.
   - But the biggest reason for avoiding common words is given by Google,
   since the resulting poor quality of search results will benefit neither the
   workgroup nor the eventual readers of our specifications.


I have no particular preferences for the name, apart from the above advice.
However, here are some partial phrases that might generate some more ideas:


   - Virtual Spaces Organization and Access -- avoids "Virtual Worlds"
   - Region Interoperation Services -- it's what the protocol targets
   strongly
   - Virtual Services Interoperation -- alludes to Zha's reformulation
   - Virtual World Services Protocol -- works well despite "ATM syndrome"
   - Virtual World State Representation System -- alludes to REST


As others have recommended as well, topological terms like "grid" don't
really help and may create confusion, so should be discouraged.  In
contrast, it would be worth encouraging use of a name that references some
unique element of this particular proposal, such as Regions, or maybe State
Transfer.


Morgaine.









On Fri, Aug 21, 2009 at 7:29 PM, Infinity Linden <infinity@lindenlab.com>wrote;wrote:

> it seems to me we're in the enviable position of having several good
> name suggestions: ARAP, VWIP, OVER, ABOVE and VWGP. We also have the
> historical name OGP.
>
> would it make sense to go around asking people to rank their name
> preferences and do Single Transferrable Vote (STV) to find the first,
> second and third most popular choices?
>
> -cheers
> -meadhbh
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>