Re: [dispatch] JSCalendar: Updated to draft version 01

["Robert Stepanek" <[e-mail]>]

Hi Marten,

thanks for your input.

On Tue, Jun 18, 2019, at 12:25 AM, Marten Gajda wrote:
> 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 ...}. 


 The reason I kept it top-level is because I deemed names as "too important" for a nested property, and N properties can occur at most once in VCARD4 (RFC6474). But checking VCARD3 (RFC 2426), I see no restriction on cardinality. Any insight if N is safe to assume to occur only once? An array of StructuredName that consists of string array properties would seem to be unnecessarily complex for the majority of uses. What would you gain in your use cases from a StructuredName type?

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.

> * 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.

> * 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


Mario also pointed me to the "application" and "device" kinds (RFC 6473, RFC 6869).

> * 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)


There's also death date for it. Which brings up another topic: VCARD BDAY and DEATHDAY allow all of the following values:

 BDAY:19960415
 BDAY:--0415
 BDAY;19531015T231000Z
 BDAY;VALUE=text:circa 1800

in JSCalendar we require them to be formatted as "YYYY-MM-DD" where any part may be 0s for unknowns. We could at least allow "YYYY-MM-DD" and "YYYY-MM-DDTHH:MM:SSZ" where any date part can be 0 for unknowns, and the time part omitted, if unknown.

> * Relationships (manager of, spouse of, etc), ideally linked via UID, I guess


Yes, we could use a structured similar to the JSCalendar "relatedTo" property (https://tools.ietf.org/html/draft-ietf-calext-jscalendar-14#section-4.1.3)

Cheers,
Robert