Re: [calsify] JSCalendar duration vs. end time

"Robert Stepanek" <rsto@fastmailteam.com> Thu, 07 March 2019 08:09 UTC

Return-Path: <rsto@fastmailteam.com>
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 D3477130ED0 for <calsify@ietfa.amsl.com>; Thu, 7 Mar 2019 00:09:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.982
X-Spam-Level:
X-Spam-Status: No, score=-1.982 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, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=G7eZbs7L; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Pv+l8UQs
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 OHYQmDCMjZfe for <calsify@ietfa.amsl.com>; Thu, 7 Mar 2019 00:09:06 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F7CE130EDA for <calsify@ietf.org>; Thu, 7 Mar 2019 00:09:06 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 76A1C3530 for <calsify@ietf.org>; Thu, 7 Mar 2019 03:09:05 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Thu, 07 Mar 2019 03:09:05 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=message-id:in-reply-to:references:date:from :to:subject:content-type; s=fm2; bh=0Y/EtfanKo8UrT9Z5HVcQcfoxGHv rM/B2qgMgDDgiz0=; b=G7eZbs7LkMBkYMhrwTj5nyGTcaTZe3kHE/CXwI3zYCl6 HdBtTmhZshI8sHFBG/KvX06v8mY2q3JsEnMFV0ZkSX8Oodu7W36DJXo8IZg/5ceT u5rdIzKPI56zvpZhXM7MeCrOyF5falj+myNb6zQv056PGyaafa1JSSSRIINKP4dl COlsBqkIYAr28dtP37BKqu5C6XoUfa0YO6spRjmgrWWQyq9aRhqBPwQ1WOtG6FyA w8U2dt4L88w0SuiwLbykzhacH6l/HRXMXPTa+njn+vNaTLUT0hZtwQE62GlbQim2 wDuMSMOW75BEpeVqIEpd4B+zBsC/697mU62Rs0lHsg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=0Y/EtfanKo8UrT9Z5 HVcQcfoxGHvrM/B2qgMgDDgiz0=; b=Pv+l8UQseyea0m6EubRpVqanc4PjhMfCt EWZA7tF8L4rHGsJD8n5JVIcsyLhNtpBdtNmoci9eiZM7u4gb7cLION9JbcxUm6wE IFARzlFwY+irFcwLdf1+ArrqZJCy1X4AqXKcodhRkaKXC31gnmqhxnaqm/R8nvQy EE8teRPLbJShIIujpU7k+Vk4FfhGgvwrY4+EcSIwyie907jOgOQmXPTIKY4dY4Pl 4q9oxtBIX5+0AlUsqJQMnOIm5EHZaH8MF36RA5emWkQRRDw5vt6YY3StbS9B2Xjn 70d/kVyDVfMMeTRWPYlWvdaG040A2tBz/hC+QKw2LNoR8ftOnAqBw==
X-ME-Sender: <xms:oNGAXOPEUSsJdaHuCrjqkVO-H3FnmvmbQ4BFkus7tvffTk5jP_eo6A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrfeejgdduudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdftohgsvghrthcuufhtvghprghnvghkfdcuoehrshhtohes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucffohhmrghinhepihgvthhfrdhorhhgne curfgrrhgrmhepmhgrihhlfhhrohhmpehrshhtohesfhgrshhtmhgrihhlthgvrghmrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:oNGAXCxen3NChS79L3WPBj6_qx8IJjPWWmFhV9pa3AFWL0qGVWtHxQ> <xmx:oNGAXHW2eIesbxLsc6LpK8D6dF4u2YTbS_5VXpE59OcjaOPbZIHbow> <xmx:oNGAXHTkz75RLsAU1ztBZtECVSiOqsIEPHKmdz48DkJOifDWQ-JAVg> <xmx:odGAXErOlRIi24_3Uo-VjcQayfFOCuMW0s4859_mehVaPy_O1gEiKw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6289E20430; Thu, 7 Mar 2019 03:09:04 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5
X-Me-Personality: 91525120
Message-Id: <5fb5e30d-f499-4825-8e91-ccedc00e0dac@www.fastmail.com>
In-Reply-To: <6fa84bbb-8f97-44e5-74a7-2dc99e4ef0c6@gmail.com>
References: <1550160126.3602072.1658018976.28709BD3@webmail.messagingengine.com> <6fa84bbb-8f97-44e5-74a7-2dc99e4ef0c6@gmail.com>
Date: Thu, 07 Mar 2019 03:09:04 -0500
From: Robert Stepanek <rsto@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="fa9419a689714d23ad5f9e0283be0c00"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/0zW9mzqyehBIdwYTFxcRzXtFHYM>
Subject: Re: [calsify] JSCalendar duration vs. end time
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: Thu, 07 Mar 2019 08:09:09 -0000

On Thu, Mar 7, 2019, at 2:25 AM, Doug Royer wrote:
> On 2/14/19 9:02 AM, Robert Stepanek wrote:
>> During CalConnect XLIV in Zurich last week, discussion arose if the JSCalendar duration property is enough to define the time span of an event, or if an end time should be allowed as well (see the latest spec here <https://tools.ietf.org/html/draft-ietf-calext-jscalendar-11>).
> This was a big debate at the time 2445 was coming out. The argument was that DURATION is a finite length of time. And that DTEND is a variable amount of time.

> [...]


Thanks for the insight, Doug. Much appreciated to understand the history of this.

> However - iCalendar is the spec, and other representations of it, must adhere to whatever the latest spec says, or the result will be the IETF has 2 or more 'iCalendar' specifications


JSCalendar isn't another representation of iCalendar. While the two data models have much in common, we do not aim at 100% compatibility. The spec explicitly aims to avoid ambiguities and pitfalls of iCalendar.

Cheers,
Robert