Re: [urn] Formal request for URN for ITU

worley@ariadne.com (Dale R. Worley) Wed, 04 July 2018 18:27 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB7D9130E07 for <urn@ietfa.amsl.com>; Wed, 4 Jul 2018 11:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Level:
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 B951m8sHqbGm for <urn@ietfa.amsl.com>; Wed, 4 Jul 2018 11:27:30 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 433A3129619 for <urn@ietf.org>; Wed, 4 Jul 2018 11:27:30 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id amTYfuOYYwfygamUzfBuhA; Wed, 04 Jul 2018 18:27:29 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id amUxfgnzTAkphamUxfqy4M; Wed, 04 Jul 2018 18:27:28 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w64IRQbd024068; Wed, 4 Jul 2018 14:27:26 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w64IRQDk024065; Wed, 4 Jul 2018 14:27:26 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>
Cc: scott.mansfield@ericsson.com, urn@ietf.org
In-Reply-To: <HE1PR07MB30973FDE0B164C8DD774BE58FA410@HE1PR07MB3097.eurprd07.prod.outlook.com> (juha.hakala@helsinki.fi)
Sender: worley@ariadne.com
Date: Wed, 04 Jul 2018 14:27:25 -0400
Message-ID: <871sci6elu.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfFwTMKLPX96/e2utNZTZytLvme80g0XzTpe88BhhNNTI8eqDPczUcDFqgCxKjjwrO7rKvOdZB9hGCLVXSeD5vgrrHdfyid6V6FIXl6c6QGd0EP3TmIUI oStlB6lAntnRrkMYIAjXYF/NgQ5woVC1c01JSOqJnfTc/KvE8mVlKEMPYO9sxReWHHMxt/hFxPXP8d9Gzb01qR5/02bwAK5TThJGEGXuRoOVWSdwnX3vW5E5 NhntNeLlo8wF1utEh0k8tyRXgiTMQAv6Dt7Y7XG6ciSiSa7vQ/zcKPLEFwtb2S2HWFIn4ZxDGAr887xJo6nA4g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/bY2sTiyKApbXzgdgUxo0Vc85DR4>
Subject: Re: [urn] Formal request for URN for ITU
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.26
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 04 Jul 2018 18:27:32 -0000

"Hakala, Juha E" <juha.hakala@helsinki.fi> writes:
> ITU is closely involved with the Handle system:
>
> http://www.itu.int/osg/csd/emerging_trends/handle_system/index.html
>
> Does "identifiers defined by ITU" cover also Handles and if so, what
> is their relation to URNs? In other words, are there ITU sectors which
> use Handles as SectorResourceSpecificStrings? If there are, it might
> be better to assign URN namespace to Handles as well. As far as I
> know, ITU is the one organization which can make such a request,
> having adopted CNRI's Handle responsibilities.

Wikipedia claims:

    Handles can be used natively. or expressed as Uniform Resource
    Identifiers (URIs) through a namespace within the info URI scheme;
    for example, 20.1000/100 may be written as the URI,
    info:hdl/20.1000/100. Some Handle System namespaces, such as Digital
    Object Identifiers, are "info:" URI namespaces in their own right;
    for example, info:doi/10.1000/182 is another way of writing the
    handle for the current revision of the DOI Handbook as a URI.

> [...] each DOI can be expressed as actionable
> URN just by adding urn:doi: in front of the DOI prefix (note that such
> NID has not been registered the DOI system or some other identifier
> yet). I assume it would not be too difficult to make Handles
> actionable URNs as well, in e.g. urn:handle: namespace.

That's interesting, in that DOIs have a defined format like
"doi:10.1000/182", which is official per the International DOI
Foundation but "doi" is NOT a registered URI scheme.

So these are equivalent, to the degree that they are defined:

    info:hdl/10.1000/182
    info:doi/10.1000/182
    doi:10.1000/182
    urn:doi:10.1000/182

Dale