Re: [Jmap] Proposal: split sharing mechanism from JMAP Calendars spec
Joris Baum <joris@audriga.com> Tue, 15 December 2020 08:22 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 B54663A0E98 for <jmap@ietfa.amsl.com>; Tue, 15 Dec 2020 00:22:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 k0JFT8W1yvYd for <jmap@ietfa.amsl.com>; Tue, 15 Dec 2020 00:22:01 -0800 (PST)
Received: from mail.audriga.com (mail.audriga.com [176.221.42.35]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B925B3A0E44 for <jmap@ietf.org>; Tue, 15 Dec 2020 00:22:01 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.audriga.com (Postfix) with ESMTP id D14A4A1E6 for <jmap@ietf.org>; Tue, 15 Dec 2020 09:21:59 +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 m6n9ImCfA9xn for <jmap@ietf.org>; Tue, 15 Dec 2020 09:21:37 +0100 (CET)
Received: from [192.168.0.94] (HSI-KBW-46-223-162-22.hsi.kabel-badenwuerttemberg.de [46.223.162.22]) (Authenticated sender: joris@audriga.com) by mail.audriga.com (Postfix) with ESMTPSA id D84E6A1E5 for <jmap@ietf.org>; Tue, 15 Dec 2020 09:21:37 +0100 (CET)
To: jmap@ietf.org
References: <1e765f38-5a7a-4498-ab6a-8361671713f5@beta.fastmail.com>
From: Joris Baum <joris@audriga.com>
Message-ID: <cef41da6-6bc5-9d36-a688-1d4f14eda08b@audriga.com>
Date: Tue, 15 Dec 2020 09:21:37 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
MIME-Version: 1.0
In-Reply-To: <1e765f38-5a7a-4498-ab6a-8361671713f5@beta.fastmail.com>
Content-Type: multipart/alternative; boundary="------------A03436E4569ADECEBCA9E7D8"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/d1RzQNsRo-XoxEDRO4GmqyGEz_c>
Subject: Re: [Jmap] Proposal: split sharing mechanism from JMAP Calendars spec
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 15 Dec 2020 08:22:06 -0000
Hi Neil, sounds like a good idea. From what I can see one would currently need to reuse the CalendarPrincipal and CalendarShareNotification for specs that are somehow similar to JMAP for Calendars. I would have done it like that in JMAP for Tasks (and probably also Notes). Since CalDAV also defines tasks and notes and the JMAP spec relates to CalDAV, reusing sharing primitives prefixed by "Calendar" would probably only be semi-weird :P. I like dropping the "Calendar" prefix, because it would make it clearer that they are generic sharing primitives and not specific to calendars. There may be similar issues with other primitives or methods that are defined in JMAP for Calendars. I am currently planning on keeping JMAP for Tasks as close as possible to JMAP for Calendars (similar to how CalDAV does it). The simplest way that I can see, would be to redefine a nearly identical primitive like CalendarEventNotification called TaskNotification. I also do not expect most of the method calls to deviate all too much from what is defined in JMAP for Calendars. This is why I am planning on simply referencing the methods from JMAP for Calendars instead of copy+pasting the definition into JMAP for Tasks (and probably Notes as well). Maybe there is a better way that I am currently not seeing, or we could move even more into a "generic" spec? Regards, Joris On 15.12.20 07:01, Neil Jenkins wrote: > Hi all, > > The JMAP Calendars draft-in-progress currently defines the > CalendarPrincipal and CalendarShareNotification data types under a > separate capability. Looking at it, I have come to the conclusion that > we should go a step further: drop "Calendar" from the names and split > them out into their own spec. These are really generic sharing > primitives that could then be referenced by the other specs — e.g. > calendars, tasks, mail sharing — to define how you share data of types > between entities within a system in a consistent way. > > Please reply with any comments, questions, objections, or agreement > with the proposal and I will write up a draft splitting out these data > types to propose for acceptance. > > Cheers, > Neil. > > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap -- Joris Baum Tel: +49 721 170293 16 Fax: +49 721 170293 179 http://www.audriga.com | http://www.twitter.com/audriga -------------------------------------------------------------------------- audriga GmbH | Durlacher Allee 47 | 76131 Karlsruhe Sitz der Gesellschaft: Karlsruhe - Amtsgericht Mannheim - HRB 713034 Geschäftsführer: Dr. Frank Dengler, Dr.-Ing. Hans-Jörg Happel --------------------------------------------------------------------------
- [Jmap] Proposal: split sharing mechanism from JMA… Neil Jenkins
- Re: [Jmap] Proposal: split sharing mechanism from… Joris Baum
- Re: [Jmap] Proposal: split sharing mechanism from… Jim Fenton
- Re: [Jmap] Proposal: split sharing mechanism from… Ken Murchison
- Re: [Jmap] Proposal: split sharing mechanism from… Bron Gondwana
- Re: [Jmap] Proposal: split sharing mechanism from… Neil Jenkins
- Re: [Jmap] Proposal: split sharing mechanism from… Alexey Melnikov
- Re: [Jmap] Proposal: split sharing mechanism from… Neil Jenkins
- Re: [Jmap] Proposal: split sharing mechanism from… Joris Baum
- Re: [Jmap] Proposal: split sharing mechanism from… Neil Jenkins
- Re: [Jmap] Proposal: split sharing mechanism from… Hans-Joerg Happel
- Re: [Jmap] Proposal: split sharing mechanism from… Neil Jenkins