Re: [ogpx] resolving the name issue
Infinity Linden <infinity@lindenlab.com> Thu, 27 August 2009 16:38 UTC
Return-Path: <infinity@lindenlab.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 3A3E33A6C49 for <ogpx@core3.amsl.com>;
Thu, 27 Aug 2009 09:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level:
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[AWL=0.156,
BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 KG3RwEDu37PS for
<ogpx@core3.amsl.com>; Thu, 27 Aug 2009 09:38:50 -0700 (PDT)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com
[209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id 0A33C28C280 for
<ogpx@ietf.org>; Thu, 27 Aug 2009 09:37:55 -0700 (PDT)
Received: by ewy3 with SMTP id 3so1351976ewy.42 for <ogpx@ietf.org>;
Thu, 27 Aug 2009 09:37:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.11.138 with SMTP id 10mr1908246wex.51.1251391077286;
Thu, 27 Aug 2009 09:37:57 -0700 (PDT)
In-Reply-To: <f72742de0908270926o6991317cw8d140a7f371e7245@mail.gmail.com>
References: <3a880e2c0908211129l7d9defa5od81261e3e5805714@mail.gmail.com>
<479011.65903.qm@web111210.mail.gq1.yahoo.com>
<f72742de0908270926o6991317cw8d140a7f371e7245@mail.gmail.com>
Date: Thu, 27 Aug 2009 09:37:57 -0700
Message-ID: <3a880e2c0908270937j73fe7567t8779d193135d0b5f@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: Joshua Bell <josh@lindenlab.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ogpx@ietf.org
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: Thu, 27 Aug 2009 16:38:51 -0000
hmm.. i fear that if we don't define a protocol name, people will simply call it "the ABOVE protocol," so we'll get a de facto name. and, there are several places in the existing drafts that use the term OGP, replacing that string with "this protocol" or "the protocol defined by ABOVE" would get kind of old. but yeah, i think what i'm saying is while we can separate the protocol name from the group name and we might be able to get away with not mentioning the protocol name in the charter, we'll need a protocol name pretty quick so we can use it in the IDs. -cheers -meadhbh On Thu, Aug 27, 2009 at 9:26 AM, Joshua Bell<josh@lindenlab.com> wrote: > It seems like we're close on draft charter text; the recent discussion has > generated some good additions and clarifications to the text. We still need > a name, though. > > Given a lack of consensus on any of the proposals for a protocol name, I > suggest we reduce the problem to just a group name, and defer any protocol > naming for now. > > * The working group name is for "casual" use; i.e. it will never be > published in an RFC > * The working group should have a limited lifetime, and dissolve; so > something "eternal" or "ideal" is actually a bad idea > * It should be clear how to pronounce and spell, so that it can be > communicated in voice > * It should be recognizable when seen on an IETF agenda > > I agree with Morgaine's points earlier on this thread about names, but feel > they primarily apply to protocol names, except for the excellent suggestion > that this be something relatively unique in Google searches. That is > somewhat in (healthy) conflict with the above points, though. > > Going back to Infinity's suggestion of listing top choices, here are mine > from the floated proposals. I don't really have a #3. Again, I'm focusing on > proposed working group names only, so in context these would be > > 1. Agent Based Open Virtual Environments Working Group - ABOVE ("above") > 2. Virtual World Region/Agent Protocol Working Group - VWRAP ("v-wrap") > > If you believe that the latest rev of the draft charter text is acceptable > as a basis for forming a working group (and remember, a group can > re-charter!), please reply with your top picks. > > > _______________________________________________ > ogpx mailing list > ogpx@ietf.org > https://www.ietf.org/mailman/listinfo/ogpx > >
- [ogpx] resolving the name issue Infinity Linden
- Re: [ogpx] resolving the name issue Carlo Wood
- Re: [ogpx] resolving the name issue Morgaine
- Re: [ogpx] resolving the name issue Bill Windwalker
- Re: [ogpx] resolving the name issue Joshua Bell
- Re: [ogpx] resolving the name issue Infinity Linden
- Re: [ogpx] resolving the name issue Morgaine
- Re: [ogpx] resolving the name issue Dave CROCKER
- Re: [ogpx] resolving the name issue Infinity Linden
- Re: [ogpx] resolving the name issue Infinity Linden
- Re: [ogpx] resolving the name issue Joshua Bell
- Re: [ogpx] resolving the name issue Dave CROCKER
- Re: [ogpx] resolving the name issue Morgaine
- Re: [ogpx] resolving the name issue Dickson, Mike (ISS Software)
- Re: [ogpx] resolving the name issue Infinity Linden
- Re: [ogpx] resolving the name issue Carlo Wood
- Re: [ogpx] resolving the name issue Carlo Wood
- Re: [ogpx] resolving the name issue Carlo Wood
- Re: [ogpx] resolving the name issue Barry Leiba
- Re: [ogpx] resolving the name issue Carlo Wood
- Re: [ogpx] resolving the name issue Kari Lippert
- Re: [ogpx] resolving the name issue Meadhbh Siobhan
- Re: [ogpx] resolving the name issue Meadhbh Siobhan
- Re: [ogpx] resolving the name issue Meadhbh Siobhan
- Re: [ogpx] resolving the name issue Carlo Wood
- Re: [ogpx] resolving the name issue Barry Leiba