Re: [dispatch] JSCalendar: Updated to draft version 01
Marten Gajda <marten@dmfs.org> Mon, 17 June 2019 22:25 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 B6E6E120094 for <dispatch@ietfa.amsl.com>; Mon, 17 Jun 2019 15:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level:
X-Spam-Status: No, score=-1.987 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, T_FILL_THIS_FORM_SHORT=0.01] 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 PcZdtKHU3GHJ for <dispatch@ietfa.amsl.com>; Mon, 17 Jun 2019 15:25:03 -0700 (PDT)
Received: from mailrelay1-1.pub.mailoutpod1-cph3.one.com (mailrelay1-1.pub.mailoutpod1-cph3.one.com [46.30.210.182]) (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 6CDF112004D for <dispatch@ietf.org>; Mon, 17 Jun 2019 15:25:03 -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=+zGj93j/EyJ4X8Eu9yHjha369xdBcujCBpT9xbLKWGc=; b=tLdBKmOq7b2Vxn9D+tJWE3IaKzXqbr/SQYeyULCK8a/hkW8KC+2x6WH/m44lapAIprfQNpwnmSfKB EXK9qj2Y8COb06/cL4NuWf1OxBaeD5Wr36NSGD8IOmDS/lgY5usVgX0HS3ZipC22g3Uzf1VSFnRVaz ZgJFAw7AdJiTmn+4=
X-HalOne-Cookie: f5a728e9ecd2bccadd29708ac88708487203f378
X-HalOne-ID: be629f80-914e-11e9-bc2c-d0431ea8a283
Received: from smtp.dmfs.org (unknown [2003:5f:6e14:3c00:201:2eff:fe40:2624]) by mailrelay1.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id be629f80-914e-11e9-bc2c-d0431ea8a283; Mon, 17 Jun 2019 22:25:00 +0000 (UTC)
Received: from boss.localdomain (p548B1ED8.dip0.t-ipconnect.de [84.139.30.216]) by smtp.dmfs.org (Postfix) with ESMTPSA id B55C329B for <dispatch@ietf.org>; Tue, 18 Jun 2019 00:24:59 +0200 (CEST)
To: dispatch@ietf.org
References: <96bef250-7821-4a85-85f5-f9df8128e96a@www.fastmail.com>
From: Marten Gajda <marten@dmfs.org>
Message-ID: <8af1f5e8-3799-7358-cc78-06c4afaaa7db@dmfs.org>
Date: Tue, 18 Jun 2019 00:24:59 +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: <96bef250-7821-4a85-85f5-f9df8128e96a@www.fastmail.com>
Content-Type: multipart/alternative; boundary="------------125E05F662C0EF65EA1D6C7D"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/TbrRvnzv_OilB3ZbRR5TPlvvBZw>
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: Mon, 17 Jun 2019 22:25:06 -0000
Hi Robert, here are a few more ideas for consideration: * instead of making name components top level elements introduce an object called "structuredName" { firstName, lastName, middleName, prefix, suffix ...}. * 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. * Add additional kind "Resource" (i.e. projector, car …). Few years back, we had a TC Resource, not sure whether the results have been published somewhere though * Support other kinds of events (i.e. see https://tools.ietf.org/html/rfc6474, also specifies additional location types: place of birth, place of death) * Relationships (manager of, spouse of, etc), ideally linked via UID, I guess Cheers, Marten Am 07.06.19 um 13:06 schrieb Robert Stepanek: > Hi all, > > I've submitted draft version 01 of draft-stepanek-jscontact: > https://tools.ietf.org/html/draft-stepanek-jscontact > > This version is includes some, but not yet all of the feedback of > individual > reviewers as well as the CalConnect XLV meeting this week. > > Changes: > - Added a new property for full names. > - Changed the single-string name component fields to arrays. > - Added a kind property, similar to VCARD KIND. > - Added a ISO-3166-1 country code property to Address. > - Added a full address property to Address. > - Added preferredContactMethod property. > - Added geo URI and time zone properties to Address. > - Added a role property. > > There following feedback needs further consideration and I'm happy about > any input: > > Names: > - Learn more about the findings of ISO/TC 37/SC4 on naming schemes, and > probably reuse it for JSContact. > - Current vendors such as Google and Apple already make use of > X-PHONETIC-{FIRST,LAST}-NAME properties for phonetic names. > It's similar to > https://tools.ietf.org/html/draft-fukuda-vcarddav-phonetic-transcription-03 > > Contact: > - Support more than one company, and consider renaming it to > affiliations or > organizations. > - Allow for a similar property such as SORT-AS in VCARD4. > - Add categories and keywords properties, similar to JSCalendar. > - Allow for hierarchies? (group includes group? contact includes contact?) > > ContactInformation: > - Add a unique id to each ContactInformation, so that sync conflicts > can be > better resolved.. (might want to change the contact information lists to > JMAP-style maps, where the id is the map key). > > ContactGroup: > - List contact objects in a group, rather than their uids. If only uid > is of > interest, the embedded contact could just define that property. > - Allow to override properties for a contact within a group. E.g. a > contact > might override its "role" for a group that defines a project. Could use > JSCalendar PatchObject in a property called contactOverrides. > > Address: > - consider renaming it to Location > - Learn more about ISO19160-6 for international address > profiles. > > Other: > - Localization most probably will be only required for names and address. > - Rename either the RFC or the Contact object to JSCard for > disambiguation? > > Cheers, > Robert > > _______________________________________________ > 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