[Jmap] Re: Éric Vyncke's No Objection on draft-ietf-jmap-contacts-09: (with COMMENT)

[Neil Jenkins <[e-mail]>]

Hi Éric,

Thank you for your review.

On Sun, 26 May 2024, at 16:58, Éric Vyncke via Datatracker wrote:
> In `This MUST be an integer >= 1, or null for no limit` does null represent the
> integer 0 or NULL (lile in SQL) ? Suggest adding text to clarify, perhaps only
> double quotes around null.

This is the JSON `null` value. The type signature `UnsignedInt|null` for this property indicates the value can either be an UnsignedInt, as defined in RFC8620, Section 1.3 <https://www.rfc-editor.org/rfc/rfc8620.html#section-1.3>,  or a JSON null value. This is consistent with how we have specified this in all the other JMAP documents, and a reference to the notational conventions is at the top of the document <https://www.ietf.org/archive/id/draft-ietf-jmap-contacts-09.html#name-notational-conventions>.

> In `If true, the user may create an AddressBook in this account` suggest to use
> 'if and only if' construct.

I have rewritten to:

The user may create an AddressBook in this account if, and only if, this is true.

> ## Section 2
> 
> Which type is 'id' ? Integer ? String ? Also applies to sections 3. If
> well-known by the JMAP community, suggest a reminder in the terminology.

Again, this is referenced at the beginning of the document in Section 1.1 Notational Conventions <https://www.ietf.org/archive/id/draft-ietf-jmap-contacts-09.html#name-notational-conventions>, which says:

*Type signatures, examples and property descriptions in this document follow the conventions established in **Section 1.1* <https://rfc-editor.org/rfc/rfc8620#section-1.1>* of [**RFC8620* <https://www.ietf.org/archive/id/draft-ietf-jmap-contacts-09.html#RFC8620>*]**. The Id and UnsignedInt data types defined in Sections **1.2* <https://rfc-editor.org/rfc/rfc8620#section-1.2>* and **1.3* <https://rfc-editor.org/rfc/rfc8620#section-1.3>* of **[**RFC8620* <https://www.ietf.org/archive/id/draft-ietf-jmap-contacts-09.html#RFC8620>*]** are also used in this document.*

> 'isDefault' text could be clearer when no AddressBook has isdefault=true.

If no AddressBook is default, it's entirely up to the client what to do. I could add this, although it seems a bit redundant.

> In the `mayRead`and others, should the following text be a normative MAY ?

No, because it's expressing a permission (is the user allowed to do this), not a choice for the implementor.

> ## Section 3.3.1
> 
> Use of `UTCDate` seems to refer to UTC date and time. It is perhaps well-know
> in the JMAP community but could benefit from some explanations.

This is defined in Section 1.4 of RFC 8620 — looks like I missed referencing this in the Notational Conventions, I'll add it in. Thanks for flagging.

> Can all `String` be UTF-8 encoded ?

Yes.

Cheers,
Neil.