Re: [Jmap] I-D Action: draft-ietf-jmap-jscontact-02.txt

Carsten Bormann <cabo@tzi.org> Wed, 17 June 2020 10:54 UTC

Return-Path: <cabo@tzi.org>
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 96FEA3A0944 for <jmap@ietfa.amsl.com>; Wed, 17 Jun 2020 03:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 bCAFCWL_il6X for <jmap@ietfa.amsl.com>; Wed, 17 Jun 2020 03:54:03 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30AD83A0949 for <jmap@ietf.org>; Wed, 17 Jun 2020 03:54:02 -0700 (PDT)
Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49n24T1GXNzysH; Wed, 17 Jun 2020 12:54:01 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <159223169353.12809.1278283414996050403@ietfa.amsl.com>
Date: Wed, 17 Jun 2020 12:53:59 +0200
Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
X-Mao-Original-Outgoing-Id: 614084039.402895-b52de24ec7030f435af9c51b01f7b5a9
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADE74BF2-99D8-41DC-B0CC-ADE7F84D598F@tzi.org>
References: <159223169353.12809.1278283414996050403@ietfa.amsl.com>
To: jmap@ietf.org
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/8QKR0CZZVYolNYpD98QyaM7v3kI>
Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-jscontact-02.txt
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: Wed, 17 Jun 2020 10:54:07 -0000

I’m trying to understand this draft, with a view to creating a CDDL description that should aid in understanding the English language definition of the structure.  I’m getting stuck at places like 2.1.5, which is inscrutable.  What is a Relation object?  What is a relation type?  Of course, I can guess from the various clues, but it would be better if that weren’t necessary.

Is there a collection of examples that could be used to disambiguate the text?  That might help in creating the CDDL (which, really, should be a one-hour effort, without all the guesswork).
Possible positive side effects would include in turn validating that set of examples, and making sure terms like vendor-specific have a well-defined meaning.

I planned to briefly join the interim meeting today, but I can't, so here’s my plea for help on the mailing list.

Grüße, Carsten


> On 2020-06-15, at 16:34, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the JSON Mail Access Protocol WG of the IETF.
> 
>        Title           : JSContact: A JSON representation of contact data
>        Authors         : Robert Stepanek
>                          Mario Loffredo
> 	Filename        : draft-ietf-jmap-jscontact-02.txt
> 	Pages           : 17
> 	Date            : 2020-06-15
> 
> Abstract:
>   This specification defines a data model and JSON representation of
>   contact card information that can be used for data storage and
>   exchange in address book or directory applications.  It aims to be an
>   alternative to the vCard data format and to be unambiguous,
>   extendable and simple to process.  In contrast to the JSON-based
>   jCard format, it is not a direct mapping from the vCard data model
>   and expands semantics where appropriate.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-jmap-jscontact/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-jmap-jscontact-02
> https://datatracker.ietf.org/doc/html/draft-ietf-jmap-jscontact-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-jscontact-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
>