1.3.1. Objects and Properties

JSContact defines data types for contact information such as addresses or names. This information typically consists of multiple related elements; for 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 that has the following:¶

1. A unique type name registered in the IANA "JSContact Types" registry (Section 3.6).¶
2. One or more object members for which the name and allowed value types are specified. Such members are called "properties".¶
3. One property named @type with a string value that matches the type name of the JSContact object. In general, this property does not need to be set explicitly as outlined in Section 1.3.4.¶

The following sections specify how to define JSContact object types. Sections 1.7 and 1.8 then define the exact requirements for property names.¶

The next paragraph illustrates how a JSContact object is defined.¶

• 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.¶

Here, a JSContact object type named Foo is defined. In addition to its @type property, it has a property named qux for which values MUST be valid according to the definition of the Number type. The property has one attribute, mandatory, which specifies that the property MUST be present for an instance of this JSContact object to be valid. Finally, a free-text description describes the semantics and further restrictions.¶

1.3.2. Type Signatures

Type signatures are given for all JSON values and JSContact definitions in this document. The following conventions are used:¶

String:

The JSON string type.¶

Number:

The JSON number type.¶

Boolean:

The JSON boolean type.¶

A[B]:

A JSON object where all keys are of type A and all values are of type B.¶

A[]:

A JSON array of values of type A.¶

A|B:

The value is either of type A or of type B.¶

* *:

The type is undefined (the value could be any type, although permitted values may be constrained by the context of this value).¶

Section 1.4 defines common data types, including signed or unsigned integers and dates.¶

1.3.3. Property Attributes

Object properties may also have a set of attributes defined along with the type signature. These have the following meanings:¶

mandatory:

The property MUST be set for an instance of this object to be valid.¶

optional:

The property can, but need not, be set for an instance of this object to be valid.¶

default:

This is followed by a JSON value. That value will be used for this property if it is omitted.¶

defaultType:

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 @type property.¶

1.3.4. The @type Property

@type:

String. Specifies the type of the object. It MUST match the type name of the JSContact object of which the JSON object is an instance of.¶

The purpose of the @type property is to help implementations identify which JSContact object type a given JSON object represents. Implementations MUST validate that JSON objects with this property conform to the specification of the JSContact object type of that name.¶

In many cases, the @type property value is implied by where its object occurs in JSContact data. Assuming that both A and B are JSContact object types:¶

• An object that is set as the value for a property with type signature A MAY have the @type property set. If the @type property is not set, then its value is implied to be A by the property definition.¶
• An object that is set as the value for a property with type signature A|B (defaultType: A) MAY have the @type property set if it is an instance of A. It MUST have the @type property set if it is an instance of B. If, instead, the defaultType attribute is not defined, then the @type property MUST also be set for A.¶
• An object that is not the value of a property, such as the root of JSON data (directly or as a member of an array), MUST have the @type property set.¶

1.4.1. Id

Where Id is given as a data type, it means a String of at least 1 and a maximum of 255 octets in size, and it MUST only contain characters from the URL and Filename Safe base64url alphabet, as defined in Section 5 of [RFC4648], excluding the pad character (=). This means the allowed characters are the ASCII alphanumeric characters (A-Za-z0-9), hyphen (-), and underscore (_).¶

In many places in 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 and, when applicable, for the objects in question to be referenced from other objects within the JSContact object. The map keys MUST be preserved across multiple versions of the JSContact object.¶

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 Card (Section 2) objects might use the same Ids in their respective photos properties. Or within the same Card, the same Id could appear in the emails and phones properties. These situations do not imply any semantic connections among the objects.¶

1.4.2. Int and UnsignedInt

Where Int is given as a data type, it means an integer in the range -2⁵³+1 <= value <= 2⁵³-1, which is the safe range for integers stored in a floating-point double, represented as a JSON Number.¶

Where UnsignedInt is given as a data type, it means an integer in the range 0 <= value <= 2⁵³-1 represented as a JSON Number.¶

1.4.3. PatchObject

A PatchObject is of type 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 format [RFC6901]. The paths have an implicit leading /, so each key is prefixed with / before applying the JSON Pointer evaluation algorithm.¶

A patch within a PatchObject is only valid if all the following conditions apply:¶

1. The pointer MAY reference inside an array, but if the last reference token in the pointer is an array index, then the patch value MUST NOT be null. The pointer MUST NOT use "-" as an array index in any of its reference tokens (i.e., you MUST NOT insert/delete from an array, but you MAY replace the contents of its existing members. To add or remove members, one needs to replace the complete array value).¶
2. All reference tokens prior to the last (i.e., the value after the final slash) MUST already exist as values in the object being patched. If the last reference token is an array index, then a member at this index MUST already exist in the referenced array.¶
3. There MUST NOT be two patches in the PatchObject where the pointer of one is the prefix of the pointer of the other, e.g., addresses/1/city and addresses.¶
4. The value for the patch MUST be valid for the property being set (of the correct type and obeying any other applicable restrictions), or if null, the property MUST be optional.¶

The value associated with each pointer determines how to apply that patch:¶

• If null, remove the property from the patched object. If the key is not present in the parent, this is a no-op.¶
• 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).¶

A PatchObject does not define its own @type (Section 1.3.4) property. Instead, an @type property in a patch MUST be handled as any other patched property value.¶

Implementations MUST reject a PatchObject in its entirety if any of its patches are invalid. Implementations MUST NOT apply partial patches.¶

1.4.4. Resource

The Resource data type defines a resource associated with the entity represented by the Card, identified by a URI [RFC3986]. Later in this 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 MAY define additional properties for their value types.¶

The @type property value MUST NOT be Resource; instead, it MUST be the name of a concrete resource type (see Section 2.6). A Resource object has the following properties.¶

@type:

String. Specifies the type of this resource object. The allowed value is defined in later sections of this document for each concrete resource type (Section 2.6).¶

kind:

String (optional). 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.¶

uri:

String (mandatory). The resource value. This MUST be a URI as defined in Section 3 of [RFC3986].¶

mediaType:

String (optional). Used for URI resource values. Provides the media type [RFC2046] of the resource identified by the URI.¶

contexts:

String[Boolean] (optional). The contexts in which to use this resource. Also see Section 1.5.1.¶

pref:

UnsignedInt (optional). The preference of the resource in relation to other resources. Also see Section 1.5.4.¶

label:

String (optional). A custom label for the value. Also see Section 1.5.3.¶

1.4.5. UTCDateTime

UTCDateTime is a string in date-time format [RFC3339], with further restrictions that any letters MUST be in uppercase and the time offset MUST be the character Z. Fractional second values MUST NOT be included unless they are non-zero, and they MUST NOT have trailing zeros to ensure there is only a single representation for each date-time.¶

For example, 2010-10-10T10:10:10.003Z is conformant, but 2010-10-10T10:10:10.000Z is invalid; the correct encoding is 2010-10-10T10:10:10Z.¶

1.5.1. contexts

Type: String[Boolean]¶

This property associates contact information with one or more contexts in which it should be used. For example, someone might have distinct phone numbers for work and private contexts and may set the desired context on the respective phone number in the phones (Section 2.3.3) property.¶

This section defines common contexts. Additional contexts may be defined in the properties or data types that make use of this property. The enumerated (Section 1.7.4) common context values are:¶

• private: the contact information that may be used in a private context.¶
• work: the contact information that may be used in a professional context.¶

1.5.2. extra

extra is a reserved property name. Implementations MUST NOT set this property in a JSContact object. Any JSContact object including a property with this name MUST be considered invalid.¶

The purpose of this reserved property name is to provide implementors with a name that 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.¶

1.5.3. label

Type: String¶

This property allows associating contact data with user-defined labels. Such labels may be set for phone numbers, email addresses, and resources. Typically, these labels are displayed along with their associated contact data in graphical user interfaces. Note that succinct labels are best for proper display on small graphical interfaces and screens.¶

1.5.4. pref

Type: UnsignedInt¶

This property allows defining a preference order for contact information. For example, a person may have two email addresses and prefer to be contacted with one of them.¶

Its value MUST be in the range of 1 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 MUST be interpreted as being least preferred.¶

Note that the preference 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.¶

1.5.5. phonetic

The phonetic property defines how to pronounce a value in the language indicated in the Card language (Section 2.1.5) property or the language tag of its localizations (Section 2.7.1). Exemplary uses of this property are defining how to pronounce Japanese names and romanizing Mandarin or Cantonese name and address components. The properties are defined as follows:¶

phonetic:

String. Contains the phonetic representation of a value. Any script language subtag in the Card language (Section 2.1.5) property MUST be ignored for use with the phonetic property. If this property is set, then at least one of the phoneticScript or phoneticSystem properties that relate to this value MUST be set.¶

phoneticScript:

String. The script used in the value of the related phonetic property. This MUST be a valid script subtag as defined in Section 2.2.3 of [RFC5646].¶

phoneticSystem:

String. The phonetic system used in the related value of the phonetic property. The enumerated (Section 1.7.4) values are:¶

• ipa: denotes the International Phonetic Alphabet [IPA].¶
• jyut: denotes the Cantonese romanization system "Jyutping".¶
• piny: denotes the Standard Mandarin romanization system "Hanyu Pinyin".¶

The relation between the phoneticSystem, phoneticScript, and phonetic properties is type-specific. This specification defines this relation in the Name (Section 2.2.1) and Address (Section 2.5.1) object types, respectively.¶

The following example illustrates the phonetic property for a name (Section 2.2.1):¶

"name": {
  "components": [{
    "kind": "given",
    "value": "John",
    "phonetic": "/ˈdʒɑːn/"
  }, {
    "kind": "surname",
    "value": "Smith",
    "phonetic": "/smɪθ/"
  }],
  "phoneticSystem": "ipa"
}

1.7.1. Case-Sensitivity

All property names, object type names, and enumerated values are case-sensitive, unless explicitly stated otherwise in their definitions. Implementations MUST handle a JSContact object as invalid if a type name, property 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 version (Section 2.1.2) property. Section 1.7.3 defines how to handle unknown properties.¶

1.7.2. IANA-Registered Properties

An IANA-registered property is any property that has been registered according to the IANA property registry rules as outlined in Section 3. All properties defined in this specification, including their object value types and enumerated values, are registered at IANA.¶

Implementations MUST validate IANA-registered properties in JSContact data, unless they are unknown to the implementation (Section 1.7.3). They MUST 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 version (Section 2.1.2) property.¶

IANA-registered property names MUST NOT contain US-ASCII control characters (U+0000 to U+001F, U+007F), the COLON (U+003A), or the QUOTATION MARK (U+0022). They 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. IANA-registered property names MUST be notated in lower camel case.¶

1.7.3. Unknown Properties

Implementations may encounter JSContact data where a property name is unknown to that implementation but the name adheres to the syntactic restrictions of IANA-registered property names. Implementations MUST make sure that such a name does not violate the case-sensitivity rules defined in Section 1.7.1. If the property name is valid, then implementations MUST NOT treat such properties as invalid. Instead, they MUST preserve them in the JSContact object.¶

Implementations that create or update JSContact data MUST only set IANA-registered properties or vendor-specific properties. Preserving properties that are unknown to the 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.¶

1.7.4. Enumerated Values

Several properties in this document restrict their allowed values to 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 "JSContact Enum Values" registry (Section 3.7). Implementations MUST only set IANA-registered or vendor-specific (Section 1.8.2) values for such properties.¶

1.8.1. Vendor-Specific Properties

Vendor-specific property names MUST start with a vendor-specific prefix followed by a name, as produced by the v-extension ABNF below. The prefix and name together form the property name. The vendor-specific prefix MUST 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 [RFC1034] [RFC1035]. The prefix ietf.org and its subdomain names are reserved for IETF specifications. The name MUST NOT contain the TILDE (U+007E) and SOLIDUS (U+002F) characters, as these require special escaping when encoding a JSON Pointer [RFC6901] for that property.¶

Vendor-specific properties MAY be set in any JSContact object. Implementations MUST preserve vendor-specific properties in JSContact data, irrespective if they know their use. They MUST NOT reject the property value as invalid, unless they are in control of the vendor-specific property as outlined in the above paragraph.¶

The ABNF rule v-extension formally defines valid vendor-specific property names. Note that the vendor prefix allows for more values than Internationalized Domain Names (IDNs) [RFC8499]; therefore, JSContact implementations can simply validate property names without implementing the full set of rules that apply to domain names.¶

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, Section 3.3

v-name = 1*(WSP / "!" / %x23-2e / %x30-7d / NON-ASCII)
  ; any characters except CTLs, DQUOTE, SOLIDUS, and TILDE

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, then the keys of such objects need not be named as vendor-specific properties, as illustrated in Figure 3:¶

"example.com:foo": "bar",
"example.com:foo2": {
  "bar": "baz"
}

1.8.2. Vendor-Specific Values

Some JSContact IANA-registered properties allow their values to be vendor-specific. One such example is the kind (Section 2.1.4) property, which enumerates its standard values but also allows for arbitrary vendor-specific values. Such vendor-specific values MUST be valid v-extension values as defined in Section 1.8.1. The example in Figure 4 illustrates this:¶

"kind": "example.com:baz"

Vendors are strongly encouraged to specify a new standard value once a vendor-specific one turns out to also be useful for other systems.¶

1.9.2. Current Version

This specification registers JSContact version value 1.0 (Table 1).¶

2.1.1. @type

Type: String (mandatory)¶

This MUST be Card, if set.¶

2.1.2. version

Type: String (mandatory)¶

This specifies the JSContact version used to define the Card. The value MUST be one of the IANA-registered JSContact Enum Values for the version property. Also see Section 1.9.2.¶

"version": "1.0"

2.1.3. created

Type: UTCDateTime (optional)¶

The date and time when the Card was created.¶

"created": "2022-09-30T14:35:10Z"

2.1.4. kind

Type: String (optional; default: individual)¶

The kind of the entity the Card represents.¶

The enumerated (Section 1.7.4) values are:¶

• individual: a single person¶
• group: a group of people or entities¶
• org: an organization¶
• location: a named location¶
• device: a device such as an appliance, a computer, or a network element¶
• application: a software application¶

"kind": "individual"

2.1.5. language

Type: String (optional)¶

This is the language tag, as defined in [RFC5646], that best describes the language used for text in the Card, optionally including additional information such as the script. Note that values MAY be localized in the localizations (Section 2.7.1) property.¶

"language": "de-AT"

2.1.6. members

Type: String[Boolean] (optional)¶

This identifies the set of Cards that are members of this group Card. Each key in the set is the uid property value of the member, and each boolean value MUST be true. If this property is set, then the value of the kind property MUST be group.¶

The opposite is not true. A group Card will usually contain the members property to specify the members of the group, but it is not required to. A group Card without the members property can be considered an abstract grouping or one whose members are known empirically (e.g., "IETF Participants").¶

"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
}

2.1.7. prodId

Type: String (optional)¶

The identifier for the product that created the Card. If set, the value MUST be at least one character long.¶

"prodId": "ACME Contacts App version 1.23.5"

2.1.8. relatedTo

Type: String[Relation] (optional)¶

This relates the object to other Cards. It is represented as a map, where each key is the uid of the related Card, and the value defines the relation. The Relation object has the following properties:¶

@type:

String. This MUST be Relation, if set.¶

relation:

String[Boolean] (optional; default: empty Object). Describes how the linked object is related to the linking object. The relation is defined as a set of relation types. The key in the set defines the relation type; the value for each key in the set MUST be true. The relationship between the two objects is undefined if the set is empty.¶

The initial list of enumerated (Section 1.7.4) relation types matches the IANA-registered TYPE [IANA-vCard] parameter values of the vCard RELATED property (Section 6.6.6 of [RFC6350]):¶

• acquaintance¶
• agent¶
• child¶
• co-resident¶
• co-worker¶
• colleague¶
• contact¶
• crush¶
• date¶
• emergency¶
• friend¶
• kin¶
• me¶
• met¶
• muse¶
• neighbor¶
• parent¶
• sibling¶
• spouse¶
• sweetheart¶

"relatedTo": {
  "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6": {
    "relation": {
      "friend": true
    }
  },
  "8cacdfb7d1ffdb59@example.com": {
    "relation": {}
  }
}

2.1.9. uid

Type: String (mandatory)¶

An identifier that is used to associate the object as the same across different systems, address books, and views. The value SHOULD be a URN [RFC8141], but for compatibility with [RFC6350], it MAY also be a URI [RFC3986] or free-text value. The value of the URN SHOULD be in the uuid namespace [RFC4122]. 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 to generate global unique identifiers. Implementors SHOULD follow any recommendations described there. Until then, implementations SHOULD generate identifiers using the random or pseudorandom UUID version described in Section 4.4 of [RFC4122].¶

"uid": "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"

2.1.10. updated

Type: UTCDateTime (optional)¶

The date and time when the data in the Card was last modified.¶

"updated": "2021-10-31T22:27:10Z"

2.2.1. name

Type: Name (optional)¶

The name of the entity represented by the Card. This can be any type of name, e.g., it can, but need not, be the legal name of a person.¶

"name": {
  "components": [
    { "kind": "given", "value": "Robert" },
    { "kind": "given2", "value": "Pau" },
    { "kind": "surname", "value": "Shou Chang" }
  ],
  "sortAs": {
    "surname": "Pau Shou Chang",
    "given": "Robert"
  },
  "isOrdered": true
}

{
  "@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"
    }
  }
}

"nicknames": {
  "k391": {
    "name": "Johnny"
  }
}

2.2.2. organizations

Type: Id[Organization] (optional)¶

The company or organization names and units associated with the Card. An Organization object has the following properties, of which at least one of the name and units properties MUST be set:¶

@type:

String. This MUST be Organization, if set.¶

name:

String (optional). The name of the organization.¶

units:

OrgUnit[] (optional). 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 MUST contain at least one entry.¶

sortAs:

String (optional). Defines how the organization name lexicographically sorts in relation to other organizations when compared by the name. The value defines the verbatim string value to compare. In absence of this property, the name property value MAY be used for comparison.¶

contexts:

String[Boolean] (optional). The contexts in which association with the organization apply. For example, membership in a choir may only apply in a private context. Also see Section 1.5.1.¶

An OrgUnit object has the following properties:¶

@type:

String. This MUST be OrgUnit, if set.¶

name:

String (mandatory). The name of the organizational unit.¶

sortAs:

String (optional). Defines how the organization unit name lexicographically sorts in relation to other organizational units of the same level when compared by the name. The level is defined by the array index of the organizational unit in the units property of the Organization object. The property value defines the verbatim string value to compare. In absence of this property, the name property value MAY be used for comparison.¶

"organizations": {
  "o1": {
    "name": "ABC, Inc.",
    "units": [
      { "name": "North American Division" },
      { "name": "Marketing" }
    ],
    "sortAs": "ABC"
  }
}

2.2.3. speakToAs

Type: SpeakToAs (optional)¶

Provides information on how to address, speak to, or refer to the entity that is represented by the Card. A SpeakToAs object has the following properties, of which at least one of the grammaticalGender and pronouns properties MUST be set:¶

@type:

String. This MUST be SpeakToAs, if set.¶

grammaticalGender:

String (optional). Defines which 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 enumerated (Section 1.7.4) values are:¶

• animate¶
• common¶
• feminine¶
• inanimate¶
• masculine¶
• neuter¶

Note that the grammatical gender does not allow inferring the gender identities or assigned sex of the contact.¶

pronouns:

Id[Pronouns] (optional). Defines the pronouns that the contact chooses to use for themselves.¶

A Pronouns object has the following properties:¶

@type:

String. This MUST be Pronouns, if set.¶

pronouns:

String (mandatory). Defines the pronouns. Any value or form is allowed. Examples in English include she/her and they/them/theirs. The value MAY be overridden in the localizations (Section 2.7.1) property.¶

contexts:

String[Boolean] (optional). The contexts in which to use the pronouns. Also see Section 1.5.1.¶

pref:

UnsignedInt (optional). The preference of the pronouns in relation to other pronouns in the same context. Also see Section 1.5.4.¶

"speakToAs": {
  "grammaticalGender": "neuter",
  "pronouns": {
    "k19": {
      "pronouns": "they/them",
      "pref": 2
    },
    "k32": {
      "pronouns": "xe/xir",
      "pref": 1
    }
  }
}

2.2.4. titles

Type: Id[Title] (optional)¶

The job titles or functional positions of the entity represented by the Card. A Title object has the following properties:¶

@type:

String. This MUST be Title, if set.¶

name:

String (mandatory). The title or role name of the entity represented by the Card.¶

kind:

String (optional; default: title). Describes the organizational or situational kind of the title. Some organizations and individuals distinguish between titles as organizational positions and roles as more temporary assignments such as in project management.¶

The enumerated (Section 1.7.4) values are:¶

• title¶
• role¶

organizationId:

Id (optional). The identifier of the organization in which this title is held.¶

"titles": {
  "le9": {
    "kind": "title",
    "name": "Research Scientist"
  },
  "k2": {
    "kind": "role",
    "name": "Project Leader",
    "organizationId": "o2"
  }
},
"organizations": {
  "o2": {
    "name": "ABC, Inc."
  }
}

2.3.1. emails

Type: Id[EmailAddress] (optional)¶

The email addresses in which to contact the entity represented by the Card. An EmailAddress object has the following properties:¶

@type:

String. This MUST be EmailAddress, if set.¶

address:

String (mandatory). The email address. This MUST be an addr-spec value as defined in Section 3.4.1 of [RFC5322].¶

contexts:

String[Boolean] (optional). The contexts in which to use this email address. Also see Section 1.5.1.¶

pref:

UnsignedInt (optional). The preference of the email address in relation to other email addresses. Also see Section 1.5.4.¶

label:

String (optional). A custom label for the value. Also see Section 1.5.3.¶

"emails": {
  "e1": {
    "contexts": {
      "work": true
    },
    "address": "jqpublic@xyz.example.com"
  },
  "e2": {
    "address": "jane_doe@example.com",
    "pref": 1
  }
}

2.3.2. onlineServices

Type: Id[OnlineService] (optional)¶

The online services that are associated with the entity represented by the Card. This can be messaging services, social media profiles, and other. An OnlineService object has the following properties, of which at least the uri or user property MUST be set:¶

@type:

String. This MUST be OnlineService, if set.¶

service:

String (optional). The name of the online service or protocol. The name MAY be capitalized the same as on the service's website, app, or publishing material, but names MUST be considered equal if they match case-insensitively. Examples are GitHub, Kakao, and Mastodon.¶

uri:

String (optional). Identifies the entity represented by the Card at the online service. This MUST be a URI as defined in Section 3 of [RFC3986].¶

user:

String (optional). Names the entity represented by the Card at the online service. Any free-text value is allowed. The service property SHOULD be set.¶

contexts:

String[Boolean] (optional). The contexts in which to use the service. Also see Section 1.5.1.¶

pref:

UnsignedInt (optional). The preference of the service in relation to other services. Also see Section 1.5.4.¶

label:

String (optional). A custom label for the value. Also see Section 1.5.3.¶

"onlineServices": {
  "x1": {
    "uri": "xmpp:alice@example.com"
  },
  "x2": {
    "service": "Mastodon",
    "user": "@alice@example2.com",
    "uri": "https://example2.com/@alice"
  }
}

2.3.3. phones

Type: Id[Phone] (optional)¶

The phone numbers in which to contact the entity represented by the Card. A Phone object has the following properties:¶

@type:

String. This MUST be Phone, if set.¶

number:

String (mandatory). The phone number as either a URI or free text. Typical URI schemes are tel [RFC3966] or sip [RFC3261], but any URI scheme is allowed.¶

features:

String[Boolean] (optional). The set of contact features that the phone number may be used for. The set is represented as an object, with each key being a method type. The boolean value MUST be true. The enumerated (Section 1.7.4) method type values are:¶

• mobile: the number for a mobile phone.¶
• voice: the number for calling by voice.¶
• text: the number that supports text messages (SMS).¶
• video: the number that supports video conferencing.¶
• main-number: the main phone number such as the number of the front desk at a company, as opposed to a direct-dial number of an individual employee.¶
• textphone: the number is for a device for people with hearing or speech difficulties.¶
• fax: the number for sending faxes.¶
• pager: the number for a pager or beeper.¶

contexts:

String[Boolean] (optional). The contexts in which to use the number. Also see Section 1.5.1.¶

pref:

UnsignedInt (optional). The preference of the number in relation to other numbers. Also see Section 1.5.4.¶

label:

String (optional). A custom label for the value. Also see Section 1.5.3.¶

"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"
  }
}

2.3.4. preferredLanguages

Type : Id[LanguagePref] (optional)¶

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

A LanguagePref object has the following properties:¶

@type:

String. This MUST be LanguagePref, if set.¶

language:

String (mandatory). The preferred language. This MUST be a language tag as defined in [RFC5646].¶

contexts:

String[Boolean] (optional). Defines the contexts in which to use the language. Also see Section 1.5.1.¶

pref:

UnsignedInt (optional). Defines the preference of the language in relation to other languages of the same contexts. Also see Section 1.5.4.¶

"preferredLanguages": {
  "l1": {
    "language": "en",
    "contexts": {
      "work": true
    },
    "pref": 1
  },
  "l2": {
    "language": "fr",
    "contexts": {
      "work": true
    },
    "pref": 2
  },
  "l3": {
    "language": "fr",
    "contexts": {
      "private": true
    }
  }
}

2.4.1. calendars

Type: Id[Calendar] (optional)¶

These are resources for calendaring such as using calendars to look up free-busy information for the entity represented by the Card. A Calendar object has all properties of the Resource (Section 1.4.4) data type, with the following additional definitions:¶

• The @type property value MUST be Calendar, if set.¶

• The kind property is mandatory. Its enumerated (Section 1.7.4) values are:¶

  • calendar: The resource is a calendar that contains entries such as calendar events or tasks.¶
  • freeBusy: The resource allows for free-busy lookups, for example, to schedule group events.¶

"calendars": {
  "calA": {
    "kind": "calendar",
    "uri": "webcal://calendar.example.com/calA.ics"
  },
  "project-a": {
    "kind": "freeBusy",
    "uri": "https://calendar.example.com/busy/project-a"
  }
}

2.4.2. schedulingAddresses

Type: Id[SchedulingAddress] (optional)¶

The scheduling addresses by which the entity may receive calendar scheduling invitations. A SchedulingAddress object has the following properties:¶

@type:

String. This MUST be SchedulingAddress, if set.¶

uri:

String (mandatory). The address to use for calendar scheduling with the contact. This MUST be a URI as defined in Section 3 of [RFC3986].¶

contexts:

String[Boolean] (optional). The contexts in which to use the scheduling address. Also see Section 1.5.1.¶

pref:

UnsignedInt (optional). The preference of the scheduling address in relation to other scheduling addresses. Also see Section 1.5.4.¶

label:

String (optional). A custom label for the scheduling address. Also see Section 1.5.3.¶

"schedulingAddresses": {
  "sched1": {
    "uri": "mailto:janedoe@example.com"
  }
}

2.5.1. addresses

Type: Id[Address] (optional)¶

A map of address identifiers to Address objects, containing physical locations.¶

"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
  }
}

"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
  }
}

"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
    }
  }
}

2.6.1. cryptoKeys

Type: Id[CryptoKey] (optional)¶

These are cryptographic resources such as public keys and certificates associated with the entity represented by the Card. A CryptoKey object has all properties of the Resource (Section 1.4.4) data type, with the following additional definition:¶

• The @type property value MUST be CryptoKey, if set.¶

The following example shows how to refer to an external cryptographic resource.¶

"cryptoKeys": {
  "mykey1": {
    "uri": "https://www.example.com/keys/jdoe.cer"
  }
}

The following example shows how to embed key data in the CryptoKey. The key data is depicted in multiple lines only for demonstration purposes.¶

"cryptoKeys": {
  "mykey2": {
    "uri": "data:application/pgp-keys;base64,LS0tLS1CRUdJTiBSU0EgUFVC
            TElDIEtFWS0tLS0tCk1JSUJDZ0tDQVFFQSt4R1ovd2N6OXVnRnBQMDdOc
            3BvNlUxN2wwWWhGaUZweHhVNHBUazNMaWZ6OVIzenNJc3UKRVJ3dGE3K2
            ZXSWZ4T28yMDhldHQvamhza2lWb2RTRXQzUUJHaDRYQmlweVdvcEt3Wjk
            zSEhhRFZaQUFMaS8yQQoreFRCdFdkRW83WEdVdWpLRHZDMi9hWkt1a2Zq
            cE9pVUk4QWhMQWZqbWxjRC9VWjFRUGgwbUhzZ2xSTkNtcEN3Cm13U1hBO
            VZObWh6K1BpQitEbWw0V1duS1cvVkhvMnVqVFh4cTcrZWZNVTRIMmZueT
            NTZTNLWU9zRlBGR1oxVE4KUVNZbEZ1U2hXckhQdGlMbVVkUG9QNkNWMm1
            NTDF0aytsN0RJSXFYclFoTFVLREFDZU01cm9NeDBrTGhVV0I4UAorMHVq
            MUNObE5ONEpSWmxDN3hGZnFpTWJGUlU5WjRONll3SURBUUFCCi0tLS0tR
            U5EIFJTQSBQVUJMSUMgS0VZLS0tLS0K"
  }
}

2.6.2. directories

Type: Id[Directory] (optional)¶

These are directory service resources such as entries in a directory or organizational directories for lookup. A Directory object has all properties of the Resource (Section 1.4.4) data type, with the following additional definitions:¶

• The @type property value MUST be Directory, if set.¶

• The kind property is mandatory. Its enumerated (Section 1.7.4) values are:¶

  • directory: the resource is a directory service that the entity represented by 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.¶
  • entry: the resource is a directory entry of the entity represented by the Card. In contrast to the directory type, this is the specific URI for the entity within a directory.¶

In addition, the Directory object has the following property:¶

listAs:

UnsignedInt (optional). Defines the position of the directory resource in the list of all Directory objects having the same kind in the Card. If set, the listAs value MUST be higher than zero. Multiple directory resources MAY have the same listAs property value or none. Sorting such entries is implementation-specific.¶

"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
  }

2.6.3. links

Type: Id[Link] (optional)¶

These are links to resources that do not fit any of the other use-case-specific resource properties. A Link object has all properties of the Resource (Section 1.4.4) data type, with the following additional definitions:¶

• The @type property value MUST be Link, if set.¶

• The kind property is optional. Its enumerated (Section 1.7.4) values are:¶

  • contact: the resource is a URI by which the entity represented by the Card may be contacted; this includes web forms or other media that require user interaction.¶

"links": {
  "link3": {
    "kind": "contact",
    "uri": "mailto:contact@example.com",
    "pref": 1
  }
}

2.6.4. media

Type: Id[Media] (optional)¶

These are media resources such as photographs, avatars, or sounds that are associated with the entity represented by the Card. A Media object has all properties of the Resource (Section 1.4.4) data type, with the following additional definitions:¶

• The @type property value MUST be Media, if set.¶

• The kind property is mandatory. Its enumerated (Section 1.7.4) values are:¶

  • photo: the resource is a photograph or avatar.¶
  • sound: the resource is audio media, e.g., to specify the proper pronunciation of the name property contents.¶
  • logo: the resource is a graphic image or logo associated with the entity represented by the Card.¶

"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..."
  }
}

2.7.1. localizations

Type: String[PatchObject] (optional)¶

This localizes property values to languages (other than the main language) in the Card. Localizations provide language-specific alternatives for existing property values and SHOULD NOT add new properties.¶

The keys in the localizations property object are language tags [RFC5646]. The values are patch objects that localize the Card in the respective language tag. The paths in the PatchObject are relative to the Card that includes the localizations property. A patch MUST NOT target the localizations property.¶

Conceptually, a Card is localized as follows:¶

• Determine the language tag in which the Card should be localized.¶
• If the localizations property includes a key for that language, obtain the PatchObject value. If there is no such key, stop.¶
• Create a copy of the Card, but do not copy the localizations property.¶
• Apply all patches in the PatchObject to the copy of the Card.¶
• Optionally, set the language property in the copy of the Card.¶
• Use the patched copy of the Card as the localized variant of the original Card.¶

A patch in the PatchObject may contain any value type. Its value MUST be a valid value according to the definition of the patched property.¶

Figure 39 localizes the name property by completely replacing its contents in Ukrainian language with Cyrillic script.¶

{
  "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": "Васильев" }
        ]
      }
    }
  }
}

Figure 40 localizes the title name by patching inside the titles property. All properties, except the name property in the Title object, are left as is.¶

"name": {
  "full": "Gabriel García Márquez"
},
"titles": {
  "t1": {
    "kind": "title",
    "name": "novelist"
  }
},
"localizations": {
  "es": {
    "titles/t1/name": "autor"
  }
}

2.8.1. anniversaries

Type: Id[Anniversary] (optional)¶

These are memorable dates and events for the entity represented by the Card. An Anniversary object has the following properties:¶

@type:

String. This MUST be Anniversary, if set.¶

kind:

String (mandatory). Specifies the kind of anniversary. The enumerated (Section 1.7.4) values are:¶

• birth: a birthday anniversary¶
• death: a deathday anniversary¶
• wedding: a wedding day anniversary¶

date:

PartialDate|Timestamp (mandatory; defaultType: PartialDate). The date of the anniversary in the Gregorian calendar. This MUST be either a whole or partial calendar date or a complete UTC timestamp (see the definition of the Timestamp and PartialDate object types below).¶

place:

Address (optional). An address associated with this anniversary, e.g., the place of birth or death.¶

A PartialDate object represents a complete or partial calendar date in the Gregorian calendar. It represents a complete date, a year, a month in a year, or a day in a month. It has the following properties, of which at least year or month and day MUST be set:¶

@type:

String. This MUST be PartialDate, if set.¶

year:

UnsignedInt (optional). The calendar year.¶

month:

UnsignedInt (optional). The calendar month, represented as the integers 1 <= month <= 12. If this property is set, then either year or day MUST be set.¶

day:

UnsignedInt (optional). The calendar month day, represented as the integers 1 <= day <= 31, depending on the validity within the month and year. If this property is set, then month MUST be set.¶

calendarScale:

String (optional). The calendar system in which this date occurs, in lowercase. This MUST be either a calendar system name registered as a Common Locale Data Repository (CLDR) [RFC7529] or a vendor-specific value. The year, month, and day still MUST be represented in the Gregorian calendar. Note that the year property might be required to convert the date between the Gregorian calendar and the respective calendar system.¶

A Timestamp object has the following properties:¶

@type:

String. This MUST be Timestamp, if set.¶

utc:

UTCDateTime (mandatory). Specifies the point in time in UTC time.¶

Figure 41 illustrates anniversaries with partial dates and a timestamp. Note how the @type property is set for the Timestamp object value according to the rules defined in Section 1.3.4.¶

"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"
    }
  }
}

2.8.2. keywords

Type: String[Boolean] (optional)¶

A set of free-text keywords, also known as tags. The set is represented as an object, with each key being a keyword. The boolean value MUST be true.¶

"keywords": {
  "internet": true,
  "IETF": true
}

2.8.3. notes

Type: Id[Note] (optional)¶

Free-text notes that are associated with the Card. A Note object has the following properties:¶

@type:

String. This MUST be Note, if set.¶

note:

String (mandatory). The free-text value of this note.¶

created:

UTCDateTime (optional). The date and time when this note was created.¶

author:

Author (optional). The author of this note.¶

An Author object has the following properties, of which at least one property other than @type MUST be set:¶

@type:

String. This MUST be Author, if set.¶

name:

String (optional). The name of this author.¶

uri:

String (optional). A URI value that identifies the author.¶

"notes": {
  "n1": {
    "note": "Open office hours are 1600 to 1715 EST, Mon-Fri",
    "created": "2022-11-23T15:01:32Z",
    "author": {
      "name": "John"
    }
  }
}

2.8.4. personalInfo

Type: Id[PersonalInfo] (optional)¶

Defines personal information about the entity represented by the Card. A PersonalInfo object has the following properties:¶

@type:

String. This MUST be PersonalInfo, if set.¶

kind:

String (mandatory). Specifies the kind of personal information. The enumerated (Section 1.7.4) values are:¶

• expertise: a field of expertise or a credential¶
• hobby: a hobby¶
• interest: an interest¶

value:

String (mandatory). The actual information.¶

level:

String (optional). Indicates the level of expertise or engagement in hobby or interest. The enumerated (Section 1.7.4) values are:¶

• high¶
• medium¶
• low¶

listAs:

UnsignedInt (optional). Defines the position of the personal information in the list of all PersonalInfo objects that have the same kind in the Card. If set, the listAs value MUST be higher than zero. Multiple personal information entries MAY have the same listAs property value or none. Sorting such entries is implementation-specific.¶

label:

String (optional). A custom label. See Section 1.5.3.¶

"personalInfo": {
  "pi2": {
    "kind": "expertise",
    "value": "chemistry",
    "level": "high"
  },
  "pi1": {
    "kind": "hobby",
    "value": "reading",
    "level": "high"
  },
  "pi6": {
    "kind": "interest",
    "value": "r&b music",
    "level": "medium"
  }
}

3.3.1. Preliminary Community Review

Notice of a potential new registration MUST be sent to the Calext WG mailing list <calsify@ietf.org> for review. This mailing list is appropriate for soliciting community feedback on a proposed registry assignment.¶

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.¶

3.3.2. Submit Request to IANA

Registration requests can be sent to IANA <iana@iana.org>.¶

3.3.3. Designated Expert Review

The primary concern of the DE is preventing name collisions and encouraging the submitter to document security and privacy considerations.¶

A new type name, property name, or enumerated value MUST NOT differ only in case from an already-registered name or value.¶

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.¶

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 in the cases where it is possible, concrete suggestions on how the request can be modified to become acceptable should be provided.¶

3.3.4. Change Procedures

Once a JSContact registry group item has been published by IANA, the 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.¶

JSContact registrations do not get deleted; instead, items that are no longer believed appropriate for use are declared obsolete by a change to their "Intended Usage" field; such items will be clearly marked in the IANA registry.¶

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.¶

3.4.1. JSContact Version Registry Template

Major Version:

The numeric value of a JSContact major version number. It MUST be a positive integer.¶

Highest Minor Version:

The maximum numeric value of a JSContact minor version for the given major version. It MUST 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.¶

3.4.2. Initial Contents of the JSContact Version Registry

The following table lists the initial valid major and minor version number ranges.¶

3.5.1. JSContact Properties Registry Template

Property Name:

The name of the property. The property name MUST NOT already be registered for any of the object types listed in the "Property Context" field of this registration. Other object types MAY have already registered a different property with the same name; however, the same name MUST only be used when the semantics are analogous.¶

Property Type:

For properties with intended usage other than "reserved", this is the type of this property, using type signatures as specified in Section 1.3.2. The property type MUST be registered in the "JSContact Types" registry. For reserved property names, the value MUST be the verbatim string "not applicable".¶

Property Context:

A comma-separated list of JSContact object types (Section 3.6.2) that contain the property. For reserved property names, the value MAY be the verbatim string "not applicable".¶

Intended Usage:

May be "common", "reserved", or "obsolete".¶

Since Version:

The JSContact version on which the property definition is based. The version MUST be one of the allowed values of the version property in the "JSContact Enum Values" registry (see Table 1).¶

Until Version:

The JSContact version after which the property was obsoleted; therefore, it MUST NOT be used in later versions. 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).¶

Change Controller:

This is who may request a change to the entry's definition (IETF for RFCs from the IETF stream).¶

Reference or Description:

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 MAY be omitted.¶

3.5.2. Initial Contents of the JSContact Properties Registry

The following table lists the initial common usage entries of the "JSContact Properties" registry. For all properties, the Since Version is 1.0, the Until Version is not set, the Change Controller is IETF, and RFC section references are for RFC 9553.¶

The following table lists the initial reserved usage entries of the "JSContact Properties" registry. For this property, the Change Controller is IETF, and the RFC section reference is for RFC 9553.¶

3.6.1. JSContact Types Registry Template

Type Name:

The name of the type.¶

Intended Usage:

May be "common", "reserved", or "obsolete".¶

Since Version:

The JSContact version on which this type definition is based. The version MUST be one of the allowed values of the version property in the "JSContact Enum Values" registry (see Table 1).¶

Until Version:

The JSContact version after which the type definition was obsoleted; therefore, it MUST NOT be used in later versions. 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).¶

Change Controller:

This is who may request a change to the entry's definition (IETF for RFCs from the IETF stream).¶

Reference or Description:

A brief description or RFC number and section reference where the Type is specified. For reserved type names, the reference or description MAY be omitted.¶

3.6.2. Initial Contents of the JSContact Types Registry

The following table lists the initial common usage entries in the "JSContact Types" registry. For all of these types, the Since Version is 1.0, the Until Version is not set, the Change Controller is IETF, and RFC section references are for RFC 9553.¶

The following table lists the initial reserved usage entry of the "JSContact Types" registry. For this type, the version is 1.0, the Change Controller is IETF, and the RFC section reference is for RFC 9553.¶

3.7.1. JSContact Enum Values Registry Property Template

This template is for adding a subregistry for a new enumerable property to the "JSContact Enum Values" registry.¶

Property Name:

The name(s) of the property or properties where these values may be used. This MUST be registered in the "JSContact Properties" registry.¶

Context:

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.¶

Since Version:

The JSContact version on which the enum value definition is based. The version MUST be one of the allowed values of the version property in the "JSContact Enum Values" registry (see Table 1).¶

Until Version:

The JSContact version after which the enum value definition was obsoleted; therefore, the enum value definition MUST NOT be used in later versions. 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).¶

Change Controller:

This is who may request a change to the entry's definition (IETF for RFCs from the IETF stream).¶

Initial Contents:

The initial list of defined values for the enum, using the template defined in Section 3.7.2. A subregistry will be created with these values for this property name/context tuple.¶

3.7.2. JSContact Enum Values Registry Value Template

This template is for adding a new enum value to a subregistry in the "JSContact Enum Values" registry.¶

Enum Value:

The verbatim value of the enum.¶

Since Version:

The JSContact version on which the enum value definition is based. The version MUST be one of the allowed values of the version property in the "JSContact Enum Values" registry (see Table 1).¶

Until Version:

The JSContact version after which the enum value was obsoleted; therefore, the enum value MUST NOT be used in later versions. 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).¶

Reference or Description:

A brief description or RFC number and section reference for the semantics of the value.¶

3.7.3. Initial Contents of the JSContact Enum Values Registry

For all entries in each subregistry created in this section, the Since Version is 1.0, the Until Version is not set, the Change Controller is IETF, and RFC section references are for RFC 9553.¶

Property Name:

contexts¶

Context:

Address¶

Initial Contents:

Table 6: JSContact Enum Values for contexts (Context: Address)

Enum Value	Reference or Description
billing	Section 2.5.1
delivery	Section 2.5.1
private	Section 1.5.1
work	Section 1.5.1

¶

Property Name:

contexts¶

Context:

Calendar, CryptoKey, Directory, EmailAddress, LanguagePref, Link, Media, Nickname, OnlineService, Organization, Phone, Pronouns, SchedulingAddress¶

Initial Contents:

Table 7: JSContact Enum Values for contexts (Context: Calendar, CryptoKey, Directory, EmailAddress, LanguagePref, Link, Media, Nickname, OnlineService, Organization, Phone, Pronouns, SchedulingAddress)

Enum Value	Reference or Description
private	Section 1.5.1
work	Section 1.5.1

¶

Property Name:

features¶

Context:

Phone¶

Initial Contents:

Table 8: JSContact Enum Values for features (Context: Phone)

Enum Value	Reference or Description
fax	Section 2.3.3
main-number	Section 2.3.3
mobile	Section 2.3.3
pager	Section 2.3.3
text	Section 2.3.3
textphone	Section 2.3.3
video	Section 2.3.3
voice	Section 2.3.3

¶

Property Name:

grammaticalGender¶

Context:

SpeakToAs¶

Initial Contents:

Table 9: JSContact Enum Values for grammaticalGender (Context: SpeakToAs)

Enum Value	Reference or Description
animate	Section 2.2.3
common	Section 2.2.3
feminine	Section 2.2.3
inanimate	Section 2.2.3
masculine	Section 2.2.3
neuter	Section 2.2.3

¶

Property Name:

kind¶

Context:

AddressComponent¶

Initial Contents:

Table 10: JSContact Enum Values for kind (Context: AddressComponent)

Enum Value	Reference or Description
apartment	Section 2.5.1
block	Section 2.5.1
building	Section 2.5.1
country	Section 2.5.1
direction	Section 2.5.1
district	Section 2.5.1
floor	Section 2.5.1
landmark	Section 2.5.1
locality	Section 2.5.1
name	Section 2.5.1
number	Section 2.5.1
postcode	Section 2.5.1
postOfficeBox	Section 2.5.1
region	Section 2.5.1
room	Section 2.5.1
separator	Section 2.5.1
subdistrict	Section 2.5.1

¶

Property Name:

kind¶

Context:

Anniversary¶

Initial Contents:

Table 11: JSContact Enum Values for kind (Context: Anniversary)

Enum Value	Reference or Description
birth	Section 2.8.1
death	Section 2.8.1
wedding	Section 2.8.1

¶

Property Name:

kind¶

Context:

Calendar¶

Initial Contents:

Table 12: JSContact Enum Values for kind (Context: Calendar)

Enum Value	Reference or Description
calendar	Section 2.4.1
freeBusy	Section 2.4.1

¶

Property Name:

kind¶

Context:

Card¶

Initial Contents:

Table 13: JSContact Enum Values for kind (Context: Card)

Enum Value	Reference or Description
application	Section 2.1.4
device	Section 2.1.4
group	Section 2.1.4
individual	Section 2.1.4
location	Section 2.1.4
org	Section 2.1.4

¶

Property Name:

kind¶

Context:

Directory¶

Initial Contents:

Table 14: JSContact Enum Values for kind (Context: Directory)

Enum Value	Reference or Description
directory	Section 2.6.2
entry	Section 2.6.2

¶

Property Name:

kind¶

Context:

Link¶

Initial Contents:

Table 15: JSContact Enum Values for kind (Context: Link)

Enum Value	Reference or Description
contact	Section 2.6.3

¶

Property Name:

kind¶

Context:

Media¶

Initial Contents:

Table 16: JSContact Enum Values for kind (Context: Media)

Enum Value	Reference or Description
logo	Section 2.6.4
photo	Section 2.6.4
sound	Section 2.6.4

¶

Property Name:

kind¶

Context:

NameComponent¶

Initial Contents:

Table 17: JSContact Enum Values for kind (Context: NameComponent)

Enum Value	Reference or Description
credential	Section 2.2.1
generation	Section 2.2.1
given	Section 2.2.1
given2	Section 2.2.1
separator	Section 2.2.1
surname	Section 2.2.1
surname2	Section 2.2.1
title	Section 2.2.1

¶

Property Name:

kind¶

Context:

PersonalInfo¶

Initial Contents:

Table 18: JSContact Enum Values for kind (Context: PersonalInfo)

Enum Value	Reference or Description
expertise	Section 2.8.4
hobby	Section 2.8.4
interest	Section 2.8.4

¶

Property Name:

kind¶

Context:

Title¶

Initial Contents:

Table 19: JSContact Enum Values for kind (Context: Title)

Enum Value	Reference or Description
role	Section 2.2.4
title	Section 2.2.4

¶

Property Name:

level¶

Context:

PersonalInfo¶

Initial Contents:

Table 20: JSContact Enum Values for level (Context: PersonalInfo)

Enum Value	Reference or Description
high	Section 2.8.4
low	Section 2.8.4
medium	Section 2.8.4

¶

Property Name:

phoneticSystem¶

Context:

Address, Name¶

Initial Contents:

Table 21: JSContact Enum Values for phoneticSystem (Context: Address, Name)

Enum Value	Reference or Description
ipa	Section 1.5.5
jyut	Section 1.5.5
piny	Section 1.5.5

¶

Property Name:

relation¶

Context:

Relation¶

Initial Contents:

Table 22: JSContact Enum Values for relation (Context: Relation)

Enum Value	Reference or Description
acquaintance	Section 2.1.8
agent	Section 2.1.8
child	Section 2.1.8
colleague	Section 2.1.8
contact	Section 2.1.8
co-resident	Section 2.1.8
co-worker	Section 2.1.8
crush	Section 2.1.8
date	Section 2.1.8
emergency	Section 2.1.8
friend	Section 2.1.8
kin	Section 2.1.8
me	Section 2.1.8
met	Section 2.1.8
muse	Section 2.1.8
neighbor	Section 2.1.8
parent	Section 2.1.8
sibling	Section 2.1.8
spouse	Section 2.1.8
sweetheart	Section 2.1.8

¶