draft-ietf-vcarddav-vcardrev-07.txt   draft-ietf-vcarddav-vcardrev-08.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) May 6, 2009 Updates: 2739 (if approved) July 13, 2009
Intended status: Standards Track Intended status: Standards Track
Expires: November 7, 2009 Expires: January 14, 2010
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-07 draft-ietf-vcarddav-vcardrev-08
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 November 7, 2009. This Internet-Draft will expire on January 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 31 skipping to change at page 2, line 31
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 6 3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 6
4. vCard Format Specification . . . . . . . . . . . . . . . . . . 7 4. vCard Format Specification . . . . . . . . . . . . . . . . . . 7
4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 8 4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 8
4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 9 4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 9
4.3. Property Value Escaping . . . . . . . . . . . . . . . . . 11 4.3. Property Value Escaping . . . . . . . . . . . . . . . . . 11
5. Property Value Data Types . . . . . . . . . . . . . . . . . . 11 5. Property Value Data Types . . . . . . . . . . . . . . . . . . 11
5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3. DATE, TIME, DATE-TIME, and TIMESTAMP . . . . . . . . . . . 14 5.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 14
5.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 15 5.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 15
5.3.4. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 15 5.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 15
5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 16
5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.8. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 16 5.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 17
5.9. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 17
6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 17 6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 17
6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 20 7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 21
7.1. General Properties . . . . . . . . . . . . . . . . . . . . 21 7.1. General Properties . . . . . . . . . . . . . . . . . . . . 21
7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 21 7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 21 7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 22 7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2. Identification Properties . . . . . . . . . . . . . . . . 24 7.2. Identification Properties . . . . . . . . . . . . . . . . 24
7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 25 7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 25 7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 26
7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 26 7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 26
7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 28 7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 28 7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2.9. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 29 7.2.9. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 29
7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 29 7.2.10. SEX . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 30
7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 31 7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4. Communications Properties . . . . . . . . . . . . . . . . 31 7.4. Communications Properties . . . . . . . . . . . . . . . . 32
7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 31 7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 32 7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 33
7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.5. Geographical Properties . . . . . . . . . . . . . . . . . 34 7.5. Geographical Properties . . . . . . . . . . . . . . . . . 35
7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 34 7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 34 7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.6. Organizational Properties . . . . . . . . . . . . . . . . 35 7.6. Organizational Properties . . . . . . . . . . . . . . . . 36
7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 35 7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 36
7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 35 7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 36 7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 38
7.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 38 7.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 39
7.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 39 7.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 40
7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 40 7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 41
7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 40 7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 41
7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 42
7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 41 7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 42
7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 41 7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 42 7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 43
7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 43 7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 44
7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 43 7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.7.8. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 44 7.7.8. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 45
7.7.9. URL . . . . . . . . . . . . . . . . . . . . . . . . . 45 7.7.9. URL . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.7.10. VERSION . . . . . . . . . . . . . . . . . . . . . . . 45 7.7.10. VERSION . . . . . . . . . . . . . . . . . . . . . . . 47
7.8. Security Properties . . . . . . . . . . . . . . . . . . . 46 7.8. Security Properties . . . . . . . . . . . . . . . . . . . 47
7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 46 7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 47
7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 47 7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 47 7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 49
7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 47 7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 49
7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 48 7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 50
7.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 49 7.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 50
7.10. Extended Properties and Parameters . . . . . . . . . . . . 49 7.10. Extended Properties and Parameters . . . . . . . . . . . . 51
8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 49 8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 51
8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 49 8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 51
8.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 50 8.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 51
8.1.2. Matching Property Instances . . . . . . . . . . . . . 50 8.1.2. Matching Property Instances . . . . . . . . . . . . . 51
8.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 50 8.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 52
8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 51 8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 51 8.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 52
8.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 51 8.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 53
8.2.3. Adding and Sharing a Property . . . . . . . . . . . . 52 8.2.3. Adding and Sharing a Property . . . . . . . . . . . . 53
8.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 52 8.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 54
8.2.5. Global Context Simplification . . . . . . . . . . . . 54 8.2.5. Global Context Simplification . . . . . . . . . . . . 55
9. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 55 9. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 56
10. Security Considerations . . . . . . . . . . . . . . . . . . . 55 10. Security Considerations . . . . . . . . . . . . . . . . . . . 56
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57
11.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 56 11.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 57
11.2. Registering New vCard Elements . . . . . . . . . . . . . . 56 11.2. Registering New vCard Elements . . . . . . . . . . . . . . 57
11.2.1. Registration Procedure . . . . . . . . . . . . . . . . 56 11.2.1. Registration Procedure . . . . . . . . . . . . . . . . 57
11.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 57 11.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 58
11.2.3. Registration Template for Groups . . . . . . . . . . . 57 11.2.3. Registration Template for Groups . . . . . . . . . . . 58
11.2.4. Registration Template for Properties . . . . . . . . . 58 11.2.4. Registration Template for Properties . . . . . . . . . 59
11.2.5. Registration Template for Parameters . . . . . . . . . 58 11.2.5. Registration Template for Parameters . . . . . . . . . 59
11.2.6. Registration Template for Value Data Types . . . . . . 59 11.2.6. Registration Template for Value Data Types . . . . . . 60
11.2.7. Registration Template for Values . . . . . . . . . . . 59 11.2.7. Registration Template for Values . . . . . . . . . . . 60
11.3. Initial vCard Elements Registries . . . . . . . . . . . . 60 11.3. Initial vCard Elements Registries . . . . . . . . . . . . 61
11.3.1. Groups Registry . . . . . . . . . . . . . . . . . . . 60 11.3.1. Groups Registry . . . . . . . . . . . . . . . . . . . 61
11.3.2. Properties Registry . . . . . . . . . . . . . . . . . 60 11.3.2. Properties Registry . . . . . . . . . . . . . . . . . 62
11.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 62 11.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 64
11.3.4. Value Data Types Registry . . . . . . . . . . . . . . 62 11.3.4. Value Data Types Registry . . . . . . . . . . . . . . 64
11.3.5. Values Registries . . . . . . . . . . . . . . . . . . 62 11.3.5. Values Registries . . . . . . . . . . . . . . . . . . 64
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 64 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 66
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66
13.1. Normative References . . . . . . . . . . . . . . . . . . . 64 13.1. Normative References . . . . . . . . . . . . . . . . . . . 66
13.2. Informative References . . . . . . . . . . . . . . . . . . 66 13.2. Informative References . . . . . . . . . . . . . . . . . . 69
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 67 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 69
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 67 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 69
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 67 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 70
A.3. New Properties and Parameters . . . . . . . . . . . . . . 67 A.3. New Properties and Parameters . . . . . . . . . . . . . . 70
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 68 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 70
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 68 publication) . . . . . . . . . . . . . . . . . . . . 71
B.1. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 68 B.1. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 71
B.2. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 68 B.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 71
B.3. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 69 B.3. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 72
B.4. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 69 B.4. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 72
B.5. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 70 B.5. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 72
B.6. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 70 B.6. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 73
B.7. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 71 B.7. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 73
B.8. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 71 B.8. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 74
B.9. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 75
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 7, line 16 skipping to change at page 7, line 16
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-07 Published specification: draft-ietf-vcarddav-vcardrev-08
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 9, line 30 skipping to change at page 9, line 30
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 = "SOURCE" / "NAME" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "GENDER" / "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "SEX"
/ "ADR" / "LABEL" / "TEL" / "EMAIL" / "IMPP" / "LANG" / "ADR" / "LABEL" / "TEL" / "EMAIL" / "IMPP" / "LANG"
/ "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "ORG" / "MEMBER" / "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "ORG" / "MEMBER"
/ "RELATED" / "CATEGORIES" / "NOTE" / "PRODID" / "REV" / "RELATED" / "CATEGORIES" / "NOTE" / "PRODID" / "REV"
/ "SORT-STRING" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL" / "SORT-STRING" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL"
/ "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI" / "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI"
/ "CALURI" / iana-token / x-name / "CALURI" / iana-token / x-name
; Parsing of the param and value is based on the "name" as ; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below. ; defined in ABNF sections below.
; Group and name are case-insensitive. ; Group and name are case-insensitive.
skipping to change at page 11, line 41 skipping to change at page 11, line 41
5. Property Value Data Types 5. Property Value Data Types
Standard value types are defined below. Standard value types are defined below.
value = text value = text
/ text-list / text-list
/ date-list / date-list
/ time-list / time-list
/ date-time-list / date-time-list
/ date-and-or-time-list
/ timestamp-list / timestamp-list
/ boolean / boolean
/ integer-list / integer-list
/ float-list / float-list
/ binary / binary
/ utc-offset
/ URI ; from Appendix A of [RFC3986] / URI ; from Appendix A of [RFC3986]
/ iana-valuespec / iana-valuespec
; Actual value type depends on property name and VALUE parameter. ; Actual value type depends on property name and VALUE parameter.
text = *VALUE-CHAR text = *VALUE-CHAR
text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR) text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)
TEXT-LIST-CHAR = "\\" / "\," / "\n" TEXT-LIST-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \ or newline> / <any VALUE-CHAR except , or \ or newline>
; Backslashes, commas, and newlines must be encoded. ; Backslashes, commas, and newlines must be encoded.
date-list = date *("," date) date-list = date *("," date)
time-list = time *("," time) time-list = time *("," time)
date-time-list = date-time *("," date-time) date-time-list = date-time *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-ortime)
timestamp-list = timestamp *("," timestamp) timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer) integer-list = integer *("," integer)
float-list = float *("," float) float-list = float *("," float)
boolean = "TRUE" / "FALSE" boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT] float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-" sign = "+" / "-"
binary = <A binary string encoded according binary = <A binary string encoded as per the "encoding" parameter>
to the "encoding" parameter>
year = 4DIGIT ; 0000-9999 year = 4DIGIT ; 0000-9999
month = 2DIGIT ; 01-12 month = 2DIGIT ; 01-12
day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
hour = 2DIGIT ; 00-23 hour = 2DIGIT ; 00-23
minute = 2DIGIT ; 00-59 minute = 2DIGIT ; 00-59
second = 2DIGIT ; 00-58/59/60 depending on leap second second = 2DIGIT ; 00-58/59/60 depending on leap second
zone = "Z" / utc-offset zone = "Z" / utc-offset
date = year month day date = year [month day]
/ year "-" month / year "-" month
/ "--" month [day] / "--" month [day]
/ "--" "-" day / "--" "-" day
date-noreduc = year month day date-noreduc = year month day
/ "--" month day / "--" month day
/ "--" "-" day / "--" "-" day
date-complete = year month day date-complete = year month day
time = hour [minute [second]] [zone] time = hour [minute [second]] [zone]
/ "-" minute [second] [zone] / "-" minute [second] [zone]
/ "-" "-" second [zone] / "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone] time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone] time-complete = hour minute second [zone]
date-time = date-noreduc "T" time-notrunc date-time = date-noreduc "T" time-notrunc
timestamp = date-complete "T" time-complete timestamp = date-complete "T" time-complete
date-and-or-time = date-time / date / "T" time
utc-offset = sign hour [minute] 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
that there is no way to override this parameter on a per-property that there is no way to override this parameter on a per-property
basis. As for the language, it is controlled by the "language" basis. As for the language, it is controlled by the "language"
property parameter defined in Section 6.1. property parameter defined in Section 6.1.
skipping to change at page 14, line 12 skipping to change at page 14, line 14
is too large, or otherwise undesirable to include directly. The is too large, or otherwise undesirable to include directly. The
format for the URI is as defined in [RFC3986]. Note that the value format for the URI is as defined in [RFC3986]. Note that the value
of a property of type "uri" is what the URI points to, not the URI of a property of type "uri" is what the URI points to, not the URI
itself. itself.
Examples for "uri": Examples for "uri":
http://www.example.com/my/picture.jpg http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen ldap://ldap.example.com/cn=babs%20jensen
5.3. DATE, TIME, DATE-TIME, and TIMESTAMP 5.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP
"date", "time", "date-time", and "timestamp": Each of these value "date", "time", "date-time", and "timestamp": Each of these value
types is based on a the definitions in [ISO.8601.2004] standard. types is based on a the definitions in [ISO.8601.2004] standard.
Multiple such values can be specified using the comma-separated Multiple such values can be specified using the comma-separated
notation. notation.
Only the basic format is supported. Only the basic format is supported.
5.3.1. DATE 5.3.1. DATE
skipping to change at page 15, line 35 skipping to change at page 15, line 36
Truncation of the date part, as specified in [ISO.8601.2000] section Truncation of the date part, as specified in [ISO.8601.2000] section
5.4.2 c), is permitted. 5.4.2 c), is permitted.
Examples for "date-time": Examples for "date-time":
19961022T140000 19961022T140000
--1022T1400 --1022T1400
---22T14 ---22T14
5.3.4. TIMESTAMP 5.3.4. DATE-AND-OR-TIME
Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous
interpretation, a standalone TIME value is always preceded by a "T".
Examples for "date-and-or-time":
19961022T140000
--1022T1400
---22T14
19850412
1985-04
1985
--0412
---12
T102200
T1022
T10
T-2200
T--00
T102200Z
T102200-0800
5.3.5. TIMESTAMP
A complete date and time of day combination as specified in A complete date and time of day combination as specified in
[ISO.8601.2004] section 4.3.2. [ISO.8601.2004] section 4.3.2.
Examples for "timestamp": Examples for "timestamp":
19961022T140000 19961022T140000
19961022T140000Z 19961022T140000Z
19961022T140000-05 19961022T140000-05
19961022T140000-0500 19961022T140000-0500
skipping to change at page 16, line 48 skipping to change at page 17, line 35
"binary": The "binary" value type specifies that the type value is "binary": The "binary" value type specifies that the type value is
inline, encoded binary data. This value type can be specified in the inline, encoded binary data. This value type can be specified in the
PHOTO, LOGO, SOUND, and KEY types. PHOTO, LOGO, SOUND, and KEY types.
If inline encoded binary data is specified, the ENCODING type If inline encoded binary data is specified, the ENCODING type
parameter MUST be used to specify the encoding format. The binary parameter MUST be used to specify the encoding format. The binary
data MUST be encoded using the "B" encoding format. Long lines of data MUST be encoded using the "B" encoding format. Long lines of
encoded binary data SHOULD BE folded to 75 characters using the encoded binary data SHOULD BE folded to 75 characters using the
folding method defined in Section 4.1. folding method defined in Section 4.1.
5.8. UTC-OFFSET 5.8. LANGUAGE-TAG
"utc-offset": The "utc-offset" value type specifies that the type
value is a signed offset from UTC. This value type can be specified
in the TZ type.
The value type is an offset from Coordinated Universal Time (UTC).
It is specified as a positive or negative difference in units of
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
to 59. Hour and minutes are 2-digits with high order zeroes required
to maintain digit count. The basic format for ISO 8601 UTC offsets
MUST be used.
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.
Property parameter values that contain the COLON (US-ASCII decimal Property parameter values that contain the COLON (US-ASCII decimal
skipping to change at page 19, line 27 skipping to change at page 19, line 47
value-type = "text" value-type = "text"
/ "uri" / "uri"
/ "date" / "date"
/ "time" / "time"
/ "date-time" / "date-time"
/ "timestamp" / "timestamp"
/ "boolean" / "boolean"
/ "integer" / "integer"
/ "float" / "float"
/ "binary" / "binary"
/ "utc-offset"
/ "language-tag" / "language-tag"
/ iana-token ; registered as described in section 12 / iana-token ; registered as described in section 12
/ x-name / x-name
6.4. PREF 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 an integer between 1 and 100 that author. Its value MUST be an integer between 1 and 100 that
quantifies the level of preferredness. Lower values correspond to a quantifies the level of preferredness. Lower values correspond to a
skipping to change at page 21, line 39 skipping to change at page 22, line 7
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: ABNF:
param = ; no parameter allowed BEGIN-param = ; no parameter allowed
value = "VCARD" BEGIN-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.
skipping to change at page 22, line 23 skipping to change at page 22, line 37
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: ABNF:
param = ; no parameter allowed END-param = ; no parameter allowed
value = "VCARD" END-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.
skipping to change at page 22, line 51 skipping to change at page 23, line 18
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: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param SOURCE-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri SOURCE-value = uri
Examples: Examples:
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/ SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf Jean%20Dupont.vcf
7.1.4. NAME 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 23, line 27 skipping to change at page 23, line 44
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: ABNF:
param = "VALUE=text" / any-param NAME-param = "VALUE=text" / any-param
value = text NAME-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.
skipping to change at page 23, line 50 skipping to change at page 24, line 21
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: ABNF:
param = "VALUE=text" / any-param KIND-param = "VALUE=text" / any-param
value = "individual" / "group" / "org" / "location" KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name / iana-token / x-name
Example: Example:
This represents someone named Jane Doe working in the marketing This represents someone named Jane Doe working in the marketing
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
skipping to change at page 24, line 49 skipping to change at page 25, line 20
Value type: A single text value. Value type: A single text value.
Cardinality: (1,n) Cardinality: (1,n)
Special notes: This property is based on the semantics of the X.520 Special notes: This property is based on the semantics of the X.520
Common Name attribute. The property MUST be present in the vCard Common Name attribute. The property MUST be present in the vCard
object. object.
ABNF: ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param FN-param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param / any-param
value = text FN-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 25, line 31 skipping to change at page 26, line 5
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: ABNF:
param = "VALUE=text" / language-param / any-param N-param = "VALUE=text" / language-param / any-param
value = list-component 3(";" list-component) N-value = list-component 3(";" list-component)
list-component = list-component-value *("," list-component-value) list-component = list-component-value *("," list-component-value)
list-component-value = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII list-component-value = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E / %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
Examples: Examples:
N:Public;John,Q.;Mr.;Esq. N:Public;John,Q.;Mr.;Esq.
N:Stevenson;John,Philip,Paul;Dr.;Jr.,M.D.,A.C.P. N:Stevenson;John,Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
skipping to change at page 26, line 17 skipping to change at page 26, line 35
Cardinality: (0,n) Cardinality: (0,n)
Special note: The nickname is the descriptive name given instead of Special note: The nickname is the descriptive name given instead of
or in addition to the one belonging to a person, place, or thing. or in addition to the one belonging to a person, place, or thing.
It can also be used to specify a familiar form of a proper name It can also be used to specify a familiar form of a proper name
specified by the FN or N properties. specified by the FN or N properties.
ABNF: ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param NICKNAME-param = "VALUE=text" / language-param / pid-param
/ any-param / pref-param / any-param
value = text-list NICKNAME-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 27, line 7 skipping to change at page 27, line 26
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF: ABNF:
param = inline-param / refer-param PHOTO-param = inline-param / refer-param
value = inline-value / refer-value PHOTO-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
param =/ pid-param / pref-param / any-param PHOTO-param =/ pid-param / pref-param / any-param
inline-param = "VALUE=binary" inline-param = "VALUE=binary"
/ encoding-param / encoding-param
/ "TYPE=" type-name "/" subtype-name / "TYPE=" type-name "/" subtype-name
; from [RFC4288] section 4.2 ; from [RFC4288] section 4.2
inline-value = binary inline-value = binary
refer-param = "VALUE=uri" refer-param = "VALUE=uri"
refer-value = uri refer-value = uri
skipping to change at page 27, line 37 skipping to change at page 28, line 10
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-and-or-time value. It can
reset to a single date-time or text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
param = "VALUE=" ("date" / "date-time" / "text") BDAY-param = "VALUE=" ("date-and-or-time" / "text")
value = date / date-time / text BDAY-value = date-and-or-time / text
; Value and parameter MUST match. ; Value and parameter MUST match.
param =/ any-param BDAY-param =/ any-param
Examples: Examples:
BDAY:19960415 BDAY:19960415
BDAY:--0415 BDAY:--0415
BDAY;VALUE=date-time:19531015T231000Z BDAY;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-and-or-time value. It can
reset to a single date-time or text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
param = "VALUE=" ("date" / "date-time" / "text") DDAY-param = "VALUE=" ("date-and-or-time" / "text")
value = date / date-time / text DDAY-value = date-and-or-time / text
; Value and parameter MUST match. ; Value and parameter MUST match.
param =/ any-param DDAY-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: ABNF:
param = "VALUE=text" / language-param / any-param BIRTH-param = "VALUE=text" / language-param / any-param
value = text BIRTH-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: ABNF:
param = "VALUE=text" / language-param / any-param DEATH-param = "VALUE=text" / language-param / any-param
value = text DEATH-value = text
Example: Example:
DEATH:Aboard the Titanic\, near Newfoundland DEATH:Aboard the Titanic\, near Newfoundland
7.2.9. GENDER 7.2.9. ANNIVERSARY
Purpose: To specify the gender of the object the vCard represents. Purpose: The date of marriage, or equivalent, of the object the
vCard represents.
Value type: A single text value. Value type: The default is a single date-and-or-time value. It can
also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The value "M" stands for male while "F" stands for ABNF:
female. IANA-registered values and x-names are also allowed.
ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
ANNIVERSARY-value = date-and-or-time / text
; Value and parameter MUST match.
ANNIVERSARY-param =/ any-param
Examples:
ANNIVERSARY:19960415
7.2.10. SEX
Purpose: To specify the sex of the object the vCard represents, as
defined in [ISO.5218.2004].
Value type: A single integer value.
Cardinality: (0,1)
Special notes: The value 0 stands for "not known", 1 stands for
"male", 2 stands for "female", and 9 stands for "not aplicable".
ABNF: ABNF:
param = "VALUE=text" / any-param SEX-param = "VALUE=integer" / any-param
value = "M" / "F" / iana-token / x-name SEX-value = "0" / "1" / "2" / "9"
Example: Example:
GENDER:F SEX:2
7.3. Delivery Addressing Properties 7.3. Delivery Addressing Properties
These types are concerned with information related to the delivery These types are concerned with information related to the delivery
addressing or label for the vCard object. addressing or label for the vCard object.
7.3.1. ADR 7.3.1. ADR
Purpose: To specify the components of the delivery address for the Purpose: To specify the components of the delivery address for the
vCard object. vCard object.
skipping to change at page 30, line 39 skipping to change at page 31, line 33
The GEO parameter can be used to indicate global positioning The GEO parameter can be used to indicate global positioning
information that is specific to this address. Its value is the information that is specific to this address. Its value is the
same as that of the GEO property. same as that of the GEO property.
The TZ parameter can be used to indicate time zone information The TZ parameter can be used to indicate time zone information
that is specific to this address. Its value is the same as that that is specific to this address. Its value is the same as that
of the TZ property. of the TZ property.
ABNF: ABNF:
param = "VALUE=text" / language-param / geo-param / tz-param ADR-param = "VALUE=text" / language-param / geo-param / tz-param
/ pid-param / pref-param / any-param / pid-param / pref-param / any-param
value = list-component 6(";" list-component) ADR-value = list-component 6(";" list-component)
geo-param = "GEO=" DQUOTE uri DQUOTE geo-param = "GEO=" DQUOTE uri DQUOTE
tz-param = "TZ=" utc-offset tz-param = "TZ=" DQUOTE (text / uri) DQUOTE
Example: In this example the post office box and the extended address Example: In this example the post office box and the extended address
are absent. are absent.
ADR;GEO="geo:12.3457,78.910":;;123 Main Street;Any Town;CA ADR;GEO="geo:12.3457,78.910":;;123 Main Street;Any Town;CA
;91921-1234 ;91921-1234;USA
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
skipping to change at page 31, line 22 skipping to change at page 32, line 19
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property value is formatted text that can be used Special notes: The property value is formatted text that can be used
to present a delivery address label for the vCard object. The to present a delivery address label for the vCard object. The
property can include the "PREF" parameter to indicate the property can include the "PREF" parameter to indicate the
preferred delivery address when more than one address is preferred delivery address when more than one address is
specified. specified.
ABNF: ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param LABEL-param = "VALUE=text" / language-param / pid-param
/ any-param / pref-param / any-param
value = text LABEL-value = text
Example: A multi-line address label. Example: A multi-line address label.
LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n
123 Main Street\nAny Town\, CA 91921-1234\nU.S.A. 123 Main Street\nAny Town\, CA 91921-1234\nU.S.A.
7.4. Communications Properties 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
skipping to change at page 32, line 25 skipping to change at page 33, line 22
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: ABNF:
param = "VALUE=uri" / type-param / pid-param / pref-param TEL-param = "VALUE=uri" / type-param / pid-param / pref-param
/ any-param / any-param
value = uri TEL-value = uri
type-value-tel = "text" / "voice" / "fax" / "cell" / "video" type-value-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / iana-token / x-name / "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
skipping to change at page 33, line 7 skipping to change at page 33, line 49
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property can include tye "PREF" parameter to Special notes: The property can include tye "PREF" parameter to
indicate a preferred-use email address when more than one is indicate a preferred-use email address when more than one is
specified. specified.
ABNF: ABNF:
param = "VALUE=text" / pid-param / pref-param / any-param EMAIL-param = "VALUE=text" / pid-param / pref-param / any-param
value = addr-spec ; from [RFC5322] section 3.4.1 EMAIL-value = addr-spec ; from [RFC5322] section 3.4.1
Type example: Type example:
WORK.EMAIL:jqpublic@xyz.example.com 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
skipping to change at page 33, line 31 skipping to change at page 34, line 24
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: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param IMPP-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri IMPP-value = uri
Example: Example:
IMPP;PREF=1:xmpp:alice@example.com IMPP;PREF=1:xmpp:alice@example.com
7.4.4. LANG 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: ABNF:
param = "VALUE=language-tag" / pid-param / pref-param / any-param LANG-param = "VALUE=language-tag" / pid-param / pref-param
value = Language-Tag / any-param
LANG-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
vCard represents. vCard represents.
7.5.1. TZ 7.5.1. TZ
Purpose: To specify information related to the time zone of the Purpose: To specify information related to the time zone of the
object the vCard represents. object the vCard represents.
Value type: The default is a single utc-offset value. It can also Value type: The default is a single text value. It can also be
be reset to a single text value. reset to a single URI value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The type value consists of a single value. Special notes: It is expected that names from the public-domain
Olson database [TZ-DB] will be used, but this is not a
restriction.
Efforts are currently being directed at creating a standard URI
scheme for expressing time zone information. Usage of such a
scheme would ensure a high level of interoperability between
implementations that support it.
ABNF: ABNF:
param = "VALUE=" ("utc-offset" / "text") TZ-param = "VALUE=" ("text" / "uri")
value = utc-offset / text TZ-value = text / uri
; Value and parameter must match ; Value and parameter must match
param =/ pid-param / pref-param / any-param TZ-param =/ pid-param / pref-param / any-param
Type examples: Type examples:
TZ:-0500 TZ:-0500; 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 URI. Value type: A single URI.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The "geo" URI scheme [I-D.mayrhofer-geo-uri] is Special notes: The "geo" URI scheme [I-D.mayrhofer-geo-uri] is
particularly well-suited for this property, but other schemes MAY particularly well-suited for this property, but other schemes MAY
be used. be used.
ABNF: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param GEO-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri GEO-value = uri
Example: Example:
GEO: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 position or job of the object the vCard
of the object the vCard represents. represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property is based on the X.520 Title attribute. Special notes: This property is based on the X.520 Title attribute.
ABNF: ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param TITLE-param = "VALUE=text" / language-param / pid-param
/ any-param / pref-param / any-param
value = text TITLE-value = text
Example: Example:
TITLE:Director\, Research and Development TITLE:Research Scientist
7.6.2. ROLE 7.6.2. ROLE
Purpose: To specify information concerning the role, occupation, or Purpose: To specify the function or part played in a particular
business category of the object the vCard represents. situation by the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property is based on the X.520 Business Category Special notes: This property is based on the X.520 Business Category
explanatory attribute. This property is included as an explanatory attribute. This property is included as an
organizational type to avoid confusion with the semantics of the organizational type to avoid confusion with the semantics of the
TITLE property and incorrect usage of that property when the TITLE property and incorrect usage of that property when the
semantics of this property is intended. semantics of this property is intended.
ABNF: ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param / any-param
value = text ROLE-value = text
Example: Example:
ROLE:Programmer ROLE:Project Leader
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
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.
skipping to change at page 37, line 7 skipping to change at page 38, line 7
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF: ABNF:
param = inline-param / refer-param LOGO-param = inline-param / refer-param
value = inline-value / refer-value LOGO-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
param =/ language-param / pid-param / pref-param / any-param LOGO-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...>
skipping to change at page 37, line 39 skipping to change at page 38, line 39
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property is based on the X.520 Organization Name Special notes: The property is based on the X.520 Organization Name
and Organization Unit attributes. The property value is a and Organization Unit attributes. The property value is a
structured type consisting of the organization name, followed by structured type consisting of the organization name, followed by
zero or more levels of organizational unit names. zero or more levels of organizational unit names.
ABNF: ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param ORG-param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param / any-param
value = component *(";" component) ORG-value = component *(";" component)
component = "\\" / "\;" / "\n" / WSP / NON-ASCII component = "\\" / "\;" / "\n" / WSP / NON-ASCII
/ %x21-3A / %x3C-5B / %x5D-7E / %x21-3A / %x3C-5B / %x5D-7E
Example: A property value consisting of an organizational name, Example: A property value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name. organizational unit #1 name and organizational unit #2 name.
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC\, Inc.;North American Division;Marketing
7.6.5. MEMBER 7.6.5. MEMBER
skipping to change at page 38, line 20 skipping to change at page 39, line 20
vCard object. For example, an e-mail distribution list could vCard object. For example, an e-mail distribution list could
employ the "mailto" URI scheme for efficiency. employ the "mailto" URI scheme for efficiency.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property MUST NOT be present unless the value of Special notes: This property MUST NOT be present unless the value of
the KIND property is "group". the KIND property is "group".
ABNF: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param MEMBER-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri MEMBER-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
skipping to change at page 39, line 25 skipping to change at page 40, line 25
Special notes: The TYPE parameter MAY be used to characterize the Special notes: The TYPE parameter MAY be used to characterize the
related individual. The understood types are: related individual. The understood types are:
* "parent" means that the related individual is the parent of the * "parent" means that the related individual is the parent of the
individual this vCard represents. individual this vCard represents.
* "child" means the opposite of "parent". * "child" means the opposite of "parent".
* "sibling" means that the two individuals are siblings. * "sibling" means that the two individuals are siblings.
* "manager" means that the related individual is the direct * "spouse" for a spouse, domestic partner, or similar relation.
* "family" for any other family relationship.
* "friend" for a friend.
* "supervisor" 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.
* "supervisee" means the opposite of "supervisor".
* "assistant" for an assistant or secretary. * "assistant" for an assistant or secretary.
* "colleague" for any other workplace relationship.
* "agent" for a person who will act on behalf of the individual * "agent" for a person who will act on behalf of the individual
or resource associated with the vCard. or resource associated with the vCard.
* "emergency" indicates an emergency contact. * "emergency" indicates an emergency contact.
Other types may be registered to IANA as described in Other types may be registered to IANA as described in
Section 11.2, and private extensions starting with "X-" may be Section 11.2, and private extensions starting with "X-" may be
used. used.
ABNF: ABNF:
param = "VALUE=" ("uri" / "text") RELATED-param = "VALUE=" ("uri" / "text")
value = uri / text RELATED-value = uri / text
; Parameter and value MUST match. ; Parameter and value MUST match.
param =/ type-param / pid-param / pref-param / any-param RELATED-param =/ type-param / pid-param / pref-param / any-param
type-param-related = "parent" / "child" / "sibling" / "manager" type-param-related = "parent" / "child" / "sibling" / "spouse"
/ "assistant" / "agent" / "emergency" / "family" / "friend" / "supervisor"
/ iana-token / x-name / "supervisee" / "assistant" / "colleague"
/ "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
skipping to change at page 40, line 28 skipping to change at page 41, line 43
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: ABNF:
param = "VALUE=text" / pid-param / pref-param / any-param CATEGORIES-param = "VALUE=text" / pid-param / pref-param
value = text-list / any-param
CATEGORIES-value = text-list
Example: Example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
7.7.2. NOTE 7.7.2. NOTE
Purpose: To specify supplemental information or a comment that is Purpose: To specify supplemental information or a comment that is
skipping to change at page 40, line 51 skipping to change at page 42, line 19
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property is based on the X.520 Description Special notes: The property is based on the X.520 Description
attribute. attribute.
ABNF: ABNF:
param = "VALUE=text" / language-param / pid-param / pref-param NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ any-param / any-param
value = text NOTE-value = text
Example: Example:
NOTE:This fax number is operational 0800 to 1715 NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri. EST\, Mon-Fri.
7.7.3. PRODID 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.
skipping to change at page 41, line 27 skipping to change at page 42, line 44
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: ABNF:
param = "VALUE=text" / any-param PRODID-param = "VALUE=text" / any-param
value = text PRODID-value = text
Example: Example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
7.7.4. REV 7.7.4. REV
Purpose: To specify revision information about the current vCard. Purpose: To specify revision information about the current vCard.
Value type: A single timestamp value. Value type: A single timestamp value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The value distinguishes the current revision of the Special notes: The value distinguishes the current revision of the
information in this vCard for other renditions of the information. information in this vCard for other renditions of the information.
ABNF: ABNF:
param = "VALUE=timestamp" / any-param REV-param = "VALUE=timestamp" / any-param
value = timestamp REV-value = timestamp
Example: Example:
REV:19951031T222710Z 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.
skipping to change at page 42, line 26 skipping to change at page 43, line 44
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: ABNF:
param = "VALUE=text" / any-param SORT-STRING-param = "VALUE=text" / any-param
value = text SORT-STRING-value = text
Examples: For the case of family name sorting, the following examples Examples: For the case of family name sorting, the following examples
define common sort string usage with the FN and N properties. define common sort string usage with the FN and N properties.
FN:Rene van der Harten FN:Rene van der Harten
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
skipping to change at page 43, line 31 skipping to change at page 45, line 5
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the audio format type. The TYPE parameter value MUST be specify the audio format type. The TYPE parameter value MUST be
an audio media type as specified in [RFC4288]. The full media an audio media type as specified in [RFC4288]. The full media
type name, including the "audio/" prefix, should be used. type name, including the "audio/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF: ABNF:
param = inline-param / refer-param SOUND-param = inline-param / refer-param
value = inline-value / refer-value SOUND-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
param =/ language-param / pid-param / pref-param / any-param SOUND-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 44, line 19 skipping to change at page 45, line 38
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: ABNF:
param = "VALUE=uri" / any-param UID-param = "VALUE=uri" / any-param
value = uri UID-value = uri
Example: Example:
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
7.7.8. CLIENTPIDMAP 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
skipping to change at page 45, line 7 skipping to change at page 46, line 23
on the usage of CLIENTPIDMAP. on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive. Zero is not PID source identifiers MUST be strictly positive. Zero is not
allowed. allowed.
As a special exception, the PID parameter MUST NOT be applied to As a special exception, the PID parameter MUST NOT be applied to
this property. this property.
ABNF: ABNF:
param = any-param CLIENTPIDMAP-param = any-param
value = 1*DIGIT ";" uri CLIENTPIDMAP-value = 1*DIGIT ";" uri
Example: Example:
TEL;PID=3.1,4.2:tel:+1-555-555-5555 TEL;PID=3.1,4.2:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5 CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
7.7.9. URL 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: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param URL-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri URL-value = uri
Example: Example:
URL:http://example.org/restaurant.french/~chezchic.html URL:http://example.org/restaurant.french/~chezchic.html
7.7.10. VERSION 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: ABNF:
param = "VALUE=text" / any-param VERSION-param = "VALUE=text" / any-param
value = "4.0" VERSION-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 46, line 40 skipping to change at page 48, line 14
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: ABNF:
param = "VALUE=text" / any-param CLASS-param = "VALUE=text" / any-param
value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token / x-name CLASS-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 47, line 30 skipping to change at page 49, line 5
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the public key or authentication certificate format. The specify the public key or authentication certificate format. The
TYPE parameter value MUST be a media type as specified in TYPE parameter value MUST be a media type as specified in
[RFC4288]. [RFC4288].
ABNF: ABNF:
param = inline-param / refer-param KEY-param = inline-param / refer-param
value = inline-value / refer-value KEY-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
param =/ pid-param / pref-param / any-param KEY-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...>
skipping to change at page 48, line 20 skipping to change at page 49, line 42
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: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param FBURL-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri FBURL-value = uri
Examples: Examples:
FBURL;PREF=1:http://www.example.com/busy/janedoe FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL:FTP://ftp.example.com/busy/project-a.ifb FBURL:FTP://ftp.example.com/busy/project-a.ifb
7.9.2. CALADRURI 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.
skipping to change at page 48, line 43 skipping to change at page 50, line 20
Value type: A single URI value. Value type: A single URI value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: Where multiple CALADRURI properties are specified, Special notes: Where multiple CALADRURI properties are specified,
the default CALADRURI property is indicated with the PREF the default CALADRURI property is indicated with the PREF
parameter. parameter.
ABNF: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param CALADRURI-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri CALADRURI-value = uri
Example: Example:
CALADRURI;PREF=1:mailto:janedoe@example.com CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe CALADRURI:http://example.com/calendar/jdoe
7.9.3. CALURI 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.
skipping to change at page 49, line 22 skipping to change at page 50, line 45
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: ABNF:
param = "VALUE=uri" / pid-param / pref-param / any-param CALURI-param = "VALUE=uri" / pid-param / pref-param / any-param
value = uri CALURI-value = uri
Examples: Examples:
CALURI;PREF=1:http://cal.example.com/calA CALURI;PREF=1:http://cal.example.com/calA
CALURI:ftp://ftp.example.com/calA.ics CALURI:ftp://ftp.example.com/calA.ics
7.10. Extended Properties and Parameters 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
skipping to change at page 55, line 12 skipping to change at page 56, line 14
example is merely intended to illustrate the possibility, which example is merely intended to illustrate the possibility, which
investigating would be, in the authors' opinion, worthwhile. investigating would be, in the authors' opinion, worthwhile.
9. Example: Authors' vCards 9. Example: Authors' vCards
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Simon Perreault FN:Simon Perreault
N:Perreault;Simon;;ing. jr,M.Sc. N:Perreault;Simon;;ing. jr,M.Sc.
BDAY:--0203 BDAY:--0203
GENDER:M ANNIVERSARY:20090808T1430-0500
SEX:1
LANG;PREF=1:fr LANG;PREF=1:fr
LANG;PREF=2:en LANG;PREF=2:en
WORK.ORG:Viagenie WORK.ORG:Viagenie
WORK.ADR:;Suite 625;2600 boul. Laurier; 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: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 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 SEX:1
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
10. 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,
skipping to change at page 56, line 43 skipping to change at page 57, line 47
11.2.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 registration of new value data types that modify existing
properties. A Standard Tracks RFC is also REQUIRED for registration properties. A Standard Tracks RFC is also REQUIRED for registration
of vCard elements that modify vCard elements previously documented in of vCard elements that modify vCard elements previously documented in
a Standard Tracks RFC. a Standard Tracks RFC.
The registration procedure begins when a completed registration The registration procedure begins when a completed registration
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
skipping to change at page 61, line 19 skipping to change at page 63, line 19
| NAME | Current | RFCXXXX, Section 7.1.4 | | NAME | Current | RFCXXXX, Section 7.1.4 |
| KIND | Current | RFCXXXX, Section 7.1.5 | | KIND | Current | RFCXXXX, Section 7.1.5 |
| FN | Current | RFCXXXX, Section 7.2.1 | | FN | Current | RFCXXXX, Section 7.2.1 |
| N | Current | RFCXXXX, Section 7.2.2 | | N | Current | RFCXXXX, Section 7.2.2 |
| NICKNAME | Current | RFCXXXX, Section 7.2.3 | | NICKNAME | Current | RFCXXXX, Section 7.2.3 |
| PHOTO | Current | RFCXXXX, Section 7.2.4 | | PHOTO | Current | RFCXXXX, Section 7.2.4 |
| BDAY | Current | RFCXXXX, Section 7.2.5 | | BDAY | Current | RFCXXXX, Section 7.2.5 |
| DDAY | Current | RFCXXXX, Section 7.2.6 | | DDAY | Current | RFCXXXX, Section 7.2.6 |
| BIRTH | Current | RFCXXXX, Section 7.2.7 | | BIRTH | Current | RFCXXXX, Section 7.2.7 |
| DEATH | Current | RFCXXXX, Section 7.2.8 | | DEATH | Current | RFCXXXX, Section 7.2.8 |
| GENDER | Current | RFCXXXX, Section 7.2.9 | | ANNIVERSARY | Current | RFCXXXX, Section 7.2.9 |
| SEX | Current | RFCXXXX, Section 7.2.10 |
| ADR | Current | RFCXXXX, Section 7.3.1 | | ADR | Current | RFCXXXX, Section 7.3.1 |
| LABEL | Current | RFCXXXX, Section 7.3.2 | | LABEL | Current | RFCXXXX, Section 7.3.2 |
| TEL | Current | RFCXXXX, Section 7.4.1 | | TEL | Current | RFCXXXX, Section 7.4.1 |
| EMAIL | Current | RFCXXXX, Section 7.4.2 | | EMAIL | Current | RFCXXXX, Section 7.4.2 |
| IMPP | Current | RFCXXXX, Section 7.4.3 | | IMPP | Current | RFCXXXX, Section 7.4.3 |
| LANG | Current | RFCXXXX, Section 7.4.4 | | LANG | Current | RFCXXXX, Section 7.4.4 |
| TZ | Current | RFCXXXX, Section 7.5.1 | | TZ | Current | RFCXXXX, Section 7.5.1 |
| GEO | Current | RFCXXXX, Section 7.5.2 | | GEO | Current | RFCXXXX, Section 7.5.2 |
| TITLE | Current | RFCXXXX, Section 7.6.1 | | TITLE | Current | RFCXXXX, Section 7.6.1 |
| ROLE | Current | RFCXXXX, Section 7.6.2 | | ROLE | Current | RFCXXXX, Section 7.6.2 |
skipping to change at page 62, line 28 skipping to change at page 64, line 28
| TYPE | Current | RFCXXXX, Section 6.6 | | TYPE | Current | RFCXXXX, Section 6.6 |
| GEO | Current | RFCXXXX, Section 7.3.1 | | GEO | Current | RFCXXXX, Section 7.3.1 |
| TZ | Current | RFCXXXX, Section 7.3.1 | | TZ | Current | RFCXXXX, Section 7.3.1 |
+-----------+---------+------------------------+ +-----------+---------+------------------------+
11.3.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.1 | | DATE | Current | RFCXXXX, Section 5.3.1 |
| TIME | Current | RFCXXXX, Section 5.3.2 | | TIME | Current | RFCXXXX, Section 5.3.2 |
| DATE-TIME | Current | RFCXXXX, Section 5.3.3 | | DATE-TIME | Current | RFCXXXX, Section 5.3.3 |
| TIMESTAMP | Current | RFCXXXX, Section 5.3.4 | | DATE-AND-OR-TIME | Current | RFCXXXX, Section 5.3.4 |
| TIMESTAMP | Current | RFCXXXX, Section 5.3.5 |
| 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.8 |
+-----------------+---------+------------------------+ +------------------+---------+------------------------+
11.3.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 |
| END | VCARD | Current | RFCXXXX, Section 7.1.2 | | END | VCARD | Current | RFCXXXX, Section 7.1.2 |
| KIND | individual | Current | RFCXXXX, Section 7.1.5 | | KIND | individual | Current | RFCXXXX, Section 7.1.5 |
| KIND | group | Current | RFCXXXX, Section 7.1.5 | | KIND | group | Current | RFCXXXX, Section 7.1.5 |
| KIND | org | Current | RFCXXXX, Section 7.1.5 | | KIND | org | Current | RFCXXXX, Section 7.1.5 |
| KIND | location | Current | RFCXXXX, Section 7.1.5 | | KIND | location | Current | RFCXXXX, Section 7.1.5 |
| GENDER | M | Current | RFCXXXX, Section 7.2.9 |
| GENDER | F | Current | RFCXXXX, Section 7.2.9 |
| CLASS | PUBLIC | Current | RFCXXXX, Section 7.8.1 | | CLASS | PUBLIC | Current | RFCXXXX, Section 7.8.1 |
| CLASS | PRIVATE | Current | RFCXXXX, Section 7.8.1 | | CLASS | PRIVATE | Current | RFCXXXX, Section 7.8.1 |
| CLASS | CONFIDENTIAL | Current | RFCXXXX, Section 7.8.1 | | CLASS | CONFIDENTIAL | Current | RFCXXXX, Section 7.8.1 |
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
The following table is to be used to initialize the parameter values The following table is to be used to initialize the parameter values
registry. registry.
+----------+-----------+-----------+---------+----------------------+ +----------+-----------+------------+---------+---------------------+
| Property | Parameter | Value | Status | Reference | | Property | Parameter | Value | Status | Reference |
+----------+-----------+-----------+---------+----------------------+ +----------+-----------+------------+---------+---------------------+
| TEL | TYPE | text | Current | RFCXXXX, | | TEL | TYPE | text | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 7.4.1 |
| TEL | TYPE | voice | Current | RFCXXXX, | | TEL | TYPE | voice | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 7.4.1 |
| TEL | TYPE | fax | Current | RFCXXXX, | | TEL | TYPE | fax | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 7.4.1 |
| TEL | TYPE | cell | Current | RFCXXXX, | | TEL | TYPE | cell | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 7.4.1 |
| TEL | TYPE | video | Current | RFCXXXX, | | TEL | TYPE | video | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 7.4.1 |
| TEL | TYPE | pager | Current | RFCXXXX, | | TEL | TYPE | pager | Current | RFCXXXX, |
| | | | | Section 7.4.1 | | | | | | Section 7.4.1 |
| RELATED | TYPE | parent | Current | RFCXXXX, | | RELATED | TYPE | parent | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 7.6.6 |
| RELATED | TYPE | child | Current | RFCXXXX, | | RELATED | TYPE | child | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 7.6.6 |
| 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 | spouse | Current | RFCXXXX, |
| | | | | Section 7.6.6 |
| RELATED | TYPE | family | Current | RFCXXXX, |
| | | | | Section 7.6.6 |
| RELATED | TYPE | friend | Current | RFCXXXX, |
| | | | | Section 7.6.6 |
| RELATED | TYPE | supervisor | Current | RFCXXXX, |
| | | | | Section 7.6.6 |
| RELATED | TYPE | supervisee | 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 | colleague | Current | RFCXXXX, |
| | | | | Section 7.6.6 |
| RELATED | TYPE | agent | Current | RFCXXXX, | | RELATED | TYPE | agent | Current | RFCXXXX, |
| | | | | Section 7.6.6 | | | | | | Section 7.6.6 |
+----------+-----------+-----------+---------+----------------------+ | RELATED | TYPE | emergency | Current | RFCXXXX, |
| | | | | Section 7.6.6 |
+----------+-----------+------------+---------+---------------------+
12. Acknowledgements 12. Acknowledgements
The authors would like to thank Tim Howes, Mark Smith, and Frank The authors would like to thank Tim Howes, Mark Smith, and Frank
Dawson, the original authors of [RFC2425] and [RFC2426], as well as Dawson, the original authors of [RFC2425] and [RFC2426], as well as
the following individuals who have participated in the drafting, the following individuals who have participated in the drafting,
review and discussion of this memo: review and discussion of this memo:
Marc Blanchet, Stephane Bortzmeyer, Dan Brickley, Chris Bryant, Dany (needs to be updated) Marc Blanchet, Stephane Bortzmeyer, Dan
Cauchie, Darryl Champagne, Cyrus Daboo, Bernard Desruisseaux, Lisa Brickley, Chris Bryant, Dany Cauchie, Darryl Champagne, Cyrus Daboo,
Dusseault, Javier Godoy, Helge Hess, Alexander Mayrhofer, Chris Bernard Desruisseaux, Lisa Dusseault, Javier Godoy, Sly Gryphon,
Newman, Mark Paterson, Julian Reschke, Peter K. Sheerin, Anil Helge Hess, Renato Iannella, Alexander Mayrhofer, Chris Newman, Mark
Srivastava, and Kurt Zeilenga. Paterson, Julian Reschke, Peter K. Sheerin, Anil Srivastava, and Kurt
Zeilenga.
13. References 13. References
13.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.
skipping to change at page 64, line 51 skipping to change at page 67, line 13
"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.
[I-D.mayrhofer-geo-uri] Mayrhofer, A. and C. Spanring, "A Uniform [I-D.mayrhofer-geo-uri] Mayrhofer, A. and C. Spanring, "A Uniform
Resource Identifier for Geographic Areas Resource Identifier for Geographic Areas
('geo' URI)", draft-mayrhofer-geo-uri-02 ('geo' URI)", draft-mayrhofer-geo-uri-02
(work in progress), February 2008. (work in progress), February 2008.
[ISO.5218.2004] International Organization for
Standardization, "Information Technology -
Codes for the representation of human
sexes", ISO Standard 5218, December 2004.
[ISO.8601.2000] International Organization for [ISO.8601.2000] International Organization for
Standardization, "Data elements and Standardization, "Data elements and
interchange formats - Information interchange formats - Information
interchange - Representation of dates and interchange - Representation of dates and
times", ISO Standard 8601, December 2000. times", ISO Standard 8601, December 2000.
[ISO.8601.2004] International Organization for [ISO.8601.2004] International Organization for
Standardization, "Data elements and Standardization, "Data elements and
interchange formats - Information interchange formats - Information
interchange - Representation of dates and interchange - Representation of dates and
skipping to change at page 66, line 47 skipping to change at page 69, line 18
Standardization, "ISO 9070, Information Standardization, "ISO 9070, Information
Processing - SGML support facilities - Processing - SGML support facilities -
Registration Procedures for Public Text Registration Procedures for Public Text
Owner Identifiers", April 1991. Owner Identifiers", April 1991.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and [RFC3406] Daigle, L., van Gulik, D., Iannella, R., 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.
[TZ-DB] Olson, A., "Time zone code and data",
<ftp://elsie.nci.nih.gov/pub/>.
URIs URIs
[1] <mailto:vcard@ietf.org> [1] <mailto:vcard@ietf.org>
[2] <mailto:iana@iana.org> [2] <mailto:iana@iana.org>
Appendix A. Differences from RFCs 2425 and 2426 Appendix A. Differences from RFCs 2425 and 2426
This appendix contains a list of changes that have been made in the This appendix contains a list of changes that have been made in the
vCard specification from RFCs 2425 and 2426. vCard specification from RFCs 2425 and 2426.
skipping to change at page 67, line 23 skipping to change at page 69, line 45
intended to be extensible but only 2426 ever extended it. intended to be extensible but only 2426 ever extended it.
o vCard is now not only a MIME type but a stand-alone format. o vCard is now not only a MIME type but a stand-alone format.
o A proper MIME type registration form has been included. o A proper MIME type registration form has been included.
o UTF-8 is now the default character set. o UTF-8 is now the default character set.
o New vCard elements can be registered from IANA. o New vCard elements can be registered from IANA.
o Changed "manager" to "supervisor".
o Added "family", "supervisee", and "colleague" RELATED types.
A.2. Removed Features A.2. Removed Features
o The group construct (i.e. GROUP.PROPERTY:...) no longer exists. o The group construct (i.e. GROUP.PROPERTY:...) no longer exists.
o The CONTEXT and CHARSET parameters are no more. o The CONTEXT and CHARSET parameters are no more.
o The MAILER property is no more. o The MAILER property is no more.
o The "intl", "dom", "postal", and "parcel" TYPE parameter values o The "intl", "dom", "postal", and "parcel" TYPE parameter values
for the ADR and LABEL properties have been removed. for the ADR and LABEL properties have been removed.
o Inline vCards (such as the value of the AGENT property) are no o Inline vCards (such as the value of the AGENT property) are no
longer supported. longer supported.
o In the N property, additional names are now subsumed into the o In the N property, additional names are now subsumed into the
given names list. given names list.
A.3. New Properties and Parameters A.3. New Properties and Parameters
o The KIND, GENDER, LANG, DDAY, BIRTH, and DEATH properties have o The KIND, SEX, LANG, DDAY, BIRTH, and DEATH properties have been
been added. added.
o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI
properties, has been merged in. properties, has been merged in.
o [RFC4770], which defines the IMPP property, has been merged in. o [RFC4770], which defines the IMPP property, has been merged in.
o The "work", "home", and "uri" TYPE parameter values for the EMAIL o The "work", "home", and "uri" TYPE parameter values for the EMAIL
property have been added. property have been added.
o The "pref" value of the TYPE parameter is now a parameter of its o The "pref" value of the TYPE parameter is now a parameter of its
skipping to change at page 68, line 25 skipping to change at page 71, line 8
o The value of TEL is now a URI. o The value of TEL is now a URI.
o The AGENT property was replaced with a type of RELATED. o The AGENT property was replaced with a type of RELATED.
o Date and time values now only support the basic format. o Date and time values now only support the basic format.
Truncation is now supported. Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -07 B.1. Changes in -08
o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to
properties with the property name.
o Replaced the GENDER property with the SEX property.
o Added the ANNIVERSARY property.
o Added the "friend" and "spouse" types of RELATED.
o TZ property now has text / uri value.
o Refined the definitions of TITLE and ROLE.
B.2. Changes in -07
o PREF is now bounded. 100 is the maximum value. o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type. o Added the "emergency" RELATED type.
o Made GEO a URI. o Made GEO a URI.
o Added GEO and TZ parameters to ADR. o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property. o Changed wording of "default" use of SOUND property.
skipping to change at page 68, line 47 skipping to change at page 72, line 5
o Completely reworked the date, time, and date-time grammars. o Completely reworked the date, time, and date-time grammars.
o Added the timestamp value type. o Added the timestamp value type.
o REV now has the timestamp value type. o REV now has the timestamp value type.
o Rewrote ABNF. o Rewrote ABNF.
o ORG can now have a single level. o ORG can now have a single level.
B.2. Changes in -06 B.3. 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 69, line 38 skipping to change at page 72, line 44
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.3. Changes in -05 B.4. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.4. Changes in -04 B.5. 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 70, line 24 skipping to change at page 73, line 31
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.5. Changes in -03 B.6. 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.6. Changes in -02 B.7. 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 71, line 14 skipping to change at page 74, line 23
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.7. Changes in -01 B.8. 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 71, line 42 skipping to change at page 75, line 5
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.8. Changes in -00 B.9. 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. 139 change blocks. 
290 lines changed or deleted 397 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/