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

worley@ariadne.com (Dale R. Worley) Wed, 12 November 2014 17:02 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 7C9D61A8AEE for <urn-nid@ietfa.amsl.com>; Wed, 12 Nov 2014 09:02:37 -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 G2ZDQVHpR0yw for <urn-nid@ietfa.amsl.com>; Wed, 12 Nov 2014 09:02:35 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22FD41A6EE5 for <urn-nid@ietf.org>; Wed, 12 Nov 2014 09:02:35 -0800 (PST)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-01v.sys.comcast.net with comcast id Eh2Y1p0052VvR6D01h2aJl; Wed, 12 Nov 2014 17:02:34 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-19v.sys.comcast.net with comcast id Eh2Z1p00C1KKtkw01h2Zzq; Wed, 12 Nov 2014 17:02:34 +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 sACH2Whc027632; Wed, 12 Nov 2014 12:02:32 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id sACH2WPC027631; Wed, 12 Nov 2014 12:02:32 -0500
Date: Wed, 12 Nov 2014 12:02:32 -0500
Message-Id: <201411121702.sACH2WPC027631@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: <476745DD-A96F-41C6-9FAD-368FB8C33DE9@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> <201411111609.sABG9uE8008942@hobgoblin.ariadne.com> <476745DD-A96F-41C6-9FAD-368FB8C33DE9@seantek.com>
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1415811754; bh=AE/G5bTP+Zw6Kv9hEK/9Eov7N5SEH3KX0YT+GTd/C2A=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject:MIME-version:Content-type; b=thJPnVd52rp8f2B24+r8IQLW7f/2ArAjDb6Vy8trM8C83W1i083+TGHOeX1E3Q7ca 7xSh7xa6pLHWJ1kaK6HxBoUGivsKwtJDwvjif4i1r0VOjYPO+A5jV4ScG8HU/7aWBh pqhxofL+bzZz0Wdtil4WFsqccLju50Za28nPNnYMWxqRl05fuA/sfOITX4273PKKqj LY39oxk+AP5A3g5SsQKz4/RgBG+hR64CRgHzbog9Mg+YOxzY4Iuxo26l8HFvt6JD9q Vke9KxGHrggKrC/3qGpFVobYAEhuQWa0l4AMRRcdjbn5uzgEdZc1h6fOiw6WOvTTWK Rak/vhur1/zuQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/DaCpokOxPcj0KqW66mWp1-A0fQQ
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: Wed, 12 Nov 2014 17:02:37 -0000

> From: Sean Leonard <dev+ietf@seantek.com>

> > 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?
> 
> Yes. After adoption of the draft.

Does that mean, "We will edit the text to make that clear."?

> That is correct. However, urn:oid (and for that matter, oid: ) and
> tag: URIs are not really used in practice.

It's true that they're rarely used, but whose problem is that?  There
should be no reason that they *can't* be used.  The real problem (as
you say in text I deleted) is that they're not *mnemonic*.  As you
note below, the mnemonic feature is crucial for your proposal.

> So to answer the question specifically: the namespace is beneficial
> to XML namespace designers who want to have short, mnemonic, unique,
> long-lived URIs, and to XML namespace users (that would be “everyone
> on the Internet”) who rely upon them. You can still use other URIs
> for XML namespaces, but this URN namespace is tailor-made to satisfy
> the needs of that subset of users.

I'd like to see that written into the document as well, as that is the
real description of the purpose of the draft.

Is there truly a lot of demand for these, in particular the "short,
mnemonic" aspects?  I can't think that I would care myself, and I've
named XML namespaces.  (I used http: URLs based on the company's
domain.)

> Compare for “Foo Description Language Version 2":
> http://www.acmecorp.com/xml/foodlv2
> tag:acmecorp.com,2014:foodlv2
> urn:xmlns:acme:foodlv2

I think to a degree the comparison is unfair.  Acme Corp. has the
domain name "acmecorp.com" because "acme.com" was taken.  Which means
that "urn:xmlns:acme" was likely to also have been taken, so Acme
Corp. will be using "urn:xmlns:acmecorp:..." or some such for their
URNs.  That lengthens the final example to
"urn:xmlns:acmecorp:foodlv2", which is still the shortest but is now
only 3 characters shorter than example 2.

Dale