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

Doug Royer <douglasroyer@gmail.com> Wed, 19 June 2019 05:23 UTC

Return-Path: <douglasroyer@gmail.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 8421612031D for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 22:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=gmail.com
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 nZfASS_-27Xr for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 22:23:37 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16B7912004F for <calsify@ietf.org>; Tue, 18 Jun 2019 22:23:37 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id w25so35233233ioc.8 for <calsify@ietf.org>; Tue, 18 Jun 2019 22:23:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=bpUQUhUe6SJqz2QpPoZ1yJJvqDmn3QbFQLN2s6Qx2ys=; b=rdTnMbTgrzOj24rZQVkvFlIPZmV8l+779RyW5pn1B4iACfawwR1cP9erQxR3CKTFbC pnCFUkVntW9MzglxDk0OxeU83bVXRAY5WLFE94qu7/RRVX200U2VLSnDHcGxpuvfRVIP 6R8bHaFtro0reoOfnyJm6gvjI5ck7admFDfKzWW9htNkpckEWGWecSTcEzJbKqS1RWFg bfDuJcmNiaVOJCSltdDvLV8PZ6tlcmGMYGgpII9zHaL2Vl+IXY2zcBr3H/e35Na1BFB3 VrLsUD253nkDlFfeX/klX/xdNAoOGOD72Vjh0QWvpbtPA0rIQs2h5KBmLafP3UNl39nc lH3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=bpUQUhUe6SJqz2QpPoZ1yJJvqDmn3QbFQLN2s6Qx2ys=; b=MJuDn0y1KwmUJtxxvvM6PAt8Fu0aeFcFJTS+XbvlbwmHRI6WC5PlXQ+vz96Gcz34J0 JGzT0i/BEfErckK8j9jJjMCAI0zhoyX1MpXjDXmJ8NyUDx5+i0+4q5Lvd8kZv34uxEDp SKhro52hayjXCd4ycl14ySnCHHKK4Th/jG4esD3fSxNZgYs1volI6ERgNDFzVCBqljz5 ZIKIl0Pu5hpfyjS6VhvIjzjNIJAhfu4Ix5ANr/jNy+sYMCKSorarARRJXvNqoVKc1j7B hR5s4rGEVeV2fYK3mTitW7Ac9FVeVh2teiEGBSUqMP199JAtb04L4ZhQLLvYrrJwAbRW Wk2Q==
X-Gm-Message-State: APjAAAW/UoqczWSK7incHm+v0Ft2LppdcUprRN2mYiqIRW0YVEqE1Jh3 awC8XpYRpISsRISq2Pv2IJyyxzu/NcRe
X-Google-Smtp-Source: APXvYqzFNIOMjQt32DYKo0opd81yziDydvvdYKUgnYNeGgpXTwoZrlPj2ZuYaIu1YeM9E3UK6cTvCA==
X-Received: by 2002:a5e:c803:: with SMTP id y3mr7645832iol.308.1560921816025; Tue, 18 Jun 2019 22:23:36 -0700 (PDT)
Received: from [192.168.1.7] ([174.27.172.40]) by smtp.googlemail.com with ESMTPSA id a8sm14724460ioh.29.2019.06.18.22.23.34 for <calsify@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jun 2019 22:23:34 -0700 (PDT)
From: Doug Royer <douglasroyer@gmail.com>
X-Google-Original-From: Doug Royer <DouglasRoyer@gmail.com>
To: calsify@ietf.org
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> <148d9346-06fc-45c0-9c69-b486578b24ed@beta.fastmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <e7ce4f4d-b885-f3ff-227e-df251b87f161@gmail.com>
Date: Tue, 18 Jun 2019 23:23:33 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <148d9346-06fc-45c0-9c69-b486578b24ed@beta.fastmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms090400040308040104030002"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Ue86Cru-aFT7T06Mn6twiTYDhaI>
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 05:23:39 -0000

On 6/18/19 10:28 PM, Neil Jenkins wrote:

> 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.

Yes, my question was as defined in the spec. And the fact that its usage 
is not consistent. Some apps give 'all-day' events with a 1 hour 
duration (or maybe it is the default event duration set by the user 
settings). Some have no DTEND (anniversary).

> 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.

I can not find an RFC that defines 'all day' events. Just anniversaries 
which some use to mean 'all day'.

> 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).

I still do not understand the concept of 'all-day' that is not really 
'all-day'. Do people really mean anniversary or day (daily) reminder?

When I check 'all day' on my google calendar, it removes DTEND, which 
makes it an anniversary type event. Then shows it consumes exactly 
24-hours when I get a summary of events. On the calendar itself, it 
shows zero duration. The google android calendar app seem to do the same 
thing.

Thunderbird keeps DTEND making it equal to DTSTART and takes away the 
TIME value from DTSTART and DTEND (making it VALUE=DATE - WITH a time 
zone). And views as a 0 seconds duration event on the user interface. 
 
 
 


So, looking at what I have, there is no consistent meaning for all-day.
-- 

Doug Royer - (http://DougRoyer.US)
Douglas.Royer@gmail.com
714-989-6135