Re: URI for XML schema and namespace

Julian Reschke <julian.reschke@gmx.de> Fri, 04 January 2008 16:36 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 1JApXP-0005vG-PY; Fri, 04 Jan 2008 11:36:51 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1JApXO-0005v3-Im for discuss-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 11:36:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JApXN-0005us-S8 for discuss@apps.ietf.org; Fri, 04 Jan 2008 11:36:50 -0500
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JApXM-0007Rb-T6 for discuss@apps.ietf.org; Fri, 04 Jan 2008 11:36:49 -0500
Received: (qmail invoked by alias); 04 Jan 2008 16:36:47 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.118]) [217.91.35.233] by mail.gmx.net (mp055) with SMTP; 04 Jan 2008 17:36:47 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/2v51DSjz2r2CYij61/Kb2R2GWL7j5FilhXpNi2c JTIUEQTDAWvrhK
Message-ID: <477E609E.6010402@gmx.de>
Date: Fri, 04 Jan 2008 17:36:46 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: URI for XML schema and namespace
References: <FB2B4EC3-BE66-4192-8657-F318BF9F0329@osafoundation.org> <00a601c84edd$2ca4dcc0$0601a8c0@pc6><000001c84ee8$789307a0$0223520a@charger> <477E568E.8050307@gmx.de> <000201c84eeb$77c9e3e0$0223520a@charger> <104301c84eed$1bbd8500$6502a8c0@china.huawei.com> <477E5DA1.9040504@gmx.de> <477E5DFD.10302@stpeter.im>
In-Reply-To: <477E5DFD.10302@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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

Peter Saint-Andre wrote:
> Besides, URNs are relatively easy to obtain, so why not use them?

Because you can't resolve them, unless you have out-of-band information 
about how to do that.

If you encounter a namespace URI such as 
"urn:ietf:params:xml:ns:contact-1.0", you'll have to google for it to 
obtain information about what it is. In this case, you'll find the right 
thing, but it would be much easier if the IANA just assigned namespace 
URIs such as

   <http://ns.ietf.org/contact-1.0>

in the first place.

The fact that it does not has caused many specs to get their namespace 
URIs from other places, such as the W3C and purl.org.

BR, Julian