draft-ietf-vcarddav-vcardrev-06.txt   draft-ietf-vcarddav-vcardrev-07.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) March 5, 2009 Updates: 2739 (if approved) May 6, 2009
Intended status: Standards Track Intended status: Standards Track
Expires: September 6, 2009 Expires: November 7, 2009
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-06 draft-ietf-vcarddav-vcardrev-07
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 45 skipping to change at page 1, line 45
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 6, 2009. This Internet-Draft will expire on November 7, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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 . . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 5 3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 6
4. vCard Format Specification . . . . . . . . . . . . . . . . . . 6 4. vCard Format Specification . . . . . . . . . . . . . . . . . . 7
4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 7 4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 8
4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 8 4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 9
4.3. Property Value Escaping . . . . . . . . . . . . . . . . . 10 4.3. Property Value Escaping . . . . . . . . . . . . . . . . . 11
5. Property Value Data Types . . . . . . . . . . . . . . . . . . 11 5. Property Value Data Types . . . . . . . . . . . . . . . . . . 11
5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3. DATE, TIME, and DATE-TIME . . . . . . . . . . . . . . . . 13 5.3. DATE, TIME, DATE-TIME, and TIMESTAMP . . . . . . . . . . . 14
5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 15
5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.3.4. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 15
5.8. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 15 5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.9. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 15 5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 16
6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 15 5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.8. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 16
5.9. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 17
6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 17
6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 19 7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 20
7.1. General Properties . . . . . . . . . . . . . . . . . . . . 19 7.1. General Properties . . . . . . . . . . . . . . . . . . . . 21
7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 19 7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 20 7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 21 7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 21 7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2. Identification Properties . . . . . . . . . . . . . . . . 22 7.2. Identification Properties . . . . . . . . . . . . . . . . 24
7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 23 7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 25
7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 23 7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 26
7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 25 7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 25 7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.9. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 25 7.2.9. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 26 7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 29
7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 26 7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4. Communications Properties . . . . . . . . . . . . . . . . 27 7.4. Communications Properties . . . . . . . . . . . . . . . . 31
7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 28 7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.5. Geographical Properties . . . . . . . . . . . . . . . . . 29 7.5. Geographical Properties . . . . . . . . . . . . . . . . . 34
7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.6. Organizational Properties . . . . . . . . . . . . . . . . 30 7.6. Organizational Properties . . . . . . . . . . . . . . . . 35
7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 30 7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 35
7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 31 7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 31 7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 32 7.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 38
7.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 33 7.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 39
7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 34 7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 40
7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 34 7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 40
7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 35 7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 35 7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 41
7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 35 7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 36 7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 42
7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 37 7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 43
7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.7.8. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 38 7.7.8. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 44
7.7.9. URL . . . . . . . . . . . . . . . . . . . . . . . . . 38 7.7.9. URL . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.7.10. VERSION . . . . . . . . . . . . . . . . . . . . . . . 39 7.7.10. VERSION . . . . . . . . . . . . . . . . . . . . . . . 45
7.8. Security Properties . . . . . . . . . . . . . . . . . . . 39 7.8. Security Properties . . . . . . . . . . . . . . . . . . . 46
7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 39 7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 46
7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 40 7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 47
7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 40 7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 47
7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 41 7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 48
7.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 41 7.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 49
7.10. Extended Properties and Parameters . . . . . . . . . . . . 42 7.10. Extended Properties and Parameters . . . . . . . . . . . . 49
8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 42 8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 49
8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 42 8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 49
8.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 42 8.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 50
8.1.2. Matching Property Instances . . . . . . . . . . . . . 43 8.1.2. Matching Property Instances . . . . . . . . . . . . . 50
8.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 43 8.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 50
8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 44 8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 44 8.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 51
8.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 44 8.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 51
8.2.3. Adding and Sharing a Property . . . . . . . . . . . . 45 8.2.3. Adding and Sharing a Property . . . . . . . . . . . . 52
8.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 45 8.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 52
8.2.5. Global Context Simplification . . . . . . . . . . . . 47 8.2.5. Global Context Simplification . . . . . . . . . . . . 54
9. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . . 47 9. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 55
10. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 56 10. Security Considerations . . . . . . . . . . . . . . . . . . . 55
11. Security Considerations . . . . . . . . . . . . . . . . . . . 57 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57 11.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 56
12.1. Registering New vCard Elements . . . . . . . . . . . . . . 57 11.2. Registering New vCard Elements . . . . . . . . . . . . . . 56
12.1.1. Registration Procedure . . . . . . . . . . . . . . . . 58 11.2.1. Registration Procedure . . . . . . . . . . . . . . . . 56
12.1.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 58 11.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 57
12.1.3. Registration Template for Groups . . . . . . . . . . . 59 11.2.3. Registration Template for Groups . . . . . . . . . . . 57
12.1.4. Registration Template for Properties . . . . . . . . . 59 11.2.4. Registration Template for Properties . . . . . . . . . 58
12.1.5. Registration Template for Parameters . . . . . . . . . 60 11.2.5. Registration Template for Parameters . . . . . . . . . 58
12.1.6. Registration Template for Value Data Types . . . . . . 60 11.2.6. Registration Template for Value Data Types . . . . . . 59
12.1.7. Registration Template for Values . . . . . . . . . . . 60 11.2.7. Registration Template for Values . . . . . . . . . . . 59
12.2. Initial vCard Elements Registries . . . . . . . . . . . . 61 11.3. Initial vCard Elements Registries . . . . . . . . . . . . 60
12.2.1. Groups Registry . . . . . . . . . . . . . . . . . . . 61 11.3.1. Groups Registry . . . . . . . . . . . . . . . . . . . 60
12.2.2. Properties Registry . . . . . . . . . . . . . . . . . 62 11.3.2. Properties Registry . . . . . . . . . . . . . . . . . 60
12.2.3. Parameters Registry . . . . . . . . . . . . . . . . . 64 11.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 62
12.2.4. Value Data Types Registry . . . . . . . . . . . . . . 64 11.3.4. Value Data Types Registry . . . . . . . . . . . . . . 62
12.2.5. Values Registries . . . . . . . . . . . . . . . . . . 64 11.3.5. Values Registries . . . . . . . . . . . . . . . . . . 62
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 66 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 64
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64
14.1. Normative References . . . . . . . . . . . . . . . . . . . 66 13.1. Normative References . . . . . . . . . . . . . . . . . . . 64
14.2. Informative References . . . . . . . . . . . . . . . . . . 68 13.2. Informative References . . . . . . . . . . . . . . . . . . 66
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 69 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 67
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 69 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 67
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 69 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 67
A.3. New Properties and Parameters . . . . . . . . . . . . . . 69 A.3. New Properties and Parameters . . . . . . . . . . . . . . 67
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 70 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 68
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) . . . . . . . . . . . . . . . . . . . . 70 publication) . . . . . . . . . . . . . . . . . . . . 68
B.1. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 70 B.1. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 68
B.2. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 71 B.2. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 68
B.3. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 71 B.3. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 69
B.4. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 71 B.4. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 69
B.5. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 72 B.5. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 70
B.6. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 72 B.6. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 70
B.7. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 73 B.7. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 71
B.8. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 71
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 45 skipping to change at page 6, line 45
Subtype name: vcard Subtype name: vcard
Required parameters: none Required parameters: none
Optional parameters: charset Optional parameters: charset
Encoding considerations: The "charset" MIME parameter is interpreted Encoding considerations: The "charset" MIME parameter is interpreted
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 10.
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.10) 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-06 Published specification: draft-ietf-vcarddav-vcardrev-07
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 7, line 7 skipping to change at page 8, line 7
4. vCard Format Specification 4. vCard Format Specification
The text/vcard MIME content type (hereafter known as "vCard") The text/vcard MIME content type (hereafter known as "vCard")
contains contact information, typically pertaining to a single contains contact information, typically pertaining to a single
contact or group of contacts. The content consists of one or more contact or group of contacts. The content consists of one or more
lines in the format given below. lines in the format given below.
4.1. Line Delimiting and Folding 4.1. Line Delimiting and Folding
Individual lines within vCard are delimited by the [RFC2822] line Individual lines within vCard are delimited by the [RFC5322] line
break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII
decimal 10). Long logical lines of text can be split into a decimal 10). Long logical lines of text can be split into a
multiple-physical-line representation using the following folding multiple-physical-line representation using the following folding
technique. Content lines SHOULD be folded to a maximum width of 75 technique. Content lines SHOULD be folded to a maximum width of 75
octets. Multi-octet characters MUST remain contiguous. The octets. Multi-octet characters MUST remain contiguous. The
rationale for this folding process can be found in [RFC2822], Section rationale for this folding process can be found in [RFC5322], Section
2.1.1. 2.1.1.
A logical line MAY be continued on the next physical line anywhere A logical line MAY be continued on the next physical line anywhere
between two characters by inserting a CRLF immediately followed by a between two characters by inserting a CRLF immediately followed by a
single white space character (space, ASCII decimal 32, or horizontal single white space character (space, ASCII decimal 32, or horizontal
tab, ASCII decimal 9). At least one character must be present on the tab, ASCII decimal 9). At least one character must be present on the
folded line. Any sequence of CRLF followed immediately by a single folded line. Any sequence of CRLF followed immediately by a single
white space character is ignored (removed) when processing the white space character is ignored (removed) when processing the
content type. For example the line: content type. For example the line:
skipping to change at page 7, line 49 skipping to change at page 8, line 49
unfolding. Unfolding is accomplished by regarding CRLF immediately unfolding. Unfolding is accomplished by regarding CRLF immediately
followed by a white space character (namely HTAB ASCII decimal 9 or followed by a white space character (namely HTAB ASCII decimal 9 or
SPACE ASCII decimal 32) as equivalent to no characters at all (i.e., SPACE ASCII decimal 32) as equivalent to no characters at all (i.e.,
the CRLF and single white space character are removed). the CRLF and single white space character are removed).
Note: It is possible for very simple implementations to generate Note: It is possible for very simple implementations to generate
improperly folded lines in the middle of a UTF-8 multi-octet improperly folded lines in the middle of a UTF-8 multi-octet
sequence. For this reason, implementations SHOULD unfold lines in sequence. For this reason, implementations SHOULD unfold lines in
such a way as to properly restore the original sequence. such a way as to properly restore the original sequence.
Note: Unfolding is done differently than in [RFC2822]. Unfolding Note: Unfolding is done differently than in [RFC5322]. Unfolding
in [RFC2822] only removes the CRLF, not the space following it. in [RFC5322] only removes the CRLF, not the space following it.
Folding is done after any content encoding of a type value. Folding is done after any content encoding of a type value.
Unfolding is done before any decoding of a type value in a content Unfolding is done before any decoding of a type value in a content
line. line.
4.2. ABNF Format Definition 4.2. ABNF Format Definition
The following ABNF uses the notation of [RFC5234], which also defines The following ABNF uses the notation of [RFC5234], which also defines
CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. After the unfolding of CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.
any folded lines as described above, the syntax for a line of this
content type is as follows: vcard-entity = 1*(vcard)
vcard = "BEGIN" ":" "VCARD" CRLF
1*contentline
"END" ":" "VCARD" CRLF
;A vCard object MUST include the VERSION and FN properties.
contentline = [group "."] name *(";" param) ":" value CRLF contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines MUST first ; When parsing a content line, folded lines MUST first
; be unfolded according to the unfolding procedure ; be unfolded according to the unfolding procedure
; described above. ; described above.
; When generating a content line, lines longer than 75 ; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding ; characters SHOULD be folded according to the folding
; procedure described above. ; procedure described above.
group = "WORK" / "HOME" / iana-token / x-name group = "WORK" / "HOME" / iana-token / x-name
name = "SOURCE" / "NAME" / "KIND" / "FN" / "N" / "NICKNAME"
name = x-name / iana-token / "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "GENDER"
/ "ADR" / "LABEL" / "TEL" / "EMAIL" / "IMPP" / "LANG"
/ "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "ORG" / "MEMBER"
/ "RELATED" / "CATEGORIES" / "NOTE" / "PRODID" / "REV"
/ "SORT-STRING" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL"
/ "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI"
/ "CALURI" / iana-token / x-name
; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below.
; Group and name are case-insensitive.
iana-token = 1*(ALPHA / DIGIT / "-") iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA ; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-") x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are ; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released ; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements. ; products, or for use in bilateral agreements.
param = param-name "=" param-value *("," param-value) param = language-param / encoding-param / value-param / pref-param
/ pid-param / type-param / geo-param / tz-param / any-param
param-name = x-name / iana-token ; Allowed parameters depend on property name.
param-value = ptext / quoted-string
ptext = *SAFE-CHAR
value = *VALUE-CHAR param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
/ valuespec ; valuespec defined in section 5.8.4
quoted-string = DQUOTE *QSAFE-CHAR DQUOTE any-param = (iana-token / x-name) "=" param-value
NON-ASCII = %x80-FF NON-ASCII = %x80-FF
; use restricted by charset parameter ; Use is restricted by charset parameter
; on outer MIME object (UTF-8 preferred) ; on outer MIME object (UTF-8 by default)
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-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
A line that begins with a white space character is a continuation of A line that begins with a white space character is a continuation of
the previous line, as described above. The white space character and the previous line, as described above. The white space character and
immediately preceeding CRLF should be discarded when reconstructing immediately preceeding CRLF should be discarded when reconstructing
the original line. Note that this line-folding convention differs the original line. Note that this line-folding convention differs
from that found in [RFC2822], in that the sequence <CRLF><WSP> found from that found in [RFC5322], in that the sequence <CRLF><WSP> found
anywhere in the content indicates a continued line and should be anywhere in the content indicates a continued line and should be
removed. removed.
Property names and parameter names are case insensitive (e.g., the Property names and parameter names are case insensitive (e.g., the
property name "fn" is the same as "FN" and "Fn"). Parameter values property name "fn" is the same as "FN" and "Fn"). Parameter values
MAY be case sensitive or case insensitive, depending on their MAY be case sensitive or case insensitive, depending on their
definition. definition.
The group construct is used to group related properties together. The group construct is used to group related properties together.
For example, groups named "WORK" and "HOME" could be used to 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 11.3.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-".
Properties defined in a vCard instance may have multiple values Properties defined in a vCard instance may have multiple values
depending on the property cardinality. The general rule for encoding depending on the property cardinality. The general rule for encoding
multi-valued properties is to simply create a new content line for multi-valued properties is to simply create a new content line for
each value (including the property name). However, it should be each value (including the property name). However, it should be
noted that some value types support encoding multiple values in a noted that some value types support encoding multiple values in a
single content line by separating the values with a comma ",". This single content line by separating the values with a comma ",". This
approach has been taken for several of the content types defined approach has been taken for several of the content types defined
skipping to change at page 11, line 15 skipping to change at page 11, line 36
Finally, newline (ASCII decimal 10) and backslash (ASCII decimal 92) Finally, newline (ASCII decimal 10) and backslash (ASCII decimal 92)
characters in values MUST be escaped by prefixing them with a characters in values MUST be escaped by prefixing them with a
backslash character. backslash character.
In all other cases, escaping MUST NOT be used. In all other cases, escaping MUST NOT be used.
5. Property Value Data Types 5. Property Value Data Types
Standard value types are defined below. Standard value types are defined below.
valuespec = text-list value = text
/ URI ; from Appendix A of [RFC3986] / text-list
/ date-list / date-list
/ time-list / time-list
/ date-time-list / date-time-list
/ timestamp-list
/ boolean / boolean
/ integer-list / integer-list
/ float-list / float-list
/ binary / binary
/ utc-offset / utc-offset
/ URI ; from Appendix A of [RFC3986]
/ iana-valuespec / iana-valuespec
; Actual value type depends on property name and VALUE parameter.
text = *VALUE-CHAR
text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR) text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)
TEXT-LIST-CHAR = "\\" / "\," / "\n" TEXT-LIST-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \ or newline> / <any VALUE-CHAR except , or \ or newline>
; Backslashes, newlines, and commas must be encoded. ; Backslashes, commas, and newlines must be encoded.
; \n or \N can be used to encode a newline.
date-list = date *("," date) date-list = date *("," date)
time-list = time *("," time) time-list = time *("," time)
date-time-list = date-time *("," date-time)
date-time-list = date "T" time *("," date "T" time) timestamp-list = timestamp *("," timestamp)
boolean = "TRUE" / "FALSE"
integer-list = integer *("," integer) integer-list = integer *("," integer)
integer = [sign] 1*DIGIT
float-list = float *("," float) float-list = float *("," float)
boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT] float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-" sign = "+" / "-"
binary = <A "B" binary encoded string as defined by [RFC2047].> binary = <A binary string encoded according
date = date-fullyear ["-" date-month ["-" date-mday]] to the "encoding" parameter>
date-fullyear = 4DIGIT
date-month = 2DIGIT ;01-12
date-mday = 2DIGIT ;01-28, 01-29, 01-30, 01-31
;based on month/year
time = time-hour [":" time-minute [":" time-second [time-secfrac]]]
[time-zone]
time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59
time-second = 2DIGIT ;00-60 (leap second)
time-secfrac = "," 1*DIGIT year = 4DIGIT ; 0000-9999
month = 2DIGIT ; 01-12
day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
hour = 2DIGIT ; 00-23
minute = 2DIGIT ; 00-59
second = 2DIGIT ; 00-58/59/60 depending on leap second
zone = "Z" / utc-offset
time-zone = "Z" / time-numzone date = year month day
/ year "-" month
/ "--" month [day]
/ "--" "-" day
date-noreduc = year month day
/ "--" month day
/ "--" "-" day
date-complete = year month day
time-numzome = sign time-hour [":"] time-minute time = hour [minute [second]] [zone]
/ "-" minute [second] [zone]
/ "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone]
utc-offset = ("+" / "-") time-hour ":" time-minute date-time = date-noreduc "T" time-notrunc
timestamp = date-complete "T" time-complete
utc-offset = sign hour [minute]
iana-valuespec = <a publicly-defined valuetype format, registered iana-valuespec = <a publicly-defined valuetype format, registered
with IANA, as defined in section 12 of this with IANA, as defined in section 12 of this
document> document>
5.1. TEXT 5.1. TEXT
"text": The "text" value type should be used to identify values that "text": The "text" value type should be used to identify values that
contain human-readable text. The character set in which the text is contain human-readable text. The character set in which the text is
represented is controlled by the "charset" MIME type parameter. Note represented is controlled by the "charset" MIME type parameter. Note
skipping to change at page 13, line 36 skipping to change at page 14, line 12
is too large, or otherwise undesirable to include directly. The is too large, or otherwise undesirable to include directly. The
format for the URI is as defined in [RFC3986]. Note that the value format for the URI is as defined in [RFC3986]. Note that the value
of a property of type "uri" is what the URI points to, not the URI of a property of type "uri" is what the URI points to, not the URI
itself. itself.
Examples for "uri": Examples for "uri":
http://www.example.com/my/picture.jpg http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen ldap://ldap.example.com/cn=babs%20jensen
5.3. DATE, TIME, and DATE-TIME 5.3. DATE, TIME, DATE-TIME, and TIMESTAMP
"date", "time", and "date-time": Each of these value types is based "date", "time", "date-time", and "timestamp": Each of these value
on a subset of the definitions in [ISO.8601.1988] standard. Multiple types is based on a the definitions in [ISO.8601.2004] standard.
"date" and "time" values can be specified using the comma-separated Multiple such values can be specified using the comma-separated
notation. notation.
Only the basic format is supported.
5.3.1. DATE
A calendar date as specified in [ISO.8601.2004] section 4.1.2.
Reduced accuracy, as specified in [ISO.8601.2004] sections 4.1.2.3 a)
and b), but not c), is permitted.
Expanded representation, as specified in [ISO.8601.2004] section
4.1.4, is forbidden.
Truncated representation, as specified in [ISO.8601.2000] sections
5.2.1.3 d), e), and f), is permitted.
Examples for "date": Examples for "date":
1985-04-12
1996-08-05,1996-11-11
19850412 19850412
1985-04
1985
--0412
---12
5.3.2. TIME
A time of day as specified in [ISO.8601.2004] section 4.2.
Reduced accuracy, as specified in [ISO.8601.2004] section 4.2.2.3, is
permitted.
Representation with decimal fraction, as specified in [ISO.8601.2004]
section 4.2.2.4, is forbidden.
Midnight is always represented by 00, never 24 (see [ISO.8601.2004]
section 4.2.3).
Truncated representation, as specified in [ISO.8601.2000] sections
5.3.1.4 a), b), and c), is permitted.
Examples for "time": Examples for "time":
10:22:00
102200 102200
10:22:00.33 1022
10:22:00.33Z 10
10:22:33,11:22:00 -2200
10:22:00-08:00 --00
102200Z
102200-0800
5.3.3. DATE-TIME
A date and time of day combination as specified in [ISO.8601.2004]
section 4.3.
Truncation of the date part, as specified in [ISO.8601.2000] section
5.4.2 c), is permitted.
Examples for "date-time": Examples for "date-time":
1996-10-22T14:00:00Z 19961022T140000
1996-08-11T12:34:56Z --1022T1400
19960811T123456Z ---22T14
1996-10-22T14:00:00Z,1996-08-11T12:34:56Z
5.3.4. TIMESTAMP
A complete date and time of day combination as specified in
[ISO.8601.2004] section 4.3.2.
Examples for "timestamp":
19961022T140000
19961022T140000Z
19961022T140000-05
19961022T140000-0500
5.4. BOOLEAN 5.4. BOOLEAN
"boolean": The "boolean" value type is used to express boolen values. "boolean": The "boolean" value type is used to express boolen values.
These values are case insensitive. These values are case insensitive.
Examples: Examples:
TRUE TRUE
false false
skipping to change at page 15, line 31 skipping to change at page 17, line 7
folding method defined in Section 4.1. folding method defined in Section 4.1.
5.8. UTC-OFFSET 5.8. UTC-OFFSET
"utc-offset": The "utc-offset" value type specifies that the type "utc-offset": The "utc-offset" value type specifies that the type
value is a signed offset from UTC. This value type can be specified value is a signed offset from UTC. This value type can be specified
in the TZ type. in the TZ type.
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., +hhmm). 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 basic format for ISO 8601 UTC offsets
offsets MUST be used. The extended format makes use of a colon MUST be used.
character as a separator of the hour and minute text fields.
5.9. LANGUAGE-TAG 5.9. LANGUAGE-TAG
"language-tag": A single language tag, as defined in [RFC4646]. "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.
skipping to change at page 16, line 12 skipping to change at page 17, line 36
Property parameter values MUST NOT contain the DQUOTE (US-ASCII Property parameter values MUST NOT contain the DQUOTE (US-ASCII
decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is
used as a delimiter for parameter values that contain restricted used as a delimiter for parameter values that contain restricted
characters or URI text. For example: characters or URI text. For example:
EMAIL;PID=8:jdoe@example.com EMAIL;PID=8:jdoe@example.com
Property parameter values that are not in quoted strings are case Property parameter values that are not in quoted strings are case
insensitive. insensitive.
The general property parameters defined by this memo are defined by
the following notation:
vcardparameter = encodingparam
/ valuetypeparam
/ languageparam
/ pref-param
/ pid-param
encodingparam = "encoding" "=" encodingtype
encodingtype = "b" ; from [RFC2047]
/ iana-token ; registered as described in
; section 12 of this document
valuetypeparam = "value" "=" valuetype
valuetype = "uri" ; URI from Appendix A of [RFC3986]
/ "text"
/ "date"
/ "time"
/ "date-time" ; date time
/ "integer"
/ "boolean"
/ "float"
/ "language-tag"
/ x-name
/ iana-token ; registered as described in
; section 12 of this document
languageparam = "language" "=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 4646
pref-param = "pref" "=" pref-value
pref-value = 1*DIGIT
pid-param = ("pid" "=" pid-value *("," pid-value))
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
multiple languages. There is no concept of "default" language, multiple languages. There is no concept of "default" language,
except as specified by any "Content-Language" MIME header parameter except as specified by any "Content-Language" MIME header parameter
that is present. The value of the "language" property parameter is a that is present. The value of the "language" property parameter is a
language tag as defined in Section 2 of [RFC4646]. language tag as defined in Section 2 of [RFC4646].
ABNF:
language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 4646
6.2. ENCODING 6.2. ENCODING
The "encoding" property parameter is used to specify an alternate The "encoding" property parameter is used to specify an alternate
encoding for a value. If the value contains a CRLF, it must be encoding for a value. If the value contains a CRLF, it must be
encoded, since CRLF is used to separate lines in the content-type encoded, since CRLF is used to separate lines in the content-type
itself. Currently, only the "b" encoding is supported. itself. Currently, only the "b" encoding is supported.
The "b" encoding can also be useful for binary values that are mixed The "b" encoding can also be useful for binary values that are mixed
with other text information in the body part (e.g., a certificate). with other text information in the body part (e.g., a certificate).
Using a per-value "b" encoding in this case leaves the other Using a per-value "b" encoding in this case leaves the other
skipping to change at page 17, line 44 skipping to change at page 18, line 35
The Content-Transfer-Encoding and the encodings of individual The Content-Transfer-Encoding and the encodings of individual
properties given by the "encoding" property parameter are independent properties given by the "encoding" property parameter are independent
of one another. When encoding a text/vcard body part for of one another. When encoding a text/vcard body part for
transmission, individual property encodings are performed first, then transmission, individual property encodings are performed first, then
the entire body part is encoded according to the Content-Transfer- the entire body part is encoded according to the Content-Transfer-
Encoding. When decoding a text/vcard body part, the Content- Encoding. When decoding a text/vcard body part, the Content-
Transfer-Encoding is decoded first, and then any individual Transfer-Encoding is decoded first, and then any individual
properties with an "encoding" property parameter are decoded. properties with an "encoding" property parameter are decoded.
ABNF:
encoding-param = "ENCODING=" encoding-type
encoding-type = "b" ; from [RFC2047]
/ iana-token ; registered as in section 12
6.3. VALUE 6.3. VALUE
The "value" parameter is optional, and is used to identify the value The "value" parameter is optional, and is used to identify the value
type (data type) and format of the value. The use of these type (data type) and format of the value. The use of these
predefined formats is encouraged even if the value parameter is not predefined formats is encouraged even if the value parameter is not
explicity used. By defining a standard set of value types and their explicity used. By defining a standard set of value types and their
formats, existing parsing and processing code can be leveraged. The formats, existing parsing and processing code can be leveraged. The
predefined data type values MUST NOT be repeated in COMMA separated predefined data type values MUST NOT be repeated in COMMA separated
value lists except within the N, NICKNAME, ADR and CATEGORIES value lists except within the N, NICKNAME, ADR and CATEGORIES
properties. properties.
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.
ABNF:
value-param = "VALUE=" value-type
value-type = "text"
/ "uri"
/ "date"
/ "time"
/ "date-time"
/ "timestamp"
/ "boolean"
/ "integer"
/ "float"
/ "binary"
/ "utc-offset"
/ "language-tag"
/ iana-token ; registered as described in section 12
/ x-name
6.4. PREF 6.4. PREF
The "pref" parameter is optional, and is used to indicate that the The "pref" parameter is optional, and is used to indicate that the
corresponding instance of a property is preferred by the vCard corresponding instance of a property is preferred by the vCard
author. Its value MUST be a strictly positive integer that author. Its value MUST be an integer between 1 and 100 that
quantifies the level of preferredness. Lower values correspond to a quantifies the level of preferredness. Lower values correspond to a
higher level of preferrredness, 1 being most preferred. The value higher level of preferrredness, 1 being most preferred.
zero MUST NOT be used.
When the parameter is absent, the default MUST be to interpret the When the parameter is absent, the default MUST be to interpret the
property instance as being least preferred. property instance as being least preferred.
Note that the value of this parameter is to be interpreted only in Note that the value of this parameter is to be interpreted only in
relation to values assigned to other instances of the same property 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 in the same vCard. A given value, or the absence of a value, MUST
NOT be interpreted on its own. NOT be interpreted on its own.
This parameter MAY be applied to any property that allows multiple This parameter MAY be applied to any property that allows multiple
instances. instances.
ABNF:
pref-param = "PREF=" (1*2DIGIT / "100")
6.5. PID 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 MAY (Section 7.7.7) on a per-property instead of per-vCard basis. It MAY
appear more than once in a given property. It MUST NOT appear on appear more than once in a given property. It MUST NOT appear on
properties that only may have one instance per vCard. Its value is properties that only may have one instance per vCard. Its value is
either a single small integer, or a pair of small integers separated either a single small integer, or a pair of small integers separated
by a dot. Multiple values may be encoded in a single PID parameter by a dot. Multiple values may be encoded in a single PID parameter
by separating the values with a comma ",". See Section 8 for more by separating the values with a comma ",". See Section 8 for more
details on its usage. details on its usage.
ABNF:
pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT]
6.6. 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.
ABNF:
type-param= = "TYPE=" type-value *("," type-value)
type-value = type-value-tel / type-value-related
/ iana-token / x-name
; This is further defined in individual property sections.
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: Property cardinalities are indicated using the following notation:
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
| Cardinality | Meaning | | Cardinality | Meaning |
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
| (1,1) | Exactly one instance per vCard MUST be present. | | (1,1) | Exactly one instance per vCard MUST be present. |
skipping to change at page 19, line 46 skipping to change at page 21, line 37
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
identifiable outside of a MIME environment. identifiable outside of a MIME environment.
ABNF:
param = ; no parameter allowed
value = "VCARD"
Example: Example:
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
skipping to change at page 20, line 26 skipping to change at page 22, line 21
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
identifiable outside of a MIME environment. identifiable outside of a MIME environment.
ABNF:
param = ; no parameter allowed
value = "VCARD"
Example: Example:
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
skipping to change at page 20, line 49 skipping to change at page 22, line 49
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.
ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
Examples: Examples:
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/ SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf Jean%20Dupont.vcf
7.1.4. NAME 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
skipping to change at page 21, line 24 skipping to change at page 23, line 25
Value type: text Value type: text
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The NAME property is used to convey the display name Special notes: The NAME property is used to convey the display name
of the entity to which the directory information pertains. Its of the entity to which the directory information pertains. Its
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.
ABNF:
param = "VALUE=text" / any-param
value = text
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) 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.
ABNF:
param = "VALUE=text" / any-param
value = "individual" / "group" / "org" / "location"
/ iana-token / x-name
Example: Example:
This represents someone named Jane Doe working in the marketing This represents someone named Jane Doe working in the marketing
department of the North American division of ABC Inc. department of the North American division of ABC Inc.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:individual KIND:individual
FN:Jane Doe FN:Jane Doe
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC\, Inc.;North American Division;Marketing
skipping to change at page 22, line 33 skipping to change at page 24, line 47
the object the vCard represents. the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (1,n) Cardinality: (1,n)
Special notes: This property is based on the semantics of the X.520 Special notes: This property is based on the semantics of the X.520
Common Name attribute. The property MUST be present in the vCard Common Name attribute. The property MUST be present in the vCard
object. object.
ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param
value = text
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
skipping to change at page 23, line 10 skipping to change at page 25, line 29
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.
ABNF:
param = "VALUE=text" / language-param / any-param
value = list-component 3(";" list-component)
list-component = list-component-value *("," list-component-value)
list-component-value = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
Examples: Examples:
N:Public;John,Q.;Mr.;Esq. N:Public;John,Q.;Mr.;Esq.
N:Stevenson;John,Philip,Paul;Dr.;Jr.,M.D.,A.C.P. N:Stevenson;John,Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
7.2.3. NICKNAME 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.
skipping to change at page 23, line 31 skipping to change at page 26, line 15
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Cardinality: (0,n) Cardinality: (0,n)
Special note: The nickname is the descriptive name given instead of Special note: The nickname is the descriptive name given instead of
or in addition to the one belonging to a person, place, or thing. or in addition to the one belonging to a person, place, or thing.
It can also be used to specify a familiar form of a proper name It can also be used to specify a familiar form of a proper name
specified by the FN or N properties. specified by the FN or N properties.
ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param
value = text-list
Examples: Examples:
NICKNAME:Robbie NICKNAME:Robbie
NICKNAME:Jim,Jimmie NICKNAME:Jim,Jimmie
WORK.NICKNAME:Boss WORK.NICKNAME:Boss
7.2.4. PHOTO 7.2.4. PHOTO
skipping to change at page 24, line 17 skipping to change at page 27, line 5
a value outside of this MIME entity. a value outside of this MIME entity.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF:
param = inline-param / refer-param
value = inline-value / refer-value
; Value and parameter MUST match.
param =/ pid-param / pref-param / any-param
inline-param = "VALUE=binary"
/ encoding-param
/ "TYPE=" type-name "/" subtype-name
; from [RFC4288] section 4.2
inline-value = binary
refer-param = "VALUE=uri"
refer-value = uri
Example: Example:
PHOTO;VALUE=uri:http://www.example.com/pub/photos PHOTO;VALUE=uri:http://www.example.com/pub/photos
/jqpublic.gif /jqpublic.gif
PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo
ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv
bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
7.2.5. BDAY 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) Cardinality: (0,1)
Examples: ABNF:
BDAY:1996-04-15 param = "VALUE=" ("date" / "date-time" / "text")
value = date / date-time / text
; Value and parameter MUST match.
BDAY:1953-10-15T23:10:00Z param =/ any-param
Examples:
BDAY:19960415
BDAY:--0415
BDAY;VALUE=date-time:19531015T231000Z
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) Cardinality: (0,1)
ABNF:
param = "VALUE=" ("date" / "date-time" / "text")
value = date / date-time / text
; Value and parameter MUST match.
param =/ any-param
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) Cardinality: (0,1)
ABNF:
param = "VALUE=text" / language-param / any-param
value = text
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) Cardinality: (0,1)
ABNF:
param = "VALUE=text" / language-param / any-param
value = text
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) 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. IANA-registered values and x-names are also allowed. female. IANA-registered values and x-names are also allowed.
ABNF:
param = "VALUE=text" / any-param
value = "M" / "F" / iana-token / x-name
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
skipping to change at page 26, line 39 skipping to change at page 30, line 29
The text components are separated by the SEMI-COLON character The text components are separated by the SEMI-COLON character
(ASCII decimal 59). Where it makes semantic sense, individual (ASCII decimal 59). Where it makes semantic sense, individual
text components can include multiple text values (e.g., a "street" text components can include multiple text values (e.g., a "street"
component with multiple lines) separated by the COMMA character component with multiple lines) separated by the COMMA character
(ASCII decimal 44). (ASCII decimal 44).
The property can include the "PREF" parameter to indicate the 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.
The GEO parameter can be used to indicate global positioning
information that is specific to this address. Its value is the
same as that of the GEO property.
The TZ parameter can be used to indicate time zone information
that is specific to this address. Its value is the same as that
of the TZ property.
ABNF:
param = "VALUE=text" / language-param / geo-param / tz-param
/ pid-param / pref-param / any-param
value = list-component 6(";" list-component)
geo-param = "GEO=" DQUOTE uri DQUOTE
tz-param = "TZ=" utc-offset
Example: In this example the post office box and the extended address Example: In this example the post office box and the extended address
are absent. are absent.
ADR:;;123 Main Street;Any Town;CA;91921-1234 ADR;GEO="geo:12.3457,78.910":;;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) Cardinality: (0,n)
Special notes: The property value is formatted text that can be used Special notes: The property value is formatted text that can be used
to present a delivery address label for the vCard object. The to present a delivery address label for the vCard object. The
property can include the "PREF" parameter to indicate the property can include the "PREF" parameter to indicate the
preferred delivery address when more than one address is preferred delivery address when more than one address is
specified. specified.
ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param
value = text
Example: A multi-line address label. Example: A multi-line address label.
LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n
123 Main Street\nAny Town\, CA 91921-1234\nU.S.A. 123 Main Street\nAny Town\, CA 91921-1234\nU.S.A.
7.4. Communications Properties 7.4. Communications Properties
These properties are concerned with information associated with the These properties are concerned with information associated with the
way communications with the object the vCard represents are carried way communications with the object the vCard represents are carried
out. out.
skipping to change at page 28, line 7 skipping to change at page 32, line 23
cellular telephone number, "video" to indicate a video cellular telephone number, "video" to indicate a video
conferencing telephone number, "pager" to indicate a paging device conferencing telephone number, "pager" to indicate a paging device
telephone number. The default type is "voice". These type telephone number. The default type is "voice". These type
parameter values can be specified as a parameter list (i.e., parameter values can be specified as a parameter list (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".
ABNF:
param = "VALUE=uri" / type-param / pid-param / pref-param
/ any-param
value = uri
type-value-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / iana-token / x-name
Example: Example:
WORK.TEL;PREF=1;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) Cardinality: (0,n)
Special notes: The property can include tye "PREF" parameter to Special notes: The property can include tye "PREF" parameter to
indicate a preferred-use email address when more than one is indicate a preferred-use email address when more than one is
specified. specified.
ABNF:
param = "VALUE=text" / pid-param / pref-param / any-param
value = addr-spec ; from [RFC5322] section 3.4.1
Type example: Type example:
WORK.EMAIL:jqpublic@xyz.example.com WORK.EMAIL:jqpublic@xyz.example.com
EMAIL;PREF=1: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) 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.
ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
Example: Example:
IMPP;PREF=1: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 single language-tag value. Value type: A single language-tag value.
Cardinality: (0,n) Cardinality: (0,n)
ABNF:
param = "VALUE=language-tag" / pid-param / pref-param / any-param
value = Language-Tag
Example: Example:
WORK.LANG;PREF=1:en WORK.LANG;PREF=1:en
WORK.LANG;PREF=2:fr WORK.LANG;PREF=2:fr
HOME.LANG=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
skipping to change at page 29, line 38 skipping to change at page 34, line 28
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) Cardinality: (0,n)
Special notes: The type value consists of a single value. Special notes: The type value consists of a single value.
ABNF:
param = "VALUE=" ("utc-offset" / "text")
value = utc-offset / text
; Value and parameter must match
param =/ pid-param / pref-param / any-param
Type examples: Type examples:
TZ:-05:00 TZ:-0500
TZ;VALUE=text:-05:00; EST; Raleigh/North America TZ;VALUE=text:-0500; EST; Raleigh/North America
;This example has a single value, not a structure text value. ;This example has a single value, not a structure text value.
7.5.2. GEO 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 URI.
separated by the SEMI-COLON character (ASCII decimal 59).
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property specifies information related to the Special notes: The "geo" URI scheme [I-D.mayrhofer-geo-uri] is
global position of the object associated with the vCard. The particularly well-suited for this property, but other schemes MAY
value specifies latitude and longitude, in that order (i.e., "LAT be used.
LON" ordering). The longitude represents the location east and
west of the prime meridian as a positive or negative real number,
respectively. The latitude represents the location north and
south of the equator as a positive or negative real number,
respectively. The longitude and latitude values MUST be expressed
in the [WGS84] reference system. They MUST be specified as
decimal degrees and should be specified to six decimal places.
This will allow for granularity within a meter of the geographical
position. The text components are separated by the SEMI-COLON
character (ASCII decimal 59). The simple formula for converting
degrees-minutes-seconds into decimal degrees is:
decimal = degrees + minutes/60 + seconds/3600. ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
Example: Example:
GEO:37.386013;-122.082932 GEO:geo:37.386013,-122.082932
7.6. Organizational Properties 7.6. Organizational Properties
These properties are concerned with information associated with These properties are concerned with information associated with
characteristics of the organization or organizational units of the characteristics of the organization or organizational units of the
object the vCard represents. object the vCard represents.
7.6.1. TITLE 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) Cardinality: (0,n)
Special notes: This property is based on the X.520 Title attribute. Special notes: This property is based on the X.520 Title attribute.
ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param
value = text
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) 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
skipping to change at page 31, line 20 skipping to change at page 36, line 17
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property is based on the X.520 Business Category Special notes: This property is based on the X.520 Business Category
explanatory attribute. This property is included as an explanatory attribute. This property is included as an
organizational type to avoid confusion with the semantics of the organizational type to avoid confusion with the semantics of the
TITLE property and incorrect usage of that property when the TITLE property and incorrect usage of that property when the
semantics of this property is intended. semantics of this property is intended.
ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param
value = text
Example: Example:
ROLE:Programmer ROLE:Programmer
7.6.3. LOGO 7.6.3. LOGO
Purpose: To specify a graphic image of a logo associated with the Purpose: To specify a graphic image of a logo associated with the
object the vCard represents. object the vCard represents.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
skipping to change at page 31, line 46 skipping to change at page 37, line 5
a value outside of this MIME entity. a value outside of this MIME entity.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF:
param = inline-param / refer-param
value = inline-value / refer-value
; Value and parameter MUST match.
param =/ language-param / pid-param / pref-param / any-param
Example: Example:
LOGO;VALUE=uri:http://www.example.com/pub/logos/abccorp.jpg LOGO;VALUE=uri:http://www.example.com/pub/logos/abccorp.jpg
LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
7.6.4. ORG 7.6.4. ORG
skipping to change at page 32, line 19 skipping to change at page 37, line 35
with the vCard. with the vCard.
Value type: A single structured text value consisting of components Value type: A single structured text value consisting of components
separated the SEMI-COLON character (ASCII decimal 59). separated the SEMI-COLON character (ASCII decimal 59).
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property is based on the X.520 Organization Name Special notes: The property is based on the X.520 Organization Name
and Organization Unit attributes. The property value is a and Organization Unit attributes. The property value is a
structured type consisting of the organization name, followed by structured type consisting of the organization name, followed by
one or more levels of organizational unit names. zero or more levels of organizational unit names.
ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param
value = component *(";" component)
component = "\\" / "\;" / "\n" / WSP / NON-ASCII
/ %x21-3A / %x3C-5B / %x5D-7E
Example: A property value consisting of an organizational name, Example: A property value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name. organizational unit #1 name and organizational unit #2 name.
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC\, Inc.;North American Division;Marketing
7.6.5. MEMBER 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) Cardinality: (0,n)
Special notes: This property MUST NOT be present unless the value of Special notes: This property MUST NOT be present unless the value of
the KIND property is "group". the KIND property is "group".
ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
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
MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519 MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
skipping to change at page 34, line 16 skipping to change at page 39, line 34
* "manager" means that the related individual is the direct * "manager" means that the related individual is the direct
hierarchical superior (i.e. supervisor or manager) of the hierarchical superior (i.e. supervisor or manager) of the
individual this vCard represents. individual this vCard represents.
* "assistant" for an assistant or secretary. * "assistant" for an assistant or secretary.
* "agent" for a person who will act on behalf of the individual * "agent" for a person who will act on behalf of the individual
or resource associated with the vCard. or resource associated with the vCard.
* "emergency" indicates an emergency contact.
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 11.2, and private extensions starting with "X-" may be
used. used.
ABNF:
param = "VALUE=" ("uri" / "text")
value = uri / text
; Parameter and value MUST match.
param =/ type-param / pid-param / pref-param / any-param
type-param-related = "parent" / "child" / "sibling" / "manager"
/ "assistant" / "agent" / "emergency"
/ iana-token / x-name
Examples: Examples:
RELATED;TYPE=manager:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=manager:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
RELATED;TYPE=assistant:http://example.com/directory/jdoe.vcf RELATED;TYPE=assistant:http://example.com/directory/jdoe.vcf
RELATED;TYPE=agent;VALUE=text:Please contact my assistant Jane Doe RELATED;TYPE=agent;VALUE=text:Please contact my assistant Jane Doe
for any inquiries. for any inquiries.
7.7. Explanatory Properties 7.7. Explanatory Properties
These properties are concerned with additional explanations, such as These properties are concerned with additional explanations, such as
skipping to change at page 34, line 43 skipping to change at page 40, line 26
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) Cardinality: (0,n)
ABNF:
param = "VALUE=text" / pid-param / pref-param / any-param
value = text-list
Example: Example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
7.7.2. NOTE 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) Cardinality: (0,n)
Special notes: The property is based on the X.520 Description Special notes: The property is based on the X.520 Description
attribute. attribute.
ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param
value = text
Example: Example:
NOTE:This fax number is operational 0800 to 1715 NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri. EST\, Mon-Fri.
7.7.3. PRODID 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) 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.
ABNF:
param = "VALUE=text" / any-param
value = text
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: A single timestamp value.
reset to a single date value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The value distinguishes the current revision of the Special notes: The value distinguishes the current revision of the
information in this vCard for other renditions of the information. information in this vCard for other renditions of the information.
Example: ABNF:
REV:1995-10-31T22:27:10Z param = "VALUE=timestamp" / any-param
value = timestamp
REV:1997-11-15 Example:
REV:19951031T222710Z
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) 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.
ABNF:
param = "VALUE=text" / any-param
value = text
Examples: For the case of family name sorting, the following examples Examples: For the case of family name sorting, the following examples
define common sort string usage with the FN and N properties. define common sort string usage with the FN and N properties.
FN:Rene van der Harten FN:Rene van der Harten
N:van der Harten;Rene;J.;Sir;R.D.O.N. N:van der Harten;Rene;J.;Sir;R.D.O.N.
SORT-STRING:Harten SORT-STRING:Harten
FN:Robert Pau Shou Chang FN:Robert Pau Shou Chang
N:Pau;Shou Chang;Robert N:Pau;Shou Chang;Robert
SORT-STRING:Pau SORT-STRING:Pau
skipping to change at page 37, line 8 skipping to change at page 43, line 8
N:del Pozo Triscon;Oscar N:del Pozo Triscon;Oscar
SORT-STRING:Pozo SORT-STRING:Pozo
FN:Chistine d'Aboville FN:Chistine d'Aboville
N:d'Aboville;Christine N:d'Aboville;Christine
SORT-STRING:Aboville SORT-STRING:Aboville
7.7.6. SOUND 7.7.6. SOUND
Purpose: To specify a digital sound content information that Purpose: To specify a digital sound content information that
annotates some aspect of the vCard. By default this property is annotates some aspect of the vCard. This property is often used
used to specify the proper pronunciation of the name property to specify the proper pronunciation of the name property value of
value of the vCard. the vCard.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of value is referenced by a URI value, then the default encoding of
8bit is used and no explicit ENCODING parameter is needed. 8bit is used and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary value. It can Value type: A single value. The default is binary value. It can
also be reset to uri value. The uri value can be used to specify also be reset to uri value. The uri value can be used to specify
a value outside of this MIME entity. a value outside of this MIME entity.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the audio format type. The TYPE parameter value MUST be specify the audio format type. The TYPE parameter value MUST be
an audio media type as specified in [RFC4288]. The full media an audio media type as specified in [RFC4288]. The full media
type name, including the "audio/" prefix, should be used. type name, including the "audio/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF:
param = inline-param / refer-param
value = inline-value / refer-value
; Value and parameter MUST match.
param =/ language-param / pid-param / pref-param / any-param
Example: Example:
SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8. SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@example.com 19960229T080000.xyzMail@example.com
SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
skipping to change at page 38, line 5 skipping to change at page 44, line 17
Value type: A single URI value. Value type: A single URI value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: This property is used to uniquely identify the object Special notes: This property is used to uniquely identify the object
that the vCard represents. The "uuid" URN namespace defined in 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.
ABNF:
param = "VALUE=uri" / any-param
value = uri
Example: Example:
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
7.7.8. CLIENTPIDMAP 7.7.8. CLIENTPIDMAP
Purpose: To give a global meaning to a local PID source identifier. Purpose: To give a global meaning to a local PID source identifier.
Value type: A semicolon-separated pair of values. The first field Value type: A semicolon-separated pair of values. The first field
is a small integer corresponding to the second field of a PID is a small integer corresponding to the second field of a PID
skipping to change at page 38, line 34 skipping to change at page 45, line 5
instance. Each distinct source identifier present in a vCard MUST instance. Each distinct source identifier present in a vCard MUST
have an associated CLIENTPIDMAP. See Section 8 for more details have an associated CLIENTPIDMAP. See Section 8 for more details
on the usage of CLIENTPIDMAP. on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive. Zero is not PID source identifiers MUST be strictly positive. Zero is not
allowed. allowed.
As a special exception, the PID parameter MUST NOT be applied to As a special exception, the PID parameter MUST NOT be applied to
this property. this property.
ABNF:
param = any-param
value = 1*DIGIT ";" uri
Example: Example:
TEL;PID=3.1,4.2:tel:+1-555-555-5555 TEL;PID=3.1,4.2:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5 CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
7.7.9. URL 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) Cardinality: (0,n)
Value type: A single uri value. Value type: A single uri value.
ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
Example: Example:
URL:http://example.org/restaurant.french/~chezchic.html URL:http://example.org/restaurant.french/~chezchic.html
7.7.10. 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) 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.
ABNF:
param = "VALUE=text" / any-param
value = "4.0"
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
skipping to change at page 39, line 52 skipping to change at page 46, line 38
PUBLIC: This vCard MAY be shared with anyone. PUBLIC: This vCard MAY be shared with anyone.
PRIVATE: This vCard MUST NOT be shared. It MAY be exported if PRIVATE: This vCard MUST NOT be shared. It MAY be exported if
explictly authorized and requested by the creator. explictly authorized and requested by the creator.
CONFIDENTIAL: This vCard MAY be shared with allowed users or CONFIDENTIAL: This vCard MAY be shared with allowed users or
systems. The exact confidentiality level is site-specific and systems. The exact confidentiality level is site-specific and
out of scope for the vCard specification. out of scope for the vCard specification.
ABNF:
param = "VALUE=text" / any-param
value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token / x-name
Examples: Examples:
CLASS:PUBLIC CLASS:PUBLIC
CLASS:PRIVATE CLASS:PRIVATE
CLASS:CONFIDENTIAL CLASS:CONFIDENTIAL
7.8.2. KEY 7.8.2. KEY
skipping to change at page 40, line 34 skipping to change at page 47, line 28
is obtained externally (e.g. with the HTTP Content-Type header) is obtained externally (e.g. with the HTTP Content-Type header)
instead of with the TYPE parameter. instead of with the TYPE parameter.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the public key or authentication certificate format. The specify the public key or authentication certificate format. The
TYPE parameter value MUST be a media type as specified in TYPE parameter value MUST be a media type as specified in
[RFC4288]. [RFC4288].
ABNF:
param = inline-param / refer-param
value = inline-value / refer-value
; Value and parameter MUST match.
param =/ pid-param / pref-param / any-param
Examples: Examples:
KEY;VALUE=uri:http://www.example.com/keys/jdoe KEY;VALUE=uri:http://www.example.com/keys/jdoe
KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN
mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g
7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8 7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
7.9. Calendar Properties 7.9. Calendar Properties
skipping to change at page 41, line 18 skipping to change at page 48, line 18
Cardinality: (0,n) Cardinality: (0,n)
Special notes: Where multiple FBURL properties are specified, the Special notes: Where multiple FBURL properties are specified, the
default FBURL property is indicated with the PREF parameter. The default FBURL property is indicated with the PREF parameter. The
FTP or HTTP type of URI points to an iCalendar object associated FTP or HTTP type of URI points to an iCalendar object associated
with a snapshot of the last six weeks of the user's busy time with a snapshot of the last six weeks of the user's busy time
data. If the iCalendar object is represented as a file or data. If the iCalendar object is represented as a file or
document, it's file type should be "ifb". document, it's file type should be "ifb".
ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
Examples: Examples:
FBURL;PREF=1:http://www.example.com/busy/janedoe FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL:FTP://ftp.example.com/busy/project-a.ifb FBURL:FTP://ftp.example.com/busy/project-a.ifb
7.9.2. CALADRURI 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) Cardinality: (0,n)
Special notes: Where multiple CALADRURI properties are specified, Special notes: Where multiple CALADRURI properties are specified,
the default CALADRURI property is indicated with the PREF the default CALADRURI property is indicated with the PREF
parameter. parameter.
ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
Example: Example:
CALADRURI;PREF=1:mailto:janedoe@example.com CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe CALADRURI:http://example.com/calendar/jdoe
7.9.3. CALURI 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.
skipping to change at page 42, line 4 skipping to change at page 49, line 12
CALADRURI;PREF=1:mailto:janedoe@example.com CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe CALADRURI:http://example.com/calendar/jdoe
7.9.3. CALURI 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) 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".
ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri
Examples: Examples:
CALURI;PREF=1:http://cal.example.com/calA CALURI;PREF=1:http://cal.example.com/calA
CALURI:ftp://ftp.example.com/calA.ics CALURI:ftp://ftp.example.com/calA.ics
7.10. Extended Properties and Parameters 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
skipping to change at page 47, line 42 skipping to change at page 55, line 5
TEL;PID=1.1:tel:+1-555-555-5555 TEL;PID=1.1:tel:+1-555-555-5555
TEL;PID=2.1:tel:+1-666-666-6666 TEL;PID=2.1:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD END:VCARD
The details of global context simplification are unspecified by this The details of global context simplification are unspecified by this
document. They are left up to the synchronization engine. This document. They are left up to the synchronization engine. This
example is merely intended to illustrate the possibility, which example is merely intended to illustrate the possibility, which
investigating would be, in the authors' opinion, worthwhile. investigating would be, in the authors' opinion, worthwhile.
9. Formal Grammar 9. Example: Authors' vCards
The following formal grammar is provided to assist developers in
building parsers for the vCard.
This syntax is written according to the form described in [RFC5234],
but it references just this small subset of [RFC5234] literals:
;*******************************************
; Basic vCard Definition
;*******************************************
vcard-entity = 1*(vcard)
vcard = "BEGIN" ":" "VCARD" 1*CRLF
1*(contentline)
;A vCard object MUST include the VERSION and FN properties.
"END" ":" "VCARD" 1*CRLF
contentline = [group "."] name *(";" param ) ":" value CRLF
; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure
; described above. When generating a content line, lines
; longer than 75 characters SHOULD be folded according to
; the folding procedure described in [MIME DIR].
group = "WORK" / "HOME" / iana-token / x-name
name = iana-token / x-name
; Parsing of the param and value is
; based on the "name" or type identifier
; as defined in ABNF sections below
iana-token = 1*(ALPHA / DIGIT / "-")
; vCard type or parameter identifier registered with IANA
x-name = "X-" 1*(ALPHA / DIGIT / "-")
; Reserved for non-standard use
param = param-name "=" param-value *("," param-value)
param-name = iana-token / x-name
param-value = ptext / quoted-string
ptext = *SAFE-CHAR
value = *VALUE-CHAR
quoted-string = DQUOTE QSAFE-CHAR DQUOTE
NON-ASCII = %x80-FF
; Use is restricted by outer MIME object (UTF-8 preferred)
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character
;*******************************************
; vCard Property Definitions
;
; Provides property-specific definitions for how the
; "value" and "param" are defined.
;*******************************************
; **** NAME ****
param = ""
; No parameters allowed
value = text-value
; **** KIND ****
param = ""
; No parameters allowed
value = kind-value
kind-value = "individual" / "group" / "org" / x-name / iana-token
; **** PROFILE ****
param = ""
; No parameters allowed
value = text-value
; Value MUST be the case insensitive value "VCARD
; **** SOURCE ****
param = source-param / pid-param
value = uri
source-param = ("VALUE" "=" "uri")
/ (x-name "=" *SAFE-CHAR)
; **** FN ****
;This type MUST be included in a vCard object.
param = text-param
; Text parameters allowed
value = text-value
; **** N ****
param = text-param
; Text parameters allowed
value = n-value
n-value = 0*3(text-value *("," text-value) ";")
text-value *("," text-value)
; Surname; Given Names; Prefix; Suffix.
; **** NICKNAME ****
param = text-param / pid-param
; Text parameters allowed
value = text-value-list
; **** PHOTO ****
param = pid-param / img-inline-param / img-refer-param
value = img-inline-value
; Value and parameter MUST match
value =/ img-refer-value
; Value and parameter MUST match
; **** BDAY ****
param = ("VALUE" "=" "date")
; Only value parameter allowed
param =/ ("VALUE" "=" "date-time")
; Only value parameter allowed
value = date-value
; Value MUST match value type
value =/ date-time-value
; Value MUST match value type
; **** GENDER ****
param = ""
; No parameters allowed
value = "M" / "F" / iana-token / x-name
; Value are case insensitive
; **** ADR ****
param = text-param / pref-param / pid-param
value = adr-value
; **** LABEL ****
param = text-param / pref-param / pid-param
value = text-value
; **** TEL ****
param = pref-param / tel-param / pid-param
; Only tel parameters allowed
value = uri-value
tel-param = "TYPE" "=" tel-type *("," tel-type)
tel-type = "VOICE" / "FAX" / "CELL" / "PAGER"
/ "VIDEO" / "TEXT" / iana-token / x-name
; Values are case insensitive
; **** EMAIL ****
param = pref-param / pid-param
value = text-value
; **** TZ ****
param = ""
; No parameters allowed
value = utc-offset-value
; **** GEO ****
param = ""
; No parameters allowed
value = float-value ";" float-value
; **** TITLE ****
param = text-param / pid-param
; Only text parameters allowed
value = text-value
; **** ROLE ****
param = text-param / pid-param
; Only text parameters allowed
value = text-value
; **** LOGO ****
param = pid-param / img-inline-param / img-refer-param
value = img-inline-value / img-refer-value
; Value and parameter MUST match
; **** ORG ****
param = text-param / pid-param
; Only text parameters allowed
value = org-value
org-value = *(text-value ";") text-value
; First is Organization Name, remainder are Organization Units.
; **** MEMBER ****
param = pid-param
value = uri
; Any valid URI scheme
; **** RELATED ****
param = ("TYPE" "=" related-type) / pid-param
; Value is case insensitive
value = uri
; Any valid URI scheme
related-type = "parent" / "child" / "sibling" / "manager"
/ "assistant" / "agent" / iana-token / x-name
; Values are case insensitive
; **** CATEGORIES ****
param = text-param / pid-param
; Only text parameters allowed
value = text-value-list
; **** NOTE ****
param = text-param / pid-param
; Only text parameters allowed
value = text-value
; **** PRODID ****
param = ""
; No parameters allowed
value = text-value
; **** REV ****
param = ["VALUE" "=" "date-time"]
; Only value parameters allowed. Values are case insensitive.
param =/ "VALUE" "=" "date"
; Only value parameters allowed. Values are case insensitive.
value = date-time-value
value =/ date-value
; **** SORT-STRING ****
param = text-param
; Only text parameters allowed
value = text-value
; **** SOUND ****
param = snd-inline-param / snd-refer-param / pid-param
value = snd-line-value
; Value MUST match value type
value =/ snd-refer-value
; Value MUST match value type
snd-inline-value = binary-value CRLF
; Value MUST be "b" encoded audio content
snd-inline-param = ("VALUE" "=" "binary")
/ ("ENCODING" "=" "b")
/ ("TYPE" "=" *SAFE-CHAR)
; Value MUST be an IANA registered audio type
snd-refer-value = uri
; URI MUST refer to audio content of given type
snd-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" *SAFE-CHAR)
; Value MUST be an IANA registered audio type
; **** UID ****
param = ""
; No parameters allowed
value = uri
; **** URL ****
param = pid-param
value = uri
; **** VERSION ****
;This type MUST be included in a vCard object.
param = ""
; No parameters allowed
value = text-value
; Value MUST be "4.0"
; **** CLASS ****
param = ""
; No parameters allowed
value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL"
/ iana-token / x-name
; Value are case insensitive
; **** KEY ****
param = key-txt-param / key-bin-param / pid-param
value = text-value
value =/ binary-value
key-txt-param = "TYPE" "=" keytype
key-bin-param = ("TYPE" "=" keytype)
/ ("ENCODING" "=" "b")
; Value MUST be a "b" encoded key or certificate
keytype = param-value
; Type MUST be a media type as defined in RFC 4288
; **** X- **** non-standard property
param = x-bin-param / x-txt-param / pid-param
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
;*******************************************
text-param = ("VALUE" "=" "ptext")
/ ("LANGUAGE" "=" langval)
/ (x-name "=" param-value)
langval = <a language string as defined in [RFC4646]>
pref-param = "PREF" "=" pref-value
pref-value = 1*DIGIT
pid-param = "PID" "=" pid-value *("," pid-value)
pid-value = 1*DIGIT
img-inline-value = binary-value
;Value MUST be "b" encoded image content
img-inline-param
img-inline-param = ("VALUE" "=" "binary")
/ ("ENCODING" "=" "b")
/ ("TYPE" "=" param-value)
;TYPE value MUST be an image media type as defined in RFC 4288
img-refer-value = uri
;URI MUST refer to image content of given type
img-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" param-value)
;TYPE value MUST be an image media type as defined in RFC 4288
adr-value = 0*6(text-value ";") text-value
; PO Box, Extended Address, Street, Locality, Region, Postal
; Code, Country Name
;*******************************************
; vCard Type Value Definition
;*******************************************
text-value-list = 1*text-value *("," 1*text-value)
text-value = *(SAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
ESCAPED-CHAR = "\\" / "\;" / "\," / "\n" / "\N"
; \\ encodes \, \n or \N encodes newline
; \; encodes ;, \, encodes ,
binary-value = <A "b" encoded text value as defined in [RFC2047]>
date-value = <A single date value as defined in [RFC2425]>
time-value = <A single time value as defined in [RFC2425]>
date-time-value = <A single date-time 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-prefix = "+" 1*DIGIT / "(" 1*DIGIT ")"
phone-ext = "ext." 1*DIGIT
uri-value = <A uri value as defined in [RFC2425]>
language-tag-value = langval
utc-offset-value = ("+" / "-") time-hour ":" time-minute
time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59
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:--0203
GENDER:M GENDER:M
LANG;PREF=1:fr
LANG;PREF=2:en
WORK.ORG:Viagenie WORK.ORG:Viagenie
WORK.ADR:;;2600 boul. Laurier\, suite 625; WORK.ADR:;Suite 625;2600 boul. Laurier;
Quebec;QC;G1V 4W1;Canada Quebec;QC;G1V 4W1;Canada
WORK.TEL;TYPE=voice;PREF=1:tel:+1-418-656-9254;ext=102 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:simon.perreault@viagenie.ca WORK.EMAIL:simon.perreault@viagenie.ca
WORK.GEO:46.772673,-71.282945 WORK.GEO: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
TZ:-0500
CLASS:PUBLIC CLASS:PUBLIC
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Pete Resnick FN:Pete Resnick
N:Resnick;Pete;; N:Resnick;Pete;;
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:presnick@qualcomm.com WORK.EMAIL:presnick@qualcomm.com
WORK.URL:http://www.qualcomm.com/~presnick/ WORK.URL:http://www.qualcomm.com/~presnick/
skipping to change at page 57, line 16 skipping to change at page 55, line 40
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: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 10. 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
display directory data in a "safe" environment (e.g., PostScript- display directory data in a "safe" environment (e.g., PostScript-
valued types). valued types).
o vCards can carry cryptographic keys or certificates, as described o vCards can carry cryptographic keys or certificates, as described
skipping to change at page 57, line 45 skipping to change at page 56, line 21
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.9 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 11. IANA Considerations
12.1. Registering New vCard Elements 11.1. MIME Type Registration
Please refer to Section 3.
11.2. Registering New vCard Elements
This section defines the process for registering new or modified This section defines the process for registering new or modified
vCard elements (i.e. properties, parameters, value data types, and vCard elements (i.e. properties, parameters, value data types, and
values) with IANA. values) with IANA.
12.1.1. Registration Procedure 11.2.1. Registration Procedure
The IETF will create a mailing list, vcard@ietf.org [1], which can be The IETF will create a mailing list, vcard@ietf.org [1], which can be
used for public discussion of vCard element proposals prior to used for public discussion of vCard element proposals prior to
registration. Use of the mailing list is strongly encouraged. The registration. Use of the mailing list is strongly encouraged. The
IESG will appoint a designated expert who will monitor the IESG will appoint a designated expert who will monitor the
vcard@ietf.org [1] mailing list and review registrations. vcard@ietf.org [1] mailing list and review registrations.
Registration of new vCard elements MUST be reviewed by the designated Registration of new vCard elements MUST be reviewed by the designated
expert and published in an RFC. A Standard Tracks RFC is REQUIRED expert and published in an RFC. A Standard Tracks RFC is REQUIRED
for the regisration of new value data types that modify existing for the regisration of new value data types that modify existing
skipping to change at page 58, line 31 skipping to change at page 57, line 10
template, defined in the sections below, is sent to template, defined in the sections below, is sent to
vcard@ietf.org [1] and iana@iana.org [2]. The designated expert is vcard@ietf.org [1] and iana@iana.org [2]. The designated expert is
expected to tell IANA and the submitter of the registration within expected to tell IANA and the submitter of the registration within
two weeks whether the registration is approved, approved with minor two weeks whether the registration is approved, approved with minor
changes, or rejected with cause. When a registration is rejected changes, or rejected with cause. When a registration is rejected
with cause, it can be re-submitted if the concerns listed in the with cause, it can be re-submitted if the concerns listed in the
cause are addressed. Decisions made by the designated expert can be cause are addressed. Decisions made by the designated expert can be
appealed to the IESG Applications Area Director, then to the IESG. appealed to the IESG Applications Area Director, then to the IESG.
They follow the normal appeals procedure for IESG decisions. They follow the normal appeals procedure for IESG decisions.
12.1.2. Vendor Namespace 11.2.2. Vendor Namespace
The vendor namespace is used for vCard elements associated with The vendor namespace is used for vCard elements associated with
commercially available products. "Vendor" or "producer" are commercially available products. "Vendor" or "producer" are
construed as equivalent and very broadly in this context. construed as equivalent and very broadly in this context.
A registration may be placed in the vendor namespace by anyone who A registration may be placed in the vendor namespace by anyone who
needs to interchange files associated with the particular product. needs to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or However, the registration formally belongs to the vendor or
organization handling the vCard elements in the namespace being organization handling the vCard elements in the namespace being
registered. Changes to the specification will be made at their registered. Changes to the specification will be made at their
skipping to change at page 59, line 8 skipping to change at page 57, line 36
well-known producer (e.g., "VND-MUDPIE") or by an IANA-approved well-known producer (e.g., "VND-MUDPIE") or by an IANA-approved
designation of the producer's name that is followed by a vCard designation of the producer's name that is followed by a vCard
element designation (e.g., "VND-BIGCOMPANY-MUDPIE"). element designation (e.g., "VND-BIGCOMPANY-MUDPIE").
While public exposure and review of vCard elements to be registered While public exposure and review of vCard elements to be registered
in the vendor namespace is not required, using the vcard@ietf.org [1] in the vendor namespace is not required, using the vcard@ietf.org [1]
mailing list for review is strongly encouraged to improve the quality mailing list for review is strongly encouraged to improve the quality
of those specifications. Registrations in the vendor namespace may of those specifications. Registrations in the vendor namespace may
be submitted directly to the IANA. be submitted directly to the IANA.
12.1.3. Registration Template for Groups 11.2.3. Registration Template for Groups
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 Allowed Properties: List of properties that may be placed inside the
group. 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 11.2.4. Registration Template for Properties
A property is defined by completing the following template. A property is defined by completing the following template.
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
skipping to change at page 60, line 8 skipping to change at page 58, line 36
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 11.2.5. Registration Template for Parameters
A parameter is defined by completing the following template. A parameter is defined by completing the following template.
Parameter name: The name of the parameter. Parameter name: The name of the parameter.
Purpose: The purpose of the parameter. Give a short but clear Purpose: The purpose of the parameter. Give a short but clear
description. description.
Description: Any special notes about the parameter, how it is to be Description: Any special notes about the parameter, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the parameter definition needs to be Format definition: The ABNF for the parameter definition needs to be
specified. specified.
Example(s): One or more examples of instances of the parameter needs Example(s): One or more examples of instances of the parameter needs
to be specified. to be specified.
12.1.6. Registration Template for Value Data Types 11.2.6. Registration Template for Value Data Types
A value data type is defined by completing the following template. A value data type is defined by completing the following template.
Value name: The name of the value type. Value name: The name of the value type.
Purpose: The purpose of the value type. Give a short but clear Purpose: The purpose of the value type. Give a short but clear
description. description.
Description: Any special notes about the value type, how it is to be Description: Any special notes about the value type, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the value type definition needs to Format definition: The ABNF for the value type definition needs to
be specified. be specified.
Example(s): One or more examples of instances of the value type Example(s): One or more examples of instances of the value type
needs to be specified. needs to be specified.
12.1.7. Registration Template for Values 11.2.7. Registration Template for Values
A value is defined by completing the following template. A value is defined by completing the following template.
Value: The value literal. Value: The value literal.
Purpose: The purpose of the value. Give a short but clear Purpose: The purpose of the value. Give a short but clear
description. description.
Conformance: The vCard properties and/or parameters that can take Conformance: The vCard properties and/or parameters that can take
this value needs to be specified. this value needs to be specified.
skipping to change at page 61, line 29 skipping to change at page 60, line 10
Purpose: This value is used to specify the access classification of Purpose: This value is used to specify the access classification of
top-secret vCards. top-secret vCards.
Conformance: This value can be used with the "CLASS" property. Conformance: This value can be used with the "CLASS" property.
Example(s): The following is an example of this value used with the Example(s): The following is an example of this value used with the
"CLASS" property: "CLASS" property:
CLASS:TOP-SECRET CLASS:TOP-SECRET
12.2. Initial vCard Elements Registries 11.3. Initial vCard Elements Registries
The IANA is requested to create and maintain the following registries The IANA is requested to create and maintain the following registries
for vCard elements with pointers to appropriate reference documents. for vCard elements with pointers to appropriate reference documents.
12.2.1. Groups Registry 11.3.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 | Allowed Properties | Reference | | Goup | Description | Status | Allowed Properties | Reference |
+------+--------------+---------+-----------------------+-----------+ +------+--------------+---------+-----------------------+-----------+
| WORK | Properties | Current | FN, NICKNAME, PHOTO, | RFCXXXX | | WORK | Properties | Current | FN, NICKNAME, PHOTO, | RFCXXXX |
| | related to | | ADR, LABEL, TEL, | | | | related to | | ADR, LABEL, TEL, | |
| | an | | EMAIL, IMPP, LANG, | | | | an | | EMAIL, IMPP, LANG, | |
| | individual's | | TZ, GEO, TITLE, ROLE, | | | | individual's | | TZ, GEO, TITLE, ROLE, | |
| | work place. | | LOGO, ORG, RELATED, | | | | work place. | | LOGO, ORG, RELATED, | |
| | | | CATEGORIES, NOTE, | | | | | | CATEGORIES, NOTE, | |
| | | | SOUND, URL, KEY | | | | | | SOUND, URL, KEY, | |
| | | | FBURL, CALADRURI, | |
| | | | CALURI | |
| HOME | Properties | Current | FN, NICKNAME, PHOTO, | RFCXXXX | | HOME | Properties | Current | FN, NICKNAME, PHOTO, | RFCXXXX |
| | related to | | ADR, LABEL, TEL, | | | | related to | | ADR, LABEL, TEL, | |
| | an | | EMAIL, IMPP, LANG, | | | | an | | EMAIL, IMPP, LANG, | |
| | individual's | | TZ, GEO, TITLE, ROLE, | | | | individual's | | TZ, GEO, TITLE, ROLE, | |
| | personal | | LOGO, ORG, RELATED, | | | | personal | | LOGO, ORG, RELATED, | |
| | life. | | CATEGORIES, NOTE, | | | | life. | | CATEGORIES, NOTE, | |
| | | | SOUND, URL, KEY | | | | | | SOUND, URL, KEY, | |
| | | | FBURL, CALADRURI, | |
| | | | CALURI | |
+------+--------------+---------+-----------------------+-----------+ +------+--------------+---------+-----------------------+-----------+
12.2.2. Properties Registry 11.3.2. Properties Registry
The following table is to be used to initialize the properties The following table is to be used to initialize the properties
registry. registry.
+--------------+---------+-------------------------+ +--------------+---------+-------------------------+
| Property | Status | Reference | | 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 |
skipping to change at page 64, line 5 skipping to change at page 62, line 5
| CLIENTPIDMAP | Current | RFCXXXX, Section 7.7.8 | | CLIENTPIDMAP | Current | RFCXXXX, Section 7.7.8 |
| URL | Current | RFCXXXX, Section 7.7.9 | | URL | Current | RFCXXXX, Section 7.7.9 |
| VERSION | Current | RFCXXXX, Section 7.7.10 | | 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 11.3.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 |
| PREF | Current | RFCXXXX, Section 6.4 |
| PID | Current | RFCXXXX, Section 6.5 | | PID | Current | RFCXXXX, Section 6.5 |
| TYPE | Current | RFCXXXX, Section 6.6 | | TYPE | Current | RFCXXXX, Section 6.6 |
+-----------+---------+----------------------+ | GEO | Current | RFCXXXX, Section 7.3.1 |
| TZ | Current | RFCXXXX, Section 7.3.1 |
+-----------+---------+------------------------+
12.2.4. Value Data Types Registry 11.3.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.1 |
| TIME | Current | RFCXXXX, Section 5.3 | | TIME | Current | RFCXXXX, Section 5.3.2 |
| DATE-TIME | Current | RFCXXXX, Section 5.3 | | DATE-TIME | Current | RFCXXXX, Section 5.3.3 |
| TIMESTAMP | Current | RFCXXXX, Section 5.3.4 |
| 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 | | LANGUAGE-TAG | Current | RFCXXXX, Section 5.9 |
+-----------------+---------+----------------------+ +-----------------+---------+------------------------+
12.2.5. Values Registries 11.3.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.
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
| Property | Value | Status | Reference | | Property | Value | Status | Reference |
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
| BEGIN | VCARD | Current | RFCXXXX, Section 7.1.1 | | BEGIN | VCARD | Current | RFCXXXX, Section 7.1.1 |
skipping to change at page 66, line 5 skipping to change at page 64, line 5
| RELATED | TYPE | sibling | Current | RFCXXXX, | | RELATED | TYPE | sibling | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 7.6.6 |
| RELATED | TYPE | manager | Current | RFCXXXX, | | RELATED | TYPE | manager | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 7.6.6 |
| RELATED | TYPE | assistant | Current | RFCXXXX, | | RELATED | TYPE | assistant | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 7.6.6 |
| RELATED | TYPE | agent | Current | RFCXXXX, | | RELATED | TYPE | agent | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 7.6.6 |
+----------+-----------+-----------+---------+----------------------+ +----------+-----------+-----------+---------+----------------------+
13. Acknowledgements 12. Acknowledgements
The authors would like to thank Frank Dawson and Tim Howes, the The authors would like to thank Tim Howes, Mark Smith, and Frank
original authors of [RFC2425] and [RFC2426], as well as the following Dawson, the original authors of [RFC2425] and [RFC2426], as well as
individuals who have participated in the drafting, review and the following individuals who have participated in the drafting,
discussion of this memo: review and 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, Bernard Desruisseaux, Lisa Cauchie, Darryl Champagne, Cyrus Daboo, Bernard Desruisseaux, Lisa
Dusseault, Javier Godoy, Helge Hess, Alexander Mayrhofer, Chris Dusseault, Javier Godoy, Helge Hess, Alexander Mayrhofer, Chris
Newman, Mark Paterson, Julian Reschke, Peter K. Sheerin, Anil Newman, Mark Paterson, Julian Reschke, Peter K. Sheerin, Anil
Srivastava, and Kurt Zeilenga. Srivastava, and Kurt Zeilenga.
14. References 13. References
14.1. Normative References 13.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.
[CCITT.X121.1988] International Telephone and Telegraph [CCITT.X121.1988] International Telephone and Telegraph
Consultative Committee, "International Consultative Committee, "International
Numbering Plan for the Public Data Networks", Numbering Plan for the Public Data
CCITT Recommendation X.121, 1988. Networks", CCITT Recommendation X.121, 1988.
[CCITT.X520.1988] International International Telephone and [CCITT.X520.1988] International International Telephone and
Telegraph Consultative Committee, Telegraph Consultative Committee,
"Information Technology - Open Systems "Information Technology - Open Systems
Interconnection - The Directory: Selected Interconnection - The Directory: Selected
Attribute Types", CCITT Recommendation X.520, Attribute Types", CCITT Recommendation
November 1988. X.520, November 1988.
[CCITT.X521.1988] International International Telephone and [CCITT.X521.1988] International International Telephone and
Telegraph Consultative Committee, Telegraph Consultative Committee,
"Information Technology - Open Systems "Information Technology - Open Systems
Interconnection - The Directory: Selected Interconnection - The Directory: Selected
Object Classes", CCITT Recommendation X.521, Object Classes", CCITT Recommendation X.521,
November 1988. November 1988.
[ISO.8601.1988] International Organization for [I-D.mayrhofer-geo-uri] Mayrhofer, A. and C. Spanring, "A Uniform
Resource Identifier for Geographic Areas
('geo' URI)", draft-mayrhofer-geo-uri-02
(work in progress), February 2008.
[ISO.8601.2000] International Organization for
Standardization, "Data elements and Standardization, "Data elements and
interchange formats - Information interchange interchange formats - Information
- Representation of dates and times", interchange - Representation of dates and
ISO Standard 8601, June 1988. times", ISO Standard 8601, December 2000.
[ISO.8601.2004] International Organization for
Standardization, "Data elements and
interchange formats - Information
interchange - Representation of dates and
times", ISO Standard 8601, December 2004.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose [RFC2046] Freed, N. and N. Borenstein, "Multipurpose
Internet Mail Extensions (MIME) Part Two: Internet Mail Extensions (MIME) Part Two:
Media Types", RFC 2046, November 1996. Media Types", RFC 2046, November 1996.
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail [RFC2047] Moore, K., "MIME (Multipurpose Internet Mail
Extensions) Part Three: Message Header Extensions) Part Three: Message Header
Extensions for Non-ASCII Text", RFC 2047, Extensions for Non-ASCII Text", RFC 2047,
November 1996. November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2119] Bradner, S., "Key words for use in RFCs to
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.
[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",
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.
[RFC3629] Yergeau, F., "UTF-8, a transformation format [RFC3629] Yergeau, F., "UTF-8, a transformation format
of ISO 10646", STD 63, RFC 3629, of ISO 10646", STD 63, RFC 3629,
November 2003. November 2003.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone [RFC3966] Schulzrinne, H., "The tel URI for Telephone
Numbers", RFC 3966, December 2004. Numbers", RFC 3966, December 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. [RFC3986] Berners-Lee, T., Fielding, R., and L.
Masinter, "Uniform Resource Identifier (URI): Masinter, "Uniform Resource Identifier
Generic Syntax", STD 66, RFC 3986, (URI): Generic Syntax", STD 66, RFC 3986,
January 2005. January 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A [RFC4122] Leach, P., Mealling, M., and R. Salz, "A
Universally Unique IDentifier (UUID) URN Universally Unique IDentifier (UUID) URN
Namespace", RFC 4122, July 2005. Namespace", RFC 4122, July 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type [RFC4288] Freed, N. and J. Klensin, "Media Type
Specifications and Registration Procedures", Specifications and Registration Procedures",
BCP 13, RFC 4288, December 2005. BCP 13, RFC 4288, December 2005.
skipping to change at page 68, line 18 skipping to change at page 66, line 27
September 2006. September 2006.
[RFC4770] Jennings, C. and J. Reschke, Ed., "vCard [RFC4770] Jennings, C. and J. Reschke, Ed., "vCard
Extensions for Instant Messaging (IM)", Extensions for Instant Messaging (IM)",
RFC 4770, January 2007. RFC 4770, January 2007.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF [RFC5234] Crocker, D. and P. Overell, "Augmented BNF
for Syntax Specifications: ABNF", STD 68, for Syntax Specifications: ABNF", STD 68,
RFC 5234, January 2008. RFC 5234, January 2008.
[oldreference_UNICODE] The International Organization for [RFC5322] Resnick, P., Ed., "Internet Message Format",
Standardization, "The Unicode Standard - RFC 5322, October 2008.
Version 2.0", The Unicode Consortium",
July 1996.
[oldreference_VCARD] Internet Mail Consortium, "vCard - The [oldreference_VCARD] Internet Mail Consortium, "vCard - The
Electronic Business Card Version 2.1", Electronic Business Card Version 2.1",
September September. September September.
14.2. Informative References 13.2. Informative References
[ISO9070] The International Organization for [ISO9070] The International Organization for
Standardization, "ISO 9070, Information Standardization, "ISO 9070, Information
Processing - SGML support facilities - Processing - SGML support facilities -
Registration Procedures for Public Text Owner Registration Procedures for Public Text
Identifiers", April 1991. Owner Identifiers", April 1991.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and
P. Faltstrom, "Uniform Resource Names (URN) P. Faltstrom, "Uniform Resource Names (URN)
Namespace Definition Mechanisms", BCP 66, Namespace Definition Mechanisms", BCP 66,
RFC 3406, October 2002. RFC 3406, October 2002.
[WGS84] National Imagery and Mapping Agency,
"Department of Defense World Geodetic System
1984, Third Edition", NIMA TR8350.2,
January 2000.
URIs URIs
[1] <mailto:vcard@ietf.org> [1] <mailto:vcard@ietf.org>
[2] <mailto:iana@iana.org> [2] <mailto:iana@iana.org>
Appendix A. Differences from RFCs 2425 and 2426 Appendix A. Differences from RFCs 2425 and 2426
This appendix contains a list of changes that have been made in the This appendix contains a list of changes that have been made in the
vCard specification from RFCs 2425 and 2426. vCard specification from RFCs 2425 and 2426.
skipping to change at page 70, line 19 skipping to change at page 68, line 19
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.
o Date and time values now only support the basic format.
Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -06 B.1. Changes in -07
o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type.
o Made GEO a URI.
o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property.
o Completely reworked the date, time, and date-time grammars.
o Added the timestamp value type.
o REV now has the timestamp value type.
o Rewrote ABNF.
o ORG can now have a single level.
B.2. Changes in -06
o Corrected omission of resetability to text value for RELATED. o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value. o Let KEY value type be reset to a URI value.
o ABNF fixes. o ABNF fixes.
o Made gender values extensible. o Made gender values extensible.
o Gave the PREF parameter a positive integer value. o Gave the PREF parameter a positive integer value.
skipping to change at page 71, line 13 skipping to change at page 69, line 38
o Removed TYPE parameter from EMAIL properties in examples. o Removed TYPE parameter from EMAIL properties in examples.
o Created the CLIENTPIDMAP property. o Created the CLIENTPIDMAP property.
o Changed PID value to a pair of small integers. o Changed PID value to a pair of small integers.
o Completely reworked synchronization mechanisms. o Completely reworked synchronization mechanisms.
o Created brand new synchronization example. o Created brand new synchronization example.
B.2. Changes in -05 B.3. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.3. Changes in -04 B.4. 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 71, line 47 skipping to change at page 70, line 24
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.4. Changes in -03 B.5. 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.5. Changes in -02 B.6. 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 72, line 38 skipping to change at page 71, line 14
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.6. Changes in -01 B.7. 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 73, line 18 skipping to change at page 71, line 42
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.7. Changes in -00 B.8. 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.
 End of changes. 175 change blocks. 
767 lines changed or deleted 737 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/