rfc-6715

vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group

D. Cauchie, B. Leiba, K. Li
date2012-08 streamIETF areaapp wgvcarddav statusPROPOSED STANDARD pages11 canonicalhttps://www.rfc-editor.org/rfc/rfc6715 doi10.17487/RFC6715 errataview
This document defines extensions to the vCard data format for representing and exchanging certain contact information. The properties covered here have been defined by the Open Mobile Alliance (OMA) Converged Address Book group, in order to synchronize, using OMA Data Synchronization, contact fields that were not already defined in the base vCard 4.0 specification. [STANDARDS-TRACK]

Extracted elements (21)

design-rationale §2.4

ORG-DIRECTORY carries a URI whose lookup mechanism is intentionally unspecified; the behavior depends on the URI scheme and the URI may or may not support automated lookup.

design-rationale §2

String-value properties such as EXPERTISE, HOBBY, and INTEREST intentionally have no fixed list of allowed strings; de facto taxonomies are expected to emerge through usage rather than specification, as these values are meant to be understood by humans rather than used for automated categorization.

design-rationale §2.2

The HOBBY and INTEREST properties are distinct: a hobby is an activity one actively engages in, while an interest is a topic one finds interesting but does not necessarily participate in. This semantic distinction is made explicit to aid correct usage.

interoperability-note §1

These vCard property extensions were defined to enable synchronization via OMA Data Synchronization (OMA-DS) of contact fields not covered by the base vCard 4.0 specification (RFC 6350). Implementations must conform to the base vCard specification for parsing and serialization.

normative-requirement §3.1 MUST

INDEX values must be strictly positive. Zero is not allowed as an INDEX value.

protocol-element §2.1

The EXPERTISE property specifies a field of expertise for the vCard subject. It accepts a single text value, supports cardinality *, and takes optional LEVEL (beginner/average/expert) and INDEX parameters.

protocol-element §2.2

The HOBBY property specifies hobbies of the vCard subject. It accepts a single text value, supports cardinality *, and takes optional LEVEL (high/medium/low) and INDEX parameters. A hobby is an activity one actively engages in, as distinct from an INTEREST.

protocol-element §3.1

The INDEX parameter indicates the position of a value within a multi-valued property. INDEX values must be strictly positive integers; zero is not allowed.

protocol-element §2.3

The INTEREST property specifies interests of the vCard subject. It accepts a single text value, supports cardinality *, and takes optional LEVEL (high/medium/low) and INDEX parameters. An interest is a topic one finds interesting but does not necessarily actively pursue, distinguishing it from HOBBY.

protocol-element §3.2

The LEVEL parameter indicates a level of expertise, hobby engagement, or interest. Allowed values are 'beginner', 'average', 'expert' for EXPERTISE, and 'high', 'medium', 'low' for HOBBY and INTEREST.

protocol-element §2.4

The ORG-DIRECTORY property specifies a URI pointing to an organizational directory to which the vCard's entity belongs. It accepts a single URI value, supports cardinality *, and takes optional PREF and INDEX parameters.

registry §5

IANA has added EXPERTISE, HOBBY, INTEREST, and ORG-URI (ORG-DIRECTORY) to the 'vCard Properties' registry defined in RFC 6350 Section 10.3.1.

registry

registry §5

IANA has added INDEX and LEVEL to the 'vCard Parameters' registry defined in RFC 6350 Section 10.3.2.

registry

registry §5

IANA has added nine entries to the 'vCard Parameter Values' registry: beginner/average/expert for EXPERTISE LEVEL, and high/medium/low each for HOBBY LEVEL and INTEREST LEVEL, as defined in RFC 6350 Section 10.3.4.

registry

security-consideration §4

This document presents no security considerations beyond those in Section 9 of the base vCard specification (RFC 6350).

security

wire-format §2.1

EXPERTISE ABNF: EXPERTISE-param allows LEVEL-param, INDEX-param, language-param, pref-param, altid-param, type-param, or any-param; EXPERTISE-value is text.

wire-format §2.2

HOBBY ABNF: HOBBY-param allows LEVEL-param, INDEX-param, language-param, pref-param, altid-param, type-param, or any-param; HOBBY-value is text.

wire-format §3.1

INDEX ABNF: INDEX-param is 'INDEX=' followed by INDEX-value, where INDEX-value is an integer.

wire-format §2.3

INTEREST ABNF: INTEREST-param allows LEVEL-param, INDEX-param, language-param, pref-param, altid-param, type-param, or any-param; INTEREST-value is text.

wire-format §3.2

LEVEL ABNF: LEVEL-param is 'LEVEL=' followed by LEVEL-value, where LEVEL-value is one of 'beginner', 'average', 'expert', 'high', 'medium', or 'low'.

wire-format §2.4

ORG-DIRECTORY ABNF: ORG-DIRECTORY-param allows pref-param, INDEX-param, language-param, pid-param, altid-param, type-param, or any-param; ORG-DIRECTORY-value is a URI.