[Gen-art] Re: Gen-ART review of draft-hansen-2717bis-2718bis-uri-guidelines-05.txt
Spencer Dawkins <spencer@mcsr-labs.org> Tue, 23 August 2005 12:36 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7Y12-0002jA-0E; Tue, 23 Aug 2005 08:36:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7Y10-0002j5-L5 for gen-art@megatron.ietf.org; Tue, 23 Aug 2005 08:36:30 -0400
Received: from rwcrmhc12.comcast.net (rwcrmhc13.comcast.net [216.148.227.118]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01191 for <gen-art@lists.ietf.org>; Tue, 23 Aug 2005 08:36:29 -0400 (EDT)
Received: from [127.0.0.1] (unknown[65.104.224.98]) by comcast.net (rwcrmhc13) with ESMTP id <2005082312325501500m51t2e>; Tue, 23 Aug 2005 12:33:11 +0000
Message-ID: <430B1763.4080704@mcsr-labs.org>
Date: Tue, 23 Aug 2005 07:32:35 -0500
From: Spencer Dawkins <spencer@mcsr-labs.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Larry Masinter <LMM@acm.org>
References: <0ILN00472J2XDK@mailsj-v1.corp.adobe.com>
In-Reply-To: <0ILN00472J2XDK@mailsj-v1.corp.adobe.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: 'Ted Hardie' <hardie@qualcomm.com>, tony+urireg@maillennium.att.com, 'Gen-Art Mailing List' <gen-art@ietf.org>, 'Scott Hollenbeck' <sah@428cobrajet.net>
Subject: [Gen-art] Re: Gen-ART review of draft-hansen-2717bis-2718bis-uri-guidelines-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: spencer@mcsr-labs.org
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org
Larry Masinter wrote: >>Intended status: Proposed Standard > > > Interesting. The .XML says "Best Current Practice". The generated > .txt and .html don't, though. However, We're definitely > intending BCP, this isn't a standards track document. > > > >>Summary - this document is almost ready for publication. It has two >>nearly-editorial changes I'd like to see considered: >> >>- the reader has to dig to notice that there are two kinds of URIs being >>registered with different requirements in the same namespace. It would >>be nice to say this pretty clearly ("These guidelines cover both >>provisional and permanent URI scheme registrations, which are part of >>the same URI namespace"), somewhere in Section 1. > > > OK. > > >>- 2.8 tries to say, "avoid trademark names", but doesn't say much about >>why this is a good idea, or (more relevant) how big a problem you have >>when someone registers your scheme name as trademark. The current text >>is probably good advice, I'm just asking if there is more guidance that >>could be provided, too. > > > I think this is pretty fuzzy advice, alas. And there might be some > dragons (or at least aligators) waiting in those waters. I don't > expect the "expert" doing "expert review" to review whether there is > a legal trademark and whether the proposed registration is or isn't > consistent with that trademark, in the various jurisdictions of the > world. > > I guess we should ask the person submitting the registration to > assert that, as far as they know, the use of the URI scheme name > doesn't have trademark problems. I might want some advice on how > to word that, though. This would be very reasonable (once you figure out what the words should be!). It may be that all you're trying to do is call the submitter's attention to section 7.4 of http://www.ietf.org/rfc/rfc3978.txt, and say, "please do your best to keep us from getting sued if we come up with a scheme name that turns out to be a trademark" (a lawyer would, of course, say it differently :-)) This is actually less restrictive than the current text (current text discourages uses of trademarks, 3978 discourages use of trademarks unless the IETF has a right to use them in specifications), I think. Spencer > Larry _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen-ART review of draft-hansen-2717bis-… Spencer Dawkins
- [Gen-art] RE: Gen-ART review of draft-hansen-2717… Larry Masinter
- [Gen-art] Re: Gen-ART review of draft-hansen-2717… Spencer Dawkins
- [Gen-art] RE: Gen-ART review of draft-hansen-2717… Scott Hollenbeck
- [Gen-art] Re: Gen-ART review of draft-hansen-2717… Tony Hansen
- [Gen-art] Re: Gen-ART review of draft-hansen-2717… Spencer Dawkins
- [Gen-art] RE: Gen-ART review of draft-hansen-2717… Larry Masinter