IETF Logo Mail Archive

Re: [Jmap] [JMAP] CalendarEvent/parse proposition for the JMAP Calendar draft

René CORDIER <rcordier@linagora.com> Mon, 17 April 2023 03:37 UTC

Return-Path: <rcordier@linagora.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBF13C14F693 for <jmap@ietfa.amsl.com>; Sun, 16 Apr 2023 20:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.692
X-Spam-Level:
X-Spam-Status: No, score=-1.692 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=linagora.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d_cbCVNTVoJa for <jmap@ietfa.amsl.com>; Sun, 16 Apr 2023 20:37:07 -0700 (PDT)
Received: from smtp.linagora.com (smtp.linagora.com [54.36.8.78]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B60DDC14F738 for <jmap@ietf.org>; Sun, 16 Apr 2023 20:37:06 -0700 (PDT)
Received: from ?Open?PaaS?SMTP?server?for?Linagora? (unknown [51.83.109.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.linagora.com (Postfix) with ESMTPSA id 085863EE1D for <jmap@ietf.org>; Mon, 17 Apr 2023 05:37:05 +0200 (CEST)
DKIM-Signature: a=rsa-sha256; b=cKLbSJWS9mWs/vOMDxk+6c/lg9uYgiUBB3WZzLzFJe49IWOZpZ3wIKm9qUqia7EO7QyQ1gfJk2rzfshtkJ1AAP8r7ZQiqaDSO9wZNgtJv51kzlJeP44SS6/PFwqNPPXKE8J9d3myNZQ1fSl/MLTcFJ+9xmI41cvYGwo9aOSOAxugEuEuOOIu+vvxB4NqfDxyejQtk0XepWcDeYkW2grothnfUTW9D4Z2tV75gi1REiZX5qk5ZqR1wUywQZheqi2PRKWHPGqp6AmEeqW+znfGb2YGYl0cgbmQzaJlLxG2RUaPGeg9Ilbi0KEzUpB8QhBThrOhXJ5XUH5WOsBygEqvvg==; s=smtpoutjames; d=linagora.com; v=1; bh=YGjWJTLJqLoTFDKBbOx0ElwkUYRi/GMZOeOzcSRQMMA=; h=from : reply-to : subject : date : to : cc : resent-date : resent-from : resent-sender : resent-to : resent-cc : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive;
MIME-Version: 1.0
X-LINAGORA-Copy-Delivery-Done: 1
From: René CORDIER <rcordier@linagora.com>
To: jmap@ietf.org
Reply-To: rcordier@linagora.com
Date: Mon, 17 Apr 2023 03:37:03 +0000
Message-ID: <Mime4j.1a4.2af06cba3a9ed28a.1878d49973e@linagora.com>
User-Agent: Team-Mail/0.7.6 Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
Content-Type: multipart/alternative; boundary="-=Part.1a5.2b8c439dc5fe70b6.1878d49973f.be0e6522a0f51322=-"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/RLMuQPh0VyLG9heJWhektqVJ1Wo>
Subject: Re: [Jmap] [JMAP] CalendarEvent/parse proposition for the JMAP Calendar draft
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2023 03:37:11 -0000

Hi Neil,

Thanks for the feedback! I will take it into account as well alongside Robert's comments and propose an updated version of this document when i have a bit of bandwidth. Then we can see how to integrate that to the Calendar draft :)

Cheers,

Rene.

On Apr 14, 2023 11:01 AM, from Neil Jenkins This is definitely a useful method. I think the result type should be pure JSCalendar rather than a JMAP CalendarEvent, because it's not saved in the store anywhere so doesn't have an id etc.

Regarding an iCalendar file with multiple events (with different UIDs), I'm happy with either returning an array of JSCalendar event objects or a single JSCalendar group object. I think I agree with Robert that the former is probably slightly better though, just because otherwise it's easy to only implement something that handles an event response and then get surprised when someone passes in a multi-event file, whereas if it's always an array you know you need to handle the possibility of multiple.

Cheers,
Neil.

_______________________________________________
Jmap mailing list
Jmap@ietf.org
https://www.ietf.org/mailman/listinfo/jmap

v2.23.0 | Report a Bug | By Email