draft-ietf-vcarddav-vcardrev-15.txt   draft-ietf-vcarddav-vcardrev-16.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 P. Resnick Obsoletes: 2425, 2426, 4770 March 10, 2011
(if approved) QUALCOMM Incorporated (if approved)
Updates: 2739 (if approved) December 9, 2010 Updates: 2739 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: June 12, 2011 Expires: September 11, 2011
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-15 draft-ietf-vcarddav-vcardrev-16
Abstract Abstract
This document defines the vCard data format for representing and This document defines the vCard data format for representing and
exchanging a variety of information about individuals and other exchanging a variety of information about individuals and other
entities (e.g., formatted and structured name and delivery addresses, entities (e.g., formatted and structured name and delivery addresses,
email address, multiple telephone numbers, photograph, logo, audio email address, multiple telephone numbers, photograph, logo, audio
clips, etc.). clips, etc.).
Status of This Memo Status of This Memo
skipping to change at page 1, line 43 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 12, 2011. This Internet-Draft will expire on September 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 25 skipping to change at page 3, line 25
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.2. Identification Properties . . . . . . . . . . . . . . . . 27 6.2. Identification Properties . . . . . . . . . . . . . . . . 27
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 28 6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 30 6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 30
6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 31 6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 30
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 31 6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 31
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 31 6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.4. Communications Properties . . . . . . . . . . . . . . . . 33 6.4. Communications Properties . . . . . . . . . . . . . . . . 33
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 34 6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 35
6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.5. Geographical Properties . . . . . . . . . . . . . . . . . 36 6.5. Geographical Properties . . . . . . . . . . . . . . . . . 36
6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.6. Organizational Properties . . . . . . . . . . . . . . . . 37 6.6. Organizational Properties . . . . . . . . . . . . . . . . 38
6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 37 6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 38
6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 39 6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 40 6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 41
6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 41 6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 42
6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 42 6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 42
6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 42 6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 43 6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 43
6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 43 6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 43 6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 44
6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 44 6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 45 6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 46
6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 45 6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 46 6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 47
6.8. Security Properties . . . . . . . . . . . . . . . . . . . 46 6.8. Security Properties . . . . . . . . . . . . . . . . . . . 47
6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 47 6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 48
6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 47 6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 48
6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 48 6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 49
6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 48 6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 49
6.10. Extended Properties and Parameters . . . . . . . . . . . . 49 6.10. Extended Properties and Parameters . . . . . . . . . . . . 50
7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 49 7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 50
7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 49 7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 50
7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 50 7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 51
7.1.2. Matching Property Instances . . . . . . . . . . . . . 50 7.1.2. Matching Property Instances . . . . . . . . . . . . . 51
7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 50 7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 51
7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 51 7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 51 7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 52
7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 51 7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 52
7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 52 7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 53
7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 52 7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 53
7.2.5. Global Context Simplification . . . . . . . . . . . . 54 7.2.5. Global Context Simplification . . . . . . . . . . . . 55
8. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 55 8. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 56
9. Security Considerations . . . . . . . . . . . . . . . . . . . 55 9. Security Considerations . . . . . . . . . . . . . . . . . . . 56
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57
10.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 56 10.1. MIME Type Registration . . . . . . . . . . . . . . . . . . 57
10.2. Registering New vCard Elements . . . . . . . . . . . . . . 57 10.2. Registering New vCard Elements . . . . . . . . . . . . . . 58
10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 57 10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 59
10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 58 10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 59
10.2.3. Registration Template for Properties . . . . . . . . . 59 10.2.3. Registration Template for Properties . . . . . . . . . 60
10.2.4. Registration Template for Parameters . . . . . . . . . 59 10.2.4. Registration Template for Parameters . . . . . . . . . 61
10.2.5. Registration Template for Value Data Types . . . . . . 60 10.2.5. Registration Template for Value Data Types . . . . . . 61
10.2.6. Registration Template for Values . . . . . . . . . . . 60 10.2.6. Registration Template for Values . . . . . . . . . . . 61
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 61 10.3. Initial vCard Elements Registries . . . . . . . . . . . . 62
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 61 10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 62
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 62 10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 63
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 63 10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 64
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 63 10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 64
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 68
12.1. Normative References . . . . . . . . . . . . . . . . . . . 65 12.1. Normative References . . . . . . . . . . . . . . . . . . . 68
12.2. Informative References . . . . . . . . . . . . . . . . . . 68 12.2. Informative References . . . . . . . . . . . . . . . . . . 70
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 69 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 71
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 69 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 71
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 69 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 71
A.3. New Properties and Parameters . . . . . . . . . . . . . . 69 A.3. New Properties and Parameters . . . . . . . . . . . . . . 72
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 70 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 72
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 70 publication) . . . . . . . . . . . . . . . . . . . . 72
B.1. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 70 B.1. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 72
B.2. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 71 B.2. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 73
B.3. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 71 B.3. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 73
B.4. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 72 B.4. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 74
B.5. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 73 B.5. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 74
B.6. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 73 B.6. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 76
B.7. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 74 B.7. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 76
B.8. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 74 B.8. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 77
B.9. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 75 B.9. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 77
B.10. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 75 B.10. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 77
B.11. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 76 B.11. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 78
B.12. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 76 B.12. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 79
B.13. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 77 B.13. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 79
B.14. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 77 B.14. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 79
B.15. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 77 B.15. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 79
B.16. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 78 B.16. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 80
B.17. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 81
1. Introduction 1. Introduction
Electronic address books have become ubiquitous. Their increased Electronic address books have become ubiquitous. Their increased
presence on portable, connected devices as well as the diversity of presence on portable, connected devices as well as the diversity of
platforms exchanging contact data call for a standard. This memo platforms exchanging contact data call for a standard. This memo
defines the vCard format, which allows the capture and exchange of defines the vCard format, which allows the capture and exchange of
information normally stored within an address book or directory information normally stored within an address book or directory
application. application.
skipping to change at page 6, line 34 skipping to change at page 6, line 34
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. Line Delimiting and Folding 3.1. Line Delimiting and Folding
Individual lines within vCard are delimited by the [RFC5322] line Individual lines within vCard are delimited by the [RFC5322] line
break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII
decimal 10). Long logical lines of text can be split into a decimal 10). Long logical lines of text can be split into a
multiple-physical-line representation using the following folding multiple-physical-line representation using the following folding
technique. Content lines SHOULD be folded to a maximum width of 75 technique. Content lines SHOULD be folded to a maximum width of 75
octets. Multi-octet characters MUST remain contiguous. The octets, excluding the line break. Multi-octet characters MUST remain
rationale for this folding process can be found in [RFC5322], Section contiguous. The rationale for this folding process can be found in
2.1.1. [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, ASCII decimal 32, or horizontal single white space character (space, ASCII decimal 32, or horizontal
tab, ASCII decimal 9). The folded line MUST contain at least one tab, ASCII decimal 9). The folded line MUST contain at least one
character. Any sequence of CRLF followed immediately by a single character. Any sequence of CRLF followed immediately by a single
white space character is ignored (removed) when processing the white space character is ignored (removed) when processing the
content type. For example the line: content type. For example the line:
NOTE:This is a long description that exists on a long line. NOTE:This is a long description that exists on a long line.
skipping to change at page 10, line 36 skipping to change at page 10, line 36
/ date-time-list / date-time-list
/ date-and-or-time-list / date-and-or-time-list
/ timestamp-list / timestamp-list
/ boolean / boolean
/ integer-list / integer-list
/ float-list / float-list
/ URI ; from Section 3 of [RFC3986] / URI ; from Section 3 of [RFC3986]
/ iana-valuespec / iana-valuespec
; Actual value type depends on property name and VALUE parameter. ; Actual value type depends on property name and VALUE parameter.
text = *VALUE-CHAR text = *TEXT-CHAR
text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)
TEXT-LIST-CHAR = "\\" / "\," / "\n" TEXT-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \> / <any VALUE-CHAR except , or \>
; Backslashes, commas, and newlines must be encoded. ; Backslashes, commas, and newlines must be encoded.
component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
list-component = list-component-value *("," list-component-value)
list-component-value = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
text-list = text *("," text)
date-list = date *("," date) date-list = date *("," date)
time-list = time *("," time) time-list = time *("," time)
date-time-list = date-time *("," date-time) date-time-list = date-time *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-or-time) date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list = timestamp *("," timestamp) timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer) integer-list = integer *("," integer)
float-list = float *("," float) float-list = float *("," float)
boolean = "TRUE" / "FALSE" boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT] float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-" sign = "+" / "-"
year = 4DIGIT ; 0000-9999 year = 4DIGIT ; 0000-9999
month = 2DIGIT ; 01-12 month = 2DIGIT ; 01-12
day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
hour = 2DIGIT ; 00-23 hour = 2DIGIT ; 00-23
skipping to change at page 12, line 43 skipping to change at page 12, line 45
demonstrating the \n literal formatted line break technique, the demonstrating the \n literal formatted line break technique, the
CRLF-followed-by-space line folding technique, and the backslash CRLF-followed-by-space line folding technique, and the backslash
escape technique. escape technique.
4.2. URI 4.2. URI
"uri": The "uri" value type should be used to identify values that "uri": The "uri" value type should be used to identify values that
are referenced by a URI (including a Content-ID URI), instead of are referenced by a URI (including a Content-ID URI), instead of
encoded in-line. These value references might be used if the value encoded in-line. These value references might be used if the value
is too large, or otherwise undesirable to include directly. The is too large, or otherwise undesirable to include directly. The
format for the URI is as defined in [RFC3986]. Note that the value format for the URI is as defined in Section 3 of [RFC3986]. Note
of a property of type "uri" is what the URI points to, not the URI that the value of a property of type "uri" is what the URI points to,
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", and "timestamp": Each of these value
types is based on the definitions in [ISO.8601.2004] standard. types is based on the definitions in [ISO.8601.2004] standard.
skipping to change at page 26, line 14 skipping to change at page 26, line 14
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
Purpose: To include extended XML-encoded vCard data in a plain Purpose: To include extended XML-encoded vCard data in a plain
vCard. vCard.
Value type: A single text value. Value type: A single text value.
Cardinality: * Cardinality: *
skipping to change at page 28, line 26 skipping to change at page 28, line 26
represents follows 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)
list-component = list-component-value *("," list-component-value)
list-component-value = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
Examples: Examples:
N:Public;John;Quinlan;Mr.;Esq. N:Public;John;Quinlan;Mr.;Esq.
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P. N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
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.
skipping to change at page 31, line 6 skipping to change at page 31, line 4
ANNIVERSARY-param =/ altid-param / calscale-param / any-param ANNIVERSARY-param =/ altid-param / calscale-param / any-param
; calscale-param can only be present when ANNIVERSARY-value is ; calscale-param can only be present when ANNIVERSARY-value is
; date-and-or-time and actually contains a date or date-time. ; date-and-or-time and actually contains a date or date-time.
Examples: Examples:
ANNIVERSARY:19960415 ANNIVERSARY:19960415
6.2.7. GENDER 6.2.7. GENDER
Purpose: To specify the components of the sex and gender identity of
the object the vCard represents.
Purpose: To specify the gender of the object the vCard represents. Value type: A single structured value with two components. Each
component has a single text value.
Value type: A single text value.
Cardinality: *1 Cardinality: *1
Special notes: The values "male" and "female" are predefined. Any Special notes: The components correspond, in sequence, to the sex
other text value MAY be used. vCard implementations MUST ignore (biological), and gender identity. Each component is optional.
values they do not understand. An IANA registry (see
Section 10.3.4) is created for registering additional well-known Sex component: A single letter. M stands for "male", F stands
values. for "female", O stands for "other", N stands for "none or not
applicable", U stands for "unknown".
Gender identity component: Free-form text.
ABNF: ABNF:
GENDER-param = "VALUE=text" / any-param GENDER-param = "VALUE=text" / any-param
GENDER-value = "male" / "female" / iana-token / text GENDER-value = sex [";" text]
Example: sex = "" / "M" / "F" / "O" / "N" / "U"
GENDER:female Examples:
GENDER:M
GENDER:F
GENDER:M;Fellow
GENDER:F;Bird
GENDER:O;intersex
GENDER:;queer
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.
skipping to change at page 32, line 6 skipping to change at page 32, line 18
address components. The component values MUST be specified in address components. The component values MUST be specified in
their corresponding position. The structured type value their corresponding position. The structured type value
corresponds, in sequence, to the post office box; the extended corresponds, in sequence, to the post office box; the extended
address (e.g. apartment or suite number); the street address; the address (e.g. apartment or suite number); the street address; the
locality (e.g., city); the region (e.g., state or province); the locality (e.g., city); the region (e.g., state or province); the
postal code; the country name (full name in the language specified postal code; the country name (full name in the language specified
in Section 5.1). When a component value is missing, the in Section 5.1). When a component value is missing, the
associated component separator MUST still be specified. associated component separator MUST still be specified.
Experience with vCard 3 has shown that the first two components Experience with vCard 3 has shown that the first two components
(post office box and extended address) are the plagued with many (post office box and extended address) are plagued with many
interoperability issues. To ensure maximal interoperability, interoperability issues. To ensure maximal interoperability,
their values SHOULD be empty. their values SHOULD be empty.
The text components are separated by the SEMI-COLON character The text components are separated by the SEMI-COLON character
(ASCII decimal 59). Where it makes semantic sense, individual (ASCII decimal 59). Where it makes semantic sense, individual
text components can include multiple text values (e.g., a "street" text components can include multiple text values (e.g., a "street"
component with multiple lines) separated by the COMMA character component with multiple lines) separated by the COMMA character
(ASCII decimal 44). (ASCII decimal 44).
The property can include the "PREF" parameter to indicate the The property can include the "PREF" parameter to indicate the
skipping to change at page 34, line 46 skipping to change at page 35, line 23
with the object the vCard represents. with the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: * 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
interpreted by an MUA as an "addr-spec", as defined in [RFC5322],
section 3.4.1. Readers should also be aware of the current work
toward internationalized email addresses
[I-D.ietf-eai-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 = addr-spec ; from [RFC5322] section 3.4.1 EMAIL-value = text
Example: Example:
EMAIL;TYPE=work:jqpublic@xyz.example.com EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;PREF=1:jane_doe@example.com EMAIL;PREF=1:jane_doe@example.com
6.4.3. IMPP 6.4.3. IMPP
Purpose: To specify the URI for instant messaging and presence Purpose: To specify the URI for instant messaging and presence
skipping to change at page 39, line 36 skipping to change at page 40, line 29
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)
component = "\\" / "\;" / "\n" / WSP / NON-ASCII
/ %x21-3A / %x3C-5B / %x5D-7E
Example: A property value consisting of an organizational name, Example: A property value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name. organizational unit #1 name and organizational unit #2 name.
ORG:ABC, Inc.;North American Division;Marketing ORG:ABC\, Inc.;North American Division;Marketing
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 e-mail distribution list could
employ the "mailto" URI scheme for efficiency. employ the "mailto" URI scheme for efficiency.
Cardinality: * Cardinality: *
skipping to change at page 41, line 4 skipping to change at page 41, line 36
VERSION:4.0 VERSION:4.0
KIND:group KIND:group
FN:Funky distribution list FN:Funky distribution list
MEMBER:mailto:subscriber1@example.com MEMBER:mailto:subscriber1@example.com
MEMBER:xmpp:subscriber2@example.com MEMBER:xmpp:subscriber2@example.com
MEMBER:sip:subscriber3@example.com MEMBER:sip:subscriber3@example.com
MEMBER:tel:+1-418-555-5555 MEMBER:tel:+1-418-555-5555
END:VCARD END:VCARD
6.6.6. RELATED 6.6.6. RELATED
Purpose: To specify a relationship between another person and the Purpose: To specify a relationship between another person and the
individual represented by this vCard. individual 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 individual. Its value is as defined in [xfn]. related individual. It contains a comma-separated list of values
that are registered from IANA as described in Section 10.2. The
registry is pre-populated with the values defined in [xfn]. This
document also specifies two additional values:
agent: a person who may sometimes act on behalf of the individual
or resource associated with the vCard.
emergency: indicates an emergency contact
ABNF: ABNF:
RELATED-param = RELATED-param-uri / RELATED-param-text RELATED-param = RELATED-param-uri / RELATED-param-text
RELATED-value = uri / text RELATED-value = uri / text
; Parameter and value MUST match. ; Parameter and value MUST match.
RELATED-param-uri = "VALUE=uri" RELATED-param-uri = "VALUE=uri"
RELATED-param-text = "VALUE=text" / language-param RELATED-param-text = "VALUE=text" / language-param
RELATED-param =/ pid-param / pref-param / altid-param / type-param RELATED-param =/ pid-param / pref-param / altid-param / type-param
/ any-param / any-param
type-param-related = xfn-value *(" " xfn-value) type-param-related = related-type-value *("," related-type-value)
; type-param-related MUST NOT be used with a property other than ; type-param-related MUST NOT be used with a property other than
; RELATED. ; RELATED.
xfn-value = "contact" / "acquaintance" / "friend" / "met" related-type-value = "contact" / "acquaintance" / "friend" / "met"
/ "co-worker" / "colleague" / "co-resident" / "neighbor" / "co-worker" / "colleague" / "co-resident"
/ "child" / "parent" / "sibling" / "spouse" / "kin" / "neighbor" / "child" / "parent"
/ "muse" / "crush" / "date" / "sweetheart" / "me" / "sibling" / "spouse" / "kin" / "muse"
/ "crush" / "date" / "sweetheart" / "me"
/ "agent" / "emergency"
Examples: Examples:
RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf
RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane
Doe for any inquiries. Doe for any inquiries.
6.7. Explanatory Properties 6.7. Explanatory Properties
skipping to change at page 44, line 34 skipping to change at page 45, line 30
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...> <...the remainder of base64-encoded data...>
6.7.6. UID 6.7.6. UID
Purpose: To specify a value that represents a globally unique Purpose: To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated identifier corresponding to the individual or resource associated
with the vCard. with the vCard.
Value type: A single URI value. Value type: A single URI value. It MAY also be reset to free-form
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. schemes MAY be used. Free-form text MAY also be used.
ABNF: ABNF:
UID-param = "VALUE=uri" / any-param UID-param = UID-uri-param / UID-text-param
UID-value = uri UID-value = UID-uri-value / UID-text-value
; Value and parameter MUST match.
UID-uri-param = "VALUE=uri"
UID-uri-value = uri
UID-text-param = "VALUE=text"
UID-text-value = text
UID-param =/ any-param
Example: Example:
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
skipping to change at page 55, line 13 skipping to change at page 56, line 13
investigating would be, in the authors' opinion, worthwhile. investigating would be, in the authors' opinion, worthwhile.
8. Example: Authors' vCards 8. Example: Authors' vCards
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Simon Perreault FN:Simon Perreault
N:Perreault;Simon;;;ing. jr,M.Sc. N:Perreault;Simon;;;ing. jr,M.Sc.
BDAY:--0203 BDAY:--0203
ANNIVERSARY:20090808T1430-0500 ANNIVERSARY:20090808T1430-0500
GENDER:male GENDER:M
LANG;PREF=1:fr LANG;PREF=1:fr
LANG;PREF=2:en LANG;PREF=2:en
ORG;TYPE=work:Viagenie ORG;TYPE=work:Viagenie
ADR;TYPE=work:;Suite D2-630;2875 Laurier; ADR;TYPE=work:;Suite D2-630;2875 Laurier;
Quebec;QC;G1V 2M2;Canada Quebec;QC;G1V 2M2;Canada
TEL;VALUE=uri;TYPE=work,voice;PREF=1:tel:+1-418-656-9254;ext=102 TEL;VALUE=uri;TYPE=work,voice;PREF=1:tel:+1-418-656-9254;ext=102
TEL;VALUE=uri;TYPE=work,cell,voice,video,text:tel:+1-418-262-6501 TEL;VALUE=uri;TYPE=work,cell,voice,video,text:tel:+1-418-262-6501
EMAIL;TYPE=work:simon.perreault@viagenie.ca EMAIL;TYPE=work:simon.perreault@viagenie.ca
GEO;TYPE=work:geo:46.772673,-71.282945 GEO;TYPE=work:geo:46.772673,-71.282945
KEY;TYPE=work;VALUE=uri: KEY;TYPE=work;VALUE=uri:
http://www.viagenie.ca/simon.perreault/simon.asc http://www.viagenie.ca/simon.perreault/simon.asc
TZ:-0500 TZ:-0500
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Pete Resnick FN:Pete Resnick
N:Resnick;Pete;;; N:Resnick;Pete;;;
GENDER:male GENDER:M
ORG;TYPE=work:QUALCOMM Incorporated ORG;TYPE=work:QUALCOMM Incorporated
ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
TEL;VALUE=uri;TYPE=work,voice:tel:+1-858-651-4478 TEL;VALUE=uri;TYPE=work,voice:tel:+1-858-651-4478
EMAIL;TYPE=work:presnick@qualcomm.com EMAIL;TYPE=work:presnick@qualcomm.com
URL;TYPE=work:http://www.qualcomm.com/~presnick/ URL;TYPE=work:http://www.qualcomm.com/~presnick/
END:VCARD END:VCARD
9. Security Considerations 9. Security Considerations
o Internet mail is often used to transport vCards and is subject to o Internet mail is often used to transport vCards and is subject to
skipping to change at page 56, line 21 skipping to change at page 57, line 21
o The information in a vCard may become out of date. In cases where o The information in a vCard may become out of date. In cases where
the vitality of data is important to an originator of a vCard, the the vitality of data is important to an originator of a vCard, the
SOURCE property (Section 6.1.3) SHOULD be specified. In addition, SOURCE property (Section 6.1.3) SHOULD be specified. In addition,
the "REV" type described in section Section 6.7.4 can be specified the "REV" type described in section Section 6.7.4 can be specified
to indicate the last time that the vCard data was updated. to indicate the last time that the vCard data was updated.
10. IANA Considerations 10. IANA Considerations
10.1. MIME Type Registration 10.1. MIME Type Registration
IANA is asked to register the following MIME Media Type (in
<http://www.iana.org/assignments/media-types/>).
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of media type text/vcard Subject: Registration of media type text/vcard
Type name: text Type name: text
Subtype name: vcard Subtype name: vcard
Required parameters: none Required parameters: none
skipping to change at page 57, line 45 skipping to change at page 58, line 47
Restrictions on usage: none Restrictions on usage: none
Author: Simon Perreault and Pete Resnick Author: Simon Perreault and Pete Resnick
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. values) with IANA. It does not contain any immediate IANA actions.
10.2.1. Registration Procedure 10.2.1. Registration Procedure
The IETF will create a mailing list, vcard@ietf.org [1], which can be The IETF will create a mailing list, vcard@ietf.org [1], which can be
used for public discussion of vCard element proposals prior to used for public discussion of vCard element proposals prior to
registration. Use of the mailing list is strongly encouraged. The registration. Use of the mailing list is strongly encouraged. The
IESG will appoint a designated expert who will monitor the IESG will appoint a designated expert who will monitor the
vcard@ietf.org [1] mailing list and review registrations. vcard@ietf.org [1] mailing list and review registrations.
Registration of new vCard elements MUST be reviewed by the designated Registration of new vCard elements MUST be reviewed by the designated
skipping to change at page 58, line 28 skipping to change at page 59, line 35
changes, or rejected with cause. When a registration is rejected changes, or rejected with cause. When a registration is rejected
with cause, it can be re-submitted if the concerns listed in the with cause, it can be re-submitted if the concerns listed in the
cause are addressed. Decisions made by the designated expert can be cause are addressed. Decisions made by the designated expert can be
appealed to the IESG Applications Area Director, then to the IESG. appealed to the IESG Applications Area Director, then to the IESG.
They follow the normal appeals procedure for IESG decisions. They follow the normal appeals procedure for IESG decisions.
Once the registration procedure concludes successfully, IANA creates Once the registration procedure concludes successfully, IANA creates
or modifies the corresponding record in the vCard registry. The or modifies the corresponding record in the vCard registry. The
completed registration template is discarded. completed registration template is discarded.
An RFC specifying new vCard elements MUST include the completed
registration templates, which MAY be expanded with additional
information. These completed templates will go in the body of the
document, and SHOULD NOT be included or repeated in the IANA
Considerations section. The IANA Considerations section MUST contain
tables (see the tables in section Section 10.3) that show exactly the
changes that IANA is requested to make to the registries. The
registry's reference column MUST point to the section in the RFC
containing to the completed the registration template.
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
organization handling the vCard elements in the namespace being organization handling the vCard elements in the namespace being
registered. Changes to the specification will be made at their registered. Changes to the specification will be made at their
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").
skipping to change at page 60, line 47 skipping to change at page 62, line 17
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 needs 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: hermaphrodite Value: supervisor
Purpose: This value is a combination of the "male" and "female" Purpose: It means that the related individual is the direct
values. hierarchical superior (i.e. supervisor or manager) of the
individual this vCard represents.
Conformance: This value can be used with the "GENDER" property. Conformance: This value can be used with the "TYPE" parameter
applied on the "RELATED" property.
Example(s): The following is an example of this value used with the Example(s):
"GENDER" property:
GENDER:hermaphrodite 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 is requested to create and maintain the following registries
for vCard elements with pointers to appropriate reference documents. for vCard elements with pointers to appropriate reference documents.
The registries will be grouped together under the heading "vCard
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 is to be used to initialize the properties
registry. registry.
+-----------+--------------+---------+------------------------+ +-----------+--------------+---------+------------------------+
| Namespace | Property | Status | Reference | | Namespace | Property | Status | Reference |
+-----------+--------------+---------+------------------------+ +-----------+--------------+---------+------------------------+
| | SOURCE | Current | RFCXXXX, Section 6.1.3 | | | SOURCE | Current | RFCXXXX, Section 6.1.3 |
skipping to change at page 64, line 14 skipping to change at page 65, line 14
+----------+------------+---------+------------------------+ +----------+------------+---------+------------------------+
| Property | Value | Status | Reference | | Property | Value | Status | Reference |
+----------+------------+---------+------------------------+ +----------+------------+---------+------------------------+
| BEGIN | VCARD | Current | RFCXXXX, Section 6.1.1 | | BEGIN | VCARD | Current | RFCXXXX, Section 6.1.1 |
| END | VCARD | Current | RFCXXXX, Section 6.1.2 | | END | VCARD | Current | RFCXXXX, Section 6.1.2 |
| KIND | individual | Current | RFCXXXX, Section 6.1.4 | | KIND | individual | Current | RFCXXXX, Section 6.1.4 |
| KIND | group | Current | RFCXXXX, Section 6.1.4 | | KIND | group | Current | RFCXXXX, Section 6.1.4 |
| KIND | org | Current | RFCXXXX, Section 6.1.4 | | KIND | org | Current | RFCXXXX, Section 6.1.4 |
| KIND | location | Current | RFCXXXX, Section 6.1.4 | | KIND | location | Current | RFCXXXX, Section 6.1.4 |
| GENDER | male | Current | RFCXXXX, Section 6.2.7 |
| GENDER | female | Current | RFCXXXX, Section 6.2.7 |
+----------+------------+---------+------------------------+ +----------+------------+---------+------------------------+
The following table is to be used to initialize the parameter values The following table is to be used to initialize the parameter values
registry. registry.
+-----------------+-----------+-----------+---------+---------------+ +--------------+-----------+--------------+---------+---------------+
| Property | Parameter | Value | Status | Reference | | Property | Parameter | Value | Status | Reference |
+-----------------+-----------+-----------+---------+---------------+ +--------------+-----------+--------------+---------+---------------+
| FN, NICKNAME, | TYPE | work | Current | RFCXXXX, | | FN, | TYPE | work | Current | RFCXXXX, |
| PHOTO, ADR, | | | | Section 5.6 | | NICKNAME, | | | | Section 5.6 |
| TEL, EMAIL, | | | | | | PHOTO, ADR, | | | | |
| IMPP, LANG, TZ, | | | | | | TEL, EMAIL, | | | | |
| GEO, TITLE, | | | | | | IMPP, LANG, | | | | |
| ROLE, LOGO, | | | | | | TZ, GEO, | | | | |
| ORG, RELATED, | | | | | | TITLE, ROLE, | | | | |
| CATEGORIES, | | | | | | LOGO, ORG, | | | | |
| NOTE, SOUND, | | | | | | RELATED, | | | | |
| URL, KEY, | | | | | | CATEGORIES, | | | | |
| FBURL, | | | | | | NOTE, SOUND, | | | | |
| CALADRURI, and | | | | | | URL, KEY, | | | | |
| CALURI | | | | | | FBURL, | | | | |
| FN, NICKNAME, | TYPE | home | Current | RFCXXXX, | | CALADRURI, | | | | |
| PHOTO, ADR, | | | | Section 5.6 | | and CALURI | | | | |
| TEL, EMAIL, | | | | | | FN, | TYPE | home | Current | RFCXXXX, |
| IMPP, LANG, TZ, | | | | | | NICKNAME, | | | | Section 5.6 |
| GEO, TITLE, | | | | | | PHOTO, ADR, | | | | |
| ROLE, LOGO, | | | | | | TEL, EMAIL, | | | | |
| ORG, RELATED, | | | | | | IMPP, LANG, | | | | |
| CATEGORIES, | | | | | | TZ, GEO, | | | | |
| NOTE, SOUND, | | | | | | TITLE, ROLE, | | | | |
| URL, KEY, | | | | | | LOGO, ORG, | | | | |
| FBURL, | | | | | | RELATED, | | | | |
| CALADRURI, and | | | | | | CATEGORIES, | | | | |
| CALURI | | | | | | NOTE, SOUND, | | | | |
| TEL | TYPE | text | Current | RFCXXXX, | | URL, KEY, | | | | |
| | | | | Section 6.4.1 | | FBURL, | | | | |
| TEL | TYPE | voice | Current | RFCXXXX, | | CALADRURI, | | | | |
| | | | | Section 6.4.1 | | and CALURI | | | | |
| TEL | TYPE | fax | Current | RFCXXXX, | | TEL | TYPE | text | Current | RFCXXXX, |
| | | | | Section 6.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | cell | Current | RFCXXXX, | | TEL | TYPE | voice | Current | RFCXXXX, |
| | | | | Section 6.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | video | Current | RFCXXXX, | | TEL | TYPE | fax | Current | RFCXXXX, |
| | | | | Section 6.4.1 | | | | | | Section 6.4.1 |
| TEL | TYPE | pager | Current | RFCXXXX, | | TEL | TYPE | cell | Current | RFCXXXX, |
| | | | | Section 6.4.1 | | | | | | Section 6.4.1 |
| BDAY, | CALSCALE | gregorian | Current | RFCXXXX, | | TEL | TYPE | video | Current | RFCXXXX, |
| ANNIVERSARY | | | | Section 6.2.5 | | | | | | Section 6.4.1 |
+-----------------+-----------+-----------+---------+---------------+ | TEL | TYPE | pager | Current | RFCXXXX, |
| | | | | Section 6.4.1 |
| BDAY, | CALSCALE | gregorian | Current | RFCXXXX, |
| ANNIVERSARY | | | | Section 6.2.5 |
| RELATED | TYPE | contact | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | acquaintance | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | friend | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | met | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | co-worker | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | colleague | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | co-resident | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | neighbor | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | child | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | parent | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | sibling | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | spouse | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | kin | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | muse | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | crush | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | date | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | sweetheart | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | me | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| | | | | and [xfn] |
| RELATED | TYPE | agent | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
| RELATED | TYPE | emergency | Current | RFCXXXX, |
| | | | | Section 6.6.6 |
+--------------+-----------+--------------+---------+---------------+
11. Acknowledgements 11. Acknowledgements
The authors would like to thank Tim Howes, Mark Smith, and Frank The authors would like to thank Tim Howes, Mark Smith, and Frank
Dawson, the original authors of [RFC2425] and [RFC2426], as well as Dawson, the original authors of [RFC2425] and [RFC2426], Pete
the following individuals who have participated in the drafting, Resnick, who got this effort started and provided help along the way,
review and discussion of this memo: as well as the following individuals who have participated in the
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 Richarson, 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
skipping to change at page 68, line 13 skipping to change at page 70, line 27
[oldreference_VCARD] Internet Mail Consortium, "vCard - The [oldreference_VCARD] Internet Mail Consortium, "vCard - The
Electronic Business Card Version 2.1", Electronic Business Card Version 2.1",
September September. September September.
[xfn] Celik, T., Mullenweg, M., and E. Meyer, [xfn] Celik, T., Mullenweg, M., and E. Meyer,
"XHTML Friends Network 1.1", "XHTML Friends Network 1.1",
<http://gmpg.org/xfn/11>. <http://gmpg.org/xfn/11>.
12.2. Informative References 12.2. Informative References
[I-D.ietf-eai-rfc5335bis] Yang, A., Steele, S., Crocker, D., and
N. Freed, "Internationalized Email
Headers", draft-ietf-eai-rfc5335bis-09
(work in progress), March 2011.
[ISO9070] The International Organization for [ISO9070] The International Organization for
Standardization, "ISO 9070, Information Standardization, "ISO 9070, Information
Processing - SGML support facilities - Processing - SGML support facilities -
Registration Procedures for Public Text Registration Procedures for Public Text
Owner Identifiers", April 1991. Owner Identifiers", April 1991.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., [RFC2616] Fielding, R., Gettys, J., Mogul, J.,
Frystyk, H., Masinter, L., Leach, P., Frystyk, H., Masinter, L., Leach, P.,
and T. Berners-Lee, "Hypertext Transfer and T. Berners-Lee, "Hypertext Transfer
Protocol -- HTTP/1.1", RFC 2616, Protocol -- HTTP/1.1", RFC 2616,
skipping to change at page 70, line 27 skipping to change at page 72, line 40
o The value of TEL is now a URI. o The value of TEL is now a URI.
o The AGENT property was replaced with a type of RELATED. o The AGENT property was replaced with a type of RELATED.
o Date and time values now only support the basic format. o Date and time values now only support the basic format.
Truncation is now supported. Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -15 B.1. 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.2. Changes in -15
o Reverted N to the 5-component format of vCard 3. o Reverted N to the 5-component format of vCard 3.
o Removed DDAY, BIRTH, and DEATH. o Removed DDAY, BIRTH, and DEATH.
o First two components in ADR SHOULD be empty. o First two components in ADR SHOULD be empty.
o Removed the LABEL property. o Removed the LABEL property.
o Removed the binary value type and the ENCODING and FMTTYPE o Removed the binary value type and the ENCODING and FMTTYPE
skipping to change at page 71, line 13 skipping to change at page 73, line 42
o RELATED now uses XFN 1.1 for its value. o RELATED now uses XFN 1.1 for its value.
o Dropped the VERSION parameter. XML MUST be version 1.0. o Dropped the VERSION parameter. XML MUST be version 1.0.
o Dropped the CLASS property. o Dropped the CLASS property.
o Property and parameter names SHOULD be upper-case. o Property and parameter names SHOULD be upper-case.
o Use ABNF for cardinality notation. o Use ABNF for cardinality notation.
B.2. Changes in -14 B.3. Changes in -14
o DQUOTE is US-ASCII decimal 34, not 22. o DQUOTE is US-ASCII decimal 34, not 22.
o Removed unused reference to RFC 2046. o Removed unused reference to RFC 2046.
o Updated reference to draft-ietf-vcarddav-vcardxml. o Updated reference to draft-ietf-vcarddav-vcardxml.
o Small fixes to the IANA registration text. o Small fixes to the IANA registration text.
o Added notes on the usage of TEL and IMPP properties. o Added notes on the usage of TEL and IMPP properties.
skipping to change at page 71, line 47 skipping to change at page 74, line 29
o Removed advice for always including VALUE parameter. o Removed advice for always including VALUE parameter.
o FMTTYPE MUST include the full MIME type. o FMTTYPE MUST include the full MIME type.
o Made ADR's ABNF more verbose. o Made ADR's ABNF more verbose.
o Organized TEL TYPE values in a table. o Organized TEL TYPE values in a table.
o Replaced TOP-SECRET example with NOINDEX. o Replaced TOP-SECRET example with NOINDEX.
B.3. Changes in -13 B.4. Changes in -13
o Changed global ABNF to make explicit that VERSION comes first. o Changed global ABNF to make explicit that VERSION comes first.
o Reworked example for LANGUAGE property. o Reworked example for LANGUAGE property.
o s/TYPE/FMTTYPE/ in two examples. o s/TYPE/FMTTYPE/ in two examples.
o Allow LANGUAGE parameter for text-valued BDAY, DDAY, and RELATED. o Allow LANGUAGE parameter for text-valued BDAY, DDAY, and RELATED.
o Tightened language on LANGUAGE parameter regarding cardinality. o Tightened language on LANGUAGE parameter regarding cardinality.
o Removed the NAME property. o Removed the NAME property.
o Adjusted semi-colon escaping rules. o Adjusted semi-colon escaping rules.
o Added the ALTID parameter. o Added the ALTID parameter.
B.4. Changes in -12 B.5. Changes in -12
o Fixed example of LANGUAGE cardinality. o Fixed example of LANGUAGE cardinality.
o Added note about YYYY-MM date format. o Added note about YYYY-MM date format.
o Fixed appendix A. o Fixed appendix A.
o VERSION property must come first. o VERSION property must come first.
o Fixed mistake in PID example. o Fixed mistake in PID example.
skipping to change at page 73, line 19 skipping to change at page 76, line 5
o BIRTH and DEATH can now have URI values. o BIRTH and DEATH can now have URI values.
o Created the FMTTYPE parameter. o Created the FMTTYPE parameter.
o KEY can now take a text value. o KEY can now take a text value.
o Added references to RFC 5545 (iCalendar). o Added references to RFC 5545 (iCalendar).
o Added namespace column in parameters registry. o Added namespace column in parameters registry.
B.5. Changes in -11 B.6. Changes in -11
o Change "XML chunk" to "XML fragment". o Change "XML chunk" to "XML fragment".
o Cite W3C document containing definition of "fragment". o Cite W3C document containing definition of "fragment".
o Added "XML" to property name ABNF. o Added "XML" to property name ABNF.
o Clarified newline escaping rule. o Clarified newline escaping rule.
o Replaced one remaining "type" with "property". o Replaced one remaining "type" with "property".
skipping to change at page 73, line 43 skipping to change at page 76, line 29
o XML property can now only contain one element that is not in the o XML property can now only contain one element that is not in the
vCard 4 namespace. vCard 4 namespace.
o Clarified interrelationship between LANGUAGE, cardinality, and o Clarified interrelationship between LANGUAGE, cardinality, and
PID. PID.
o Added "textphone" TEL type. o Added "textphone" TEL type.
o Fixed quoting of comma in ORG examples. o Fixed quoting of comma in ORG examples.
B.6. Changes in -10 B.7. Changes in -10
o Added component in SORT-STRING for sorting by given name. Fixed o Added component in SORT-STRING for sorting by given name. Fixed
and expanded the examples. and expanded the examples.
o Fixed KIND-value ABNF. o Fixed KIND-value ABNF.
o Fixed deprecated media type. o Fixed deprecated media type.
o Created the CALSCALE parameter. o Created the CALSCALE parameter.
o Strenghtened the stance on character set. o Strenghtened the stance on character set.
o Defined the Language-Tag ABNF. o Defined the Language-Tag ABNF.
o Made explicit the fact that IANA does not register templates. o Made explicit the fact that IANA does not register templates.
o Created the XML property. o Created the XML property.
o Added social networking examples to URL property. o Added social networking examples to URL property.
B.7. Changes in -09 B.8. Changes in -09
o Removed special meaning for groups. Removed the "work" and "home" o Removed special meaning for groups. Removed the "work" and "home"
groups. Removed the group registry. Re-introduced the "work" and groups. Removed the group registry. Re-introduced the "work" and
"home" TYPE parameter values. Applied the TYPE parameter to "home" TYPE parameter values. Applied the TYPE parameter to
properties which supported the "work" and "home" groups. properties which supported the "work" and "home" groups.
o Vendor namespace now uses private enterprise number in prefix. o Vendor namespace now uses private enterprise number in prefix.
o Added "thing" value for KIND property. o Added "thing" value for KIND property.
B.8. Changes in -08 B.9. Changes in -08
o Allow 1985 (year only) in date ABNF. o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example. o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value. o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME. o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to o Prefixed "param" and "value" production rules specific to
skipping to change at page 75, line 5 skipping to change at page 77, line 39
o Replaced the GENDER property with the SEX property. o Replaced the GENDER property with the SEX property.
o Added the ANNIVERSARY property. o Added the ANNIVERSARY property.
o Added the "friend" and "spouse" types of RELATED. o Added the "friend" and "spouse" types of RELATED.
o TZ property now has text / uri value. o TZ property now has text / uri value.
o Refined the definitions of TITLE and ROLE. o Refined the definitions of TITLE and ROLE.
B.9. Changes in -07 B.10. Changes in -07
o PREF is now bounded. 100 is the maximum value. o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type. o Added the "emergency" RELATED type.
o Made GEO a URI. o Made GEO a URI.
o Added GEO and TZ parameters to ADR. o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property. o Changed wording of "default" use of SOUND property.
skipping to change at page 75, line 27 skipping to change at page 78, line 13
o Completely reworked the date, time, and date-time grammars. o Completely reworked the date, time, and date-time grammars.
o Added the timestamp value type. o Added the timestamp value type.
o REV now has the timestamp value type. o REV now has the timestamp value type.
o Rewrote ABNF. o Rewrote ABNF.
o ORG can now have a single level. o ORG can now have a single level.
B.10. Changes in -06 B.11. Changes in -06
o Corrected omission of resetability to text value for RELATED. o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value. o Let KEY value type be reset to a URI value.
o ABNF fixes. o ABNF fixes.
o Made gender values extensible. o Made gender values extensible.
o Gave the PREF parameter a positive integer value. o Gave the PREF parameter a positive integer value.
skipping to change at page 76, line 19 skipping to change at page 79, line 5
o Removed TYPE parameter from EMAIL properties in examples. o Removed TYPE parameter from EMAIL properties in examples.
o Created the CLIENTPIDMAP property. o Created the CLIENTPIDMAP property.
o Changed PID value to a pair of small integers. o Changed PID value to a pair of small integers.
o Completely reworked synchronization mechanisms. o Completely reworked synchronization mechanisms.
o Created brand new synchronization example. o Created brand new synchronization example.
B.11. Changes in -05 B.12. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.12. Changes in -04 B.13. Changes in -04
o Added "location" value for KIND property. o Added "location" value for KIND property.
o Some fixes to ABNF. o Some fixes to ABNF.
o Moved "pref" from being a TYPE value to a parameter in its own o Moved "pref" from being a TYPE value to a parameter in its own
right. right.
o Removed the "work" and "home" TYPE values. o Removed the "work" and "home" TYPE values.
skipping to change at page 77, line 5 skipping to change at page 79, line 39
o Removed TYPE parameter from EMAIL and IMPP properties. o Removed TYPE parameter from EMAIL and IMPP properties.
o Replaced AGENT with a type of RELATED. o Replaced AGENT with a type of RELATED.
o Use example.org domain in URL example. o Use example.org domain in URL example.
o Created initial IANA table of values. o Created initial IANA table of values.
o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL. o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.
B.13. Changes in -03 B.14. Changes in -03
o Various changes to the synchronization mechanisms. o Various changes to the synchronization mechanisms.
o Allowed truncated format for dated. See issue #236. o Allowed truncated format for dated. See issue #236.
B.14. Changes in -02 B.15. Changes in -02
o Removed useless text in IMPP description. o Removed useless text in IMPP description.
o Added CalDAV-SCHED example to CALADRURI. o Added CalDAV-SCHED example to CALADRURI.
o Removed CAPURI property. o Removed CAPURI property.
o Dashes in dates and colons in times are now mandatory. o Dashes in dates and colons in times are now mandatory.
o Allow for dates such as 2008 and 2008-05 and times such as 07 and o Allow for dates such as 2008 and 2008-05 and times such as 07 and
skipping to change at page 77, line 44 skipping to change at page 80, line 30
o Changed the presence of UID and PID when synchronization is to be o Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD. used from MUST to SHOULD.
o Added the RELATED (Section 6.6.6) property. o Added the RELATED (Section 6.6.6) property.
o Fixed many ABNF typos (issue #252). o Fixed many ABNF typos (issue #252).
o Changed formatting of ABNF comments to make them easier to read o Changed formatting of ABNF comments to make them easier to read
(issue #226). (issue #226).
B.15. Changes in -01 B.16. Changes in -01
o Merged [RFC2739] in. o Merged [RFC2739] in.
o Converted all foobar.com, abc.com, etc. to example.com. o Converted all foobar.com, abc.com, etc. to example.com.
o Fixed bugs in ABNF. o Fixed bugs in ABNF.
o Made explicit that coordinates in the GEO property are expressed o Made explicit that coordinates in the GEO property are expressed
in the WGS 84 reference system. in the WGS 84 reference system.
skipping to change at page 78, line 25 skipping to change at page 81, line 9
o Added Section 7. o Added Section 7.
o Created IANA process for registering new parameters, value types, o Created IANA process for registering new parameters, value types,
and properties. and properties.
o Created the initial IANA registries. o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288. o Created vendor namespace based on text from RFC 4288.
B.16. Changes in -00 B.17. Changes in -00
o Name change because draft has been accepted as WG item. o Name change because draft has been accepted as WG item.
Otherwise, same as draft-resnick-vcarddav-vcardrev-01. Otherwise, same as draft-resnick-vcarddav-vcardrev-01.
o Removed reference to RFC 2234. o Removed reference to RFC 2234.
o Fixed errata from o Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426. http://www.rfc-editor.org/errata_search.php?rfc=2426.
o Removed passage referring to RFC 2425 profiles. o Removed passage referring to RFC 2425 profiles.
skipping to change at page 79, line 27 skipping to change at page 82, line 12
o Updated obsolete references. o Updated obsolete references.
o Allowed BDAY and DDAY value types to be text values for fuzzy o Allowed BDAY and DDAY value types to be text values for fuzzy
dates. dates.
o Removed the CHARSET property. Now the encoding is always UTF-8, o Removed the CHARSET property. Now the encoding is always UTF-8,
except when overridden by the Content-Type (which is considered a except when overridden by the Content-Type (which is considered a
compatibility feature). compatibility feature).
Authors' Addresses 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
URI: http://www.viagenie.ca URI: http://www.viagenie.ca
Peter W. Resnick
QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, CA 92121-1714
US
Phone: +1 858 651 4478
EMail: presnick@qualcomm.com
URI: http://www.qualcomm.com/~presnick/
 End of changes. 74 change blocks. 
206 lines changed or deleted 345 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/