draft-ietf-vcarddav-vcardrev-21.txt   draft-ietf-vcarddav-vcardrev-22.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 May 21, 2011 Obsoletes: 2425, 2426, 4770 May 26, 2011
(if approved) (if approved)
Updates: 2739 (if approved) Updates: 2739 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: November 22, 2011 Expires: November 27, 2011
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-21 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, 2739, and clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and
4770. updates RFC 2739.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 22, 2011. This Internet-Draft will expire on November 27, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 29
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. vCard Format Specification . . . . . . . . . . . . . . . . . . 6 3. vCard Format Specification . . . . . . . . . . . . . . . . . . 6
3.1. Charset . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Charset . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 6 3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 6
3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7 3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 7
3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 9 3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 10
4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10 4. Property Value Data Types . . . . . . . . . . . . . . . . . . 10
4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 13 4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 13
4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 14 4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 14
4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14 4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14
4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 15 4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 15
4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 3, line 14 skipping to change at page 3, line 14
5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 24 6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. General Properties . . . . . . . . . . . . . . . . . . . . 24 6.1. General Properties . . . . . . . . . . . . . . . . . . . . 24
6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 25 6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2. Identification Properties . . . . . . . . . . . . . . . . 29 6.2. Identification Properties . . . . . . . . . . . . . . . . 29
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 31 6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 31 6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 33 6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 32
6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 33 6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 33
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 34 6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 34
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4. Communications Properties . . . . . . . . . . . . . . . . 35 6.4. Communications Properties . . . . . . . . . . . . . . . . 35
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 37 6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 37
6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.5. Geographical Properties . . . . . . . . . . . . . . . . . 39 6.5. Geographical Properties . . . . . . . . . . . . . . . . . 39
6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6. Organizational Properties . . . . . . . . . . . . . . . . 40 6.6. Organizational Properties . . . . . . . . . . . . . . . . 40
6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 40 6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 42 6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 42
skipping to change at page 4, line 43 skipping to change at page 4, line 43
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 65 10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 65
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 66 10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 66
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 67 10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 67
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 67 10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 67
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70
12.1. Normative References . . . . . . . . . . . . . . . . . . . 70 12.1. Normative References . . . . . . . . . . . . . . . . . . . 70
12.2. Informative References . . . . . . . . . . . . . . . . . . 73 12.2. Informative References . . . . . . . . . . . . . . . . . . 73
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 75 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 75
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 75 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 75
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 75 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 76
A.3. New Properties and Parameters . . . . . . . . . . . . . . 75 A.3. New Properties and Parameters . . . . . . . . . . . . . . 76
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 76 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 76
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 76 publication) . . . . . . . . . . . . . . . . . . . . 77
B.1. Changes in -21 . . . . . . . . . . . . . . . . . . . . . . 76 B.1. Changes in -22 . . . . . . . . . . . . . . . . . . . . . . 77
B.2. Changes in -20 . . . . . . . . . . . . . . . . . . . . . . 76 B.2. Changes in -21 . . . . . . . . . . . . . . . . . . . . . . 77
B.3. Changes in -19 . . . . . . . . . . . . . . . . . . . . . . 77 B.3. Changes in -20 . . . . . . . . . . . . . . . . . . . . . . 77
B.4. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 77 B.4. Changes in -19 . . . . . . . . . . . . . . . . . . . . . . 78
B.5. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 77 B.5. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 78
B.6. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 78 B.6. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 78
B.7. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 78 B.7. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 79
B.8. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 79 B.8. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 79
B.9. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 80 B.9. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 80
B.10. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 80 B.10. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 81
B.11. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 81 B.11. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 81
B.12. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 82 B.12. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 82
B.13. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 82 B.13. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 83
B.14. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 82 B.14. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 83
B.15. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 83 B.15. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 83
B.16. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 83 B.16. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 84
B.17. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 84 B.17. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 84
B.18. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 84 B.18. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 85
B.19. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 85 B.19. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 85
B.20. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 85 B.20. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 86
B.21. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 86 B.21. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 86
B.22. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 86 B.22. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 87
B.23. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 87
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.
A high-level overview of the differences from RFCs 2425 and 2426 can
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
skipping to change at page 6, line 38 skipping to change at page 6, line 41
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).
3.2. Line Delimiting and Folding 3.2. Line Delimiting and Folding
Individual lines within vCard are delimited by the [RFC5322] line Individual lines within vCard are delimited by the [RFC5322] line
break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII break, which is a CRLF sequence (U+000D followed by U+000A). Long
decimal 10). Long logical lines of text can be split into a logical lines of text can be split into a multiple-physical-line
multiple-physical-line representation using the following folding representation using the following folding technique. Content lines
technique. Content lines SHOULD be folded to a maximum width of 75 SHOULD be folded to a maximum width of 75 octets, excluding the line
octets, excluding the line break. Multi-octet characters MUST remain break. Multi-octet characters MUST remain contiguous. The rationale
contiguous. The rationale for this folding process can be found in for this folding process can be found in [RFC5322], Section 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 (U+0020) or horizontal tab
tab, (ASCII decimal 9)). The folded line MUST contain at least one (U+0009)). The folded line MUST contain at least one character. Any
character. Any sequence of CRLF followed immediately by a single sequence of CRLF followed immediately by a single white space
white space character is ignored (removed) when processing the character is ignored (removed) when processing the content type. For
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 ASCII decimal 9 or followed by a white space character (namely HTAB (U+0009) or SPACE
SPACE ASCII decimal 32) as equivalent to no characters at all (i.e., (U+0020)) as equivalent to no characters at all (i.e., the CRLF and
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.
Folding is done after any content encoding of a type value. Folding is done after any content encoding of a type value.
skipping to change at page 8, line 39 skipping to change at page 8, line 42
param = language-param / value-param / pref-param / pid-param param = language-param / value-param / pref-param / pid-param
/ type-param / geo-parameter / tz-parameter / sort-as-param / type-param / geo-parameter / tz-parameter / sort-as-param
/ calscale-param / any-param / calscale-param / any-param
; Allowed parameters depend on property name. ; Allowed parameters depend on property name.
param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
any-param = (iana-token / x-name) "=" param-value *("," param-value) any-param = (iana-token / x-name) "=" param-value *("," param-value)
NON-ASCII = %x80-FF NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; Use is restricted by UTF-8 ; UTF8-{2,3,4} are defined in [RFC3629]
QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE ; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":" ; Any character except CTLs, DQUOTE, ";", ":"
VALUE-CHAR = WSP / VCHAR / NON-ASCII VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character ; Any textual character
skipping to change at page 9, line 51 skipping to change at page 10, line 8
multi-valued properties is to simply create a new content line for multi-valued properties is to simply create a new content line for
each value (including the property name). However, it should be each value (including the property name). However, it should be
noted that some value types support encoding multiple values in a noted that some value types support encoding multiple values in a
single content line by separating the values with a comma ",". This single content line by separating the values with a comma ",". This
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 (ASCII decimal 44). Therefore, a COMMA character in a character (U+002C). Therefore, a COMMA character in a value MUST be
value MUST be escaped with a BACKSLASH character (ASCII decimal 92), escaped with a BACKSLASH character (U+005C), even for properties that
even for properties that don't allow multiple instances (for don't allow multiple instances (for consistency).
consistency).
Some properties (e.g. N and ADR) comprise multiple fields delimited Some properties (e.g. N and ADR) comprise multiple fields delimited
by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI- by a SEMI-COLON character (U+003B). Therefore, a SEMI-COLON in a
COLON in a field of such a "compound" property MUST be escaped with a field of such a "compound" property MUST be escaped with a BACKSLASH
BACKSLASH character. SEMI-COLON characters in non-compound character. SEMI-COLON characters in non-compound properties MAY be
properties MAY be escaped. On input, an escaped SEMI-COLON character escaped. On input, an escaped SEMI-COLON character is never a field
is never a field separator. An unescaped SEMI-COLON character may be separator. An unescaped SEMI-COLON character may be a field
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
BACKSLASH character. NEWLINE (ASCII decimal 10) characters in values BACKSLASH character. NEWLINE (U+000A) characters in values MUST be
MUST be encoded by two characters: a BACKSLASH followed by either an encoded by two characters: a BACKSLASH followed by either an 'n'
'n' (ASCII decimal 110) or an 'N' (ASCII decimal 78). (U+006E) or an 'N' (U+004E).
In all other cases, escaping MUST NOT be used. In all other cases, escaping MUST NOT be used.
4. Property Value Data Types 4. Property Value Data Types
Standard value types are defined below. Standard value types are defined below.
value = text value = text
/ text-list / text-list
/ date-list / date-list
skipping to change at page 11, line 4 skipping to change at page 11, line 6
/ boolean / boolean
/ integer-list / integer-list
/ float-list / float-list
/ URI ; from Section 3 of [RFC3986] / URI ; from Section 3 of [RFC3986]
/ utc-offset / utc-offset
/ Language-Tag / Language-Tag
/ iana-valuespec / iana-valuespec
; Actual value type depends on property name and VALUE parameter. ; Actual value type depends on property name and VALUE parameter.
text = *TEXT-CHAR text = *TEXT-CHAR
TEXT-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \> TEXT-CHAR = "\\" / "\," / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-5B / %x5D-7E
; Backslashes, commas, and newlines must be encoded. ; Backslashes, commas, and newlines must be encoded.
component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E / %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
list-component = component *("," component) list-component = component *("," component)
text-list = text *("," text) text-list = text *("," text)
date-list = date *("," date) date-list = date *("," date)
time-list = time *("," time) time-list = time *("," time)
date-time-list = date-time *("," date-time) date-time-list = date-time *("," date-time)
skipping to change at page 12, line 31 skipping to change at page 12, line 32
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 (ASCII decimal 92) followed by a as the character sequence backslash (U+005C) followed by a Latin
Latin small letter n (ASCII decimal 110) or a Latin capital letter N small letter n (U+006E) or a Latin capital letter N (U+004E), that is
(ASCII decimal 78), that is "\n" or "\N". "\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
skipping to change at page 17, line 6 skipping to change at page 17, line 6
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 (US-ASCII decimal 44). separated by a COMMA (U+002C).
Property parameter value elements that contain the COLON (US-ASCII Property parameter value elements that contain the COLON (U+003A),
decimal 58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII SEMICOLON (U+003B) or COMMA (U+002C) character separators MUST be
decimal 44) character separators MUST be specified as quoted-string specified as quoted-string text values. Property parameter values
text values. Property parameter values MUST NOT contain the DQUOTE MUST NOT contain the DQUOTE (U+0022) character. The DQUOTE character
(US-ASCII decimal 34) character. The DQUOTE character is used as a is used as a delimiter for parameter values that contain restricted
delimiter for parameter values that contain restricted characters or characters or URI text.
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
The LANGUAGE property parameter is used to identify data in multiple The LANGUAGE property parameter is used to identify data in multiple
languages. There is no concept of "default" language, except as languages. There is no concept of "default" language, except as
specified by any "Content-Language" MIME header parameter that is specified by any "Content-Language" MIME header parameter that is
present [RFC3282]. The value of the LANGUAGE property parameter is a present [RFC3282]. The value of the LANGUAGE property parameter is a
skipping to change at page 17, line 38 skipping to change at page 17, line 37
ROLE;LANGUAGE=tr:hoca ROLE;LANGUAGE=tr:hoca
ABNF: ABNF:
language-param = "LANGUAGE=" Language-Tag language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 5646 ; Language-Tag is defined in section 2.1 of RFC 5646
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:
skipping to change at page 18, line 26 skipping to change at page 18, line 26
/ "boolean" / "boolean"
/ "integer" / "integer"
/ "float" / "float"
/ "utc-offset" / "utc-offset"
/ "language-tag" / "language-tag"
/ iana-token ; registered as described in section 12 / iana-token ; registered as described in section 12
/ x-name / x-name
5.3. PREF 5.3. PREF
The PREF parameter is optional and is used to indicate that the The PREF parameter is OPTIONAL and is used to indicate that the
corresponding instance of a property is preferred by the vCard corresponding instance of a property is preferred by the vCard
author. Its value MUST be an integer between 1 and 100 that author. Its value MUST be an integer between 1 and 100 that
quantifies the level of preference. Lower values correspond to a quantifies the level of preference. Lower values correspond to a
higher level of preference, 1 being most preferred. higher level of preference, 1 being most preferred.
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
skipping to change at page 24, line 44 skipping to change at page 24, line 44
delimit an entity containing a related set of properties within an delimit an entity containing a related set of properties within an
text/vcard content-type. This construct can be used instead of 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 = 0dummy ; no parameter allowed BEGIN-param = 0" " ; no parameter allowed
BEGIN-value = "VCARD" BEGIN-value = "VCARD"
dummy = "A" ; This is used to pacify ABNF parsers.
Example: Example:
BEGIN:VCARD BEGIN:VCARD
6.1.2. END 6.1.2. END
Purpose: To denote the end of a syntactic entity within a text/vcard Purpose: To denote the end of a syntactic entity within a text/vcard
content-type. content-type.
Value type: text Value type: text
skipping to change at page 25, line 32 skipping to change at page 25, line 28
delimit an entity containing a related set of properties within an delimit an entity containing a related set of properties within an
text/vcard content-type. This construct can be used instead of or text/vcard content-type. This construct can be used instead of or
in addition to wrapping separate sets of information inside in addition to wrapping separate sets of information inside
additional MIME headers. It is provided for applications that additional MIME headers. It is provided for applications that
wish to define content that can contain multiple entities within wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be the same text/vcard content-type or to define content that can be
identifiable outside of a MIME environment. identifiable outside of a MIME environment.
ABNF: ABNF:
END-param = 0dummy ; no parameter allowed END-param = 0" " ; no parameter allowed
END-value = "VCARD" END-value = "VCARD"
Example: Example:
END:VCARD END:VCARD
6.1.3. SOURCE 6.1.3. SOURCE
Purpose: To identify the source of directory information contained Purpose: To identify the source of directory information contained
in the content type. in the content type.
skipping to change at page 30, line 42 skipping to change at page 30, line 29
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 SEMI-COLON
character (ASCII decimal 59). Individual text components can character (U+003B). Individual text components can include
include multiple text values separated by the COMMA character multiple text values separated by the COMMA character (U+002C).
(ASCII decimal 44). This property is based on the semantics of This property is based on the semantics of the X.520 individual
the X.520 individual name attributes. The property SHOULD be name attributes. The property SHOULD be present in the vCard
present in the vCard object when the name of the object the vCard object when the name of the object the vCard represents follows
represents follows the X.520 model. 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 23 skipping to change at page 31, line 11
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.
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(ASCII decimal 44). (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 a 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:
skipping to change at page 34, line 4 skipping to change at page 33, line 44
Sex component: A single letter. M stands for "male", F stands Sex component: A single letter. M stands for "male", F stands
for "female", O stands for "other", N stands for "none or not for "female", O stands for "other", N stands for "none or not
applicable", U stands for "unknown". applicable", U stands for "unknown".
Gender identity component: Free-form text. Gender identity component: Free-form text.
ABNF: ABNF:
GENDER-param = "VALUE=text" / any-param GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text] GENDER-value = sex [";" text]
sex = "" / "M" / "F" / "O" / "N" / "U" sex = "" / "M" / "F" / "O" / "N" / "U"
Examples: Examples:
GENDER:M GENDER:M
GENDER:F GENDER:F
GENDER:M;Fellow GENDER:M;Fellow
GENDER:F;Bird GENDER:F;grrrl
GENDER:O;intersex GENDER:O;intersex
GENDER:;queer GENDER:;it's complicated
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 SEMI-
COLON character (ASCII decimal 59). COLON 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;
skipping to change at page 35, line 6 skipping to change at page 34, line 48
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 SEMI-COLON character
(ASCII decimal 59). Where it makes semantic sense, individual (U+003B). Where it makes semantic sense, individual text
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
(ASCII decimal 44). (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 delivery address label for the address. Its value is a
plain-text string representing the formatted address. Newlines plain-text string representing the formatted address. Newlines
skipping to change at page 39, line 34 skipping to change at page 39, line 34
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. restriction. See also [I-D.lear-iana-timezone-database].
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
skipping to change at page 42, line 35 skipping to change at page 42, line 35
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 (ASCII decimal 59). separated by the SEMI-COLON 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. The property value is a
structured type consisting of the organization name, followed by structured type consisting of the organization name, followed by
zero or more levels of organizational unit names. zero or more levels of organizational unit names.
The SORT-AS parameter MAY be applied to this property. The SORT-AS parameter MAY be applied to this property.
skipping to change at page 45, line 45 skipping to change at page 45, line 45
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
(ASCII decimal 44). (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
skipping to change at page 51, line 20 skipping to change at page 51, line 20
KEY-uri-value = URI KEY-uri-value = URI
KEY-text-param = "VALUE=text" KEY-text-param = "VALUE=text"
KEY-text-value = text KEY-text-value = text
KEY-param =/ altid-param / pid-param / pref-param / type-param KEY-param =/ altid-param / pid-param / pref-param / type-param
/ any-param / any-param
Examples: Examples:
KEY:http://www.example.com/keys/jdoe KEY:http://www.example.com/keys/jdoe.cer
KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe
KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE
UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l
<... remainder of base64-encoded data ...> <... remainder of base64-encoded data ...>
6.9. Calendar Properties 6.9. Calendar Properties
These properties are further specified in [RFC2739]. These properties are further specified in [RFC2739].
skipping to change at page 59, line 44 skipping to change at page 59, line 44
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 privacy provisions, they can easily no inherent authentication or confidentiality provisions, they can
be carried by any security mechanism that transfers MIME objects easily be carried by any security mechanism that transfers MIME
to address authentication or privacy (e.g. S/MIME [RFC5751], objects to address authentication or confidentiality (e.g. S/MIME
OpenPGP [RFC4880]). In cases where the privacy or authenticity of [RFC5751], OpenPGP [RFC4880]). In cases where the confidentiality
information contained in vCard is a concern, the vCard SHOULD be or authenticity of information contained in vCard is a concern,
transported using one of these secure mechanisms. The KEY the vCard SHOULD be transported using one of these secure
property (Section 6.8.1) can be used to transport the public key mechanisms. The KEY property (Section 6.8.1) can be used to
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 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.
o Many vCard properties may be used to transport URIs. Please refer
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 is asked to register the following Media Type (in
<http://www.iana.org/assignments/media-types/>). <http://www.iana.org/assignments/media-types/>), and to mark the
text/directory Media Type as 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 15 skipping to change at page 61, line 15
In addition, the following media types are known to have been used In addition, the following media types are known to have been used
to refer to vCard data. They should be considered deprecated in to refer to vCard data. They should be considered deprecated in
favor of text/vcard. favor of text/vcard.
* text/directory * text/directory
* text/directory; profile=vcard * text/directory; profile=vcard
* text/x-vcard * text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-21 Published specification: draft-ietf-vcarddav-vcardrev-22
Applications that use this media type: They are numerous, diverse, Applications that use this media type: They are numerous, diverse,
and include mail user agents, instant messaging clients, address and include mail user agents, instant messaging clients, address
book applications, directory servers, customer relationship book applications, directory servers, customer relationship
management software. management software.
Additional information: Additional information:
Magic number(s): Magic number(s):
skipping to change at page 62, line 35 skipping to change at page 62, line 35
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 [I-D.ietf-vcarddav-vcardxml]. An XML representation SHOULD be
defined for new vCard objects. defined for new vCard 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 70, line 41 skipping to change at page 70, line 41
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 Telegraph [CCITT.E163.1988] International Telephone and
Consultative Committee, "Numbering Plan Telegraph Consultative Committee,
for the International Telephone "Numbering Plan for the
Service", CCITT Recommendation E.163, International Telephone Service",
1988. CCITT Recommendation E.163, 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 [CCITT.X121.1988] International Telephone and
and Telegraph Consultative Committee, Telegraph Consultative Committee,
"Information Technology - Open Systems "International Numbering Plan for
Interconnection - The Directory: the Public Data Networks",
Selected Attribute Types", CCITT Recommendation X.121, 1988.
CCITT Recommendation X.520,
November 1988.
[CCITT.X521.1988] International International Telephone [CCITT.X520.1988] International International
and Telegraph Consultative Committee, Telephone and Telegraph
"Information Technology - Open Systems Consultative Committee,
Interconnection - The Directory: "Information Technology - Open
Selected Object Classes", Systems Interconnection - The
CCITT Recommendation X.521, Directory: Selected Attribute
November 1988. Types", CCITT Recommendation
X.520, November 1988.
[I-D.ietf-vcarddav-vcardxml] Perreault, S., "vCard XML [CCITT.X521.1988] International International
Representation", Telephone and Telegraph
draft-ietf-vcarddav-vcardxml-08 (work Consultative Committee,
in progress), April 2011. "Information Technology - Open
Systems Interconnection - The
Directory: Selected Object
Classes", CCITT Recommendation
X.521, November 1988.
[IEEE.754.2008] Institute of Electrical and Electronics [I-D.ietf-vcarddav-vcardxml] Perreault, S., "vCard XML
Engineers, "IEEE Standard for Floating- Representation",
Point Arithmetic", IEEE Standard 754, draft-ietf-vcarddav-vcardxml-08
August 2008. (work in progress), April 2011.
[ISO.8601.2000] International Organization for [IEEE.754.2008] Institute of Electrical and
Standardization, "Data elements and Electronics Engineers, "IEEE
interchange formats - Information Standard for Floating-Point
interchange - Representation of dates Arithmetic", IEEE Standard 754,
and times", ISO Standard 8601, August 2008.
December 2000.
[ISO.8601.2004] International Organization for [ISO.8601.2000] International Organization for
Standardization, "Data elements and Standardization, "Data elements
interchange formats - Information and interchange formats -
interchange - Representation of dates Information interchange -
and times", ISO Standard 8601, Representation of dates and
December 2004. times", ISO Standard 8601,
December 2000.
[RFC2045] Freed, N. and N. Borenstein, [ISO.8601.2004] International Organization for
"Multipurpose Internet Mail Extensions Standardization, "Data elements
(MIME) Part One: Format of Internet and interchange formats -
Message Bodies", RFC 2045, Information interchange -
November 1996. Representation of dates and
times", ISO Standard 8601,
December 2004.
[RFC2046] Freed, N. and N. Borenstein, [RFC2045] Freed, N. and N. Borenstein,
"Multipurpose Internet Mail Extensions "Multipurpose Internet Mail
(MIME) Part Two: Media Types", Extensions (MIME) Part One: Format
RFC 2046, November 1996. of Internet Message Bodies",
RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs [RFC2046] Freed, N. and N. Borenstein,
to Indicate Requirement Levels", "Multipurpose Internet Mail
BCP 14, RFC 2119, March 1997. Extensions (MIME) Part Two: Media
Types", RFC 2046, November 1996.
[RFC2739] Small, T., Hennessy, D., and F. Dawson, [RFC2119] Bradner, S., "Key words for use in
"Calendar Attributes for vCard and RFCs to Indicate Requirement
LDAP", RFC 2739, January 2000. Levels", BCP 14, RFC 2119,
March 1997.
[RFC3536] Hoffman, P., "Terminology Used in [RFC2739] Small, T., Hennessy, D., and F.
Internationalization in the IETF", Dawson, "Calendar Attributes for
RFC 3536, May 2003. vCard and LDAP", RFC 2739,
January 2000.
[RFC3629] Yergeau, F., "UTF-8, a transformation [RFC3629] Yergeau, F., "UTF-8, a
format of ISO 10646", STD 63, RFC 3629, transformation format of ISO
November 2003. 10646", STD 63, RFC 3629,
November 2003.
[RFC3966] Schulzrinne, H., "The tel URI for [RFC3966] Schulzrinne, H., "The tel URI for
Telephone Numbers", RFC 3966, Telephone Numbers", RFC 3966,
December 2004. December 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. [RFC3986] Berners-Lee, T., Fielding, R., and
Masinter, "Uniform Resource Identifier L. Masinter, "Uniform Resource
(URI): Generic Syntax", STD 66, Identifier (URI): Generic Syntax",
RFC 3986, January 2005. STD 66, RFC 3986, January 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, [RFC4122] Leach, P., Mealling, M., and R.
"A Universally Unique IDentifier (UUID) Salz, "A Universally Unique
URN Namespace", RFC 4122, July 2005. IDentifier (UUID) URN Namespace",
RFC 4122, July 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type [RFC4288] Freed, N. and J. Klensin, "Media
Specifications and Registration Type Specifications and
Procedures", BCP 13, RFC 4288, Registration Procedures", BCP 13,
December 2005. RFC 4288, December 2005.
[RFC5234] Crocker, D. and P. Overell, "Augmented [RFC5234] Crocker, D. and P. Overell,
BNF for Syntax Specifications: ABNF", "Augmented BNF for Syntax
STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68,
RFC 5234, January 2008.
[RFC5322] Resnick, P., Ed., "Internet Message [RFC5322] Resnick, P., Ed., "Internet
Format", RFC 5322, October 2008. Message Format", RFC 5322,
October 2008.
[RFC5545] Desruisseaux, B., "Internet Calendaring [RFC5545] Desruisseaux, B., "Internet
and Scheduling Core Object Calendaring and Scheduling Core
Specification (iCalendar)", RFC 5545, Object Specification (iCalendar)",
September 2009. RFC 5545, September 2009.
[RFC5546] Daboo, C., "iCalendar Transport- [RFC5546] Daboo, C., "iCalendar Transport-
Independent Interoperability Protocol Independent Interoperability
(iTIP)", RFC 5546, December 2009. Protocol (iTIP)", RFC 5546,
December 2009.
[RFC5646] Phillips, A. and M. Davis, "Tags for [RFC5646] Phillips, A. and M. Davis, "Tags
Identifying Languages", BCP 47, for Identifying Languages",
RFC 5646, September 2009. BCP 47, RFC 5646, September 2009.
[RFC5870] Mayrhofer, A. and C. Spanring, "A [RFC5870] Mayrhofer, A. and C. Spanring, "A
Uniform Resource Identifier for Uniform Resource Identifier for
Geographic Locations ('geo' URI)", Geographic Locations ('geo' URI)",
RFC 5870, June 2010. RFC 5870, June 2010.
[W3C.REC-xml-20081126] Sperberg-McQueen, C., Yergeau, F., [W3C.REC-xml-20081126] Paoli, J., Yergeau, F., Bray, T.,
Bray, T., Paoli, J., and E. Maler, Maler, E., and C. Sperberg-
"Extensible Markup Language (XML) 1.0 McQueen, "Extensible Markup
(Fifth Edition)", World Wide Web Language (XML) 1.0 (Fifth
Consortium Recommendation REC-xml- Edition)", World Wide Web
20081126, November 2008, <http:// Consortium Recommendation REC-xml-
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. Meyer, [xfn] Celik, T., Mullenweg, M., and E.
"XHTML Friends Network 1.1", 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, [I-D.ietf-eai-rfc5335bis] Yang, A. and S. Steele,
"Internationalized Email Headers", "Internationalized Email Headers",
draft-ietf-eai-rfc5335bis-10 (work in draft-ietf-eai-rfc5335bis-10 (work
progress), March 2011. in progress), March 2011.
[ISO9070] The International Organization for [I-D.lear-iana-timezone-database] Lear, E. and P. Eggert, "IANA
Standardization, "ISO 9070, Information Procedures for Maintaining the
Processing - SGML support facilities - Timezone Database", draft-lear-
Registration Procedures for Public Text iana-timezone-database-04 (work in
Owner Identifiers", April 1991. progress), May 2011.
[RFC1738] Berners-Lee, T., Masinter, L., and M. [ISO9070] The International Organization for
McCahill, "Uniform Resource Locators Standardization, "ISO 9070,
(URL)", RFC 1738, December 1994. Information Processing - SGML
support facilities - Registration
Procedures for Public Text Owner
Identifiers", April 1991.
[RFC2397] Masinter, L., "The "data" URL scheme", [RFC1738] Berners-Lee, T., Masinter, L., and
RFC 2397, August 1998. M. McCahill, "Uniform Resource
Locators (URL)", RFC 1738,
December 1994.
[RFC2425] Howes, T., Smith, M., and F. Dawson, "A [RFC2397] Masinter, L., "The "data" URL
MIME Content-Type for Directory scheme", RFC 2397, August 1998.
Information", RFC 2425, September 1998.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME [RFC2425] Howes, T., Smith, M., and F.
Directory Profile", RFC 2426, Dawson, "A MIME Content-Type for
September 1998. Directory Information", RFC 2425,
September 1998.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., [RFC2426] Dawson, F. and T. Howes, "vCard
Frystyk, H., Masinter, L., Leach, P., MIME Directory Profile", RFC 2426,
and T. Berners-Lee, "Hypertext Transfer September 1998.
Protocol -- HTTP/1.1", RFC 2616,
June 1999.
[RFC3282] Alvestrand, H., "Content Language [RFC2616] Fielding, R., Gettys, J., Mogul,
Headers", RFC 3282, May 2002. J., Frystyk, H., Masinter, L.,
Leach, P., and T. Berners-Lee,
"Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999.
[RFC3406] Daigle, L., van Gulik, D., Iannella, [RFC3282] Alvestrand, H., "Content Language
R., and P. Faltstrom, "Uniform Resource Headers", RFC 3282, May 2002.
Names (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406,
October 2002.
[RFC4770] Jennings, C. and J. Reschke, Ed., [RFC3406] Daigle, L., van Gulik, D.,
"vCard Extensions for Instant Messaging Iannella, R., and P. Faltstrom,
(IM)", RFC 4770, January 2007. "Uniform Resource Names (URN)
Namespace Definition Mechanisms",
BCP 66, RFC 3406, October 2002.
[RFC4880] Callas, J., Donnerhacke, L., Finney, [RFC3536] Hoffman, P., "Terminology Used in
H., Shaw, D., and R. Thayer, "OpenPGP Internationalization in the IETF",
Message Format", RFC 4880, RFC 3536, May 2003.
November 2007.
[RFC5751] Ramsdell, B. and S. Turner, "Secure/ [RFC4770] Jennings, C. and J. Reschke, Ed.,
Multipurpose Internet Mail Extensions "vCard Extensions for Instant
(S/MIME) Version 3.2 Message Messaging (IM)", RFC 4770,
Specification", RFC 5751, January 2010. January 2007.
[RFC6068] Duerst, M., Masinter, L., and J. [RFC4880] Callas, J., Donnerhacke, L.,
Zawinski, "The 'mailto' URI Scheme", Finney, H., Shaw, D., and R.
RFC 6068, October 2010. Thayer, "OpenPGP Message Format",
RFC 4880, November 2007.
[TZ-DB] Olson, A., "Time zone code and data", [RFC5751] Ramsdell, B. and S. Turner,
<ftp://elsie.nci.nih.gov/pub/>. "Secure/Multipurpose Internet Mail
Extensions (S/MIME) Version 3.2
Message Specification", RFC 5751,
January 2010.
[vCard21] Internet Mail Consortium, "vCard - The [RFC6068] Duerst, M., Masinter, L., and J.
Electronic Business Card Version 2.1", Zawinski, "The 'mailto' URI
September September. Scheme", RFC 6068, October 2010.
[TZ-DB] Olson, A., "Time zone code and
data",
<ftp://elsie.nci.nih.gov/pub/>.
[vCard21] Internet Mail Consortium, "vCard -
The Electronic Business Card
Version 2.1", September September.
URIs URIs
[1] <mailto:vcarddav@ietf.org> [1] <mailto:vcarddav@ietf.org>
[2] <mailto:iana@iana.org> [2] <mailto:iana@iana.org>
Appendix A. Differences from RFCs 2425 and 2426 Appendix A. Differences from RFCs 2425 and 2426
This appendix contains a list of changes that have been made in the This appendix contains a high-level overview of the major changes
vCard specification from RFCs 2425 and 2426. that have been made in the vCard specification from RFCs 2425 and
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 default character set. o UTF-8 is now the only possible character set.
o New vCard elements can be registered from IANA. o New vCard elements can be registered from IANA.
o Expanded text on character set.
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 Inline vCards (such as the value of the AGENT property) are no
longer supported. longer supported.
o In the N property, each component may now contain multiple comma-
separated values.
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.
o [RFC4770], which defines the IMPP property, has been merged in. o [RFC4770], which defines the IMPP property, has been merged in.
o The "work", "home", and "uri" TYPE parameter values for the EMAIL o The "work" and "home" TYPE parameter values are now applicable to
property have been added. many more properties.
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 A.4. Other Changes
o Synchronization is addressed in Section 7. o Synchronization is addressed in Section 7.
o The N property is no longer mandatory. o The N property is no longer mandatory.
o In the N property, each component may now contain multiple comma-
separated values.
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 -21 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. o Minor ABNF clarification.
B.2. Changes in -20 B.3. Changes in -20
o Reworded security considerations. o Reworded security considerations.
o Specified range of integer and float value types. o Specified range of integer and float value types.
o Adjusted IANA considerations wording. o Adjusted IANA considerations wording.
o Added missing date-and-or-type to the VALUE ABNF. o Added missing date-and-or-type to the VALUE ABNF.
o s/vcard@ietf.org/vcarddav@ietf.org/ o s/vcard@ietf.org/vcarddav@ietf.org/
skipping to change at page 77, line 18 skipping to change at page 78, line 21
o Removed Pete Resnick's example vCard. o Removed Pete Resnick's example vCard.
o vcarddav@ietf.org is the contact person for the media type. 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 o Add missing pref-param, pid-param, and any-param to the PHOTO
property. property.
o Re-added missing section on UTC-OFFSET value type. o Re-added missing section on UTC-OFFSET value type.
B.3. Changes in -19 B.4. Changes in -19
o Fixed nits. o Fixed nits.
o Fixed MEDIATYPE ABNF. o Fixed MEDIATYPE ABNF.
B.4. Changes in -18 B.5. Changes in -18
o Fix missing text in KIND section. o Fix missing text in KIND section.
B.5. Changes in -17 B.6. Changes in -17
o s/individual/entity/ o s/individual/entity/
o Moved section 3.4 for better flow. o Moved section 3.4 for better flow.
o Removed text overriding general MIME and HTTP rules. o Removed text overriding general MIME and HTTP rules.
o Fixed redundant ABNF. o Fixed redundant ABNF.
o Fixed parameter value quoting in examples. o Fixed parameter value quoting in examples.
skipping to change at page 78, line 20 skipping to change at page 79, line 24
IANA Considerations section. IANA Considerations section.
o Removed underspecified "Status" column in IANA registry. o Removed underspecified "Status" column in IANA registry.
o Moved obsoleted references to Informative section. o Moved obsoleted references to Informative section.
o Moved iCalendar references to Normative section. o Moved iCalendar references to Normative section.
o Expanded specification of KIND values. o Expanded specification of KIND values.
o Recommend defining an XML representation for new vCard objects. o Recommend defining an XML representation for new vCard elements.
B.6. Changes in -16 B.7. Changes in -16
o RELATED: Added XFN values into IANA registry. o RELATED: Added XFN values into IANA registry.
o RELATED: Added values "agent" and "emergency". o RELATED: Added values "agent" and "emergency".
o EMAIL is now free-form text, with informative reference to EAI. o EMAIL is now free-form text, with informative reference to EAI.
o GENDER now has two components: one for biological sex, the other o GENDER now has two components: one for biological sex, the other
for gender identity. for gender identity.
o Bugfixes to the core ABNF. o Bugfixes to the core ABNF.
o Clarified IANA considerations. o Clarified IANA considerations.
o UID may be reset to free-form text. o UID may be reset to free-form text.
B.7. Changes in -15 B.8. 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 79, line 25 skipping to change at page 80, line 28
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.8. Changes in -14 B.9. 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 80, line 11 skipping to change at page 81, line 15
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.9. Changes in -13 B.10. 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.10. Changes in -12 B.11. 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 81, line 32 skipping to change at page 82, line 36
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.11. Changes in -11 B.12. 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 82, line 9 skipping to change at page 83, line 12
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.12. Changes in -10 B.13. 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.13. Changes in -09 B.14. 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.14. Changes in -08 B.15. 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 83, line 15 skipping to change at page 84, line 20
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.15. Changes in -07 B.16. 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 83, line 37 skipping to change at page 84, line 42
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.16. Changes in -06 B.17. 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 84, line 28 skipping to change at page 85, line 34
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.17. Changes in -05 B.18. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.18. Changes in -04 B.19. 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 85, line 15 skipping to change at page 86, line 20
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.19. Changes in -03 B.20. 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.20. Changes in -02 B.21. 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 86, line 5 skipping to change at page 87, line 12
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.21. Changes in -01 B.22. 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 86, line 33 skipping to change at page 87, line 40
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.22. Changes in -00 B.23. Changes in -00
o Name change because draft has been accepted as WG item. o Name change because draft has been accepted as WG item.
Otherwise, same as draft-resnick-vcarddav-vcardrev-01. Otherwise, same as draft-resnick-vcarddav-vcardrev-01.
o Removed reference to RFC 2234. o Removed reference to RFC 2234.
o Fixed errata from o Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426. http://www.rfc-editor.org/errata_search.php?rfc=2426.
o Removed passage referring to RFC 2425 profiles. o Removed passage referring to RFC 2425 profiles.
 End of changes. 115 change blocks. 
306 lines changed or deleted 359 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/