IETF Logo Mail Archive

Re: [calsify] JSCalendar duration vs. end time

"Robert Stepanek" <rsto@fastmailteam.com> Fri, 15 February 2019 08:20 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 A40E3130E7E for <calsify@ietfa.amsl.com>; Fri, 15 Feb 2019 00:20:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.983
X-Spam-Level:
X-Spam-Status: No, score=-1.983 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] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=fTPoN0mW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=cV+vkEyc
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 HYQM2fnJIf6e for <calsify@ietfa.amsl.com>; Fri, 15 Feb 2019 00:20:09 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24825129A87 for <calsify@ietf.org>; Fri, 15 Feb 2019 00:20:09 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F167122694 for <calsify@ietf.org>; Fri, 15 Feb 2019 03:20:07 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Fri, 15 Feb 2019 03:20:07 -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=fm1; bh=YwJF7jNA6cP6c7s1g+RI6um2jy6/ YirdIfH7KYZdCno=; b=fTPoN0mWFBkO2RZsonm71k5NXc1iZb/0HQMILRJMXtpV Oe7Aq83OCJ4hgXMPQxODiRPlKzliqrUgOw6jZzi8vACwYIEGBk1YeGHpmYSA0bXY E4yhpB9paVTSR9NACqTZtUR1OMbqbM3HlZEM3wLCpLCqjCwidk+FxJ3eJj3VaLgP xe7NduWkvtdstkTBbS6zJWMY9IbGDBgmoNyJb1am8L/D069hJiBWco4NPLh/LaJY f+vFVf6F+5TZaI+hRgcC2HwCQW7e5Bv7eye6CFw7Bv0E8LgmVznRUmVvHEcE3eSe 1WobxWZYtN9fv3SKHPiq4NHbZDDiOXnDkGpSX66FVw==
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=YwJF7jNA6cP6c7s1g +RI6um2jy6/YirdIfH7KYZdCno=; b=cV+vkEycXk4uWiDfyza8NsyDQizjmWsLs T427G3HJLuWo0CRgLQzk3T3A2k5sl+NdDeYc83II+3OF8YhHonjiPllLnaLs9U/y vpxM1p/Q6ksCQP/itrLJW5EosVdzXpIHG+bh2RiB7Iaw0o1Q0krQiQ0xfBgmHILR d0przzMeKzl9cBhKY9GzucV0P+r6DF36CeA2QoIu1Jd5e4HwA1Xv6KNL5zXDX3Ig s05D3FAF+kW9VV7UG+I16nL4kuEk3mjTMzjaeFJw+LVvexf665bynIQpvc+3Sqmu 2EDmXLRaBh/lzQ6bTmNKJ7Yc5ZCQNbjQF5M/RHwoP4zrRHmL2FXBQ==
X-ME-Sender: <xms:N3ZmXI9ElB70EcovEJ8XM3TAcn062OPulRIHYO4NFLXVVzakAVTNDQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledruddtiedgudduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucenucfjughrpefofgfkjghffffhvffutgesrgdtreerreertdenucfhrhhomh epfdftohgsvghrthcuufhtvghprghnvghkfdcuoehrshhtohesfhgrshhtmhgrihhlthgv rghmrdgtohhmqeenucfrrghrrghmpehmrghilhhfrhhomheprhhsthhosehfrghsthhmrg hilhhtvggrmhdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:N3ZmXI18jJsviHOAlrxrTmilLZeJ7-WeC278-_ThtVj2cfx5r2z7XA> <xmx:N3ZmXNjDTFQLXlg_ui4rT50Qkt9OWg-z5Nv0Lqkem-OEzBIxIRvoJA> <xmx:N3ZmXIbxLQofZ22REbvzrDIlRL_y9c4r2SNZpzHcThAWsh5X6wypsw> <xmx:N3ZmXPFf7laEHrKus2y1fut3L4CtU_CPcDuAs3W7g1Glnq5oapLxgg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 34C7620250; Fri, 15 Feb 2019 03:20:07 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-832-gba113d7-fmstable-20190201v1
X-Me-Personality: 91525120
Message-Id: <392569fa-f464-4e8a-9c7a-f2e3401c30af@www.fastmail.com>
In-Reply-To: <029301d4c4fd$5eaca610$1c05f230$@caldavsynchronizer.org>
References: <1550160126.3602072.1658018976.28709BD3@webmail.messagingengine.com> <aec2692f-a2dc-4004-b1e4-4e3d3680aa9b@beta.fastmail.com> <029301d4c4fd$5eaca610$1c05f230$@caldavsynchronizer.org>
Date: Fri, 15 Feb 2019 03:20:06 -0500
From: Robert Stepanek <rsto@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="eeac7526c13f4afe9b9cd6d50f3e7b5e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/EcQHPnwCvgPz9A1Byn6lIDb91fg>
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: Fri, 15 Feb 2019 08:20:11 -0000

On Fri, Feb 15, 2019, at 8:09 AM, Alexander Nimmervoll wrote:
> So why do you stick to due instead of start+duration for JSTasks?



There is no duration for tasks, the time properties of JSEvent and JSTask differ (see section 5 in the spec).

For events, a start is mandatory, optionally defining a duration.

For tasks, all time properties are optional. It can be defined to start at a certain time, be due at a certain time and have an estimated duration, but none of these are mandatory. We got asked to allow estimatedDuration and the time span between start and due to not match, which can be useful to highlight resource issues in project planning. Admittly, implementations still need to handle due-before-start issues for JSTask.

> For the airline example with start and end time and fixed scheduled duration an idea would also be to use the estimatedDuration property for the scheduled flight-time or something similar.



The estimatedDuration property is not defined for events.

Cheers,
Robert

v2.23.0 | Report a Bug | By Email