draft-ietf-vcarddav-vcardrev-05.txt   draft-ietf-vcarddav-vcardrev-06.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) November 3, 2008 Updates: 2739 (if approved) March 5, 2009
Intended status: Standards Track Intended status: Standards Track
Expires: May 7, 2009 Expires: September 6, 2009
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-05 draft-ietf-vcarddav-vcardrev-06
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79. This document may contain material
have been or will be disclosed, and any of which he or she becomes from IETF Documents or IETF Contributions published or made publicly
aware will be disclosed, in accordance with Section 6 of BCP 79. available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 May 7, 2009. This Internet-Draft will expire on September 6, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
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 an individual (e.g.,
formatted and structured name and delivery addresses, email address, formatted and structured name and delivery addresses, email address,
multiple telephone numbers, photograph, logo, audio clips, etc.). multiple telephone numbers, photograph, logo, audio clips, etc.).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 5 3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 5
4. vCard Format Specification . . . . . . . . . . . . . . . . . . 6 4. vCard Format Specification . . . . . . . . . . . . . . . . . . 6
4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 7 4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 7
4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 8 4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 8
5. Property Value Data Types . . . . . . . . . . . . . . . . . . 10 4.3. Property Value Escaping . . . . . . . . . . . . . . . . . 10
5. Property Value Data Types . . . . . . . . . . . . . . . . . . 11
5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3. DATE, TIME, and DATE-TIME . . . . . . . . . . . . . . . . 13 5.3. DATE, TIME, and DATE-TIME . . . . . . . . . . . . . . . . 13
5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.8. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 15 5.8. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 15
5.9. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 15
6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 15 6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 15
6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16 6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.4. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.5. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 18 6.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1. General Properties . . . . . . . . . . . . . . . . . . . . 18 7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 19
7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 18 7.1. General Properties . . . . . . . . . . . . . . . . . . . . 19
7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 19 7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 19 7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 20
7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 20
7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.2. Identification Properties . . . . . . . . . . . . . . . . 21 7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 21 7.2. Identification Properties . . . . . . . . . . . . . . . . 22
7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 21 7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 22 7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 22 7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 23
7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 23 7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 24 7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 25
7.2.9. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 24 7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 25
7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 24 7.2.9. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 25
7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 26
7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 25 7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.4. Communications Properties . . . . . . . . . . . . . . . . 25 7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 26
7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 25 7.4. Communications Properties . . . . . . . . . . . . . . . . 27
7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 26 7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 28
7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.5. Geographical Properties . . . . . . . . . . . . . . . . . 27 7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.5. Geographical Properties . . . . . . . . . . . . . . . . . 29
7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.6. Organizational Properties . . . . . . . . . . . . . . . . 28 7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 28 7.6. Organizational Properties . . . . . . . . . . . . . . . . 30
7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 30
7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 30 7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 30 7.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 31 7.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 32
7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 32 7.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 33
7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 32 7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 34
7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 34
7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 33 7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 35
7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 33 7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 34 7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 36
7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 35 7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 37
7.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 35 7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 35 7.7.8. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 38
7.8. Security Properties . . . . . . . . . . . . . . . . . . . 36 7.7.9. URL . . . . . . . . . . . . . . . . . . . . . . . . . 38
7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 36 7.7.10. VERSION . . . . . . . . . . . . . . . . . . . . . . . 39
7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.8. Security Properties . . . . . . . . . . . . . . . . . . . 39
7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 37 7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 39
7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 37 7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 38 7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 40
7.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 38 7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 40
7.10. Extended Properties and Parameters . . . . . . . . . . . . 38 7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 41
8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 38 7.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 41
8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 39 7.10. Extended Properties and Parameters . . . . . . . . . . . . 42
8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 39 8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 42
9. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . . 41 8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 42
10. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 50 8.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 42
11. Security Considerations . . . . . . . . . . . . . . . . . . . 50 8.1.2. Matching Property Instances . . . . . . . . . . . . . 43
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 8.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 43
12.1. Registering New vCard Elements . . . . . . . . . . . . . . 51 8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 44
12.1.1. Registration Procedure . . . . . . . . . . . . . . . . 51 8.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 44
12.1.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 52 8.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 44
12.1.3. Registration Template for Groups . . . . . . . . . . . 52 8.2.3. Adding and Sharing a Property . . . . . . . . . . . . 45
12.1.4. Registration Template for Properties . . . . . . . . . 52 8.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 45
12.1.5. Registration Template for Parameters . . . . . . . . . 53 8.2.5. Global Context Simplification . . . . . . . . . . . . 47
12.1.6. Registration Template for Value Data Types . . . . . . 53 9. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . . 47
12.1.7. Registration Template for Values . . . . . . . . . . . 54 10. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 56
12.2. Initial vCard Elements Registries . . . . . . . . . . . . 54 11. Security Considerations . . . . . . . . . . . . . . . . . . . 57
12.2.1. Groups Registry . . . . . . . . . . . . . . . . . . . 55 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57
12.2.2. Properties Registry . . . . . . . . . . . . . . . . . 55 12.1. Registering New vCard Elements . . . . . . . . . . . . . . 57
12.2.3. Parameters Registry . . . . . . . . . . . . . . . . . 57 12.1.1. Registration Procedure . . . . . . . . . . . . . . . . 58
12.2.4. Value Data Types Registry . . . . . . . . . . . . . . 57 12.1.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 58
12.2.5. Values Registries . . . . . . . . . . . . . . . . . . 57 12.1.3. Registration Template for Groups . . . . . . . . . . . 59
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 59 12.1.4. Registration Template for Properties . . . . . . . . . 59
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 59 12.1.5. Registration Template for Parameters . . . . . . . . . 60
14.1. Normative References . . . . . . . . . . . . . . . . . . . 59 12.1.6. Registration Template for Value Data Types . . . . . . 60
14.2. Informative References . . . . . . . . . . . . . . . . . . 61 12.1.7. Registration Template for Values . . . . . . . . . . . 60
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 62 12.2. Initial vCard Elements Registries . . . . . . . . . . . . 61
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 62 12.2.1. Groups Registry . . . . . . . . . . . . . . . . . . . 61
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 62 12.2.2. Properties Registry . . . . . . . . . . . . . . . . . 62
A.3. New Properties and Parameters . . . . . . . . . . . . . . 62 12.2.3. Parameters Registry . . . . . . . . . . . . . . . . . 64
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 63 12.2.4. Value Data Types Registry . . . . . . . . . . . . . . 64
12.2.5. Values Registries . . . . . . . . . . . . . . . . . . 64
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 66
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66
14.1. Normative References . . . . . . . . . . . . . . . . . . . 66
14.2. Informative References . . . . . . . . . . . . . . . . . . 68
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 69
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 69
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 69
A.3. New Properties and Parameters . . . . . . . . . . . . . . 69
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) . . . . . . . . . . . . . . . . . . . . 63 publication) . . . . . . . . . . . . . . . . . . . . 70
B.1. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 63 B.1. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 70
B.2. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 63 B.2. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 71
B.3. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 64 B.3. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 71
B.4. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 64 B.4. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 71
B.5. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 64 B.5. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 72
B.6. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 65 B.6. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 72
B.7. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 73
1. Introduction 1. Introduction
Note: This draft contains much of the same text as 2425 and 2426 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 which may not be correct. Those two RFCs have been merged and the
structure of this draft is what's new. Some vCard-specific structure of this draft is what's new. Some vCard-specific
suggestions have been added, but for the most part this is still very 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 open. But we'd like to get feedback on the structure mostly so that
it may be fixed. it may be fixed.
skipping to change at page 5, line 52 skipping to change at page 5, line 52
as defined in [RFC2046], section 4.1.2. If it is omitted, the as defined in [RFC2046], section 4.1.2. If it is omitted, the
default encoding is UTF-8 as defined in [RFC3629]. default encoding is UTF-8 as defined in [RFC3629].
Security considerations: See Section 11. Security considerations: See Section 11.
Interoperability considerations: The text/vcard media type is Interoperability considerations: The text/vcard media type is
intended to identify vCard data of any version. There are older intended to identify vCard data of any version. There are older
specifications of vCard [RFC2426][oldreference_VCARD] still in specifications of vCard [RFC2426][oldreference_VCARD] still in
common use. While these formats are similar, they are not common use. While these formats are similar, they are not
strictly compatible. In general, it is necessary to inspect the strictly compatible. In general, it is necessary to inspect the
value of the VERSION property (see Section 7.7.9) for identifying value of the VERSION property (see Section 7.7.10) for identifying
the standard to which a given vCard object conforms. the standard to which a given vCard object conforms.
In addition, the following media types are known to have been used In addition, the following media types are known to have been used
to refer to vCard data. They should be considered deprecated in to refer to vCard data. They should be considered deprecated in
favor of text/vcard. favor of text/vcard.
* text/directory * text/directory
* text/directory; type=vcard * text/directory; type=vcard
* text/x-vcard * text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-05 Published specification: draft-ietf-vcarddav-vcardrev-06
Applications that use this media type: They are numerous, diverse, Applications that use this media type: They are numerous, diverse,
and include mail user agents, instant messaging clients, address and include mail user agents, instant messaging clients, address
book applications, directory servers, customer relationship book applications, directory servers, customer relationship
management software, etc. management software, etc.
Additional information: Additional information:
Magic number(s): Magic number(s):
skipping to change at page 10, line 23 skipping to change at page 10, line 23
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 For example, groups named "WORK" and "HOME" could be used to
segregate properties such as telephone number, address, etc. segregate properties such as telephone number, address, etc.
Displaying of groups is left entirely up to the application. Displaying of groups is left entirely up to the application.
Predefined groups with assigned meaning are listed in Section 12.2.1. Predefined groups with assigned meaning are listed in Section 12.2.1.
It is possible to register new groups from IANA. Unregistered groups It is possible to register new groups from IANA. Unregistered groups
MAY be used and MUST start with "X-". MAY be used and MUST start with "X-".
Each property defined in a vCard instance MAY have multiple values. Properties defined in a vCard instance may have multiple values
The general rule for encoding multi-valued properties is to simply depending on the property cardinality. The general rule for encoding
create a new content line for each value (including the property multi-valued properties is to simply create a new content line for
name). However, it should be noted that some value types support each value (including the property name). However, it should be
encoding multiple values in a single content line by separating the noted that some value types support encoding multiple values in a
values with a comma ",". This approach has been taken for several of single content line by separating the values with a comma ",". This
the content types defined below (date, time, integer, float), for approach has been taken for several of the content types defined
space-saving reasons. below (date, time, integer, float), for space-saving reasons.
5. Property Value Data Types 4.3. Property Value Escaping
Lists of values are delimited by a list delimiter, specified by the A property instance may contain one or more values delimited by a
COMMA character (ASCII decimal 44). A COMMA character in a value COMMA character (ASCII decimal 44). Therefore, a COMMA character in
MUST be escaped with a BACKSLASH character (ASCII decimal 92). a value MUST be escaped with a BACKSLASH character (ASCII decimal
92), even for properties that don't allow multiple instances (for
consistency).
Compound type values are delimited by a field delimiter, specified by Some properties (e.g. N and ADR) comprise multiple fields delimited
the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI-
component of a compound property value MUST be escaped with a COLON in a field of such a "compound" property MUST be escaped with a
BACKSLASH character (ASCII decimal 92). BACKSLASH character. SEMI-COLON characters in non-compound
properties MUST NOT be escaped.
Furthermore, some fields of compound properties may contain a list of
values delimited by a COMMA character. Therefore, a COMMA character
in one of a field's values MUST be escaped with a BACKSLASH
character, even for fields that don't allow multiple values (for
consistency). Compound properties allowing multiple instances MUST
NOT be encoded in a single content line.
Finally, newline (ASCII decimal 10) and backslash (ASCII decimal 92)
characters in values MUST be escaped by prefixing them with a
backslash character.
In all other cases, escaping MUST NOT be used.
5. Property Value Data Types
Standard value types are defined below. Standard value types are defined below.
valuespec = text-list valuespec = text-list
/ URI ; from Appendix A of [RFC3986] / URI ; from Appendix A of [RFC3986]
/ date-list / date-list
/ time-list / time-list
/ date-time-list / date-time-list
/ boolean / boolean
/ integer-list / integer-list
skipping to change at page 15, line 20 skipping to change at page 15, line 38
The value type is an offset from Coordinated Universal Time (UTC). The value type is an offset from Coordinated Universal Time (UTC).
It is specified as a positive or negative difference in units of It is specified as a positive or negative difference in units of
hours and minutes (e.g., +hh:mm). The time is specified as a 24-hour hours and minutes (e.g., +hh:mm). The time is specified as a 24-hour
clock. Hour values are from 00 to 23, and minute values are from 00 clock. Hour values are from 00 to 23, and minute values are from 00
to 59. Hour and minutes are 2-digits with high order zeroes required to 59. Hour and minutes are 2-digits with high order zeroes required
to maintain digit count. The extended format for ISO 8601 UTC to maintain digit count. The extended format for ISO 8601 UTC
offsets MUST be used. The extended format makes use of a colon offsets MUST be used. The extended format makes use of a colon
character as a separator of the hour and minute text fields. character as a separator of the hour and minute text fields.
5.9. LANGUAGE-TAG
"language-tag": A single language tag, as defined in [RFC4646].
6. Property Parameters 6. 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
skipping to change at page 16, line 27 skipping to change at page 16, line 37
valuetypeparam = "value" "=" valuetype valuetypeparam = "value" "=" valuetype
valuetype = "uri" ; URI from Appendix A of [RFC3986] valuetype = "uri" ; URI from Appendix A of [RFC3986]
/ "text" / "text"
/ "date" / "date"
/ "time" / "time"
/ "date-time" ; date time / "date-time" ; date time
/ "integer" / "integer"
/ "boolean" / "boolean"
/ "float" / "float"
/ "language-tag"
/ x-name / x-name
/ iana-token ; registered as described in / iana-token ; registered as described in
; section 12 of this document ; section 12 of this document
languageparam = "language" "=" Language-Tag languageparam = "language" "=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 4646 ; Language-Tag is defined in section 2.1 of RFC 4646
pref-param = "pref" pref-param = "pref" "=" pref-value
pref-value = 1*DIGIT
pid-param = ("pid" "=" pid-value *("," pid-value)) pid-param = ("pid" "=" pid-value *("," pid-value))
pid-value = 1*DIGIT pid-value = 1*DIGIT
Applications MUST ignore x-param and iana-param value they don't Applications MUST ignore x-param and iana-param value they don't
recognize. recognize.
6.1. LANGUAGE 6.1. LANGUAGE
The "language" property parameter is used to identify data in The "language" property parameter is used to identify data in
skipping to change at page 18, line 5 skipping to change at page 18, line 15
properties. properties.
Including the value type explicitly as part of each property provides Including the value type explicitly as part of each property provides
an extra hint to keep parsing simple and support more generalized an extra hint to keep parsing simple and support more generalized
applications. For example a search engine would not have to know the applications. For example a search engine would not have to know the
particular value types for all of the items for which it is particular value types for all of the items for which it is
searching. Because the value type is explicit in the definition, the searching. Because the value type is explicit in the definition, the
search engine could look for dates in any item type and provide search engine could look for dates in any item type and provide
results that can still be interpreted. results that can still be interpreted.
6.4. PID 6.4. PREF
The "pref" parameter is optional, and is used to indicate that the
corresponding instance of a property is preferred by the vCard
author. Its value MUST be a strictly positive integer that
quantifies the level of preferredness. Lower values correspond to a
higher level of preferrredness, 1 being most preferred. The value
zero MUST NOT be used.
When the parameter is absent, the default MUST be to interpret the
property instance as being least preferred.
Note that the value of this parameter is to be interpreted only in
relation to values assigned to other instances of the same property
in the same vCard. A given value, or the absence of a value, MUST
NOT be interpreted on its own.
This parameter MAY be applied to any property that allows multiple
instances.
6.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 (Section 7.7.7) on a per-property instead of per-vCard basis. It MAY
MUST NOT appear more than once in a given property. It MUST NOT appear more than once in a given property. It MUST NOT appear on
appear on properties that only may have one instance per vCard. Its properties that only may have one instance per vCard. Its value is
value is a small integer. For synchronization purposes, it MAY either a single small integer, or a pair of small integers separated
contain more than one value to resolve conflicts (see Section 8). by a dot. Multiple values may be encoded in a single PID parameter
Note that the "pid" parameter's values are not globally unique, so it by separating the values with a comma ",". See Section 8 for more
is possible for duplicate values to be created. details on its usage.
6.5. TYPE 6.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: PHOTO, ADR, LABEL, TEL, EMAIL, IMPP, LOGO,
MEMBER, SOUND, and KEY. MEMBER, SOUND, and KEY.
7. vCard Properties 7. 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:
+-------------+--------------------------------------------------+
| Cardinality | Meaning |
+-------------+--------------------------------------------------+
| (1,1) | Exactly one instance per vCard MUST be present. |
| (0,1) | Exactly one instance per vCard MAY be present. |
| (1,n) | One or more instances per vCard MUST be present. |
| (0,n) | One or more instances per vCard MAY be present. |
+-------------+--------------------------------------------------+
7.1. General Properties 7.1. General Properties
7.1.1. BEGIN 7.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)
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".
The BEGIN property is used in conjunction with the END property to The BEGIN property is used in conjunction with the END property to
delimit an entity containing a related set of properties within an delimit an entity containing a related set of properties within an
text/vcard content-type. This construct can be used instead of or text/vcard content-type. This construct can be used instead of or
in addition to wrapping separate sets of information inside in addition to wrapping separate sets of information inside
additional MIME headers. It is provided for applications that additional MIME headers. It is provided for applications that
wish to define content that can contain multiple entities within wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be the same text/vcard content-type or to define content that can be
skipping to change at page 19, line 16 skipping to change at page 20, line 12
BEGIN:VCARD BEGIN:VCARD
7.1.2. END 7.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)
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".
The END property is used in conjunction with the BEGIN property to The END property is used in conjunction with the BEGIN property to
delimit an entity containing a related set of properties within an delimit an entity containing a related set of properties within an
text/vcard content-type. This construct can be used instead of or text/vcard content-type. This construct can be used instead of or
in addition to wrapping separate sets of information inside in addition to wrapping separate sets of information inside
additional MIME headers. It is provided for applications that additional MIME headers. It is provided for applications that
wish to define content that can contain multiple entities within wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be the same text/vcard content-type or to define content that can be
skipping to change at page 19, line 39 skipping to change at page 20, line 37
END:VCARD END:VCARD
7.1.3. SOURCE 7.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)
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
be included. be included.
skipping to change at page 20, line 17 skipping to change at page 21, line 17
SOURCE:http://directory.example.com/addressbooks/jdoe/ SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf Jean%20Dupont.vcf
7.1.4. NAME 7.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)
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
value is the displayable, presentation text associated with the value is the displayable, presentation text associated with the
source for the vCard, as specified in the SOURCE property. source for the vCard, as specified in the SOURCE property.
Example: Example:
NAME:Babs Jensen's Contact Information NAME:Babs Jensen's Contact Information
7.1.5. KIND 7.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)
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, an x-name or an iana-
token. If this property is absent, "individual" MUST be assumed token. If this property is absent, "individual" MUST be assumed
as default. as default.
Example: Example:
This represents someone named Jane Doe working in the marketing This represents someone named Jane Doe working in the marketing
department of the North American division of ABC Inc. department of the North American division of ABC Inc.
skipping to change at page 21, line 27 skipping to change at page 22, line 27
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 7.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)
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.
Example: Example:
FN:Mr. John Q. Public\, Esq. FN:Mr. John Q. Public\, Esq.
7.2.2. N 7.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)
Special note: The structured property value corresponds, in Special note: The structured property value corresponds, in
sequence, to the Surname, Given Names, Honorific Prefixes, and sequence, to the Surname, Given Names, Honorific Prefixes, and
Honorific Suffixes. The text components are separated by the Honorific Suffixes. The text components are separated by the
SEMI-COLON character (ASCII decimal 59). Individual text SEMI-COLON character (ASCII decimal 59). Individual text
components can include multiple text values (e.g., multiple components can include multiple text values (e.g., multiple
Additional Names) separated by the COMMA character (ASCII decimal Additional Names) separated by the COMMA character (ASCII decimal
44). This property is based on the semantics of the X.520 44). This property is based on the semantics of the X.520
individual name attributes. The property SHOULD be present in the individual name attributes. The property SHOULD be present in the
vCard object when the name of the object the vCard represents vCard object when the name of the object the vCard represents
follows the X.520 model. follows the X.520 model.
skipping to change at page 22, line 20 skipping to change at page 23, line 24
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 7.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)
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.
Examples: Examples:
NICKNAME:Robbie NICKNAME:Robbie
NICKNAME:Jim,Jimmie NICKNAME:Jim,Jimmie
WORK.NICKNAME:Boss
7.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
a value outside of this MIME entity. a value outside of this MIME entity.
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.
Example: Example:
PHOTO;VALUE=uri:http://www.example.com/pub/photos PHOTO;VALUE=uri:http://www.example.com/pub/photos
/jqpublic.gif /jqpublic.gif
skipping to change at page 23, line 23 skipping to change at page 24, line 35
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
7.2.5. BDAY 7.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 value. It can also be Value type: The default is a single date value. It can also be
reset to a single date-time or text value. reset to a single date-time or text value.
Cardinality: (0,1)
Examples: Examples:
BDAY:1996-04-15 BDAY:1996-04-15
BDAY:1953-10-15T23:10:00Z BDAY:1953-10-15T23:10:00Z
BDAY;VALUE=text:circa 1800 BDAY;VALUE=text:circa 1800
7.2.6. DDAY 7.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 value. It can also be Value type: The default is a single date value. It can also be
reset to a single date-time or text value. reset to a single date-time or text value.
Cardinality: (0,1)
7.2.7. BIRTH 7.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)
Example: Example:
BIRTH:Babies'R'Us Hospital BIRTH:Babies'R'Us Hospital
7.2.8. DEATH 7.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)
Example: Example:
DEATH:Aboard the Titanic\, near Newfoundland DEATH:Aboard the Titanic\, near Newfoundland
7.2.9. GENDER 7.2.9. GENDER
Purpose: To specify the gender of the object the vCard represents. Purpose: To specify the gender of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,1)
Special notes: The value "M" stands for male while "F" stands for Special notes: The value "M" stands for male while "F" stands for
female. female. IANA-registered values and x-names are also allowed.
Example: Example:
GENDER:F GENDER:F
7.3. Delivery Addressing Properties 7.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 7.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)
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 25, line 27 skipping to change at page 27, line 5
ADR:;;123 Main Street;Any Town;CA;91921-1234 ADR:;;123 Main Street;Any Town;CA;91921-1234
7.3.2. LABEL 7.3.2. LABEL
Purpose: To specify the formatted text corresponding to delivery Purpose: To specify the formatted text corresponding to 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)
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.
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.
skipping to change at page 26, line 5 skipping to change at page 27, line 33
7.4.1. TEL 7.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)
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. prefered-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
skipping to change at page 26, line 28 skipping to change at page 28, line 9
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 (i.e.,
"TYPE=text;TYPE=voice") or as a value list (i.e., "TYPE=text;TYPE=voice") or as a value list (i.e.,
"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".
Example: Example:
WORK.TEL;PREF;TYPE=voice,msg:tel:+1-555-555-5555;ext=5555 WORK.TEL;PREF=1;TYPE=voice,msg:tel:+1-555-555-5555;ext=5555
HOME.TEL:tel:+33-01-23-45-67 HOME.TEL:tel:+33-01-23-45-67
7.4.2. EMAIL 7.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)
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.
Type example: Type example:
WORK.EMAIL:jqpublic@xyz.example.com WORK.EMAIL:jqpublic@xyz.example.com
EMAIL;PREF:jane_doe@example.com EMAIL;PREF=1:jane_doe@example.com
7.4.3. IMPP 7.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)
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.
Example: Example:
IMPP;PREF:xmpp:alice@example.com IMPP;PREF=1:xmpp:alice@example.com
7.4.4. LANG 7.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 list of text values. Value type: A single language-tag value.
Special notes: The list is to be interpreted as defined in Cardinality: (0,n)
[RFC2616], Section 14.4, i.e. as the value of an Accept-Language
HTTP header. This lets one specify preference among languages.
Note that any SEMI-COLON character (ASCII decimal 59) must be
escaped.
Example: Example:
LANG:fr,en\;q=0.9 WORK.LANG;PREF=1:en
WORK.LANG;PREF=2:fr
HOME.LANG=fr
7.5. Geographical Properties 7.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 7.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 utc-offset value. It can also Value type: The default is a single utc-offset value. It can also
be reset to a single text value. be reset to a single text value.
Cardinality: (0,n)
Special notes: The type value consists of a single value. Special notes: The type value consists of a single value.
Type examples: Type examples:
TZ:-05:00 TZ:-05:00
TZ;VALUE=text:-05:00; EST; Raleigh/North America TZ;VALUE=text:-05:00; 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 7.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 structured value consisting of two float values Value type: A single structured value consisting of two float values
separated by the SEMI-COLON character (ASCII decimal 59). separated by the SEMI-COLON character (ASCII decimal 59).
Cardinality: (0,n)
Special notes: This property specifies information related to the Special notes: This property specifies information related to the
global position of the object associated with the vCard. The global position of the object associated with the vCard. The
value specifies latitude and longitude, in that order (i.e., "LAT value specifies latitude and longitude, in that order (i.e., "LAT
LON" ordering). The longitude represents the location east and LON" ordering). The longitude represents the location east and
west of the prime meridian as a positive or negative real number, west of the prime meridian as a positive or negative real number,
respectively. The latitude represents the location north and respectively. The latitude represents the location north and
south of the equator as a positive or negative real number, south of the equator as a positive or negative real number,
respectively. The longitude and latitude values MUST be expressed respectively. The longitude and latitude values MUST be expressed
in the [WGS84] reference system. They MUST be specified as in the [WGS84] reference system. They MUST be specified as
decimal degrees and should be specified to six decimal places. decimal degrees and should be specified to six decimal places.
skipping to change at page 29, line 7 skipping to change at page 30, line 44
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 7.6.1. TITLE
Purpose: To specify the job title, functional position or function Purpose: To specify the job title, functional position or function
of the object the vCard represents. of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
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.
Example: Example:
TITLE:Director\, Research and Development TITLE:Director\, Research and Development
7.6.2. ROLE 7.6.2. ROLE
Purpose: To specify information concerning the role, occupation, or Purpose: To specify information concerning the role, occupation, or
business category of the object the vCard represents. business category of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
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.
Example: Example:
ROLE:Programmer ROLE:Programmer
skipping to change at page 29, line 44 skipping to change at page 31, line 38
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)
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.
Example: Example:
LOGO;VALUE=uri:http://www.example.com/pub/logos/abccorp.jpg LOGO;VALUE=uri:http://www.example.com/pub/logos/abccorp.jpg
skipping to change at page 30, line 20 skipping to change at page 32, line 14
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
7.6.4. ORG 7.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)
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
one or more levels of organizational unit names. one or more levels of organizational unit names.
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 7.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 tpe: 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)
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".
Examples: Examples:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:group KIND:group
FN:The Doe family FN:The Doe family
MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
skipping to change at page 31, line 38 skipping to change at page 33, line 38
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 7.6.6. RELATED
Purpose: To specify a relationship the individual this vCard Purpose: To specify a relationship the individual this vCard
represents has with another. represents has with another.
Value type: A single URI. 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.
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 the opposite of "parent".
* "sibling" means that the two individuals are siblings. * "sibling" means that the two individuals are siblings.
skipping to change at page 32, line 19 skipping to change at page 34, line 24
or resource associated with the vCard. or resource associated with the vCard.
Other types may be registered to IANA as described in Other types may be registered to IANA as described in
Section 12.1, and private extensions starting with "X-" may be Section 12.1, and private extensions starting with "X-" may be
used. used.
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
for any inquiries.
7.7. Explanatory Properties 7.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 7.7.1. CATEGORIES
Purpose: To specify application category information about the Purpose: To specify application category information about the
vCard. vCard.
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)
Example: Example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
7.7.2. NOTE 7.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)
Special notes: The property is based on the X.520 Description Special notes: The property is based on the X.520 Description
attribute. attribute.
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 7.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)
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 assure that the text
value is unique. value is unique.
Example: Example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
7.7.4. REV 7.7.4. REV
Purpose: To specify revision information about the current vCard. Purpose: To specify revision information about the current vCard.
Value type: The default is a single date-time value. Can also be Value type: The default is a single date-time value. Can also be
reset to a single date value. reset to a single date value.
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.
Example: Example:
REV:1995-10-31T22:27:10Z REV:1995-10-31T22:27:10Z
REV:1997-11-15 REV:1997-11-15
7.7.5. SORT-STRING 7.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)
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 locale- or national-
language- specific sorting of the formatted name and structured language- specific sorting of the formatted name and structured
name types. Without this information, sorting algorithms could name types. Without this information, sorting algorithms could
incorrectly sort this vCard within a sequence of sorted vCards. incorrectly sort this vCard within a sequence of sorted vCards.
When this property is present in a vCard, then this family name or When this property is present in a vCard, then this family name or
given name value is used for sorting the vCard. given name value is used for sorting the vCard.
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.
skipping to change at page 34, line 45 skipping to change at page 37, line 21
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)
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.
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
skipping to change at page 35, line 21 skipping to change at page 37, line 47
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
7.7.7. UID 7.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.
Special notes: The type is used to uniquely identify the object that Cardinality: (0,1)
the vCard represents. The "uuid" URN namespace defined in
Special notes: This property is used to uniquely identify the object
that the vCard represents. The "uuid" URN namespace defined in
[RFC4122] is particularly well-suited to this task, but other URI [RFC4122] is particularly well-suited to this task, but other URI
schemes MAY be used. schemes MAY be used.
This property MUST NOT appear more than once in a given vCard.
Example: Example:
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
7.7.8. URL 7.7.8. CLIENTPIDMAP
Purpose: To give a global meaning to a local PID source identifier.
Value type: A semicolon-separated pair of values. The first field
is a small integer corresponding to the second field of a PID
parameter instance. The second field is a URI. The "uuid" URN
namespace defined in [RFC4122] is particularly well-suited to this
task, but other URI schemes MAY be used.
Cardinality: (0,n)
Special notes: PID source identifiers (the source identifier is the
second field in a PID parameter instance) are small integers that
only have significance within the scope of a single vCard
instance. Each distinct source identifier present in a vCard MUST
have an associated CLIENTPIDMAP. See Section 8 for more details
on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive. Zero is not
allowed.
As a special exception, the PID parameter MUST NOT be applied to
this property.
Example:
TEL;PID=3.1,4.2:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
7.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)
Value type: A single uri value. Value type: A single uri value.
Example: Example:
URL:http://example.org/restaurant.french/~chezchic.html URL:http://example.org/restaurant.french/~chezchic.html
7.7.9. VERSION 7.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)
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
specification. specification.
Example: Example:
VERSION:4.0 VERSION:4.0
7.8. Security Properties 7.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 7.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)
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
of the owner for general access to information described by the of the owner for general access to information described by the
vCard object. vCard object.
Predefined values are: Predefined values are:
PUBLIC: This vCard MAY be shared with anyone. PUBLIC: This vCard MAY be shared with anyone.
skipping to change at page 37, line 16 skipping to change at page 40, line 22
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
reset to text value. The text value can be used to specify a text reset to uri value. The uri value can be used to specify a value
key. outside of this MIME entity. In this case, the key's media type
is obtained externally (e.g. with the HTTP Content-Type header)
instead of with the TYPE parameter.
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].
Example: Examples:
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 7.9. Calendar Properties
These properties are further specified in [RFC2739]. These properties are further specified in [RFC2739].
skipping to change at page 37, line 36 skipping to change at page 41, line 4
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 7.9. Calendar Properties
These properties are further specified in [RFC2739]. These properties are further specified in [RFC2739].
7.9.1. FBURL 7.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)
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, it's file type should be "ifb".
Examples: Examples:
FBURL;PREF: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 7.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)
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.
Example: Example:
CALADRURI;PREF:mailto:janedoe@example.com CALADRURI;PREF=1:mailto:janedoe@example.com
CALDARURI:http://example.com/calendar/jdoe CALADRURI:http://example.com/calendar/jdoe
7.9.3. CALURI 7.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)
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, it's file
type should be "ics". type should be "ics".
Examples: Examples:
CALURI;PREF: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 7.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 8. 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 8.1. Mechanisms
Two vCards for which the UID properties (Section 7.7.7) are Two mechanisms are available: the UID property is used to match
equivalent MUST be considered representations of the same object. multiple instances of the same vCard, while the PID parameter is used
Equivalence is determined as specified in [RFC3986], Section 6. to match multiple instances of the same property.
vCards without a UID property MAY be matched to vCards with a UID The term "matching" is used here to mean recognizing that two
property where a synchronization engine determines there is instances are in fact representations of the same object. For
sufficient similarity to assume equivalence. The particular strategy example, a single vCard that is shared with someone results in two
and criteria used is out of scope for this document. vCard instances. After they have evolved separately, they still
represent the same object, and therefore may be matched by a
synchronization engine.
Updates to vCards with multiple instances of particular properties 8.1.1. Matching vCard Instances
MAY use the PID associated with each property to aid in determining
what values have changed. Since PIDs are not globally unique, they
can only be used as guidelines to synchronization engine logic. Such
logic is out of scope for this document.
Note that when a synchronization engine performs conflict resolution, vCard instances for which the UID properties (Section 7.7.7) are
it is possible that new values, from multiple sources and with equivalent MUST be matched. Equivalence is determined as specified
different PIDs, are in fact the same value. In such a situation, a in [RFC3986], Section 6.
synchronization engine MAY choose to represent this situation by
using multiple PID values - first the final desired PID value,
followed by a ",", followed by any prior PID values for that
particular property. The recipient of multiple PID values for a
single property should update to only use the desired new PID value
in future communications.
8.2. Example In all other cases, vCard instances MAY be matched at the discretion
of the synchronization engine.
Two vCards are to be synchronized: 8.1.2. Matching Property Instances
Property instances belonging to unmatched vCards MUST NOT be matched.
Property instances whose name (e.g. EMAIL, TEL, etc.) is not the
same MUST NOT be matched.
Property instances whose name is CLIENTPIDMAP are handled separately
and MUST NOT be matched. The synchronization MUST ensure that there
is consistency of CLIENTPIDMAPs among matched vCard instances.
Property instances belonging to matched vCards, whose name is the
same, and whose maximum cardinality is 1 MUST be matched.
Property instances belonging to matched vCards, whose name is the
same, and whose PID parameters match MUST be matched. See
Section 8.1.3 for details on PID matching.
In all other cases, property instances MAY be matched at the
discretion of the synchronization engine.
8.1.3. PID Matching
Two PID values for which the first fields are equivalent represent
the same local value.
Two PID values representing the same local value and for which the
second fields point to CLIENTPIDMAP properties whose second field
URIs are equivalent (as specified in [RFC3986], Section 6) also
represent the same global value.
PID parameters for which at least one pair of their values represent
the same global value MUST be matched.
In all other cases, PID parameters MAY be matched at the discretion
of the synchronization engine.
For example, PID value "5.1", in the first vCard below, and PID value
"6.2", in the second vCard below, represent the same global value.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da EMAIL;PID=4.2,5.1:jdoe@example.com
FN:Jane Doe CLIENTPIDMAP:1;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
HOME.TEL;PID=1:tel:+33-01-23-45-67 CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
HOME.TEL;PID=3:tel:+1-800-555-1234
EMAIL;PID=1:jdoe@example.com
IMPP;PREF:xmpp:jdoe@example.com
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da EMAIL;PID=5.1,6.2:john@example.com
FN:Jane Doe CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
HOME.TEL;PID=1:tel:+33-01-23-45-67 CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
HOME.TEL;PID=4:tel:+1-800-555-5678
EMAIL;PID=1:jdoe@example.com
IMPP;PREF:xmpp:jdoe@example.com
END:VCARD END:VCARD
Assuming a synchronization engine is presented with the two vCards, 8.2. Example
it may decide based upon logic out of scope of this document, that
both vCards are representations of the same object, and create a 8.2.1. Creation
merged vCard such as:
The following simple vCard is first created on a given device.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:Jane Doe FN:J. Doe
HOME.TEL;PID=1:tel:+33-01-23-45-67 EMAIL;PID=1.1:jdoe@example.com
HOME.TEL;PID=3:tel:+1-800-555-1234 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
HOME.TEL;PID=4:tel:+1-800-555-5678
EMAIL;PID=1:jdoe@example.com
IMPP;PREF:xmpp:jdoe@example.com
END:VCARD END:VCARD
If the synchronization engine then is presented with an updated vCard This new vCard is assigned the UID
such as: "urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating
device. The EMAIL property is assigned PID 1, and this PID is given
global context by associating it with
"urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which represents the
creating device. The FN property has no PID because it is forbidden
by its maximum cardinality of 1.
8.2.2. Initial Sharing
This vCard is shared with a second device. Upon inspecting the UID
property, the second device understands that this is a new vCard
(i.e. unmatched) and thus the synchronization results in a simple
copy.
8.2.3. Adding and Sharing a Property
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
receives:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:Jane Doe FN:J. Doe
HOME.TEL;PID=1:tel:+33-01-23-45-67 EMAIL;PID=1.1:jdoe@example.com
HOME.TEL;PID=4:tel:+1-800-555-5678 TEL;PID=1.1:tel:+1-555-555-5555
EMAIL;PID=1:jdoe@example.com CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
EMAIL;PID=2:fred.smithdoe@example.com
IMPP;PREF:xmpp:jdoe@example.com
END:VCARD END:VCARD
It may use the PIDs on each property to determine that the second Upon inspecting the UID property, the second device matches the vCard
phone number in the sequence has been deleted, and a new email it received to the vCard that it already has stored. It then starts
address has been added. Note that there may be data beyond what is comparing the properties of the two vCards in same-named pairs.
available within a vCard, such as a speed dial number, that is
specific to each individual property instance, which is why providing
a correlation between versions is significant.
If the synchronization engine next received the following vCard from The FN properties are matched automatically because their maximum
a different source: cardinality is 1. Since the property value is the same, no update
takes place.
The EMAIL properties are matched because the PID parameters have the
same global value. Since the property value is the same, no update
takes place.
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.
Therefore, this property is copied from the new vCard to the stored
vCard.
The CLIENTPIDMAP property is handled separately by the
synchronization engine. It ensures that it is consistent with the
stored one. If it was not, the results would be up to the
synchronization engine, and thus undefined by this document.
8.2.4. Simultaneous Editing
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
happens. Here are the vCards that are communicated to each other:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:Jane Doe FN:J. Doe
TEL;PID=1;TYPE=home:tel:+33-01-23-45-67 EMAIL;PID=1.1:jdoe@example.com
TEL;PID=4;TYPE=home:tel:+1-800-555-5678 EMAIL;PID=2.1:boss@example.com
EMAIL;PID=1:jdoe@example.com TEL;PID=1.1:tel:+1-555-555-5555
EMAIL;PID=5:fred.smithdoe@example.com TEL;PID=2.1:tel:+1-666-666-6666
IMPP;TYPE=personal,pref:xmpp:jdoe@example.com CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD END:VCARD
It may determine that that the new email address with PID=5 is BEGIN:VCARD
equivalent to the existing email address with PID=2. It could inform VERSION:4.0
the new data source to use the PID value 2 by specifying the UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
following line in the vCard returned to that last source: FN:J. Doe
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1:tel:+1-555-555-5555
TEL;PID=2.2:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
EMAIL;PID=2,5:fred.smithdoe@example.com On the first device, the same PID source identifier (1) is reused for
the new EMAIL and TEL properties. On the second device, a new source
identifier (2) is generated, and a corresponding CLIENTPIDMAP
property is created. It contains the second device's identifier,
"urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".
After receipt of the updated PID values, the new source should begin The new EMAIL properties are unmatched on both sides since the PID
to use PID=2 for that email address in future communications with global value is new in both cases. The sync thus results in a copy
that synchronization engine. on both sides.
Although the situation appears to be the same for the TEL properties,
in this case the synchronization engine is particularly smart and
matches the two new TEL properties even though their PID global
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
discretion of the synchronization engine. Therefore, the two
properties are merged.
All this results in the following vCard which is stored on both
devices:
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1:tel:+1-555-555-5555
TEL;PID=2.1,2.2:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
8.2.5. Global Context Simplification
The two devices finish their synchronization procedure by simplifying
their global contexts. Since they haven't talked to any other
device, the following vCard is for all purposes equivalent to the
above. It is also shorter.
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=3.1:ceo@example.com
TEL;PID=1.1:tel:+1-555-555-5555
TEL;PID=2.1:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
The details of global context simplification are unspecified by this
document. They are left up to the synchronization engine. This
example is merely intended to illustrate the possibility, which
investigating would be, in the authors' opinion, worthwhile.
9. Formal Grammar 9. Formal Grammar
The following formal grammar is provided to assist developers in The following formal grammar is provided to assist developers in
building parsers for the vCard. building parsers for the vCard.
This syntax is written according to the form described in [RFC5234], This syntax is written according to the form described in [RFC5234],
but it references just this small subset of [RFC5234] literals: but it references just this small subset of [RFC5234] literals:
;******************************************* ;*******************************************
skipping to change at page 42, line 39 skipping to change at page 49, line 4
quoted-string = DQUOTE QSAFE-CHAR DQUOTE quoted-string = DQUOTE QSAFE-CHAR DQUOTE
NON-ASCII = %x80-FF NON-ASCII = %x80-FF
; Use is restricted by outer MIME object (UTF-8 preferred) ; Use is restricted by outer MIME object (UTF-8 preferred)
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE ; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":", "," ; Any character except CTLs, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / VCHAR / NON-ASCII VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character ; Any textual character
;******************************************* ;*******************************************
; vCard Type Definition ; vCard Property Definitions
; ;
; Provides type-specific definitions for how the ; Provides property-specific definitions for how the
; "value" and "param" are defined. ; "value" and "param" are defined.
;******************************************* ;*******************************************
; **** NAME **** ; **** NAME ****
param = "" param = ""
; No parameters allowed ; No parameters allowed
value = text-value value = text-value
; **** KIND **** ; **** KIND ****
param = "" param = ""
; No parameters allowed ; No parameters allowed
value = kind-value value = kind-value
kind-value = "individual" / "group" / "org" / x-name / iana-token kind-value = "individual" / "group" / "org" / x-name / iana-token
skipping to change at page 43, line 22 skipping to change at page 49, line 35
kind-value = "individual" / "group" / "org" / x-name / iana-token kind-value = "individual" / "group" / "org" / x-name / iana-token
; **** PROFILE **** ; **** PROFILE ****
param = "" param = ""
; No parameters allowed ; No parameters allowed
value = text-value value = text-value
; Value MUST be the case insensitive value "VCARD ; Value MUST be the case insensitive value "VCARD
; **** SOURCE **** ; **** SOURCE ****
param = source-param param = source-param / pid-param
; Only source parameters allowed
value = uri value = uri
source-param = ("VALUE" "=" "uri") source-param = ("VALUE" "=" "uri")
/ (x-name "=" *SAFE-CHAR) / (x-name "=" *SAFE-CHAR)
; **** FN **** ; **** FN ****
;This type MUST be included in a vCard object. ;This type MUST be included in a vCard object.
param = text-param param = text-param
; Text parameters allowed ; Text parameters allowed
skipping to change at page 44, line 26 skipping to change at page 50, line 37
param =/ ("VALUE" "=" "date-time") param =/ ("VALUE" "=" "date-time")
; Only value parameter allowed ; Only value parameter allowed
value = date-value value = date-value
; Value MUST match value type ; Value MUST match value type
value =/ date-time-value value =/ date-time-value
; Value MUST match value type ; Value MUST match value type
; **** GENDER ****
param = ""
; No parameters allowed
value = "M" / "F" / iana-token / x-name
; Value are case insensitive
; **** ADR **** ; **** ADR ****
param = text-param / pref-param / pid-param param = text-param / pref-param / pid-param
value = adr-value value = adr-value
; **** LABEL **** ; **** LABEL ****
param = text-param / pref-param / pid-param param = text-param / pref-param / pid-param
value = text-value value = text-value
; **** TEL **** ; **** TEL ****
param = pref-param / tel-param / pid-param param = pref-param / tel-param / pid-param
; Only tel parameters allowed ; Only tel parameters allowed
value = uri-value value = uri-value
tel-param = "TYPE" "=" tel-type *("," tel-type) tel-param = "TYPE" "=" tel-type *("," tel-type)
tel-type = "VOICE" / "FAX" / "CELL" / "PAGER" tel-type = "VOICE" / "FAX" / "CELL" / "PAGER"
skipping to change at page 46, line 4 skipping to change at page 52, line 22
; **** MEMBER **** ; **** MEMBER ****
param = pid-param param = pid-param
value = uri value = uri
; Any valid URI scheme ; Any valid URI scheme
; **** RELATED **** ; **** RELATED ****
param = ("TYPE" "=" related-type) / pid-param param = ("TYPE" "=" related-type) / pid-param
; Value is case insensitive ; Value is case insensitive
value = uri value = uri
; Any valid URI scheme ; Any valid URI scheme
related-type = "parent" / "child" / "sibling" / "manager" related-type = "parent" / "child" / "sibling" / "manager"
/ "assistant" / iana-token / "X-" word / "assistant" / "agent" / iana-token / x-name
; Values are case insensitive ; Values are case insensitive
; **** CATEGORIES **** ; **** CATEGORIES ****
param = text-param / pid-param param = text-param / pid-param
; Only text parameters allowed ; Only text parameters allowed
value = text-value-list value = text-value-list
; **** NOTE **** ; **** NOTE ****
param = text-param / pid-param param = text-param / pid-param
skipping to change at page 47, line 17 skipping to change at page 53, line 36
; Value MUST be "b" encoded audio content ; Value MUST be "b" encoded audio content
snd-inline-param = ("VALUE" "=" "binary") snd-inline-param = ("VALUE" "=" "binary")
/ ("ENCODING" "=" "b") / ("ENCODING" "=" "b")
/ ("TYPE" "=" *SAFE-CHAR) / ("TYPE" "=" *SAFE-CHAR)
; Value MUST be an IANA registered audio type ; Value MUST be an IANA registered audio type
snd-refer-value = uri snd-refer-value = uri
; URI MUST refer to audio content of given type ; URI MUST refer to audio content of given type
snd-refer-param = ("VALUE" "=" "uri") snd-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" word) / ("TYPE" "=" *SAFE-CHAR)
; Value MUST be an IANA registered audio type ; Value MUST be an IANA registered audio type
; **** UID **** ; **** UID ****
param = "" param = ""
; No parameters allowed ; No parameters allowed
value = uri value = uri
; **** URL **** ; **** URL ****
param = pid-param param = pid-param
skipping to change at page 48, line 14 skipping to change at page 54, line 34
value =/ binary-value value =/ binary-value
key-txt-param = "TYPE" "=" keytype key-txt-param = "TYPE" "=" keytype
key-bin-param = ("TYPE" "=" keytype) key-bin-param = ("TYPE" "=" keytype)
/ ("ENCODING" "=" "b") / ("ENCODING" "=" "b")
; Value MUST be a "b" encoded key or certificate ; Value MUST be a "b" encoded key or certificate
keytype = param-value keytype = param-value
; Type MUST be a media type as defined in RFC 4288 ; Type MUST be a media type as defined in RFC 4288
; **** X- **** non-standard type ; **** X- **** non-standard property
param = text-param / (x-name "=" param-value) param = x-bin-param / x-txt-param / pid-param
; Only text or non-standard parameters allowed
value = text-value value = x-bin-value / x-txt-value
; Value and parameter MUST match
x-bin-param = ("ENCODING" "=" "b") / text-param
x-txt-param = text-param
x-bin-value = binary-value
x-txt-value = text-value-list
;******************************************* ;*******************************************
; vCard Commonly Used Parameter Definition ; vCard Commonly Used Parameter Definition
;******************************************* ;*******************************************
text-param = ("VALUE" "=" "ptext") text-param = ("VALUE" "=" "ptext")
/ ("LANGUAGE" "=" langval) / ("LANGUAGE" "=" langval)
/ (x-name "=" param-value) / (x-name "=" param-value)
langval = <a language string as defined in [RFC4646]> langval = <a language string as defined in [RFC4646]>
pref-param = "PREF" pref-param = "PREF" "=" pref-value
pref-value = 1*DIGIT
pid-param = ("PID" "=" pid-value *("," pid-value)) pid-param = "PID" "=" pid-value *("," pid-value)
pid-value = 1*DIGIT pid-value = 1*DIGIT
img-inline-value = binary-value img-inline-value = binary-value
;Value MUST be "b" encoded image content ;Value MUST be "b" encoded image content
img-inline-param img-inline-param
img-inline-param = ("VALUE" "=" "binary") img-inline-param = ("VALUE" "=" "binary")
/ ("ENCODING" "=" "b") / ("ENCODING" "=" "b")
/ ("TYPE" "=" param-value) / ("TYPE" "=" param-value)
skipping to change at page 49, line 37 skipping to change at page 56, line 16
float-value = <A single float value as defined in [RFC2425]> float-value = <A single float value as defined in [RFC2425]>
phone-number-value = phone-prefix 1*(SP 1*DIGIT) [phone-ext] phone-number-value = phone-prefix 1*(SP 1*DIGIT) [phone-ext]
phone-prefix = "+" 1*DIGIT / "(" 1*DIGIT ")" phone-prefix = "+" 1*DIGIT / "(" 1*DIGIT ")"
phone-ext = "ext." 1*DIGIT phone-ext = "ext." 1*DIGIT
uri-value = <A uri value as defined in [RFC2425]> uri-value = <A uri value as defined in [RFC2425]>
language-tag-value = langval
utc-offset-value = ("+" / "-") time-hour ":" time-minute utc-offset-value = ("+" / "-") time-hour ":" time-minute
time-hour = 2DIGIT ;00-23 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59 time-minute = 2DIGIT ;00-59
10. Example: Authors' vCards 10. 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:1983-02-03 BDAY:1983-02-03
GENDER:M GENDER:M
WORK.ORG:Viagenie WORK.ORG:Viagenie
WORK.ADR:;;2600 boul. Laurier\, suite 625; WORK.ADR:;;2600 boul. Laurier\, suite 625;
Quebec;QC;G1V 4W1;Canada Quebec;QC;G1V 4W1;Canada
WORK.TEL;TYPE=voice;PREF:tel:+1-418-656-9254;ext=102 WORK.TEL;TYPE=voice;PREF=1:tel:+1-418-656-9254;ext=102
WORK.TEL;TYPE=cell,voice,video,text:tel:+1-418-262-6501 WORK.TEL;TYPE=cell,voice,video,text:tel:+1-418-262-6501
WORK.TEL;TYPE=fax:tel:+1-418-656-9257 WORK.TEL;TYPE=fax:tel:+1-418-656-9257
WORK.EMAIL;TYPE=internet:simon.perreault@viagenie.ca WORK.EMAIL:simon.perreault@viagenie.ca
WORK.GEO:46.772673,-71.282945 WORK.GEO:46.772673,-71.282945
WORK.KEY;VALUE=uri:http://www.viagenie.ca/simon.perreault/simon.asc WORK.KEY;VALUE=uri:http://www.viagenie.ca/simon.perreault/simon.asc
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;;
GENDER:M GENDER:M
WORK.ORG:QUALCOMM Incorporated WORK.ORG:QUALCOMM Incorporated
WORK.ADR:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US WORK.ADR:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
WORK.TEL;TYPE=voice:tel:+1-858-651-4478 WORK.TEL;TYPE=voice:tel:+1-858-651-4478
WORK.EMAIL;TYPE=internet:presnick@qualcomm.com WORK.EMAIL:presnick@qualcomm.com
WORK.URL:http://www.qualcomm.com/~presnick/ WORK.URL:http://www.qualcomm.com/~presnick/
END:VCARD END:VCARD
11. Security Considerations 11. Security Considerations
o Internet mail is subject to many well known security attacks, o Internet mail is subject to many well known security attacks,
including monitoring, replay, and forgery. Care should be taken including monitoring, replay, and forgery. Care should be taken
by any directory service in allowing information to leave the by any directory service in allowing information to leave the
scope of the service itself, where any access controls can no scope of the service itself, where any access controls can no
longer be guaranteed. Applications should also take care to longer be guaranteed. Applications should also take care to
skipping to change at page 51, line 13 skipping to change at page 57, line 40
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
threats of "spoofed" vCard information is a concern, the vCard threats 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.8 SHOULD BE specified. In "URL" type described in Section 7.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 7.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.
12. IANA Considerations 12. IANA Considerations
12.1. Registering New vCard Elements 12.1. 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
skipping to change at page 52, line 43 skipping to change at page 59, line 20
A group is defined by completing the following template. A group is defined by completing the following template.
Group name: The name of the group. Group name: The name of the group.
Purpose: The purpose of the group. Give a short but clear Purpose: The purpose of the group. Give a short but clear
description. description.
Description: Any special notes about the group, how it is to be Description: Any special notes about the group, how it is to be
used, etc. 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 Example(s): One or more examples of instances of the value type
needs to be specified. needs to be specified.
12.1.4. Registration Template for Properties 12.1.4. Registration Template for Properties
A property is defined by completing the following template. A property is defined by completing the following template.
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.
12.1.5. Registration Template for Parameters 12.1.5. Registration Template for Parameters
skipping to change at page 55, line 9 skipping to change at page 61, line 38
12.2. Initial vCard Elements Registries 12.2. 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.
12.2.1. Groups Registry 12.2.1. Groups Registry
The following table is to be used to initialize the groups registry. The following table is to be used to initialize the groups registry.
+------+--------------------------------------+---------+-----------+ +------+--------------+---------+-----------------------+-----------+
| Goup | Description | Status | Reference | | Goup | Description | Status | Allowed Properties | Reference |
+------+--------------------------------------+---------+-----------+ +------+--------------+---------+-----------------------+-----------+
| WORK | Properties related to an | Current | RFCXXXX | | WORK | Properties | Current | FN, NICKNAME, PHOTO, | RFCXXXX |
| | individual's work place. | | | | | related to | | ADR, LABEL, TEL, | |
| HOME | Properties related to an | Current | RFCXXXX | | | an | | EMAIL, IMPP, LANG, | |
| | individual's home. | | | | | individual's | | TZ, GEO, TITLE, ROLE, | |
+------+--------------------------------------+---------+-----------+ | | work place. | | LOGO, ORG, RELATED, | |
| | | | CATEGORIES, NOTE, | |
| | | | SOUND, URL, KEY | |
| 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 | |
+------+--------------+---------+-----------------------+-----------+
12.2.2. Properties Registry 12.2.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 | | Property | Status | Reference |
+-------------+---------+------------------------+ +--------------+---------+-------------------------+
| SOURCE | Current | RFCXXXX, Section 7.1.3 | | SOURCE | Current | RFCXXXX, Section 7.1.3 |
| NAME | Current | RFCXXXX, Section 7.1.4 | | NAME | Current | RFCXXXX, Section 7.1.4 |
| KIND | Current | RFCXXXX, Section 7.1.5 | | KIND | Current | RFCXXXX, Section 7.1.5 |
| FN | Current | RFCXXXX, Section 7.2.1 | | FN | Current | RFCXXXX, Section 7.2.1 |
| N | Current | RFCXXXX, Section 7.2.2 | | N | Current | RFCXXXX, Section 7.2.2 |
| NICKNAME | Current | RFCXXXX, Section 7.2.3 | | NICKNAME | Current | RFCXXXX, Section 7.2.3 |
| PHOTO | Current | RFCXXXX, Section 7.2.4 | | PHOTO | Current | RFCXXXX, Section 7.2.4 |
| BDAY | Current | RFCXXXX, Section 7.2.5 | | BDAY | Current | RFCXXXX, Section 7.2.5 |
| DDAY | Current | RFCXXXX, Section 7.2.6 | | DDAY | Current | RFCXXXX, Section 7.2.6 |
| BIRTH | Current | RFCXXXX, Section 7.2.7 | | BIRTH | Current | RFCXXXX, Section 7.2.7 |
skipping to change at page 56, line 41 skipping to change at page 63, line 41
| ORG | Current | RFCXXXX, Section 7.6.4 | | ORG | Current | RFCXXXX, Section 7.6.4 |
| MEMBER | Current | RFCXXXX, Section 7.6.5 | | MEMBER | Current | RFCXXXX, Section 7.6.5 |
| RELATED | Current | RFCXXXX, Section 7.6.6 | | RELATED | Current | RFCXXXX, Section 7.6.6 |
| CATEGORIES | Current | RFCXXXX, Section 7.7.1 | | CATEGORIES | Current | RFCXXXX, Section 7.7.1 |
| NOTE | Current | RFCXXXX, Section 7.7.2 | | NOTE | Current | RFCXXXX, Section 7.7.2 |
| PRODID | Current | RFCXXXX, Section 7.7.3 | | PRODID | Current | RFCXXXX, Section 7.7.3 |
| REV | Current | RFCXXXX, Section 7.7.4 | | REV | Current | RFCXXXX, Section 7.7.4 |
| SORT-STRING | Current | RFCXXXX, Section 7.7.5 | | SORT-STRING | Current | RFCXXXX, Section 7.7.5 |
| SOUND | Current | RFCXXXX, Section 7.7.6 | | SOUND | Current | RFCXXXX, Section 7.7.6 |
| UID | Current | RFCXXXX, Section 7.7.7 | | UID | Current | RFCXXXX, Section 7.7.7 |
| URL | Current | RFCXXXX, Section 7.7.8 | | CLIENTPIDMAP | Current | RFCXXXX, Section 7.7.8 |
| VERSION | Current | RFCXXXX, Section 7.7.9 | | URL | Current | RFCXXXX, Section 7.7.9 |
| VERSION | Current | RFCXXXX, Section 7.7.10 |
| CLASS | Current | RFCXXXX, Section 7.8.1 | | CLASS | Current | RFCXXXX, Section 7.8.1 |
| KEY | Current | RFCXXXX, Section 7.8.2 | | KEY | Current | RFCXXXX, Section 7.8.2 |
| FBURL | Current | RFCXXXX, Section 7.9.1 | | FBURL | Current | RFCXXXX, Section 7.9.1 |
| CALADRURI | Current | RFCXXXX, Section 7.9.2 | | CALADRURI | Current | RFCXXXX, Section 7.9.2 |
| CALURI | Current | RFCXXXX, Section 7.9.3 | | CALURI | Current | RFCXXXX, Section 7.9.3 |
+-------------+---------+------------------------+ +--------------+---------+-------------------------+
12.2.3. Parameters Registry 12.2.3. 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 6.1 |
| ENCODING | Current | RFCXXXX, Section 6.2 | | ENCODING | Current | RFCXXXX, Section 6.2 |
| VALUE | Current | RFCXXXX, Section 6.3 | | VALUE | Current | RFCXXXX, Section 6.3 |
| PID | Current | RFCXXXX, Section 6.4 | | PID | Current | RFCXXXX, Section 6.5 |
| TYPE | Current | RFCXXXX, Section 6.5 | | TYPE | Current | RFCXXXX, Section 6.6 |
+-----------+---------+----------------------+ +-----------+---------+----------------------+
12.2.4. Value Data Types Registry 12.2.4. 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 5.7 |
| BOOLEAN | Current | RFCXXXX, Section 5.4 | | BOOLEAN | Current | RFCXXXX, Section 5.4 |
| DATE | Current | RFCXXXX, Section 5.3 | | DATE | Current | RFCXXXX, Section 5.3 |
| TIME | Current | RFCXXXX, Section 5.3 | | TIME | Current | RFCXXXX, Section 5.3 |
| DATE-TIME | Current | RFCXXXX, Section 5.3 | | DATE-TIME | Current | RFCXXXX, Section 5.3 |
| FLOAT | Current | RFCXXXX, Section 5.6 | | FLOAT | Current | RFCXXXX, Section 5.6 |
| INTEGER | Current | RFCXXXX, Section 5.5 | | INTEGER | Current | RFCXXXX, Section 5.5 |
| TEXT | Current | RFCXXXX, Section 5.1 | | TEXT | Current | RFCXXXX, Section 5.1 |
| URI | Current | RFCXXXX, Section 5.2 | | URI | Current | RFCXXXX, Section 5.2 |
| LANGUAGE-TAG | Current | RFCXXXX, Section 5.9 |
+-----------------+---------+----------------------+ +-----------------+---------+----------------------+
12.2.5. Values Registries 12.2.5. 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.
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
skipping to change at page 59, line 13 skipping to change at page 66, line 13
+----------+-----------+-----------+---------+----------------------+ +----------+-----------+-----------+---------+----------------------+
13. Acknowledgements 13. Acknowledgements
The authors would like to thank Frank Dawson and Tim Howes, the The authors would like to thank Frank Dawson and Tim Howes, the
original authors of [RFC2425] and [RFC2426], as well as the following original authors of [RFC2425] and [RFC2426], as well as the following
individuals who have participated in the drafting, review and individuals who have participated in the drafting, review and
discussion of this memo: discussion of this memo:
Marc Blanchet, Stephane Bortzmeyer, Dan Brickley, Chris Bryant, Dany Marc Blanchet, Stephane Bortzmeyer, Dan Brickley, Chris Bryant, Dany
Cauchie, Darryl Champagne, Cyrus Daboo, Lisa Dusseault, Javier Godoy, Cauchie, Darryl Champagne, Cyrus Daboo, Bernard Desruisseaux, Lisa
Helge Hess, Alexander Mayrhofer, Chris Newman, Mark Paterson, Julian Dusseault, Javier Godoy, Helge Hess, Alexander Mayrhofer, Chris
Reschke, Peter K. Sheerin, Anil Srivastava, and Kurt Zeilenga. Newman, Mark Paterson, Julian Reschke, Peter K. Sheerin, Anil
Srivastava, and Kurt Zeilenga.
14. References 14. References
14.1. Normative References 14.1. Normative References
[CCITT.E163.1988] International Telephone and Telegraph [CCITT.E163.1988] International Telephone and Telegraph
Consultative Committee, "Numbering Plan for Consultative Committee, "Numbering Plan for
the International Telephone Service", the International Telephone Service",
CCITT Recommendation E.163, 1988. CCITT Recommendation E.163, 1988.
skipping to change at page 60, line 23 skipping to change at page 67, line 23
Indicate Requirement Levels", BCP 14, Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997. RFC 2119, March 1997.
[RFC2425] Howes, T., Smith, M., and F. Dawson, "A MIME [RFC2425] Howes, T., Smith, M., and F. Dawson, "A MIME
Content-Type for Directory Information", Content-Type for Directory Information",
RFC 2425, September 1998. RFC 2425, September 1998.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME [RFC2426] Dawson, F. and T. Howes, "vCard MIME
Directory Profile", RFC 2426, September 1998. Directory Profile", RFC 2426, September 1998.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk,
H., Masinter, L., Leach, P., and T. Berners-
Lee, "Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999.
[RFC2739] Small, T., Hennessy, D., and F. Dawson, [RFC2739] Small, T., Hennessy, D., and F. Dawson,
"Calendar Attributes for vCard and LDAP", "Calendar Attributes for vCard and LDAP",
RFC 2739, January 2000. RFC 2739, January 2000.
[RFC2822] Resnick, P., "Internet Message Format", [RFC2822] Resnick, P., "Internet Message Format",
RFC 2822, April 2001. RFC 2822, April 2001.
[RFC2978] Freed, N. and J. Postel, "IANA Charset [RFC2978] Freed, N. and J. Postel, "IANA Charset
Registration Procedures", BCP 19, RFC 2978, Registration Procedures", BCP 19, RFC 2978,
October 2000. October 2000.
skipping to change at page 63, line 8 skipping to change at page 70, line 5
been added. been added.
o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI
properties, has been merged in. properties, has been merged in.
o [RFC4770], which defines the IMPP property, has been merged in. o [RFC4770], which defines the IMPP property, has been merged in.
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
own, with a positive integer value indicating the level of
preferredness.
A.4. Other Changes A.4. Other Changes
o Synchronization is addressed in Section 8. o Synchronization is addressed in Section 8.
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.
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 -05 B.1. Changes in -06
o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value.
o ABNF fixes.
o Made gender values extensible.
o Gave the PREF parameter a positive integer value.
o Removed usage of the undefined "word" ABNF production rule.
o Defined property cardinalities.
o Defined properties allowable in WORK and HOME groups.
o Simplified the LANG property to use the vCard preference
mechanism.
o Created the "language-tag" value type.
o Added PID to ABNF of SOURCE allowed parameters.
o Clarified escaping rules.
o Changed ABNF definition of non-standard X- properties.
o Removed TYPE parameter from EMAIL properties in examples.
o Created the CLIENTPIDMAP property.
o Changed PID value to a pair of small integers.
o Completely reworked synchronization mechanisms.
o Created brand new synchronization example.
B.2. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.2. Changes in -04 B.3. 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 64, line 7 skipping to change at page 71, line 47
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.3. Changes in -03 B.4. 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.4. Changes in -02 B.5. 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 64, line 46 skipping to change at page 72, line 38
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 7.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.5. Changes in -01 B.6. 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.
skipping to change at page 65, line 27 skipping to change at page 73, line 18
o Added Section 8. o Added Section 8.
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.6. Changes in -00 B.7. 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.
skipping to change at page 67, line 4 skipping to change at line 3361
Peter W. Resnick Peter W. Resnick
QUALCOMM Incorporated QUALCOMM Incorporated
5775 Morehouse Drive 5775 Morehouse Drive
San Diego, CA 92121-1714 San Diego, CA 92121-1714
US US
Phone: +1 858 651 4478 Phone: +1 858 651 4478
EMail: presnick@qualcomm.com EMail: presnick@qualcomm.com
URI: http://www.qualcomm.com/~presnick/ URI: http://www.qualcomm.com/~presnick/
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
This document was produced using xml2rfc v1.33 (of
http://xml.resource.org/) from a source in RFC-2629 XML format.
 End of changes. 142 change blocks. 
284 lines changed or deleted 679 lines changed or added

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