<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="std" consensus="true" docName="draft-ietf-calext-rfc9555bis-03" ipr="pre5378Trust200902" tocInclude="true" tocDepth="4" sortRefs="true" symRefs="true" updates="9553, 9554" obsoletes="9555" xml:lang="en" version="3">
  <front>
    <title abbrev="JSContact: Converting vCard">JSContact: Converting from and to vCard</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-calext-rfc9555bis-03"/>
    <author fullname="Mario Loffredo" initials="M." surname="Loffredo">
      <organization>IIT-CNR/Registro.it</organization>
      <address>
        <postal>
          <street>Via Moruzzi, 1</street>
          <city>Pisa</city>
          <country>Italy</country>
          <code>56124</code>
        </postal>
        <email>mario.loffredo@iit.cnr.it</email>
        <uri>https://www.iit.cnr.it</uri>
      </address>
    </author>
    <author fullname="Robert Stepanek" initials="R." surname="Stepanek">
      <organization>Fastmail</organization>
      <address>
        <postal>
          <extaddr>PO Box 234</extaddr>
          <street>Collins St. West</street>
          <city>Melbourne</city>
          <region>VIC</region>
          <code>8007</code>
          <country>Australia</country>
        </postal>
        <email>rsto@fastmailteam.com</email>
        <uri>https://www.fastmail.com</uri>
      </address>
    </author>
    <date year="2026" month="November" day="19"/>
    <area>art</area>
    <workgroup>calext</workgroup>
    <keyword>JSON</keyword>
    <keyword>contacts</keyword>
    <keyword>vCard</keyword>
    <keyword>jCard</keyword>
    <abstract>
      <t>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. This document obsoletes RFC 9555 and updates RFC 9553 and RFC 9554.</t>
    </abstract>
    <note removeInRFC="true">
      <t>Differences from RFC 9555 are documented in <xref target="differences_from_rfc9555"/>.</t>
    </note>
  </front>
  <middle>
    <section>
      <name>Introduction</name>
      <section anchor="notational_conventions" numbered="true" toc="default">
        <name>Notational Conventions</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
        <t>The ABNF definitions in this document use the notations of <xref target="RFC5234"/>. ABNF rules not defined in this document are defined in either <xref target="RFC5234"/> (such as the ABNF for CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT) or <xref target="RFC6350"/>.</t>
      </section>
      <section anchor="scope_and_goals">
        <name>Scope and Goals</name>
        <t>This document outlines how to convert between the <xref target="RFC6350">vCard</xref> and <xref target="RFC9553">JSContact</xref> data formats.  It describes which elements are common to both, but also highlights where the two formats differ. For each common element, it defines a conversion rule and includes an example of how to convert that element. All vCard and JSContact elements that IANA registers for common use are in scope. Elements that IANA registers for reserved use and obsolete elements are out of scope.</t>
        <t>For elements that have no counterpart in the other format, it is the goal of this document to define how to preserve them during conversion, but in general it is not the goal to achieve this by defining new standard elements. Instead, this document defines vCard and JSContact elements to preserve elements that have no equivalent in the other format. These conversion-specific properties are defined in Section <xref target="vcard_prop_jsprop" format="counter"/> for vCard, and <xref target="jscontact_prop_vcard"/> for JSContact. </t>
        <t>This document obsoletes <xref target="RFC9555"/>. For contents that remain unchanged, it includes all verified errata for the obsoleted document. The conversion rules are updated for JSContact versions "2.0" and "3.0", defined in <xref target="RFC9982"/> and <xref target="I-D.loffredo-calext-jscontact-eai"/>.</t>
        <t><xref target="updates_to_jscontact"/> replaces the JSContact "vCardProps", "vCardParams" and "vCardName" properties originally defined in <xref target="RFC9555"/> with the new "vCard" property. The new property allows for edge cases where the former elements were insufficient. For vCard, <xref target="updates_to_vcard"/> replaces the <xref target="RFC9554" section="4.7" sectionFormat="parens">PROP-ID</xref> parameter with the new JSID parameter. Both changes align the conversion-specific elements of vCard and JSContact with those defined for iCalendar and JSCalendar in <xref target="I-D.ietf-calext-jscalendar-icalendar"/>, allowing for code reuse for implementations that support these formats.</t>
        <t><xref target="jscontact_updated_address_kinds"/> updates the definitions of the "name" and "number" AddressComponent kinds, originally defined in <xref target="RFC9553"/>, to ease conversion between JSContact and vCard.  This also requires updating the definition of the ADR property (<xref target="vcard_updated_adr"/>), which, if implemented strictly, could lead to data loss.  Similarly, <xref target="vcard_updated_n"/> updates the definition of the N property to avoid data loss.</t>
      </section>
      <section>
        <name>How to Read the Examples</name>
        <t>Later sections contain examples that illustrate how to convert between the vCard and JSContact data formats.  The notation of these examples is such that their main points should be clear to the reader, but their contents can also be parsed for automated testing. The following sections define the notation for such examples.</t>
        <section anchor="notation_vcard">
          <name>vCard Examples</name>
          <t>A vCard example contains either an extract or a complete representation of vCard data. The following rules apply:</t>
          <ul>
            <li>An example that only contains vCard properties implicitly represents a vCard (e.g. the <tt>BEGIN:VCARD</tt> and <tt>END:VCARD</tt> lines are implicit).</li>
            <li>The vCard implicitly contains all mandatory properties with some value. If they are not included in the example, then their actual value is irrelevant for the example. The default value for the VERSION property is "4.0".</li>
          </ul>
          <t><xref target="example_notation_vcard_implicit_explicit"/> contains three examples, all of which represent the same vCard data.  In the first example, the <tt>BEGIN</tt> and <tt>END</tt> lines and the mandatory properties are implicit. In the second example, only the BEGIN and END lines of the vCard are implicit. The third example depicts a complete vCard, nothing is implicit.</t>
          <figure anchor="example_notation_vcard_implicit_explicit">
            <name>Examples for implicit and explicit vCard notation</name>
            <sourcecode type="vcard"><![CDATA[
EMAIL:foo@example.com
]]></sourcecode>
            <sourcecode type="vcard"><![CDATA[
VERSION:4.0
FN:Foo
EMAIL:foo@example.com
]]></sourcecode>
            <sourcecode type="vcard"><![CDATA[
BEGIN:VCARD
VERSION:4.0
FN:Foo
EMAIL:foo@example.com
END:VCARD
]]></sourcecode>
          </figure>
          <t>A line containing just the value <tt>...</tt> stands for any other properties that might be present in the vCard but are irrelevant for this example.  The value <tt>...</tt> does not represent a property for which at least one same-named property is explicitly stated in the example. <xref target="example_notation_vcard_dotdotdot"/> illustrates this as an alternative representation for the examples of <xref target="example_notation_vcard_implicit_explicit"/>.</t>
          <figure anchor="example_notation_vcard_dotdotdot">
            <name>Example for additional properties represented by <tt>...</tt>
            </name>
            <sourcecode type="vcard"><![CDATA[
BEGIN:VCARD
...
EMAIL:foo@example.com
]]></sourcecode>
          </figure>
          <t>A line starting with a single space represents the continuation of a folded content line (<xref target="RFC6350" section="3.2"/>).  <xref target="example_notation_vcard_folded"/> illustrates this.</t>
          <figure anchor="example_notation_vcard_folded">
            <name>Example for a folded content line</name>
            <sourcecode type="vcard"><![CDATA[
FN:Joannes Chrysostomus Wolfg
 angus Theophilus Mozart
]]></sourcecode>
          </figure>
        </section>
        <section anchor="notation_jscontact">
          <name>JSContact Examples</name>
          <t>A JSContact example always represents a Card object, even if the example only depicts other JSContact objects and properties.</t>
          <t>JSContact objects are depicted either explicitly or implicitly. An explicit JSContact object starts and ends with braces.  An implicit JSContact object omits braces, it only consists of JSON name/value pairs, separated by comma.</t>
          <t>An implicit JSContact object is assumed to be of type Card, unless it contains the <tt>@type</tt> property with a different value.  It is assumed to contain all mandatory properties with some value; if they are not depicted, their actual value is irrelevant for the main point of the example. The default version of the Card is "2.0".</t>
          <t>A JSContact property that is set to its default value is equivalent to the property being omitted.  An example may depict either.</t>
          <t><xref target="example_notation_jscontact_implicit_explicit"/> illustrates this with multiple examples, all of which represent the same JSContact data.  The first example contains an implicit JSContact object of type Card.  The second example contains an explicit Name object but the Card object containing it is omitted.  The third example contains the full Card object, nothing is omitted.</t>
          <figure anchor="example_notation_jscontact_implicit_explicit">
            <name>Examples for implicit and explicit JSContact object notation</name>
            <sourcecode type="json"><![CDATA[
"name": {
  "full": "John Doe"
}
]]></sourcecode>
            <sourcecode type="json"><![CDATA[
"@type": "Name",
"full": "John Doe"
]]></sourcecode>
            <sourcecode type="json"><![CDATA[
{
  "@type": "Card",
  "version": "2.0",
  "name": {
    "full": "John Doe"
  }
}
]]></sourcecode>
          </figure>
          <t>A property with name <tt>"..."</tt> and value <tt>""</tt> stands for additional properties that might be present in a JSContact object but are irrelevant for this example, including mandatory properties. <xref target="example_notation_jscontact_dotdotdot"/> illustrates this as an alternative representation for the examples of <xref target="example_notation_jscontact_implicit_explicit"/>.</t>
          <figure anchor="example_notation_jscontact_dotdotdot">
            <name>Example for additional properties represented by <tt>...</tt>
            </name>
            <sourcecode type="json"><![CDATA[
"name": {
  "full": "John Doe",
  "...": ""
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="notation_conversion">
          <name>Conversion Examples</name>
          <t>A conversion example depicts vCard data together with the JSContact data it converts to.  The vCard data follows the notation defined in <xref target="notation_vcard"/>, the JSContact data follows the notation defined in <xref target="notation_jscontact"/>.</t>
          <t>The vCard data is preceded by a line containing just <tt>---&#160;vCard:</tt>, and the JSContact data is preceded by a line containing just <tt>---&#160;JSContact:</tt>.  These marker lines are not part of the example data.  Empty lines are not part of the example data either and are ignored.  <xref target="example_notation_conversion"/> illustrates this.</t>
          <figure anchor="example_notation_conversion">
            <name>Example for the notation of a conversion example</name>
            <sourcecode><![CDATA[
--- vCard:
FN:John Doe

--- JSContact:
"name": {
  "full": "John Doe"
}
]]></sourcecode>
          </figure>
          <t>A conversion example applies in both directions: the vCard data converts to the JSContact data, and the JSContact data converts to the vCard data.</t>
          <t>Keys of JSON objects that represent a collection of same-typed values (<xref target="choosing_identifiers"/>) are illustrative, unless the vCard data sets them with the <xref target="vcard_param_jsid">JSID parameter</xref>.</t>
          <t>Similarly, the names of vCard property groups and the values of ALTID parameters are illustrative.</t>
          <t>Unless the conversion rules for an element state otherwise, the order of vCard elements is not significant, including properties and parameters.  Similarly, the order of JSON arrays is insignificant, unless the conversion rules state otherwise or a JSON pointer in the example refers to an array element by its index (e.g. "name/components/0/phonetic" in a "localizations" property).  The order of components within a structured vCard value is significant, but the order of values within one such component is not (e.g. the order of multiple entries in an N property's surnames component is insignificant).</t>
        </section>
      </section>
    </section>
    <section anchor="vcard_jscontact_conversion">
      <name>Converting vCard to JSContact</name>
      <t>This section contains the conversion rules from the vCard to the JSContact Card.</t>
      <section>
        <name>General Rules</name>
        <section anchor="convert_card_uid">
          <name>The Card uid Property</name>
          <t>The UID property converts to the Card object's "uid" property, see <xref target="vcard_prop_uid"/>. In contrast to JSContact version "2.0", the Card object's "uid" property was mandatory in version "1.0".</t>
          <t>Implementations that convert a vCard without a <xref target="RFC6350" section="6.7.6" sectionFormat="parens">UID property</xref> to a Card of version "2.0" or higher <bcp14>MUST NOT</bcp14> generate a unique identifier as value for the <xref target="RFC9553" section="2.1.9" sectionFormat="parens">"uid" property</xref>.</t>
          <t>When converting a vCard without UID property to JSContact version "1.0", implementations <bcp14>MUST</bcp14> generate a value for the "uid" property. Generating unique identifiers is implementation-specific. An implementation <bcp14>SHOULD</bcp14> generate the same value when generating the same Card multiple times. <xref target="RFC9982" section="2"/> describes why this is problematic. Consequently, implementations <bcp14>SHOULD NOT</bcp14> convert to version "1.0" Card objects.</t>
        </section>
        <section anchor="choosing_identifiers">
          <name>Choosing Identifiers</name>
          <t>Multivalued properties in JSContact are typically represented as a JSON object where the object keys are of the Id type (<xref target="RFC9553" derivedContent="RFC9553" section="1.4.1" sectionFormat="of"/>) and the object values are the converted vCard property.  In the absence of the JSID parameter (see <xref target="vcard_param_jsid"/>), implementations are free to choose any identifier as key for such entries.  Whatever identifier generation scheme implementations use, they <bcp14>MUST</bcp14> generate values that are valid according to the definition of the Id type in <xref target="RFC9553"/>.  For example, this could be an incrementing number across all identifier keys in the Card object or only unique within one JSON object.</t>
        </section>
        <section anchor="vcard_unknown">
          <name>Preserving vCard Elements</name>
          <t>vCard data may contain elements that do not convert to JSContact. This includes standard vCard elements, such as the ALTID and PID parameters, as well as extended properties and parameters (see <xref target="RFC6350" sectionFormat="of" section="6.10"/>). This document defines the conversion-specific <xref target="jscontact_prop_vcard" sectionFormat="parens">"vCard" property</xref> to support preserving these elements.</t>
        </section>
      </section>
      <section anchor="vcard_parameters">
        <name>vCard Parameters</name>
        <t>This section contains the conversion rules for vCard parameters.</t>
        <section anchor="vcard_param_altid">
          <name>ALTID</name>
          <t>The <xref target="RFC6350" section="5.4" sectionFormat="parens">ALTID parameter</xref> does not convert to JSContact, but several conversion rules make use of this parameter to combine multiple vCard properties into one JSContact object.  For an example of this, see <xref target="vcard_prop_adr"/>.</t>
        </section>
        <section anchor="vcard_param_author">
          <name>AUTHOR</name>
          <t>The <xref target="RFC9554" section="4.1" sectionFormat="parens">AUTHOR parameter</xref> on a NOTE property converts to the "uri" property of the <xref target="RFC9553" section="2.8.3" sectionFormat="parens">Author object</xref>.  That Author object is set as the value of the "author" property of the <xref target="RFC9553" section="2.8.3" sectionFormat="parens">Note object</xref>.</t>
        </section>
        <section anchor="vcard_param_author_name">
          <name>AUTHOR-NAME</name>
          <t>The <xref target="RFC9554" section="4.2" sectionFormat="parens">AUTHOR-NAME parameter</xref> on a NOTE property converts to the "name" property of the <xref target="RFC9553" section="2.8.3" sectionFormat="parens">Author object</xref>.  That Author object is set as the value of the "author" property of the Note object.</t>
        </section>
        <section anchor="vcard_param_calscale">
          <name>CALSCALE</name>
          <t>The <xref target="RFC6350" section="5.8" sectionFormat="parens">CALSCALE parameter</xref> set on a BDAY, DEATHDATE, or ANNIVERSARY property converts to the "calendarScale" property of the <xref target="RFC9553" section="2.8.1" sectionFormat="parens">PartialDate object</xref>.</t>
        </section>
        <section anchor="vcard_param_cc">
          <name>CC</name>
          <t>The <xref target="RFC8605" section="3.1" sectionFormat="parens">CC parameter</xref> on an ADR property converts to the "countryCode" property of the <xref target="RFC9553" section="2.5.1.1" sectionFormat="parens">Address object</xref>.</t>
        </section>
        <section anchor="vcard_param_created">
          <name>CREATED</name>
          <t>The <xref target="RFC9554" section="4.3" sectionFormat="parens">CREATED parameter</xref> on a NOTE property converts to the "created" property of the <xref target="RFC9553" section="2.8.3" sectionFormat="parens">Note object</xref>.</t>
        </section>
        <section anchor="vcard_param_derived">
          <name>DERIVED</name>
          <t>The <xref target="RFC9554" section="4.4" sectionFormat="parens">DERIVED parameter</xref> does not convert to JSContact.  If the DERIVED parameter is set to "true" on a vCard property, then implementations <bcp14>MUST NOT</bcp14> convert that property to JSContact.</t>
        </section>
        <section anchor="vcard_param_geo">
          <name>GEO</name>
          <t>The <xref target="RFC6350" section="5.10" sectionFormat="parens">GEO parameter</xref> set on an ADR property converts to the "coordinates" property of the <xref target="RFC9553" section="2.5.1.1" sectionFormat="parens">Address object</xref>. Also see the conversion of the GEO property in <xref target="vcard_prop_geo"/>.</t>
        </section>
        <section anchor="vcard_param_group">
          <name>GROUP</name>
          <t>The <xref target="RFC7095" section="3.3.1.2" sectionFormat="parens">GROUP parameter</xref> does not convert to JSContact.  It exclusively is for use in jCard and <bcp14>MUST NOT</bcp14> be set in a vCard.</t>
          <t>Preserving the exact group name when converting from vCard to JSContact and back to vCard is not necessary.  Any group identifiers will do, as long as the resulting vCard groups its properties equally to the original vCard.  Implementations <bcp14>MAY</bcp14> preserve the original group name in the VCardProperty object's "parameters" property (<xref target="jscontact_prop_vcard"/>).</t>
          <t>The following examples illustrate how to convert the GROUP parameter:</t>
          <figure anchor="test_vcard_param_group">
            <name>Example of How to Preserve the Group Name for a Known Property</name>
            <sourcecode><![CDATA[
--- vCard:
item1.TEL;VALUE=uri:tel:+1-555-555-5555
item1.X-ABLabel:Test

--- JSContact:
"phones": {
  "p1": {
    "number": "tel:+1-555-555-5555",
    "label": "Test"
  }
},
"vCard": {
  "convertedProperties": {
    "phones/p1/number": {
      "name": "tel",
      "parameters": {
        "group": "item1"
      }
    },
    "phones/p1/label": {
      "name": "x-ablabel",
      "parameters": {
        "group": "item1"
      }
    }
  }
}
]]></sourcecode>
          </figure>
          <figure anchor="test_vcard_param_group_2">
            <name>Example of How to Preserve the Group Name for an Unknown Property</name>
            <sourcecode><![CDATA[
--- vCard:
item2.X-FOO:bar

--- JSContact:
"vCard": {
  "properties": [
    ["x-foo", {
      "group": "item2"
    }, "unknown", "bar"]
  ]
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_param_index">
          <name>INDEX</name>
          <t>The <xref target="RFC6715" section="3.1" sectionFormat="parens">INDEX parameter</xref> set on the EXPERTISE, HOBBY, INTEREST, and ORG-DIRECTORY properties converts to the PersonalInfo (<xref target="RFC9553" derivedContent="RFC9553" section="2.8.4" sectionFormat="of"/>) and Directory (<xref target="RFC9553" derivedContent="RFC9553" section="2.6.2" sectionFormat="of"/>) objects' "listAs" property.</t>
        </section>
        <section anchor="vcard_param_language">
          <name>LANGUAGE</name>
          <t>The <xref target="RFC6350" section="5.1" sectionFormat="parens">LANGUAGE parameter</xref> converts to the Card object's "localizations" property (<xref target="RFC9553" derivedContent="RFC9553" section="2.7.1" sectionFormat="of"/>).</t>
          <t>Localizations in vCard and JSContact differ subtly.  For example, alternative vCard properties that share an ALTID value are peers, whereas JSContact models localizations as patches to the properties of the non-localized Card.  Similarly, JSContact defines the main language for the Card, whereas a vCard only has a default language if it contains the <xref target="RFC9554" section="3.3" sectionFormat="parens">LANGUAGE property</xref>; individual vCard properties can also be in a language different from the vCard's default language.  Finally, some JSContact properties convert to vCard parameters (e.g., LABEL), but whether the LANGUAGE parameter applies to parameter values is not defined.  Converting localizations is therefore implementation-specific, and conversion between implementations can be lossy.  Implementations that convert to a <xref target="I-D.ietf-calext-jscontact-profiles">JSContact profile</xref> <bcp14>MUST</bcp14> adhere to the profile-specific restrictions, if any.</t>
          <t>The following guidelines cover the common case of localized property values, such as of the FN, N, ADR, ORG and TITLE properties.  For vCard properties that share the same ALTID parameter value:</t>
          <ul>
            <li>One of these properties converts to the non-localized Card.  This is preferably the property without the LANGUAGE parameter, or else the property whose LANGUAGE parameter value equals the Card's "language" property.</li>
            <li>Each other property converts to a PatchObject in the "localizations" property, keyed by its LANGUAGE parameter value.  The patch replaces either the JSContact object to which the property converts (e.g., "organizations/o1") or some of its properties (e.g., "titles/t1/name").</li>
          </ul>
          <t>The following examples illustrate how to convert the LANGUAGE parameter:</t>
          <figure anchor="test_vcard_param_language">
            <name>LANGUAGE Conversion Example: Card Language</name>
            <sourcecode><![CDATA[
--- vCard:
LANGUAGE:en
FN;LANGUAGE=en:John Doe
TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=1;LANGUAGE=fr:Patron

--- JSContact:
"language": "en",
"name": {
  "full": "John Doe"
},
"titles": {
  "t1": {
    "name": "Boss"
  }
},
"localizations": {
  "fr": {
    "titles/t1/name": "Patron"
  }
}
]]></sourcecode>
          </figure>
          <figure anchor="test_vcard_param_language_2">
            <name>LANGUAGE Conversion Example: Property without Language</name>
            <sourcecode><![CDATA[
--- vCard:
FN:John Doe
TITLE;ALTID=1:Boss
TITLE;ALTID=1;LANGUAGE=fr:Patron

--- JSContact:
"name": {
  "full": "John Doe"
},
"titles": {
  "t1": {
    "name": "Boss"
  }
},
"localizations": {
  "fr": {
    "titles/t1/name": "Patron"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_param_label">
          <name>LABEL</name>
          <t>The <xref target="RFC6350" section="6.3.1" sectionFormat="parens">LABEL parameter</xref> on an ADR property converts to the "full" property of the <xref target="RFC9553" section="2.5.1" sectionFormat="parens">Address object</xref>.</t>
        </section>
        <section anchor="vcard_param_level">
          <name>LEVEL</name>
          <t>The <xref target="RFC6715" section="3.2" sectionFormat="parens">LEVEL parameter</xref> converts to the "level" property of the <xref target="RFC9553" section="2.8.4" sectionFormat="parens">PersonalInfo object</xref>.  If this parameter is set on the EXPERTISE property, then its values convert as follows:
      </t>
          <ul spacing="compact">
            <li>"beginner" converts to "low";</li>
            <li>"average" converts to "medium"; and</li>
            <li>"expert" converts to "high".</li>
          </ul>
          <t>In all other cases, the values convert verbatim, but lowercase <bcp14>MUST</bcp14> be used for the JSContact value.</t>
        </section>
        <section anchor="vcard_param_mediatype">
          <name>MEDIATYPE</name>
          <t>The <xref target="RFC6350" section="5.7" sectionFormat="parens">MEDIATYPE parameter</xref> converts to the "mediaType" property of the <xref target="RFC9553" section="1.4.4" sectionFormat="parens">Resource object</xref>.</t>
        </section>
        <section anchor="vcard_param_phonetic">
          <name>PHONETIC</name>
          <t>The <xref target="RFC9554" section="4.6" sectionFormat="parens">PHONETIC parameter</xref> converts to the Name (<xref target="RFC9553" derivedContent="RFC9553" section="2.2.1" sectionFormat="of"/>) and Address (<xref target="RFC9553" derivedContent="RFC9553" section="2.5.1" sectionFormat="of"/>) objects' "phoneticSystem" property unless the parameter value is "script", in which case the "phoneticSystem" property is not set.  The value of the SCRIPT parameter converts to the "phoneticScript" property (see <xref target="vcard_param_phonetic"/>).</t>
          <t>The related N or ADR property is defined by the vCard ALTID parameter. The conversion rules for the <xref target="vcard_prop_n">N</xref> and <xref target="vcard_prop_adr">ADR</xref> properties define how the vCard components convert to JSContact.  The component values of the property on which the PHONETIC parameter is set, convert to the respective NameComponent or AddressComponent objects' "phonetic" properties.  If more than one property has the PHONETIC parameter set and relates to the same property, then they convert to the Card object's "localizations" property according to their LANGUAGE parameter values as outlined in <xref target="vcard_param_language"/>.</t>
          <t>The following example illustrates how to convert the PHONETIC parameter:</t>
          <figure anchor="test_vcard_param_phonetic">
            <name>PHONETIC Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
LANGUAGE:zh-Hant
N;ALTID=1;LANGUAGE=zh-Hant:孫;中山;文,逸仙;;
N;ALTID=1;PHONETIC=jyut;
 SCRIPT=Latn;LANGUAGE=yue:syun1;zung1saan1;man4,jat6sin1;;

--- JSContact:
"language": "zh-Hant",
"name": {
  "components": [
    { "kind": "surname", "value": "孫" },
    { "kind": "given", "value": "中山" },
    { "kind": "given2", "value": "文" },
    { "kind": "given2", "value": "逸仙" }
  ]
},
"localizations": {
  "yue": {
    "name/phoneticSystem": "jyut",
    "name/phoneticScript": "Latn",
    "name/components/0/phonetic": "syun1",
    "name/components/1/phonetic": "zung1saan1",
    "name/components/2/phonetic": "man4",
    "name/components/3/phonetic": "jat6sin1"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_param_pid">
          <name>PID</name>
          <t>The <xref target="RFC6350" section="5.5" sectionFormat="parens">PID parameter</xref> does not convert to JSContact.</t>
        </section>
        <section anchor="vcard_param_pref">
          <name>PREF</name>
          <t>The <xref target="RFC6350" section="5.3" sectionFormat="parens">PREF parameter</xref> converts to the "pref" property of that JSContact object, to which the vCard property having this parameter converts.</t>
        </section>
        <section anchor="vcard_param_propid">
          <name>PROP-ID</name>
          <t>The <xref target="RFC9554" section="4.7" sectionFormat="parens">PROP-ID parameter</xref> is deprecated. The <xref target="vcard_param_jsid">JSID</xref> parameter replaces it.</t>
          <t>The PROP-ID parameter <bcp14>MUST</bcp14> be ignored if the JSID parameter is set on the same property. If the JSID parameter is not set, implementations <bcp14>MAY</bcp14>  convert the PROP-ID parameter to the key of the JSContact object to which the vCard property converts to.</t>
          <t>The following example illustrates how to convert the PROP-ID parameter:</t>
          <figure anchor="example_vcard_param_propid">
            <name>PROP-ID Conversion Example</name>
            <sourcecode type="vcard"><![CDATA[
TEL;PROP-ID=xyz;VALUE=uri:tel:+1-555-555-5555;ext=5555
]]></sourcecode>
            <sourcecode type="json"><![CDATA[
"phones": {
  "xyz": {
    "number": "tel:+1-555-555-5555;ext=5555"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_param_script">
          <name>SCRIPT</name>
          <t>The <xref target="RFC9554" section="4.8" sectionFormat="parens">SCRIPT parameter</xref> converts to the Name (<xref target="RFC9553" derivedContent="RFC9553" section="2.2.1" sectionFormat="of"/>) or Address (<xref target="RFC9553" derivedContent="RFC9553" section="2.5.1" sectionFormat="of"/>) objects' "phoneticScript" property.  Also see <xref target="vcard_param_phonetic"/>.</t>
        </section>
        <section anchor="vcard_param_service_type">
          <name>SERVICE-TYPE</name>
          <t>The <xref target="RFC9554" section="4.9" sectionFormat="parens">SERVICE-TYPE parameter</xref> converts to the "service" property of the <xref target="RFC9553" section="2.3.2" sectionFormat="parens">OnlineService object</xref>.</t>
        </section>
        <section anchor="vcard_param_sort_as">
          <name>SORT-AS</name>
          <t>The <xref target="RFC6350" section="5.9" sectionFormat="parens">SORT-AS parameter</xref> converts to the Name, Organization, and OrgUnit objects' "sortAs" properties.</t>
        </section>
        <section anchor="vcard_param_type">
          <name>TYPE</name>
          <t>The <xref target="RFC6350" section="5.6" sectionFormat="parens">TYPE parameter</xref> either converts to the "contexts" property or the "kind" property, as defined in later sections. If not specified otherwise, the vCard "home" and "work" parameter values convert to the JSContact "private" and "work" contexts, respectively.</t>
        </section>
        <section anchor="vcard_param_tz">
          <name>TZ</name>
          <t>The <xref target="RFC6350" section="5.11" sectionFormat="parens">TZ parameter</xref> on an ADR property converts to the "timeZone" property of the <xref target="RFC9553" section="2.5.1" sectionFormat="parens">Address object</xref>.  Also see the conversion of the TZ property in <xref target="vcard_prop_tz"/>.</t>
        </section>
        <section anchor="vcard_param_username">
          <name>USERNAME</name>
          <t>The <xref target="RFC9554" section="4.10" sectionFormat="parens">USERNAME parameter</xref> converts to the "user" property of the <xref target="RFC9553" section="2.3.2" sectionFormat="parens">OnlineService object</xref>.</t>
        </section>
        <section anchor="vcard_param_value">
          <name>VALUE</name>
          <t>The <xref target="RFC6350" section="5.2" sectionFormat="parens">VALUE parameter</xref> does not convert to JSContact.</t>
        </section>
      </section>
      <section anchor="vcard_props">
        <name>vCard Properties</name>
        <section anchor="vcard_prop_adr">
          <name>ADR</name>
          <t>The <xref target="RFC6350" section="6.3.1" sectionFormat="parens">ADR property</xref> converts to an <xref target="RFC9553" section="2.5.1" sectionFormat="parens">Address object</xref>. The converted object is set in the "addresses" property of the Card object. The ADR property value converts to the "components" property of the Address object.  The ADR property converts to the same Address object as the <xref target="vcard_prop_geo">GEO property</xref> and <xref target="vcard_prop_tz">TZ property</xref> if either they are members of the same vCard property group, or if they are part of no group.</t>
          <t>Each component in the structured value of the ADR property converts to an AddressComponent. The component value converts to the AddressComponent object's "value" property, the component position determines the value of the AddressComponent object's "kind" property as follows:</t>
          <table anchor="adr_kind_conversion">
            <name>ADR Components Conversion</name>
            <thead>
              <tr>
                <th align="left">ADR component</th>
                <th align="left">AddressComponent kind</th>
                <th align="left">Remarks</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">post office box</td>
                <td align="left">postOfficeBox</td>
                <td align="left"><xref target="RFC6350"/> recommends that this component not be set.</td>
              </tr>
              <tr>
                <td align="left">extended address</td>
                <td align="left">apartment</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">street address</td>
                <td align="left">name</td>
                <td align="left">
                  <t>Do not convert if the "street number" or "street name" component has a non-empty value (see <xref target="vcard_updated_adr"/>). The value may contain both the street name and number (see <xref target="jscontact_updated_address_kinds"/>).</t>
                </td>
              </tr>
              <tr>
                <td align="left">locality</td>
                <td align="left">locality</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">region</td>
                <td align="left">region</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">postal code</td>
                <td align="left">postcode</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">country</td>
                <td align="left">country</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">room</td>
                <td align="left">room</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">apartment</td>
                <td align="left">apartment</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">floor</td>
                <td align="left">floor</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">street number</td>
                <td align="left">number</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">street name</td>
                <td align="left">name</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">building</td>
                <td align="left">building</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">block</td>
                <td align="left">block</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">subdistrict</td>
                <td align="left">subdistrict</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">district</td>
                <td align="left">district</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">landmark</td>
                <td align="left">landmark</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
              <tr>
                <td align="left">direction</td>
                <td align="left">direction</td>
                <td>Defined in <xref target="RFC9554"/>.</td>
              </tr>
            </tbody>
          </table>
          <t>Each comma-separated value in an ADR component converts to its own AddressComponent of the same kind.  If the <xref target="vcard_param_jscomps">JSCOMPS</xref> parameter is set and valid, then the Address object's "isOrdered" property value is "true", and the "defaultSeparator" property and any separator name components are set according to the parameter value.  The order in the "components" property <bcp14>MUST</bcp14> adhere to the order of the JSCOMPS parameter value.  If the JSCOMPS parameter is not set or not valid, then the Address object's "isOrdered" property value is "false", and the "defaultSeparator" property <bcp14>MUST NOT</bcp14> be set. In this case, the order in the "components" property is implementation-specific; one option is to follow the order of values in the ADR structured value when read from left to right.</t>
          <t>The values "billing" and "delivery" of the TYPE parameter, defined in Sections <xref target="RFC9554" sectionFormat="bare" section="5.1"/> and <xref target="RFC9554" sectionFormat="bare" section="5.2"/> of <xref target="RFC9554"/>, convert to the corresponding entries of the Address object's "contexts" property.  All other parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The path of the ADR property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "addresses/{id}/components", where "{id}" denotes the identifier of the Address object.</t>
          <t>The following example illustrates how to convert the ADR property.  The "street number" and "street name" components have non-empty values, so the "street address" component does not convert:</t>
          <figure anchor="test_vcard_prop_adr">
            <name>ADR Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
ADR;TYPE=work;CC=US:;;54321 Oak St;Reston;VA;20190;USA;;;;54321;Oak St;;;;;;

--- JSContact:
"addresses": {
  "ADDR-1" : {
    "contexts": { "work": true },
    "components": [
      { "kind": "number", "value": "54321" },
      { "kind": "name", "value": "Oak St" },
      { "kind": "locality", "value": "Reston" },
      { "kind": "region", "value": "VA" },
      { "kind": "postcode", "value": "20190" },
      { "kind": "country", "value": "USA" }
    ],
    "countryCode": "US"
  }
}
]]></sourcecode>
          </figure>
          <t>The following example illustrates how to convert an ADR property that only contains the components defined in <xref target="RFC6350"/>.  The "street address" component contains both the street name and number, and converts to a single AddressComponent of kind "name":</t>
          <figure anchor="test_vcard_prop_adr_2">
            <name>ADR Conversion Example with Combined Street Address</name>
            <sourcecode><![CDATA[
--- vCard:
ADR;CC=AT:;;Hauptstraße 5;Wien;;1010;Austria

--- JSContact:
"addresses": {
  "ADDR-1" : {
    "components": [
      { "kind": "name", "value": "Hauptstraße 5" },
      { "kind": "locality", "value": "Wien" },
      { "kind": "postcode", "value": "1010" },
      { "kind": "country", "value": "Austria" }
    ],
    "countryCode": "AT"
  }
}
]]></sourcecode>
          </figure>
          <t>See <xref target="vcard_param_jscomps_examples"/> for examples of how to use the JSCOMPS parameter for structured property values.</t>
        </section>
        <section anchor="vcard_prop_anniversary">
          <name>ANNIVERSARY</name>
          <t>The <xref target="RFC6350" section="6.2.6" sectionFormat="parens">ANNIVERSARY property</xref> converts to an Anniversary object.  The converted object is set in the "anniversaries" property of the Card object. The ANNIVERSARY property value converts to the "date" property of the Anniversary object. The Anniversary "kind" is "wedding".  See <xref target="vcard_prop_bday"/> how to convert property values of type TIMESTAMP and DATE.</t>
          <t>The following example illustrates how to convert the ANNIVERSARY property:</t>
          <figure anchor="test_vcard_prop_anniversary">
            <name>ANNIVERSARY Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
ANNIVERSARY:19860201

--- JSContact:
"anniversaries": {
  "ANNIVERSARY-1" : {
    "kind": "wedding",
    "date": {
      "year": 1986,
      "month": 2,
      "day": 1
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_bday">
          <name>BDAY</name>
          <t>The <xref target="RFC6350" section="6.2.5" sectionFormat="parens">BDAY property</xref> converts to an Anniversary object.  The converted object is set in the "anniversaries" property of the Card object. The BDAY property value converts to the "date" property of the Anniversary object. The Anniversary "kind" is "birth".</t>
          <t>If the property value type is <xref target="RFC6350" derivedContent="RFC6350" section="4.3.5" sectionFormat="parens">DATE</xref> and defines at least a year or a month and day, then the value converts to a PartialDate object. If the property value type is <xref target="RFC6350" derivedContent="RFC6350" section="4.3.5" sectionFormat="parens">TIMESTAMP</xref> then the value converts to the Timestamp object's "utc" property. Otherwise it does not convert to JSContact.  A BDAY property and the BIRTHPLACE property (see <xref target="vcard_prop_birthplace"/>) convert to the same Anniversary object if their ALTID parameter values match or are not set on either property.</t>
          <t>The following example illustrates how to convert the BDAY property:</t>
          <figure anchor="test_vcard_prop_bday">
            <name>BDAY Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
BDAY:19531015T231000Z
BIRTHPLACE:
 123 Main Street\nAny Town, CA 91921-1234\nU.S.A.

--- JSContact:
"anniversaries": {
  "ANNIVERSARY-1" : {
    "kind": "birth",
    "date": {
      "@type": "Timestamp",
      "utc": "1953-10-15T23:10:00Z"
    },
    "place": {
      "full":
         "123 Main Street\nAny Town, CA 91921-1234\nU.S.A."
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_birthplace">
          <name>BIRTHPLACE</name>
          <t>The <xref target="RFC6474" section="2.1" sectionFormat="parens">BIRTHPLACE property</xref> converts to an Anniversary object.  The converted object is set in the "anniversaries" property of the Card object. The BIRTHPLACE property value converts to the "place" property of the Anniversary object. The Anniversary "kind" is "birth". The BIRTHPLACE and the BDAY property can convert to the same Anniversary object, see <xref target="vcard_prop_bday"/>.</t>
          <t>The property value converts to an Address object. If the property value is of type TEXT it converts to the "full" property of the Address object. If the property value is of type URI and uses the "geo:" URI scheme then it converts to the "coordinates" property of the Address object. A property having any other value does not convert to an Anniversary object.</t>
          <t>The path of the BIRTHPLACE property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "anniversaries/{id}/place", where "{id}" denotes the identifier of the Anniversary object.</t>
        </section>
        <section anchor="vcard_prop_caladruri">
          <name>CALADRURI</name>
          <t>The <xref target="RFC6350" section="6.9.2" sectionFormat="parens">CALADRURI property</xref> converts to a <xref target="RFC9553" section="2.4.2" sectionFormat="parens">SchedulingAddress object</xref>.  The converted object is set in the "schedulingAddresses" property of the Card object.  The CALADRURI property value converts to the "uri" property of the SchedulingAddress object. The PREF parameter converts according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the CALADRURI property:</t>
          <figure anchor="test_vcard_prop_caladruri">
            <name>CALADRURI Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:https://example.com/calendar/jdoe

--- JSContact:
"schedulingAddresses": {
  "SCHEDULING-1": {
    "uri": "mailto:janedoe@example.com",
    "pref": 1
  },
  "SCHEDULING-2": {
    "uri": "https://example.com/calendar/jdoe"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_caluri">
          <name>CALURI</name>
          <t>The <xref target="RFC6350" section="6.9.3" sectionFormat="parens">CALURI property</xref> converts to a <xref target="RFC9553" section="2.4.1" sectionFormat="parens">Calendar object</xref>.  The converted object is set in the "calendars" property of the Card object.  The "kind" property of the Calendar object is set to "calendar".  The CALURI property value converts to the "uri" property of the Calendar object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the CALURI property:</t>
          <figure anchor="test_vcard_prop_caluri">
            <name>CALURI Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
CALURI;PREF=1:https://cal.example.com/calA
CALURI;MEDIATYPE=text/calendar:https://ftp.example.com/calA.ics

--- JSContact:
"calendars": {
  "CAL-1": {
    "kind": "calendar",
    "uri": "https://cal.example.com/calA",
    "pref": 1
  },
  "CAL-2": {
    "kind": "calendar",
    "uri": "https://ftp.example.com/calA.ics",
    "mediaType": "text/calendar"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_categories">
          <name>CATEGORIES</name>
          <t>The <xref target="RFC6350" section="6.7.1" sectionFormat="parens">CATEGORIES property</xref> converts to the "keywords" property of the Card object.  Each text value of the CATEGORIES property becomes a key in the "keywords" property.</t>
          <t>The PREF parameter does not convert to JSContact; implementations <bcp14>MAY</bcp14> insert the keywords by order of preference.</t>
          <t>The path of the CATEGORIES property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "keywords". Because more than one vCard property can convert to the "keywords" property, preserving conversion information for a single CATEGORIES property is implementation-specific.</t>
          <t>The following example illustrates how to convert the CATEGORIES property:</t>
          <figure anchor="test_vcard_prop_categories">
            <name>CATEGORIES Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
CATEGORIES:internet,IETF,Industry,Information Technology

--- JSContact:
"keywords": {
  "internet": true,
  "IETF": true,
  "Industry": true,
  "Information Technology": true
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_clientpidmap">
          <name>CLIENTPIDMAP</name>
          <t>The <xref target="RFC6350" section="6.7.7" sectionFormat="parens">CLIENTPIDMAP property</xref> does not convert to JSContact.</t>
        </section>
        <section anchor="vcard_prop_contact_uri">
          <name>CONTACT-URI</name>
          <t>The <xref target="RFC8605" section="2.1" sectionFormat="parens">CONTACT-URI property</xref> converts to a <xref target="RFC9553" section="2.6.3" sectionFormat="parens">Link object</xref>.  The converted object is set in the "links" property of the Card object.  The "kind" property of the Link object is set to "contact".  The CONTACT-URI property value converts to the "uri" property of the Link object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the CONTACT-URI property:</t>
          <figure anchor="test_vcard_prop_contact_uri">
            <name>CONTACT-URI Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
CONTACT-URI;PREF=1:mailto:contact@example.com

--- JSContact:
"links": {
  "CONTACT-1": {
    "kind": "contact",
    "uri": "mailto:contact@example.com",
    "pref": 1
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_created">
          <name>CREATED</name>
          <t>The <xref target="RFC9554" section="3.1" sectionFormat="parens">CREATED property</xref> converts to the "created" property of the Card object.</t>
          <t>The following example illustrates how to convert the CREATED property:</t>
          <figure anchor="test_vcard_prop_created">
            <name>CREATED Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
CREATED:19940930T143510Z

--- JSContact:
"created": "1994-09-30T14:35:10Z"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_email">
          <name>EMAIL</name>
          <t>The <xref target="RFC6350" section="6.4.2" sectionFormat="parens">EMAIL property</xref> converts to an <xref target="RFC9553" section="2.3.1" sectionFormat="parens">EmailAddress object</xref>.  The converted object is set in the "emails" property of the Card object.  The EMAIL property value converts to the "address" property of the EmailAddress object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>Only values that are valid "addr-spec" values as defined in <xref target="RFC5322" section="3.4.1"/> and extended in <xref target="RFC6532" section="3.2"/> convert to JSContact. The EMAIL property value converts to and from the "address" property without modification. In particular, vCard property values may contain non-ASCII characters (<xref target="RFC6350" section="3.1"/>), so internationalized email addresses need not be percent-encoded or otherwise transformed.</t>
          <t>If the property value is an internationalized email address, then it only converts to a Card of version "3.0" or higher (<xref target="I-D.loffredo-calext-jscontact-eai"/>). How to convert other values, or internationalized email addresses to lower JSContact versions, is implementation-specific. Implementations <bcp14>MAY</bcp14> preserve them in the VCard object's "properties" property (<xref target="jscontact_prop_vcard"/>).</t>
          <t>The following example illustrates how to convert the EMAIL property:</t>
          <figure anchor="test_vcard_prop_email">
            <name>EMAIL Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;PREF=1:jane_doe@example.com

--- JSContact:
"emails": {
  "EMAIL-1": {
    "contexts": { "work": true },
    "address": "jqpublic@xyz.example.com"
  },
  "EMAIL-2": {
    "address": "jane_doe@example.com",
    "pref": 1
  }
}
]]></sourcecode>
          </figure>
          <t>The following example illustrates how to convert the EMAIL property with an internationalized email address:</t>
          <figure anchor="test_vcard_prop_email_intl">
            <name>EMAIL Conversion Example with Internationalized Email Address</name>
            <sourcecode><![CDATA[
--- vCard:
EMAIL:jürgen@example.com

--- JSContact:
"version": "3.0",
"emails": {
  "EMAIL-1": {
    "address": "jürgen@example.com"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_deathdate">
          <name>DEATHDATE</name>
          <t>The <xref target="RFC6474" section="2.3" sectionFormat="parens">DEATHDATE property</xref> converts to an Anniversary object.  The converted object is set in the "anniversaries" property of the Card object. The DEATHDATE property value converts to the "date" property of the Anniversary object. The Anniversary "kind" is "death".  See <xref target="vcard_prop_bday"/> how to convert property values of type TIMESTAMP and DATE.  A DEATHDATE property and the DEATHPLACE property (see <xref target="vcard_prop_deathplace"/>) convert to the same Anniversary object if their ALTID parameter values match or are not set on either property.</t>
          <t>The following example illustrates how to convert the DEATHDATE property:</t>
          <figure anchor="test_vcard_prop_deathdate">
            <name>DEATHDATE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
DEATHDATE:19960415
DEATHPLACE:
 5 Court Street\nNew England\, ND 58647\nU.S.A.

--- JSContact:
"anniversaries": {
  "ANNIVERSARY-2" : {
    "kind": "death",
    "date": {
      "year": 1996,
      "month": 4,
      "day": 15
    },
    "place": {
      "full": "5 Court Street\nNew England, ND 58647\nU.S.A."
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_deathplace">
          <name>DEATHPLACE</name>
          <t>The <xref target="RFC6474" section="2.2" sectionFormat="parens">DEATHPLACE property</xref> converts to an Anniversary object.  The converted object is set in the "anniversaries" property of the Card object. The DEATHPLACE property value converts to the "place" property of the Anniversary object. The Anniversary "kind" is "death". The DEATHPLACE and the DEATHDATE property can convert to the same Anniversary object, see <xref target="vcard_prop_deathdate"/>.</t>
          <t>The property value converts to an Address object. If the property value is of type TEXT it converts to the "full" property of the Address object. If the property value is of type URI and uses the "geo:" URI scheme then it converts to the "coordinates" property of the Address object. A property having any other value does not convert to an Anniversary object.</t>
          <t>The path of the DEATHPLACE property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "anniversaries/{id}/place", where "{id}" denotes the identifier of the Anniversary object.</t>
        </section>
        <section anchor="vcard_prop_expertise">
          <name>EXPERTISE</name>
          <t>The <xref target="RFC6715" section="2.1" sectionFormat="parens">EXPERTISE property</xref> converts to a <xref target="RFC9553" section="2.8.4" sectionFormat="parens">PersonalInfo object</xref>.  The converted object is set in the "personalInfo" property of the Card object.  The "kind" property of the PersonalInfo object is set to "expertise".  The EXPERTISE property value converts to the "value" property of the PersonalInfo object.  The INDEX and LEVEL parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the EXPERTISE property:</t>
          <figure anchor="test_vcard_prop_expertise">
            <name>EXPERTISE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
EXPERTISE;LEVEL=beginner;INDEX=2:Chinese literature
EXPERTISE;INDEX=1;LEVEL=expert:chemistry

--- JSContact:
"personalInfo": {
  "PERSINFO-1" : {
    "kind": "expertise",
    "value": "Chinese literature",
     "level": "low",
     "listAs": 2
  },
  "PERSINFO-2" : {
    "kind": "expertise",
    "value": "chemistry",
    "level": "high",
    "listAs": 1
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_fburl">
          <name>FBURL</name>
          <t>The <xref target="RFC6350" section="6.9.1" sectionFormat="parens">FBURL property</xref> converts to a <xref target="RFC9553" section="2.4.1" sectionFormat="parens">Calendar object</xref>.  The converted object is set in the "calendars" property of the Card object.  The "kind" property of the Calendar object is set to "freeBusy".  The FBURL property value converts to the "uri" property of the Calendar object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the FBURL property:</t>
          <figure anchor="test_vcard_prop_fburl">
            <name>FBURL Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
FBURL;PREF=1:https://www.example.com/busy/janedoe
FBURL;MEDIATYPE=text/calendar:https://example.com/busy/project-a.ifb

--- JSContact:
"calendars": {
  "FBURL-1": {
    "kind": "freeBusy",
    "uri": "https://www.example.com/busy/janedoe",
    "pref": 1
  },
  "FBURL-2": {
    "kind": "freeBusy",
    "uri": "https://example.com/busy/project-a.ifb",
    "mediaType": "text/calendar"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_fn">
          <name>FN</name>
          <t>The <xref target="RFC6350" section="6.2.1" sectionFormat="parens">FN property</xref> converts to the <xref target="RFC9553" section="2.2.1" sectionFormat="parens">Name object</xref> in the "name" property of the Card object.  The FN property value converts to the "full" property of the Name object.</t>
          <t>If the LANGUAGE parameter is set, then the FN property converts as outlined in <xref target="vcard_param_language"/>.  In the unexpected case where the vCard contains more than one FN property without the LANGUAGE parameter, convert the FN property that has the least parameters.  If multiple such FN properties are present, choose any of them. All other FN properties do not convert to JSContact. Implementations <bcp14>MAY</bcp14> preserve them in the VCard object's "properties" property (<xref target="jscontact_prop_vcard"/>).</t>
          <t>The path of the FN property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "name/full".</t>
          <t>The following example illustrates how to convert the FN property:</t>
          <figure anchor="test_vcard_prop_fn">
            <name>FN Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
FN:John Q. Public, Esq.

--- JSContact:
"name": {
  "full": "John Q. Public, Esq."
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_gender">
          <name>GENDER</name>
          <t>The <xref target="RFC6350" section="6.2.7" sectionFormat="parens">GENDER property</xref> does not convert to JSContact. Note that the Card object's "speakToAs" property defines how to address and refer to an individual represented by the Card, as do the newly defined vCard GRAMGENDER and PRONOUNS properties of <xref target="RFC9554"/>.</t>
        </section>
        <section anchor="vcard_prop_geo">
          <name>GEO</name>
          <t>The <xref target="RFC6350" section="6.5.2" sectionFormat="parens">GEO property</xref> converts to an <xref target="RFC9553" section="2.5.1" sectionFormat="parens">Address object</xref>.  The converted object is set in the "addresses" property of the Card object.  The GEO property value converts to the "coordinates" property of the Address object.  See <xref target="vcard_prop_adr"/> how to convert the GEO property together with the ADR and TZ property.</t>
          <t>The path of the GEO property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "addresses/{id}/coordinates", where "{id}" denotes the identifier of the Address object.</t>
        </section>
        <section anchor="vcard_prop_gramgender">
          <name>GRAMGENDER</name>
          <t>The <xref target="RFC9554" section="3.2" sectionFormat="parens">GRAMGENDER property</xref> converts to the <xref target="RFC9553" section="2.2.4" sectionFormat="parens">SpeakToAs object</xref>.  The converted object is set in the "speakToAs" property of the Card object.  The GRAMGENDER property value converts to the "grammaticalGender" property of the SpeakToAs object.</t>
          <t>The following example illustrates how to convert the GRAMGENDER property:</t>
          <figure anchor="test_vcard_prop_gramgender">
            <name>GRAMGENDER Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
GRAMGENDER:NEUTER

--- JSContact:
"speakToAs": {
  "grammaticalGender": "neuter"
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_hobby">
          <name>HOBBY</name>
          <t>The <xref target="RFC6715" section="2.2" sectionFormat="parens">HOBBY property</xref> converts to a <xref target="RFC9553" section="2.8.4" sectionFormat="parens">PersonalInfo object</xref>.  The converted object is set in the "personalInfo" property of the Card object.  The "kind" property of the PersonalInfo object is set to "hobby".  The HOBBY property value converts to the "value" property of the PersonalInfo object.  The INDEX and LEVEL parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the HOBBY property:</t>
          <figure anchor="test_vcard_prop_hobby">
            <name>HOBBY Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
HOBBY;INDEX=1;LEVEL=high:reading
HOBBY;INDEX=2;LEVEL=high:sewing

--- JSContact:
"personalInfo": {
  "PERSINFO-1" : {
    "kind": "hobby",
    "value": "reading",
    "level": "high",
    "listAs": 1
  },
  "PERSINFO-2" : {
    "kind": "hobby",
    "value": "sewing",
    "level": "high",
    "listAs": 2
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_impp">
          <name>IMPP</name>
          <t>The <xref target="RFC6350" section="6.4.3" sectionFormat="parens">IMPP property</xref> converts to an <xref target="RFC9553" section="2.3.2" sectionFormat="parens">OnlineService object</xref>.  The converted object is set in the "onlineServices" property of the Card object.  The IMPP property value converts to the "uri" property of the OnlineService object.  The SERVICE-TYPE, USERNAME, PREF, and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>Implementations <bcp14>MAY</bcp14> use the <xref target="jscontact_prop_vcard">"vCard" property</xref> to indicate that the OnlineService object was converted from the IMPP property.</t>
          <t>The following example illustrates how to convert the IMPP property:</t>
          <figure anchor="test_vcard_prop_impp">
            <name>IMPP Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
IMPP;PREF=1:xmpp:alice@example.com

--- JSContact:
"onlineServices": {
  "OS-1": {
    "uri": "xmpp:alice@example.com",
    "pref": 1
  }
},
"vCard": {
  "convertedProperties": {
    "onlineServices/OS-1/uri": {
      "name": "impp"
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_interest">
          <name>INTEREST</name>
          <t>The <xref target="RFC6715" section="2.3" sectionFormat="parens">INTEREST property</xref> converts to a <xref target="RFC9553" section="2.8.4" sectionFormat="parens">PersonalInfo object</xref>.  The converted object is set in the "personalInfo" property of the Card object.  The "kind" property of the PersonalInfo object is set to "interest".  The INTEREST property value converts to the "value" property of the PersonalInfo object.  The INDEX and LEVEL parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the INTEREST property:</t>
          <figure anchor="test_vcard_prop_interest">
            <name>INTEREST Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
INTEREST;INDEX=1;LEVEL=medium:r&b music
INTEREST;INDEX=2;LEVEL=high:rock&roll music

--- JSContact:
"personalInfo": {
  "PERSINFO-1" : {
    "kind": "interest",
    "value": "r&b music",
    "level": "medium",
    "listAs": 1
  },
  "PERSINFO-2" : {
    "kind": "interest",
    "value": "rock&roll music",
    "level": "high",
    "listAs": 2
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_key">
          <name>KEY</name>
          <t>The <xref target="RFC6350" section="6.8.1" sectionFormat="parens">KEY property</xref> converts to a <xref target="RFC9553" section="2.6.1" sectionFormat="parens">CryptoKey object</xref>.  The converted object is set in the "cryptoKeys" property of the Card object.  The KEY property value converts to the "uri" property of the CryptoKey object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the KEY property:</t>
          <figure anchor="test_vcard_prop_key">
            <name>KEY Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
KEY:https://www.example.com/keys/jdoe.cer

--- JSContact:
"cryptoKeys": {
  "KEY-1": {
    "uri": "https://www.example.com/keys/jdoe.cer"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_kind">
          <name>KIND</name>
          <t>The <xref target="RFC6350" section="6.1.4" sectionFormat="parens">KIND property</xref> converts to the "kind" property of the Card object.  Allowed values are those described in <xref target="RFC6350" sectionFormat="of" section="6.1.4"/> and extended with the values declared in <xref target="RFC6473"/> and <xref target="RFC6869"/>.</t>
          <t>The following example illustrates how to convert the KIND property:</t>
          <figure anchor="test_vcard_prop_kind">
            <name>KIND Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
KIND:individual

--- JSContact:
"kind": "individual"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_lang">
          <name>LANG</name>
          <t>The <xref target="RFC6350" section="6.4.4" sectionFormat="parens">LANG property</xref> converts to a <xref target="RFC9553" section="2.3.4" sectionFormat="parens">LanguagePref object</xref>.  The converted object is set in the "preferredLanguages" property of the Card object.  The LANG property value converts to the "language" property of the LanguagePref object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the LANG property:</t>
          <figure anchor="test_vcard_prop_lang">
            <name>LANG Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
LANG;TYPE=work;PREF=1:en
LANG;TYPE=work;PREF=2:fr
LANG;TYPE=home:fr

--- JSContact:
"preferredLanguages": {
  "LANG-1": {
    "language": "en",
    "contexts": { "work": true },
    "pref": 1
  },
  "LANG-2": {
    "language": "fr",
    "contexts": { "work": true },
    "pref": 2
  },
  "LANG-3": {
    "language": "fr",
    "contexts": { "private": true }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_language">
          <name>LANGUAGE</name>
          <t>The <xref target="RFC9554" section="3.3" sectionFormat="parens">LANGUAGE property</xref> converts to the "language" property of the Card object.</t>
          <t>The following example illustrates how to convert the LANGUAGE property:</t>
          <figure anchor="test_vcard_prop_language">
            <name>LANGUAGE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
LANGUAGE:de-AT

--- JSContact:
"language": "de-AT"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_logo">
          <name>LOGO</name>
          <t>The <xref target="RFC6350" section="6.6.3" sectionFormat="parens">LOGO property</xref> converts to a <xref target="RFC9553" section="2.6.4" sectionFormat="parens">Media object</xref>.  The converted object is set in the "media" property of the Card object.  The "kind" property of the Media object is set to "logo".  The LOGO property value converts to the "uri" property of the Media object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the LOGO property:</t>
          <figure anchor="test_vcard_prop_logo">
            <name>LOGO Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
LOGO:https://www.example.com/pub/logos/abccorp.jpg

--- JSContact:
"media": {
  "LOGO-1": {
    "kind": "logo",
    "uri": "https://www.example.com/pub/logos/abccorp.jpg"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_member">
          <name>MEMBER</name>
          <t>The <xref target="RFC6350" section="6.6.5" sectionFormat="parens">MEMBER property</xref> converts to the "members" property of the Card object.  The MEMBER property value becomes a key in the "members" property.</t>
          <t><xref target="RFC6350"/> defines the MEMBER property value type to be URI only, but <xref target="I-D.ietf-calext-vcard4-bis"/> extends its definition to also allow free-form text. The PREF parameter does not convert to JSContact.</t>
          <t>Implementations <bcp14>MAY</bcp14> use the <xref target="jscontact_prop_vcard">"vCard" property</xref> to preserve the value type of the MEMBER property. The path of the MEMBER property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "members/{value}", where "{value}" denotes the MEMBER property value.</t>
          <t>The following examples illustrate how to convert the MEMBER property:</t>
          <figure anchor="test_vcard_prop_member">
            <name>Converting the MEMBER Property</name>
            <sourcecode><![CDATA[
--- vCard:
KIND:group
FN:The Doe family
MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519

--- JSContact:
"kind": "group",
"name": {
  "full": "The Doe family"
},
"members": {
  "urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af": true,
  "urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519": true
}
]]></sourcecode>
          </figure>
          <figure anchor="test_vcard_prop_member_text">
            <name>Converting the MEMBER Property with text value</name>
            <sourcecode><![CDATA[
--- vCard:
KIND:group
MEMBER;VALUE=text:AD8B50F23FF244F1@example.com

--- JSContact:
"kind": "group",
"members": {
  "AD8B50F23FF244F1@example.com": true
},
"vCard": {
  "convertedProperties": {
    "members/AD8B50F23FF244F1@example.com": {
      "name": "member",
      "valueType": "text"
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_n">
          <name>N</name>
          <t>The <xref target="RFC6350" section="6.2.2" sectionFormat="parens">N property</xref> converts to the <xref target="RFC9553" section="2.2.1" sectionFormat="parens">Name object</xref> in the "name" property of the Card object. The N property value converts to the "components" property of the Name object.</t>
          <t>Each component in the structured value of the N property converts to a NameComponent. The component value converts to the NameComponent object's "value" property, the component position determines the value of the NameComponent object's "kind" property as follows:</t>
          <table anchor="n_kind_conversion">
            <name>N Components Conversion</name>
            <thead>
              <tr>
                <th align="left">N component</th>
                <th align="left">NameComponent kind</th>
                <th align="left">Remarks</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Family name</td>
                <td align="left">surname</td>
                <td align="left">Ignore one equal value for each value of the Secondary surname component (see <xref target="vcard_updated_n"/> and <xref target="test_vcard_prop_n_equal_surnames"/>).</td>
              </tr>
              <tr>
                <td align="left">Given name</td>
                <td align="left">given</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">Additional name</td>
                <td align="left">given2</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">Honorific prefix</td>
                <td align="left">title</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">Honorific suffix</td>
                <td align="left">credential</td>
                <td align="left">Ignore one equal value for each value of the Generation component (see <xref target="vcard_updated_n"/>).</td>
              </tr>
              <tr>
                <td align="left">Secondary surname</td>
                <td align="left">surname2</td>
                <td align="left"/>
              </tr>
              <tr>
                <td align="left">Generation</td>
                <td align="left">generation</td>
                <td align="left"/>
              </tr>
            </tbody>
          </table>
          <t>Each comma-separated value in an N component converts to its own NameComponent of the same kind.  If the <xref target="vcard_param_jscomps">JSCOMPS</xref> parameter is set and valid, then the Name object's "isOrdered" property value is "true", and the "defaultSeparator" property and any "separator" NameComponent objects are set according to the parameter value.  The order in the "components" property <bcp14>MUST</bcp14> adhere to the order of the JSCOMPS parameter value.  If the JSCOMPS parameter is not set or not valid, then the Name object's "isOrdered" property value is "false", and the "defaultSeparator" property <bcp14>MUST NOT</bcp14> be set.  In this case, the order in the "components" property is implementation-specific; one option is to follow the order of values in the N structured value when read from left to right.</t>
          <t>If the SORT-AS parameter is set, then its structured value converts to the Name object's "sortAs" property according to <xref target="n_kind_conversion"/>.  An empty or non-existent component value indicates that no sort is defined for this kind.</t>
          <t>The path of the N property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "name/components".</t>
          <t>The following example illustrates how to convert the N property:</t>
          <figure anchor="test_vcard_prop_n">
            <name>N Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
N;SORT-AS="Stevenson,John Philip":Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.;;Jr.

--- JSContact:
"name": {
  "components":[
    { "kind": "surname", "value": "Stevenson" },
    { "kind": "given", "value": "John" },
    { "kind": "given2", "value": "Philip" },
    { "kind": "given2", "value": "Paul" },
    { "kind": "title", "value": "Dr." },
    { "kind": "credential", "value": "M.D." },
    { "kind": "credential", "value": "A.C.P." },
    { "kind": "generation", "value": "Jr." }
  ],
  "sortAs": {
    "surname": "Stevenson",
    "given": "John Philip"
  },
  "...": ""
}
]]></sourcecode>
          </figure>
          <t>The following example illustrates how to convert the N property of a person with two equal surnames.  For backwards compatibility with <xref target="RFC6350"/>, the "family name" component contains both surnames.  The "secondary surname" component contains the value "Pérez" once, so only one of the two equal values in the "family name" component is ignored (see <xref target="vcard_updated_n"/>):</t>
          <figure anchor="test_vcard_prop_n_equal_surnames">
            <name>N Conversion Example with Equal Surnames</name>
            <sourcecode><![CDATA[
--- vCard:
N:Pérez,Pérez;Ana;;;;Pérez;

--- JSContact:
"name": {
  "components":[
    { "kind": "surname", "value": "Pérez" },
    { "kind": "given", "value": "Ana" },
    { "kind": "surname2", "value": "Pérez" }
  ],
  "...": ""
}
]]></sourcecode>
          </figure>
          <t>See <xref target="vcard_param_jscomps_examples"/> for examples of how to use the JSCOMPS parameter for structured property values.</t>
        </section>
        <section anchor="vcard_prop_nickname">
          <name>NICKNAME</name>
          <t>The <xref target="RFC6350" section="6.2.3" sectionFormat="parens">NICKNAME property</xref> converts to a <xref target="RFC9553" section="2.2.2" sectionFormat="parens">Nickname object</xref>.  The converted object is set in the "nicknames" property of the Card object.  The NICKNAME property value converts to the "name" property of the Nickname object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the NICKNAME property:</t>
          <figure anchor="test_vcard_prop_nickname">
            <name>NICKNAME Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
NICKNAME:Johnny

--- JSContact:
"nicknames": {
   "NICK-1": {
    "name": "Johnny"
   }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_note">
          <name>NOTE</name>
          <t>The <xref target="RFC6350" section="6.7.2" sectionFormat="parens">NOTE property</xref> converts to a <xref target="RFC9553" section="2.8.3" sectionFormat="parens">Note object</xref>.  The converted object is set in the "notes" property of the Card object.  The NOTE property value converts to the "note" property of the Note object.  The ALTID and LANGUAGE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the NOTE property:</t>
          <figure anchor="test_vcard_prop_note">
            <name>NOTE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
NOTE;CREATED=20221123T150132Z;AUTHOR-NAME="John":
 Office hours are from 0800 to 1715 EST\, Mon-Fri.

--- JSContact:
"notes": {
  "NOTE-1" : {
     "note": "Office hours are from 0800 to 1715 EST, Mon-Fri.",
     "created": "2022-11-23T15:01:32Z",
     "author": {
       "name": "John"
     }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_org">
          <name>ORG</name>
          <t>The <xref target="RFC6350" section="6.6.4" sectionFormat="parens">ORG property</xref> converts to an <xref target="RFC9553" section="2.2.3" sectionFormat="parens">Organization object</xref>. The converted object is set in the "organizations" property of the Card object.  The organization name in the ORG property value converts to the "name" property of the Organization object. Any organizational unit names convert to the "units" property.</t>
          <t>Implementations <bcp14>MAY</bcp14> allow representation of organizational units without the organizational name.  In this case, the first component of the ORG value <bcp14>MUST</bcp14> be an empty string (e.g., "ORG:;DepartmentA").  The ALTID and LANGUAGE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The first item of the comma-separated SORT-AS parameter value converts to the Organization object's "sortAs" property.  The subsequent items convert to the "sortAs" property of the corresponding OrgUnit object.  The TYPE parameter converts according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The order of the elements in the "units" property is significant, and so is the order of the items in the SORT-AS parameter value (see <xref target="notation_conversion"/>).</t>
          <t>The path of the ORG property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "organizations/{id}/name", where "{id}" denotes the identifier of the Organization object.</t>
          <t>The following example illustrates how to convert the ORG property:</t>
          <figure anchor="test_vcard_prop_org">
            <name>ORG Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
ORG;SORT-AS="ABC":ABC\, Inc.;North American Division;Marketing

--- JSContact:
"organizations": {
  "ORG-1": {
    "name": "ABC, Inc.",
    "units":[
      { "name": "North American Division" },
      { "name": "Marketing" }
    ],
    "sortAs": "ABC"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_org_directory">
          <name>ORG-DIRECTORY</name>
          <t>The <xref target="RFC6715" section="2.4" sectionFormat="parens">ORG-DIRECTORY property</xref> converts to a <xref target="RFC9553" section="2.6.2" sectionFormat="parens">Directory object</xref>.  The converted object is set in the "directories" property of the Card object.  The "kind" property of the Directory object is set to "directory".  The ORG-DIRECTORY property value converts to the "uri" property of the Directory object.  The INDEX, PREF, and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the ORG-DIRECTORY property:</t>
          <figure anchor="test_vcard_prop_org_directory">
            <name>ORG-DIRECTORY Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
ORG-DIRECTORY;INDEX=1:https://directory.mycompany.example.com
ORG-DIRECTORY;PREF=1:ldap://ldap.tech.example/o=Tech,ou=Engineering

--- JSContact:
"directories": {
  "DIRECTORY-1": {
    "kind": "directory",
    "uri": "https://directory.mycompany.example.com",
    "listAs": 1
  },
  "DIRECTORY-2": {
    "kind": "directory",
    "uri": "ldap://ldap.tech.example/o=Tech,ou=Engineering",
    "pref": 1
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_photo">
          <name>PHOTO</name>
          <t>The <xref target="RFC6350" section="6.2.4" sectionFormat="parens">PHOTO property</xref> converts to a <xref target="RFC9553" section="2.6.4" sectionFormat="parens">Media object</xref>.  The converted object is set in the "media" property of the Card object.  The "kind" property of the Media object is set to "photo".  The PHOTO property value converts to the "uri" property of the Media object.  The PREF and MEDIATYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the PHOTO property:</t>
          <figure anchor="test_vcard_prop_photo">
            <name>PHOTO Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
PHOTO:https://www.example.com/pub/photos/jqpublic.gif

--- JSContact:
"media": {
   "PHOTO-1": {
     "kind": "photo",
     "uri": "https://www.example.com/pub/photos/jqpublic.gif"
   }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_prodid">
          <name>PRODID</name>
          <t>The <xref target="RFC6350" section="6.7.3" sectionFormat="parens">PRODID property</xref> converts to the "prodId" property of the Card object.</t>
          <t>The following example illustrates how to convert the PRODID property:</t>
          <figure anchor="test_vcard_prop_prodid">
            <name>PRODID Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
PRODID:ACME Contacts App version 1.23.5

--- JSContact:
"prodId": "ACME Contacts App version 1.23.5"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_pronouns">
          <name>PRONOUNS</name>
          <t>The <xref target="RFC9554" section="3.4" sectionFormat="parens">PRONOUNS property</xref> converts to a Pronouns object (<xref target="RFC9553" section="2.2.4"/>).  The converted object is set in the "pronouns" property of the SpeakToAs object, which is set in the "speakToAs" property of the Card object.  The PRONOUNS property value converts to the "pronouns" property of the Pronouns object.</t>
          <t>The following example illustrates how to convert the PRONOUNS property:</t>
          <figure anchor="test_vcard_prop_pronouns">
            <name>PRONOUNS Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
PRONOUNS;PREF=2:they/them
PRONOUNS;PREF=1:xe/xir

--- JSContact:
"speakToAs": {
  "pronouns": {
    "PRONOUNS-1": {
      "pronouns": "they/them",
      "pref": 2
    },
    "PRONOUNS-2": {
      "pronouns": "xe/xir",
      "pref": 1
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_related">
          <name>RELATED</name>
          <t>The <xref target="RFC6350" section="6.6.6" sectionFormat="parens">RELATED property</xref> converts to the "relatedTo" property of the Card object.  The RELATED property value becomes a key in the "relatedTo" property, and the corresponding value is a <xref target="RFC9553" section="2.1.8" sectionFormat="parens">Relation object</xref>.  The TYPE parameters convert to the "relation" property of the Relation object.  Any other parameters convert as defined in <xref target="jscontact_prop_vcard"/>.</t>
          <t>The path of the RELATED property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "relatedTo/{value}", where "{value}" denotes the RELATED property value.</t>
          <t>The following example illustrates how to convert the RELATED property:</t>
          <figure anchor="test_vcard_prop_related">
            <name>RELATED Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
RELATED;TYPE=contact:https://example.com/directory/john.vcf
RELATED;VALUE=text:Please contact my deputy John for any inquiries.

--- JSContact:
"relatedTo" : {
  "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6" : {
    "relation" : {
      "friend" : true
    }
  },
  "https://example.com/directory/john.vcf" : {
    "relation" : {
      "contact" : true
    }
  },
  "Please contact my deputy John for any inquiries." : {
    "relation" : { }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_rev">
          <name>REV</name>
          <t>The <xref target="RFC6350" section="6.7.4" sectionFormat="parens">REV property</xref> converts to the "updated" property of the Card object.</t>
          <t>The following example illustrates how to convert the REV property:</t>
          <figure anchor="test_vcard_prop_rev">
            <name>REV Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
REV:19951031T222710Z

--- JSContact:
"updated": "1995-10-31T22:27:10Z"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_role">
          <name>ROLE</name>
          <t>The <xref target="RFC6350" section="6.6.2" sectionFormat="parens">ROLE property</xref> converts to a <xref target="RFC9553" section="2.2.5" sectionFormat="parens">Title object</xref>.  The converted object is set in the "titles" property of the Card object.  The "kind" property of the Title object is set to "role".  The ROLE property value converts to the "name" property of the Title object.</t>
          <t>If the vCard contains an ORG property and either the ROLE and ORG property are not part of a vCard property group, or they are both in the same group, then the "organizationId" property of the Title object is set to the identifier to which the ORG property converts in the "organizations" property of the Card object.  The ALTID and LANGUAGE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the ROLE property:</t>
          <figure anchor="test_vcard_prop_role">
            <name>ROLE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
group1.ROLE:Project Leader
group1.ORG:ABC, Inc.

--- JSContact:
"titles": {
  "ROLE-1": {
    "kind": "role",
    "name": "Project Leader",
    "organizationId": "ORG-1"
  }
},
"organizations": {
  "ORG-1": {
    "name": "ABC, Inc."
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_socialprofile">
          <name>SOCIALPROFILE</name>
          <t>The <xref target="RFC9554" section="3.5" sectionFormat="parens">SOCIALPROFILE property</xref> converts to an <xref target="RFC9553" section="2.3.2" sectionFormat="parens">OnlineService object</xref>.  The converted object is set in the "onlineServices" property of the Card object.  If the SOCIALPROFILE property value is of type URI, then it converts to the "uri" property of the OnlineService object; otherwise it converts to the "user" property.  The SERVICE-TYPE, USERNAME, PREF, and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>Implementations <bcp14>MAY</bcp14> use the <xref target="jscontact_prop_vcard">"vCard" property</xref> to indicate that the OnlineService object was converted from the SOCIALPROFILE property.</t>
          <t>The following example illustrates how to convert the SOCIALPROFILE property:</t>
          <figure anchor="test_vcard_prop_socialprofile">
            <name>SOCIALPROFILE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
SOCIALPROFILE;SERVICE-TYPE=Mastodon:https://example.com/@foo

--- JSContact:
"onlineServices": {
  "OS-1": {
    "service": "Mastodon",
    "uri": "https://example.com/@foo"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_sound">
          <name>SOUND</name>
          <t>The <xref target="RFC6350" section="6.7.5" sectionFormat="parens">SOUND property</xref> converts to a <xref target="RFC9553" section="2.6.4" sectionFormat="parens">Media object</xref>.  The converted object is set in the "media" property of the Card object.  The "kind" property of the Media object is set to "sound".  The SOUND property value converts to the "uri" property of the Media object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the SOUND property:</t>
          <figure anchor="test_vcard_prop_sound">
            <name>SOUND Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
SOUND:CID:JOHNQPUBLIC.19960229T080000.xyzMail@example.com

--- JSContact:
"media": {
  "SOUND-1": {
    "kind": "sound",
    "uri": "CID:JOHNQPUBLIC.19960229T080000.xyzMail@example.com"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_source">
          <name>SOURCE</name>
          <t>The <xref target="RFC6350" section="6.1.3" sectionFormat="parens">SOURCE property</xref> converts to a <xref target="RFC9553" section="2.6.2" sectionFormat="parens">Directory object</xref>.  The converted object is set in the "directories" property of the Card object.  The "kind" property of the Directory object is set to "entry".  The SOURCE property value converts to the "uri" property of the Directory object.  The PREF and MEDIATYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the SOURCE property:</t>
          <figure anchor="test_vcard_prop_source">
            <name>SOURCE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
SOURCE:https://dir.example.com/addrbook/jdoe/Jean%20Dupont.vcf

--- JSContact:
"directories": {
   "ENTRY-1": {
     "kind": "entry",
     "uri": "https://dir.example.com/addrbook/jdoe/Jean%20Dupont.vcf"
   }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_tel">
          <name>TEL</name>
          <t>The <xref target="RFC6350" section="6.4.1" sectionFormat="parens">TEL property</xref> converts to a <xref target="RFC9553" section="2.3.3" sectionFormat="parens">Phone object</xref>.  The converted object is set in the "phones" property of the Card object.</t>
          <t>The TEL-specific values of the TYPE parameter convert to the "features" property keys as outlined in <xref target="tel_type_conversion"/>.  Note that <xref target="RFC6350" sectionFormat="of" section="6.4.1"/> defines the default type to be "voice", but the default Phone object's "features" property is absent by default.  Accordingly, an implementation <bcp14>SHOULD</bcp14> only set the Phone object's "features" property if the TEL property actually has a TEL-specific TYPE parameter set.</t>
          <table anchor="tel_type_conversion">
            <name>TEL TYPE Conversion</name>
            <thead>
              <tr>
                <th align="left">TYPE value</th>
                <th align="left">Phone feature</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">cell</td>
                <td align="left">mobile</td>
              </tr>
              <tr>
                <td align="left">fax</td>
                <td align="left">fax</td>
              </tr>
              <tr>
                <td align="left">main-number</td>
                <td align="left">main-number</td>
              </tr>
              <tr>
                <td align="left">pager</td>
                <td align="left">pager</td>
              </tr>
              <tr>
                <td align="left">text</td>
                <td align="left">text</td>
              </tr>
              <tr>
                <td align="left">textphone</td>
                <td align="left">textphone</td>
              </tr>
              <tr>
                <td align="left">video</td>
                <td align="left">video</td>
              </tr>
              <tr>
                <td align="left">voice</td>
                <td align="left">voice</td>
              </tr>
            </tbody>
          </table>
          <t>The TEL property value converts to the "number" property of the Phone object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the TEL property:</t>
          <figure anchor="test_vcard_prop_tel">
            <name>TEL Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555
TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67

--- JSContact:
"phones": {
  "PHONE-1": {
    "contexts": { "private": true },
    "features": { "voice": true },
    "number": "tel:+1-555-555-5555;ext=5555",
    "pref": 1
  },
  "PHONE-2": {
    "contexts": { "private": true },
    "number": "tel:+33-01-23-45-67"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_title">
          <name>TITLE</name>
          <t>The <xref target="RFC6350" section="6.6.1" sectionFormat="parens">TITLE property</xref> converts to a <xref target="RFC9553" section="2.2.5" sectionFormat="parens">Title object</xref>.  The converted object is set in the "titles" property of the Card object.  The TITLE property value converts to the "name" property of the Title object. The same rules as in <xref target="vcard_prop_role"/> apply for setting the Title object's "organizationId" property.  The ALTID and LANGUAGE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the TITLE property:</t>
          <figure anchor="test_vcard_prop_title">
            <name>TITLE Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
TITLE:Research Scientist

--- JSContact:
"titles": {
  "TITLE-1": {
    "kind": "title",
    "name": "Research Scientist"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_tz">
          <name>TZ</name>
          <t>The <xref target="RFC6350" section="6.5.1" sectionFormat="parens">TZ property</xref> converts to an <xref target="RFC9553" section="2.5.1" sectionFormat="parens">Address object</xref>.  The converted object is set in the "addresses" property of the Card object. The TZ property value converts to the "timeZone" property of the Address object. See <xref target="vcard_prop_adr"/> how to convert the TZ property together with the ADR and GEO property.</t>
          <t>A value of type TEXT converts verbatim. A value of type UTC-OFFSET converts if the offset has zero minutes and the hour offset is between -12 and +14, both inclusively:</t>
          <ul>
            <li>If the hour offset is zero, use the time zone name "Etc/UTC".</li>
            <li>Otherwise, construct the time zone name with "Etc/GMT" suffixed with the string representation of the reversed sign hour offset, including the sign but excluding leading zeros and minutes.  For example, the UTC offset value "-0500" converts to "Etc/GMT+5".</li>
          </ul>
          <t>Any other UTC-OFFSET property value, or any other value type, does not convert to JSContact.</t>
          <t>The path of the TZ property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "addresses/{id}/timeZone", where "{id}" denotes the identifier of the Address object.</t>
        </section>
        <section anchor="vcard_prop_uid">
          <name>UID</name>
          <t>The <xref target="RFC6350" section="6.7.6" sectionFormat="parens">UID property</xref> converts to the "uid" property of the Card object.</t>
          <t>Implementations <bcp14>MAY</bcp14> use the <xref target="jscontact_prop_vcard">"vCard" property</xref> to preserve the value type of the UID property.</t>
          <t>The following examples illustrate how to convert the UID property:</t>
          <figure anchor="test_vcard_prop_uid">
            <name>UID Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

--- JSContact:
"uid": "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"
]]></sourcecode>
          </figure>
          <figure anchor="test_vcard_prop_uid_valuetype">
            <name>UID Conversion Example with Value Type</name>
            <sourcecode><![CDATA[
--- vCard:
UID;VALUE=text:77A50EF0-54CA-40B0-B878-B3580B4100A2

--- JSContact:
"uid": "77A50EF0-54CA-40B0-B878-B3580B4100A2",
"vCard": {
  "convertedProperties": {
    "uid": {
      "name": "uid",
      "valueType": "text"
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_url">
          <name>URL</name>
          <t>The <xref target="RFC6350" section="6.7.8" sectionFormat="parens">URL property</xref> converts to a <xref target="RFC9553" section="2.6.3" sectionFormat="parens">Link object</xref>.  The converted object is set in the "links" property of the Card object.  The URL property value converts to the "uri" property of the Link object.  The PREF and TYPE parameters convert according to the rules defined in <xref target="vcard_parameters"/>.</t>
          <t>The following example illustrates how to convert the URL property:</t>
          <figure anchor="test_vcard_prop_url">
            <name>URL Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
URL:https://example.org/restaurant.french/~chezchic.html

--- JSContact:
"links": {
  "LINK-1": {
    "uri": "https://example.org/restaurant.french/~chezchic.html"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_version">
          <name>VERSION</name>
          <t>The <xref target="RFC6350" section="6.7.9" sectionFormat="parens">VERSION property</xref> does not convert to JSContact.</t>
        </section>
        <section anchor="vcard_prop_xablabel">
          <name>X-ABLabel</name>
          <t>The X-ABLabel property is experimental but widely in use in existing vCard data.  The X-ABLabel property is preceded by a vCard property group name, and it converts to the JSContact object that was converted from a vCard property of the same group.  The X-ABLabel property value converts to the "label" property of that object.</t>
          <t>The group name is not preserved; implementations are free to choose any unique group name when converting back to vCard.  For an example on how to preserve the group name, see <xref target="vcard_param_group"/>. The path of the X-ABLabel property in the <xref target="jscontact_prop_vcard" sectionFormat="parens">"convertedProperties" property</xref> is "*/label", where "*" denotes the path of the object on which the label is set.</t>
          <t>The following example illustrates how to convert the X-ABLabel property:</t>
          <figure anchor="test_vcard_prop_xablabel">
            <name>X-ABLabel Conversion Example</name>
            <sourcecode><![CDATA[
--- vCard:
item1.TEL;VALUE=uri:tel:+1-555-555-5555
item1.X-ABLabel:foo

--- JSContact:
"phones": {
  "p1": {
    "number": "tel:+1-555-555-5555",
    "label": "foo"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vcard_prop_xml">
          <name>XML</name>
          <t>The <xref target="RFC6350" section="6.1.5" sectionFormat="parens">XML property</xref> does not convert to JSContact.</t>
        </section>
      </section>
    </section>
    <section anchor="convert_jscontact_to_vcard">
      <name>Converting JSContact to vCard</name>
      <t>This section defines the conversion rules for each JSContact object type. Each subsection lists the properties of one object type and the relevant document sections for their conversion to vCard.</t>
      <section anchor="convert_jscontact_to_vcard_new_address">
        <name>Address</name>
        <t>The Address object converts to the ADR property. Each AddressComponent object in the <xref target="RFC9553" section="2.5.1.1" sectionFormat="parens">"components" property</xref> converts to a component in the structured value of the ADR property.
</t>
        <table anchor="address_component_conversion">
          <name>AddressComponent conversion</name>
          <thead>
            <tr>
              <th align="left">AddressComponent kind</th>
              <th align="left">ADR component</th>
              <th align="left">Remarks</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">apartment</td>
              <td align="left">apartment</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">block</td>
              <td align="left">block</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">building</td>
              <td align="left">building</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">country</td>
              <td align="left">country</td>
              <td align="left">
                <xref target="vcard_prop_adr"/>
              </td>
            </tr>
            <tr>
              <td align="left">direction</td>
              <td align="left">direction</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">district</td>
              <td align="left">district</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">floor</td>
              <td align="left">floor</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">landmark</td>
              <td align="left">landmark</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">locality</td>
              <td align="left">locality</td>
              <td align="left">
                <xref target="vcard_prop_adr"/>
              </td>
            </tr>
            <tr>
              <td align="left">name</td>
              <td align="left">street name or street address</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">number</td>
              <td align="left">street number</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">postcode</td>
              <td align="left">postal code</td>
              <td align="left">
                <xref target="vcard_prop_adr"/>
              </td>
            </tr>
            <tr>
              <td align="left">postOfficeBox</td>
              <td align="left">post office box</td>
              <td align="left">
                <xref target="vcard_prop_adr"/>
              </td>
            </tr>
            <tr>
              <td align="left">region</td>
              <td align="left">region</td>
              <td align="left">
                <xref target="vcard_prop_adr"/>
              </td>
            </tr>
            <tr>
              <td align="left">room</td>
              <td align="left">room</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">subdistrict</td>
              <td align="left">subdistrict</td>
              <td align="left"><xref target="vcard_prop_adr"/>, and remarks below</td>
            </tr>
          </tbody>
        </table>
        <t>The following remarks aim for interoperability with vCard implementations that only support the ADR property as defined in <xref target="RFC6350"/>:</t>
        <ul>
          <li>
            <t>If the address contains at least one "name" AddressComponent but none of kind "number", then these address components convert to the ADR "street address" component defined in <xref target="RFC6350"/>.  They do not convert to the "street name" component defined in <xref target="RFC9554"/>.</t>
          </li>
          <li>
            <t>If the address contains at least one "number" AddressComponent and zero or more of kind "name", then the "name" and "number" AddressComponents convert to the "street name" and "street number" ADR components introduced in <xref target="RFC9554"/>.  If both kinds are set, implementations <bcp14>SHOULD</bcp14> combine the "street name" and "street number" component values to set the ADR "street address" component defined in <xref target="RFC6350"/>, separated by a single space character (U+0020).  Whether the street number precedes or follows a street name differs by country.  If the "isOrdered" property value of the Address object is "true", then the values combine in the order of the "components" property.  Otherwise, the order is implementation-specific, for example, based on the "countryCode" property.</t>
          </li>
          <li>
            <t>Implementations <bcp14>SHOULD NOT</bcp14> set the components defined in <xref target="RFC9554"/> if all their values are empty.  Readers that implement the original definition in <xref target="RFC9554"/> or the conversion rules in <xref target="RFC9555"/> might otherwise ignore the "street address" and "extended address" components.</t>
          </li>
        </ul>
        <t>The other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_address">
          <name>Properties of the Address object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>coordinates</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>GEO</td>
              <td>Sections <xref target="vcard_param_geo" format="counter"/> and <xref target="vcard_prop_geo" format="counter"/>, and remarks below</td>
            </tr>
            <tr>
              <td>countryCode</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>CC</td>
              <td>
                <xref target="vcard_param_cc"/>
              </td>
            </tr>
            <tr>
              <td>defaultSeparator</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>JSCOMPS</td>
              <td>
                <xref target="vcard_param_jscomps"/>
              </td>
            </tr>
            <tr>
              <td>full</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>LABEL</td>
              <td>
                <xref target="vcard_param_label"/>
              </td>
            </tr>
            <tr>
              <td>isOrdered</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>JSCOMPS</td>
              <td>
                <xref target="vcard_param_jscomps"/>
              </td>
            </tr>
            <tr>
              <td>phoneticScript</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>SCRIPT</td>
              <td>
                <xref target="vcard_param_script"/>
              </td>
            </tr>
            <tr>
              <td>phoneticSystem</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>PHONETIC</td>
              <td>
                <xref target="vcard_param_phonetic"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
            <tr>
              <td>timeZone</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>TZ</td>
              <td>Sections <xref target="vcard_param_tz" format="counter"/> and <xref target="vcard_prop_tz" format="counter"/>, and remarks below</td>
            </tr>
          </tbody>
        </table>
        <t>Remarks:</t>
        <ul>
          <li>The "coordinates" and "timeZone" properties <bcp14>SHOULD</bcp14> convert to the GEO and TZ parameters, but implementations <bcp14>MAY</bcp14> alternatively convert them to the same-named properties e.g. to preserve original vCard data.</li>
        </ul>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_anniversary">
        <name>Anniversary</name>
        <t>The Anniversary object converts to one of the following properties, determined by the Anniversary object's "kind" property value:</t>
        <ul>
          <li>If the "kind" is "wedding" and the Anniversary object's "date" property is set, then it converts to the <xref target="vcard_prop_anniversary">ANNIVERSARY</xref> property. How to convert the "place" property is implementation-specific.</li>
          <li>If the "kind" is "birth", then the "date" property value converts to the <xref target="vcard_prop_bday">BDAY</xref> property and the "place" property converts to the <xref target="vcard_prop_birthplace">BIRTHPLACE</xref> property.</li>
          <li>If the "kind" is "death", then the "date" property value converts to the <xref target="vcard_prop_deathdate">DEATHDATE</xref> property and the "place" property converts to the <xref target="vcard_prop_deathplace">DEATHPLACE</xref> property.</li>
        </ul>
        <t>A "date" property value of type PartialDate converts to the DATE property value type. The "calendarScale" property converts to the CALSCALE parameter. A "date" property value of type Timestamp converts to the TIMESTAMP property value type by converting the "utc" property. How to convert a "place" property value having any Address property other than the "full" property set is implementation-specific.</t>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_calendar">
        <name>Calendar</name>
        <t>The Calendar object converts to one of the following properties, determined by the Calendar object's "kind" property value. If the "kind" is "calendar" then it converts to the <xref target="vcard_prop_caluri">CALURI</xref> property. If the "kind" is "freeBusy" then it converts to the <xref target="vcard_prop_fburl">FBURL</xref> property.</t>
        <t>Its "uri" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_calendar">
          <name>Properties of the Calendar object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.4.1" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.4.1" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>mediaType</td>
              <td>
                <xref target="RFC9553" section="2.4.1" sectionFormat="comma"/>
              </td>
              <td>MEDIATYPE</td>
              <td>
                <xref target="vcard_param_mediatype"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.4.1" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_card">
        <name>Card</name>
        <t>The Card object converts to a <xref target="RFC6350">vCard</xref>.</t>
        <t>Its properties other than the "localizations" property convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_card">
          <name>Properties of the Card object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Property (or Parameter)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>addresses</td>
              <td>
                <xref target="RFC9553" section="2.5.1.1" sectionFormat="comma"/>
              </td>
              <td>ADR</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_address">Address object</xref>
              </td>
            </tr>
            <tr>
              <td>anniversaries</td>
              <td>
                <xref target="RFC9553" section="2.8.1" sectionFormat="comma"/>
              </td>
              <td>ANNIVERSARY</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_anniversary">Anniversary object</xref>
              </td>
            </tr>
            <tr>
              <td>calendars</td>
              <td>
                <xref target="RFC9553" section="2.4.1" sectionFormat="comma"/>
              </td>
              <td>CALURI, FBURL</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_calendar">Calendar object</xref>
              </td>
            </tr>
            <tr>
              <td>created</td>
              <td>
                <xref target="RFC9553" section="2.1.3" sectionFormat="comma"/>
              </td>
              <td>CREATED</td>
              <td>
                <xref target="vcard_prop_created"/>
              </td>
            </tr>
            <tr>
              <td>cryptoKeys</td>
              <td>
                <xref target="RFC9553" section="2.6.1" sectionFormat="comma"/>
              </td>
              <td>KEY</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_crypto_key">CryptoKey object</xref>
              </td>
            </tr>
            <tr>
              <td>directories</td>
              <td>
                <xref target="RFC9553" section="2.6.2" sectionFormat="comma"/>
              </td>
              <td>SOURCE, ORG-DIRECTORY</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_directory">Directory object</xref>
              </td>
            </tr>
            <tr>
              <td>emails</td>
              <td>
                <xref target="RFC9553" section="2.3.1" sectionFormat="comma"/>
              </td>
              <td>EMAIL</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_email_address">EmailAddress object</xref>
              </td>
            </tr>
            <tr>
              <td>keywords</td>
              <td>
                <xref target="RFC9553" section="2.8.2" sectionFormat="comma"/>
              </td>
              <td>CATEGORIES</td>
              <td>
                <xref target="vcard_prop_categories"/>
              </td>
            </tr>
            <tr>
              <td>kind</td>
              <td>
                <xref target="RFC9553" section="2.1.4" sectionFormat="comma"/>
              </td>
              <td>KIND</td>
              <td>
                <xref target="vcard_prop_kind"/>
              </td>
            </tr>
            <tr>
              <td>language</td>
              <td>
                <xref target="RFC9553" section="2.1.5" sectionFormat="comma"/>
              </td>
              <td>LANGUAGE</td>
              <td>
                <xref target="vcard_prop_language"/>
              </td>
            </tr>
            <tr>
              <td>links</td>
              <td>
                <xref target="RFC9553" section="2.6.3" sectionFormat="comma"/>
              </td>
              <td>CONTACT-URI, URL</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_link">Link object</xref>
              </td>
            </tr>
            <tr>
              <td>media</td>
              <td>
                <xref target="RFC9553" section="2.6.4" sectionFormat="comma"/>
              </td>
              <td>PHOTO, LOGO, SOUND</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_media">Media object</xref>
              </td>
            </tr>
            <tr>
              <td>members</td>
              <td>
                <xref target="RFC9553" section="2.1.6" sectionFormat="comma"/>
              </td>
              <td>MEMBER</td>
              <td>
                <xref target="vcard_prop_member"/>
              </td>
            </tr>
            <tr>
              <td>name</td>
              <td>
                <xref target="RFC9553" section="2.2.1.1" sectionFormat="comma"/>
              </td>
              <td>N</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_name">Name object</xref>
              </td>
            </tr>
            <tr>
              <td>nicknames</td>
              <td>
                <xref target="RFC9553" section="2.2.2" sectionFormat="comma"/>
              </td>
              <td>NICKNAME</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_nickname">Nickname object</xref>
              </td>
            </tr>
            <tr>
              <td>notes</td>
              <td>
                <xref target="RFC9553" section="2.8.3" sectionFormat="comma"/>
              </td>
              <td>NOTE</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_note">Note object</xref>
              </td>
            </tr>
            <tr>
              <td>onlineServices</td>
              <td>
                <xref target="RFC9553" section="2.3.2" sectionFormat="comma"/>
              </td>
              <td>IMPP, SOCIALPROFILE</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_online_service">OnlineService object</xref>
              </td>
            </tr>
            <tr>
              <td>organizations</td>
              <td>
                <xref target="RFC9553" section="2.2.3" sectionFormat="comma"/>
              </td>
              <td>ORG</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_organization">Organization object</xref>
              </td>
            </tr>
            <tr>
              <td>personalInfo</td>
              <td>
                <xref target="RFC9553" section="2.8.4" sectionFormat="comma"/>
              </td>
              <td>EXPERTISE, HOBBY, INTEREST</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_personal_info">PersonalInfo object</xref>
              </td>
            </tr>
            <tr>
              <td>phones</td>
              <td>
                <xref target="RFC9553" section="2.3.3" sectionFormat="comma"/>
              </td>
              <td>TEL</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_phone">Phone object</xref>
              </td>
            </tr>
            <tr>
              <td>preferredLanguages</td>
              <td>
                <xref target="RFC9553" section="2.3.4" sectionFormat="comma"/>
              </td>
              <td>LANG</td>
              <td>
                <xref target="vcard_prop_lang"/>
              </td>
            </tr>
            <tr>
              <td>prodId</td>
              <td>
                <xref target="RFC9553" section="2.1.7" sectionFormat="comma"/>
              </td>
              <td>PRODID</td>
              <td>
                <xref target="vcard_prop_prodid"/>
              </td>
            </tr>
            <tr>
              <td>relatedTo</td>
              <td>
                <xref target="RFC9553" section="2.1.8" sectionFormat="comma"/>
              </td>
              <td>RELATED</td>
              <td>
                <xref target="vcard_prop_related"/>
              </td>
            </tr>
            <tr>
              <td>schedulingAddresses</td>
              <td>
                <xref target="RFC9553" section="2.4.2" sectionFormat="comma"/>
              </td>
              <td>CALADRURI</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_scheduling_address">SchedulingAddress object</xref>
              </td>
            </tr>
            <tr>
              <td>speakToAs</td>
              <td>
                <xref target="RFC9553" section="2.2.4" sectionFormat="comma"/>
              </td>
              <td>GRAMGENDER, PRONOUNS</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_speak_to_as">SpeakToAs object</xref>
              </td>
            </tr>
            <tr>
              <td>titles</td>
              <td>
                <xref target="RFC9553" section="2.2.5" sectionFormat="comma"/>
              </td>
              <td>TITLE</td>
              <td>
                <xref target="convert_jscontact_to_vcard_new_title">Title object</xref>
              </td>
            </tr>
            <tr>
              <td>uid</td>
              <td>
                <xref target="RFC9553" section="2.1.9" sectionFormat="comma"/>
              </td>
              <td>UID</td>
              <td>
                <xref target="vcard_prop_uid"/>
              </td>
            </tr>
            <tr>
              <td>updated</td>
              <td>
                <xref target="RFC9553" section="2.1.10" sectionFormat="comma"/>
              </td>
              <td>REV</td>
              <td>
                <xref target="vcard_prop_rev"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>The Card object's "@type" and "version" properties do not convert to a vCard property; a vCard generated from a Card always has a VERSION property value of "4.0" (see <xref target="vcard_prop_version"/>).</t>
        <t>Converting the "localizations" property is implementation-specific (see <xref target="vcard_param_language"/>).  For the common case of localized property values, one option is to apply each localization's PatchObject to the non-localized Card and convert each patched JSContact object to a vCard property using the rules outlined in <xref target="jscontact_to_vcard_props_card"/>.  The <xref target="vcard_param_language">LANGUAGE parameter</xref> of the resulting property is set to the localization's language tag, and its <xref target="vcard_param_altid">ALTID parameter</xref> value equals that of the non-localized vCard property.</t>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_crypto_key">
        <name>CryptoKey</name>
        <t>The CryptoKey object converts to the <xref target="vcard_prop_key">KEY property</xref>.</t>
        <t>Its "uri" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_crypto_key">
          <name>Properties of the CryptoKey object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.6.1" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.6.1" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>mediaType</td>
              <td>
                <xref target="RFC9553" section="2.6.1" sectionFormat="comma"/>
              </td>
              <td>MEDIATYPE</td>
              <td>
                <xref target="vcard_param_mediatype"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.6.1" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_directory">
        <name>Directory</name>
        <t>The Directory object converts to one of the following properties, determined by the Directory object's "kind" property value. If the "kind" is "entry" then it converts to the <xref target="vcard_prop_source">SOURCE</xref> property. If the "kind" is "directory" then it converts to the <xref target="vcard_prop_org_directory">ORG-DIRECTORY</xref> property.</t>
        <t>Its "uri" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_directory">
          <name>Properties of the Directory object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.6.2" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.6.2" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>listAs</td>
              <td>
                <xref target="RFC9553" section="2.6.2" sectionFormat="comma"/>
              </td>
              <td>INDEX</td>
              <td>
                <xref target="vcard_param_index"/>
              </td>
            </tr>
            <tr>
              <td>mediaType</td>
              <td>
                <xref target="RFC9553" section="2.6.2" sectionFormat="comma"/>
              </td>
              <td>MEDIATYPE</td>
              <td>
                <xref target="vcard_param_mediatype"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.6.2" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_email_address">
        <name>EmailAddress</name>
        <t>The EmailAddress object converts to the <xref target="vcard_prop_email">EMAIL</xref> property.</t>
        <t>Its "address" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_email_address">
          <name>Properties of the EmailAddress object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.3.1" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.3.1" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.3.1" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_language_pref">
        <name>LanguagePref</name>
        <t>The LanguagePref object converts to the <xref target="vcard_prop_lang">LANG property</xref>.</t>
        <t>Its "language" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_language_pref">
          <name>Properties of the LanguagePref object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.3.4" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.3.4" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_link">
        <name>Link</name>
        <t>The Link object converts to one of the following properties, determined by the Link object's "kind" property value. If the "kind" property is not set then it converts to the <xref target="vcard_prop_url">URL property</xref>. If the "kind" is "contact" then it converts to the <xref target="vcard_prop_contact_uri">CONTACT-URI</xref> property.</t>
        <t>Its "uri" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_link">
          <name>Properties of the Link object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.6.3" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.6.3" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>mediaType</td>
              <td>
                <xref target="RFC9553" section="2.6.3" sectionFormat="comma"/>
              </td>
              <td>MEDIATYPE</td>
              <td>
                <xref target="vcard_param_mediatype"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.6.3" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_media">
        <name>Media</name>
        <t>The Media object converts to one of the following properties, determined by the Media object's "kind" property value. If the "kind" is "photo" then it converts to the <xref target="vcard_prop_photo">PHOTO property</xref>. If the "kind" is "logo" then it converts to the <xref target="vcard_prop_logo">LOGO property</xref>. If the "kind" is "sound" then it converts to the <xref target="vcard_prop_sound">SOUND property</xref>.</t>
        <t>Its "uri" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_media">
          <name>Properties of the Media object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.6.4" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.6.4" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>mediaType</td>
              <td>
                <xref target="RFC9553" section="2.6.4" sectionFormat="comma"/>
              </td>
              <td>MEDIATYPE</td>
              <td>
                <xref target="vcard_param_mediatype"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.6.4" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_name">
        <name>Name</name>
        <t>The Name object converts to the <xref target="vcard_prop_n">N property</xref>. Each NameComponent object in the <xref target="RFC9553" section="2.2.1.1" sectionFormat="parens">"components" property</xref> converts to a component in the structured value of the N property.</t>
        <table anchor="name_component_conversion">
          <name>NameComponent conversion</name>
          <thead>
            <tr>
              <th align="left">NameComponent kind</th>
              <th align="left">N component</th>
              <th align="left">Remarks</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">credential</td>
              <td align="left">Honorific suffix</td>
              <td align="left">
                <xref target="vcard_prop_n"/>
              </td>
            </tr>
            <tr>
              <td align="left">generation</td>
              <td align="left">Generation</td>
              <td align="left"><xref target="vcard_prop_n"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">given</td>
              <td align="left">Given name</td>
              <td align="left">
                <xref target="vcard_prop_n"/>
              </td>
            </tr>
            <tr>
              <td align="left">given2</td>
              <td align="left">Additional name</td>
              <td align="left">
                <xref target="vcard_prop_n"/>
              </td>
            </tr>
            <tr>
              <td align="left">surname</td>
              <td align="left">Family name</td>
              <td align="left">
                <xref target="vcard_prop_n"/>
              </td>
            </tr>
            <tr>
              <td align="left">surname2</td>
              <td align="left">Secondary surname</td>
              <td align="left"><xref target="vcard_prop_n"/>, and remarks below</td>
            </tr>
            <tr>
              <td align="left">title</td>
              <td align="left">Honorific prefix</td>
              <td align="left">
                <xref target="vcard_prop_n"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>The following remarks aim for interoperability with vCard implementations that only support the N property as defined in <xref target="RFC6350"/>:</t>
        <ul>
          <li>
            <t>In addition to converting the "surname2" kind to the "Secondary surname" component, implementations <bcp14>SHOULD</bcp14> also append the value to the "Family name" component.  Also see <xref target="vcard_updated_n"/>.</t>
          </li>
          <li>
            <t>In addition to converting the "generation" kind to the "Generation" component, implementations <bcp14>SHOULD</bcp14> also append the value to the "Honorific suffix" component.  Also see <xref target="vcard_updated_n"/>.</t>
          </li>
          <li>
            <t>Implementations <bcp14>SHOULD NOT</bcp14> set the "Secondary surname" and "Generation" components if both their values are empty (see <xref target="vcard_updated_n"/>).</t>
          </li>
        </ul>
        <t>The "full" property converts to the <xref target="vcard_prop_fn">FN property</xref>.</t>
        <t>The "full" property is optional, but the FN property is defined to be mandatory in <xref target="RFC6350"/>. How to set the FN property if the "full" property is not set is implementation-specific. Implementations <bcp14>MAY</bcp14> derive the full name from the NameComponents objects.  If the "isOrdered" property value is "true", then this can be done by concatenating the name component values.  Alternatively, an implementation can choose any other heuristic to generate the full name from its components such as <xref target="CLDRPersonName"/>. If the FN property value is derived, implementations <bcp14>SHOULD</bcp14> set the <xref target="RFC9554" section="4.4" sectionFormat="parens">DERIVED parameter</xref>.</t>
        <t>The other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_name">
          <name>Properties of the Name object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>defaultSeparator</td>
              <td>
                <xref target="RFC9553" section="2.2.1.1" sectionFormat="comma"/>
              </td>
              <td>JSCOMPS</td>
              <td>
                <xref target="vcard_param_jscomps"/>
              </td>
            </tr>
            <tr>
              <td>phoneticScript</td>
              <td>
                <xref target="RFC9553" section="2.2.1.1" sectionFormat="comma"/>
              </td>
              <td>SCRIPT</td>
              <td>
                <xref target="vcard_param_script"/>
              </td>
            </tr>
            <tr>
              <td>phoneticSystem</td>
              <td>
                <xref target="RFC9553" section="2.2.1.1" sectionFormat="comma"/>
              </td>
              <td>PHONETIC</td>
              <td>
                <xref target="vcard_param_phonetic"/>
              </td>
            </tr>
            <tr>
              <td>isOrdered</td>
              <td>
                <xref target="RFC9553" section="2.2.1.1" sectionFormat="comma"/>
              </td>
              <td>JSCOMPS</td>
              <td>
                <xref target="vcard_param_jscomps"/>
              </td>
            </tr>
            <tr>
              <td>sortAs</td>
              <td>
                <xref target="RFC9553" section="2.2.1.1" sectionFormat="comma"/>
              </td>
              <td>SORT-AS</td>
              <td>
                <xref target="vcard_param_sort_as"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_nickname">
        <name>Nickname</name>
        <t>The Nickname object converts to <xref target="vcard_prop_nickname">NICKNAME property</xref>.</t>
        <t>Its "name" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_nickname">
          <name>Properties of the Nickname object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.2.2" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.2.2" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_note">
        <name>Note</name>
        <t>The Note object converts to the <xref target="vcard_prop_note">NOTE property</xref>.</t>
        <t>Its "note" property converts to the property value.</t>
        <t>The Author object set as the value of its "author" property converts as follows:</t>
        <table anchor="jscontact_to_vcard_props_author">
          <name>Properties of the Author object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>name</td>
              <td>
                <xref target="RFC9553" section="2.8.3" sectionFormat="comma"/>
              </td>
              <td>AUTHOR-NAME</td>
              <td>
                <xref target="vcard_param_author_name"/>
              </td>
            </tr>
            <tr>
              <td>uri</td>
              <td>
                <xref target="RFC9553" section="2.8.3" sectionFormat="comma"/>
              </td>
              <td>AUTHOR</td>
              <td>
                <xref target="vcard_param_author"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_note">
          <name>Properties of the Note object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>created</td>
              <td>
                <xref target="RFC9553" section="2.8.3" sectionFormat="comma"/>
              </td>
              <td>CREATED</td>
              <td>
                <xref target="vcard_param_created"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_online_service">
        <name>OnlineService</name>
        <t>The OnlineService object converts to the <xref target="vcard_prop_impp">IMPP property</xref> or <xref target="vcard_prop_socialprofile">SOCIALPROFILE property</xref>. Which property to convert to is implementation-specific. Implementations <bcp14>SHOULD</bcp14> preserve the property name indicated in the <xref target="jscontact_prop_vcard">vCard property</xref>.</t>
        <t>If its "uri" property is set, but neither the user or "service" properties are set, then implementations <bcp14>SHOULD</bcp14> choose IMPP if the "uri" property value is a URI with scheme "xmpp".</t>
        <t>Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_online_service">
          <name>Properties of the OnlineService object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.3.2" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.3.2" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.3.2" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
            <tr>
              <td>service</td>
              <td>
                <xref target="RFC9553" section="2.3.2" sectionFormat="comma"/>
              </td>
              <td>SERVICE-TYPE</td>
              <td>
                <xref target="vcard_param_service_type"/>
              </td>
            </tr>
            <tr>
              <td>user</td>
              <td>
                <xref target="RFC9553" section="2.3.2" sectionFormat="comma"/>
              </td>
              <td>USERNAME</td>
              <td>
                <xref target="vcard_param_username"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_organization">
        <name>Organization</name>
        <t>The Organization object converts to the <xref target="vcard_prop_org">ORG property</xref>.</t>
        <t>Its "name" property converts to the first component in the structured property value. The "name" property of any OrgUnit object in its "units" property converts to additional components in the structured property value, in order of appearance.</t>
        <t>Its "sortAs" property converts to the first component in the structured value of the <xref target="vcard_param_sort_as">SORT-AS parameter</xref>. The "sortAs" property of any OrgUnit object in its "units" property converts to additional components in the structured parameter value, in order of appearance.</t>
        <t>Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_organization">
          <name>Properties of the Organization object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.2.3" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_personal_info">
        <name>PersonalInfo</name>
        <t>The PersonalInfo object converts to one of the following properties, determined by the PersonalInfo object's "kind" property value. If the "kind" is "expertise" then it converts to the <xref target="vcard_prop_expertise">EXPERTISE property</xref>. If the "kind" is "hobby" then it converts to the <xref target="vcard_prop_hobby">HOBBY property</xref>. If the "kind" is "interest" then it converts to the <xref target="vcard_prop_interest">INTEREST property</xref>.</t>
        <t>Its "value" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_personal_info">
          <name>Properties of the PersonalInfo object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.8.4" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>listAs</td>
              <td>
                <xref target="RFC9553" section="2.8.4" sectionFormat="comma"/>
              </td>
              <td>INDEX</td>
              <td>
                <xref target="vcard_param_index"/>
              </td>
            </tr>
            <tr>
              <td>level</td>
              <td>
                <xref target="RFC9553" section="2.8.4" sectionFormat="comma"/>
              </td>
              <td>LEVEL</td>
              <td>
                <xref target="vcard_param_level"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_phone">
        <name>Phone</name>
        <t>The Phone object converts to the <xref target="vcard_prop_tel">TEL property</xref></t>
        <t>Its "number" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_phone">
          <name>Properties of the Phone object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.3.3" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>features</td>
              <td>
                <xref target="RFC9553" section="2.3.3" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_prop_tel"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.3.3" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.3.3" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_scheduling_address">
        <name>SchedulingAddress</name>
        <t>The SchedulingAddress object converts to the <xref target="vcard_prop_caladruri">CALADRURI property</xref>.</t>
        <t>Its "uri" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_scheduling_address">
          <name>Properties of the SchedulingAddress object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.4.2" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>label</td>
              <td>
                <xref target="RFC9553" section="2.4.2" sectionFormat="comma"/>
              </td>
              <td>X-ABLabel (Property)</td>
              <td>
                <xref target="vcard_prop_xablabel"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.4.2" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_speak_to_as">
        <name>SpeakToAs</name>
        <t>The SpeakToAs object converts to the <xref target="vcard_prop_gramgender">GRAMGENDER property</xref> and <xref target="vcard_prop_pronouns">PRONOUNS property</xref>.</t>
        <t>Its "grammaticalGender" property converts to the property value of the GRAMGENDER property.</t>
        <t>Its "pronouns" property converts to PRONOUNS properties, one for each entry. The Pronouns object's "pronouns" property converts to the property value. Its other properties convert as follows:</t>
        <table anchor="jscontact_to_vcard_props_pronouns">
          <name>Properties of the Pronouns object</name>
          <thead>
            <tr>
              <th>Name</th>
              <th>Reference</th>
              <th>Parameter (or other)</th>
              <th>See</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>contexts</td>
              <td>
                <xref target="RFC9553" section="2.2.4" sectionFormat="comma"/>
              </td>
              <td>TYPE</td>
              <td>
                <xref target="vcard_param_type"/>
              </td>
            </tr>
            <tr>
              <td>pref</td>
              <td>
                <xref target="RFC9553" section="2.2.4" sectionFormat="comma"/>
              </td>
              <td>PREF</td>
              <td>
                <xref target="vcard_param_pref"/>
              </td>
            </tr>
          </tbody>
        </table>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
      <section anchor="convert_jscontact_to_vcard_new_title">
        <name>Title</name>
        <t>The Title object converts to one of the following properties, determined by the Title object's "kind" property value. If the "kind" is "title" or not set then it converts to the <xref target="vcard_prop_title">TITLE property</xref>. If the "kind" is "role" then it converts to the <xref target="vcard_prop_role">ROLE property</xref>.</t>
        <t>Its "name" property converts to the property value. Its "organizationId" property converts by assigning the TITLE property and the ORG property to the same vCard property group (see <xref target="vcard_prop_role"/>).</t>
        <t>Other properties <bcp14>MAY</bcp14> be converted to <xref target="vcard_prop_jsprop">JSPROP properties</xref>.</t>
      </section>
    </section>
    <section anchor="updates_to_jscontact">
      <name>Updates to JSContact</name>
      <section anchor="jscontact_new_properties">
        <name>New Properties</name>
        <section anchor="jscontact_prop_vcard">
          <name>vCard</name>
          <dl newline="true">
            <dt>Name:</dt>
            <dd>vCard</dd>
            <dt>Context:</dt>
            <dd>A Card object</dd>
            <dt>Type:</dt>
            <dd><tt>VCard</tt> (optional)</dd>
            <dt>Description</dt>
            <dd>
              <t>This property contains information about vCard data that got converted to a JSContact Card object.  It allows for preserving arbitrary vCard elements, such as extension properties and parameters. This specification defines the VCard object type for converting a vCard to a JSContact Card object. Future specifications <bcp14>MAY</bcp14> define additional value types for this property.</t>
              <t>A VCard object has the following properties:</t>
              <dl>
                <dt>@type: String</dt>
                <dd>This specifies the type of this object. This <bcp14>MUST</bcp14> be <tt>VCard</tt>, if set.</dd>
                <dt>convertedProperties: String[VCardProperty] (optional)</dt>
                <dd>
                  <t>This contains conversion-related information about the vCard properties that got partially or fully converted to JSContact.  Each key defines the path to a JSContact element.  The value for each key contains information about the vCard property which converted to the JSContact element located at that key.</t>
                  <t>Unless otherwise defined for a specific vCard property, the path points to the JSContact property that the vCard property value converts to (e.g., see <xref target="test_vcard_prop_impp"/>). Whether a path points into the "localizations" property, or a localization patches the "vCard" property, is implementation-specific.</t>
                  <t>The key <bcp14>MUST</bcp14> be a valid key of a PatchObject as defined in <xref target="RFC9553" section="1.4.3" sectionFormat="of"/>.  The key <bcp14>MAY</bcp14> point into a nested object.</t>
                </dd>
                <dt>properties: *[][] (optional)</dt>
                <dd>This contains properties of the vCard which did not convert to standard JSContact elements. The value <bcp14>MUST</bcp14> be a list of vCard properties formatted in jCard as defined in <xref target="RFC7095" section="3.3" sectionFormat="of"/>. The order of the list elements is not significant, but the order of the elements within each jCard-formatted property is.
              </dd>
              </dl>
              <t>A VCardProperty object has the following properties:</t>
              <dl>
                <dt>@type: String</dt>
                <dd>This specifies the type of this object. This <bcp14>MUST</bcp14> be <tt>VCardProperty</tt>, if set.</dd>
                <dt>name: String (mandatory)</dt>
                <dd>This is the name of the vCard property in lowercase.</dd>
                <dt>valueType: String (optional)</dt>
                <dd>This is the name of the vCard property value type in lowercase.</dd>
                <dt>parameters: String[String|String[]] (optional)</dt>
                <dd>This contains parameters of the vCard property. The value <bcp14>MUST</bcp14> comply with vCard parameters formatted in jCard as defined in <xref target="RFC7095" section="3.4" sectionFormat="of"/>.</dd>
              </dl>
            </dd>
          </dl>
          <t>The example in <xref target="test_jscontact_prop_vcard"/> describes how to convert unknown vCard elements to the "vCard" property. The "X-FOO" parameter set on the FN property illustrates how to preserve an unknown vCard parameter on a property that does convert to a standard JSContact element. The "X-BAR" property illustrates how to convert entirely unknown vCard properties.</t>
          <figure anchor="test_jscontact_prop_vcard">
            <name>Converting unknown vCard elements to the vCard property</name>
            <sourcecode><![CDATA[
--- vCard:
VERSION:4.0
FN;X-FOO=bar:test
X-BAR:bam

--- JSContact:
"name": {
  "full": "test"
},
"vCard": {
  "version": "4.0",
  "convertedProperties": {
    "name/full": {
      "name": "fn",
      "parameters": {
        "x-foo": "bar"
      }
    }
  },
  "properties": [
    [
      "x-bar",
      {},
      "unknown",
      "bam"
    ]
  ]
}
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="jscontact_updated_address_kinds">
        <name>Updated AddressComponent Kinds</name>
        <t>This section updates the definitions of the "name" and "number" AddressComponent kinds, originally defined in <xref target="RFC9553" section="2.5.1.2"/>.  The new definitions improve interoperability with existing vCard data.  These changes do not invalidate existing JSContact data and do not introduce new JSContact elements, so no JSContact version change is required.</t>
        <t>The original definition stated that the "name" AddressComponent contains the street name; the new definition states that it can contain both the street name and number.  This aligns the definition with vCard address semantics before <xref target="RFC9554"/>, and thus the majority of existing vCard data, which does not separate street name and number.  <xref target="RFC9555"/> already instructed implementations to convert such combined street name and number values from the <xref target="RFC6350"/> ADR "street address" component to an AddressComponent of kind "name".  This now aligns the JSContact definitions with that conversion rule.</t>
        <t>The new definition of the "number" AddressComponent kind clarifies that it signifies the house or building number in addresses without a street name, which can occur in Japanese addresses, for example.</t>
        <t>The definitions for the "name" and "number" kinds are replaced entirely as follows:</t>
        <t>OLD:</t>
        <blockquote>
          <ul>
            <li>number: the street number, e.g., "123".  This value is not restricted to numeric values and can include any value such as number ranges ("112-10"), grid style ("39.2 RD"), alphanumerics ("N6W23001"), or fractionals ("123 1/2").</li>
            <li>name: the street name.</li>
          </ul>
        </blockquote>
        <t>NEW:</t>
        <blockquote>
          <ul>
            <li>number: the street number, e.g., "123".  This value is not restricted to numeric values and can include any value such as number ranges ("112-10"), grid style ("39.2 RD"), alphanumerics ("N6W23001"), or fractionals ("123 1/2").  In addresses without a street name, this is the house or building number (see Figure 33 of <xref target="RFC9553"/>).</li>
            <li>name: the street name.  Some implementations do not store the street name and number separately, in which case this component contains both the street name and number, e.g., "54321 Oak St".  If so, an AddressComponent of kind "number" <bcp14>SHOULD NOT</bcp14> be set in addition.</li>
          </ul>
        </blockquote>
        <t>The definitions of other AddressComponent kinds remain unchanged.</t>
      </section>
    </section>
    <section anchor="updates_to_vcard">
      <name>Updates to vCard</name>
      <section>
        <name>Updated Properties</name>
        <section anchor="vcard_updated_adr">
          <name>ADR</name>
          <t>This section updates the definition of the ADR property, as originally defined in <xref target="RFC6350" section="6.3.1"/> and extended in <xref target="RFC9554" section="2.1"/>.  The original definition stated that the presence of any of the new address components defined in <xref target="RFC9554"/> requires implementations to ignore the ADR "street address" component. This was a mistake; the presence of, say, a "district" component is no reason to ignore a "street address" value.  Also, the statement could be read as if this rule applies even if the values of all of the newly defined components are empty.</t>
          <t>The following text replaces the second paragraph of <xref target="RFC9554" section="2.1"/>:</t>
          <t>OLD:</t>
          <blockquote>
            <t>Implementations SHOULD write a combined value of these components in the street address component for backwards compatibility, but they SHOULD ignore the street component during reads if the ADR property value contains any of the new components.</t>
          </blockquote>
          <t>NEW:</t>
          <blockquote>
              <t>Implementations <bcp14>SHOULD</bcp14> write a combined value of the "street number" and "street name" components in the "street address" component for backwards compatibility, if both have a non-empty value.  Whether to also combine the values of other components in the "street address" component is implementation-specific.</t>
              <t>During reads, implementations <bcp14>SHOULD</bcp14> ignore the "street address" component if the "street number" or "street name" component has a non-empty value.  Absent or empty values, or the presence of any other address component, do not cause the "street address" component to be ignored.</t>
          </blockquote>
          <t>Also, the ABNF in <xref target="RFC9554" section="2.1"/> requires all eighteen components to be present, even if the components defined there are all empty.  This makes ADR property values that conform to <xref target="RFC6350"/> invalid.  Writing these empty components conveys no information and unnecessarily breaks interoperability.  The following text replaces the definition of "ADR-value" in the ABNF of <xref target="RFC9554" section="2.1"/>.  The definitions of the components remain unchanged.</t>
          <t>OLD:</t>
          <sourcecode type="abnf"><![CDATA[
ADR-value = ; defined in RFC 6350, Section 6.3.1.:
            ADR-component-pobox ";"
            ADR-component-ext ";"
            ADR-component-street ";"
            ADR-component-locality ";"
            ADR-component-region ";"
            ADR-component-code ";"
            ADR-component-country ";"
            ; defined in this document:
            ADR-component-room ";"
            ADR-component-apartment ";"
            ADR-component-floor ";"
            ADR-component-streetnumber ";"
            ADR-component-streetname ";"
            ADR-component-building ";"
            ADR-component-block ";"
            ADR-component-subdistrict ";"
            ADR-component-district ";"
            ADR-component-landmark ";"
            ADR-component-direction
]]></sourcecode>
          <t>NEW:</t>
          <sourcecode type="abnf"><![CDATA[
ADR-value = ; defined in RFC 6350, Section 6.3.1:
            ADR-component-pobox ";"
            ADR-component-ext ";"
            ADR-component-street ";"
            ADR-component-locality ";"
            ADR-component-region ";"
            ADR-component-code ";"
            ADR-component-country
            ; defined in RFC 9554, optional as a group:
            [";" ADR-component-room
             ";" ADR-component-apartment
             ";" ADR-component-floor
             ";" ADR-component-streetnumber
             ";" ADR-component-streetname
             ";" ADR-component-building
             ";" ADR-component-block
             ";" ADR-component-subdistrict
             ";" ADR-component-district
             ";" ADR-component-landmark
             ";" ADR-component-direction]
]]></sourcecode>
          <t>Implementations <bcp14>SHOULD NOT</bcp14> write the components defined in <xref target="RFC9554"/> if all their values are empty.</t>
        </section>
        <section anchor="vcard_updated_n">
          <name>N</name>
          <t>This section updates the definition of the N property, as originally defined in <xref target="RFC6350" section="6.2.2"/> and extended in <xref target="RFC9554" section="2.2"/>.  The original definition stated that implementations should ignore any value in the "family name" and "honorific suffixes" components if an equal value is set in the "secondary surname" and "generation" components, respectively.  This was a mistake; in Spanish names, the two surnames can be equal.  For example, both surnames of "Ana Pérez Pérez" are "Pérez".  For backwards compatibility, writers add both surnames to the "family name" component.  Readers that implement the original definition of <xref target="RFC9554"/> then ignore both surname values in the "family name" component, and the first surname is lost.</t>
          <t>The following text replaces the third paragraph of <xref target="RFC9554" section="2.2"/>:</t>
          <t>OLD:</t>
          <blockquote>
            <t>Currently, implementations typically place secondary surnames in the family name component and generational markers in the honorific suffixes component.  For backwards compatibility, implementations SHOULD add such values to both the newly defined components and their backwards-compatible counterpart.  Reading N property values, implementations SHOULD ignore any value in the backwards-compatible component if an equal value is set in the new component accordingly.  For example, a "Jr." that occurs in both honorific suffixes and generation should only be handled as a generational marker.</t>
          </blockquote>
          <t>NEW:</t>
          <blockquote>
              <t>Currently, implementations typically place secondary surnames in the family name component and generational markers in the honorific suffixes component.  For backwards compatibility, implementations <bcp14>SHOULD</bcp14> add such values to both the newly defined components and their backwards-compatible counterpart.</t>
              <t>During reads, implementations <bcp14>SHOULD</bcp14> ignore one value in the backwards-compatible component for each equal value in the new component, starting from the last value of the backwards-compatible component.  Any other values in the backwards-compatible component, even if equal, are not ignored.  For example, a "Jr." that occurs in both honorific suffixes and generation should only be handled as a generational marker.  In contrast, if the family name component contains the value "Pérez" twice and the secondary surname component contains it once, then both the family name and the secondary surname are "Pérez".</t>
          </blockquote>
          <t>Also, the ABNF in <xref target="RFC9554" section="2.2"/> requires all seven components to be present, even if the "secondary surname" and "generation" components are both empty.  This makes N property values that conform to <xref target="RFC6350"/> invalid.  Writing these empty components conveys no information and unnecessarily breaks interoperability.  The following text replaces the definition of "N-value" in the ABNF of <xref target="RFC9554" section="2.2"/>:</t>
          <t>OLD:</t>
          <sourcecode type="abnf"><![CDATA[
N-value = list-component 6(";" list-component)
]]></sourcecode>
          <t>NEW:</t>
          <sourcecode type="abnf"><![CDATA[
N-value = list-component 4(";" list-component)
          [2(";" list-component)]
]]></sourcecode>
          <t>Implementations <bcp14>SHOULD NOT</bcp14> write the "secondary surname" and "generation" components if both their values are empty.</t>
        </section>
      </section>
      <section>
        <name>New Parameters</name>
        <section anchor="vcard_param_jscomps">
          <name>JSCOMPS</name>
          <dl>
            <dt>Parameter name:</dt>
            <dd>JSCOMPS</dd>
            <dt>Purpose:</dt>
            <dd>Defines the order and separators for the elements of a structured property value.</dd>
            <dt>Description:</dt>
            <dd>
              <t>The JSCOMPS parameter value facilitates converting name and address components between JSContact and vCard.  It preserves the order of the components of the JSContact property and contains the verbatim values of separator components.</t>
              <t>If this parameter is set and its value is valid (see later), then implementations <bcp14>MUST</bcp14> set the "isOrdered" property of the Name or Address object to "true". Otherwise, they <bcp14>MUST</bcp14> set the "isOrdered" property value to "false".</t>
              <t>The JSCOMPS parameter value is a structured type value. Its value <bcp14>MUST</bcp14> be quoted.  The parameter value consists of a sequence of entries, separated by the SEMICOLON character (U+003B).  The first entry defines the value of the "defaultSeparator" property.  If it is the empty string, then no default separator is defined. Otherwise, the first entry <bcp14>MUST</bcp14> be a separator entry.  All following entries processed in order result in an ordered list of JSContact components and <bcp14>MUST</bcp14> be one of the following two kinds:</t>
              <ol>
                <li>
                  <t>A positional.  This refers to a component value in the vCard structured value.  A position consists of the numeric index of a component in the structured value, optionally followed by a COMMA (U+002C) character and the non-zero index of a value within that component.  The zero index selects the first component or value, respectively.  The second index is zero by default, in which case it <bcp14>MUST</bcp14> be omitted (as well as the leading COMMA).</t>
                  <t>The resulting JSContact component is formed by determining its kind by the position in the vCard structured value.  The component value is the verbatim value of the vCard component.  Figures <xref target="test_vcard_param_jscomps" format="counter"/> and <xref target="test_vcard_param_jscomps_2" format="counter"/> illustrate this by example.</t>
                </li>
                <li>
                  <t>A separator.  This contains the verbatim value of a separator component.  It starts with the LATIN SMALL LETTER S (U+0073) character, followed by the COMMA (U+002C) character, followed by zero or more "param-value" characters (see <xref target="RFC6350" sectionFormat="of" section="3.3"/>), where the COMMA (U+002C) and SEMICOLON (U+003B) characters <bcp14>MUST</bcp14> be escaped according to the rules defined in <xref target="RFC6350" sectionFormat="of" section="3.4"/>.  <xref target="test_vcard_param_jscomps_3"/> illustrates this by example.</t>
                  <t>The resulting JSContact component is formed by setting its "kind" to "separator" and its value to the verbatim value of the entry.</t>
                </li>
              </ol>
              <t>A JSCOMPS parameter value is valid if and only if:</t>
              <ul>
                <li>All indexes in the positional entries refer to an existing component value in the vCard property value.</li>
                <li>
                  <t>The count of positional entries equals the count of deduplicated component values.  Deduplication is required because some values may occur in both their designated and backwards-compatible components in the vCard property value:</t>
                  <ul>
                    <li>A value that occurs in both the N property secondary surname component and the family name component only counts once.</li>
                    <li>A value that occurs in both the N property generation component and the honorific suffix component only counts once.</li>
                    <li>A value in the ADR property "street address" component does not count if the "street number" or "street name" component has a non-empty value.  Also see <xref target="vcard_updated_adr"/>.</li>
                    <li>All other values count once each.</li>
                  </ul>
                </li>
              </ul>
            </dd>
            <dt>Format definition:</dt>
            <dd>
              <sourcecode name="" type="abnf"><![CDATA[
jscomps-param     = "JSCOMPS" "="
                      DQUOTE [jscomps-entry-sep ] ";" jscomps-entrylist DQUOTE

jscomps-entrylist  = jscomps-entry *(";" jscomps-entry)
jscomps-entry      = jscomps-entry-pos / jscomps-entry-sep
jscomps-entry-pos  = 1*DIGIT [ "," 1*DIGIT ]
jscomps-entry-sep  = "s" "," jscomps-entry-verb
jscomps-entry-verb = *QSAFE-CHAR ; encode special characters according to RFC 6868
]]></sourcecode>
            </dd>
            <dt anchor="vcard_param_jscomps_examples">Example(s):</dt>
            <dd>
              <t>The following example demonstrates the use of positional entries for the name "Jane Doe".  The given name is ordered before the surname.  No secondary index is required for either positional because both are zero.</t>
              <figure anchor="test_vcard_param_jscomps">
                <name>Example of Positional Entries</name>
                <sourcecode><![CDATA[
--- JSContact:
"name": {
  "components": [
    { "kind": "given", "value": "Jane" },
    { "kind": "surname", "value": "Doe" }
  ],
  "isOrdered": true,
  "...": ""
}

--- vCard:
N;JSCOMPS=";1;0":Doe;Jane;;;
FN;DERIVED=TRUE:Jane Doe
]]></sourcecode>
              </figure>
              <t>The following example demonstrates a secondary positional index.  The "Jr." generation marker only counts once because it occurs in both the designated generation component and the backwards-compatible honorific suffixes component.</t>
              <figure anchor="test_vcard_param_jscomps_2">
                <name>Example of a Secondary Positional Index</name>
                <sourcecode><![CDATA[
--- JSContact:
"name": {
  "components": [
    { "kind": "given", "value": "John" },
    { "kind": "given2", "value": "Philip" },
    { "kind": "given2", "value": "Paul" },
    { "kind": "surname", "value": "Stevenson" },
    { "kind": "generation", "value": "Jr." },
    { "kind": "credential", "value": "M.D." }
  ],
  "isOrdered": true,
  "...": ""
}

--- vCard:
N;JSCOMPS=";1;2;2,1;0;6;4,1":Stevenson;John;Philip,Paul;;Jr.,M.D.;;Jr.
]]></sourcecode>
              </figure>
              <t>The following example demonstrates the use of separator entries for the (shortened for brevity) address "54321 Oak St, Reston". The first entry defines the default separator to be ", ".  The first and second positional entries are separated with the separator value " ".  For backwards compatibility, the "street address" component of the ADR property contains both the street number and name, but it is not referred to in the JSCOMPS parameter and does not contribute to the count of values.</t>
              <figure anchor="test_vcard_param_jscomps_3">
                <name>Example of Separator Entries</name>
                <sourcecode><![CDATA[
--- JSContact:
"addresses": {
  "a1": {
    "components": [
      { "kind": "number", "value": "54321" },
      { "kind": "separator", "value": " " },
      { "kind": "name", "value": "Oak St" },
      { "kind": "locality", "value": "Reston" }
    ],
    "defaultSeparator": ", ",
    "isOrdered": true
  }
}

--- vCard:
ADR;JSCOMPS="s,\, ;10;s, ;11;3":;;54321 Oak St;Reston;;;;;;;54321;Oak St;;;;;;
]]></sourcecode>
              </figure>
              <t>The following example demonstrates the use of positional entries for the (shortened for brevity) address "Hauptstraße 5, Wien".  The "street address" component contains both the street name and number.  The "street name" and "street number" components are not set, so the "street address" component counts and is referred to in the JSCOMPS parameter.</t>
              <figure anchor="test_vcard_param_jscomps_4">
                <name>Example of a Combined Street Address</name>
                <sourcecode><![CDATA[
--- JSContact:
"addresses": {
  "a1": {
    "components": [
      { "kind": "name", "value": "Hauptstraße 5" },
      { "kind": "locality", "value": "Wien" }
    ],
    "defaultSeparator": ", ",
    "isOrdered": true
  }
}

--- vCard:
ADR;JSCOMPS="s,\, ;2;3":;;Hauptstraße 5;Wien;;;
]]></sourcecode>
              </figure>
            </dd>
          </dl>
        </section>
        <section anchor="vcard_param_jsid">
          <name>JSID</name>
          <dl newline="true">
            <dt>Parameter Name:</dt>
            <dd>JSID</dd>
            <dt>Purpose:</dt>
            <dd>Specifies the JSContact identifier of the associated property.</dd>
            <dt>Description:</dt>
            <dd>
              <t>This parameter specifies the JSON object key of the JSContact object to which a vCard property converts. For example, this parameter set on an EMAIL property defines the key of the EmailAddress object in the Card object's "emails" property (see below for an example).</t>
              <t>The value of the JSID parameter <bcp14>MUST</bcp14> be a valid key according to the definition of the JSContact property to which the property that this parameter is set on converts to. Typically, this requires the value to be a valid <xref target="RFC9553" section="1.4.1" sectionFormat="parens">Id</xref>.</t>
            </dd>
            <dt>Format Definition:</dt>
            <dd>
              <sourcecode type="abnf"><![CDATA[
jsid-param  = "JSID" "=" param-value
]]></sourcecode>
            </dd>
            <dt>Example(s):</dt>
            <dd>
              <figure anchor="test_vcard_param_jsid">
                <name>Converting the JSID parameter on an EMAIL property</name>
                <sourcecode><![CDATA[
--- vCard:
EMAIL;JSID=xyz:jane_doe@example.com

--- JSContact:
"emails": {
  "xyz": {
    "address": "jane_doe@example.com"
  }
}
]]></sourcecode>
              </figure>
            </dd>
          </dl>
        </section>
        <section anchor="vcard_param_jsptr">
          <name>JSPTR</name>
          <dl>
            <dt>Parameter name:</dt>
            <dd>JSPTR</dd>
            <dt>Purpose:</dt>
            <dd>To specify a pointer to a JSContact property.</dd>
            <dt>Description:</dt>
            <dd>
              <t>This parameter is set on a <xref target="vcard_prop_jsprop">JSPROP</xref> property.  Its value points to a JSContact property.  The parameter has a single value that <bcp14>MUST</bcp14> be a valid PatchObject key as defined in <xref target="RFC9553" section="1.4.3"/>. The parameter value <bcp14>MUST</bcp14> be quoted and is case-sensitive.</t>
            </dd>
            <dt>Format definition:</dt>
            <dd>
              <sourcecode name="" type="abnf"><![CDATA[
jsptr-param  = "JSPTR" "=" DQUOTE *QSAFE-CHAR DQUOTE
]]></sourcecode>
            </dd>
            <dt>Example(s):</dt>
            <dd>
              <t>For further examples, see <xref target="vcard_prop_jsprop_examples"/>.</t>
              <sourcecode name="" type="vcard"><![CDATA[
JSPROP;JSPTR="example.com:foo":"bar"
]]></sourcecode>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="new_vcard_props">
        <name>New vCard Properties</name>
        <section anchor="vcard_prop_jsprop">
          <name>JSPROP</name>
          <dl>
            <dt>Property name:</dt>
            <dd>JSPROP</dd>
            <dt>Purpose:</dt>
            <dd>Represents a JSContact property in vCard.</dd>
            <dt>Value type:</dt>
            <dd>TEXT; also see "Format definition" below for value restrictions.</dd>
            <dt>Conformance:</dt>
            <dd>Can be specified multiple times in a vCard.</dd>
            <dt>Property parameters:</dt>
            <dd>
          The JSPTR parameter <bcp14>MUST</bcp14> be set for this property.
          Other IANA-registered and experimental property parameters can be specified on this property.
        </dd>
            <dt>Description:</dt>
            <dd>
              <t>This property converts an arbitrary JSContact property from and to vCard.  The vCard property value is the JSON-encoded value of the JSContact property, represented as a TEXT value.  The format of the JSON value <bcp14>MUST</bcp14> be compact, e.g., without insignificant whitespace as defined in <xref target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259" section="2"/>.  The value of the JSPTR parameter points to the JSContact property within the Card.</t>
              <t>The root of the JSON pointer is always the Card object that this vCard converts to, irrespective if the JSON pointer starts with the SOLIDUS (U+002F) character.  The pointer <bcp14>MUST NOT</bcp14> reference into an array.</t>
              <t>All JSPROP properties in a vCard together form a PatchObject as defined in <xref target="RFC9553"/>.  The value of its JSPTR parameter corresponds to a key in the PatchObject; the value of the JSPROP property corresponds to the value for that key.  When converting from vCard to JSContact, the PatchObject <bcp14>MUST</bcp14> only be applied after all other vCard properties have already been converted.  The PatchObject <bcp14>MUST</bcp14> be valid, including the restriction that an invalid PatchObject <bcp14>MUST NOT</bcp14> be applied.</t>
            </dd>
            <dt>Format definition:</dt>
            <dd>
              <t>This property is defined by the following notation:</t>
              <sourcecode name="" type="abnf"><![CDATA[
jsprop = "JSPROP" jsprop-param ":" TEXT

jsprop-param  = *(
            ; The following are MANDATORY and MUST NOT
            ; occur more than once
            ( ";" jsptr-param ) /    ; see next section
            ( ";" "VALUE" "=" "TEXT")
            ;
            ; The following is OPTIONAL
            ; and MAY occur more than once.
            ;
            (";" other-param)
            ;
            )
]]></sourcecode>
            </dd>
            <dt anchor="vcard_prop_jsprop_examples">Example(s):</dt>
            <dd>
              <t>This illustrates how to convert a property at the top level in a Card object that is unknown to the implementation.</t>
              <figure anchor="test_vcard_prop_jsprop">
                <name>Unknown Property Example</name>
                <sourcecode><![CDATA[
--- JSContact:
"someUnknownProperty": true

--- vCard:
JSPROP;JSPTR="someUnknownProperty":true
]]></sourcecode>
              </figure>
              <t>This illustrates how to convert a vendor-specific property at the top level of a Card object.  Note the required use of quoted string for the JSPTR value, which allows the path to include the COLON (U+003A) character.</t>
              <figure anchor="test_vcard_prop_jsprop_2">
                <name>Vendor-Specific Property Conversion Example</name>
                <sourcecode><![CDATA[
--- JSContact:
"example.com:foo": {
  "bar": 1234
}

--- vCard:
JSPROP;JSPTR="example.com:foo":{"bar":1234}
]]></sourcecode>
              </figure>
              <t>This illustrates how to convert a vendor-specific property at a nested level in a Card object using a path relative to the Card object.  Although not recommended, the property name includes the SOLIDUS (U+002F) character, which requires escaping in the JSON pointer.</t>
              <figure anchor="test_vcard_prop_jsprop_3">
                <name>Nested Vendor-Specific Property Example with a Path Relative to Card</name>
                <sourcecode><![CDATA[
--- JSContact:
"phones": {
  "phone1": {
    "number": "+33-01-23-45-67",
    "example.com:foo/bar": "tux hux"
  }
}

--- vCard:
TEL;JSID=phone1:+33-01-23-45-67
JSPROP;JSPTR="phones/phone1/example.com:foo~1bar":
 "tux hux"
]]></sourcecode>
              </figure>
            </dd>
          </dl>
        </section>
      </section>
    </section>
    <section anchor="security_considerations">
      <name>Security Considerations</name>
      <t>This specification defines how to convert between the JSContact and vCard formats.
      The security considerations for parsing and formatting such data apply and are outlined in <xref target="RFC9553" sectionFormat="of" section="4"/> and <xref target="RFC6350" sectionFormat="of" section="9"/>.</t>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <t>This document obsoletes <xref target="RFC9555"/>. It registers new elements in the vCard and JSContact registries, updates the reference of entries that <xref target="RFC9555"/> originally registered to this document, and obsoletes the JSContact elements that this document replaces.</t>
      <section>
        <name>Changes to the "vCard Element Registries"</name>
        <t>IANA will add the following entry to the "Parameters" registry:</t>
        <dl spacing="compact">
          <dt>Parameter</dt>
          <dd>JSID</dd>
          <dt>Reference</dt>
          <dd>
            <xref target="vcard_param_jsid"/>
          </dd>
        </dl>
        <t>IANA will update the Reference to this document for the following entry in the "Properties" registry, which <xref target="RFC9555"/> originally registered:</t>
        <dl spacing="compact">
          <dt>Property</dt>
          <dd>JSPROP</dd>
          <dt>Reference</dt>
          <dd>
            <xref target="vcard_prop_jsprop"/>
          </dd>
        </dl>
        <t>IANA will update the Reference to this document for the following entries in the "Parameters" registry, which <xref target="RFC9555"/> originally registered:</t>
        <dl spacing="compact">
          <dt>Parameter</dt>
          <dd>JSCOMPS</dd>
          <dt>Reference</dt>
          <dd>
            <xref target="vcard_param_jscomps"/>
          </dd>
        </dl>
        <dl spacing="compact">
          <dt>Parameter</dt>
          <dd>JSPTR</dd>
          <dt>Reference</dt>
          <dd>
            <xref target="vcard_param_jsptr"/>
          </dd>
        </dl>
        <t>IANA will add <xref target="vcard_updated_adr"/> and <xref target="vcard_updated_n"/> of this document as references for the ADR and N properties, respectively, in the "Properties" registry.</t>
      </section>
      <section>
        <name>Changes to the "JSContact Registries"</name>
        <section>
          <name>"JSContact Properties" Registry</name>
          <t>IANA will add the following entry to the "JSContact Properties" registry:</t>
          <dl spacing="compact">
            <dt>Property Name</dt>
            <dd>vCard</dd>
            <dt>Property Type</dt>
            <dd>VCard</dd>
            <dt>Property Context</dt>
            <dd>Card</dd>
            <dt>Reference or Description</dt>
            <dd>
              <xref target="jscontact_prop_vcard"/>
            </dd>
            <dt>Intended Usage</dt>
            <dd>common</dd>
            <dt>Change Controller</dt>
            <dd>IETF</dd>
          </dl>
          <t>IANA will change the Intended Usage from "common" to "obsolete" for the following entries in the "JSContact Properties" registry, which <xref target="RFC9555"/> originally registered. For each entry, the Property Name and its changed fields are listed.</t>
          <dl spacing="compact">
            <dt>Property Name</dt>
            <dd>vCardProps</dd>
            <dt>Reference or Description</dt>
            <dd>
              <xref target="jscontact_obsoleted_properties"/>
            </dd>
            <dt>Intended Usage</dt>
            <dd>obsolete</dd>
          </dl>
          <dl spacing="compact">
            <dt>Property Name</dt>
            <dd>vCardParams</dd>
            <dt>Reference or Description</dt>
            <dd>
              <xref target="jscontact_obsoleted_properties"/>
            </dd>
            <dt>Intended Usage</dt>
            <dd>obsolete</dd>
          </dl>
          <dl spacing="compact">
            <dt>Property Name</dt>
            <dd>vCardName</dd>
            <dt>Reference or Description</dt>
            <dd>
              <xref target="jscontact_obsoleted_properties"/>
            </dd>
            <dt>Intended Usage</dt>
            <dd>obsolete</dd>
          </dl>
        </section>
        <section>
          <name>"JSContact Types" Registry</name>
          <t>IANA will add the following entries to the "JSContact Types" registry:</t>
          <dl spacing="compact">
            <dt>Type Name</dt>
            <dd>VCard</dd>
            <dt>Type Reference</dt>
            <dd>
              <xref target="jscontact_prop_vcard"/>
            </dd>
            <dt>Intended Usage</dt>
            <dd>common</dd>
            <dt>Change Controller</dt>
            <dd>IETF</dd>
          </dl>
          <dl spacing="compact">
            <dt>Type Name</dt>
            <dd>VCardProperty</dd>
            <dt>Type Reference</dt>
            <dd>
              <xref target="jscontact_prop_vcard"/>
            </dd>
            <dt>Intended Usage</dt>
            <dd>common</dd>
            <dt>Change Controller</dt>
            <dd>IETF</dd>
          </dl>
          <t>IANA will change the Intended Usage from "common" to "obsolete" for the following entry in the "JSContact Types" registry, which <xref target="RFC9555"/> originally registered. For each entry, the Type Name and its changed fields are listed.</t>
          <dl spacing="compact">
            <dt>Type Name</dt>
            <dd>JCardProp</dd>
            <dt>Type Reference</dt>
            <dd>
              <xref target="jscontact_obsoleted_types"/>
            </dd>
            <dt>Intended Usage</dt>
            <dd>obsolete</dd>
          </dl>
        </section>
        <section>
          <name>"JSContact Enum Values" Registry</name>
          <t>IANA will add <xref target="jscontact_updated_address_kinds"/> of this document to the Reference or Description of the following enum values in the subregistry for the "kind" property in the "AddressComponent" context of the "JSContact Enum Values" registry:</t>
          <ul spacing="compact">
            <li>name</li>
            <li>number</li>
          </ul>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.calconnect-vobject-i18n" to="vOBJECT"/>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <!-- [I-D.ietf-calext-jscontact] in EDIT state as of 2/12/24; companion document RFC 9553 -->
        <reference anchor="RFC9553" target="https://www.rfc-editor.org/info/rfc9553">
          <front>
            <title>JSContact: A JSON Representation of Contact Data</title>
            <author initials="R" surname="Stepanek" fullname="Robert Stepanek">
              <organization/>
            </author>
            <author initials="M" surname="Loffredo" fullname="Mario Loffredo">
              <organization/>
            </author>
            <date month="March" year="2024"/>
          </front>
          <seriesInfo name="RFC" value="9553"/>
          <seriesInfo name="DOI" value="10.17487/RFC9553"/>
        </reference>
        <!-- [I-D.ietf-calext-vcard-jscontact-extensions] in REF state as of 2/12/24; companion document RFC 9554 -->
        <reference anchor="RFC9554" target="https://www.rfc-editor.org/info/rfc9554">
          <front>
            <title>vCard Format Extension for JSContact</title>
            <author initials="R." surname="Stepanek" fullname="Robert Stepanek">
              <organization>Fastmail</organization>
            </author>
            <author initials="M." surname="Loffredo" fullname="Mario Loffredo">
              <organization>IIT-CNR</organization>
            </author>
            <date month="March" year="2024"/>
          </front>
          <seriesInfo name="RFC" value="9554"/>
          <seriesInfo name="DOI" value="10.17487/RFC9554"/>
        </reference>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5322.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6350.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6473.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6474.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6532.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6715.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6869.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7095.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9555.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9982.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-calext-jscontact-profiles.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-calext-vcard4-bis.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.loffredo-calext-jscontact-eai.xml"/>
      </references>
      <references>
        <name>Informative References</name>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-calext-jscalendar-icalendar.xml"/>
        <!--[I-D.calconnect-vobject-i18n] IESG state Expired. Entered the long way to get the correct initials-->
        <reference anchor="I-D.calconnect-vobject-i18n" target="https://datatracker.ietf.org/doc/html/draft-calconnect-vobject-i18n-00">
          <front>
            <title>vObject Internationalization</title>
            <author fullname="Ronald Henry Tse" initials="R." surname="Tse">
              <organization>Ribose</organization>
            </author>
            <author fullname="Peter Tam" initials="P." surname="Tam">
              <organization>Ribose</organization>
            </author>
            <author fullname="Michael Douglass" initials="M." surname="Douglass">
              <organization>Spherical Cow Group</organization>
            </author>
            <date day="7" month="June" year="2018"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-calconnect-vobject-i18n-00"/>
        </reference>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8605.xml"/>
        <reference anchor="CLDRPersonName" target="https://www.unicode.org/reports/tr35/tr35-personNames.html">
          <front>
            <title>Unicode Locale Data Markup Language (LDML) Part 8: Person Names</title>
            <author fullname="M. Davis">
              <organization/>
            </author>
            <author fullname="P. Edberg">
              <organization/>
            </author>
            <author fullname="R. Gillam">
              <organization/>
            </author>
            <author fullname="A. Kolisnychenko">
              <organization/>
            </author>
            <author fullname="M. McKenna">
              <organization/>
            </author>
            <author>
              <organization>other CLDR committee members</organization>
            </author>
            <date year="2023" month="July"/>
          </front>
          <seriesInfo name="Unicode Technical Standard" value="#35"/>
          <seriesInfo name="Version" value="44.1"/>
        </reference>
      </references>
    </references>
    <section anchor="differences_from_rfc9555">
      <name>Differences from RFC 9555</name>
      <t>This section documents all significant differences from RFC 9555. Insignificant differences, such as formatting, grammar or typos are not documented.</t>
      <section>
        <name>Applied Errata</name>
        <t>The following errata was applied to this document:</t>
        <ul>
          <li>
            <eref target="https://www.rfc-editor.org/errata/eid8555">Errata 8555</eref>
          </li>
        </ul>
      </section>
      <section>
        <name>Changed Conversion Rules</name>
        <section>
          <name>vCard to JSContact</name>
          <ul>
            <li>Converting the UID property to the "uid" property is redefined for JSContact version "2.0". See <xref target="convert_card_uid"/>.</li>
            <li>Converting the EMAIL property is redefined for JSContact version "3.0". See <xref target="vcard_prop_email"/>.</li>
            <li>Converting the ADR property is revised for ignored street addresses, multiple values, component order, and localizations.  See <xref target="vcard_prop_adr"/>.</li>
            <li>Converting the N property is revised for ignored values, multiple values, and component order.  See <xref target="vcard_prop_n"/>.</li>
            <li>Converting localizations is implementation-specific, with guidelines for the common case.  See <xref target="vcard_param_language"/>.</li>
          </ul>
        </section>
        <section>
          <name>JSContact to vCard</name>
          <ul>
            <li>Converting the Address object is revised for street names and numbers.  See <xref target="convert_jscontact_to_vcard_new_address"/>.</li>
            <li>Converting the Name object is revised for secondary surnames, generations, and empty components.  See <xref target="convert_jscontact_to_vcard_new_name"/>.</li>
            <li>Converting the "localizations" property is implementation-specific, with guidelines for the common case.  See <xref target="convert_jscontact_to_vcard_new_card"/>.</li>
          </ul>
        </section>
        <section>
          <name>JSCOMPS Parameter</name>
          <ul>
            <li>The rule for counting the "street address" component values of the ADR property is aligned with the updated ADR property definition.  See <xref target="vcard_param_jscomps"/>.</li>
          </ul>
        </section>
      </section>
      <section>
        <name>Changes to JSContact</name>
        <section>
          <name>Updated AddressComponent Kinds</name>
          <t>The definition of the "name" AddressComponent kind now allows values that contain both the street name and number.  The definition of the "number" kind now covers house or building numbers in addresses without a street name.  See <xref target="jscontact_updated_address_kinds"/>.</t>
        </section>
        <section anchor="jscontact_obsoleted_properties">
          <name>Obsoleted Properties</name>
          <t>The following JSContact properties became obsolete:</t>
          <dl newline="true" spacing="normal" anchor="obsolete_prop_vcardprops">
            <dt>
              <strong>vCardProps</strong>
            </dt>
            <dd>
              <t>This property is deprecated, the "properties" property of the newly defined <xref target="jscontact_prop_vcard">VCard type</xref> replaces it. <xref target="example_obsolete_vcardprops"/> illustrates this using the same example as<xref target="RFC9555" section="2.15.1" sectionFormat="of"/>.</t>
              <figure anchor="example_obsolete_vcardprops">
                <name>Example for Representing the Obsolete vCardProps Property</name>
                <sourcecode type="json"><![CDATA[
"vCardProps": [
  ["x-foo", { }, "unknown", "bar"]
]
]]></sourcecode>
                <sourcecode type="json"><![CDATA[
"vCard": {
  "properties": [
    ["x-foo", { }, "unknown", "bar"]
  ]
}
]]></sourcecode>
              </figure>
            </dd>
          </dl>
          <dl newline="true" spacing="normal">
            <dt>
              <strong>vCardParams</strong>
            </dt>
            <dd>
              <t>This property is deprecated, the "parameters" property of the newly defined <xref target="jscontact_prop_vcard">VCardProperty type</xref> replaces it. <xref target="example_obsolete_vcardparams"/> illustrates this using the same example as <xref target="RFC9555" section="2.15.2" sectionFormat="of"/>.</t>
              <figure anchor="example_obsolete_vcardparams">
                <name>Example for Representing the Obsolete vCardParams Property</name>
                <sourcecode type="json"><![CDATA[
"emails": {
  "email1": {
    "address": "jane_doe@example.com",
    "vCardParams": {
      "x-foo": "Bar"
    }
  }
}
]]></sourcecode>
                <sourcecode type="json"><![CDATA[
"emails": {
  "email1": {
    "address": "jane_doe@example.com"
  }
},
"vCard": {
  "convertedProperties": {
    "emails/email1/address": {
      "name": "email",
      "parameters": {
        "x-foo": "Bar"
      }
    }
  }
}
]]></sourcecode>
              </figure>
            </dd>
          </dl>
          <dl newline="true" spacing="normal">
            <dt>
              <strong>vCardName</strong>
            </dt>
            <dd>
              <t>This property is deprecated, the "name" property of the newly defined <xref target="jscontact_prop_vcard">VCardProperty type</xref> replaces it. <xref target="example_obsolete_vcardname"/> illustrates this using the same example as <xref target="RFC9555" section="2.15.3" sectionFormat="of"/>.</t>
              <figure anchor="example_obsolete_vcardname">
                <name>Example for Representing the Obsolete vCardName Property</name>
                <sourcecode type="json"><![CDATA[
"onlineServices": {
  "os1": {
    "uri": "xmpp:alice@example.com",
    "vCardName": "impp"
  }
}
]]></sourcecode>
                <sourcecode type="json"><![CDATA[
"onlineServices": {
  "os1": {
    "uri": "xmpp:alice@example.com"
  }
},
"vCard": {
  "convertedProperties": {
    "onlineServices/os1/uri": {
      "name": "impp"
    }
  }
}
]]></sourcecode>
              </figure>
            </dd>
          </dl>
        </section>
        <section anchor="jscontact_obsoleted_types">
          <name>Obsoleted Types</name>
          <t>The following JSContact type definitions became obsolete:</t>
          <dl newline="true" spacing="normal">
            <dt>
              <strong>JCardProp</strong>
            </dt>
            <dd>
              <t>This type is deprecated because the "vCardProps" property became deprecated. Also see <xref target="obsolete_prop_vcardprops"/>.</t>
            </dd>
          </dl>
        </section>
      </section>
      <section>
        <name>Changes to vCard</name>
        <section>
          <name>Updated ADR Property</name>
          <t>The "street address" component of the ADR property is only ignored if specific components defined in <xref target="RFC9554"/> have a non-empty value.  The components defined in <xref target="RFC9554"/> are optional.  See <xref target="vcard_updated_adr"/>.</t>
        </section>
        <section>
          <name>Updated N Property</name>
          <t>Only one equal value is ignored per secondary surname or generation value.  The components defined in <xref target="RFC9554"/> are optional.  See <xref target="vcard_updated_n"/>.</t>
        </section>
        <section>
          <name>Obsoleted Parameters</name>
          <t>The following vCard parameters became obsolete:</t>
          <dl newline="true" spacing="normal" anchor="obsolete_prop_prop_id">
            <dt>
              <strong>PROP-ID</strong>
            </dt>
            <dd>
              <t>This parameter is deprecated, the newly defined <xref target="vcard_param_jsid">JSID parameter</xref> replaces it. <xref target="vcard_param_propid"/> defines how to process the PROP-ID in presence and absence of the JSID parameter.</t>
            </dd>
          </dl>
        </section>
      </section>
    </section>
    <section anchor="Acknowledgments" numbered="false">
      <name>Acknowledgements</name>
      <t>The definition and examples of the <xref target="vcard_param_phonetic">PHONETIC</xref> and <xref target="vcard_param_script">SCRIPT</xref> parameters are based on the initial draft version of <xref target="I-D.calconnect-vobject-i18n"/>.</t>
    </section>
  </back>
</rfc>
