Re: [calsify] JSCalendar: fractional seconds

Marten Gajda <marten@dmfs.org> Thu, 06 June 2019 12:04 UTC

Return-Path: <marten@dmfs.org>
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 B0929120139 for <calsify@ietfa.amsl.com>; Thu, 6 Jun 2019 05:04:05 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dmfs.org
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 vG0qbXWiHAkb for <calsify@ietfa.amsl.com>; Thu, 6 Jun 2019 05:04:03 -0700 (PDT)
Received: from mailrelay1-1.pub.mailoutpod1-cph3.one.com (mailrelay1-1.pub.mailoutpod1-cph3.one.com [46.30.210.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E00B112004F for <calsify@ietf.org>; Thu, 6 Jun 2019 05:04:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dmfs.org; s=20140924; h=content-type:in-reply-to:mime-version:date:message-id:from:references:to: subject:from; bh=fD6qjzHAQcGZQjAFMAyscgSNkRtXNWu3EqaUNmdsTyM=; b=zF2IR7TTmD4X1xXCSKoy1BCfmnIaWvOJ1FWUnfUKMqpfRB1sdCCbgRpPrhLOLdvEL7uZjhd2vmLDS +a5KEj7unGhJ0jXCVh80I8HvelmYKMU7Os+1z7Qmu0e7eR6QAxBo5aGGTqQ7WLvLkuv39sf/lXnjLH ODfgp8YcjVHyOerg=
X-HalOne-Cookie: cf1ff79195288d95dc785159c412c672a43a6148
X-HalOne-ID: 2a9bd84b-8853-11e9-bc2a-d0431ea8a283
Received: from smtp.dmfs.org (unknown [2003:5f:6e16:2f00:201:2eff:fe40:2624]) by mailrelay1.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id 2a9bd84b-8853-11e9-bc2a-d0431ea8a283; Thu, 06 Jun 2019 12:03:59 +0000 (UTC)
Received: from boss.localdomain (unknown [5.148.88.162]) by smtp.dmfs.org (Postfix) with ESMTPSA id C783A589 for <calsify@ietf.org>; Thu, 6 Jun 2019 14:03:58 +0200 (CEST)
To: calsify@ietf.org
References: <b8c456ff-d350-456f-a662-d212620704ea@www.fastmail.com>
From: Marten Gajda <marten@dmfs.org>
Message-ID: <eb8ecdbc-a57b-83ec-0448-5de985e32d2a@dmfs.org>
Date: Thu, 06 Jun 2019 14:03:56 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <b8c456ff-d350-456f-a662-d212620704ea@www.fastmail.com>
Content-Type: multipart/alternative; boundary="------------355FD07BC6B85EB6507C1135"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/H90ADZigVoQ91ir4IfOl0e1ilJc>
Subject: Re: [calsify] JSCalendar: fractional seconds
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: Thu, 06 Jun 2019 12:04:06 -0000

Is this parameter is meant to preserve the fractional seconds for
round-trips or are iCalendar clients encouraged to use the value?

I mean, would a client that's aware of X-FRACSEC have to match
RECURRENCE-IDs ,RDATES and EXDATES taking the fractional seconds into
account?

I think we should advise against that and make clear that this is not
meant to increase the precision of times in iCalendar, but merely to
preserve it.

Btw, how do we cope with unaware clients doing partial updates? I.e. a
client which is not aware of X-FRACSEC adds a new recurrence-override
(not adding X-FRACSEC to RECURRENCE-ID). When being converted back to
JSCalendar, this would result in an additional instance instead of an
override.

Marten

Am 06.06.19 um 13:49 schrieb Robert Stepanek:
> It just occurred to me that the current JSCalendar RFC draft
> ambiguously defines if fractional seconds are allowed in the LocalDate
> time type.
>
> To be clear: we intend to allow fractional seconds in the start
> property (and any other LocalDate property). The next version of the
> RFC draft will define this more clearly.
>
> Unfortunately, fractional second date-times and durations can not be
> round-tripped out of the box with iCalendar. We will define an
> iCalendar extension parameter in the informational guide for mapping
> iCalendar and JSCalendar (draft-ietf-calext-jscalendar-icalendar):
>
>   * X-FRACSEC of value type INTEGER
>   * This parameter MAY be set on iCalendar properties of type
>     DATE-TIME or DURATION. It MUST NOT be set more than once per property.
>   * The value of this parameter defines the fractional seconds of the
>     DATE-TIME or DURATION type.
>   * This will allow iCalendar implementations  not being aware of this
>     extension parameter to display the time value "good enough" with
>     second precision.
>
>
> Please let me know if you prefer another approach.
>
> Cheers,
> Robert
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

-- 
Marten Gajda
CEO

dmfs GmbH
Schandauer Straße 34
01309 Dresden
GERMANY

phone: +49 177 4427167
email: marten@dmfs.org

Managing Director: Marten Gajda
Registered address: Dresden
Registered No.: AG Dresden HRB 34881
VAT Reg. No.: DE303248743