Re: [ogpx] resolving the name issue
Morgaine <morgaine.dinova@googlemail.com> Fri, 28 August 2009 11:16 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 5DCA33A6E42 for <ogpx@core3.amsl.com>;
Fri, 28 Aug 2009 04:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.711
X-Spam-Level:
X-Spam-Status: No, score=-1.711 tagged_above=-999 required=5 tests=[AWL=0.265,
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 u8SRBXQkcJHX for
<ogpx@core3.amsl.com>; Fri, 28 Aug 2009 04:16:07 -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 815833A6F9E for
<ogpx@ietf.org>; Fri, 28 Aug 2009 04:16:06 -0700 (PDT)
Received: by ewy3 with SMTP id 3so321093ewy.42 for <ogpx@ietf.org>;
Fri, 28 Aug 2009 04:16:09 -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=+EXgoRfDqJcJNqtwviRDnJ5h4H94vDqIZ15BKl9w6bQ=;
b=KnRjueQOyB6xDVXIVvPcsU1Iv/fAPskfwk+MYSj0WHB20yrWeoNHcqJoO9Q6Z9IL5/
6VZcab7238XTRO0YgrL2zzTZIlYZ/VBP5yc9Pj+WlWjHMZJpuOIpullwcBTRsaOg/act
ORZe55NVtyT0hQtXDgGf+Xaz/u6fmu2nu6Vk0=
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=QuqPCrcL/rAIxRtrpvaNjo9Dy13fRytHt8iLEBPKJlm6BstHDmVVGgjCaLIhIy1M/B
OOdIhxHeHzIfLvgSUGdfvB3U946svZOeB3Izhbujjf3F43S/fpOfKcRCyDin0OvxcUTY
3xhT+xjMMfomoPk2MwszH7QI/YSHvhh8R7Tm0=
MIME-Version: 1.0
Received: by 10.211.147.5 with SMTP id z5mr1062996ebn.87.1251458169083;
Fri, 28 Aug 2009 04:16:09 -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: Fri, 28 Aug 2009 12:16:09 +0100
Message-ID: <e0b04bba0908280416w60e9c7cdre7e3eaef3e244cb1@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=001636c5b94a9e95b5047231cf66
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: Fri, 28 Aug 2009 11:16:08 -0000
On Thu, Aug 27, 2009 at 5:26 PM, Joshua Bell <josh@lindenlab.com> wrote: > > 1. Agent Based Open Virtual Environments Working Group - ABOVE ("above") > 2. Virtual World Region/Agent Protocol Working Group - VWRAP ("v-wrap") > I support the *Region/Agent* part of #2 because it refers to the central idea in this proposal that makes it distinct from other interop protocols. In particular, it distinguishes this work from other proposals that would be in the scope of MMOX. In contrast, the *Virtual World* part of #2 just adds fuel to the problems that have been highlighted here about the redefinition of this phrase in OGP compared to its use by everyone else in this sphere. That issue isn't going away, and will become ever harder as we begin to focus on use cases for cross-world interop. Building upon *Region/Agent*, various other possible constructs for the group name come to mind. Note that the "world[s]" issue can be avoided while retaining *Virtual*: - Region/Agent Domain Interop Group -- RADIG - Virtual Region/Agent Interop Group -- VRAIG - Virtual Region/Agent eXchange group -- VRAX group - Virtual Region/Agent Interop X -- VRAIX, X = {proto, group, apps} - Virtual Region/Agent Domain group -- VRAD group - Virtual Domains Interop Protocol/Group -- VDIP/VDIG - and so on ("Virtual Domains" actually reflects the central idea well) Note that simply dropping "World" from your #2 achieves the same thing and makes it more pronounceable: - Virtual Region/Agent Protocol / Working Group - VRAP ("vrap") As you pointed out, the group name is not as crucial as the eventual protocol name, but as Infinity mentioned, the group name suggests a de facto protocol name so we can't leave the latter dangling for too long. I suspect that a protocol name that differs from the group name will just sow confusion, and doesn't add value. It may be best to go through this ordeal just once. Morgaine. ======================= On Thu, Aug 27, 2009 at 5:26 PM, 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