[dispatch] JSContact Updated (was Re: JSCalendar: Updated to draft version 01)

[Ben Campbell <[e-mail]>]

If anyone else is confused by the subject header (as I was), the topic is “JSContact”, not “JSCalendar”.

Thanks!

Ben.

> On Jun 7, 2019, at 6:06 AM, Robert Stepanek <[e-mail]> wrote:
> 
> Hi all,
> 
> I've submitted draft version 01 of draft-stepanek-jscontact:
> https://tools.ietf.org/html/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 <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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dispatch