Re: [Jmap] [calsify] New JSCalendar I-Ds and missing iCalendar conversion
Joris Baum <joris@audriga.com> Thu, 14 December 2023 07:18 UTC
Return-Path: <joris@audriga.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 39687C14CE24; Wed, 13 Dec 2023 23:18:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 nSZ_6_k6dmoT; Wed, 13 Dec 2023 23:18:30 -0800 (PST)
Received: from mail.audriga.com (mail.audriga.com [176.221.42.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70883C14CEFF; Wed, 13 Dec 2023 23:18:30 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.audriga.com (Postfix) with ESMTP id 015B7A0B7; Thu, 14 Dec 2023 08:18:28 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mail.audriga.com
Received: from mail.audriga.com ([127.0.0.1]) by localhost (mail.audriga.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qC7yZNehZhLI; Thu, 14 Dec 2023 08:18:25 +0100 (CET)
Received: from [192.168.0.103] (dslb-092-072-095-028.092.072.pools.vodafone-ip.de [92.72.95.28]) (Authenticated sender: joris@audriga.com) by mail.audriga.com (Postfix) with ESMTPSA id AA99EA066; Thu, 14 Dec 2023 08:18:25 +0100 (CET)
Content-Type: multipart/alternative; boundary="------------JWbUG3eKP4yXGfURadx1gieg"
Message-ID: <647f349f-0da7-47cd-8238-c4cfe34da7bf@audriga.com>
Date: Thu, 14 Dec 2023 08:18:25 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: calsify@ietf.org, IETF JMAP Mailing List <jmap@ietf.org>
References: <d9660927-f2c2-44dd-b1ad-bc513ae9faf6@app.fastmail.com> <0d5c0cb2-0e6e-4b0d-9fb6-86f256204a94@app.fastmail.com>
From: Joris Baum <joris@audriga.com>
Autocrypt: addr=joris@audriga.com; keydata= xjMEXmiiVxYJKwYBBAHaRw8BAQdAdZHr1ErnL1M6znXii/tmQdbrX2WYv7z2IOX24nQI/ILN HkpvcmlzIEJhdW0gPGpvcmlzQGF1ZHJpZ2EuY29tPsKWBBMWCAA+FiEEcn/m2ZrBrKtT4eWN /E+o0tJIXvAFAl5oolcCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQ/E+o 0tJIXvBxNwD9FTxAqK3hInm0FO8PkbKnoMs39U8uIsyWzZ6OQxNKAqoBAILUwL4+zZ27pJwr cpLaLrbGJ7jFH4gvaXD9pSsVrN4OzjgEXmiiVxIKKwYBBAGXVQEFAQEHQOwg+TuTO26r4K5V BzYwVGK9EXrx6UpBxiubgDlHdY0KAwEIB8J+BBgWCAAmFiEEcn/m2ZrBrKtT4eWN/E+o0tJI XvAFAl5oolcCGwwFCQlmAYAACgkQ/E+o0tJIXvC2HwD/VjK0qWcInLxsNA+4IpgsZeR6U3bO K0NUuXoxZLGiOG8BAJNp3V+nFFgguUohvpSzw7sI4h4QXKVuVMhpG43PHVsD
In-Reply-To: <0d5c0cb2-0e6e-4b0d-9fb6-86f256204a94@app.fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/zzdbZaFkRCzsuWqRykhu-mxVAcM>
Subject: Re: [Jmap] [calsify] New JSCalendar I-Ds and missing iCalendar conversion
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: Thu, 14 Dec 2023 07:18:35 -0000
Hi, from reading the forwarded discussion on the calext list I understand that JMAP Calendars shall be put on hold until a new JSCalendar extension document has been written? It would be good to get a confirmation for this on the jmap list by one of the JMAP Calendars spec authors. Regards, Joris On 12.12.23 17:10, Robert Stepanek wrote: > On Thu, Dec 7, 2023, at 2:56 PM, Robert Stepanek wrote: >> Are we going to require draft-ietf-calext-jscalendar-icalendar be >> published together with any new JSCalendar I-D, or are we fine adding >> new JSCalendar properties without standard iCalendar conversion? >> >> As the author of both the iCalendar conversion and that new I-D I >> prefer to get both iCalendar conversion and new JSCalendar properties >> done at the same time. That's the only way we can be sure to not have >> missed a thing. > > We made a decision. Mike and I will start working on the > jscalendar-icalendar I-D again. I will also work on a JSCalendar > extension document to close any current gaps in JSCalendar with > regards to iCalendar conversion. This will make sure that iCalendar > conversion is covered before we start publishing JSCalendar extensions. > > All other work that depends on JSCalendar will have to wait should it > require properties of this upcoming JSCalendar extension. > > Regards, > Robert > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify -- Joris Baum Tel: +49 721 170293 16 Fax: +49 721 170293 179 http://www.audriga.com |http://www.twitter.com/audriga -------------------------------------------------------------------------- audriga GmbH | Alter Schlachthof 57 | 76137 Karlsruhe Sitz der Gesellschaft: Karlsruhe - Amtsgericht Mannheim - HRB 713034 Geschäftsführer: Dr. Frank Dengler, Dr. Hans-Jörg Happel --------------------------------------------------------------------------