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

Sean Leonard <dev+ietf@seantek.com> Wed, 17 December 2014 08:38 UTC

Return-Path: <dev+ietf@seantek.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 2BB621A1AFF for <urn-nid@ietfa.amsl.com>; Wed, 17 Dec 2014 00:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] 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 NrRL9QST3der for <urn-nid@ietfa.amsl.com>; Wed, 17 Dec 2014 00:38:12 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B9031A1AF8 for <urn-nid@ietf.org>; Wed, 17 Dec 2014 00:38:12 -0800 (PST)
Received: from [192.168.123.151] (unknown [23.241.1.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6753822E25C; Wed, 17 Dec 2014 03:37:52 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Review and URN assignment for draft-seantek-xmlns-urn-00
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <201411132041.sADKfWp9031017@hobgoblin.ariadne.com>
Date: Wed, 17 Dec 2014 00:37:51 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <564FB558-0693-4606-A8B8-704B3E2BE0FC@seantek.com>
References: <6A6694AE-BC9B-4058-8DE5-6B2FA8AE5B84@seantek.com> <201411111609.sABG9uE8008942@hobgoblin.ariadne.com> <476745DD-A96F-41C6-9FAD-368FB8C33DE9@seantek.com> <201411121702.sACH2WPC027631@hobgoblin.ariadne.com> <E26AE05A-CD67-4D65-AC5C-73B46B23D338@seantek.com> <201411132041.sADKfWp9031017@hobgoblin.ariadne.com>
To: "Dale R. Worley" <worley@ariadne.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/Dp3dkuNUwD1uZQ4bebth_bAPZRI
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, 17 Dec 2014 08:38:14 -0000

On Nov 13, 2014, at 12:41 PM, Dale R. Worley <worley@ariadne.com> wrote:

>> From: Sean Leonard <dev+ietf@seantek.com>
> 
>> One reason I wrote it was to deal with the brouhaha on urn@ietf.org
>> about fragments (so-called “f-components”). XML namespaces don’t use
>> fragments much, but RDF does. This proposal represents one attempt
>> to deal with fragments in a systematic and URN + URI-compatible way.
> 
> That sounds useful.  But given that the brouhaha exists, you need to
> discuss more explicitly that you expect to use these URNs (1) with
> fragment identifiers and/or (2) containing fragment identifiers -- and
> the consequences thereof.  I don't think you have to solve the general
> problem, but since the general problem hasn't been solved, you have to
> show that you've thought through all the aspects that could arise in
> your envisioned use cases.
> 
> (BTW, are fragment identifiers used with XML namespace identifiers?)

Thanks for the continued review—and sorry that I went on IETF hiatus for a few weeks. It happens with the holidays and with coming back from a beautiful tropical island. :)

To answer this question: to my knowledge fragment identifiers are not really used with XML namespace identifiers. Fragment identifiers are used with RDF (nodes). That being said, the XML-based mechanisms for comparing URIs are the same between XML namespaces and RDF (nodes)—both treat the URI as an opaque string and compare for exact equality. Thus the fragment matters in both cases to the extent that it is a different sequence of characters. As a second-order matter, both offer the temptation for an application to dereference the URI to get some XML namespace or RDF-related resource, even though that is not guaranteed or even implied by the relevant specs.

Sean