Re: URI for XML schema and namespace

Peter Saint-Andre <stpeter@stpeter.im> Fri, 04 January 2008 16:20 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JApHO-000346-0I; Fri, 04 Jan 2008 11:20:18 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1JApHM-00033x-5q for discuss-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 11:20:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JApHL-00033p-SB for discuss@apps.ietf.org; Fri, 04 Jan 2008 11:20:15 -0500
Received: from dizzyd.com ([207.210.219.225]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JApHL-0007B0-6Z for discuss@apps.ietf.org; Fri, 04 Jan 2008 11:20:15 -0500
Received: from wrk225.corp.jabber.com (dencfw1.jabber.com [207.182.164.5]) (Authenticated sender: stpeter) by dizzyd.com (Postfix) with ESMTP id A19C3404A1; Fri, 4 Jan 2008 09:20:08 -0700 (MST)
Message-ID: <477E5CB6.3040705@stpeter.im>
Date: Fri, 04 Jan 2008 09:20:06 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: tbray@textuality.com
Subject: Re: URI for XML schema and namespace
References: <FB2B4EC3-BE66-4192-8657-F318BF9F0329@osafoundation.org> <00a601c84edd$2ca4dcc0$0601a8c0@pc6> <000001c84ee8$789307a0$0223520a@charger> <517bf110801040758l1e304856i8ade84f1c98eefed@mail.gmail.com>
In-Reply-To: <517bf110801040758l1e304856i8ade84f1c98eefed@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080309090907070208060707"
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017
Cc: Apps Discuss <discuss@apps.ietf.org>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Tim Bray wrote:
> On Jan 4, 2008 7:42 AM, Scott Hollenbeck <sah-ietf@tengwar.com> wrote:
> 
>>> What is the currently recommended form for a URI for an XML
>>> schema and an XML namespace?
>>>
>>> The question has come up on ForCES where I, citing RFC3688
>>> say it should be urn:
>>> whereas the others cite RFC3470 to say that http: is recommended.
>>>
>>> Other opinions welcome.
> 
> Well, the Architecture of the World Wide Web
> (http://www.w3.org/TR/webarch) argues strongly that http: URIs are
> generally useful on the grounds that they can in principle (don't have
> to be, but can) be used to retrieve some human-readable explanatory
> material about whatever it is the URI names.   Also the URI itself
> tends to be a bit more human-readable, which seems worthwhile to me.

If http URI, type into browser location bar.

If URN, type into browser search bar.

I don't see a great deal of difference. :)

> The downside, as Scott points out, is that if you want to do that, you
> have to find a domain to put after the http:// part, 

... and ensure that the domain is stable, and that the people running 
the domain will reliably host your namespace, and ...

> and the IETF just
> doesn't do that.  In the case of RFC4287 and 5023, we borrowed one
> from the W3C.

FWIW, we Jabberites used https URIs like http://jabber.org/protocol/* 
for a long time but recently switched to URNs like urn:xmpp:* because 
they're more stable (what happens if the person registering jabber.org 
loses control over the domain?) and will last forever.

The choice of http URI vs. URN seems like a toss-up to me.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/