Re: [Uri-review] draft-farrell-decade-ni

Graham Klyne <GK@ninebynine.org> Tue, 08 May 2012 12:17 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 2FF1321F8497 for <uri-review@ietfa.amsl.com>; Tue, 8 May 2012 05:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.082
X-Spam-Level:
X-Spam-Status: No, score=-7.082 tagged_above=-999 required=5 tests=[AWL=-0.483, 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 bdEVqzea3Ipx for <uri-review@ietfa.amsl.com>; Tue, 8 May 2012 05:17:43 -0700 (PDT)
Received: from relay0.mail.ox.ac.uk (relay0.mail.ox.ac.uk [129.67.1.161]) by ietfa.amsl.com (Postfix) with ESMTP id 86A2E21F8473 for <uri-review@ietf.org>; Tue, 8 May 2012 05:17:43 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay0.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1SRjMM-00041F-0u; Tue, 08 May 2012 13:17:42 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=Eskarina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1SRjML-0005LH-6g; Tue, 08 May 2012 13:17:42 +0100
Message-ID: <4FA90DAC.4020507@ninebynine.org>
Date: Tue, 08 May 2012 13:12:28 +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: Eric Johnson <eric@tibco.com>
References: <4F9EB644.60309@cs.tcd.ie> <4FA39FE9.5010306@tibco.com> <4FA62A44.4060101@ninebynine.org> <4FA79123.1050900@tibco.com> <4FA832AE.9080901@ninebynine.org> <4FA8E1FE.5020309@tibco.com>
In-Reply-To: <4FA8E1FE.5020309@tibco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Cc: uri-review@ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Uri-review] draft-farrell-decade-ni
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: Tue, 08 May 2012 12:17:44 -0000

On 08/05/2012 10:06, Eric Johnson wrote:
> Taking your point, perhaps at a minimum the proposal should document which
> hierarchical operations will yield a result with "a defined meaning according to
> the rules of the ni: scheme", and which ones won't. Especially so since the
> proposed scheme uses the "//" indicator which implies hierarchical operations,
> and we've already agreed that some such operations are meaningless.

Not quite: my original response suggested an application of this structure which 
might have useful meaning.  It's just your example that is not given a defined 
meaning by the ni: spec.

I think it's pretty clear which hierarchical operations have defined meaning: 
apply the resolution rule and see if the result has defined meaning per the 
spec.  (I suppose one might add a warning:  "Injudicious resolution of relative 
URI references with respect to an ni: base URI may yield an ni: URI whose 
interpretation is not defined by this specification.")

...

(I feel that I'm spending more time on this than the issue deserves.  I don't 
feel especially strongly that the scheme should be hierarchical or not, and 
hierarchical seems OK to me.  I mainly feel it's not worth changing a spec that 
others have thought about more deeply than I without a compelling reason.)

#g
--