<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rfc>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="pre5378Trust200902" submissionType="IETF" category="std" xml:lang="en" consensus="true" docName="draft-ietf-calext-vcard-jscontact-extensions-08" obsoletes="" updates="6350" tocInclude="true" symRefs="true" sortRefs="true" version="3">
  <front>
    <title abbrev="vCard JSContact Extensions">vCard Format Extension for JSContact</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-calext-vcard-jscontact-extensions-08"/>
    <author initials="R." surname="Stepanek" fullname="Robert Stepanek">
      <organization>Fastmail</organization>
      <address>
        <postal>
          <street>PO Box 234, Collins St West</street>
          <city>Melbourne</city>
          <code>VIC 8007</code>
          <country>Australia</country>
          <region> </region>
        </postal>
        <email>rsto@fastmailteam.com</email>
      </address>
    </author>
    <author initials="M." surname="Loffredo" fullname="Mario Loffredo">
      <organization>IIT-CNR</organization>
      <address>
        <postal>
          <street>Via Moruzzi,1</street>
          <city>Pisa</city>
          <code>56124</code>
          <country>Italy</country>
          <region> </region>
        </postal>
        <email>mario.loffredo@iit.cnr.it</email>
      </address>
    </author>
    <date year="2023" month="July" day="3"/>
    <area>Applications</area>
    <workgroup>Calendaring Extensions</workgroup>
    <keyword>addressbook</keyword>
    <keyword>contacts</keyword>
    <keyword>cards</keyword>
    <keyword>vCard</keyword>
    <keyword>JSContact</keyword>
    <abstract>
      <t>
        This document defines a set of new properties for vCard and extends the use of existing ones.
        Their primary purpose is to align the same set of features between the JSContact and vCard formats,
        but the new definitions also aim to be useful within just the vCard format.  This document updates
        RFC 6350 (vCard).
      </t>
    </abstract>
  </front>
  <middle>
    <section>
      <name>Introduction</name>
      <t>
        The JSContact <xref target="I-D.ietf-calext-jscontact"/> format aims to be an alternative to the
        vCard <xref target="RFC6350"/> format for representation of contact and address book
        data.  As such, it introduces new semantics that are not covered in the current
        definition of vCard and its various extensions.  Converting contact data between
        the two formats is defined in <xref target="I-D.ietf-calext-jscontact-vcard"/> with the goal of
        not losing any semantics during conversion.  To do so, this document
        defines a new set of properties for vCard and extends existing definitions.
      </t>
      <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>
      </section>
      <section anchor="abnf-notations">
        <name>ABNF Notations</name>
        <t>The ABNF definitions in this document use the notations of <xref target="RFC5234"/>. ABNF rules not defined in this document either are defined in <xref target="RFC5234"/> (such as the ABNF for CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT) or <xref target="RFC6350"/>.
        </t>
      </section>
    </section>
    <section>
      <name>Updated Properties</name>
      <section anchor="prop-adr">
        <name>ADR Property</name>
        <t>This specification modifies the definition of the "ADR" property.  It extends its structured value with additional address components to better support the variety of international addresses.  It separates the address parts that currently typically are combined in street address component values into distinct components, such as street names, street numbers, apartment numbers, floors.  Implementations <bcp14>SHOULD</bcp14> write a combined value of these components in the street address component for backwards compatibility, but <bcp14>SHOULD</bcp14> ignore it during read if applicable new component values are available.</t>
        <t>The following change is made to the first paragraph in the "Special Notes" section, originally specified in <xref target="RFC6350" section="6.3.1"/>.  All remaining paragraphs of that section in the original specification still apply.</t>
        <dl>
          <dt>Special notes:</dt>
          <dd>The structured type value consists of a sequence of
             address components.  The component values MUST be specified in
             their corresponding position.  The structured type value
             corresponds, in sequence, to<br/>
                the post office box;<br/>
                the extended address (e.g., apartment or suite number);<br/>
                the street address;<br/>
                the locality (e.g., city);<br/>
                the region (e.g., state or province);<br/>
                the postal code;<br/>
                the country name (full name in the language specified in
                <xref target="RFC6350" section="5.1"/>);<br/>
                the room or suite number or identifier<br/>
                the apartment number, extension designation or box number.<br/>
                the building floor or level;<br/>
                the street name;<br/>
                the street number;<br/>
                the building, tower, condominium;<br/>
                the block name or number;<br/>
                the subdistrict;<br/>
                the district;<br/>
                the landmark or another publicly known prominent feature that can substitute the street name and number, e.g., "White House"", "Taj Mahal"";<br/>
                the cardinal direction or quadrant, e.g., "North"<br/>
            </dd>
        </dl>
        <t>The following change is made to the definition of "ADR-value" in the "ABNF" section, originally specified in <xref target="RFC6350" section="6.3.1"/>.</t>
        <dl>
          <dt>ABNF</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
            ADR-component-street ";" ADR-component-locality ";"
            ADR-component-region ";" ADR-component-code ";"
            ADR-component-country ";"
            ; above components are defined in RFC 6350, section 6.3.1
            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
ADR-component-pobox    = list-component
ADR-component-ext      = list-component
ADR-component-street   = list-component
ADR-component-locality = list-component
ADR-component-region   = list-component
ADR-component-code     = list-component
ADR-component-country  = list-component
ADR-component-room     = list-component
ADR-component-apartment = list-component
ADR-component-floor    = list-component
ADR-component-streetname = list-component
ADR-component-streetnumber = list-component
ADR-component-building = list-component
ADR-component-block    = list-component
ADR-component-subdistrict = list-component
ADR-component-district = list-component
ADR-component-landmark = list-component
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="new-properties">
      <name>New Properties</name>
      <section anchor="prop-created">
        <name>CREATED Property</name>
        <dl>
          <dt>Property name:</dt>
          <dd>CREATED</dd>
          <dt>Purpose:</dt>
          <dd>This property defines the date and time when the vCard was created</dd>
          <dt>Value type:</dt>
          <dd>A single timestamp value.</dd>
          <dt>Cardinality:</dt>
          <dd>*1</dd>
          <dt>Property parameters:</dt>
          <dd>VALUE</dd>
          <dt>Description:</dt>
          <dd>
            This is the time stamp when the vCard was created.  Copying the
            vCard across systems does not count as a new creation, nor does
            a new revision.  Instead, the time stamp value typically
            stays unchanged for the existence of the vCard.
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <t>This property is defined by the following notation:</t>
            <sourcecode name="" type="abnf"><![CDATA[
created       = "CREATED" createdparam ":" timestamp

createdparam  = *(
                 ;
                 ; The following are OPTIONAL,
                 ; but MUST NOT occur more than once.
                 ;
                 (";" "VALUE" "=" "timestamp") /
                 ;
                 ; The following are OPTIONAL,
                 ; and MAY occur more than once.
                 ;
                 (";" any-param)
                 ;
                 )
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
CREATED:20220705093412Z
CREATED;VALUE=TIMESTAMP:20211022T140000-05
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="prop-deflanguage">
        <name>DEFLANGUAGE Property</name>
        <dl>
          <dt>Property name:</dt>
          <dd>DEFLANGUAGE</dd>
          <dt>Purpose:</dt>
          <dd>This property defines the default language that human-readable text values in this vCard should be assumed written in.</dd>
          <dt>Value type:</dt>
          <dd>A single Language-Tag value as defined in <xref target="RFC6350" section="4"/>.</dd>
          <dt>Cardinality:</dt>
          <dd>*1</dd>
          <dt>Property parameters:</dt>
          <dd>The LANGUAGE parameter <bcp14>MUST NOT</bcp14> be assigned to this property.</dd>
          <dt>Description:</dt>
          <dd>
            This property defines the language in which property values of type
            <tt>TEXT</tt> shall be assumed to be written for this vCard.
            If a vCard property includes the <tt>LANGUAGE</tt> parameter, then the
            parameter value has higher precedence than the <tt>DEFLANGUAGE</tt>
            property value.
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <t>This property is defined by the following notation:</t>
            <sourcecode name="" type="abnf"><![CDATA[
deflanguage       = "DEFLANGUAGE" any-param ":" Language-Tag
               ; Language-Tag is defined in RFC6350, Section 4.
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
DEFLANGUAGE:de-AT
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="prop-gramgender">
        <name>GRAMGENDER Property</name>
        <dl>
          <dt>Property name:</dt>
          <dd>GRAMGENDER</dd>
          <dt>Purpose:</dt>
          <dd>
            This property defines which grammatical gender to use in salutations and other grammatical constructs.
          </dd>
          <dt>Value type:</dt>
          <dd>A single text value, restricted to an enumerated list of allowed values.</dd>
          <dt>Cardinality:</dt>
          <dd>*</dd>
          <dt>Property parameters:</dt>
          <dd>LANG</dd>
          <dt>Description:</dt>
          <dd>
            <t>
              This property defines the grammatical gender that the contact prefers
              to be addressed by or referred at in written or spoken form.
              For example, the German language distinguishes by grammatical gender in salutations such as "Sehr geehrte" (feminine) and "Sehr geehrter" (masculine).
              Multiple occurrences of this property
              <bcp14>MUST</bcp14> be distinguished by the LANG parameter.
            </t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <t>This property is defined by the following notation:</t>
            <sourcecode name="" type="abnf"><![CDATA[
gramgender       = "GRAMGENDER" gramgender-param
                      ":" gramgender-value

gramgender-param =
                *(
                 ;
                 ; The following are OPTIONAL,
                 ; but MUST NOT occur more than once.
                 ;
                 (";" language-param) /
                 ;
                 ; The following are OPTIONAL,
                 ; and MAY occur more than once.
                 ;
                 (";" any-param)
                 ;
                 )

gramgender-value = "animate" /
                   "common" /
                   "feminine" /
                   "inanimate" /
                   "masculine" /
                   "neuter" /
                   iana-token /
                   x-name
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
GRAMGENDER:neuter
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="prop-pronouns">
        <name>PRONOUNS Property</name>
        <dl>
          <dt>Property name:</dt>
          <dd>PRONOUNS</dd>
          <dt>Purpose:</dt>
          <dd>
            This property defines the pronouns that shall be used
            to refer to the entity represented by this vCard.
          </dd>
          <dt>Value type:</dt>
          <dd>A single text value.</dd>
          <dt>Cardinality:</dt>
          <dd>*</dd>
          <dt>Property parameters:</dt>
          <dd>LANG, PREF, TYPE</dd>
          <dt>Description:</dt>
          <dd>
            This property contains the pronouns that the contact chooses to use for themselves.
            The value is free-form text.  These pronouns shall be used
            when addressing or referring to the contact.  Multiple occurrences of
            this property <bcp14>MAY</bcp14> define pronouns for multiple languages,
            preferences and contexts.  Multiple pronouns in the same language
            <bcp14>SHOULD</bcp14> use the PREF parameter, otherwise, the order of
            preference is implementation-specific.
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <t>This property is defined by the following notation:</t>
            <sourcecode name="" type="abnf"><![CDATA[
pronouns       = "PRONOUNS" pronouns-param ":" text

pronouns-param =
                *(
                 ;
                 ; The following are OPTIONAL,
                 ; but MUST NOT occur more than once.
                 ;
                 (";" language-param) /
                 (";" pref-param) /
                 (";" type-param) /
                 (";" altid-param) /
                 ;
                 ; The following are OPTIONAL,
                 ; and MAY occur more than once.
                 ;
                 (";" any-param)
                 ;
                 )
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
PRONOUNS;LANG=en;PREF=1:xe/xir
PRONOUNS;LANG=en;PREF=2:they/them
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="prop-socialprofile">
        <name>SOCIALPROFILE Property</name>
        <dl>
          <dt>Property name:</dt>
          <dd>SOCIALPROFILE</dd>
          <dt>Purpose:</dt>
          <dd>To specify the URI or username for social media profiles associated with the object the vCard represents.</dd>
          <dt>Value type:</dt>
          <dd>A single URI or TEXT value.  The default value type is URI.</dd>
          <dt>Cardinality:</dt>
          <dd>*</dd>
          <dt>Property parameters:</dt>
          <dd>The SERVICE-TYPE parameter <bcp14>MUST</bcp14> be assigned to this property if the value type is TEXT, it <bcp14>MAY</bcp14> be assigned if the value type is URI.  In either case, it <bcp14>MUST NOT</bcp14> be assigned more than once.</dd>
          <dt>Description:</dt>
          <dd>
            Several vCard address book implementations currently use an experimental X-SOCIALPROFILE property to store social media profiles for contacts.  This specification provides an IANA-registered property for the same purpose.  In addition to the typical use of this property with URI values, it also allows setting usernames for social media services as free-text TEXT values, in which case the service name <bcp14>MUST</bcp14> be provided as a parameter.  Names <bcp14>MUST</bcp14> be considered equal if they match case-insensitively.
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <t>This property is defined by the following notation:</t>
            <sourcecode name="" type="abnf"><![CDATA[
socialpr       = "SOCIALPROFILE" socialpr-param ":"
                                 socialpr-value

socialpr-param = "VALUE=uri" / "VALUE=text" /
                 service-type-param / any-param

socialpr-value = URI / text
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
SOCIALPROFILE;SERVICE-TYPE=Mastodon:https://example.com/@foo
SOCIALPROFILE:https://example.com/ietf
SOCIALPROFILE;SERVICE-TYPE=SomeSite;VALUE=text:peter94
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="new-parameters">
      <name>New Parameters</name>
      <section anchor="param-author">
        <name>AUTHOR Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>AUTHOR</dd>
          <dt>Purpose:</dt>
          <dd>This parameter identifies the author of the associated property value.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This parameter <bcp14>MAY</bcp14> be set on any property where conveying authorship is desired.  It identifies the author as a URI <xref target="RFC3986"/>.  Since every valid URI includes the COLON (U+003A) character, the parameter value <bcp14>MUST</bcp14> be quoted.  Note that as an alternative or in addition to this parameter, the <tt>AUTHOR-NAME</tt> parameter allows naming an author as free-text value (see <xref target="param-author-name"/>).</t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
author-param    = "AUTHOR" "=" DQUOTE URI DQUOTE
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
NOTE;AUTHOR="mailto:john@example.com":This is some note.
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="param-author-name">
        <name>AUTHOR-NAME Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>AUTHOR-NAME</dd>
          <dt>Purpose:</dt>
          <dd>This parameter names the author of the associated property value.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This parameter <bcp14>MAY</bcp14> be set on any property where conveying authorship is desired.  It names the author as a free-text value.  The parameter value <bcp14>MUST NOT</bcp14> be empty.  Implementations <bcp14>MUST</bcp14> take care to quote the name part, if otherwise the part would not be a valid <tt>param-value</tt> (see <xref target="RFC6350" section="3.3"/>).  Note that as an alternative or in addition to this parameter, the <tt>AUTHOR</tt> parameter allows identifying an author by URI (see <xref target="param-author"/>).</t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
author-name-param    = "AUTHOR-NAME" "=" param-value ; not empty
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
NOTE;AUTHOR-NAME=John Doe:This is some note.
NOTE;AUTHOR-NAME="_:l33tHckr:_":A note by an unusual author name.
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="param-created">
        <name>CREATED Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>CREATED</dd>
          <dt>Purpose:</dt>
          <dd>This parameter defines the date and time when a property was created in a vCard.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This parameter <bcp14>MAY</bcp14> be set on any property to define the point in time when the property was created.  The value <bcp14>MUST</bcp14> be a valid TIMESTAMP value as defined in <xref target="RFC6350" section="4.3.5"/>.  Generally, updating a property value <bcp14>SHOULD NOT</bcp14> change the creation timestamp.</t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
created-param = "CREATED" "=" param-value ;
             ; a valid TIMESTAMP of Section 4.3.5 of [RFC6350]
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
NOTE;CREATED=20221122T151823Z:This is some note.
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="param-derived">
        <name>DERIVED Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>DERIVED</dd>
          <dt>Purpose:</dt>
          <dd>This parameter specifies that the value of the associated property is derived from some other property values in the same vCard.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This property parameter <bcp14>SHOULD</bcp14> be specified on an property if the property value is derived from some other properties in the same vCard.  When present with a value of <tt>true</tt>, clients <bcp14>MUST NOT</bcp14> update the property.</t>
            <t>For an example, an implementation may derive the value of the FN property from the name components of the N property by use of the <xref target="param-fmt">FMT</xref> parameter.  It indicates this fact by setting the DERIVED parameter on the FN property to <tt>true</tt>.</t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
derived-param    = "DERIVED" "=" ("true" / "false")
; Default is false
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
N:;John;Quinlan;Mr.;
FN;DERIVED=TRUE:Mr.  John Quinlan
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="param-fmt">
        <name>FMT Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>FMT</dd>
          <dt>Purpose:</dt>
          <dd>This parameter defines how to form a TEXT value from the components of a structured property value.</dd>
          <dt>Description:</dt>
          <dd>
            <t>The N and ADR properties use structured value types to define the constituent components of a name or address.  In contrast, the FN property and LABEL parameter contain full names or addresses as a single TEXT value, which might redundantly redefine the information in their structured value counterparts and bears the risk of their values going out of sync.  Instead, implementations should be guided how to form a full name or address of a given N or ADR property.  This is what the FMT parameter aims to achieve.  In addition to the component values, it also allows to define what values implementations <bcp14>SHOULD</bcp14> insert <em>in between</em> components, such that the resulting name or address is formatted appropriately and locale-specific.</t>
            <t>The FMT parameter value is a structured type value. It consists of a sequence of formatting instructions, where a formatting instruction defines what value to concatenate to the result TEXT value.  There are two kinds of formatting instruction:</t>
            <ol>
              <li>
                <t>A positional.  This instructs to concatenate to the result the value of a structured property component value at a specified position.  A position consists of a numeric index of a component in the structured value, optionally followed by a COMMA (U+002C) character and the index of a value within that component.  The zero index selects the first component or value, respectively.  The second index by default is zero, in which case it <bcp14>MAY</bcp14> be omitted, otherwise it <bcp14>MUST NOT</bcp14> be omitted.</t>
                <t>If a positional instruction contains a position of a non-existent or empty component value, then the entire FMT parameter <bcp14>MUST</bcp14> be considered invalid and <bcp14>MUST</bcp14> be ignored.</t>
              </li>
              <li>A separator.  This instructs to concatenate to the result a verbatim value defined in this formatting instruction. It starts with the LATIN SMALL LETTER S (U+0073) character, followed by COMMA (U+002C), followed by zero or more <xref target="RFC6350" section="3.3"><tt>param-value</tt></xref> characters, where the COMMA (U+002c) and SEMICOLON (U+003B) character <bcp14>MUST</bcp14> be escaped according to the rules defined in <xref target="RFC6350" section="3.4"/>.</li>
            </ol>
            <t>The first entry in the sequence of formatting instructions either <bcp14>MUST</bcp14> be the empty string or it <bcp14>MUST</bcp14> be a separator formatting instruction.  If the first entry is a separator formatting instruction, then this defines the default separator value to insert in between the values indicated by two consecutive positional formatting instructions.  Any separator formatting instruction in later entries has higher precedence than this default separator.  If the first entry is the empty string, the default separator is undefined and implementation-specific.  The FMT parameter value either includes exactly one separator formatting instruction for the default separator, or an optional default separator followed by at least one formatting instruction (see Format definition).</t>
            <t>Some implementations might not support the FMT parameter.  For backwards compatibility, implementations <bcp14>SHOULD</bcp14> generate the FN property based on the N property and FMT instructions.  In this case, they <bcp14>SHOULD</bcp14> set the <xref target="param-derived">DERIVED</xref> parameter on the FN property.  They <bcp14>MAY</bcp14> generate a LABEL parameter for the ADR property.</t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
fmt-param     = "FMT" "=" DQUOTE (
                            (fmt-inst-sep [";" fmt-instlist]) /
                            (";" fmt-instlist)
                          ) DQUOTE

fmt-instlist  = fmt-inst *(";" fmt-inst)
fmt-inst      = fmt-inst-pos / fmt-inst-sep
fmt-inst-pos  = 1*DIGIT ["," 1*DIGIT]
fmt-inst-sep  = "s" "," fmt-inst-verb
fmt-inst-verb = *QSAFE-CHAR     ; note: the ";" character MUST be escaped as "\;"
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <t>The following examples demonstrates how to generate the same value as the FN property value using the FMT parameter.  The first format instruction defines a single SPACE (U+0020) character as default to separate two component values.  The next format instructions select the first value of the second component of the N property value (the given name), followed by the first value of the first component in the N property value (the surname).</t>
            <sourcecode name="" type="abnf"><![CDATA[
FN;DERIVED=TRUE::Rene van der Harten
N;FMT="s, ;1,0;0,0":van der Harten;Rene,J.;Sir;R.D.O.N.
]]></sourcecode>
            <t>where the positions can be reduced to shorter form</t>
            <sourcecode name="" type="abnf"><![CDATA[
FN;DERIVED=TRUE::Rene van der Harten
N;FMT="s, ;1;0":van der Harten;Rene,J.;Sir;R.D.O.N.
]]></sourcecode>
            <t>An implementation may decide to not explicitly define a default separator.  Assuming that the implementation uses space to separate name components, the FMT parameter value would then be for example:</t>
            <sourcecode name="" type="abnf"><![CDATA[
FN;DERIVED=TRUE:Rene van der Harten
N;FMT=";1;0":van der Harten;Rene,J.;Sir;R.D.O.N.
]]></sourcecode>
            <t>The following example demonstrates how the honorific suffix could be preceded by the SEMICOLON (U+003B) and SPACE (U+0020) characters.</t>
            <sourcecode name="" type="abnf"><![CDATA[
FN;DERIVED=TRUE:Rene van der Harten; R.D.O.N.
N;FMT=";1;0;s,\; ;3":van der Harten;Rene,J.;Sir;R.D.O.N.
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="param-propid">
        <name>PROP-ID Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>PROP-ID</dd>
          <dt>Purpose:</dt>
          <dd>This parameter identifies a property among all its siblings of the same property name.</dd>
          <dt>Description:</dt>
          <dd>
            <t>
              This parameter uniquely identifies a property among all of its siblings with the same name within a vCard.  A valid PROP-ID value must be of 1 and a maximum of 255 octets in size, and it MUST only contain the ASCII alphanumeric characters (<tt>A-Za-z0-9</tt>), hyphen (<tt>-</tt>), and underscore (<tt>_</tt>).  The identifier only has the purpose to uniquely identify siblings, its value has no other meaning.  If an application makes use of PROP-ID it <bcp14>SHOULD</bcp14> assign a unique identifier to each sibling property of the same name within their embedding component.  The same identifier <bcp14>MAY</bcp14> be used for properties of a different name, and it <bcp14>MAY</bcp14> also be assigned to a same-named property that is not a sibling.
            </t>
            <t>
              Resolving duplicate identifier conflicts is specific to the application.  Similarly, handling properties where some but not all siblings have a PROP-ID is assigned, is application-specific.
            </t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
prop-id-param  = "PROP-ID" "=" 1*255(ALPHA / DIGIT / "-"/ "_")
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
PHOTO;PROP-ID=p827:data:image/jpeg;base64,MIICajCCAdOgAwIBAg
        <...remainder of base64-encoded data...>
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="param-service-type">
        <name>SERVICE-TYPE Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>SERVICE-TYPE</dd>
          <dt>Purpose:</dt>
          <dd>To define the online service name associated with a messaging or social media profile.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This parameter <bcp14>MAY</bcp14> be specified on a IMPP or SOCIALPROFILE property to name the online service associated with that property value.  Its value is case-sensitive, its letter cases <bcp14>MUST</bcp14> be preserved.</t>
            <t>Several vCard address book implementations currently use an experimental X-SERVICE-TYPE parameter.  This specification provides an IANA-registered parameter for the same purpose.</t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
service-type-param    = "SERVICE-TYPE" "=" param-value
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
SOCIALPROFILE;SERVICE-TYPE=Mastodon:https://example.com/@foo
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="param-username">
        <name>USERNAME Parameter</name>
        <dl>
          <dt>Parameter name:</dt>
          <dd>USERNAME</dd>
          <dt>Purpose:</dt>
          <dd>To define a user name, such as the user of a messaging or social media service.</dd>
          <dt>Description:</dt>
          <dd>
            <t>This parameter <bcp14>MAY</bcp14> be specified on a IMPP or SOCIALPROFILE property to name the user with that property value.  Its value is case-sensitive, its letter cases <bcp14>MUST</bcp14> be preserved.  The IMPP or SOCIALPROFILE value type <bcp14>MUST</bcp14> be URI.</t>
          </dd>
          <dt>Format definition:</dt>
          <dd>
            <sourcecode name="" type="abnf"><![CDATA[
username-param    = "USERNAME" "=" param-value
]]></sourcecode>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
SOCIALPROFILE;USERNAME="The Foo":https://example.com/@foo
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="new-values">
      <name>New Values</name>
      <section anchor="value-adr-type-billing">
        <name>Billing Address Type Value</name>
        <dl>
          <dt>Value:</dt>
          <dd>billing</dd>
          <dt>Purpose:</dt>
          <dd>This indicates to use this address for billing, e.g., to send invoices to.</dd>
          <dt>Conformance:</dt>
          <dd>
            <t>This value can be used with the "TYPE" parameter applied on the "ADR" property.</t>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
ADR;TYPE=billing:;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
]]></sourcecode>
          </dd>
        </dl>
      </section>
      <section anchor="value-adr-type-delivery">
        <name>Delivery Address Type Value</name>
        <dl>
          <dt>Value:</dt>
          <dd>delivery</dd>
          <dt>Purpose:</dt>
          <dd>This indicates to use this address for delivery, e.g., to send packages to.</dd>
          <dt>Conformance:</dt>
          <dd>
            <t>This value can be used with the "TYPE" parameter applied on the "ADR" property.</t>
          </dd>
          <dt>Example(s):</dt>
          <dd>
            <sourcecode name=""><![CDATA[
ADR;TYPE=delivery:;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
]]></sourcecode>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This specification extends the vCard Format Specification.  The same security considerations as outlined in <xref target="RFC6350" section="9"/> apply.</t>
    </section>
    <section anchor="IANA">
      <!-- All drafts are required to have an IANA considerations section.  See RFC 8126 for a guide.-->
      <name>IANA Considerations</name>
      <section>
        <name>Changes to the "vCard Properties" registry</name>
        <section>
          <name>New property definitions</name>
          <t>IANA is requested to add the following entries to the "vCard Properties" registry, defined in Section 10.3.1. of <xref target="RFC6350"/>.</t>
          <table anchor="new_properties">
            <name>New vCard Properties</name>
            <thead>
              <tr>
                <th align="left">Namespace</th>
                <th align="left">Property</th>
                <th align="left">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td/>
                <td align="left">CREATED</td>
                <td align="left">This document, <xref target="prop-created"/></td>
              </tr>
              <tr>
                <td/>
                <td align="left">DEFLANGUAGE</td>
                <td align="left">This document, <xref target="prop-deflanguage"/></td>
              </tr>
              <tr>
                <td/>
                <td align="left">GRAMGENDER</td>
                <td align="left">This document, <xref target="prop-gramgender"/></td>
              </tr>
              <tr>
                <td/>
                <td align="left">PRONOUNS</td>
                <td align="left">This document, <xref target="prop-pronouns"/></td>
              </tr>
              <tr>
                <td/>
                <td align="left">SOCIALPROFILE</td>
                <td align="left">This document, <xref target="prop-socialprofile"/></td>
              </tr>
            </tbody>
          </table>
        </section>
        <section>
          <name>Updated vCard properties</name>
          <t>IANA is requested to add <xref target="prop-adr"/> of this document as reference for the ADR property.</t>
        </section>
      </section>
      <section>
        <name>Changes to the "vCard Parameters" registry</name>
        <t>IANA is requested to add the following entries to the "vCard Parameters" registry, defined in Section 10.3.2. of <xref target="RFC6350"/>.</t>
        <table anchor="new_parameters">
          <name>New vCard Parameters</name>
          <thead>
            <tr>
              <th align="left">Namespace</th>
              <th align="left">Parameter</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td/>
              <td align="left">AUTHOR</td>
              <td align="left">This document, <xref target="param-author"/></td>
            </tr>
            <tr>
              <td/>
              <td align="left">AUTHOR-NAME</td>
              <td align="left">This document, <xref target="param-author-name"/></td>
            </tr>
            <tr>
              <td/>
              <td align="left">CREATED</td>
              <td align="left">This document, <xref target="param-created"/></td>
            </tr>
            <tr>
              <td/>
              <td align="left">FMT</td>
              <td align="left">This document, <xref target="param-fmt"/></td>
            </tr>
            <tr>
              <td/>
              <td align="left">DERIVED</td>
              <td align="left">This document, <xref target="param-derived"/></td>
            </tr>
            <tr>
              <td/>
              <td align="left">PROP-ID</td>
              <td align="left">This document, <xref target="param-propid"/></td>
            </tr>
            <tr>
              <td/>
              <td align="left">SERVICE-TYPE</td>
              <td align="left">This document, <xref target="param-service-type"/></td>
            </tr>
            <tr>
              <td/>
              <td align="left">USERNAME</td>
              <td align="left">This document, <xref target="param-username"/></td>
            </tr>
          </tbody>
        </table>
      </section>
      <section>
        <name>Changes to the "vCard Property Values" registry</name>
        <t>IANA is requested to add the following entries to the "vCard Property Values" registry, defined in Section 10.3.4. of <xref target="RFC6350"/>.</t>
        <table anchor="new_values">
          <name>New vCard Property Values</name>
          <thead>
            <tr>
              <th align="left">Property</th>
              <th align="left">Value</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">GRAMGENDER</td>
              <td align="left">animate</td>
              <td align="left">This document, <xref target="prop-gramgender"/></td>
            </tr>
            <tr>
              <td align="left">GRAMGENDER</td>
              <td align="left">common</td>
              <td align="left">This document, <xref target="prop-gramgender"/></td>
            </tr>
            <tr>
              <td align="left">GRAMGENDER</td>
              <td align="left">feminine</td>
              <td align="left">This document, <xref target="prop-gramgender"/></td>
            </tr>
            <tr>
              <td align="left">GRAMGENDER</td>
              <td align="left">inanimate</td>
              <td align="left">This document, <xref target="prop-gramgender"/></td>
            </tr>
            <tr>
              <td align="left">GRAMGENDER</td>
              <td align="left">masculine</td>
              <td align="left">This document, <xref target="prop-gramgender"/></td>
            </tr>
            <tr>
              <td align="left">GRAMGENDER</td>
              <td align="left">neuter</td>
              <td align="left">This document, <xref target="prop-gramgender"/></td>
            </tr>
          </tbody>
        </table>
      </section>
      <section>
        <name>Changes to the "vCard Parameter Values" registry</name>
        <t>IANA is requested to add the following entries to the "vCard Parameter Values" registry, defined in Section 10.3.4. of <xref target="RFC6350"/>.</t>
        <table anchor="new_param_values">
          <name>New vCard Property Values</name>
          <thead>
            <tr>
              <th align="left">Property</th>
              <th align="left">Parameter</th>
              <th align="left">Value</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">ADR</td>
              <td align="left">TYPE</td>
              <td align="left">billing</td>
              <td align="left">This document, <xref target="value-adr-type-billing"/></td>
            </tr>
            <tr>
              <td align="left">ADR</td>
              <td align="left">TYPE</td>
              <td align="left">delivery</td>
              <td align="left">This document, <xref target="value-adr-type-delivery"/></td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.3986.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5234.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.6350.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-calext-jscontact.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-calext-jscontact-vcard.xml"/>
      </references>
    </references>
  </back>
</rfc>
