draft-ietf-vcarddav-vcardrev-12.txt   draft-ietf-vcarddav-vcardrev-13.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 P. Resnick Obsoletes: 2425, 2426, 4770 P. Resnick
(if approved) QUALCOMM Incorporated (if approved) QUALCOMM Incorporated
Updates: 2739 (if approved) July 12, 2010 Updates: 2739 (if approved) August 2, 2010
Intended status: Standards Track Intended status: Standards Track
Expires: January 13, 2011 Expires: February 3, 2011
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-12 draft-ietf-vcarddav-vcardrev-13
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.). clips, etc.).
Status of This Memo Status of This Memo
skipping to change at page 1, line 43 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 13, 2011. This Internet-Draft will expire on February 3, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 37 skipping to change at page 2, line 37
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. Line Delimiting and Folding . . . . . . . . . . . . . . . 6 3.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 6
3.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7 3.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7
3.3. Property Value Escaping . . . . . . . . . . . . . . . . . 9 3.3. Property Value Escaping . . . . . . . . . . . . . . . . . 9
3.4. Character Set . . . . . . . . . . . . . . . . . . . . . . 10 3.4. Character Set . . . . . . . . . . . . . . . . . . . . . . 10
4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10 4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10
4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 12 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 . . . . . . . . . . . . . . . . . . . . . . . . . 13
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16 4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16
5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16 5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16
5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.5. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.6. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.7. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.7. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.8. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.9. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.10. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.11. VERSION . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.12. FMTTYPE . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.12. VERSION . . . . . . . . . . . . . . . . . . . . . . . . . 23
6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 22 5.13. FMTTYPE . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. General Properties . . . . . . . . . . . . . . . . . . . . 23 6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1. General Properties . . . . . . . . . . . . . . . . . . . . 24
6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1.6. XML . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2. Identification Properties . . . . . . . . . . . . . . . . 27 6.2. Identification Properties . . . . . . . . . . . . . . . . 28
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 31 6.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 31 6.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 32 6.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2.9. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 32 6.2.9. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 34
6.2.10. SEX . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.2.10. SEX . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 33 6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 35
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 34 6.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4. Communications Properties . . . . . . . . . . . . . . . . 35 6.4. Communications Properties . . . . . . . . . . . . . . . . 36
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 36
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 . . . . . . . . . . . . . . . . . . . . . . . . . 40 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 . . . . . . . . . . . . . . . . . . 46
6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 44 6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 46
6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 45 6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 45 6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 46 6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 48
6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 47 6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 47 6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 49
6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 48 6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 49 6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 50
6.8. Security Properties . . . . . . . . . . . . . . . . . . . 49 6.8. Security Properties . . . . . . . . . . . . . . . . . . . 51
6.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 49 6.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 51
6.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 50 6.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 51 6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 53
6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 51 6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 53
6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 52 6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 53
6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 52 6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 54
6.10. Extended Properties and Parameters . . . . . . . . . . . . 53 6.10. Extended Properties and Parameters . . . . . . . . . . . . 55
7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 53 7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 55
7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 53 7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 55
7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 54 7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 55
7.1.2. Matching Property Instances . . . . . . . . . . . . . 54 7.1.2. Matching Property Instances . . . . . . . . . . . . . 55
7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 54 7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 56
7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 55 7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 55 7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 56
7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 55 7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 57
7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 56 7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 57
7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 56 7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 58
7.2.5. Global Context Simplification . . . . . . . . . . . . 58 7.2.5. Global Context Simplification . . . . . . . . . . . . 59
8. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 59 8. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 60
9. Security Considerations . . . . . . . . . . . . . . . . . . . 59 9. Security Considerations . . . . . . . . . . . . . . . . . . . 60
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
10.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 60 10.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 61
10.2. Registering New vCard Elements . . . . . . . . . . . . . . 61 10.2. Registering New vCard Elements . . . . . . . . . . . . . . 63
10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 62 10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 63
10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 62 10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 63
10.2.3. Registration Template for Properties . . . . . . . . . 63 10.2.3. Registration Template for Properties . . . . . . . . . 64
10.2.4. Registration Template for Parameters . . . . . . . . . 63 10.2.4. Registration Template for Parameters . . . . . . . . . 64
10.2.5. Registration Template for Value Data Types . . . . . . 64 10.2.5. Registration Template for Value Data Types . . . . . . 65
10.2.6. Registration Template for Values . . . . . . . . . . . 64 10.2.6. Registration Template for Values . . . . . . . . . . . 65
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 65 10.3. Initial vCard Elements Registries . . . . . . . . . . . . 66
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 65 10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 66
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 67 10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 68
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 67 10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 68
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 68 10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 69
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 71 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
12.1. Normative References . . . . . . . . . . . . . . . . . . . 71 12.1. Normative References . . . . . . . . . . . . . . . . . . . 72
12.2. Informative References . . . . . . . . . . . . . . . . . . 73 12.2. Informative References . . . . . . . . . . . . . . . . . . 74
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 74 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 . . . . . . . . . . . . . . 75 A.3. New Properties and Parameters . . . . . . . . . . . . . . 76
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 -12 . . . . . . . . . . . . . . . . . . . . . . 75 B.1. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 76
B.2. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 76 B.2. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 77
B.3. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 77 B.3. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 78
B.4. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 77 B.4. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 78
B.5. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 78 B.5. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 79
B.6. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 78 B.6. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 79
B.7. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 79 B.7. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 79
B.8. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 79 B.8. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 80
B.9. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 79 B.9. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 81
B.10. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 80 B.10. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 81
B.11. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 80 B.11. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 81
B.12. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 81 B.12. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 82
B.13. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 82 B.13. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 82
B.14. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 83
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 7, line 38 skipping to change at page 7, line 38
line. line.
3.2. ABNF Format Definition 3.2. ABNF Format Definition
The following ABNF uses the notation of [RFC5234], which also defines The following ABNF uses the notation of [RFC5234], which also defines
CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.
vcard-entity = 1*(vcard) vcard-entity = 1*(vcard)
vcard = "BEGIN" ":" "VCARD" CRLF vcard = "BEGIN" ":" "VCARD" CRLF
"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 first.
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 = 1*(ALPHA / DIGIT / "-") group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "NAME" / "KIND" / "FN" / "N" / "NICKNAME" name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH"
/ "ANNIVERSARY" / "SEX" / "ADR" / "LABEL" / "TEL" / "EMAIL" / "ANNIVERSARY" / "SEX" / "ADR" / "LABEL" / "TEL" / "EMAIL"
/ "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO"
/ "ORG" / "MEMBER" / "RELATED" / "CATEGORIES" / "NOTE" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES" / "NOTE"
/ "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL"
/ "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI" / "CLASS" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ "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
; defined in ABNF sections below. ; defined in ABNF sections below.
; Group and name are case-insensitive. ; Group and name are case-insensitive.
iana-token = 1*(ALPHA / DIGIT / "-") iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA ; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-") x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are ; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released ; reserved for experimental use, not intended for released
skipping to change at page 9, line 39 skipping to change at page 9, line 40
Some properties may contain one or more values delimited by a COMMA Some properties may contain one or more values delimited by a COMMA
character (ASCII decimal 44). Therefore, a COMMA character in a character (ASCII decimal 44). Therefore, a COMMA character in a
value MUST be escaped with a BACKSLASH character (ASCII decimal 92), value MUST be escaped with a BACKSLASH character (ASCII decimal 92),
even for properties that don't allow multiple instances (for even for properties that don't allow multiple instances (for
consistency). consistency).
Some properties (e.g. N and ADR) comprise multiple fields delimited Some properties (e.g. N and ADR) comprise multiple fields delimited
by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI- by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI-
COLON in a field of such a "compound" property MUST be escaped with a COLON in a field of such a "compound" property MUST be escaped with a
BACKSLASH character. SEMI-COLON characters in non-compound BACKSLASH character. SEMI-COLON characters in non-compound
properties MUST NOT be escaped. properties MAY be escaped. On input, an escaped SEMI-COLON character
is never a field separator. An unescaped SEMI-COLON character may be
a field separator, depending on the property in which it appears.
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
skipping to change at page 10, line 36 skipping to change at page 10, line 39
/ binary / binary
/ URI ; from Section 3 of [RFC3986] / URI ; from Section 3 of [RFC3986]
/ iana-valuespec / iana-valuespec
; Actual value type depends on property name and VALUE parameter. ; Actual value type depends on property name and VALUE parameter.
text = *VALUE-CHAR text = *VALUE-CHAR
text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR) text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)
TEXT-LIST-CHAR = "\\" / "\," / "\n" TEXT-LIST-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \ or newline> / <any VALUE-CHAR except , or \>
; 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-or-time) date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list = timestamp *("," timestamp) timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer) integer-list = integer *("," integer)
float-list = float *("," float) float-list = float *("," float)
skipping to change at page 16, line 51 skipping to change at page 17, line 21
languages. There is no concept of "default" language, except as languages. There is no concept of "default" language, except as
specified by any "Content-Language" MIME header parameter that is specified by any "Content-Language" MIME header parameter that is
present. The value of the LANGUAGE property parameter is a language present. The value of the LANGUAGE property parameter is a language
tag as defined in Section 2 of [RFC5646]. tag as defined in Section 2 of [RFC5646].
ABNF: ABNF:
language-param = "LANGUAGE=" Language-Tag language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 5646 ; Language-Tag is defined in section 2.1 of RFC 5646
Properties with different LANGUAGE parameters that represent the same
data count as 1 toward cardinality and MUST have the same PID value
if the PID parameter is used. This is because there is logically a
single property which is expressed in multiple languages.
Therefore, since BIRTH (Section 6.2.7) has cardinality (0,1), these
two examples would be legal:
BIRTH;LANGUAGE=fr:Ville de Quebec
BIRTH;LANGUAGE=en:Quebec City
BIRTH;PID=1;LANGUAGE=fr:Ville de Quebec
BIRTH;PID=1;LANGUAGE=en:Quebec City
while these three would not:
BIRTH;PID=1;LANGUAGE=fr:Ville de Quebec
BIRTH;PID=2;LANGUAGE=en:Quebec City
BIRTH;LANGUAGE=fr:Ville de Quebec
BIRTH:Quebec City
BIRTH;LANGUAGE=fr:Ville de Quebec
BIRTH;LANGUAGE=en:Quebec City
BIRTH;LANGUAGE=en:Montreal
5.2. ENCODING 5.2. ENCODING
The ENCODING property parameter is used to specify an alternate The ENCODING property parameter is used to specify an alternate
encoding for a value. If the value contains a CRLF, it must be encoding for a value. If the value contains a CRLF, it must be
encoded, since CRLF is used to separate lines in the content-type encoded, since CRLF is used to separate lines in the content-type
itself. Currently, only the "b" encoding is supported. itself. Currently, only the "b" encoding is supported.
The "b" encoding ([RFC2047], section 4.1) can also be useful for The "b" encoding ([RFC2047], section 4.1) can also be useful for
binary values that are mixed with other text information in the body binary values that are mixed with other text information in the body
part (e.g., a certificate). Using a per-value "b" encoding in this part (e.g., a certificate). Using a per-value "b" encoding in this
skipping to change at page 19, line 29 skipping to change at page 19, line 18
NOT be interpreted on its own. NOT be interpreted on its own.
This parameter MAY be applied to any property that allows multiple This parameter MAY be applied to any property that allows multiple
instances. instances.
ABNF: ABNF:
pref-param = "PREF=" (1*2DIGIT / "100") pref-param = "PREF=" (1*2DIGIT / "100")
; An integer between 1 and 100. ; An integer between 1 and 100.
5.5. PID 5.5. ALTID
The ALTID parameter is used to "tag" property instances as being
alternative representations of the same logical property. For
example, translations of a property in multiple languages generates
multiple property instances having different LANGUAGE (Section 5.1)
parameter which are tagged with the same ALTID value.
This parameter's value is treated as an opaque string. Its sole
purpose is to be compared for equality against other ALTID parameter
values.
Two property instances are considered alternative representations of
the same logical property if and only if their names as well as the
value of their ALTID parameters are identical. Property instances
without the ALTID parameter MUST NOT be considered an alternative
representation of any other property instance. Values for the ALTID
parameter are not globally unique: they MAY be reused for different
property names.
Property instances having the same ALTID parameter value count as 1
toward cardinality. Therefore, since BIRTH (Section 6.2.7) has
cardinality (0,1) and TITLE (Section 6.6.1) has cardinality (0,n),
these three examples would be legal:
BIRTH;ALTID=1;LANGUAGE=fr:Ville de Quebec
BIRTH;ALTID=1;LANGUAGE=en:Quebec City
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
while this one would not:
BIRTH;ALTID=1;LANGUAGE=fr:Ville de Quebec
BIRTH:Quebec City
(Two instances of the BIRTH property.)
and these three would be legal but questionable:
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=2;LANGUAGE=en:Boss
(Should probably have the same ALTID value.)
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE:LANGUAGE=en:Boss
(Second line should probably have ALTID=1.)
BIRTH;ALTID=1;LANGUAGE=fr:Ville de Quebec
BIRTH;ALTID=1;LANGUAGE=en:Quebec City
BIRTH;ALTID=1;LANGUAGE=en:Montreal
(The last line should probably have ALTID=2. But that would be
illegal because BIRTH has cardinality (0,1).)
The ALTID property MAY also be used in may contexts other than with
the LANGUAGE parameter. Here's an example with two representations
of the same photo in different file formats:
PHOTO;ALTID=1;ENCODING=b;FMTTYPE=image/jpeg:...
PHOTO;ALTID=1;ENCODING=b;FMTTYPE=image/jp2:...
ABNF:
altid-param = "ALTID=" text
5.6. PID
The PID parameter is used to identify a specific property among The PID parameter is used to identify a specific property among
multiple instances. It plays a role analogous to the UID property multiple instances. It plays a role analogous to the UID property
(Section 6.7.6) on a per-property instead of per-vCard basis. It MAY (Section 6.7.6) on a per-property instead of per-vCard basis. It MAY
appear more than once in a given property. It MUST NOT appear on appear more than once in a given property. It MUST NOT appear on
properties that may have only one instance per vCard. Its value is properties that may have only one instance per vCard. Its value is
either a single small positive integer, or a pair of small positive either a single small positive integer, or a pair of small positive
integers separated by a dot. Multiple values may be encoded in a integers separated by a dot. Multiple values may be encoded in a
single PID parameter by separating the values with a comma ",". See single PID parameter by separating the values with a comma ",". See
Section 7 for more details on its usage. Section 7 for more details on its usage.
ABNF: ABNF:
pid-param = "PID=" pid-value *("," pid-value) pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT] pid-value = 1*DIGIT ["." 1*DIGIT]
5.6. TYPE 5.7. TYPE
The TYPE parameter has multiple, different uses. In general, it is a The TYPE parameter has multiple, different uses. In general, it is a
way of specifying class characteristics of the associated property. way of specifying class characteristics of the associated property.
Most of the time, its value is a comma-separated subset of a pre- Most of the time, its value is a comma-separated subset of a pre-
defined enumeration. In this document, the following properties make defined enumeration. In this document, the following properties make
use of this parameter: FN, NICKNAME, PHOTO, ADR, LABEL, TEL, EMAIL, use of this parameter: FN, NICKNAME, PHOTO, ADR, LABEL, TEL, EMAIL,
IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES,
NOTE, SOUND, URL, KEY, FIBURL, CALADRURI, and CALURI. The TYPE NOTE, SOUND, URL, KEY, FIBURL, CALADRURI, and CALURI. The TYPE
parameter MUST NOT be applied on other properties defined in this parameter MUST NOT be applied on other properties defined in this
document. document.
skipping to change at page 20, line 25 skipping to change at page 21, line 38
"individual", or to none in other cases. "individual", or to none in other cases.
ABNF: ABNF:
type-param = "TYPE=" type-value *("," type-value) type-param = "TYPE=" type-value *("," type-value)
type-value = "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. CALSCALE 5.8. CALSCALE
The CALSCALE parameter is used to define the calendar system in which The CALSCALE parameter is used to define the calendar system in which
a date or date-time value is expressed. The only value specified in a date or date-time value is expressed. The only value specified in
this document is "gregorian", which stands for the Gregorian system. this document is "gregorian", which stands for the Gregorian system.
It is the default when the parameter is absent. It is the default when the parameter is absent.
ABNF: ABNF:
calscale-param = "CALSCALE=" calscale-value calscale-param = "CALSCALE=" calscale-value
calscale-value = "gregorian" / iana-token / x-name calscale-value = "gregorian" / iana-token / x-name
5.8. 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 single structured text value which MUST This parameter's value is a single structured text value which MUST
have as many or less components as the corresponding property value have as many or less components as the corresponding property value
has. has.
skipping to change at page 22, line 5 skipping to change at page 23, line 23
If sorted by given name the results would be: If sorted by given name the results would be:
Christine d'Aboville Christine d'Aboville
H. James de Mann H. James de Mann
Osamu Koura Osamu Koura
Oscar del Pozo Oscar del Pozo
Rene van der Harten Rene van der Harten
Robert Pau Shou Chang Robert Pau Shou Chang
5.9. GEO 5.10. GEO
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 an address. Its value is the same as information that is specific to an address. Its value is the same as
that of the GEO property. that of the GEO property.
ABNF: ABNF:
geo-param = "GEO=" DQUOTE uri DQUOTE geo-param = "GEO=" DQUOTE uri DQUOTE
5.10. TZ 5.11. TZ
The TZ parameter can be used to indicate time zone information that The TZ parameter can be used to indicate time zone information that
is specific to an address. Its value is the same as that of the TZ is specific to an address. Its value is the same as that of the TZ
property. property.
ABNF: ABNF:
tz-param = "TZ=" DQUOTE (text / uri) DQUOTE tz-param = "TZ=" DQUOTE (text / uri) DQUOTE
5.11. VERSION 5.12. VERSION
The VERSION parameter indicates the version number of a property The VERSION parameter indicates the version number of a property
value's format. In this specification, it is only used witht the XML value's format. In this specification, it is only used witht the XML
property (Section 6.1.6) to indicate the XML version of the value. property (Section 6.1.5) to indicate the XML version of the value.
ABNF: ABNF:
version-param = "VERSION=" param-value version-param = "VERSION=" param-value
5.12. FMTTYPE 5.13. FMTTYPE
The FMTTYPE parameter indicates the content type [RFC4288] of a The FMTTYPE parameter indicates the content type [RFC4288] of a
property's value. It is most often used on properties with a property's value. It is most often used on properties with a
"binary" value type. "binary" value type.
ABNF: ABNF:
fmttype-param = "FMTTYPE=" type-name "/" subtype-name fmttype-param = "FMTTYPE=" type-name "/" subtype-name
; "type-name" and "subtype-name" are defined in ; "type-name" and "subtype-name" are defined in
; Section 4.2 of [RFC4288]. ; Section 4.2 of [RFC4288].
skipping to change at page 24, line 51 skipping to change at page 26, line 21
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:
SOURCE-param = "VALUE=uri" / pid-param / pref-param / any-param SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ any-param
SOURCE-value = uri SOURCE-value = uri
Examples: Examples:
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/ SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf Jean%20Dupont.vcf
6.1.4. NAME 6.1.4. KIND
Purpose: To identify the displayable name of the directory entity to
which information in the vCard pertains.
Value type: text
Cardinality: (0,1)
Special notes: The NAME property is used to convey the display name
of the entity to which the directory information pertains. Its
value is the displayable, presentation text associated with the
source for the vCard, as specified in the SOURCE property.
ABNF:
NAME-param = "VALUE=text" / any-param
NAME-value = text
Example:
NAME:Babs Jensen's Contact Information
6.1.5. KIND
Purpose: To specify the kind of object the vCard represents. Purpose: To specify the kind of object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,1) Cardinality: (0,1)
Special notes: The value may be one of: "individual" for a single Special notes: The value may be one of: "individual" for a single
person, "group" for a group, "org" for an organization, "location" person, "group" for a group, "org" for an organization, "location"
for a named geographical place, "thing" for an inanimate object for a named geographical place, "thing" for an inanimate object
skipping to change at page 26, line 28 skipping to change at page 27, line 27
This represents the department itself, commonly known as ABC This represents the department itself, commonly known as ABC
Marketing. Marketing.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:org KIND:org
FN:ABC Marketing FN:ABC Marketing
ORG:ABC, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
END:VCARD END:VCARD
6.1.6. XML 6.1.5. XML
Purpose: To include extended XML-encoded vCard data in a plain Purpose: To include extended XML-encoded vCard data in a plain
vCard. vCard.
Value type: A single text value (default) or a single binary value. Value type: A single text value (default) or a single binary value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The content of this property is a single XML element Special notes: The content of this property is a single XML element
whose namespace MUST be explicitly specified using the xmlns whose namespace MUST be explicitly specified using the xmlns
attribute and MUST NOT be the vCard 4 namespace attribute and MUST NOT be the vCard 4 namespace
("urn:ietf:params:xml:ns:vcard-4.0"). The element is to be ("urn:ietf:params:xml:ns:vcard-4.0"). The element is to be
interpreted as if it was contained in a <vcard> element, as interpreted as if it was contained in a <vcard> element, as
defined in [I-D.ietf-vcarddav-vcardxml]. defined in [I-D.ietf-vcarddav-vcardxml].
The fragment is subject to normal line folding and escaping, i.e. The fragment is subject to normal line folding and escaping, i.e.
replace all backslashes with "\\", then replace all newlines with replace all backslashes with "\\", then replace all newlines with
"\n", then fold long lines. "\n", then fold long lines.
The VERSION parameter (Section 5.11) indicates the XML version of The VERSION parameter (Section 5.12) indicates the XML version of
the property's content (e.g. "1.0"). It MUST be present. the property's content (e.g. "1.0"). It MUST be present.
The value type MAY be set to "binary", in which case the ENCODING The value type MAY be set to "binary", in which case the ENCODING
parameter (Section 5.2) MUST be used. parameter (Section 5.2) MUST be used.
Support for this property is OPTIONAL, but implementations of this Support for this property is OPTIONAL, but implementations of this
specification MUST preserve instances of this property when specification MUST preserve instances of this property when
propagating vCards. propagating vCards.
See [I-D.ietf-vcarddav-vcardxml] for more information on the See [I-D.ietf-vcarddav-vcardxml] for more information on the
skipping to change at page 27, line 27 skipping to change at page 28, line 27
XML-param = XML-text-param / XML-binary-param XML-param = XML-text-param / XML-binary-param
XML-value = XML-text-value / XML-binary-value XML-value = XML-text-value / XML-binary-value
; Value and parameter MUST match. ; Value and parameter MUST match.
XML-text-param = "VALUE=text" XML-text-param = "VALUE=text"
XML-text-value = text XML-text-value = text
XML-binary-param = "VALUE=binary" / encoding-param XML-binary-param = "VALUE=binary" / encoding-param
XML-binary-param = binary XML-binary-param = binary
XML-param =/ version-param XML-param =/ altid-param / version-param
; VERSION parameter MUST be present. ; VERSION parameter MUST be present.
6.2. Identification Properties 6.2. Identification Properties
These types are used to capture information associated with the These types are used to capture information associated with the
identification and naming of the person or resource associated with identification and naming of the person or resource associated with
the vCard. the vCard.
6.2.1. FN 6.2.1. FN
skipping to change at page 27, line 51 skipping to change at page 28, line 51
Value type: A single text value. Value type: A single text value.
Cardinality: (1,n) Cardinality: (1,n)
Special notes: This property is based on the semantics of the X.520 Special notes: This property is based on the semantics of the X.520
Common Name attribute. The property MUST be present in the vCard Common Name attribute. The property MUST be present in the vCard
object. object.
ABNF: ABNF:
FN-param = "VALUE=text" / type-param / language-param / pid-param FN-param = "VALUE=text" / type-param / language-param / altid-param
/ pref-param / any-param / pid-param / pref-param / any-param
FN-value = text FN-value = text
Example: Example:
FN:Mr. John Q. Public\, Esq. FN:Mr. John Q. Public\, Esq.
6.2.2. N 6.2.2. N
Purpose: To specify the components of the name of the object the Purpose: To specify the components of the name of the object the
skipping to change at page 28, line 36 skipping to change at page 29, line 36
separated by the COMMA character (ASCII decimal 44). This separated by the COMMA character (ASCII decimal 44). This
property is based on the semantics of the X.520 individual name property is based on the semantics of the X.520 individual name
attributes. The property SHOULD be present in the vCard object attributes. The property SHOULD be present in the vCard object
when the name of the object the vCard represents follows the X.520 when the name of the object the vCard represents follows the X.520
model. model.
The SORT-AS parameter MAY be applied to this property. The SORT-AS parameter MAY be applied to this property.
ABNF: ABNF:
N-param = "VALUE=text" / sort-as-param / language-param / any-param N-param = "VALUE=text" / sort-as-param / language-param
/ altid-param / any-param
N-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.
skipping to change at page 29, line 23 skipping to change at page 30, line 23
Cardinality: (0,n) Cardinality: (0,n)
Special note: The nickname is the descriptive name given instead of Special note: The nickname is the descriptive name given instead of
or in addition to the one belonging to a person, place, or thing. or in addition to the one belonging to a person, place, or thing.
It can also be used to specify a familiar form of a proper name It can also be used to specify a familiar form of a proper name
specified by the FN or N properties. specified by the FN or N properties.
ABNF: ABNF:
NICKNAME-param = "VALUE=text" / type-param / language-param NICKNAME-param = "VALUE=text" / type-param / language-param
/ pid-param / pref-param / any-param / altid-param / pid-param / pref-param / any-param
NICKNAME-value = text-list NICKNAME-value = text-list
Examples: Examples:
NICKNAME:Robbie NICKNAME:Robbie
NICKNAME:Jim,Jimmie NICKNAME:Jim,Jimmie
NICKNAME;TYPE=work:Boss NICKNAME;TYPE=work:Boss
skipping to change at page 30, line 13 skipping to change at page 31, line 13
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property SHOULD include the parameter FMTTYPE to Special notes: This property SHOULD include the parameter FMTTYPE to
specify the graphic image format type. The FMTTYPE parameter specify the graphic image format type. The FMTTYPE parameter
value MUST be an image media type as specified in [RFC4288]. The value MUST be an image media type as specified in [RFC4288]. The
full media type name, including the "image/" prefix, SHOULD be full media type name, including the "image/" prefix, SHOULD be
used. However, implementations SHOULD be able to handle bare used. However, implementations SHOULD be able to handle bare
subtypes. subtypes.
ABNF: ABNF:
PHOTO-param = inline-param / refer-param / type-param PHOTO-param = inline-param / refer-param / altid-param / type-param
PHOTO-value = inline-value / refer-value PHOTO-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
PHOTO-param =/ pid-param / pref-param / any-param PHOTO-param =/ pid-param / pref-param / any-param
inline-param = "VALUE=binary" / encoding-param / fmttype-param inline-param = "VALUE=binary" / encoding-param / fmttype-param
inline-value = binary inline-value = binary
refer-param = "VALUE=uri" / fmttype-param refer-param = "VALUE=uri" / fmttype-param
refer-value = uri refer-value = uri
skipping to change at page 30, line 46 skipping to change at page 32, line 5
Purpose: To specify the birth date of the object the vCard Purpose: To specify the birth date of the object the vCard
represents. represents.
Value type: The default is a single date-and-or-time value. It can Value type: The default is a single date-and-or-time value. It can
also be reset to a single text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
BDAY-param = "VALUE=" ("date-and-or-time" / "text") BDAY-param = BDAY-param-date / BDAY-param-text
BDAY-value = date-and-or-time / text BDAY-value = date-and-or-time / text
; Value and parameter MUST match. ; Value and parameter MUST match.
BDAY-param =/ calscale-param / any-param BDAY-param-date = "VALUE=date-and-or-time"
BDAY-param-text = "VALUE=text" / language-param
BDAY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when BDAY-value is ; calscale-param can only be present when BDAY-value is
; date-and-or-time and actually contains a date or date-time. ; date-and-or-time and actually contains a date or date-time.
Examples: Examples:
BDAY:19960415 BDAY:19960415
BDAY:--0415 BDAY:--0415
BDAY;19531015T231000Z BDAY;19531015T231000Z
BDAY;VALUE=text:circa 1800 BDAY;VALUE=text:circa 1800
skipping to change at page 31, line 25 skipping to change at page 32, line 35
Purpose: To specify the date of death of the object the vCard Purpose: To specify the date of death of the object the vCard
represents. represents.
Value type: The default is a single date-and-or-time value. It can Value type: The default is a single date-and-or-time value. It can
also be reset to a single text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
DDAY-param = "VALUE=" ("date-and-or-time" / "text") DDAY-param = DDAY-param-date / DDAY-param-text
DDAY-value = date-and-or-time / text DDAY-value = date-and-or-time / text
; Value and parameter MUST match. ; Value and parameter MUST match.
DDAY-param =/ calscale-param / any-param DDAY-param-date = "VALUE=date-and-or-time"
DDAY-param-text = "VALUE=text" / language-param
DDAY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when DDAY-value is ; calscale-param can only be present when DDAY-value is
; date-and-or-time and actually contains a date or date-time. ; date-and-or-time and actually contains a date or date-time.
6.2.7. BIRTH 6.2.7. BIRTH
Purpose: To specify the place of birth of the object the vCard Purpose: To specify the place of birth of the object the vCard
represents. represents.
Value type: A single text value (default) or a single URI value. Value type: A single text value (default) or a single URI value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
BIRTH-param = "VALUE=" / ("text" / "uri") BIRTH-param = "VALUE=" / ("text" / "uri")
BIRTH-value = text / uri BIRTH-value = text / uri
; Value and parameter MUST match. ; Value and parameter MUST match.
BIRTH-param =/ language-param / any-param BIRTH-param =/ altid-param / language-param / any-param
Examples: Examples:
BIRTH:Babies'R'Us Hospital BIRTH:Babies'R'Us Hospital
BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
BIRTH;VALUE=uri:geo:46.769307,-71.283079 BIRTH;VALUE=uri:geo:46.769307,-71.283079
6.2.8. DEATH 6.2.8. DEATH
skipping to change at page 32, line 28 skipping to change at page 33, line 40
Value type: A single text value (default) or a single URI value. Value type: A single text value (default) or a single URI value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
DEATH-param = "VALUE=" ("text / "uri") DEATH-param = "VALUE=" ("text / "uri")
DEATH-value = text / uri DEATH-value = text / uri
; Value and parameter MUST match. ; Value and parameter MUST match.
DEATH-param =/ language-param / any-param DEATH-param =/ altid-param / language-param / any-param
Examples: Examples:
DEATH:Aboard the Titanic\, near Newfoundland DEATH:Aboard the Titanic\, near Newfoundland
DEATH;VALUE=uri:http://example.com/ships/titanic.vcf DEATH;VALUE=uri:http://example.com/ships/titanic.vcf
DEATH;VALUE=uri:41.731944,-49.945833 DEATH;VALUE=uri:41.731944,-49.945833
6.2.9. ANNIVERSARY 6.2.9. ANNIVERSARY
skipping to change at page 33, line 9 skipping to change at page 34, line 21
also be reset to a single text value. also be reset to a single text value.
Cardinality: (0,1) Cardinality: (0,1)
ABNF: ABNF:
ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text") ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
ANNIVERSARY-value = date-and-or-time / text ANNIVERSARY-value = date-and-or-time / text
; Value and parameter MUST match. ; Value and parameter MUST match.
ANNIVERSARY-param =/ calscale-param / any-param ANNIVERSARY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when ANNIVERSARY-value is ; calscale-param can only be present when ANNIVERSARY-value is
; date-and-or-time and actually contains a date or date-time. ; date-and-or-time and actually contains a date or date-time.
Examples: Examples:
ANNIVERSARY:19960415 ANNIVERSARY:19960415
6.2.10. SEX 6.2.10. SEX
Purpose: To specify the sex of the object the vCard represents, as Purpose: To specify the sex of the object the vCard represents, as
skipping to change at page 34, line 31 skipping to change at page 35, line 44
The property can include the "PREF" parameter to indicate the The property can include the "PREF" parameter to indicate the
preferred delivery address when more than one address is preferred delivery address when more than one address is
specified. specified.
The GEO and TZ parameters MAY be used with this property. The GEO and TZ parameters MAY be used with this property.
ABNF: ABNF:
ADR-param = "VALUE=text" / language-param / geo-param / tz-param ADR-param = "VALUE=text" / language-param / geo-param / tz-param
/ pid-param / pref-param / type-param / any-param / altid-param / pid-param / pref-param / type-param
/ any-param
ADR-value = list-component 6(";" list-component) ADR-value = list-component 6(";" list-component)
Example: In this example the post office box and the extended address Example: In this example the post office box and the extended address
are absent. are absent.
ADR;GEO="geo:12.3457,78.910":;;123 Main Street;Any Town;CA ADR;GEO="geo:12.3457,78.910":;;123 Main Street;Any Town;CA
;91921-1234;USA ;91921-1234;USA
6.3.2. LABEL 6.3.2. LABEL
skipping to change at page 35, line 9 skipping to change at page 36, line 23
Special notes: The property value is formatted text that can be used Special notes: The property value is formatted text that can be used
to present a delivery address label for the vCard object. The to present a delivery address label for the vCard object. The
property can include the "PREF" parameter to indicate the property can include the "PREF" parameter to indicate the
preferred delivery address when more than one address is preferred delivery address when more than one address is
specified. specified.
ABNF: ABNF:
LABEL-param = "VALUE=text" / language-param / pid-param LABEL-param = "VALUE=text" / language-param / pid-param
/ pref-param / type-param / any-param / pref-param / altid-param / type-param / any-param
LABEL-value = text LABEL-value = text
Example: A multi-line address label. Example: A multi-line address label.
LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n LABEL:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n
123 Main Street\nAny Town\, CA 91921-1234\nU.S.A. 123 Main Street\nAny Town\, CA 91921-1234\nU.S.A.
6.4. Communications Properties 6.4. Communications Properties
These properties are concerned with information associated with the These properties are concerned with information associated with the
skipping to change at page 36, line 11 skipping to change at page 37, line 27
parameter values can be specified as a parameter list (e.g., parameter values can be specified as a parameter list (e.g.,
"TYPE=text;TYPE=voice") or as a value list (e.g., "TYPE=text;TYPE=voice") or as a value list (e.g.,
"TYPE=text,voice"). The default can be overridden to another set "TYPE=text,voice"). The default can be overridden to another set
of values by specifying one or more alternate values. For of values by specifying one or more alternate values. For
example, the default TYPE of "voice" can be reset to a VOICE and example, the default TYPE of "voice" can be reset to a VOICE and
FAX telephone number by the value list "TYPE=voice,fax". FAX telephone number by the value list "TYPE=voice,fax".
ABNF: ABNF:
TEL-param = "VALUE=uri" / type-param / pid-param / pref-param TEL-param = "VALUE=uri" / type-param / pid-param / pref-param
/ any-param / altid-param / any-param
TEL-value = uri TEL-value = uri
type-param-tel = "text" / "voice" / "fax" / "cell" / "video" type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / "textphone" / iana-token / x-name / "pager" / "textphone" / iana-token / x-name
; type-param-tel MUST NOT be used with a property other than TEL. ; type-param-tel MUST NOT be used with a property other than TEL.
Example: Example:
TEL;PREF=1;TYPE=voice,msg,home:tel:+1-555-555-5555;ext=5555 TEL;PREF=1;TYPE=voice,msg,home:tel:+1-555-555-5555;ext=5555
TEL;TYPE=home:tel:+33-01-23-45-67 TEL;TYPE=home:tel:+33-01-23-45-67
skipping to change at page 36, line 39 skipping to change at page 38, line 8
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property can include tye "PREF" parameter to Special notes: The property can include tye "PREF" parameter to
indicate a preferred-use email address when more than one is indicate a preferred-use email address when more than one is
specified. specified.
ABNF: ABNF:
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
EMAIL-value = addr-spec ; from [RFC5322] section 3.4.1 EMAIL-value = addr-spec ; from [RFC5322] section 3.4.1
Type example: Type example:
EMAIL;TYPE=work:jqpublic@xyz.example.com EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;PREF=1:jane_doe@example.com EMAIL;PREF=1:jane_doe@example.com
6.4.3. IMPP 6.4.3. IMPP
skipping to change at page 37, line 24 skipping to change at page 38, line 36
Special notes: The property may include the "PREF" parameter to Special notes: The property may include the "PREF" parameter to
indicate that this is a preferred address and has the same indicate that this is a preferred address and has the same
semantics as the "PREF" parameter in a TEL property. semantics as the "PREF" parameter in a TEL property.
This property is adapted from [RFC4770], which is made obsolete by This property is adapted from [RFC4770], which is made obsolete by
this document. this document.
ABNF: ABNF:
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
IMPP-value = uri IMPP-value = uri
Example: Example:
IMPP;PREF=1:xmpp:alice@example.com IMPP;PREF=1:xmpp:alice@example.com
6.4.4. LANG 6.4.4. LANG
Purpose: To specify the language(s) that may be used for contacting Purpose: To specify the language(s) that may be used for contacting
the individual associated with the vCard. the individual associated with the vCard.
Value type: A single language-tag value. Value type: A single language-tag value.
Cardinality: (0,n) Cardinality: (0,n)
ABNF: ABNF:
LANG-param = "VALUE=language-tag" / pid-param / pref-param LANG-param = "VALUE=language-tag" / pid-param / pref-param
/ type-param / any-param / altid-param / type-param / any-param
LANG-value = Language-Tag LANG-value = Language-Tag
Example: Example:
LANG;TYPE=work;PREF=1:en LANG;TYPE=work;PREF=1:en
LANG;TYPE=work;PREF=2:fr LANG;TYPE=work;PREF=2:fr
LANG;TYPE=home:fr LANG;TYPE=home:fr
6.5. Geographical Properties 6.5. Geographical Properties
skipping to change at page 38, line 42 skipping to change at page 40, line 11
saving time shifts that occur in may regions, but often entire saving time shifts that occur in may regions, but often entire
regions will "re-base" their overall offset. The actual offset regions will "re-base" their overall offset. The actual offset
may be +/- 1 hour (or perhaps a little more) than the one given. may be +/- 1 hour (or perhaps a little more) than the one given.
ABNF: ABNF:
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset") TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / uri / utc-offset TZ-value = text / uri / utc-offset
; Value and parameter MUST match ; Value and parameter MUST match
TZ-param =/ pid-param / pref-param / type-param / any-param TZ-param =/ altid-param / pid-param / pref-param / type-param
/ any-param
Examples: Examples:
TZ:Raleigh/North America TZ:Raleigh/North America
TZ;VALUE=utc-offset:-0500 TZ;VALUE=utc-offset:-0500
; Note: utc-offset format is NOT RECOMMENDED. ; Note: utc-offset format is NOT RECOMMENDED.
6.5.2. GEO 6.5.2. GEO
skipping to change at page 39, line 20 skipping to change at page 40, line 36
Value type: A single URI. Value type: A single URI.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The "geo" URI scheme [RFC5870] is particularly well- Special notes: The "geo" URI scheme [RFC5870] is particularly well-
suited for this property, but other schemes MAY be used. suited for this property, but other schemes MAY be used.
ABNF: ABNF:
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
GEO-value = uri GEO-value = uri
Example: Example:
GEO:geo:37.386013,-122.082932 GEO:geo:37.386013,-122.082932
6.6. Organizational Properties 6.6. Organizational Properties
These properties are concerned with information associated with These properties are concerned with information associated with
characteristics of the organization or organizational units of the characteristics of the organization or organizational units of the
skipping to change at page 39, line 47 skipping to change at page 41, line 16
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: This property is based on the X.520 Title attribute. Special notes: This property is based on the X.520 Title attribute.
ABNF: ABNF:
TITLE-param = "VALUE=text" / language-param / pid-param TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / type-param / any-param / pref-param / altid-param / type-param / any-param
TITLE-value = text TITLE-value = text
Example: Example:
TITLE:Research Scientist TITLE:Research Scientist
6.6.2. ROLE 6.6.2. ROLE
Purpose: To specify the function or part played in a particular Purpose: To specify the function or part played in a particular
situation by the object the vCard represents. situation by the object the vCard represents.
skipping to change at page 40, line 23 skipping to change at page 41, line 41
Special notes: This property is based on the X.520 Business Category Special notes: This property is based on the X.520 Business Category
explanatory attribute. This property is included as an explanatory attribute. This property is included as an
organizational type to avoid confusion with the semantics of the organizational type to avoid confusion with the semantics of the
TITLE property and incorrect usage of that property when the TITLE property and incorrect usage of that property when the
semantics of this property is intended. semantics of this property is intended.
ABNF: ABNF:
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / any-param / type-param / altid-param / any-param
ROLE-value = text ROLE-value = text
Example: Example:
ROLE:Project Leader ROLE:Project Leader
6.6.3. LOGO 6.6.3. LOGO
Purpose: To specify a graphic image of a logo associated with the Purpose: To specify a graphic image of a logo associated with the
object the vCard represents. object the vCard represents.
skipping to change at page 41, line 12 skipping to change at page 42, line 35
used. However, implementations SHOULD be able to handle bare used. However, implementations SHOULD be able to handle bare
subtypes. subtypes.
ABNF: ABNF:
LOGO-param = inline-param / refer-param LOGO-param = inline-param / refer-param
LOGO-value = inline-value / refer-value LOGO-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
LOGO-param =/ language-param / pid-param / pref-param / type-param LOGO-param =/ language-param / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
Examples: Examples:
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;FMTTYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJ LOGO;ENCODING=b;FMTTYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJ
KoZAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW1 KoZAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW1
1bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTe 1bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTe
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
skipping to change at page 41, line 43 skipping to change at page 43, line 20
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.
The SORT-AS parameter MAY be applied to this property. The SORT-AS parameter MAY be applied to this property.
ABNF: ABNF:
ORG-param = "VALUE=text" / sort-as-param / language-param ORG-param = "VALUE=text" / sort-as-param / language-param
/ pid-param / pref-param / type-param / any-param / pid-param / pref-param / altid-param / type-param
/ any-param
ORG-value = component *(";" component) ORG-value = component *(";" component)
component = "\\" / "\;" / "\n" / WSP / NON-ASCII component = "\\" / "\;" / "\n" / WSP / NON-ASCII
/ %x21-3A / %x3C-5B / %x5D-7E / %x21-3A / %x3C-5B / %x5D-7E
Example: A property value consisting of an organizational name, Example: A property value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name. organizational unit #1 name and organizational unit #2 name.
ORG:ABC, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
skipping to change at page 42, line 20 skipping to change at page 43, line 47
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:
MEMBER-param = "VALUE=uri" / pid-param / pref-param / any-param MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ any-param
MEMBER-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
skipping to change at page 44, line 7 skipping to change at page 45, line 33
* "agent" for a person who may sometimes act on behalf of the * "agent" for a person who may sometimes act on behalf of the
individual or resource associated with the vCard. individual 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 10.2, and private extensions may be used. Section 10.2, and private extensions may be used.
ABNF: ABNF:
RELATED-param = "VALUE=" ("uri" / "text") RELATED-param = RELATED-param-uri / RELATED-param-text
RELATED-value = uri / text RELATED-value = uri / text
; Parameter and value MUST match. ; Parameter and value MUST match.
RELATED-param =/ type-param / pid-param / pref-param / type-param RELATED-param-uri = "VALUE=uri"
RELATED-param-text = "VALUE=text" / language-param
RELATED-param =/ pid-param / pref-param / altid-param / type-param
/ any-param / any-param
type-param-related = "parent" / "child" / "sibling" / "spouse" type-param-related = "parent" / "child" / "sibling" / "spouse"
/ "family" / "friend" / "supervisor" / "family" / "friend" / "supervisor"
/ "supervisee" / "assistant" / "colleague" / "supervisee" / "assistant" / "colleague"
/ "agent" / "emergency" / iana-token / x-name / "agent" / "emergency" / iana-token / x-name
; type-param-related MUST NOT be used with a property other than ; type-param-related MUST NOT be used with a property other than
; RELATED. ; RELATED.
Examples: Examples:
skipping to change at page 44, line 47 skipping to change at page 46, line 29
vCard. Also known as "tags". vCard. Also known as "tags".
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Cardinality: (0,n) Cardinality: (0,n)
ABNF: ABNF:
CATEGORIES-param = "VALUE=text" / pid-param / pref-param CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ type-param / any-param / type-param / altid-param / any-param
CATEGORIES-value = text-list CATEGORIES-value = text-list
Example: Example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
6.7.2. NOTE 6.7.2. NOTE
skipping to change at page 45, line 24 skipping to change at page 47, line 8
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property is based on the X.520 Description Special notes: The property is based on the X.520 Description
attribute. attribute.
ABNF: ABNF:
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / any-param / type-param / altid-param / any-param
NOTE-value = text NOTE-value = text
Example: Example:
NOTE:This fax number is operational 0800 to 1715 NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri. EST\, Mon-Fri.
6.7.3. PRODID 6.7.3. PRODID
Purpose: To specify the identifier for the product that created the Purpose: To specify the identifier for the product that created the
skipping to change at page 47, line 12 skipping to change at page 48, line 45
type name, including the "audio/" prefix, SHOULD be used. type name, including the "audio/" prefix, SHOULD be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
ABNF: ABNF:
SOUND-param = inline-param / refer-param SOUND-param = inline-param / refer-param
SOUND-value = inline-value / refer-value SOUND-value = inline-value / refer-value
; Value and parameter MUST match. ; Value and parameter MUST match.
SOUND-param =/ language-param / pid-param / pref-param / type-param SOUND-param =/ language-param / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
Example: Example:
SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8. SOUND;FMTTYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@example.com 19960229T080000.xyzMail@example.com
SOUND;FMTTYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQ SOUND;FMTTYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQ
YJKAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW1 YJKAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW1
1bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTe 1bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTe
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
6.7.6. UID 6.7.6. UID
Purpose: To specify a value that represents a globally unique Purpose: To specify a value that represents a globally unique
skipping to change at page 49, line 8 skipping to change at page 50, line 38
object that the vCard refers to. Examples for individuals include object that the vCard refers to. Examples for individuals include
personal web sites, blogs, and social networking site identifiers. personal web sites, blogs, and social networking site identifiers.
Cardinality: (0,n) Cardinality: (0,n)
Value type: A single uri value. Value type: A single uri value.
ABNF: ABNF:
URL-param = "VALUE=uri" / pid-param / pref-param / type-param URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
URL-value = uri URL-value = uri
Example: Example:
URL:http://example.org/restaurant.french/~chezchic.html URL:http://example.org/restaurant.french/~chezchic.html
6.7.9. VERSION 6.7.9. 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.
skipping to change at page 51, line 21 skipping to change at page 52, line 51
ABNF: ABNF:
KEY-param = inline-param / refer-param / KEY-text-param KEY-param = inline-param / refer-param / KEY-text-param
KEY-value = inline-value / refer-value / KEY-text-value KEY-value = inline-value / refer-value / KEY-text-value
; Value and parameter MUST match. ; Value and parameter MUST match.
KEY-text-param = "VALUE=text" KEY-text-param = "VALUE=text"
KEY-text-value = text KEY-text-value = text
KEY-param =/ pid-param / pref-param / type-param / any-param KEY-param =/ altid-param / pid-param / pref-param / type-param
/ any-param
Examples: Examples:
KEY;VALUE=uri:http://www.example.com/keys/jdoe KEY;VALUE=uri:http://www.example.com/keys/jdoe
KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN KEY;FMTTYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0R
mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g SINmGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+
7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8 J2g7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/x
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
6.9. Calendar Properties 6.9. Calendar Properties
These properties are further specified in [RFC2739]. These properties are further specified in [RFC2739].
6.9.1. FBURL 6.9.1. FBURL
Purpose: To specify the URI for the busy time associated with the Purpose: To specify the URI for the busy time associated with the
object that the vCard represents. object that the vCard represents.
skipping to change at page 52, line 8 skipping to change at page 53, line 37
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 [RFC5545] object FTP or HTTP type of URI points to an iCalendar [RFC5545] object
associated with a snapshot of the next few weeks or months of busy associated with a snapshot of the next few weeks or months of busy
time data. If the iCalendar object is represented as a file or time data. If the iCalendar object is represented as a file or
document, its file type should be "ifb". document, its file type should be "ifb".
ABNF: ABNF:
FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
FBURL-value = uri FBURL-value = uri
Examples: Examples:
FBURL;PREF=1:http://www.example.com/busy/janedoe FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL:FTP://ftp.example.com/busy/project-a.ifb FBURL:FTP://ftp.example.com/busy/project-a.ifb
6.9.2. CALADRURI 6.9.2. CALADRURI
Purpose: To specify the calendar user address [RFC5545] to which a Purpose: To specify the calendar user address [RFC5545] to which a
skipping to change at page 52, line 33 skipping to change at page 54, line 16
Cardinality: (0,n) Cardinality: (0,n)
Special notes: Where multiple CALADRURI properties are specified, Special notes: Where multiple CALADRURI properties are specified,
the default CALADRURI property is indicated with the PREF the default CALADRURI property is indicated with the PREF
parameter. parameter.
ABNF: ABNF:
CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
CALADRURI-value = uri CALADRURI-value = uri
Example: Example:
CALADRURI;PREF=1:mailto:janedoe@example.com CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe CALADRURI:http://example.com/calendar/jdoe
6.9.3. CALURI 6.9.3. CALURI
Purpose: To specify the URI for a calendar associated with the Purpose: To specify the URI for a calendar associated with the
skipping to change at page 53, line 14 skipping to change at page 54, line 43
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 [RFC5545] property should contain a URI pointing to an iCalendar [RFC5545]
object associated with a snapshot of the user's calendar store. object associated with a snapshot of the user's calendar store.
If the iCalendar object is represented as a file or document, its If the iCalendar object is represented as a file or document, its
file type should be "ics". file type should be "ics".
ABNF: ABNF:
CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ any-param / altid-param / any-param
CALURI-value = uri CALURI-value = uri
Examples: Examples:
CALURI;PREF=1:http://cal.example.com/calA CALURI;PREF=1:http://cal.example.com/calA
CALURI:ftp://ftp.example.com/calA.ics CALURI:ftp://ftp.example.com/calA.ics
6.10. Extended Properties and Parameters 6.10. Extended Properties and Parameters
The properties and parameters defined by this document can be The properties and parameters defined by this document can be
skipping to change at page 61, line 18 skipping to change at page 62, line 25
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-12 Published specification: draft-ietf-vcarddav-vcardrev-13
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 66, line 9 skipping to change at page 67, line 9
10.3.1. Properties Registry 10.3.1. Properties Registry
The following table is to be used to initialize the properties The following table is to be used to initialize the properties
registry. registry.
+-----------+--------------+---------+-------------------------+ +-----------+--------------+---------+-------------------------+
| Namespace | Property | Status | Reference | | Namespace | Property | Status | Reference |
+-----------+--------------+---------+-------------------------+ +-----------+--------------+---------+-------------------------+
| | SOURCE | Current | RFCXXXX, Section 6.1.3 | | | SOURCE | Current | RFCXXXX, Section 6.1.3 |
| | NAME | Current | RFCXXXX, Section 6.1.4 | | | KIND | Current | RFCXXXX, Section 6.1.4 |
| | KIND | Current | RFCXXXX, Section 6.1.5 | | | XML | Current | RFCXXXX, Section 6.1.5 |
| | XML | Current | RFCXXXX, Section 6.1.6 |
| | FN | Current | RFCXXXX, Section 6.2.1 | | | FN | Current | RFCXXXX, Section 6.2.1 |
| | N | Current | RFCXXXX, Section 6.2.2 | | | N | Current | RFCXXXX, Section 6.2.2 |
| | NICKNAME | Current | RFCXXXX, Section 6.2.3 | | | NICKNAME | Current | RFCXXXX, Section 6.2.3 |
| | PHOTO | Current | RFCXXXX, Section 6.2.4 | | | PHOTO | Current | RFCXXXX, Section 6.2.4 |
| | BDAY | Current | RFCXXXX, Section 6.2.5 | | | BDAY | Current | RFCXXXX, Section 6.2.5 |
| | DDAY | Current | RFCXXXX, Section 6.2.6 | | | DDAY | Current | RFCXXXX, Section 6.2.6 |
| | BIRTH | Current | RFCXXXX, Section 6.2.7 | | | BIRTH | Current | RFCXXXX, Section 6.2.7 |
| | DEATH | Current | RFCXXXX, Section 6.2.8 | | | DEATH | Current | RFCXXXX, Section 6.2.8 |
| | ANNIVERSARY | Current | RFCXXXX, Section 6.2.9 | | | ANNIVERSARY | Current | RFCXXXX, Section 6.2.9 |
| | SEX | Current | RFCXXXX, Section 6.2.10 | | | SEX | Current | RFCXXXX, Section 6.2.10 |
skipping to change at page 67, line 17 skipping to change at page 68, line 17
The following table is to be used to initialize the parameters The following table is to be used to initialize the parameters
registry. registry.
+-----------+-----------+---------+-----------------------+ +-----------+-----------+---------+-----------------------+
| Namespace | Parameter | Status | Reference | | Namespace | Parameter | Status | Reference |
+-----------+-----------+---------+-----------------------+ +-----------+-----------+---------+-----------------------+
| | LANGUAGE | Current | RFCXXXX, Section 5.1 | | | LANGUAGE | Current | RFCXXXX, Section 5.1 |
| | ENCODING | Current | RFCXXXX, Section 5.2 | | | ENCODING | Current | RFCXXXX, Section 5.2 |
| | VALUE | Current | RFCXXXX, Section 5.3 | | | VALUE | Current | RFCXXXX, Section 5.3 |
| | PREF | Current | RFCXXXX, Section 5.4 | | | PREF | Current | RFCXXXX, Section 5.4 |
| | PID | Current | RFCXXXX, Section 5.5 | | | ALTID | Current | RFCXXXX, Section 5.5 |
| | TYPE | Current | RFCXXXX, Section 5.6 | | | PID | Current | RFCXXXX, Section 5.6 |
| | CALSCALE | Current | RFCXXXX, Section 5.7 | | | TYPE | Current | RFCXXXX, Section 5.7 |
| | SORT-AS | Current | RFCXXXX, Section 5.8 | | | CALSCALE | Current | RFCXXXX, Section 5.8 |
| | GEO | Current | RFCXXXX, Section 5.9 | | | SORT-AS | Current | RFCXXXX, Section 5.9 |
| | TZ | Current | RFCXXXX, Section 5.10 | | | GEO | Current | RFCXXXX, Section 5.10 |
| | VERSION | Current | RFCXXXX, Section 5.11 | | | TZ | Current | RFCXXXX, Section 5.11 |
| | FMTTYPE | Current | RFCXXXX, Section 5.12 | | | VERSION | Current | RFCXXXX, Section 5.12 |
| | FMTTYPE | Current | RFCXXXX, Section 5.13 |
+-----------+-----------+---------+-----------------------+ +-----------+-----------+---------+-----------------------+
10.3.3. Value Data Types Registry 10.3.3. Value Data Types Registry
The following table is to be used to initialize the parameters The following table is to be used to initialize the parameters
registry. registry.
+------------------+---------+------------------------+ +------------------+---------+------------------------+
| Value Data Type | Status | Reference | | Value Data Type | Status | Reference |
+------------------+---------+------------------------+ +------------------+---------+------------------------+
skipping to change at page 68, line 17 skipping to change at page 69, line 17
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 6.1.1 | | BEGIN | VCARD | Current | RFCXXXX, Section 6.1.1 |
| END | VCARD | Current | RFCXXXX, Section 6.1.2 | | END | VCARD | Current | RFCXXXX, Section 6.1.2 |
| KIND | individual | Current | RFCXXXX, Section 6.1.5 | | KIND | individual | Current | RFCXXXX, Section 6.1.4 |
| KIND | group | Current | RFCXXXX, Section 6.1.5 | | KIND | group | Current | RFCXXXX, Section 6.1.4 |
| KIND | org | Current | RFCXXXX, Section 6.1.5 | | KIND | org | Current | RFCXXXX, Section 6.1.4 |
| KIND | location | Current | RFCXXXX, Section 6.1.5 | | KIND | location | Current | RFCXXXX, Section 6.1.4 |
| KIND | thing | Current | RFCXXXX, Section 6.1.5 | | KIND | thing | Current | RFCXXXX, Section 6.1.4 |
| CLASS | PUBLIC | Current | RFCXXXX, Section 6.8.1 | | CLASS | PUBLIC | Current | RFCXXXX, Section 6.8.1 |
| CLASS | PRIVATE | Current | RFCXXXX, Section 6.8.1 | | CLASS | PRIVATE | Current | RFCXXXX, Section 6.8.1 |
| CLASS | CONFIDENTIAL | Current | RFCXXXX, Section 6.8.1 | | CLASS | CONFIDENTIAL | Current | RFCXXXX, Section 6.8.1 |
+----------+--------------+---------+------------------------+ +----------+--------------+---------+------------------------+
The following table is to be used to initialize the parameter values The following table is to be used to initialize the parameter values
registry. registry.
+----------------+-----------+------------+---------+---------------+ +----------------+-----------+------------+---------+---------------+
| Property | Parameter | Value | Status | Reference | | Property | Parameter | Value | Status | Reference |
+----------------+-----------+------------+---------+---------------+ +----------------+-----------+------------+---------+---------------+
| FN, NICKNAME, | TYPE | work | Current | RFCXXXX, | | FN, NICKNAME, | TYPE | work | Current | RFCXXXX, |
| PHOTO, ADR, | | | | Section 5.6 | | PHOTO, ADR, | | | | Section 5.7 |
| LABEL, TEL, | | | | | | LABEL, TEL, | | | | |
| EMAIL, IMPP, | | | | | | EMAIL, IMPP, | | | | |
| LANG, TZ, GEO, | | | | | | LANG, TZ, GEO, | | | | |
| TITLE, ROLE, | | | | | | TITLE, ROLE, | | | | |
| LOGO, ORG, | | | | | | LOGO, ORG, | | | | |
| RELATED, | | | | | | RELATED, | | | | |
| CATEGORIES, | | | | | | CATEGORIES, | | | | |
| NOTE, SOUND, | | | | | | NOTE, SOUND, | | | | |
| URL, KEY, | | | | | | URL, KEY, | | | | |
| FIBURL, | | | | | | FIBURL, | | | | |
| CALADRURI, and | | | | | | CALADRURI, and | | | | |
| CALURI | | | | | | CALURI | | | | |
| FN, NICKNAME, | TYPE | home | Current | RFCXXXX, | | FN, NICKNAME, | TYPE | home | Current | RFCXXXX, |
| PHOTO, ADR, | | | | Section 5.6 | | PHOTO, ADR, | | | | Section 5.7 |
| LABEL, TEL, | | | | | | LABEL, TEL, | | | | |
| EMAIL, IMPP, | | | | | | EMAIL, IMPP, | | | | |
| LANG, TZ, GEO, | | | | | | LANG, TZ, GEO, | | | | |
| TITLE, ROLE, | | | | | | TITLE, ROLE, | | | | |
| LOGO, ORG, | | | | | | LOGO, ORG, | | | | |
| RELATED, | | | | | | RELATED, | | | | |
| CATEGORIES, | | | | | | CATEGORIES, | | | | |
| NOTE, SOUND, | | | | | | NOTE, SOUND, | | | | |
| URL, KEY, | | | | | | URL, KEY, | | | | |
| FIBURL, | | | | | | FIBURL, | | | | |
skipping to change at page 74, line 40 skipping to change at page 75, line 40
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.
A.2. Removed Features A.2. Removed Features
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 NAME and MAILER properties are 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.
skipping to change at page 75, line 22 skipping to change at page 76, line 22
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
own, with a positive integer value indicating the level of own, with a positive integer value indicating the level of
preference. preference.
o The PID parameter has been added. o The ALTID and PID parameters have been added.
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 -12 B.1. Changes in -13
o Changed global ABNF to make explicit that VERSION comes first.
o Reworked example for LANGUAGE property.
o s/TYPE/FMTTYPE/ in two examples.
o Allow LANGUAGE parameter for text-valued BDAY, DDAY, and RELATED.
o Tightened language on LANGUAGE parameter regarding cardinality.
o Removed the NAME property.
o Adjusted semi-colon escaping rules.
o Added the ALTID parameter.
B.2. 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 76, line 44 skipping to change at page 78, line 15
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.2. Changes in -11 B.3. 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 77, line 21 skipping to change at page 78, line 39
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.3. Changes in -10 B.4. 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.4. Changes in -09 B.5. 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.5. Changes in -08 B.6. 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 78, line 28 skipping to change at page 79, line 47
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.6. Changes in -07 B.7. 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 79, line 5 skipping to change at page 80, line 21
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.7. Changes in -06 B.8. 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 79, line 44 skipping to change at page 81, line 13
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.8. Changes in -05 B.9. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.9. Changes in -04 B.10. 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 80, line 31 skipping to change at page 81, line 47
o Removed TYPE parameter from EMAIL and IMPP properties. o Removed TYPE parameter from EMAIL and IMPP properties.
o Replaced AGENT with a type of RELATED. o Replaced AGENT with a type of RELATED.
o Use example.org domain in URL example. o Use example.org domain in URL example.
o Created initial IANA table of values. o Created initial IANA table of values.
o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL. o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.
B.10. Changes in -03 B.11. 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.11. Changes in -02 B.12. 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 81, line 23 skipping to change at page 82, line 38
o Changed the presence of UID and PID when synchronization is to be o Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD. used from MUST to SHOULD.
o Added the RELATED (Section 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.12. Changes in -01 B.13. 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 82, line 5 skipping to change at page 83, line 18
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.13. Changes in -00 B.14. 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. 90 change blocks. 
266 lines changed or deleted 324 lines changed or added

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