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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 16 October 2013 04:08 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 79B5911E8242 for <apps-discuss@ietfa.amsl.com>; Tue, 15 Oct 2013 21:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.634
X-Spam-Level:
X-Spam-Status: No, score=-103.634 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 EuGXY7c716tR for <apps-discuss@ietfa.amsl.com>; Tue, 15 Oct 2013 21:08:16 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 4244311E8244 for <apps-discuss@ietf.org>; Tue, 15 Oct 2013 21:08:06 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r9G47xte007900; Wed, 16 Oct 2013 13:07:59 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 260b_8359_8b307c4e_3618_11e3_a2f0_001e6722eec2; Wed, 16 Oct 2013 13:07:58 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id C8262BF521; Wed, 16 Oct 2013 13:07:58 +0900 (JST)
Message-ID: <525E1109.1000308@it.aoyama.ac.jp>
Date: Wed, 16 Oct 2013 13:07:37 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
References: <20131010144721.30339.98848.idtracker@ietfa.amsl.com> <7e12b97cac364127b5ab56574eecf627@BY2PR03MB269.namprd03.prod.outlook.com> <c4gd591k17rvsrcn0prrafkudknqsbaahl@hive.bjoern.hoehrmann.de> <23c10ed0337840bd91fb413e9160a4d0@BY2PR03MB269.namprd03.prod.outlook.com> <7mid59tid3u4apv460egn4an94h1mre6a6@hive.bjoern.hoehrmann.de> <1fdc5b0c5ef043d4884aabd31a3d8c81@BY2PR03MB269.namprd03.prod.outlook.com> <5256D82B.2060602@att.com> <525DEF96.6050907@it.aoyama.ac.jp>
In-Reply-To: <525DEF96.6050907@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
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 04:08:22 -0000

On 2013/10/16 10:44, "Martin J. Dürst" wrote:

> It should be pointed out that the IRI WG imploded not because of *I*RI
> issues (i.e. not because of internationalization issues) but because of
> strong differences between browser implementers (or those who claimed to
> represent them on the few occasions they showed up in the WG) and others
> more e.g. with an IETF apps background.
>
> The main differences were:
> - Whether to concentrate on how things ought to behave, with occasional
> detours into aberrations of implementations, or how some actual
> implementations behaved, warts and all
> - Spec style: IETF style (ABNFs plus additional constraints) vs.
> pseudo-code style
> - Whether to create a spec for protocol elements or a spec including
> browser APIs

one more:
- Whether to use 'instant' publishing (each change to the spec, however 
minor, results in a new publication) or 'occasional' publishing (such as 
usual with Internet Drafts and RFCs).

> - What to call the things (URIs/IRIs vs. URLs)
> - Whether there was a need to distinguish 'resource' and 'representation'
> - Whether to have every change go through a WG approval process or
> whether to have a strong editor who would listen to input when appropriate