[dispatch] Feedback requested: draft-jenkins-jscalendar

Robert Stepanek <rsto@fastmailteam.com> Thu, 28 September 2017 08:43 UTC

Return-Path: <rsto@fastmailteam.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D87AC13455A for <dispatch@ietfa.amsl.com>; Thu, 28 Sep 2017 01:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=messagingengine.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 NlV6mBeSytdH for <dispatch@ietfa.amsl.com>; Thu, 28 Sep 2017 01:43:40 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F05F13457E for <dispatch@ietf.org>; Thu, 28 Sep 2017 01:43:40 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9647120778; Thu, 28 Sep 2017 04:43:39 -0400 (EDT)
Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Thu, 28 Sep 2017 04:43:39 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=dQR5ToTSUw5zwpa76SG3wrJbr42xV Os+L92UcPZXKTw=; b=IKxLEQZqdmUldTnq95PGanHvIl8AWWsgflFIzFDnFki9w d/kg9csesBfZyYFwxCcd9fMMMQhj8yzOgWKIoPYjzavuHKEp1u0liuEz4C+tc0Cc 8q5Gu1OpXeAoWsS6OiON1scaMsQzsv6APW24dCruHFE3SYOFdUUOwoWSolOiikXq zLgTtnii4LrZ132Ps8Kt/yEnQ5kjCclzk8LPJMap791kB74VLAkocuVxB55xwASx UA+tt6bSDSj7YC/4hc6p6J0cJv9/Ibe8R0nOhDSaPzcin/tYE3cFvQ7VTIfKwIid UMSOi7Q96e8CbwX7FzP1TVa1T/9uZlW5zpPyzckRg==
X-ME-Sender: <xms:O7bMWeaggTB9W-OArqnawo0tG8c-zDcR7RlLMBr6zYvRaecRR7lxqQ>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 6BBD46269A; Thu, 28 Sep 2017 04:43:39 -0400 (EDT)
Message-Id: <1506588219.485384.1120927832.1112E2F6@webmail.messagingengine.com>
From: Robert Stepanek <rsto@fastmailteam.com>
To: dispatch@ietf.org
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Neil Jenkins <neilj@fastmailteam.com>, Bron Gondwana <brong@fastmailteam.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-6cb49228
Date: Thu, 28 Sep 2017 10:43:39 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/BJc8lFl4J-GThT4OgaojQ4yLhIE>
Subject: [dispatch] Feedback requested: draft-jenkins-jscalendar
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 08:43:45 -0000

Hi,

over the last year we have been working on JSCalendar, a JSON-based
representation of calendar data as an alternative to iCalendar
(RFC5545).  We already got extensive feedback from the members of
CalConnect  and individual contributors and we'd very much like to get
the discussion started on our proposal at IETF.

There's an increasing amount of proprietary calendar data formats in the
industry, most of them JSON-based. We believe that a new standardised
calendar data representation that meets the requirements of these
applications would help to reduce interoperability issues while
overcoming iCalendar pitfalls and ambiguities.

The current draft version is located at
https://datatracker.ietf.org/doc/draft-jenkins-jscalendar/

Do you have any feedback on this? What would make you use  the new
format, what is it currently missing?

Thanks for your thoughts,
Robert

P.S.: This message got cross-posted to the CALSIFY workgroup.