Re: [urn] 2141bis questions - (10) Backward compatibility

Juha Hakala <juha.hakala@helsinki.fi> Mon, 26 January 2015 05:21 UTC

Return-Path: <juha.hakala@helsinki.fi>
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 6525E1A1BF2 for <urn@ietfa.amsl.com>; Sun, 25 Jan 2015 21:21:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 GhRd347z2OG9 for <urn@ietfa.amsl.com>; Sun, 25 Jan 2015 21:21:37 -0800 (PST)
Received: from smtp-rs1-vallila2.fe.helsinki.fi (smtp-rs1-vallila2.fe.helsinki.fi [128.214.173.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E09E1A1BED for <urn@ietf.org>; Sun, 25 Jan 2015 21:21:36 -0800 (PST)
Received: from [128.214.71.180] (lh2-kkl1206.lib.helsinki.fi [128.214.71.180]) (authenticated bits=0) by smtp-rs1.it.helsinki.fi (8.14.4/8.14.4) with ESMTP id t0Q5LV3j016651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 26 Jan 2015 07:21:32 +0200
Message-ID: <54C5CEDB.6060003@helsinki.fi>
Date: Mon, 26 Jan 2015 07:21:31 +0200
From: Juha Hakala <juha.hakala@helsinki.fi>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Peter Saint-Andre - &yet <peter@andyet.net>, urn@ietf.org
References: <E164F0F42FAE04DAB79EC713@JcK-HP8200.jck.com> <54AA709D.2050107@helsinki.fi> <54C45F87.30608@andyet.net> <83A5A9CF54B42BA6D710080F@JcK-HP8200.jck.com>
In-Reply-To: <83A5A9CF54B42BA6D710080F@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/K2w70eTKcbJRJ0W4fxeDQPE49r8>
Subject: Re: [urn] 2141bis questions - (10) Backward compatibility
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: Mon, 26 Jan 2015 05:21:39 -0000

Hello,

on the basis of experiences gathered during the revision of ISBN and NBN 
namespace registration requests, the revised text below works fine.

It is important to include changes both in namespace management 
processes and in underlying technologies, since a technological change 
may have a major impact on the management of the namespace (for 
instance, a change in the syntax of the identifier  may alter the way in 
which the URNs can be resolved).

Juha

On 25.1.2015 11:58, John C Klensin wrote:
>
> --On Saturday, January 24, 2015 20:14 -0700 Peter Saint-Andre -
> &yet <peter@andyet.net> wrote:
>
>> On 1/5/15 4:08 AM, Juha Hakala wrote:
>>> Hello,
>>>
>>> On 25.12.2014 9:01, John C Klensin wrote:
>>>> The registration procedures for formal and informal
>>>> namespaces (Sections 8.1 and 8.2) both provide for revisions
>>>> of the registration by updating the template.   Especially
>>>> given some discussions in the WG, I think we should impose
>>>> an explicit requirement for a description of differences
>>>> from prior versions and/or backward compatibility in updated
>>>> registrations.
>>>>
>>>> Do others agree?
>>> + 1
>> Good idea.
> I rarely object to making a requirement stronger.   In the
> working draft, ast sentence of section 8.1 tentatively revised
> to read:
>
> 	"A revised registration MUST describe differences from
> 	prior versions and SHOULD make special note of any
> 	relevant changes in the underlying technologies or
> 	namespace management processes."
>
> and a new template section added (A.10) to provide an explicit
> slot for revision information.
>
> That work?
>
>      john
>
>
>
>
>


-- 

  Juha Hakala
  Senior advisor

  The National Library of Finland
  Library Network Services
  P.O.Box 26 (Teollisuuskatu 23)
  FIN-00014 Helsinki University
  Tel. +358 9 191 44293
  Mobile +358 50 3827678