draft-ietf-vcarddav-vcardrev-18.txt   draft-ietf-vcarddav-vcardrev-19.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 April 6, 2011 Obsoletes: 2425, 2426, 4770 April 9, 2011
(if approved) (if approved)
Updates: 2739 (if approved) Updates: 2739 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: October 8, 2011 Expires: October 11, 2011
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-18 draft-ietf-vcarddav-vcardrev-19
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.). This document obsoletes RFCs 2425, 2426, 2739, and
4770.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on October 11, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 8, 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
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
described in the BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
skipping to change at page 4, line 45 skipping to change at page 4, line 40
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 64 10.3. Initial vCard Elements Registries . . . . . . . . . . . . 64
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 64 10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 64
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 65 10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 65
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 66 10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 66
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 66 10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 66
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69 12.1. Normative References . . . . . . . . . . . . . . . . . . . 69
12.2. Informative References . . . . . . . . . . . . . . . . . . 72 12.2. Informative References . . . . . . . . . . . . . . . . . . 72
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 73 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 74
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 74 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 74
A.3. New Properties and Parameters . . . . . . . . . . . . . . 74 A.3. New Properties and Parameters . . . . . . . . . . . . . . 74
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 74 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 75
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 75 publication) . . . . . . . . . . . . . . . . . . . . 75
B.1. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 75 B.1. Changes in -19 . . . . . . . . . . . . . . . . . . . . . . 75
B.2. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 75 B.2. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 75
B.3. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 76 B.3. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 75
B.4. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 76 B.4. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 76
B.5. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 77 B.5. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 76
B.6. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 78 B.6. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 77
B.7. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 78 B.7. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 78
B.8. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 79 B.8. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 78
B.9. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 80 B.9. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 79
B.10. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 80 B.10. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 80
B.11. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 80 B.11. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 80
B.12. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 81 B.12. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 80
B.13. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 81 B.13. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 81
B.14. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 82 B.14. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 81
B.15. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 82 B.15. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 82
B.16. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 83 B.16. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 82
B.17. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 83 B.17. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 83
B.18. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 84 B.18. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 83
B.19. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 84 B.19. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 84
B.20. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 84
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.
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", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
3. vCard Format Specification 3. vCard Format Specification
The text/vcard MIME content type (hereafter known as "vCard", see The text/vcard MIME content type (hereafter known as "vCard", see
Section 10.1) contains contact information, typically pertaining to a Section 10.1) contains contact information, typically pertaining to a
single contact or group of contacts. The content consists of one or single contact or group of contacts. The content consists of one or
more lines in the format given below. more lines in the format given below.
3.1. Character Set 3.1. Character Set
skipping to change at page 6, line 46 skipping to change at page 6, line 47
break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII
decimal 10). Long logical lines of text can be split into a decimal 10). Long logical lines of text can be split into a
multiple-physical-line representation using the following folding multiple-physical-line representation using the following folding
technique. Content lines SHOULD be folded to a maximum width of 75 technique. Content lines SHOULD be folded to a maximum width of 75
octets, excluding the line break. Multi-octet characters MUST remain octets, excluding the line break. Multi-octet characters MUST remain
contiguous. The rationale for this folding process can be found in contiguous. The rationale for this folding process can be found in
[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 (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.
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.
skipping to change at page 7, line 40 skipping to change at page 7, line 42
Folding is done after any content encoding of a type value. Folding is done after any content encoding of a type value.
Unfolding is done before any decoding of a type value in a content Unfolding is done before any decoding of a type value in a content
line. line.
3.3. ABNF Format Definition 3.3. ABNF Format Definition
The following ABNF uses the notation of [RFC5234], which also defines The following ABNF uses the notation of [RFC5234], which also defines
CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.
vcard-entity = 1*(vcard) vcard-entity = 1*vcard
vcard = "BEGIN" ":" "VCARD" CRLF vcard = "BEGIN:VCARD" CRLF
"VERSION" ":" "4.0" CRLF "VERSION:4.0" CRLF
1*contentline 1*contentline
"END" ":" "VCARD" CRLF "END:VCARD" CRLF
; A vCard object MUST include the VERSION and FN properties. ; A vCard object MUST include the VERSION and FN properties.
; VERSION MUST come immediately after BEGIN:VCARD. ; VERSION MUST come immediately after BEGIN:VCARD.
contentline = [group "."] name *(";" param) ":" value CRLF contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines must first ; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure ; be unfolded according to the unfolding procedure
; described above. ; described above.
; When generating a content line, lines longer than 75 ; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding ; characters SHOULD be folded according to the folding
; procedure described above. ; procedure described above.
group = 1*(ALPHA / DIGIT / "-") group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME" name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / / "TEL" / "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
/ "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE" / "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
/ "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES" / "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
/ "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP" / "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
/ "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML" / "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ iana-token / x-name / iana-token / x-name
; Parsing of the param and value is based on the "name" as ; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below. ; defined in ABNF sections below.
; Group and name are case-insensitive. ; Group and name are case-insensitive.
iana-token = 1*(ALPHA / DIGIT / "-") iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA ; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-") x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are ; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released ; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements. ; products, or for use in bilateral agreements.
param = language-param / value-param / pref-param / pid-param param = language-param / value-param / pref-param / pid-param
/ type-param / geo-param / tz-param / sort-as-param / type-param / geo-parameter / tz-parameter / sort-as-param
/ calscale-param / version-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 = %x80-FF
; Use is restricted by UTF-8 ; Use is restricted by UTF-8
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE ; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-39 / %x3C-7E / NON-ASCII SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":" ; Any character except CTLs, DQUOTE, ";", ":"
VALUE-CHAR = WSP / VCHAR / NON-ASCII VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character ; Any textual character
A line that begins with a white space character is a continuation of A line that begins with a white space character is a continuation of
the previous line, as described above. The white space character and the previous line, as described above. The white space character and
immediately preceeding CRLF should be discarded when reconstructing immediately preceeding CRLF should be discarded when reconstructing
the original line. Note that this line-folding convention differs the original line. Note that this line-folding convention differs
from that found in [RFC5322], in that the sequence <CRLF><WSP> found from that found in [RFC5322], in that the sequence <CRLF><WSP> found
skipping to change at page 11, line 29 skipping to change at page 11, line 31
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
minute = 2DIGIT ; 00-59 minute = 2DIGIT ; 00-59
second = 2DIGIT ; 00-58/59/60 depending on leap second second = 2DIGIT ; 00-58/59/60 depending on leap second
zone = utc-designator / utc-offset zone = utc-designator / utc-offset
utc-designator = %d90 ; uppercase "Z" utc-designator = %x5A ; uppercase "Z"
date = year [month day] date = year [month day]
/ year "-" month / year "-" month
/ "--" month [day] / "--" month [day]
/ "--" "-" day / "--" "-" day
date-noreduc = year month day date-noreduc = year month day
/ "--" month day / "--" month day
/ "--" "-" day / "--" "-" day
date-complete = year month day date-complete = year month day
time = hour [minute [second]] [zone] time = hour [minute [second]] [zone]
/ "-" minute [second] [zone] / "-" minute [second] [zone]
/ "-" "-" second [zone] / "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone] time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone] time-complete = hour minute second [zone]
time-designator = %d84 ; uppercase "T" time-designator = %x54 ; uppercase "T"
date-time = date-noreduc time-designator time-notrunc date-time = date-noreduc time-designator time-notrunc
timestamp = date-complete time-designator time-complete timestamp = date-complete time-designator time-complete
date-and-or-time = date-time / date / time-designator time date-and-or-time = date-time / date / time-designator time
utc-offset = sign hour [minute] utc-offset = sign hour [minute]
Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1> Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1>
iana-valuespec = <value-spec, see Section 12> iana-valuespec = <value-spec, see Section 12>
; a publicly-defined valuetype format, registered ; a publicly-defined valuetype format, registered
; with IANA, as defined in section 12 of this ; with IANA, as defined in section 12 of this
; document ; document
4.1. TEXT 4.1. TEXT
"text": The "text" value type should be used to identify values that "text": The "text" value type should be used to identify values that
skipping to change at page 17, line 19 skipping to change at page 17, line 19
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, and is used to identify the value The VALUE parameter is optional, used to identify the value type
type (data type) and format of the value. The use of these (data type) and format of the value. The use of these predefined
predefined formats is encouraged even if the value parameter is not formats is encouraged even if the value parameter is not explicitly
explicitly used. By defining a standard set of value types and their used. By defining a standard set of value types and their formats,
formats, existing parsing and processing code can be leveraged. The existing parsing and processing code can be leveraged. The
predefined data type values MUST NOT be repeated in COMMA separated predefined data type values MUST NOT be repeated in COMMA separated
value lists except within the N, NICKNAME, ADR and CATEGORIES value lists except within the N, NICKNAME, ADR, and CATEGORIES
properties. properties.
ABNF: ABNF:
value-param = "VALUE=" value-type value-param = "VALUE=" value-type
value-type = "text" value-type = "text"
/ "uri" / "uri"
/ "date" / "date"
/ "time" / "time"
skipping to change at page 17, line 48 skipping to change at page 17, line 48
/ "boolean" / "boolean"
/ "integer" / "integer"
/ "float" / "float"
/ "language-tag" / "language-tag"
/ "utc-offset" / "utc-offset"
/ 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 20, line 12 skipping to change at page 20, line 12
altid-param = "ALTID=" param-value altid-param = "ALTID=" param-value
5.5. PID 5.5. PID
The PID parameter is used to identify a specific property among The PID parameter is used to identify a specific property among
multiple instances. It plays a role analogous to the UID property multiple instances. It plays a role analogous to the UID property
(Section 6.7.6) on a per-property instead of per-vCard basis. It MAY (Section 6.7.6) on a per-property instead of per-vCard basis. It MAY
appear more than once in a given property. It MUST NOT appear on appear more than once in a given property. It MUST NOT appear on
properties that may have only one instance per vCard. Its value is properties that may have only one instance per vCard. Its value is
either a single small positive integer, or a pair of small positive either a single small positive integer or a pair of small positive
integers separated by a dot. Multiple values may be encoded in a integers separated by a dot. Multiple values may be encoded in a
single PID parameter by separating the values with a comma ",". See single PID parameter by separating the values with a comma ",". See
Section 7 for more details on its usage. Section 7 for more details on its usage.
ABNF: ABNF:
pid-param = "PID=" pid-value *("," pid-value) pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT] pid-value = 1*DIGIT ["." 1*DIGIT]
5.6. TYPE 5.6. TYPE
skipping to change at page 21, line 21 skipping to change at page 21, line 21
"data" scheme allows the media type to be explicitly indicated as "data" scheme allows the media type to be explicitly indicated as
part of the URI [RFC2397]. Another scheme, "http", provides the part of the URI [RFC2397]. Another scheme, "http", provides the
media type as part of the URI resolution process, with the Content- media type as part of the URI resolution process, with the Content-
Type HTTP header [RFC2616]. The MEDIATYPE parameter is intended to Type HTTP header [RFC2616]. The MEDIATYPE parameter is intended to
be used with URI schemes that do not provide such functionality (e.g. be used with URI schemes that do not provide such functionality (e.g.
"ftp" [RFC1738]). "ftp" [RFC1738]).
ABNF: ABNF:
mediatype-param = "MEDIATYPE=" mediatype mediatype-param = "MEDIATYPE=" mediatype
mediatype = type "/" subtype *( ";" attribute "=" value ) mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "type", "subtype", "attribute", and "value" are from [RFC2045]. ; "attribute" and "value" are from [RFC2045]
; "type-name" and "subtype-name" are from [RFC4288]
5.8. CALSCALE 5.8. CALSCALE
The CALSCALE parameter is identical to the CALSCALE property in The CALSCALE parameter is identical to the CALSCALE property in
iCalendar (see [RFC5545], section 3.7.1). It is used to define the iCalendar (see [RFC5545], section 3.7.1). It is used to define the
calendar system in which a date or date-time value is expressed. The calendar system in which a date or date-time value is expressed. The
only value specified by iCalendar is "gregorian", which stands for only value specified by iCalendar is "gregorian", which stands for
the Gregorian system. It is the default when the parameter is the Gregorian system. It is the default when the parameter is
absent. Additional values may be defined in extension documents and absent. Additional values may be defined in extension documents and
registered from IANA (see Section 10.3.4). A vCard implementation registered from IANA (see Section 10.3.4). A vCard implementation
skipping to change at page 23, line 13 skipping to change at page 23, line 13
Robert Pau Shou Chang Robert Pau Shou Chang
5.10. GEO 5.10. GEO
The GEO parameter can be used to indicate global positioning The GEO parameter can be used to indicate global positioning
information that is specific to an address. Its value is the same as information that is specific to an address. Its value is the same as
that of the GEO property (see Section 6.5.2). that of the GEO property (see Section 6.5.2).
ABNF: ABNF:
geo-param = "GEO=" DQUOTE uri DQUOTE geo-parameter = "GEO=" DQUOTE URI DQUOTE
5.11. TZ 5.11. TZ
The TZ parameter can be used to indicate time zone information that The TZ parameter can be used to indicate time zone information that
is specific to an address. Its value is the same as that of the TZ is specific to an address. Its value is the same as that of the TZ
property. property.
ABNF: ABNF:
tz-param = "TZ=" (param-value / DQUOTE uri DQUOTE) tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
6. vCard Properties 6. vCard Properties
What follows is an enumeration of the standard vCard properties. What follows is an enumeration of the standard vCard properties.
6.1. General Properties 6.1. General Properties
6.1.1. BEGIN 6.1.1. BEGIN
Purpose: To denote the beginning of a syntactic entity within a Purpose: To denote the beginning of a syntactic entity within a
skipping to change at page 24, line 7 skipping to change at page 24, line 7
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:
BEGIN-param = ; no parameter allowed BEGIN-param = 0<nothing> ; no parameter allowed
BEGIN-value = "VCARD" BEGIN-value = "VCARD"
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.
skipping to change at page 24, line 37 skipping to change at page 24, line 37
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 = ; no parameter allowed END-param = 0<nothing> ; 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 25, line 20 skipping to change at page 25, line 20
and/or other information referencing the vCard to which the and/or other information referencing the vCard to which the
information pertains. When directory information is available information pertains. When directory information is available
from more than one source, the sending entity can pick what it from more than one source, the sending entity can pick what it
considers to be the best source, or multiple SOURCE properties can considers to be the best source, or multiple SOURCE properties can
be included. be included.
ABNF: ABNF:
SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param / mediatype-param / any-param
SOURCE-value = uri SOURCE-value = URI
Examples: Examples:
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/ SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf Jean%20Dupont.vcf
6.1.4. KIND 6.1.4. KIND
skipping to change at page 26, line 30 skipping to change at page 26, line 30
organization as a whole, as is the case with a group vCard. organization as a whole, as is the case with a group vCard.
For example, an EMAIL property might specify the address of a For example, an EMAIL property might specify the address of a
contact point for the organization. contact point for the organization.
"location" for a named geographical place. A location vCard will "location" for a named geographical place. A location vCard will
usually contain a GEO property, but it is not required to. A usually contain a GEO property, but it is not required to. A
location vCard without a GEO property can be considered an location vCard without a GEO property can be considered an
abstract location, or one whose definition is known empirically abstract location, or one whose definition is known empirically
(perhaps "New England" or "The Seashore"). (perhaps "New England" or "The Seashore").
All properties in an location vCard apply to the location All properties in a location vCard apply to the location
itself, and not with any entity that might exist at that itself, and not with any entity that might exist at that
location. For example, in a vCard for an office building, an location. For example, in a vCard for an office building, an
ADR property might give the mailing address for the building, ADR property might give the mailing address for the building,
and a TEL property might specify the telephone number of the and a TEL property might specify the telephone number of the
receptionist. receptionist.
An x-name. vCards MAY include private or experimental values for An x-name. vCards MAY include private or experimental values for
KIND. Remember that x-name values are not intended for general KIND. Remember that x-name values are not intended for general
use, and are unlikely to interoperate. use, and are unlikely to interoperate.
An iana-token. Additional values may be registered with IANA (see An iana-token. Additional values may be registered with IANA (see
Section 10.3.4). A new value's specification document MUST Section 10.3.4). A new value's specification document MUST
specify which properties make sense for that new kind of vCard, specify which properties make sense for that new kind of vCard
and which do not. and which do not.
Implementations MUST support the specific string values defined Implementations MUST support the specific string values defined
above. If this property is absent, "individual" MUST be assumed above. If this property is absent, "individual" MUST be assumed
as the default. If this property is present but the as the default. If this property is present but the
implementation does not understand its value (the value is an implementation does not understand its value (the value is an
x-name or iana-token that the implementation does not support), x-name or iana-token that the implementation does not support),
the implementation SHOULD act in a neutral way, which usually the implementation SHOULD act in a neutral way, which usually
means treating the vCard as though its kind were "individual". means treating the vCard as though its kind were "individual".
skipping to change at page 31, line 13 skipping to change at page 31, line 13
annotates some aspect of the object the vCard represents. annotates some aspect of the object the vCard represents.
Value type: A single URI. Value type: A single URI.
Cardinality: * Cardinality: *
ABNF: ABNF:
PHOTO-param = "VALUE=uri" / altid-param / type-param PHOTO-param = "VALUE=uri" / altid-param / type-param
/ mediatype-param / mediatype-param
PHOTO-value = uri PHOTO-value = URI
Examples: Examples:
PHOTO:http://www.example.com/pub/photos/jqpublic.gif PHOTO:http://www.example.com/pub/photos/jqpublic.gif
PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of base64-encoded data...> <...remainder of base64-encoded data...>
skipping to change at page 34, line 20 skipping to change at page 34, line 20
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
are encoded as \n, as they are for property values. are encoded as \n, as they are for property values.
ABNF: ABNF:
label-param = "LABEL=" param-value label-param = "LABEL=" param-value
ADR-param = "VALUE=text" / label-param / language-param / geo-param ADR-param = "VALUE=text" / label-param / language-param
/ tz-param / altid-param / pid-param / pref-param / geo-parameter / tz-parameter / altid-param / pid-param
/ type-param / any-param / pref-param / type-param / any-param
ADR-value = ADR-component-pobox ";" ADR-component-ext ";" ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
ADR-component-street ";" ADR-component-locality ";" ADR-component-street ";" ADR-component-locality ";"
ADR-component-region ";" ADR-component-code ";" ADR-component-region ";" ADR-component-code ";"
ADR-component-country ADR-component-country
ADR-component-pobox = list-component ADR-component-pobox = list-component
ADR-component-ext = list-component ADR-component-ext = list-component
ADR-component-street = list-component ADR-component-street = list-component
ADR-component-locality = list-component ADR-component-locality = list-component
ADR-component-region = list-component ADR-component-region = list-component
ADR-component-code = list-component ADR-component-code = list-component
skipping to change at page 36, line 15 skipping to change at page 36, line 15
ABNF: ABNF:
TEL-param = TEL-text-param / TEL-uri-param TEL-param = TEL-text-param / TEL-uri-param
TEL-value = TEL-text-value / TEL-uri-value TEL-value = TEL-text-value / TEL-uri-value
; Value and parameter MUST match ; Value and parameter MUST match
TEL-text-param = "VALUE=text" TEL-text-param = "VALUE=text"
TEL-text-value = text TEL-text-value = text
TEL-uri-param = "VALUE=uri" / mediatype-param TEL-uri-param = "VALUE=uri" / mediatype-param
TEL-uri-value = uri TEL-uri-value = URI
TEL-param =/ type-param / pid-param / pref-param / altid-param TEL-param =/ type-param / pid-param / pref-param / altid-param
/ any-param / any-param
type-param-tel = "text" / "voice" / "fax" / "cell" / "video" type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / "textphone" / iana-token / x-name / "pager" / "textphone" / iana-token / x-name
; type-param-tel MUST NOT be used with a property other than TEL. ; type-param-tel MUST NOT be used with a property other than TEL.
Example: Example:
skipping to change at page 37, line 35 skipping to change at page 37, line 35
and/or video, the TEL property (Section 6.4.1) SHOULD be used in and/or video, the TEL property (Section 6.4.1) SHOULD be used in
addition to this property. addition to this property.
This property is adapted from [RFC4770], which is made obsolete by This property is adapted from [RFC4770], which is made obsolete by
this document. this document.
ABNF: ABNF:
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
IMPP-value = uri IMPP-value = URI
Example: Example:
IMPP;PREF=1:xmpp:alice@example.com IMPP;PREF=1:xmpp:alice@example.com
6.4.4. LANG 6.4.4. LANG
Purpose: To specify the language(s) that may be used for contacting Purpose: To specify the language(s) that may be used for contacting
the entity associated with the vCard. the entity associated with the vCard.
skipping to change at page 39, line 6 skipping to change at page 39, line 6
Note that utc-offset values SHOULD NOT be used because the UTC Note that utc-offset values SHOULD NOT be used because the UTC
offset varies with time - not just because of the usual daylight offset varies with time - not just because of the usual daylight
saving time shifts that occur in may regions, but often entire saving time shifts that occur in may regions, but often entire
regions will "re-base" their overall offset. The actual offset regions will "re-base" their overall offset. The actual offset
may be +/- 1 hour (or perhaps a little more) than the one given. may be +/- 1 hour (or perhaps a little more) than the one given.
ABNF: ABNF:
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset") TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / uri / utc-offset TZ-value = text / URI / utc-offset
; Value and parameter MUST match ; Value and parameter MUST match
TZ-param =/ altid-param / pid-param / pref-param / type-param TZ-param =/ altid-param / pid-param / pref-param / type-param
/ mediatype-param / any-param / mediatype-param / any-param
Examples: Examples:
TZ:Raleigh/North America TZ:Raleigh/North America
TZ;VALUE=utc-offset:-0500 TZ;VALUE=utc-offset:-0500
skipping to change at page 39, line 35 skipping to change at page 39, line 35
Cardinality: * Cardinality: *
Special notes: The "geo" URI scheme [RFC5870] is particularly well- Special notes: The "geo" URI scheme [RFC5870] is particularly well-
suited for this property, but other schemes MAY be used. suited for this property, but other schemes MAY be used.
ABNF: ABNF:
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
GEO-value = uri GEO-value = URI
Example: Example:
GEO:geo:37.386013,-122.082932 GEO:geo:37.386013,-122.082932
6.6. Organizational Properties 6.6. Organizational Properties
These properties are concerned with information associated with These properties are concerned with information associated with
characteristics of the organization or organizational units of the characteristics of the organization or organizational units of the
object that the vCard represents. object that the vCard represents.
skipping to change at page 41, line 18 skipping to change at page 41, line 18
object the vCard represents. object the vCard represents.
Value type: A single URI. Value type: A single URI.
Cardinality: * Cardinality: *
ABNF: ABNF:
LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param / any-param / type-param / mediatype-param / altid-param / any-param
LOGO-value = uri LOGO-value = URI
Examples: Examples:
LOGO:http://www.example.com/pub/logos/abccorp.jpg LOGO:http://www.example.com/pub/logos/abccorp.jpg
LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...> <...the remainder of base64-encoded data...>
skipping to change at page 42, line 27 skipping to change at page 42, line 27
Cardinality: * Cardinality: *
Special notes: This property MUST NOT be present unless the value of Special notes: This property MUST NOT be present unless the value of
the KIND property is "group". the KIND property is "group".
ABNF: ABNF:
MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param / mediatype-param / any-param
MEMBER-value = uri MEMBER-value = URI
Examples: Examples:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:group KIND:group
FN:The Doe family FN:The Doe family
MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519 MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD END:VCARD
skipping to change at page 44, line 6 skipping to change at page 44, line 6
document also specifies two additional values: document also specifies two additional values:
agent: an entity who may sometimes act on behalf of the entity agent: an entity who may sometimes act on behalf of the entity
associated with the vCard. associated with the vCard.
emergency: indicates an emergency contact emergency: indicates an emergency contact
ABNF: ABNF:
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" / mediatype-param RELATED-param-uri = "VALUE=uri" / mediatype-param
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 = related-type-value *("," related-type-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
skipping to change at page 46, line 50 skipping to change at page 46, line 50
Value type: A single URI. Value type: A single URI.
Cardinality: * Cardinality: *
ABNF: ABNF:
SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param / type-param / mediatype-param / altid-param
/ any-param / any-param
SOUND-value = uri SOUND-value = URI
Example: Example:
SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...> <...the remainder of base64-encoded data...>
skipping to change at page 47, line 34 skipping to change at page 47, line 34
[RFC4122] is particularly well-suited to this task, but other URI [RFC4122] is particularly well-suited to this task, but other URI
schemes MAY be used. Free-form text MAY also be used. schemes MAY be used. Free-form text MAY also be used.
ABNF: ABNF:
UID-param = UID-uri-param / UID-text-param UID-param = UID-uri-param / UID-text-param
UID-value = UID-uri-value / UID-text-value UID-value = UID-uri-value / UID-text-value
; Value and parameter MUST match. ; Value and parameter MUST match.
UID-uri-param = "VALUE=uri" UID-uri-param = "VALUE=uri"
UID-uri-value = uri UID-uri-value = URI
UID-text-param = "VALUE=text" UID-text-param = "VALUE=text"
UID-text-value = text UID-text-value = text
UID-param =/ any-param UID-param =/ any-param
Example: Example:
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
skipping to change at page 48, line 24 skipping to change at page 48, line 24
PID source identifiers MUST be strictly positive. Zero is not PID source identifiers MUST be strictly positive. Zero is not
allowed. allowed.
As a special exception, the PID parameter MUST NOT be applied to As a special exception, the PID parameter MUST NOT be applied to
this property. this property.
ABNF: ABNF:
CLIENTPIDMAP-param = any-param CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" uri CLIENTPIDMAP-value = 1*DIGIT ";" URI
Example: Example:
TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555 TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5 CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
6.7.8. URL 6.7.8. URL
skipping to change at page 48, line 47 skipping to change at page 48, line 47
personal web sites, blogs, and social networking site identifiers. personal web sites, blogs, and social networking site identifiers.
Cardinality: * Cardinality: *
Value type: A single uri value. Value type: A single uri value.
ABNF: ABNF:
URL-param = "VALUE=uri" / pid-param / pref-param / type-param URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
URL-value = uri URL-value = URI
Example: Example:
URL:http://example.org/restaurant.french/~chezchic.html URL:http://example.org/restaurant.french/~chezchic.html
6.7.9. VERSION 6.7.9. VERSION
Purpose: To specify the version of the vCard specification used to Purpose: To specify the version of the vCard specification used to
format this vCard. format this vCard.
skipping to change at page 50, line 10 skipping to change at page 50, line 10
Cardinality: * Cardinality: *
ABNF: ABNF:
KEY-param = KEY-uri-param / KEY-text-param KEY-param = KEY-uri-param / KEY-text-param
KEY-value = KEY-uri-value / KEY-text-value KEY-value = KEY-uri-value / KEY-text-value
; Value and parameter MUST match. ; Value and parameter MUST match.
KEY-uri-param = "VALUE=uri" / mediatype-param KEY-uri-param = "VALUE=uri" / mediatype-param
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
skipping to change at page 51, line 5 skipping to change at page 51, line 5
[RFC5545] object associated with a snapshot of the next few weeks [RFC5545] object associated with a snapshot of the next few weeks
or months of busy time data. If the iCalendar object is or months of busy time data. If the iCalendar object is
represented as a file or document, its file extension should be represented as a file or document, its file extension should be
".ifb". ".ifb".
ABNF: ABNF:
FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
FBURL-value = uri FBURL-value = URI
Examples: Examples:
FBURL;PREF=1:http://www.example.com/busy/janedoe FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb
6.9.2. CALADRURI 6.9.2. CALADRURI
Purpose: To specify the calendar user address [RFC5545] to which a Purpose: To specify the calendar user address [RFC5545] to which a
scheduling request [RFC5546] should be sent for the object scheduling request [RFC5546] should be sent for the object
skipping to change at page 51, line 30 skipping to change at page 51, line 30
Cardinality: * Cardinality: *
Special notes: Where multiple CALADRURI properties are specified, Special notes: Where multiple CALADRURI properties are specified,
the default CALADRURI property is indicated with the PREF the default CALADRURI property is indicated with the PREF
parameter. parameter.
ABNF: ABNF:
CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
CALADRURI-value = uri CALADRURI-value = URI
Example: Example:
CALADRURI;PREF=1:mailto:janedoe@example.com CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe CALADRURI:http://example.com/calendar/jdoe
6.9.3. CALURI 6.9.3. CALURI
Purpose: To specify the URI for a calendar associated with the Purpose: To specify the URI for a calendar associated with the
object represented by the vCard. object represented by the vCard.
skipping to change at page 52, line 9 skipping to change at page 52, line 9
default CALURI property is indicated with the PREF parameter. The default CALURI property is indicated with the PREF parameter. The
property should contain a URI pointing to an iCalendar [RFC5545] property should contain a URI pointing to an iCalendar [RFC5545]
object associated with a snapshot of the user's calendar store. object associated with a snapshot of the user's calendar store.
If the iCalendar object is represented as a file or document, its If the iCalendar object is represented as a file or document, its
file extension should be ".ics". file extension should be ".ics".
ABNF: ABNF:
CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param / mediatype-param / altid-param / any-param
CALURI-value = uri CALURI-value = URI
Examples: Examples:
CALURI;PREF=1:http://cal.example.com/calA CALURI;PREF=1:http://cal.example.com/calA
CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics
6.10. Extended Properties and Parameters 6.10. Extended Properties and Parameters
The properties and parameters defined by this document can be The properties and parameters defined by this document can be
extended. Non-standard, private properties and parameters with a extended. Non-standard, private properties and parameters with a
skipping to change at page 60, line 19 skipping to change at page 60, line 19
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-18 Published specification: draft-ietf-vcarddav-vcardrev-19
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 60, line 41 skipping to change at page 60, line 41
Macintosh file type code(s): Macintosh file type code(s):
Person & email address to contact for further information: Simon Person & email address to contact for further information: Simon
Perreault <simon.perreault@viagenie.ca> Perreault <simon.perreault@viagenie.ca>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author: Simon Perreault and Pete Resnick Author: Simon Perreault
Change controller: IETF Change controller: IETF
10.2. Registering New vCard Elements 10.2. Registering New vCard Elements
This section defines the process for registering new or modified This section defines the process for registering new or modified
vCard elements (i.e. properties, parameters, value data types, and vCard elements (i.e. properties, parameters, value data types, and
values) with IANA. It does not contain any immediate IANA actions. values) with IANA. It does not contain any immediate IANA actions.
10.2.1. Registration Procedure 10.2.1. Registration Procedure
skipping to change at page 70, line 40 skipping to change at page 70, line 40
and times", ISO Standard 8601, and times", ISO Standard 8601,
December 2000. December 2000.
[ISO.8601.2004] International Organization for [ISO.8601.2004] International Organization for
Standardization, "Data elements and Standardization, "Data elements and
interchange formats - Information interchange formats - Information
interchange - Representation of dates interchange - Representation of dates
and times", ISO Standard 8601, and times", ISO Standard 8601,
December 2004. December 2004.
[RFC1738] Berners-Lee, T., Masinter, L., and M.
McCahill, "Uniform Resource Locators
(URL)", RFC 1738, December 1994.
[RFC2045] Freed, N. and N. Borenstein, [RFC2045] Freed, N. and N. Borenstein,
"Multipurpose Internet Mail Extensions "Multipurpose Internet Mail Extensions
(MIME) Part One: Format of Internet (MIME) Part One: Format of Internet
Message Bodies", RFC 2045, Message Bodies", RFC 2045,
November 1996. November 1996.
[RFC2046] Freed, N. and N. Borenstein, [RFC2046] Freed, N. and N. Borenstein,
"Multipurpose Internet Mail Extensions "Multipurpose Internet Mail Extensions
(MIME) Part Two: Media Types", (MIME) Part Two: Media Types",
RFC 2046, November 1996. RFC 2046, November 1996.
skipping to change at page 71, line 31 skipping to change at page 71, line 27
[RFC3986] Berners-Lee, T., Fielding, R., and L. [RFC3986] Berners-Lee, T., Fielding, R., and L.
Masinter, "Uniform Resource Identifier Masinter, "Uniform Resource Identifier
(URI): Generic Syntax", STD 66, (URI): Generic Syntax", STD 66,
RFC 3986, January 2005. RFC 3986, January 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, [RFC4122] Leach, P., Mealling, M., and R. Salz,
"A Universally Unique IDentifier (UUID) "A Universally Unique IDentifier (UUID)
URN Namespace", RFC 4122, July 2005. URN Namespace", RFC 4122, July 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type
Specifications and Registration
Procedures", BCP 13, RFC 4288,
December 2005.
[RFC5234] Crocker, D. and P. Overell, "Augmented [RFC5234] Crocker, D. and P. Overell, "Augmented
BNF for Syntax Specifications: ABNF", BNF for Syntax Specifications: ABNF",
STD 68, RFC 5234, January 2008. STD 68, RFC 5234, January 2008.
[RFC5322] Resnick, P., Ed., "Internet Message [RFC5322] Resnick, P., Ed., "Internet Message
Format", RFC 5322, October 2008. Format", RFC 5322, October 2008.
[RFC5545] Desruisseaux, B., "Internet Calendaring [RFC5545] Desruisseaux, B., "Internet Calendaring
and Scheduling Core Object and Scheduling Core Object
Specification (iCalendar)", RFC 5545, Specification (iCalendar)", RFC 5545,
skipping to change at page 72, line 8 skipping to change at page 72, line 10
[RFC5646] Phillips, A. and M. Davis, "Tags for [RFC5646] Phillips, A. and M. Davis, "Tags for
Identifying Languages", BCP 47, Identifying Languages", BCP 47,
RFC 5646, September 2009. RFC 5646, September 2009.
[RFC5870] Mayrhofer, A. and C. Spanring, "A [RFC5870] Mayrhofer, A. and C. Spanring, "A
Uniform Resource Identifier for Uniform Resource Identifier for
Geographic Locations ('geo' URI)", Geographic Locations ('geo' URI)",
RFC 5870, June 2010. RFC 5870, June 2010.
[W3C.REC-xml-20081126] Yergeau, F., Maler, E., Paoli, J., [W3C.REC-xml-20081126] Bray, T., Yergeau, F., Maler, E.,
Sperberg-McQueen, C., and T. Bray, Paoli, J., and C. Sperberg-McQueen,
"Extensible Markup Language (XML) 1.0 "Extensible Markup Language (XML) 1.0
(Fifth Edition)", World Wide Web (Fifth Edition)", World Wide Web
Consortium Recommendation REC-xml- Consortium Recommendation REC-xml-
20081126, November 2008, <http:// 20081126, November 2008, <http://
www.w3.org/TR/2008/REC-xml-20081126>. www.w3.org/TR/2008/REC-xml-20081126>.
[xfn] Celik, T., Mullenweg, M., and E. Meyer, [xfn] Celik, T., Mullenweg, M., and E. Meyer,
"XHTML Friends Network 1.1", "XHTML Friends Network 1.1",
<http://gmpg.org/xfn/11>. <http://gmpg.org/xfn/11>.
skipping to change at page 72, line 33 skipping to change at page 72, line 35
"Internationalized Email Headers", "Internationalized Email Headers",
draft-ietf-eai-rfc5335bis-10 (work in draft-ietf-eai-rfc5335bis-10 (work in
progress), March 2011. 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.
[RFC1738] Berners-Lee, T., Masinter, L., and M.
McCahill, "Uniform Resource Locators
(URL)", RFC 1738, December 1994.
[RFC2397] Masinter, L., "The "data" URL scheme", [RFC2397] Masinter, L., "The "data" URL scheme",
RFC 2397, August 1998. RFC 2397, August 1998.
[RFC2425] Howes, T., Smith, M., and F. Dawson, "A [RFC2425] Howes, T., Smith, M., and F. Dawson, "A
MIME Content-Type for Directory MIME Content-Type for Directory
Information", RFC 2425, September 1998. Information", RFC 2425, September 1998.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME [RFC2426] Dawson, F. and T. Howes, "vCard MIME
Directory Profile", RFC 2426, Directory Profile", RFC 2426,
September 1998. September 1998.
skipping to change at page 75, line 15 skipping to change at page 75, line 21
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 -18 B.1. Changes in -19
o Fixed nits.
o Fixed MEDIATYPE ABNF.
B.2. Changes in -18
o Fix missing text in KIND section. o Fix missing text in KIND section.
B.2. Changes in -17 B.3. Changes in -17
o s/individual/entity/ o s/individual/entity/
o Moved section 3.4 for better flow. o Moved section 3.4 for better flow.
o Removed text overriding general MIME and HTTP rules. o Removed text overriding general MIME and HTTP rules.
o Fixed redundant ABNF. o Fixed redundant ABNF.
o Fixed parameter value quoting in examples. o Fixed parameter value quoting in examples.
skipping to change at page 76, line 13 skipping to change at page 76, line 24
o Removed underspecified "Status" column in IANA registry. o Removed underspecified "Status" column in IANA registry.
o Moved obsoleted references to Informative section. o Moved obsoleted references to Informative section.
o Moved iCalendar references to Normative section. o Moved iCalendar references to Normative section.
o Expanded specification of KIND values. o Expanded specification of KIND values.
o Recommend defining an XML representation for new vCard objects. o Recommend defining an XML representation for new vCard objects.
B.3. Changes in -16 B.4. 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.4. Changes in -15 B.5. Changes in -15
o Reverted N to the 5-component format of vCard 3. o Reverted N to the 5-component format of vCard 3.
o Removed DDAY, BIRTH, and DEATH. o Removed DDAY, BIRTH, and DEATH.
o First two components in ADR SHOULD be empty. o First two components in ADR SHOULD be empty.
o Removed the LABEL property. o Removed the LABEL property.
o Removed the binary value type and the ENCODING and FMTTYPE o Removed the binary value type and the ENCODING and FMTTYPE
skipping to change at page 77, line 15 skipping to change at page 77, line 25
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.5. Changes in -14 B.6. Changes in -14
o DQUOTE is US-ASCII decimal 34, not 22. o DQUOTE is US-ASCII decimal 34, not 22.
o Removed unused reference to RFC 2046. o Removed unused reference to RFC 2046.
o Updated reference to draft-ietf-vcarddav-vcardxml. o Updated reference to draft-ietf-vcarddav-vcardxml.
o Small fixes to the IANA registration text. o Small fixes to the IANA registration text.
o Added notes on the usage of TEL and IMPP properties. o Added notes on the usage of TEL and IMPP properties.
skipping to change at page 78, line 5 skipping to change at page 78, line 11
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.6. Changes in -13 B.7. 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.7. Changes in -12 B.8. Changes in -12
o Fixed example of LANGUAGE cardinality. o Fixed example of LANGUAGE cardinality.
o Added note about YYYY-MM date format. o Added note about YYYY-MM date format.
o Fixed appendix A. o Fixed appendix A.
o VERSION property must come first. o VERSION property must come first.
o Fixed mistake in PID example. o Fixed mistake in PID example.
skipping to change at page 79, line 26 skipping to change at page 79, line 32
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.8. Changes in -11 B.9. Changes in -11
o Change "XML chunk" to "XML fragment". o Change "XML chunk" to "XML fragment".
o Cite W3C document containing definition of "fragment". o Cite W3C document containing definition of "fragment".
o Added "XML" to property name ABNF. o Added "XML" to property name ABNF.
o Clarified newline escaping rule. o Clarified newline escaping rule.
o Replaced one remaining "type" with "property". o Replaced one remaining "type" with "property".
skipping to change at page 80, line 5 skipping to change at page 80, line 9
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.9. Changes in -10 B.10. 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.10. Changes in -09 B.11. 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.11. Changes in -08 B.12. Changes in -08
o Allow 1985 (year only) in date ABNF. o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example. o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value. o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME. o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to o Prefixed "param" and "value" production rules specific to
skipping to change at page 81, line 13 skipping to change at page 81, line 15
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.12. Changes in -07 B.13. Changes in -07
o PREF is now bounded. 100 is the maximum value. o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type. o Added the "emergency" RELATED type.
o Made GEO a URI. o Made GEO a URI.
o Added GEO and TZ parameters to ADR. o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property. o Changed wording of "default" use of SOUND property.
skipping to change at page 81, line 35 skipping to change at page 81, line 37
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.13. Changes in -06 B.14. Changes in -06
o Corrected omission of resetability to text value for RELATED. o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value. o Let KEY value type be reset to a URI value.
o ABNF fixes. o ABNF fixes.
o Made gender values extensible. o Made gender values extensible.
o Gave the PREF parameter a positive integer value. o Gave the PREF parameter a positive integer value.
skipping to change at page 82, line 26 skipping to change at page 82, line 28
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.14. Changes in -05 B.15. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.15. Changes in -04 B.16. Changes in -04
o Added "location" value for KIND property. o Added "location" value for KIND property.
o Some fixes to ABNF. o Some fixes to ABNF.
o Moved "pref" from being a TYPE value to a parameter in its own o Moved "pref" from being a TYPE value to a parameter in its own
right. right.
o Removed the "work" and "home" TYPE values. o Removed the "work" and "home" TYPE values.
skipping to change at page 83, line 13 skipping to change at page 83, line 15
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.16. Changes in -03 B.17. 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.17. Changes in -02 B.18. Changes in -02
o Removed useless text in IMPP description. o Removed useless text in IMPP description.
o Added CalDAV-SCHED example to CALADRURI. o Added CalDAV-SCHED example to CALADRURI.
o Removed CAPURI property. o Removed CAPURI property.
o Dashes in dates and colons in times are now mandatory. o Dashes in dates and colons in times are now mandatory.
o Allow for dates such as 2008 and 2008-05 and times such as 07 and o Allow for dates such as 2008 and 2008-05 and times such as 07 and
skipping to change at page 84, line 5 skipping to change at page 84, line 5
o Changed the presence of UID and PID when synchronization is to be o Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD. used from MUST to SHOULD.
o Added the RELATED (Section 6.6.6) property. o Added the RELATED (Section 6.6.6) property.
o Fixed many ABNF typos (issue #252). o Fixed many ABNF typos (issue #252).
o Changed formatting of ABNF comments to make them easier to read o Changed formatting of ABNF comments to make them easier to read
(issue #226). (issue #226).
B.18. Changes in -01 B.19. Changes in -01
o Merged [RFC2739] in. o Merged [RFC2739] in.
o Converted all foobar.com, abc.com, etc. to example.com. o Converted all foobar.com, abc.com, etc. to example.com.
o Fixed bugs in ABNF. o Fixed bugs in ABNF.
o Made explicit that coordinates in the GEO property are expressed o Made explicit that coordinates in the GEO property are expressed
in the WGS 84 reference system. in the WGS 84 reference system.
skipping to change at page 84, line 33 skipping to change at page 84, line 33
o Added Section 7. o Added Section 7.
o Created IANA process for registering new parameters, value types, o Created IANA process for registering new parameters, value types,
and properties. and properties.
o Created the initial IANA registries. o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288. o Created vendor namespace based on text from RFC 4288.
B.19. Changes in -00 B.20. Changes in -00
o Name change because draft has been accepted as WG item. o Name change because draft has been accepted as WG item.
Otherwise, same as draft-resnick-vcarddav-vcardrev-01. Otherwise, same as draft-resnick-vcarddav-vcardrev-01.
o Removed reference to RFC 2234. o Removed reference to RFC 2234.
o Fixed errata from o Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426. http://www.rfc-editor.org/errata_search.php?rfc=2426.
o Removed passage referring to RFC 2425 profiles. o Removed passage referring to RFC 2425 profiles.
 End of changes. 79 change blocks. 
119 lines changed or deleted 127 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/