Re: [Jmap] Which spec to use for Calendar?

Robert Stepanek <rsto@fastmailteam.com> Mon, 30 November 2020 08:32 UTC

Return-Path: <rsto@fastmailteam.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 632643A1121 for <jmap@ietfa.amsl.com>; Mon, 30 Nov 2020 00:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=MNrHM06U; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Uu9l0ZLh
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 4ofMtSGVCcWq for <jmap@ietfa.amsl.com>; Mon, 30 Nov 2020 00:32:36 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4E1F3A1120 for <jmap@ietf.org>; Mon, 30 Nov 2020 00:32:36 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C697E5C0052 for <jmap@ietf.org>; Mon, 30 Nov 2020 03:32:35 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute4.internal (MEProxy); Mon, 30 Nov 2020 03:32:35 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=R3bEvZL 8MG4AuDQxzYKtFbeJI9wAEfZq11AUKc4zPWE=; b=MNrHM06UG4S4dJiQNikTV6W HDYe1gP97sw/5c2guYzD96OvXp/v64d+93pwKdhkCADqHq9hZMluCSLWLLwh/fmJ dG1g5ZmiUN7UdUezN0S0XEAMVjMAoSF2CNp+fV74P3gYVFZcxDOvyZG4EwkJfqmJ wxExCAyJfpLc9qk3Qv6OzgsTQP7ymSsQ29vNCjCbjfiimU6O/F0h4/cMh/LlSANP l8epi2mE6DP91AHZvfwDrM6ezaf3l3wgmZNngWe5pLbe496E1yXwdJxnc8KOQB25 6idU/MZ5FKZ4Bw9USBwePt1pkHHeX2vB5H6AlYe6gWtVeGeP+qXdg+TcaTBRWtw= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=R3bEvZ L8MG4AuDQxzYKtFbeJI9wAEfZq11AUKc4zPWE=; b=Uu9l0ZLh0ZDbSE/HElUYr5 4nlCnk2grxYuXrWjiGx+9pfniIKUPANK784Gaz7Ki5Jw4IHYdj2ZKsw5MGhhdaQJ XOTuOpAaiUXWijCu90NeCE7MBRcoiO898puNK1OnzTaILQ1eDLV5Dg7QjaeWLlvW yEzjVL+O3mAkZy75Sa1yUMymkWE5bCuCQClc16dtVjzPpoQC30ZdbjXYPIh/LkPh +2Z7Kj9JmO05Jz4A115jsFyRdsn9mZ4XFTgmnKPMl4775OPyMg5S78vUsqwHylfv Z8LVP59Zh9A4SdDvlshTbdYZ47/v97haW0v2JqJiDi55BGIhhhur88+po9jISIWw ==
X-ME-Sender: <xms:I67EX0Bm9FCeWMVwRT34X4hmSF0d3JYDY2ADLwVthVk0XtFwZcqsNw> <xme:I67EX2gl4xYu8zUtI2VoAR40F2X14TwP_zgjXU35QRDPtfsnj-hDv88A70rldJ0Ka cnwvXEeKusg0Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehledguddvtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrg dtreerreertdenucfhrhhomhepfdftohgsvghrthcuufhtvghprghnvghkfdcuoehrshht ohesfhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeeggfefud ekfefglefgteekgefhgfehvefhtdevveevvdefheduieffieeigfetieenucffohhmrghi nhepjhhmrghprdhiohdpihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomheprhhsthhosehfrghsthhmrghilhhtvggrmhdrtgho mh
X-ME-Proxy: <xmx:I67EX3m1knX7H9cbHYj4ky-UDr8RYd--SKDkBEZ2-YFnbPbVtC39LQ> <xmx:I67EX6xm8VxHlHfa2Rlj2UocCAyEx_sNuZwKVEVotM0ZIp2KVhC2Hg> <xmx:I67EX5QD239ElD8Pv39jB5nTM_cdtT0budm5sSp9yEhaSZ8enapZNQ> <xmx:I67EXwdZk05NabqfHpLDhH1Y3CWkqkdNK2m123kC6LSZREXOBz-85g>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7A0AF180093; Mon, 30 Nov 2020 03:32:35 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-622-g4a97c0b-fm-20201115.001-g4a97c0b3
Mime-Version: 1.0
Message-Id: <483b9167-df7d-4191-a751-416a502e17b0@www.fastmail.com>
In-Reply-To: <CAK-uCxs7jfdEfPn+GzddMg4FV7xByYcTi5e+9-h+-TZ649b+3Q@mail.gmail.com>
References: <CAK-uCxs7jfdEfPn+GzddMg4FV7xByYcTi5e+9-h+-TZ649b+3Q@mail.gmail.com>
Date: Mon, 30 Nov 2020 09:32:15 +0100
From: Robert Stepanek <rsto@fastmailteam.com>
To: jmap@ietf.org
Content-Type: multipart/alternative; boundary="e558b31d27394fde9de529b31974e6f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Gy9R_0hhbYxR0IvhN42bXhRU6Jc>
Subject: Re: [Jmap] Which spec to use for Calendar?
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: Mon, 30 Nov 2020 08:32:38 -0000

Hi Stephan,

On Fri, Nov 27, 2020, at 5:22 PM, Stephan Wissel wrote:
> we started to create a JSON schema (using OpenAPI 3) for jsCalendar.

Great!

> I see 2 documents describing it:
> https://jmap.io/spec-calendars.html
> https://tools.ietf.org/html/draft-ietf-calext-jscalendar-32
> [...]
> Question: Which document should we follow here and how does JSCalendar relate to Calendar?

The jscalendar document in the IETF calext group describes the data model for calendar entries. The document at jmap.io is a proposed internet draft for a calendaring API that uses this data model. The internet draft for the latter is worked on in the IETF jmap working group: https://datatracker.ietf.org/doc/draft-ietf-jmap-calendars/

> We seen attributes "type" and "@type".

They are unrelated, the @type property is metadata. I assume you mean having both "type" and "@type" can be confusing, and I agree. However, I am not aware of any "type" property in JSCalendar. I do know there is a "type" property defined for CalendarEventNotification in the JMAP Calendars draft. That should probably be renamed.

Cheers,
Robert