draft-ietf-vcarddav-vcardrev-22.txt   rfc6350.txt 
Network Working Group S. Perreault Internet Engineering Task Force (IETF) S. Perreault
Internet-Draft Viagenie Request for Comments: 6350 Viagenie
Obsoletes: 2425, 2426, 4770 May 26, 2011 Obsoletes: 2425, 2426, 4770 August 2011
(if approved) Updates: 2739
Updates: 2739 (if approved) Category: Standards Track
Intended status: Standards Track ISSN: 2070-1721
Expires: November 27, 2011
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-22
Abstract Abstract
This document defines the vCard data format for representing and This document defines the vCard data format for representing and
exchanging a variety of information about individuals and other exchanging a variety of information about individuals and other
entities (e.g., formatted and structured name and delivery addresses, entities (e.g., formatted and structured name and delivery addresses,
email address, multiple telephone numbers, photograph, logo, audio email address, multiple telephone numbers, photograph, logo, audio
clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and
updates RFC 2739. updates RFC 2739.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on November 27, 2011. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6350.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 19
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. vCard Format Specification . . . . . . . . . . . . . . . . . . 6 3. vCard Format Specification . . . . . . . . . . . . . . . . . . 5
3.1. Charset . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Charset . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 6 3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 5
3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7 3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 6
3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 10 3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 9
4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10 4. Property Value Data Types . . . . . . . . . . . . . . . . . . 9
4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 13 4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 12
4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 14 4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 13
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 . . . . . . . . . . . . . . . . . . . . . . 14
4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.7. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 16 4.7. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 15
4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16 4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16
5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16 5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16
5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.2. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.3. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.4. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.4. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.7. MEDIATYPE . . . . . . . . . . . . . . . . . . . . . . . . 21 5.7. MEDIATYPE . . . . . . . . . . . . . . . . . . . . . . . . 20
5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. General Properties . . . . . . . . . . . . . . . . . . . . 24
6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2. Identification Properties . . . . . . . . . . . . . . . . 29
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 32
6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 33
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 34
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4. Communications Properties . . . . . . . . . . . . . . . . 35
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 37
6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.5. Geographical Properties . . . . . . . . . . . . . . . . . 39
6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6. Organizational Properties . . . . . . . . . . . . . . . . 40
6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 43
6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 44
6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 45
6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 45
6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 48
6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 50
6.8. Security Properties . . . . . . . . . . . . . . . . . . . 50
6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 51 6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 23
6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 51 6.1. General Properties . . . . . . . . . . . . . . . . . . . . 23
6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 52 6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 23
6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 52 6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.10. Extended Properties and Parameters . . . . . . . . . . . . 53 6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 24
7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 53 6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 53 6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 53 6.2. Identification Properties . . . . . . . . . . . . . . . . 28
7.1.2. Matching Property Instances . . . . . . . . . . . . . 54 6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 54 6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 55 6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 29
7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 55 6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 55 6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 56 6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 31
7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 56 6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 32
7.2.5. Global Context Simplification . . . . . . . . . . . . 58 6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 32
8. Example: Author's vCard . . . . . . . . . . . . . . . . . . . 59 6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 32
9. Security Considerations . . . . . . . . . . . . . . . . . . . 59 6.4. Communications Properties . . . . . . . . . . . . . . . . 34
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 34
10.1. Media Type Registration . . . . . . . . . . . . . . . . . 60 6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 36
10.2. Registering New vCard Elements . . . . . . . . . . . . . . 61 6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 36
10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 61 6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 37
10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 62 6.5. Geographical Properties . . . . . . . . . . . . . . . . . 37
10.2.3. Registration Template for Properties . . . . . . . . . 63 6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 37
10.2.4. Registration Template for Parameters . . . . . . . . . 63 6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.2.5. Registration Template for Value Data Types . . . . . . 64 6.6. Organizational Properties . . . . . . . . . . . . . . . . 39
10.2.6. Registration Template for Values . . . . . . . . . . . 64 6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 39
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 65 6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 65 6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 40
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 66 6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 40
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 67 6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 41
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 67 6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 42
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70 6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 43
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 43
12.1. Normative References . . . . . . . . . . . . . . . . . . . 70 6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 44
12.2. Informative References . . . . . . . . . . . . . . . . . . 73 6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 75 6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 45
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 75 6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 45
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 76 6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 46
A.3. New Properties and Parameters . . . . . . . . . . . . . . 76 6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 47
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 76 6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 47
Appendix B. Change Log (to be removed by RFC Editor prior to 6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 48
publication) . . . . . . . . . . . . . . . . . . . . 77 6.8. Security Properties . . . . . . . . . . . . . . . . . . . 48
B.1. Changes in -22 . . . . . . . . . . . . . . . . . . . . . . 77 6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 48
B.2. Changes in -21 . . . . . . . . . . . . . . . . . . . . . . 77 6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 49
B.3. Changes in -20 . . . . . . . . . . . . . . . . . . . . . . 77 6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 49
B.4. Changes in -19 . . . . . . . . . . . . . . . . . . . . . . 78 6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 50
B.5. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 78 6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 50
B.6. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 78
B.7. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 79 6.10. Extended Properties and Parameters . . . . . . . . . . . . 51
B.8. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 79 7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 51
B.9. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 80 7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 51
B.10. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 81 7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 51
B.11. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 81 7.1.2. Matching Property Instances . . . . . . . . . . . . . 52
B.12. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 82 7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 52
B.13. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 83 7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 53
B.14. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 83 7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 53
B.15. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 83 7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 53
B.16. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 84 7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 54
B.17. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 84 7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 54
B.18. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 85 7.2.5. Global Context Simplification . . . . . . . . . . . . 56
B.19. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 85 8. Example: Author's vCard . . . . . . . . . . . . . . . . . . . 56
B.20. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 86 9. Security Considerations . . . . . . . . . . . . . . . . . . . 57
B.21. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 86 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58
B.22. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 87 10.1. Media Type Registration . . . . . . . . . . . . . . . . . 58
B.23. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 87 10.2. Registering New vCard Elements . . . . . . . . . . . . . . 59
10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 59
10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 60
10.2.3. Registration Template for Properties . . . . . . . . . 61
10.2.4. Registration Template for Parameters . . . . . . . . . 61
10.2.5. Registration Template for Value Data Types . . . . . . 62
10.2.6. Registration Template for Values . . . . . . . . . . . 62
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 63
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 64
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 65
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 65
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 66
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69
12.2. Informative References . . . . . . . . . . . . . . . . . . 71
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 73
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 73
A.3. New Properties and Parameters . . . . . . . . . . . . . . 73
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 that exchange 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.
A high-level overview of the differences from RFCs 2425 and 2426 can A high-level overview of the differences from RFCs 2425 and 2426 can
be found in Appendix A. be found in Appendix A.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
3. vCard Format Specification 3. vCard Format Specification
The text/vcard MIME content type (hereafter known as "vCard", see The text/vcard MIME content type (hereafter known as "vCard"; see
Section 10.1) contains contact information, typically pertaining to a Section 10.1) contains contact information, typically pertaining to a
single contact or group of contacts. The content consists of one or single contact or group of contacts. The content consists of one or
more lines in the format given below. more lines in the format given below.
3.1. Charset 3.1. Charset
The charset (see [RFC3536] for internationalization terminology) for The charset (see [RFC3536] for internationalization terminology) for
vCard is UTF-8 as defined in [RFC3629]. There is no way to override vCard is UTF-8 as defined in [RFC3629]. There is no way to override
this. It is invalid to specify a value other than "UTF-8" in the this. It is invalid to specify a value other than "UTF-8" in the
"charset" MIME parameter (see Section 10.1). "charset" MIME parameter (see Section 10.1).
skipping to change at page 7, line 5 skipping to change at page 6, line 5
SHOULD be folded to a maximum width of 75 octets, excluding the line SHOULD be folded to a maximum width of 75 octets, excluding the line
break. Multi-octet characters MUST remain contiguous. The rationale break. Multi-octet characters MUST remain contiguous. The rationale
for this folding process can be found in [RFC5322], Section 2.1.1. for this folding process can be found in [RFC5322], Section 2.1.1.
A logical line MAY be continued on the next physical line anywhere A logical line MAY be continued on the next physical line anywhere
between two characters by inserting a CRLF immediately followed by a between two characters by inserting a CRLF immediately followed by a
single white space character (space (U+0020) or horizontal tab single white space character (space (U+0020) or horizontal tab
(U+0009)). The folded line MUST contain at least one character. Any (U+0009)). The folded line MUST contain at least one character. Any
sequence of CRLF followed immediately by a single white space sequence of CRLF followed immediately by a single white space
character is ignored (removed) when processing the content type. For character is ignored (removed) when processing the content type. For
example the line: example, the line:
NOTE:This is a long description that exists on a long line. NOTE:This is a long description that exists on a long line.
can be represented as: can be represented as:
NOTE:This is a long description NOTE:This is a long description
that exists on a long line. that exists on a long line.
It could also be represented as: It could also be represented as:
NOTE:This is a long descrip NOTE:This is a long descrip
tion that exists o tion that exists o
n a long line. n a long line.
The process of moving from this folded multiple-line representation The process of moving from this folded multiple-line representation
of a property definition to its single line representation is called of a property definition to its single-line representation is called
unfolding. Unfolding is accomplished by regarding CRLF immediately unfolding. Unfolding is accomplished by regarding CRLF immediately
followed by a white space character (namely HTAB (U+0009) or SPACE followed by a white space character (namely, HTAB (U+0009) or SPACE
(U+0020)) as equivalent to no characters at all (i.e., the CRLF and (U+0020)) as equivalent to no characters at all (i.e., the CRLF and
single white space character are removed). single white space character are removed).
Note: It is possible for very simple implementations to generate Note: It is possible for very simple implementations to generate
improperly folded lines in the middle of a UTF-8 multi-octet improperly folded lines in the middle of a UTF-8 multi-octet
sequence. For this reason, implementations SHOULD unfold lines in sequence. For this reason, implementations SHOULD unfold lines in
such a way as to properly restore the original sequence. such a way as to properly restore the original sequence.
Note: Unfolding is done differently than in [RFC5322]. Unfolding Note: Unfolding is done differently than in [RFC5322]. Unfolding
in [RFC5322] only removes the CRLF, not the space following it. in [RFC5322] only removes the CRLF, not the space following it.
skipping to change at page 8, line 8 skipping to change at page 7, line 8
vcard = "BEGIN:VCARD" CRLF vcard = "BEGIN:VCARD" CRLF
"VERSION:4.0" CRLF "VERSION:4.0" CRLF
1*contentline 1*contentline
"END:VCARD" CRLF "END:VCARD" CRLF
; A vCard object MUST include the VERSION and FN properties. ; A vCard object MUST include the VERSION and FN properties.
; VERSION MUST come immediately after BEGIN:VCARD. ; VERSION MUST come immediately after BEGIN:VCARD.
contentline = [group "."] name *(";" param) ":" value CRLF contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines must first ; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure ; be unfolded according to the unfolding procedure
; described in section 3.2. ; described in Section 3.2.
; When generating a content line, lines longer than 75 ; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding ; characters SHOULD be folded according to the folding
; procedure described in section 3.2. ; procedure described in Section 3.2.
group = 1*(ALPHA / DIGIT / "-") group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME" name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL" / "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
/ "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE" / "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
/ "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES" / "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
/ "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP" / "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
/ "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML" / "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ iana-token / x-name / iana-token / x-name
; Parsing of the param and value is based on the "name" as ; Parsing of the param and value is based on the "name" as
skipping to change at page 9, line 13 skipping to change at page 8, line 13
; Any textual character ; Any textual character
A line that begins with a white space character is a continuation of A line that begins with a white space character is a continuation of
the previous line, as described in Section 3.2. The white space the previous line, as described in Section 3.2. The white space
character and immediately preceeding CRLF should be discarded when character and immediately preceeding CRLF should be discarded when
reconstructing the original line. Note that this line-folding reconstructing the original line. Note that this line-folding
convention differs from that found in [RFC5322], in that the sequence convention differs from that found in [RFC5322], in that the sequence
<CRLF><WSP> found anywhere in the content indicates a continued line <CRLF><WSP> found anywhere in the content indicates a continued line
and should be removed. and should be removed.
Property names and parameter names are case insensitive (e.g., the Property names and parameter names are case-insensitive (e.g., the
property name "fn" is the same as "FN" and "Fn"). Parameter values property name "fn" is the same as "FN" and "Fn"). Parameter values
MAY be case-sensitive or case-insensitive, depending on their MAY be case-sensitive or case-insensitive, depending on their
definition. Parameter values that are not explicitly defined as definition. Parameter values that are not explicitly defined as
being case-sensitive are case-insenstive. Based on experience with being case-sensitive are case-insensitive. Based on experience with
vCard 3 interoperability, it is RECOMMENDED that property and vCard 3 interoperability, it is RECOMMENDED that property and
parameter names be upper-case on output. parameter names be upper-case on output.
The group construct is used to group related properties together. The group construct is used to group related properties together.
The group name is a syntactic convention used to indicate that all The group name is a syntactic convention used to indicate that all
property names prefaced with the same group name SHOULD be grouped property names prefaced with the same group name SHOULD be grouped
together when displayed by an application. It has no other together when displayed by an application. It has no other
significance. Implementations that do not understand or support significance. Implementations that do not understand or support
grouping MAY simply strip off any text before a "." to the left of grouping MAY simply strip off any text before a "." to the left of
the type name and present the types and values as normal. the type name and present the types and values as normal.
Property cardinalities are indicated using the following notation, Property cardinalities are indicated using the following notation,
which is based on ABNF (see [RFC5234], section 3.6): which is based on ABNF (see [RFC5234], Section 3.6):
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
| Cardinality | Meaning | | Cardinality | Meaning |
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
| 1 | Exactly one instance per vCard MUST be present. | | 1 | Exactly one instance per vCard MUST be present. |
| *1 | Exactly one instance per vCard MAY be present. | | *1 | Exactly one instance per vCard MAY be present. |
| 1* | One or more instances per vCard MUST be present. | | 1* | One or more instances per vCard MUST be present. |
| * | One or more instances per vCard MAY be present. | | * | One or more instances per vCard MAY be present. |
+-------------+--------------------------------------------------+ +-------------+--------------------------------------------------+
skipping to change at page 10, line 12 skipping to change at page 9, line 12
approach has been taken for several of the content types defined approach has been taken for several of the content types defined
below (date, time, integer, float). below (date, time, integer, float).
3.4. Property Value Escaping 3.4. Property Value Escaping
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 (U+002C). Therefore, a COMMA character in a value MUST be character (U+002C). Therefore, a COMMA character in a value MUST be
escaped with a BACKSLASH character (U+005C), even for properties that escaped with a BACKSLASH character (U+005C), even for properties that
don't allow multiple instances (for consistency). don't allow multiple instances (for 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 (U+003B). Therefore, a SEMI-COLON in a by a SEMICOLON character (U+003B). Therefore, a SEMICOLON in a field
field of such a "compound" property MUST be escaped with a BACKSLASH of such a "compound" property MUST be escaped with a BACKSLASH
character. SEMI-COLON characters in non-compound properties MAY be character. SEMICOLON characters in non-compound properties MAY be
escaped. On input, an escaped SEMI-COLON character is never a field escaped. On input, an escaped SEMICOLON character is never a field
separator. An unescaped SEMI-COLON character may be a field separator. An unescaped SEMICOLON character may be a field
separator, depending on the property in which it appears. 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
skipping to change at page 12, line 15 skipping to change at page 11, line 15
date-time = date-noreduc time-designator time-notrunc date-time = date-noreduc time-designator time-notrunc
timestamp = date-complete time-designator time-complete timestamp = date-complete time-designator time-complete
date-and-or-time = date-time / date / time-designator time date-and-or-time = date-time / date / time-designator time
utc-offset = sign hour [minute] utc-offset = sign hour [minute]
Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1> Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1>
iana-valuespec = <value-spec, see Section 12> iana-valuespec = <value-spec, see Section 12>
; a publicly-defined valuetype format, registered ; a publicly defined valuetype format, registered
; with IANA, as defined in section 12 of this ; with IANA, as defined in Section 12 of this
; document ; document.
4.1. TEXT 4.1. TEXT
"text": The "text" value type should be used to identify values that "text": The "text" value type should be used to identify values that
contain human-readable text. As for the language, it is controlled contain human-readable text. As for the language, it is controlled
by the LANGUAGE property parameter defined in Section 5.1. by the LANGUAGE property parameter defined in Section 5.1.
Examples for "text": Examples for "text":
this is a text value this is a text value
this is one value,this is another this is one value,this is another
this is a single value\, with a comma encoded this is a single value\, with a comma encoded
A formatted text line break in a text value type MUST be represented A formatted text line break in a text value type MUST be represented
as the character sequence backslash (U+005C) followed by a Latin as the character sequence backslash (U+005C) followed by a Latin
small letter n (U+006E) or a Latin capital letter N (U+004E), that is small letter n (U+006E) or a Latin capital letter N (U+004E), that
"\n" or "\N". is, "\n" or "\N".
For example a multiple line NOTE value of: For example, a multiple line NOTE value of:
Mythical Manager Mythical Manager
Hyjinx Software Division Hyjinx Software Division
BabsCo, Inc. BabsCo, Inc.
could be represented as: could be represented as:
NOTE:Mythical Manager\nHyjinx Software Division\n NOTE:Mythical Manager\nHyjinx Software Division\n
BabsCo\, Inc.\n BabsCo\, Inc.\n
skipping to change at page 13, line 22 skipping to change at page 12, line 22
that the value of a property of type "uri" is what the URI points to, that the value of a property of type "uri" is what the URI points to,
not the URI itself. not the URI itself.
Examples for "uri": Examples for "uri":
http://www.example.com/my/picture.jpg http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen ldap://ldap.example.com/cn=babs%20jensen
4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP 4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP
"date", "time", "date-time", and "timestamp": Each of these value "date", "time", "date-time", "date-and-or-time", and "timestamp":
types is based on the definitions in [ISO.8601.2004] standard. Each of these value types is based on the definitions in
Multiple such values can be specified using the comma-separated [ISO.8601.2004]. Multiple such values can be specified using the
notation. comma-separated notation.
Only the basic format is supported. Only the basic format is supported.
4.3.1. DATE 4.3.1. DATE
A calendar date as specified in [ISO.8601.2004] section 4.1.2. A calendar date as specified in [ISO.8601.2004], Section 4.1.2.
Reduced accuracy, as specified in [ISO.8601.2004] sections 4.1.2.3 a) Reduced accuracy, as specified in [ISO.8601.2004], Sections 4.1.2.3
and b), but not c), is permitted. a) and b), but not c), is permitted.
Expanded representation, as specified in [ISO.8601.2004] section Expanded representation, as specified in [ISO.8601.2004], Section
4.1.4, is forbidden. 4.1.4, is forbidden.
Truncated representation, as specified in [ISO.8601.2000] sections Truncated representation, as specified in [ISO.8601.2000], Sections
5.2.1.3 d), e), and f), is permitted. 5.2.1.3 d), e), and f), is permitted.
Examples for "date": Examples for "date":
19850412 19850412
1985-04 1985-04
1985 1985
--0412 --0412
---12 ---12
Note the use of YYYY-MM in the second example above. YYYYMM is Note the use of YYYY-MM in the second example above. YYYYMM is
disallowed to prevent confusion with YYMMDD. Note also that disallowed to prevent confusion with YYMMDD. Note also that
YYYY-MM-DD is disallowed since we are using the basic format instead YYYY-MM-DD is disallowed since we are using the basic format instead
of the extended format. of the extended format.
4.3.2. TIME 4.3.2. TIME
A time of day as specified in [ISO.8601.2004] section 4.2. A time of day as specified in [ISO.8601.2004], Section 4.2.
Reduced accuracy, as specified in [ISO.8601.2004] section 4.2.2.3, is Reduced accuracy, as specified in [ISO.8601.2004], Section 4.2.2.3,
permitted. is permitted.
Representation with decimal fraction, as specified in [ISO.8601.2004] Representation with decimal fraction, as specified in
section 4.2.2.4, is forbidden. [ISO.8601.2004], Section 4.2.2.4, is forbidden.
The midnight hour is always represented by 00, never 24 (see The midnight hour is always represented by 00, never 24 (see
[ISO.8601.2004] section 4.2.3). [ISO.8601.2004], Section 4.2.3).
Truncated representation, as specified in [ISO.8601.2000] sections Truncated representation, as specified in [ISO.8601.2000], Sections
5.3.1.4 a), b), and c), is permitted. 5.3.1.4 a), b), and c), is permitted.
Examples for "time": Examples for "time":
102200 102200
1022 1022
10 10
-2200 -2200
--00 --00
102200Z 102200Z
102200-0800 102200-0800
4.3.3. DATE-TIME 4.3.3. DATE-TIME
A date and time of day combination as specified in [ISO.8601.2004] A date and time of day combination as specified in [ISO.8601.2004],
section 4.3. Section 4.3.
Truncation of the date part, as specified in [ISO.8601.2000] section Truncation of the date part, as specified in [ISO.8601.2000], Section
5.4.2 c), is permitted. 5.4.2 c), is permitted.
Examples for "date-time": Examples for "date-time":
19961022T140000 19961022T140000
--1022T1400 --1022T1400
---22T14 ---22T14
4.3.4. DATE-AND-OR-TIME 4.3.4. DATE-AND-OR-TIME
Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous
interpretation, a standalone TIME value is always preceded by a "T". interpretation, a stand-alone TIME value is always preceded by a "T".
Examples for "date-and-or-time": Examples for "date-and-or-time":
19961022T140000 19961022T140000
--1022T1400 --1022T1400
---22T14 ---22T14
19850412 19850412
1985-04 1985-04
1985 1985
--0412 --0412
skipping to change at page 15, line 26 skipping to change at page 14, line 31
T1022 T1022
T10 T10
T-2200 T-2200
T--00 T--00
T102200Z T102200Z
T102200-0800 T102200-0800
4.3.5. TIMESTAMP 4.3.5. TIMESTAMP
A complete date and time of day combination as specified in A complete date and time of day combination as specified in
[ISO.8601.2004] section 4.3.2. [ISO.8601.2004], Section 4.3.2.
Examples for "timestamp": Examples for "timestamp":
19961022T140000 19961022T140000
19961022T140000Z 19961022T140000Z
19961022T140000-05 19961022T140000-05
19961022T140000-0500 19961022T140000-0500
4.4. BOOLEAN 4.4. BOOLEAN
"boolean": The "boolean" value type is used to express boolean "boolean": The "boolean" value type is used to express boolean
values. These values are case insensitive. values. These values are case-insensitive.
Examples: Examples:
TRUE TRUE
false false
True True
4.5. INTEGER 4.5. INTEGER
"integer": The "integer" value type is used to express signed "integer": The "integer" value type is used to express signed
integers in decimal format. If sign is not specified, the value is integers in decimal format. If sign is not specified, the value is
assumed positive "+". Multiple "integer" values can be specified assumed positive "+". Multiple "integer" values can be specified
using the comma-separated notation. The maximum value is using the comma-separated notation. The maximum value is
9223372036854775807 and the minimum value is -9223372036854775808. 9223372036854775807, and the minimum value is -9223372036854775808.
These limits correspond to a signed 64-bit integer using two's- These limits correspond to a signed 64-bit integer using two's-
complement arithmetic. complement arithmetic.
Examples: Examples:
1234567890 1234567890
-1234556790 -1234556790
+1234556790,432109876 +1234556790,432109876
4.6. FLOAT 4.6. FLOAT
"float": The "float" value type is used to express real numbers. If "float": The "float" value type is used to express real numbers. If
sign is not specified, the value is assumed positive "+". Multiple sign is not specified, the value is assumed positive "+". Multiple
"float" values can be specified using the comma-separated notation. "float" values can be specified using the comma-separated notation.
Implementations MUST support a precision equal or better than that of Implementations MUST support a precision equal or better than that of
the IEEE "binary64" format [IEEE.754.2008]. the IEEE "binary64" format [IEEE.754.2008].
Note: Scientific notation is disallowed. Implementors wishing to Note: Scientific notation is disallowed. Implementers wishing to
use their favorite language's %f formatting should be careful. use their favorite language's %f formatting should be careful.
Examples: Examples:
20.30 20.30
1000000.0000001 1000000.0000001
1.333,3.14 1.333,3.14
4.7. UTC-OFFSET 4.7. UTC-OFFSET
"utc-offset": The "utc-offset" value type specifies that the property "utc-offset": The "utc-offset" value type specifies that the property
value is a signed offset from UTC. This value type can be specified value is a signed offset from UTC. This value type can be specified
in the TZ property. in the TZ property.
The value type is an offset from Coordinated Universal Time (UTC). The value type is an offset from Coordinated Universal Time (UTC).
It is specified as a positive or negative difference in units of It is specified as a positive or negative difference in units of
hours and minutes (e.g., +hhmm). The time is specified as a 24-hour hours and minutes (e.g., +hhmm). The time is specified as a 24-hour
clock. Hour values are from 00 to 23, and minute values are from 00 clock. Hour values are from 00 to 23, and minute values are from 00
to 59. Hour and minutes are 2-digits with high order zeroes required to 59. Hour and minutes are 2 digits with high-order zeroes required
to maintain digit count. The basic format for ISO 8601 UTC offsets to maintain digit count. The basic format for ISO 8601 UTC offsets
MUST be used. MUST be used.
4.8. LANGUAGE-TAG 4.8. LANGUAGE-TAG
"language-tag": A single language tag, as defined in [RFC5646]. "language-tag": A single language tag, as defined in [RFC5646].
5. Property Parameters 5. Property Parameters
A property can have attributes associated with it. These "property A property can have attributes associated with it. These "property
parameters" contain meta-information about the property or the parameters" contain meta-information about the property or the
property value. In some cases the property parameter can be multi- property value. In some cases, the property parameter can be multi-
valued in which case the property parameter value elements are valued in which case the property parameter value elements are
separated by a COMMA (U+002C). separated by a COMMA (U+002C).
Property parameter value elements that contain the COLON (U+003A), Property parameter value elements that contain the COLON (U+003A),
SEMICOLON (U+003B) or COMMA (U+002C) character separators MUST be SEMICOLON (U+003B), or COMMA (U+002C) character separators MUST be
specified as quoted-string text values. Property parameter values specified as quoted-string text values. Property parameter values
MUST NOT contain the DQUOTE (U+0022) character. The DQUOTE character MUST NOT contain the DQUOTE (U+0022) character. The DQUOTE character
is used as a delimiter for parameter values that contain restricted is used as a delimiter for parameter values that contain restricted
characters or URI text. characters or URI text.
Applications MUST ignore x-param and iana-param values they don't Applications MUST ignore x-param and iana-param values they don't
recognize. recognize.
5.1. LANGUAGE 5.1. LANGUAGE
skipping to change at page 17, line 42 skipping to change at page 17, line 4
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
5.2. VALUE 5.2. VALUE
The VALUE parameter is OPTIONAL, used to identify the value type The VALUE parameter is OPTIONAL, used to identify the value type
(data type) and format of the value. The use of these predefined (data type) and format of the value. The use of these predefined
formats is encouraged even if the value parameter is not explicitly formats is encouraged even if the value parameter is not explicitly
used. By defining a standard set of value types and their formats, used. By defining a standard set of value types and their formats,
existing parsing and processing code can be leveraged. The existing parsing and processing code can be leveraged. The
predefined data type values MUST NOT be repeated in COMMA separated predefined data type values MUST NOT be repeated in COMMA-separated
value lists except within the N, NICKNAME, ADR, and CATEGORIES value lists except within the N, NICKNAME, ADR, and CATEGORIES
properties. properties.
ABNF: ABNF:
value-param = "VALUE=" value-type value-param = "VALUE=" value-type
value-type = "text" value-type = "text"
/ "uri" / "uri"
/ "date" / "date"
skipping to change at page 18, line 30 skipping to change at page 17, line 33
/ "language-tag" / "language-tag"
/ iana-token ; registered as described in section 12 / iana-token ; registered as described in section 12
/ x-name / x-name
5.3. PREF 5.3. PREF
The PREF parameter is OPTIONAL and is used to indicate that the The PREF parameter is OPTIONAL and is used to indicate that the
corresponding instance of a property is preferred by the vCard corresponding instance of a property is preferred by the vCard
author. Its value MUST be an integer between 1 and 100 that author. Its value MUST be an integer between 1 and 100 that
quantifies the level of preference. Lower values correspond to a quantifies the level of preference. Lower values correspond to a
higher level of preference, 1 being most preferred. higher level of preference, with 1 being most preferred.
When the parameter is absent, the default MUST be to interpret the When the parameter is absent, the default MUST be to interpret the
property instance as being least preferred. property instance as being least preferred.
Note that the value of this parameter is to be interpreted only in Note that the value of this parameter is to be interpreted only in
relation to values assigned to other instances of the same property relation to values assigned to other instances of the same property
in the same vCard. A given value, or the absence of a value, MUST in the same vCard. A given value, or the absence of a value, MUST
NOT be interpreted on its own. NOT be interpreted on its own.
This parameter MAY be applied to any property that allows multiple This parameter MAY be applied to any property that allows multiple
skipping to change at page 19, line 5 skipping to change at page 18, line 11
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.4. ALTID 5.4. ALTID
The ALTID parameter is used to "tag" property instances as being The ALTID parameter is used to "tag" property instances as being
alternative representations of the same logical property. For alternative representations of the same logical property. For
example, translations of a property in multiple languages generates example, translations of a property in multiple languages generates
multiple property instances having different LANGUAGE (Section 5.1) multiple property instances having different LANGUAGE (Section 5.1)
parameter which are tagged with the same ALTID value. parameter that are tagged with the same ALTID value.
This parameter's value is treated as an opaque string. Its sole This parameter's value is treated as an opaque string. Its sole
purpose is to be compared for equality against other ALTID parameter purpose is to be compared for equality against other ALTID parameter
values. values.
Two property instances are considered alternative representations of Two property instances are considered alternative representations of
the same logical property if and only if their names as well as the the same logical property if and only if their names as well as the
value of their ALTID parameters are identical. Property instances value of their ALTID parameters are identical. Property instances
without the ALTID parameter MUST NOT be considered an alternative without the ALTID parameter MUST NOT be considered an alternative
representation of any other property instance. Values for the ALTID representation of any other property instance. Values for the ALTID
skipping to change at page 20, line 8 skipping to change at page 19, line 4
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;; N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N:Yamada;Taro;;; N:Yamada;Taro;;;
(Two instances of the N property.) (Two instances of the N property.)
and these three would be legal but questionable: and these three would be legal but questionable:
TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=2;LANGUAGE=en:Boss TITLE;ALTID=2;LANGUAGE=en:Boss
(Should probably have the same ALTID value.) (Should probably have the same ALTID value.)
TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE:LANGUAGE=en:Boss TITLE:LANGUAGE=en:Boss
(Second line should probably have ALTID=1.) (Second line should probably have ALTID=1.)
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;; N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N;ALTID=1;LANGUAGE=en:Yamada;Taro;;; N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
N;ALTID=1;LANGUAGE=en:Smith;John;;; N;ALTID=1;LANGUAGE=en:Smith;John;;;
(The last line should probably have ALTID=2. But that would be (The last line should probably have ALTID=2. But that would be
illegal because N has cardinality *1.) illegal because N has cardinality *1.)
The ALTID property MAY also be used in may contexts other than with The ALTID property MAY also be used in may contexts other than with
the LANGUAGE parameter. Here's an example with two representations the LANGUAGE parameter. Here's an example with two representations
of the same photo in different file formats: of the same photo in different file formats:
PHOTO;ALTID=1:data:image/jpeg;base64,... PHOTO;ALTID=1:data:image/jpeg;base64,...
PHOTO;ALTID=1;data:image/jp2;base64,... PHOTO;ALTID=1;data:image/jp2;base64,...
ABNF: ABNF:
skipping to change at page 20, line 51 skipping to change at page 19, line 46
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.6. 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
defined enumeration. In this document, the following properties make predefined enumeration. In this document, the following properties
use of this parameter: FN, NICKNAME, PHOTO, ADR, TEL, EMAIL, IMPP, make use of this parameter: FN, NICKNAME, PHOTO, ADR, TEL, EMAIL,
LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, NOTE, IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES,
SOUND, URL, KEY, FBURL, CALADRURI, and CALURI. The TYPE parameter NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI. The TYPE
MUST NOT be applied on other properties defined in this document. parameter MUST NOT be applied on other properties defined in this
document.
The "work" and "home" values act like tags. The "work" value implies The "work" and "home" values act like tags. The "work" value implies
that the property is related to an individual's work place, while the that the property is related to an individual's work place, while the
"home" value implies that the property is related to an individual's "home" value implies that the property is related to an individual's
personal life. When neither "work" nor "home" is present, it is personal life. When neither "work" nor "home" is present, it is
implied that the property is related to both an individual's work implied that the property is related to both an individual's work
place and personal life in the case that the KIND property's value is place and personal life in the case that the KIND property's value is
"individual", or to none in other cases. "individual", or to none in other cases.
ABNF: ABNF:
skipping to change at page 21, line 36 skipping to change at page 20, line 35
The MEDIATYPE parameter is used with properties whose value is a URI. The MEDIATYPE parameter is used with properties whose value is a URI.
Its use is OPTIONAL. It provides a hint to the vCard consumer Its use is OPTIONAL. It provides a hint to the vCard consumer
application about the media type [RFC2046] of the resource identified application about the media type [RFC2046] of the resource identified
by the URI. Some URI schemes do not need this parameter. For by the URI. Some URI schemes do not need this parameter. For
example, the "data" scheme allows the media type to be explicitly example, the "data" scheme allows the media type to be explicitly
indicated as part of the URI [RFC2397]. Another scheme, "http", indicated as part of the URI [RFC2397]. Another scheme, "http",
provides the media type as part of the URI resolution process, with provides the media type as part of the URI resolution process, with
the Content-Type HTTP header [RFC2616]. The MEDIATYPE parameter is the Content-Type HTTP header [RFC2616]. The MEDIATYPE parameter is
intended to be used with URI schemes that do not provide such intended to be used with URI schemes that do not provide such
functionality (e.g. "ftp" [RFC1738]). functionality (e.g., "ftp" [RFC1738]).
ABNF: ABNF:
mediatype-param = "MEDIATYPE=" mediatype mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value ) mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "attribute" and "value" are from [RFC2045] ; "attribute" and "value" are from [RFC2045]
; "type-name" and "subtype-name" are from [RFC4288] ; "type-name" and "subtype-name" are from [RFC4288]
5.8. CALSCALE 5.8. CALSCALE
The CALSCALE parameter is identical to the CALSCALE property in The CALSCALE parameter is identical to the CALSCALE property in
iCalendar (see [RFC5545], section 3.7.1). It is used to define the iCalendar (see [RFC5545], Section 3.7.1). It is used to define the
calendar system in which a date or date-time value is expressed. The calendar system in which a date or date-time value is expressed. The
only value specified by iCalendar is "gregorian", which stands for only value specified by iCalendar is "gregorian", which stands for
the Gregorian system. It is the default when the parameter is the Gregorian system. It is the default when the parameter is
absent. Additional values may be defined in extension documents and absent. Additional values may be defined in extension documents and
registered from IANA (see Section 10.3.4). A vCard implementation registered with IANA (see Section 10.3.4). A vCard implementation
MUST ignore properties with a CALSCALE parameter value that it does MUST ignore properties with a CALSCALE parameter value that it does
not understand. not understand.
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.9. SORT-AS 5.9. SORT-AS
The "sort-as" parameter is used to specify the string to be used for The "sort-as" parameter is used to specify the string to be used for
national-language-specific sorting. Without this information, national-language-specific sorting. Without this information,
sorting algorithms could incorrectly sort this vCard within a sorting algorithms could incorrectly sort this vCard within a
sequence of sorted vCards. When this property is present in a vCard, sequence of sorted vCards. When this property is present in a vCard,
then the given strings are used for sorting the vCard. then the given strings are used for sorting the vCard.
This parameter's value is a comma-separated list which MUST have as This parameter's value is a comma-separated list that MUST have as
many or fewer elements as the corresponding property value has many or fewer elements as the corresponding property value has
components. This parameter's value is case-sensitive. components. This parameter's value is case-sensitive.
ABNF: ABNF:
sort-as-param = "SORT-AS=" sort-as-value sort-as-param = "SORT-AS=" sort-as-value
sort-as-value = param-value *("," param-value) sort-as-value = param-value *("," param-value)
Examples: For the case of surname and given name sorting, the Examples: For the case of surname and given name sorting, the
skipping to change at page 23, line 19 skipping to change at page 22, line 4
N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;; N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;
FN:Osamu Koura FN:Osamu Koura
N;SORT-AS="Koura,Osamu":Koura;Osamu;; N;SORT-AS="Koura,Osamu":Koura;Osamu;;
FN:Oscar del Pozo FN:Oscar del Pozo
N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;; N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;
FN:Chistine d'Aboville FN:Chistine d'Aboville
N;SORT-AS="Aboville,Christine":d'Aboville;Christine;; N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;
FN:H. James de Mann FN:H. James de Mann
N;SORT-AS="Mann,James":de Mann;Henry,James;; N;SORT-AS="Mann,James":de Mann;Henry,James;;
If sorted by surname the results would be: If sorted by surname, the results would be:
Christine d'Aboville Christine d'Aboville
Rene van der Harten Rene van der Harten
Osamu Koura Osamu Koura
H. James de Mann H. James de Mann
Robert Pau Shou Chang Robert Pau Shou Chang
Oscar del Pozo Oscar del Pozo
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.10. GEO 5.10. GEO
skipping to change at page 24, line 34 skipping to change at page 23, line 24
text/vcard content-type. text/vcard content-type.
Value type: text Value type: text
Cardinality: 1 Cardinality: 1
Special notes: The content entity MUST begin with the BEGIN property Special notes: The content entity MUST begin with the BEGIN property
with a value of "VCARD". The value is case-insensitive. with a value of "VCARD". The value is case-insensitive.
The BEGIN property is used in conjunction with the END property to The BEGIN property is used in conjunction with the END property to
delimit an entity containing a related set of properties within an delimit an entity containing a related set of properties within a
text/vcard content-type. This construct can be used instead of text/vcard content-type. This construct can be used instead of
including multiple vCards as body parts inside of a multipart/ including multiple vCards as body parts inside of a multipart/
alternative MIME message. It is provided for applications that alternative MIME message. It is provided for applications that
wish to define content that can contain multiple entities within wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be the same text/vcard content-type or to define content that can be
identifiable outside of a MIME environment. identifiable outside of a MIME environment.
ABNF: ABNF:
BEGIN-param = 0" " ; no parameter allowed BEGIN-param = 0" " ; no parameter allowed
skipping to change at page 25, line 18 skipping to change at page 24, line 6
content-type. content-type.
Value type: text Value type: text
Cardinality: 1 Cardinality: 1
Special notes: The content entity MUST end with the END type with a Special notes: The content entity MUST end with the END type with a
value of "VCARD". The value is case-insensitive. value of "VCARD". The value is case-insensitive.
The END property is used in conjunction with the BEGIN property to The END property is used in conjunction with the BEGIN property to
delimit an entity containing a related set of properties within an delimit an entity containing a related set of properties within a
text/vcard content-type. This construct can be used instead of or text/vcard content-type. This construct can be used instead of or
in addition to wrapping separate sets of information inside in addition to wrapping separate sets of information inside
additional MIME headers. It is provided for applications that additional MIME headers. It is provided for applications that
wish to define content that can contain multiple entities within wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be the same text/vcard content-type or to define content that can be
identifiable outside of a MIME environment. identifiable outside of a MIME environment.
ABNF: ABNF:
END-param = 0" " ; no parameter allowed END-param = 0" " ; no parameter allowed
skipping to change at page 27, line 25 skipping to change at page 26, line 20
All properties in a location vCard apply to the location All properties in a location vCard apply to the location
itself, and not with any entity that might exist at that itself, and not with any entity that might exist at that
location. For example, in a vCard for an office building, an location. For example, in a vCard for an office building, an
ADR property might give the mailing address for the building, ADR property might give the mailing address for the building,
and a TEL property might specify the telephone number of the and a TEL property might specify the telephone number of the
receptionist. receptionist.
An x-name. vCards MAY include private or experimental values for An x-name. vCards MAY include private or experimental values for
KIND. Remember that x-name values are not intended for general KIND. Remember that x-name values are not intended for general
use, and are unlikely to interoperate. use and are unlikely to interoperate.
An iana-token. Additional values may be registered with IANA (see An iana-token. Additional values may be registered with IANA (see
Section 10.3.4). A new value's specification document MUST Section 10.3.4). A new value's specification document MUST
specify which properties make sense for that new kind of vCard specify which properties make sense for that new kind of vCard
and which do not. and which do not.
Implementations MUST support the specific string values defined Implementations MUST support the specific string values defined
above. If this property is absent, "individual" MUST be assumed above. If this property is absent, "individual" MUST be assumed
as the default. If this property is present but the as the default. If this property is present but the
implementation does not understand its value (the value is an implementation does not understand its value (the value is an
skipping to change at page 28, line 12 skipping to change at page 27, line 8
vCards to different panes, tabs, or selections in the user vCards to different panes, tabs, or selections in the user
interface. interface.
Some clients might also make functional distinctions among the Some clients might also make functional distinctions among the
kinds, ignoring "location" vCards for some purposes and kinds, ignoring "location" vCards for some purposes and
considering only "location" vCards for others. considering only "location" vCards for others.
When designing those sorts of visual and functional distinctions, When designing those sorts of visual and functional distinctions,
client implementations have to decide how to fit unsupported kinds client implementations have to decide how to fit unsupported kinds
into the scheme. What icon is used for them? The one for into the scheme. What icon is used for them? The one for
"individual"? A unique one, such as an icon of a question-mark? "individual"? A unique one, such as an icon of a question mark?
Which tab do they go into? It is beyond the scope of this Which tab do they go into? It is beyond the scope of this
specification to answer these questions, but these are things specification to answer these questions, but these are things
implementors need to consider. implementers need to consider.
ABNF: ABNF:
KIND-param = "VALUE=text" / any-param KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location" KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name / iana-token / x-name
Example: Example:
This represents someone named Jane Doe working in the marketing This represents someone named Jane Doe working in the marketing
department of the North American division of ABC Inc. department of the North American division of ABC Inc.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:individual KIND:individual
FN:Jane Doe FN:Jane Doe
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD END:VCARD
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.5. XML 6.1.5. XML
skipping to change at page 29, line 15 skipping to change at page 28, line 7
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
Special notes: The content of this property is a single XML 1.0 Special notes: The content of this property is a single XML 1.0
[W3C.REC-xml-20081126] element whose namespace MUST be explicitly [W3C.REC-xml-20081126] element whose namespace MUST be explicitly
specified using the xmlns attribute and MUST NOT be the vCard 4 specified using the xmlns attribute and MUST NOT be the vCard 4
namespace ("urn:ietf:params:xml:ns:vcard-4.0"). (This implies namespace ("urn:ietf:params:xml:ns:vcard-4.0"). (This implies
that it cannot duplicate a standard vCard property.) The element that it cannot duplicate a standard vCard property.) The element
is to be interpreted as if it was contained in a <vcard> element, is to be interpreted as if it was contained in a <vcard> element,
as defined in [I-D.ietf-vcarddav-vcardxml]. as defined in [RFC6351].
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.
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 [RFC6351] for more information on the intended use of this
intended use of this property. property.
ABNF: ABNF:
XML-param = "VALUE=text" / altid-param XML-param = "VALUE=text" / altid-param
XML-value = text XML-value = text
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 entity associated with the vCard. identification and naming of the entity associated with the vCard.
skipping to change at page 29, line 48 skipping to change at page 28, line 40
6.2.1. FN 6.2.1. FN
Purpose: To specify the formatted text corresponding to the name of Purpose: To specify the formatted text corresponding to the name of
the object the vCard represents. the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: 1* Cardinality: 1*
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 [CCITT.X520.1988]. The property MUST be
object. present in the vCard object.
ABNF: ABNF:
FN-param = "VALUE=text" / type-param / language-param / altid-param FN-param = "VALUE=text" / type-param / language-param / altid-param
/ pid-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.
skipping to change at page 30, line 28 skipping to change at page 29, line 18
vCard represents. vCard represents.
Value type: A single structured text value. Each component can have Value type: A single structured text value. Each component can have
multiple values. multiple values.
Cardinality: *1 Cardinality: *1
Special note: The structured property value corresponds, in Special note: The structured property value corresponds, in
sequence, to the Family Names (also known as surnames), Given sequence, to the Family Names (also known as surnames), Given
Names, Additional Names, Honorific Prefixes, and Honorific Names, Additional Names, Honorific Prefixes, and Honorific
Suffixes. The text components are separated by the SEMI-COLON Suffixes. The text components are separated by the SEMICOLON
character (U+003B). Individual text components can include character (U+003B). Individual text components can include
multiple text values separated by the COMMA character (U+002C). multiple text values separated by the COMMA character (U+002C).
This property is based on the semantics of the X.520 individual This property is based on the semantics of the X.520 individual
name attributes. The property SHOULD be present in the vCard name attributes [CCITT.X520.1988]. The property SHOULD be present
object when the name of the object the vCard represents follows in the vCard object when the name of the object the vCard
the X.520 model. represents follows the X.520 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 N-param = "VALUE=text" / sort-as-param / language-param
/ altid-param / any-param / altid-param / any-param
N-value = list-component 4(";" list-component) N-value = list-component 4(";" list-component)
Examples: Examples:
skipping to change at page 31, line 14 skipping to change at page 30, line 4
6.2.3. NICKNAME 6.2.3. NICKNAME
Purpose: To specify the text corresponding to the nickname of the Purpose: To specify the text corresponding to the nickname of the
object the vCard represents. object the vCard represents.
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(U+002C). (U+002C).
Cardinality: * Cardinality: *
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 the object the vCard or in addition to the one belonging to the object the vCard
represents. It can also be used to specify a familiar form of a represents. It can also be used to specify a familiar form of a
proper name specified by the FN or N properties. proper name 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
/ altid-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:
skipping to change at page 34, line 22 skipping to change at page 32, line 50
6.3. Delivery Addressing Properties 6.3. Delivery Addressing Properties
These types are concerned with information related to the delivery These types are concerned with information related to the delivery
addressing or label for the vCard object. addressing or label for the vCard object.
6.3.1. ADR 6.3.1. ADR
Purpose: To specify the components of the delivery address for the Purpose: To specify the components of the delivery address for the
vCard object. vCard object.
Value type: A single structured text value, separated by the SEMI- Value type: A single structured text value, separated by the
COLON character (U+003B). SEMICOLON character (U+003B).
Cardinality: * Cardinality: *
Special notes: The structured type value consists of a sequence of Special notes: The structured type value consists of a sequence of
address components. The component values MUST be specified in address components. The component values MUST be specified in
their corresponding position. The structured type value their corresponding position. The structured type value
corresponds, in sequence, to corresponds, in sequence, to
the post office box; the post office box;
the extended address (e.g. apartment or suite number); the extended address (e.g., apartment or suite number);
the street address; the street address;
the locality (e.g., city); the locality (e.g., city);
the region (e.g., state or province); the region (e.g., state or province);
the postal code; the postal code;
the country name (full name in the language specified in the country name (full name in the language specified in
Section 5.1). Section 5.1).
When a component value is missing, the associated component When a component value is missing, the associated component
separator MUST still be specified. separator MUST still be specified.
Experience with vCard 3 has shown that the first two components Experience with vCard 3 has shown that the first two components
(post office box and extended address) are plagued with many (post office box and extended address) are plagued with many
interoperability issues. To ensure maximal interoperability, interoperability issues. To ensure maximal interoperability,
their values SHOULD be empty. their values SHOULD be empty.
The text components are separated by the SEMI-COLON character The text components are separated by the SEMICOLON character
(U+003B). Where it makes semantic sense, individual text (U+003B). Where it makes semantic sense, individual text
components can include multiple text values (e.g., a "street" components can include multiple text values (e.g., a "street"
component with multiple lines) separated by the COMMA character component with multiple lines) separated by the COMMA character
(U+002C). (U+002C).
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.
The property can also include a "LABEL" parameter to present a The property can also include a "LABEL" parameter to present a
delivery delivery address label for the address. Its value is a delivery address label for the address. Its value is a plain-text
plain-text string representing the formatted address. Newlines string representing the formatted address. Newlines are encoded
are encoded as \n, as they are for property values. as \n, as they are for property values.
ABNF: ABNF:
label-param = "LABEL=" param-value label-param = "LABEL=" param-value
ADR-param = "VALUE=text" / label-param / language-param ADR-param = "VALUE=text" / label-param / language-param
/ geo-parameter / tz-parameter / altid-param / pid-param / geo-parameter / tz-parameter / altid-param / pid-param
/ pref-param / type-param / any-param / pref-param / type-param / any-param
ADR-value = ADR-component-pobox ";" ADR-component-ext ";" ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
ADR-component-street ";" ADR-component-locality ";" ADR-component-street ";" ADR-component-locality ";"
ADR-component-region ";" ADR-component-code ";" ADR-component-region ";" ADR-component-code ";"
ADR-component-country ADR-component-country
ADR-component-pobox = list-component ADR-component-pobox = list-component
ADR-component-ext = list-component ADR-component-ext = list-component
ADR-component-street = list-component ADR-component-street = list-component
ADR-component-locality = list-component ADR-component-locality = list-component
ADR-component-region = list-component ADR-component-region = list-component
ADR-component-code = list-component ADR-component-code = list-component
skipping to change at page 35, line 35 skipping to change at page 34, line 17
ADR-component-region ";" ADR-component-code ";" ADR-component-region ";" ADR-component-code ";"
ADR-component-country ADR-component-country
ADR-component-pobox = list-component ADR-component-pobox = list-component
ADR-component-ext = list-component ADR-component-ext = list-component
ADR-component-street = list-component ADR-component-street = list-component
ADR-component-locality = list-component ADR-component-locality = list-component
ADR-component-region = list-component ADR-component-region = list-component
ADR-component-code = list-component ADR-component-code = list-component
ADR-component-country = list-component ADR-component-country = 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
are absent. address are absent.
ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n
Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n
U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A. U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
6.4. Communications Properties 6.4. Communications Properties
These properties describe information about how to communicate with These properties describe information about how to communicate with
the object the vCard represents. the object the vCard represents.
skipping to change at page 36, line 4 skipping to change at page 34, line 30
ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n
Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n
U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A. U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
6.4. Communications Properties 6.4. Communications Properties
These properties describe information about how to communicate with These properties describe information about how to communicate with
the object the vCard represents. the object the vCard represents.
6.4.1. TEL 6.4.1. TEL
Purpose: To specify the telephone number for telephony communication Purpose: To specify the telephone number for telephony communication
with the object the vCard represents. with the object the vCard represents.
Value type: By default it is a single free-form text value (for Value type: By default, it is a single free-form text value (for
backward compatibility with vCard 3), but it SHOULD be reset to a backward compatibility with vCard 3), but it SHOULD be reset to a
URI value. It is expected that the URI scheme will be "tel", as URI value. It is expected that the URI scheme will be "tel", as
specified in [RFC3966], but other schemes MAY be used. specified in [RFC3966], but other schemes MAY be used.
Cardinality: * Cardinality: *
Special notes: This property is based on the X.520 Telephone Number Special notes: This property is based on the X.520 Telephone Number
attribute. attribute [CCITT.X520.1988].
The property can include the "PREF" parameter to indicate a The property can include the "PREF" parameter to indicate a
preferred-use telephone number. preferred-use telephone number.
The property can include the parameter "TYPE" to specify intended The property can include the parameter "TYPE" to specify intended
use for the telephone number. The predefined values for the TYPE use for the telephone number. The predefined values for the TYPE
parameter are: parameter are:
+-----------+-------------------------------------------------------+ +-----------+-------------------------------------------------------+
| Value | Description | | Value | Description |
+-----------+-------------------------------------------------------+ +-----------+-------------------------------------------------------+
| text | Indicates that the telephone number supports text | | text | Indicates that the telephone number supports text |
| | messages (SMS). | | | messages (SMS). |
| voice | Indicates a voice telephone number. | | voice | Indicates a voice telephone number. |
| fax | Indicates a facsimile telephone number. | | fax | Indicates a facsimile telephone number. |
| cell | Indicates a cellular or mobile telephone number. | | cell | Indicates a cellular or mobile telephone number. |
| video | Indicates a video conferencing telephone number. | | video | Indicates a video conferencing telephone number. |
| pager | Indicates a paging device telephone number. | | pager | Indicates a paging device telephone number. |
| textphone | Indicates a telecommunication device for people with | | textphone | Indicates a telecommunication device for people with |
| | hearing or speech difficulties.. | | | hearing or speech difficulties. |
+-----------+-------------------------------------------------------+ +-----------+-------------------------------------------------------+
The default type is "voice". These type parameter values can be The default type is "voice". These type parameter values can be
specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a
value list (e.g., TYPE="text,voice"). The default can be value list (e.g., TYPE="text,voice"). The default can be
overridden to another set of values by specifying one or more overridden to another set of values by specifying one or more
alternate values. For example, the default TYPE of "voice" can be alternate values. For example, the default TYPE of "voice" can be
reset to a VOICE and FAX telephone number by the value list reset to a VOICE and FAX telephone number by the value list
TYPE="voice,fax". TYPE="voice,fax".
If this property's value is a URI that can also be used for If this property's value is a URI that can also be used for
instant messaging, the IMPP (Section 6.4.3) property SHOULD be instant messaging, the IMPP (Section 6.4.3) property SHOULD be
used in addition to this property. used in addition to this property.
ABNF: ABNF:
TEL-param = TEL-text-param / TEL-uri-param TEL-param = TEL-text-param / TEL-uri-param
TEL-value = TEL-text-value / TEL-uri-value TEL-value = TEL-text-value / TEL-uri-value
; Value and parameter MUST match ; Value and parameter MUST match.
TEL-text-param = "VALUE=text" TEL-text-param = "VALUE=text"
TEL-text-value = text TEL-text-value = text
TEL-uri-param = "VALUE=uri" / mediatype-param TEL-uri-param = "VALUE=uri" / mediatype-param
TEL-uri-value = URI TEL-uri-value = URI
TEL-param =/ type-param / pid-param / pref-param / altid-param TEL-param =/ type-param / pid-param / pref-param / altid-param
/ any-param / any-param
skipping to change at page 37, line 43 skipping to change at page 36, line 24
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
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.
Even though the value is free-form UTF-8 text, it is likely to be Even though the value is free-form UTF-8 text, it is likely to be
interpreted by an MUA as an "addr-spec", as defined in [RFC5322], interpreted by a Mail User Agent (MUA) as an "addr-spec", as
section 3.4.1. Readers should also be aware of the current work defined in [RFC5322], Section 3.4.1. Readers should also be aware
toward internationalized email addresses of the current work toward internationalized email addresses
[I-D.ietf-eai-rfc5335bis]. [RFC5335bis].
ABNF: ABNF:
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ altid-param / any-param / altid-param / any-param
EMAIL-value = text EMAIL-value = text
Example: Example:
EMAIL;TYPE=work:jqpublic@xyz.example.com EMAIL;TYPE=work:jqpublic@xyz.example.com
skipping to change at page 39, line 34 skipping to change at page 38, line 12
Purpose: To specify information related to the time zone of the Purpose: To specify information related to the time zone of the
object the vCard represents. object the vCard represents.
Value type: The default is a single text value. It can also be Value type: The default is a single text value. It can also be
reset to a single URI or utc-offset value. reset to a single URI or utc-offset value.
Cardinality: * Cardinality: *
Special notes: It is expected that names from the public-domain Special notes: It is expected that names from the public-domain
Olson database [TZ-DB] will be used, but this is not a Olson database [TZ-DB] will be used, but this is not a
restriction. See also [I-D.lear-iana-timezone-database]. restriction. See also [IANA-TZ].
Efforts are currently being directed at creating a standard URI Efforts are currently being directed at creating a standard URI
scheme for expressing time zone information. Usage of such a scheme for expressing time zone information. Usage of such a
scheme would ensure a high level of interoperability between scheme would ensure a high level of interoperability between
implementations that support it. implementations that support it.
Note that utc-offset values SHOULD NOT be used because the UTC Note that utc-offset values SHOULD NOT be used because the UTC
offset varies with time - not just because of the usual daylight offset varies with time -- not just because of the usual daylight
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 =/ altid-param / pid-param / pref-param / type-param TZ-param =/ altid-param / pid-param / pref-param / type-param
/ mediatype-param / any-param / mediatype-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
Purpose: To specify information related to the global positioning of Purpose: To specify information related to the global positioning of
the object the vCard represents. the object the vCard represents.
Value type: A single URI. Value type: A single URI.
Cardinality: * Cardinality: *
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
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
GEO-value = URI GEO-value = URI
Example: Example:
skipping to change at page 41, line 4 skipping to change at page 39, line 22
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
object that the vCard represents. object that the vCard represents.
6.6.1. TITLE 6.6.1. TITLE
Purpose: To specify the position or job of the object the vCard Purpose: To specify the position or job of the object the vCard
represents. represents.
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
Special notes: This property is based on the X.520 Title attribute. Special notes: This property is based on the X.520 Title attribute
[CCITT.X520.1988].
ABNF: ABNF:
TITLE-param = "VALUE=text" / language-param / pid-param TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / altid-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
skipping to change at page 41, line 31 skipping to change at page 40, line 4
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.
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
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 [CCITT.X520.1988]. This property is
organizational type to avoid confusion with the semantics of the included as an organizational type to avoid confusion with the
TITLE property and incorrect usage of that property when the semantics of the TITLE property and incorrect usage of that
semantics of this property is intended. property when the 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 / altid-param / any-param / type-param / altid-param / any-param
ROLE-value = text ROLE-value = text
Example: Example:
ROLE:Project Leader ROLE:Project Leader
skipping to change at page 42, line 35 skipping to change at page 40, line 50
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...> <...the remainder of base64-encoded data...>
6.6.4. ORG 6.6.4. ORG
Purpose: To specify the organizational name and units associated Purpose: To specify the organizational name and units associated
with the vCard. with the vCard.
Value type: A single structured text value consisting of components Value type: A single structured text value consisting of components
separated by the SEMI-COLON character (U+003B). separated by the SEMICOLON character (U+003B).
Cardinality: * Cardinality: *
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 [CCITT.X520.1988]. The property
structured type consisting of the organization name, followed by value is a structured type consisting of the organization name,
zero or more levels of organizational unit names. followed by 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 / altid-param / type-param / pid-param / pref-param / altid-param / type-param
/ any-param / any-param
ORG-value = component *(";" component) ORG-value = component *(";" component)
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
6.6.5. MEMBER 6.6.5. MEMBER
Purpose: To include a member in the group this vCard represents. Purpose: To include a member in the group this vCard represents.
Value type: A single URI. It MAY refer to something other than a Value type: A single URI. It MAY refer to something other than a
vCard object. For example, an e-mail distribution list could vCard object. For example, an email distribution list could
employ the "mailto" URI scheme [RFC6068] for efficiency. employ the "mailto" URI scheme [RFC6068] for efficiency.
Cardinality: * Cardinality: *
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 / altid-param MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
skipping to change at page 44, line 26 skipping to change at page 42, line 47
Purpose: To specify a relationship between another entity and the Purpose: To specify a relationship between another entity and the
entity represented by this vCard. entity represented by this vCard.
Value type: A single URI. It can also be reset to a single text Value type: A single URI. It can also be reset to a single text
value. The text value can be used to specify textual information. value. The text value can be used to specify textual information.
Cardinality: * Cardinality: *
Special notes: The TYPE parameter MAY be used to characterize the Special notes: The TYPE parameter MAY be used to characterize the
related entity. It contains a comma-separated list of values that related entity. It contains a comma-separated list of values that
are registered from IANA as described in Section 10.2. The are registered with IANA as described in Section 10.2. The
registry is pre-populated with the values defined in [xfn]. This registry is pre-populated with the values defined in [xfn]. This
document also specifies two additional values: document also specifies two additional values:
agent: an entity who may sometimes act on behalf of the entity agent: an entity who may sometimes act on behalf of the entity
associated with the vCard. associated with the vCard.
emergency: indicates an emergency contact emergency: indicates an emergency contact
ABNF: ABNF:
skipping to change at page 45, line 42 skipping to change at page 43, line 46
6.7. Explanatory Properties 6.7. Explanatory Properties
These properties are concerned with additional explanations, such as These properties are concerned with additional explanations, such as
that related to informational notes or revisions specific to the that related to informational notes or revisions specific to the
vCard. vCard.
6.7.1. CATEGORIES 6.7.1. CATEGORIES
Purpose: To specify application category information about the Purpose: To specify application category information about the
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
(U+002C). (U+002C).
Cardinality: * Cardinality: *
ABNF: ABNF:
CATEGORIES-param = "VALUE=text" / pid-param / pref-param CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ type-param / altid-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 46, line 23 skipping to change at page 44, line 26
6.7.2. NOTE 6.7.2. NOTE
Purpose: To specify supplemental information or a comment that is Purpose: To specify supplemental information or a comment that is
associated with the vCard. associated with the vCard.
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
Special notes: The property is based on the X.520 Description Special notes: The property is based on the X.520 Description
attribute. attribute [CCITT.X520.1988].
ABNF: ABNF:
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-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
skipping to change at page 48, line 24 skipping to change at page 46, line 26
Purpose: To specify a value that represents a globally unique Purpose: To specify a value that represents a globally unique
identifier corresponding to the entity associated with the vCard. identifier corresponding to the entity associated with the vCard.
Value type: A single URI value. It MAY also be reset to free-form Value type: A single URI value. It MAY also be reset to free-form
text. text.
Cardinality: *1 Cardinality: *1
Special notes: This property is used to uniquely identify the object Special notes: This property is used to uniquely identify the object
that the vCard represents. The "uuid" URN namespace defined in that the vCard represents. The "uuid" URN namespace defined in
[RFC4122] is particularly well-suited to this task, but other URI [RFC4122] is particularly well suited to this task, but other URI
schemes MAY be used. Free-form text MAY also be used. schemes MAY be used. Free-form text MAY also be used.
ABNF: ABNF:
UID-param = UID-uri-param / UID-text-param UID-param = UID-uri-param / UID-text-param
UID-value = UID-uri-value / UID-text-value UID-value = UID-uri-value / UID-text-value
; Value and parameter MUST match. ; Value and parameter MUST match.
UID-uri-param = "VALUE=uri" UID-uri-param = "VALUE=uri"
UID-uri-value = URI UID-uri-value = URI
skipping to change at page 48, line 52 skipping to change at page 47, line 12
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
6.7.7. CLIENTPIDMAP 6.7.7. CLIENTPIDMAP
Purpose: To give a global meaning to a local PID source identifier. Purpose: To give a global meaning to a local PID source identifier.
Value type: A semicolon-separated pair of values. The first field Value type: A semicolon-separated pair of values. The first field
is a small integer corresponding to the second field of a PID is a small integer corresponding to the second field of a PID
parameter instance. The second field is a URI. The "uuid" URN parameter instance. The second field is a URI. The "uuid" URN
namespace defined in [RFC4122] is particularly well-suited to this namespace defined in [RFC4122] is particularly well suited to this
task, but other URI schemes MAY be used. task, but other URI schemes MAY be used.
Cardinality: * Cardinality: *
Special notes: PID source identifiers (the source identifier is the Special notes: PID source identifiers (the source identifier is the
second field in a PID parameter instance) are small integers that second field in a PID parameter instance) are small integers that
only have significance within the scope of a single vCard only have significance within the scope of a single vCard
instance. Each distinct source identifier present in a vCard MUST instance. Each distinct source identifier present in a vCard MUST
have an associated CLIENTPIDMAP. See Section 7 for more details have an associated CLIENTPIDMAP. See Section 7 for more details
on the usage of CLIENTPIDMAP. on the usage of CLIENTPIDMAP.
skipping to change at page 49, line 36 skipping to change at page 47, line 45
Example: Example:
TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555 TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5 CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
6.7.8. URL 6.7.8. URL
Purpose: To specify a uniform resource locator associated with the Purpose: To specify a uniform resource locator associated with the
object that the vCard refers to. Examples for individuals include object to which the vCard refers. Examples for individuals
personal web sites, blogs, and social networking site identifiers. include personal web sites, blogs, and social networking site
identifiers.
Cardinality: * Cardinality: *
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
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
URL-value = URI URL-value = URI
skipping to change at page 54, line 9 skipping to change at page 52, line 12
equivalent MUST be matched. Equivalence is determined as specified equivalent MUST be matched. Equivalence is determined as specified
in [RFC3986], Section 6. in [RFC3986], Section 6.
In all other cases, vCard instances MAY be matched at the discretion In all other cases, vCard instances MAY be matched at the discretion
of the synchronization engine. of the synchronization engine.
7.1.2. Matching Property Instances 7.1.2. Matching Property Instances
Property instances belonging to unmatched vCards MUST NOT be matched. Property instances belonging to unmatched vCards MUST NOT be matched.
Property instances whose name (e.g. EMAIL, TEL, etc.) is not the Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
same MUST NOT be matched. same MUST NOT be matched.
Property instances whose name is CLIENTPIDMAP are handled separately Property instances whose name is CLIENTPIDMAP are handled separately
and MUST NOT be matched. The synchronization MUST ensure that there and MUST NOT be matched. The synchronization MUST ensure that there
is consistency of CLIENTPIDMAPs among matched vCard instances. is consistency of CLIENTPIDMAPs among matched vCard instances.
Property instances belonging to matched vCards, whose name is the Property instances belonging to matched vCards, whose name is the
same, and whose maximum cardinality is 1 MUST be matched. same, and whose maximum cardinality is 1, MUST be matched.
Property instances belonging to matched vCards, whose name is the Property instances belonging to matched vCards, whose name is the
same, and whose PID parameters match MUST be matched. See same, and whose PID parameters match, MUST be matched. See
Section 7.1.3 for details on PID matching. Section 7.1.3 for details on PID matching.
In all other cases, property instances MAY be matched at the In all other cases, property instances MAY be matched at the
discretion of the synchronization engine. discretion of the synchronization engine.
7.1.3. PID Matching 7.1.3. PID Matching
Two PID values for which the first fields are equivalent represent Two PID values for which the first fields are equivalent represent
the same local value. the same local value.
skipping to change at page 55, line 51 skipping to change at page 53, line 48
with "urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which with "urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which
represents the creating device. We are at liberty to reuse the same represents the creating device. We are at liberty to reuse the same
local value since instances of different properties will never be local value since instances of different properties will never be
matched. The N property has no PID because it is forbidden by its matched. The N property has no PID because it is forbidden by its
maximum cardinality of 1. maximum cardinality of 1.
7.2.2. Initial Sharing 7.2.2. Initial Sharing
This vCard is shared with a second device. Upon inspecting the UID This vCard is shared with a second device. Upon inspecting the UID
property, the second device understands that this is a new vCard property, the second device understands that this is a new vCard
(i.e. unmatched) and thus the synchronization results in a simple (i.e., unmatched) and thus the synchronization results in a simple
copy. copy.
7.2.3. Adding and Sharing a Property 7.2.3. Adding and Sharing a Property
A new phone number is created on the first device, then the vCard is A new phone number is created on the first device, then the vCard is
shared with the second device. This is what the second device shared with the second device. This is what the second device
receives: receives:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
skipping to change at page 57, line 41 skipping to change at page 55, line 41
the new EMAIL and TEL properties. On the second device, a new source the new EMAIL and TEL properties. On the second device, a new source
identifier (2) is generated, and a corresponding CLIENTPIDMAP identifier (2) is generated, and a corresponding CLIENTPIDMAP
property is created. It contains the second device's identifier, property is created. It contains the second device's identifier,
"urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee". "urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".
The new EMAIL properties are unmatched on both sides since the PID The new EMAIL properties are unmatched on both sides since the PID
global value is new in both cases. The sync thus results in a copy global value is new in both cases. The sync thus results in a copy
on both sides. on both sides.
Although the situation appears to be the same for the TEL properties, Although the situation appears to be the same for the TEL properties,
in this case the synchronization engine is particularly smart and in this case, the synchronization engine is particularly smart and
matches the two new TEL properties even though their PID global matches the two new TEL properties even though their PID global
values are different. Note that in this case, the rules of section values are different. Note that in this case, the rules of
Section 7.1.2 state that two properties MAY be matched at the Section 7.1.2 state that two properties MAY be matched at the
discretion of the synchronization engine. Therefore, the two discretion of the synchronization engine. Therefore, the two
properties are merged. properties are merged.
All this results in the following vCard which is stored on both All this results in the following vCard, which is stored on both
devices: devices:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe FN:J. Doe
N:Doe;J.;;; N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com EMAIL;PID=2.1:boss@example.com
EMAIL;PID=2.2:ceo@example.com EMAIL;PID=2.2:ceo@example.com
skipping to change at page 58, line 42 skipping to change at page 56, line 42
EMAIL;PID=2.1:boss@example.com EMAIL;PID=2.1:boss@example.com
EMAIL;PID=3.1:ceo@example.com EMAIL;PID=3.1:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555 TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666 TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD END:VCARD
The details of global context simplification are unspecified by this The details of global context simplification are unspecified by this
document. They are left up to the synchronization engine. This document. They are left up to the synchronization engine. This
example is merely intended to illustrate the possibility, which example is merely intended to illustrate the possibility, which
investigating would be, in the authors' opinion, worthwhile. investigating would be, in the author's opinion, worthwhile.
8. Example: Author's vCard 8. Example: Author's vCard
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Simon Perreault FN:Simon Perreault
N:Perreault;Simon;;;ing. jr,M.Sc. N:Perreault;Simon;;;ing. jr,M.Sc.
BDAY:--0203 BDAY:--0203
ANNIVERSARY:20090808T1430-0500 ANNIVERSARY:20090808T1430-0500
GENDER:M GENDER:M
skipping to change at page 59, line 32 skipping to change at page 57, line 22
GEO;TYPE=work:geo:46.772673,-71.282945 GEO;TYPE=work:geo:46.772673,-71.282945
KEY;TYPE=work;VALUE=uri: KEY;TYPE=work;VALUE=uri:
http://www.viagenie.ca/simon.perreault/simon.asc http://www.viagenie.ca/simon.perreault/simon.asc
TZ:-0500 TZ:-0500
URL;TYPE=home:http://nomis80.org URL;TYPE=home:http://nomis80.org
END:VCARD END:VCARD
9. Security Considerations 9. Security Considerations
o Internet mail is often used to transport vCards and is subject to o Internet mail is often used to transport vCards and is subject to
many well known security attacks, including monitoring, replay, many well-known security attacks, including monitoring, replay,
and forgery. Care should be taken by any directory service in and forgery. Care should be taken by any directory service in
allowing information to leave the scope of the service itself, allowing information to leave the scope of the service itself,
where any access controls or confidentiality can no longer be where any access controls or confidentiality can no longer be
guaranteed. Applications should also take care to display guaranteed. Applications should also take care to display
directory data in a "safe" environment directory data in a "safe" environment.
o vCards can carry cryptographic keys or certificates, as described o vCards can carry cryptographic keys or certificates, as described
in Section 6.8.1. in Section 6.8.1.
o vCards often carry information that can be sensitive (e.g. o vCards often carry information that can be sensitive (e.g.,
birthday, address, and phone information). Although vCards have birthday, address, and phone information). Although vCards have
no inherent authentication or confidentiality provisions, they can no inherent authentication or confidentiality provisions, they can
easily be carried by any security mechanism that transfers MIME easily be carried by any security mechanism that transfers MIME
objects to address authentication or confidentiality (e.g. S/MIME objects to address authentication or confidentiality (e.g., S/MIME
[RFC5751], OpenPGP [RFC4880]). In cases where the confidentiality [RFC5751], OpenPGP [RFC4880]). In cases where the confidentiality
or authenticity of information contained in vCard is a concern, or authenticity of information contained in vCard is a concern,
the vCard SHOULD be transported using one of these secure the vCard SHOULD be transported using one of these secure
mechanisms. The KEY property (Section 6.8.1) can be used to mechanisms. The KEY property (Section 6.8.1) can be used to
transport the public key used by these mechanisms. transport the public key used by these mechanisms.
o The information in a vCard may become out of date. In cases where o The information in a vCard may become out of date. In cases where
the vitality of data is important to an originator of a vCard, the the vitality of data is important to an originator of a vCard, the
SOURCE property (Section 6.1.3) SHOULD be specified. In addition, SOURCE property (Section 6.1.3) SHOULD be specified. In addition,
the "REV" type described in section Section 6.7.4 can be specified the "REV" type described in Section 6.7.4 can be specified to
to indicate the last time that the vCard data was updated. indicate the last time that the vCard data was updated.
o Many vCard properties may be used to transport URIs. Please refer o Many vCard properties may be used to transport URIs. Please refer
to [RFC3986] section 7 for considerations related to URIs. to [RFC3986], Section 7, for considerations related to URIs.
10. IANA Considerations 10. IANA Considerations
10.1. Media Type Registration 10.1. Media Type Registration
IANA is asked to register the following Media Type (in IANA has registered the following Media Type (in
<http://www.iana.org/assignments/media-types/>), and to mark the <http://www.iana.org/>) and marked the text/directory Media Type as
text/directory Media Type as DEPRECATED. DEPRECATED.
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of media type text/vcard Subject: Registration of media type text/vcard
Type name: text Type name: text
Subtype name: vcard Subtype name: vcard
Required parameters: none Required parameters: none
skipping to change at page 61, line 10 skipping to change at page 58, line 50
While these formats are similar, they are not strictly compatible. While these formats are similar, they are not strictly compatible.
In general, it is necessary to inspect the value of the VERSION In general, it is necessary to inspect the value of the VERSION
property (see Section 6.7.9) for identifying the standard to which property (see Section 6.7.9) for identifying the standard to which
a given vCard object conforms. a given vCard object conforms.
In addition, the following media types are known to have been used In addition, the following media types are known to have been used
to refer to vCard data. They should be considered deprecated in to refer to vCard data. They should be considered deprecated in
favor of text/vcard. favor of text/vcard.
* text/directory * text/directory
* text/directory; profile=vcard * text/directory; profile=vcard
* text/x-vcard * text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-22 Published specification: RFC 6350
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, and customer relationship
management software. management software.
Additional information: Additional information:
Magic number(s): Magic number(s):
File extension(s): .vcf .vcard File extension(s): .vcf .vcard
Macintosh file type code(s): Macintosh file type code(s):
skipping to change at page 61, line 44 skipping to change at page 59, line 34
Restrictions on usage: none Restrictions on usage: none
Author: Simon Perreault Author: Simon Perreault
Change controller: IETF Change controller: IETF
10.2. Registering New vCard Elements 10.2. Registering New vCard Elements
This section defines the process for registering new or modified This section defines the process for registering new or modified
vCard elements (i.e. properties, parameters, value data types, and vCard elements (i.e., properties, parameters, value data types, and
values) with IANA. It does not contain any immediate IANA actions. values) with IANA.
10.2.1. Registration Procedure 10.2.1. Registration Procedure
The IETF will create a mailing list, vcarddav@ietf.org [1], which can The IETF has created a mailing list, vcarddav@ietf.org, which can be
be used for public discussion of vCard element proposals prior to used for public discussion of vCard element proposals prior to
registration. Use of the mailing list is strongly encouraged. The registration. Use of the mailing list is strongly encouraged. The
IESG will appoint a designated expert who will monitor the IESG has appointed a designated expert who will monitor the
vcarddav@ietf.org [1] mailing list and review registrations. vcarddav@ietf.org mailing list and review registrations.
Registration of new vCard elements MUST be reviewed by the designated Registration of new vCard elements MUST be reviewed by the designated
expert and published in an RFC. A Standard Track RFC is REQUIRED for expert and published in an RFC. A Standards Track RFC is REQUIRED
the registration of new value data types that modify existing for the registration of new value data types that modify existing
properties. A Standard Track RFC is also REQUIRED for registration properties. A Standards Track RFC is also REQUIRED for registration
of vCard elements that modify vCard elements previously documented in of vCard elements that modify vCard elements previously documented in
a Standard Track RFC. a Standards Track RFC.
The registration procedure begins when a completed registration The registration procedure begins when a completed registration
template, defined in the sections below, is sent to template, defined in the sections below, is sent to vcarddav@ietf.org
vcarddav@ietf.org [1] and iana@iana.org [2]. The designated expert and iana@iana.org. Within two weeks, the designated expert is
is expected to tell IANA and the submitter of the registration within expected to tell IANA and the submitter of the registration whether
two weeks whether the registration is approved, approved with minor the registration is approved, approved with minor changes, or
changes, or rejected with cause. When a registration is rejected rejected with cause. When a registration is rejected with cause, it
with cause, it can be re-submitted if the concerns listed in the can be re-submitted if the concerns listed in the cause are
cause are addressed. Decisions made by the designated expert can be addressed. Decisions made by the designated expert can be appealed
appealed to the IESG Applications Area Director, then to the IESG. to the IESG Applications Area Director, then to the IESG. They
They follow the normal appeals procedure for IESG decisions. follow the normal appeals procedure for IESG decisions.
Once the registration procedure concludes successfully, IANA creates Once the registration procedure concludes successfully, IANA creates
or modifies the corresponding record in the vCard registry. The or modifies the corresponding record in the vCard registry. The
completed registration template is discarded. completed registration template is discarded.
An RFC specifying new vCard elements MUST include the completed An RFC specifying new vCard elements MUST include the completed
registration templates, which MAY be expanded with additional registration templates, which MAY be expanded with additional
information. These completed templates are intended to go in the information. These completed templates are intended to go in the
body of the document, not in the IANA Considerations section. body of the document, not in the IANA Considerations section.
Finally, note that there is an XML representation for vCard defined Finally, note that there is an XML representation for vCard defined
in [I-D.ietf-vcarddav-vcardxml]. An XML representation SHOULD be in [RFC6351]. An XML representation SHOULD be defined for new vCard
defined for new vCard elements. elements.
10.2.2. Vendor Namespace 10.2.2. Vendor Namespace
The vendor namespace is used for vCard elements associated with The vendor namespace is used for vCard elements associated with
commercially available products. "Vendor" or "producer" are commercially available products. "Vendor" or "producer" are
construed as equivalent and very broadly in this context. construed as equivalent and very broadly in this context.
A registration may be placed in the vendor namespace by anyone who A registration may be placed in the vendor namespace by anyone who
needs to interchange files associated with the particular product. needs to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or However, the registration formally belongs to the vendor or
skipping to change at page 63, line 9 skipping to change at page 60, line 49
registered. Changes to the specification will be made at their registered. Changes to the specification will be made at their
request, as discussed in subsequent sections. request, as discussed in subsequent sections.
vCard elements belonging to the vendor namespace will be vCard elements belonging to the vendor namespace will be
distinguished by the "VND-" prefix. This is followed by an IANA- distinguished by the "VND-" prefix. This is followed by an IANA-
registered Private Enterprise Number (PEN), a dash, and a vCard registered Private Enterprise Number (PEN), a dash, and a vCard
element designation of the vendor's choosing (e.g., "VND-123456- element designation of the vendor's choosing (e.g., "VND-123456-
MUDPIE"). MUDPIE").
While public exposure and review of vCard elements to be registered While public exposure and review of vCard elements to be registered
in the vendor namespace is not required, using the in the vendor namespace are not required, using the vcarddav@ietf.org
vcarddav@ietf.org [1] mailing list for review is strongly encouraged mailing list for review is strongly encouraged to improve the quality
to improve the quality of those specifications. Registrations in the of those specifications. Registrations in the vendor namespace may
vendor namespace may be submitted directly to the IANA. be submitted directly to the IANA.
10.2.3. Registration Template for Properties 10.2.3. Registration Template for Properties
A property is defined by completing the following template. A property is defined by completing the following template.
Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor- Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-
specific property (where NNNN is replaced by the vendor's PEN). specific property (where NNNN is replaced by the vendor's PEN).
Property name: The name of the property. Property name: The name of the property.
skipping to change at page 63, line 41 skipping to change at page 61, line 32
Property parameters: Any of the valid property parameters for the Property parameters: Any of the valid property parameters for the
property MUST be specified. property MUST be specified.
Description: Any special notes about the property, how it is to be Description: Any special notes about the property, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the property definition needs to be Format definition: The ABNF for the property definition needs to be
specified. specified.
Example(s): One or more examples of instances of the property needs Example(s): One or more examples of instances of the property need
to be specified. to be specified.
10.2.4. Registration Template for Parameters 10.2.4. Registration Template for Parameters
A parameter is defined by completing the following template. A parameter is defined by completing the following template.
Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor- Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-
specific property (where NNNN is replaced by the vendor's PEN). specific property (where NNNN is replaced by the vendor's PEN).
Parameter name: The name of the parameter. Parameter name: The name of the parameter.
Purpose: The purpose of the parameter. Give a short but clear Purpose: The purpose of the parameter. Give a short but clear
description. description.
Description: Any special notes about the parameter, how it is to be Description: Any special notes about the parameter, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the parameter definition needs to be Format definition: The ABNF for the parameter definition needs to be
specified. specified.
Example(s): One or more examples of instances of the parameter needs Example(s): One or more examples of instances of the parameter need
to be specified. to be specified.
10.2.5. Registration Template for Value Data Types 10.2.5. Registration Template for Value Data Types
A value data type is defined by completing the following template. A value data type is defined by completing the following template.
Value name: The name of the value type. Value name: The name of the value type.
Purpose: The purpose of the value type. Give a short but clear Purpose: The purpose of the value type. Give a short but clear
description. description.
Description: Any special notes about the value type, how it is to be Description: Any special notes about the value type, how it is to be
used, etc. used, etc.
Format definition: The ABNF for the value type definition needs to Format definition: The ABNF for the value type definition needs to
be specified. be specified.
Example(s): One or more examples of instances of the value type Example(s): One or more examples of instances of the value type need
needs to be specified. to be specified.
10.2.6. Registration Template for Values 10.2.6. Registration Template for Values
A value is defined by completing the following template. A value is defined by completing the following template.
Value: The value literal. Value: The value literal.
Purpose: The purpose of the value. Give a short but clear Purpose: The purpose of the value. Give a short but clear
description. description.
Conformance: The vCard properties and/or parameters that can take Conformance: The vCard properties and/or parameters that can take
this value needs to be specified. this value needs to be specified.
Example(s): One or more examples of instances of the value needs to Example(s): One or more examples of instances of the value need to
be specified. be specified.
The following is a fictitious example of a registration of a vCard The following is a fictitious example of a registration of a vCard
value: value:
Value: supervisor Value: supervisor
Purpose: It means that the related entity is the direct hierarchical Purpose: It means that the related entity is the direct hierarchical
superior (i.e. supervisor or manager) of the entity this vCard superior (i.e., supervisor or manager) of the entity this vCard
represents. represents.
Conformance: This value can be used with the "TYPE" parameter Conformance: This value can be used with the "TYPE" parameter
applied on the "RELATED" property. applied on the "RELATED" property.
Example(s): Example(s):
RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
10.3. Initial vCard Elements Registries 10.3. Initial vCard Elements Registries
The IANA is requested to create and maintain the following registries The IANA has created and will maintain the following registries for
for vCard elements with pointers to appropriate reference documents. vCard elements with pointers to appropriate reference documents. The
The registries will be grouped together under the heading "vCard registries are grouped together under the heading "vCard Elements".
Elements".
10.3.1. Properties Registry 10.3.1. Properties Registry
The following table is to be used to initialize the properties The following table has been used to initialize the properties
registry. registry.
+-----------+--------------+------------------------+ +-----------+--------------+-------------------------+
| Namespace | Property | Reference | | Namespace | Property | Reference |
+-----------+--------------+------------------------+ +-----------+--------------+-------------------------+
| | SOURCE | RFCXXXX, Section 6.1.3 | | | SOURCE | RFC 6350, Section 6.1.3 |
| | KIND | RFCXXXX, Section 6.1.4 | | | KIND | RFC 6350, Section 6.1.4 |
| | XML | RFCXXXX, Section 6.1.5 | | | XML | RFC 6350, Section 6.1.5 |
| | FN | RFCXXXX, Section 6.2.1 | | | FN | RFC 6350, Section 6.2.1 |
| | N | RFCXXXX, Section 6.2.2 | | | N | RFC 6350, Section 6.2.2 |
| | NICKNAME | RFCXXXX, Section 6.2.3 | | | NICKNAME | RFC 6350, Section 6.2.3 |
| | PHOTO | RFCXXXX, Section 6.2.4 | | | PHOTO | RFC 6350, Section 6.2.4 |
| | BDAY | RFCXXXX, Section 6.2.5 | | | BDAY | RFC 6350, Section 6.2.5 |
| | ANNIVERSARY | RFCXXXX, Section 6.2.6 | | | ANNIVERSARY | RFC 6350, Section 6.2.6 |
| | GENDER | RFCXXXX, Section 6.2.7 | | | GENDER | RFC 6350, Section 6.2.7 |
| | ADR | RFCXXXX, Section 6.3.1 | | | ADR | RFC 6350, Section 6.3.1 |
| | TEL | RFCXXXX, Section 6.4.1 | | | TEL | RFC 6350, Section 6.4.1 |
| | EMAIL | RFCXXXX, Section 6.4.2 | | | EMAIL | RFC 6350, Section 6.4.2 |
| | IMPP | RFCXXXX, Section 6.4.3 | | | IMPP | RFC 6350, Section 6.4.3 |
| | LANG | RFCXXXX, Section 6.4.4 | | | LANG | RFC 6350, Section 6.4.4 |
| | TZ | RFCXXXX, Section 6.5.1 | | | TZ | RFC 6350, Section 6.5.1 |
| | GEO | RFCXXXX, Section 6.5.2 | | | GEO | RFC 6350, Section 6.5.2 |
| | TITLE | RFCXXXX, Section 6.6.1 | | | TITLE | RFC 6350, Section 6.6.1 |
| | ROLE | RFCXXXX, Section 6.6.2 | | | ROLE | RFC 6350, Section 6.6.2 |
| | LOGO | RFCXXXX, Section 6.6.3 | | | LOGO | RFC 6350, Section 6.6.3 |
| | ORG | RFCXXXX, Section 6.6.4 | | | ORG | RFC 6350, Section 6.6.4 |
| | MEMBER | RFCXXXX, Section 6.6.5 | | | MEMBER | RFC 6350, Section 6.6.5 |
| | RELATED | RFCXXXX, Section 6.6.6 | | | RELATED | RFC 6350, Section 6.6.6 |
| | CATEGORIES | RFCXXXX, Section 6.7.1 | | | CATEGORIES | RFC 6350, Section 6.7.1 |
| | NOTE | RFCXXXX, Section 6.7.2 | | | NOTE | RFC 6350, Section 6.7.2 |
| | PRODID | RFCXXXX, Section 6.7.3 | | | PRODID | RFC 6350, Section 6.7.3 |
| | REV | RFCXXXX, Section 6.7.4 | | | REV | RFC 6350, Section 6.7.4 |
| | SOUND | RFCXXXX, Section 6.7.5 | | | SOUND | RFC 6350, Section 6.7.5 |
| | UID | RFCXXXX, Section 6.7.6 | | | UID | RFC 6350, Section 6.7.6 |
| | CLIENTPIDMAP | RFCXXXX, Section 6.7.7 | | | CLIENTPIDMAP | RFC 6350, Section 6.7.7 |
| | URL | RFCXXXX, Section 6.7.8 | | | URL | RFC 6350, Section 6.7.8 |
| | VERSION | RFCXXXX, Section 6.7.9 | | | VERSION | RFC 6350, Section 6.7.9 |
| | KEY | RFCXXXX, Section 6.8.1 | | | KEY | RFC 6350, Section 6.8.1 |
| | FBURL | RFCXXXX, Section 6.9.1 | | | FBURL | RFC 6350, Section 6.9.1 |
| | CALADRURI | RFCXXXX, Section 6.9.2 | | | CALADRURI | RFC 6350, Section 6.9.2 |
| | CALURI | RFCXXXX, Section 6.9.3 | | | CALURI | RFC 6350, Section 6.9.3 |
+-----------+--------------+------------------------+ +-----------+--------------+-------------------------+
10.3.2. Parameters Registry 10.3.2. Parameters Registry
The following table is to be used to initialize the parameters The following table has been used to initialize the parameters
registry. registry.
+-----------+-----------+-----------------------+ +-----------+-----------+------------------------+
| Namespace | Parameter | Reference | | Namespace | Parameter | Reference |
+-----------+-----------+-----------------------+ +-----------+-----------+------------------------+
| | LANGUAGE | RFCXXXX, Section 5.1 | | | LANGUAGE | RFC 6350, Section 5.1 |
| | VALUE | RFCXXXX, Section 5.2 | | | VALUE | RFC 6350, Section 5.2 |
| | PREF | RFCXXXX, Section 5.3 | | | PREF | RFC 6350, Section 5.3 |
| | ALTID | RFCXXXX, Section 5.4 | | | ALTID | RFC 6350, Section 5.4 |
| | PID | RFCXXXX, Section 5.5 | | | PID | RFC 6350, Section 5.5 |
| | TYPE | RFCXXXX, Section 5.6 | | | TYPE | RFC 6350, Section 5.6 |
| | MEDIATYPE | RFCXXXX, Section 5.7 | | | MEDIATYPE | RFC 6350, Section 5.7 |
| | CALSCALE | RFCXXXX, Section 5.8 | | | CALSCALE | RFC 6350, Section 5.8 |
| | SORT-AS | RFCXXXX, Section 5.9 | | | SORT-AS | RFC 6350, Section 5.9 |
| | GEO | RFCXXXX, Section 5.10 | | | GEO | RFC 6350, Section 5.10 |
| | TZ | RFCXXXX, Section 5.11 | | | TZ | RFC 6350, Section 5.11 |
+-----------+-----------+-----------------------+ +-----------+-----------+------------------------+
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 has been used to initialize the parameters
registry. registry.
+------------------+------------------------+ +------------------+-------------------------+
| Value Data Type | Reference | | Value Data Type | Reference |
+------------------+------------------------+ +------------------+-------------------------+
| BOOLEAN | RFCXXXX, Section 4.4 | | BOOLEAN | RFC 6350, Section 4.4 |
| DATE | RFCXXXX, Section 4.3.1 | | DATE | RFC 6350, Section 4.3.1 |
| TIME | RFCXXXX, Section 4.3.2 | | DATE-AND-OR-TIME | RFC 6350, Section 4.3.4 |
| DATE-TIME | RFCXXXX, Section 4.3.3 | | DATE-TIME | RFC 6350, Section 4.3.3 |
| DATE-AND-OR-TIME | RFCXXXX, Section 4.3.4 | | FLOAT | RFC 6350, Section 4.6 |
| TIMESTAMP | RFCXXXX, Section 4.3.5 | | INTEGER | RFC 6350, Section 4.5 |
| FLOAT | RFCXXXX, Section 4.6 | | LANGUAGE-TAG | RFC 6350, Section 4.8 |
| INTEGER | RFCXXXX, Section 4.5 | | TEXT | RFC 6350, Section 4.1 |
| TEXT | RFCXXXX, Section 4.1 | | TIME | RFC 6350, Section 4.3.2 |
| URI | RFCXXXX, Section 4.2 | | TIMESTAMP | RFC 6350, Section 4.3.5 |
| UTC-OFFSET | RFCXXXX, Section 4.7 | | URI | RFC 6350, Section 4.2 |
| LANGUAGE-TAG | RFCXXXX, Section 4.8 | | UTC-OFFSET | RFC 6350, Section 4.7 |
+------------------+------------------------+ +------------------+-------------------------+
10.3.4. Values Registries 10.3.4. Values Registries
Separate tables will be used for property and parameter values. Separate tables are 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 | Reference | | Property | Value | Reference |
+----------+------------+------------------------+ +----------+------------+-------------------------+
| BEGIN | VCARD | RFCXXXX, Section 6.1.1 | | BEGIN | VCARD | RFC 6350, Section 6.1.1 |
| END | VCARD | RFCXXXX, Section 6.1.2 | | END | VCARD | RFC 6350, Section 6.1.2 |
| KIND | individual | RFCXXXX, Section 6.1.4 | | KIND | individual | RFC 6350, Section 6.1.4 |
| KIND | group | RFCXXXX, Section 6.1.4 | | KIND | group | RFC 6350, Section 6.1.4 |
| KIND | org | RFCXXXX, Section 6.1.4 | | KIND | org | RFC 6350, Section 6.1.4 |
| KIND | location | RFCXXXX, Section 6.1.4 | | KIND | location | RFC 6350, Section 6.1.4 |
+----------+------------+------------------------+ +----------+------------+-------------------------+
The following table is to be used to initialize the parameter values The following table has been used to initialize the parameter values
registry. registry.
+------------------------+-----------+--------------+---------------+ +------------------------+-----------+--------------+---------------+
| Property | Parameter | Value | Reference | | Property | Parameter | Value | Reference |
+------------------------+-----------+--------------+---------------+ +------------------------+-----------+--------------+---------------+
| FN, NICKNAME, PHOTO, | TYPE | work | RFCXXXX, | | FN, NICKNAME, PHOTO, | TYPE | work | RFC 6350, |
| ADR, TEL, EMAIL, IMPP, | | | Section 5.6 | | ADR, TEL, EMAIL, IMPP, | | | Section 5.6 |
| LANG, TZ, GEO, TITLE, | | | | | LANG, TZ, GEO, TITLE, | | | |
| ROLE, LOGO, ORG, | | | | | ROLE, LOGO, ORG, | | | |
| RELATED, CATEGORIES, | | | | | RELATED, CATEGORIES, | | | |
| NOTE, SOUND, URL, KEY, | | | | | NOTE, SOUND, URL, KEY, | | | |
| FBURL, CALADRURI, and | | | | | FBURL, CALADRURI, and | | | |
| CALURI | | | | | CALURI | | | |
| FN, NICKNAME, PHOTO, | TYPE | home | RFCXXXX, | | FN, NICKNAME, PHOTO, | TYPE | home | RFC 6350, |
| ADR, TEL, EMAIL, IMPP, | | | Section 5.6 | | ADR, TEL, EMAIL, IMPP, | | | Section 5.6 |
| LANG, TZ, GEO, TITLE, | | | | | LANG, TZ, GEO, TITLE, | | | |
| ROLE, LOGO, ORG, | | | | | ROLE, LOGO, ORG, | | | |
| RELATED, CATEGORIES, | | | | | RELATED, CATEGORIES, | | | |
| NOTE, SOUND, URL, KEY, | | | | | NOTE, SOUND, URL, KEY, | | | |
| FBURL, CALADRURI, and | | | | | FBURL, CALADRURI, and | | | |
| CALURI | | | | | CALURI | | | |
| TEL | TYPE | text | RFCXXXX, | | TEL | TYPE | text | RFC 6350, |
| | | | Section 6.4.1 | | | | | Section 6.4.1 |
| TEL | TYPE | voice | RFCXXXX, | | TEL | TYPE | voice | RFC 6350, |
| | | | Section 6.4.1 | | | | | Section 6.4.1 |
| TEL | TYPE | fax | RFCXXXX, | | TEL | TYPE | fax | RFC 6350, |
| | | | Section 6.4.1 | | | | | Section 6.4.1 |
| TEL | TYPE | cell | RFCXXXX, | | TEL | TYPE | cell | RFC 6350, |
| | | | Section 6.4.1 | | | | | Section 6.4.1 |
| TEL | TYPE | video | RFCXXXX, | | TEL | TYPE | video | RFC 6350, |
| | | | Section 6.4.1 | | | | | Section 6.4.1 |
| TEL | TYPE | pager | RFCXXXX, | | TEL | TYPE | pager | RFC 6350, |
| | | | Section 6.4.1 | | | | | Section 6.4.1 |
| BDAY, ANNIVERSARY | CALSCALE | gregorian | RFCXXXX, | | TEL | TYPE | textphone | RFC 6350, |
| | | | Section 6.2.5 | | | | | Section 6.4.1 |
| RELATED | TYPE | contact | RFCXXXX, | | BDAY, ANNIVERSARY | CALSCALE | gregorian | RFC 6350, |
| | | | Section 5.8 |
| RELATED | TYPE | contact | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | acquaintance | RFCXXXX, | | RELATED | TYPE | acquaintance | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | friend | RFCXXXX, | | RELATED | TYPE | friend | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | met | RFCXXXX, | | RELATED | TYPE | met | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | co-worker | RFCXXXX, | | RELATED | TYPE | co-worker | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | colleague | RFCXXXX, | | RELATED | TYPE | colleague | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | co-resident | RFCXXXX, | | RELATED | TYPE | co-resident | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | neighbor | RFCXXXX, | | RELATED | TYPE | neighbor | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | child | RFCXXXX, | | RELATED | TYPE | child | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | parent | RFCXXXX, | | RELATED | TYPE | parent | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | sibling | RFCXXXX, | | RELATED | TYPE | sibling | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | spouse | RFCXXXX, | | RELATED | TYPE | spouse | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | kin | RFCXXXX, | | RELATED | TYPE | kin | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | muse | RFCXXXX, | | RELATED | TYPE | muse | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | crush | RFCXXXX, | | RELATED | TYPE | crush | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | date | RFCXXXX, | | RELATED | TYPE | date | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | sweetheart | RFCXXXX, | | RELATED | TYPE | sweetheart | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | me | RFCXXXX, | | RELATED | TYPE | me | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| | | | and [xfn] | | | | | and [xfn] |
| RELATED | TYPE | agent | RFCXXXX, | | RELATED | TYPE | agent | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
| RELATED | TYPE | emergency | RFCXXXX, | | RELATED | TYPE | emergency | RFC 6350, |
| | | | Section 6.6.6 | | | | | Section 6.6.6 |
+------------------------+-----------+--------------+---------------+ +------------------------+-----------+--------------+---------------+
11. Acknowledgements 11. Acknowledgments
The authors would like to thank Tim Howes, Mark Smith, and Frank The authors would like to thank Tim Howes, Mark Smith, and Frank
Dawson, the original authors of [RFC2425] and [RFC2426], Pete Dawson, the original authors of [RFC2425] and [RFC2426], Pete
Resnick, who got this effort started and provided help along the way, Resnick, who got this effort started and provided help along the way,
as well as the following individuals who have participated in the as well as the following individuals who have participated in the
drafting, review and discussion of this memo: drafting, review, and discussion of this memo:
Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie
Hoeneisen, Bjoern Hoehrmann, Caleb Richarson, Chris Bryant, Chris Hoeneisen, Bjoern Hoehrmann, Caleb Richardson, Chris Bryant, Chris
Newman, Cyrus Daboo, Daisuke Miyakawa, Dan Brickley, Dan Mosedale, Newman, Cyrus Daboo, Daisuke Miyakawa, Dan Brickley, Dan Mosedale,
Dany Cauchie, Darryl Champagne, Dave Thewlis, Filip Navara, Florian Dany Cauchie, Darryl Champagne, Dave Thewlis, Filip Navara, Florian
Zeitz, Helge Hess, Jari Urpalainen, Javier Godoy, Jean-Luc Schellens, Zeitz, Helge Hess, Jari Urpalainen, Javier Godoy, Jean-Luc Schellens,
Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Julian Reschke, Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Julian Reschke,
Kepeng Li, Kevin Marks, Kevin Wu Won, Kurt Zeilenga. Lisa Dusseault, Kepeng Li, Kevin Marks, Kevin Wu Won, Kurt Zeilenga, Lisa Dusseault,
Marc Blanchet, Mark Paterson, Markus Lorenz, Michael Haardt, Mike Marc Blanchet, Mark Paterson, Markus Lorenz, Michael Haardt, Mike
Douglass, Nick Levinson, Peter K. Sheerin, Peter Mogensen, Peter Douglass, Nick Levinson, Peter K. Sheerin, Peter Mogensen, Peter
Saint-Andre, Renato Iannella, Rohit Khare, Sly Gryphon, Stephane Saint-Andre, Renato Iannella, Rohit Khare, Sly Gryphon, Stephane
Bortzmeyer, Tantek Celik, and Zoltan Ordogh. Bortzmeyer, Tantek Celik, and Zoltan Ordogh.
12. References 12. References
12.1. Normative References 12.1. Normative References
[CCITT.E163.1988] International Telephone and [CCITT.X520.1988]
Telegraph Consultative Committee, International Telephone and Telegraph Consultative
"Numbering Plan for the Committee, "Information Technology - Open Systems
International Telephone Service", Interconnection - The Directory: Selected Attribute
CCITT Recommendation E.163, 1988. Types", CCITT Recommendation X.520, November 1988.
[CCITT.X121.1988] International Telephone and
Telegraph Consultative Committee,
"International Numbering Plan for
the Public Data Networks",
CCITT Recommendation X.121, 1988.
[CCITT.X520.1988] International International
Telephone and Telegraph
Consultative Committee,
"Information Technology - Open
Systems Interconnection - The
Directory: Selected Attribute
Types", CCITT Recommendation
X.520, November 1988.
[CCITT.X521.1988] International International
Telephone and Telegraph
Consultative Committee,
"Information Technology - Open
Systems Interconnection - The
Directory: Selected Object
Classes", CCITT Recommendation
X.521, November 1988.
[I-D.ietf-vcarddav-vcardxml] Perreault, S., "vCard XML [IEEE.754.2008]
Representation", Institute of Electrical and Electronics Engineers,
draft-ietf-vcarddav-vcardxml-08 "Standard for Binary Floating-Point Arithmetic",
(work in progress), April 2011. IEEE Standard 754, August 2008.
[IEEE.754.2008] Institute of Electrical and [ISO.8601.2000]
Electronics Engineers, "IEEE International Organization for Standardization, "Data
Standard for Floating-Point elements and interchange formats - Information interchange
Arithmetic", IEEE Standard 754, - Representation of dates and times", ISO Standard 8601,
August 2008. December 2000.
[ISO.8601.2000] International Organization for [ISO.8601.2004]
Standardization, "Data elements International Organization for Standardization, "Data
and interchange formats - elements and interchange formats - Information interchange
Information interchange - - Representation of dates and times", ISO Standard 8601,
Representation of dates and December 2004.
times", ISO Standard 8601,
December 2000.
[ISO.8601.2004] International Organization for [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Standardization, "Data elements Extensions (MIME) Part One: Format of Internet Message
and interchange formats - Bodies", RFC 2045, November 1996.
Information interchange -
Representation of dates and
times", ISO Standard 8601,
December 2004.
[RFC2045] Freed, N. and N. Borenstein, [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
"Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046,
Extensions (MIME) Part One: Format November 1996.
of Internet Message Bodies",
RFC 2045, November 1996.
[RFC2046] Freed, N. and N. Borenstein, [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
"Multipurpose Internet Mail Requirement Levels", BCP 14, RFC 2119, March 1997.
Extensions (MIME) Part Two: Media
Types", RFC 2046, November 1996.
[RFC2119] Bradner, S., "Key words for use in [RFC2739] Small, T., Hennessy, D., and F. Dawson, "Calendar
RFCs to Indicate Requirement Attributes for vCard and LDAP", RFC 2739, January 2000.
Levels", BCP 14, RFC 2119,
March 1997.
[RFC2739] Small, T., Hennessy, D., and F. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
Dawson, "Calendar Attributes for 10646", STD 63, RFC 3629, November 2003.
vCard and LDAP", RFC 2739,
January 2000.
[RFC3629] Yergeau, F., "UTF-8, a [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers",
transformation format of ISO RFC 3966, December 2004.
10646", STD 63, RFC 3629,
November 2003.
[RFC3966] Schulzrinne, H., "The tel URI for [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Telephone Numbers", RFC 3966, Resource Identifier (URI): Generic Syntax", STD 66,
December 2004. RFC 3986, January 2005.
[RFC3986] Berners-Lee, T., Fielding, R., and [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
L. Masinter, "Uniform Resource Unique IDentifier (UUID) URN Namespace", RFC 4122,
Identifier (URI): Generic Syntax", July 2005.
STD 66, RFC 3986, January 2005.
[RFC4122] Leach, P., Mealling, M., and R. [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Salz, "A Universally Unique Registration Procedures", BCP 13, RFC 4288, December 2005.
IDentifier (UUID) URN Namespace",
RFC 4122, July 2005.
[RFC4288] Freed, N. and J. Klensin, "Media [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Type Specifications and Specifications: ABNF", STD 68, RFC 5234, January 2008.
Registration Procedures", BCP 13,
RFC 4288, December 2005.
[RFC5234] Crocker, D. and P. Overell, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
"Augmented BNF for Syntax October 2008.
Specifications: ABNF", STD 68,
RFC 5234, January 2008.
[RFC5322] Resnick, P., Ed., "Internet [RFC5545] Desruisseaux, B., "Internet Calendaring and Scheduling
Message Format", RFC 5322, Core Object Specification (iCalendar)", RFC 5545,
October 2008. September 2009.
[RFC5545] Desruisseaux, B., "Internet [RFC5546] Daboo, C., "iCalendar Transport-Independent
Calendaring and Scheduling Core Interoperability Protocol (iTIP)", RFC 5546,
Object Specification (iCalendar)", December 2009.
RFC 5545, September 2009.
[RFC5546] Daboo, C., "iCalendar Transport- [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Independent Interoperability Languages", BCP 47, RFC 5646, September 2009.
Protocol (iTIP)", RFC 5546,
December 2009.
[RFC5646] Phillips, A. and M. Davis, "Tags [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource
for Identifying Languages", Identifier for Geographic Locations ('geo' URI)",
BCP 47, RFC 5646, September 2009. RFC 5870, June 2010.
[RFC5870] Mayrhofer, A. and C. Spanring, "A [RFC6351] Perreault, S., "xCard: vCard XML Representation",
Uniform Resource Identifier for RFC 6351, August 2011.
Geographic Locations ('geo' URI)",
RFC 5870, June 2010.
[W3C.REC-xml-20081126] Paoli, J., Yergeau, F., Bray, T., [W3C.REC-xml-20081126]
Maler, E., and C. Sperberg- Maler, E., Yergeau, F., Sperberg-McQueen, C., Paoli, J.,
McQueen, "Extensible Markup and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth
Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC-
Edition)", World Wide Web xml-20081126, November 2008,
Consortium Recommendation REC-xml- <http://www.w3.org/TR/2008/REC-xml-20081126>.
20081126, November 2008, <http://
www.w3.org/TR/2008/
REC-xml-20081126>.
[xfn] Celik, T., Mullenweg, M., and E. [xfn] Celik, T., Mullenweg, M., and E. Meyer, "XFN 1.1 profile",
Meyer, "XHTML Friends Network <http://gmpg.org/xfn/11>.
1.1", <http://gmpg.org/xfn/11>.
12.2. Informative References 12.2. Informative References
[I-D.ietf-eai-rfc5335bis] Yang, A. and S. Steele, [IANA-TZ] Lear, E. and P. Eggert, "IANA Procedures for Maintaining
"Internationalized Email Headers", the Timezone Database", Work in Progress, May 2011.
draft-ietf-eai-rfc5335bis-10 (work
in progress), March 2011.
[I-D.lear-iana-timezone-database] Lear, E. and P. Eggert, "IANA
Procedures for Maintaining the
Timezone Database", draft-lear-
iana-timezone-database-04 (work in
progress), May 2011.
[ISO9070] The International Organization for
Standardization, "ISO 9070,
Information Processing - SGML
support facilities - Registration
Procedures for Public Text Owner
Identifiers", April 1991.
[RFC1738] Berners-Lee, T., Masinter, L., and
M. McCahill, "Uniform Resource
Locators (URL)", RFC 1738,
December 1994.
[RFC2397] Masinter, L., "The "data" URL [ISO9070] International Organization for Standardization,
scheme", RFC 2397, August 1998. "Information Processing - SGML support facilities -
Registration Procedures for Public Text Owner
Identifiers", ISO 9070, April 1991.
[RFC2425] Howes, T., Smith, M., and F. [RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
Dawson, "A MIME Content-Type for Resource Locators (URL)", RFC 1738, December 1994.
Directory Information", RFC 2425,
September 1998.
[RFC2426] Dawson, F. and T. Howes, "vCard [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397,
MIME Directory Profile", RFC 2426, August 1998.
September 1998.
[RFC2616] Fielding, R., Gettys, J., Mogul, [RFC2425] Howes, T., Smith, M., and F. Dawson, "A MIME Content-Type
J., Frystyk, H., Masinter, L., for Directory Information", RFC 2425, September 1998.
Leach, P., and T. Berners-Lee,
"Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999.
[RFC3282] Alvestrand, H., "Content Language [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile",
Headers", RFC 3282, May 2002. RFC 2426, September 1998.
[RFC3406] Daigle, L., van Gulik, D., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Iannella, R., and P. Faltstrom, Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
"Uniform Resource Names (URN) Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
Namespace Definition Mechanisms",
BCP 66, RFC 3406, October 2002.
[RFC3536] Hoffman, P., "Terminology Used in [RFC3282] Alvestrand, H., "Content Language Headers", RFC 3282,
Internationalization in the IETF", May 2002.
RFC 3536, May 2003.
[RFC4770] Jennings, C. and J. Reschke, Ed., [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"vCard Extensions for Instant "Uniform Resource Names (URN) Namespace Definition
Messaging (IM)", RFC 4770, Mechanisms", BCP 66, RFC 3406, October 2002.
January 2007.
[RFC4880] Callas, J., Donnerhacke, L., [RFC3536] Hoffman, P., "Terminology Used in Internationalization in
Finney, H., Shaw, D., and R. the IETF", RFC 3536, May 2003.
Thayer, "OpenPGP Message Format",
RFC 4880, November 2007.
[RFC5751] Ramsdell, B. and S. Turner, [RFC4770] Jennings, C. and J. Reschke, Ed., "vCard Extensions for
"Secure/Multipurpose Internet Mail Instant Messaging (IM)", RFC 4770, January 2007.
Extensions (S/MIME) Version 3.2
Message Specification", RFC 5751,
January 2010.
[RFC6068] Duerst, M., Masinter, L., and J. [RFC4880] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R.
Zawinski, "The 'mailto' URI Thayer, "OpenPGP Message Format", RFC 4880, November 2007.
Scheme", RFC 6068, October 2010.
[TZ-DB] Olson, A., "Time zone code and [RFC5335bis]
data", Yang, A. and S. Steele, "Internationalized Email Headers",
<ftp://elsie.nci.nih.gov/pub/>. Work in Progress, July 2011.
[vCard21] Internet Mail Consortium, "vCard - [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet
The Electronic Business Card Mail Extensions (S/MIME) Version 3.2 Message
Version 2.1", September September. Specification", RFC 5751, January 2010.
URIs [RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto'
URI Scheme", RFC 6068, October 2010.
[1] <mailto:vcarddav@ietf.org> [TZ-DB] Olson, A., "Time zone code and data",
<ftp://elsie.nci.nih.gov/pub/>.
[2] <mailto:iana@iana.org> [vCard21] Internet Mail Consortium, "vCard - The Electronic Business
Card Version 2.1", September 1996.
Appendix A. Differences from RFCs 2425 and 2426 Appendix A. Differences from RFCs 2425 and 2426
This appendix contains a high-level overview of the major changes This appendix contains a high-level overview of the major changes
that have been made in the vCard specification from RFCs 2425 and that have been made in the vCard specification from RFCs 2425 and
2426. It is incomplete as it only lists the most important changes. 2426. It is incomplete, as it only lists the most important changes.
A.1. New Structure A.1. New Structure
o [RFC2425] and [RFC2426] have been merged. o [RFC2425] and [RFC2426] have been merged.
o vCard is now not only a MIME type but a stand-alone format. o vCard is now not only a MIME type but a stand-alone format.
o A proper MIME type registration form has been included. o A proper MIME type registration form has been included.
o UTF-8 is now the only possible character set. o UTF-8 is now the only possible character set.
skipping to change at page 76, line 14 skipping to change at page 73, line 32
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 NAME, MAILER, LABEL, and CLASS properties are no more. o The NAME, MAILER, LABEL, and CLASS 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 property have been removed. for the ADR property have been removed.
o Inline vCards (such as the value of the AGENT property) are no o In-line vCards (such as the value of the AGENT property) are no
longer supported. longer supported.
A.3. New Properties and Parameters A.3. New Properties and Parameters
o The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP o The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP
properties have been added. properties have been added.
o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI
properties, has been merged in. properties, has been merged in.
skipping to change at page 76, line 40 skipping to change at page 74, line 9
o The "pref" value of the TYPE parameter is now a parameter of its o The "pref" value of the TYPE parameter is now a parameter of its
own, with a positive integer value indicating the level of own, with a positive integer value indicating the level of
preference. preference.
o The ALTID and PID parameters have been added. o The ALTID and PID parameters have been added.
o The MEDIATYPE parameter has been added and replaces the TYPE o The MEDIATYPE parameter has been added and replaces the TYPE
parameter when it was used for indicating the media type of the parameter when it was used for indicating the media type of the
property's content. property's content.
A.4. Other Changes
o Synchronization is addressed in Section 7.
o The N property is no longer mandatory.
o In the N property, each component may now contain multiple comma-
separated values.
o The value of TEL is now a URI.
o The AGENT property was replaced with a type of RELATED.
o Date and time values now only support the basic format.
Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to
publication)
B.1. Changes in -22
o Made reference to RFC3536 informative instead of normative.
o Adjusted ABNF for readability (no normative changes).
o Added informative reference to draft-lear-iana-timezone-database.
o Tweaked Appendix A a little bit.
o s/privacy/confidentiality/
o Changed all references to ASCII characters into Unicode code
points.
o Added pointer to URI security considerations.
o Adjusted GENDER examples.
o Clearly ask IANA to mark text/directory as DEPRECATED.
o Adjusted updating/obsoleting text in abstract.
B.2. Changes in -21
o Minor ABNF clarification.
B.3. Changes in -20
o Reworded security considerations.
o Specified range of integer and float value types.
o Adjusted IANA considerations wording.
o Added missing date-and-or-type to the VALUE ABNF.
o s/vcard@ietf.org/vcarddav@ietf.org/
o More precise wording: charset instead of character set
o Make parameter values case-insensitive by default.
o Escaping newlines can be done with \n or \N.
o Make SORT-AS value case-sensitive.
o Better formatting for ADR special notes.
o Removed Pete Resnick's example vCard.
o vcarddav@ietf.org is the contact person for the media type.
o Add missing pref-param, pid-param, and any-param to the PHOTO
property.
o Re-added missing section on UTC-OFFSET value type.
B.4. Changes in -19
o Fixed nits.
o Fixed MEDIATYPE ABNF.
B.5. Changes in -18
o Fix missing text in KIND section.
B.6. Changes in -17
o s/individual/entity/
o Moved section 3.4 for better flow.
o Removed text overriding general MIME and HTTP rules.
o Fixed redundant ABNF.
o Fixed parameter value quoting in examples.
o Added informative reference for Content-Language header.
o Moved cardinality table earlier for better flow.
o Added normative reference for XML 1.0.
o Added informative reference for mailto: scheme.
o Clarified where the VERSION property must go.
o Created the MEDIATYPE parameter.
o Fixed text/vcard encoding considerations.
o Added .vcard file extension.
o Removed need for extension documents to contain tables in their
IANA Considerations section.
o Removed underspecified "Status" column in IANA registry.
o Moved obsoleted references to Informative section.
o Moved iCalendar references to Normative section.
o Expanded specification of KIND values.
o Recommend defining an XML representation for new vCard elements.
B.7. Changes in -16
o RELATED: Added XFN values into IANA registry.
o RELATED: Added values "agent" and "emergency".
o EMAIL is now free-form text, with informative reference to EAI.
o GENDER now has two components: one for biological sex, the other
for gender identity.
o Bugfixes to the core ABNF.
o Clarified IANA considerations.
o UID may be reset to free-form text.
B.8. Changes in -15
o Reverted N to the 5-component format of vCard 3.
o Removed DDAY, BIRTH, and DEATH.
o First two components in ADR SHOULD be empty.
o Removed the LABEL property.
o Removed the binary value type and the ENCODING and FMTTYPE
parameters.
o Renamed SEX to GENDER. Set predefined values to "male" and
"female".
o Reverted TEL to take a text value by default, but SHOULD be reset
to a URI.
o Refer to iCalendar for CALSCALE.
o Removed the "thing" value for KIND.
o RELATED now uses XFN 1.1 for its value.
o Dropped the VERSION parameter. XML MUST be version 1.0.
o Dropped the CLASS property.
o Property and parameter names SHOULD be upper-case.
o Use ABNF for cardinality notation.
B.9. Changes in -14
o DQUOTE is US-ASCII decimal 34, not 22.
o Removed unused reference to RFC 2046.
o Updated reference to draft-ietf-vcarddav-vcardxml.
o Small fixes to the IANA registration text.
o Added notes on the usage of TEL and IMPP properties.
o Clarified "country name" component of ADR property.
o Removed usage of undefined type value "msg" in TEL example.
o Fixed parameter value quoting rules and ABNF.
o Added example to LANGUAGE property.
o Fixed synchronization example regarding the cardinality of FN.
o Added implementation note for float value type.
o Removed advice for always including VALUE parameter.
o FMTTYPE MUST include the full MIME type.
o Made ADR's ABNF more verbose.
o Organized TEL TYPE values in a table.
o Replaced TOP-SECRET example with NOINDEX.
B.10. 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.11. Changes in -12
o Fixed example of LANGUAGE cardinality.
o Added note about YYYY-MM date format.
o Fixed appendix A.
o VERSION property must come first.
o Fixed mistake in PID example.
o Removed two changes from Appendix A which were probably intended
to go into this change log section.
o Explicitly state that the value for the BEGIN and END properties
is case-insensitive.
o Removed the SORT-STRING property. Created the SORT-AS parameter.
o "T" and "Z" in dates and times are now mandatory uppercase.
o Added the "version" MIME parameter.
o More consistent capitalization.
o Added missing "ANNIVERSARY" in name production rule.
o Added missing calscale-param in param production rule.
o Moved definition of GEO and TZ parameters to section 5.
o Simplified discussion of encoding.
o Removed restriction for "work" and "home" values of TYPE parameter
w.r.t. the KIND property.
o XML value may now be binary.
o Created VERSION parameter for XML.
o BIRTH and DEATH can now have URI values.
o Created the FMTTYPE parameter.
o KEY can now take a text value.
o Added references to RFC 5545 (iCalendar).
o Added namespace column in parameters registry.
B.12. Changes in -11
o Change "XML chunk" to "XML fragment".
o Cite W3C document containing definition of "fragment".
o Added "XML" to property name ABNF.
o Clarified newline escaping rule.
o Replaced one remaining "type" with "property".
o Removed case insensitivity of parameter values.
o XML property can now only contain one element that is not in the
vCard 4 namespace.
o Clarified interrelationship between LANGUAGE, cardinality, and
PID.
o Added "textphone" TEL type.
o Fixed quoting of comma in ORG examples.
B.13. Changes in -10
o Added component in SORT-STRING for sorting by given name. Fixed
and expanded the examples.
o Fixed KIND-value ABNF.
o Fixed deprecated media type.
o Created the CALSCALE parameter.
o Strenghtened the stance on character set.
o Defined the Language-Tag ABNF.
o Made explicit the fact that IANA does not register templates.
o Created the XML property.
o Added social networking examples to URL property.
B.14. Changes in -09
o Removed special meaning for groups. Removed the "work" and "home"
groups. Removed the group registry. Re-introduced the "work" and
"home" TYPE parameter values. Applied the TYPE parameter to
properties which supported the "work" and "home" groups.
o Vendor namespace now uses private enterprise number in prefix.
o Added "thing" value for KIND property.
B.15. Changes in -08
o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to
properties with the property name.
o Replaced the GENDER property with the SEX property.
o Added the ANNIVERSARY property.
o Added the "friend" and "spouse" types of RELATED.
o TZ property now has text / uri value.
o Refined the definitions of TITLE and ROLE.
B.16. Changes in -07
o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type.
o Made GEO a URI.
o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property.
o Completely reworked the date, time, and date-time grammars.
o Added the timestamp value type.
o REV now has the timestamp value type.
o Rewrote ABNF.
o ORG can now have a single level.
B.17. Changes in -06
o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value.
o ABNF fixes.
o Made gender values extensible.
o Gave the PREF parameter a positive integer value.
o Removed usage of the undefined "word" ABNF production rule.
o Defined property cardinalities.
o Defined properties allowable in WORK and HOME groups.
o Simplified the LANG property to use the vCard preference
mechanism.
o Created the "language-tag" value type.
o Added PID to ABNF of SOURCE allowed parameters.
o Clarified escaping rules.
o Changed ABNF definition of non-standard X- properties.
o Removed TYPE parameter from EMAIL properties in examples.
o Created the CLIENTPIDMAP property.
o Changed PID value to a pair of small integers.
o Completely reworked synchronization mechanisms.
o Created brand new synchronization example.
B.18. Changes in -05
o Added multi PID value proposal.
B.19. Changes in -04
o Added "location" value for KIND property.
o Some fixes to ABNF.
o Moved "pref" from being a TYPE value to a parameter in its own
right.
o Removed the "work" and "home" TYPE values.
o Reintroduced the group construct.
o Assigned meaning to WORK and HOME groups.
o Restricted the TEL TYPE parameter value set.
o In N property, removed additional names, and replaced with
multiple given names.
o Removed TYPE parameter from EMAIL and IMPP properties.
o Replaced AGENT with a type of RELATED.
o Use example.org domain in URL example.
o Created initial IANA table of values.
o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.
B.20. Changes in -03
o Various changes to the synchronization mechanisms.
o Allowed truncated format for dated. See issue #236.
B.21. Changes in -02
o Removed useless text in IMPP description.
o Added CalDAV-SCHED example to CALADRURI.
o Removed CAPURI property.
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
07:54.
o Removed inline vCard value.
o Made AGENT only accept URI references instead of inline vCards.
o Added the MEMBER property.
o Renamed the UID parameter to PID.
o Changed the value type of the PID parameter to "a small integer."
o Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD.
o Added the RELATED (Section 6.6.6) property.
o Fixed many ABNF typos (issue #252).
o Changed formatting of ABNF comments to make them easier to read
(issue #226).
B.22. Changes in -01
o Merged [RFC2739] in.
o Converted all foobar.com, abc.com, etc. to example.com.
o Fixed bugs in ABNF.
o Made explicit that coordinates in the GEO property are expressed
in the WGS 84 reference system.
o Clarified folding issues with multi-byte characters.
o Made the value of TEL a URI.
o Added the UID parameter.
o Made the UID property's value type a URI.
o Added Section 7.
o Created IANA process for registering new parameters, value types,
and properties.
o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288.
B.23. Changes in -00
o Name change because draft has been accepted as WG item.
Otherwise, same as draft-resnick-vcarddav-vcardrev-01.
o Removed reference to RFC 2234.
o Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426.
o Removed passage referring to RFC 2425 profiles.
o Renamed Section 6.4 from "Telecommunications Adressing Properties"
to "Communications Properties.
o Added Appendix A and Appendix B.
o Added reference to [RFC4770].
o Removed the group construct.
o Made the N property no longer mandatory.
o Added the KIND property.
o Clarified meaning of TYPE parameter value for PHOTO, LOGO, KEY,
and SOUND.
o Removed the CONTEXT parameter.
o Removed the MAILER property.
o Made reference to [ISO9070] informative.
o Removed "intl", "dom", "postal", and "parcel" TYPE parameter
values for the ADR and LABEL properties.
o Clarified meaning of "extended address" ADR field.
o Mentioned [RFC3406] as another method of generating PRODID values.
o Updated obsolete references.
o Allowed BDAY and DDAY value types to be text values for fuzzy
dates.
o Removed the CHARSET property. Now the encoding is always UTF-8,
except when overridden by the Content-Type (which is considered a
compatibility feature).
Author's Address Author's Address
Simon Perreault Simon Perreault
Viagenie Viagenie
2875 Laurier, suite D2-630 2875 Laurier, suite D2-630
Quebec, QC G1V 2M2 Quebec, QC G1V 2M2
Canada Canada
Phone: +1 418 656 9254 Phone: +1 418 656 9254
EMail: simon.perreault@viagenie.ca EMail: simon.perreault@viagenie.ca
 End of changes. 221 change blocks. 
1230 lines changed or deleted 541 lines changed or added

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