Re: Review and URN assignment for draft-seantek-xmlns-urn-00

worley@ariadne.com (Dale R. Worley) Tue, 11 November 2014 16:10 UTC

Return-Path: <worley@ariadne.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9A01A902B for <urn-nid@ietfa.amsl.com>; Tue, 11 Nov 2014 08:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 05A5Qt86brO5 for <urn-nid@ietfa.amsl.com>; Tue, 11 Nov 2014 08:09:59 -0800 (PST)
Received: from resqmta-po-07v.sys.comcast.net (resqmta-po-07v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:166]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA89A1A8BB5 for <urn-nid@ietf.org>; Tue, 11 Nov 2014 08:09:58 -0800 (PST)
Received: from resomta-po-07v.sys.comcast.net ([96.114.154.231]) by resqmta-po-07v.sys.comcast.net with comcast id EG9F1p0064zp9eg01G9yxu; Tue, 11 Nov 2014 16:09:58 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-07v.sys.comcast.net with comcast id EG9x1p0011KKtkw01G9xy0; Tue, 11 Nov 2014 16:09:58 +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 sABG9uUW008943; Tue, 11 Nov 2014 11:09:56 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id sABG9uE8008942; Tue, 11 Nov 2014 11:09:56 -0500
Date: Tue, 11 Nov 2014 11:09:56 -0500
Message-Id: <201411111609.sABG9uE8008942@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Sean Leonard <dev+ietf@seantek.com>
In-reply-to: <6A6694AE-BC9B-4058-8DE5-6B2FA8AE5B84@seantek.com> (dev+ietf@seantek.com)
Subject: Re: Review and URN assignment for draft-seantek-xmlns-urn-00
References: <6A6694AE-BC9B-4058-8DE5-6B2FA8AE5B84@seantek.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1415722198; bh=ZGFRnkc1YtErRagTsqc90YcpK6YDbh1Jkq7oy78/4KU=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=Ehl6txQktD2/UbKdNHZCFPGV1ry4hleLVmo7ddjvnpJaL54W50pY1ZkzOc0FYOFIZ +ZbPizHXrm4FPeTCNQErDvnTKSzV5OfWJ9CSRAq0zVAsIExceGdo0ArhdSWR/CwVKR SlDaBXSQBnINnAsGi3nBpHmtBfIHqm86aU8U9fvwPWYD5ka7IGecNyf4LqS2zhu4sv vTe0cFOy3DPsMTLRa4TTkDU6L/nl0Kid9qHsn/c7LW2O9rHO2Ph1j7ykwCr1CdUUY8 3QWtgb6p5u2oizgk49pSLr/lcqgeCVDOvkiKtEAxMeWGAvKh18AhwRHppikgFlJ+w/ vUhRPb5GSEaQA==
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/j_kuXz9NSxFGmkqzQtAWPe8cof0
Cc: urn-nid@ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 16:10:02 -0000

I'd like to see more discussion of why this NID is needed.  The draft
says:

   Experience suggests that several URN namespace registrations have
   been proposed over the years, where the primary (yet only
   occasionally stated) purpose is to create short URIs for the
   registrant's XML namespaces.

That's true, but one can create URIs to name one's XML namespaces in
many ways already.  One can use "oid" URNs, or "tag" URIs, or build
HTTP URLs based on one's domain registration.

The draft continues:

   registrant's XML namespaces.  An XML namespace designer now has the
   option of choosing a short, memorable identifier ...

I assume that means "This draft provides an XML namespace designer
with the option...", even though the "now" in that sentence is
ambiguous -- does it refer to the time before adoption of the draft or
after?

It seems that mnemonicity is a goal.  But in practice, the nicely
mnemonic values will be taken fairly quickly and future registrants
will be restricted to non-mnemonic values -- unless some sort of
de-facto grouping convention comes to be used.

I've got some other issues with this draft, but they can be postponed
until we resolve why the NID is needed.  (They are very similar to my
issues with draft-seantek-rdf-urn-00.)

Dale