rsto/draft-stepanek-jscontact

draft-stepanek-jscontact's Issues

Should we change Address.type to optional?

This information might be missing in some contexts.

Array-typed members identified by a singular noun

The specification contains some array-typed members identified by a plural noun (e.g. addresses, anniversaries, notes) while some others are identified by a singular noun (e.g. jobTitle, role, organization).

Should we change the "name" member to optional ?

After the entry into force of GDPR, sensitive information like name can be subject to a redaction process. In some contexts, a placeholder value (i.e. "REDACTED FOR PRIVACY") is used to show that information exists but can't be published. It might make sense to change the "name" member from mandatory to optional.

timeZone as UTC offset

Should we allow the representation of a time zone as an UTC offset to facilitate the automatic conversion from vCard/jCard ?

mediaType in ContactMethod

A mediaType member might be added to ContactMethod object

Default boolean values

Since the type of isPreferred properties is Boolean, the default value should be false instead of "false".

JSPROP definition does not allow patching arrays

There is an inconsistency between the JSPROP definition in the JSContact/vCard conversion document and the definition of the PatchObject in the JSContact spec. The JSPROP definition states:

The pointer MUST NOT reference into an array.

but the PatchObject allows patching existing array members. We had to allow patching array members to make localizing name and address components efficient, as well as better supporting phonetics in these properties.

We should consider removing this restriction from JSPROP in a future update of the spec.

Add language to Address

Evaluate the opportunity to add language among the Address members.

VCard-to-JSContact conversion when multiple FN properties occur

There is an inconsistency in handling the conversion of multiple FN properties. Before converting to Name.full the FN property that has the least parameters set, the FN property with the lowest PREF value must be selected first.

birthplace and deathplace as geo URI

Mapping document should include the treatment of RFC6474 birthplace and deathplace defined as geo URI

Correction of some typos

Some typos must be corrected:

• change "jobTitle[ ]: String" into "jobTitle: String[ ]"
• change "role[ ]: String" into "role: String[ ]"