Re: [calsify] JSCalendar: alternative to current all-day events

"Neil Jenkins" <neilj@fastmailteam.com> Wed, 19 June 2019 04:28 UTC

Return-Path: <neilj@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 F16851201E4 for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 21:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=PpgNHjSL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=wiC1p4uP
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 YIywKUDcIWXV for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 21:28:27 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89A2912018D for <calsify@ietf.org>; Tue, 18 Jun 2019 21:28:27 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BA6CA2238F for <calsify@ietf.org>; Wed, 19 Jun 2019 00:28:26 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Wed, 19 Jun 2019 00:28:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=LAiyutk ZWXahb0RVaGovaVbvl/oJ27BBnpCIQ0bMcPo=; b=PpgNHjSLhG8FyD1uSQKyD/q mKqb3HZINmVpX9nHVTw3vsUAHM29F/2TiulCvV8A0E0HRbiipRE6D1l6t24oW6nI SgqtH1TfsnPGA2EZPG/RdvjL81ObVweZWyNr/Ia21Rw1y8Lt9CUqpABp5bKoXLJh oajG8EMEGK+XiRAg9pYKH98AdSeJLA/NSROsef0rZS1i8wdmQfBYrWS4fiqqJ3NS CzrGOflOKl/MxrFFNZgd02aoclm5ZNlwygbZ8lsb9TnZHdqgXl+maggvAfMi6Jna iDeJ0+SL4i/iRFtu1L1pLkjqK4XHb+H3spx9YYlGUq7fBkCz1/LCq39grASLNCg= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=LAiyut kZWXahb0RVaGovaVbvl/oJ27BBnpCIQ0bMcPo=; b=wiC1p4uPhbviGLe5MlbWf9 2XmPlbLLOJ21fIGLicIpsPsQmoIgFacBxXfoEr7vPksuDIBFFRAdEy3m5URX1lWW xNcbd6vAOHO3WjoPiQljdfGxyepVbJ7AAinRt2RtTitRn05Apt/jkWiSNcaqK7kt afqsH6WR+ki6GGJCpd3i3uttUeSXdHjGH30/mqe85OiaJniJi43QxC5RDzwRScL/ ITRxAzO1osymwTwonvCPTOhggUq6xj36aY7X1pLmR0Cvn79vkZyHm0SerB4pUsXu jIarStRaCaMITPMVOPKS9gzqdOhNfuDAu0K6QzSK1o7ZUF9gpJYBM+2jSrg7QAXA ==
X-ME-Sender: <xms:6bkJXXUQknECauWtoAPkwvdtJNc5mdxHPwWq18xQTshTVcbW-3jS1Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrtddugdekfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdfpvghilhculfgvnhhkihhnshdfuceonhgvihhljhesfhgr shhtmhgrihhlthgvrghmrdgtohhmqeenucfrrghrrghmpehmrghilhhfrhhomhepnhgvih hljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:6bkJXb4MgfngbDvu4FjQ_0fK-2V1uOkZztbiY3vWfkrSviW6Cz9YIA> <xmx:6bkJXWIqjL-aHocaGKf_T7sqt5Y19KHIuQAcOgEqyyqxkb-yrJP4AQ> <xmx:6bkJXUK3rWO0xgZy18Oi3UAlDfsOBqh8kJEXpajYjiULYwJa8BUoRA> <xmx:6rkJXQC4Y7RCprdAUAXJotIdctSxQYJy5xzBupv8FNmUbOQoAmU47w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id AFFB618073C; Wed, 19 Jun 2019 00:28:25 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-666-gb2312fa-fmstable-20190614v4
Mime-Version: 1.0
Message-Id: <148d9346-06fc-45c0-9c69-b486578b24ed@beta.fastmail.com>
In-Reply-To: <e75bcfba-8a79-1a88-4380-c5e13053013e@gmail.com>
References: <7ec4462f-9e69-409e-9925-6f0beae7424c@www.fastmail.com> <e7b2189a-1967-2266-11e1-9e994fbe12c1@gmail.com> <69247523-c59b-49b2-9304-3f460cdbbc24@beta.fastmail.com> <2da7e240-326b-23fb-3a29-190d4b65f31f@gmail.com> <8397aa6c-4924-a47e-66c4-98f4b459e70e@gmail.com> <e75bcfba-8a79-1a88-4380-c5e13053013e@gmail.com>
Date: Wed, 19 Jun 2019 14:28:25 +1000
From: Neil Jenkins <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="c029def5653a4bdea6581a9dcec70356"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/YjCXkDK3WfL3cYOxBBi5lUTHm0s>
Subject: Re: [calsify] JSCalendar: alternative to current all-day events
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, 19 Jun 2019 04:28:30 -0000

On Wed, 19 Jun 2019, at 07:13, Doug Royer wrote:
> Great - It needs to be documented in the spec.

Yes, I have suggested text in a previous email in this thread.

> Exactly how will they be displayed differently?

I suggest try using a common CUA such as Outlook, Google Calendar, Apple Calendar. These all have an option to mark an event as "all day" (this is literally the term normally used in the interface), which causes the client to display it separate to timed events in the spatial view (e.g. Day, Week view) of the calendar.

When storing in iCalendar format, clients distinguish these events by using the DATE format rather than the DATETIME format. In JSCalendar we are using an explicit boolean property instead, which we believe is better aligned with developers' mental model and is easier to implement.

This particular thread is discussing loosening some current restrictions, designed to ensure a 1:1 mapping to iCalendar, to allow more representation of data not currently possible in iCalendar (which some developers have expressed a wish for in their applications).

Neil.