Re: [Uri-review] New URI scheme for review

Graham Klyne <GK@ninebynine.org> Wed, 19 October 2011 15:52 UTC

Return-Path: <GK@ninebynine.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C92CD21F851F for <uri-review@ietfa.amsl.com>; Wed, 19 Oct 2011 08:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.577
X-Spam-Level:
X-Spam-Status: No, score=-6.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MCCIahKWHvNP for <uri-review@ietfa.amsl.com>; Wed, 19 Oct 2011 08:52:06 -0700 (PDT)
Received: from relay1.mail.ox.ac.uk (relay1.mail.ox.ac.uk [129.67.1.165]) by ietfa.amsl.com (Postfix) with ESMTP id 5E37A21F87D9 for <uri-review@ietf.org>; Wed, 19 Oct 2011 08:52:05 -0700 (PDT)
Received: from smtp0.mail.ox.ac.uk ([129.67.1.205]) by relay1.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1RGYR0-0003fo-5q; Wed, 19 Oct 2011 16:52:02 +0100
Received: from tinos.zoo.ox.ac.uk ([129.67.24.47]) by smtp0.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1RGYR0-0004PH-2F; Wed, 19 Oct 2011 16:52:02 +0100
Message-ID: <4E9ED275.2070506@ninebynine.org>
Date: Wed, 19 Oct 2011 14:36:53 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: uri-review@ietf.org
References: <CAHcUcOGgv8deMk3yw0FH8HrHee5Hi0pXcFCRwYDfaO_ta_nuGA@mail.gmail.com> <CAHhFybrUH3TA5_pUkNi-5j82HZHhyt_Z4xibnQ8=JZ_dCXidDQ@mail.gmail.com>
In-Reply-To: <CAHhFybrUH3TA5_pUkNi-5j82HZHhyt_Z4xibnQ8=JZ_dCXidDQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Subject: Re: [Uri-review] New URI scheme for review
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2011 15:52:09 -0000

On 11/10/2011 07:00, Frank Ellermann wrote:
> On 11 October 2011 01:30, Bob Van Zant<bob@eventbrite.com>  wrote:
>
>> It looks like most URI schemes like this one are never registered
>> with IANA. It seems like The Right Thing to do and so I present to
>> the list the URI scheme com-eventbrite-attendee.
>
> Yeah.  I'd be tempted to reject it as "vanity URI scheme in conflict
> with RFC 4395 2.1 Demonstratable, New, Long-Lived Utility", but that
> might be not "the right thing", and besides only the expert reviewer
> (= not me) could say so.

As a reviewer, that's not how I see the review process.  It's not one reviewer 
making a quality judgement, but checking that the stated requirements for 
registration have been met.

 From what I've seen, I'd say there's at least enough information here to 
justify a provisional registration.  For permanent registration, I'd be looking 
for evidence of community consensus that this is useful and well-conceived and 
has long-lived value.  I don't think "vanity" per se is a consideration or concern.

...

Speaking for myself, this does indeed look like a case that is not easily 
satisfied by existing URI schemes.  I had some thoughts along the lines of the 
"exec" scheme mentioned later in this thread, but I'm not sure either way: 
essentially, in the tradition of handling comp sci problems, it's another level 
of indirection, and I don't know if there would be enough new URI schemes like 
this to justify that new level.

Maybe there's scope for a URI scheme for encoding "web intent" style handoff? 
(http://webintents.org/)

For a proprietary application that does not claim to interoperate with others I 
think the name form chosen is very appropriate - later maybe we'll even see more 
open interoperability in this event space using a more generic name-form?

#g
--

> Disclaimer, I have not yet read the 4395bis drafts, maybe 4395bis
> will drop the "long-lived utility" blurb in favour of a new "above
> all let's have it registered" approach.
>
> With that out of the way, are you sure that you want an OPTIONAL
> query part in the syntax?  If the query part is actually REQUIRED
> for this scheme maybe remove the square brackets in the syntax:
>
>> URI scheme syntax.
>>     uri = "com-eventbrite-attendee:" method [ "?" query ]
>>     method = "resetpassword" / "tickets"
>
> If you happen to have a web page with more technical details please
> add it to the references.  If that is not (yet) the case it is no
> problem, your explanation in the registration template is clear.
>
> -Frank
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>