Re: [calsify] draft-daboo-icalendar-rscale-04 editorial nits

Cyrus Daboo <cyrus@daboo.name> Sat, 04 October 2014 16:29 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3721A00DF for <calsify@ietfa.amsl.com>; Sat, 4 Oct 2014 09:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.014
X-Spam-Level:
X-Spam-Status: No, score=0.014 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.786] 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 e_IWWflzvnGU for <calsify@ietfa.amsl.com>; Sat, 4 Oct 2014 09:28:59 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB3671A00DD for <calsify@ietf.org>; Sat, 4 Oct 2014 09:28:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 4DFFBB0F543; Sat, 4 Oct 2014 12:26:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nifYzryT47eb; Sat, 4 Oct 2014 12:26:33 -0400 (EDT)
Received: from [192.168.1.232] (94.197.120.241.threembb.co.uk [94.197.120.241]) by daboo.name (Postfix) with ESMTPSA id D68F3B0F538; Sat, 4 Oct 2014 12:26:32 -0400 (EDT)
Date: Sat, 04 Oct 2014 17:28:52 +0100
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@andrew.cmu.edu>, calsify@ietf.org
Message-ID: <FDF2BEB55679BADC1A5A0D51@cyrus.local>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1745"
Archived-At: http://mailarchive.ietf.org/arch/msg/calsify/6xSqzX27dkOy8v62WsZ5HoMBB6w
Subject: Re: [calsify] draft-daboo-icalendar-rscale-04 editorial nits
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Oct 2014 16:29:00 -0000

Hi Ken,
Thanks for your review. I will apply fixes to the WG -00 draft which I am 
working on now.

--On October 3, 2014 at 9:32:04 AM -0400 Ken Murchison 
<murch@andrew.cmu.edu> wrote:

> Section 3, 2nd last sent: This might be more of a regional thing, but
> should "later" be "latter" ?

Fixed.

> Section 3, last sent: Since iCalendar uses ISO weeks, should we say "The
> number of whole [ISO.8601.2004] weeks in a year is either 52 or 53" ?

Well the ISO things refers to how weeks are numbered not actual weeks in a 
year - there are always 52 whole weeks in a year (if you start counting 
from 1st January). I would be willingly to clarify the text with this 
change:

    The number of whole weeks in a year is 52 (though the [ISO.8601.2004]
    week numbering scheme used by iCalendar [RFC5545] can have a numeric
    count up to 53).

> Section 3: para 3: The two items listed seem more like guidelines,
> principles, or rules rather than a procedure.  Should we change "the
> following procedure is used" to "the following principles are followed"
> or "the following rules are used" or some other permutation?

I will use "principles".

> Section, 1st sent: "clients and server" -> "clients and servers"

Fixed.

> Section 11.1, UNICODE.CLDR: Should we use the following URI rather than
> picking a particular release?
> http://www.unicode.org/repos/cldr/tags/latest/common/bcp47/calendar.xml

I have updated that to the latest release. However, I am not sure about 
doing what you suggest given that this is a normative reference. I would 
have thought a "stable" reference is preferred rather than a "moving 
target". It would be good to get some feedback from the 
chairs/ADs/RFC-Editor (or anyone else) on that.

-- 
Cyrus Daboo