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

Alexey Melnikov <> Thu, 17 December 2020 10:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4C2E13A15BF for <>; Thu, 17 Dec 2020 02:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ti0k7tvslc7y for <>; Thu, 17 Dec 2020 02:44:09 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1A3C03A09E8 for <>; Thu, 17 Dec 2020 02:44:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1608201848;; s=june2016;; 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 [] ( []) by (submission channel) via TCP with ESMTPSA id <>; Thu, 17 Dec 2020 10:44:07 +0000
To: Neil Jenkins <>, IETF JMAP Mailing List <>
References: <>
From: Alexey Melnikov <>
Message-ID: <>
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: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------EB0A2D9FD48A94E4475967F4"
Content-Language: en-GB
Archived-At: <>
Subject: Re: [Jmap] Proposal: split sharing mechanism from JMAP Calendars spec
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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,