ContactCard/query sorting support for name/surname an name/givenname

[pbleser-oc]

RFC 9610 currently specifies sorting capabilities for the JMAP ContactCard/query operation as follows in section 3.3.2 Sorting:

The following values for the "property" field on the Comparator object MUST be supported for sorting:

• "created" - The "created" date on the ContactCard.
• "updated" - The "updated" date on the ContactCard.

The following values for the "property" field on the Comparator object SHOULD be supported for sorting:

• "name/given" - The value of the first NameComponent in the "name" property whose "kind" is "given".
• "name/surname" - The value of the first NameComponent in the "name" property whose "kind" is "surname"."name/surname2" - The value of the first NameComponent in the "name" property whose "kind" is "surname2".

Unfortunately, at the time of writing, Stalwart only supports created and updated, as using name/surname yields an error response:

"error",{"type":"unsupportedSort","description":"name/surname"}

Would it be possible to implement support for those attributes in the future ?

I can imagine that there must be quite some complexity involved since they are deep attributes of a nested Name object, but

• humans definitely expect address book entries to be sorted after surname, givenname
• without server-side sorting, pagination cannot be achieved as the only option is to pull all the contacts of an addressbook, and sorting them in memory on the client