RE: URI for XML schema and namespace

Chris Newman <Chris.Newman@Sun.COM> Fri, 04 January 2008 23:46 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 1JAwEo-000084-LA; Fri, 04 Jan 2008 18:46:06 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1JAwEn-0008Vo-TO for discuss-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 18:46:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JAwEn-0008Tc-Gu for discuss@apps.ietf.org; Fri, 04 Jan 2008 18:46:05 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JAwEj-0008SX-R6 for discuss@apps.ietf.org; Fri, 04 Jan 2008 18:46:05 -0500
Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m04Nk1nR011675 for <discuss@apps.ietf.org>; Fri, 4 Jan 2008 23:46:01 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JU500F018IN3N00@mail-amer.sun.com> (original mail from Chris.Newman@Sun.COM) for discuss@apps.ietf.org; Fri, 04 Jan 2008 16:46:01 -0700 (MST)
Received: from [10.1.110.5] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JU500H178ONF910@mail-amer.sun.com>; Fri, 04 Jan 2008 16:46:01 -0700 (MST)
Date: Fri, 04 Jan 2008 15:46:02 -0800
From: Chris Newman <Chris.Newman@Sun.COM>
Subject: RE: URI for XML schema and namespace
In-reply-to: <105601c84ef1$90d0d870$6502a8c0@china.huawei.com>
To: David Harrington <ietfdbh@comcast.net>, "'Julian Reschke'" <julian.reschke@gmx.de>
Message-id: <BF4EFF66D86A25114BC4C81A@446E7922C82D299DB29D899F>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
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> <105601c84ef1$90d0d870$6502a8c0@china.huawei.com>
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
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

As Applications Area Director, I'm not aware of anyone ever asking for that.

I'm holding a discuss position on:
   draft-narten-iana-considerations-rfc2434bis-08
because the present text forbids use of IANA URLs and I consider that an 
unacceptable new restriction for IANA considerations.

Current IETF practice discourages use of IANA URLs in IETF specifications. 
However, we have one case, RFC 4790, where stable iana.org http URLs are 
provided to registry elements and that was done with IANA's permission.  In 
that case, the registry was created to be useful to both the IETF and the W3C. 
The stable http URLs make the W3C happier so it was worth doing that way.

I would support a similar approach for iana.org http XML namespaces if someone 
spent the time to write up the rules and get IANA's consent.

Using an ietf.org http URIs for XML namespaces is a bad idea.  The IETF has 
deliberately kept the registry function for our standards separate and I 
consider that a feature.  Also, ietf.org is operated by the Secretariat 
function so using that domain for registrations would require additional (and 
more expensive) coordination than iana.org.  It _might_ be feasible to set up a 
redirect from ietf.org to iana.org for XML namespaces, but I worry that's just 
one additional level of complexity where things could break (especially if we 
transition the secretariat function between vendors periodically as we're in 
the process of doing now).

To summarize the options:
1. URNs for XML namespaces -- present IETF common practice
2. non-IETF http URLs for XML namespaces -- acceptable
3. iana.org http URLs for XML namespaces -- nobody has tried this, seems 
feasible to me.
4. ietf.org http URLs for XML namespaces -- nobody has tried this.  I think 
it's a bad idea.

                - Chris

David Harrington wrote on 1/4/08 11:47 -0500:

> Hi Julian,
>
> That's an interesting observation, but it didn't answer my question.
> Has anybody explicitly asked the people who can create such a
> permanent web site to do so?
> Has anybody fashioned an explicit proposal for the establishment of
> permanent IETF URIs?
>
> Am I off-target with my question?
> Would this simply be a bad idea?
> If it is a good idea, who wants it badly enough to write such a
> proposal?
>
> David Harrington
> dbharrington@comcast.net
> ietfdbh@comcast.net
>
>> -----Original Message-----
>> From: Julian Reschke [mailto:julian.reschke@gmx.de]
>> Sent: Friday, January 04, 2008 11:24 AM
>> To: David Harrington
>> Cc: 'Scott Hollenbeck'; 'Apps Discuss'
>> Subject: Re: URI for XML schema and namespace
>>
>> David Harrington wrote:
>> > Has anybody actually asked Ray to get such a  permanent
>> part of IETF's
>> > own web space allocated and setup? Would entries on the web site
>> > require IANA assignment, e.g. as a registry?
>> >
>> > I'm asking because I am new to the discussion, and simply don't
> know
>> > the answer.
>> >
>> > dbh
>>
>> I think historically there's a lot of reluctance inside IANA (or the
>
>> whole IESG) to consider any URI starting with "http" as permanent.
>>
>> BR, Julian
>>
>
>
>
>
>