IETF Logo Mail Archive

Re: [Jcardcal] Last Minute jCal changes? RSCALE extension might mess with data type

Peter Saint-Andre <stpeter@stpeter.im> Thu, 03 April 2014 13:51 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: jcardcal@ietfa.amsl.com
Delivered-To: jcardcal@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAE4B1A01C3 for <jcardcal@ietfa.amsl.com>; Thu, 3 Apr 2014 06:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 NlFujWT94juF for <jcardcal@ietfa.amsl.com>; Thu, 3 Apr 2014 06:51:46 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CD2731A0299 for <jcardcal@ietf.org>; Thu, 3 Apr 2014 06:51:46 -0700 (PDT)
Received: from aither.local (unknown [24.8.184.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6B1C94010C; Thu, 3 Apr 2014 07:51:37 -0600 (MDT)
Message-ID: <533D6768.4000808@stpeter.im>
Date: Thu, 03 Apr 2014 07:51:36 -0600
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.4.0
MIME-Version: 1.0
To: Philipp Kewisch <kewisch@gmail.com>, Pete Resnick <presnick@qti.qualcomm.com>, bert.greevenbosch@huawei.com
References: <533D55F0.6020608@gmail.com>
In-Reply-To: <533D55F0.6020608@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/jcardcal/Rh-WjDyn0f67607z59-Vho7BEq8
Cc: draft-daboo-icalendar-rscale@tools.ietf.org, "jcardcal@ietf.org" <jcardcal@ietf.org>
Subject: Re: [Jcardcal] Last Minute jCal changes? RSCALE extension might mess with data type
X-BeenThere: jcardcal@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: JSON data formats for vCard and iCalendar WG <jcardcal.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jcardcal/>
List-Post: <mailto:jcardcal@ietf.org>
List-Help: <mailto:jcardcal-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 13:51:54 -0000

On 4/3/14, 6:37 AM, Philipp Kewisch wrote:
> Hi Folks,
>
> this is very late in the game, but I just came across this today while
> updating my ical.js library. Taking a look at the RSCALE draft:
> http://tools.ietf.org/html/draft-daboo-icalendar-rscale-03 I noticed
> that possible values for monthnum can now contain a string too instead
> of just digits:
>
> monthnum        = [plus / minus] 1*2DIGIT  ["L"]
>                      ; Existing element modified to include a positive
>                      ; or negative offset capability, as well as a leap
>                      ; month indicator suffix.

With my WG chair hat on, I have concerns.

Why is the RSCALE draft modifying an existing element from RFC 5545 
instead of defining a new element? How certain are we that the draft 
Cyrus and Gregory are working on will end up changing monthnum? Do we 
really want to be tracking an I-D with an uncertain future?

It seems more prudent, at this late date, to align only with RFC 5545.

Peter

v2.23.0 | Report a Bug | By Email