Re: [dispatch] JSCalendar: Updated to draft version 01
Marten Gajda <marten@dmfs.org> Tue, 18 June 2019 22:04 UTC
Return-Path: <marten@dmfs.org>
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 BD38A120457 for <dispatch@ietfa.amsl.com>; Tue, 18 Jun 2019 15:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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=dmfs.org
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 KlYHcn9cWNO6 for <dispatch@ietfa.amsl.com>; Tue, 18 Jun 2019 15:04:30 -0700 (PDT)
Received: from mailrelay2-1.pub.mailoutpod1-cph3.one.com (mailrelay2-1.pub.mailoutpod1-cph3.one.com [46.30.210.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 892B512042F for <dispatch@ietf.org>; Tue, 18 Jun 2019 15:04:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dmfs.org; s=20140924; h=content-type:in-reply-to:mime-version:date:message-id:from:references:to: subject:from; bh=0qvY/eRsv+rgUkPrmtInA3rUNFggwWflM+XXZVZBP0M=; b=FoGJ8pmaob47cXU5ZjXgjjt/xgWaCQjQDVO/z6kIWxrWABHBW84MZfgx+caZLJvFgDuyJFKvlDU9o +KhdWarA2VKA7wLHJAoCF7sl+vihozIUEZr3j2n/qYKP0LXMNT6kejTGTHl2KfCNHOSX6+jPWfzBqs jRLWCYrRTMeB3hiE=
X-HalOne-Cookie: e843e4ae66ba164a51a114bdc8092c859d3f8876
X-HalOne-ID: 09094523-9215-11e9-b9a7-d0431ea8a290
Received: from smtp.dmfs.org (unknown [2003:5f:6e14:3c00:201:2eff:fe40:2624]) by mailrelay2.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id 09094523-9215-11e9-b9a7-d0431ea8a290; Tue, 18 Jun 2019 22:04:25 +0000 (UTC)
Received: from boss.localdomain (p548B1ED8.dip0.t-ipconnect.de [84.139.30.216]) by smtp.dmfs.org (Postfix) with ESMTPSA id 5891B377 for <dispatch@ietf.org>; Wed, 19 Jun 2019 00:04:25 +0200 (CEST)
To: dispatch@ietf.org
References: <96bef250-7821-4a85-85f5-f9df8128e96a@www.fastmail.com> <8af1f5e8-3799-7358-cc78-06c4afaaa7db@dmfs.org> <6ed41ace-0198-4e7a-8258-ca8ab06b020e@www.fastmail.com>
From: Marten Gajda <marten@dmfs.org>
Message-ID: <8d11eb06-07cb-2de6-3d43-e2f0d6c3b1ac@dmfs.org>
Date: Wed, 19 Jun 2019 00:04:24 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <6ed41ace-0198-4e7a-8258-ca8ab06b020e@www.fastmail.com>
Content-Type: multipart/alternative; boundary="------------386C79B2E1BA4F06E7839011"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/dwwgUo469T__J9TKckZgxM7RlRg>
Subject: Re: [dispatch] JSCalendar: Updated to draft version 01
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Jun 2019 22:04:39 -0000
Am 18.06.19 um 16:09 schrieb Robert Stepanek: > What would you gain in your use cases from a StructuredName type? Mostly a cleaner data model. > > Mario Loffredo also pointed out to me that FN can occur more than once > in VCARD, so fullName might also need to become an array. I've never seen a vCard with more than one N or FN property. Since a single FN is the normal case we could use a plain string for the name and put only the additional names into an array: { "name": "default formatted name goes here", "additionalNames": ["other formatted names", "go into this array"], … } or maybe join this with the nickname fields and give the names a label { "name": "default formatted name goes here", "aliases": { "formatted": "other formatted name", "nickname": "nick" }, … } Just thinking out loud here > >> * ContactInformation -> use URIs instead of plain strings? e.g. vCard >> 4 prefers "tel:" URIs. Not sure if that's a good idea though. They >> are machine readable, but not necessarily user friendly. >> > > I'd rather keep plain strings, and restrict them to URIs for certain > ContactInformation "type" and "label" combinations. how about supporting both? { "name": "John Doe", "phones": [{ "type": "home", "value": "+1234567890", "href": "tel:+1-234-567-890" }] } A client which doesn't support both is supposed to remove the other one when it updates either. Cheers, Marten > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch -- Marten Gajda CEO dmfs GmbH Schandauer Straße 34 01309 Dresden GERMANY phone: +49 177 4427167 email: marten@dmfs.org Managing Director: Marten Gajda Registered address: Dresden Registered No.: AG Dresden HRB 34881 VAT Reg. No.: DE303248743
- [dispatch] JSCalendar: Updated to draft version 01 Robert Stepanek
- Re: [dispatch] JSCalendar: Updated to draft versi… Marten Gajda
- Re: [dispatch] JSCalendar: Updated to draft versi… Robert Stepanek
- Re: [dispatch] JSCalendar: Updated to draft versi… Marten Gajda
- Re: [dispatch] JSCalendar: Updated to draft versi… Mario Loffredo
- [dispatch] JSContact Updated (was Re: JSCalendar:… Ben Campbell
- Re: [dispatch] JSContact Updated (was Re: JSCalen… Robert Stepanek