RE: URI for XML schema and namespace

"Scott Hollenbeck" <sah-ietf@tengwar.com> Fri, 04 January 2008 17:40 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 1JAqXT-0005oL-Lq; Fri, 04 Jan 2008 12:40:59 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1JAqXS-0005oC-GS for discuss-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 12:40:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JAqXS-0005n3-6F for discuss@apps.ietf.org; Fri, 04 Jan 2008 12:40:58 -0500
Received: from eastrmmtao103.cox.net ([68.230.240.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JAqXR-00008s-Tj for discuss@apps.ietf.org; Fri, 04 Jan 2008 12:40:58 -0500
Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20080104174058.VZKK24467.eastrmmtao103.cox.net@eastrmimpo02.cox.net>; Fri, 4 Jan 2008 12:40:58 -0500
Received: from charger ([68.100.33.12]) by eastrmimpo02.cox.net with bizsmtp id Z5gN1Y00E0FiBvo0000000; Fri, 04 Jan 2008 12:40:23 -0500
From: "Scott Hollenbeck" <sah-ietf@tengwar.com>
To: "'Julian Reschke'" <julian.reschke@gmx.de>, "'Peter Saint-Andre'" <stpeter@stpeter.im>
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> <477E609E.6010402@gmx.de>
Subject: RE: URI for XML schema and namespace
Date: Fri, 4 Jan 2008 12:40:58 -0500
Message-ID: <001f01c84ef8$f7142e50$0223520a@charger>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <477E609E.6010402@gmx.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AchO8AmVh67TW/dCSf+/wnZd1F/SfAACFhWA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de] 
> Sent: Friday, January 04, 2008 11:37 AM
> To: Peter Saint-Andre
> Cc: 'Apps Discuss'
> Subject: Re: URI for XML schema and namespace
> 
> 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.

That assumes that they need to be resolved.  When they're used to uniquely
identify an XML namespace they don't *need* to be, though I agree that it
might be nice if they *could* be.

-Scott-