CurrentPROPOSED STANDARDIETF stream

RFC 9982: JSContact Version 2.0: A JSON Representation of Contact Data

In plain English — editorial summary, not part of the RFC

This document defines version "2.0" of JSContact. It defines the uid property of a Card object to be optional, rather than mandatory, as defined previously in version "1.0". All other definitions of JSContact version "1.0" remain as defined in RFC 9553. This document updates RFC 9555 by redefining how to convert the now optional uid property from and to vCard. It also registers the vCard JSCOMPS parameter at IANA, which was defined but not registered in RFC 9555.

Document record

Document ID
RFC9982
Published
May 2026
Authors
R. Stepanek
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
7
Also known as
Updates:
RFC 9555

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9982-jscontact-version-2-0-a-json-representation-of-contact-data