Re: [calsify] Feedback on draft-ietf-calext-icalendar-series

Marten Gajda <marten@dmfs.org> Wed, 20 November 2019 16:00 UTC

Return-Path: <marten@dmfs.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7DE21208FE for <calsify@ietfa.amsl.com>; Wed, 20 Nov 2019 08:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dmfs.org
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 lSpxtzpisebq for <calsify@ietfa.amsl.com>; Wed, 20 Nov 2019 08:00:08 -0800 (PST)
Received: from mailrelay3-1.pub.mailoutpod1-cph3.one.com (mailrelay3-1.pub.mailoutpod1-cph3.one.com [46.30.210.184]) (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 436651208F6 for <calsify@ietf.org>; Wed, 20 Nov 2019 08:00:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dmfs.org; s=20191106; h=content-type:in-reply-to:mime-version:date:message-id:from:references:to: subject:from; bh=84w1S4d1GHd0cPyf/Xm1FPUygNMhbFnZ03rVmiIpeNo=; b=btlfTvIJZGzLc9w6GemTS9Vugb6FmOSs320H2RzxUQGBj3/EKgcYl/tSyiSAjlEWgFOQlZVAIGQSW kTUsmGaGpRZntsTkcRtuLINW02EeEYatiBqOh4B4Zf6aEZJrMNH4TXElY9pI60utnd+uRbFn7wWUDu O8orUJ6iNPf6VugIEE0hvXmoYJhT/xZtWB+1nZDEddSRtmRQdDi7i03v48UCLtOwOnRWgO3KNJlEor qLskO576aAdESn1RmNIL6YjEomal0Nuz8/jFMOrE7BvbE0PrgGbkiS5YbLyhUCZp9lGxXJKH86t+Uq wc0ARbBnttdMzPlXDchiMrC6u158Tig==
X-HalOne-Cookie: 3a40d7fca001ee40aeeffeeaa7c5b4eb565f1ab7
X-HalOne-ID: d0c91088-0bae-11ea-b5f1-d0431ea8bb03
Received: from smtp.dmfs.org (unknown [2003:fa:af05:8e00:201:2eff:fe40:2624]) by mailrelay3.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id d0c91088-0bae-11ea-b5f1-d0431ea8bb03; Wed, 20 Nov 2019 16:00:04 +0000 (UTC)
Received: from boss.localdomain (pD95ED904.dip0.t-ipconnect.de [217.94.217.4]) by smtp.dmfs.org (Postfix) with ESMTPSA id 3401C3A9 for <calsify@ietf.org>; Wed, 20 Nov 2019 17:00:04 +0100 (CET)
To: calsify@ietf.org
References: <1f7475db-bcad-4c27-bb30-f043665b1f96@dogfood.fastmail.com> <7773f271-9273-db87-511c-81ee19a30ec4@gmail.com>
From: Marten Gajda <marten@dmfs.org>
Message-ID: <2597b107-c18a-c523-e247-cc3d03620660@dmfs.org>
Date: Wed, 20 Nov 2019 17:00:03 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <7773f271-9273-db87-511c-81ee19a30ec4@gmail.com>
Content-Type: multipart/alternative; boundary="------------853D3DE2BF088E8E87C56F35"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/y9ECua75xtCd-gMf8u1FAu0hb_U>
Subject: Re: [calsify] Feedback on draft-ietf-calext-icalendar-series
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 20 Nov 2019 16:00:11 -0000

Am 19.11.19 um 17:12 schrieb Michael Douglass:
>
> Thanks Neil
>
> On 11/18/19 07:14, Neil Jenkins wrote:
>> I think this concept is good, but this spec needs a fair bit more 
>> work (as noted in the meeting today, this should have been a call for 
>> adoption, not WGLC!)
>>
>> The "series master" is a kind of template; it's not an event itself, 
>> it just generates them. It might make more sense therefore to make 
>> this a different component, e.g. |VEVENTTEMPLATE|. Clients that don't 
>> support the spec should simply ignore them, which is what we want. We 
>> can also then reuse standard RRULE etc. properties and don't need to 
>> define separate SRULE etc. properties.
>>
> Good idea - I'll work on that.
>
I like the idea of a separate SRULE. It allows you to declare series of 
recurring events. That way you can specify more complex recurrence 
patterns which you can't express with a single RRULE. For instance, an 
event recurring every 1st Monday of June for three days or an event 
recurring on eight consecutive days starting every other week.

Marten

-- 
Marten Gajda
CEO

dmfs GmbH
Schandauer Straße 34
01309 Dresden
GERMANY

phone: +49 177 4427167
email: marten@dmfs.org

Managing Director: Marten Gajda
Registered address: Dresden
Registered No.: AG Dresden HRB 34881
VAT Reg. No.: DE303248743