Re: [apps-discuss] FW: New Version Notification for draft-thaler-uri-scheme-reg-ps-00.txt

Graham Klyne <GK@ninebynine.org> Wed, 16 October 2013 09:11 UTC

Return-Path: <GK@ninebynine.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75CB11E8267 for <apps-discuss@ietfa.amsl.com>; Wed, 16 Oct 2013 02:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.941
X-Spam-Level:
X-Spam-Status: No, score=-5.941 tagged_above=-999 required=5 tests=[AWL=0.659, 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 Oc+9WcaswhXy for <apps-discuss@ietfa.amsl.com>; Wed, 16 Oct 2013 02:10:56 -0700 (PDT)
Received: from relay11.mail.ox.ac.uk (relay11.mail.ox.ac.uk [129.67.1.162]) by ietfa.amsl.com (Postfix) with ESMTP id 557F621F9985 for <apps-discuss@ietf.org>; Wed, 16 Oct 2013 02:10:52 -0700 (PDT)
Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay11.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <GK@ninebynine.org>) id 1VWN7y-0005yf-c4; Wed, 16 Oct 2013 10:10:50 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=conina.local) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1VWN7y-0007G5-4E; Wed, 16 Oct 2013 10:10:50 +0100
Message-ID: <525E4596.3020304@ninebynine.org>
Date: Wed, 16 Oct 2013 08:51:50 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <20131010144721.30339.98848.idtracker@ietfa.amsl.com> <7e12b97cac364127b5ab56574eecf627@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <7e12b97cac364127b5ab56574eecf627@BY2PR03MB269.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] FW: New Version Notification for draft-thaler-uri-scheme-reg-ps-00.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 09:11:02 -0000

Hi,

Sorry I'm a bit late to the party here.

(Disclosure: I'm the "expert" reviewer.)

I agree with your premise that the URI scheme registration process doesn't scale 
*if* every application is registered as a separate URI scheme.

I think this suggests a deeper conflict than just the registration process.  Web 
architecture is conceived using a global namespace of URIs, and (for reasons 
covered in RFC4395) adding new schemes in that context can be expensive.

The scenario you raise is one of *local* use of URIs to invoke applications on a 
platform.  It might be argued that this is an abuse of URI schemes, but there is 
clearly some local utility in doing this.  If, in the spirit of "rough consensus 
and running code", we allow such use, how is this to be balanced with the 
concerns of the global web, for which URIs have been defined in the first place?

The web is about content as much, if not more, than about protocols. And URIs 
are part of that content, not just elements in the protocols that drive Web 
interactions.

As reviewer, one question I ask myself when I review a URI scheme registration 
request is "what does this URI identify?".  That's hard to answer coherently 
when it is being used as a protocol trick to fire up an application. 
(Personally, I'd prefer to see application invocation handled more in the style 
of Web Intents (http://www.w3.org/TR/web-intents/) than tying them to URI schemes.)

So my question is: should we promote this proliferation of URI schemes to fire 
up applications?  If so, how are we to reconcile this use with the needs of the 
Web as a global information system?

#g
--


On 10/10/2013 15:51, Dave Thaler wrote:
> This is relevant to appsawg.  Comments welcome.
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Thursday, October 10, 2013 7:47 AM
> To: Dave Thaler
> Subject: New Version Notification for draft-thaler-uri-scheme-reg-ps-00.txt
>
>
> A new version of I-D, draft-thaler-uri-scheme-reg-ps-00.txt
> has been successfully submitted by Dave Thaler and posted to the IETF repository.
>
> Filename:	 draft-thaler-uri-scheme-reg-ps
> Revision:	 00
> Title:		 Guidelines and Registration Procedures for New URI Schemes: Problem Statement
> Creation date:	 2013-10-10
> Group:		 Individual Submission
> Number of pages: 6
> URL:             http://www.ietf.org/internet-drafts/draft-thaler-uri-scheme-reg-ps-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-thaler-uri-scheme-reg-ps
> Htmlized:        http://tools.ietf.org/html/draft-thaler-uri-scheme-reg-ps-00
>
>
> Abstract:
>     This document describes some problems with the existing guidelines
>     and procedures, as documented in RFC 4395, for new URI schemes.
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>