Re: [urn] META URN namespace registration

worley@ariadne.com Sun, 24 May 2020 15:23 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 D74463A0A8B for <urn@ietfa.amsl.com>; Sun, 24 May 2020 08:23:13 -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 3_DSz8pObOeR for <urn@ietfa.amsl.com>; Sun, 24 May 2020 08:23:11 -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 B618B3A0A88 for <urn@ietf.org>; Sun, 24 May 2020 08:23:11 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id csEyjyb9pUcArcsT0jeVeE; Sun, 24 May 2020 15:23:10 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1590333790; bh=C8iRXQh179h8x5gUoPUlZxp5dx8ls47E2jpOY4V8AA4=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=VCb94BW2mXlaxteHSUgrNhmYw7yj+oWNs5IrhtJ2yKHTcH1pBxSJYRmUhjZavKZDT eJYKxA44xtjAu+kT+aw2+GZx8wRbyso3AMhnYL1blxUOSvCVeeWVFtdQbt7skFI7Y8 LfmJ9mzspM3/bJQUnb6pK+I+ADmGHy0GdvaY2ldCDUyX4i24RV1dfsyCdvfbc7vhl+ 0im3wGdhkZ+TxCa7ZYo84QcdJtp+XTLtliXPGVSaTNMOHMSztma+DZezs+tCCYH0D9 /OfwbFc9kCd5BdlAefaVaJsfVXh9pjhDyesjKmbWjtWkqkajWQRU+CPrX2/FBKgzNo u/05iZgUCu5pQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-09v.sys.comcast.net with ESMTPA id csSyjnOmaOvcxcsSzjupfb; Sun, 24 May 2020 15:23:10 +0000
X-Xfinity-VMeta: sc=0.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 04OFN2VI032094 for <urn@ietf.org>; Sun, 24 May 2020 11:23:02 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 04OFN2At032091; Sun, 24 May 2020 11:23:02 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: urn@ietf.org
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 24 May 2020 11:23:01 -0400
Message-ID: <87mu5xl5m2.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/31ZP_cspcSD2nanSBQLz7u-UTcM>
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: Sun, 24 May 2020 15:23:14 -0000

"Hakala, Juha E" <juha.hakala@helsinki.fi> writes:
> I have received no feedback to the heavily revised urn:meta
> registration request which I posted in March, and without further
> comments there is not much I can do.

My apologies for not attending to this sooner.

I believe that the urn:meta proposal should be approved after the
following editorial issues have been resolved:

1. At different places in the document two alternative schemes for
delimiters in the syntax are specified or used.  The alternatives are:
(a) the prefix is subdivided using colons, and separated from the
meta-string by a hyphen, and (b) the prefix is subdivided using
hyphens, and separated from the meta-string by a colon.  Instances
are:

1A. The natural-language specification of the syntax uses (a):

    Syntax:  

    The Namespace-Specific String (NSS) consists of three parts:

       o a prefix consisting of a code identifying the metadata format and
	  optional sub-namespace code(s) separated by a colon(s); 

       o a hyphen (-) as the delimiting character; and,

    a string assigned under the auspices of the format maintenance agency. 

1B. The ABNF specification of the syntax uses (b):

	meta-nss     = prefix ":" meta-string

	prefix      = format-code *( "-" subspc )
		    ; The entire prefix is case insensitive.

1C. Some examples use (a):

    (and as a default) URNs http://example.com/urn:meta:marc-<nss>

    is http://example.com/, urn:meta:marc-bd245 would be resolved by

    http://example.com/urn:meta:marc-bd245 

    is http://example.com/, urn:meta:marc-ad100 would be resolved by

    http://example.com/urn:meta:marc-ad100  

Some examples use (b):

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

    http://example.com/, urn:meta:dc-terms:title would be resolved by

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

2. The document recommends using hyphen as an internal delimiter in
meta-string.  This does not conflict with either (a) or (b), but the
author may want to coordinate this choice with the resolution of item 1.

    Within the meta-string, it is recommended that a hyphen is used
    for separating different sections of the identifier from one
    another in order to improve the human readability of the string.

3. The text uses the term "sub-namespace" but does not define it.  It
appears to mean the same as the ABNF symbol "subspc" (which is also
nused in the text).  I think the clearest solution is to replace
"subspc" in all three locations with "sub-namespace".

       o a prefix consisting of a code identifying the metadata format and
	  optional sub-namespace code(s) separated by a colon(s); 

	prefix      = format-code *( "-" subspc )
		    ; The entire prefix is case insensitive.
	subspc      = 1*(ALPHA / DIGIT)
		    ; As assigned by the respective format maintenance agency.

    Sub-namespaces may
    be used to differentiate formats within these format families if
    necessary.

    A registrant may provide additional base URLs for
    prefixes composed of that format-code and one or more following
    subspc's.

4. Comparing this usage of the example.com URL with the others, I
believe that it was intended to end with "/":

    In this example, URNs are expressed as HTTP URIs which use
    (non-existent) URN resolver located http://example.com.

5. In this example, "<nss>" should be "<meta-string>", unless I am
completely misreading its intention:

    (and as a default) URNs http://example.com/urn:meta:marc-<nss>

Dale