Expand description
The IANA “JMAP Data Types” registry (RFC 9404 §6.3, its fields restated by draft-ietf-jmap-blobext-03 §11.5), with the “Supports History” column draft-ietf-jmap-object-history-03 §7.2 adds.
One shared table read by Blob/lookup (which type names may be looked up, and which capability each needs) and by object history (which types support it), so the two never disagree.
Rows are the registrations in RFC 9404 Table 1, RFC 9425, RFC 9661,
RFC 9670, RFC 9610, draft-ietf-jmap-calendars-34 and
draft-ietf-jmap-filenode-20, plus the registrations requested by the
draft-atwood-jmap drafts (chat, chat-mimi, graph, graph-edit, scene and
vtc), each citing its document in DataTypeEntry::reference.
“Supports History” is object-history-03 §7.2 Table 1 for the types that
table lists. For the draft-atwood types it is the value those drafts are
to register (decision 22 in docs/design/DECISIONS.md); a type with no
value takes the §7.2 default, “No”.
§Example
use jmap_types::data_types::data_type;
let email = data_type("Email").unwrap();
assert_eq!(email.capability, "urn:ietf:params:jmap:mail");
assert!(email.can_reference_blobs);
assert!(data_type("NoSuchType").is_none());Structs§
- Data
Type Entry - One row of the “JMAP Data Types” registry.
Constants§
- DATA_
TYPES - Every registered data type, sorted by
DataTypeEntry::type_name(byte order).
Functions§
- data_
type - The registry row for
type_name, compared case-sensitively as type names are;Nonewhen the type is not registered.