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

René CORDIER <rcordier@linagora.com> Wed, 12 April 2023 07:26 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 7EABCC152A26 for <jmap@ietfa.amsl.com>; Wed, 12 Apr 2023 00:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.694
X-Spam-Level:
X-Spam-Status: No, score=-1.694 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 dXZumiKpYp7j for <jmap@ietfa.amsl.com>; Wed, 12 Apr 2023 00:26:22 -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 CAF81C1527AE for <jmap@ietf.org>; Wed, 12 Apr 2023 00:26:22 -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 82FFB3EE63 for <jmap@ietf.org>; Wed, 12 Apr 2023 09:26:20 +0200 (CEST)
DKIM-Signature: a=rsa-sha256; b=lyRjLHnZ/7RSg4O5yy2K07/qIvE4SDuzK+UlXmXhnvNZPdi8DkNiQLc1keXle7kThmGMqkueKSqsW7xlnDV04Mdn6W3K1n+wveQzYdazt91XCFRqO8QtMPmUtoXMXy1X/46DJrKV3yrDBUDaPej87OQcigyH2flk5Su8+2estocihkzIrO2Va+APvzaeuSWTp83rWRbtv2mvzkx/6vrQ2CQrV5DVV7f8skjdyraly9hm7Ncnc2qSFBgHeO1d35QYpGncprjvvho10KZddrMs6uLYHbdZMxBooN+YPPvnmOvXolSMlFwy4ggxVN952/U3BHF5VCOGImJSQsRGoHGn2g==; s=smtpoutjames; d=linagora.com; v=1; bh=/5SWxAlRwzjQtc2dif9ksV2Ik1L853dUm7jcgPL5uIA=; 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: Wed, 12 Apr 2023 07:26:18 +0000
Message-ID: <Mime4j.6.e7ae1c1fa90e3ca2.187745bb130@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.7.cc044f229e738fd6.187745bb130.ad88946ddfa6a325=-"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/etv-A3us6l0TDEEh5SmanfXFkX8>
Subject: [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: Wed, 12 Apr 2023 07:26:27 -0000

Hi guys,

At Linagora we have an internal need of showing what we call a blue bar on top of Calendar event emails that you receive. It would allow the client to show the user details of a Calendar event he received in a nice and generic way when reading the corresponding email (because Calendar email sent events are not formatted the same way depending of the calendar).

We came up with a custom method called CalendarEvent/parse. It would allow to parse a .ics calendar file attached to the mail to extract properties defined in RFC5545 to allow client to show events from different calendars in the same way. 

For more details, we have a document that defines our custom method here: https://github.com/linagora/tmail-backend/blob/master/docs/modules/ROOT/pages/tmail-backend/jmap-extensions/calendarEventParsing.adoc

Regarding the implementation, we just finished to integrate it on our backend server, but not yet on the front.

We were just wondering if this would interest the JMAP IETF community group? As part more precisely of the Jmap Calendar draft (https://datatracker.ietf.org/doc/draft-ietf-jmap-calendars/), or as an extension, or ...? Just let us know if you think it could be an interesting method to add, and we would be happy to help contributing it ! (of course with the necessary changes to fit the stye of a RFC).

Don't hesitate if you have any feedback or questions, and thank you for your attention.

Cheers,

Rene.