RFC 9555: JSContact: Converting from and to vCard
In plain English — editorial summary, not part of the RFC
This document defines how to convert contact information between the JSContact and vCard data formats. It defines conversion rules for every JSContact and vCard element registered at IANA at the time of publication. It also defines new JSContact properties as well as vCard properties and parameters, to support converting arbitrary or unknown JSContact and vCard elements.
Document record
- Document ID
- RFC9555
- Published
- May 2024
- Authors
- M. Loffredo; R. Stepanek
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 60
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7095jCard: The JSON Format for vCardCurrent
January 2014
- RFC 9553JSContact: A JSON Representation of Contact DataCurrent
May 2024
- RFC 9554vCard Format Extensions for JSContactCurrent
May 2024
- RFC 9610JSON Meta Application Protocol (JMAP) for ContactsCurrent
December 2024
- RFC 9535JSONPath: Query Expressions for JSONCurrent
February 2024
- RFC 9661The JSON Meta Application Protocol (JMAP) for Sieve ScriptsCurrent
September 2024
- RFC 9670JSON Meta Application Protocol (JMAP) SharingCurrent
November 2024
- RFC 9425JSON Meta Application Protocol (JMAP) for QuotasCurrent
June 2023
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?