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

"Neil Jenkins" <neilj@fastmailteam.com> Tue, 18 June 2019 03:16 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 4CC1E120116 for <calsify@ietfa.amsl.com>; Mon, 17 Jun 2019 20:16:04 -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=f+EbO7Gg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=luqSQ1Z/
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 CacwnYVicfOc for <calsify@ietfa.amsl.com>; Mon, 17 Jun 2019 20:16:02 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1387612003F for <calsify@ietf.org>; Mon, 17 Jun 2019 20:16:02 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E366C22136 for <calsify@ietf.org>; Mon, 17 Jun 2019 23:16:00 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Mon, 17 Jun 2019 23:16:00 -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=xOJ2bh6 5kifxbc7A3aW3FRJjG3RFDBalqeOK3S0Pwq4=; b=f+EbO7GgviWgiQC968qhPxF 4lW8qSvQ9GK4VkK5VbKYiMbJDMQFpKkMI0drpUi8StsUTUOmTCPvV71sZB26UGrK gkDKYy5ze7R3iPQPUJpxdoRD8BfPsj3i8RBIL1tmzje8koDhzLrw2BCGTVC5UNCP TpbZVxR/wFm7UV8UscgQOe6J/zoqmcWFhxldU9p1G7LlXji/nVsilzYmT89B1Whc 4ktBZBeutRbe6fs2TLrUQkEbQXdhfyyo1yyicjoi1/FoDb+1YHFZcxsCQiD48foK VGVyOVd77eC86UKMMi0BBFvk2mkyPpU5WHeoQBbkv1H9CxckKEcA80ahGVPQKGQ= =
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=xOJ2bh 65kifxbc7A3aW3FRJjG3RFDBalqeOK3S0Pwq4=; b=luqSQ1Z/U6mxjOspQXftsf Pa/cgXxkLzDpCyahOq6vad45y48z5ZA6K+rAJEDKRm0HLBATTijwfQsLr/+8YlGU KkviMp3WL06zCXbIQIOP1KjSe/nZ9z3rTaazAvNMfgrVdmOTZc6u5ktyRS3NGN/p ZmcylxtV2Gy/7uyjHxr4CXqoWO49UuHir5kI5cfyzKQ1InHnLtEaM4zgV8yJcnae 1QwvETKUNzmvbcHQiJDSKJ+CY3ZCZb/cCd+AuF/b7Ns7YYyTSVt3QaXHlXNpfR8Q N60edhgf/JZhNruRKouJFCxzm2TsgxcWWg4ld61vcVodnD/XM0jvVGkVHsVFMJyQ ==
X-ME-Sender: <xms:cFcIXQ8dnjsz7qaPrQrv2F-f7Owpkgv9RROXA06gjKLt_kQxzLzK8w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeikedgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfpfgvihhlucflvghnkhhinhhsfdcuoehnvghilhhjsehf rghsthhmrghilhhtvggrmhdrtghomheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvg hilhhjsehfrghsthhmrghilhhtvggrmhdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:cFcIXQddDCUeJCSRMyWmwcWfrVMnfXDeqT94mkAf6uw9lwW4Dyb7IQ> <xmx:cFcIXZFhrSBx8_Bhp4uFnFSEywvWPajRXVl7pq13v56QTIN2v-OeiQ> <xmx:cFcIXedRuGk5J9YxT8EQm7OVQBtXfCaxaq1bXaxYpWwktZXuuXAbfw> <xmx:cFcIXf-ZAP6lbX68bFT6BZRJLoKwy6EsA8hZTXvoL7N8o7w_MRuzCw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3B424180725; Mon, 17 Jun 2019 23:16:00 -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: <fea05db4-850a-4f66-a526-b2b7cbe5dc82@beta.fastmail.com>
In-Reply-To: <7ec4462f-9e69-409e-9925-6f0beae7424c@www.fastmail.com>
References: <7ec4462f-9e69-409e-9925-6f0beae7424c@www.fastmail.com>
Date: Tue, 18 Jun 2019 13:15:59 +1000
From: Neil Jenkins <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="1dddc7c784eb4586ba640aa950a3e02a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/JHoSxx6L1zT-2dcjoCJxkOCeZnw>
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: Tue, 18 Jun 2019 03:16:04 -0000

On Fri, 7 Jun 2019, at 01:56, Robert Stepanek wrote:
> Calendar users want to set their calendar on their birthday, when they only would like to set it for the complete day in their usual time zone. They still want it to show up as an all-day event in their UI.

Suppose I have such an event (24h long, starts at midnight on 1st Jan 2020 in Australia/Melbourne). It is unclear to me what I should show the user if their time zone is different (e.g. I view the calendar in Europe/London); does it show up in the "all day" section on both 31st Dec and 1st Jan? That's the only sensible thing I can come up with. But that would give the impression the event happens over two days, which is incorrect. (But perhaps the issue here is really more that the birthday should not have been given a time zone.)

I agree the name could perhaps be better. `showWithoutTime` perhaps? And a description something like:

*Indicates the time is not important to display to the user when rendering this event, for example an event that conceptually occurs all day or across multiple days, such as "New Year's Day" or "Italy Vacation". While the time component is important for free-busy calculations and checking for scheduling clashes, calendars may choose to omit displaying it and/or display the event separately to other events to enhance the user's view of their schedule.*

I also agree we want this for JSTask. For example you might set a *due* of `2019-06-30T23:59:59` , i.e. the task deadline is by the end of 30 June. Most UIs would probably just want to show *Due: 30 June*, but it would make sense to have this explicitly stated on the JSTask object so you could signal when the time truly was important.

Neil.