RFC 9553, "JSContact: A JSON Representation of Contact Data", May 2024

Errata ID: 8267
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: n4n5
Date Reported: 2025-01-28

Section 2.6.1. cryptoKeys says:

A CryptoKey object has all properties of the Resource (Section 1.4.4)
data type, with the following additional definition:

The @type property value MUST be "CryptoKey", if set.

It should say:

A CryptoKey object has all properties of the Resource (Section 1.4.4)
data type, with the following additional definition:

- The @type property value MUST be "CryptoKey", if set.

- The kind property is optional. Its enumerated (Section 1.7.5) values
   are:

  - link
  - embed

Notes:

I've noticed that CryptoKey is defined as a Resource but the CryptoKey "kind" is never defined.

The Resource specify that for kind: "The allowed values are defined in the property definition that makes use of the Resource type. Some property definitions may change this property from being optional to mandatory."


The proposed values in the corrected text are only suggestion from the example of the RFC

As values of "kind" type are registered with IANA we can see that the CryptoKey kind is not present at
https://www.iana.org/assignments/jscontact/jscontact.xhtml#jscontact-enum-values


If the CryptoKey kind is missing, I guess iana should also update the enum (email from the RFC: iana@iana.org)

Report New Errata