Re: [urn] IANA repository Re: New Version Notification for draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt (fwd)

Peter Saint-Andre <stpeter@stpeter.im> Sun, 25 March 2012 23:35 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E719E21F8456 for <urn@ietfa.amsl.com>; Sun, 25 Mar 2012 16:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7bDN4wQmAg41 for <urn@ietfa.amsl.com>; Sun, 25 Mar 2012 16:35:05 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD7621F8453 for <urn@ietf.org>; Sun, 25 Mar 2012 16:35:05 -0700 (PDT)
Received: from squire.lan (unknown [82.66.240.205]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3F77C4009B; Sun, 25 Mar 2012 17:47:57 -0600 (MDT)
Message-ID: <4F6FABA1.9050806@stpeter.im>
Date: Mon, 26 Mar 2012 01:34:57 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
References: <201203122052.VAA22918@TR-Sys.de> <4F6F1695.9090606@thinkingcat.com> <61D1B733-0575-4DDF-B2CB-CCEDC25BAC1F@viagenie.ca>
In-Reply-To: <61D1B733-0575-4DDF-B2CB-CCEDC25BAC1F@viagenie.ca>
X-Enigmail-Version: 1.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: urn@ietf.org
Subject: Re: [urn] IANA repository Re: New Version Notification for draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt (fwd)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Mar 2012 23:35:08 -0000

On 3/25/12 3:07 PM, Marc Blanchet wrote:
> 
> Le 2012-03-25 à 14:59, Leslie Daigle a écrit :
> 
>>
>> Hi,
>>
>> Is this point in the document:
>>
>>>  [[ NOTE: It would be preferable to restore the generic, most
>>>   universally supported (HTML) form of the registry be identified by an
>>>   implementation-neutral URL, as previously supported by IANA:
>>>   <http://www.iana.org/assignments/urn-namespaces>.  Yet, currently
>>>   this URI and similar forms all resolve to an XML version.
>>>   The content there should link to alternate forms (.xml, .txt), and
>>>   those alternate versions should indicate the *other* versions; i.e.,
>>>   where the .txt version (currently only available at ftp.IANA.ORG
>>> <http://ftp.IANA.ORG>)
>>>   also says, "This registry is also available in XML and plain text
>>>   formats.", it should better say: "This registry is also available in
>>>   HTML and XML formats."  Similarly, the XML form should point to the
>>>   HTML and plain text forms. ]]
>>
>>
>> actually a question for the URN document, or rather something for the
>> IESG/IAB to explain or take up with IANA?  I.e., it seems to me that
>> this is a broader question of references to IANA registries, and not
>> just *this* reference to *an* IANA registry?
> 
> - actually, the note above (the extract from the document) is wrong.
>  +  each XML registry has in the note: "This registry is also available
> in plain text
> <http://www.iana.org/assignments/urn-namespaces/urn-namespaces.txt>."
>  and the .txt is available by http.
>  + the html version is redundant. the xml version has xsl statement for
> browsers to render it in html on the fly. so no need to have a separate
> html page.

Yes, this text is quite out of place in the document and needs to be
removed.

Peter

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