Re: [VCARDDAV] vcardrev nits

Kurt Zeilenga <Kurt.Zeilenga@Isode.com> Wed, 16 September 2009 10:18 UTC

Return-Path: <Kurt.Zeilenga@Isode.com>
X-Original-To: vcarddav@core3.amsl.com
Delivered-To: vcarddav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A66D3A6936 for <vcarddav@core3.amsl.com>; Wed, 16 Sep 2009 03:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1E09lyRIUEM for <vcarddav@core3.amsl.com>; Wed, 16 Sep 2009 03:18:46 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 577053A68C2 for <vcarddav@ietf.org>; Wed, 16 Sep 2009 03:18:46 -0700 (PDT)
Received: from [192.168.1.108] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <SrC7tgB9YZ6M@rufus.isode.com>; Wed, 16 Sep 2009 11:19:34 +0100
X-SMTP-Protocol-Errors: NORDNS
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
In-Reply-To: <4AB0B66D.2020405@gmx.de>
Date: Wed, 16 Sep 2009 11:19:33 +0100
Message-Id: <19BA774F-0587-4D8E-BB83-05AB96DFF0AA@Isode.com>
References: <4AB00791.4040005@stpeter.im> <4A6CDE38802D481BAF82CDF30E08B75E@Javier2> <4AB095A2.2090407@gmx.de> <A7EB3517-B7DA-44D6-81FA-31B7EBAB9BD4@Isode.com> <4AB0B66D.2020405@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1076)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Cc: vcarddav@ietf.org
Subject: Re: [VCARDDAV] vcardrev nits
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2009 10:18:47 -0000

On Sep 16, 2009, at 10:57 AM, Julian Reschke wrote:

> Kurt Zeilenga wrote:
>> ...
>> I disagree.
>> If for some reason the I-D refers to information in the (to be)  
>> obsoleted information, then yes.  But this is no different than any  
>> other informational reference.   However, if the I-D simply has:
>> Obsoletes: RFC X
>> and text:
>>    This document obsoletes RFC X.
>> There is no need to have an informative reference and, in my  
>> opinion, having a informative reference for just such is  
>> distracting and ought to be avoided.
>> ...
>
> You are right if there's nothing else that needs to be said.
>
> Frequently however, a revision of spec actually makes changes, in  
> which case I would expect a "changes since rfc xxxx" section, which  
> optimally should be precise in what changed (potentially including  
> references to specific sections in the original spec).

I would avoid adding a reference even in this case.  But I don't care  
strongly about it.  I'm fine with leaving the decision to the  
document's editor.

-- Kurt