rfc-6474

vCard Format Extensions: Place of Birth, Place and Date of Death

K. Li, B. Leiba
date2011-12 streamIETF areaapp wgvcarddav statusPROPOSED STANDARD pages6 canonicalhttps://www.rfc-editor.org/rfc/rfc6474 doi10.17487/RFC6474 errataview
The base vCard 4.0 specification defines a large number of properties, including date of birth. This specification adds three new properties to vCard 4.0: place of birth, place of death, and date of death. [STANDARDS-TRACK]

Extracted elements (13)

design-rationale §2.3

The presence of a DEATHDATE property indicates that the subject of the vCard is known to be dead. The absence of this property makes no statement one way or the other — absence does not imply the subject is alive.

interoperability-note §1

This specification extends vCard 4.0 as defined in RFC 6350. Syntax specifications use ABNF as described in RFC 5234 and follow the conventions of the base vCard specification, ensuring compatibility with vCard 4.0 implementations that support extension properties.

normative-requirement §2.1 MUST

For the BIRTHPLACE property, the value type and VALUE parameter MUST match — if VALUE=uri is specified, the value must be a URI; if VALUE=text or default, the value must be text.

normative-requirement §2.3 MUST

For the DEATHDATE property, the value type and VALUE parameter MUST match. Additionally, CALSCALE can only be present when DEATHDATE-value is date-and-or-time and actually contains a date or date-time.

normative-requirement §2.2 MUST

For the DEATHPLACE property, the value type and VALUE parameter MUST match — if VALUE=uri is specified, the value must be a URI; if VALUE=text or default, the value must be text.

protocol-element §2.1

The BIRTHPLACE property specifies the place of birth of the object the vCard represents. It accepts a single text value (default) or a single URI value, with cardinality *1. Supported parameters include VALUE, LANGUAGE, altid-param, and any-param.

yang

protocol-element §2.3

The DEATHDATE property specifies the date of death of the object the vCard represents. The default value type is date-and-or-time, which can be reset to text. Cardinality is *1; supported parameters are VALUE, CALSCALE, and LANGUAGE.

protocol-element §2.2

The DEATHPLACE property specifies the place of death of the object the vCard represents. It accepts a single text value (default) or a single URI value, with cardinality *1. Supported parameters include VALUE, LANGUAGE, altid-param, and any-param.

registry §4

IANA has added three entries to the vCard Properties registry (defined in RFC 6350 Section 10.3.1): BIRTHPLACE (Section 2.1), DEATHPLACE (Section 2.2), and DEATHDATE (Section 2.3), all with no namespace.

registry

security-consideration §3

The properties defined in this document (BIRTHPLACE, DEATHPLACE, DEATHDATE) present no security considerations beyond those in Section 9 of the base vCard specification RFC 6350.

security

wire-format §2.1

BIRTHPLACE ABNF: BIRTHPLACE-param = "VALUE=" ("text" / "uri"); BIRTHPLACE-value = text / uri. The value type and VALUE parameter MUST match. Also accepts altid-param, language-param, and any-param.

wire-format §2.3

DEATHDATE ABNF: DEATHDATE-param = DEATHDATE-param-date / DEATHDATE-param-text; DEATHDATE-value = date-and-or-time / text. CALSCALE can only be present when the value is date-and-or-time and actually contains a date or date-time. LANGUAGE can only be present when the value is text.

wire-format §2.2

DEATHPLACE ABNF: DEATHPLACE-param = "VALUE=" ("text" / "uri"); DEATHPLACE-value = text / uri. The value type and VALUE parameter MUST match. Also accepts altid-param, language-param, and any-param.