Re: [ogpx] resolving the name issue

Infinity Linden <infinity@lindenlab.com> Fri, 28 August 2009 15:21 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 7AE3B3A6872 for <ogpx@core3.amsl.com>; Fri, 28 Aug 2009 08:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.826
X-Spam-Level:
X-Spam-Status: No, score=-1.826 tagged_above=-999 required=5 tests=[AWL=0.151, 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 r0dWtdCYQLcz for <ogpx@core3.amsl.com>; Fri, 28 Aug 2009 08:21:41 -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 64ABE3A659C for <ogpx@ietf.org>; Fri, 28 Aug 2009 08:21:41 -0700 (PDT)
Received: by ewy3 with SMTP id 3so511733ewy.42 for <ogpx@ietf.org>; Fri, 28 Aug 2009 08:21:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.52.76 with SMTP id d54mr264945wec.119.1251472904245; Fri, 28 Aug 2009 08:21:44 -0700 (PDT)
In-Reply-To: <4A97F4EA.2030803@dcrocker.net>
References: <3a880e2c0908211129l7d9defa5od81261e3e5805714@mail.gmail.com> <479011.65903.qm@web111210.mail.gq1.yahoo.com> <f72742de0908270926o6991317cw8d140a7f371e7245@mail.gmail.com> <3a880e2c0908270937j73fe7567t8779d193135d0b5f@mail.gmail.com> <4A97F4EA.2030803@dcrocker.net>
Date: Fri, 28 Aug 2009 08:21:44 -0700
Message-ID: <3a880e2c0908280821v44782ac7u6deedc7335faae80@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Fri, 28 Aug 2009 15:21:42 -0000

but above is just so cool!

On Fri, Aug 28, 2009 at 8:16 AM, Dave CROCKER<dhc@dcrocker.net> wrote:
>
>
> Infinity Linden wrote:
>>
>> 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.
>
>
> If the working group were going to deal with a number of independent (but
> related) specifications, each of which would have their own name, then
> giving the working group yet-a-different name would make sense.  And no,
> it's not the end of the world one way or the other, but it IS less confusing
> to have the wg name and the primary specification name match.
>
> The comment about a name that is too common a word, like ABOVE, is
> well-taken.
>
> I think vwrap is reasonable.
>
> (It also permits flights of analogy and other whimsy.  Not essential, of
> course, but can add some entertainment to a community effort...)
>
> d/
> --
>
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>