[urn] editorial comments on draft-ietf-urnbis-ns-reg-transition-01
Peter Saint-Andre <stpeter@stpeter.im> Wed, 12 February 2014 16:10 UTC
Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E149B1A040E for <urn@ietfa.amsl.com>; Wed, 12 Feb 2014 08:10:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0ixcuMLeGPA for <urn@ietfa.amsl.com>; Wed, 12 Feb 2014 08:10:54 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 27A9F1A047A for <urn@ietf.org>; Wed, 12 Feb 2014 08:10:54 -0800 (PST)
Received: from aither.local (unknown [24.8.129.242]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id CE2FE40410; Wed, 12 Feb 2014 09:10:52 -0700 (MST)
Message-ID: <52FB9D0C.3070508@stpeter.im>
Date: Wed, 12 Feb 2014 09:10:52 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: urn@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [urn] editorial comments on draft-ietf-urnbis-ns-reg-transition-01
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 12 Feb 2014 16:10:57 -0000
Thanks to John and Juha for working on this document. Overall I think the substance is fine. Here are a few small editorial issues I noticed. 1. Expand URN on first use: As a part of the initial development of the Uniform Resource Name (URN) system... 2. This is a bit awkward: model that focuses more on attempting to get all namespaces that follow the syntax of formal ones registered I suggest: model that focuses more on encouraging registration of all namespaces that follow the formal namespace syntax 3. There's a stray word here: collected as a possible consistent with that goal Should be: collected as possible consistent with that goal 4. A missing and: [RFC3044], International Standard Book Numbers (ISBNs) [RFC3187] Should be: [RFC3044] and International Standard Book Numbers (ISBNs) [RFC3187] 5. This text might be slightly ambiguous: For both ISSN and ISBN URNs, it is intended that the registrations track the evolution of ISO standardization without requiring resubmission of the templates or other formal IETF or IANA registration update approval procedures. I assume that refers to the current registrations, not any future registrations. 6. This is a bit of a run-on sentence: The revised ISBN namespace reflects the updated version of the ISO Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b] and allows for the use of both the ten character numbers described in RFC 3187 and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10) and the expanded ones of the revised standard (known as ISBN-13). Perhaps: The revised ISBN namespace reflects the updated version of the ISO Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b]. The namespace allows for the use of both the ten character numbers described in RFC 3187 and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10), as well as the expanded ones of the revised standard (known as ISBN-13). 7. Typo here: IANA is requested to update the registry entries for URN ISSNs, ISBNs, and NRNs I assume that "NBNs" is meant instead of "NRNs". 8. I sense some ambiguity here: IANA is requested to update the registry entries for URN ISSNs, ISBNs, and NRNs to reflect the new, RFC 3406bis-complaint templates as soon as they are available and to no longer reference the now- historic RFCs. Other registrations and templates conforming to the newer rules may be substituted for the older ones when they are available. However, neither this document nor RFC 3406bis invalidates existing registrations other than those listed above, so IANA needs to be prepared to maintain a registry whose contents reflect both old and new templates. I think "other registrations and templates" might be referring to registrations and templates for namespaces other than ISSN, ISBN, and NBN. I think "supersedes" might be more appropriate than "invalidates". And I think "a registry whose contents reflect both old and new templates" does not imply that IANA would point to both an old and a new template for the same namespace, but for different namespaces. Thus I suggest: IANA is requested to update the registry entries for URN ISSNs, ISBNs, and NBNs to reflect the new, RFC 3406bis-complaint templates as soon as they are available and to no longer reference the now- historic RFCs for those namespaces. With respect to namespaces other than those listed above, registrations and templates conforming to the newer rules may be substituted for the older ones when they are available. However, neither this document nor RFC 3406bis supersedes existing registrations other than those listed above. Therefore, IANA needs to be prepared to maintain a registry whose contents reflect old templates for some namespaces and new templates for other namespaces. Peter -- Peter Saint-Andre https://stpeter.im/
- Re: [urn] ISSNs, ISBNs, and automatic definition … Juha Hakala
- [urn] editorial comments on draft-ietf-urnbis-ns-… Peter Saint-Andre
- Re: [urn] editorial comments on draft-ietf-urnbis… John C Klensin
- [urn] ISSNs, ISBNs, and automatic definition upgr… John C Klensin
- Re: [urn] editorial comments on draft-ietf-urnbis… jehakala