IETF Logo Mail Archive

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

Philipp Kewisch <kewisch@gmail.com> Thu, 03 April 2014 14:00 UTC

Return-Path: <kewisch@gmail.com>
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 78FEB1A0218 for <jcardcal@ietfa.amsl.com>; Thu, 3 Apr 2014 07:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 To3KDh2-Mhot for <jcardcal@ietfa.amsl.com>; Thu, 3 Apr 2014 07:00:13 -0700 (PDT)
Received: from mail-bk0-x22d.google.com (mail-bk0-x22d.google.com [IPv6:2a00:1450:4008:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id F15591A0216 for <jcardcal@ietf.org>; Thu, 3 Apr 2014 07:00:12 -0700 (PDT)
Received: by mail-bk0-f45.google.com with SMTP id na10so177224bkb.18 for <jcardcal@ietf.org>; Thu, 03 Apr 2014 07:00:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rjlHyxooi4XqMWyx6M5Q8UQT9uS1Lv5gUzx8MnClzeE=; b=S4Horw0AFlYy8lHo2Fhq55aB2AxQMwtLi2lltEzQ/qQkw9NId8uh8S4I6EgXc7fAzl jL9Anuw6vq6/WPuI/efaahBw+PV2pfpOhAHnlsqtF7a3+W+yrPCfbD6pCbD9gQuuvcJ0 6XvQzHiuIiKps/9NtCxg4oxFCePyyi0TwpglwUNxTngUUm7DWGfFaJA98sGN+GLiRA8p 2zxZdkp1oByYnyPX07FKuRi0KyhFKFgVrjpZFhmgvr9ywSH0Rlwe8DQoH+bzApzLe51h 0KPAdE7xHaeeHRCQoAevsm+cWsZE8lj622XLFeb+SBX2sZZg4c90WiGuOBUFb38X0bN8 BTZw==
X-Received: by 10.204.171.204 with SMTP id i12mr11611bkz.172.1396533608070; Thu, 03 Apr 2014 07:00:08 -0700 (PDT)
Received: from oskar.fritz.box (dslb-188-108-000-171.pools.arcor-ip.net. [188.108.0.171]) by mx.google.com with ESMTPSA id el11sm5413294bkb.8.2014.04.03.07.00.06 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Apr 2014 07:00:07 -0700 (PDT)
Message-ID: <533D6966.9070701@gmail.com>
Date: Thu, 03 Apr 2014 16:00:06 +0200
From: Philipp Kewisch <kewisch@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Thunderbird/28.0
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>, Peter Saint-Andre <stpeter@stpeter.im>, Pete Resnick <presnick@qti.qualcomm.com>, bert.greevenbosch@huawei.com
References: <533D55F0.6020608@gmail.com> <533D6768.4000808@stpeter.im> <7D633CDA8E408479C296FC81@caldav.corp.apple.com>
In-Reply-To: <7D633CDA8E408479C296FC81@caldav.corp.apple.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/jcardcal/HgG0Jw10NOaAMqp6o6msEymPdE0
Cc: draft-daboo-icalendar-rscale@tools.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 14:00:18 -0000

On 4/3/14, 3:57 PM, Cyrus Daboo wrote:
> Hi Peter,
>
> --On April 3, 2014 at 7:51:36 AM -0600 Peter Saint-Andre
> <stpeter@stpeter.im> wrote:
>
>> 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.
>
> I would agree that jcal should not change at this point. RSCALE is
> still a draft and can be changed if real problems are encountered.
>
Hi Peter, Cyrus,

thanks for letting me know. I would also prefer not to make any further
changes to jCal, I just wanted to bring it up in case someone thinks
otherwise.

Philipp

v2.23.0 | Report a Bug | By Email