Re: [urn] META URN namespace registration

worley@ariadne.com Wed, 27 May 2020 02:55 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 8389E3A0D5B for <urn@ietfa.amsl.com>; Tue, 26 May 2020 19:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Level:
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 HwQRyXYOxpBG for <urn@ietfa.amsl.com>; Tue, 26 May 2020 19:55:05 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (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 2AAC93A0AEC for <urn@ietf.org>; Tue, 26 May 2020 19:55:04 -0700 (PDT)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-02v.sys.comcast.net with ESMTP id dlrKjv5SQjoMldmDfjUftv; Wed, 27 May 2020 02:55:03 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1590548103; bh=gqJ0GTRDBIXIY0g20whXR4o14n8cokF8ORA8h1ncFXI=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=BlOS5nXrTQ8Mh9rZgOYXQa3MhE2mHllKEaXvyg7tFyWUMXZ4cWpJgdGCLmJPZBPzX 9w3D41jD8QquacUrRU53mwRWR0l5WsjWoq4W7jlixGbX55zKgcDeCmrMqNn78nFb7C 9OJclZ02uySuJMbxYazN6m5j3QgknU/S2PN+/OOyV4jRo+cIWK4XjfeHlirgKvXkzT tU5CPmeAIeZca09j0kSSnl827nXH+r1MCVunhEDUSWdsOSAA3PtZuBqEnzZpr4e+Al 3mall+EgzXXRUujeKjDV/rgv1IJMStbEMDkDIPEt2oYK+I6auq1YoaphIrh20MvqyQ Ey50t2b9jyqwA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-03v.sys.comcast.net with ESMTPA id dmDdj1dr8tcQpdmDejrHz1; Wed, 27 May 2020 02:55:02 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
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 04R2t0wd021224; Tue, 26 May 2020 22:55:01 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 04R2t06N021217; Tue, 26 May 2020 22:55:00 -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: urn@ietf.org
In-Reply-To: <AM6PR07MB51080E1C8435498002361388FAB00@AM6PR07MB5108.eurprd07.prod.outlook.com> (juha.hakala@helsinki.fi)
Sender: worley@ariadne.com
Date: Tue, 26 May 2020 22:55:00 -0400
Message-ID: <87eer6jddn.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/tlYUSaOlw2epiTWXeXwaQaH4k2g>
Subject: Re: [urn] META URN namespace registration
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
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, 27 May 2020 02:55:07 -0000

This looks good to me, except possibly these:

    Namespace URN:META:MARC: contains URNs which identify the tags of

You almost certainly don't want the final ":", as that presupposes that
a sub-namespace code will follow.  Other examples use "URN:META:MARC".

    Assuming that the registered resolver base URL for urn:meta:dc is
    http://example.com/, urn:meta:dc:terms-title would be resolved by
    fetching

    http://example.com/urn:meta:dc:terms-title

After looking at these again, I realize that there is an open question
whether the prefix is "dc:terms" or "dc".  There is no mention in the
registrations that "dc:terms" is a defined sub-namespace, but nothing
rules out that it exists.  If the intended prefix is "dc", then the URN
should be "urn:meta:dc-terms-title".  If the intended prefix is
"dc:terms", it would prevent the reader from making this mistake if you
state that explicitly.  Indeed, if "dc" is expected to have
sub-namespaces, it might be useful to annotate its registration with
their names.

Dale