<?xml version="1.0" encoding="utf-8"?> encoding="UTF-8"?>
<!DOCTYPE rfc> rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="*trust200902" ipr="trust200902" docName="draft-ietf-calext-jscontact-16" number="9553" submissionType="IETF" consensus="true" category="std" xml:lang="en" consensus="true" docName="draft-ietf-calext-jscontact-16" obsoletes="" updates="" tocInclude="true" symRefs="true" sortRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.6.0 -->
  <front>
    <!--[rfced] *AD, changes were submitted twice after the document
    was initially approved. Please review the updates from version 15
    to version 17 and let us know if you approve. The updates can
    be viewed in this diff file:
    https://www.rfc-editor.org/authors/rfc9553-ad-diff.html

    Additionally, under "Until Version" (4 instances), we updated the
    key words for clarity by replacing "MUST be not set, or be one of
    the allowed values" with "MUST NOT be set or MUST be one of the
    allowed values" as shown below. Please review and approve of this
    change to the key words.

    Original:
       The Until Version value either MUST NOT be set, or be one of the
       allowed values of the version property in the JSContact Enum Value
       registry (see Table 1).

    Current:
       The Until Version value either MUST NOT be set or MUST be one of
       the allowed values of the version property in the "JSContact Enum
       Values" registry (see Table 1).
    -->

    <title abbrev="JSContact">JSContact: A JSON representation Representation of contact data</title> Contact Data</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-calext-jscontact-16"/> name="RFC" value="9553"/>
    <author initials="R." surname="Stepanek" fullname="Robert Stepanek">
      <organization>Fastmail</organization>
      <address>
        <postal>
          <street>PO
          <extaddr>PO Box 234, Collins St 234</extaddr>
          <street>Collins St. West</street>
          <city>Melbourne</city>
          <code>VIC 8007</code>
          <region>VIC</region>
          <code>8007</code>
          <country>Australia</country>
          <region> </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> Moruzzi, 1</street>
          <city>Pisa</city>
          <code>56124</code>
          <country>Italy</country>
          <region> </region>
          <region/>
        </postal>
        <email>mario.loffredo@iit.cnr.it</email>
      </address>
    </author>
    <date year="2023" month="November" day="9"/>
    <area>Applications</area>
    <workgroup>Calendaring Extensions</workgroup> year="2024" month="March"/>
    <area>art</area>
    <workgroup>calext</workgroup>
    <keyword>JSON</keyword>
    <keyword>addressbook</keyword>
    <keyword>contacts</keyword>
    <keyword>cards</keyword>
    <keyword>VCARD</keyword>
    <abstract>
      <t>This specification defines a data model and JSON JavaScript Object Notation (JSON) representation of contact card
        information that can be used for data storage and exchange in address book or directory applications. It aims to
        be an alternative to the vCard data format and to be unambiguous, extendable extendable, and simple to process. In contrast
        to the JSON-based jCard format, it is not a direct mapping from the vCard data model and expands semantics where appropriate.</t>
        appropriate. Two additional specifications define new vCard elements and how to convert between JSContact and
        vCard.
      </t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>This document defines a data model for contact card data normally used in address book or directory
        applications and services. It aims to be an alternative to the vCard data format <xref target="RFC6350" format="default"/>.</t> format="default"/>.
      </t>
      <t>The key design considerations for this data model are as follows:</t>
      <ul spacing="normal">
        <li>The data model and set of attributes should mostly be mostly compatible with the one model defined for the vCard data
          format
          <xref target="RFC6350" format="default"/>
          and extensions (<xref
          <xref target="RFC6473" format="default"/>, format="default"/>
          <xref target="RFC6474" format="default"/>, format="default"/>
          <xref target="RFC6715" format="default"/>, format="default"/>
          <xref target="RFC6869" format="default"/>, format="default"/>
          <xref target="RFC8605" format="default"/>). format="default"/>. The specification should add new attributes or value types where
          appropriate. Not all existing vCard definitions need an equivalent in JSContact, especially if the vCard
          definition is considered to be obsolete or otherwise inappropriate. Conversion between the data formats need
          not fully preserve semantic meaning.</li>
        <li>The meaning.
        </li>
        <!--[rfced] Please clarify the meaning of "reducing complexity of
        their representation". Is the intended meaning that the
        attributes must be described as simple key-value pairs to
        reduce complexity (option A) or to reduce complexity of the
        representation of the card data (option B)?

        Original:
           The attributes of the card data represented must be described as
           simple key-value pairs, reducing complexity of their representation.</li>
           representation.

        Perhaps:
        A) The attributes of the card data being represented must be
           described as simple key-value pairs to reduce complexity.

        or

        B) The attributes of the card data must be described as simple
           key-value pairs to reduce the complexity of the representation
           of the card data.
        -->
        <li>The attributes of the card data must be described as simple key-value pairs to reduce the complexity of the
          representation of the card data.
        </li>
        <li>The data model should avoid all ambiguities and make it difficult to make mistakes during implementation.</li> implementation.
        </li>
        <li>Extensions, such as new properties and components, <bcp14>MUST NOT</bcp14> lead to requiring an a required update to of this document.</li>
          document.
        </li>
      </ul>
      <t>The representation of this data model is defined in the I-JSON Internet JSON (I-JSON) format <xref target="RFC7493" format="default"/>,
        which is a strict subset of the JavaScript Object Notation (JSON) Data Interchange Format JSON data interchange format <xref target="RFC8259" format="default"/>. Using
        JSON is mostly a pragmatic choice: its widespread use makes JSContact easier to adopt, and the availability of
        production-ready JSON implementations eliminates a whole category of parser-related interoperability issues.</t> issues.
      </t>
      <section anchor="relation-to-vcard" numbered="true" toc="default">
        <name>Motivation and Relation to vCard, jCard jCard, and xCard</name>
        <t>The vCard data format
          <xref target="RFC6350"/>
          is an interchange format for contacts data between address book service providers and vendors. However, this
          format has gone through multiple specifications specification iterations with only a subset of its deprecated <xref target="RFC2426">version 3</xref> 3
          </xref> being widely in use. Consequently, products and services internally use a richer an internal contact data model that is
          richer than what they expose when serializing that information to vCard. In addition, service providers often
          use a proprietary JSON representation of contact data in their APIs.</t> APIs.
        </t>
        <t>JSContact provides a standard JSON-based data model and representation of contact data as an alternative to
          proprietary formats.</t>
        <t>While formats.
        </t>
        <t>At the time of writing this document, several features missing features in vCard were brought to the attention of the authors,
          authors such as social media contacts, gender pronouns pronouns, and others. This highlights how vCard is not perceived
          as an evolving format and consequently and, consequently, hasn't been updated since close to for about ten years. JSContact addresses these
          unmet demands and defines new vCard properties and parameters to allow interchanging them in both formats.</t> formats.
        </t>
        <t>Two additional documents define the relation of JSContact and vCard:
          <xref target="RFC9554" format="default"/>
          defines new vCard properties and parameters, and
          <xref target="RFC9555" format="default"/>
          defines how to convert JSContact data from and to vCard.
        </t>
        <t>The xCard
          <xref target="RFC6351" format="default"/>
          and jCard
          <xref target="RFC7095" format="default"/>
          specifications define alternative representations for vCard data, data in XML and JSON format formats, respectively. Both
          explicitly aim to not change the underlying data model. Accordingly, they are regarded as equal to vCard in
          the context of this document.</t> document.
        </t>
      </section>
      <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</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</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 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> here.
        </t>
        <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 either
          <xref target="RFC5234"/>
          (such as the ABNF for CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT) or <xref target="RFC6350"/>.</t> target="RFC6350"/>.
        </t>
      </section>
      <section anchor="data-type-notations">
        <name>Data Type Notations</name>
        <t>This section introduces the notations and terminology used to define data types in JSContact.</t>
        <t>The underlying format for JSContact is JSON and JSON, so also its data types also build on JSON values. The terms "object"
          and "array" as well as the four primitive types ("strings", "numbers", "booleans", and "null") are to be
          interpreted as described in <xref target="RFC8259" section="1"/>. All JSContact data <bcp14>MUST</bcp14> be
          valid according to the constraints given in <xref target="RFC7493">I-JSON</xref>. Unless otherwise noted, all
          member names in JSON objects and all string values are case-sensitive. Within the context of JSON objects, the
          term "key" is synonymous with "member name" as defined in <xref target="RFC8259" section="1"/>.</t> section="1"/>.
        </t>
        <section anchor="objects-and-properties" numbered="true" toc="default">
          <name>Objects and Properties</name>
          <!-- [rfced] The use of <tt> and <em>

a) In the html and pdf outputs, the text enclosed in <tt> is output in
fixed-width font. In the txt output, there are no changes to the font,
and the quotation marks have been removed.

In the html and pdf outputs, the text enclosed in <em> is output in
italics. In the txt output, the text enclosed in <em> appears with an
underscore before and after.

Please review carefully and let us know if the output is acceptable or
if any updates are needed.

b) Some terms appear with and without the "<tt>" element, for example,
"@type", "Card", "version", etc. Please review and let us know if any
updates are needed for consistency.
-->
          <t>JSContact defines data types for contact information such as addresses or names. This information typically
            consists of multiple related elements, elements; for example example, a personal name and surname together form a name. These
            related elements are organized in JSContact objects. A JSContact object is a JSON object which:</t> that has the
            following:
          </t>
          <ol>
            <li>Has a
            <li>A unique type name registered in the IANA  <xref target="iana-type-registry">IANA JSContact Types Registry</xref>.</li>
            <li>Has one target="iana-type-registry">"JSContact Types"
              registry</xref>.
            </li>
            <li>One or more object members for which the name and allowed value types are specified. Such members are
              called "properties".</li>
            <li>Has one "properties".
            </li>
            <li>One property named <tt>@type</tt> @type with a string value that matches the type name of this the JSContact object. In
              general, this property does not need to be set explicitly as outlined in <xref target="prop-type"/>.</li> target="prop-type"/>.
            </li>
          </ol>
          <t>The following sections specify how to define JSContact object types. Sections
            <xref target="validating-jscontact"/> target="validating-jscontact" format="counter"/>
            and
            <xref target="vendor-specific-extensions"/> target="vendor-specific-extensions" format="counter"/>
            then define the exact requirements for property names.</t> names.
          </t>
          <t>The next paragraph illustrates how a JSContact object is defined:</t>
          <blockquote> defined.  The names "Foo" and "baz" are only for demonstration and have no meaning outside the example.</t>
          <ul empty="true" anchor="example-foo-object">
            <li>
            <t>A Foo object has the following properties:</t>
            <ul>
              <li><tt>qux</tt>: Number (mandatory).  Defines
            <dl spacing="normal">
              <dt>@type: String.</dt>
              <dd>The JSContact type of the qux-ishness object. The value <bcp14>MUST</bcp14> be "Foo", if set.
              </dd>
              <dt>baz: Number (mandatory).</dt>
              <dd>The baz level of this the contact. The value <bcp14>MUST</bcp14> be an integer greater than 0 and less
                than 10.</li> 10.
              </dd>
            </dl>
            </li>
          </ul>
          </blockquote>
          <t>Here,
	  <t>The above paragraph illustrates the following:</t>
          <ul>
            <li>It defines a JSContact object type named <tt>Foo</tt> is defined.  In addition to its <tt>@type</tt> "Foo" that has two properties, named "@type" and "baz".</li>
            <li>The @type property adheres to the rules outlined in <xref target="prop-type"/>. Because of this, it has a is
              neither defined to be mandatory nor optional, as this depends on how the Foo object type is used.
            </li>
            <li>The baz property named <tt>qux</tt> for which values value <bcp14>MUST</bcp14> be valid according to the definition of the <tt>Number</tt> Number type.  The
            </li>
            <li>The property has one attribute, <tt>mandatory</tt>, "mandatory", which specifies that the property <bcp14>MUST</bcp14> be
              present for an instance a value of this JSContact the Foo object type to be valid.  Finally, a
            </li>
            <li>The free-text description of the baz property describes the semantics and further restrictions.</t> restrictions for its
              values.
            </li>
          </ul>
          <!--[rfced] Section 1.3.1. Please clarify the meaning of "qux-ishness"
          as no other RFCs contain this term. Is it a well-known term, or
          can it perhaps be rephrased for clarity?

          Also, we removed the blockquote element from this text
          because it is not a direct quote. Please let us know
          if any further updates are needed.

          Original:
             A Foo object has the following properties:

                qux: Number (mandatory). Defines the qux-ishness of this contact.
                The value MUST be an integer greater than 0 and less than 10.
          -->
        </section>
        <section anchor="type-signatures" numbered="true" toc="default">
          <name>Type Signatures</name>
          <t>Type signatures are given for all JSON values and JSContact definitions in this document. The following
            conventions are used:</t>
          <ul used:
          </t>
          <dl spacing="normal">
            <li><tt>String</tt> - The
            <dt>String:</dt>
            <dd>The JSON string type.</li>
            <li><tt>Number</tt> - The type.</dd>
            <dt>Number:</dt>
            <dd>The JSON number type.</li>
            <li><tt>Boolean</tt> - The type.</dd>
            <dt>Boolean:</dt>
            <dd>The JSON boolean type.</li>
            <li><tt>A[B]</tt> - A type.</dd>
            <dt>A[B]:</dt>
            <dd>A JSON object where the all keys are all of the type <tt>A</tt>, A and the all values are all of the type <tt>B</tt>.</li>
            <li><tt>A[]</tt> - A B.</dd>
            <dt>A[]:</dt>
            <dd>A JSON array of values of type <tt>A</tt>.</li>
            <li><tt>A|B</tt> - The A.</dd>
            <dt>A|B:</dt>
            <dd>The value is either of type <tt>A</tt> A or of type <tt>B</tt>.</li>
            <li><tt>*</tt> - The B.</dd>
            <dt>*:</dt>
            <dd>The type is undefined (the value could be any type, although permitted values may be constrained by the
              context of this value).</li>
          </ul> value).
            </dd>
          </dl>
          <t><xref target="common-data-types"/>
            defines common data types, including signed or unsigned integers and dates.</t> dates.
          </t>
        </section>
        <section anchor="property-attributes" numbered="true" toc="default">
          <name>Property Attributes</name>
          <t>Object properties may also have a set of attributes defined along with the type signature. These have the
            following meanings:</t>
          <ul>
            <li><tt>mandatory</tt>: The meanings:
          </t>
          <dl spacing="normal">
            <dt>mandatory:</dt>
            <dd>The property <bcp14>MUST</bcp14> be set for an instance of this object to be valid.</li>
            <li><tt>optional</tt>: The valid.
            </dd>
            <dt>optional:</dt>
            <dd>The property can can, but not need not, be set for an instance of this object to be valid.</li>
            <li><tt>default</tt>: This valid.</dd>
            <dt>default:</dt>
            <dd>This is followed by a JSON value. That value will be used for this property if it is omitted.</li>
            <li><tt>defaultType</tt>: This omitted.</dd>
            <dt>defaultType:</dt>
            <dd>This is followed by the name of a JSContact object type. A property value of JSContact object type is
              expected to be of this named type, in case it omits the <tt>@type</tt> property.</li>
          </ul> @type property.
            </dd>
          </dl>
        </section>
        <section anchor="prop-type" numbered="true" toc="default">
          <name>The <tt>@type</tt> @type Property</name>
          <t>This property is defined as:</t>
          <ul>
            <li><tt>@type</tt>: String.  Specifies the
          <dl spacing="normal">
            <dt>@type: String.</dt>
            <dd>The JSContact type of this a JSON object.  This It <bcp14>MUST</bcp14> match the
              type name of the JSContact object of which this the JSON object is an instance of.</li>
          </ul> of.
            </dd>
          </dl>
          <t>The purpose of this the @type property is to help implementations identify which JSContact object type a given
            JSON object represents. Implementations <bcp14>MUST</bcp14> validate that JSON objects with this property
            conform to the specification of the JSContact object type of that name.</t> name.
          </t>
          <t>In many cases cases, the <tt>@type</tt> @type property value is implied by where its object occurs in JSContact data. Assuming
            that both <tt>A</tt> A and <tt>B</tt> B are JSContact object types:</t> types:
          </t>
          <ul>
            <li>An object that is set as the value for a property with type signature <tt>A</tt> "A" <bcp14>MAY</bcp14> have the <tt>@type</tt>
              @type property set. If the <tt>@type</tt> @type property is not set set, then its value is implied to be <tt>A</tt> A by the property definition.</li>
              definition.
            </li>
            <li>An object that is set as the value for a property with type signature <tt>A|B "A|B (defaultType: A)</tt> <bcp14>MAY</bcp14> A)" <bcp14>
              MAY
            </bcp14> have the <tt>@type</tt> @type property set if it is an instance of <tt>A</tt>. A. It <bcp14>MUST</bcp14> have the <tt>@type</tt> @type
              property set if it is an instance of <tt>B</tt>.  If instead B. If, instead, the <tt>defaultType</tt> defaultType attribute is not defined defined, then the <tt>@type</tt>
              @type property <bcp14>MUST</bcp14> also be set for <tt>A</tt>.</li> A.
            </li>
            <li>An object that is not the value of a property, such as the root of topmost object in JSON data (directly or as a
              member of an array), <bcp14>MUST</bcp14> have the <tt>@type</tt> @type property set.</li> set.
            </li>
          </ul>
        </section>
      </section>
      <section anchor="common-data-types" numbered="true" toc="default">
        <name>Common Data Types</name>
        <t>In addition to the standard JSON data types, a couple of additional data types are common to the definitions
          of JSContact objects and properties.</t> properties.
        </t>
        <section anchor="id" numbered="true" toc="default">
          <name>Id</name>
          <t>Where <tt>Id</tt> "Id" is given as a data type, it means a <tt>String</tt> String of at least 1 and a maximum of 255 octets in size,
            and it <bcp14>MUST</bcp14> only contain characters from the <tt>URL "URL and Filename Safe</tt> Safe" base64url alphabet, as
            defined in Section 5 of <xref target="RFC4648" format="default"/>, sectionFormat="of" section="5"/>, excluding the pad character (<tt>=</tt>). ("="). This
            means the allowed characters are the ASCII alphanumeric characters (<tt>A-Za-z0-9</tt>), ("A-Za-z0-9"), hyphen (<tt>-</tt>), ("-"), and
            underscore (<tt>_</tt>).</t> ("_").
          </t>
          <t>In many places in JSContact JSContact, a JSON map is used where the map keys are of type Id and the map values are
            all the same type of object. This construction represents an unordered set of objects, with the added
            advantage that each entry has a name (the corresponding map key). This allows for more concise patching of objects,
            objects and, when applicable, for the objects in question to be referenced from other objects within the
            JSContact object. The map keys <bcp14>MUST</bcp14> be preserved across multiple versions of the JSContact object.</t>
            object.
          </t>
          <t>Unless otherwise specified for a particular property, there are no uniqueness constraints on an Id value
            (other than, of course, the requirement that you cannot have two values with the same key within a single
            JSON map). For example, two <xref target="card">Card</xref> objects might use the same Ids in their
            respective <tt>photos</tt> photos properties. Or within the same Card Card, the same Id could appear in the <tt>emails</tt> emails and <tt>phones</tt> phones
            properties. These situations do not imply any semantic connections among the objects.</t> objects.
          </t>
        </section>
        <section anchor="int-unsignedint" numbered="true" toc="default">
          <name>Int and UnsignedInt</name>
          <t>Where <tt>Int</tt> "Int" is given as a data type, it means an integer in the range -2<sup>53</sup>+1 &lt;= value &lt;= 2<sup>53</sup>-1, 2<sup>
            53</sup>-1, which is the safe range for integers stored in a floating-point double, represented as a JSON <tt>Number</tt>.</t>
            Number.
          </t>
          <t>Where <tt>UnsignedInt</tt> "UnsignedInt" is given as a data type, it means an integer in the range 0 &lt;= value &lt;= 2<sup>53</sup>-1, 2<sup>
            53</sup>-1 represented as a JSON <tt>Number</tt>.</t> Number.
          </t>
        </section>
        <section anchor="patchobject" numbered="true" toc="default">
          <name>PatchObject</name>
          <t>A PatchObject is of type <tt>String[*]</tt>, "String[*]" and represents an unordered set of patches on a JSON object. Each key
            is a path represented in a subset of the JSON pointer Pointer format <xref target="RFC6901"/>. The paths have an
            implicit leading <tt>/</tt>, "/", so each key is prefixed with <tt>/</tt> "/" before applying the JSON pointer Pointer evaluation algorithm.</t>
            algorithm.
          </t>
          <t>A patch within a PatchObject is only valid if all the following conditions apply:</t>
          <ol>
            <li>The pointer <bcp14>MAY</bcp14> reference inside an array array, but if the last reference token in the pointer
              is an array index, then the patch value <bcp14>MUST NOT</bcp14> be null. The pointer <bcp14>MUST NOT</bcp14> NOT
              </bcp14> use "-" as an array index in any of its reference tokens (i.e., you <bcp14>MUST NOT</bcp14> insert/delete
              from an array, but you <bcp14>MAY</bcp14> replace the contents of its existing members. To add or remove
              members, one needs to replace the complete array value).</li> value).
            </li>
            <li>All reference tokens prior to the last (i.e., the value after the final slash) <bcp14>MUST</bcp14> already
              exist as values in the object being patched. If the last reference token is an array index, then a member
              at this index <bcp14>MUST</bcp14> already exist in the referenced array.</li> array.
            </li>
            <li>There <bcp14>MUST NOT</bcp14> be two patches in the PatchObject where the pointer of one is the prefix
              of the pointer of the other, e.g., <tt>addresses/1/city</tt> "addresses/1/city" and <tt>addresses</tt>.</li> "addresses".
            </li>
            <li>The value for the patch <bcp14>MUST</bcp14> be valid for the property being set (of the correct type and
              obeying any other applicable restrictions), or if null null, the property <bcp14>MUST</bcp14> be optional.</li> optional.
            </li>
          </ol>
          <t>The value associated with each pointer determines how to apply that patch:</t>
          <ul>
            <li>If null, remove the property from the patched object. If the key is not present in the parent, this is a no-op.</li>
              no-op.
            </li>
            <li>If non-null, set the value given as the value for this property (this may be a replacement or addition
              to the object being patched).</li> patched).
            </li>
          </ul>
          <t>A PatchObject does not define its own <xref target="prop-type"><tt>@type</tt></xref> target="prop-type">@type</xref> property. Instead, a <tt>@type</tt> the @type
            property in a patch <bcp14>MUST</bcp14> be handled as any other patched property value.</t> value.
          </t>
          <t>Implementations <bcp14>MUST</bcp14> reject a PatchObject in its entirety a PatchObject if any of its patches are invalid.
            Implementations <bcp14>MUST NOT</bcp14> apply partial patches.</t> patches.
          </t>
        </section>
        <section anchor="resource" numbered="true" toc="default">
          <name>Resource</name>
          <t>This
          <!--[rfced] When the term "Card" is referred to in the running text,
          there is a mix of "this Card" and "the Card". For consistency and
          clarity, we updated several instances of "this Card" to "the
          Card". Please review and let us know if any further updates are
          needed.

          One example

          Original:
             The date and time when the data in this Card was last
             modified.

          Current:
             The date and time when the data in the Card was last
             modified.
          -->
          <t>The Resource data type defines a resource associated with the entity represented by this the Card, identified by
            a URI <xref target="RFC3986" format="default"/>.  Several property definitions later Later in this document document, several property definitions refer
            to the Resource data type as the basis for their property-specific value types. The Resource data type defines the
            properties that are common to all of them. Property definitions making use of Resource <bcp14>MAY</bcp14> define
            additional properties for their value types.</t>
          <t>The <tt>@type</tt> property value <bcp14>MUST NOT</bcp14> be <tt>Resource</tt>, instead it <bcp14>MUST</bcp14> be the name of a concrete resource type (see <xref target="resource-properties"/>).  A types.
          </t>
          <t>A Resource object has the following properties.</t>
          <ul properties:</t>
          <dl spacing="normal">
            <li>
              <t>@type: <tt>String</tt>.  Specifies the
            <dt>@type: String.</dt>
            <dd>The JSContact type of this resource the object.  The allowed value is defined in later sections <bcp14>MUST NOT</bcp14> be "Resource"; instead, the value <bcp14>MUST</bcp14> be the name
            of this document for each a concrete resource type (<xref target="resource-properties"/>).</t>
            </li>
            <li>
              <t>kind: <tt>String</tt> (optional). (see <xref target="resource-properties"/>).</dd>
            <dt>kind: String (optional).</dt>
            <dd>
              The kind of the resource. The allowed values are defined in the property definition that makes use of the
              Resource type. Some property definitions may change this property from being optional to mandatory.
</t>
            </li>
            <li>uri: <tt>String</tt> (mandatory).
            </dd>
            <dt>uri: String (mandatory).</dt>
            <dd>
              The resource value. This <bcp14>MUST</bcp14> be a <em>URI</em> as defined in Section 3 of <xref target="RFC3986" format="default"/>.</li>
            <li>mediaType: <tt>String</tt> (optional).
Used for URI resource values.  Provides the sectionFormat="of" section="3"/>.
            </dd>
            <dt>mediaType: String (optional).</dt>
            <dd>
              The media type <xref target="RFC2046" format="default"/> of the resource identified by the URI.</li>
            <li>contexts: <tt>String[Boolean]</tt> (optional). uri property value.
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>
              The contexts in which to use this resource. Also see <xref target="prop-contexts"/>.</li>
            <li>pref: <tt>UnsignedInt</tt> (optional). target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>
              The preference of this the resource in relation to other resources. Also see <xref target="prop-pref"/>.</li>
            <li>label: <tt>String</tt> (optional). target="prop-pref"/>.
            </dd>
            <dt>label: String (optional).</dt>
            <dd>
              A custom label for the value, value. Also see <xref target="prop-label"/>.</li>
          </ul> target="prop-label"/>.
            </dd>
          </dl>
        </section>
        <section anchor="utcdatetime" numbered="true" toc="default">
          <name>UTCDateTime</name>
          <t>This
          <t>The UTCDateTime type is a string String in "date-time" format <xref target="RFC3339" format="default"/> <tt>date-time</tt> format, format="default"/>, with the
            further restrictions that any letters <bcp14>MUST</bcp14> be in uppercase, uppercase and the time offset <bcp14>MUST</bcp14> <bcp14>MUST
            </bcp14> be the character <tt>Z</tt>. "Z". Fractional second values <bcp14>MUST NOT</bcp14> be included unless non-zero they are
            non-zero, and they <bcp14>MUST NOT</bcp14> have trailing zeros, zeros to ensure there is only a single
            representation for each date-time.</t> date-time.
          </t>
          <t>For example, <tt>2010-10-10T10:10:10.003Z</tt> "2010-10-10T10:10:10.003Z" is conformant, but <tt>2010-10-10T10:10:10.000Z</tt> "2010-10-10T10:10:10.000Z" is invalid and invalid; the
            correct encoding is correctly encoded as <tt>2010-10-10T10:10:10Z</tt>.</t> "2010-10-10T10:10:10Z".
          </t>
        </section>
      </section>
      <section anchor="common-properties">
        <name>Common Properties</name>
        <t>Most of the properties in this document are specific to a single JSContact object type. Such properties are
          defined along with the respective object type. The properties in this section are common to multiple data
          types and are defined here to avoid repetition. Note that these properties <bcp14>MUST</bcp14> only be set for
          a JSContact object if they are explicitly mentioned to be allowed as allowable for this object type.</t>
        <section anchor="prop-contexts" numbered="true" toc="default">
          <name>contexts</name>
          <t>Type: <tt>String[Boolean]</tt></t>
          <t>This type.
        </t>
        <!--[rfced] Within Sections 1.5.1 to 2.8.4, there is inconsistency in
        the way the property names are introduced - some of the lead-in
        sentences are fragments and some work off of the property name in
        the title. May we make this consistent by including the property
        name (enclosed with <tt> in the XML file if preferred) in the lead-in
        sentence as shown in the examples below? Note that there are 25 instances.

        Some examples (see the text for more instances)

        Original:
           1.5.1  contexts

             Type: String[Boolean]

             This property associates contact information with one or more contexts
             in which it should be used.

        Perhaps:
           1.5.1  contexts

             Type: String[Boolean]

             The contexts property associates contact information with one or more
             contexts in which it should be used.

        ...
        Original:
           2.3.4  preferredLanguages

             Type: Id{LanguagePref] (optional).

             Defines the preferred languages for contacting the entity associated
             with this Card.

        Perhaps:
           2.3.4  preferredLanguages

             Type: Id{LanguagePref] (optional).

             The preferredLanguages property defines the preferred languages for
             contacting the entity associated with the Card.

        ...
        Original:
           2.6.2.  directories

             Type: Id[Directory] (optional).

             These are directory service resources, such as entries in a
             directory or organizational directories for lookup.

        Perhaps:
           2.6.2.  directories

             Type: Id[Directory] (optional)

             The directories property specifies directory service resources
             such as entries in a directory or organizational directories
             for lookup.
        -->
        <section anchor="prop-contexts" numbered="true" toc="default">
          <name>contexts</name>
          <dl spacing="normal">
            <dt>contexts: String[Boolean].</dt>
            <dd>
              <t>The contexts in which to use the contact information. For example, someone might have distinct phone numbers for work and private contexts, contexts and may set the desired context on the respective phone number in the <xref target="phones"><tt>phones</tt></xref> property.</t> target="phones"> phones </xref> property. </t>
              <t>This section defines common contexts. Additional contexts may be defined in the properties or data
                types that make use of this property. The <xref target="enumerated-values">enumerated</xref> target="enumerated-values">enumerated
                </xref> common context values are:</t> are:
              </t>
              <ul spacing="normal">
            <li><tt>private</tt>:
                <li>private: the contact information that may be used in a private context.</li>
            <li><tt>work</tt>:
                <li>work: the contact information that may be used in a professional context.</li>
              </ul>
        </section>
        <section anchor="prop-extra" numbered="true" toc="default">
          <name>extra</name>
          <t>This is a reserved property name. Implementations <bcp14>MUST NOT</bcp14> set this property in a JSContact object.  Any JSContact object including a property with this name <bcp14>MUST</bcp14> be considered invalid.</t>
          <t>The purpose of this reserved property name is to provide implementors with a name which is certain to never occur as a property name in a JSContact object.  Implementations might want to map unknown or vendor-specific properties to a variable with this name, but this is implementation-specific.</t>
            </dd>
          </dl>
        </section>
        <section anchor="prop-label" numbered="true" toc="default">
          <name>label</name>
          <t>Type: <tt>String</tt></t>
          <t>This property allows associating contact data
          <dl spacing="normal">
            <dt>label: String.</dt>
            <dd>The labels associated with user-defined labels. the contact data. Such labels may be set for
              phone numbers, email addresses addresses, and other resources. Typically, these labels are displayed along with their
              associated contact data in graphical user interfaces.  Such Note that succinct labels are best be succinct to properly for proper
              display on small graphical interfaces and screens.</t> screens.
            </dd>
          </dl>
        </section>
        <section anchor="prop-pref" numbered="true" toc="default">
          <name>pref</name>
          <t>Type: <tt>UnsignedInt</tt></t>
          <t>This property allows defining a
          <dl spacing="normal">
            <dt>pref: UnsignedInt.</dt>
            <dd>
              <t>A preference order for contact information. For example, a person may
                have two email addresses and prefer to be contacted with one of them.</t>
          <t>Its them.
              </t>
              <t>The value <bcp14>MUST</bcp14> be in the range of 1 and to 100. Lower values correspond to a higher level of
                preference, with 1 being most preferred. If no preference is set, then the contact information <bcp14>MUST</bcp14> <bcp14>
                  MUST
                </bcp14> be interpreted as being least preferred.</t> preferred.
              </t>
              <t>Note that the preference only is only defined in relation to contact information of the same type. For
                example, the preference orders within emails and phone numbers are independent of each other.</t> other.
              </t>
            </dd>
          </dl>
        </section>
        <section anchor="prop-phonetic" numbered="true" toc="default">
          <name>phonetic</name>
          <t>This property defines
          <t>The following properties define how to pronounce a value in the language indicated in the Card <xref target="language">language</xref> target="language">language
          </xref> property or the language tag of its <xref target="localizations">localizations</xref>. Exemplary uses
            of these properties are to define defining how to pronounce Japanese names, or for romanization of names and romanizing Mandarin or Cantonese name
            and address components. The properties are defined as follows:</t>
          <ul follows:
          </t>
          <dl spacing="normal">
            <li>
              <t>phonetic: <tt>String</tt>.
                Contains the
            <dt>phonetic: String.</dt>
            <dd>
              The phonetic representation of a value.

              <!--[rfced] Can "ignored for use with" be updated as "ignored and not
              used with" for clarity as shown below?

              Original:
                 Any script language subtag in the Card <xref target="language">language</xref> language (Section 2.1.5)
                 property <bcp14>MUST</bcp14> MUST be ignored for use with the <tt>phonetic</tt> phonetic property.

              Perhaps:
                 Any script language subtag in the Card language (Section 2.1.5)
                 property MUST be ignored and not used with the phonetic property.
              -->

              Any script language subtag in the Card <xref target="language">language</xref> property <bcp14>MUST
            </bcp14> be ignored and not used with the phonetic property. If this property is set, then at least one of
              the <tt>phoneticScript</tt> phoneticScript or <tt>phoneticSystem</tt> phoneticSystem properties that relate to this value <bcp14>MUST</bcp14> be set.</t>
            </li>
            <li>
              <t>phoneticScript: <tt>String</tt>. set.
            </dd>
            <dt>phoneticScript: String.</dt>
            <dd>
              The script used in the value of the related <tt>phonetic</tt> phonetic property. This <bcp14>MUST</bcp14> be a valid script
              subtag as defined in <xref target="RFC5646" section="2.2.3"/>.</t>
            </li>
            <li>
              <t>phoneticSystem: <tt>String</tt>. section="2.2.3"/>.
            </dd>
            <dt>phoneticSystem: String.</dt>
            <dd>
              <t>
                The phonetic system used in the related value of the <tt>phonetic</tt> phonetic property. The <xref target="enumerated-values">enumerated values</xref> are:</t>
              </xref> values are:
              </t>
              <ul>
                <li><tt>ipa</tt>:
                <li>ipa: denotes the <xref target="IPA">International Phonetic Alphabet</xref>.</li>
                <li><tt>jyut</tt>: Alphabet</xref>.
                </li>
                <li>jyut: denotes the Cantonese romanization system "Jyutping".</li>
                <li><tt>piny</tt>:
                <li>piny: denotes the Standard Mandarin romanization system "Hanyu Pinyin".</li>
              </ul>
            </li>
          </ul>
            </dd>
          </dl>
          <t>The relation between the <tt>phoneticSystem</tt>, <tt>phoneticScript</tt> phoneticSystem, phoneticScript, and <tt>phonetic</tt> phonetic properties is type-specific. This
            specification defines this relation in the <xref target="name">Name</xref> and <xref target="addresses">Address</xref> target="address">
              Address
            </xref> object types, respectively.</t> respectively.
          </t>
          <t>The following example illustrates the <tt>phonetic</tt> phonetic property for a <xref target="name">name</xref>:</t> target="name-prop">name</xref>:
          </t>
          <figure anchor="example-phonetic">
            <name>Example of <tt>phonetic</tt> a phonetic Property for the name Name "John Smith" as pronounced Pronounced in the USA.</name> USA</name>
            <sourcecode name="" type="json"><![CDATA[
"name": {
  "components": [{
    "kind": "given",
    "value": "John",
    "phonetic": "/ˈdʒɑːn/"
  }, {
    "kind": "surname",
    "value": "Smith",
    "phonetic": "/smɪθ/"
  }],
  "phoneticSystem": "ipa"
}
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="internationalization">
        <name>Internationalization</name>
        <t>JSContact aims to be used for international contacts and addressbook address book data. Notably Notably, text values such as
          names and addresses are likely to cover a wide range of languages and cultures. This section describes
          internationalization for free-form text values, values as well as for Uniform Resource Identifiers (URIs).</t> (URIs).
        </t>
        <section>
          <name>Free-form text</name>
          <name>Free-Form Text</name>
          <t>Properties having free-form text values <bcp14>MAY</bcp14> contain any valid sequence of Unicode characters
            encoded as a JSON string. Such values can contain unidirectional left-to-right and right-to-left text, as
            well as bidirectional text using Unicode Directional Formatting Characters as described in Section 2 of <xref target="UBiDi"/>. Implementations setting bidirectional text <bcp14>MUST</bcp14> make sure that each
            property value complies with the requirements of the Unicode Bidirectional Algorithm. Implementations <bcp14>MUST NOT</bcp14> <bcp14>
              MUST NOT
            </bcp14> assume that text values of adjacent properties are processed or displayed as a combined string, string; for example
            example, the values of a given name component and a surname component may or may not to be rendered together.</t> together.
          </t>
        </section>
        <section>
          <name>URIs</name>
          <t>Several properties require their string value to be a URI as defined in <xref target="RFC3986"/>.
            Implementations <bcp14>MUST</bcp14> make sure to use proper percent-encoding for URIs that can not cannot be
            represented using unreserved URI characters.
            <xref target="RFC3987" section="3.1"/>
            defines how to convert Internationalized Resource Identifiers to URIs.

            <!--[rfced] We notice that "URL Living Standard"
            <https://url.spec.whatwg.org> is from the WHATWG and not the
            W3C. We updated the running text and reference entry to reflect
            this as shown below. Please let us know if any further changes
            are needed.

            Original:
               JSContact makes no recommendation how to display URIs, but
               section "4.8.3 Internationalization and special characters"
               of the <xref target="W3C-URL">W3C W3C URL Standard [W3C-URL] provides guidance for URLs
               found in context of a web browser.

               [W3C-URL]  "W3C WG URL Standard</xref> - Living Standard - Last Updated 21 August
                          2023", <https://url.spec.whatwg.org>.

            Current:
               JSContact makes no recommendation on how to display URIs, but the
               WHATWG URL Living Standard (see "Internationalization and special characters"
               (Section 4.8.3) of [WHATWG-URL]) provides guidance for URLs found in
               the context of a web browser.</t> browser.

               [WHATWG-URL]  WHATWG, "URL Living Standard", January 2024,
                             <https://url.spec.whatwg.org>.
            -->

            JSContact makes no recommendation on how to display URIs, but the WHATWG URL Living Standard (see
            "Internationalization and special characters" (Section 4.8.3) of <xref target="WHATWG-URL"/>) provides
            guidance for URLs found in the context of a web browser.
          </t>
        </section>
      </section>
      <section anchor="validating-jscontact">
        <name>Validating JSContact</name>
        <t>This specification distinguishes between three kinds of properties regarding validation: IANA-registered
          properties and unknown properties properties, which are defined in this section, while and vendor-specific properties properties, which
          are defined in <xref target="vendor-specific-properties"/>. A JSContact object is invalid if any of its
          properties are invalid.</t> invalid.
        </t>
        <t>This document defines for whether each property if it is mandatory or optional. A mandatory property <bcp14>MUST</bcp14> <bcp14>MUST
        </bcp14> be present for a JSContact object to be valid. An optional property does not need to be present. The
          values of both required and optional properties <bcp14>MUST</bcp14> adhere to the data type and definition of
          that property.</t> property.
        </t>
        <section anchor="case-sensitivity">
          <name>Case-Sensitivity</name>
          <t>All property names, object type names names, and enumerated values are case-sensitive, if not unless explicitly stated
            otherwise in their according definition. definitions. Implementations <bcp14>MUST</bcp14> handle a JSContact object as invalid if
            a type name, property name name, or enumerated value only differs in case from one defined for any JSContact
            version known to that implementation. This applies regardless of what JSContact version the Card object
            defines in its <xref target="prop-version"><tt>version</tt></xref> target="prop-version">version</xref> property.
            <xref target="unknown-properties"/>
            defines how to handle unknown properties.</t> properties.
          </t>
        </section>
        <section anchor="iana-registered-properties" numbered="true" toc="default">
          <name>IANA-registered
          <name>IANA-Registered Properties</name>
          <t>
            An IANA-registered property is any property that has been registered according to the IANA property registry
            rules as outlined in <xref target="iana-considerations"/>. All properties defined in this specification,
            including their object value types and enumerated values, are registered at IANA.
          </t>
          <t>
            Implementations <bcp14>MUST</bcp14> validate IANA-registered properties in JSContact data, unless they are
            unknown to the implementation (see <xref (<xref target="unknown-properties"/>). They <bcp14>MUST</bcp14> reject invalid
            IANA-registered properties. A property is invalid if its name matches the name of an IANA-registered
            property but the value violates its definition according to the JSContact specification version defined in
            the Card <tt>version</tt> property (<xref target="prop-version"/>). <xref target="prop-version">version</xref> property.
          </t>
          <t>
          <t><!-- [rfced] The RFC Production Center has been advised that "ASCII"
            and not "US-ASCII" should be used.  May we change two instances
            of "US-ASCII" in this document to "ASCII"?

            Original:
               IANA-registered property names <bcp14>MUST NOT</bcp14> MUST NOT contain US-ASCII control
               characters (U+0000 to U+001F, U+007F), the <tt>COLON</tt> COLON (U+003A) or <tt>QUOTATION MARK</tt>
               QUOTATION MARK (U+0022) characters.  They <bcp14>MUST</bcp14> MUST only contain US-ASCII
               alphanumeric characters that match the ALPHA and DIGIT rules defined
               in Appendix B.1 of [RFC5234]) or the COMMERCIAL AT (U+0040)
               character.

            Perhaps:
               IANA-registered property names MUST NOT contain ASCII control
               characters (U+0000 to U+001F, U+007F), the COLON (U+003A) or
               QUOTATION MARK (U+0022) characters.  They MUST only contain ASCII
               alphanumeric characters that match the ALPHA and DIGIT rules defined
               in Appendix B.1 of [RFC5234]) or the COMMERCIAL AT (U+0040)
               character.
            -->

            IANA-registered property names <bcp14>MUST NOT</bcp14> contain ASCII control characters (U+0000 to U+001F,
            U+007F), the COLON (U+003A), or the QUOTATION MARK (U+0022). They <bcp14>MUST</bcp14> only contain ASCII
            alphanumeric characters that match the ALPHA and DIGIT rules defined in
            <xref target="RFC5234" section="B.1"/>) section="B.1"/>
            or the <tt>COMMERCIAL AT</tt> COMMERCIAL AT (U+0040) character. IANA-registered property names <bcp14>MUST</bcp14> be notated in
            lower camel case.
          </t>
        </section>
        <section anchor="reserved-properties">
          <name>Reserved Properties</name>
          <t>IANA-registered properties can be reserved (<xref target="iana-registry-policy"/>).  Implementations <bcp14>MUST NOT</bcp14> set properties having a reserved name in JSContact
            objects for which this property is reserved or all objects if the property context in the registry is "not applicable".
            Reserved properties have no type, and their type signature is "not applicable".  Any JSContact object including a property that is reserved in context of this object <bcp14>MUST</bcp14> be considered invalid.</t>
          <t>This document reserves one property:</t>
          <section anchor="prop-extra" numbered="true" toc="default">
            <name>extra</name>
            <dl spacing="normal">
              <dt>extra: not applicable.</dt>
              <dd>The reserved property "extra" provides implementors with a property name that is certain to never
                occur as a property in any JSContact object. Implementations might want to map unknown or vendor-specific
                properties to a variable with this name, but this is implementation-specific.
              </dd>
            </dl>
          </section>
        </section>
        <section anchor="unknown-properties" numbered="true" toc="default">
          <name>Unknown Properties</name>
          <t>
            Implementations may encounter JSContact data where a property name is unknown to that implementation, implementation but the
            name adheres to the syntactic restrictions of IANA-registered property names. Implementations <bcp14>MUST</bcp14> <bcp14>MUST
          </bcp14> make sure that such a name does not violate the case-sensitivity rules defined in <xref target="case-sensitivity"/>. If the property name is valid, then implementations <bcp14>MUST NOT</bcp14> NOT
          </bcp14> treat such properties as invalid. Instead, they <bcp14>MUST</bcp14> preserve them in the JSContact object.</t>
            object.
          </t>
          <t>Implementations that create or update JSContact data <bcp14>MUST</bcp14> only set IANA-registered
            properties or vendor-specific properties. Preserving properties that are unknown to the implementation, implementation is to
            allow applications and services to interoperate without data loss, even if not all of them implement the
            same set of JSContact extensions.
          </t>
        </section>
        <section anchor="enumerated-values" numbered="true" toc="default">
          <name>Enumerated Values</name>
          <t>Several properties in this document restrict their allowed values to be from a list of String values. These values
            are case-sensitive. If not noted otherwise for a specific property, the initial list of values for such
            properties is registered at IANA in the <xref target="iana-enum-registry">JSContact target="iana-enum-registry">"JSContact Enum Values Registry</xref>. Values"
              registry</xref>. Implementations <bcp14>MUST</bcp14> only set IANA-registered or <xref target="vendor-specific-values">vendor-specific</xref> target="vendor-specific-values">vendor-specific
            </xref> values for such properties.</t> properties.
          </t>
        </section>
      </section>
      <section anchor="vendor-specific-extensions">
        <name>Vendor-Specific Extensions</name>
        <t>Vendors may extend properties and values for experimentation or to store contacts data that only is only useful
          for a single service or application. Such extensions are not meant for interoperation.  If instead If, instead,
          interoperation is desired, vendors are strongly encouraged to define and register new properties, types types, and
          values at IANA. IANA as defined in <xref target="iana-considerations"/> defines how to register new properties, types or values at IANA. target="iana-considerations"/>.
          <xref target="iana-registered-properties"/>
          defines the naming conventions for IANA-registered elements.</t> elements.
        </t>
        <section anchor="vendor-specific-properties" numbered="true" toc="default">
          <name>Vendor-specific
          <name>Vendor-Specific Properties</name>
          <t>
            Vendor-specific property names <bcp14>MUST</bcp14> start with a vendor-specific prefix followed by a name,
            as produced by the <tt>v-extension</tt> "v-extension" ABNF below. The prefix and name together form the property name. The
            vendor-specific prefix <bcp14>MUST</bcp14> be a domain name under control of the service or application that
            sets the property, but it need not resolve in the Domain Name System
            <xref target="RFC1034"/> and
            <xref target="RFC1035"/>. The prefix <tt>ietf.org</tt> "ietf.org" and its subdomain names are reserved for IETF
            specifications. The name <bcp14>MUST NOT</bcp14> contain the <tt>TILDE</tt> TILDE (U+007E) and <tt>SOLIDUS</tt> SOLIDUS (U+002F) characters,
            as these require special-escaping special escaping when encoding a JSON Pointer
            <xref target="RFC6901"/>
            for that property.
          </t>
          <t>
            Vendor-specific properties <bcp14>MAY</bcp14> be set in any JSContact object. Implementations <bcp14>MUST</bcp14> <bcp14>MUST
          </bcp14> preserve vendor-specific properties in JSContact data, irrespective if they know their use. They <bcp14>MUST NOT</bcp14> <bcp14>
            MUST NOT
          </bcp14> reject the property value as invalid, unless they are in control of the vendor-specific property as
            outlined in the above paragraph.
          </t>
          <t>The ABNF rule <tt>v-extension</tt> "v-extension" formally defines valid vendor-specific property names. Note that the vendor
            prefix allows for more values than are allowed as Internationalized Domain Names (IDN) (IDNs) <xref target="RFC8499"/>.  This is to allow target="RFC8499"/>; therefore,
            JSContact implementations can simply validate property names without implementing the full set of rules that
            apply to domain names.</t> names.
          </t>
          <figure anchor="vendor-property-abnf">
            <name>ABNF rules Rules for vendor-specific property names</name> Vendor-Specific Property Names</name>
            <sourcecode name="" type="abnf"><![CDATA[
v-extension = v-prefix ":" v-name

v-prefix = v-label *("." v-label)

v-label = alnum-int / alnum-int *(alnum-int / "-") alnum-int

alnum-int = ALPHA / DIGIT / NON-ASCII
  ; see RFC 6350 6350, Section 3.3

v-name = 1*(WSP / "!" / %x23-2e / %x30-7d / NON-ASCII)
  ; any characters except CTLs, DQUOTE, SOLIDUS SOLIDUS, and TILDE
]]></sourcecode>
          </figure>
          <t>
            The value of vendor-specific properties can be any valid JSON value, and naming restrictions do not apply to
            such values. Specifically, if the property value is a JSON object object, then the keys of such objects need not be
            named as vendor-specific properties.  The example properties, as illustrated in <xref target="vendor-property-example"/> illustrates this: target="vendor-property-example"/>:
          </t>
          <figure anchor="vendor-property-example">
            <name>Examples of vendor-specific properties</name>
            <artwork><![CDATA[ Vendor-Specific Properties</name>
            <sourcecode type=""><![CDATA[
"example.com:foo": "bar",
"example.com:foo2": {
  "bar": "baz"
}
]]></artwork>
]]></sourcecode>
          </figure>
        </section>
        <section anchor="vendor-specific-values" numbered="true" toc="default">
          <name>Vendor-specific
          <name>Vendor-Specific Values</name>
          <t>
            Some JSContact IANA-registered properties allow their values to be vendor-specific. One such example is the <tt>kind</tt> property  <xref target="kind"/>, target="kind">"kind"
          </xref> property, which enumerates its standard values but also allows for arbitrary vendor-specific values.
            Such vendor-specific values <bcp14>MUST</bcp14> be valid <tt>v-extension</tt> "v-extension" values as defined in <xref target="vendor-specific-properties"/>. The example in
            <xref target="vendor-value-example"/>
            illustrates this:
          </t>
          <figure anchor="vendor-value-example">
            <name>Example of a vendor-specific value</name>
            <artwork><![CDATA[ Vendor-Specific Value</name>
            <sourcecode><![CDATA[
"kind": "example.com:baz"
]]></artwork>
]]></sourcecode>
          </figure>
          <t>
            Vendors are strongly encouraged to specify a new standard value once a vendor-specific one turns out to also
            be useful also for other systems.
          </t>
        </section>
      </section>
      <section anchor="versioning">
        <name>Versioning</name>
        <t>Every instance of a JSContact <xref target="card">Card</xref> indicates which JSContact version its
          IANA-registered properties and values are based on.

          <!--[rfced] As "MIME" is no longer used in the IANA registry, may we
          update the text as follows?

          Original:
             The version is indicated both in the version (Section 2.1.2)
             property within the Card and in the version (Section 3.1) parameter
             of the JSContact MIME content type.

          Perhaps:
             The version is indicated both in the version (Section 2.1.2)
             property within the Card and in the version (Section 3.1) parameter
             of the JSContact media type.
          -->

          The version is indicated both in the <xref target="prop-version"><tt>version</tt></xref> target="prop-version">version</xref> property within the Card and
          in the <xref target="iana-media-type">version</xref> parameter of the JSContact MIME content media type. All
          IANA-registered elements indicate the version at which they got were introduced or obsoleted.</t>
        <section>
          <name>Version Format and Requirements</name> obsoleted.
        </t>
        <t>A JSContact version consists of a numeric major and minor version, separated by the <tt>FULL STOP</tt> character (U+002E).  Later versions are numerically higher than former versions, with the major version being more significant than the minor version. A version value is produced by the ABNF</t>
          <sourcecode name="" type="abnf"><![CDATA[
jsversion = 1*DIGIT "." 1*DIGIT
]]></sourcecode> version.</t>
        <t>Differing major version values indicate substantial differences in JSContact semantics and format.
          Implementations <bcp14>MUST</bcp14> be prepared that for property definitions and other JSContact elements that
          differ in a backwards-incompatible manner.</t> manner.
        </t>
        <t>Differing minor version values indicate additions that enrich JSContact data, data but do not introduce
          backwards-incompatible changes. Typically, these are new property enum values or properties with a narrow
          semantic scope. A new minor version <bcp14>MUST NOT</bcp14> require implementations to change their processing
          of JSContact data. Changing the major version number resets the minor version number to zero.</t> zero.
        </t>
        <section anchor="version-format-and-reqs">
          <name>Version Format and Requirements</name>
          <t>A version value starts with the numeric major version, followed by the FULL STOP character (U+002E),
            followed by the numeric minor version. Later versions are numerically higher than former versions, with the
            major version being more significant than the minor version. A version value is produced by the following
            ABNF:
          </t>
          <!--[rfced] Should Figure 5 have a title? Please review, and provide
          a title if desired.
          -->
          <figure>
            <name>The ABNF for JSContact Version Values</name>
            <sourcecode name="" type="abnf"><![CDATA[
jsversion = 1*DIGIT "." 1*DIGIT
]]></sourcecode>
          </figure>
        </section>
        <section anchor="current-version">
          <name>Current Version</name>
          <t>This specification registers JSContact version value <tt>1.0</tt> "1.0" (<xref target="tab-iana-version-registry"/>).</t> target="tab-iana-version-registry"/>).
          </t>
        </section>
      </section>
    </section>
    <section anchor="card" numbered="true" toc="default">
      <name>Card</name>
      <t>This section defines the JSContact object type Card. A Card stores contact information, typically that of a
        person, organization organization, or company.</t> company.
      </t>
      <t>Its media type is defined in <xref target="iana-media-type"/>.</t> target="iana-media-type"/>.
      </t>
      <t><xref target="example-card"/>
        shows a basic Card for the person "John Doe". As the object is the topmost object in the JSON data data, it has the <tt>@type</tt>
        @type property set according to the rules defined in <xref target="prop-type"/>.</t> target="prop-type"/>.
      </t>
      <figure anchor="example-card">
        <name>Example of a basic <tt>Card</tt></name> Basic Card</name>
        <sourcecode name="" type="json"><![CDATA[
{
  "@type": "Card",
  "version": "1.0",
  "uid": "22B2C7DF-9120-4969-8460-05956FE6B065",
  "kind": "individual",
  "name": {
    "components": [
      { "kind": "given", "value": "John" },
      { "kind": "surname", "value": "Doe" }
    ],
    "isOrdered": true
  }
}
]]></sourcecode>
      </figure>
      <section anchor="metadata-properties" numbered="true" toc="default">
        <name>Metadata Properties</name>
        <t>This section defines properties about this instance of a Card, Card such as its unique identifier, its creation
          date, and how it relates to other Cards and other metadata information.</t> information.
        </t>
        <section anchor="cardtype" numbered="true" toc="default">
          <name>@type</name>
          <t>Type: <tt>String</tt> (mandatory).</t>
          <t>This
          <dl spacing="normal">
            <dt>@type: String (mandatory).</dt>
            <dd>The JSContact type of the Card object. The value <bcp14>MUST</bcp14> be <tt>Card</tt>, if set.</t> "Card".
            </dd>
          </dl>
        </section>
        <section anchor="prop-version" numbered="true" toc="default">
          <name>version</name>
          <t>Type: <tt>String</tt> (mandatory).</t>
          <t>Specifies the
          <dl spacing="normal">
            <dt>version: String (mandatory).</dt>
            <dd>The JSContact version used to define of this Card. The value <bcp14>MUST</bcp14> be one of
              the IANA-registered JSContact Enum Values Version values for the <tt>version</tt> version property. Also see <xref target="current-version"/>.</t> target="current-version"/>.
            </dd>
          </dl>
          <figure anchor="example-version">
            <name><tt>version</tt> example</name>
            <name>Example for the version Property</name>
            <sourcecode name="" type="json"><![CDATA[
"version": "1.0"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="created" numbered="true" toc="default">
          <name>created</name>
          <t>Type: <tt>UTCDateTime</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>created: UTCDateTime (optional).</dt>
            <dd>The date and time when this the Card was created.</t> created.</dd>
          </dl>
          <figure anchor="example-created">
            <name><tt>created</tt> example</name>
            <name>Example for the created Property</name>
            <sourcecode name="" type="json"><![CDATA[
"created": "2022-09-30T14:35:10Z"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="kind" numbered="true" toc="default">
          <name>kind</name>
          <t>Type: <tt>String</tt> (optional,
          <dl spacing="normal">
            <dt>kind: String (optional; default: <tt>individual</tt>).  The "individual").</dt>
            <dd>
              <t>The kind of the entity the Card represents.</t>
              <t>The <xref target="enumerated-values">enumerated</xref> values are:</t> are:
              </t>
              <ul spacing="normal">
            <li><tt>individual</tt>:
                <!--[rfced] In Section 2.1.4 under the definition of "device", we made
                the examples singular since "device" is singular. If you prefer
                otherwise, please let us know.

                Original:
                   *  device: a device, such as appliances, computers, or network
                      elements

                Current:
                   *  device: a device such as an appliance, a computer, or a network
                      element
                -->
                <li>individual: a single person</li>
            <li><tt>group</tt>:
                <li>group: a group person of persons people or entities</li>
            <li><tt>org</tt>:
                <li>org: an organization</li>
            <li><tt>location</tt>:
                <li>location: a named location</li>
            <li><tt>device</tt>:
                <li>device: a device, device such as appliances, computers, an appliance, a computer, or a network elements</li>
            <li><tt>application</tt>: element</li>
                <li>application: a software application</li>
              </ul>
            </dd>
          </dl>
          <figure anchor="example-kind">
            <name><tt>kind</tt> example</name>
            <name>Example for the kind Property</name>
            <sourcecode name="" type="json"><![CDATA[
"kind": "individual"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="language" numbered="true" toc="default">
          <name>language</name>
          <t>Type: <tt>String</tt> (optional).</t>
          <t>This is the
          <dl spacing="normal">
            <dt>language: String (optional).</dt>
            <dd>
              <t>The language tag, as defined in <xref target="RFC5646"/>, that best describes the language used
                for text in the Card, optionally including additional information such as the script. Note that values <bcp14>MAY</bcp14> <bcp14>
                  MAY
                </bcp14> be localized in the <tt>localizations</tt> property  <xref target="localizations"/>.</t> target="localizations">
                  localizations
                </xref> property.
              </t>
            </dd>
          </dl>
          <figure anchor="example-language">
            <name><tt>language</tt> example</name>
            <name>Example for the language Property</name>
            <sourcecode name="" type="json"><![CDATA[
"language": "de-AT"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="members" numbered="true" toc="default">
          <name>members</name>
          <t>Type: <tt>String[Boolean]</tt> (optional).</t>
          <t>This identifies the
          <dl spacing="normal">
            <dt>members: String[Boolean] (optional).</dt>
            <dd>
              <t>The set of Cards that are members of this group Card. Each key in the set is the <tt>uid</tt> uid
                property value of the member, and each boolean value <bcp14>MUST</bcp14> be <tt>true</tt>. "true". If this property is
                set, then the value of the <tt>kind</tt> kind property <bcp14>MUST</bcp14> be <tt>group</tt>.</t> "group".
              </t>
              <t>The opposite is not true. A group Card will usually contain the <tt>members</tt> members property to specify the members
                of the group, but it is not required to. A group Card without the <tt>members</tt> members property can be considered an
                abstract grouping, grouping or one whose members are known empirically (e.g., "IETF Participants").</t> Participants").
              </t>
            </dd>
          </dl>
          <figure anchor="example-members">
            <name><tt>members</tt> example</name>
            <name>Example for the members Property</name>
            <sourcecode name="" type="json"><![CDATA[
"kind": "group",
"name": {
  "full": "The Doe family"
},
"uid": "urn:uuid:ab4310aa-fa43-11e9-8f0b-362b9e155667",
"members": {
  "urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af": true,
  "urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519": true
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="prodId" numbered="true" toc="default">
          <name>prodId</name>
          <t>Type: <tt>String</tt> (optional).</t>
          <dl spacing="normal">
            <dt>prodId: String (optional).</dt>
            <dd>
              <t>The identifier for the product that created the Card. If set, the value <bcp14>MUST</bcp14> be at least
                one character long.</t> long.
              </t>
            </dd>
          </dl>
          <figure anchor="example-prodId">
            <name><tt>prodId</tt> example</name>
            <name>Example for the prodId Property</name>
            <sourcecode name="" type="json"><![CDATA[
"prodId": "ACME Contacts App version 1.23.5"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="relatedTo" numbered="true" toc="default">
          <name>relatedTo</name>
          <t>Type: <tt>String[Relation]</tt> (optional).</t>
          <t>Relates the object
          <dl spacing="normal">
            <dt>relatedTo: String[Relation] (optional).</dt>
            <dd>
              <t>The set of Card objects that relate to other Cards.  This the Card. The value is represented as a map, where each key is the <tt>uid</tt> uid property
                value of the related Card Card, and the value defines the relation.  The
              </t>
            </dd>
          </dl>
          <t>The Relation object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
            This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Relation</tt>, "Relation", if set.
         </li>
            <li>
              <t>relation: <tt>String[Boolean]</tt> (optional,
            </dd>
            <dt>relation: String[Boolean] (optional; default: empty Object)
                Describes how Object).</dt>
            <dd>
              <t>The relationship of the linked object is related Card to the linking object.  The relation is Card, defined as a set of relation types.
              The key keys in the set defines define the relation type, type; the value values for each key in the set <bcp14>MUST</bcp14> be <tt>true</tt>. "true".
              The relationship between the two objects is undefined if the set is empty.</t> empty.
              </t>
              <t>The initial list of <xref target="enumerated-values">enumerated</xref> relation types matches the
                IANA-registered <xref target="IANAvCard">TYPE parameter</xref> target="IANA-vCard">TYPE</xref> parameter values of the vCard RELATED property
                (<xref target="RFC6350" section="6.6.6"/>):</t> section="6.6.6"/>):
              </t>
              <!--[rfced] In Section 2.1.8, we updated the order of the enumerated
              relation types list by moving "co-resident" and "co-worker" above
              "colleague". The list is now in alphabetical order. Please let us
              know of any objections.

              There are several other lists in the document. Please review and let
              us know if any other terms should be placed in alphabetical order.
              -->
              <ul>
                <li>
                  <tt>acquaintance</tt>
                  acquaintance
                </li>
                <li>
                  <tt>agent</tt>
                  agent
                </li>
                <li>
                  <tt>child</tt>
                  child
                </li>
                <li>
                  <tt>colleague</tt>
                  co-resident
                </li>
                <li>
                  <tt>contact</tt>
                  co-worker
                </li>
                <li>
                  <tt>co-resident</tt>
                  colleague
                </li>
                <li>
                  <tt>co-worker</tt>
                  contact
                </li>
                <li>
                  <tt>crush</tt>
                  crush
                </li>
                <li>
                  <tt>date</tt>
                  date
                </li>
                <li>
                  <tt>emergency</tt>
                  emergency
                </li>
                <li>
                  <tt>friend</tt>
                  friend
                </li>
                <li>
                  <tt>kin</tt>
                  kin
                </li>
                <li>
                  <tt>me</tt>
                  me
                </li>
                <li>
                  <tt>met</tt>
                  met
                </li>
                <li>
                  <tt>muse</tt>
                  muse
                </li>
                <li>
                  <tt>neighbor</tt>
                  neighbor
                </li>
                <li>
                  <tt>parent</tt>
                  parent
                </li>
                <li>
                  <tt>sibling</tt>
                  sibling
                </li>
                <li>
                  <tt>spouse</tt>
                  spouse
                </li>
                <li>
                  <tt>sweetheart</tt>
                </li>
              </ul>
                  sweetheart
                </li>
              </ul>
            </dd>
          </dl>
          <figure anchor="example-relatedto">
            <name><tt>relatedTo</tt> example</name>
            <name>Example for the relatedTo Property</name>
            <sourcecode name="" type="json"><![CDATA[
"relatedTo": {
  "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6": {
    "relation": {
      "friend": true
    }
  },
  "8cacdfb7d1ffdb59@example.com": {
    "relation": {}
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="uid" numbered="true" toc="default">
          <name>uid</name>
          <t>Type: <tt>String</tt> (mandatory).</t>
          <dl spacing="normal">
            <dt>uid: String (mandatory).</dt>
            <dd>
              <t>An identifier, used to associate identifier that associates the object as the same across different systems, address books books,
                and views. The value <bcp14>SHOULD</bcp14> be a URN <xref target="RFC8141"/> target="RFC8141"/>, but for compatibility with
                <xref target="RFC6350"/> target="RFC6350"/>, it <bcp14>MAY</bcp14> also be a URI
                <xref target="RFC3986"/>
                or free-text value. The value of the URN <bcp14>SHOULD</bcp14> be in the <tt>uuid</tt> "uuid" namespace <xref target="RFC4122" format="default"/>.
              </t>
              <!--[rfced] FYI: For clarity and ease of reading, we added a reference
              to RFC 4122 as shown below.

              Original:
                 As of this writing, a <xref target="I-D.ietf-uuidrev-rfc4122bis">revision</xref> revision [I-D.ietf-uuidrev-rfc4122bis] of the
                 UUID standard document is being worked on and is likely to
                 introduce new UUID versions and best practices to generate global
                 unique identifiers.

              Current:
                 As of this writing, a revision [UUID] of the Universally Unique
                 Identifier (UUID) Standards Track document [RFC4122] is in
                 progress and will likely introduce new UUID versions and
                 best practices for generating global unique identifiers [UUID].
              -->
              <t>As of this writing, a <xref target="I-D.ietf-uuidrev-rfc4122bis">revision</xref> of the Universally
                Unique Identifier (UUID) Standards Track document
                <xref target="RFC4122" format="default"/>
                is in progress and will likely introduce new UUID versions and best practices to generate global unique
                identifiers. Implementors <bcp14>SHOULD</bcp14> follow any recommendations described there. Until then,
                implementations <bcp14>SHOULD</bcp14> generate identifiers using the random or pseudo-random pseudorandom UUID version
                described in <xref target="RFC4122" section="4.4"/>.</t> section="4.4"/>.
              </t>
            </dd>
          </dl>
          <figure anchor="example-uid">
            <name><tt>uid</tt> example</name>
            <name>Example for the uid Property</name>
            <sourcecode name="" type="json"><![CDATA[
"uid": "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"
]]></sourcecode>
          </figure>
        </section>
        <section anchor="updated" numbered="true" toc="default">
          <name>updated</name>
          <t>Type: <tt>UTCDateTime</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>updated: UTCDateTime (optional).</dt>
            <dd>The date and time when the data in this the Card was last modified.</t> modified.</dd>
          </dl>
          <figure anchor="example-updated">
            <name><tt>updated</tt> example</name>
            <name>Example for the updated Property</name>
            <sourcecode name="" type="json"><![CDATA[
"updated": "2021-10-31T22:27:10Z"
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="name-and-organization-properties" numbered="true" toc="default">
        <name>Name and Organization Properties</name>
        <t>This section defines properties that name the entity represented by this Card, the Card and its related organizations
          and roles, as well as roles. It also describes how to refer to the entity represented by this the Card in spoken or written language.</t> language.
        </t>
        <section anchor="name" anchor="name-prop" numbered="true" toc="default">
          <name>name</name>
          <t>Type: <tt>Name</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>name: Name (optional).</dt>
            <dd>The name of the entity represented by this the Card. This can be any type of name, e.g., it can can, but need not
              not, be the legal name of a person.</t>
          <section> person.
            </dd>
          </dl>
          <section anchor="name">
            <name>Name object</name> Object</name>
            <t>A Name object has the following properties</t>
            <ul properties:</t>
            <dl spacing="normal">
              <li>@type: <tt>String</tt>.
              This
              <dt>@type: String.</dt>
              <dd>
                The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Name</tt>, "Name", if set.
          </li>
              <li>
                <t>components: <tt>NameComponent[]</tt> (optional).  The
              </dd>
              <dt>components: NameComponent[] (optional).</dt>
              <dd>
                <t>The <xref target="namecomponent">components</xref> making up this name.  This The components property <bcp14>MUST</bcp14> <bcp14>
                  MUST
                </bcp14> be set if the <tt>full</tt> full property is not set, otherwise set; otherwise, it <bcp14>SHOULD</bcp14> be set. The
                  component list <bcp14>MUST</bcp14> have at least one entry having a different <tt>kind</tt> kind property value than <tt>separator</tt>.</t>
                  "separator".
                </t>
                <t>Name components <bcp14>SHOULD</bcp14> be ordered such that when their values are joined as a String produce String,
                  a valid full name of this entity. the entity is produced. If so, implementations <bcp14>MUST</bcp14> set the <tt>isOrdered</tt>
                  isOrdered property value to <tt>true</tt>.</t> "true".
                </t>
                <t>If the name components are ordered, then the <tt>defaultSeparator</tt> defaultSeparator property and name components of with the
                  kind <tt>separator</tt> property value set to "separator" give guidance on what characters to insert between components,
                  but implementations are free to choose any others.  In lack of When lacking a separator, inserting a single Space space
                  character in between the name component values is a good choice.</t>
                <t>If instead choice.
                </t>
                <t>If, instead, the name components follow no particular order, then the <tt>isOrdered</tt> isOrdered property value <bcp14>MUST</bcp14> <bcp14>
                  MUST
                </bcp14> be <tt>false</tt>, "false", the <tt>components</tt> components property <bcp14>MUST NOT</bcp14> contain a NameComponent of with the
                  kind <tt>separator</tt> property value set to "separator", and the <tt>defaultSeparator</tt> defaultSeparator property <bcp14>MUST NOT</bcp14> be set.</t>
                  set.
                </t>
                <t><xref target="example-name-twoword"/> is
                  shows an example for the name "Vincent van Gogh". Note how a single name component value may consist
                  of multiple words.  <xref target="example-name-surname2"/> illustrates a name with a second surname, such as a Spanish name.  Additional examples are shown in <xref target="example-name-sortas"/> and <xref target="example-localizations-replace"/>.</t>
                </t>
                <figure anchor="example-name-twoword">
                  <name>Example for of a surname Surname with two words</name> Two Words</name>
                  <sourcecode name="" type="json"><![CDATA[
"name": {
  "components": [
    { "kind": "given", "value": "Vincent" },
    { "kind": "surname", "value": "van Gogh" }
  ],
  "isOrdered": true
}
]]></sourcecode>
                </figure>
                <!--[rfced] FYI: The text that describes Figure 16 was located above
                Figure 15, so we placed it above Figure 16 instead. The update is
                shown in Section 2.2.1.1.
                -->
                <t><xref target="example-name-surname2"/>
                  illustrates a name with a second surname such as a Spanish name. Additional examples are shown in
                  Figures
                  <xref target="example-name-sortas" format="counter"/>
                  and <xref target="example-localizations-replace" format="counter"/>.
                </t>
                <figure anchor="example-name-surname2">
                  <name>Example for of a second surname</name> Second Surname</name>
                  <sourcecode name="" type="json"><![CDATA[
"name": {
  "components": [
    { "kind": "given", "value": "Diego" },
    { "kind": "surname", "value": "Rivera" },
    { "kind": "surname2", "value": "Barrientos" }
  ],
  "isOrdered": true
}
]]></sourcecode>
                </figure>
              </li>
              <li>isOrdered: <tt>Boolean</tt> (optional,
              </dd>
              <dt>isOrdered: Boolean (optional; default: <tt>false</tt>).  This indicates "false").</dt>
              <dd>The indicator if the name component sequence components in the <tt>components</tt> components property is ordered.</li>
              <li>defaultSeparator: <tt>String</tt> (optional). are ordered.</dd>
              <dt>defaultSeparator: String (optional).</dt>
              <dd>
                The default separator to insert between name component values when concatenating all name component
                values to a single String.

                <!--[rfced] FYI: For ease, we added links to Sections 2.2.1.2
                (NameComponent) and 2.5.1.2 (AddressComponent) in the text
                shown below. If any further updates are needed, please let us
                know.

                Section 2.2.1.1
                Original:
                   Also see the definition of the <tt>separator</tt> separator kind for
                   the NameComponent object.  This

                Current:
                   Also see the definition of the separator kind for
                   the NameComponent (Section 2.2.1.2) object.
                ...
                Section 2.5.1.1
                Original:
                   Also see the definition of the separator kind
                   for the AddressComponent object.

                Current:
                   Also see the definition of the separator kind
                   for the AddressComponent (Section 2.5.1.2) object.
                -->    Also see the definition of the kind property value "separator" for the <xref target="namecomponent">
                NameComponent
              </xref> object. The defaultSeparator property <bcp14>MUST NOT</bcp14> be set if the Name <tt>isOrdered</tt> isOrdered
                property value is <tt>false</tt> "false" or if the <tt>components</tt> components property is not set.</li>
              <li>
                <t>full: <tt>String</tt> (optional).
            This is the set.
              </dd>
              <dt>full: String (optional).</dt>
              <dd>
                <t>
                  The full name representation of this the Name.  This The full property <bcp14>MUST</bcp14> be set if the <tt>components</tt>
                  components property is not set.</t> set.
                </t>
                <figure anchor="example-full">
                  <name><tt>full</tt> example</name>
                  <name>Example for the full Property</name>
                  <sourcecode name="" type="json"><![CDATA[
"full": "Mr. John Q. Public, Esq."
]]></sourcecode>
                </figure>
              </li>
              <li>
                <t>sortAs: <tt>String[String]</tt> (optional).</t>
                <t>This defines how this name
              </dd>
              <dt>
                sortAs: String[String] (optional).
              </dt>
              <dd>
                <t>The value to lexicographically sorts sort the name in relation to other names when compared by a name
                  component type. The key keys in the map defines define the name component type. The value for that key defines values define the
                  verbatim string to compare when sorting by this the name component type. Absence of a key indicates that this
                  the name component type <bcp14>SHOULD NOT</bcp14> be considered during sort. Sorting by that missing
                  name component type type, or if the <tt>sortAs</tt> sortAs property is not set set, is implementation-specific.  This The sortAs
                  property <bcp14>MUST NOT</bcp14> be set if the <tt>components</tt> components property is not set.</t> set.
                </t>
                <t>Each key in the map <bcp14>MUST</bcp14> be a valid name component type value as defined for the <tt>kind</tt> kind
                  property of the NameComponent object (see below). For each key in the map map, there <bcp14>MUST</bcp14> exist
                  at least one NameComponent object having that has the type in the <tt>components</tt> components property of this name.</t> the name.
                </t>
                <t><xref target="example-name-sortas"/>
                  illustrates the use of sortAs. the sortAs property. The property value indicates that the middle name followed
                  by both surnames should be used when sorting this the name by surname. The absence of the <tt>middle</tt> "middle" indicates
                  that the middle name on its own should be disregarded during sort. Even though the name only contains
                  one name component for the given name, the sortAs property still explicitly defines how to sort by the
                  given name as otherwise name; otherwise, sorting by it would be undefined.</t>
              </li>
              <li>
                <t>phoneticScript: <tt>String</tt> undefined.
                </t>
              </dd>
              <dt>
                phoneticScript: String (optional).
              </dt>
              <dd>
                The script used in the value of the NameComponent <tt>phonetic</tt> phonetic property.  Also see <xref target="prop-phonetic"/>. See
                <xref target="prop-phonetic"/>
                for more information and
                <xref target="example-name-phonetic"/>
                for an example.</t>
              </li>
              <li>
                <t>phoneticSystem: <tt>String</tt> example.
              </dd>
              <dt>
                phoneticSystem: String (optional).
              </dt>
              <dd>
                <t>
                  The phonetic system used in the NameComponent <tt>phonetic</tt> phonetic property.  Also      see <xref target="prop-phonetic"/>. See
                  <xref target="prop-phonetic"/>
                  for more information and
                  <xref target="example-name-phonetic"/>
                  for an example.</t>
              </li>
            </ul> example.
                </t>
              </dd>
            </dl>
            <figure anchor="example-name-sortas">
              <name>Example for <tt>sortAs</tt></name> the sortAs Property</name>
              <sourcecode name="" type="json"><![CDATA[
"name": {
  "components": [
    { "kind": "given", "value": "Robert" },
    { "kind": "given2", "value": "Pau" },
    { "kind": "surname", "value": "Shou Chang" }
  ],
  "sortAs": {
    "surname": "Pau Shou Chang",
    "given": "Robert"
  },
  "isOrdered": true
}
]]></sourcecode>
            </figure>
            <figure anchor="example-name-phonetic">
              <name>Example for <tt>phonetic</tt> the phonetic and <tt>localizations</tt></name>
            <artwork><![CDATA[ localizations Properties</name>
              <sourcecode type=""><![CDATA[
{
  "@type": "Card",
  "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"
    }
  }
}
]]></artwork>
]]></sourcecode>
            </figure>
          </section>
          <section anchor="namecomponent">
            <name>NameComponent</name>
            <t>A NameComponent object has the following properties:</t>
            <ul
            <dl spacing="normal">
              <li>@type: <tt>String</tt>.
              This
              <dt>@type: String.</dt>
              <dd>
                The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>NameComponent</tt>, "NameComponent", if set.
          </li>
              <li>value: <tt>String</tt> (mandatory).
              </dd>
              <dt>value: String (mandatory).</dt>
              <dd>
                The value of this the name component. This can be composed of one or multiple words, words such as "Poe" or "van Gogh".</li>
              <li>
                <t>kind: <tt>String</tt> (mandatory).
                Gogh".
              </dd>
              <dt>kind: String (mandatory).</dt>
              <dd>
                <t>
                  The kind of this the name component. The <xref target="enumerated-values">enumerated</xref> values are:
                </t>
                <ul spacing="normal">
                  <li><tt>title</tt>:
                  <li>title: an honorific title or prefix, e.g.,  "Mr", "Ms", "Dr".</li>
                  <li><tt>given</tt>: "Mr.", "Ms.", or "Dr.".</li>
                  <li>given: a given name, also known as "first name", name" or "personal name".</li>
                  <li><tt>given2</tt>:
                  <li>given2: a name that appears between the given and surname, surname such as a middle name or patronymic name.</li>
                  <li><tt>surname</tt>:
                    name.
                  </li>
                  <li>surname: a surname, also known as "last name", name" or "family name".</li>
                  <li><tt>surname2</tt>:
                  <li>surname2: a secondary surname (used in some cultures), also known as "maternal surname".</li>
                  <li><tt>credential</tt>:
                  <li>credential: a credential, also known as "accreditation qualifier" or "honorific suffix", e.g.,
                    "B.A.", "Esq.".</li>
                  <li><tt>generation</tt>: "Esq.".
                  </li>
                  <li>generation: a generation marker or qualifier, e.g.,  “Jr.” "Jr." or “III”.</li>
                  <li><tt>separator</tt>: "III".</li>
                  <li>separator: a formatting separator between two ordered name non-separator components. The <tt>value</tt> value
                    property of the component includes the verbatim separator, for example example, a hyphen character or even
                    an empty string. This value has higher precedence than the <tt>defaultSeparator</tt> defaultSeparator property of the Name.
                    Implementations <bcp14>MUST NOT</bcp14> insert two consecutive separator components, instead components; instead, they <bcp14>SHOULD</bcp14> <bcp14>
                      SHOULD
                    </bcp14> insert a single separator component with the combined value. This component kind <bcp14>MUST NOT</bcp14> <bcp14>
                      MUST NOT
                    </bcp14> be set if the Name <tt>isOrdered</tt> isOrdered property value is <tt>false</tt>.</li>
                </ul> "false".
                  </li>
              <li>phonetic: <tt>String</tt> (optional).  This defines how to pronounce this
                </ul>
              </dd>
              <dt>phonetic: String (optional).</dt>
              <dd>The pronounciation of the name component. If this property is set, then at least one of the Name
                object <tt>phoneticSystem</tt> properties, phoneticSystem or <tt>phoneticScript</tt> properties phoneticScript, <bcp14>MUST</bcp14> be set. Also see <xref target="prop-phonetic"/>.</li>
            </ul> target="prop-phonetic"/>.
              </dd>
            </dl>
          </section>
        </section>
        <section anchor="nicknames" numbered="true" toc="default">
          <name>nicknames</name>
            <t>Type: <tt>Id[Nickname]</tt> (optional).</t>
            <t>The
          <dl spacing="normal">
            <dt>nicknames: Id[Nickname] (optional).</dt>
            <dd>The nicknames of the entity represented by this Card.  A the Card.</dd>
          </dl>
          <t>A Nickname object has the following properties:</t>
            <ul
          <dl spacing="normal">
              <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Nickname</tt>, "Nickname", if set.
          </li>
              <li>name: <tt>String</tt> (mandatory).
            </dd>
            <dt>name: String (mandatory).</dt>
            <dd>
              The nickname.
        </li>
              <li>contexts: <tt>String[Boolean]</tt> (optional)
The
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which to use this the nickname. Also see <xref target="prop-contexts"/>.</li>
              <li>pref: <tt>UnsignedInt</tt> (optional). target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>
              The preference of this the nickname in relation to other nicknames. Also see <xref target="prop-pref"/>.</li>
            </ul> target="prop-pref"/>.
            </dd>
          </dl>
          <figure anchor="example-nicknames">
              <name><tt>nicknames</tt> example</name>
            <name>Example for the nicknames Property</name>
            <sourcecode name="" type="json"><![CDATA[
"nicknames": {
  "k391": {
    "name": "Johnny"
  }
}
]]></sourcecode>
          </figure>
        </section>
        </section>
        <section anchor="organizations" numbered="true" toc="default">
          <name>organizations</name>
          <t>Type: <tt>Id[Organization]</tt> (optional).</t>
          <t>The companies
          <dl spacing="normal">
            <dt>organizations: Id[Organization] (optional).</dt>
            <dd>The company or organizations organization names and units associated with this Card.  An the Card.</dd>
          </dl>
          <t>An Organization object has the following properties, of which at least one of the <tt>name</tt> name and <tt>units</tt> units properties <bcp14>MUST</bcp14> <bcp14>
            MUST
          </bcp14> be set:</t>
          <ul set:
          </t>
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Organization</tt>, "Organization", if set.
          </li>
            <li>name: <tt>String</tt> (optional).
            </dd>
            <dt>name: String (optional).</dt>
            <dd>
              The name of this the organization.
        </li>
            <li>units: <tt>OrgUnit[]</tt> (optional).
            A
            </dd>
            <dt>units: OrgUnit[] (optional).</dt>
            <dd>A list of organizational units, ordered as descending by hierarchy (e.g., a geographic or functional
              division sorts before a department within that division). If set, the list <bcp14>MUST</bcp14> contain at
              least one entry.
        </li>
            <li>sortAs: <tt>String</tt> (optional).
            This defines how this organization name
            </dd>
            <dt>sortAs: String (optional).</dt>
            <dd>
              The value to lexicographically sorts sort the organization in relation to other organizations when compared
              by name. The value defines the verbatim string value to compare. In absence of this property, the <tt>name</tt> name
              property value <bcp14>MAY</bcp14> be used for comparison.
        </li>
            <li>contexts: <tt>String[Boolean]</tt> (optional).
The
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which association with this the organization apply. applies. For example, membership in a choir may
              only apply in a private context. Also see <xref target="prop-contexts"/>.</li>
          </ul>
          <t>A target="prop-contexts"/>.
            </dd>
          </dl>
          <t>An OrgUnit object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>OrgUnit</tt>, "OrgUnit", if set.
          </li>
            <li>name: <tt>String</tt> (mandatory).
            </dd>
            <dt>name: String (mandatory).</dt>
            <dd>
              The name of this the organizational unit.
        </li>
            <li>sortAs: <tt>String</tt> (optional).
            This defines how this organization unit name
            </dd>
            <dt>sortAs: String (optional).</dt>
            <dd>
              The value to lexicographically sorts sort the organizational unit in relation to other organizational units
              of the same level when compared by name. The level is defined by the array index of this the organizational
              unit in the <tt>units</tt> units property of the Organization object. The property value defines the verbatim string
              value to compare. In absence of this property, the <tt>name</tt> name property value <bcp14>MAY</bcp14> be used for
              comparison.
        </li>
          </ul>
            </dd>
          </dl>
          <figure anchor="example-organizations">
            <name><tt>organizations</tt> example</name>
            <name>Example for the organizations Property</name>
            <sourcecode name="" type="json"><![CDATA[
"organizations": {
  "o1": {
    "name": "ABC, Inc.",
    "units": [
      { "name": "North American Division" },
      { "name": "Marketing" }
    ],
    "sortAs": "ABC"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="speakToAs" numbered="true" toc="default">
          <name>speakToAs</name>
          <t>Type: <tt>SpeakToAs</tt> (optional).</t>
          <t>Provides
          <dl spacing="normal">
            <dt>speakToAs: SpeakToAs (optional).</dt>
            <dd>The information how to address, speak to to, or refer to the entity that is represented by this the
              Card.  A
            </dd>
          </dl>
          <t>A SpeakToAs object has the following properties, of which at least one of the <tt>grammaticalGender</tt> grammaticalGender and <tt>pronouns</tt>
            pronouns properties <bcp14>MUST</bcp14> be set:</t>
          <ul set:
          </t>
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>SpeakToAs</tt>, "SpeakToAs", if set.
          </li>
            <li>
              <t>grammaticalGender: <tt>String</tt>
            </dd>
            <dt>
              grammaticalGender: String (optional).
              Defines which
            </dt>
            <dd>
              <t>
                The grammatical gender to use in salutations and other grammatical constructs. For example,
                the German language distinguishes by grammatical gender in salutations such as "Sehr geehrte" (feminine)
                and "Sehr geehrter" (masculine). The <xref target="enumerated-values">enumerated</xref> values are:</t> are:
              </t>
              <ul spacing="normal"> spacing="compact">
                <li>
                  <tt>animate</tt>
                  animate
                </li>
                <li>
                  <tt>common</tt>
                  common
                </li>
                <li>
                  <tt>feminine</tt>
                  feminine
                </li>
                <li>
                  <tt>inanimate</tt>
                  inanimate
                </li>
                <li>
                  <tt>masculine</tt>
                  masculine
                </li>
                <li>
                  <tt>neuter</tt>
                  neuter
                </li>
              </ul>
              <t>Note that the grammatical gender does not allow inferring the gender identities or assigned sex of the contact.</t>
            </li>
            <li>
              <t>pronouns: <tt>Id[Pronouns]</tt> (optional).
             Defines the
                contact.
              </t>
            </dd>
            <dt>pronouns: Id[Pronouns] (optional).</dt>
            <dd>
              <t>
                The pronouns that the contact chooses to use for themselves.</t>
            </li>
          </ul> themselves.
              </t>
            </dd>
          </dl>
          <t>A Pronouns object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Pronouns</tt>, "Pronouns", if set.
          </li>
            <li>pronouns: <tt>String</tt> (mandatory).
              Defines the
            </dd>
            <dt>pronouns: String (mandatory).</dt>
            <dd>
              The pronouns. Any value or form is allowed. Examples in English include <tt>she/her</tt> "she/her" and <tt>they/them/theirs</tt>.
              "they/them/theirs". The value <bcp14>MAY</bcp14> be overridden in the <tt>localizations</tt> property (<xref target="localizations"/>).</li>
            <li>contexts: <tt>String[Boolean]</tt> (optional).
The <xref target="localizations">
              localizations
            </xref> property.
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which to use these the pronouns. Also see <xref target="prop-contexts"/>.</li>
            <li>pref: <tt>UnsignedInt</tt> (optional). target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>
              The preference of these the pronouns in relation to other pronouns in the same context. Also see <xref target="prop-pref"/>.</li>
          </ul> target="prop-pref"/>.
            </dd>
          </dl>
          <figure anchor="example-speakToAs">
            <name><tt>speakToAs</tt> example</name>
            <name>Example for the speakToAs Property</name>
            <sourcecode name="" type="json"><![CDATA[
"speakToAs": {
  "grammaticalGender": "neuter",
  "pronouns": {
    "k19": {
      "pronouns": "they/them",
      "pref": 2
    },
    "k32": {
      "pronouns": "xe/xir",
      "pref": 1
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="titles" numbered="true" toc="default">
          <name>titles</name>
          <t>Type : <tt>Id[Title]</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>titles: Id[Title] (optional).</dt>
            <dd>The job titles or functional positions of the entity represented by this Card.  A the Card.</dd>
          </dl>
          <t>A Title object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Title</tt>, "Title", if set.
          </li>
            <li>name: <tt>String</tt> (mandatory).
            </dd>
            <dt>name: String (mandatory).</dt>
            <dd>
              The title or role name of the entity represented by this Card.
        </li>
            <li>
              <t>kind: <tt>String</tt> (optional, default <tt>title</tt>).
          Describes the Card.
            </dd>
            <dt>kind: String (optional; default: "title").</dt>
            <dd>
              <t>
                The organizational or situational kind of this the title. Some organizations and individuals
                distinguish between <em>titles</em> as organizational positions and <em>roles</em> as more temporary assignments,
                assignments such as in project management.</t> management.
              </t>
              <t>The <xref target="enumerated-values">enumerated</xref> values are:</t>
              <ul>
                <li>
                  <tt>title</tt>
                </li>
                <li>
                  <tt>role</tt>
                </li> are:
              </t>
              <ul spacing="compact">
                <li>title</li>
                <li>role</li>
              </ul>
            </li>
            <li>organizationId: <tt>Id</tt> (optional).
            </dd>
            <dt>organizationId: Id (optional).</dt>
            <dd>
              The identifier of the organization in which this title is held.
        </li>
          </ul>
            </dd>
          </dl>
          <figure anchor="example-titles">
            <name><tt>titles</tt> example</name>
            <name>Example for the titles Property</name>
            <sourcecode name="" type="json"><![CDATA[
"titles": {
  "le9": {
    "kind": "title",
    "name": "Research Scientist"
  },
  "k2": {
    "kind": "role",
    "name": "Project Leader",
    "organizationId": "o2"
  }
},
"organizations": {
  "o2": {
    "name": "ABC, Inc."
  }
}
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="contact-properties" numbered="true" toc="default">
        <name>Contact Properties</name>
        <t>This section defines properties how to properties contact the entity represented by this the Card.</t>
        <section anchor="emails" numbered="true" toc="default">
          <name>emails</name>
          <t>Type: <tt>Id[EmailAddress]</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>emails: Id[EmailAddress] (optional).</dt>
            <dd>The email addresses in which to contact the entity represented by this Card.  An the Card.</dd>
          </dl>
          <t>An EmailAddress object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>EmailAddress</tt>, "EmailAddress", if set.
          </li>
            <li>address: <tt>String</tt> (mandatory).
            </dd>
            <dt>address: String (mandatory).</dt>
            <dd>
              The email address. This <bcp14>MUST</bcp14> be an <em>addr-spec</em> value as defined in Section 3.4.1 of <xref target="RFC5322" format="default"/>.</li>
            <li>contexts: <tt>String[Boolean]</tt> (optional).
The sectionFormat="of" section="3.4.1"/>.
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which to use this email address. Also see <xref target="prop-contexts"/>.</li>
            <li>pref: <tt>UnsignedInt</tt> (optional). target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>
              The preference of this the email address in relation to other email addresses. Also see <xref target="prop-pref"/>.</li>
            <li>label: <tt>String</tt> (optional). target="prop-pref"/>.
            </dd>
            <dt>label: String (optional).</dt>
            <dd>
              A custom label for the value, value. Also see <xref target="prop-label"/>.</li>
          </ul> target="prop-label"/>.
            </dd>
          </dl>
          <figure anchor="example-emails">
            <name><tt>emails</tt> example</name>
            <name>Example for the emails Property</name>
            <sourcecode name="" type="json"><![CDATA[
"emails": {
  "e1": {
    "contexts": {
      "work": true
    },
    "address": "jqpublic@xyz.example.com"
  },
  "e2": {
    "address": "jane_doe@example.com",
    "pref": 1
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="onlineServices" numbered="true" toc="default">
          <name>onlineServices</name>
          <t>Type: <tt>Id[OnlineService]</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>onlineServices: Id[OnlineService] (optional).</dt>
            <dd>The online services that are associated with the entity represented by this the Card. This can be messaging
              services, social media profiles, and other.  An
            </dd>
          </dl>
          <t>An OnlineService object has the following properties, of which at least the <tt>uri</tt> uri or <tt>user</tt> user property <bcp14>MUST</bcp14> <bcp14>
            MUST
          </bcp14> be set:</t>
          <ul set:
          </t>
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>OnlineService</tt>, "OnlineService", if set.
        </li>
            <li>service: <tt>String</tt> (optional).
            </dd>
            <dt>service: String (optional).</dt>
            <dd>
              The name of the online service or protocol. The name <bcp14>MAY</bcp14> be capitalized the same as on the
              service's website, app app, or publishing material, but names <bcp14>MUST</bcp14> be considered equal is if they
              match case-insensitively. Examples are <tt>GitHub</tt>, <tt>kakao</tt>, <tt>Mastodon</tt>.</li>
            <li>uri: <tt>String</tt> (optional).
This identifies "GitHub", "kakao", and "Mastodon".
            </dd>
            <dt>uri: String (optional).</dt>
            <dd>
              The identifier for the entity represented by this card the Card at the online service. This <bcp14>MUST</bcp14> be a <em>URI</em> <em>
              URI
            </em> as defined in Section 3 of <xref target="RFC3986" format="default"/>.</li>
            <li>user: <tt>String</tt> (optional).
              This names sectionFormat="of" section="3"/>.
            </dd>
            <dt>user: String (optional).</dt>
            <dd>
              The name the entity represented by this the Card at the online service. Any free-text value is allowed. The <tt>service</tt>
              service property <bcp14>SHOULD</bcp14> be set.</li>
            <li>contexts: <tt>String[Boolean]</tt> (optional).
The set.
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which to use this the service. Also see <xref target="prop-contexts"/>.</li>
            <li>pref: <tt>UnsignedInt</tt> (optional). target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>
              The preference of this the service in relation to other services. Also see <xref target="prop-pref"/>.</li>
            <li>label: <tt>String</tt> (optional). target="prop-pref"/>.
            </dd>
            <dt>label: String (optional).</dt>
            <dd>
              A custom label for the value, value. Also see <xref target="prop-label"/>.</li>
          </ul> target="prop-label"/>.
            </dd>
          </dl>
          <figure anchor="example-onlineServices">
            <name><tt>onlineServices</tt> example</name>
            <name>Example for the onlineServices Property</name>
            <sourcecode name="" type="json"><![CDATA[
"onlineServices": {
  "x1": {
    "uri": "xmpp:alice@example.com"
  },
  "x2": {
    "service": "Mastodon",
    "user": "@alice@example2.com",
    "uri": "https://example2.com/@alice"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="phones" numbered="true" toc="default">
          <name>phones</name>
          <t>Type: <tt>Id[Phone]</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>phones: Id[Phone] (optional).</dt>
            <dd>The phone numbers by which to contact the entity represented by this Card.  A Phone the Card.</dd>
          </dl>
          <t>Phone object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Phone</tt>, "Phone", if set.
          </li>
            <li>number: <tt>String</tt> (mandatory).
            </dd>
            <dt>number: String (mandatory).</dt>
            <dd>
              The phone number, number as either a URI or free-text. free text. Typical URI schemes are the "tel"
              <xref target="RFC3966" format="default"/> <tt>tel</tt>
              or "sip" <xref target="RFC3261" format="default"/> <tt>sip</tt> schemes, format="default"/>, but any URI scheme is allowed.</li>
            <li>
              <t>features: <tt>String[Boolean]</tt> (optional). allowed.
            </dd>
            <dt>features: String[Boolean] (optional).</dt>
            <dd>
              <t>
                The set of contact features that this the phone number may be used for. The set is represented as an object,
                with each key being a method type. The boolean value <bcp14>MUST</bcp14> be <tt>true</tt>. "true". The <xref target="enumerated-values">enumerated</xref> target="enumerated-values">enumerated
              </xref> method type values are:
              </t>
              <ul spacing="normal">
                <li><tt>mobile</tt>: the spacing="compact">
                <li>mobile: this number is for a mobile phone.</li>
                <li><tt>voice</tt>: the
                <li>voice: this number is for supports calling by voice.</li>
                <li><tt>text</tt>: the
                <li>text: this number supports text messages (SMS).</li>
                <li><tt>video</tt>: the
                <li>video: this number supports video conferencing.</li>
                <li><tt>main-number</tt>:
                <li>main-number: this number is the a main phone number, number such as the number of the front-desk front desk at a company,
                  as opposed to a direct-dial number of an individual employee.</li>
                <li><tt>textphone</tt>: the employee.
                </li>
                <li>textphone: this number is for a device for people with hearing or speech difficulties.</li>
                <li><tt>fax</tt>: the
                <li>fax: this number is for supports sending faxes.</li>
                <li><tt>pager</tt>: the
                <li>pager: this number is for a pager or beeper.</li>
              </ul>
            </li>
            <li>contexts: <tt>String[Boolean]</tt> (optional).
The
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which to use this the number. Also see <xref target="prop-contexts"/>.</li>
            <li>pref: <tt>UnsignedInt</tt> (optional). target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>
              The preference of this the number in relation to other numbers. Also see <xref target="prop-pref"/>.</li>
            <li>label: <tt>String</tt> (optional). target="prop-pref"/>.
            </dd>
            <dt>label: String (optional).</dt>
            <dd>
              A custom label for the value, value. Also see <xref target="prop-label"/>.</li>
          </ul> target="prop-label"/>.
            </dd>
          </dl>
          <figure anchor="example-phones">
            <name><tt>phones</tt> example</name>
            <name>Example for the phones Property</name>
            <sourcecode name="" type="json"><![CDATA[
"phones": {
  "tel0": {
    "contexts": {
      "private": true
    },
    "features": {
      "voice": true
    },
    "number": "tel:+1-555-555-5555;ext=5555",
    "pref": 1
  },
  "tel3": {
    "contexts": {
      "work": true
    },
    "number": "tel:+1-201-555-0123"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="preferredLanguages" numbered="true" toc="default">
          <name>preferredLanguages</name>
          <t>Type
          <dl spacing="normal">
            <dt>preferredLanguages : <tt>Id[LanguagePref]</tt> (optional).</t>
          <t>Defines the Id[LanguagePref] (optional).</dt>
            <dd>The preferred languages for contacting the entity associated with this Card.</t> the Card.</dd>
          </dl>
          <t>A LanguagePref object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>LanguagePref</tt>, "LanguagePref", if set.
          </li>
            <li>language: <tt>String</tt> (mandatory).  The
            </dd>
            <dt>language: String (mandatory).</dt>
            <dd>The preferred language. This <bcp14>MUST</bcp14> be a language tag as defined in <xref target="RFC5646"/>.</li>
            <li>contexts: <tt>String[Boolean]</tt> (optional).
Defines the target="RFC5646"/>
              .
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which to use this the language. Also see <xref target="prop-contexts"/>.</li>
            <li>pref: <tt>UnsignedInt</tt> (optional).
Defines the target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>The preference of this the language in relation to other languages of the same contexts. Also see <xref target="prop-pref"/>.</li>
          </ul> target="prop-pref"/>.
            </dd>
          </dl>
          <figure anchor="example-preferredLanguages">
            <name><tt>preferredLanguages</tt> example</name>
            <name>Example for the preferredLanguages Property</name>
            <sourcecode name="" type="json"><![CDATA[
"preferredLanguages": {
  "l1": {
    "language": "en",
    "contexts": {
      "work": true
    },
    "pref": 1
  },
  "l2": {
    "language": "fr",
    "contexts": {
      "work": true
    },
    "pref": 2
  },
  "l3": {
    "language": "fr",
    "contexts": {
      "private": true
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="calendaring-and-scheduling-properties" numbered="true" toc="default">
        <name>Calendaring and Scheduling Properties</name>
        <t>This section defines properties how to schedule for scheduling calendar events with the entity represented by this the Card.</t>
        <section anchor="calendars" numbered="true" toc="default">
          <name>calendars</name>
          <t>Type: <tt>Id[Calendar]</tt> (optional).</t>
          <t>These are
          <dl spacing="normal">
            <dt>calendars: Id[Calendar] (optional).</dt>
            <dd>The calendaring resources for calendaring, such as calendars to lookup free-busy information for of the entity represented by this Card.  A the Card, such as to look up free-busy information.</dd>
          </dl>
          <t>A Calendar object has all properties of the <xref target="resource">Resource</xref> data type, with the
            following additional definitions:</t> definitions:
          </t>
          <ul>
            <li>The <tt>@type</tt> @type property value <bcp14>MUST</bcp14> be <tt>Calendar</tt>, "Calendar", if set.</li>
            <li><t>The <tt>kind</tt> set.
            </li>
            <li>
              <t>The kind property is mandatory. Its <xref target="enumerated-values">enumerated</xref> values are:</t>
              <ul> are:
              </t>
              <ul spacing="normal">
                <li>
                  <tt>calendar</tt>: the
                  calendar: The resource is a calendar that contains entries such as calendar events or tasks.</li> tasks.
                </li>
                <li>
                  <tt>freeBusy</tt>: the
                  freeBusy: The resource allows for free-busy lookups, for example example, to schedule group events.</li> events.
                </li>
              </ul>
            </li>
          </ul>
          <figure anchor="example-calendars">
            <name><tt>calendars</tt> example</name>
            <name>Example for the calendars Property</name>
            <sourcecode name="" type="json"><![CDATA[
"calendars": {
  "calA": {
    "kind": "calendar",
    "uri": "webcal://calendar.example.com/calA.ics"
  },
  "project-a": {
    "kind": "freeBusy",
    "uri": "https://calendar.example.com/busy/project-a"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="schedulingAddresses" numbered="true" toc="default">
          <name>schedulingAddresses</name>
          <t>Type: <tt>Id[SchedulingAddress]</tt> (optional).</t>
          <t>The
          <dl spacing="normal">
            <dt>schedulingAddresses: Id[SchedulingAddress] (optional).</dt>
            <dd>The scheduling addresses by which the entity may receive calendar scheduling invitations.  A invitations.</dd>
          </dl>
          <t>A SchedulingAddress object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>
              <t>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>SchedulingAddress</tt>, "SchedulingAddress", if set.</t>
            </li>
            <li>uri: <tt>String</tt> (mandatory). set.
            </dd>
            <dt>uri: String (mandatory).</dt>
            <dd>
              The address to use for calendar scheduling with this the contact. This <bcp14>MUST</bcp14> be a URI as defined
              in Section 3 of <xref target="RFC3986" format="default"/>.</li>
            <li>contexts: <tt>String[Boolean]</tt> (optional).
The sectionFormat="of" section="3"/>.
            </dd>
            <dt>contexts: String[Boolean] (optional).</dt>
            <dd>The contexts in which to use this the scheduling address. Also see <xref target="prop-contexts"/>.</li>
            <li>pref: <tt>UnsignedInt</tt> (optional). target="prop-contexts"/>.
            </dd>
            <dt>pref: UnsignedInt (optional).</dt>
            <dd>
              The preference of this the scheduling address in relation to other scheduling address. addresses. Also see <xref target="prop-pref"/>.</li>
            <li>label: <tt>String</tt> (optional). target="prop-pref"/>.
            </dd>
            <dt>label: String (optional).</dt>
            <dd>
              A custom label for the scheduling address, address. Also see <xref target="prop-label"/>.</li>
          </ul> target="prop-label"/>.
            </dd>
          </dl>
          <figure anchor="example-schedulingAddresses">
            <name><tt>schedulingAddresses</tt> example</name>
            <name>Example for the schedulingAddresses Property</name>
            <sourcecode name="" type="json"><![CDATA[
"schedulingAddresses": {
  "sched1": {
    "uri": "mailto:janedoe@example.com"
  }
}
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="address-and-location-properties" numbered="true" toc="default">
        <name>Address and Location Properties</name>
        <t>This section defines properties for postal addresses and geographical locations associated with the entity
          represented by this Card.</t> the Card.
        </t>
        <section anchor="addresses" anchor="addresses-prop" numbered="true" toc="default">
          <name>addresses</name>
          <t>Type: <tt>Id[Address]</tt> (optional).</t>
          <t>A map
          <dl spacing="normal">
            <dt>addresses: Id[Address] (optional).</dt>
            <dd>The addresses of address identifiers to Address objects, containing physical locations.</t>
          <section> the entity represented by the Card, such as postal addresses or geographic locations.</dd>
          </dl>
          <section anchor="address">
            <name>Address object</name> Object</name>
            <t>An Address object has the following properties:</t>
            <ul properties, of which at least one of components, coordinates,
              countryCode, full or timeZone <bcp14>MUST</bcp14> be set:
            </t>
            <dl spacing="normal">
              <li>@type: <tt>String</tt>.
              This
              <dt>@type: String.</dt>
              <dd>
                The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Address</tt>, "Address", if set.
          </li>
              <li>
                <t>components: <tt>AddressComponent[]</tt>
              </dd>
              <dt>
                components: AddressComponent[] (optional).  The
              </dt>
              <dd>
                <t>The <xref target="addresscomponent">components</xref> making that make up this address.  This property <bcp14>MUST</bcp14> be set if the <tt>full</tt> property is not set, otherwise it <bcp14>SHOULD</bcp14> be set. address. The component list <bcp14>MUST</bcp14> <bcp14>
                  MUST
                </bcp14> have at least one entry having that has a different <tt>kind</tt> kind property value other than <tt>separator</tt>.</t> "separator".
                </t>
                <t>Address components <bcp14>SHOULD</bcp14> be ordered such that when their values are joined as a String produce
                  String, a valid full address. address is produced. If so, implementations <bcp14>MUST</bcp14> set the <tt>isOrdered</tt> isOrdered
                  property value to <tt>true</tt>.</t> "true".
                </t>
                <t>If the address components are ordered, then the <tt>defaultSeparator</tt> defaultSeparator property and address components of with
                  the kind <tt>separator</tt> property value set to "separator" give guidance on what characters to insert between
                  components, but implementations are free to choose any others.  In lack of When lacking a separator, inserting a
                  single Space space character in between address component values is a good choice.</t>
                <t>If instead choice.
                </t>
                <t>If, instead, the address components follow no particular order, then the <tt>isOrdered</tt> isOrdered property value <bcp14>MUST</bcp14> <bcp14>
                  MUST
                </bcp14> be <tt>false</tt>, "false", the <tt>components</tt> components property <bcp14>MUST NOT</bcp14> contain a an AddressComponent of with
                  the kind <tt>separator</tt> property value set to "separator", and the <tt>defaultSeparator</tt> defaultSeparator property <bcp14>MUST NOT</bcp14> be set.</t>
              </li>
              <li>isOrdered: <tt>Boolean</tt> (optional,
                  set.
                </t>
              </dd>
              <dt>isOrdered: Boolean (optional; default: <tt>false</tt>).  This indicates "false").</dt>
              <dd>The indicator if the address component sequence components in the <tt>components</tt> components property is ordered.</li>
              <li>countryCode: <tt>String</tt> (optional). are ordered.</dd>
              <dt>countryCode: String (optional).</dt>
              <dd>
                The Alpha-2 country code <xref target="ISO.3166-1.2006"/>.</li>
              <li>coordinates: <tt>String</tt> (optional).  A target="ISO.3166-1"/>.
              </dd>
              <dt>coordinates: String (optional).</dt>
              <dd>A "geo:" URI
                <xref target="RFC5870" format="default"/> "geo:" URI
                for the address.</li>
              <li>timeZone: <tt>String</tt> (optional).  Identifies the address.
              </dd>
              <dt>timeZone: String (optional).</dt>
              <dd>The time zone this in which the address is located in. located. This <bcp14>MUST</bcp14> be a time zone name
                registered in the IANA <xref target="IANATZ">IANA Time target="IANA-TZ">Time Zone Database</xref>.</li>
              <li>
                <t>contexts: <tt>String[Boolean]</tt> Database</xref>.
              </dd>
              <dt>
                contexts: String[Boolean] (optional).
              </dt>
              <dd>
                <t>
                  The contexts of the address information. in which to use this address. The boolean value <bcp14>MUST</bcp14> be <tt>true</tt>. "true". In addition
                  to the common contexts (<xref target="prop-contexts"/>), allowed key values are:
                </t>
                <ul spacing="normal">
                  <li><tt>billing</tt>: spacing="compact">
                  <li>billing: an address to be used for billing.</li>
                  <li><tt>delivery</tt>:
                  <li>delivery: an address to be used for delivering physical items.</li>
                </ul>
              </li>
              <li>full: <tt>String</tt> (optional).
              This is the
              </dd>
              <dt>full: String (optional).</dt>
              <dd>
                The full address, including street, region region, or country. The purpose of this property is to define an
                address, even if the individual address components are not known.  If the <tt>street</tt> property is set, the <tt>full</tt> property <bcp14>SHOULD NOT</bcp14> be set.
            </li>
              <li>defaultSeparator: <tt>String</tt> (optional).
              </dd>
              <dt>defaultSeparator: String (optional).</dt>
              <dd>
                The default separator to insert between address component values when concatenating all address
                component values to a single String. Also see the definition of the <tt>separator</tt> kind property value "separator" for
                the AddressComponent <xref target="addresscomponent">AddressComponent</xref> object.  This The defaultSeparator property <bcp14>MUST NOT</bcp14> <bcp14>
                MUST NOT
              </bcp14> be set if the Address <tt>isOrdered</tt> isOrdered property value is <tt>false</tt> "false" or if the <tt>components</tt> components property is not set.</li>
              <li>pref: <tt>UnsignedInt</tt> (optional).
                set.
              </dd>
              <dt>pref: UnsignedInt (optional).</dt>
              <dd>
                The preference of this the address in relation to other addresses. Also see <xref target="prop-pref"/>.</li>
              <li>
                <t>phoneticScript: <tt>String</tt> target="prop-pref"/>.
              </dd>
              <dt>
                phoneticScript: String (optional).
              </dt>
              <dd>
                The script used in the value of the AddressComponent <tt>phonetic</tt> phonetic property. Also see <xref target="prop-phonetic"/>.</t>
              </li>
              <li>
                <t>phoneticSystem: <tt>String</tt> target="prop-phonetic"/>.
              </dd>
              <dt>
                phoneticSystem: String (optional).
              </dt>
              <dd>
                The phonetic system used in the AddressComponent <tt>phonetic</tt> phonetic property. Also see <xref target="prop-phonetic"/>.</t>
              </li>
            </ul> target="prop-phonetic"/>.
              </dd>
            </dl>
            <t>The following example illustrates the use of the <tt>address</tt> property. address property for "54321 Oak St, Reston, CA 20190,
              USA". Additional examples are shown in <xref target="address-examples"/>.</t> target="address-examples"/>.
            </t>
            <figure anchor="example-address-us">
              <name>Example
              <!--[rfced] Titles for Figures 30-32

              a) May we remove the postal addresses from the titles of
              Figures 30 and 31 to make them more concise? If so, may we list
              the addresses in the text above the figures as shown below?

              Original:
              Section 2.5.1.1
                 The following example illustrates the use of the address property.
                 Additional examples are in Section 2.5.1.3.

                 Figure 30: Example of the address "54321 Oak St, Reston, VA CA 20190, USA"</name> USA"

              Section 2.5.1.3
                 The following are examples of addresses, in addition to Figure 30.

                 Figure 31: Example of the address "46, 1 Sukhumvit 51 Alley,
                            Khlong Tan Nuea, Watthana, Bangkok 10110, Thailand"

              Perhaps:
              Section 2.5.1.1
                 The following example illustrates the use of the address property for
                 "54321 Oak St, Reston, CA 20190, USA". Additional examples are shown
                 in Section 2.5.1.3.

                 Figure 30: Example of an Address in the USA

              Section 2.5.1.3
                 The following example illustrates the use of the address property for
                 "46, 1 Sukhumvit 51 Alley, Khlong Tan Nuea, Watthana, Bangkok 10110,
                 Thailand". See Figure 30 for an additional example.

                 Figure 31: Example of an Address in Thailand

              b) FYI: We removed the section mention (Section 2.7.1) from the title of
              Figure 32 and placed it within the added text above the figure as shown
              below. Please let us know of any concerns.

              Original:
              Section 2.5.1.3
                 Figure 32: Example of an address in Tokyo and its localization
                            Section 2.7.1 in Japanese.

              Current:
                 The following example illustrates the use of an address in Tokyo and
                 its localization (Section 2.7.1) in Japanese.

                 Figure 32: Example of an Address in Tokyo and Its Localization
                            in Japanese
              -->
              <name>Example of an Address in the USA</name>
              <sourcecode name="" type="json"><![CDATA[
"addresses": {
  "k23": {
    "contexts": {
      "work": true
    },
    "components": [
      { "kind": "number", "value": "54321" },
      { "kind": "separator", "value": " " },
      { "kind": "name", "value": "Oak St" },
      { "kind": "locality", "value": "Reston" },
      { "kind": "region", "value": "VA" },
      { "kind": "separator", "value": " " },
      { "kind": "postcode", "value": "20190" },
      { "kind": "country", "value": "USA" }
    ],
    "countryCode": "US",
    "defaultSeparator": ", ",
    "isOrdered": true
  }
}
]]></sourcecode>
            </figure>
          </section>
          <section anchor="addresscomponent">
            <name>AddressComponent object</name> Object</name>
            <t>An AddressComponent object has the following properties:</t>
            <ul
            <dl spacing="normal">
              <li>@type: <tt>String</tt>.
              This
              <dt>@type: String.</dt>
              <dd>
                The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>AddressComponent</tt>, "AddressComponent", if set.
            </li>
              <li>value: <tt>String</tt> (mandatory).
              </dd>
              <dt>value: String (mandatory).</dt>
              <dd>
                The value of this the address component.</li>
              <li>
                <t>kind: <tt>String</tt> component.
              </dd>
              <dt>
                kind: String (mandatory).
              </dt>
              <dd>
                <t>
                  The kind of this the address component. The <xref target="enumerated-values">enumerated</xref> values are:
                </t>
                <ul spacing="normal">
                  <li><tt>room</tt>: spacing="compact">
                  <li>room: the room or room, suite number number, or identifier.</li>
                  <li><tt>apartment</tt>:
                  <li>apartment: the extension designation, designation such as the apartment number or unit number, unit, or box number.</li>
                  <li><tt>floor</tt>:
                  <li>floor: the floor or level this the address is located on.</li>
                  <li><tt>building</tt>:
                  <li>building: the building, tower, or condominium this the address is located in.</li>
                  <li><tt>number</tt>:
                  <li>number: the street number, e.g., "123". This value is not restricted to numeric values, values and can
                    include any value such as number ranges ("112–10"), ("112-10"), grid style ("39.2 RD"), alphanumerics ("N6W23001")
                    ("N6W23001"), or fractionals ("123 1/2").</li>
                  <li><tt>name</tt>: 1/2").
                  </li>
                  <li>name: the street name.</li>
                  <li><tt>block</tt>:
                  <li>block: the block name or number.</li>
                  <li><tt>subdistrict</tt>:
                  <li>subdistrict: the subdistrict, ward ward, or other subunit of a district.</li>
                  <li><tt>district</tt>:
                  <li>district: the district name.</li>
                  <li><tt>locality</tt>:
                  <li>locality: the municipality, city, town, village, post-town, post town, or another other locality.</li>
                  <li><tt>region</tt>:
                  <li>region: the administrative area, area such as province, state, prefecture, county, or canton.</li>
                  <li><tt>postcode</tt>:
                  <li>postcode: the postal code, post code, ZIP code code, or other short code associated with the address by
                    the relevant country's postal system.</li>
                  <li><tt>country</tt>: system.
                  </li>
                  <li>country: the country name.</li>
                  <li><tt>direction</tt>:
                  <li>direction: the Cardinal cardinal direction or quadrant, e.g.,  "North".</li>
                  <li><tt>landmark</tt>: "north".</li>
                  <li>landmark: the publicly known prominent feature that can substitute the street name and number,
                    e.g., White House, Taj Mahal.</li>
                  <li><tt>postOfficeBox</tt>: "White House" or "Taj Mahal".
                  </li>
                  <li>postOfficeBox: the post office box number or identifier.</li>
                  <li><tt>separator</tt>:
                  <li>separator: a formatting separator between two ordered address non-separator components. The <tt>value</tt> value
                    property of the component includes the verbatim separator, for example example, a hyphen character or even
                    an empty string. This value has higher precedence than the <tt>defaultSeparator</tt> defaultSeparator property of the Address.
                    Implementations <bcp14>MUST NOT</bcp14> insert two consecutive separator components, instead components; instead, they <bcp14>SHOULD</bcp14> <bcp14>
                      SHOULD
                    </bcp14> insert a single separator component with the combined value. This component kind <bcp14>MUST NOT</bcp14> <bcp14>
                      MUST NOT
                    </bcp14> be set if the Address <tt>isOrdered</tt> isOrdered property value is <tt>false</tt>.</li>
                </ul> "false".
                  </li>
              <li>phonetic: <tt>String</tt> (optional).  This defines how to pronounce this
                </ul>
              </dd>
              <dt>phonetic: String (optional).</dt>
              <dd>The pronounciation of the name component. If this property is set, then at least one of the Address
                object <tt>phoneticSystem</tt> phoneticSystem or <tt>phoneticScript</tt> phoneticScript properties <bcp14>MUST</bcp14> be set. Also see <xref target="prop-phonetic"/>.</li>
            </ul> target="prop-phonetic"/>.
              </dd>
            </dl>
          </section>
          <section anchor="address-examples">
            <name>Address examples</name>
            <name>Additional Address Examples</name>
            <t>The following are examples of addresses, in addition to <xref target="example-address-us"/>.</t>
            <figure anchor="example-address-th">
              <name>Example example illustrates the use of the address property for "46, 1 Sukhumvit 51 Alley, Khlong
              Tan Nuea, Watthana, Bangkok 10110, Thailand"</name> Thailand".
            </t>
            <figure anchor="example-address-th">
              <name>Example of an Address in Thailand</name>
              <sourcecode name="" type="json"><![CDATA[
"addresses": {
  "k25": {
    "components": [
      { "kind": "number", "value": "46" },
      { "kind": "name", "value": "1 Sukhumvit 51 Alley" },
      { "kind": "subdistrict", "value": "Khlong Tan Nuea" },
      { "kind": "district", "value": " Watthana" },
      { "kind": "locality", "value": "Bangkok" },
      { "kind": "country", "value": "Thailand" },
      { "kind": "postcode", "value": "10110" }
    ],
    "defaultSeparator": ", ",
    "isOrdered": true
  }
}
]]></sourcecode>
            </figure>
            <t>
              The following example illustrates the use of the address property for "2-7-2 Marunouchi, Chiyoda-ku, Tokyo
              100-8994" and its Japanese localization (<xref target="localizations"/>).
            </t>
            <figure anchor="example-address-jp">
              <name>Example of an address Address in Tokyo and its localization <xref target="localizations"/> Its Localization in Japanese.</name> Japanese</name>
              <sourcecode name="" type="json"><![CDATA[
"addresses": {
   "k26": {
     "components": [
       { "kind": "block", "value": "2-7" },
       { "kind": "separator", "value": "-" },
       { "kind": "number", "value": "2" },
       { "kind": "separator", "value": " " },
       { "kind": "district", "value": "Marunouchi" },
       { "kind": "locality", "value": "Chiyoda-ku" },
       { "kind": "region", "value": "Tokyo" },
       { "kind": "separator", "value": " " },
       { "kind": "postcode", "value": "100-8994" }
     ],
     "defaultSeparator": ", ",
     "full": "2-7-2 Marunouchi, Chiyoda-ku, Tokyo 100-8994",
     "isOrdered": true
   }
},
"localizations": {
  "jp": {
    "addresses/k26": {
      "components": [
        { "kind": "region", "value": "東京都" },
        { "kind": "locality", "value": "千代田区" },
        { "kind": "district", "value": "丸ノ内" },
        { "kind": "block", "value": "2-7" },
        { "kind": "separator", "value": "-" },
        { "kind": "number", "value": "2" },
        { "kind": "postcode", "value": "〒100-8994" }
      ],
      "defaultSeparator": "",
      "full": "〒100-8994東京都千代田区丸ノ内2-7-2",
      "isOrdered": true
    }
  }
}
]]></sourcecode>
            </figure>
          </section>
        </section>
      </section>
      <section anchor="resource-properties" numbered="true" toc="default">
        <name>Resource Properties</name>
        <t>This section defines properties for digital resources associated with the entity represented by this the Card.</t>
        <section anchor="cryptoKeys" numbered="true" toc="default">
          <name>cryptoKeys</name>
          <t>Type: <tt>Id[CryptoKey]</tt> (optional).</t>
          <t>These are
          <dl spacing="normal">
            <dt>cryptoKeys: Id[CryptoKey] (optional).</dt>
            <dd>The cryptographic resources such as public keys and certificates associated with the entity
              represented by this the Card.  A
            </dd>
          </dl>
          <t>A CryptoKey object has all properties of the <xref target="resource">Resource</xref> data type, with the
            following additional definitions:</t> definition:
          </t>
          <ul>
            <li>The <tt>@type</tt> @type property value <bcp14>MUST</bcp14> be <tt>CryptoKey</tt>, "CryptoKey", if set.</li> set.
            </li>
          </ul>
          <t>The following example shows how to refer to an external cryptographic resource.</t>
          <figure anchor="example-cryptoKeys-external">
            <name><tt>cryptoKeys</tt> example
            <name>Example of cryptoKeys with external data</name> External Data</name>
            <sourcecode name="" type="json"><![CDATA[
"cryptoKeys": {
  "mykey1": {
    "uri": "https://www.example.com/keys/jdoe.cer"
  }
}
]]></sourcecode>
          </figure>
          <t>The following example shows how to embed key data in the CryptoKey. The key data is depicted in multiple
            lines only for demonstration purposes.</t> purposes.
          </t>
          <figure anchor="example-cryptoKeys-embedded">
            <name><tt>cryptoKeys</tt> example
            <name>Example of cryptoKeys with embedded data</name>
            <sourcecode name="" type="json"><![CDATA[ Embedded Data</name>
            <!--[rfced] The sourcecode in Figure 34 (Section 2.6.1) was 8
            characters over the 72-character limit, so we adjusted the line
            breaks as shown below.  Please let us know if any further updates
            are needed.

            Original:
            "cryptoKeys": {
              "mykey2": {
                "uri": "data:application/pgp-keys;base64,LS0tLS1CRUdJTiBSU0EgUFVCTElDIEtF
                        WS0tLS0tCk1JSUJDZ0tDQVFFQSt4R1ovd2N6OXVnRnBQMDdOc3BvNlUxN2wwWWhGa
                        UZweHhVNHBUazNMaWZ6OVIzenNJc3UKRVJ3dGE3K2ZXSWZ4T28yMDhldHQvamhza2
                        lWb2RTRXQzUUJHaDRYQmlweVdvcEt3WjkzSEhhRFZaQUFMaS8yQQoreFRCdFdkRW8
                        3WEdVdWpLRHZDMi9hWkt1a2ZqcE9pVUk4QWhMQWZqbWxjRC9VWjFRUGgwbUhzZ2xS
                        TkNtcEN3Cm13U1hBOVZObWh6K1BpQitEbWw0V1duS1cvVkhvMnVqVFh4cTcrZWZNV
                        TRIMmZueTNTZTNLWU9zRlBGR1oxVE4KUVNZbEZ1U2hXckhQdGlMbVVkUG9QNkNWMm
                        1NTDF0aytsN0RJSXFYclFoTFVLREFDZU01cm9NeDBrTGhVV0I4UAorMHVqMUNObE5
                        ONEpSWmxDN3hGZnFpTWJGUlU5WjRONll3SURBUUFCCi0tLS0tRU5EIFJTQSBQVUJM
                        SUMgS0VZLS0tLS0K"
              }
            }

            Current:
            "cryptoKeys": {
              "mykey2": {
                "uri": "data:application/pgp-keys;base64,LS0tLS1CRUdJTiBSU0EgUFVC
                        TElDIEtFWS0tLS0tCk1JSUJDZ0tDQVFFQSt4R1ovd2N6OXVnRnBQMDdOc
                        3BvNlUxN2wwWWhGaUZweHhVNHBUazNMaWZ6OVIzenNJc3UKRVJ3dGE3K2
                        ZXSWZ4T28yMDhldHQvamhza2lWb2RTRXQzUUJHaDRYQmlweVdvcEt3Wjk
                        zSEhhRFZaQUFMaS8yQQoreFRCdFdkRW83WEdVdWpLRHZDMi9hWkt1a2Zq
                        cE9pVUk4QWhMQWZqbWxjRC9VWjFRUGgwbUhzZ2xSTkNtcEN3Cm13U1hBO
                        VZObWh6K1BpQitEbWw0V1duS1cvVkhvMnVqVFh4cTcrZWZNVTRIMmZueT
                        NTZTNLWU9zRlBGR1oxVE4KUVNZbEZ1U2hXckhQdGlMbVVkUG9QNkNWMm1
                        NTDF0aytsN0RJSXFYclFoTFVLREFDZU01cm9NeDBrTGhVV0I4UAorMHVq
                        MUNObE5ONEpSWmxDN3hGZnFpTWJGUlU5WjRONll3SURBUUFCCi0tLS0tR
                        U5EIFJTQSBQVUJMSUMgS0VZLS0tLS0K"
              }
            }
            -->
            <sourcecode name="" type="json"><![CDATA[
"cryptoKeys": {
  "mykey2": {
    "uri": "data:application/pgp-keys;base64,LS0tLS1CRUdJTiBSU0EgUFVC
            TElDIEtFWS0tLS0tCk1JSUJDZ0tDQVFFQSt4R1ovd2N6OXVnRnBQMDdOc
            3BvNlUxN2wwWWhGaUZweHhVNHBUazNMaWZ6OVIzenNJc3UKRVJ3dGE3K2
            ZXSWZ4T28yMDhldHQvamhza2lWb2RTRXQzUUJHaDRYQmlweVdvcEt3Wjk
            zSEhhRFZaQUFMaS8yQQoreFRCdFdkRW83WEdVdWpLRHZDMi9hWkt1a2Zq
            cE9pVUk4QWhMQWZqbWxjRC9VWjFRUGgwbUhzZ2xSTkNtcEN3Cm13U1hBO
            VZObWh6K1BpQitEbWw0V1duS1cvVkhvMnVqVFh4cTcrZWZNVTRIMmZueT
            NTZTNLWU9zRlBGR1oxVE4KUVNZbEZ1U2hXckhQdGlMbVVkUG9QNkNWMm1
            NTDF0aytsN0RJSXFYclFoTFVLREFDZU01cm9NeDBrTGhVV0I4UAorMHVq
            MUNObE5ONEpSWmxDN3hGZnFpTWJGUlU5WjRONll3SURBUUFCCi0tLS0tR
            U5EIFJTQSBQVUJMSUMgS0VZLS0tLS0K"
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="directories" numbered="true" toc="default">
          <name>directories</name>
          <t>Type: <tt>Id[Directory]</tt> (optional).</t>
          <t>These are directory service resources, such as entries in a directory or organizational
          <dl spacing="normal">
            <dt>directories: Id[Directory] (optional).</dt>
            <dd>The directories for lookup.  A containing information about the entitity represented by the Card.</dd>
          </dl>
          <t>A Directory object has all properties of the <xref target="resource">Resource</xref> data type, with the
            following additional definitions:</t> definitions:
          </t>
          <ul>
            <li>The <tt>@type</tt> @type property value <bcp14>MUST</bcp14> be <tt>Directory</tt>, "Directory", if set.</li> set.
            </li>
            <li>
              <t>The <tt>kind</tt> kind property is mandatory. Its <xref target="enumerated-values">enumerated</xref> values are:</t> are:
              </t>
              <ul>
                <li><tt>directory</tt>:
                <li>directory: the resource is a directory service where that the entity represented by this the Card is a part of.
                  This typically is an organizational directory that also contains associated entities, e.g., co-workers
                  and management in a company directory.</li>
                <li><tt>entry</tt>: directory.
                </li>
                <li>entry: the resource is a directory entry of the entity represented by this the Card. In contrast to the <tt>directory</tt>
                  "directory" type, this is the specific URI for the entity <em>within</em> a directory.</li> directory.
                </li>
              </ul>
            </li>
          </ul>
          <t>In addition, the Directory object has the following property:</t>
          <ul>
            <li>listAs: <tt>UnsignedInt</tt> (optional).
          This defines the
          <dl>
            <dt>listAs: UnsignedInt (optional).</dt>
            <dd>
              The position of this the directory resource in the list of all Directory objects having the same <tt>kind</tt> kind
              property value in this the Card. If set, the <tt>listAs</tt> listAs value <bcp14>MUST</bcp14> be higher than zero. Multiple
              directory resources <bcp14>MAY</bcp14> have the same <tt>listAs</tt> listAs property value, value or none. Sorting such
              same-valued entries is implementation-specific.
        </li>
          </ul>
            </dd>
          </dl>
          <figure anchor="example-directories">
            <name><tt>directories</tt> example</name>
            <name>Example for the directories Property</name>
            <sourcecode name="" type="json"><![CDATA[
"directories": {
  "dir1": {
    "kind": "entry",
    "uri": "https://dir.example.com/addrbook/jdoe/Jean%20Dupont.vcf"
  },
  "dir2": {
    "kind": "directory",
    "uri": "ldap://ldap.example/o=Example%20Tech,ou=Engineering",
    "pref": 1
  }
]]></sourcecode>
          </figure>
        </section>
        <section anchor="links" numbered="true" toc="default">
          <name>links</name>
          <t>Type: <tt>Id[Link]</tt> (optional).</t>
          <t>These are
          <dl spacing="normal">
            <dt>links: Id[Link] (optional).</dt>
            <dd>The links to resources that do not fit any of the other use-case specific use-case-specific resource properties.  A
            </dd>
          </dl>
          <t>A Link object has all properties of the <xref target="resource">Resource</xref> data type, with the
            following additional definitions:</t> definitions:
          </t>
          <ul>
            <li>The <tt>@type</tt> @type property value <bcp14>MUST</bcp14> be <tt>Link</tt>, "Link", if set.</li>
            <li><t>The <tt>kind</tt> set.
            </li>
            <li>
              <t>The kind property is optional. Its <xref target="enumerated-values">enumerated</xref> values are:</t> are:
              </t>
              <ul>
                <li><tt>contact</tt>:
                <li>contact: the resource is a URI by which the entity represented by this the Card may be contacted, including contacted; this
                  includes web forms or other media that require user interaction.</li> interaction.
                </li>
              </ul>
            </li>
          </ul>
          <figure anchor="example-links">
            <name><tt>links</tt> example</name>
            <name>Example for the links Property</name>
            <sourcecode name="" type="json"><![CDATA[
"links": {
  "link3": {
    "kind": "contact",
    "uri": "mailto:contact@example.com",
    "pref": 1
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="media" numbered="true" toc="default">
          <name>media</name>
          <t>Type: <tt>Id[Media]</tt> (optional).</t>
          <t>These are
          <dl spacing="normal">
            <dt>media: Id[Media] (optional).</dt>
            <dd>The media resources such as photographs, avatars, or sounds that are associated with the entity
              represented by this the Card.  A
            </dd>
          </dl>
          <t>A Media object has all properties of the <xref target="resource">Resource</xref> data type, with the
            following additional definitions:</t> definitions:
          </t>
          <ul>
            <li>The <tt>@type</tt> @type property value <bcp14>MUST</bcp14> be <tt>Media</tt>, "Media", if set.</li> set.
            </li>
            <li>
              <t>The <tt>kind</tt> kind property is mandatory. Its <xref target="enumerated-values">enumerated</xref> values are:</t>
              <ul>
                <li><tt>photo</tt>: are:
              </t>
              <ul spacing="normal">
                <li>photo: the resource is a photograph or avatar.</li>
                <li><tt>sound</tt>:
                <li>sound: the resource is audio media, e.g., to specify the proper pronunciation of the name property contents.</li>
                <li><tt>logo</tt>:
                  contents.
                </li>
                <li>logo: the resource is a graphic image or logo associated with the entity represented by this Card.</li> the Card.
                </li>
              </ul>
            </li>
          </ul>
          <figure anchor="example-media">
            <name><tt>media</tt> example</name>
            <name>Example for the media Property</name>
            <sourcecode name="" type="json"><![CDATA[
"media": {
  "res45": {
    "kind": "sound",
    "uri": "CID:JOHNQ.part8.19960229T080000.xyzMail@example.com"
  },
  "res47": {
    "kind": "logo",
    "uri": "https://www.example.com/pub/logos/abccorp.jpg"
  },
  "res1": {
    "kind": "photo",
    "uri": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAASABIAAD/4..."
  }
}
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="multilingual-properties" numbered="true" toc="default">
        <name>Multilingual Properties</name>
        <t>This section defines properties how to localize for localizing the content of this the Card in human languages.</t>
        <section anchor="localizations" numbered="true" toc="default">
          <name>localizations</name>
          <t>Type:
          <dl spacing="normal">
            <dt>localizations: String[PatchObject] (optional).</t>
          <t>This localizes (optional).</dt>
            <dd>
              <t>The property values in this Card localized to languages other than the main language. <xref target="language">main language</xref> of
                the Card. Localizations provide language-specific alternatives for existing property values and <bcp14>SHOULD NOT</bcp14> <bcp14>
                  SHOULD NOT
                </bcp14> add new properties.</t>
          <t>The properties. The keys in the localizations property object value are language tags <xref target="RFC5646"/>. The target="RFC5646"/>; the values are patch objects which of type PatchObject and localize the Card in the respective that language
                tag. The paths in the PatchObject are relative to the Card that includes the <tt>localizations</tt> localizations property. A
                patch <bcp14>MUST NOT</bcp14> target the <tt>localizations</tt> property.</t> localizations property.
              </t>
            </dd>
          </dl>
          <t>Conceptually, a Card is localized as follows:</t>
          <ul>
            <li>Determine the language tag in which this the Card should be localized in.</li> localized.</li>
            <li>If the localizations property includes a key for that language, obtain the PatchObject value. If there
              is no such key, stop.</li> stop.
            </li>
            <li>Create a copy of the Card, but do not copy the localizations property.</li>
            <li>Apply all patches in the PatchObject to the copy of the Card.</li>
            <li>Optionally, set the <tt>language</tt> language property in the copy of the Card.</li>
            <li>Use the patched copy of the Card as the localized variant of the original Card.</li>
          </ul>
          <t>A patch in the PatchObject may contain any value type. Its value <bcp14>MUST</bcp14> be a valid value
            according to the definition of the patched property.</t> property.
          </t>
          <t><xref target="example-localizations-replace"/>
            localizes the <tt>name</tt> name property by completely replacing its contents in Ukrainian language with Cyrillic script.</t> script.
          </t>
          <figure anchor="example-localizations-replace">
            <name>Example for localizing of Localizing a top-level property</name>
            <artwork><![CDATA[ Top-Level Property</name>
            <sourcecode type=""><![CDATA[
{
  "name": {
    "components": [
      { "kind": "title", "value": "Mr." },
      { "kind": "given", "value": "Ivan" },
      { "kind": "given2", "value": "Petrovich" },
      { "kind": "surname", "value": "Vasiliev" }
    ]
  },
  "localizations": {
    "uk-Cyrl": {
      "name": {
        "components": [
          { "kind": "title", "value": "г-н" },
          { "kind": "given", "value": "Иван" },
          { "kind": "given2", "value": "Петрович" },
          { "kind": "surname", "value": "Васильев" }
        ]
      }
    }
  }
}
]]></artwork>
]]></sourcecode>
          </figure>
          <t><xref target="example-localizations-patch"/>
            localizes the title name by patching <em>inside</em> the <tt>titles</tt> titles property. All properties but properties, except the <tt>name</tt> name
            property in the Title object object, are left as-is.</t> as is.
          </t>
          <figure anchor="example-localizations-patch">
            <name>Example for localizing of Localizing a nested property</name>
            <artwork><![CDATA[ Nested Property</name>
            <!--[rfced] In Figure 39, is the term "autor" correct, or should it be
            "author"?

            Original:
                "titles/t1/name": "autor"
            -->
            <sourcecode type=""><![CDATA[
"name": {
  "full": "Gabriel García Márquez"
},
"titles": {
  "t1": {
    "kind": "title",
    "name": "novelist"
  }
},
"localizations": {
  "es": {
    "titles/t1/name": "autor" "escritor"
  }
}
]]></artwork>
]]></sourcecode>
          </figure>
        </section>
      </section>
      <section anchor="additional-properties" numbered="true" toc="default">
        <name>Additional Properties</name>
        <t>This section defines properties for which none of the previous sections are appropriate.</t>
        <section anchor="anniversaries" numbered="true" toc="default">
          <name>anniversaries</name>
          <t>Type :
          <dl spacing="normal">
            <dt>anniversaries: Id[Anniversary] (optional).</t>
          <t>These are (optional).</dt>
            <dd>The memorable dates and events for the entity represented by this Card.  An the Card.</dd>
          </dl>
          <t>An Anniversary object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Anniversary</tt>, "Anniversary", if set.
          </li>
            <li>
              <t>kind: <tt>String</tt>
            </dd>
            <dt>
              kind: String (mandatory).
              Specifies the
            </dt>
            <dd>
              <t>
                The kind of the anniversary. The <xref target="enumerated-values">enumerated</xref> values are:
              </t>
              <ul spacing="normal">
                <li><tt>birth</tt>: spacing="compact">
                <li>birth: a birthday anniversary</li>
                <li><tt>death</tt>:
                <li>death: a deathday anniversary</li>
                <li><tt>wedding</tt>:
                <li>wedding: a wedding day anniversary</li>
              </ul>
            </li>
            <li>
              <t>date: <tt>PartialDate|Timestamp</tt> (mandatory,
            </dd>
            <dt>
              date: PartialDate|Timestamp (mandatory; defaultType: <tt>PartialDate</tt>).</t> PartialDate).
            </dt>
            <dd>
              <t>The date of this the anniversary in the Gregorian calendar. This <bcp14>MUST</bcp14> either be either a whole or
                partial calendar date or a complete UTC timestamp (see the definition of the Timestamp and PartialDate
                object types below).</t>
            </li>
            <li>place: below).
              </t>
            </dd>
            <dt>place: Address (optional).
            An (optional).</dt>
            <dd>An address associated with this anniversary, e.g., the place of birth or death.</li>
          </ul> death.</dd>
          </dl>
          <t>A PartialDate object represents a complete or partial calendar date in the Gregorian calendar. It
            represents either a complete date, or a year, or a month in a year, or a day in a month. It has the following properties, of which at least <tt>year</tt> or <tt>month</tt> and <tt>day</tt> <bcp14>MUST</bcp14> be set:</t>
          <ul properties:
          </t>
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>PartialDate</tt>, "PartialDate", if set.
          </li>
            <li>year: <tt>UnsignedInt</tt>
            </dd>
            <dt>year:</dt>
            <dd>UnsignedInt (optional).  This is the The calendar year.</li>
            <li>month: <tt>UnsignedInt</tt> (optional).  This is the year.</dd>
            <dt>month: UnsignedInt (optional).</dt>
            <dd>The calendar month, represented as the integers 1 &lt;= month &lt;= 12. If this property is set set, then
              either <tt>year</tt> the year or <tt>day</tt> the day property <bcp14>MUST</bcp14> be set.</li>
            <li>day: <tt>UnsignedInt</tt> (optional).  This is the set.
            </dd>
            <dt>day: UnsignedInt (optional).</dt>
            <dd>The calendar month day, represented as the integers 1 &lt;= day &lt;= 31, depending on the validity
              within the month and year. If this property is set set, then <tt>month</tt> the month property <bcp14>MUST</bcp14> be set.</li>
            <li>calendarScale: <tt>String</tt> (optional).  This is the set.
            </dd>
            <dt>calendarScale: String (optional).</dt>
            <dd>The calendar system in which this date occurs, in lowercase. This <bcp14>MUST</bcp14> be either a CLDR-registered
              calendar system name registered as a Common Locale Data Repository (CLDR)
              <xref target="RFC7529" format="default"/>
              or a vendor-specific value. The year, month month, and day still <bcp14>MUST</bcp14> be represented in the
              Gregorian calendar. Note that the <tt>year</tt> year property might be required to convert the date between the
              Gregorian calendar and the respective calendar system.</li>
          </ul> system.
            </dd>
          </dl>
          <t>A Timestamp object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Timestamp</tt>, "Timestamp", if set.
          </li>
            <li>utc: <tt>UTCDateTime</tt> (mandatory).  Specifies the
            </dd>
            <dt>utc: UTCDateTime (mandatory).</dt>
            <dd>The point in time in UTC time.
      </li>
          </ul>
            </dd>
          </dl>
          <t><xref target="example-anniversaries"/>
            illustrates anniversaries with partial dates and a timestamp. Note how the <tt>@type</tt> @type property is set for the <tt>Timestamp</tt>
            Timestamp object value according to the rules defined in <xref target="prop-type"/>.</t> target="prop-type"/>.
          </t>
          <figure anchor="example-anniversaries">
            <name><tt>anniversaries</tt> example</name>
            <name>Example for the anniversaries Property</name>
            <sourcecode name="" type="json"><![CDATA[
"anniversaries": {
  "k8": {
    "kind": "birth",
    "date": {
      "year": 1953,
      "month": 4,
      "day": 15
    }
  },
  "k9": {
    "kind": "death",
    "date": {
      "@type": "Timestamp",
      "utc": "2019-10-15T23:10:00Z"
    },
    "place": {
      "full": "4445 Tree Street\nNew England, ND 58647\nUSA"
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="keywords" numbered="true" toc="default">
          <name>keywords</name>
          <t>Type: <tt>String[Boolean]</tt> (optional).
A
          <dl spacing="normal">
            <dt>keywords: String[Boolean] (optional).</dt>
            <dd>
              <t>The set of free-text keywords, also known as <em>tags</em>.  The Each key in the set is represented as an object, with each key being a keyword.  The keyword, each boolean value <bcp14>MUST</bcp14> be <tt>true</tt>.</t> "true".
              </t>
            </dd>
          </dl>
          <figure anchor="example-keywords">
            <name><tt>keywords</tt> example</name>
            <name>Example for the keywords Property</name>
            <sourcecode name="" type="json"><![CDATA[
"keywords": {
  "internet": true,
  "IETF": true
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="notes" numbered="true" toc="default">
          <name>notes</name>
          <t>Type: <tt>Id[Note]</tt> (optional).</t>
          <t>Free-text
          <dl spacing="normal">
            <dt>notes: Id[Note] (optional).</dt>
            <dd>The free-text notes that are associated with this Card.  A the Card.</dd>
          </dl>
          <t>A Note object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Note</tt>, "Note", if set.
        </li>
            <li>
              <t>note: <tt>String</tt>
            </dd>
            <dt>
              note: String (mandatory).  The free text
            </dt>
            <dd>The free-text value of this note.</t>
            </li>
            <li>
              <t>created: <tt>UTCDateTime</tt> note.
            </dd>
            <dt>
              created: UTCDateTime (optional).  The
            </dt>
            <dd>The date and time when this note was created.</t>
            </li>
            <li>
              <t>author: <tt>Author</tt> created.
            </dd>
            <dt>
              author: Author (optional).  The
            </dt>
            <dd>The author of this note.</t>
            </li>
          </ul> note.
            </dd>
          </dl>
          <t>An Author object has the following properties, of which at least one property other than <tt>@type</tt> <bcp14>MUST</bcp14> @type <bcp14>
            MUST
          </bcp14> be set:</t>
          <ul set:
          </t>
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>Author</tt>, "Author", if set.
        </li>
            <li>
              <t>name: <tt>String</tt>
            </dd>
            <dt>
              name: String (optional).  The
            </dt>
            <dd>The name of this author.</t>
            </li>
            <li>
              <t>uri: <tt>String</tt> author.
            </dd>
            <dt>
              uri: String (optional).  A
            </dt>
            <dd>
              <t>The URI value that identifies the author.</t>
            </li>
          </ul>
            </dd>
          </dl>
          <figure anchor="example-notes">
            <name><tt>notes</tt> example</name>
            <name>Example for the notes Property</name>
            <sourcecode name="" type="json"><![CDATA[
"notes": {
  "n1": {
    "note": "Open office hours are 1600 to 1715 EST, Mon-Fri",
    "created": "2022-11-23T15:01:32Z",
    "author": {
      "name": "John"
    }
  }
}
]]></sourcecode>
          </figure>
        </section>
        <section anchor="personalInfo" numbered="true" toc="default">
          <name>personalInfo</name>
          <t>Type: <tt>Id[PersonalInfo]</tt> (optional).</t>
          <t>Defines
          <dl spacing="normal">
            <dt>personalInfo: Id[PersonalInfo] (optional).</dt>
            <dd>The personal information about of the entity represented by this Card.
A the Card.</dd>
          </dl>
          <t>A PersonalInfo object has the following properties:</t>
          <ul
          <dl spacing="normal">
            <li>@type: <tt>String</tt>.
              This
            <dt>@type: String.</dt>
            <dd>
              The JSContact type of the object. The value <bcp14>MUST</bcp14> be <tt>PersonalInfo</tt>, "PersonalInfo", if set.
          </li>
            <li>
              <t>kind: <tt>String</tt>
            </dd>
            <dt>
              kind: String (mandatory).
              Specifies the
            </dt>
            <dd>
              <t>
                The kind of this personal information. The <xref target="enumerated-values">enumerated</xref> values
                are:
              </t>
              <ul spacing="normal">
                <li><tt>expertise</tt>:
                <li>expertise: a field of expertise or a credential</li>
                <li><tt>hobby</tt>:
                <li>hobby: a hobby</li>
                <li><tt>interest</tt>:
                <li>interest: an interest</li>
              </ul>
            </li>
            <li>value: <tt>String</tt> (mandatory).
            </dd>
            <dt>value: String (mandatory).</dt>
            <dd>
              The actual information.</li>
            <li>
              <t>level: <tt>String</tt> information.
            </dd>
            <dt>
              level: String (optional).
              Indicates the
            </dt>
            <dd>
              <t>
                The level of expertise, expertise or engagement in hobby or interest. The <xref target="enumerated-values">enumerated</xref> values are:</t>
              <ul spacing="normal">
                <li>
                  <tt>high</tt>
                  high
                </li>
                <li>
                  <tt>medium</tt>
                  medium
                </li>
                <li>
                  <tt>low</tt>
                  low
                </li>
              </ul>
            </li>
            <li>listAs: <tt>UnsignedInt</tt> (optional).
            This defines the
            </dd>
            <dt>listAs: UnsignedInt (optional).</dt>
            <dd>
              The position of this the personal information in the list of all PersonalInfo objects having that have the
              same <tt>kind</tt> kind property value in this the Card. If set, the <tt>listAs</tt> listAs value <bcp14>MUST</bcp14> be higher than zero.
              Multiple personal information entries <bcp14>MAY</bcp14> have the same <tt>listAs</tt> listAs property value, value or none.
              Sorting such same-valued entries is implementation-specific.
        </li>
            <li>label: <tt>String</tt> (optional).
            </dd>
            <dt>label: String (optional).</dt>
            <dd>
              A custom label. See <xref target="prop-label"/>.</li>
          </ul> target="prop-label"/>.
            </dd>
          </dl>
          <figure anchor="example-personalInfo">
            <name><tt>personalInfo</tt> example</name>
            <name>Example for the personalInfo Property</name>
            <sourcecode name="" type="json"><![CDATA[
"personalInfo": {
  "pi2": {
    "kind": "expertise",
    "value": "chemistry",
    "level": "high"
  },
  "pi1": {
    "kind": "hobby",
    "value": "reading",
    "level": "high"
  },
  "pi6": {
    "kind": "interest",
    "value": "r&b music",
    "level": "medium"
  }
}
]]></sourcecode>
          </figure>
        </section>
      </section>
    </section>
    <section anchor="iana-considerations" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <section anchor="iana-media-type" numbered="true" toc="default">
        <name>Media Type Registration</name>
        <t><xref target="I-D.ietf-calext-jscontact"/>
        <!-- [rfced] We have included some specific questions about the IANA
text below. In addition to responding to those questions, please
review all of the IANA-related updates carefully and let us know
if any further updates are needed.

a) FYI: In Section 3.5.1, we placed the "Reference or Description" entry
below the "Change Controller" entry to match the order of the template
at https://www.iana.org/assignments/jscontact/.

b) In Sections 3.5.1, 3.6.1, and 3.7.1, may we update the definition of
"Change Controller" as shown below to make the text parallel with the
other entries?

Original:
   Change Controller:  This is who may request a change to this entry's
      definition (IETF for RFCs from the IETF stream).

Perhaps:
   Change Controller:  Person or entity responsible for requesting a
   change to the entry's definition (IETF for RFCs from the IETF stream).

c) In Sections 3.5.1, 3.6.1, 3.7.1, and 3.7.2:

- Is "Table 1" the correct reference in the sentences below (note that
there are 4 instances of each sentence)? Table 1 displays values from
the "JSContact Version" registry, not the "JSContact Enum Value" registry.
Please let us know if an update is needed to the registry name and/or the
table number.

Original:
   The version MUST be one of the allowed values of the version property
   in the JSContact Enum Value registry (see Table 1).

   The Until Version value either MUST be not set, or one of the allowed
   values of the version property in the JSContact Enum Value registry
   (see Table 1).

d) In Section 3.5.2 (Table 2):

- Note that the content of Table 2 in the PDF output is cut off rather
than wrapping. We have opened an issue for this. Please see
<https://github.com/ietf-tools/xml2rfc/issues/1110>.

- As Table is 2 characters past the 72-character limit, may we reformat
the table to fit by removing the Ref column and linking each section
number to the corresponding Property Context? For an example of the output,
see <https://www.rfc-editor.org/authors/rfc9553-table.pdf#table-2>.

- FYI: We have moved the entry for the "version" property name to appear
above "year" so that it appears in alphabetical order. Please let us know if
you prefer the previous order.

- FYI: Under "contexts", "label", "pref", and "uri", we ordered
Section "1.4.4" first in the Reference column since this section
corresponds to these terms. Please let us know if you prefer otherwise.

- Under the "@type" property name in the "References" column, should
references to Sections "2.5.1.2" and "2.2.1.2" be added for
"AddressComponent" and "NameComponent", respectively, or does Sections
"2.5.1" and "2.2.1" serve as the references for these terms?

If Sections "2.5.1.2" and "2.2.1.2" are used, should Sections "2.5.1"
and "2.2.1" also be updated under the "AddressComponent" and
"NameComponent" entries, respectively, in Tables 2 and 4 for
consistency?

- Under "full" and "isOrdered", should "Section 2.5.1" be
"Section 2.5.1.1" instead for direct access to these terms?

- Under "phoneticScript" and "phoneticSystem", should
"Section 2.2.1" be "Section 2.2.1.1" instead for direct
access to these terms?

e) In Section 3.7.1, should the definition of "Reference" be added
after "Change Controller" to match the template at
https://www.iana.org/assignments/jscontact? Also, since "Initial
Contents" is not included in the template, should it be removed and
made into a separate paragraph?

f) In Section 3.7.2, should the definition of "Change Controller" be
added after "Until Version" to match the template at
https://www.iana.org/assignments/jscontact?

g) In Section 3.7.3:

- FYI: We have moved the "phoneticSystem" entry and table above the
"relation" entry and table so that it appears in alphabetical order.
Please let us know if you prefer otherwise.

- Should the following updates be made so that readers are taken directly
to the enum values?
    - In Table 6, should Section "2.5.1" be updated to "2.5.1.1"?
    - In Table 10, should Section "2.5.1" be updated to "2.5.1.2"?
    - In Table 17, should Section "2.2.1" be updated to "2.2.1.2"?
-->
        <t>This document defines a media type for use with JSContact data formatted in JSON.</t>
        <dl newline="true" newline="false" spacing="normal">
          <dt>Type name:</dt>
          <dd>application</dd>
          <dt>Subtype name:</dt>
          <dd>jscontact+json</dd>
          <dt>Required parameters:</dt>
          <dd>
            <t>None</t>
          </dd>
          <dt>Optional parameters:</dt>
          <dd>
            <dl newline="false" spacing="normal">
              <dt>version</dt>
              <dd>This
            <t>version</t>
            <t>This parameter conveys the version of the JSContact data in the body part. It <bcp14>MUST NOT</bcp14> occur
              more than once. If this parameter is set, then the values of all JSContact <xref target="iana-property-registry-version"><tt>version</tt></xref> target="iana-property-registry-version">version
              </xref> properties in the body part <bcp14>MUST</bcp14> match the parameter value.</dd>
            </dl> value.
            </t>
          </dd>
          <dt>Encoding considerations:</dt>
          <dd>This is the same as the encoding considerations of application/json, as specified in <xref target="RFC8259" sectionFormat="of" section="11"/>.</dd> section="11"/>.
          </dd>
          <dt>Security considerations:</dt>
          <dd> See
          <dd>See
            <xref target="security-considerations" format="default"/>
            of <xref target="I-D.ietf-calext-jscontact"/>.</dd> RFC 9553.
          </dd>
          <dt>Interoperability considerations:</dt>
          <dd>While JSContact is designed to avoid ambiguities as much as possible, when converting objects from other
            contact formats to/from JSContact, it is possible that differing representations for the same logical data
            or ambiguities in interpretation might arise. The semantic equivalence of two JSContact objects may be
            determined differently by different applications, for example, where URL values differ in case between the
            two objects.</dd> objects.
          </dd>
          <dt>Published specification:</dt>
          <dd>TBD</dd>
          <dd>RFC 9553</dd>
          <dt>Applications that use this media type:</dt>
          <dd>Applications that currently make use of the text/vcard text/vCard media type can use this as an alternative.</dd>
          <dt>Fragment identifier considerations:</dt>
          <dd>A JSON Pointer fragment identifier may be used, as defined in <xref target="RFC6901" sectionFormat="comma" section="6"/>.</dd> section="6"/>.
          </dd>
          <dt>Additional information:</dt>
          <dd>
            <t>
              <br/>
            </t>
            <dl newline="false" spacing="normal"> spacing="compact">
              <dt>Magic number(s):</dt>
              <dd>N/A</dd>
              <dt>File extensions(s):</dt>
              <dd>N/A</dd>
              <dt>Macintosh file type code(s):</dt>
              <dd>N/A</dd>
            </dl>
          </dd>
          <dt>Person &amp; email address to contact for further information:</dt>
          <dd>calsify@ietf.org</dd>
          <dt>Intended usage:</dt>
          <dd>COMMON</dd>
          <dt>Restrictions on usage:</dt>
          <dd>N/A</dd>
          <dt>Author:</dt>
          <dd>See the "Author's Address" "Authors' Addresses" section of <xref target="I-D.ietf-calext-jscontact"/>.</dd> RFC 9553.</dd>
          <dt>Change controller:</dt>
          <dd>IETF</dd>
        </dl>
      </section>
      <section anchor="iana-jscontact-registry" numbered="true" toc="default">
        <name>Creation of the "JSContact" JSContact Registry Group</name>
        <t>IANA is asked to create has created the "JSContact" registry group. The new registry definitions in the following sections all
          belong to that group.</t> group.
        </t>
      </section>
      <section anchor="iana-registry-policy" numbered="true" toc="default">
        <name>Registry Policy and Change Procedures</name>
        <!--[rfced] Since "backwards-incompatibility" is mentioned in Section
        1.9.1, should the reference below be updated from Section 1.9 to
        Section 1.9.1?

        Original:
           Registry assignments that introduce backwards-incompatible
           (Section 1.9) changes require the JSContact major version
           to change, other changes only require to change the minor
           version.

        Perhaps:
           Registry assignments that introduce backwards-incompatible
           (Section 1.9.1) changes require the JSContact major version
           to change; other changes only require a change to the minor
           version.
        -->
        <t>Registry assignments that introduce <xref target="versioning">backwards-incompatible</xref> changes require
          the JSContact major version to change, change; other changes only require to a change to the minor version. The registry
          policy for assignments that require the JSContact major version to change is Standards Action (<xref target="RFC8126" sectionFormat="comma" section="4.9"/>). The registry policy for other assignments is
          Specification Required (<xref target="RFC8126" sectionFormat="comma" section="4.6"/>).</t> section="4.6"/>).
        </t>
        <t>The Designated Expert designated expert (DE) decides if a major or minor version change is required and assigns the new version
          to the <xref target="iana-version-registry">Version Registry</xref>. target="iana-version-registry">"JSContact Version" registry</xref>. Version numbers increment by
          one, and a major version change resets the minor version to zero. An assignment may apply multiple changes and
          to more than one registry at once, in which case a single version change is sufficient. If the registry policy
          is Specification Required, then the Designated Expert DE may decide that it is enough to document the new assignment in the
          Description item of the respective registry.</t> registry.
        </t>
        <t>A registration <bcp14>MUST</bcp14> have an intended usage of <tt>common</tt>, <tt>reserved</tt>, "common", "reserved", or <tt>obsolete</tt>.</t> "obsolete".
        </t>
        <ul>
          <li>A <tt>common</tt> "common" usage denotes an item with shared semantics and syntax across systems. Up-to-date systems <bcp14>MUST</bcp14> <bcp14>
            MUST
          </bcp14> expect such items to occur in JSContact data.</li> data.
          </li>
          <li>A <tt>reserved</tt> "reserved" usage reserves an item in the registry without assigning semantics to avoid name collisions
            with future extensions or protocol use.</li> use. Implementations <bcp14>MUST NOT</bcp14> expect or add items with
            such names outside the protocols or extensions that use them; otherwise, any such JSContact data is invalid.
          </li>
          <li>An <tt>obsolete</tt> "obsolete" usage denotes an item that is no longer expected to be added by up-to-date systems. A new
            assignment has probably been defined defined, covering the obsolete item's semantics.</li> semantics. Implementations <bcp14>MUST
            </bcp14> expect such items to occur in JSContact data up to the "Until Version" registry field, inclusively.
            They <bcp14>MUST NOT</bcp14> add such items for any version after which the item got obsolete; otherwise,
            any such JSContact data is invalid.
          </li>
        </ul>
        <t>The intended usage of registry items may change between versions, but the DE must carefully
          consider the impact on existing implementations and standards before doing so.
        </t>
        <t>The registration procedure is not a formal standards process but rather an administrative procedure intended
          to allow community comment comments and to check whether it is coherent without excessive time delay. It is designed
          to encourage vendors to document and register new items they add for use cases not covered by the original
          specification, leading to increased interoperability.</t> interoperability.
        </t>
        <section anchor="iana-registry-preliminary-community-review" numbered="true" toc="default">
          <name>Preliminary Community Review</name>
          <t>Notice of a potential new registration <bcp14>MUST</bcp14> be sent to the Calext WG mailing list &lt;calsify@ietf.org&gt;
            for review. This mailing list is appropriate to solicit for soliciting community feedback on a proposed registry assignment.</t>
            assignment.
          </t>
          <t>The intent of the public posting to this list is to solicit comments and feedback on the choice of the item
            name or value, the unambiguity of its description, and a review of any interoperability or security
            considerations. The submitter may submit a revised registration proposal or abandon the registration
            completely at any time.</t> time.
          </t>
        </section>
        <section anchor="iana-registry-submit-request-to-iana" numbered="true" toc="default">
          <name>Submit Request to IANA</name>
          <t>Registration requests can be sent to IANA &lt;iana@iana.org&gt;.</t>
        </section>
        <section anchor="iana-registry-designated-expert-review" numbered="true" toc="default">
          <name>Designated Expert Review</name>
          <t>The primary concern of the designated expert (DE) DE is preventing name collisions and encouraging the submitter to document
            security and privacy considerations.</t> considerations.
          </t>
          <t>A new type name, property name name, or enumerated value <bcp14>MUST NOT</bcp14> differ only in case from an already registered
            already-registered name or value.</t> value.
          </t>
          <t>For a common-use registration, the DE is expected to confirm that suitable documentation is available to
            ensure interoperability. The DE should also verify that the new assignment does not conflict with work that
            is active or already published within the IETF.</t> IETF.
          </t>
          <t>The DE will either approve or deny the registration request and publish a notice of the decision to the
            Calext WG mailing list or its successor, as well as inform IANA. A denial notice must be justified by an
            explanation, and, and in the cases where it is possible, concrete suggestions on how the request can be modified
            to become acceptable should be provided.</t> provided.
          </t>
        </section>
        <section anchor="iana-registry-change-procedures" numbered="true" toc="default">
          <name>Change Procedures</name>
          <t>Once a JSContact registry group item has been published by IANA, the change controller Change Controller may request a change
            to its definition. The same procedure that would be appropriate for the original registration request is
            used to process a change request.</t> request.
          </t>
          <t>JSContact registrations dot do not get deleted; instead, items that are no longer believed appropriate for use
            are declared obsolete by a change to their "intended usage" "Intended Usage" field; such items will be clearly marked in the
            IANA registry.</t> registry.
          </t>
          <t>Significant changes to a JSContact registry item's definition should be requested only when there are
            serious omissions or errors in the published specification, as such changes may cause interoperability
            issues. When review is required, a change request may be denied if it renders entities that were valid under
            the previous definition invalid under the new definition.</t> definition.
          </t>
        </section>
      </section>
      <section anchor="iana-version-registry" numbered="true" toc="default">
        <name>Creation of the "JSContact Version" JSContact Version Registry</name>
        <t>IANA is asked to create has created the "JSContact Version" registry. The purpose of this new registry is to define the allowed
          value range of JSContact major and minor version numbers.</t> numbers.
        </t>
        <t>The registry entries sort numerically in ascending order by the "Major Version" column, entries with equal "Major Version" sort numerically in ascending order by the "Minor Version" column.</t>
        <t>The registry process is outlined in <xref target="iana-registry-policy" format="default"/>.</t> format="default"/>.
        </t>
        <section anchor="iana-version-registry-template" numbered="true" toc="default">
          <name>"JSContact Version"
          <name>JSContact Version Registry Template</name>
          <dl newline="false">
            <dt>Major Version:</dt>
            <dd>This is the
            <dd>The numeric value of a JSContact major version number. It <bcp14>MUST</bcp14> be a positive integer.</dd> integer.
            </dd>
            <dt>Highest Minor Version:</dt>
            <dd> This is the
            <dd>The maximum numeric value of a JSContact minor version for the given major version. It <bcp14>MUST</bcp14> <bcp14>MUST
            </bcp14> be zero or a positive integer. All numbers less than or equal to this value are valid minor version
              values for the given major version.</dd> version.
            </dd>
          </dl>
        </section>
        <section anchor="iana-version-registry-contents" numbered="true" toc="default">
          <name>Initial Contents for of the "JSContact Version" JSContact Version Registry</name>
          <t>The following table lists the initial valid major and minor version number ranges.</t>
          <table anchor="tab-iana-version-registry" align="center">
            <name>JSContact Versions</name> Version Registry</name>
            <thead>
              <tr>
                <th align="left">Major Version</th>
                <th align="left">Highest Minor Version</th>
                <th align="left">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">1</td>
                <td align="left">0</td>
                <td align="left">RFC 9553</td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
      <section anchor="iana-property-registry" numbered="true" toc="default">
        <name>Creation of the "JSContact Properties" JSContact Properties Registry</name>
        <t>IANA is asked to create has created the "JSContact Properties" registry. The purpose of this new registry is to allow
          interoperability of extensions to JSContact objects</t> objects.
        </t>
        <t>The registry entries sort alphabetically in ascending order by the following columns: "Property Name" column first,
          "Property Context" second, and "Since Version" third. Equal entries sort in any order.</t> order.
        </t>
        <t>The registry process for a new property is outlined in <xref target="iana-registry-policy" format="default"/>.</t> format="default"/>.
        </t>
        <section anchor="iana-property-registry-template" numbered="true" toc="default">
          <name>"JSContact Properties"
          <name>JSContact Properties Registry Template</name>
          <dl newline="false">
            <dt>Property Name:</dt>
            <dd>This is the
            <dd>The name of the property. The property name <bcp14>MUST NOT</bcp14> already be registered for any of the
              object types listed in the "Property Context" field of this registration. Other object types <bcp14>MAY</bcp14> already <bcp14>MAY
              </bcp14> have already registered a different property with the same name; however, the same name <bcp14>MUST</bcp14> <bcp14>
                MUST
              </bcp14> only be used when the semantics are analogous.</dd> analogous.
            </dd>
            <dt>Property Type:</dt>
            <dd> This
            <dd>For properties with intended usage other than "reserved", this is the type of this property, using type signatures,
              signatures as specified in <xref target="type-signatures" format="default"/>. The property type <bcp14>MUST</bcp14> <bcp14>
                MUST
              </bcp14> be registered in the "JSContact Types" registry.</dd> registry. For reserved property names, the value MUST be
              the verbatim string "not applicable".
            </dd>
            <dt>Property Context:</dt>
            <dd>This is a
            <dd>A comma-separated list of JSContact object types (<xref target="iana-type-registry-contents"/>) that
              contain this property.</dd>
            <dt>Reference or Description:</dt>
            <dd>This is a brief description or RFC number and section reference where the property. For reserved property is specified (omitted for "reserved" property names). This must include references to all RFC documents where this property is introduced or updated.</dd> names, the value MAY be the verbatim string "not applicable".
            </dd>
            <dt>Intended Usage:</dt>
            <dd>This may
            <dd>May be "common", "reserved", or "obsolete".</dd>
            <dt>Since Version:</dt>
            <dd>This defines the
            <dd>The JSContact version on which this the property definition is based on. based. The version <bcp14>MUST</bcp14> be one
              of the allowed values of the <tt>version</tt> version property in the JSContact Enum Value "JSContact Version" registry (see <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
            <dt>Until Version:</dt>
            <dd>This defines the
            <dd>The JSContact version after which this the property got obsoleted and was obsoleted; therefore, it <bcp14>MUST NOT</bcp14> be
              used in later versions. The Until Version value either <bcp14>MUST NOT</bcp14> be set, set or <bcp14>MUST
              </bcp14> be one of the allowed values of the <tt>version</tt> version property in the JSContact Enum Value "JSContact Version" registry (see
              <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
            <dt>Change Controller:</dt>
            <dd>This is who may request
            <dd>Person or entity responsible for requesting a change to this the entry's definition (<tt>IETF</tt> ("IETF" for RFCs from the
              IETF stream).</dd> stream).
            </dd>
            <dt>Reference or Description:</dt>
            <dd>A brief description or RFC number and section reference where the property is specified. This must
              include references to all RFC documents where this property is introduced or updated. For reserved
              property names, the reference or description <bcp14>MAY</bcp14> be omitted.
            </dd>
          </dl>
        </section>
        <section anchor="iana-property-registry-contents" numbered="true" toc="default">
          <name>Initial Contents for of the "JSContact Properties" JSContact Properties Registry</name>
          <t>The following table lists the initial <tt>common</tt> "common" usage entries of the "JSContact Properties" registry.  The For
            all properties, the Since Version for all properties is <tt>1.0</tt>.  The "1.0", the Until Version for all properties is not set.  All set, the Change Controller is "IETF",
            and RFC section references are for <xref target="I-D.ietf-calext-jscontact"/>.  The change controller for all these properties is <tt>IETF</tt>.</t> RFC 9553.
          </t>
          <table anchor="tab-iana-property-registry" align="center">
            <name>JSContact Properties with "common" usage</name> Usage</name>
            <thead>
              <tr>
                <th align="left">Property Name</th>
                <th align="left">Property Type</th>
                <th align="left">Property Context</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <!-- Everything in here should be sorted alphabetically: table entries by property name, the references for each property alphabetically by the object type or property they refer to -->
            <tbody>
              <tr>
                <td align="left">@type</td>
                <td align="left">String</td>
                <td align="left">Address, AddressComponent, Anniversary, Author, Card, Calendar,  CryptoKey, Directory, EmailAddress, LanguagePref, Link, Media, Name, NameComponent, Nickname, Note, OnlineService, Organization, OrgUnit, PartialDate,PersonalInfo, Phone, Pronouns, Relation, SchedulingAddress, SpeakToAs, Timestamp, Title</td>
                <td align="left"><xref target="addresses" format="default"/>, <xref target="anniversaries" format="default"/>, <xref target="cardtype" format="default"/>, <xref target="calendars" format="default"/>, <xref target="cryptoKeys" format="default"/>, <xref target="directories" format="default"/>, <xref target="emails" format="default"/>, <xref target="preferredLanguages" format="default"/>, <xref target="links" format="default"/>, <xref target="media" format="default"/>, <xref target="name" format="default"/>, <xref target="nicknames" format="default"/>, <xref align="left">Address (<xref target="address"/>), AddressComponent (<xref target="addresscomponent"/>), Anniversary (<xref target="anniversaries"/>), Author (<xref target="notes" format="default"/>, <xref target="onlineServices" format="default"/>, <xref target="organizations" format="default"/>, <xref target="personalInfo" format="default"/>, <xref target="phones" format="default"/>, <xref target="speakToAs" format="default"/>, <xref target="relatedTo" format="default"/>, <xref target="schedulingAddresses" format="default"/>, <xref target="titles" format="default"/></td>
              </tr>
              <tr anchor="iana-property-registry-version">
                <td align="left">version</td>
                <td align="left">String</td>
                <td align="left">Card</td>
                <td align="left"> format="default"/>), Card (<xref target="cardtype"/>), Calendar (<xref target="calendars"/>), CryptoKey (<xref target="cryptoKeys"/>), Directory (<xref target="directories"/>), EmailAddress (<xref target="emails"/>), LanguagePref (<xref target="preferredLanguages"/>), Link <xref target="prop-version" format="default"/> target="links"/>), Media (<xref target="media"/>), Name (<xref target="name"/>), NameComponent (<xref target="namecomponent"/>), Nickname (<xref target="nicknames"/>), Note (<xref target="notes"/>), OnlineService (<xref target="onlineServices"/>), Organization (<xref target="organizations"/>), OrgUnit (<xref target="organizations"/>), PartialDate (<xref target="anniversaries"/>), PersonalInfo (<xref target="personalInfo"/>), Phone (<xref target="phones"/>), Pronouns (<xref target="speakToAs"/>), Relation (<xref target="relatedTo"/>), SchedulingAddress (<xref target="schedulingAddresses"/>), SpeakToAs (<xref target="speakToAs"/>), Timestamp (<xref target="anniversaries" format="default"/>), Title (<xref target="titles"/>)
                </td>
              </tr>
              <tr>
                <td align="left">address</td>
                <td align="left">String</td>
                <td align="left">EmailAddress</td>
                <td align="left">
                  <xref align="left">EmailAddress (<xref target="emails" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">addresses</td>
                <td align="left">Id[Address]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref target="addresses" format="default"/>
                </td> align="left">Card (<xref target="address" format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">anniversaries</td>
                <td align="left">Id[Anniversary]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="anniversaries" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">author</td>
                <td align="left">Author</td>
                <td align="left">Note</td>
                <td align="left">
                  <xref align="left">Note (<xref target="notes" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">calendars</td>
                <td align="left">Id[Calendar]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="calendars" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">calendarScale</td>
                <td align="left">String</td>
                <td align="left">PartialDate</td>
                <td align="left">
                  <xref align="left">PartialDate (<xref target="anniversaries" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">components</td>
                <td align="left">AddressComponent[]</td>
                <td align="left">Address</td>
                <td align="left">
                  <xref target="addresses" format="default"/>
                </td> align="left">Address (<xref target="address" format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">components</td>
                <td align="left">NameComponent[]</td>
                <td align="left">Name</td>
                <td align="left">
                  <xref target="name" format="default"/>
                </td> align="left">Name (<xref target="namecomponent" format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">contexts</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Address, Calendar,  CryptoKey, Directory, EmailAddress, LanguagePref, Link, Media, Nickname, OnlineService, Organization, Phone, Pronouns, SchedulingAddress</td>
                <td align="left"><xref target="prop-contexts" format="default"/>, <xref target="addresses" format="default"/>, <xref target="calendars" format="default"/>, <xref target="cryptoKeys" format="default"/>, <xref target="directories" format="default"/>, <xref target="emails" format="default"/>, <xref target="preferredLanguages" format="default"/>, <xref target="links" format="default"/>, <xref target="media" format="default"/>, <xref target="nicknames" format="default"/>, <xref target="onlineServices" format="default"/>, <xref target="organizations" format="default"/>, <xref target="phones" format="default"/>, <xref target="speakToAs" format="default"/>, align="left">Address (<xref target="address"/>), Calendar (<xref target="calendars"/>), CryptoKey (<xref target="cryptoKeys"/>), Directory (<xref target="directories"/>), EmailAddress (<xref target="emails"/>), LanguagePref (<xref target="preferredLanguages"/>), Link (<xref target="links"/>), Media (<xref target="media"/>), Nickname (<xref target="nicknames"/>), OnlineService (<xref target="onlineServices"/>), Organization (<xref target="organizations"/>), Phone (<xref target="phones"/>), Pronouns (<xref target="speakToAs"/>), SchedulingAddress (<xref target="schedulingAddresses"/>). Also see Sections <xref target="schedulingAddresses" format="default"/><xref target="resource" format="default"/></td> format="counter"/> and <xref target="prop-contexts" format="counter"/>.
                </td>
              </tr>
              <tr>
                <td align="left">coordinates</td>
                <td align="left">String</td>
                <td align="left">Address</td>
                <td align="left">
                  <xref target="addresses" format="default"/>
                </td> align="left">Address (<xref target="address" format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">countryCode</td>
                <td align="left">String</td>
                <td align="left">Address</td>
                <td align="left">
                  <xref target="addresses" format="default"/>
                </td> align="left">Address (<xref target="address" format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">created</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Card, Note</td>
                <td align="left"><xref target="created" format="default"/>, <xref target="notes" format="default"/></td> align="left">Card (<xref target="created"/>), Note (<xref target="notes"/>)</td>
              </tr>
              <tr>
                <td align="left">date</td>
                <td align="left">PartialDate|Timestamp</td>
                <td align="left">Anniversary</td>
                <td align="left">
                  <xref align="left">Anniversary (<xref target="anniversaries" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">day</td>
                <td align="left">UnsignedInt</td>
                <td align="left">PartialDate</td>
                <td align="left">
                  <xref align="left">PartialDate (<xref target="anniversaries" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">defaultSeparator</td>
                <td align="left">String</td>
                <td align="left">Address, Name</td>
                <td align="left"><xref target="addresses" format="default"/>,
                  <xref target="name" format="default"/></td> align="left">Address (<xref target="address"/>), Name (<xref target="name"/>)</td>
              </tr>
              <tr>
                <td align="left">directories</td>
                <td align="left">Id[Directory]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="directories" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">emails</td>
                <td align="left">Id[EmailAddress]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="emails" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">features</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Phone</td>
                <td align="left">
                  <xref align="left">Phone (<xref target="phones" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">full</td>
                <td align="left">String</td>
                <td align="left">Address, Name</td>
                <td align="left"><xref target="addresses" format="default"/>,
                  <xref target="name" format="default"/></td> align="left">Address (<xref target="address"/>), Name (<xref target="name"/>)</td>
              </tr>
              <tr>
                <td align="left">grammaticalGender</td>
                <td align="left">String</td>
                <td align="left">SpeakToAs</td>
                <td align="left">
                  <xref align="left">SpeakToAs (<xref target="speakToAs" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">isOrdered</td>
                <td align="left">Boolean</td>
                <td align="left">Address, Name</td>
                <td align="left"><xref target="addresses" format="default"/>,
                  <xref target="name" format="default"/></td> align="left">Address (<xref target="address"/>), Name (<xref target="name"/>)</td>
              </tr>
              <tr>
                <td align="left">keywords</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="keywords" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">kind</td>
                <td align="left">String</td>
                <td align="left">AddressComponent, Anniversary, Calendar, Card, CryptoKey, Directory, Link, Media, NameComponent, PersonalInfo, Title</td>
                <td align="left"><xref target="addresses" format="default"/>, <xref target="anniversaries" format="default"/>, <xref target="calendars" format="default"/>, <xref target="kind" format="default"/>, <xref target="cryptoKeys" format="default"/>, <xref target="directories" format="default"/>, <xref target="links" format="default"/>, <xref target="media" format="default"/>, <xref target="name" format="default"/>, <xref target="personalInfo" format="default"/>, <xref target="titles" format="default"/></td> align="left">AddressComponent (<xref target="addresscomponent"/>), Anniversary (<xref target="anniversaries"/>), Calendar (<xref target="calendars"/>), Card (<xref target="kind"/>), CryptoKey (<xref target="cryptoKeys"/>), Directory (<xref target="directories"/>), Link (<xref target="links"/>), Media (<xref target="media"/>), NameComponent (<xref target="namecomponent"/>), PersonalInfo (<xref target="personalInfo"/>), Title (<xref target="titles"/>)
                </td>
              </tr>
              <tr>
                <td align="left">label</td>
                <td align="left">String</td>
                <td align="left">Calendar, CryptoKey, Directory, EmailAddress, Link, Media, OnlineService, PersonalInfo, Phone, SchedulingAddress</td>
                <td align="left"><xref target="prop-label" format="default"/>, <xref target="calendars" format="default"/>, <xref target="cryptoKeys" format="default"/>, <xref target="directories" format="default"/>, <xref target="emails" format="default"/>, <xref target="links" format="default"/>, <xref target="media" format="default"/>, <xref target="onlineServices" format="default"/>, <xref target="personalInfo" format="default"/>, <xref target="phones" format="default"/>, <xref target="schedulingAddresses" format="default"/>, align="left">Calendar (<xref target="calendars"/>), CryptoKey (<xref target="cryptoKeys"/>), Directory (<xref target="directories"/>), EmailAddress (<xref target="emails"/>), Link (<xref target="links"/>), Media (<xref target="media"/>), OnlineService (<xref target="onlineServices"/>), PersonalInfo (<xref target="personalInfo"/>), Phone (<xref target="phones"/>), SchedulingAddress (<xref target="schedulingAddresses"/>). Also see Sections <xref target="resource" format="default"/></td> format="counter"/> and <xref target="prop-label" format="counter"/>.
                </td>
              </tr>
              <tr>
                <td align="left">language</td>
                <td align="left">String</td>
                <td align="left">Card, LanguagePref</td>
                <td align="left"><xref target="language" format="default"/>,
                  <xref target="preferredLanguages" format="default"/></td> align="left">Card (<xref target="language"/>), LanguagePref (<xref target="preferredLanguages"/>)</td>
              </tr>
              <tr>
                <td align="left">level</td>
                <td align="left">String</td>
                <td align="left">PersonalInfo</td>
                <td align="left">
                  <xref target="personalInfo" format="default"/>
                </td> align="left">PersonalInfo (<xref target="personalInfo"/>)</td>
              </tr>
              <tr>
                <td align="left">links</td>
                <td align="left">Id[Link]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="links" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">listAs</td>
                <td align="left">UnsignedInt</td>
                <td align="left">Directory, PersonalInfo</td>
                <td align="left"><xref target="directories" format="default"/>, <xref target="personalInfo" format="default"/></td> align="left">Directory (<xref target="directories"/>), PersonalInfo (<xref target="personalInfo"/>)</td>
              </tr>
              <tr>
                <td align="left">localizations</td>
                <td align="left">String[PatchObject]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="localizations" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">media</td>
                <td align="left">Id[Media]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="media" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">mediaType</td>
                <td align="left">String</td>
                <td align="left">Calendar, CryptoKey, Directory, Link, Media</td>
                <td align="left"><xref target="resource" format="default"/>, <xref target="calendars" format="default"/>, <xref target="cryptoKeys" format="default"/>, <xref target="directories" format="default"/>, <xref target="links" format="default"/>, align="left">Calendar (<xref target="calendars"/>), CryptoKey (<xref target="cryptoKeys"/>), Directory (<xref target="directories"/>), Link (<xref target="links"/>), Media (<xref target="media"/>). Also see <xref target="media" format="default"/></td> target="resource"/>.</td>
              </tr>
              <tr>
                <td align="left">members</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card  (<xref target="members" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">month</td>
                <td align="left">UnsignedInt</td>
                <td align="left">PartialDate</td>
                <td align="left">
                  <xref align="left">PartialDate (<xref target="anniversaries" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">name</td>
                <td align="left">Name</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="name" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">name</td>
                <td align="left">String</td>
                <td align="left">Author, Nickname, Organization, OrgUnit, Title</td>
                <td align="left"><xref target="notes" format="default"/>, <xref target="nicknames" format="default"/>, <xref target="organizations" format="default"/>, <xref target="titles" format="default"/></td> align="left">Author  (<xref target="notes"/>), Nickname (<xref target="nicknames"/>), Organization (<xref target="organizations"/>), OrgUnit (<xref target="organizations"/>), Title (<xref target="titles"/>)</td>
              </tr>
              <tr>
                <td align="left">nicknames</td>
                <td align="left">Id[Nickname]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card  (<xref target="nicknames" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">note</td>
                <td align="left">String</td>
                <td align="left">Note</td>
                <td align="left">
                  <xref align="left">Note (<xref target="notes" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">notes</td>
                <td align="left">Id[Note]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="notes" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">number</td>
                <td align="left">String</td>
                <td align="left">Phone</td>
                <td align="left">
                  <xref align="left">Phone (<xref target="phones" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">onlineServices</td>
                <td align="left">Id[OnlineService]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="onlineServices" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">organizationId</td>
                <td align="left">String</td>
                <td align="left">Title</td>
                <td align="left">
                  <xref align="left">Title (<xref target="titles" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">organizations</td>
                <td align="left">Id[Organization]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="organizations" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">personalInfo</td>
                <td align="left">Id[PersonalInfo]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="personalInfo" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">phones</td>
                <td align="left">Id[Phone]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="phones" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">phonetic</td>
                <td align="left">String</td>
                <td align="left">AddressComponent, NameComponent</td>
                <td align="left"><xref target="addresscomponent" format="default"/>,
                  <xref target="namecomponent" format="default"/></td> align="left">AddressComponent (<xref target="addresscomponent"/>), NameComponent (<xref target="namecomponent"/>)</td>
              </tr>
              <tr>
                <td align="left">phoneticScript</td>
                <td align="left">String</td>
                <td align="left">Address, Name</td>
                <td align="left"><xref target="name" format="default"/>,
                  <xref target="addresses" format="default"/></td> align="left">Address (<xref target="address"/>), Name (<xref target="name"/>)</td>
              </tr>
              <tr>
                <td align="left">phoneticSystem</td>
                <td align="left">String</td>
                <td align="left">Address, Name</td>
                <td align="left"><xref target="name" format="default"/>,
                  <xref target="addresses" format="default"/></td> align="left">Address (<xref target="address" format="counter"/>), Name (<xref target="name"/>)</td>
              </tr>
              <tr>
                <td align="left">place</td>
                <td align="left">Address</td>
                <td align="left">Anniversary</td>
                <td align="left">
                  <xref align="left">Anniversary (<xref target="anniversaries" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">pref</td>
                <td align="left">UnsignedInt</td>
                <td align="left">Address, Calendar,  CryptoKey, Directory, EmailAddress, LanguagePref, Link, Media, Nickname, OnlineService, Phone, Pronouns, SchedulingAddress</td>
                <td align="left"><xref target="prop-pref" format="default"/>, <xref target="addresses" format="default"/>, <xref target="calendars" format="default"/>, <xref target="cryptoKeys" format="default"/>, <xref target="directories" format="default"/>, <xref target="emails" format="default"/>, <xref target="preferredLanguages" format="default"/>, <xref target="links" format="default"/>, <xref target="media" format="default"/>, <xref target="nicknames" format="default"/>, <xref target="onlineServices" format="default"/>, <xref target="phones" format="default"/>, <xref target="speakToAs" format="default"/>, <xref target="schedulingAddresses" format="default"/>, align="left">Address (<xref target="address"/>), Calendar (<xref target="calendars"/>), CryptoKey (<xref target="cryptoKeys"/>), Directory (<xref target="directories"/>), EmailAddress (<xref target="emails"/>), LanguagePref (<xref target="preferredLanguages"/>), Link (<xref target="links"/>), Media (<xref target="media"/>), Nickname (<xref target="nicknames"/>), OnlineService (<xref target="onlineServices"/>), Phone (<xref target="phones"/>), Pronouns (<xref target="speakToAs"/>), SchedulingAddress (<xref target="schedulingAddresses"/>). Also see Sections <xref target="resource" format="default"/></td> format="counter"/> and <xref target="prop-pref" format="counter"/>.
                </td>
              </tr>
              <tr>
                <td align="left">preferredLanguages</td>
                <td align="left">String[LanguagePref]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="preferredLanguages" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">prodId</td>
                <td align="left">String</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="prodId" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">pronouns</td>
                <td align="left">Id[Pronouns]</td>
                <td align="left">SpeakToAs</td>
                <td align="left">
                  <xref align="left">SpeakToAs (<xref target="speakToAs" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">relatedTo</td>
                <td align="left">String[Relation]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="relatedTo" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">relation</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Relation</td>
                <td align="left">
                  <xref align="left">Relation (<xref target="relatedTo" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">schedulingAddresses</td>
                <td align="left">Id[SchedulingAddress]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="schedulingAddresses" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">service</td>
                <td align="left">String</td>
                <td align="left">OnlineService</td>
                <td align="left">
                  <xref align="left">OnlineService (<xref target="onlineServices" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">sortAs</td>
                <td align="left">String[String]</td>
                <td align="left">Name</td>
                <td align="left">
                  <xref align="left">Name (<xref target="name" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">sortAs</td>
                <td align="left">String</td>
                <td align="left">Organization, OrgUnit</td>
                <td align="left">
                  <xref align="left">Organization (<xref target="organizations" format="default"/>
                </td> format="default"/>), OrgUnit (<xref target="organizations"/>)</td>
              </tr>
              <tr>
                <td align="left">speakToAs</td>
                <td align="left">SpeakToAs</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="speakToAs" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">timeZone</td>
                <td align="left">String</td>
                <td align="left">Address</td>
                <td align="left">
                  <xref target="addresses" format="default"/>
                </td> align="left">Address (<xref target="address" format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">titles</td>
                <td align="left">Id[Title]</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="titles" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">uid</td>
                <td align="left">String</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="uid" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">units</td>
                <td align="left">OrgUnit[]</td>
                <td align="left">Organization</td>
                <td align="left">
                  <xref align="left">Organization (<xref target="organizations" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">updated</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Card</td>
                <td align="left">
                  <xref align="left">Card (<xref target="updated" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">uri</td>
                <td align="left">String</td>
                <td align="left">Author, Calendar, CryptoKey, Directory, Link, Media, OnlineService, SchedulingAddress</td>
                <td align="left"><xref target="notes" format="default"/>, <xref target="resource" format="default"/>, <xref target="calendars" format="default"/>, <xref target="cryptoKeys" format="default"/>, <xref target="directories" format="default"/>, <xref target="links" format="default"/>, <xref target="media" format="default"/>, <xref target="onlineServices" format="default"/>, align="left">Author (<xref target="notes"/>), Calendar (<xref target="calendars"/>), CryptoKey (<xref target="cryptoKeys"/>), Directory (<xref target="directories"/>), Link (<xref target="links"/>), Media (<xref target="media"/>), OnlineService (<xref target="onlineServices"/>), SchedulingAddress (<xref target="schedulingAddresses"/>). Also see <xref target="schedulingAddresses" format="default"/></td> target="resource"/>.
                </td>
              </tr>
              <tr>
                <td align="left">user</td>
                <td align="left">String</td>
                <td align="left">OnlineService</td>
                <td align="left">
                  <xref align="left">OnlineService (<xref target="onlineServices" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">utc</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Timestamp</td>
                <td align="left">
                  <xref align="left">Timestamp (<xref target="anniversaries" format="default"/>
                </td> format="default"/>)</td>
              </tr>
              <tr>
                <td align="left">value</td>
                <td align="left">String</td>
                <td align="left">AddressComponent, NameComponent, PersonalInfo</td> align="left">AddressComponent (<xref target="addresscomponent"/>), NameComponent (<xref target="namecomponent"/>), PersonalInfo (<xref target="personalInfo"/>)</td>
              </tr>
              <tr anchor="iana-property-registry-version">
                <td align="left"><xref target="addresses" format="default"/>,
                  <xref target="name" format="default"/>,
                  <xref target="personalInfo" format="default"/></td> align="left">version</td>
                <td align="left">String</td>
                <td align="left">Card (<xref target="prop-version"/>)</td>
              </tr>
              <tr>
                <td align="left">year</td>
                <td align="left">UnsignedInt</td>
                <td align="left">PartialDate</td>
                <td align="left">
                  <xref target="anniversaries" format="default"/>
                </td> align="left">PartialDate (<xref target="anniversaries"/>)</td>
              </tr>
            </tbody>
          </table>
          <t>The following table lists the initial <tt>reserved</tt> "reserved" usage entries of the "JSContact Properties" registry.  All For
            this property, the Change Controller is "IETF", and the RFC section references are for <xref target="I-D.ietf-calext-jscontact"/>.  The change controller for all these properties reference is <tt>IETF</tt>.</t> for RFC 9553.
          </t>
          <table anchor="tab-iana-reserved-property-registry" align="center">
            <name>JSContact Properties with "reserved" usage</name> Usage</name>
            <thead>
              <tr>
                <th align="left">Property Name</th>
                <th align="left">Property Type</th>
                <th align="left">Property Context</th>
                <th align="left">Reference or Description</th> align="left">Reference/Description</th>
                <th align="left">Intended Usage</th>
              </tr>
            </thead>
            <!-- Everything in here should be sorted alphabetically: table entries by property name, the references for each property alphabetically by the object type or property they refer to -->
            <tbody>
              <tr>
                <td align="left">extra</td>
                <td align="left">not applicable</td>
                <td align="left">not applicable</td>
                <td align="left">
                  <xref target="prop-extra" format="default"/>
                </td>
                <td align="left">reserved</td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
      <section anchor="iana-type-registry" numbered="true" toc="default">
        <name>Creation of the "JSContact Types" JSContact Types Registry</name>
        <t>IANA is asked to create has created the "JSContact Types" registry. The purpose of this new registry is to avoid name collisions
          for JSContact type names and provide a complete reference for all data types used for JSContact property values.</t>
          values.
        </t>
        <t>The registry entries sort alphabetically in ascending order by the "Type Name" column. Equal entries sort in
          any order.</t> order.
        </t>
        <t>The registry process for a new type is outlined in <xref target="iana-registry-policy" format="default"/>.</t> format="default"/>.
        </t>
        <section anchor="iana-type-registry-template" numbered="true" toc="default">
          <name>"JSContact Types"
          <name>JSContact Types Registry Template</name>
          <dl newline="false">
            <dt>Type Name:</dt>
            <dd>the
            <dd>The name of the type</dd>
            <dt>Reference or Description:</dt>
            <dd>a brief description or RFC number and section reference where the Type is specified (may be omitted for "reserved" type names)</dd> type.</dd>
            <dt>Intended Usage:</dt>
            <dd>common, reserved,
            <dd>May be "common", "reserved", or obsolete</dd> "obsolete".</dd>
            <dt>Since Version:</dt>
            <dd>This defines the
            <dd>The JSContact version on which this type definition is based on. based. The version <bcp14>MUST</bcp14> be one of
              the allowed values of the <tt>version</tt> version property in the JSContact Enum Value "JSContact Version" registry (see <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
            <dt>Until Version:</dt>
            <dd>This defines the
            <dd>The JSContact version after which this the type definition got obsoleted and was obsoleted; therefore, it <bcp14>MUST NOT</bcp14> NOT
            </bcp14> be used in later versions. The Until Version value either <bcp14>MUST</bcp14> <bcp14>MUST NOT</bcp14> be not set, set or <bcp14>
              MUST
            </bcp14> be one of the allowed values of the <tt>version</tt> version property in the JSContact Enum Value "JSContact Version" registry (see <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
            <dt>Change Controller:</dt>
            <dd>This is who may request
            <dd>Person or entity responsible for requesting a change to this the entry's definition (<tt>IETF</tt> ("IETF" for RFCs from the
              IETF stream).</dd> stream).
            </dd>
            <dt>Reference or Description:</dt>
            <dd>A brief description or RFC number and section reference where the Type is specified. For reserved type
              names, the reference or description <bcp14>MAY</bcp14> be omitted.
            </dd>
          </dl>
        </section>
        <section anchor="iana-type-registry-contents" numbered="true" toc="default">
          <name>Initial Contents for of the "JSContact Types" JSContact Types Registry</name>
          <t>The following table lists the initial <tt>common</tt> "common" usage entries of in the JSContact Types "JSContact Types" registry.  The For all of
            these types, the Since Version for all types is <tt>1.0</tt>.  The "1.0", the Until Version for all types is not set.  All set, the Change Controller is "IETF", and
            RFC section references are for <xref target="I-D.ietf-calext-jscontact"/>.  The change controller for all these properties is <tt>IETF</tt>.</t> RFC 9553.
          </t>
          <table anchor="tab-iana-type-registry-common" align="left">
            <name>JSContact Types with "common" usage</name> Usage</name>
            <thead>
              <tr>
                <th align="left">Type Name</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Address</td>
                <td align="left">
                  <xref target="addresses" target="address" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">AddressComponent</td>
                <td align="left">
                  <xref target="addresses" target="addresscomponent" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Anniversary</td>
                <td align="left">
                  <xref target="anniversaries" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Author</td>
                <td align="left">
                  <xref target="notes" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Boolean</td>
                <td align="left">
                  <xref target="type-signatures" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Calendar</td>
                <td align="left">
                  <xref target="calendars" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Card</td>
                <td align="left">
                  <xref target="card" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">CryptoKey</td>
                <td align="left">
                  <xref target="cryptoKeys" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Directory</td>
                <td align="left">
                  <xref target="directories" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">EmailAddress</td>
                <td align="left">
                  <xref target="emails" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Id</td>
                <td align="left">
                  <xref target="id" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Int</td>
                <td align="left">
                  <xref target="int-unsignedint" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">LanguagePref</td>
                <td align="left">
                  <xref target="preferredLanguages" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="links" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Media</td>
                <td align="left">
                  <xref target="media" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Name</td>
                <td align="left">
                  <xref target="name" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">NameComponent</td>
                <td align="left">
                  <xref target="name" target="namecomponent" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Nickname</td>
                <td align="left">
                  <xref target="nicknames" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Note</td>
                <td align="left">
                  <xref target="notes" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Number</td>
                <td align="left">
                  <xref target="type-signatures" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">OnlineService</td>
                <td align="left">
                  <xref target="onlineServices" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Organization</td>
                <td align="left">
                  <xref target="organizations" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">OrgUnit</td>
                <td align="left">
                  <xref target="organizations" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">PartialDate</td>
                <td align="left">
                  <xref target="anniversaries" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">PatchObject</td>
                <td align="left">
                  <xref target="patchobject" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">PersonalInfo</td>
                <td align="left">
                  <xref target="personalInfo" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Phone</td>
                <td align="left">
                  <xref target="phones" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Pronouns</td>
                <td align="left">
                  <xref target="speakToAs" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Relation</td>
                <td align="left">
                  <xref target="relatedTo" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">SchedulingAddress</td>
                <td align="left">
                  <xref target="schedulingAddresses" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">SpeakToAs</td>
                <td align="left">
                  <xref target="speakToAs" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">String</td>
                <td align="left">
                  <xref target="type-signatures" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Timestamp</td>
                <td align="left">
                  <xref target="anniversaries" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">Title</td>
                <td align="left">
                  <xref target="titles" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">UnsignedInt</td>
                <td align="left">
                  <xref target="int-unsignedint" format="default"/>
                </td>
              </tr>
              <tr>
                <td align="left">UTCDateTime</td>
                <td align="left">
                  <xref target="utcdatetime" format="default"/>
                </td>
              </tr>
            </tbody>
          </table>
          <t>The following table lists the initial <tt>reserved</tt> "reserved" usage entries entry of the JSContact Types "JSContact Types" registry.  All types are for For this
            type, the version <tt>1.0</tt>.  All is "1.0", the Change Controller is "IETF", and the RFC section references are for <xref target="I-D.ietf-calext-jscontact"/>.  The change controller for all these properties reference is <tt>IETF</tt>.</t> for RFC 9553.
          </t>
          <table anchor="tab-iana-type-registry-reserved" align="left">
            <name>JSContact Types with "reserved" usage</name> Usage</name>
            <thead>
              <tr>
                <th align="left">Type Name</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Resource</td>
                <td align="left">
                  <xref target="resource" format="default"/>
                </td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
      <section anchor="iana-enum-registry" numbered="true" toc="default">
        <name>Creation of the "JSContact JSContact Enum Values" Values Registry</name>
        <t>IANA is asked to create has created the "JSContact Enum Values" registry. The purpose of the new registry is to allow
          interoperable extension of semantics for JSContact properties with enumerable values. Each such property will
          have a subregistry of allowed values.</t> values.
        </t>
        <t>The registry entries sort alphabetically in ascending order by the following columns: "Property Name" column first,
          "Property Context" second, and "Since Version" third. The enum values sort alphabetically ascending. in ascending order.
          Equal entries sort in any order.</t> order.
        </t>
        <t>The registry process for a new enum value or adding a new enumerable property is outlined in <xref target="iana-registry-policy" format="default"/>.</t> format="default"/>.
        </t>
        <section anchor="iana-enum-registry-registry-template" numbered="true" toc="default">
          <name>"JSContact
          <name>JSContact Enum Values" Values Registry Property Template</name>
          <t>This template is for adding a subregistry for a new enumerable property to the "JSContact Enum" registry.</t> Enum Values"
            registry.
          </t>
          <dl newline="false">
            <dt>Property Name:</dt>
            <dd>These are the
            <dd>The name(s) of the property or properties where these values may be used. This <bcp14>MUST</bcp14> be
              registered in the "JSContact Properties" registry.</dd> registry.
            </dd>
            <dt>Context:</dt>
            <dd>This is the
            <dd>The list of allowed object types where the property or properties may appear, as registered in the
              "JSContact Properties" registry. This disambiguates where there may be two distinct properties with the
              same name in different contexts.</dd> contexts.
            </dd>
            <dt>Since Version:</dt>
            <dd>This defines the
            <dd>The JSContact version on which this the enum value definition is based on. based. The version <bcp14>MUST</bcp14> be
              one of the allowed values of the <tt>version</tt> version property in the JSContact Enum Value "JSContact Version" registry (see <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
            <dt>Until Version:</dt>
            <dd>This defines the
            <dd>The JSContact version after which this the enum value definition was obsoleted; therefore, the enum value
              definition got obsoleted and <bcp14>MUST NOT</bcp14> be used in later versions. The Until Version value either <bcp14>MUST</bcp14> <bcp14>MUST
                NOT
              </bcp14> be not set, set or <bcp14>MUST</bcp14> be one of the allowed values of the <tt>version</tt> version property in the JSContact Enum Value
              "JSContact Version" registry (see <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
            <dt>Change Controller:</dt>
            <dd>This is who may request
            <dd>Person or entity responsible for requesting a change to this the entry's definition (<tt>IETF</tt> ("IETF" for RFCs from the
              IETF stream).</dd>
            <dt>Initial Contents:</dt>
            <dd>This is stream).
            </dd>
            <dt>Reference or Description:</dt><dd>A brief description or RFC number and
            section reference for the semantics of the value.</dd>
	  </dl>
	    <t>
            Note that the initial contents will be the initial list of defined values for this the enum, using the template defined in <xref target="iana-enum-registry-value-template" format="default"/>. A subregistry will be created with
              these values for this property name/context tuple.</dd>
          </dl> tuple.
            </t>

        </section>
        <section anchor="iana-enum-registry-value-template" numbered="true" toc="default">
          <name>"JSContact
          <name>JSContact Enum Values" Values Registry Value Template</name>
          <t>This template is for adding a new enum value to a subregistry in the JSContact "JSContact Enum Values" registry.</t>
          <dl newline="false">
            <dt>Enum Value:</dt>
            <dd>The verbatim value of the enum.</dd>
            <dt>Reference or Description:</dt>
            <dd>A brief description or RFC number and section reference for the semantics of this value.</dd>
            <dt>Since Version:</dt>
            <dd>The JSContact version on which the enum value definition is based on. based. The version <bcp14>MUST</bcp14> be
              one of the allowed values of the <tt>version</tt> version property in the JSContact Enum Value "JSContact Version" registry (see <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
            <dt>Until Version:</dt>
            <dd>The JSContact version after which this the enum value was obsoleted; therefore, the enum value got obsoleted and <bcp14>MUST NOT</bcp14>
              NOT
            </bcp14> be used in later versions. The Until Version value either <bcp14>MUST</bcp14> <bcp14>MUST NOT</bcp14> be not set, set or <bcp14>
              MUST
            </bcp14> be one of the allowed values of the <tt>version</tt> version property in the JSContact Enum Value "JSContact Version" registry (see <xref target="tab-iana-version-registry"/>).</dd> target="tab-iana-version-registry"/>).
            </dd>
	    <dt> Change Controller:</dt><dd>Person or entity responsible for requesting a
      change to the entry's definition ("IETF" for RFCs from the IETF
      stream).</dd>
            <dt>Reference or Description:</dt>
            <dd>A brief description or RFC number and section reference for the semantics of the value.</dd>
          </dl>
        </section>
        <section anchor="iana-enum-registry-contents" numbered="true" toc="default">
          <name>Initial Contents for of the "JSContact JSContact Enum Values" Values Registry</name>
          <t>For all entries in each subregistry created in this section, all RFC section references are for <xref target="I-D.ietf-calext-jscontact"/>.  For all entries, the Since Version is <tt>1.0</tt>, "1.0", the Until Version
            is not set, the Change Controller is <tt>IETF</tt>.</t> "IETF", and RFC section references are for RFC 9553.
          </t>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>contexts</dd>
            <dt>Context:</dt>
            <dd>Address</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-addr-contexts" align="left">
                <name>JSContact Enum Values for contexts (Context: Address)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">billing</td>
                    <td align="left">
                      <xref target="addresses" target="address" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">delivery</td>
                    <td align="left">
                      <xref target="addresses" target="address" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">private</td>
                    <td align="left">
                      <xref target="prop-contexts" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">work</td>
                    <td align="left">
                      <xref target="prop-contexts" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>contexts</dd>
            <dt>Context:</dt>
            <dd>Calendar, CryptoKey, Directory, EmailAddress, LanguagePref, Link, Media, Nickname, OnlineService,
              Organization, Phone, Pronouns, SchedulingAddress</dd> SchedulingAddress
            </dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-contexts" align="left">
                <name>JSContact Enum Values for contexts (Context: Calendar, CryptoKey, Directory, EmailAddress,
                  LanguagePref, Link, Media, Nickname, OnlineService, Organization, Phone, Pronouns, SchedulingAddress)</name> SchedulingAddress)
                </name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">private</td>
                    <td align="left">
                      <xref target="prop-contexts" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">work</td>
                    <td align="left">
                      <xref target="prop-contexts" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>features</dd>
            <dt>Context:</dt>
            <dd>Phone</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-phone-features" align="left">
                <name>JSContact Enum Values for features (Context: Phone)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">fax</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">main-number</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">mobile</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">pager</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">text</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">textphone</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">video</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">voice</td>
                    <td align="left">
                      <xref target="phones" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>grammaticalGender</dd>
            <dt>Context:</dt>
            <dd>SpeakToAs</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-speaktoas-grammaticalgender" align="left">
                <name>JSContact Enum Values for kind grammaticalGender (Context: SpeakToAs)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">animate</td>
                    <td align="left">
                      <xref target="speakToAs" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">common</td>
                    <td align="left">
                      <xref target="speakToAs" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">feminine</td>
                    <td align="left">
                      <xref target="speakToAs" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">inanimate</td>
                    <td align="left">
                      <xref target="speakToAs" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">masculine</td>
                    <td align="left">
                      <xref target="speakToAs" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">neuter</td>
                    <td align="left">
                      <xref target="speakToAs" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>AddressComponent</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-addresscomponent-kind" align="left">
                <name>JSContact Enum Values for kind (Context: AddressComponent)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">apartment</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">block</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">building</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">country</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">direction</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">district</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">floor</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">landmark</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">locality</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">name</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">number</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">postcode</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">postOfficeBox</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">region</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">room</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">separator</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">subdistrict</td>
                    <td align="left">
                      <xref target="addresses" target="addresscomponent" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>Anniversary</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-anniversary-kind" align="left">
                <name>JSContact Enum Values for kind (Context: Anniversary)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">birth</td>
                    <td align="left">
                      <xref target="anniversaries" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">death</td>
                    <td align="left">
                      <xref target="anniversaries" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">wedding</td>
                    <td align="left">
                      <xref target="anniversaries" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>Calendar</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-calendarresource-kind" align="left">
                <name>JSContact Enum Values for kind (Context: Calendar)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">calendar</td>
                    <td align="left">
                      <xref target="calendars" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">freeBusy</td>
                    <td align="left">
                      <xref target="calendars" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>Card</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-card-kind" align="left">
                <name>JSContact Enum Values for kind (Context: Card)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">application</td>
                    <td align="left">
                      <xref target="kind" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">device</td>
                    <td align="left">
                      <xref target="kind" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">group</td>
                    <td align="left">
                      <xref target="kind" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">individual</td>
                    <td align="left">
                      <xref target="kind" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">location</td>
                    <td align="left">
                      <xref target="kind" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">org</td>
                    <td align="left">
                      <xref target="kind" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>Directory</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-directoryresource-kind" align="left">
                <name>JSContact Enum Values for kind (Context: Directory)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">directory</td>
                    <td align="left">
                      <xref target="directories" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">entry</td>
                    <td align="left">
                      <xref target="directories" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>Link</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-linkresource-kind" align="left">
                <name>JSContact Enum Values for kind (Context: Link)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">contact</td>
                    <td align="left">
                      <xref target="links" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>Media</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-mediaresource-kind" align="left">
                <name>JSContact Enum Values for kind (Context: Media)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">logo</td>
                    <td align="left">
                      <xref target="media" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">photo</td>
                    <td align="left">
                      <xref target="media" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">sound</td>
                    <td align="left">
                      <xref target="media" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>NameComponent</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-namecomponent-kind" align="left">
                <name>JSContact Enum Values for kind (Context: NameComponent)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">credential</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">generation</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">given</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">given2</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">separator</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">surname</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">surname2</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">title</td>
                    <td align="left">
                      <xref target="name" target="namecomponent" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>PersonalInfo</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-personalinformation-kind" align="left">
                <name>JSContact Enum Values for kind (Context: PersonalInfo)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">expertise</td>
                    <td align="left">
                      <xref target="personalInfo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">hobby</td>
                    <td align="left">
                      <xref target="personalInfo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">interest</td>
                    <td align="left">
                      <xref target="personalInfo" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>kind</dd>
            <dt>Context:</dt>
            <dd>Title</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-title-kind" align="left">
                <name>JSContact Enum Values for kind (Context: Title)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">role</td>
                    <td align="left">
                      <xref target="titles" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">title</td>
                    <td align="left">
                      <xref target="titles" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>level</dd>
            <dt>Context:</dt>
            <dd>PersonalInfo</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-personalinformation-level" align="left">
                <name>JSContact Enum Values for level (Context: PersonalInfo)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">high</td>
                    <td align="left">
                      <xref target="personalInfo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">low</td>
                    <td align="left">
                      <xref target="personalInfo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">medium</td>
                    <td align="left">
                      <xref target="personalInfo" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>phoneticSystem</dd>
            <dt>Context:</dt>
            <dd>Address, Name</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-pronounce-system" align="left">
                <name>JSContact Enum Values for phoneticSystem (Context: Address, Name)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">ipa</td>
                    <td align="left">
                      <xref target="prop-phonetic" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">jyut</td>
                    <td align="left">
                      <xref target="prop-phonetic" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">piny</td>
                    <td align="left">
                      <xref target="prop-phonetic" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>relation</dd>
            <dt>Context:</dt>
            <dd>Relation</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-relation-relation" align="left">
                <name>JSContact Enum Values for relation (Context: Relation)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">acquaintance</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">agent</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">child</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">colleague</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">contact</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">co-resident</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">co-worker</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">crush</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">date</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">emergency</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">friend</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">kin</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">me</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">met</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">muse</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">neighbor</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">parent</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">sibling</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">spouse</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">sweetheart</td>
                    <td align="left">
                      <xref target="relatedTo" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
          <dl spacing="compact" newline="false" indent="20">
            <dt>Property Name:</dt>
            <dd>phoneticSystem</dd>
            <dt>Context:</dt>
            <dd>Address, Name</dd>
            <dt>Initial Contents:</dt>
            <dd>
              <table anchor="tab-iana-enum-pronounce-system" align="left">
                <name>JSContact Enum Values for phoneticSystem (Context: Address, Name)</name>
                <thead>
                  <tr>
                    <th align="left">Enum Value</th>
                    <th align="left">Reference or Description</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">ipa</td>
                    <td align="left">
                      <xref target="prop-phonetic" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">jyut</td>
                    <td align="left">
                      <xref target="prop-phonetic" format="default"/>
                    </td>
                  </tr>
                  <tr>
                    <td align="left">piny</td>
                    <td align="left">
                      <xref target="prop-phonetic" format="default"/>
                    </td>
                  </tr>
                </tbody>
              </table>
            </dd>
          </dl>
        </section>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>Contact information is very privacy-sensitive. privacy sensitive. It can reveal the identity, location and location, credentials information,
        employment status, interests and hobbies, and social network of a user. Its transmission and storage must be
        done carefully to protect it from possible threats, threats such as eavesdropping, replay, message insertion, deletion,
        modification, and on-path attacks.</t> attacks.
      </t>
      <t>The data being stored and transmitted may be used in systems with real-world consequences. For example, a
        malicious actor might provide JSContact data that uses the name of another person but insert their contact
        details to impersonate the unknown victim. Such systems must be careful to authenticate all data they receive to
        prevent them from being subverted and ensure the change comes from an authorized entity.</t> entity.
      </t>
      <t>This document only defines the data format; such considerations are primarily the concern of the API or method
        of storage and transmission of such files.</t> files.
      </t>
      <section anchor="json-parsing" numbered="true" toc="default">
        <name>JSON Parsing</name>
        <t>The security considerations of
          <xref target="RFC8259" format="default"/>
          apply to the use of JSON as the data interchange format.
        </t>
        <t>As for any serialization format, parsers need to thoroughly check the syntax of the supplied data. JSON uses
          opening and closing brackets for several types and structures, and it is possible that the end of the supplied
          data will be reached when scanning for a matching closing bracket; this is an error condition, and
          implementations need to stop scanning at the end of the supplied data.</t> data.
        </t>
        <t>JSON also uses a string encoding with some escape sequences to encode special characters within a string.
          Care is needed when processing these escape sequences to ensure that they are fully formed before the special
          processing is triggered, with special care taken when the escape sequences appear adjacent to other
          (non-escaped) special characters or adjacent to the end of data (as in the previous paragraph).</t> paragraph).
        </t>
        <t>If parsing JSON into a non-textual structured data format, implementations may need to allocate storage to
          hold JSON string elements. Since JSON does not use explicit string lengths, the risk of denial of service due
          to resource exhaustion is small, but implementations may still wish to place limits on the size of allocations
          they are willing to make in any given context, to avoid untrusted data causing excessive memory allocation.</t> allocation.
        </t>
      </section>
      <section anchor="uri-values" numbered="true" toc="default">
        <name>URI Values</name>
        <t>Several JSContact properties contain URIs as values, and processing these properties requires extra care.
          <xref target="RFC3986" sectionFormat="of" section="7"/>
          discusses security risks related to URIs.</t> URIs.
        </t>
        <t>Fetching remote resources carries inherent risks. Connections must only be allowed on well-known ports, using
          allowed protocols (generally, just HTTP/HTTPS on their default ports). The URL must be resolved externally and
          not allowed to access internal resources. Connecting to an external source reveals IP (and therefore often
          location) information.</t> information.
        </t>
        <t>A maliciously constructed JSContact object may contain a very large number of URIs. In the case of published
          address books with a large number of subscribers, such objects could be widely distributed. Implementations
          should be careful to limit the automatic fetching of linked resources to reduce the risk of this being an
          amplification vector for a denial-of-service attack.</t> attack.
        </t>
      </section>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.ietf-uuidrev-rfc4122bis" to="UUID"/>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1034.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1034.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1035.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1035.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2046.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2046.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2426.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2426.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4122.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4122.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5322.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5322.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5870.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5870.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6350.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6350.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6901.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6901.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7493.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7493.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7529.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7529.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/>
        <!--[rfced] The 2006 version of this reference has been withdrawn;
        therefore, we replaced it with the 2020 version. Please let us
        know if any further updates are needed.

        Original:
           [ISO.3166-1.2006]
                International Organization for Standardization, "Codes for
                the representation of names of countries, 3rd edition",
                ISO Standard 3166-1, 2006.

        Current:
           [ISO.3166-1]
                International Organization for Standardization, "Codes for
                the representation of names of countries and their subdivisions -
                Part 1: Country codes", ISO 3166-1:2020, August 2020.
        -->
        <reference anchor="ISO.3166-1.2006"> anchor="ISO.3166-1">
          <front>
            <title>Codes for the representation of names of countries, 3rd
              edition</title> countries and their subdivisions -- Part 1: Country codes
            </title>
            <author>
              <organization>International Organization for Standardization</organization>
            </author>
            <date year="2006"/> month="August" year="2020"/>
          </front>
          <seriesInfo name="ISO" value="Standard 3166-1"/> value="3166-1:2020"/>
        </reference>
        <reference anchor="IANATZ" anchor="IANA-TZ" target="https://www.iana.org/time-zones">
          <front>
            <title>IANA Time
            <title>Time Zone Database</title>
            <author/>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="IANAvCard" target="https://www.iana.org/assignments/vcard-elements/vcard-elements.xhtml"> anchor="IANA-vCard" target="https://www.iana.org/assignments/vcard-elements">
          <front>
            <title>IANA vCard
            <title>vCard Elements</title>
            <author/>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3966.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3966.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3987.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3987.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6351.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6351.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6473.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6473.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6474.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6474.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6715.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6715.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6869.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6869.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7095.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7095.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8499.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8499.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8605.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-uuidrev-rfc4122bis.xml"/> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8605.xml"/>
        <!--[I-D.ietf-uuidrev-rfc4122bis] in RFC-EDITOR state; entered the long way to include the correct initials-->
        <reference anchor="I-D.ietf-uuidrev-rfc4122bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-uuidrev-rfc4122bis-14">
          <front>
            <title>Universally Unique IDentifiers (UUID)</title>
            <author fullname="Kyzer R. Davis" initials="K. R." surname="Davis">
              <organization>Cisco Systems</organization>
            </author>
            <author fullname="Brad Peabody" initials="B. G." surname="Peabody">
              <organization>Uncloud</organization>
            </author>
            <author fullname="P. Leach" initials="P." surname="Leach">
              <organization>University of Washington</organization>
            </author>
            <date day="6" month="November" year="2023"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-uuidrev-rfc4122bis-14"/>
        </reference>

        <!--[I-D.ietf-calext-vcard-jscontact-extensions] in AUTH48 state; entered the long way to include the correct initials--><!-- This is going to be RFC 9554 -->
<reference anchor="RFC9554" target="https://www.rfc-editor.org/info/rfc9554">
          <front>
            <title>vCard Format Extension for JSContact</title>
            <author fullname="Robert Stepanek" initials="R." surname="Stepanek">
              <organization>Fastmail</organization>
            </author>
            <author fullname="Mario Loffredo" initials="M." surname="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>

        <!--[I-D.ietf-calext-jscontact-vcard] in AUTH48 state; entered the long way to include the correct initials--> <!-- This is going to be RFC 9555 -->
        <reference anchor="RFC9555" target="https://www.rfc-editor.org/info/rfc9555">
          <front>
            <title>vCard Format Extension for JSContact</title>
            <author fullname="Robert Stepanek" initials="R." surname="Stepanek">
              <organization>Fastmail</organization>
            </author>
            <author fullname="Mario Loffredo" initials="M." surname="Loffredo">
              <organization>IIT-CNR</organization>
            </author>
            <date month="March" year="2024"/>
          </front>
          <seriesInfo name="RFC" value="9555"/>
	   <seriesInfo name="DOI" value="10.17487/RFC9555"/>
        </reference>

        <!-- [I-D.ietf-uuidrev-rfc4122bis] in EDIT state; companion document RFC YYY1
<reference anchor="RFCYYY1" target="https://www.rfc-editor.org/info/rfcYYY1">
<front>
<title>Universally Unique IDentifiers (UUID)</title>
<author initials="K. R." surname="Davis" fullname="Kyzer R. Davis">
<organization>Cisco Systems</organization>
</author>
<author initials="B. G." surname="Peabody" fullname="Brad Peabody">
<organization>Uncloud</organization>
</author>
<author initials="P." surname="Leach" fullname="P. Leach">
<organization>University of Washington</organization>
</author>
<date month="November" year="2024"/>
</front>
<seriesInfo name="RFC" value="YYY1"/>
<seriesInfo name="DOI" value="10.17487/RFCYYY1"/>
</reference>
-->
        <!-- Note: Removed [I-D.ietf-calext-jscontact] as it is a self-reference.
     <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-calext-jscontact.xml"/> href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-calext-jscontact.xml"/>-->
        <reference anchor="IPA" target="https://www.internationalphoneticalphabet.org/">
          <front>
            <title>International Phonetic Alphabet</title>
            <author/>
            <author>
              <organization>IPA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="UBiDi" target="https://www.unicode.org/reports/tr9/">
          <front>
            <title>Unicode®
            <title>Unicode Standard Annex #9: Unicode Bidirectional Algorithm</title>
            <author/>
            <author>
              <organization>The Unicode Consortium</organization>
            </author>
            <date month="August" year="2023"/>
          </front>
          <seriesInfo name="Unicode" value="15.1.0"/>
          <refcontent>Revision 48</refcontent>
        </reference>
        <reference anchor="W3C-URL" anchor="WHATWG-URL" target="https://url.spec.whatwg.org">
          <front>
            <title>W3C WG URL -
            <title>URL Living Standard — Last Updated 21 August 2023</title>
            <author/> Standard</title>
            <author>
              <organization>WHATWG
              </organization>
            </author>
            <date month="January" year="2024"/>
          </front>
        </reference>
      </references>
    </references>
    <!-- [rfced] Terminology

a) Throughout the text, the following terminology appears to be used
inconsistently. Please review these occurrences and let us know if/how they
may be made consistent.

  kind separator vs. separator kind

Additionally, let us know if/how the capitalization of "resource" terminology
should be made consistent. Please note that "resource values" and "Resource
data type" are used consistently.

  Resource data type vs. resource data type
  Resource object vs. resource object
  Resource type vs. resource type

b) Note that we updated the text with the latter forms for consistency. Please
let us know if any further updates are needed.

  Cardinal -> cardinal (per use in other RFCs)
  Data Interchange Format -> data interchange format (per RFC 8259)
  JSON pointer -> JSON Pointer (but lowercase "pointer" when used in general) (per RFC 6901)
-->
    <!-- [rfced] FYI: We have added expansions for the following abbreviations
per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each
expansion in the document carefully to ensure correctness.

  Common Locale Data Repository (CLDR)
  Internet JSON (I-JSON)
  Universally Unique Identifier (UUID)
-->
    <!-- [rfced] Please review the "Inclusive Language" portion of the online
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed.

Note that our script did not flag any words in particular, but this should
still be reviewed as a best practice.
-->
  </back>
</rfc>