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

Michael Douglass <mikeadouglass@gmail.com> Tue, 18 June 2019 19:26 UTC

Return-Path: <mikeadouglass@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 E7B60120404 for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 12:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 1F-H1TmD4p8o for <calsify@ietfa.amsl.com>; Tue, 18 Jun 2019 12:26:09 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 8767812031D for <calsify@ietf.org>; Tue, 18 Jun 2019 12:26:09 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id c70so9331403qkg.7 for <calsify@ietf.org>; Tue, 18 Jun 2019 12:26:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=jcEDwgtVwujerwj6hEbVHM5m8yLy2+o9E40ObLy3SRc=; b=imr6X9JQOxoy9Hnyu3+ex6ukxWQNn3XVsFY1JPv6T2MM35gbJ0B1Lniz7yzcP9FcFa hs/FMp9iWTBOfED/Ik5jbsDIpniX4hOriVTiTcR7EnZ++4x6l8HaXOEHKaQuKxTuXcnS EPCOq4xSa9kCNsDpR29Q0EDbnnEIDfuvtSh5+4fJTqdGmsPQ+GcAX1Af/qv8DajLUdJf bCrwyues0o7CJIdJYq581BFRaPRUL95Y+LQJVPiYS1XnFIrnYeFEz9rXBxnfOUzppRjw h+mt+FhyR6ZC3a/rctTVSfja5tKElhNr0ymaAO3RaPzhqR0X1DXY0vy3693VLIzvmR+S vd7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=jcEDwgtVwujerwj6hEbVHM5m8yLy2+o9E40ObLy3SRc=; b=tRzmAw+aZQVtavcm0I9zKcPrmQnVl51lG9PRgbmCDOuuGeFdDbSssOT+uhQF97Hyxz MaGD6IRn4jzcxKEtELmPF5YYdJ7TToSH6g/d8du4m9kuqgcBQLTubzim7rkDo48A6zvO inMcS/5H4wNTPFaz2luWAuuLQwK7HdQdwYdbv8zSv1izds4va4yTS4L0BAj0K3oDvQRC ezPacc/uBnEetkTtz7h6Wd51I5UlalEkaiV4Q1UdkahyfvrK98v+uEBdgowlQqI62yBs kFkrlvu/VMkBLSJyoDMBVcYq7KdbsZ5MJD/tQuebw/zJnXRCrYWycA7RlhYnPhM3ShL2 z9CQ==
X-Gm-Message-State: APjAAAXyNkjMiTrfu2GIJRlefzopJknhbmluOuR59D9w1HmdG+LoxR63 a4kaNeT3f9SVRIJS3QipnCOC1zra8a0=
X-Google-Smtp-Source: APXvYqwxW3TKA2BDZAmXOhBGrBfRkpCQqGUeydMRO26gyvtp488nWc3QuXMrnhyvs5XxV49kUQiwPQ==
X-Received: by 2002:a37:9e93:: with SMTP id h141mr74921025qke.142.1560885968348; Tue, 18 Jun 2019 12:26:08 -0700 (PDT)
Received: from Michaels-MacBook-Pro.local (cpe-74-70-80-66.nycap.res.rr.com. [74.70.80.66]) by smtp.googlemail.com with ESMTPSA id r39sm11675740qtc.87.2019.06.18.12.26.07 for <calsify@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jun 2019 12:26:07 -0700 (PDT)
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>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <8397aa6c-4924-a47e-66c4-98f4b459e70e@gmail.com>
Date: Tue, 18 Jun 2019 15:26:06 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <2da7e240-326b-23fb-3a29-190d4b65f31f@gmail.com>
Content-Type: multipart/alternative; boundary="------------0D8CD6B1248D5F7597BCD027"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/6N5VW4vrwXDk0UUsTFXNWsDxDUQ>
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 19:26:12 -0000

Putting aside the  exact representation for the moment there is a need - 
expressed by calendar users - to represent what they mean by "all day".

For birthdays etc the current date-only is probably fine (though 
possibly being able to flag these as anniversary events might be useful).

However, for public and social events things are different. These are 
generally known as 'all day' - the start and end may be ill-defined if 
at all. They also often take place in a specific timezone.

For years creators of ics files have been trying to put timezones on 
dates. I tell them they can't - they say why? The only answer is that 
the standard says so. They want to flag an all day event as taking place 
in a certain timezone. Setting the start and end to midnight doesn't 
have the same meaning - that is a 24hour event.

The uis for public calendars need to know the difference between a true 
24hour event and an all-day event in a certain timezone - we display 
them differently.

So I think the first issue is to decide whether our users are simply 
being unreasonable or if they have a genuine unfulfilled need.

If you want an analogy - we can either see where people walk and then 
lay down the paths or we can lay the paths and forever repair the grass.


On 6/18/19 13:50, Doug Royer wrote:
> On 6/17/19 6:39 PM, Bron Gondwana wrote:
>> On Tue, Jun 18, 2019, at 09:25, Doug Royer wrote:
>>>   "Indicates whether this event is meant to represent an all-day event,
>>>     and SHOULD be presented accordingly in a calendaring application.
>>>     The value of this property is independent of the actual time-span
>>>     covered by this event."
>>>
>>>
>>> So, an isAllDay could as an example, be 36 or more hours long?
>>
>> It certainly could.  This is already very possible with iCalendar, 
>> e.g. this event here:
>>
> (example not included)
>>
>> Which is an "all day event" with a duration of 5 days.
>
> So, with, or without 'isAllDay' they mean EXACTLY the same thing. What 
> is the point of 'isAllDay' when with or without it, it means the same 
> thing?
>
> If I am incorrect, what does it mean?
>
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify