Re: [urn] [apps-discuss] URNs are not URIs (another look at RFC 3986)

SM <sm@resistor.net> Tue, 06 May 2014 18:25 UTC

Return-Path: <sm@resistor.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEC1B1A0234 for <urn@ietfa.amsl.com>; Tue, 6 May 2014 11:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAGDJJEt1CYt for <urn@ietfa.amsl.com>; Tue, 6 May 2014 11:25:43 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 247B91A01C4 for <urn@ietf.org>; Tue, 6 May 2014 11:25:42 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s46IPQ3J006524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 May 2014 11:25:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1399400736; bh=2VcsEIYZhgW4sytlPqVZF2vKzQ1KhTEc3Ve/yzWf/9k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FO8cNGXQ5XVztJmS1WsyjZce3DOI4XrQFfGT2bi0zQP9dloGNUHKPyNKTTgkR0Xj9 2pRpyhHOaSomiqS+2r+rK9QZOw5fJef0lDgRfR0ULLurfRyMIw0Y58hVXQfYx/zLDH GpL57LnwlkS5zO6C9bLP8giPLcxXx0EgjHtHccN4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1399400736; i=@resistor.net; bh=2VcsEIYZhgW4sytlPqVZF2vKzQ1KhTEc3Ve/yzWf/9k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Bxo9PKrLJNZHlUoT6c0u5gw6Dp4qnwDu2W0EFEASRcVttGBKQwRBe1JQVVvEeRYSu vMg7QQXAYKYzM2gaI4w16IKT3Xt0sG6NG6Ci8JHQoeSE72N2WRSGCOUombR/G8kEY9 oadNpq/f9L5UPMZZhcsSgJ8zc8pHlxJDHRUeWK9I=
Message-Id: <6.2.5.6.2.20140506104843.0bfed448@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 06 May 2014 11:23:41 -0700
To: John C Klensin <john-ietf@jck.com>, jehakala@mappi.helsinki.fi
From: SM <sm@resistor.net>
In-Reply-To: <CCE2B61EFCBECEAE1EB3CA3E@JCK-EEE10>
References: <C93A34DBE97565AD96CEC321@JcK-HP8200.jck.com> <534BED18.9090009@gmx.de> <3D39F1AA700A179F3C051DE2@JcK-HP8200.jck.com> <534D3410.50607@ninebynine.org> <54ecc96adba240159cf624c54c507136@BL2PR02MB307.namprd02.prod.outlook.com> <952E89C207E59D25CD5953D6@JCK-EEE10> <20140502180642.Horde.k922N8-cIl2au4mAP9neJA2@webmail.helsinki.fi> <6.2.5.6.2.20140505145214.0e626308@resistor.net> <CCE2B61EFCBECEAE1EB3CA3E@JCK-EEE10>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/urn/rpwnS78bhPK5ErtJfLvA0xp2j34
Cc: julian.reschke@gmx.de, urn@ietf.org, Graham Klyne <GK@ninebynine.org>
Subject: Re: [urn] [apps-discuss] URNs are not URIs (another look at RFC 3986)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 18:25:43 -0000

Hi John,
At 04:09 06-05-2014, John C Klensin wrote:
>I think it is obvious that different groups have different
>perceived requirements.  For better or worse and despite a sense
>that more education and listening would be helpful, I think the
>"my perspective is right and you are wrong" tone of many of the
>recent discussions are not leading us toward progress.

I agree that the recent discussions are not leading towards progress.

>Perhaps a more useful way to look at this is to try to
>understand the needs of real communities [1] and then figure out
>what we need to have in a URN standard to meet those needs.  My
>working hypothesis is that, after trying to do with within the
>constraints of 3986 and the compromises people are willing to
>make is that it is not possible.  I hope we can do better than
>    urn:nid:<stuff>
>but maybe, if all we can do is to push NIS and tail syntax to
>NID definitions and registrations, that is better than permanent
>(sic) paralysis.

Factual information would help in understanding the needs of the 
various communities.  I am not sure whether that would lead towards 
progress.  The probability of "we can do better" is very low.

Regards,
-sm