draft-ietf-vcarddav-vcardrev-08.txt   draft-ietf-vcarddav-vcardrev-09.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 P. Resnick Obsoletes: 2425, 2426, 4770 P. Resnick
(if approved) QUALCOMM Incorporated (if approved) QUALCOMM Incorporated
Updates: 2739 (if approved) July 13, 2009 Updates: 2739 (if approved) October 20, 2009
Intended status: Standards Track Intended status: Standards Track
Expires: January 14, 2010 Expires: April 23, 2010
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-08 draft-ietf-vcarddav-vcardrev-09
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 45 skipping to change at page 1, line 45
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 14, 2010. This Internet-Draft will expire on April 23, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract Abstract
This document defines the vCard data format for representing and This document defines the vCard data format for representing and
exchanging a variety of information about an individual (e.g., exchanging a variety of information about individuals and other
formatted and structured name and delivery addresses, email address, entities (e.g., formatted and structured name and delivery addresses,
multiple telephone numbers, photograph, logo, audio clips, etc.). email address, multiple telephone numbers, photograph, logo, audio
clips, etc.).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 6 3. vCard Format Specification . . . . . . . . . . . . . . . . . . 6
4. vCard Format Specification . . . . . . . . . . . . . . . . . . 7 3.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 6
4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 8 3.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7
4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 9 3.3. Property Value Escaping . . . . . . . . . . . . . . . . . 9
4.3. Property Value Escaping . . . . . . . . . . . . . . . . . 11 4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10
5. Property Value Data Types . . . . . . . . . . . . . . . . . . 11 4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 12
5.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 14 4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 13
5.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 15 4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14
5.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 15 4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 14
5.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 16 4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 15
5.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 17 5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16
6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 17 5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 19
7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 21 6.1. General Properties . . . . . . . . . . . . . . . . . . . . 20
7.1. General Properties . . . . . . . . . . . . . . . . . . . . 21 6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 20
7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 21 6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 20
7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 22 6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 22 6.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.2. Identification Properties . . . . . . . . . . . . . . . . 23
7.2. Identification Properties . . . . . . . . . . . . . . . . 24 6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 25
7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 26 6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 25
7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 26 6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 28 6.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.9. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 28
7.2.9. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 29 6.2.10. SEX . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2.10. SEX . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 29
7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 30 6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 30
7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 31 6.4. Communications Properties . . . . . . . . . . . . . . . . 31
7.4. Communications Properties . . . . . . . . . . . . . . . . 32 6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 33 6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.5. Geographical Properties . . . . . . . . . . . . . . . . . 33
7.5. Geographical Properties . . . . . . . . . . . . . . . . . 35 6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.6. Organizational Properties . . . . . . . . . . . . . . . . 35
7.6. Organizational Properties . . . . . . . . . . . . . . . . 36 6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 35
7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 36 6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 38
7.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 39 6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 39
7.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 40 6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 40
7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 41 6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 40
7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 41 6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 42 6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 41
7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 42 6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 42
7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 43 6.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 42
7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 43 6.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 43
7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 44 6.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 45 6.7.8. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 44
7.7.8. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 45 6.7.9. URL . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.7.9. URL . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.7.10. VERSION . . . . . . . . . . . . . . . . . . . . . . . 46
7.7.10. VERSION . . . . . . . . . . . . . . . . . . . . . . . 47 6.8. Security Properties . . . . . . . . . . . . . . . . . . . 46
7.8. Security Properties . . . . . . . . . . . . . . . . . . . 47 6.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 46
7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 47 6.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 48 6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 48
7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 49 6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 48
7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 49 6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 49
7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 50 6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 49
7.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 50 6.10. Extended Properties and Parameters . . . . . . . . . . . . 50
7.10. Extended Properties and Parameters . . . . . . . . . . . . 51 7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 50
8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 51 7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 50
8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 51 7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 50
8.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 51 7.1.2. Matching Property Instances . . . . . . . . . . . . . 50
8.1.2. Matching Property Instances . . . . . . . . . . . . . 51 7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 51
8.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 52 7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 52 7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 52
8.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 52 7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 52
8.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 53 7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 52
8.2.3. Adding and Sharing a Property . . . . . . . . . . . . 53 7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 53
8.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 54 7.2.5. Global Context Simplification . . . . . . . . . . . . 54
8.2.5. Global Context Simplification . . . . . . . . . . . . 55 8. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 55
9. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 56 9. Security Considerations . . . . . . . . . . . . . . . . . . . 56
10. Security Considerations . . . . . . . . . . . . . . . . . . . 56 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57 10.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 56
11.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 57 10.2. Registering New vCard Elements . . . . . . . . . . . . . . 58
11.2. Registering New vCard Elements . . . . . . . . . . . . . . 57 10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 58
11.2.1. Registration Procedure . . . . . . . . . . . . . . . . 57 10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 59
11.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 58 10.2.3. Registration Template for Properties . . . . . . . . . 59
11.2.3. Registration Template for Groups . . . . . . . . . . . 58 10.2.4. Registration Template for Parameters . . . . . . . . . 60
11.2.4. Registration Template for Properties . . . . . . . . . 59 10.2.5. Registration Template for Value Data Types . . . . . . 60
11.2.5. Registration Template for Parameters . . . . . . . . . 59 10.2.6. Registration Template for Values . . . . . . . . . . . 60
11.2.6. Registration Template for Value Data Types . . . . . . 60 10.3. Initial vCard Elements Registries . . . . . . . . . . . . 61
11.2.7. Registration Template for Values . . . . . . . . . . . 60 10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 61
11.3. Initial vCard Elements Registries . . . . . . . . . . . . 61 10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 63
11.3.1. Groups Registry . . . . . . . . . . . . . . . . . . . 61 10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 63
11.3.2. Properties Registry . . . . . . . . . . . . . . . . . 62 10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 63
11.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 64 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65
11.3.4. Value Data Types Registry . . . . . . . . . . . . . . 64 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
11.3.5. Values Registries . . . . . . . . . . . . . . . . . . 64 12.1. Normative References . . . . . . . . . . . . . . . . . . . 65
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 66 12.2. Informative References . . . . . . . . . . . . . . . . . . 68
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 68
13.1. Normative References . . . . . . . . . . . . . . . . . . . 66 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 68
13.2. Informative References . . . . . . . . . . . . . . . . . . 69 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 69
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 69 A.3. New Properties and Parameters . . . . . . . . . . . . . . 69
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 69 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 69
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 70
A.3. New Properties and Parameters . . . . . . . . . . . . . . 70
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 70
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 71 publication) . . . . . . . . . . . . . . . . . . . . 70
B.1. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 71 B.1. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 70
B.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 71 B.2. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 70
B.3. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 72 B.3. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 70
B.4. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 72 B.4. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 71
B.5. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 72 B.5. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 72
B.6. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 73 B.6. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 72
B.7. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 73 B.7. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 72
B.8. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 74 B.8. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 73
B.9. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 75 B.9. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 73
B.10. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 74
1. Introduction 1. Introduction
Note: This draft contains much of the same text as 2425 and 2426
which may not be correct. Those two RFCs have been merged and the
structure of this draft is what's new. Some vCard-specific
suggestions have been added, but for the most part this is still very
open. But we'd like to get feedback on the structure mostly so that
it may be fixed.
Electronic address books have become ubiquitous. Their increased Electronic address books have become ubiquitous. Their increased
presense on portable, connected devices as well as the diversity of presence on portable, connected devices as well as the diversity of
platforms exchanging contact data call for a standard. This memo platforms exchanging contact data call for a standard. This memo
defines the vCard format, which allows the capture and exchange of defines the vCard format, which allows the capture and exchange of
information normally stored within an address book or directory information normally stored within an address book or directory
application. application.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. MIME Type Registration 3. vCard Format Specification
To: ietf-types@iana.org
Subject: Registration of media type text/vcard
Type name: text
Subtype name: vcard
Required parameters: none
Optional parameters: charset
Encoding considerations: The "charset" MIME parameter is interpreted
as defined in [RFC2046], section 4.1.2. If it is omitted, the
default encoding is UTF-8 as defined in [RFC3629].
Security considerations: See Section 10.
Interoperability considerations: The text/vcard media type is
intended to identify vCard data of any version. There are older
specifications of vCard [RFC2426][oldreference_VCARD] still in
common use. While these formats are similar, they are not
strictly compatible. In general, it is necessary to inspect the
value of the VERSION property (see Section 7.7.10) for identifying
the standard to which a given vCard object conforms.
In addition, the following media types are known to have been used
to refer to vCard data. They should be considered deprecated in
favor of text/vcard.
* text/directory
* text/directory; type=vcard
* text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-08
Applications that use this media type: They are numerous, diverse,
and include mail user agents, instant messaging clients, address
book applications, directory servers, customer relationship
management software, etc.
Additional information:
Magic number(s):
File extension(s): .vcf
Macintosh file type code(s):
Person & email address to contact for further information: Simon
Perreault <simon.perreault@viagenie.ca>
Intended usage: COMMON
Restrictions on usage: none
Author: Simon Perreault and Pete Resnick
Change controller: IETF
4. vCard Format Specification
The text/vcard MIME content type (hereafter known as "vCard") The text/vcard MIME content type (hereafter known as "vCard", see
contains contact information, typically pertaining to a single Section 10.1) contains contact information, typically pertaining to a
contact or group of contacts. The content consists of one or more single contact or group of contacts. The content consists of one or
lines in the format given below. more lines in the format given below.
4.1. Line Delimiting and Folding 3.1. Line Delimiting and Folding
Individual lines within vCard are delimited by the [RFC5322] line Individual lines within vCard are delimited by the [RFC5322] line
break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII
decimal 10). Long logical lines of text can be split into a decimal 10). Long logical lines of text can be split into a
multiple-physical-line representation using the following folding multiple-physical-line representation using the following folding
technique. Content lines SHOULD be folded to a maximum width of 75 technique. Content lines SHOULD be folded to a maximum width of 75
octets. Multi-octet characters MUST remain contiguous. The octets. Multi-octet characters MUST remain contiguous. The
rationale for this folding process can be found in [RFC5322], Section rationale for this folding process can be found in [RFC5322], Section
2.1.1. 2.1.1.
A logical line MAY be continued on the next physical line anywhere A logical line MAY be continued on the next physical line anywhere
between two characters by inserting a CRLF immediately followed by a between two characters by inserting a CRLF immediately followed by a
single white space character (space, ASCII decimal 32, or horizontal single white space character (space, ASCII decimal 32, or horizontal
tab, ASCII decimal 9). At least one character must be present on the tab, ASCII decimal 9). The folded line MUST contain at least one
folded line. Any sequence of CRLF followed immediately by a single character. Any sequence of CRLF followed immediately by a single
white space character is ignored (removed) when processing the white space character is ignored (removed) when processing the
content type. For example the line: content type. For example the line:
DESCRIPTION:This is a long description that exists on a long line. DESCRIPTION:This is a long description that exists on a long line.
can be represented as: can be represented as:
DESCRIPTION:This is a long description DESCRIPTION:This is a long description
that exists on a long line. that exists on a long line.
skipping to change at page 9, line 4 skipping to change at page 7, line 27
Note: It is possible for very simple implementations to generate Note: It is possible for very simple implementations to generate
improperly folded lines in the middle of a UTF-8 multi-octet improperly folded lines in the middle of a UTF-8 multi-octet
sequence. For this reason, implementations SHOULD unfold lines in sequence. For this reason, implementations SHOULD unfold lines in
such a way as to properly restore the original sequence. such a way as to properly restore the original sequence.
Note: Unfolding is done differently than in [RFC5322]. Unfolding Note: Unfolding is done differently than in [RFC5322]. Unfolding
in [RFC5322] only removes the CRLF, not the space following it. in [RFC5322] only removes the CRLF, not the space following it.
Folding is done after any content encoding of a type value. Folding is done after any content encoding of a type value.
Unfolding is done before any decoding of a type value in a content Unfolding is done before any decoding of a type value in a content
line. line.
4.2. ABNF Format Definition 3.2. ABNF Format Definition
The following ABNF uses the notation of [RFC5234], which also defines The following ABNF uses the notation of [RFC5234], which also defines
CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.
vcard-entity = 1*(vcard) vcard-entity = 1*(vcard)
vcard = "BEGIN" ":" "VCARD" CRLF vcard = "BEGIN" ":" "VCARD" CRLF
1*contentline 1*contentline
"END" ":" "VCARD" CRLF "END" ":" "VCARD" CRLF
;A vCard object MUST include the VERSION and FN properties. ;A vCard object MUST include the VERSION and FN properties.
contentline = [group "."] name *(";" param) ":" value CRLF contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines MUST first ; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure ; be unfolded according to the unfolding procedure
; described above. ; described above.
; When generating a content line, lines longer than 75 ; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding ; characters SHOULD be folded according to the folding
; procedure described above. ; procedure described above.
group = "WORK" / "HOME" / iana-token / x-name group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "NAME" / "KIND" / "FN" / "N" / "NICKNAME" name = "SOURCE" / "NAME" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "SEX" / "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "SEX"
/ "ADR" / "LABEL" / "TEL" / "EMAIL" / "IMPP" / "LANG" / "ADR" / "LABEL" / "TEL" / "EMAIL" / "IMPP" / "LANG"
/ "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "ORG" / "MEMBER" / "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "ORG" / "MEMBER"
/ "RELATED" / "CATEGORIES" / "NOTE" / "PRODID" / "REV" / "RELATED" / "CATEGORIES" / "NOTE" / "PRODID" / "REV"
/ "SORT-STRING" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL" / "SORT-STRING" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL"
/ "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI" / "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI"
/ "CALURI" / iana-token / x-name / "CALURI" / iana-token / x-name
; Parsing of the param and value is based on the "name" as ; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below. ; defined in ABNF sections below.
skipping to change at page 10, line 36 skipping to change at page 9, line 9
from that found in [RFC5322], in that the sequence <CRLF><WSP> found from that found in [RFC5322], in that the sequence <CRLF><WSP> found
anywhere in the content indicates a continued line and should be anywhere in the content indicates a continued line and should be
removed. removed.
Property names and parameter names are case insensitive (e.g., the Property names and parameter names are case insensitive (e.g., the
property name "fn" is the same as "FN" and "Fn"). Parameter values property name "fn" is the same as "FN" and "Fn"). Parameter values
MAY be case sensitive or case insensitive, depending on their MAY be case sensitive or case insensitive, depending on their
definition. definition.
The group construct is used to group related properties together. The group construct is used to group related properties together.
For example, groups named "WORK" and "HOME" could be used to The group name is a syntactic convention used to indicate that all
segregate properties such as telephone number, address, etc. property names prefaced with the same group name SHOULD be grouped
Displaying of groups is left entirely up to the application. together when displayed by an application. It has no other
Predefined groups with assigned meaning are listed in Section 11.3.1. significance. Implementations that do not understand or support
It is possible to register new groups from IANA. Unregistered groups grouping MAY simply strip off any text before a "." to the left of
MAY be used and MUST start with "X-". the type name and present the types and values as normal.
Properties defined in a vCard instance may have multiple values Properties defined in a vCard instance may have multiple values
depending on the property cardinality. The general rule for encoding depending on the property cardinality. The general rule for encoding
multi-valued properties is to simply create a new content line for multi-valued properties is to simply create a new content line for
each value (including the property name). However, it should be each value (including the property name). However, it should be
noted that some value types support encoding multiple values in a noted that some value types support encoding multiple values in a
single content line by separating the values with a comma ",". This single content line by separating the values with a comma ",". This
approach has been taken for several of the content types defined approach has been taken for several of the content types defined
below (date, time, integer, float), for space-saving reasons. below (date, time, integer, float), for space-saving reasons.
4.3. Property Value Escaping 3.3. Property Value Escaping
A property instance may contain one or more values delimited by a A property instance may contain one or more values delimited by a
COMMA character (ASCII decimal 44). Therefore, a COMMA character in COMMA character (ASCII decimal 44). Therefore, a COMMA character in
a value MUST be escaped with a BACKSLASH character (ASCII decimal a value MUST be escaped with a BACKSLASH character (ASCII decimal
92), even for properties that don't allow multiple instances (for 92), even for properties that don't allow multiple instances (for
consistency). consistency).
Some properties (e.g. N and ADR) comprise multiple fields delimited Some properties (e.g. N and ADR) comprise multiple fields delimited
by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI- by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI-
COLON in a field of such a "compound" property MUST be escaped with a COLON in a field of such a "compound" property MUST be escaped with a
skipping to change at page 11, line 32 skipping to change at page 10, line 5
character, even for fields that don't allow multiple values (for character, even for fields that don't allow multiple values (for
consistency). Compound properties allowing multiple instances MUST consistency). Compound properties allowing multiple instances MUST
NOT be encoded in a single content line. NOT be encoded in a single content line.
Finally, newline (ASCII decimal 10) and backslash (ASCII decimal 92) Finally, newline (ASCII decimal 10) and backslash (ASCII decimal 92)
characters in values MUST be escaped by prefixing them with a characters in values MUST be escaped by prefixing them with a
backslash character. backslash character.
In all other cases, escaping MUST NOT be used. In all other cases, escaping MUST NOT be used.
5. Property Value Data Types 4. Property Value Data Types
Standard value types are defined below. Standard value types are defined below.
value = text value = text
/ text-list / text-list
/ date-list / date-list
/ time-list / time-list
/ date-time-list / date-time-list
/ date-and-or-time-list / date-and-or-time-list
/ timestamp-list / timestamp-list
/ boolean / boolean
/ integer-list / integer-list
/ float-list / float-list
/ binary / binary
/ URI ; from Appendix A of [RFC3986] / URI ; from Section 3 of [RFC3986]
/ iana-valuespec / iana-valuespec
; Actual value type depends on property name and VALUE parameter. ; Actual value type depends on property name and VALUE parameter.
text = *VALUE-CHAR text = *VALUE-CHAR
text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR) text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)
TEXT-LIST-CHAR = "\\" / "\," / "\n" TEXT-LIST-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \ or newline> / <any VALUE-CHAR except , or \ or newline>
; Backslashes, commas, and newlines must be encoded. ; Backslashes, commas, and newlines must be encoded.
date-list = date *("," date) date-list = date *("," date)
time-list = time *("," time) time-list = time *("," time)
date-time-list = date-time *("," date-time) date-time-list = date-time *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-ortime) date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list = timestamp *("," timestamp) timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer) integer-list = integer *("," integer)
float-list = float *("," float) float-list = float *("," float)
boolean = "TRUE" / "FALSE" boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT] float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-" sign = "+" / "-"
skipping to change at page 13, line 4 skipping to change at page 11, line 24
date-complete = year month day date-complete = year month day
time = hour [minute [second]] [zone] time = hour [minute [second]] [zone]
/ "-" minute [second] [zone] / "-" minute [second] [zone]
/ "-" "-" second [zone] / "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone] time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone] time-complete = hour minute second [zone]
date-time = date-noreduc "T" time-notrunc date-time = date-noreduc "T" time-notrunc
timestamp = date-complete "T" time-complete timestamp = date-complete "T" time-complete
date-and-or-time = date-time / date / "T" time date-and-or-time = date-time / date / "T" time
utc-offset = sign hour [minute] utc-offset = sign hour [minute]
iana-valuespec = <a publicly-defined valuetype format, registered> iana-valuespec = <value-spec, see Section 12>
<with IANA, as defined in section 12 of this> ; a publicly-defined valuetype format, registered
<document> ; with IANA, as defined in section 12 of this
; document
5.1. TEXT 4.1. TEXT
"text": The "text" value type should be used to identify values that "text": The "text" value type should be used to identify values that
contain human-readable text. The character set in which the text is contain human-readable text. The character set in which the text is
represented is controlled by the "charset" MIME type parameter. Note represented is controlled by the "charset" MIME type parameter. Note
that there is no way to override this parameter on a per-property that there is no way to override this parameter on a per-property
basis. As for the language, it is controlled by the "language" basis. As for the language, it is controlled by the "language"
property parameter defined in Section 6.1. property parameter defined in Section 5.1.
Examples for "text": Examples for "text":
this is a text value this is a text value
this is one value,this is another this is one value,this is another
this is a single value\, with a comma encoded this is a single value\, with a comma encoded
A formatted text line break in a text value type MUST be represented A formatted text line break in a text value type MUST be represented
as the character sequence backslash (ASCII decimal 92) followed by a as the character sequence backslash (ASCII decimal 92) followed by a
Latin small letter n (ASCII decimal 110) or a Latin capital letter N Latin small letter n (ASCII decimal 110) or a Latin capital letter N
skipping to change at page 13, line 47 skipping to change at page 12, line 21
could be represented as: could be represented as:
DESCRIPTION:Mythical Manager\nHyjinx Software Division\n DESCRIPTION:Mythical Manager\nHyjinx Software Division\n
BabsCo\, Inc.\n BabsCo\, Inc.\n
demonstrating the \n literal formatted line break technique, the demonstrating the \n literal formatted line break technique, the
CRLF-followed-by-space line folding technique, and the backslash CRLF-followed-by-space line folding technique, and the backslash
escape technique. escape technique.
5.2. URI 4.2. URI
"uri": The "uri" value type should be used to identify values that "uri": The "uri" value type should be used to identify values that
are referenced by a URI (including a Content-ID URI), instead of are referenced by a URI (including a Content-ID URI), instead of
encoded in-line. These value references might be used if the value encoded in-line. These value references might be used if the value
is too large, or otherwise undesirable to include directly. The is too large, or otherwise undesirable to include directly. The
format for the URI is as defined in [RFC3986]. Note that the value format for the URI is as defined in [RFC3986]. Note that the value
of a property of type "uri" is what the URI points to, not the URI of a property of type "uri" is what the URI points to, not the URI
itself. itself.
Examples for "uri": Examples for "uri":
http://www.example.com/my/picture.jpg http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen ldap://ldap.example.com/cn=babs%20jensen
5.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP 4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP
"date", "time", "date-time", and "timestamp": Each of these value "date", "time", "date-time", and "timestamp": Each of these value
types is based on a the definitions in [ISO.8601.2004] standard. types is based on the definitions in [ISO.8601.2004] standard.
Multiple such values can be specified using the comma-separated Multiple such values can be specified using the comma-separated
notation. notation.
Only the basic format is supported. Only the basic format is supported.
5.3.1. DATE 4.3.1. DATE
A calendar date as specified in [ISO.8601.2004] section 4.1.2. A calendar date as specified in [ISO.8601.2004] section 4.1.2.
Reduced accuracy, as specified in [ISO.8601.2004] sections 4.1.2.3 a) Reduced accuracy, as specified in [ISO.8601.2004] sections 4.1.2.3 a)
and b), but not c), is permitted. and b), but not c), is permitted.
Expanded representation, as specified in [ISO.8601.2004] section Expanded representation, as specified in [ISO.8601.2004] section
4.1.4, is forbidden. 4.1.4, is forbidden.
Truncated representation, as specified in [ISO.8601.2000] sections Truncated representation, as specified in [ISO.8601.2000] sections
5.2.1.3 d), e), and f), is permitted. 5.2.1.3 d), e), and f), is permitted.
Examples for "date": Examples for "date":
19850412 19850412
1985-04 1985-04
1985 1985
--0412 --0412
---12 ---12
5.3.2. TIME 4.3.2. TIME
A time of day as specified in [ISO.8601.2004] section 4.2. A time of day as specified in [ISO.8601.2004] section 4.2.
Reduced accuracy, as specified in [ISO.8601.2004] section 4.2.2.3, is Reduced accuracy, as specified in [ISO.8601.2004] section 4.2.2.3, is
permitted. permitted.
Representation with decimal fraction, as specified in [ISO.8601.2004] Representation with decimal fraction, as specified in [ISO.8601.2004]
section 4.2.2.4, is forbidden. section 4.2.2.4, is forbidden.
Midnight is always represented by 00, never 24 (see [ISO.8601.2004] Midnight is always represented by 00, never 24 (see [ISO.8601.2004]
skipping to change at page 15, line 22 skipping to change at page 13, line 45
Examples for "time": Examples for "time":
102200 102200
1022 1022
10 10
-2200 -2200
--00 --00
102200Z 102200Z
102200-0800 102200-0800
5.3.3. DATE-TIME 4.3.3. DATE-TIME
A date and time of day combination as specified in [ISO.8601.2004] A date and time of day combination as specified in [ISO.8601.2004]
section 4.3. section 4.3.
Truncation of the date part, as specified in [ISO.8601.2000] section Truncation of the date part, as specified in [ISO.8601.2000] section
5.4.2 c), is permitted. 5.4.2 c), is permitted.
Examples for "date-time": Examples for "date-time":
19961022T140000 19961022T140000
--1022T1400 --1022T1400
---22T14 ---22T14
5.3.4. DATE-AND-OR-TIME 4.3.4. DATE-AND-OR-TIME
Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous
interpretation, a standalone TIME value is always preceded by a "T". interpretation, a standalone TIME value is always preceded by a "T".
Examples for "date-and-or-time": Examples for "date-and-or-time":
19961022T140000 19961022T140000
--1022T1400 --1022T1400
---22T14 ---22T14
19850412 19850412
skipping to change at page 16, line 23 skipping to change at page 14, line 34
--0412 --0412
---12 ---12
T102200 T102200
T1022 T1022
T10 T10
T-2200 T-2200
T--00 T--00
T102200Z T102200Z
T102200-0800 T102200-0800
5.3.5. TIMESTAMP 4.3.5. TIMESTAMP
A complete date and time of day combination as specified in A complete date and time of day combination as specified in
[ISO.8601.2004] section 4.3.2. [ISO.8601.2004] section 4.3.2.
Examples for "timestamp": Examples for "timestamp":
19961022T140000 19961022T140000
19961022T140000Z 19961022T140000Z
19961022T140000-05 19961022T140000-05
19961022T140000-0500 19961022T140000-0500
5.4. BOOLEAN 4.4. BOOLEAN
"boolean": The "boolean" value type is used to express boolen values. "boolean": The "boolean" value type is used to express boolen values.
These values are case insensitive. These values are case insensitive.
Examples: Examples:
TRUE TRUE
false false
True True
5.5. INTEGER 4.5. INTEGER
"integer": The "integer" value type is used to express signed "integer": The "integer" value type is used to express signed
integers in decimal format. If sign is not specified, the value is integers in decimal format. If sign is not specified, the value is
assumed positive "+". Multiple "integer" values can be specified assumed positive "+". Multiple "integer" values can be specified
using the comma-separated notation. using the comma-separated notation.
Examples: Examples:
1234567890 1234567890
-1234556790 -1234556790
+1234556790,432109876 +1234556790,432109876
5.6. FLOAT 4.6. FLOAT
"float": The "float" value type is used to express real numbers. If "float": The "float" value type is used to express real numbers. If
sign is not specified, the value is assumed positive "+". Multiple sign is not specified, the value is assumed positive "+". Multiple
"float" values can be specified using the comma-separated notation. "float" values can be specified using the comma-separated notation.
Examples: Examples:
20.30 20.30
1000000.0000001 1000000.0000001
1.333,3.14 1.333,3.14
5.7. BINARY 4.7. BINARY
"binary": The "binary" value type specifies that the type value is "binary": The "binary" value type specifies that the type value is
inline, encoded binary data. This value type can be specified in the inline, encoded binary data. This value type can be specified in the
PHOTO, LOGO, SOUND, and KEY types. PHOTO, LOGO, SOUND, and KEY types.
If inline encoded binary data is specified, the ENCODING type If inline encoded binary data is specified, the ENCODING type
parameter MUST be used to specify the encoding format. The binary parameter MUST be used to specify the encoding format. The binary
data MUST be encoded using the "B" encoding format. Long lines of data MUST be encoded using the "B" encoding format. Long lines of
encoded binary data SHOULD BE folded to 75 characters using the encoded binary data SHOULD BE folded to 75 characters using the
folding method defined in Section 4.1. folding method defined in Section 3.1.
5.8. LANGUAGE-TAG 4.8. LANGUAGE-TAG
"language-tag": A single language tag, as defined in [RFC4646]. "language-tag": A single language tag, as defined in [RFC5646].
6. Property Parameters 5. Property Parameters
A property can have attributes associated with it. These "property A property can have attributes associated with it. These "property
parameters" contain meta-information about the property or the parameters" contain meta-information about the property or the
property value. property value.
Property parameter values that contain the COLON (US-ASCII decimal Property parameter values that contain the COLON (US-ASCII decimal
58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44) 58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44)
character separators MUST be specified as quoted-string text values. character separators MUST be specified as quoted-string text values.
Property parameter values MUST NOT contain the DQUOTE (US-ASCII Property parameter values MUST NOT contain the DQUOTE (US-ASCII
decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is
used as a delimiter for parameter values that contain restricted used as a delimiter for parameter values that contain restricted
characters or URI text. For example: characters or URI text. For example:
EMAIL;PID=8:jdoe@example.com EMAIL;PID=8:jdoe@example.com
Property parameter values that are not in quoted strings are case Property parameter values that are not in quoted strings are case
insensitive. insensitive.
Applications MUST ignore x-param and iana-param value they don't Applications MUST ignore x-param and iana-param values they don't
recognize. recognize.
6.1. LANGUAGE 5.1. LANGUAGE
The "language" property parameter is used to identify data in The "language" property parameter is used to identify data in
multiple languages. There is no concept of "default" language, multiple languages. There is no concept of "default" language,
except as specified by any "Content-Language" MIME header parameter except as specified by any "Content-Language" MIME header parameter
that is present. The value of the "language" property parameter is a that is present. The value of the "language" property parameter is a
language tag as defined in Section 2 of [RFC4646]. language tag as defined in Section 2 of [RFC5646].
ABNF: ABNF:
language-param = "LANGUAGE=" Language-Tag language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 4646 ; Language-Tag is defined in section 2.1 of RFC 5646
6.2. ENCODING 5.2. ENCODING
The "encoding" property parameter is used to specify an alternate The "encoding" property parameter is used to specify an alternate
encoding for a value. If the value contains a CRLF, it must be encoding for a value. If the value contains a CRLF, it must be
encoded, since CRLF is used to separate lines in the content-type encoded, since CRLF is used to separate lines in the content-type
itself. Currently, only the "b" encoding is supported. itself. Currently, only the "b" encoding is supported.
The "b" encoding can also be useful for binary values that are mixed The "b" encoding can also be useful for binary values that are mixed
with other text information in the body part (e.g., a certificate). with other text information in the body part (e.g., a certificate).
Using a per-value "b" encoding in this case leaves the other Using a per-value "b" encoding in this case leaves the other
information in a more readable form. The encoded base 64 value can information in a more readable form. The encoded base 64 value can
skipping to change at page 19, line 14 skipping to change at page 17, line 28
Transfer-Encoding is decoded first, and then any individual Transfer-Encoding is decoded first, and then any individual
properties with an "encoding" property parameter are decoded. properties with an "encoding" property parameter are decoded.
ABNF: ABNF:
encoding-param = "ENCODING=" encoding-type encoding-param = "ENCODING=" encoding-type
encoding-type = "b" ; from [RFC2047] encoding-type = "b" ; from [RFC2047]
/ iana-token ; registered as in section 12 / iana-token ; registered as in section 12
6.3. VALUE 5.3. VALUE
The "value" parameter is optional, and is used to identify the value The "value" parameter is optional, and is used to identify the value
type (data type) and format of the value. The use of these type (data type) and format of the value. The use of these
predefined formats is encouraged even if the value parameter is not predefined formats is encouraged even if the value parameter is not
explicity used. By defining a standard set of value types and their explicity used. By defining a standard set of value types and their
formats, existing parsing and processing code can be leveraged. The formats, existing parsing and processing code can be leveraged. The
predefined data type values MUST NOT be repeated in COMMA separated predefined data type values MUST NOT be repeated in COMMA separated
value lists except within the N, NICKNAME, ADR and CATEGORIES value lists except within the N, NICKNAME, ADR and CATEGORIES
properties. properties.
skipping to change at page 20, line 5 skipping to change at page 18, line 23
/ "date-time" / "date-time"
/ "timestamp" / "timestamp"
/ "boolean" / "boolean"
/ "integer" / "integer"
/ "float" / "float"
/ "binary" / "binary"
/ "language-tag" / "language-tag"
/ iana-token ; registered as described in section 12 / iana-token ; registered as described in section 12
/ x-name / x-name
6.4. PREF 5.4. PREF
The "pref" parameter is optional, and is used to indicate that the The "pref" parameter is optional, and is used to indicate that the
corresponding instance of a property is preferred by the vCard corresponding instance of a property is preferred by the vCard
author. Its value MUST be an integer between 1 and 100 that author. Its value MUST be an integer between 1 and 100 that
quantifies the level of preferredness. Lower values correspond to a quantifies the level of preferredness. Lower values correspond to a
higher level of preferrredness, 1 being most preferred. higher level of preferrredness, 1 being most preferred.
When the parameter is absent, the default MUST be to interpret the When the parameter is absent, the default MUST be to interpret the
property instance as being least preferred. property instance as being least preferred.
skipping to change at page 20, line 28 skipping to change at page 18, line 46
in the same vCard. A given value, or the absence of a value, MUST in the same vCard. A given value, or the absence of a value, MUST
NOT be interpreted on its own. NOT be interpreted on its own.
This parameter MAY be applied to any property that allows multiple This parameter MAY be applied to any property that allows multiple
instances. instances.
ABNF: ABNF:
pref-param = "PREF=" (1*2DIGIT / "100") pref-param = "PREF=" (1*2DIGIT / "100")
6.5. PID 5.5. PID
The "pid" parameter is used to identify a specific property among The "pid" parameter is used to identify a specific property among
multiple instances. It plays a role analogous to the UID property multiple instances. It plays a role analogous to the UID property
(Section 7.7.7) on a per-property instead of per-vCard basis. It MAY (Section 6.7.7) on a per-property instead of per-vCard basis. It MAY
appear more than once in a given property. It MUST NOT appear on appear more than once in a given property. It MUST NOT appear on
properties that only may have one instance per vCard. Its value is properties that only may have one instance per vCard. Its value is
either a single small integer, or a pair of small integers separated either a single small integer, or a pair of small integers separated
by a dot. Multiple values may be encoded in a single PID parameter by a dot. Multiple values may be encoded in a single PID parameter
by separating the values with a comma ",". See Section 8 for more by separating the values with a comma ",". See Section 7 for more
details on its usage. details on its usage.
ABNF: ABNF:
pid-param = "PID=" pid-value *("," pid-value) pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT] pid-value = 1*DIGIT ["." 1*DIGIT]
6.6. TYPE 5.6. TYPE
The "type" parameter has multiple, different uses. In general, it is The "type" parameter has multiple, different uses. In general, it is
a way of specifying class characteristics of the associated property. a way of specifying class characteristics of the associated property.
Most of the time, its value is a comma-separated subset of a pre- Most of the time, its value is a comma-separated subset of a pre-
defined enumeration. In this document, the following properties make defined enumeration. In this document, the following properties make
use of this parameter: PHOTO, ADR, LABEL, TEL, EMAIL, IMPP, LOGO, use of this parameter: FN, NICKNAME, PHOTO, ADR, LABEL, TEL, EMAIL,
MEMBER, SOUND, and KEY. IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES,
NOTE, SOUND, URL, KEY, FIBURL, CALADRURI, and CALURI. The TYPE
parameter MUST NOT be applied on other properties defined in this
document.
The "work" and "home" values can be used wherever the TYPE parameter
is allowed, but only when the KIND property is absent or its value is
"individual". They act like tags. The "work" value implies that the
property is related to an individual's work place, while the "home"
value implies that the property is related to an individual's
personal life. When neither "work" nor "home" is present, it is
implied that the property is related to both an individual's work
place and personal life in case the KIND property's value is
"individual", or to none in other cases.
ABNF: ABNF:
type-param= = "TYPE=" type-value *("," type-value) type-param = "TYPE=" type-value *("," type-value)
type-value = type-value-tel / type-value-related type-value = "work" / "home" / type-param-tel
/ iana-token / x-name / type-param-related / iana-token / x-name
; This is further defined in individual property sections. ; This is further defined in individual property sections.
7. vCard Properties 6. vCard Properties
What follows is an enumeration of the standard vCard properties. What follows is an enumeration of the standard vCard properties.
Property cardinalities are indicated using the following notation: Property cardinalities are indicated using the following notation:
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
| Cardinality | Meaning | | Cardinality | Meaning |
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
| (1,1) | Exactly one instance per vCard MUST be present. | | (1,1) | Exactly one instance per vCard MUST be present. |
| (0,1) | Exactly one instance per vCard MAY be present. | | (0,1) | Exactly one instance per vCard MAY be present. |
| (1,n) | One or more instances per vCard MUST be present. | | (1,n) | One or more instances per vCard MUST be present. |
| (0,n) | One or more instances per vCard MAY be present. | | (0,n) | One or more instances per vCard MAY be present. |
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
7.1. General Properties 6.1. General Properties
7.1.1. BEGIN 6.1.1. BEGIN
Purpose: To denote the beginning of a syntactic entity within a Purpose: To denote the beginning of a syntactic entity within a
text/vcard content-type. text/vcard content-type.
Value type: text Value type: text
Cardinality: (1,1) Cardinality: (1,1)
Special notes: The content entity MUST begin with the BEGIN property Special notes: The content entity MUST begin with the BEGIN property
with a value of "VCARD". with a value of "VCARD".
skipping to change at page 22, line 14 skipping to change at page 20, line 46
ABNF: ABNF:
BEGIN-param = ; no parameter allowed BEGIN-param = ; no parameter allowed
BEGIN-value = "VCARD" BEGIN-value = "VCARD"
Example: Example:
BEGIN:VCARD BEGIN:VCARD
7.1.2. END 6.1.2. END
Purpose: To denote the end of a syntactic entity within a text/vcard Purpose: To denote the end of a syntactic entity within a text/vcard
content-type. content-type.
Value type: text Value type: text
Cardinality: (1,1) Cardinality: (1,1)
Special notes: The content entity MUST end with the END type with a Special notes: The content entity MUST end with the END type with a
value of "VCARD". value of "VCARD".
skipping to change at page 22, line 44 skipping to change at page 21, line 30
ABNF: ABNF:
END-param = ; no parameter allowed END-param = ; no parameter allowed
END-value = "VCARD" END-value = "VCARD"
Example: Example:
END:VCARD END:VCARD
7.1.3. SOURCE 6.1.3. SOURCE
Purpose: To identify the source of directory information contained Purpose: To identify the source of directory information contained
in the content type. in the content type.
Value type: uri Value type: uri
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The SOURCE property is used to provide the means by Special notes: The SOURCE property is used to provide the means by
which applications knowledgable in the given directory service which applications knowledgable in the given directory service
protocol can obtain additional or more up-to-date information from protocol can obtain additional or more up-to-date information from
the directory service. It contains a URI as defined in [RFC3986] the directory service. It contains a URI as defined in [RFC3986]
and/or other information referencing the vCard to which the and/or other information referencing the vCard to which the
information pertains. When directory information is available information pertains. When directory information is available
from more than one source, the sending entity can pick what it from more than one source, the sending entity can pick what it
considers to be the best source, or multiple SOURCE properties can considers to be the best source, or multiple SOURCE properties can
skipping to change at page 23, line 28 skipping to change at page 22, line 12
SOURCE-param = "VALUE=uri" / pid-param / pref-param / any-param SOURCE-param = "VALUE=uri" / pid-param / pref-param / any-param
SOURCE-value = uri SOURCE-value = uri
Examples: Examples:
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/ SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf Jean%20Dupont.vcf
7.1.4. NAME 6.1.4. NAME
Purpose: To identify the displayable name of the directory entity to Purpose: To identify the displayable name of the directory entity to
which information in the vCard pertains. which information in the vCard pertains.
Value type: text Value type: text
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The NAME property is used to convey the display name Special notes: The NAME property is used to convey the display name
of the entity to which the directory information pertains. Its of the entity to which the directory information pertains. Its
skipping to change at page 24, line 5 skipping to change at page 22, line 35
ABNF: ABNF:
NAME-param = "VALUE=text" / any-param NAME-param = "VALUE=text" / any-param
NAME-value = text NAME-value = text
Example: Example:
NAME:Babs Jensen's Contact Information NAME:Babs Jensen's Contact Information
7.1.5. KIND 6.1.5. KIND
Purpose: To specify the kind of object the vCard represents. Purpose: To specify the kind of object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The value may be one of: "individual" for a single Special notes: The value may be one of: "individual" for a single
person, "group" for a group of people, "org" for an organization, person, "group" for a group of people, "org" for an organization,
"location" for a named geographical place, an x-name or an iana- "location" for a named geographical place, "thing" for an
token. If this property is absent, "individual" MUST be assumed inanimate object (e.g. a device, a server, etc.), an x-name or an
as default. iana-token. If this property is absent, "individual" MUST be
assumed as default.
ABNF: ABNF:
KIND-param = "VALUE=text" / any-param KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location" KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name / iana-token / x-name
Example: Example:
This represents someone named Jane Doe working in the marketing This represents someone named Jane Doe working in the marketing
skipping to change at page 24, line 47 skipping to change at page 23, line 33
This represents the department itself, commonly known as ABC This represents the department itself, commonly known as ABC
Marketing. Marketing.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:org KIND:org
FN:ABC Marketing FN:ABC Marketing
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD END:VCARD
7.2. Identification Properties 6.2. Identification Properties
These types are used to capture information associated with the These types are used to capture information associated with the
identification and naming of the person or resource associated with identification and naming of the person or resource associated with
the vCard. the vCard.
7.2.1. FN 6.2.1. FN
Purpose: To specify the formatted text corresponding to the name of Purpose: To specify the formatted text corresponding to the name of
the object the vCard represents. the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (1,n) Cardinality: (1,n)
Special notes: This property is based on the semantics of the X.520 Special notes: This property is based on the semantics of the X.520
Common Name attribute. The property MUST be present in the vCard Common Name attribute. The property MUST be present in the vCard
object. object.
ABNF: ABNF:
FN-param = "VALUE=text" / language-param / pid-param / pref-param FN-param = "VALUE=text" / type-param / language-param / pid-param
/ any-param / pref-param / any-param
FN-value = text FN-value = text
Example: Example:
FN:Mr. John Q. Public\, Esq. FN:Mr. John Q. Public\, Esq.
7.2.2. N 6.2.2. N
Purpose: To specify the components of the name of the object the Purpose: To specify the components of the name of the object the
vCard represents. vCard represents.
Value type: A single structured text value. Each component can have Value type: A single structured text value. Each component can have
multiple values. multiple values.
Cardinality: (0,1) Cardinality: (0,1)
Special note: The structured property value corresponds, in Special note: The structured property value corresponds, in
skipping to change at page 26, line 18 skipping to change at page 25, line 5
list-component = list-component-value *("," list-component-value) list-component = list-component-value *("," list-component-value)
list-component-value = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII list-component-value = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E / %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
Examples: Examples:
N:Public;John,Q.;Mr.;Esq. N:Public;John,Q.;Mr.;Esq.
N:Stevenson;John,Philip,Paul;Dr.;Jr.,M.D.,A.C.P. N:Stevenson;John,Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
7.2.3. NICKNAME 6.2.3. NICKNAME
Purpose: To specify the text corresponding to the nickname of the Purpose: To specify the text corresponding to the nickname of the
object the vCard represents. object the vCard represents.
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Cardinality: (0,n) Cardinality: (0,n)
Special note: The nickname is the descriptive name given instead of Special note: The nickname is the descriptive name given instead of
or in addition to the one belonging to a person, place, or thing. or in addition to the one belonging to a person, place, or thing.
It can also be used to specify a familiar form of a proper name It can also be used to specify a familiar form of a proper name
specified by the FN or N properties. specified by the FN or N properties.
ABNF: ABNF:
NICKNAME-param = "VALUE=text" / language-param / pid-param NICKNAME-param = "VALUE=text" / type-param / language-param
/ pref-param / any-param / pid-param / pref-param / any-param
NICKNAME-value = text-list NICKNAME-value = text-list
Examples: Examples:
NICKNAME:Robbie NICKNAME:Robbie
NICKNAME:Jim,Jimmie NICKNAME:Jim,Jimmie
WORK.NICKNAME:Boss NICKNAME;TYPE=work:Boss
6.2.4. PHOTO
7.2.4. PHOTO
Purpose: To specify an image or photograph information that Purpose: To specify an image or photograph information that
annotates some aspect of the object the vCard represents. annotates some aspect of the object the vCard represents.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding is value is referenced by a URI value, then the default encoding is
used and no explicit ENCODING parameter is needed. used and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary value. It can Value type: A single value. The default is binary value. It can
also be reset to uri value. The uri value can be used to specify also be reset to uri value. The uri value can be used to specify
skipping to change at page 27, line 17 skipping to change at page 26, line 4
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding is value is referenced by a URI value, then the default encoding is
used and no explicit ENCODING parameter is needed. used and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary value. It can Value type: A single value. The default is binary value. It can
also be reset to uri value. The uri value can be used to specify also be reset to uri value. The uri value can be used to specify
a value outside of this MIME entity. a value outside of this MIME entity.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, SHOULD be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF: ABNF:
PHOTO-param = inline-param / refer-param PHOTO-param = inline-param / refer-param / type-param
PHOTO-value = inline-value / refer-value PHOTO-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
PHOTO-param =/ pid-param / pref-param / any-param PHOTO-param =/ pid-param / pref-param / any-param
inline-param = "VALUE=binary" inline-param = "VALUE=binary"
/ encoding-param / encoding-param
/ "TYPE=" type-name "/" subtype-name / "TYPE=" type-name "/" subtype-name
; from [RFC4288] section 4.2 ; from [RFC4288] section 4.2
inline-value = binary inline-value = binary
skipping to change at page 28, line 5 skipping to change at page 26, line 37
Example: Example:
PHOTO;VALUE=uri:http://www.example.com/pub/photos PHOTO;VALUE=uri:http://www.example.com/pub/photos
/jqpublic.gif /jqpublic.gif
PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo
ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv
bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
7.2.5. BDAY 6.2.5. BDAY
Purpose: To specify the birth date of the object the vCard Purpose: To specify the birth date of the object the vCard
represents. represents.
Value type: The default is a single date-and-or-time value. It can Value type: The default is a single date-and-or-time value. It can
also be reset to a single text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
skipping to change at page 28, line 30 skipping to change at page 27, line 18
BDAY-param =/ any-param BDAY-param =/ any-param
Examples: Examples:
BDAY:19960415 BDAY:19960415
BDAY:--0415 BDAY:--0415
BDAY;19531015T231000Z BDAY;19531015T231000Z
BDAY;VALUE=text:circa 1800 BDAY;VALUE=text:circa 1800
7.2.6. DDAY 6.2.6. DDAY
Purpose: To specify the date of death of the object the vCard Purpose: To specify the date of death of the object the vCard
represents. represents.
Value type: The default is a single date-and-or-time value. It can Value type: The default is a single date-and-or-time value. It can
also be reset to a single text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
DDAY-param = "VALUE=" ("date-and-or-time" / "text") DDAY-param = "VALUE=" ("date-and-or-time" / "text")
DDAY-value = date-and-or-time / text DDAY-value = date-and-or-time / text
; Value and parameter MUST match. ; Value and parameter MUST match.
DDAY-param =/ any-param DDAY-param =/ any-param
7.2.7. BIRTH 6.2.7. BIRTH
Purpose: To specify the place of birth of the object the vCard Purpose: To specify the place of birth of the object the vCard
represents. represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
BIRTH-param = "VALUE=text" / language-param / any-param BIRTH-param = "VALUE=text" / language-param / any-param
BIRTH-value = text BIRTH-value = text
Example: Example:
BIRTH:Babies'R'Us Hospital BIRTH:Babies'R'Us Hospital
7.2.8. DEATH 6.2.8. DEATH
Purpose: To specify the place of death of the object the vCard Purpose: To specify the place of death of the object the vCard
represents. represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
DEATH-param = "VALUE=text" / language-param / any-param DEATH-param = "VALUE=text" / language-param / any-param
DEATH-value = text DEATH-value = text
Example: Example:
DEATH:Aboard the Titanic\, near Newfoundland DEATH:Aboard the Titanic\, near Newfoundland
7.2.9. ANNIVERSARY 6.2.9. ANNIVERSARY
Purpose: The date of marriage, or equivalent, of the object the Purpose: The date of marriage, or equivalent, of the object the
vCard represents. vCard represents.
Value type: The default is a single date-and-or-time value. It can Value type: The default is a single date-and-or-time value. It can
also be reset to a single text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
skipping to change at page 30, line 15 skipping to change at page 29, line 5
ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text") ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
ANNIVERSARY-value = date-and-or-time / text ANNIVERSARY-value = date-and-or-time / text
; Value and parameter MUST match. ; Value and parameter MUST match.
ANNIVERSARY-param =/ any-param ANNIVERSARY-param =/ any-param
Examples: Examples:
ANNIVERSARY:19960415 ANNIVERSARY:19960415
7.2.10. SEX 6.2.10. SEX
Purpose: To specify the sex of the object the vCard represents, as Purpose: To specify the sex of the object the vCard represents, as
defined in [ISO.5218.2004]. defined in [ISO.5218.2004].
Value type: A single integer value. Value type: A single integer value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The value 0 stands for "not known", 1 stands for Special notes: The value 0 stands for "not known", 1 stands for
"male", 2 stands for "female", and 9 stands for "not aplicable". "male", 2 stands for "female", and 9 stands for "not applicable".
ABNF: ABNF:
SEX-param = "VALUE=integer" / any-param SEX-param = "VALUE=integer" / any-param
SEX-value = "0" / "1" / "2" / "9" SEX-value = "0" / "1" / "2" / "9"
Example: Example:
SEX:2 SEX:2
7.3. Delivery Addressing Properties 6.3. Delivery Addressing Properties
These types are concerned with information related to the delivery These types are concerned with information related to the delivery
addressing or label for the vCard object. addressing or label for the vCard object.
7.3.1. ADR 6.3.1. ADR
Purpose: To specify the components of the delivery address for the Purpose: To specify the components of the delivery address for the
vCard object. vCard object.
Value type: A single structured text value, separated by the SEMI- Value type: A single structured text value, separated by the SEMI-
COLON character (ASCII decimal 59). COLON character (ASCII decimal 59).
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The structured type value consists of a sequence of Special notes: The structured type value consists of a sequence of
address components. The component values MUST be specified in address components. The component values MUST be specified in
their corresponding position. The structured type value their corresponding position. The structured type value
corresponds, in sequence, to the post office box; the extended corresponds, in sequence, to the post office box; the extended
address (e.g. apartment or suite number); the street address; the address (e.g. apartment or suite number); the street address; the
locality (e.g., city); the region (e.g., state or province); the locality (e.g., city); the region (e.g., state or province); the
postal code; the country name. When a component value is missing, postal code; the country name. When a component value is missing,
the associated component separator MUST still be specified. the associated component separator MUST still be specified.
The text components are separated by the SEMI-COLON character The text components are separated by the SEMI-COLON character
skipping to change at page 31, line 34 skipping to change at page 30, line 26
information that is specific to this address. Its value is the information that is specific to this address. Its value is the
same as that of the GEO property. same as that of the GEO property.
The TZ parameter can be used to indicate time zone information The TZ parameter can be used to indicate time zone information
that is specific to this address. Its value is the same as that that is specific to this address. Its value is the same as that
of the TZ property. of the TZ property.
ABNF: ABNF:
ADR-param = "VALUE=text" / language-param / geo-param / tz-param ADR-param = "VALUE=text" / language-param / geo-param / tz-param
/ pid-param / pref-param / any-param / pid-param / pref-param / type-param / any-param
ADR-value = list-component 6(";" list-component) ADR-value = list-component 6(";" list-component)
geo-param = "GEO=" DQUOTE uri DQUOTE geo-param = "GEO=" DQUOTE uri DQUOTE
tz-param = "TZ=" DQUOTE (text / uri) DQUOTE tz-param = "TZ=" DQUOTE (text / uri) DQUOTE
Example: In this example the post office box and the extended address Example: In this example the post office box and the extended address
are absent. are absent.
ADR;GEO="geo:12.3457,78.910":;;123 Main Street;Any Town;CA ADR;GEO="geo:12.3457,78.910":;;123 Main Street;Any Town;CA
;91921-1234;USA ;91921-1234;USA
7.3.2. LABEL 6.3.2. LABEL
Purpose: To specify the formatted text corresponding to delivery
Purpose: To specify the formatted text corresponding to a delivery
address of the object the vCard represents. address of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property value is formatted text that can be used Special notes: The property value is formatted text that can be used
to present a delivery address label for the vCard object. The to present a delivery address label for the vCard object. The
property can include the "PREF" parameter to indicate the property can include the "PREF" parameter to indicate the
preferred delivery address when more than one address is preferred delivery address when more than one address is
specified. specified.
ABNF: ABNF:
LABEL-param = "VALUE=text" / language-param / pid-param LABEL-param = "VALUE=text" / language-param / pid-param
/ pref-param / any-param / pref-param / type-param / any-param
LABEL-value = text LABEL-value = text
Example: A multi-line address label. Example: A multi-line address label.
LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n
123 Main Street\nAny Town\, CA 91921-1234\nU.S.A. 123 Main Street\nAny Town\, CA 91921-1234\nU.S.A.
7.4. Communications Properties 6.4. Communications Properties
These properties are concerned with information associated with the These properties are concerned with information associated with the
way communications with the object the vCard represents are carried way communications with the object the vCard represents are carried
out. out.
7.4.1. TEL 6.4.1. TEL
Purpose: To specify the telephone number for telephony communication Purpose: To specify the telephone number for telephony communication
with the object the vCard represents. with the object the vCard represents.
Value type: A single URI value. It is expected that the URI scheme Value type: A single URI value. It is expected that the URI scheme
will be "tel", as specified in [RFC3966], but other schemes MAY be will be "tel", as specified in [RFC3966], but other schemes MAY be
used. used.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property is based on the X.520 Telephone Number Special notes: This property is based on the X.520 Telephone Number
attribute. attribute.
The property can include the "PREF" parameter to indicate a The property can include the "PREF" parameter to indicate a
prefered-use telephone number. preferred-use telephone number.
The property can include the parameter "TYPE" to specify intended The property can include the parameter "TYPE" to specify intended
use for the telephone number. The TYPE parameter values can use for the telephone number. The TYPE parameter values can
include: "text" to indicate the telephone number supports text include: "text" to indicate the telephone number supports text
messages, "voice" to indicate a voice telephone number, "fax" to messages, "voice" to indicate a voice telephone number, "fax" to
indicate a facsimile telephone number, "cell" to indicate a indicate a facsimile telephone number, "cell" to indicate a
cellular telephone number, "video" to indicate a video cellular or mobile telephone number, "video" to indicate a video
conferencing telephone number, "pager" to indicate a paging device conferencing telephone number, "pager" to indicate a paging device
telephone number. The default type is "voice". These type telephone number. The default type is "voice". These type
parameter values can be specified as a parameter list (i.e., parameter values can be specified as a parameter list (e.g.,
"TYPE=text;TYPE=voice") or as a value list (i.e., "TYPE=text;TYPE=voice") or as a value list (e.g.,
"TYPE=text,voice"). The default can be overridden to another set "TYPE=text,voice"). The default can be overridden to another set
of values by specifying one or more alternate values. For of values by specifying one or more alternate values. For
example, the default TYPE of "voice" can be reset to a VOICE and example, the default TYPE of "voice" can be reset to a VOICE and
FAX telephone number by the value list "TYPE=voice,fax". FAX telephone number by the value list "TYPE=voice,fax".
ABNF: ABNF:
TEL-param = "VALUE=uri" / type-param / pid-param / pref-param TEL-param = "VALUE=uri" / type-param / pid-param / pref-param
/ any-param / any-param
TEL-value = uri TEL-value = uri
type-value-tel = "text" / "voice" / "fax" / "cell" / "video" type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / iana-token / x-name / "pager" / iana-token / x-name
; type-param-tel MUST NOT be used with a property other than TEL.
Example: Example:
WORK.TEL;PREF=1;TYPE=voice,msg:tel:+1-555-555-5555;ext=5555 TEL;PREF=1;TYPE=voice,msg,home:tel:+1-555-555-5555;ext=5555
HOME.TEL:tel:+33-01-23-45-67 TEL;TYPE=home:tel:+33-01-23-45-67
7.4.2. EMAIL 6.4.2. EMAIL
Purpose: To specify the electronic mail address for communication Purpose: To specify the electronic mail address for communication
with the object the vCard represents. with the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property can include tye "PREF" parameter to Special notes: The property can include tye "PREF" parameter to
indicate a preferred-use email address when more than one is indicate a preferred-use email address when more than one is
specified. specified.
ABNF: ABNF:
EMAIL-param = "VALUE=text" / pid-param / pref-param / any-param EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ any-param
EMAIL-value = addr-spec ; from [RFC5322] section 3.4.1 EMAIL-value = addr-spec ; from [RFC5322] section 3.4.1
Type example: Type example:
WORK.EMAIL:jqpublic@xyz.example.com EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;PREF=1:jane_doe@example.com EMAIL;PREF=1:jane_doe@example.com
7.4.3. IMPP 6.4.3. IMPP
Purpose: To specify the URI for instant messaging and presence Purpose: To specify the URI for instant messaging and presence
protocol communications with the object the vCard represents. protocol communications with the object the vCard represents.
Value type: A single URI. Value type: A single URI.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property may include the "PREF" parameter to Special notes: The property may include the "PREF" parameter to
indicate that this is a preferred address and has the same indicate that this is a preferred address and has the same
semantics as the "PREF" parameter in a TEL property. semantics as the "PREF" parameter in a TEL property.
This property is adapted from [RFC4770], which is made obsolete by
this document.
ABNF: ABNF:
IMPP-param = "VALUE=uri" / pid-param / pref-param / any-param IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param
IMPP-value = uri IMPP-value = uri
Example: Example:
IMPP;PREF=1:xmpp:alice@example.com IMPP;PREF=1:xmpp:alice@example.com
7.4.4. LANG 6.4.4. LANG
Purpose: To specify the language(s) that may be used for contacting Purpose: To specify the language(s) that may be used for contacting
the individual associated with the vCard. the individual associated with the vCard.
Value type: A single language-tag value. Value type: A single language-tag value.
Cardinality: (0,n) Cardinality: (0,n)
ABNF: ABNF:
LANG-param = "VALUE=language-tag" / pid-param / pref-param LANG-param = "VALUE=language-tag" / pid-param / pref-param
/ any-param / type-param / any-param
LANG-value = Language-Tag LANG-value = Language-Tag
Example: Example:
WORK.LANG;PREF=1:en LANG;TYPE=work;PREF=1:en
WORK.LANG;PREF=2:fr LANG;TYPE=work;PREF=2:fr
HOME.LANG=fr LANG;TYPE=home=fr
7.5. Geographical Properties 6.5. Geographical Properties
These properties are concerned with information associated with These properties are concerned with information associated with
geographical positions or regions associated with the object the geographical positions or regions associated with the object the
vCard represents. vCard represents.
7.5.1. TZ 6.5.1. TZ
Purpose: To specify information related to the time zone of the Purpose: To specify information related to the time zone of the
object the vCard represents. object the vCard represents.
Value type: The default is a single text value. It can also be Value type: The default is a single text value. It can also be
reset to a single URI value. reset to a single URI or utc-offset value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: It is expected that names from the public-domain Special notes: It is expected that names from the public-domain
Olson database [TZ-DB] will be used, but this is not a Olson database [TZ-DB] will be used, but this is not a
restriction. restriction.
Efforts are currently being directed at creating a standard URI Efforts are currently being directed at creating a standard URI
scheme for expressing time zone information. Usage of such a scheme for expressing time zone information. Usage of such a
scheme would ensure a high level of interoperability between scheme would ensure a high level of interoperability between
implementations that support it. implementations that support it.
Note that utc-offset values SHOULD NOT be used because the UTC
offset varies with time - not just because of the usual DST shifts
that occur in may regions, but often entire regions will "re-base"
their offset entirely. The actual offset may be +/- 1 hour (or
perhaps a little more) than the one given.
ABNF: ABNF:
TZ-param = "VALUE=" ("text" / "uri") TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / uri TZ-value = text / uri / utc-offset
; Value and parameter must match ; Value and parameter must match
TZ-param =/ pid-param / pref-param / any-param TZ-param =/ pid-param / pref-param / type-param / any-param
Type examples: Type examples:
TZ:-0500; EST; Raleigh/North America TZ:-0500; EST; Raleigh/North America
;This example has a single value, not a structure text value. ;This example has a single value, not a structure text value.
7.5.2. GEO 6.5.2. GEO
Purpose: To specify information related to the global positioning of Purpose: To specify information related to the global positioning of
the object the vCard represents. the object the vCard represents.
Value type: A single URI. Value type: A single URI.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The "geo" URI scheme [I-D.mayrhofer-geo-uri] is Special notes: The "geo" URI scheme [I-D.ietf-geopriv-geo-uri] is
particularly well-suited for this property, but other schemes MAY particularly well-suited for this property, but other schemes MAY
be used. be used.
ABNF: ABNF:
GEO-param = "VALUE=uri" / pid-param / pref-param / any-param GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param
GEO-value = uri GEO-value = uri
Example: Example:
GEO:geo:37.386013,-122.082932 GEO:geo:37.386013,-122.082932
7.6. Organizational Properties 6.6. Organizational Properties
These properties are concerned with information associated with These properties are concerned with information associated with
characteristics of the organization or organizational units of the characteristics of the organization or organizational units of the
object the vCard represents. object the vCard represents.
7.6.1. TITLE 6.6.1. TITLE
Purpose: To specify the position or job of the object the vCard Purpose: To specify the position or job of the object the vCard
represents. represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property is based on the X.520 Title attribute. Special notes: This property is based on the X.520 Title attribute.
ABNF: ABNF:
TITLE-param = "VALUE=text" / language-param / pid-param TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / any-param / pref-param / type-param / any-param
TITLE-value = text TITLE-value = text
Example: Example:
TITLE:Research Scientist TITLE:Research Scientist
7.6.2. ROLE 6.6.2. ROLE
Purpose: To specify the function or part played in a particular Purpose: To specify the function or part played in a particular
situation by the object the vCard represents. situation by the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property is based on the X.520 Business Category Special notes: This property is based on the X.520 Business Category
explanatory attribute. This property is included as an explanatory attribute. This property is included as an
organizational type to avoid confusion with the semantics of the organizational type to avoid confusion with the semantics of the
TITLE property and incorrect usage of that property when the TITLE property and incorrect usage of that property when the
semantics of this property is intended. semantics of this property is intended.
ABNF: ABNF:
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param / type-param / any-param
ROLE-value = text ROLE-value = text
Example: Example:
ROLE:Project Leader ROLE:Project Leader
7.6.3. LOGO 6.6.3. LOGO
Purpose: To specify a graphic image of a logo associated with the Purpose: To specify a graphic image of a logo associated with the
object the vCard represents. object the vCard represents.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of value is referenced by a URI value, then the default encoding of
8bit is used and no explicit ENCODING parameter is needed. 8bit is used and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary value. It can Value type: A single value. The default is binary value. It can
also be reset to uri value. The uri value can be used to specify also be reset to uri value. The uri value can be used to specify
a value outside of this MIME entity. a value outside of this MIME entity.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, SHOULD be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF: ABNF:
LOGO-param = inline-param / refer-param LOGO-param = inline-param / refer-param
LOGO-value = inline-value / refer-value LOGO-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
LOGO-param =/ language-param / pid-param / pref-param / any-param LOGO-param =/ language-param / pid-param / pref-param / type-param
/ any-param
Example: Example:
LOGO;VALUE=uri:http://www.example.com/pub/logos/abccorp.jpg LOGO;VALUE=uri:http://www.example.com/pub/logos/abccorp.jpg
LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
7.6.4. ORG 6.6.4. ORG
Purpose: To specify the organizational name and units associated Purpose: To specify the organizational name and units associated
with the vCard. with the vCard.
Value type: A single structured text value consisting of components Value type: A single structured text value consisting of components
separated the SEMI-COLON character (ASCII decimal 59). separated the SEMI-COLON character (ASCII decimal 59).
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property is based on the X.520 Organization Name Special notes: The property is based on the X.520 Organization Name
and Organization Unit attributes. The property value is a and Organization Unit attributes. The property value is a
structured type consisting of the organization name, followed by structured type consisting of the organization name, followed by
zero or more levels of organizational unit names. zero or more levels of organizational unit names.
ABNF: ABNF:
ORG-param = "VALUE=text" / language-param / pid-param / pref-param ORG-param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param / type-param / any-param
ORG-value = component *(";" component) ORG-value = component *(";" component)
component = "\\" / "\;" / "\n" / WSP / NON-ASCII component = "\\" / "\;" / "\n" / WSP / NON-ASCII
/ %x21-3A / %x3C-5B / %x5D-7E / %x21-3A / %x3C-5B / %x5D-7E
Example: A property value consisting of an organizational name, Example: A property value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name. organizational unit #1 name and organizational unit #2 name.
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC\, Inc.;North American Division;Marketing
7.6.5. MEMBER 6.6.5. MEMBER
Purpose: To include a member in the group this vCard represents. Purpose: To include a member in the group this vCard represents.
Value tpe: A single URI. It MAY refer to something other than a Value type: A single URI. It MAY refer to something other than a
vCard object. For example, an e-mail distribution list could vCard object. For example, an e-mail distribution list could
employ the "mailto" URI scheme for efficiency. employ the "mailto" URI scheme for efficiency.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property MUST NOT be present unless the value of Special notes: This property MUST NOT be present unless the value of
the KIND property is "group". the KIND property is "group".
ABNF: ABNF:
skipping to change at page 40, line 5 skipping to change at page 39, line 5
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:group KIND:group
FN:Funky distribution list FN:Funky distribution list
MEMBER:mailto:subscriber1@example.com MEMBER:mailto:subscriber1@example.com
MEMBER:xmpp:subscriber2@example.com MEMBER:xmpp:subscriber2@example.com
MEMBER:sip:subscriber3@example.com MEMBER:sip:subscriber3@example.com
MEMBER:tel:+1-418-555-5555 MEMBER:tel:+1-418-555-5555
END:VCARD END:VCARD
7.6.6. RELATED 6.6.6. RELATED
Purpose: To specify a relationship the individual this vCard Purpose: To specify a relationship between another person and the
represents has with another. individual represented by this vCard.
Value type: A single URI. It can also be reset to a single text Value type: A single URI. It can also be reset to a single text
value. The text value can be used to specify textual information. value. The text value can be used to specify textual information.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The TYPE parameter MAY be used to characterize the Special notes: The TYPE parameter MAY be used to characterize the
related individual. The understood types are: related individual. The understood types are:
* "parent" means that the related individual is the parent of the * "parent" means that the related individual is the parent of the
individual this vCard represents. individual this vCard represents.
* "child" means the opposite of "parent". * "child" means that the related individual is the child of the
individual this vCard represents. Note that the parent/child
relationship does not need to be biological.
* "sibling" means that the two individuals are siblings. * "sibling" means that the two individuals are siblings.
* "spouse" for a spouse, domestic partner, or similar relation. * "spouse" for a spouse, domestic partner, or similar relation.
* "family" for any other family relationship. * "family" for any other family relationship.
* "friend" for a friend. * "friend" for a friend.
* "supervisor" means that the related individual is the direct * "supervisor" means that the related individual is the direct
skipping to change at page 40, line 47 skipping to change at page 39, line 49
* "assistant" for an assistant or secretary. * "assistant" for an assistant or secretary.
* "colleague" for any other workplace relationship. * "colleague" for any other workplace relationship.
* "agent" for a person who will act on behalf of the individual * "agent" for a person who will act on behalf of the individual
or resource associated with the vCard. or resource associated with the vCard.
* "emergency" indicates an emergency contact. * "emergency" indicates an emergency contact.
Other types may be registered to IANA as described in Other types may be registered to IANA as described in
Section 11.2, and private extensions starting with "X-" may be Section 10.2, and private extensions starting with "X-" may be
used. used.
ABNF: ABNF:
RELATED-param = "VALUE=" ("uri" / "text") RELATED-param = "VALUE=" ("uri" / "text")
RELATED-value = uri / text RELATED-value = uri / text
; Parameter and value MUST match. ; Parameter and value MUST match.
RELATED-param =/ type-param / pid-param / pref-param / any-param RELATED-param =/ type-param / pid-param / pref-param / type-param
/ any-param
type-param-related = "parent" / "child" / "sibling" / "spouse" type-param-related = "parent" / "child" / "sibling" / "spouse"
/ "family" / "friend" / "supervisor" / "family" / "friend" / "supervisor"
/ "supervisee" / "assistant" / "colleague" / "supervisee" / "assistant" / "colleague"
/ "agent" / "emergency" / iana-token / x-name / "agent" / "emergency" / iana-token / x-name
; type-param-related MUST NOT be used with a property other than
; RELATED.
Examples: Examples:
RELATED;TYPE=manager:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=manager:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
RELATED;TYPE=assistant:http://example.com/directory/jdoe.vcf RELATED;TYPE=assistant:http://example.com/directory/jdoe.vcf
RELATED;TYPE=agent;VALUE=text:Please contact my assistant Jane Doe RELATED;TYPE=agent;VALUE=text:Please contact my assistant Jane Doe
for any inquiries. for any inquiries.
7.7. Explanatory Properties 6.7. Explanatory Properties
These properties are concerned with additional explanations, such as These properties are concerned with additional explanations, such as
that related to informational notes or revisions specific to the that related to informational notes or revisions specific to the
vCard. vCard.
7.7.1. CATEGORIES 6.7.1. CATEGORIES
Purpose: To specify application category information about the Purpose: To specify application category information about the
vCard. vCard. Also known as "tags".
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Cardinality: (0,n) Cardinality: (0,n)
ABNF: ABNF:
CATEGORIES-param = "VALUE=text" / pid-param / pref-param CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ any-param / type-param / any-param
CATEGORIES-value = text-list CATEGORIES-value = text-list
Example: Example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
7.7.2. NOTE 6.7.2. NOTE
Purpose: To specify supplemental information or a comment that is Purpose: To specify supplemental information or a comment that is
associated with the vCard. associated with the vCard.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property is based on the X.520 Description Special notes: The property is based on the X.520 Description
attribute. attribute.
ABNF: ABNF:
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param / type-param / any-param
NOTE-value = text NOTE-value = text
Example: Example:
NOTE:This fax number is operational 0800 to 1715 NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri. EST\, Mon-Fri.
7.7.3. PRODID 6.7.3. PRODID
Purpose: To specify the identifier for the product that created the Purpose: To specify the identifier for the product that created the
vCard object. vCard object.
Type value: A single text value. Type value: A single text value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: Implementations SHOULD use a method such as that Special notes: Implementations SHOULD use a method such as that
specified for Formal Public Identifiers in [ISO9070] or for specified for Formal Public Identifiers in [ISO9070] or for
Universal Resource Names in [RFC3406] to assure that the text Universal Resource Names in [RFC3406] to ensure that the text
value is unique. value is unique.
ABNF: ABNF:
PRODID-param = "VALUE=text" / any-param PRODID-param = "VALUE=text" / any-param
PRODID-value = text PRODID-value = text
Example: Example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
7.7.4. REV 6.7.4. REV
Purpose: To specify revision information about the current vCard. Purpose: To specify revision information about the current vCard.
Value type: A single timestamp value. Value type: A single timestamp value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The value distinguishes the current revision of the Special notes: The value distinguishes the current revision of the
information in this vCard for other renditions of the information. information in this vCard for other renditions of the information.
ABNF: ABNF:
REV-param = "VALUE=timestamp" / any-param REV-param = "VALUE=timestamp" / any-param
REV-value = timestamp REV-value = timestamp
Example: Example:
REV:19951031T222710Z REV:19951031T222710Z
7.7.5. SORT-STRING 6.7.5. SORT-STRING
Purpose: To specify the family name or given name text to be used Purpose: To specify the family name or given name text to be used
for national-language-specific sorting of the FN and N types. for national-language-specific sorting of the FN and N types.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The sort string is used to provide family name or Special notes: The sort string is used to provide family name or
given name text that is to be used in locale- or national- given name text that is to be used in sorting of the formatted
language- specific sorting of the formatted name and structured name and structured name types in the context of a particular
name types. Without this information, sorting algorithms could locale or national language. Without this information, sorting
incorrectly sort this vCard within a sequence of sorted vCards. algorithms could incorrectly sort this vCard within a sequence of
When this property is present in a vCard, then this family name or sorted vCards. When this property is present in a vCard, then
given name value is used for sorting the vCard. this family name or given name value is used for sorting the
vCard.
ABNF: ABNF:
SORT-STRING-param = "VALUE=text" / any-param SORT-STRING-param = "VALUE=text" / any-param
SORT-STRING-value = text SORT-STRING-value = text
Examples: For the case of family name sorting, the following examples Examples: For the case of family name sorting, the following examples
define common sort string usage with the FN and N properties. define common sort string usage with the FN and N properties.
FN:Rene van der Harten FN:Rene van der Harten
skipping to change at page 44, line 25 skipping to change at page 43, line 25
SORT-STRING:Koura SORT-STRING:Koura
FN:Oscar del Pozo FN:Oscar del Pozo
N:del Pozo Triscon;Oscar N:del Pozo Triscon;Oscar
SORT-STRING:Pozo SORT-STRING:Pozo
FN:Chistine d'Aboville FN:Chistine d'Aboville
N:d'Aboville;Christine N:d'Aboville;Christine
SORT-STRING:Aboville SORT-STRING:Aboville
7.7.6. SOUND 6.7.6. SOUND
Purpose: To specify a digital sound content information that Purpose: To specify a digital sound content information that
annotates some aspect of the vCard. This property is often used annotates some aspect of the vCard. This property is often used
to specify the proper pronunciation of the name property value of to specify the proper pronunciation of the name property value of
the vCard. the vCard.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of value is referenced by a URI value, then the default encoding of
8bit is used and no explicit ENCODING parameter is needed. 8bit is used and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary value. It can Value type: A single value. The default is binary value. It can
also be reset to uri value. The uri value can be used to specify also be reset to uri value. The uri value can be used to specify
a value outside of this MIME entity. a value outside of this MIME entity.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the audio format type. The TYPE parameter value MUST be specify the audio format type. The TYPE parameter value MUST be
an audio media type as specified in [RFC4288]. The full media an audio media type as specified in [RFC4288]. The full media
type name, including the "audio/" prefix, should be used. type name, including the "audio/" prefix, SHOULD be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF: ABNF:
SOUND-param = inline-param / refer-param SOUND-param = inline-param / refer-param
SOUND-value = inline-value / refer-value SOUND-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
SOUND-param =/ language-param / pid-param / pref-param / any-param SOUND-param =/ language-param / pid-param / pref-param / type-param
/ any-param
Example: Example:
SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8. SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@example.com 19960229T080000.xyzMail@example.com
SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
7.7.7. UID 6.7.7. UID
Purpose: To specify a value that represents a globally unique Purpose: To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated identifier corresponding to the individual or resource associated
with the vCard. with the vCard.
Value type: A single URI value. Value type: A single URI value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: This property is used to uniquely identify the object Special notes: This property is used to uniquely identify the object
skipping to change at page 45, line 45 skipping to change at page 44, line 46
ABNF: ABNF:
UID-param = "VALUE=uri" / any-param UID-param = "VALUE=uri" / any-param
UID-value = uri UID-value = uri
Example: Example:
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
7.7.8. CLIENTPIDMAP 6.7.8. CLIENTPIDMAP
Purpose: To give a global meaning to a local PID source identifier. Purpose: To give a global meaning to a local PID source identifier.
Value type: A semicolon-separated pair of values. The first field Value type: A semicolon-separated pair of values. The first field
is a small integer corresponding to the second field of a PID is a small integer corresponding to the second field of a PID
parameter instance. The second field is a URI. The "uuid" URN parameter instance. The second field is a URI. The "uuid" URN
namespace defined in [RFC4122] is particularly well-suited to this namespace defined in [RFC4122] is particularly well-suited to this
task, but other URI schemes MAY be used. task, but other URI schemes MAY be used.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: PID source identifiers (the source identifier is the Special notes: PID source identifiers (the source identifier is the
second field in a PID parameter instance) are small integers that second field in a PID parameter instance) are small integers that
only have significance within the scope of a single vCard only have significance within the scope of a single vCard
instance. Each distinct source identifier present in a vCard MUST instance. Each distinct source identifier present in a vCard MUST
have an associated CLIENTPIDMAP. See Section 8 for more details have an associated CLIENTPIDMAP. See Section 7 for more details
on the usage of CLIENTPIDMAP. on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive. Zero is not PID source identifiers MUST be strictly positive. Zero is not
allowed. allowed.
As a special exception, the PID parameter MUST NOT be applied to As a special exception, the PID parameter MUST NOT be applied to
this property. this property.
ABNF: ABNF:
CLIENTPIDMAP-param = any-param CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" uri CLIENTPIDMAP-value = 1*DIGIT ";" uri
Example: Example:
TEL;PID=3.1,4.2:tel:+1-555-555-5555 TEL;PID=3.1,4.2:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5 CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
7.7.9. URL 6.7.9. URL
Purpose: To specify a uniform resource locator associated with the Purpose: To specify a uniform resource locator associated with the
object that the vCard refers to. object that the vCard refers to.
Cardinality: (0,n) Cardinality: (0,n)
Value type: A single uri value. Value type: A single uri value.
ABNF: ABNF:
URL-param = "VALUE=uri" / pid-param / pref-param / any-param URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param
URL-value = uri URL-value = uri
Example: Example:
URL:http://example.org/restaurant.french/~chezchic.html URL:http://example.org/restaurant.french/~chezchic.html
7.7.10. VERSION 6.7.10. VERSION
Purpose: To specify the version of the vCard specification used to Purpose: To specify the version of the vCard specification used to
format this vCard. format this vCard.
Value type: A single text value. Value type: A single text value.
Cardinality: (1,1) Cardinality: (1,1)
Special notes: The property MUST be present in the vCard object. Special notes: The property MUST be present in the vCard object.
The value MUST be "4.0" if the vCard corresponds to this The value MUST be "4.0" if the vCard corresponds to this
skipping to change at page 47, line 27 skipping to change at page 46, line 31
ABNF: ABNF:
VERSION-param = "VALUE=text" / any-param VERSION-param = "VALUE=text" / any-param
VERSION-value = "4.0" VERSION-value = "4.0"
Example: Example:
VERSION:4.0 VERSION:4.0
7.8. Security Properties 6.8. Security Properties
These properties are concerned with the security of communication These properties are concerned with the security of communication
pathways or access to the vCard. pathways or access to the vCard.
7.8.1. CLASS 6.8.1. CLASS
Purpose: To specify the access classification for a vCard object. Purpose: To specify the access classification for a vCard object.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: An access classification is only one component of the Special notes: An access classification is only one component of the
general security model for a directory service. The general security model for a directory service. The
classification attribute provides a method of capturing the intent classification attribute provides a method of capturing the intent
skipping to change at page 48, line 26 skipping to change at page 47, line 30
/ x-name / x-name
Examples: Examples:
CLASS:PUBLIC CLASS:PUBLIC
CLASS:PRIVATE CLASS:PRIVATE
CLASS:CONFIDENTIAL CLASS:CONFIDENTIAL
7.8.2. KEY 6.8.2. KEY
Purpose: To specify a public key or authentication certificate Purpose: To specify a public key or authentication certificate
associated with the object that the vCard represents. associated with the object that the vCard represents.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is a text value, then the default encoding of 8bit is used value is a text value, then the default encoding of 8bit is used
and no explicit ENCODING parameter is needed. and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary. It can also be Value type: A single value. The default is binary. It can also be
skipping to change at page 49, line 5 skipping to change at page 48, line 7
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the public key or authentication certificate format. The specify the public key or authentication certificate format. The
TYPE parameter value MUST be a media type as specified in TYPE parameter value MUST be a media type as specified in
[RFC4288]. [RFC4288].
ABNF: ABNF:
KEY-param = inline-param / refer-param KEY-param = inline-param / refer-param
KEY-value = inline-value / refer-value KEY-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
KEY-param =/ pid-param / pref-param / any-param KEY-param =/ pid-param / pref-param / type-param / any-param
Examples: Examples:
KEY;VALUE=uri:http://www.example.com/keys/jdoe KEY;VALUE=uri:http://www.example.com/keys/jdoe
KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN
mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g
7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8 7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
7.9. Calendar Properties 6.9. Calendar Properties
These properties are further specified in [RFC2739]. These properties are further specified in [RFC2739].
7.9.1. FBURL 6.9.1. FBURL
Purpose: To specify the URI for a user's busy time in a vCard Purpose: To specify the URI for a user's busy time in a vCard
object. object.
Value type: A single URI value. Value type: A single URI value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: Where multiple FBURL properties are specified, the Special notes: Where multiple FBURL properties are specified, the
default FBURL property is indicated with the PREF parameter. The default FBURL property is indicated with the PREF parameter. The
FTP or HTTP type of URI points to an iCalendar object associated FTP or HTTP type of URI points to an iCalendar object associated
with a snapshot of the last six weeks of the user's busy time with a snapshot of the last six weeks of the user's busy time
data. If the iCalendar object is represented as a file or data. If the iCalendar object is represented as a file or
document, it's file type should be "ifb". document, its file type should be "ifb".
ABNF: ABNF:
FBURL-param = "VALUE=uri" / pid-param / pref-param / any-param FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param
FBURL-value = uri FBURL-value = uri
Examples: Examples:
FBURL;PREF=1:http://www.example.com/busy/janedoe FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL:FTP://ftp.example.com/busy/project-a.ifb FBURL:FTP://ftp.example.com/busy/project-a.ifb
7.9.2. CALADRURI 6.9.2. CALADRURI
Purpose: To specify the location to which an event request should be Purpose: To specify the location to which an event request should be
sent for the user. sent for the user.
Value type: A single URI value. Value type: A single URI value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: Where multiple CALADRURI properties are specified, Special notes: Where multiple CALADRURI properties are specified,
the default CALADRURI property is indicated with the PREF the default CALADRURI property is indicated with the PREF
parameter. parameter.
ABNF: ABNF:
CALADRURI-param = "VALUE=uri" / pid-param / pref-param / any-param CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param
CALADRURI-value = uri CALADRURI-value = uri
Example: Example:
CALADRURI;PREF=1:mailto:janedoe@example.com CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe CALADRURI:http://example.com/calendar/jdoe
7.9.3. CALURI 6.9.3. CALURI
Purpose: To specify the URI for a user's calendar in a vCard object. Purpose: To specify the URI for a user's calendar in a vCard object.
Value type: A single URI value. Value type: A single URI value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: Where multiple CALURI properties are specified, the Special notes: Where multiple CALURI properties are specified, the
default CALURI property is indicated with the PREF parameter. The default CALURI property is indicated with the PREF parameter. The
property should contain a URI pointing to an iCalendar object property should contain a URI pointing to an iCalendar object
associated with a snapshot of the user's calendar store. If the associated with a snapshot of the user's calendar store. If the
iCalendar object is represented as a file or document, it's file iCalendar object is represented as a file or document, its file
type should be "ics". type should be "ics".
ABNF: ABNF:
CALURI-param = "VALUE=uri" / pid-param / pref-param / any-param CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param
CALURI-value = uri CALURI-value = uri
Examples: Examples:
CALURI;PREF=1:http://cal.example.com/calA CALURI;PREF=1:http://cal.example.com/calA
CALURI:ftp://ftp.example.com/calA.ics CALURI:ftp://ftp.example.com/calA.ics
7.10. Extended Properties and Parameters 6.10. Extended Properties and Parameters
The properties and parameters defined by this document can be The properties and parameters defined by this document can be
extended. Non-standard, private properties and parameters with a extended. Non-standard, private properties and parameters with a
name starting with "X-" may be defined bilaterally between two name starting with "X-" may be defined bilaterally between two
cooperating agents without outside registration or standardization. cooperating agents without outside registration or standardization.
8. Synchronization 7. Synchronization
vCard data often needs to be synchronized between devices. In this vCard data often needs to be synchronized between devices. In this
context, synchronization is defined as the intelligent merging of two context, synchronization is defined as the intelligent merging of two
representations of the same object. vCard 4.0 includes mechanisms to representations of the same object. vCard 4.0 includes mechanisms to
aid this process. aid this process.
8.1. Mechanisms 7.1. Mechanisms
Two mechanisms are available: the UID property is used to match Two mechanisms are available: the UID property is used to match
multiple instances of the same vCard, while the PID parameter is used multiple instances of the same vCard, while the PID parameter is used
to match multiple instances of the same property. to match multiple instances of the same property.
The term "matching" is used here to mean recognizing that two The term "matching" is used here to mean recognizing that two
instances are in fact representations of the same object. For instances are in fact representations of the same object. For
example, a single vCard that is shared with someone results in two example, a single vCard that is shared with someone results in two
vCard instances. After they have evolved separately, they still vCard instances. After they have evolved separately, they still
represent the same object, and therefore may be matched by a represent the same object, and therefore may be matched by a
synchronization engine. synchronization engine.
8.1.1. Matching vCard Instances 7.1.1. Matching vCard Instances
vCard instances for which the UID properties (Section 7.7.7) are vCard instances for which the UID properties (Section 6.7.7) are
equivalent MUST be matched. Equivalence is determined as specified equivalent MUST be matched. Equivalence is determined as specified
in [RFC3986], Section 6. in [RFC3986], Section 6.
In all other cases, vCard instances MAY be matched at the discretion In all other cases, vCard instances MAY be matched at the discretion
of the synchronization engine. of the synchronization engine.
8.1.2. Matching Property Instances 7.1.2. Matching Property Instances
Property instances belonging to unmatched vCards MUST NOT be matched. Property instances belonging to unmatched vCards MUST NOT be matched.
Property instances whose name (e.g. EMAIL, TEL, etc.) is not the Property instances whose name (e.g. EMAIL, TEL, etc.) is not the
same MUST NOT be matched. same MUST NOT be matched.
Property instances whose name is CLIENTPIDMAP are handled separately Property instances whose name is CLIENTPIDMAP are handled separately
and MUST NOT be matched. The synchronization MUST ensure that there and MUST NOT be matched. The synchronization MUST ensure that there
is consistency of CLIENTPIDMAPs among matched vCard instances. is consistency of CLIENTPIDMAPs among matched vCard instances.
Property instances belonging to matched vCards, whose name is the Property instances belonging to matched vCards, whose name is the
same, and whose maximum cardinality is 1 MUST be matched. same, and whose maximum cardinality is 1 MUST be matched.
Property instances belonging to matched vCards, whose name is the Property instances belonging to matched vCards, whose name is the
same, and whose PID parameters match MUST be matched. See same, and whose PID parameters match MUST be matched. See
Section 8.1.3 for details on PID matching. Section 7.1.3 for details on PID matching.
In all other cases, property instances MAY be matched at the In all other cases, property instances MAY be matched at the
discretion of the synchronization engine. discretion of the synchronization engine.
8.1.3. PID Matching 7.1.3. PID Matching
Two PID values for which the first fields are equivalent represent Two PID values for which the first fields are equivalent represent
the same local value. the same local value.
Two PID values representing the same local value and for which the Two PID values representing the same local value and for which the
second fields point to CLIENTPIDMAP properties whose second field second fields point to CLIENTPIDMAP properties whose second field
URIs are equivalent (as specified in [RFC3986], Section 6) also URIs are equivalent (as specified in [RFC3986], Section 6) also
represent the same global value. represent the same global value.
PID parameters for which at least one pair of their values represent PID parameters for which at least one pair of their values represent
skipping to change at page 52, line 46 skipping to change at page 52, line 5
CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
EMAIL;PID=5.1,6.2:john@example.com EMAIL;PID=5.1,6.2:john@example.com
CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527 CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
END:VCARD END:VCARD
8.2. Example 7.2. Example
8.2.1. Creation 7.2.1. Creation
The following simple vCard is first created on a given device. The following simple vCard is first created on a given device.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe FN:J. Doe
EMAIL;PID=1.1:jdoe@example.com EMAIL;PID=1.1:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD END:VCARD
This new vCard is assigned the UID This new vCard is assigned the UID
"urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating "urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating
device. The EMAIL property is assigned PID 1, and this PID is given device. The EMAIL property is assigned PID 1, and this PID is given
global context by associating it with global context by associating it with
"urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which represents the "urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which represents the
creating device. The FN property has no PID because it is forbidden creating device. The FN property has no PID because it is forbidden
by its maximum cardinality of 1. by its maximum cardinality of 1.
8.2.2. Initial Sharing 7.2.2. Initial Sharing
This vCard is shared with a second device. Upon inspecting the UID This vCard is shared with a second device. Upon inspecting the UID
property, the second device understands that this is a new vCard property, the second device understands that this is a new vCard
(i.e. unmatched) and thus the synchronization results in a simple (i.e. unmatched) and thus the synchronization results in a simple
copy. copy.
8.2.3. Adding and Sharing a Property 7.2.3. Adding and Sharing a Property
A new phone number is created on the first device, then the vCard is A new phone number is created on the first device, then the vCard is
shared with the second device. This is what the second device shared with the second device. This is what the second device
receives: receives:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe FN:J. Doe
EMAIL;PID=1.1:jdoe@example.com EMAIL;PID=1.1:jdoe@example.com
skipping to change at page 54, line 16 skipping to change at page 53, line 23
The TEL property in the new vCard is not matched to any in the stored The TEL property in the new vCard is not matched to any in the stored
vCard because no property in the stored vCard has the same name. vCard because no property in the stored vCard has the same name.
Therefore, this property is copied from the new vCard to the stored Therefore, this property is copied from the new vCard to the stored
vCard. vCard.
The CLIENTPIDMAP property is handled separately by the The CLIENTPIDMAP property is handled separately by the
synchronization engine. It ensures that it is consistent with the synchronization engine. It ensures that it is consistent with the
stored one. If it was not, the results would be up to the stored one. If it was not, the results would be up to the
synchronization engine, and thus undefined by this document. synchronization engine, and thus undefined by this document.
8.2.4. Simultaneous Editing 7.2.4. Simultaneous Editing
A new email address and a new phone number are added to the vCard on A new email address and a new phone number are added to the vCard on
each of the two devices, and then a new synchronization event each of the two devices, and then a new synchronization event
happens. Here are the vCards that are communicated to each other: happens. Here are the vCards that are communicated to each other:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe FN:J. Doe
EMAIL;PID=1.1:jdoe@example.com EMAIL;PID=1.1:jdoe@example.com
skipping to change at page 55, line 11 skipping to change at page 54, line 17
"urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee". "urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".
The new EMAIL properties are unmatched on both sides since the PID The new EMAIL properties are unmatched on both sides since the PID
global value is new in both cases. The sync thus results in a copy global value is new in both cases. The sync thus results in a copy
on both sides. on both sides.
Although the situation appears to be the same for the TEL properties, Although the situation appears to be the same for the TEL properties,
in this case the synchronization engine is particularly smart and in this case the synchronization engine is particularly smart and
matches the two new TEL properties even though their PID global matches the two new TEL properties even though their PID global
values are different. Note that in this case, the rules of section values are different. Note that in this case, the rules of section
Section 8.1.2 state that two properties may be matched at the Section 7.1.2 state that two properties may be matched at the
discretion of the synchronization engine. Therefore, the two discretion of the synchronization engine. Therefore, the two
properties are merged. properties are merged.
All this results in the following vCard which is stored on both All this results in the following vCard which is stored on both
devices: devices:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe FN:J. Doe
EMAIL;PID=1.1:jdoe@example.com EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com EMAIL;PID=2.1:boss@example.com
EMAIL;PID=2.2:ceo@example.com EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1:tel:+1-555-555-5555 TEL;PID=1.1:tel:+1-555-555-5555
TEL;PID=2.1,2.2:tel:+1-666-666-6666 TEL;PID=2.1,2.2:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD END:VCARD
8.2.5. Global Context Simplification 7.2.5. Global Context Simplification
The two devices finish their synchronization procedure by simplifying The two devices finish their synchronization procedure by simplifying
their global contexts. Since they haven't talked to any other their global contexts. Since they haven't talked to any other
device, the following vCard is for all purposes equivalent to the device, the following vCard is for all purposes equivalent to the
above. It is also shorter. above. It is also shorter.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe FN:J. Doe
skipping to change at page 56, line 7 skipping to change at page 55, line 22
TEL;PID=1.1:tel:+1-555-555-5555 TEL;PID=1.1:tel:+1-555-555-5555
TEL;PID=2.1:tel:+1-666-666-6666 TEL;PID=2.1:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD END:VCARD
The details of global context simplification are unspecified by this The details of global context simplification are unspecified by this
document. They are left up to the synchronization engine. This document. They are left up to the synchronization engine. This
example is merely intended to illustrate the possibility, which example is merely intended to illustrate the possibility, which
investigating would be, in the authors' opinion, worthwhile. investigating would be, in the authors' opinion, worthwhile.
9. Example: Authors' vCards 8. Example: Authors' vCards
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Simon Perreault FN:Simon Perreault
N:Perreault;Simon;;ing. jr,M.Sc. N:Perreault;Simon;;ing. jr,M.Sc.
BDAY:--0203 BDAY:--0203
ANNIVERSARY:20090808T1430-0500 ANNIVERSARY:20090808T1430-0500
SEX:1 SEX:1
LANG;PREF=1:fr LANG;PREF=1:fr
LANG;PREF=2:en LANG;PREF=2:en
WORK.ORG:Viagenie ORG;TYPE=work:Viagenie
WORK.ADR:;Suite 625;2600 boul. Laurier; ADR;TYPE=work:;Suite 625;2600 boul. Laurier;
Quebec;QC;G1V 4W1;Canada Quebec;QC;G1V 4W1;Canada
WORK.TEL;TYPE=voice;PREF=1:tel:+1-418-656-9254;ext=102 TEL;TYPE=work,voice;PREF=1:tel:+1-418-656-9254;ext=102
WORK.TEL;TYPE=cell,voice,video,text:tel:+1-418-262-6501 TEL;TYPE=work,cell,voice,video,text:tel:+1-418-262-6501
WORK.TEL;TYPE=fax:tel:+1-418-656-9257 TEL;TYPE=work,fax:tel:+1-418-656-9257
WORK.EMAIL:simon.perreault@viagenie.ca EMAIL;TYPE=work:simon.perreault@viagenie.ca
WORK.GEO:geo:46.772673,-71.282945 GEO;TYPE=work:geo:46.772673,-71.282945
WORK.KEY;VALUE=uri:http://www.viagenie.ca/simon.perreault/simon.asc KEY;TYPE=work;VALUE=uri:
http://www.viagenie.ca/simon.perreault/simon.asc
TZ:-0500 TZ:-0500
CLASS:PUBLIC CLASS:PUBLIC
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Pete Resnick FN:Pete Resnick
N:Resnick;Pete;; N:Resnick;Pete;;
SEX:1 SEX:1
WORK.ORG:QUALCOMM Incorporated ORG;TYPE=work:QUALCOMM Incorporated
WORK.ADR:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
WORK.TEL;TYPE=voice:tel:+1-858-651-4478 TEL;TYPE=work,voice:tel:+1-858-651-4478
WORK.EMAIL:presnick@qualcomm.com EMAIL;TYPE=work:presnick@qualcomm.com
WORK.URL:http://www.qualcomm.com/~presnick/ URL;TYPE=work:http://www.qualcomm.com/~presnick/
END:VCARD END:VCARD
10. Security Considerations 9. Security Considerations
o Internet mail is subject to many well known security attacks, o Internet mail is often used to transport vCards and is subject to
including monitoring, replay, and forgery. Care should be taken many well known security attacks, including monitoring, replay,
by any directory service in allowing information to leave the and forgery. Care should be taken by any directory service in
scope of the service itself, where any access controls can no allowing information to leave the scope of the service itself,
longer be guaranteed. Applications should also take care to where any access controls can no longer be guaranteed.
display directory data in a "safe" environment (e.g., PostScript- Applications should also take care to display directory data in a
valued types). "safe" environment (e.g., PostScript-valued types).
o vCards can carry cryptographic keys or certificates, as described o vCards can carry cryptographic keys or certificates, as described
in Section 7.8.2. in Section 6.8.2.
o Section 7.8.1 specifies a desired security classification policy o Section 6.8.1 specifies a desired security classification policy
for a particular vCard. That policy is not enforced in any way. for a particular vCard. That policy is not enforced in any way.
o The vCard objects have no inherent authentication or privacy, but o The vCard objects have no inherent authentication or privacy, but
can easily be carried by any security mechanism that transfers can easily be carried by any security mechanism that transfers
MIME objects with authentication or privacy. In cases where MIME objects with authentication or privacy. In cases where the
threats of "spoofed" vCard information is a concern, the vCard threat of "spoofed" vCard information is a concern, the vCard
SHOULD BE transported using one of these secure mechanisms. SHOULD BE transported using one of these secure mechanisms.
o The information in a vCard may become out of date. In cases where o The information in a vCard may become out of date. In cases where
the vitality of data is important to an originator of a vCard, the the vitality of data is important to an originator of a vCard, the
"URL" type described in Section 7.7.9 SHOULD BE specified. In "URL" type described in Section 6.7.9 SHOULD BE specified. In
addition, the "REV" type described in section Section 7.7.4 can be addition, the "REV" type described in section Section 6.7.4 can be
specified to indicate the last time that the vCard data was specified to indicate the last time that the vCard data was
updated. updated.
11. IANA Considerations 10. IANA Considerations
11.1. MIME Type Registration 10.1. MIME Type Registration
To: ietf-types@iana.org
Please refer to Section 3. Subject: Registration of media type text/vcard
11.2. Registering New vCard Elements Type name: text
Subtype name: vcard
Required parameters: none
Optional parameters: charset
Encoding considerations: The "charset" MIME parameter is interpreted
as defined in [RFC2046], section 4.1.2. If it is omitted, the
default encoding is UTF-8 as defined in [RFC3629].
Security considerations: See Section 9.
Interoperability considerations: The text/vcard media type is
intended to identify vCard data of any version. There are older
specifications of vCard [RFC2426][oldreference_VCARD] still in
common use. While these formats are similar, they are not
strictly compatible. In general, it is necessary to inspect the
value of the VERSION property (see Section 6.7.10) for identifying
the standard to which a given vCard object conforms.
In addition, the following media types are known to have been used
to refer to vCard data. They should be considered deprecated in
favor of text/vcard.
* text/directory
* text/directory; type=vcard
* text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-09
Applications that use this media type: They are numerous, diverse,
and include mail user agents, instant messaging clients, address
book applications, directory servers, customer relationship
management software, etc.
Additional information:
Magic number(s):
File extension(s): .vcf
Macintosh file type code(s):
Person & email address to contact for further information: Simon
Perreault <simon.perreault@viagenie.ca>
Intended usage: COMMON
Restrictions on usage: none
Author: Simon Perreault and Pete Resnick
Change controller: IETF
10.2. Registering New vCard Elements
This section defines the process for registering new or modified This section defines the process for registering new or modified
vCard elements (i.e. properties, parameters, value data types, and vCard elements (i.e. properties, parameters, value data types, and
values) with IANA. values) with IANA.
11.2.1. Registration Procedure 10.2.1. Registration Procedure
The IETF will create a mailing list, vcard@ietf.org [1], which can be The IETF will create a mailing list, vcard@ietf.org [1], which can be
used for public discussion of vCard element proposals prior to used for public discussion of vCard element proposals prior to
registration. Use of the mailing list is strongly encouraged. The registration. Use of the mailing list is strongly encouraged. The
IESG will appoint a designated expert who will monitor the IESG will appoint a designated expert who will monitor the
vcard@ietf.org [1] mailing list and review registrations. vcard@ietf.org [1] mailing list and review registrations.
Registration of new vCard elements MUST be reviewed by the designated Registration of new vCard elements MUST be reviewed by the designated
expert and published in an RFC. A Standard Tracks RFC is REQUIRED expert and published in an RFC. A Standard Tracks RFC is REQUIRED
for the registration of new value data types that modify existing for the registration of new value data types that modify existing
skipping to change at page 58, line 16 skipping to change at page 59, line 5
template, defined in the sections below, is sent to template, defined in the sections below, is sent to
vcard@ietf.org [1] and iana@iana.org [2]. The designated expert is vcard@ietf.org [1] and iana@iana.org [2]. The designated expert is
expected to tell IANA and the submitter of the registration within expected to tell IANA and the submitter of the registration within
two weeks whether the registration is approved, approved with minor two weeks whether the registration is approved, approved with minor
changes, or rejected with cause. When a registration is rejected changes, or rejected with cause. When a registration is rejected
with cause, it can be re-submitted if the concerns listed in the with cause, it can be re-submitted if the concerns listed in the
cause are addressed. Decisions made by the designated expert can be cause are addressed. Decisions made by the designated expert can be
appealed to the IESG Applications Area Director, then to the IESG. appealed to the IESG Applications Area Director, then to the IESG.
They follow the normal appeals procedure for IESG decisions. They follow the normal appeals procedure for IESG decisions.
11.2.2. Vendor Namespace 10.2.2. Vendor Namespace
The vendor namespace is used for vCard elements associated with The vendor namespace is used for vCard elements associated with
commercially available products. "Vendor" or "producer" are commercially available products. "Vendor" or "producer" are
construed as equivalent and very broadly in this context. construed as equivalent and very broadly in this context.
A registration may be placed in the vendor namespace by anyone who A registration may be placed in the vendor namespace by anyone who
needs to interchange files associated with the particular product. needs to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or However, the registration formally belongs to the vendor or
organization handling the vCard elements in the namespace being organization handling the vCard elements in the namespace being
registered. Changes to the specification will be made at their registered. Changes to the specification will be made at their
request, as discussed in subsequent sections. request, as discussed in subsequent sections.
vCard elements belonging to the vendor namespace will be vCard elements belonging to the vendor namespace will be
distinguished by the "VND-" prefix. That may be followed, at the distinguished by the "VND-" prefix. This is followed by an IANA-
discretion of the registrant, by either a vCard element name from a registered Private Enterprise Number (PEN), a dash, and a vCard
well-known producer (e.g., "VND-MUDPIE") or by an IANA-approved element designation of the vendor's choosing (e.g., "VND-123456-
designation of the producer's name that is followed by a vCard MUDPIE").
element designation (e.g., "VND-BIGCOMPANY-MUDPIE").
While public exposure and review of vCard elements to be registered While public exposure and review of vCard elements to be registered
in the vendor namespace is not required, using the vcard@ietf.org [1] in the vendor namespace is not required, using the vcard@ietf.org [1]
mailing list for review is strongly encouraged to improve the quality mailing list for review is strongly encouraged to improve the quality
of those specifications. Registrations in the vendor namespace may of those specifications. Registrations in the vendor namespace may
be submitted directly to the IANA. be submitted directly to the IANA.
11.2.3. Registration Template for Groups 10.2.3. Registration Template for Properties
A group is defined by completing the following template.
Group name: The name of the group.
Purpose: The purpose of the group. Give a short but clear
description.
Description: Any special notes about the group, how it is to be
used, etc.
Allowed Properties: List of properties that may be placed inside the
group.
Example(s): One or more examples of instances of the value type
needs to be specified.
11.2.4. Registration Template for Properties
A property is defined by completing the following template. A property is defined by completing the following template.
Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-
specific property (where NNNN is replaced by the vendor's PEN).
Property name: The name of the property. Property name: The name of the property.
Purpose: The purpose of the property. Give a short but clear Purpose: The purpose of the property. Give a short but clear
description. description.
Value type: Any of the valid value types for the property value Value type: Any of the valid value types for the property value
needs to be specified. The default value type also needs to be needs to be specified. The default value type also needs to be
specified. specified.
Property parameters: Any of the valid property parameters for the Property parameters: Any of the valid property parameters for the
property MUST be specified. property MUST be specified.
Groups: List of already-existing groups whose allowed properties
list must be updated by adding this new property.
Description: Any special notes about the property, how it is to be Description: Any special notes about the property, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the property definition needs to be Format definition: The ABNF for the property definition needs to be
specified. specified.
Example(s): One or more examples of instances of the property needs Example(s): One or more examples of instances of the property needs
to be specified. to be specified.
11.2.5. Registration Template for Parameters 10.2.4. Registration Template for Parameters
A parameter is defined by completing the following template. A parameter is defined by completing the following template.
Parameter name: The name of the parameter. Parameter name: The name of the parameter.
Purpose: The purpose of the parameter. Give a short but clear Purpose: The purpose of the parameter. Give a short but clear
description. description.
Description: Any special notes about the parameter, how it is to be Description: Any special notes about the parameter, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the parameter definition needs to be Format definition: The ABNF for the parameter definition needs to be
specified. specified.
Example(s): One or more examples of instances of the parameter needs Example(s): One or more examples of instances of the parameter needs
to be specified. to be specified.
11.2.6. Registration Template for Value Data Types 10.2.5. Registration Template for Value Data Types
A value data type is defined by completing the following template. A value data type is defined by completing the following template.
Value name: The name of the value type. Value name: The name of the value type.
Purpose: The purpose of the value type. Give a short but clear Purpose: The purpose of the value type. Give a short but clear
description. description.
Description: Any special notes about the value type, how it is to be Description: Any special notes about the value type, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the value type definition needs to Format definition: The ABNF for the value type definition needs to
be specified. be specified.
Example(s): One or more examples of instances of the value type Example(s): One or more examples of instances of the value type
needs to be specified. needs to be specified.
11.2.7. Registration Template for Values 10.2.6. Registration Template for Values
A value is defined by completing the following template. A value is defined by completing the following template.
Value: The value literal. Value: The value literal.
Purpose: The purpose of the value. Give a short but clear Purpose: The purpose of the value. Give a short but clear
description. description.
Conformance: The vCard properties and/or parameters that can take Conformance: The vCard properties and/or parameters that can take
this value needs to be specified. this value needs to be specified.
skipping to change at page 61, line 17 skipping to change at page 61, line 31
Purpose: This value is used to specify the access classification of Purpose: This value is used to specify the access classification of
top-secret vCards. top-secret vCards.
Conformance: This value can be used with the "CLASS" property. Conformance: This value can be used with the "CLASS" property.
Example(s): The following is an example of this value used with the Example(s): The following is an example of this value used with the
"CLASS" property: "CLASS" property:
CLASS:TOP-SECRET CLASS:TOP-SECRET
11.3. Initial vCard Elements Registries 10.3. Initial vCard Elements Registries
The IANA is requested to create and maintain the following registries The IANA is requested to create and maintain the following registries
for vCard elements with pointers to appropriate reference documents. for vCard elements with pointers to appropriate reference documents.
11.3.1. Groups Registry 10.3.1. Properties Registry
The following table is to be used to initialize the groups registry.
+------+--------------+---------+-----------------------+-----------+
| Goup | Description | Status | Allowed Properties | Reference |
+------+--------------+---------+-----------------------+-----------+
| WORK | Properties | Current | FN, NICKNAME, PHOTO, | RFCXXXX |
| | related to | | ADR, LABEL, TEL, | |
| | an | | EMAIL, IMPP, LANG, | |
| | individual's | | TZ, GEO, TITLE, ROLE, | |
| | work place. | | LOGO, ORG, RELATED, | |
| | | | CATEGORIES, NOTE, | |
| | | | SOUND, URL, KEY, | |
| | | | FBURL, CALADRURI, | |
| | | | CALURI | |
| HOME | Properties | Current | FN, NICKNAME, PHOTO, | RFCXXXX |
| | related to | | ADR, LABEL, TEL, | |
| | an | | EMAIL, IMPP, LANG, | |
| | individual's | | TZ, GEO, TITLE, ROLE, | |
| | personal | | LOGO, ORG, RELATED, | |
| | life. | | CATEGORIES, NOTE, | |
| | | | SOUND, URL, KEY, | |
| | | | FBURL, CALADRURI, | |
| | | | CALURI | |
+------+--------------+---------+-----------------------+-----------+
11.3.2. Properties Registry
The following table is to be used to initialize the properties The following table is to be used to initialize the properties
registry. registry.
+--------------+---------+-------------------------+ +-----------+--------------+---------+-------------------------+
| Property | Status | Reference | | Namespace | Property | Status | Reference |
+--------------+---------+-------------------------+ +-----------+--------------+---------+-------------------------+
| SOURCE | Current | RFCXXXX, Section 7.1.3 | | | SOURCE | Current | RFCXXXX, Section 6.1.3 |
| NAME | Current | RFCXXXX, Section 7.1.4 | | | NAME | Current | RFCXXXX, Section 6.1.4 |
| KIND | Current | RFCXXXX, Section 7.1.5 | | | KIND | Current | RFCXXXX, Section 6.1.5 |
| FN | Current | RFCXXXX, Section 7.2.1 | | | FN | Current | RFCXXXX, Section 6.2.1 |
| N | Current | RFCXXXX, Section 7.2.2 | | | N | Current | RFCXXXX, Section 6.2.2 |
| NICKNAME | Current | RFCXXXX, Section 7.2.3 | | | NICKNAME | Current | RFCXXXX, Section 6.2.3 |
| PHOTO | Current | RFCXXXX, Section 7.2.4 | | | PHOTO | Current | RFCXXXX, Section 6.2.4 |
| BDAY | Current | RFCXXXX, Section 7.2.5 | | | BDAY | Current | RFCXXXX, Section 6.2.5 |
| DDAY | Current | RFCXXXX, Section 7.2.6 | | | DDAY | Current | RFCXXXX, Section 6.2.6 |
| BIRTH | Current | RFCXXXX, Section 7.2.7 | | | BIRTH | Current | RFCXXXX, Section 6.2.7 |
| DEATH | Current | RFCXXXX, Section 7.2.8 | | | DEATH | Current | RFCXXXX, Section 6.2.8 |
| ANNIVERSARY | Current | RFCXXXX, Section 7.2.9 | | | ANNIVERSARY | Current | RFCXXXX, Section 6.2.9 |
| SEX | Current | RFCXXXX, Section 7.2.10 | | | SEX | Current | RFCXXXX, Section 6.2.10 |
| ADR | Current | RFCXXXX, Section 7.3.1 | | | ADR | Current | RFCXXXX, Section 6.3.1 |
| LABEL | Current | RFCXXXX, Section 7.3.2 | | | LABEL | Current | RFCXXXX, Section 6.3.2 |
| TEL | Current | RFCXXXX, Section 7.4.1 | | | TEL | Current | RFCXXXX, Section 6.4.1 |
| EMAIL | Current | RFCXXXX, Section 7.4.2 | | | EMAIL | Current | RFCXXXX, Section 6.4.2 |
| IMPP | Current | RFCXXXX, Section 7.4.3 | | | IMPP | Current | RFCXXXX, Section 6.4.3 |
| LANG | Current | RFCXXXX, Section 7.4.4 | | | LANG | Current | RFCXXXX, Section 6.4.4 |
| TZ | Current | RFCXXXX, Section 7.5.1 | | | TZ | Current | RFCXXXX, Section 6.5.1 |
| GEO | Current | RFCXXXX, Section 7.5.2 | | | GEO | Current | RFCXXXX, Section 6.5.2 |
| TITLE | Current | RFCXXXX, Section 7.6.1 | | | TITLE | Current | RFCXXXX, Section 6.6.1 |
| ROLE | Current | RFCXXXX, Section 7.6.2 | | | ROLE | Current | RFCXXXX, Section 6.6.2 |
| LOGO | Current | RFCXXXX, Section 7.6.3 | | | LOGO | Current | RFCXXXX, Section 6.6.3 |
| ORG | Current | RFCXXXX, Section 7.6.4 | | | ORG | Current | RFCXXXX, Section 6.6.4 |
| MEMBER | Current | RFCXXXX, Section 7.6.5 | | | MEMBER | Current | RFCXXXX, Section 6.6.5 |
| RELATED | Current | RFCXXXX, Section 7.6.6 | | | RELATED | Current | RFCXXXX, Section 6.6.6 |
| CATEGORIES | Current | RFCXXXX, Section 7.7.1 | | | CATEGORIES | Current | RFCXXXX, Section 6.7.1 |
| NOTE | Current | RFCXXXX, Section 7.7.2 | | | NOTE | Current | RFCXXXX, Section 6.7.2 |
| PRODID | Current | RFCXXXX, Section 7.7.3 | | | PRODID | Current | RFCXXXX, Section 6.7.3 |
| REV | Current | RFCXXXX, Section 7.7.4 | | | REV | Current | RFCXXXX, Section 6.7.4 |
| SORT-STRING | Current | RFCXXXX, Section 7.7.5 | | | SORT-STRING | Current | RFCXXXX, Section 6.7.5 |
| SOUND | Current | RFCXXXX, Section 7.7.6 | | | SOUND | Current | RFCXXXX, Section 6.7.6 |
| UID | Current | RFCXXXX, Section 7.7.7 | | | UID | Current | RFCXXXX, Section 6.7.7 |
| CLIENTPIDMAP | Current | RFCXXXX, Section 7.7.8 | | | CLIENTPIDMAP | Current | RFCXXXX, Section 6.7.8 |
| URL | Current | RFCXXXX, Section 7.7.9 | | | URL | Current | RFCXXXX, Section 6.7.9 |
| VERSION | Current | RFCXXXX, Section 7.7.10 | | | VERSION | Current | RFCXXXX, Section 6.7.10 |
| CLASS | Current | RFCXXXX, Section 7.8.1 | | | CLASS | Current | RFCXXXX, Section 6.8.1 |
| KEY | Current | RFCXXXX, Section 7.8.2 | | | KEY | Current | RFCXXXX, Section 6.8.2 |
| FBURL | Current | RFCXXXX, Section 7.9.1 | | | FBURL | Current | RFCXXXX, Section 6.9.1 |
| CALADRURI | Current | RFCXXXX, Section 7.9.2 | | | CALADRURI | Current | RFCXXXX, Section 6.9.2 |
| CALURI | Current | RFCXXXX, Section 7.9.3 | | | CALURI | Current | RFCXXXX, Section 6.9.3 |
+--------------+---------+-------------------------+ +-----------+--------------+---------+-------------------------+
11.3.3. Parameters Registry 10.3.2. Parameters Registry
The following table is to be used to initialize the parameters The following table is to be used to initialize the parameters
registry. registry.
+-----------+---------+------------------------+ +-----------+---------+------------------------+
| Parameter | Status | Reference | | Parameter | Status | Reference |
+-----------+---------+------------------------+ +-----------+---------+------------------------+
| LANGUAGE | Current | RFCXXXX, Section 6.1 | | LANGUAGE | Current | RFCXXXX, Section 5.1 |
| ENCODING | Current | RFCXXXX, Section 6.2 | | ENCODING | Current | RFCXXXX, Section 5.2 |
| VALUE | Current | RFCXXXX, Section 6.3 | | VALUE | Current | RFCXXXX, Section 5.3 |
| PREF | Current | RFCXXXX, Section 6.4 | | PREF | Current | RFCXXXX, Section 5.4 |
| PID | Current | RFCXXXX, Section 6.5 | | PID | Current | RFCXXXX, Section 5.5 |
| TYPE | Current | RFCXXXX, Section 6.6 | | TYPE | Current | RFCXXXX, Section 5.6 |
| GEO | Current | RFCXXXX, Section 7.3.1 | | GEO | Current | RFCXXXX, Section 6.3.1 |
| TZ | Current | RFCXXXX, Section 7.3.1 | | TZ | Current | RFCXXXX, Section 6.3.1 |
+-----------+---------+------------------------+ +-----------+---------+------------------------+
11.3.4. Value Data Types Registry 10.3.3. Value Data Types Registry
The following table is to be used to initialize the parameters The following table is to be used to initialize the parameters
registry. registry.
+------------------+---------+------------------------+ +------------------+---------+------------------------+
| Value Data Type | Status | Reference | | Value Data Type | Status | Reference |
+------------------+---------+------------------------+ +------------------+---------+------------------------+
| BINARY | Current | RFCXXXX, Section 5.7 | | BINARY | Current | RFCXXXX, Section 4.7 |
| BOOLEAN | Current | RFCXXXX, Section 5.4 | | BOOLEAN | Current | RFCXXXX, Section 4.4 |
| DATE | Current | RFCXXXX, Section 5.3.1 | | DATE | Current | RFCXXXX, Section 4.3.1 |
| TIME | Current | RFCXXXX, Section 5.3.2 | | TIME | Current | RFCXXXX, Section 4.3.2 |
| DATE-TIME | Current | RFCXXXX, Section 5.3.3 | | DATE-TIME | Current | RFCXXXX, Section 4.3.3 |
| DATE-AND-OR-TIME | Current | RFCXXXX, Section 5.3.4 | | DATE-AND-OR-TIME | Current | RFCXXXX, Section 4.3.4 |
| TIMESTAMP | Current | RFCXXXX, Section 5.3.5 | | TIMESTAMP | Current | RFCXXXX, Section 4.3.5 |
| FLOAT | Current | RFCXXXX, Section 5.6 | | FLOAT | Current | RFCXXXX, Section 4.6 |
| INTEGER | Current | RFCXXXX, Section 5.5 | | INTEGER | Current | RFCXXXX, Section 4.5 |
| TEXT | Current | RFCXXXX, Section 5.1 | | TEXT | Current | RFCXXXX, Section 4.1 |
| URI | Current | RFCXXXX, Section 5.2 | | URI | Current | RFCXXXX, Section 4.2 |
| LANGUAGE-TAG | Current | RFCXXXX, Section 5.8 | | LANGUAGE-TAG | Current | RFCXXXX, Section 4.8 |
+------------------+---------+------------------------+ +------------------+---------+------------------------+
11.3.5. Values Registries 10.3.4. Values Registries
Separate tables will be used for property and parameter values. Separate tables will be used for property and parameter values.
The following table is to be used to initialize the property values The following table is to be used to initialize the property values
registry. registry.
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
| Property | Value | Status | Reference | | Property | Value | Status | Reference |
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
| BEGIN | VCARD | Current | RFCXXXX, Section 7.1.1 | | BEGIN | VCARD | Current | RFCXXXX, Section 6.1.1 |
| END | VCARD | Current | RFCXXXX, Section 7.1.2 | | END | VCARD | Current | RFCXXXX, Section 6.1.2 |
| KIND | individual | Current | RFCXXXX, Section 7.1.5 | | KIND | individual | Current | RFCXXXX, Section 6.1.5 |
| KIND | group | Current | RFCXXXX, Section 7.1.5 | | KIND | group | Current | RFCXXXX, Section 6.1.5 |
| KIND | org | Current | RFCXXXX, Section 7.1.5 | | KIND | org | Current | RFCXXXX, Section 6.1.5 |
| KIND | location | Current | RFCXXXX, Section 7.1.5 | | KIND | location | Current | RFCXXXX, Section 6.1.5 |
| CLASS | PUBLIC | Current | RFCXXXX, Section 7.8.1 | | KIND | thing | Current | RFCXXXX, Section 6.1.5 |
| CLASS | PRIVATE | Current | RFCXXXX, Section 7.8.1 | | CLASS | PUBLIC | Current | RFCXXXX, Section 6.8.1 |
| CLASS | CONFIDENTIAL | Current | RFCXXXX, Section 7.8.1 | | CLASS | PRIVATE | Current | RFCXXXX, Section 6.8.1 |
| CLASS | CONFIDENTIAL | Current | RFCXXXX, Section 6.8.1 |
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
The following table is to be used to initialize the parameter values The following table is to be used to initialize the parameter values
registry. registry.
+----------+-----------+------------+---------+---------------------+ +----------+-----------+------------+---------+---------------------+
| Property | Parameter | Value | Status | Reference | | Property | Parameter | Value | Status | Reference |
+----------+-----------+------------+---------+---------------------+ +----------+-----------+------------+---------+---------------------+
| TEL | TYPE | text | Current | RFCXXXX, | | TEL | TYPE | text | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | voice | Current | RFCXXXX, | | TEL | TYPE | voice | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | fax | Current | RFCXXXX, | | TEL | TYPE | fax | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | cell | Current | RFCXXXX, | | TEL | TYPE | cell | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | video | Current | RFCXXXX, | | TEL | TYPE | video | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | pager | Current | RFCXXXX, | | TEL | TYPE | pager | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 6.4.1 |
| RELATED | TYPE | parent | Current | RFCXXXX, | | RELATED | TYPE | parent | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | child | Current | RFCXXXX, | | RELATED | TYPE | child | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | sibling | Current | RFCXXXX, | | RELATED | TYPE | sibling | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | spouse | Current | RFCXXXX, | | RELATED | TYPE | spouse | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | family | Current | RFCXXXX, | | RELATED | TYPE | family | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | friend | Current | RFCXXXX, | | RELATED | TYPE | friend | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | supervisor | Current | RFCXXXX, | | RELATED | TYPE | supervisor | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | supervisee | Current | RFCXXXX, | | RELATED | TYPE | supervisee | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | assistant | Current | RFCXXXX, | | RELATED | TYPE | assistant | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | colleague | Current | RFCXXXX, | | RELATED | TYPE | colleague | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | agent | Current | RFCXXXX, | | RELATED | TYPE | agent | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
| RELATED | TYPE | emergency | Current | RFCXXXX, | | RELATED | TYPE | emergency | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 6.6.6 |
+----------+-----------+------------+---------+---------------------+ +----------+-----------+------------+---------+---------------------+
12. Acknowledgements 11. Acknowledgements
The authors would like to thank Tim Howes, Mark Smith, and Frank The authors would like to thank Tim Howes, Mark Smith, and Frank
Dawson, the original authors of [RFC2425] and [RFC2426], as well as Dawson, the original authors of [RFC2425] and [RFC2426], as well as
the following individuals who have participated in the drafting, the following individuals who have participated in the drafting,
review and discussion of this memo: review and discussion of this memo:
(needs to be updated) Marc Blanchet, Stephane Bortzmeyer, Dan Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
Brickley, Chris Bryant, Dany Cauchie, Darryl Champagne, Cyrus Daboo, Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie
Bernard Desruisseaux, Lisa Dusseault, Javier Godoy, Sly Gryphon, Hoeneisen, Caleb Richarson, Chris Bryant, Chris Newman, Cyrus Daboo,
Helge Hess, Renato Iannella, Alexander Mayrhofer, Chris Newman, Mark Dan Brickley, Dan Mosedale, Dany Cauchie, Darryl Champagne, Dave
Paterson, Julian Reschke, Peter K. Sheerin, Anil Srivastava, and Kurt Thewlis, Helge Hess, Jari Urpalainen, Javier Godoy, Jean-Luc
Zeilenga. Schellens, Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Julian
Reschke, Kepeng Li, Kurt Zeilenga. Lisa Dusseault, Marc Blanchet,
13. References Mark Paterson, Markus Lorenz, Mike Douglass, Peter K. Sheerin, Peter
Mogensen, Peter St-Andre, Renato Iannella, Sly Gryphon, Stephane
Bortzmeyer, and Tantek Celik.
13.1. Normative References 12. References
[CCITT.E163.1988] International Telephone and Telegraph 12.1. Normative References
Consultative Committee, "Numbering Plan for
the International Telephone Service",
CCITT Recommendation E.163, 1988.
[CCITT.X121.1988] International Telephone and Telegraph [CCITT.E163.1988] International Telephone and Telegraph
Consultative Committee, "International Consultative Committee, "Numbering Plan
Numbering Plan for the Public Data for the International Telephone Service",
Networks", CCITT Recommendation X.121, 1988. CCITT Recommendation E.163, 1988.
[CCITT.X520.1988] International International Telephone and [CCITT.X121.1988] International Telephone and Telegraph
Telegraph Consultative Committee, Consultative Committee, "International
"Information Technology - Open Systems Numbering Plan for the Public Data
Interconnection - The Directory: Selected Networks", CCITT Recommendation X.121,
Attribute Types", CCITT Recommendation 1988.
X.520, November 1988.
[CCITT.X521.1988] International International Telephone and [CCITT.X520.1988] International International Telephone and
Telegraph Consultative Committee, Telegraph Consultative Committee,
"Information Technology - Open Systems "Information Technology - Open Systems
Interconnection - The Directory: Selected Interconnection - The Directory: Selected
Object Classes", CCITT Recommendation X.521, Attribute Types", CCITT Recommendation
November 1988. X.520, November 1988.
[I-D.mayrhofer-geo-uri] Mayrhofer, A. and C. Spanring, "A Uniform [CCITT.X521.1988] International International Telephone and
Resource Identifier for Geographic Areas Telegraph Consultative Committee,
('geo' URI)", draft-mayrhofer-geo-uri-02 "Information Technology - Open Systems
(work in progress), February 2008. Interconnection - The Directory: Selected
Object Classes", CCITT Recommendation
X.521, November 1988.
[ISO.5218.2004] International Organization for [I-D.ietf-geopriv-geo-uri] Mayrhofer, A. and C. Spanring, "A Uniform
Standardization, "Information Technology - Resource Identifier for Geographic
Codes for the representation of human Locations ('geo' URI)",
sexes", ISO Standard 5218, December 2004. draft-ietf-geopriv-geo-uri-02 (work in
progress), September 2009.
[ISO.8601.2000] International Organization for [ISO.5218.2004] International Organization for
Standardization, "Data elements and Standardization, "Information Technology
interchange formats - Information - Codes for the representation of human
interchange - Representation of dates and sexes", ISO Standard 5218, December 2004.
times", ISO Standard 8601, December 2000.
[ISO.8601.2004] International Organization for [ISO.8601.2000] International Organization for
Standardization, "Data elements and Standardization, "Data elements and
interchange formats - Information interchange formats - Information
interchange - Representation of dates and interchange - Representation of dates and
times", ISO Standard 8601, December 2004. times", ISO Standard 8601, December 2000.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose [ISO.8601.2004] International Organization for
Internet Mail Extensions (MIME) Part Two: Standardization, "Data elements and
Media Types", RFC 2046, November 1996. interchange formats - Information
interchange - Representation of dates and
times", ISO Standard 8601, December 2004.
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein,
Extensions) Part Three: Message Header "Multipurpose Internet Mail Extensions
Extensions for Non-ASCII Text", RFC 2047, (MIME) Part Two: Media Types", RFC 2046,
November 1996. November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2047] Moore, K., "MIME (Multipurpose Internet
Indicate Requirement Levels", BCP 14, Mail Extensions) Part Three: Message
RFC 2119, March 1997. Header Extensions for Non-ASCII Text",
RFC 2047, November 1996.
[RFC2425] Howes, T., Smith, M., and F. Dawson, "A MIME [RFC2119] Bradner, S., "Key words for use in RFCs
Content-Type for Directory Information", to Indicate Requirement Levels", BCP 14,
RFC 2425, September 1998. RFC 2119, March 1997.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME [RFC2425] Howes, T., Smith, M., and F. Dawson, "A
Directory Profile", RFC 2426, MIME Content-Type for Directory
September 1998. Information", RFC 2425, September 1998.
[RFC2739] Small, T., Hennessy, D., and F. Dawson, [RFC2426] Dawson, F. and T. Howes, "vCard MIME
"Calendar Attributes for vCard and LDAP", Directory Profile", RFC 2426,
RFC 2739, January 2000. September 1998.
[RFC2978] Freed, N. and J. Postel, "IANA Charset [RFC2739] Small, T., Hennessy, D., and F. Dawson,
Registration Procedures", BCP 19, RFC 2978, "Calendar Attributes for vCard and LDAP",
October 2000. RFC 2739, January 2000.
[RFC3629] Yergeau, F., "UTF-8, a transformation format [RFC3629] Yergeau, F., "UTF-8, a transformation
of ISO 10646", STD 63, RFC 3629, format of ISO 10646", STD 63, RFC 3629,
November 2003. November 2003.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone [RFC3966] Schulzrinne, H., "The tel URI for
Numbers", RFC 3966, December 2004. Telephone Numbers", RFC 3966,
December 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. [RFC3986] Berners-Lee, T., Fielding, R., and L.
Masinter, "Uniform Resource Identifier Masinter, "Uniform Resource Identifier
(URI): Generic Syntax", STD 66, RFC 3986, (URI): Generic Syntax", STD 66, RFC 3986,
January 2005. January 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A [RFC4122] Leach, P., Mealling, M., and R. Salz, "A
Universally Unique IDentifier (UUID) URN Universally Unique IDentifier (UUID) URN
Namespace", RFC 4122, July 2005. Namespace", RFC 4122, July 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type [RFC4288] Freed, N. and J. Klensin, "Media Type
Specifications and Registration Procedures", Specifications and Registration
BCP 13, RFC 4288, December 2005. Procedures", BCP 13, RFC 4288,
December 2005.
[RFC4646] Phillips, A. and M. Davis, "Tags for [RFC4770] Jennings, C. and J. Reschke, Ed., "vCard
Identifying Languages", BCP 47, RFC 4646, Extensions for Instant Messaging (IM)",
September 2006. RFC 4770, January 2007.
[RFC4770] Jennings, C. and J. Reschke, Ed., "vCard [RFC5234] Crocker, D. and P. Overell, "Augmented
Extensions for Instant Messaging (IM)", BNF for Syntax Specifications: ABNF",
RFC 4770, January 2007. STD 68, RFC 5234, January 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF [RFC5322] Resnick, P., Ed., "Internet Message
for Syntax Specifications: ABNF", STD 68, Format", RFC 5322, October 2008.
RFC 5234, January 2008.
[RFC5322] Resnick, P., Ed., "Internet Message Format", [RFC5646] Phillips, A. and M. Davis, "Tags for
RFC 5322, October 2008. Identifying Languages", BCP 47, RFC 5646,
September 2009.
[oldreference_VCARD] Internet Mail Consortium, "vCard - The [oldreference_VCARD] Internet Mail Consortium, "vCard - The
Electronic Business Card Version 2.1", Electronic Business Card Version 2.1",
September September. September September.
13.2. Informative References 12.2. Informative References
[ISO9070] The International Organization for [ISO9070] The International Organization for
Standardization, "ISO 9070, Information Standardization, "ISO 9070, Information
Processing - SGML support facilities - Processing - SGML support facilities -
Registration Procedures for Public Text Registration Procedures for Public Text
Owner Identifiers", April 1991. Owner Identifiers", April 1991.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and [RFC3406] Daigle, L., van Gulik, D., Iannella, R.,
P. Faltstrom, "Uniform Resource Names (URN) and P. Faltstrom, "Uniform Resource Names
Namespace Definition Mechanisms", BCP 66, (URN) Namespace Definition Mechanisms",
RFC 3406, October 2002. BCP 66, RFC 3406, October 2002.
[TZ-DB] Olson, A., "Time zone code and data", [TZ-DB] Olson, A., "Time zone code and data",
<ftp://elsie.nci.nih.gov/pub/>. <ftp://elsie.nci.nih.gov/pub/>.
URIs URIs
[1] <mailto:vcard@ietf.org> [1] <mailto:vcard@ietf.org>
[2] <mailto:iana@iana.org> [2] <mailto:iana@iana.org>
Appendix A. Differences from RFCs 2425 and 2426 Appendix A. Differences from RFCs 2425 and 2426
This appendix contains a list of changes that have been made in the This appendix contains a list of changes that have been made in the
skipping to change at page 70, line 41 skipping to change at page 69, line 41
o The "work", "home", and "uri" TYPE parameter values for the EMAIL o The "work", "home", and "uri" TYPE parameter values for the EMAIL
property have been added. property have been added.
o The "pref" value of the TYPE parameter is now a parameter of its o The "pref" value of the TYPE parameter is now a parameter of its
own, with a positive integer value indicating the level of own, with a positive integer value indicating the level of
preferredness. preferredness.
A.4. Other Changes A.4. Other Changes
o Synchronization is addressed in Section 8. o Synchronization is addressed in Section 7.
o The N property is no longer mandatory. o The N property is no longer mandatory.
o The value of TEL is now a URI. o The value of TEL is now a URI.
o The AGENT property was replaced with a type of RELATED. o The AGENT property was replaced with a type of RELATED.
o Date and time values now only support the basic format. o Date and time values now only support the basic format.
Truncation is now supported. Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -08 B.1. Changes in -09
o Removed special meaning for groups. Removed the "work" and "home"
groups. Removed the group registry. Re-introduced the "work" and
"home" TYPE parameter values. Applied the TYPE parameter to
properties which supported the "work" and "home" groups.
o Vendor namespace now uses private enterprise number in prefix.
o Added "thing" value for KIND property.
B.2. Changes in -08
o Allow 1985 (year only) in date ABNF. o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example. o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value. o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME. o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to o Prefixed "param" and "value" production rules specific to
skipping to change at page 71, line 31 skipping to change at page 70, line 42
o Replaced the GENDER property with the SEX property. o Replaced the GENDER property with the SEX property.
o Added the ANNIVERSARY property. o Added the ANNIVERSARY property.
o Added the "friend" and "spouse" types of RELATED. o Added the "friend" and "spouse" types of RELATED.
o TZ property now has text / uri value. o TZ property now has text / uri value.
o Refined the definitions of TITLE and ROLE. o Refined the definitions of TITLE and ROLE.
B.2. Changes in -07 B.3. Changes in -07
o PREF is now bounded. 100 is the maximum value. o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type. o Added the "emergency" RELATED type.
o Made GEO a URI. o Made GEO a URI.
o Added GEO and TZ parameters to ADR. o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property. o Changed wording of "default" use of SOUND property.
skipping to change at page 72, line 5 skipping to change at page 71, line 17
o Completely reworked the date, time, and date-time grammars. o Completely reworked the date, time, and date-time grammars.
o Added the timestamp value type. o Added the timestamp value type.
o REV now has the timestamp value type. o REV now has the timestamp value type.
o Rewrote ABNF. o Rewrote ABNF.
o ORG can now have a single level. o ORG can now have a single level.
B.3. Changes in -06 B.4. Changes in -06
o Corrected omission of resetability to text value for RELATED. o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value. o Let KEY value type be reset to a URI value.
o ABNF fixes. o ABNF fixes.
o Made gender values extensible. o Made gender values extensible.
o Gave the PREF parameter a positive integer value. o Gave the PREF parameter a positive integer value.
skipping to change at page 72, line 44 skipping to change at page 72, line 9
o Removed TYPE parameter from EMAIL properties in examples. o Removed TYPE parameter from EMAIL properties in examples.
o Created the CLIENTPIDMAP property. o Created the CLIENTPIDMAP property.
o Changed PID value to a pair of small integers. o Changed PID value to a pair of small integers.
o Completely reworked synchronization mechanisms. o Completely reworked synchronization mechanisms.
o Created brand new synchronization example. o Created brand new synchronization example.
B.4. Changes in -05 B.5. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.5. Changes in -04 B.6. Changes in -04
o Added "location" value for KIND property. o Added "location" value for KIND property.
o Some fixes to ABNF. o Some fixes to ABNF.
o Moved "pref" from being a TYPE value to a parameter in its own o Moved "pref" from being a TYPE value to a parameter in its own
right. right.
o Removed the "work" and "home" TYPE values. o Removed the "work" and "home" TYPE values.
skipping to change at page 73, line 31 skipping to change at page 72, line 43
o Removed TYPE parameter from EMAIL and IMPP properties. o Removed TYPE parameter from EMAIL and IMPP properties.
o Replaced AGENT with a type of RELATED. o Replaced AGENT with a type of RELATED.
o Use example.org domain in URL example. o Use example.org domain in URL example.
o Created initial IANA table of values. o Created initial IANA table of values.
o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL. o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.
B.6. Changes in -03 B.7. Changes in -03
o Various changes to the synchronization mechanisms. o Various changes to the synchronization mechanisms.
o Allowed truncated format for dated. See issue #236. o Allowed truncated format for dated. See issue #236.
B.7. Changes in -02 B.8. Changes in -02
o Removed useless text in IMPP description. o Removed useless text in IMPP description.
o Added CalDAV-SCHED example to CALADRURI. o Added CalDAV-SCHED example to CALADRURI.
o Removed CAPURI property. o Removed CAPURI property.
o Dashes in dates and colons in times are now mandatory. o Dashes in dates and colons in times are now mandatory.
o Allow for dates such as 2008 and 2008-05 and times such as 07 and o Allow for dates such as 2008 and 2008-05 and times such as 07 and
skipping to change at page 74, line 16 skipping to change at page 73, line 31
o Added the MEMBER property. o Added the MEMBER property.
o Renamed the UID parameter to PID. o Renamed the UID parameter to PID.
o Changed the value type of the PID parameter to "a small integer." o Changed the value type of the PID parameter to "a small integer."
o Changed the presence of UID and PID when synchronization is to be o Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD. used from MUST to SHOULD.
o Added the RELATED (Section 7.6.6) property. o Added the RELATED (Section 6.6.6) property.
o Fixed many ABNF typos (issue #252). o Fixed many ABNF typos (issue #252).
o Changed formatting of ABNF comments to make them easier to read o Changed formatting of ABNF comments to make them easier to read
(issue #226). (issue #226).
B.8. Changes in -01 B.9. Changes in -01
o Merged [RFC2739] in. o Merged [RFC2739] in.
o Converted all foobar.com, abc.com, etc. to example.com. o Converted all foobar.com, abc.com, etc. to example.com.
o Fixed bugs in ABNF. o Fixed bugs in ABNF.
o Made explicit that coordinates in the GEO property are expressed o Made explicit that coordinates in the GEO property are expressed
in the WGS 84 reference system. in the WGS 84 reference system.
o Clarified folding issues with multi-byte characters. o Clarified folding issues with multi-byte characters.
o Made the value of TEL a URI. o Made the value of TEL a URI.
o Added the UID parameter. o Added the UID parameter.
o Made the UID property's value type a URI. o Made the UID property's value type a URI.
o Added Section 8. o Added Section 7.
o Created IANA process for registering new parameters, value types, o Created IANA process for registering new parameters, value types,
and properties. and properties.
o Created the initial IANA registries. o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288. o Created vendor namespace based on text from RFC 4288.
B.9. Changes in -00 B.10. Changes in -00
o Name change because draft has been accepted as WG item. o Name change because draft has been accepted as WG item.
Otherwise, same as draft-resnick-vcarddav-vcardrev-01. Otherwise, same as draft-resnick-vcarddav-vcardrev-01.
o Removed reference to RFC 2234. o Removed reference to RFC 2234.
o Fixed errata from o Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426. http://www.rfc-editor.org/errata_search.php?rfc=2426.
o Removed passage referring to RFC 2425 profiles. o Removed passage referring to RFC 2425 profiles.
o Renamed Section 7.4 from "Telecommunications Adressing Properties" o Renamed Section 6.4 from "Telecommunications Adressing Properties"
to "Communications Properties. to "Communications Properties.
o Added Appendix A and Appendix B. o Added Appendix A and Appendix B.
o Added reference to [RFC4770]. o Added reference to [RFC4770].
o Removed the group construct. o Removed the group construct.
o Made the N property no longer mandatory. o Made the N property no longer mandatory.
 End of changes. 279 change blocks. 
719 lines changed or deleted 722 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/