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

"Robert Stepanek" <rsto@fastmailteam.com> Tue, 18 June 2019 11:55 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 C7DD612015A for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 04:55:38 -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=fnDMzc7l; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=OjoJw45u
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 FqU3JBHItbGv for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 04:55:36 -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 C82AF120075 for <calsify@ietf.org>; Tue, 18 Jun 2019 04:55:35 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B73C82239F for <calsify@ietf.org>; Tue, 18 Jun 2019 07:55:34 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Tue, 18 Jun 2019 07:55:34 -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=O7vfiLc DKHaTXAyRLNS+Xd0UfF4dKnIXmMtOu4YndRQ=; b=fnDMzc7lxsVhf1FV5LCc/0G ogO1w2s/l4ZAbT9lySfqcYte7rEzK7gIsbJYzTacU+6CnvwHEWXmB14Ui5YI6PlK 1kx7JZGG/CRBtvvlARVlkGcTw3nSkeCdouo4ULWDOtU+V2+N4pXNbCk3UNjP6FlN pO329j89lRUOqtshqjBaurfSVWomgwD07xAmHzpHK+InmFbI3njHwFLxa/oyXPyY bPsfv6oI941YSWt+IE0053W+/m/L3cFOGVx5NgWHHQfBW/nlRySHqfu6bcW9CBhr 7S37N2qeTC5+msVROo60j46kn7qzhHlAHT7A8ydCoQ3x+Qq4MKJDOkpZotDsfvA= =
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=O7vfiL cDKHaTXAyRLNS+Xd0UfF4dKnIXmMtOu4YndRQ=; b=OjoJw45uF+JaIYc5bU8GGP KOtKu022JmGuI62EAj5FYb8EVq11de6Zb85MEUxMx/2308Ii5Y1CjmnJC4Kt/yqG sm8dxk5LsGCgBYL3zod0llsks2JL6yg4QFHKebqV1WkrDklj/HNjuFDa6s1sx003 O6ZWxcTZLJBtvRM9q0XHcyH8VUD7XmaK/EsLtLs28xDz2wgYMlAkTaTvnJXJlVFK +rzDZs46qw2Nz0JZnUD/ykVhpnXydetV1jOw8yYE8YtvLxXncTtW3RfmuZ/cn1/F jztfAJH4iEh+7/HMneQ3ZRvrMUbR3GsQdcFcJZTNsTvMG7W2pXBT8WnLLwfHmybQ ==
X-ME-Sender: <xms:NtEIXYtNzkW7t54RgL3k3rRnoSzLFPsRgg3CQL7JR03nW_WoSNjZnw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrtddtgddugecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdftohgsvghrthcuufhtvghprghnvghkfdcuoehrshhtohes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucfrrghrrghmpehmrghilhhfrhhomheprh hsthhosehfrghsthhmrghilhhtvggrmhdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:NtEIXbwuD6yyZf2UGPFCFS1gAmTbAtqjOewZur566LA1rEi9pSWjDg> <xmx:NtEIXZxDUPVZvD4SspjOu4q5UMHjmtt0b2mDkxTZAXML7UBrnHr8qg> <xmx:NtEIXYiSt4oO97Gf4sMjgwUNfk2eK9pvaQB4pXN3U8k-ecycfRStqQ> <xmx:NtEIXT7e--940NvusatKcJuHPOFDO5iqj2exgeEqxM0fssaroUsn6g>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 46EF0180776; Tue, 18 Jun 2019 07:55:34 -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: <12b5d7b2-5d97-4bcb-b918-31833b557fef@www.fastmail.com>
In-Reply-To: <fea05db4-850a-4f66-a526-b2b7cbe5dc82@beta.fastmail.com>
References: <7ec4462f-9e69-409e-9925-6f0beae7424c@www.fastmail.com> <fea05db4-850a-4f66-a526-b2b7cbe5dc82@beta.fastmail.com>
Date: Tue, 18 Jun 2019 13:55:33 +0200
From: Robert Stepanek <rsto@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="eeea7e65e41349ddb5aeb3d08474a1d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/LR4-drj4Z3e9KlBMZ_pdtgxwPIo>
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 11:55:39 -0000

On Tue, Jun 18, 2019, at 5:16 AM, Neil Jenkins wrote:
> 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 also wouldn't set a timezone on my birthday, but there's been a number of people at last CalConnect reporting that this actually is what users do. I don't have a good answer how to render that if the event timezone and UI timezone don't match - probably a calendaring UI should just ignore the "isAllDay" property if the timezones of the UI and event don't match.

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

That's fine for me as well. I chose "isAllDay" rather than "showAsAllDay", because I figured that "show" implies a graphical user interface, which might not be adequate in all cases (think: calendar applications for visual impaired). But I'm not too vested in it.

> I also agree we want this for JSTask. 

Yeah, there's several people now asking for it, so I guess I shouldn't have removed it in the first place. But it's great we got that established :)