IETF Logo Mail Archive

Re: [Jmap] Proposal: split sharing mechanism from JMAP Calendars spec

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 17 December 2020 10:44 UTC

Return-Path: <alexey.melnikov@isode.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 4C2E13A15BF for <jmap@ietfa.amsl.com>; Thu, 17 Dec 2020 02:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 ti0k7tvslc7y for <jmap@ietfa.amsl.com>; Thu, 17 Dec 2020 02:44:09 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3C03A09E8 for <jmap@ietf.org>; Thu, 17 Dec 2020 02:44:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1608201848; d=isode.com; s=june2016; i=@isode.com; bh=1hwJa95ct78nD1MXtL4gfn7SDs//VjNRMOVe113hJYs=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=H2JQzJ68yrQ2iSskdgCJvOCz5pVabayapJ0MeJG1u8bb0YEWjs7ELq23TaY5rQiveBLKzz m92O0XECewDCgBR6Hfyfy+WZKmrbfPpK3sXCIaVNzfudc+imNZijPMOY0BqrjQcTqswWUY aJfViGBciL7expevKn48sSA6O09sSfo=;
Received: from [172.27.251.141] (connect.isode.net [172.20.0.72]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <X9s2dwAuQWUH@waldorf.isode.com>; Thu, 17 Dec 2020 10:44:07 +0000
To: Neil Jenkins <neilj@fastmailteam.com>, IETF JMAP Mailing List <jmap@ietf.org>
References: <1e765f38-5a7a-4498-ab6a-8361671713f5@beta.fastmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <ddb1ba56-46ca-f8bf-8967-77f7f0526009@isode.com>
Date: Thu, 17 Dec 2020 10:42:11 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
In-Reply-To: <1e765f38-5a7a-4498-ab6a-8361671713f5@beta.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------EB0A2D9FD48A94E4475967F4"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/s-h98OZ7mvnZdqrkB_66pDclBUY>
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: Thu, 17 Dec 2020 10:44:10 -0000

Hi Neil,

On 15/12/2020 06: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.

CalendarShareNotification is referencing CalendarRights. The latter 
looks rather calendar specific.

If you can generalize CalendarRights, what you suggest above looks like 
a good direction.

> 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.


Best Regards,

Alexey

v2.23.0 | Report a Bug | By Email