draft-ietf-vcarddav-vcardrev-19.txt   draft-ietf-vcarddav-vcardrev-20.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 April 9, 2011 Obsoletes: 2425, 2426, 4770 May 20, 2011
(if approved) (if approved)
Updates: 2739 (if approved) Updates: 2739 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: October 11, 2011 Expires: November 21, 2011
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-19 draft-ietf-vcarddav-vcardrev-20
Abstract Abstract
This document defines the vCard data format for representing and This document defines the vCard data format for representing and
exchanging a variety of information about individuals and other exchanging a variety of information about individuals and other
entities (e.g., formatted and structured name and delivery addresses, entities (e.g., formatted and structured name and delivery addresses,
email address, multiple telephone numbers, photograph, logo, audio email address, multiple telephone numbers, photograph, logo, audio
clips, etc.). This document obsoletes RFCs 2425, 2426, 2739, and clips, etc.). This document obsoletes RFCs 2425, 2426, 2739, and
4770. 4770.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 11, 2011. This Internet-Draft will expire on November 21, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. vCard Format Specification . . . . . . . . . . . . . . . . . . 6 3. vCard Format Specification . . . . . . . . . . . . . . . . . . 6
3.1. Character Set . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Charset . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 6 3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 6
3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7 3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7
3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 9 3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 9
4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10 4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10
4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 13 4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 13
4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 14 4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 14
4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14 4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14
4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 15 4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 15
4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.7. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16 4.7. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 16
4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16
5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16 5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16
5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.2. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.4. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.7. MEDIATYPE . . . . . . . . . . . . . . . . . . . . . . . . 21 5.7. MEDIATYPE . . . . . . . . . . . . . . . . . . . . . . . . 21
5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 23 6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. General Properties . . . . . . . . . . . . . . . . . . . . 23 6.1. General Properties . . . . . . . . . . . . . . . . . . . . 24
6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2. Identification Properties . . . . . . . . . . . . . . . . 28 6.2. Identification Properties . . . . . . . . . . . . . . . . 29
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 31 6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 32 6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 32
6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 32 6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 33
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 33 6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 34
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4. Communications Properties . . . . . . . . . . . . . . . . 34 6.4. Communications Properties . . . . . . . . . . . . . . . . 35
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 36 6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 37
6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.5. Geographical Properties . . . . . . . . . . . . . . . . . 38 6.5. Geographical Properties . . . . . . . . . . . . . . . . . 39
6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6. Organizational Properties . . . . . . . . . . . . . . . . 39 6.6. Organizational Properties . . . . . . . . . . . . . . . . 40
6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 39 6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 42 6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 43
6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 43 6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 44
6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 44 6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 45
6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 44 6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 45
6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 45 6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 45 6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 46 6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 47 6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 47 6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 48
6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 48 6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 49 6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 50
6.8. Security Properties . . . . . . . . . . . . . . . . . . . 49 6.8. Security Properties . . . . . . . . . . . . . . . . . . . 50
6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 49 6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 50
6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 50 6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 51
6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 51 6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 51
6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 51 6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 52
6.10. Extended Properties and Parameters . . . . . . . . . . . . 52 6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 52
7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 52 6.10. Extended Properties and Parameters . . . . . . . . . . . . 53
7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 52 7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 53
7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 52 7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 53
7.1.2. Matching Property Instances . . . . . . . . . . . . . 53 7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 53
7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 53 7.1.2. Matching Property Instances . . . . . . . . . . . . . 54
7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 54 7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 54
7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 54 7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 54 7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 55 7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 55
7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 55 7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 56
7.2.5. Global Context Simplification . . . . . . . . . . . . 57 7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 56
8. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 58 7.2.5. Global Context Simplification . . . . . . . . . . . . 58
9. Security Considerations . . . . . . . . . . . . . . . . . . . 58 8. Example: Author's vCard . . . . . . . . . . . . . . . . . . . 59
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59 9. Security Considerations . . . . . . . . . . . . . . . . . . . 59
10.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 59 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60
10.2. Registering New vCard Elements . . . . . . . . . . . . . . 60 10.1. Media Type Registration . . . . . . . . . . . . . . . . . 60
10.2. Registering New vCard Elements . . . . . . . . . . . . . . 61
10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 61 10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 61
10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 61 10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 62
10.2.3. Registration Template for Properties . . . . . . . . . 62 10.2.3. Registration Template for Properties . . . . . . . . . 63
10.2.4. Registration Template for Parameters . . . . . . . . . 63 10.2.4. Registration Template for Parameters . . . . . . . . . 63
10.2.5. Registration Template for Value Data Types . . . . . . 63 10.2.5. Registration Template for Value Data Types . . . . . . 64
10.2.6. Registration Template for Values . . . . . . . . . . . 63 10.2.6. Registration Template for Values . . . . . . . . . . . 64
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 64 10.3. Initial vCard Elements Registries . . . . . . . . . . . . 65
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 64 10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 65
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 65 10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 66
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 66 10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 67
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 66 10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 67
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69 12.1. Normative References . . . . . . . . . . . . . . . . . . . 70
12.2. Informative References . . . . . . . . . . . . . . . . . . 72 12.2. Informative References . . . . . . . . . . . . . . . . . . 73
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 75
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 74 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 75
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 74 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 75
A.3. New Properties and Parameters . . . . . . . . . . . . . . 74 A.3. New Properties and Parameters . . . . . . . . . . . . . . 75
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 75 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 76
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) . . . . . . . . . . . . . . . . . . . . 75 publication) . . . . . . . . . . . . . . . . . . . . 76
B.1. Changes in -19 . . . . . . . . . . . . . . . . . . . . . . 75 B.1. Changes in -20 . . . . . . . . . . . . . . . . . . . . . . 76
B.2. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 75 B.2. Changes in -19 . . . . . . . . . . . . . . . . . . . . . . 77
B.3. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 75 B.3. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 77
B.4. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 76 B.4. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 77
B.5. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 76 B.5. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 78
B.6. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 77 B.6. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 78
B.7. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 78 B.7. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 79
B.8. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 78 B.8. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 80
B.9. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 79 B.9. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 80
B.10. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 80 B.10. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 81
B.11. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 80 B.11. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 82
B.12. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 80 B.12. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 82
B.13. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 81 B.13. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 82
B.14. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 81 B.14. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 83
B.15. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 82 B.15. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 83
B.16. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 82 B.16. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 84
B.17. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 83 B.17. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 84
B.18. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 83 B.18. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 85
B.19. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 84 B.19. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 85
B.20. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 84 B.20. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 86
B.21. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 86
1. Introduction 1. Introduction
Electronic address books have become ubiquitous. Their increased Electronic address books have become ubiquitous. Their increased
presence on portable, connected devices as well as the diversity of presence on portable, connected devices as well as the diversity of
platforms exchanging contact data call for a standard. This memo platforms exchanging contact data call for a standard. This memo
defines the vCard format, which allows the capture and exchange of defines the vCard format, which allows the capture and exchange of
information normally stored within an address book or directory information normally stored within an address book or directory
application. application.
skipping to change at page 6, line 28 skipping to change at page 6, line 28
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
3. vCard Format Specification 3. vCard Format Specification
The text/vcard MIME content type (hereafter known as "vCard", see The text/vcard MIME content type (hereafter known as "vCard", see
Section 10.1) contains contact information, typically pertaining to a Section 10.1) contains contact information, typically pertaining to a
single contact or group of contacts. The content consists of one or single contact or group of contacts. The content consists of one or
more lines in the format given below. more lines in the format given below.
3.1. Character Set 3.1. Charset
The character set for vCard is UTF-8 as defined in [RFC3629]. There The charset (see [RFC3536] for internationalization terminology) for
is no way to override this. It is invalid to specify a different vCard is UTF-8 as defined in [RFC3629]. There is no way to override
character set in the "charset" MIME parameter (see Section 10.1). this. It is invalid to specify a value other than "UTF-8" in the
"charset" MIME parameter (see Section 10.1).
3.2. Line Delimiting and Folding 3.2. Line Delimiting and Folding
Individual lines within vCard are delimited by the [RFC5322] line Individual lines within vCard are delimited by the [RFC5322] line
break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII
decimal 10). Long logical lines of text can be split into a decimal 10). Long logical lines of text can be split into a
multiple-physical-line representation using the following folding multiple-physical-line representation using the following folding
technique. Content lines SHOULD be folded to a maximum width of 75 technique. Content lines SHOULD be folded to a maximum width of 75
octets, excluding the line break. Multi-octet characters MUST remain octets, excluding the line break. Multi-octet characters MUST remain
contiguous. The rationale for this folding process can be found in contiguous. The rationale for this folding process can be found in
skipping to change at page 8, line 5 skipping to change at page 8, line 5
vcard = "BEGIN:VCARD" CRLF vcard = "BEGIN:VCARD" CRLF
"VERSION:4.0" CRLF "VERSION:4.0" CRLF
1*contentline 1*contentline
"END:VCARD" CRLF "END:VCARD" CRLF
; A vCard object MUST include the VERSION and FN properties. ; A vCard object MUST include the VERSION and FN properties.
; VERSION MUST come immediately after BEGIN:VCARD. ; VERSION MUST come immediately after BEGIN:VCARD.
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 in section 3.2.
; 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 in section 3.2.
group = 1*(ALPHA / DIGIT / "-") group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME" name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL" / "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
/ "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE" / "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
/ "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES" / "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
/ "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP" / "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
/ "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML" / "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ iana-token / x-name / 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
skipping to change at page 9, line 4 skipping to change at page 9, line 4
QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE ; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":" ; Any character except CTLs, DQUOTE, ";", ":"
VALUE-CHAR = WSP / VCHAR / NON-ASCII VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character ; Any textual character
A line that begins with a white space character is a continuation of A line that begins with a white space character is a continuation of
the previous line, as described above. The white space character and the previous line, as described in Section 3.2. The white space
immediately preceeding CRLF should be discarded when reconstructing character and immediately preceeding CRLF should be discarded when
the original line. Note that this line-folding convention differs reconstructing the original line. Note that this line-folding
from that found in [RFC5322], in that the sequence <CRLF><WSP> found convention differs from that found in [RFC5322], in that the sequence
anywhere in the content indicates a continued line and should be <CRLF><WSP> found anywhere in the content indicates a continued line
removed. and should be removed.
Property names and parameter names are case insensitive (e.g., the Property names and parameter names are case insensitive (e.g., the
property name "fn" is the same as "FN" and "Fn"). Parameter values property name "fn" is the same as "FN" and "Fn"). Parameter values
MAY be case sensitive or case insensitive, depending on their MAY be case-sensitive or case-insensitive, depending on their
definition. Based on experience with vCard 3 interoperability, it is definition. Parameter values that are not explicitly defined as
RECOMMENDED that property and parameter names be upper-case on being case-sensitive are case-insenstive. Based on experience with
output. vCard 3 interoperability, it is RECOMMENDED that property and
parameter names be upper-case on output.
The group construct is used to group related properties together. The group construct is used to group related properties together.
The group name is a syntactic convention used to indicate that all The group name is a syntactic convention used to indicate that all
property names prefaced with the same group name SHOULD be grouped property names prefaced with the same group name SHOULD be grouped
together when displayed by an application. It has no other together when displayed by an application. It has no other
significance. Implementations that do not understand or support significance. Implementations that do not understand or support
grouping MAY simply strip off any text before a "." to the left of grouping MAY simply strip off any text before a "." to the left of
the type name and present the types and values as normal. the type name and present the types and values as normal.
Property cardinalities are indicated using the following notation, Property cardinalities are indicated using the following notation,
skipping to change at page 10, line 24 skipping to change at page 10, line 25
Furthermore, some fields of compound properties may contain a list of Furthermore, some fields of compound properties may contain a list of
values delimited by a COMMA character. Therefore, a COMMA character values delimited by a COMMA character. Therefore, a COMMA character
in one of a field's values MUST be escaped with a BACKSLASH in one of a field's values MUST be escaped with a BACKSLASH
character, even for fields that don't allow multiple values (for character, even for fields that don't allow multiple values (for
consistency). Compound properties allowing multiple instances MUST consistency). Compound properties allowing multiple instances MUST
NOT be encoded in a single content line. NOT be encoded in a single content line.
Finally, BACKSLASH characters in values MUST be escaped with a Finally, BACKSLASH characters in values MUST be escaped with a
BACKSLASH character. NEWLINE (ASCII decimal 10) characters in values BACKSLASH character. NEWLINE (ASCII decimal 10) characters in values
MUST be encoded by two characters: a BACKSLASH followed by an 'n' MUST be encoded by two characters: a BACKSLASH followed by either an
(ASCII decimal 110). 'n' (ASCII decimal 110) or an 'N' (ASCII decimal 78).
In all other cases, escaping MUST NOT be used. In all other cases, escaping MUST NOT be used.
4. Property Value Data Types 4. Property Value Data Types
Standard value types are defined below. Standard value types are defined below.
value = text value = text
/ text-list / text-list
/ date-list / date-list
/ time-list / time-list
/ date-time-list / date-time-list
/ date-and-or-time-list / date-and-or-time-list
/ timestamp-list / timestamp-list
/ boolean / boolean
/ integer-list / integer-list
/ float-list / float-list
/ URI ; from Section 3 of [RFC3986] / URI ; from Section 3 of [RFC3986]
/ utc-offset
/ Language-Tag
/ 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 = *TEXT-CHAR text = *TEXT-CHAR
TEXT-CHAR = "\\" / "\," / "\n" TEXT-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \> / <any VALUE-CHAR except , or \>
; Backslashes, commas, and newlines must be encoded. ; Backslashes, commas, and newlines must be encoded.
component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E / %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
list-component = component *("," component) list-component = component *("," component)
text-list = text *("," text) text-list = text *("," text)
date-list = date *("," date) date-list = date *("," date)
skipping to change at page 12, line 48 skipping to change at page 13, line 8
NOTE:Mythical Manager\nHyjinx Software Division\n NOTE:Mythical Manager\nHyjinx Software Division\n
BabsCo\, Inc.\n BabsCo\, Inc.\n
demonstrating the \n literal formatted line break technique, the demonstrating the \n literal formatted line break technique, the
CRLF-followed-by-space line folding technique, and the backslash CRLF-followed-by-space line folding technique, and the backslash
escape technique. escape technique.
4.2. URI 4.2. URI
"uri": The "uri" value type should be used to identify values that "uri": The "uri" value type should be used to identify values that
are referenced by a URI (including a Content-ID URI), instead of are referenced by a Uniform Resource Identifier (URI) instead of
encoded in-line. These value references might be used if the value encoded in-line. These value references might be used if the value
is too large, or otherwise undesirable to include directly. The is too large, or otherwise undesirable to include directly. The
format for the URI is as defined in Section 3 of [RFC3986]. Note format for the URI is as defined in Section 3 of [RFC3986]. Note
that the value of a property of type "uri" is what the URI points to, that the value of a property of type "uri" is what the URI points to,
not the URI itself. not the URI 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
skipping to change at page 15, line 51 skipping to change at page 15, line 51
TRUE TRUE
false false
True True
4.5. INTEGER 4.5. INTEGER
"integer": The "integer" value type is used to express signed "integer": The "integer" value type is used to express signed
integers in decimal format. If sign is not specified, the value is integers in decimal format. If sign is not specified, the value is
assumed positive "+". Multiple "integer" values can be specified assumed positive "+". Multiple "integer" values can be specified
using the comma-separated notation. using the comma-separated notation. The maximum value is
9223372036854775807 and the minimum value is -9223372036854775808.
These limits correspond to a signed 64-bit integer using two's-
complement arithmetic.
Examples: Examples:
1234567890 1234567890
-1234556790 -1234556790
+1234556790,432109876 +1234556790,432109876
4.6. FLOAT 4.6. FLOAT
"float": The "float" value type is used to express real numbers. If "float": The "float" value type is used to express real numbers. If
sign is not specified, the value is assumed positive "+". Multiple sign is not specified, the value is assumed positive "+". Multiple
"float" values can be specified using the comma-separated notation. "float" values can be specified using the comma-separated notation.
Implementations MUST support a precision equal or better than that of
the IEEE "binary64" format [IEEE.754.2008].
Note: Scientific notation is disallowed. Implementors wishing to Note: Scientific notation is disallowed. Implementors wishing to
use their favorite language's %f formatting should be careful. use their favorite language's %f formatting should be careful.
Examples: Examples:
20.30 20.30
1000000.0000001 1000000.0000001
1.333,3.14 1.333,3.14
4.7. LANGUAGE-TAG 4.7. UTC-OFFSET
"utc-offset": The "utc-offset" value type specifies that the property
value is a signed offset from UTC. This value type can be specified
in the TZ property.
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.
4.8. LANGUAGE-TAG
"language-tag": A single language tag, as defined in [RFC5646]. "language-tag": A single language tag, as defined in [RFC5646].
5. Property Parameters 5. Property Parameters
A property can have attributes associated with it. These "property A property can have attributes associated with it. These "property
parameters" contain meta-information about the property or the parameters" contain meta-information about the property or the
property value. In some cases the property parameter can be multi- property value. In some cases the property parameter can be multi-
valued in which case the property parameter value elements are valued in which case the property parameter value elements are
separated by a COMMA (US-ASCII decimal 44). separated by a COMMA (US-ASCII decimal 44).
skipping to change at page 17, line 37 skipping to change at page 18, line 14
ABNF: ABNF:
value-param = "VALUE=" value-type value-param = "VALUE=" value-type
value-type = "text" value-type = "text"
/ "uri" / "uri"
/ "date" / "date"
/ "time" / "time"
/ "date-time" / "date-time"
/ "date-and-or-time"
/ "timestamp" / "timestamp"
/ "boolean" / "boolean"
/ "integer" / "integer"
/ "float" / "float"
/ "language-tag"
/ "utc-offset" / "utc-offset"
/ "language-tag"
/ iana-token ; registered as described in section 12 / iana-token ; registered as described in section 12
/ x-name / x-name
5.3. PREF 5.3. 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 preference. Lower values correspond to a quantifies the level of preference. Lower values correspond to a
higher level of preference, 1 being most preferred. higher level of preference, 1 being most preferred.
skipping to change at page 21, line 9 skipping to change at page 21, line 29
type-param = "TYPE=" type-value *("," type-value) type-param = "TYPE=" type-value *("," type-value)
type-value = "work" / "home" / type-param-tel type-value = "work" / "home" / type-param-tel
/ type-param-related / iana-token / x-name / type-param-related / iana-token / x-name
; This is further defined in individual property sections. ; This is further defined in individual property sections.
5.7. MEDIATYPE 5.7. MEDIATYPE
The MEDIATYPE parameter is used with properties whose value is a URI. The MEDIATYPE parameter is used with properties whose value is a URI.
Its use is OPTIONAL. It provides a hint to the vCard consumer Its use is OPTIONAL. It provides a hint to the vCard consumer
application about the media type of the resource identified by the application about the media type [RFC2046] of the resource identified
URI. Some URI schemes do not need this parameter. For example, the by the URI. Some URI schemes do not need this parameter. For
"data" scheme allows the media type to be explicitly indicated as example, the "data" scheme allows the media type to be explicitly
part of the URI [RFC2397]. Another scheme, "http", provides the indicated as part of the URI [RFC2397]. Another scheme, "http",
media type as part of the URI resolution process, with the Content- provides the media type as part of the URI resolution process, with
Type HTTP header [RFC2616]. The MEDIATYPE parameter is intended to the Content-Type HTTP header [RFC2616]. The MEDIATYPE parameter is
be used with URI schemes that do not provide such functionality (e.g. intended to be used with URI schemes that do not provide such
"ftp" [RFC1738]). functionality (e.g. "ftp" [RFC1738]).
ABNF: ABNF:
mediatype-param = "MEDIATYPE=" mediatype mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value ) mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "attribute" and "value" are from [RFC2045] ; "attribute" and "value" are from [RFC2045]
; "type-name" and "subtype-name" are from [RFC4288] ; "type-name" and "subtype-name" are from [RFC4288]
5.8. CALSCALE 5.8. CALSCALE
skipping to change at page 21, line 52 skipping to change at page 22, line 24
5.9. SORT-AS 5.9. SORT-AS
The "sort-as" parameter is used to specify the string to be used for The "sort-as" parameter is used to specify the string to be used for
national-language-specific sorting. Without this information, national-language-specific sorting. Without this information,
sorting algorithms could incorrectly sort this vCard within a sorting algorithms could incorrectly sort this vCard within a
sequence of sorted vCards. When this property is present in a vCard, sequence of sorted vCards. When this property is present in a vCard,
then the given strings are used for sorting the vCard. then the given strings are used for sorting the vCard.
This parameter's value is a comma-separated list which MUST have as This parameter's value is a comma-separated list which MUST have as
many or less elements as the corresponding property value has many or fewer elements as the corresponding property value has
components. components. This parameter's value is case-sensitive.
ABNF: ABNF:
sort-as-param = "SORT-AS=" sort-as-value sort-as-param = "SORT-AS=" sort-as-value
sort-as-value = param-value *("," param-value) sort-as-value = param-value *("," param-value)
Examples: For the case of surname and given name sorting, the Examples: For the case of surname and given name sorting, the
following examples define common sort string usage with the N following examples define common sort string usage with the N
property. property.
skipping to change at page 23, line 45 skipping to change at page 24, line 35
Value type: text Value type: text
Cardinality: 1 Cardinality: 1
Special notes: The content entity MUST begin with the BEGIN property Special notes: The content entity MUST begin with the BEGIN property
with a value of "VCARD". The value is case-insensitive. with a value of "VCARD". The value is case-insensitive.
The BEGIN property is used in conjunction with the END property to The BEGIN property is used in conjunction with the END property to
delimit an entity containing a related set of properties within an delimit an entity containing a related set of properties within an
text/vcard content-type. This construct can be used instead of or text/vcard content-type. This construct can be used instead of
in addition to wrapping separate sets of information inside including multiple vCards as body parts inside of a multipart/
additional MIME headers. It is provided for applications that alternative MIME message. 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:
BEGIN-param = 0<nothing> ; no parameter allowed BEGIN-param = 0<nothing> ; no parameter allowed
BEGIN-value = "VCARD" BEGIN-value = "VCARD"
Example: Example:
skipping to change at page 31, line 12 skipping to change at page 31, line 46
Purpose: To specify an image or photograph information that Purpose: To specify an image or photograph information that
annotates some aspect of the object the vCard represents. annotates some aspect of the object the vCard represents.
Value type: A single URI. Value type: A single URI.
Cardinality: * Cardinality: *
ABNF: ABNF:
PHOTO-param = "VALUE=uri" / altid-param / type-param PHOTO-param = "VALUE=uri" / altid-param / type-param
/ mediatype-param / mediatype-param / pref-param / pid-param / any-param
PHOTO-value = URI PHOTO-value = URI
Examples: Examples:
PHOTO:http://www.example.com/pub/photos/jqpublic.gif PHOTO:http://www.example.com/pub/photos/jqpublic.gif
PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of base64-encoded data...> <...remainder of base64-encoded data...>
skipping to change at page 33, line 33 skipping to change at page 34, line 30
vCard object. vCard object.
Value type: A single structured text value, separated by the SEMI- Value type: A single structured text value, separated by the SEMI-
COLON character (ASCII decimal 59). COLON character (ASCII decimal 59).
Cardinality: * Cardinality: *
Special notes: The structured type value consists of a sequence of Special notes: The structured type value consists of a sequence of
address components. The component values MUST be specified in address components. The component values MUST be specified in
their corresponding position. The structured type value their corresponding position. The structured type value
corresponds, in sequence, to the post office box; the extended corresponds, in sequence, to
address (e.g. apartment or suite number); the street address; the the post office box;
locality (e.g., city); the region (e.g., state or province); the the extended address (e.g. apartment or suite number);
postal code; the country name (full name in the language specified the street address;
in Section 5.1). When a component value is missing, the the locality (e.g., city);
associated component separator MUST still be specified. the region (e.g., state or province);
the postal code;
the country name (full name in the language specified in
Section 5.1).
When a component value is missing, the associated component
separator MUST still be specified.
Experience with vCard 3 has shown that the first two components Experience with vCard 3 has shown that the first two components
(post office box and extended address) are plagued with many (post office box and extended address) are plagued with many
interoperability issues. To ensure maximal interoperability, interoperability issues. To ensure maximal interoperability,
their values SHOULD be empty. their values SHOULD be empty.
The text components are separated by the SEMI-COLON character The text components are separated by the SEMI-COLON character
(ASCII decimal 59). Where it makes semantic sense, individual (ASCII decimal 59). Where it makes semantic sense, individual
text components can include multiple text values (e.g., a "street" text components can include multiple text values (e.g., a "street"
component with multiple lines) separated by the COMMA character component with multiple lines) separated by the COMMA character
skipping to change at page 58, line 5 skipping to change at page 59, line 5
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555 TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666 TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD END:VCARD
The details of global context simplification are unspecified by this The details of global context simplification are unspecified by this
document. They are left up to the synchronization engine. This document. They are left up to the synchronization engine. This
example is merely intended to illustrate the possibility, which example is merely intended to illustrate the possibility, which
investigating would be, in the authors' opinion, worthwhile. investigating would be, in the authors' opinion, worthwhile.
8. Example: Authors' vCards 8. Example: Author's vCard
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Simon Perreault FN:Simon Perreault
N:Perreault;Simon;;;ing. jr,M.Sc. N:Perreault;Simon;;;ing. jr,M.Sc.
BDAY:--0203 BDAY:--0203
ANNIVERSARY:20090808T1430-0500 ANNIVERSARY:20090808T1430-0500
GENDER:M GENDER:M
LANG;PREF=1:fr LANG;PREF=1:fr
LANG;PREF=2:en LANG;PREF=2:en
ORG;TYPE=work:Viagenie ORG;TYPE=work:Viagenie
ADR;TYPE=work:;Suite D2-630;2875 Laurier; ADR;TYPE=work:;Suite D2-630;2875 Laurier;
Quebec;QC;G1V 2M2;Canada Quebec;QC;G1V 2M2;Canada
TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102 TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102
TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501 TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501
EMAIL;TYPE=work:simon.perreault@viagenie.ca EMAIL;TYPE=work:simon.perreault@viagenie.ca
GEO;TYPE=work:geo:46.772673,-71.282945 GEO;TYPE=work:geo:46.772673,-71.282945
KEY;TYPE=work;VALUE=uri: KEY;TYPE=work;VALUE=uri:
http://www.viagenie.ca/simon.perreault/simon.asc http://www.viagenie.ca/simon.perreault/simon.asc
TZ:-0500 TZ:-0500
END:VCARD URL;TYPE=home:http://nomis80.org
BEGIN:VCARD
VERSION:4.0
FN:Pete Resnick
N:Resnick;Pete;;;
GENDER:M
ORG;TYPE=work:QUALCOMM Incorporated
ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
TEL;VALUE=uri;TYPE="work,voice":tel:+1-858-651-4478
EMAIL;TYPE=work:presnick@qualcomm.com
URL;TYPE=work:http://www.qualcomm.com/~presnick/
END:VCARD END:VCARD
9. Security Considerations 9. Security Considerations
o Internet mail is often used to transport vCards and is subject to o Internet mail is often used to transport vCards and is subject to
many well known security attacks, including monitoring, replay, many well known security attacks, including monitoring, replay,
and forgery. Care should be taken by any directory service in and forgery. Care should be taken by any directory service in
allowing information to leave the scope of the service itself, allowing information to leave the scope of the service itself,
where any access controls or confidentiality can no longer be where any access controls or confidentiality can no longer be
guaranteed. Applications should also take care to display guaranteed. Applications should also take care to display
directory data in a "safe" environment directory data in a "safe" environment
o vCards can carry cryptographic keys or certificates, as described o vCards can carry cryptographic keys or certificates, as described
in Section 6.8.1. in Section 6.8.1.
o The vCard objects have no inherent authentication or privacy, but o vCards often carry information that can be sensitive (e.g.
can easily be carried by any security mechanism that transfers birthday, address, and phone information). Although vCards have
MIME objects with authentication or privacy (e.g. S/MIME no inherent authentication or privacy provisions, they can easily
[RFC5751], OpenPGP [RFC4880]). In cases where the threat of be carried by any security mechanism that transfers MIME objects
"spoofed" vCard information is a concern, the vCard SHOULD BE to address authentication or privacy (e.g. S/MIME [RFC5751],
transported using one of these secure mechanisms. OpenPGP [RFC4880]). In cases where the privacy or authenticity of
information contained in vCard is a concern, the vCard SHOULD be
transported using one of these secure mechanisms. The KEY
property (Section 6.8.1) can be used to transport the public key
used by these mechanisms.
o The information in a vCard may become out of date. In cases where o The information in a vCard may become out of date. In cases where
the vitality of data is important to an originator of a vCard, the the vitality of data is important to an originator of a vCard, the
SOURCE property (Section 6.1.3) SHOULD be specified. In addition, SOURCE property (Section 6.1.3) SHOULD be specified. In addition,
the "REV" type described in section Section 6.7.4 can be specified the "REV" type described in section Section 6.7.4 can be specified
to indicate the last time that the vCard data was updated. to indicate the last time that the vCard data was updated.
10. IANA Considerations 10. IANA Considerations
10.1. MIME Type Registration 10.1. Media Type Registration
IANA is asked to register the following MIME Media Type (in IANA is asked to register the following Media Type (in
<http://www.iana.org/assignments/media-types/>). <http://www.iana.org/assignments/media-types/>).
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of media type text/vcard Subject: Registration of media type text/vcard
Type name: text Type name: text
Subtype name: vcard Subtype name: vcard
skipping to change at page 60, line 19 skipping to change at page 61, line 15
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; profile=vcard * text/directory; profile=vcard
* text/x-vcard * text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-19 Published specification: draft-ietf-vcarddav-vcardrev-20
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. management software.
Additional information: Additional information:
Magic number(s): Magic number(s):
File extension(s): .vcf .vcard File extension(s): .vcf .vcard
Macintosh file type code(s): Macintosh file type code(s):
Person & email address to contact for further information: Simon Person & email address to contact for further information: vCard
Perreault <simon.perreault@viagenie.ca> discussion mailing list <vcarddav@ietf.org>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author: Simon Perreault Author: Simon Perreault
Change controller: IETF Change controller: IETF
10.2. Registering New vCard Elements 10.2. Registering New vCard Elements
This section defines the process for registering new or modified This section defines the process for registering new or modified
vCard elements (i.e. properties, parameters, value data types, and vCard elements (i.e. properties, parameters, value data types, and
values) with IANA. It does not contain any immediate IANA actions. values) with IANA. It does not contain any immediate IANA actions.
10.2.1. Registration Procedure 10.2.1. Registration Procedure
The IETF will create a mailing list, vcard@ietf.org [1], which can be The IETF will create a mailing list, vcarddav@ietf.org [1], which can
used for public discussion of vCard element proposals prior to be 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. vcarddav@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 Track RFC is REQUIRED for
for the registration of new value data types that modify existing the registration of new value data types that modify existing
properties. A Standard Tracks RFC is also REQUIRED for registration properties. A Standard Track 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 Track 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 vcarddav@ietf.org [1] and iana@iana.org [2]. The designated expert
expected to tell IANA and the submitter of the registration within is expected to tell IANA and the submitter of the registration within
two weeks whether the registration is approved, approved with minor two weeks whether the registration is approved, approved with minor
changes, or rejected with cause. When a registration is rejected changes, or rejected with cause. When a registration is rejected
with cause, it can be re-submitted if the concerns listed in the with cause, it can be re-submitted if the concerns listed in the
cause are addressed. Decisions made by the designated expert can be cause are addressed. Decisions made by the designated expert can be
appealed to the IESG Applications Area Director, then to the IESG. appealed to the IESG Applications Area Director, then to the IESG.
They follow the normal appeals procedure for IESG decisions. They follow the normal appeals procedure for IESG decisions.
Once the registration procedure concludes successfully, IANA creates Once the registration procedure concludes successfully, IANA creates
or modifies the corresponding record in the vCard registry. The or modifies the corresponding record in the vCard registry. The
completed registration template is discarded. completed registration template is discarded.
An RFC specifying new vCard elements MUST include the completed An RFC specifying new vCard elements MUST include the completed
registration templates, which MAY be expanded with additional registration templates, which MAY be expanded with additional
information. These completed templates will go in the body of the information. These completed templates are intended to go in the
document, and SHOULD NOT be included or repeated in the IANA body of the document, not in the IANA Considerations section.
Considerations section.
Finally, note that there is an XML representation for vCard defined Finally, note that there is an XML representation for vCard defined
in [I-D.ietf-vcarddav-vcardxml]. An XML representation SHOULD be in [I-D.ietf-vcarddav-vcardxml]. An XML representation SHOULD be
defined for new vCard objects. defined for new vCard objects.
10.2.2. Vendor Namespace 10.2.2. Vendor Namespace
The vendor namespace is used for vCard elements associated with The vendor namespace is used for vCard elements associated with
commercially available products. "Vendor" or "producer" are commercially available products. "Vendor" or "producer" are
construed as equivalent and very broadly in this context. construed as equivalent and very broadly in this context.
skipping to change at page 62, line 17 skipping to change at page 63, line 9
registered. Changes to the specification will be made at their registered. Changes to the specification will be made at their
request, as discussed in subsequent sections. request, as discussed in subsequent sections.
vCard elements belonging to the vendor namespace will be vCard elements belonging to the vendor namespace will be
distinguished by the "VND-" prefix. This is followed by an IANA- distinguished by the "VND-" prefix. This is followed by an IANA-
registered Private Enterprise Number (PEN), a dash, and a vCard registered Private Enterprise Number (PEN), a dash, and a vCard
element designation of the vendor's choosing (e.g., "VND-123456- element designation of the vendor's choosing (e.g., "VND-123456-
MUDPIE"). MUDPIE").
While public exposure and review of vCard elements to be registered While public exposure and review of vCard elements to be registered
in the vendor namespace is not required, using the vcard@ietf.org [1] in the vendor namespace is not required, using the
mailing list for review is strongly encouraged to improve the quality vcarddav@ietf.org [1] mailing list for review is strongly encouraged
of those specifications. Registrations in the vendor namespace may to improve the quality of those specifications. Registrations in the
be submitted directly to the IANA. vendor namespace may be submitted directly to the IANA.
10.2.3. Registration Template for Properties 10.2.3. Registration Template for Properties
A property is defined by completing the following template. A property is defined by completing the following template.
Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor- Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-
specific property (where NNNN is replaced by the vendor's PEN). specific property (where NNNN is replaced by the vendor's PEN).
Property name: The name of the property. Property name: The name of the property.
skipping to change at page 66, line 39 skipping to change at page 67, line 39
| BOOLEAN | RFCXXXX, Section 4.4 | | BOOLEAN | RFCXXXX, Section 4.4 |
| DATE | RFCXXXX, Section 4.3.1 | | DATE | RFCXXXX, Section 4.3.1 |
| TIME | RFCXXXX, Section 4.3.2 | | TIME | RFCXXXX, Section 4.3.2 |
| DATE-TIME | RFCXXXX, Section 4.3.3 | | DATE-TIME | RFCXXXX, Section 4.3.3 |
| DATE-AND-OR-TIME | RFCXXXX, Section 4.3.4 | | DATE-AND-OR-TIME | RFCXXXX, Section 4.3.4 |
| TIMESTAMP | RFCXXXX, Section 4.3.5 | | TIMESTAMP | RFCXXXX, Section 4.3.5 |
| FLOAT | RFCXXXX, Section 4.6 | | FLOAT | RFCXXXX, Section 4.6 |
| INTEGER | RFCXXXX, Section 4.5 | | INTEGER | RFCXXXX, Section 4.5 |
| TEXT | RFCXXXX, Section 4.1 | | TEXT | RFCXXXX, Section 4.1 |
| URI | RFCXXXX, Section 4.2 | | URI | RFCXXXX, Section 4.2 |
| LANGUAGE-TAG | RFCXXXX, Section 4.7 | | UTC-OFFSET | RFCXXXX, Section 4.7 |
| LANGUAGE-TAG | RFCXXXX, Section 4.8 |
+------------------+------------------------+ +------------------+------------------------+
10.3.4. Values Registries 10.3.4. Values Registries
Separate tables will be used for property and parameter values. Separate tables will be used for property and parameter values.
The following table is to be used to initialize the property values The following table is to be used to initialize the property values
registry. registry.
+----------+------------+------------------------+ +----------+------------+------------------------+
skipping to change at page 70, line 26 skipping to change at page 71, line 26
Interconnection - The Directory: Interconnection - The Directory:
Selected Object Classes", Selected Object Classes",
CCITT Recommendation X.521, CCITT Recommendation X.521,
November 1988. November 1988.
[I-D.ietf-vcarddav-vcardxml] Perreault, S., "vCard XML [I-D.ietf-vcarddav-vcardxml] Perreault, S., "vCard XML
Representation", Representation",
draft-ietf-vcarddav-vcardxml-08 (work draft-ietf-vcarddav-vcardxml-08 (work
in progress), April 2011. in progress), April 2011.
[IEEE.754.2008] Institute of Electrical and Electronics
Engineers, "IEEE Standard for Floating-
Point Arithmetic", IEEE Standard 754,
August 2008.
[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 interchange - Representation of dates
and times", ISO Standard 8601, and times", ISO Standard 8601,
December 2000. 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
skipping to change at page 71, line 10 skipping to change at page 72, line 15
RFC 2046, November 1996. RFC 2046, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs [RFC2119] Bradner, S., "Key words for use in RFCs
to Indicate Requirement Levels", to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997. BCP 14, RFC 2119, March 1997.
[RFC2739] Small, T., Hennessy, D., and F. Dawson, [RFC2739] Small, T., Hennessy, D., and F. Dawson,
"Calendar Attributes for vCard and "Calendar Attributes for vCard and
LDAP", RFC 2739, January 2000. LDAP", RFC 2739, January 2000.
[RFC3536] Hoffman, P., "Terminology Used in
Internationalization in the IETF",
RFC 3536, May 2003.
[RFC3629] Yergeau, F., "UTF-8, a transformation [RFC3629] Yergeau, F., "UTF-8, a transformation
format of ISO 10646", STD 63, RFC 3629, format of ISO 10646", STD 63, RFC 3629,
November 2003. November 2003.
[RFC3966] Schulzrinne, H., "The tel URI for [RFC3966] Schulzrinne, H., "The tel URI for
Telephone Numbers", RFC 3966, Telephone Numbers", RFC 3966,
December 2004. December 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. [RFC3986] Berners-Lee, T., Fielding, R., and L.
Masinter, "Uniform Resource Identifier Masinter, "Uniform Resource Identifier
skipping to change at page 72, line 10 skipping to change at page 73, line 18
[RFC5646] Phillips, A. and M. Davis, "Tags for [RFC5646] Phillips, A. and M. Davis, "Tags for
Identifying Languages", BCP 47, Identifying Languages", BCP 47,
RFC 5646, September 2009. RFC 5646, September 2009.
[RFC5870] Mayrhofer, A. and C. Spanring, "A [RFC5870] Mayrhofer, A. and C. Spanring, "A
Uniform Resource Identifier for Uniform Resource Identifier for
Geographic Locations ('geo' URI)", Geographic Locations ('geo' URI)",
RFC 5870, June 2010. RFC 5870, June 2010.
[W3C.REC-xml-20081126] Bray, T., Yergeau, F., Maler, E., [W3C.REC-xml-20081126] Sperberg-McQueen, C., Yergeau, F.,
Paoli, J., and C. Sperberg-McQueen, Bray, T., Paoli, J., and E. Maler,
"Extensible Markup Language (XML) 1.0 "Extensible Markup Language (XML) 1.0
(Fifth Edition)", World Wide Web (Fifth Edition)", World Wide Web
Consortium Recommendation REC-xml- Consortium Recommendation REC-xml-
20081126, November 2008, <http:// 20081126, November 2008, <http://
www.w3.org/TR/2008/REC-xml-20081126>. www.w3.org/TR/2008/REC-xml-20081126>.
[xfn] Celik, T., Mullenweg, M., and E. Meyer, [xfn] Celik, T., Mullenweg, M., and E. Meyer,
"XHTML Friends Network 1.1", "XHTML Friends Network 1.1",
<http://gmpg.org/xfn/11>. <http://gmpg.org/xfn/11>.
skipping to change at page 73, line 43 skipping to change at page 74, line 51
[TZ-DB] Olson, A., "Time zone code and data", [TZ-DB] Olson, A., "Time zone code and data",
<ftp://elsie.nci.nih.gov/pub/>. <ftp://elsie.nci.nih.gov/pub/>.
[vCard21] Internet Mail Consortium, "vCard - The [vCard21] Internet Mail Consortium, "vCard - The
Electronic Business Card Version 2.1", Electronic Business Card Version 2.1",
September September. September September.
URIs URIs
[1] <mailto:vcard@ietf.org> [1] <mailto:vcarddav@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.
A.1. New Structure A.1. New Structure
skipping to change at page 75, line 5 skipping to change at page 76, line 11
o The "work", "home", and "uri" TYPE parameter values for the EMAIL o The "work", "home", and "uri" TYPE parameter values for the EMAIL
property have been added. property have been added.
o The "pref" value of the TYPE parameter is now a parameter of its o The "pref" value of the TYPE parameter is now a parameter of its
own, with a positive integer value indicating the level of own, with a positive integer value indicating the level of
preference. preference.
o The ALTID and PID parameters have been added. o The ALTID and PID parameters have been added.
o The MEDIATYPE parameter has been added and replaces the TYPE
parameter when it was used for indicating the media type of the
property's content.
A.4. Other Changes A.4. Other Changes
o Synchronization is addressed in Section 7. o Synchronization is addressed in Section 7.
o The N property is no longer mandatory. o The N property is no longer mandatory.
o The value of TEL is now a URI. o The value of TEL is now a URI.
o The AGENT property was replaced with a type of RELATED. o The AGENT property was replaced with a type of RELATED.
o Date and time values now only support the basic format. o Date and time values now only support the basic format.
Truncation is now supported. Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -19 B.1. Changes in -20
o Reworded security considerations.
o Specified range of integer and float value types.
o Adjusted IANA considerations wording.
o Added missing date-and-or-type to the VALUE ABNF.
o s/vcard@ietf.org/vcarddav@ietf.org/
o More precise wording: charset instead of character set
o Make parameter values case-insensitive by default.
o Escaping newlines can be done with \n or \N.
o Make SORT-AS value case-sensitive.
o Better formatting for ADR special notes.
o Removed Pete Resnick's example vCard.
o vcarddav@ietf.org is the contact person for the media type.
o Add missing pref-param, pid-param, and any-param to the PHOTO
property.
o Re-added missing section on UTC-OFFSET value type.
B.2. Changes in -19
o Fixed nits. o Fixed nits.
o Fixed MEDIATYPE ABNF. o Fixed MEDIATYPE ABNF.
B.2. Changes in -18 B.3. Changes in -18
o Fix missing text in KIND section. o Fix missing text in KIND section.
B.3. Changes in -17 B.4. Changes in -17
o s/individual/entity/ o s/individual/entity/
o Moved section 3.4 for better flow. o Moved section 3.4 for better flow.
o Removed text overriding general MIME and HTTP rules. o Removed text overriding general MIME and HTTP rules.
o Fixed redundant ABNF. o Fixed redundant ABNF.
o Fixed parameter value quoting in examples. o Fixed parameter value quoting in examples.
skipping to change at page 76, line 24 skipping to change at page 78, line 18
o Removed underspecified "Status" column in IANA registry. o Removed underspecified "Status" column in IANA registry.
o Moved obsoleted references to Informative section. o Moved obsoleted references to Informative section.
o Moved iCalendar references to Normative section. o Moved iCalendar references to Normative section.
o Expanded specification of KIND values. o Expanded specification of KIND values.
o Recommend defining an XML representation for new vCard objects. o Recommend defining an XML representation for new vCard objects.
B.4. Changes in -16 B.5. Changes in -16
o RELATED: Added XFN values into IANA registry. o RELATED: Added XFN values into IANA registry.
o RELATED: Added values "agent" and "emergency". o RELATED: Added values "agent" and "emergency".
o EMAIL is now free-form text, with informative reference to EAI. o EMAIL is now free-form text, with informative reference to EAI.
o GENDER now has two components: one for biological sex, the other o GENDER now has two components: one for biological sex, the other
for gender identity. for gender identity.
o Bugfixes to the core ABNF. o Bugfixes to the core ABNF.
o Clarified IANA considerations. o Clarified IANA considerations.
o UID may be reset to free-form text. o UID may be reset to free-form text.
B.5. Changes in -15 B.6. Changes in -15
o Reverted N to the 5-component format of vCard 3. o Reverted N to the 5-component format of vCard 3.
o Removed DDAY, BIRTH, and DEATH. o Removed DDAY, BIRTH, and DEATH.
o First two components in ADR SHOULD be empty. o First two components in ADR SHOULD be empty.
o Removed the LABEL property. o Removed the LABEL property.
o Removed the binary value type and the ENCODING and FMTTYPE o Removed the binary value type and the ENCODING and FMTTYPE
skipping to change at page 77, line 25 skipping to change at page 79, line 19
o RELATED now uses XFN 1.1 for its value. o RELATED now uses XFN 1.1 for its value.
o Dropped the VERSION parameter. XML MUST be version 1.0. o Dropped the VERSION parameter. XML MUST be version 1.0.
o Dropped the CLASS property. o Dropped the CLASS property.
o Property and parameter names SHOULD be upper-case. o Property and parameter names SHOULD be upper-case.
o Use ABNF for cardinality notation. o Use ABNF for cardinality notation.
B.6. Changes in -14 B.7. Changes in -14
o DQUOTE is US-ASCII decimal 34, not 22. o DQUOTE is US-ASCII decimal 34, not 22.
o Removed unused reference to RFC 2046. o Removed unused reference to RFC 2046.
o Updated reference to draft-ietf-vcarddav-vcardxml. o Updated reference to draft-ietf-vcarddav-vcardxml.
o Small fixes to the IANA registration text. o Small fixes to the IANA registration text.
o Added notes on the usage of TEL and IMPP properties. o Added notes on the usage of TEL and IMPP properties.
skipping to change at page 78, line 11 skipping to change at page 80, line 5
o Removed advice for always including VALUE parameter. o Removed advice for always including VALUE parameter.
o FMTTYPE MUST include the full MIME type. o FMTTYPE MUST include the full MIME type.
o Made ADR's ABNF more verbose. o Made ADR's ABNF more verbose.
o Organized TEL TYPE values in a table. o Organized TEL TYPE values in a table.
o Replaced TOP-SECRET example with NOINDEX. o Replaced TOP-SECRET example with NOINDEX.
B.7. Changes in -13 B.8. Changes in -13
o Changed global ABNF to make explicit that VERSION comes first. o Changed global ABNF to make explicit that VERSION comes first.
o Reworked example for LANGUAGE property. o Reworked example for LANGUAGE property.
o s/TYPE/FMTTYPE/ in two examples. o s/TYPE/FMTTYPE/ in two examples.
o Allow LANGUAGE parameter for text-valued BDAY, DDAY, and RELATED. o Allow LANGUAGE parameter for text-valued BDAY, DDAY, and RELATED.
o Tightened language on LANGUAGE parameter regarding cardinality. o Tightened language on LANGUAGE parameter regarding cardinality.
o Removed the NAME property. o Removed the NAME property.
o Adjusted semi-colon escaping rules. o Adjusted semi-colon escaping rules.
o Added the ALTID parameter. o Added the ALTID parameter.
B.8. Changes in -12 B.9. Changes in -12
o Fixed example of LANGUAGE cardinality. o Fixed example of LANGUAGE cardinality.
o Added note about YYYY-MM date format. o Added note about YYYY-MM date format.
o Fixed appendix A. o Fixed appendix A.
o VERSION property must come first. o VERSION property must come first.
o Fixed mistake in PID example. o Fixed mistake in PID example.
skipping to change at page 79, line 32 skipping to change at page 81, line 26
o BIRTH and DEATH can now have URI values. o BIRTH and DEATH can now have URI values.
o Created the FMTTYPE parameter. o Created the FMTTYPE parameter.
o KEY can now take a text value. o KEY can now take a text value.
o Added references to RFC 5545 (iCalendar). o Added references to RFC 5545 (iCalendar).
o Added namespace column in parameters registry. o Added namespace column in parameters registry.
B.9. Changes in -11 B.10. Changes in -11
o Change "XML chunk" to "XML fragment". o Change "XML chunk" to "XML fragment".
o Cite W3C document containing definition of "fragment". o Cite W3C document containing definition of "fragment".
o Added "XML" to property name ABNF. o Added "XML" to property name ABNF.
o Clarified newline escaping rule. o Clarified newline escaping rule.
o Replaced one remaining "type" with "property". o Replaced one remaining "type" with "property".
skipping to change at page 80, line 9 skipping to change at page 82, line 5
o XML property can now only contain one element that is not in the o XML property can now only contain one element that is not in the
vCard 4 namespace. vCard 4 namespace.
o Clarified interrelationship between LANGUAGE, cardinality, and o Clarified interrelationship between LANGUAGE, cardinality, and
PID. PID.
o Added "textphone" TEL type. o Added "textphone" TEL type.
o Fixed quoting of comma in ORG examples. o Fixed quoting of comma in ORG examples.
B.10. Changes in -10 B.11. Changes in -10
o Added component in SORT-STRING for sorting by given name. Fixed o Added component in SORT-STRING for sorting by given name. Fixed
and expanded the examples. and expanded the examples.
o Fixed KIND-value ABNF. o Fixed KIND-value ABNF.
o Fixed deprecated media type. o Fixed deprecated media type.
o Created the CALSCALE parameter. o Created the CALSCALE parameter.
o Strenghtened the stance on character set. o Strenghtened the stance on character set.
o Defined the Language-Tag ABNF. o Defined the Language-Tag ABNF.
o Made explicit the fact that IANA does not register templates. o Made explicit the fact that IANA does not register templates.
o Created the XML property. o Created the XML property.
o Added social networking examples to URL property. o Added social networking examples to URL property.
B.11. Changes in -09 B.12. Changes in -09
o Removed special meaning for groups. Removed the "work" and "home" o Removed special meaning for groups. Removed the "work" and "home"
groups. Removed the group registry. Re-introduced the "work" and groups. Removed the group registry. Re-introduced the "work" and
"home" TYPE parameter values. Applied the TYPE parameter to "home" TYPE parameter values. Applied the TYPE parameter to
properties which supported the "work" and "home" groups. properties which supported the "work" and "home" groups.
o Vendor namespace now uses private enterprise number in prefix. o Vendor namespace now uses private enterprise number in prefix.
o Added "thing" value for KIND property. o Added "thing" value for KIND property.
B.12. Changes in -08 B.13. Changes in -08
o Allow 1985 (year only) in date ABNF. o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example. o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value. o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME. o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to o Prefixed "param" and "value" production rules specific to
skipping to change at page 81, line 15 skipping to change at page 83, line 13
o Replaced the GENDER property with the SEX property. o Replaced the GENDER property with the SEX property.
o Added the ANNIVERSARY property. o Added the ANNIVERSARY property.
o Added the "friend" and "spouse" types of RELATED. o Added the "friend" and "spouse" types of RELATED.
o TZ property now has text / uri value. o TZ property now has text / uri value.
o Refined the definitions of TITLE and ROLE. o Refined the definitions of TITLE and ROLE.
B.13. Changes in -07 B.14. 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 81, line 37 skipping to change at page 83, line 35
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.14. Changes in -06 B.15. 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 82, line 28 skipping to change at page 84, line 26
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.15. Changes in -05 B.16. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.16. Changes in -04 B.17. 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 83, line 15 skipping to change at page 85, line 13
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.17. Changes in -03 B.18. 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.18. Changes in -02 B.19. 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 84, line 5 skipping to change at page 86, line 5
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 6.6.6) property. o Added the RELATED (Section 6.6.6) property.
o Fixed many ABNF typos (issue #252). o Fixed many ABNF typos (issue #252).
o Changed formatting of ABNF comments to make them easier to read o Changed formatting of ABNF comments to make them easier to read
(issue #226). (issue #226).
B.19. Changes in -01 B.20. 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 84, line 33 skipping to change at page 86, line 33
o Added Section 7. o Added Section 7.
o Created IANA process for registering new parameters, value types, o Created IANA process for registering new parameters, value types,
and properties. and properties.
o Created the initial IANA registries. o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288. o Created vendor namespace based on text from RFC 4288.
B.20. Changes in -00 B.21. 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. 79 change blocks. 
220 lines changed or deleted 289 lines changed or added

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