source: trunk/Documents/RFC 6350 vCard Format Specification.html

Last change on this file was 41, checked in by chronos, 4 years ago
  • Added: Sample files.
  • Added: vCard standard document.
File size: 197.6 KB
RevLine 
[41]1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
3 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
4 <meta name="robots" content="index,follow">
5 <meta name="creator" content="rfcmarkup version 1.129b">
6 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
7 <meta name="DC.Identifier" content="urn:ietf:rfc:6350">
8 <meta name="DC.Relation.Replaces" content="RFC2425, RFC2426, RFC4770"><meta name="DC.Creator" content="S. Perreault"><meta name="DC.Date.Issued" content="August, 2011">
9 <meta name="DC.Title" content="vCard Format Specification">
10 <title>RFC 6350: vCard Format Specification</title>
11
12
13 <style type="text/css">
14 @media only screen
15 and (min-width: 992px)
16 and (max-width: 1199px) {
17 body { font-size: 14pt; }
18 div.content { width: 96ex; margin: 0 auto; }
19 }
20 @media only screen
21 and (min-width: 768px)
22 and (max-width: 991px) {
23 body { font-size: 14pt; }
24 div.content { width: 96ex; margin: 0 auto; }
25 }
26 @media only screen
27 and (min-width: 480px)
28 and (max-width: 767px) {
29 body { font-size: 11pt; }
30 div.content { width: 96ex; margin: 0 auto; }
31 }
32 @media only screen
33 and (max-width: 479px) {
34 body { font-size: 8pt; }
35 div.content { width: 96ex; margin: 0 auto; }
36 }
37 @media only screen
38 and (min-device-width : 375px)
39 and (max-device-width : 667px) {
40 body { font-size: 9.5pt; }
41 div.content { width: 96ex; margin: 0; }
42 }
43 @media only screen
44 and (min-device-width: 1200px) {
45 body { font-size: 10pt; margin: 0 4em; }
46 div.content { width: 96ex; margin: 0; }
47 }
48 h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {
49 font-weight: bold;
50 line-height: 0pt;
51 display: inline;
52 white-space: pre;
53 font-family: monospace;
54 font-size: 1em;
55 font-weight: bold;
56 }
57 pre {
58 font-size: 1em;
59 margin-top: 0px;
60 margin-bottom: 0px;
61 }
62 .pre {
63 white-space: pre;
64 font-family: monospace;
65 }
66 .header{
67 font-weight: bold;
68 }
69 .newpage {
70 page-break-before: always;
71 }
72 .invisible {
73 text-decoration: none;
74 color: white;
75 }
76 a.selflink {
77 color: black;
78 text-decoration: none;
79 }
80 @media print {
81 body {
82 font-family: monospace;
83 font-size: 10.5pt;
84 }
85 h1, h2, h3, h4, h5, h6 {
86 font-size: 1em;
87 }
88
89 a:link, a:visited {
90 color: inherit;
91 text-decoration: none;
92 }
93 .noprint {
94 display: none;
95 }
96 }
97 @media screen {
98 .grey, .grey a:link, .grey a:visited {
99 color: #777;
100 }
101 .docinfo {
102 background-color: #EEE;
103 }
104 .top {
105 border-top: 7px solid #EEE;
106 }
107 .bgwhite { background-color: white; }
108 .bgred { background-color: #F44; }
109 .bggrey { background-color: #666; }
110 .bgbrown { background-color: #840; }
111 .bgorange { background-color: #FA0; }
112 .bgyellow { background-color: #EE0; }
113 .bgmagenta{ background-color: #F4F; }
114 .bgblue { background-color: #66F; }
115 .bgcyan { background-color: #4DD; }
116 .bggreen { background-color: #4F4; }
117
118 .legend { font-size: 90%; }
119 .cplate { font-size: 70%; border: solid grey 1px; }
120 }
121 </style>
122 <!--[if IE]>
123 <style>
124 body {
125 font-size: 13px;
126 margin: 10px 10px;
127 }
128 </style>
129 <![endif]--> <script type="text/javascript"><!--
130 function addHeaderTags() {
131 var spans = document.getElementsByTagName("span");
132 for (var i=0; i < spans.length; i++) {
133 var elem = spans[i];
134 if (elem) {
135 var level = elem.getAttribute("class");
136 if (level == "h1" || level == "h2" || level == "h3" || level == "h4" || level == "h5" || level == "h6") {
137 elem.innerHTML = "<"+level+">"+elem.innerHTML+"</"+level+">";
138 }
139 }
140 }
141 }
142 var legend_html = "Colour legend:<br /> <table> <tr><td>Unknown:</td> <td><span class='cplate bgwhite'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Draft:</td> <td><span class='cplate bgred'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Informational:</td> <td><span class='cplate bgorange'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Experimental:</td> <td><span class='cplate bgyellow'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Best Common Practice:</td> <td><span class='cplate bgmagenta'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Proposed Standard:</td> <td><span class='cplate bgblue'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Draft Standard (old designation):</td> <td><span class='cplate bgcyan'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Internet Standard:</td> <td><span class='cplate bggreen'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Historic:</td> <td><span class='cplate bggrey'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Obsolete:</td> <td><span class='cplate bgbrown'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> </table>";
143 function showElem(id) {
144 var elem = document.getElementById(id);
145 elem.innerHTML = eval(id+"_html");
146 elem.style.visibility='visible';
147 }
148 function hideElem(id) {
149 var elem = document.getElementById(id);
150 elem.style.visibility='hidden';
151 elem.innerHTML = "";
152 }
153 // -->
154 </script></head><body><span class="pre noprint docinfo">[<a href="https://www.rfc-editor.org/" title="RFC Editor">RFC Home</a>] [<a href="https://www.rfc-editor.org/rfc/rfc6350.txt">TEXT</a>|<a href="https://www.rfc-editor.org/rfc/pdfrfc/rfc6350.txt.pdf">PDF</a>|<a href="https://www.rfc-editor.org/rfc/rfc6350.html">HTML</a>] [<a href="https://datatracker.ietf.org/doc/rfc6350" title="IETF Datatracker information for this document">Tracker</a>] [<a href="https://datatracker.ietf.org/ipr/search/?rfc=6350&amp;submit=rfc" title="IPR disclosures related to this document">IPR</a>] [<a class="boldtext" href="https://www.rfc-editor.org/errata/rfc6350" target="_blank">Errata</a>] [<a href="https://www.rfc-editor.org/info/rfc6350" title="Info page">Info page</a>] </span><br><span class="pre noprint docinfo"> </span><br><span class="pre noprint docinfo"> PROPOSED STANDARD</span><br><span class="pre noprint docinfo">Updated by: <a href="https://www.rfc-editor.org/rfc/rfc6868" target="_blank">6868</a> <span style="color: #C00;">Errata Exist</span></span><pre>Internet Engineering Task Force (IETF) S. Perreault
155Request for Comments: 6350 Viagenie
156Obsoletes: <a href="https://www.rfc-editor.org/rfc/rfc2425">2425</a>, <a href="https://www.rfc-editor.org/rfc/rfc2426">2426</a>, <a href="https://www.rfc-editor.org/rfc/rfc4770">4770</a> August 2011
157Updates: <a href="https://www.rfc-editor.org/rfc/rfc2739">2739</a>
158Category: Standards Track
159ISSN: 2070-1721
160
161
162 <span class="h1">vCard Format Specification</span>
163
164Abstract
165
166 This document defines the vCard data format for representing and
167 exchanging a variety of information about individuals and other
168 entities (e.g., formatted and structured name and delivery addresses,
169 email address, multiple telephone numbers, photograph, logo, audio
170 clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and
171 updates <a href="https://www.rfc-editor.org/rfc/rfc2739">RFC 2739</a>.
172
173Status of This Memo
174
175 This is an Internet Standards Track document.
176
177 This document is a product of the Internet Engineering Task Force
178 (IETF). It represents the consensus of the IETF community. It has
179 received public review and has been approved for publication by the
180 Internet Engineering Steering Group (IESG). Further information on
181 Internet Standards is available in <a href="https://www.rfc-editor.org/rfc/rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
182
183 Information about the current status of this document, any errata,
184 and how to provide feedback on it may be obtained at
185 <a href="http://www.rfc-editor.org/info/rfc6350">http://www.rfc-editor.org/info/rfc6350</a>.
186
187Copyright Notice
188
189 Copyright (c) 2011 IETF Trust and the persons identified as the
190 document authors. All rights reserved.
191
192 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
193 Provisions Relating to IETF Documents
194 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
195 publication of this document. Please review these documents
196 carefully, as they describe your rights and restrictions with respect
197 to this document. Code Components extracted from this document must
198 include Simplified BSD License text as described in Section 4.e of
199 the Trust Legal Provisions and are provided without warranty as
200 described in the Simplified BSD License.
201
202
203
204
205<span class="grey">Perreault Standards Track [Page 1]</span></pre>
206<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-2"></span>
207<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
208
209
210 This document may contain material from IETF Documents or IETF
211 Contributions published or made publicly available before November
212 10, 2008. The person(s) controlling the copyright in some of this
213 material may not have granted the IETF Trust the right to allow
214 modifications of such material outside the IETF Standards Process.
215 Without obtaining an adequate license from the person(s) controlling
216 the copyright in such materials, this document may not be modified
217 outside the IETF Standards Process, and derivative works of it may
218 not be created outside the IETF Standards Process, except to format
219 it for publication as an RFC or to translate it into languages other
220 than English.
221
222Table of Contents
223
224 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
225 <a href="#section-2">2</a>. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
226 <a href="#section-3">3</a>. vCard Format Specification . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
227 <a href="#section-3.1">3.1</a>. Charset . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
228 <a href="#section-3.2">3.2</a>. Line Delimiting and Folding . . . . . . . . . . . . . . . <a href="#page-5">5</a>
229 <a href="#section-3.3">3.3</a>. ABNF Format Definition . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
230 <a href="#section-3.4">3.4</a>. Property Value Escaping . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
231 <a href="#section-4">4</a>. Property Value Data Types . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
232 <a href="#section-4.1">4.1</a>. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
233 <a href="#section-4.2">4.2</a>. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
234 <a href="#section-4.3">4.3</a>. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . <a href="#page-12">12</a>
235 <a href="#section-4.3.1">4.3.1</a>. DATE . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
236 <a href="#section-4.3.2">4.3.2</a>. TIME . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
237 <a href="#section-4.3.3">4.3.3</a>. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
238 <a href="#section-4.3.4">4.3.4</a>. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
239 <a href="#section-4.3.5">4.3.5</a>. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
240 <a href="#section-4.4">4.4</a>. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
241 <a href="#section-4.5">4.5</a>. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
242 <a href="#section-4.6">4.6</a>. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
243 <a href="#section-4.7">4.7</a>. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
244 <a href="#section-4.8">4.8</a>. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
245 <a href="#section-5">5</a>. Property Parameters . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
246 <a href="#section-5.1">5.1</a>. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
247 <a href="#section-5.2">5.2</a>. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
248 <a href="#section-5.3">5.3</a>. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
249 <a href="#section-5.4">5.4</a>. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
250 <a href="#section-5.5">5.5</a>. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
251 <a href="#section-5.6">5.6</a>. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
252 <a href="#section-5.7">5.7</a>. MEDIATYPE . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
253 <a href="#section-5.8">5.8</a>. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
254 <a href="#section-5.9">5.9</a>. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
255 <a href="#section-5.10">5.10</a>. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
256 <a href="#section-5.11">5.11</a>. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
257
258
259
260
261<span class="grey">Perreault Standards Track [Page 2]</span></pre>
262<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-3"></span>
263<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
264
265
266 <a href="#section-6">6</a>. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
267 <a href="#section-6.1">6.1</a>. General Properties . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
268 <a href="#section-6.1.1">6.1.1</a>. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
269 <a href="#section-6.1.2">6.1.2</a>. END . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
270 <a href="#section-6.1.3">6.1.3</a>. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
271 <a href="#section-6.1.4">6.1.4</a>. KIND . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-25">25</a>
272 <a href="#section-6.1.5">6.1.5</a>. XML . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
273 <a href="#section-6.2">6.2</a>. Identification Properties . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
274 <a href="#section-6.2.1">6.2.1</a>. FN . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
275 <a href="#section-6.2.2">6.2.2</a>. N . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
276 <a href="#section-6.2.3">6.2.3</a>. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
277 <a href="#section-6.2.4">6.2.4</a>. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
278 <a href="#section-6.2.5">6.2.5</a>. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
279 <a href="#section-6.2.6">6.2.6</a>. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a>
280 <a href="#section-6.2.7">6.2.7</a>. GENDER . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a>
281 <a href="#section-6.3">6.3</a>. Delivery Addressing Properties . . . . . . . . . . . . . . <a href="#page-32">32</a>
282 <a href="#section-6.3.1">6.3.1</a>. ADR . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a>
283 <a href="#section-6.4">6.4</a>. Communications Properties . . . . . . . . . . . . . . . . <a href="#page-34">34</a>
284 <a href="#section-6.4.1">6.4.1</a>. TEL . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a>
285 <a href="#section-6.4.2">6.4.2</a>. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
286 <a href="#section-6.4.3">6.4.3</a>. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
287 <a href="#section-6.4.4">6.4.4</a>. LANG . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
288 <a href="#section-6.5">6.5</a>. Geographical Properties . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
289 <a href="#section-6.5.1">6.5.1</a>. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
290 <a href="#section-6.5.2">6.5.2</a>. GEO . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
291 <a href="#section-6.6">6.6</a>. Organizational Properties . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
292 <a href="#section-6.6.1">6.6.1</a>. TITLE . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
293 <a href="#section-6.6.2">6.6.2</a>. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
294 <a href="#section-6.6.3">6.6.3</a>. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
295 <a href="#section-6.6.4">6.6.4</a>. ORG . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
296 <a href="#section-6.6.5">6.6.5</a>. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
297 <a href="#section-6.6.6">6.6.6</a>. RELATED . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-42">42</a>
298 <a href="#section-6.7">6.7</a>. Explanatory Properties . . . . . . . . . . . . . . . . . . <a href="#page-43">43</a>
299 <a href="#section-6.7.1">6.7.1</a>. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . <a href="#page-43">43</a>
300 <a href="#section-6.7.2">6.7.2</a>. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-44">44</a>
301 <a href="#section-6.7.3">6.7.3</a>. PRODID . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-44">44</a>
302 <a href="#section-6.7.4">6.7.4</a>. REV . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-45">45</a>
303 <a href="#section-6.7.5">6.7.5</a>. SOUND . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-45">45</a>
304 <a href="#section-6.7.6">6.7.6</a>. UID . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a>
305 <a href="#section-6.7.7">6.7.7</a>. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a>
306 <a href="#section-6.7.8">6.7.8</a>. URL . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-47">47</a>
307 <a href="#section-6.7.9">6.7.9</a>. VERSION . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-48">48</a>
308 <a href="#section-6.8">6.8</a>. Security Properties . . . . . . . . . . . . . . . . . . . <a href="#page-48">48</a>
309 <a href="#section-6.8.1">6.8.1</a>. KEY . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-48">48</a>
310 <a href="#section-6.9">6.9</a>. Calendar Properties . . . . . . . . . . . . . . . . . . . <a href="#page-49">49</a>
311 <a href="#section-6.9.1">6.9.1</a>. FBURL . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-49">49</a>
312 <a href="#section-6.9.2">6.9.2</a>. CALADRURI . . . . . . . . . . . . . . . . . . . . . . <a href="#page-50">50</a>
313 <a href="#section-6.9.3">6.9.3</a>. CALURI . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-50">50</a>
314
315
316
317<span class="grey">Perreault Standards Track [Page 3]</span></pre>
318<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-4"></span>
319<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
320
321
322 <a href="#section-6.10">6.10</a>. Extended Properties and Parameters . . . . . . . . . . . . <a href="#page-51">51</a>
323 <a href="#section-7">7</a>. Synchronization . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-51">51</a>
324 <a href="#section-7.1">7.1</a>. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-51">51</a>
325 <a href="#section-7.1.1">7.1.1</a>. Matching vCard Instances . . . . . . . . . . . . . . . <a href="#page-51">51</a>
326 <a href="#section-7.1.2">7.1.2</a>. Matching Property Instances . . . . . . . . . . . . . <a href="#page-52">52</a>
327 <a href="#section-7.1.3">7.1.3</a>. PID Matching . . . . . . . . . . . . . . . . . . . . . <a href="#page-52">52</a>
328 <a href="#section-7.2">7.2</a>. Example . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-53">53</a>
329 <a href="#section-7.2.1">7.2.1</a>. Creation . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-53">53</a>
330 <a href="#section-7.2.2">7.2.2</a>. Initial Sharing . . . . . . . . . . . . . . . . . . . <a href="#page-53">53</a>
331 <a href="#section-7.2.3">7.2.3</a>. Adding and Sharing a Property . . . . . . . . . . . . <a href="#page-54">54</a>
332 <a href="#section-7.2.4">7.2.4</a>. Simultaneous Editing . . . . . . . . . . . . . . . . . <a href="#page-54">54</a>
333 <a href="#section-7.2.5">7.2.5</a>. Global Context Simplification . . . . . . . . . . . . <a href="#page-56">56</a>
334 <a href="#section-8">8</a>. Example: Author's vCard . . . . . . . . . . . . . . . . . . . <a href="#page-56">56</a>
335 <a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-57">57</a>
336 <a href="#section-10">10</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-58">58</a>
337 <a href="#section-10.1">10.1</a>. Media Type Registration . . . . . . . . . . . . . . . . . <a href="#page-58">58</a>
338 <a href="#section-10.2">10.2</a>. Registering New vCard Elements . . . . . . . . . . . . . . <a href="#page-59">59</a>
339 <a href="#section-10.2.1">10.2.1</a>. Registration Procedure . . . . . . . . . . . . . . . . <a href="#page-59">59</a>
340 <a href="#section-10.2.2">10.2.2</a>. Vendor Namespace . . . . . . . . . . . . . . . . . . . <a href="#page-60">60</a>
341 <a href="#section-10.2.3">10.2.3</a>. Registration Template for Properties . . . . . . . . . <a href="#page-61">61</a>
342 <a href="#section-10.2.4">10.2.4</a>. Registration Template for Parameters . . . . . . . . . <a href="#page-61">61</a>
343 <a href="#section-10.2.5">10.2.5</a>. Registration Template for Value Data Types . . . . . . <a href="#page-62">62</a>
344 <a href="#section-10.2.6">10.2.6</a>. Registration Template for Values . . . . . . . . . . . <a href="#page-62">62</a>
345 <a href="#section-10.3">10.3</a>. Initial vCard Elements Registries . . . . . . . . . . . . <a href="#page-63">63</a>
346 <a href="#section-10.3.1">10.3.1</a>. Properties Registry . . . . . . . . . . . . . . . . . <a href="#page-64">64</a>
347 <a href="#section-10.3.2">10.3.2</a>. Parameters Registry . . . . . . . . . . . . . . . . . <a href="#page-65">65</a>
348 <a href="#section-10.3.3">10.3.3</a>. Value Data Types Registry . . . . . . . . . . . . . . <a href="#page-65">65</a>
349 <a href="#section-10.3.4">10.3.4</a>. Values Registries . . . . . . . . . . . . . . . . . . <a href="#page-66">66</a>
350 <a href="#section-11">11</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-69">69</a>
351 <a href="#section-12">12</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-69">69</a>
352 <a href="#section-12.1">12.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-69">69</a>
353 <a href="#section-12.2">12.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-71">71</a>
354 <a href="#appendix-A">Appendix A</a>. Differences from RFCs 2425 and 2426 . . . . . . . . . <a href="#page-73">73</a>
355 <a href="#appendix-A.1">A.1</a>. New Structure . . . . . . . . . . . . . . . . . . . . . . <a href="#page-73">73</a>
356 <a href="#appendix-A.2">A.2</a>. Removed Features . . . . . . . . . . . . . . . . . . . . . <a href="#page-73">73</a>
357 <a href="#appendix-A.3">A.3</a>. New Properties and Parameters . . . . . . . . . . . . . . <a href="#page-73">73</a>
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373<span class="grey">Perreault Standards Track [Page 4]</span></pre>
374<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-5"></span>
375<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
376
377
378<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
379
380 Electronic address books have become ubiquitous. Their increased
381 presence on portable, connected devices as well as the diversity of
382 platforms that exchange contact data call for a standard. This memo
383 defines the vCard format, which allows the capture and exchange of
384 information normally stored within an address book or directory
385 application.
386
387 A high-level overview of the differences from RFCs 2425 and 2426 can
388 be found in <a href="#appendix-A">Appendix A</a>.
389
390<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions</span>
391
392 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
393 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
394 "OPTIONAL" in this document are to be interpreted as described in
395 [<a href="https://www.rfc-editor.org/rfc/rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
396
397<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. vCard Format Specification</span>
398
399 The text/vcard MIME content type (hereafter known as "vCard"; see
400 <a href="#section-10.1">Section 10.1</a>) contains contact information, typically pertaining to a
401 single contact or group of contacts. The content consists of one or
402 more lines in the format given below.
403
404<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Charset</span>
405
406 The charset (see [<a href="https://www.rfc-editor.org/rfc/rfc3536" title="&quot;Terminology Used in Internationalization in the IETF&quot;">RFC3536</a>] for internationalization terminology) for
407 vCard is UTF-8 as defined in [<a href="https://www.rfc-editor.org/rfc/rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>]. There is no way to override
408 this. It is invalid to specify a value other than "UTF-8" in the
409 "charset" MIME parameter (see <a href="#section-10.1">Section 10.1</a>).
410
411<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Line Delimiting and Folding</span>
412
413 Individual lines within vCard are delimited by the [<a href="https://www.rfc-editor.org/rfc/rfc5322" title="&quot;Internet Message Format&quot;">RFC5322</a>] line
414 break, which is a CRLF sequence (U+000D followed by U+000A). Long
415 logical lines of text can be split into a multiple-physical-line
416 representation using the following folding technique. Content lines
417 SHOULD be folded to a maximum width of 75 octets, excluding the line
418 break. Multi-octet characters MUST remain contiguous. The rationale
419 for this folding process can be found in <a href="https://www.rfc-editor.org/rfc/rfc5322#section-2.1.1">[RFC5322], Section&nbsp;2.1.1</a>.
420
421 A logical line MAY be continued on the next physical line anywhere
422 between two characters by inserting a CRLF immediately followed by a
423 single white space character (space (U+0020) or horizontal tab
424 (U+0009)). The folded line MUST contain at least one character. Any
425 sequence of CRLF followed immediately by a single white space
426
427
428
429<span class="grey">Perreault Standards Track [Page 5]</span></pre>
430<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-6"></span>
431<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
432
433
434 character is ignored (removed) when processing the content type. For
435 example, the line:
436
437 NOTE:This is a long description that exists on a long line.
438
439 can be represented as:
440
441 NOTE:This is a long description
442 that exists on a long line.
443
444 It could also be represented as:
445
446 NOTE:This is a long descrip
447 tion that exists o
448 n a long line.
449
450 The process of moving from this folded multiple-line representation
451 of a property definition to its single-line representation is called
452 unfolding. Unfolding is accomplished by regarding CRLF immediately
453 followed by a white space character (namely, HTAB (U+0009) or SPACE
454 (U+0020)) as equivalent to no characters at all (i.e., the CRLF and
455 single white space character are removed).
456
457 Note: It is possible for very simple implementations to generate
458 improperly folded lines in the middle of a UTF-8 multi-octet
459 sequence. For this reason, implementations SHOULD unfold lines in
460 such a way as to properly restore the original sequence.
461
462 Note: Unfolding is done differently than in [<a href="https://www.rfc-editor.org/rfc/rfc5322" title="&quot;Internet Message Format&quot;">RFC5322</a>]. Unfolding
463 in [<a href="https://www.rfc-editor.org/rfc/rfc5322" title="&quot;Internet Message Format&quot;">RFC5322</a>] only removes the CRLF, not the space following it.
464
465 Folding is done after any content encoding of a type value.
466 Unfolding is done before any decoding of a type value in a content
467 line.
468
469<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. ABNF Format Definition</span>
470
471 The following ABNF uses the notation of [<a href="https://www.rfc-editor.org/rfc/rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>], which also defines
472 CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.
473
474 vcard-entity = 1*vcard
475
476 vcard = "BEGIN:VCARD" CRLF
477 "VERSION:4.0" CRLF
478 1*contentline
479 "END:VCARD" CRLF
480 ; A vCard object MUST include the VERSION and FN properties.
481 ; VERSION MUST come immediately after BEGIN:VCARD.
482
483
484
485<span class="grey">Perreault Standards Track [Page 6]</span></pre>
486<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-7"></span>
487<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
488
489
490 contentline = [group "."] name *(";" param) ":" value CRLF
491 ; When parsing a content line, folded lines must first
492 ; be unfolded according to the unfolding procedure
493 ; described in <a href="#section-3.2">Section 3.2</a>.
494 ; When generating a content line, lines longer than 75
495 ; characters SHOULD be folded according to the folding
496 ; procedure described in <a href="#section-3.2">Section 3.2</a>.
497
498 group = 1*(ALPHA / DIGIT / "-")
499 name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
500 / "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
501 / "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
502 / "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
503 / "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
504 / "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
505 / iana-token / x-name
506 ; Parsing of the param and value is based on the "name" as
507 ; defined in ABNF sections below.
508 ; Group and name are case-insensitive.
509
510 iana-token = 1*(ALPHA / DIGIT / "-")
511 ; identifier registered with IANA
512
513 x-name = "x-" 1*(ALPHA / DIGIT / "-")
514 ; Names that begin with "x-" or "X-" are
515 ; reserved for experimental use, not intended for released
516 ; products, or for use in bilateral agreements.
517
518 param = language-param / value-param / pref-param / pid-param
519 / type-param / geo-parameter / tz-parameter / sort-as-param
520 / calscale-param / any-param
521 ; Allowed parameters depend on property name.
522
523 param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
524
525 any-param = (iana-token / x-name) "=" param-value *("," param-value)
526
527 NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
528 ; UTF8-{2,3,4} are defined in [<a href="https://www.rfc-editor.org/rfc/rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>]
529
530 QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
531 ; Any character except CTLs, DQUOTE
532
533 SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
534 ; Any character except CTLs, DQUOTE, ";", ":"
535
536 VALUE-CHAR = WSP / VCHAR / NON-ASCII
537 ; Any textual character
538
539
540
541<span class="grey">Perreault Standards Track [Page 7]</span></pre>
542<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-8"></span>
543<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
544
545
546 A line that begins with a white space character is a continuation of
547 the previous line, as described in <a href="#section-3.2">Section 3.2</a>. The white space
548 character and immediately preceeding CRLF should be discarded when
549 reconstructing the original line. Note that this line-folding
550 convention differs from that found in [<a href="https://www.rfc-editor.org/rfc/rfc5322" title="&quot;Internet Message Format&quot;">RFC5322</a>], in that the sequence
551 &lt;CRLF&gt;&lt;WSP&gt; found anywhere in the content indicates a continued line
552 and should be removed.
553
554 Property names and parameter names are case-insensitive (e.g., the
555 property name "fn" is the same as "FN" and "Fn"). Parameter values
556 MAY be case-sensitive or case-insensitive, depending on their
557 definition. Parameter values that are not explicitly defined as
558 being case-sensitive are case-insensitive. Based on experience with
559 vCard 3 interoperability, it is RECOMMENDED that property and
560 parameter names be upper-case on output.
561
562 The group construct is used to group related properties together.
563 The group name is a syntactic convention used to indicate that all
564 property names prefaced with the same group name SHOULD be grouped
565 together when displayed by an application. It has no other
566 significance. Implementations that do not understand or support
567 grouping MAY simply strip off any text before a "." to the left of
568 the type name and present the types and values as normal.
569
570 Property cardinalities are indicated using the following notation,
571 which is based on ABNF (see <a href="https://www.rfc-editor.org/rfc/rfc5234#section-3.6">[RFC5234], Section&nbsp;3.6</a>):
572
573 +-------------+--------------------------------------------------+
574 | Cardinality | Meaning |
575 +-------------+--------------------------------------------------+
576 | 1 | Exactly one instance per vCard MUST be present. |
577 | *1 | Exactly one instance per vCard MAY be present. |
578 | 1* | One or more instances per vCard MUST be present. |
579 | * | One or more instances per vCard MAY be present. |
580 +-------------+--------------------------------------------------+
581
582 Properties defined in a vCard instance may have multiple values
583 depending on the property cardinality. The general rule for encoding
584 multi-valued properties is to simply create a new content line for
585 each value (including the property name). However, it should be
586 noted that some value types support encoding multiple values in a
587 single content line by separating the values with a comma ",". This
588 approach has been taken for several of the content types defined
589 below (date, time, integer, float).
590
591
592
593
594
595
596
597<span class="grey">Perreault Standards Track [Page 8]</span></pre>
598<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-9"></span>
599<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
600
601
602<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Property Value Escaping</span>
603
604 Some properties may contain one or more values delimited by a COMMA
605 character (U+002C). Therefore, a COMMA character in a value MUST be
606 escaped with a BACKSLASH character (U+005C), even for properties that
607 don't allow multiple instances (for consistency).
608
609 Some properties (e.g., N and ADR) comprise multiple fields delimited
610 by a SEMICOLON character (U+003B). Therefore, a SEMICOLON in a field
611 of such a "compound" property MUST be escaped with a BACKSLASH
612 character. SEMICOLON characters in non-compound properties MAY be
613 escaped. On input, an escaped SEMICOLON character is never a field
614 separator. An unescaped SEMICOLON character may be a field
615 separator, depending on the property in which it appears.
616
617 Furthermore, some fields of compound properties may contain a list of
618 values delimited by a COMMA character. Therefore, a COMMA character
619 in one of a field's values MUST be escaped with a BACKSLASH
620 character, even for fields that don't allow multiple values (for
621 consistency). Compound properties allowing multiple instances MUST
622 NOT be encoded in a single content line.
623
624 Finally, BACKSLASH characters in values MUST be escaped with a
625 BACKSLASH character. NEWLINE (U+000A) characters in values MUST be
626 encoded by two characters: a BACKSLASH followed by either an 'n'
627 (U+006E) or an 'N' (U+004E).
628
629 In all other cases, escaping MUST NOT be used.
630
631<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Property Value Data Types</span>
632
633 Standard value types are defined below.
634
635 value = text
636 / text-list
637 / date-list
638 / time-list
639 / date-time-list
640 / date-and-or-time-list
641 / timestamp-list
642 / boolean
643 / integer-list
644 / float-list
645 / URI ; from <a href="https://www.rfc-editor.org/rfc/rfc3986#section-3">Section&nbsp;3 of [RFC3986]</a>
646 / utc-offset
647 / Language-Tag
648 / iana-valuespec
649 ; Actual value type depends on property name and VALUE parameter.
650
651
652
653<span class="grey">Perreault Standards Track [Page 9]</span></pre>
654<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-10"></span>
655<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
656
657
658 text = *TEXT-CHAR
659
660 TEXT-CHAR = "\\" / "\," / "\n" / WSP / NON-ASCII
661 / %x21-2B / %x2D-5B / %x5D-7E
662 ; Backslashes, commas, and newlines must be encoded.
663
664 component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
665 / %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
666 list-component = component *("," component)
667
668 text-list = text *("," text)
669 date-list = date *("," date)
670 time-list = time *("," time)
671 date-time-list = date-time *("," date-time)
672 date-and-or-time-list = date-and-or-time *("," date-and-or-time)
673 timestamp-list = timestamp *("," timestamp)
674 integer-list = integer *("," integer)
675 float-list = float *("," float)
676
677 boolean = "TRUE" / "FALSE"
678 integer = [sign] 1*DIGIT
679 float = [sign] 1*DIGIT ["." 1*DIGIT]
680
681 sign = "+" / "-"
682
683 year = 4DIGIT ; 0000-9999
684 month = 2DIGIT ; 01-12
685 day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
686 hour = 2DIGIT ; 00-23
687 minute = 2DIGIT ; 00-59
688 second = 2DIGIT ; 00-58/59/60 depending on leap second
689 zone = utc-designator / utc-offset
690 utc-designator = %x5A ; uppercase "Z"
691
692 date = year [month day]
693 / year "-" month
694 / "--" month [day]
695 / "--" "-" day
696 date-noreduc = year month day
697 / "--" month day
698 / "--" "-" day
699 date-complete = year month day
700
701 time = hour [minute [second]] [zone]
702 / "-" minute [second] [zone]
703 / "-" "-" second [zone]
704 time-notrunc = hour [minute [second]] [zone]
705 time-complete = hour minute second [zone]
706
707
708
709<span class="grey">Perreault Standards Track [Page 10]</span></pre>
710<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-11"></span>
711<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
712
713
714 time-designator = %x54 ; uppercase "T"
715 date-time = date-noreduc time-designator time-notrunc
716 timestamp = date-complete time-designator time-complete
717
718 date-and-or-time = date-time / date / time-designator time
719
720 utc-offset = sign hour [minute]
721
722 Language-Tag = &lt;Language-Tag, defined in <a href="https://www.rfc-editor.org/rfc/rfc5646#section-2.1">[RFC5646], Section&nbsp;2.1</a>&gt;
723
724 iana-valuespec = &lt;value-spec, see <a href="#section-12">Section 12</a>&gt;
725 ; a publicly defined valuetype format, registered
726 ; with IANA, as defined in <a href="#section-12">Section 12</a> of this
727 ; document.
728
729<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. TEXT</span>
730
731 "text": The "text" value type should be used to identify values that
732 contain human-readable text. As for the language, it is controlled
733 by the LANGUAGE property parameter defined in <a href="#section-5.1">Section 5.1</a>.
734
735 Examples for "text":
736
737 this is a text value
738 this is one value,this is another
739 this is a single value\, with a comma encoded
740
741 A formatted text line break in a text value type MUST be represented
742 as the character sequence backslash (U+005C) followed by a Latin
743 small letter n (U+006E) or a Latin capital letter N (U+004E), that
744 is, "\n" or "\N".
745
746 For example, a multiple line NOTE value of:
747
748 Mythical Manager
749 Hyjinx Software Division
750 BabsCo, Inc.
751
752 could be represented as:
753
754 NOTE:Mythical Manager\nHyjinx Software Division\n
755 BabsCo\, Inc.\n
756
757 demonstrating the \n literal formatted line break technique, the
758 CRLF-followed-by-space line folding technique, and the backslash
759 escape technique.
760
761
762
763
764
765<span class="grey">Perreault Standards Track [Page 11]</span></pre>
766<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-12"></span>
767<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
768
769
770<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. URI</span>
771
772 "uri": The "uri" value type should be used to identify values that
773 are referenced by a Uniform Resource Identifier (URI) instead of
774 encoded in-line. These value references might be used if the value
775 is too large, or otherwise undesirable to include directly. The
776 format for the URI is as defined in <a href="https://www.rfc-editor.org/rfc/rfc3986#section-3">Section&nbsp;3 of [RFC3986]</a>. Note
777 that the value of a property of type "uri" is what the URI points to,
778 not the URI itself.
779
780 Examples for "uri":
781
782 http://www.example.com/my/picture.jpg
783 ldap://ldap.example.com/cn=babs%20jensen
784
785<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP</span>
786
787 "date", "time", "date-time", "date-and-or-time", and "timestamp":
788 Each of these value types is based on the definitions in
789 [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>]. Multiple such values can be specified using the
790 comma-separated notation.
791
792 Only the basic format is supported.
793
794<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. DATE</span>
795
796 A calendar date as specified in [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], Section 4.1.2.
797
798 Reduced accuracy, as specified in [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], Sections <a href="#section-4.1.2.3">4.1.2.3</a>
799 a) and b), but not c), is permitted.
800
801 Expanded representation, as specified in [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], <a href="#section-4.1.4">Section</a>
802 <a href="#section-4.1.4">4.1.4</a>, is forbidden.
803
804 Truncated representation, as specified in [<a href="#ref-ISO.8601.2000">ISO.8601.2000</a>], Sections
805 5.2.1.3 d), e), and f), is permitted.
806
807 Examples for "date":
808
809 19850412
810 1985-04
811 1985
812 --0412
813 ---12
814
815
816
817
818
819
820
821<span class="grey">Perreault Standards Track [Page 12]</span></pre>
822<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-13"></span>
823<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
824
825
826 Note the use of YYYY-MM in the second example above. YYYYMM is
827 disallowed to prevent confusion with YYMMDD. Note also that
828 YYYY-MM-DD is disallowed since we are using the basic format instead
829 of the extended format.
830
831<span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>. TIME</span>
832
833 A time of day as specified in [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], Section 4.2.
834
835 Reduced accuracy, as specified in [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], Section 4.2.2.3,
836 is permitted.
837
838 Representation with decimal fraction, as specified in
839 [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], Section 4.2.2.4, is forbidden.
840
841 The midnight hour is always represented by 00, never 24 (see
842 [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], Section 4.2.3).
843
844 Truncated representation, as specified in [<a href="#ref-ISO.8601.2000">ISO.8601.2000</a>], Sections
845 5.3.1.4 a), b), and c), is permitted.
846
847 Examples for "time":
848
849 102200
850 1022
851 10
852 -2200
853 --00
854 102200Z
855 102200-0800
856
857<span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>. DATE-TIME</span>
858
859 A date and time of day combination as specified in [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>],
860 Section 4.3.
861
862 Truncation of the date part, as specified in [<a href="#ref-ISO.8601.2000">ISO.8601.2000</a>], <a href="#section-5.4.2">Section</a>
863 <a href="#section-5.4.2">5.4.2</a> c), is permitted.
864
865 Examples for "date-time":
866
867 19961022T140000
868 --1022T1400
869 ---22T14
870
871
872
873
874
875
876
877<span class="grey">Perreault Standards Track [Page 13]</span></pre>
878<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-14"></span>
879<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
880
881
882<span class="h4"><a class="selflink" id="section-4.3.4" href="#section-4.3.4">4.3.4</a>. DATE-AND-OR-TIME</span>
883
884 Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous
885 interpretation, a stand-alone TIME value is always preceded by a "T".
886
887 Examples for "date-and-or-time":
888
889 19961022T140000
890 --1022T1400
891 ---22T14
892 19850412
893 1985-04
894 1985
895 --0412
896 ---12
897 T102200
898 T1022
899 T10
900 T-2200
901 T--00
902 T102200Z
903 T102200-0800
904
905<span class="h4"><a class="selflink" id="section-4.3.5" href="#section-4.3.5">4.3.5</a>. TIMESTAMP</span>
906
907 A complete date and time of day combination as specified in
908 [<a href="#ref-ISO.8601.2004">ISO.8601.2004</a>], Section 4.3.2.
909
910 Examples for "timestamp":
911
912 19961022T140000
913 19961022T140000Z
914 19961022T140000-05
915 19961022T140000-0500
916
917<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. BOOLEAN</span>
918
919 "boolean": The "boolean" value type is used to express boolean
920 values. These values are case-insensitive.
921
922 Examples:
923
924 TRUE
925 false
926 True
927
928
929
930
931
932
933<span class="grey">Perreault Standards Track [Page 14]</span></pre>
934<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-15"></span>
935<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
936
937
938<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. INTEGER</span>
939
940 "integer": The "integer" value type is used to express signed
941 integers in decimal format. If sign is not specified, the value is
942 assumed positive "+". Multiple "integer" values can be specified
943 using the comma-separated notation. The maximum value is
944 9223372036854775807, and the minimum value is -9223372036854775808.
945 These limits correspond to a signed 64-bit integer using two's-
946 complement arithmetic.
947
948 Examples:
949
950 1234567890
951 -1234556790
952 +1234556790,432109876
953
954<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. FLOAT</span>
955
956 "float": The "float" value type is used to express real numbers. If
957 sign is not specified, the value is assumed positive "+". Multiple
958 "float" values can be specified using the comma-separated notation.
959 Implementations MUST support a precision equal or better than that of
960 the IEEE "binary64" format [<a href="#ref-IEEE.754.2008">IEEE.754.2008</a>].
961
962 Note: Scientific notation is disallowed. Implementers wishing to
963 use their favorite language's %f formatting should be careful.
964
965 Examples:
966
967 20.30
968 1000000.0000001
969 1.333,3.14
970
971<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. UTC-OFFSET</span>
972
973 "utc-offset": The "utc-offset" value type specifies that the property
974 value is a signed offset from UTC. This value type can be specified
975 in the TZ property.
976
977 The value type is an offset from Coordinated Universal Time (UTC).
978 It is specified as a positive or negative difference in units of
979 hours and minutes (e.g., +hhmm). The time is specified as a 24-hour
980 clock. Hour values are from 00 to 23, and minute values are from 00
981 to 59. Hour and minutes are 2 digits with high-order zeroes required
982 to maintain digit count. The basic format for ISO 8601 UTC offsets
983 MUST be used.
984
985
986
987
988
989<span class="grey">Perreault Standards Track [Page 15]</span></pre>
990<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-16"></span>
991<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
992
993
994<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. LANGUAGE-TAG</span>
995
996 "language-tag": A single language tag, as defined in [<a href="https://www.rfc-editor.org/rfc/rfc5646" title="&quot;Tags for Identifying Languages&quot;">RFC5646</a>].
997
998<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Property Parameters</span>
999
1000 A property can have attributes associated with it. These "property
1001 parameters" contain meta-information about the property or the
1002 property value. In some cases, the property parameter can be multi-
1003 valued in which case the property parameter value elements are
1004 separated by a COMMA (U+002C).
1005
1006 Property parameter value elements that contain the COLON (U+003A),
1007 SEMICOLON (U+003B), or COMMA (U+002C) character separators MUST be
1008 specified as quoted-string text values. Property parameter values
1009 MUST NOT contain the DQUOTE (U+0022) character. The DQUOTE character
1010 is used as a delimiter for parameter values that contain restricted
1011 characters or URI text.
1012
1013 Applications MUST ignore x-param and iana-param values they don't
1014 recognize.
1015
1016<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. LANGUAGE</span>
1017
1018 The LANGUAGE property parameter is used to identify data in multiple
1019 languages. There is no concept of "default" language, except as
1020 specified by any "Content-Language" MIME header parameter that is
1021 present [<a href="https://www.rfc-editor.org/rfc/rfc3282" title="&quot;Content Language Headers&quot;">RFC3282</a>]. The value of the LANGUAGE property parameter is a
1022 language tag as defined in <a href="https://www.rfc-editor.org/rfc/rfc5646#section-2">Section&nbsp;2 of [RFC5646]</a>.
1023
1024 Examples:
1025
1026 ROLE;LANGUAGE=tr:hoca
1027
1028 ABNF:
1029
1030 language-param = "LANGUAGE=" Language-Tag
1031 ; Language-Tag is defined in <a href="https://www.rfc-editor.org/rfc/rfc5646#section-2.1">section&nbsp;2.1 of RFC 5646</a>
1032
1033<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. VALUE</span>
1034
1035 The VALUE parameter is OPTIONAL, used to identify the value type
1036 (data type) and format of the value. The use of these predefined
1037 formats is encouraged even if the value parameter is not explicitly
1038 used. By defining a standard set of value types and their formats,
1039 existing parsing and processing code can be leveraged. The
1040
1041
1042
1043
1044
1045<span class="grey">Perreault Standards Track [Page 16]</span></pre>
1046<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-17"></span>
1047<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1048
1049
1050 predefined data type values MUST NOT be repeated in COMMA-separated
1051 value lists except within the N, NICKNAME, ADR, and CATEGORIES
1052 properties.
1053
1054 ABNF:
1055
1056 value-param = "VALUE=" value-type
1057
1058 value-type = "text"
1059 / "uri"
1060 / "date"
1061 / "time"
1062 / "date-time"
1063 / "date-and-or-time"
1064 / "timestamp"
1065 / "boolean"
1066 / "integer"
1067 / "float"
1068 / "utc-offset"
1069 / "language-tag"
1070 / iana-token ; registered as described in <a href="#section-12">section 12</a>
1071 / x-name
1072
1073<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. PREF</span>
1074
1075 The PREF parameter is OPTIONAL and is used to indicate that the
1076 corresponding instance of a property is preferred by the vCard
1077 author. Its value MUST be an integer between 1 and 100 that
1078 quantifies the level of preference. Lower values correspond to a
1079 higher level of preference, with 1 being most preferred.
1080
1081 When the parameter is absent, the default MUST be to interpret the
1082 property instance as being least preferred.
1083
1084 Note that the value of this parameter is to be interpreted only in
1085 relation to values assigned to other instances of the same property
1086 in the same vCard. A given value, or the absence of a value, MUST
1087 NOT be interpreted on its own.
1088
1089 This parameter MAY be applied to any property that allows multiple
1090 instances.
1091
1092 ABNF:
1093
1094 pref-param = "PREF=" (1*2DIGIT / "100")
1095 ; An integer between 1 and 100.
1096
1097
1098
1099
1100
1101<span class="grey">Perreault Standards Track [Page 17]</span></pre>
1102<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-18"></span>
1103<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1104
1105
1106<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. ALTID</span>
1107
1108 The ALTID parameter is used to "tag" property instances as being
1109 alternative representations of the same logical property. For
1110 example, translations of a property in multiple languages generates
1111 multiple property instances having different LANGUAGE (<a href="#section-5.1">Section 5.1</a>)
1112 parameter that are tagged with the same ALTID value.
1113
1114 This parameter's value is treated as an opaque string. Its sole
1115 purpose is to be compared for equality against other ALTID parameter
1116 values.
1117
1118 Two property instances are considered alternative representations of
1119 the same logical property if and only if their names as well as the
1120 value of their ALTID parameters are identical. Property instances
1121 without the ALTID parameter MUST NOT be considered an alternative
1122 representation of any other property instance. Values for the ALTID
1123 parameter are not globally unique: they MAY be reused for different
1124 property names.
1125
1126 Property instances having the same ALTID parameter value count as 1
1127 toward cardinality. Therefore, since N (<a href="#section-6.2.2">Section 6.2.2</a>) has
1128 cardinality *1 and TITLE (<a href="#section-6.6.1">Section 6.6.1</a>) has cardinality *, these
1129 three examples would be legal:
1130
1131 N;ALTID=1;LANGUAGE=jp:&lt;U+5C71&gt;&lt;U+7530&gt;;&lt;U+592A&gt;&lt;U+90CE&gt;;;;
1132 N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
1133 (&lt;U+XXXX&gt; denotes a UTF8-encoded Unicode character.)
1134
1135 TITLE;ALTID=1;LANGUAGE=fr:Patron
1136 TITLE;ALTID=1;LANGUAGE=en:Boss
1137
1138 TITLE;ALTID=1;LANGUAGE=fr:Patron
1139 TITLE;ALTID=1;LANGUAGE=en:Boss
1140 TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
1141
1142 while this one would not:
1143
1144 N;ALTID=1;LANGUAGE=jp:&lt;U+5C71&gt;&lt;U+7530&gt;;&lt;U+592A&gt;&lt;U+90CE&gt;;;;
1145 N:Yamada;Taro;;;
1146 (Two instances of the N property.)
1147
1148 and these three would be legal but questionable:
1149
1150 TITLE;ALTID=1;LANGUAGE=fr:Patron
1151 TITLE;ALTID=2;LANGUAGE=en:Boss
1152 (Should probably have the same ALTID value.)
1153
1154
1155
1156
1157<span class="grey">Perreault Standards Track [Page 18]</span></pre>
1158<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-19"></span>
1159<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1160
1161
1162 TITLE;ALTID=1;LANGUAGE=fr:Patron
1163 TITLE:LANGUAGE=en:Boss
1164 (Second line should probably have ALTID=1.)
1165
1166 N;ALTID=1;LANGUAGE=jp:&lt;U+5C71&gt;&lt;U+7530&gt;;&lt;U+592A&gt;&lt;U+90CE&gt;;;;
1167 N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
1168 N;ALTID=1;LANGUAGE=en:Smith;John;;;
1169 (The last line should probably have ALTID=2. But that would be
1170 illegal because N has cardinality *1.)
1171
1172 The ALTID property MAY also be used in may contexts other than with
1173 the LANGUAGE parameter. Here's an example with two representations
1174 of the same photo in different file formats:
1175
1176 PHOTO;ALTID=1:data:image/jpeg;base64,...
1177 PHOTO;ALTID=1;data:image/jp2;base64,...
1178
1179 ABNF:
1180
1181 altid-param = "ALTID=" param-value
1182
1183<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. PID</span>
1184
1185 The PID parameter is used to identify a specific property among
1186 multiple instances. It plays a role analogous to the UID property
1187 (<a href="#section-6.7.6">Section 6.7.6</a>) on a per-property instead of per-vCard basis. It MAY
1188 appear more than once in a given property. It MUST NOT appear on
1189 properties that may have only one instance per vCard. Its value is
1190 either a single small positive integer or a pair of small positive
1191 integers separated by a dot. Multiple values may be encoded in a
1192 single PID parameter by separating the values with a comma ",". See
1193 <a href="#section-7">Section 7</a> for more details on its usage.
1194
1195 ABNF:
1196
1197 pid-param = "PID=" pid-value *("," pid-value)
1198 pid-value = 1*DIGIT ["." 1*DIGIT]
1199
1200<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. TYPE</span>
1201
1202 The TYPE parameter has multiple, different uses. In general, it is a
1203 way of specifying class characteristics of the associated property.
1204 Most of the time, its value is a comma-separated subset of a
1205 predefined enumeration. In this document, the following properties
1206 make use of this parameter: FN, NICKNAME, PHOTO, ADR, TEL, EMAIL,
1207 IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES,
1208
1209
1210
1211
1212
1213<span class="grey">Perreault Standards Track [Page 19]</span></pre>
1214<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-20"></span>
1215<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1216
1217
1218 NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI. The TYPE
1219 parameter MUST NOT be applied on other properties defined in this
1220 document.
1221
1222 The "work" and "home" values act like tags. The "work" value implies
1223 that the property is related to an individual's work place, while the
1224 "home" value implies that the property is related to an individual's
1225 personal life. When neither "work" nor "home" is present, it is
1226 implied that the property is related to both an individual's work
1227 place and personal life in the case that the KIND property's value is
1228 "individual", or to none in other cases.
1229
1230 ABNF:
1231
1232 type-param = "TYPE=" type-value *("," type-value)
1233
1234 type-value = "work" / "home" / type-param-tel
1235 / type-param-related / iana-token / x-name
1236 ; This is further defined in individual property sections.
1237
1238<span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. MEDIATYPE</span>
1239
1240 The MEDIATYPE parameter is used with properties whose value is a URI.
1241 Its use is OPTIONAL. It provides a hint to the vCard consumer
1242 application about the media type [<a href="https://www.rfc-editor.org/rfc/rfc2046" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types&quot;">RFC2046</a>] of the resource identified
1243 by the URI. Some URI schemes do not need this parameter. For
1244 example, the "data" scheme allows the media type to be explicitly
1245 indicated as part of the URI [<a href="https://www.rfc-editor.org/rfc/rfc2397" title="&quot;The &quot;">RFC2397</a>]. Another scheme, "http",
1246 provides the media type as part of the URI resolution process, with
1247 the Content-Type HTTP header [<a href="https://www.rfc-editor.org/rfc/rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>]. The MEDIATYPE parameter is
1248 intended to be used with URI schemes that do not provide such
1249 functionality (e.g., "ftp" [<a href="https://www.rfc-editor.org/rfc/rfc1738" title="&quot;Uniform Resource Locators (URL)&quot;">RFC1738</a>]).
1250
1251 ABNF:
1252
1253 mediatype-param = "MEDIATYPE=" mediatype
1254 mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
1255 ; "attribute" and "value" are from [<a href="https://www.rfc-editor.org/rfc/rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]
1256 ; "type-name" and "subtype-name" are from [<a href="https://www.rfc-editor.org/rfc/rfc4288" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC4288</a>]
1257
1258<span class="h3"><a class="selflink" id="section-5.8" href="#section-5.8">5.8</a>. CALSCALE</span>
1259
1260 The CALSCALE parameter is identical to the CALSCALE property in
1261 iCalendar (see <a href="https://www.rfc-editor.org/rfc/rfc5545#section-3.7.1">[RFC5545], Section&nbsp;3.7.1</a>). It is used to define the
1262 calendar system in which a date or date-time value is expressed. The
1263 only value specified by iCalendar is "gregorian", which stands for
1264 the Gregorian system. It is the default when the parameter is
1265 absent. Additional values may be defined in extension documents and
1266
1267
1268
1269<span class="grey">Perreault Standards Track [Page 20]</span></pre>
1270<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-21"></span>
1271<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1272
1273
1274 registered with IANA (see <a href="#section-10.3.4">Section 10.3.4</a>). A vCard implementation
1275 MUST ignore properties with a CALSCALE parameter value that it does
1276 not understand.
1277
1278 ABNF:
1279
1280 calscale-param = "CALSCALE=" calscale-value
1281
1282 calscale-value = "gregorian" / iana-token / x-name
1283
1284<span class="h3"><a class="selflink" id="section-5.9" href="#section-5.9">5.9</a>. SORT-AS</span>
1285
1286 The "sort-as" parameter is used to specify the string to be used for
1287 national-language-specific sorting. Without this information,
1288 sorting algorithms could incorrectly sort this vCard within a
1289 sequence of sorted vCards. When this property is present in a vCard,
1290 then the given strings are used for sorting the vCard.
1291
1292 This parameter's value is a comma-separated list that MUST have as
1293 many or fewer elements as the corresponding property value has
1294 components. This parameter's value is case-sensitive.
1295
1296 ABNF:
1297
1298 sort-as-param = "SORT-AS=" sort-as-value
1299
1300 sort-as-value = param-value *("," param-value)
1301
1302 Examples: For the case of surname and given name sorting, the
1303 following examples define common sort string usage with the N
1304 property.
1305
1306 FN:Rene van der Harten
1307 N;SORT-AS="Harten,Rene":van der Harten;Rene,J.;Sir;R.D.O.N.
1308
1309 FN:Robert Pau Shou Chang
1310 N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;
1311
1312 FN:Osamu Koura
1313 N;SORT-AS="Koura,Osamu":Koura;Osamu;;
1314
1315 FN:Oscar del Pozo
1316 N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;
1317
1318 FN:Chistine d'Aboville
1319 N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;
1320
1321
1322
1323
1324
1325<span class="grey">Perreault Standards Track [Page 21]</span></pre>
1326<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-22"></span>
1327<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1328
1329
1330 FN:H. James de Mann
1331 N;SORT-AS="Mann,James":de Mann;Henry,James;;
1332
1333 If sorted by surname, the results would be:
1334
1335 Christine d'Aboville
1336 Rene van der Harten
1337 Osamu Koura
1338 H. James de Mann
1339 Robert Pau Shou Chang
1340 Oscar del Pozo
1341
1342 If sorted by given name, the results would be:
1343
1344 Christine d'Aboville
1345 H. James de Mann
1346 Osamu Koura
1347 Oscar del Pozo
1348 Rene van der Harten
1349 Robert Pau Shou Chang
1350
1351<span class="h3"><a class="selflink" id="section-5.10" href="#section-5.10">5.10</a>. GEO</span>
1352
1353 The GEO parameter can be used to indicate global positioning
1354 information that is specific to an address. Its value is the same as
1355 that of the GEO property (see <a href="#section-6.5.2">Section 6.5.2</a>).
1356
1357 ABNF:
1358
1359 geo-parameter = "GEO=" DQUOTE URI DQUOTE
1360
1361<span class="h3"><a class="selflink" id="section-5.11" href="#section-5.11">5.11</a>. TZ</span>
1362
1363 The TZ parameter can be used to indicate time zone information that
1364 is specific to an address. Its value is the same as that of the TZ
1365 property.
1366
1367 ABNF:
1368
1369 tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381<span class="grey">Perreault Standards Track [Page 22]</span></pre>
1382<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-23"></span>
1383<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1384
1385
1386<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. vCard Properties</span>
1387
1388 What follows is an enumeration of the standard vCard properties.
1389
1390<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. General Properties</span>
1391
1392<span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. BEGIN</span>
1393
1394 Purpose: To denote the beginning of a syntactic entity within a
1395 text/vcard content-type.
1396
1397 Value type: text
1398
1399 Cardinality: 1
1400
1401 Special notes: The content entity MUST begin with the BEGIN property
1402 with a value of "VCARD". The value is case-insensitive.
1403
1404 The BEGIN property is used in conjunction with the END property to
1405 delimit an entity containing a related set of properties within a
1406 text/vcard content-type. This construct can be used instead of
1407 including multiple vCards as body parts inside of a multipart/
1408 alternative MIME message. It is provided for applications that
1409 wish to define content that can contain multiple entities within
1410 the same text/vcard content-type or to define content that can be
1411 identifiable outside of a MIME environment.
1412
1413 ABNF:
1414
1415 BEGIN-param = 0" " ; no parameter allowed
1416 BEGIN-value = "VCARD"
1417
1418 Example:
1419
1420 BEGIN:VCARD
1421
1422<span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. END</span>
1423
1424 Purpose: To denote the end of a syntactic entity within a text/vcard
1425 content-type.
1426
1427 Value type: text
1428
1429 Cardinality: 1
1430
1431 Special notes: The content entity MUST end with the END type with a
1432 value of "VCARD". The value is case-insensitive.
1433
1434
1435
1436
1437<span class="grey">Perreault Standards Track [Page 23]</span></pre>
1438<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-24"></span>
1439<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1440
1441
1442 The END property is used in conjunction with the BEGIN property to
1443 delimit an entity containing a related set of properties within a
1444 text/vcard content-type. This construct can be used instead of or
1445 in addition to wrapping separate sets of information inside
1446 additional MIME headers. It is provided for applications that
1447 wish to define content that can contain multiple entities within
1448 the same text/vcard content-type or to define content that can be
1449 identifiable outside of a MIME environment.
1450
1451 ABNF:
1452
1453 END-param = 0" " ; no parameter allowed
1454 END-value = "VCARD"
1455
1456 Example:
1457
1458 END:VCARD
1459
1460<span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>. SOURCE</span>
1461
1462 Purpose: To identify the source of directory information contained
1463 in the content type.
1464
1465 Value type: uri
1466
1467 Cardinality: *
1468
1469 Special notes: The SOURCE property is used to provide the means by
1470 which applications knowledgable in the given directory service
1471 protocol can obtain additional or more up-to-date information from
1472 the directory service. It contains a URI as defined in [<a href="https://www.rfc-editor.org/rfc/rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]
1473 and/or other information referencing the vCard to which the
1474 information pertains. When directory information is available
1475 from more than one source, the sending entity can pick what it
1476 considers to be the best source, or multiple SOURCE properties can
1477 be included.
1478
1479 ABNF:
1480
1481 SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
1482 / mediatype-param / any-param
1483 SOURCE-value = URI
1484
1485 Examples:
1486
1487 SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
1488
1489
1490
1491
1492
1493<span class="grey">Perreault Standards Track [Page 24]</span></pre>
1494<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-25"></span>
1495<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1496
1497
1498 SOURCE:http://directory.example.com/addressbooks/jdoe/
1499 Jean%20Dupont.vcf
1500
1501<span class="h4"><a class="selflink" id="section-6.1.4" href="#section-6.1.4">6.1.4</a>. KIND</span>
1502
1503 Purpose: To specify the kind of object the vCard represents.
1504
1505 Value type: A single text value.
1506
1507 Cardinality: *1
1508
1509 Special notes: The value may be one of the following:
1510
1511 "individual" for a vCard representing a single person or entity.
1512 This is the default kind of vCard.
1513
1514 "group" for a vCard representing a group of persons or entities.
1515 The group's member entities can be other vCards or other types
1516 of entities, such as email addresses or web sites. A group
1517 vCard will usually contain MEMBER properties to specify the
1518 members of the group, but it is not required to. A group vCard
1519 without MEMBER properties can be considered an abstract
1520 grouping, or one whose members are known empirically (perhaps
1521 "IETF Participants" or "Republican U.S. Senators").
1522
1523 All properties in a group vCard apply to the group as a whole,
1524 and not to any particular MEMBER. For example, an EMAIL
1525 property might specify the address of a mailing list associated
1526 with the group, and an IMPP property might refer to a group
1527 chat room.
1528
1529 "org" for a vCard representing an organization. An organization
1530 vCard will not (in fact, MUST NOT) contain MEMBER properties,
1531 and so these are something of a cross between "individual" and
1532 "group". An organization is a single entity, but not a person.
1533 It might represent a business or government, a department or
1534 division within a business or government, a club, an
1535 association, or the like.
1536
1537 All properties in an organization vCard apply to the
1538 organization as a whole, as is the case with a group vCard.
1539 For example, an EMAIL property might specify the address of a
1540 contact point for the organization.
1541
1542
1543
1544
1545
1546
1547
1548
1549<span class="grey">Perreault Standards Track [Page 25]</span></pre>
1550<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-26"></span>
1551<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1552
1553
1554 "location" for a named geographical place. A location vCard will
1555 usually contain a GEO property, but it is not required to. A
1556 location vCard without a GEO property can be considered an
1557 abstract location, or one whose definition is known empirically
1558 (perhaps "New England" or "The Seashore").
1559
1560 All properties in a location vCard apply to the location
1561 itself, and not with any entity that might exist at that
1562 location. For example, in a vCard for an office building, an
1563 ADR property might give the mailing address for the building,
1564 and a TEL property might specify the telephone number of the
1565 receptionist.
1566
1567 An x-name. vCards MAY include private or experimental values for
1568 KIND. Remember that x-name values are not intended for general
1569 use and are unlikely to interoperate.
1570
1571 An iana-token. Additional values may be registered with IANA (see
1572 <a href="#section-10.3.4">Section 10.3.4</a>). A new value's specification document MUST
1573 specify which properties make sense for that new kind of vCard
1574 and which do not.
1575
1576 Implementations MUST support the specific string values defined
1577 above. If this property is absent, "individual" MUST be assumed
1578 as the default. If this property is present but the
1579 implementation does not understand its value (the value is an
1580 x-name or iana-token that the implementation does not support),
1581 the implementation SHOULD act in a neutral way, which usually
1582 means treating the vCard as though its kind were "individual".
1583 The presence of MEMBER properties MAY, however, be taken as an
1584 indication that the unknown kind is an extension of "group".
1585
1586 Clients often need to visually distinguish contacts based on what
1587 they represent, and the KIND property provides a direct way for
1588 them to do so. For example, when displaying contacts in a list,
1589 an icon could be displayed next to each one, using distinctive
1590 icons for the different kinds; a client might use an outline of a
1591 single person to represent an "individual", an outline of multiple
1592 people to represent a "group", and so on. Alternatively, or in
1593 addition, a client might choose to segregate different kinds of
1594 vCards to different panes, tabs, or selections in the user
1595 interface.
1596
1597 Some clients might also make functional distinctions among the
1598 kinds, ignoring "location" vCards for some purposes and
1599 considering only "location" vCards for others.
1600
1601
1602
1603
1604
1605<span class="grey">Perreault Standards Track [Page 26]</span></pre>
1606<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-27"></span>
1607<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1608
1609
1610 When designing those sorts of visual and functional distinctions,
1611 client implementations have to decide how to fit unsupported kinds
1612 into the scheme. What icon is used for them? The one for
1613 "individual"? A unique one, such as an icon of a question mark?
1614 Which tab do they go into? It is beyond the scope of this
1615 specification to answer these questions, but these are things
1616 implementers need to consider.
1617
1618 ABNF:
1619
1620 KIND-param = "VALUE=text" / any-param
1621 KIND-value = "individual" / "group" / "org" / "location"
1622 / iana-token / x-name
1623
1624 Example:
1625
1626 This represents someone named Jane Doe working in the marketing
1627 department of the North American division of ABC Inc.
1628
1629 BEGIN:VCARD
1630 VERSION:4.0
1631 KIND:individual
1632 FN:Jane Doe
1633 ORG:ABC\, Inc.;North American Division;Marketing
1634 END:VCARD
1635
1636 This represents the department itself, commonly known as ABC
1637 Marketing.
1638
1639 BEGIN:VCARD
1640 VERSION:4.0
1641 KIND:org
1642 FN:ABC Marketing
1643 ORG:ABC\, Inc.;North American Division;Marketing
1644 END:VCARD
1645
1646<span class="h4"><a class="selflink" id="section-6.1.5" href="#section-6.1.5">6.1.5</a>. XML</span>
1647
1648 Purpose: To include extended XML-encoded vCard data in a plain
1649 vCard.
1650
1651 Value type: A single text value.
1652
1653 Cardinality: *
1654
1655 Special notes: The content of this property is a single XML 1.0
1656 [<a href="#ref-W3C.REC-xml-20081126">W3C.REC-xml-20081126</a>] element whose namespace MUST be explicitly
1657 specified using the xmlns attribute and MUST NOT be the vCard 4
1658
1659
1660
1661<span class="grey">Perreault Standards Track [Page 27]</span></pre>
1662<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-28"></span>
1663<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1664
1665
1666 namespace ("urn:ietf:params:xml:ns:vcard-4.0"). (This implies
1667 that it cannot duplicate a standard vCard property.) The element
1668 is to be interpreted as if it was contained in a &lt;vcard&gt; element,
1669 as defined in [<a href="https://www.rfc-editor.org/rfc/rfc6351" title="&quot;xCard: vCard XML Representation&quot;">RFC6351</a>].
1670
1671 The fragment is subject to normal line folding and escaping, i.e.,
1672 replace all backslashes with "\\", then replace all newlines with
1673 "\n", then fold long lines.
1674
1675 Support for this property is OPTIONAL, but implementations of this
1676 specification MUST preserve instances of this property when
1677 propagating vCards.
1678
1679 See [<a href="https://www.rfc-editor.org/rfc/rfc6351" title="&quot;xCard: vCard XML Representation&quot;">RFC6351</a>] for more information on the intended use of this
1680 property.
1681
1682 ABNF:
1683
1684 XML-param = "VALUE=text" / altid-param
1685 XML-value = text
1686
1687<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Identification Properties</span>
1688
1689 These types are used to capture information associated with the
1690 identification and naming of the entity associated with the vCard.
1691
1692<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. FN</span>
1693
1694 Purpose: To specify the formatted text corresponding to the name of
1695 the object the vCard represents.
1696
1697 Value type: A single text value.
1698
1699 Cardinality: 1*
1700
1701 Special notes: This property is based on the semantics of the X.520
1702 Common Name attribute [<a href="#ref-CCITT.X520.1988">CCITT.X520.1988</a>]. The property MUST be
1703 present in the vCard object.
1704
1705 ABNF:
1706
1707 FN-param = "VALUE=text" / type-param / language-param / altid-param
1708 / pid-param / pref-param / any-param
1709 FN-value = text
1710
1711 Example:
1712
1713 FN:Mr. John Q. Public\, Esq.
1714
1715
1716
1717<span class="grey">Perreault Standards Track [Page 28]</span></pre>
1718<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-29"></span>
1719<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1720
1721
1722<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. N</span>
1723
1724 Purpose: To specify the components of the name of the object the
1725 vCard represents.
1726
1727 Value type: A single structured text value. Each component can have
1728 multiple values.
1729
1730 Cardinality: *1
1731
1732 Special note: The structured property value corresponds, in
1733 sequence, to the Family Names (also known as surnames), Given
1734 Names, Additional Names, Honorific Prefixes, and Honorific
1735 Suffixes. The text components are separated by the SEMICOLON
1736 character (U+003B). Individual text components can include
1737 multiple text values separated by the COMMA character (U+002C).
1738 This property is based on the semantics of the X.520 individual
1739 name attributes [<a href="#ref-CCITT.X520.1988">CCITT.X520.1988</a>]. The property SHOULD be present
1740 in the vCard object when the name of the object the vCard
1741 represents follows the X.520 model.
1742
1743 The SORT-AS parameter MAY be applied to this property.
1744
1745 ABNF:
1746
1747 N-param = "VALUE=text" / sort-as-param / language-param
1748 / altid-param / any-param
1749 N-value = list-component 4(";" list-component)
1750
1751 Examples:
1752
1753 N:Public;John;Quinlan;Mr.;Esq.
1754
1755 N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
1756
1757<span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>. NICKNAME</span>
1758
1759 Purpose: To specify the text corresponding to the nickname of the
1760 object the vCard represents.
1761
1762 Value type: One or more text values separated by a COMMA character
1763 (U+002C).
1764
1765 Cardinality: *
1766
1767
1768
1769
1770
1771
1772
1773<span class="grey">Perreault Standards Track [Page 29]</span></pre>
1774<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-30"></span>
1775<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1776
1777
1778 Special note: The nickname is the descriptive name given instead of
1779 or in addition to the one belonging to the object the vCard
1780 represents. It can also be used to specify a familiar form of a
1781 proper name specified by the FN or N properties.
1782
1783 ABNF:
1784
1785 NICKNAME-param = "VALUE=text" / type-param / language-param
1786 / altid-param / pid-param / pref-param / any-param
1787 NICKNAME-value = text-list
1788
1789 Examples:
1790
1791 NICKNAME:Robbie
1792
1793 NICKNAME:Jim,Jimmie
1794
1795 NICKNAME;TYPE=work:Boss
1796
1797<span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>. PHOTO</span>
1798
1799 Purpose: To specify an image or photograph information that
1800 annotates some aspect of the object the vCard represents.
1801
1802 Value type: A single URI.
1803
1804 Cardinality: *
1805
1806 ABNF:
1807
1808 PHOTO-param = "VALUE=uri" / altid-param / type-param
1809 / mediatype-param / pref-param / pid-param / any-param
1810 PHOTO-value = URI
1811
1812 Examples:
1813
1814 PHOTO:http://www.example.com/pub/photos/jqpublic.gif
1815
1816 PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
1817 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
1818 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
1819 &lt;...remainder of base64-encoded data...&gt;
1820
1821<span class="h4"><a class="selflink" id="section-6.2.5" href="#section-6.2.5">6.2.5</a>. BDAY</span>
1822
1823 Purpose: To specify the birth date of the object the vCard
1824 represents.
1825
1826
1827
1828
1829<span class="grey">Perreault Standards Track [Page 30]</span></pre>
1830<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-31"></span>
1831<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1832
1833
1834 Value type: The default is a single date-and-or-time value. It can
1835 also be reset to a single text value.
1836
1837 Cardinality: *1
1838
1839 ABNF:
1840
1841 BDAY-param = BDAY-param-date / BDAY-param-text
1842 BDAY-value = date-and-or-time / text
1843 ; Value and parameter MUST match.
1844
1845 BDAY-param-date = "VALUE=date-and-or-time"
1846 BDAY-param-text = "VALUE=text" / language-param
1847
1848 BDAY-param =/ altid-param / calscale-param / any-param
1849 ; calscale-param can only be present when BDAY-value is
1850 ; date-and-or-time and actually contains a date or date-time.
1851
1852 Examples:
1853
1854 BDAY:19960415
1855 BDAY:--0415
1856 BDAY;19531015T231000Z
1857 BDAY;VALUE=text:circa 1800
1858
1859<span class="h4"><a class="selflink" id="section-6.2.6" href="#section-6.2.6">6.2.6</a>. ANNIVERSARY</span>
1860
1861 Purpose: The date of marriage, or equivalent, of the object the
1862 vCard represents.
1863
1864 Value type: The default is a single date-and-or-time value. It can
1865 also be reset to a single text value.
1866
1867 Cardinality: *1
1868
1869 ABNF:
1870
1871 ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
1872 ANNIVERSARY-value = date-and-or-time / text
1873 ; Value and parameter MUST match.
1874
1875 ANNIVERSARY-param =/ altid-param / calscale-param / any-param
1876 ; calscale-param can only be present when ANNIVERSARY-value is
1877 ; date-and-or-time and actually contains a date or date-time.
1878
1879 Examples:
1880
1881 ANNIVERSARY:19960415
1882
1883
1884
1885<span class="grey">Perreault Standards Track [Page 31]</span></pre>
1886<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-32"></span>
1887<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1888
1889
1890<span class="h4"><a class="selflink" id="section-6.2.7" href="#section-6.2.7">6.2.7</a>. GENDER</span>
1891
1892 Purpose: To specify the components of the sex and gender identity of
1893 the object the vCard represents.
1894
1895 Value type: A single structured value with two components. Each
1896 component has a single text value.
1897
1898 Cardinality: *1
1899
1900 Special notes: The components correspond, in sequence, to the sex
1901 (biological), and gender identity. Each component is optional.
1902
1903 Sex component: A single letter. M stands for "male", F stands
1904 for "female", O stands for "other", N stands for "none or not
1905 applicable", U stands for "unknown".
1906
1907 Gender identity component: Free-form text.
1908
1909 ABNF:
1910
1911 GENDER-param = "VALUE=text" / any-param
1912 GENDER-value = sex [";" text]
1913
1914 sex = "" / "M" / "F" / "O" / "N" / "U"
1915
1916 Examples:
1917
1918 GENDER:M
1919 GENDER:F
1920 GENDER:M;Fellow
1921 GENDER:F;grrrl
1922 GENDER:O;intersex
1923 GENDER:;it's complicated
1924
1925<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Delivery Addressing Properties</span>
1926
1927 These types are concerned with information related to the delivery
1928 addressing or label for the vCard object.
1929
1930<span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>. ADR</span>
1931
1932 Purpose: To specify the components of the delivery address for the
1933 vCard object.
1934
1935 Value type: A single structured text value, separated by the
1936 SEMICOLON character (U+003B).
1937
1938
1939
1940
1941<span class="grey">Perreault Standards Track [Page 32]</span></pre>
1942<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-33"></span>
1943<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
1944
1945
1946 Cardinality: *
1947
1948 Special notes: The structured type value consists of a sequence of
1949 address components. The component values MUST be specified in
1950 their corresponding position. The structured type value
1951 corresponds, in sequence, to
1952 the post office box;
1953 the extended address (e.g., apartment or suite number);
1954 the street address;
1955 the locality (e.g., city);
1956 the region (e.g., state or province);
1957 the postal code;
1958 the country name (full name in the language specified in
1959 <a href="#section-5.1">Section 5.1</a>).
1960
1961 When a component value is missing, the associated component
1962 separator MUST still be specified.
1963
1964 Experience with vCard 3 has shown that the first two components
1965 (post office box and extended address) are plagued with many
1966 interoperability issues. To ensure maximal interoperability,
1967 their values SHOULD be empty.
1968
1969 The text components are separated by the SEMICOLON character
1970 (U+003B). Where it makes semantic sense, individual text
1971 components can include multiple text values (e.g., a "street"
1972 component with multiple lines) separated by the COMMA character
1973 (U+002C).
1974
1975 The property can include the "PREF" parameter to indicate the
1976 preferred delivery address when more than one address is
1977 specified.
1978
1979 The GEO and TZ parameters MAY be used with this property.
1980
1981 The property can also include a "LABEL" parameter to present a
1982 delivery address label for the address. Its value is a plain-text
1983 string representing the formatted address. Newlines are encoded
1984 as \n, as they are for property values.
1985
1986 ABNF:
1987
1988 label-param = "LABEL=" param-value
1989
1990 ADR-param = "VALUE=text" / label-param / language-param
1991 / geo-parameter / tz-parameter / altid-param / pid-param
1992 / pref-param / type-param / any-param
1993
1994
1995
1996
1997<span class="grey">Perreault Standards Track [Page 33]</span></pre>
1998<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-34"></span>
1999<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2000
2001
2002 ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
2003 ADR-component-street ";" ADR-component-locality ";"
2004 ADR-component-region ";" ADR-component-code ";"
2005 ADR-component-country
2006 ADR-component-pobox = list-component
2007 ADR-component-ext = list-component
2008 ADR-component-street = list-component
2009 ADR-component-locality = list-component
2010 ADR-component-region = list-component
2011 ADR-component-code = list-component
2012 ADR-component-country = list-component
2013
2014 Example: In this example, the post office box and the extended
2015 address are absent.
2016
2017 ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n
2018 Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n
2019 U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
2020
2021<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Communications Properties</span>
2022
2023 These properties describe information about how to communicate with
2024 the object the vCard represents.
2025
2026<span class="h4"><a class="selflink" id="section-6.4.1" href="#section-6.4.1">6.4.1</a>. TEL</span>
2027
2028 Purpose: To specify the telephone number for telephony communication
2029 with the object the vCard represents.
2030
2031 Value type: By default, it is a single free-form text value (for
2032 backward compatibility with vCard 3), but it SHOULD be reset to a
2033 URI value. It is expected that the URI scheme will be "tel", as
2034 specified in [<a href="https://www.rfc-editor.org/rfc/rfc3966" title="&quot;The tel URI for Telephone Numbers&quot;">RFC3966</a>], but other schemes MAY be used.
2035
2036 Cardinality: *
2037
2038 Special notes: This property is based on the X.520 Telephone Number
2039 attribute [<a href="#ref-CCITT.X520.1988">CCITT.X520.1988</a>].
2040
2041 The property can include the "PREF" parameter to indicate a
2042 preferred-use telephone number.
2043
2044 The property can include the parameter "TYPE" to specify intended
2045 use for the telephone number. The predefined values for the TYPE
2046 parameter are:
2047
2048
2049
2050
2051
2052
2053<span class="grey">Perreault Standards Track [Page 34]</span></pre>
2054<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-35"></span>
2055<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2056
2057
2058 +-----------+-------------------------------------------------------+
2059 | Value | Description |
2060 +-----------+-------------------------------------------------------+
2061 | text | Indicates that the telephone number supports text |
2062 | | messages (SMS). |
2063 | voice | Indicates a voice telephone number. |
2064 | fax | Indicates a facsimile telephone number. |
2065 | cell | Indicates a cellular or mobile telephone number. |
2066 | video | Indicates a video conferencing telephone number. |
2067 | pager | Indicates a paging device telephone number. |
2068 | textphone | Indicates a telecommunication device for people with |
2069 | | hearing or speech difficulties. |
2070 +-----------+-------------------------------------------------------+
2071
2072 The default type is "voice". These type parameter values can be
2073 specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a
2074 value list (e.g., TYPE="text,voice"). The default can be
2075 overridden to another set of values by specifying one or more
2076 alternate values. For example, the default TYPE of "voice" can be
2077 reset to a VOICE and FAX telephone number by the value list
2078 TYPE="voice,fax".
2079
2080 If this property's value is a URI that can also be used for
2081 instant messaging, the IMPP (<a href="#section-6.4.3">Section 6.4.3</a>) property SHOULD be
2082 used in addition to this property.
2083
2084 ABNF:
2085
2086 TEL-param = TEL-text-param / TEL-uri-param
2087 TEL-value = TEL-text-value / TEL-uri-value
2088 ; Value and parameter MUST match.
2089
2090 TEL-text-param = "VALUE=text"
2091 TEL-text-value = text
2092
2093 TEL-uri-param = "VALUE=uri" / mediatype-param
2094 TEL-uri-value = URI
2095
2096 TEL-param =/ type-param / pid-param / pref-param / altid-param
2097 / any-param
2098
2099 type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
2100 / "pager" / "textphone" / iana-token / x-name
2101 ; type-param-tel MUST NOT be used with a property other than TEL.
2102
2103
2104
2105
2106
2107
2108
2109<span class="grey">Perreault Standards Track [Page 35]</span></pre>
2110<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-36"></span>
2111<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2112
2113
2114 Example:
2115
2116 TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555
2117 TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67
2118
2119<span class="h4"><a class="selflink" id="section-6.4.2" href="#section-6.4.2">6.4.2</a>. EMAIL</span>
2120
2121 Purpose: To specify the electronic mail address for communication
2122 with the object the vCard represents.
2123
2124 Value type: A single text value.
2125
2126 Cardinality: *
2127
2128 Special notes: The property can include tye "PREF" parameter to
2129 indicate a preferred-use email address when more than one is
2130 specified.
2131
2132 Even though the value is free-form UTF-8 text, it is likely to be
2133 interpreted by a Mail User Agent (MUA) as an "addr-spec", as
2134 defined in <a href="https://www.rfc-editor.org/rfc/rfc5322#section-3.4.1">[RFC5322], Section&nbsp;3.4.1</a>. Readers should also be aware
2135 of the current work toward internationalized email addresses
2136 [<a href="#ref-RFC5335bis">RFC5335bis</a>].
2137
2138 ABNF:
2139
2140 EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
2141 / altid-param / any-param
2142 EMAIL-value = text
2143
2144 Example:
2145
2146 EMAIL;TYPE=work:jqpublic@xyz.example.com
2147
2148 EMAIL;PREF=1:jane_doe@example.com
2149
2150<span class="h4"><a class="selflink" id="section-6.4.3" href="#section-6.4.3">6.4.3</a>. IMPP</span>
2151
2152 Purpose: To specify the URI for instant messaging and presence
2153 protocol communications with the object the vCard represents.
2154
2155 Value type: A single URI.
2156
2157 Cardinality: *
2158
2159 Special notes: The property may include the "PREF" parameter to
2160 indicate that this is a preferred address and has the same
2161 semantics as the "PREF" parameter in a TEL property.
2162
2163
2164
2165<span class="grey">Perreault Standards Track [Page 36]</span></pre>
2166<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-37"></span>
2167<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2168
2169
2170 If this property's value is a URI that can be used for voice
2171 and/or video, the TEL property (<a href="#section-6.4.1">Section 6.4.1</a>) SHOULD be used in
2172 addition to this property.
2173
2174 This property is adapted from [<a href="https://www.rfc-editor.org/rfc/rfc4770" title="&quot;vCard Extensions for Instant Messaging (IM)&quot;">RFC4770</a>], which is made obsolete by
2175 this document.
2176
2177 ABNF:
2178
2179 IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
2180 / mediatype-param / altid-param / any-param
2181 IMPP-value = URI
2182
2183 Example:
2184
2185 IMPP;PREF=1:xmpp:alice@example.com
2186
2187<span class="h4"><a class="selflink" id="section-6.4.4" href="#section-6.4.4">6.4.4</a>. LANG</span>
2188
2189 Purpose: To specify the language(s) that may be used for contacting
2190 the entity associated with the vCard.
2191
2192 Value type: A single language-tag value.
2193
2194 Cardinality: *
2195
2196 ABNF:
2197
2198 LANG-param = "VALUE=language-tag" / pid-param / pref-param
2199 / altid-param / type-param / any-param
2200 LANG-value = Language-Tag
2201
2202 Example:
2203
2204 LANG;TYPE=work;PREF=1:en
2205 LANG;TYPE=work;PREF=2:fr
2206 LANG;TYPE=home:fr
2207
2208<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Geographical Properties</span>
2209
2210 These properties are concerned with information associated with
2211 geographical positions or regions associated with the object the
2212 vCard represents.
2213
2214<span class="h4"><a class="selflink" id="section-6.5.1" href="#section-6.5.1">6.5.1</a>. TZ</span>
2215
2216 Purpose: To specify information related to the time zone of the
2217 object the vCard represents.
2218
2219
2220
2221<span class="grey">Perreault Standards Track [Page 37]</span></pre>
2222<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-38"></span>
2223<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2224
2225
2226 Value type: The default is a single text value. It can also be
2227 reset to a single URI or utc-offset value.
2228
2229 Cardinality: *
2230
2231 Special notes: It is expected that names from the public-domain
2232 Olson database [<a href="#ref-TZ-DB" title="&quot;Time zone code and data&quot;">TZ-DB</a>] will be used, but this is not a
2233 restriction. See also [<a href="#ref-IANA-TZ" title="&quot;IANA Procedures for Maintaining the Timezone Database&quot;">IANA-TZ</a>].
2234
2235 Efforts are currently being directed at creating a standard URI
2236 scheme for expressing time zone information. Usage of such a
2237 scheme would ensure a high level of interoperability between
2238 implementations that support it.
2239
2240 Note that utc-offset values SHOULD NOT be used because the UTC
2241 offset varies with time -- not just because of the usual daylight
2242 saving time shifts that occur in may regions, but often entire
2243 regions will "re-base" their overall offset. The actual offset
2244 may be +/- 1 hour (or perhaps a little more) than the one given.
2245
2246 ABNF:
2247
2248 TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
2249 TZ-value = text / URI / utc-offset
2250 ; Value and parameter MUST match.
2251
2252 TZ-param =/ altid-param / pid-param / pref-param / type-param
2253 / mediatype-param / any-param
2254
2255 Examples:
2256
2257 TZ:Raleigh/North America
2258
2259 TZ;VALUE=utc-offset:-0500
2260 ; Note: utc-offset format is NOT RECOMMENDED.
2261
2262<span class="h4"><a class="selflink" id="section-6.5.2" href="#section-6.5.2">6.5.2</a>. GEO</span>
2263
2264 Purpose: To specify information related to the global positioning of
2265 the object the vCard represents.
2266
2267 Value type: A single URI.
2268
2269 Cardinality: *
2270
2271 Special notes: The "geo" URI scheme [<a href="https://www.rfc-editor.org/rfc/rfc5870" title="&quot;A Uniform Resource Identifier for Geographic Locations ('geo' URI)&quot;">RFC5870</a>] is particularly well
2272 suited for this property, but other schemes MAY be used.
2273
2274
2275
2276
2277<span class="grey">Perreault Standards Track [Page 38]</span></pre>
2278<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-39"></span>
2279<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2280
2281
2282 ABNF:
2283
2284 GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
2285 / mediatype-param / altid-param / any-param
2286 GEO-value = URI
2287
2288 Example:
2289
2290 GEO:geo:37.386013,-122.082932
2291
2292<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Organizational Properties</span>
2293
2294 These properties are concerned with information associated with
2295 characteristics of the organization or organizational units of the
2296 object that the vCard represents.
2297
2298<span class="h4"><a class="selflink" id="section-6.6.1" href="#section-6.6.1">6.6.1</a>. TITLE</span>
2299
2300 Purpose: To specify the position or job of the object the vCard
2301 represents.
2302
2303 Value type: A single text value.
2304
2305 Cardinality: *
2306
2307 Special notes: This property is based on the X.520 Title attribute
2308 [<a href="#ref-CCITT.X520.1988">CCITT.X520.1988</a>].
2309
2310 ABNF:
2311
2312 TITLE-param = "VALUE=text" / language-param / pid-param
2313 / pref-param / altid-param / type-param / any-param
2314 TITLE-value = text
2315
2316 Example:
2317
2318 TITLE:Research Scientist
2319
2320<span class="h4"><a class="selflink" id="section-6.6.2" href="#section-6.6.2">6.6.2</a>. ROLE</span>
2321
2322 Purpose: To specify the function or part played in a particular
2323 situation by the object the vCard represents.
2324
2325 Value type: A single text value.
2326
2327 Cardinality: *
2328
2329
2330
2331
2332
2333<span class="grey">Perreault Standards Track [Page 39]</span></pre>
2334<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-40"></span>
2335<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2336
2337
2338 Special notes: This property is based on the X.520 Business Category
2339 explanatory attribute [<a href="#ref-CCITT.X520.1988">CCITT.X520.1988</a>]. This property is
2340 included as an organizational type to avoid confusion with the
2341 semantics of the TITLE property and incorrect usage of that
2342 property when the semantics of this property is intended.
2343
2344 ABNF:
2345
2346 ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
2347 / type-param / altid-param / any-param
2348 ROLE-value = text
2349
2350 Example:
2351
2352 ROLE:Project Leader
2353
2354<span class="h4"><a class="selflink" id="section-6.6.3" href="#section-6.6.3">6.6.3</a>. LOGO</span>
2355
2356 Purpose: To specify a graphic image of a logo associated with the
2357 object the vCard represents.
2358
2359 Value type: A single URI.
2360
2361 Cardinality: *
2362
2363 ABNF:
2364
2365 LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
2366 / type-param / mediatype-param / altid-param / any-param
2367 LOGO-value = URI
2368
2369 Examples:
2370
2371 LOGO:http://www.example.com/pub/logos/abccorp.jpg
2372
2373 LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
2374 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
2375 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
2376 &lt;...the remainder of base64-encoded data...&gt;
2377
2378<span class="h4"><a class="selflink" id="section-6.6.4" href="#section-6.6.4">6.6.4</a>. ORG</span>
2379
2380 Purpose: To specify the organizational name and units associated
2381 with the vCard.
2382
2383 Value type: A single structured text value consisting of components
2384 separated by the SEMICOLON character (U+003B).
2385
2386
2387
2388
2389<span class="grey">Perreault Standards Track [Page 40]</span></pre>
2390<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-41"></span>
2391<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2392
2393
2394 Cardinality: *
2395
2396 Special notes: The property is based on the X.520 Organization Name
2397 and Organization Unit attributes [<a href="#ref-CCITT.X520.1988">CCITT.X520.1988</a>]. The property
2398 value is a structured type consisting of the organization name,
2399 followed by zero or more levels of organizational unit names.
2400
2401 The SORT-AS parameter MAY be applied to this property.
2402
2403 ABNF:
2404
2405 ORG-param = "VALUE=text" / sort-as-param / language-param
2406 / pid-param / pref-param / altid-param / type-param
2407 / any-param
2408 ORG-value = component *(";" component)
2409
2410 Example: A property value consisting of an organizational name,
2411 organizational unit #1 name, and organizational unit #2 name.
2412
2413 ORG:ABC\, Inc.;North American Division;Marketing
2414
2415<span class="h4"><a class="selflink" id="section-6.6.5" href="#section-6.6.5">6.6.5</a>. MEMBER</span>
2416
2417 Purpose: To include a member in the group this vCard represents.
2418
2419 Value type: A single URI. It MAY refer to something other than a
2420 vCard object. For example, an email distribution list could
2421 employ the "mailto" URI scheme [<a href="https://www.rfc-editor.org/rfc/rfc6068" title="&quot;The 'mailto' URI Scheme&quot;">RFC6068</a>] for efficiency.
2422
2423 Cardinality: *
2424
2425 Special notes: This property MUST NOT be present unless the value of
2426 the KIND property is "group".
2427
2428 ABNF:
2429
2430 MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
2431 / mediatype-param / any-param
2432 MEMBER-value = URI
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445<span class="grey">Perreault Standards Track [Page 41]</span></pre>
2446<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-42"></span>
2447<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2448
2449
2450 Examples:
2451
2452 BEGIN:VCARD
2453 VERSION:4.0
2454 KIND:group
2455 FN:The Doe family
2456 MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
2457 MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
2458 END:VCARD
2459 BEGIN:VCARD
2460 VERSION:4.0
2461 FN:John Doe
2462 UID:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
2463 END:VCARD
2464 BEGIN:VCARD
2465 VERSION:4.0
2466 FN:Jane Doe
2467 UID:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
2468 END:VCARD
2469
2470 BEGIN:VCARD
2471 VERSION:4.0
2472 KIND:group
2473 FN:Funky distribution list
2474 MEMBER:mailto:subscriber1@example.com
2475 MEMBER:xmpp:subscriber2@example.com
2476 MEMBER:sip:subscriber3@example.com
2477 MEMBER:tel:+1-418-555-5555
2478 END:VCARD
2479
2480<span class="h4"><a class="selflink" id="section-6.6.6" href="#section-6.6.6">6.6.6</a>. RELATED</span>
2481
2482 Purpose: To specify a relationship between another entity and the
2483 entity represented by this vCard.
2484
2485 Value type: A single URI. It can also be reset to a single text
2486 value. The text value can be used to specify textual information.
2487
2488 Cardinality: *
2489
2490 Special notes: The TYPE parameter MAY be used to characterize the
2491 related entity. It contains a comma-separated list of values that
2492 are registered with IANA as described in <a href="#section-10.2">Section 10.2</a>. The
2493 registry is pre-populated with the values defined in [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>]. This
2494 document also specifies two additional values:
2495
2496 agent: an entity who may sometimes act on behalf of the entity
2497 associated with the vCard.
2498
2499
2500
2501<span class="grey">Perreault Standards Track [Page 42]</span></pre>
2502<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-43"></span>
2503<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2504
2505
2506 emergency: indicates an emergency contact
2507
2508 ABNF:
2509
2510 RELATED-param = RELATED-param-uri / RELATED-param-text
2511 RELATED-value = URI / text
2512 ; Parameter and value MUST match.
2513
2514 RELATED-param-uri = "VALUE=uri" / mediatype-param
2515 RELATED-param-text = "VALUE=text" / language-param
2516
2517 RELATED-param =/ pid-param / pref-param / altid-param / type-param
2518 / any-param
2519
2520 type-param-related = related-type-value *("," related-type-value)
2521 ; type-param-related MUST NOT be used with a property other than
2522 ; RELATED.
2523
2524 related-type-value = "contact" / "acquaintance" / "friend" / "met"
2525 / "co-worker" / "colleague" / "co-resident"
2526 / "neighbor" / "child" / "parent"
2527 / "sibling" / "spouse" / "kin" / "muse"
2528 / "crush" / "date" / "sweetheart" / "me"
2529 / "agent" / "emergency"
2530
2531 Examples:
2532
2533 RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
2534 RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf
2535 RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane
2536 Doe for any inquiries.
2537
2538<span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Explanatory Properties</span>
2539
2540 These properties are concerned with additional explanations, such as
2541 that related to informational notes or revisions specific to the
2542 vCard.
2543
2544<span class="h4"><a class="selflink" id="section-6.7.1" href="#section-6.7.1">6.7.1</a>. CATEGORIES</span>
2545
2546 Purpose: To specify application category information about the
2547 vCard, also known as "tags".
2548
2549 Value type: One or more text values separated by a COMMA character
2550 (U+002C).
2551
2552 Cardinality: *
2553
2554
2555
2556
2557<span class="grey">Perreault Standards Track [Page 43]</span></pre>
2558<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-44"></span>
2559<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2560
2561
2562 ABNF:
2563
2564 CATEGORIES-param = "VALUE=text" / pid-param / pref-param
2565 / type-param / altid-param / any-param
2566 CATEGORIES-value = text-list
2567
2568 Example:
2569
2570 CATEGORIES:TRAVEL AGENT
2571
2572 CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
2573
2574<span class="h4"><a class="selflink" id="section-6.7.2" href="#section-6.7.2">6.7.2</a>. NOTE</span>
2575
2576 Purpose: To specify supplemental information or a comment that is
2577 associated with the vCard.
2578
2579 Value type: A single text value.
2580
2581 Cardinality: *
2582
2583 Special notes: The property is based on the X.520 Description
2584 attribute [<a href="#ref-CCITT.X520.1988">CCITT.X520.1988</a>].
2585
2586 ABNF:
2587
2588 NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
2589 / type-param / altid-param / any-param
2590 NOTE-value = text
2591
2592 Example:
2593
2594 NOTE:This fax number is operational 0800 to 1715
2595 EST\, Mon-Fri.
2596
2597<span class="h4"><a class="selflink" id="section-6.7.3" href="#section-6.7.3">6.7.3</a>. PRODID</span>
2598
2599 Purpose: To specify the identifier for the product that created the
2600 vCard object.
2601
2602 Type value: A single text value.
2603
2604 Cardinality: *1
2605
2606 Special notes: Implementations SHOULD use a method such as that
2607 specified for Formal Public Identifiers in [<a href="#ref-ISO9070" title="&quot;Information Processing - SGML support facilities - Registration Procedures for Public Text Owner Identifiers&quot;">ISO9070</a>] or for
2608 Universal Resource Names in [<a href="https://www.rfc-editor.org/rfc/rfc3406" title="&quot;Uniform Resource Names (URN) Namespace Definition Mechanisms&quot;">RFC3406</a>] to ensure that the text
2609 value is unique.
2610
2611
2612
2613<span class="grey">Perreault Standards Track [Page 44]</span></pre>
2614<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-45"></span>
2615<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2616
2617
2618 ABNF:
2619
2620 PRODID-param = "VALUE=text" / any-param
2621 PRODID-value = text
2622
2623 Example:
2624
2625 PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
2626
2627<span class="h4"><a class="selflink" id="section-6.7.4" href="#section-6.7.4">6.7.4</a>. REV</span>
2628
2629 Purpose: To specify revision information about the current vCard.
2630
2631 Value type: A single timestamp value.
2632
2633 Cardinality: *1
2634
2635 Special notes: The value distinguishes the current revision of the
2636 information in this vCard for other renditions of the information.
2637
2638 ABNF:
2639
2640 REV-param = "VALUE=timestamp" / any-param
2641 REV-value = timestamp
2642
2643 Example:
2644
2645 REV:19951031T222710Z
2646
2647<span class="h4"><a class="selflink" id="section-6.7.5" href="#section-6.7.5">6.7.5</a>. SOUND</span>
2648
2649 Purpose: To specify a digital sound content information that
2650 annotates some aspect of the vCard. This property is often used
2651 to specify the proper pronunciation of the name property value of
2652 the vCard.
2653
2654 Value type: A single URI.
2655
2656 Cardinality: *
2657
2658 ABNF:
2659
2660 SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
2661 / type-param / mediatype-param / altid-param
2662 / any-param
2663 SOUND-value = URI
2664
2665
2666
2667
2668
2669<span class="grey">Perreault Standards Track [Page 45]</span></pre>
2670<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-46"></span>
2671<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2672
2673
2674 Example:
2675
2676 SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
2677
2678 SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
2679 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
2680 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
2681 &lt;...the remainder of base64-encoded data...&gt;
2682
2683<span class="h4"><a class="selflink" id="section-6.7.6" href="#section-6.7.6">6.7.6</a>. UID</span>
2684
2685 Purpose: To specify a value that represents a globally unique
2686 identifier corresponding to the entity associated with the vCard.
2687
2688 Value type: A single URI value. It MAY also be reset to free-form
2689 text.
2690
2691 Cardinality: *1
2692
2693 Special notes: This property is used to uniquely identify the object
2694 that the vCard represents. The "uuid" URN namespace defined in
2695 [<a href="https://www.rfc-editor.org/rfc/rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>] is particularly well suited to this task, but other URI
2696 schemes MAY be used. Free-form text MAY also be used.
2697
2698 ABNF:
2699
2700 UID-param = UID-uri-param / UID-text-param
2701 UID-value = UID-uri-value / UID-text-value
2702 ; Value and parameter MUST match.
2703
2704 UID-uri-param = "VALUE=uri"
2705 UID-uri-value = URI
2706
2707 UID-text-param = "VALUE=text"
2708 UID-text-value = text
2709
2710 UID-param =/ any-param
2711
2712 Example:
2713
2714 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725<span class="grey">Perreault Standards Track [Page 46]</span></pre>
2726<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-47"></span>
2727<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2728
2729
2730<span class="h4"><a class="selflink" id="section-6.7.7" href="#section-6.7.7">6.7.7</a>. CLIENTPIDMAP</span>
2731
2732 Purpose: To give a global meaning to a local PID source identifier.
2733
2734 Value type: A semicolon-separated pair of values. The first field
2735 is a small integer corresponding to the second field of a PID
2736 parameter instance. The second field is a URI. The "uuid" URN
2737 namespace defined in [<a href="https://www.rfc-editor.org/rfc/rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>] is particularly well suited to this
2738 task, but other URI schemes MAY be used.
2739
2740 Cardinality: *
2741
2742 Special notes: PID source identifiers (the source identifier is the
2743 second field in a PID parameter instance) are small integers that
2744 only have significance within the scope of a single vCard
2745 instance. Each distinct source identifier present in a vCard MUST
2746 have an associated CLIENTPIDMAP. See <a href="#section-7">Section 7</a> for more details
2747 on the usage of CLIENTPIDMAP.
2748
2749 PID source identifiers MUST be strictly positive. Zero is not
2750 allowed.
2751
2752 As a special exception, the PID parameter MUST NOT be applied to
2753 this property.
2754
2755 ABNF:
2756
2757 CLIENTPIDMAP-param = any-param
2758 CLIENTPIDMAP-value = 1*DIGIT ";" URI
2759
2760 Example:
2761
2762 TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
2763 EMAIL;PID=4.1,5.2:jdoe@example.com
2764 CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
2765 CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
2766
2767<span class="h4"><a class="selflink" id="section-6.7.8" href="#section-6.7.8">6.7.8</a>. URL</span>
2768
2769 Purpose: To specify a uniform resource locator associated with the
2770 object to which the vCard refers. Examples for individuals
2771 include personal web sites, blogs, and social networking site
2772 identifiers.
2773
2774 Cardinality: *
2775
2776 Value type: A single uri value.
2777
2778
2779
2780
2781<span class="grey">Perreault Standards Track [Page 47]</span></pre>
2782<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-48"></span>
2783<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2784
2785
2786 ABNF:
2787
2788 URL-param = "VALUE=uri" / pid-param / pref-param / type-param
2789 / mediatype-param / altid-param / any-param
2790 URL-value = URI
2791
2792 Example:
2793
2794 URL:http://example.org/restaurant.french/~chezchic.html
2795
2796<span class="h4"><a class="selflink" id="section-6.7.9" href="#section-6.7.9">6.7.9</a>. VERSION</span>
2797
2798 Purpose: To specify the version of the vCard specification used to
2799 format this vCard.
2800
2801 Value type: A single text value.
2802
2803 Cardinality: 1
2804
2805 Special notes: This property MUST be present in the vCard object,
2806 and it must appear immediately after BEGIN:VCARD. The value MUST
2807 be "4.0" if the vCard corresponds to this specification. Note
2808 that earlier versions of vCard allowed this property to be placed
2809 anywhere in the vCard object, or even to be absent.
2810
2811 ABNF:
2812
2813 VERSION-param = "VALUE=text" / any-param
2814 VERSION-value = "4.0"
2815
2816 Example:
2817
2818 VERSION:4.0
2819
2820<span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Security Properties</span>
2821
2822 These properties are concerned with the security of communication
2823 pathways or access to the vCard.
2824
2825<span class="h4"><a class="selflink" id="section-6.8.1" href="#section-6.8.1">6.8.1</a>. KEY</span>
2826
2827 Purpose: To specify a public key or authentication certificate
2828 associated with the object that the vCard represents.
2829
2830 Value type: A single URI. It can also be reset to a text value.
2831
2832 Cardinality: *
2833
2834
2835
2836
2837<span class="grey">Perreault Standards Track [Page 48]</span></pre>
2838<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-49"></span>
2839<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2840
2841
2842 ABNF:
2843
2844 KEY-param = KEY-uri-param / KEY-text-param
2845 KEY-value = KEY-uri-value / KEY-text-value
2846 ; Value and parameter MUST match.
2847
2848 KEY-uri-param = "VALUE=uri" / mediatype-param
2849 KEY-uri-value = URI
2850
2851 KEY-text-param = "VALUE=text"
2852 KEY-text-value = text
2853
2854 KEY-param =/ altid-param / pid-param / pref-param / type-param
2855 / any-param
2856
2857 Examples:
2858
2859 KEY:http://www.example.com/keys/jdoe.cer
2860
2861 KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe
2862
2863 KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE
2864 UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l
2865 &lt;... remainder of base64-encoded data ...&gt;
2866
2867<span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a>. Calendar Properties</span>
2868
2869 These properties are further specified in [<a href="https://www.rfc-editor.org/rfc/rfc2739" title="&quot;Calendar Attributes for vCard and LDAP&quot;">RFC2739</a>].
2870
2871<span class="h4"><a class="selflink" id="section-6.9.1" href="#section-6.9.1">6.9.1</a>. FBURL</span>
2872
2873 Purpose: To specify the URI for the busy time associated with the
2874 object that the vCard represents.
2875
2876 Value type: A single URI value.
2877
2878 Cardinality: *
2879
2880 Special notes: Where multiple FBURL properties are specified, the
2881 default FBURL property is indicated with the PREF parameter. The
2882 FTP [<a href="https://www.rfc-editor.org/rfc/rfc1738" title="&quot;Uniform Resource Locators (URL)&quot;">RFC1738</a>] or HTTP [<a href="https://www.rfc-editor.org/rfc/rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>] type of URI points to an iCalendar
2883 [<a href="https://www.rfc-editor.org/rfc/rfc5545" title="&quot;Internet Calendaring and Scheduling Core Object Specification (iCalendar)&quot;">RFC5545</a>] object associated with a snapshot of the next few weeks
2884 or months of busy time data. If the iCalendar object is
2885 represented as a file or document, its file extension should be
2886 ".ifb".
2887
2888
2889
2890
2891
2892
2893<span class="grey">Perreault Standards Track [Page 49]</span></pre>
2894<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-50"></span>
2895<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2896
2897
2898 ABNF:
2899
2900 FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
2901 / mediatype-param / altid-param / any-param
2902 FBURL-value = URI
2903
2904 Examples:
2905
2906 FBURL;PREF=1:http://www.example.com/busy/janedoe
2907 FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb
2908
2909<span class="h4"><a class="selflink" id="section-6.9.2" href="#section-6.9.2">6.9.2</a>. CALADRURI</span>
2910
2911 Purpose: To specify the calendar user address [<a href="https://www.rfc-editor.org/rfc/rfc5545" title="&quot;Internet Calendaring and Scheduling Core Object Specification (iCalendar)&quot;">RFC5545</a>] to which a
2912 scheduling request [<a href="https://www.rfc-editor.org/rfc/rfc5546" title="&quot;iCalendar Transport-Independent Interoperability Protocol (iTIP)&quot;">RFC5546</a>] should be sent for the object
2913 represented by the vCard.
2914
2915 Value type: A single URI value.
2916
2917 Cardinality: *
2918
2919 Special notes: Where multiple CALADRURI properties are specified,
2920 the default CALADRURI property is indicated with the PREF
2921 parameter.
2922
2923 ABNF:
2924
2925 CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
2926 / mediatype-param / altid-param / any-param
2927 CALADRURI-value = URI
2928
2929 Example:
2930
2931 CALADRURI;PREF=1:mailto:janedoe@example.com
2932 CALADRURI:http://example.com/calendar/jdoe
2933
2934<span class="h4"><a class="selflink" id="section-6.9.3" href="#section-6.9.3">6.9.3</a>. CALURI</span>
2935
2936 Purpose: To specify the URI for a calendar associated with the
2937 object represented by the vCard.
2938
2939 Value type: A single URI value.
2940
2941 Cardinality: *
2942
2943 Special notes: Where multiple CALURI properties are specified, the
2944 default CALURI property is indicated with the PREF parameter. The
2945 property should contain a URI pointing to an iCalendar [<a href="https://www.rfc-editor.org/rfc/rfc5545" title="&quot;Internet Calendaring and Scheduling Core Object Specification (iCalendar)&quot;">RFC5545</a>]
2946
2947
2948
2949<span class="grey">Perreault Standards Track [Page 50]</span></pre>
2950<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-51"></span>
2951<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
2952
2953
2954 object associated with a snapshot of the user's calendar store.
2955 If the iCalendar object is represented as a file or document, its
2956 file extension should be ".ics".
2957
2958 ABNF:
2959
2960 CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
2961 / mediatype-param / altid-param / any-param
2962 CALURI-value = URI
2963
2964 Examples:
2965
2966 CALURI;PREF=1:http://cal.example.com/calA
2967 CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics
2968
2969<span class="h3"><a class="selflink" id="section-6.10" href="#section-6.10">6.10</a>. Extended Properties and Parameters</span>
2970
2971 The properties and parameters defined by this document can be
2972 extended. Non-standard, private properties and parameters with a
2973 name starting with "X-" may be defined bilaterally between two
2974 cooperating agents without outside registration or standardization.
2975
2976<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Synchronization</span>
2977
2978 vCard data often needs to be synchronized between devices. In this
2979 context, synchronization is defined as the intelligent merging of two
2980 representations of the same object. vCard 4.0 includes mechanisms to
2981 aid this process.
2982
2983<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Mechanisms</span>
2984
2985 Two mechanisms are available: the UID property is used to match
2986 multiple instances of the same vCard, while the PID parameter is used
2987 to match multiple instances of the same property.
2988
2989 The term "matching" is used here to mean recognizing that two
2990 instances are in fact representations of the same object. For
2991 example, a single vCard that is shared with someone results in two
2992 vCard instances. After they have evolved separately, they still
2993 represent the same object, and therefore may be matched by a
2994 synchronization engine.
2995
2996<span class="h4"><a class="selflink" id="section-7.1.1" href="#section-7.1.1">7.1.1</a>. Matching vCard Instances</span>
2997
2998 vCard instances for which the UID properties (<a href="#section-6.7.6">Section 6.7.6</a>) are
2999 equivalent MUST be matched. Equivalence is determined as specified
3000 in <a href="https://www.rfc-editor.org/rfc/rfc3986#section-6">[RFC3986], Section&nbsp;6</a>.
3001
3002
3003
3004
3005<span class="grey">Perreault Standards Track [Page 51]</span></pre>
3006<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-52"></span>
3007<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3008
3009
3010 In all other cases, vCard instances MAY be matched at the discretion
3011 of the synchronization engine.
3012
3013<span class="h4"><a class="selflink" id="section-7.1.2" href="#section-7.1.2">7.1.2</a>. Matching Property Instances</span>
3014
3015 Property instances belonging to unmatched vCards MUST NOT be matched.
3016
3017 Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
3018 same MUST NOT be matched.
3019
3020 Property instances whose name is CLIENTPIDMAP are handled separately
3021 and MUST NOT be matched. The synchronization MUST ensure that there
3022 is consistency of CLIENTPIDMAPs among matched vCard instances.
3023
3024 Property instances belonging to matched vCards, whose name is the
3025 same, and whose maximum cardinality is 1, MUST be matched.
3026
3027 Property instances belonging to matched vCards, whose name is the
3028 same, and whose PID parameters match, MUST be matched. See
3029 <a href="#section-7.1.3">Section 7.1.3</a> for details on PID matching.
3030
3031 In all other cases, property instances MAY be matched at the
3032 discretion of the synchronization engine.
3033
3034<span class="h4"><a class="selflink" id="section-7.1.3" href="#section-7.1.3">7.1.3</a>. PID Matching</span>
3035
3036 Two PID values for which the first fields are equivalent represent
3037 the same local value.
3038
3039 Two PID values representing the same local value and for which the
3040 second fields point to CLIENTPIDMAP properties whose second field
3041 URIs are equivalent (as specified in <a href="https://www.rfc-editor.org/rfc/rfc3986#section-6">[RFC3986], Section&nbsp;6</a>) also
3042 represent the same global value.
3043
3044 PID parameters for which at least one pair of their values represent
3045 the same global value MUST be matched.
3046
3047 In all other cases, PID parameters MAY be matched at the discretion
3048 of the synchronization engine.
3049
3050 For example, PID value "5.1", in the first vCard below, and PID value
3051 "5.2", in the second vCard below, represent the same global value.
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061<span class="grey">Perreault Standards Track [Page 52]</span></pre>
3062<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-53"></span>
3063<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3064
3065
3066 BEGIN:VCARD
3067 VERSION:4.0
3068 EMAIL;PID=4.2,5.1:jdoe@example.com
3069 CLIENTPIDMAP:1;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
3070 CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
3071 END:VCARD
3072
3073 BEGIN:VCARD
3074 VERSION:4.0
3075 EMAIL;PID=5.1,5.2:john@example.com
3076 CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
3077 CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
3078 END:VCARD
3079
3080<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Example</span>
3081
3082<span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a>. Creation</span>
3083
3084 The following simple vCard is first created on a given device.
3085
3086 BEGIN:VCARD
3087 VERSION:4.0
3088 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
3089 FN;PID=1.1:J. Doe
3090 N:Doe;J.;;;
3091 EMAIL;PID=1.1:jdoe@example.com
3092 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
3093 END:VCARD
3094
3095 This new vCard is assigned the UID
3096 "urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating
3097 device. The FN and EMAIL properties are assigned the same local
3098 value of 1, and this value is given global context by associating it
3099 with "urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which
3100 represents the creating device. We are at liberty to reuse the same
3101 local value since instances of different properties will never be
3102 matched. The N property has no PID because it is forbidden by its
3103 maximum cardinality of 1.
3104
3105<span class="h4"><a class="selflink" id="section-7.2.2" href="#section-7.2.2">7.2.2</a>. Initial Sharing</span>
3106
3107 This vCard is shared with a second device. Upon inspecting the UID
3108 property, the second device understands that this is a new vCard
3109 (i.e., unmatched) and thus the synchronization results in a simple
3110 copy.
3111
3112
3113
3114
3115
3116
3117<span class="grey">Perreault Standards Track [Page 53]</span></pre>
3118<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-54"></span>
3119<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3120
3121
3122<span class="h4"><a class="selflink" id="section-7.2.3" href="#section-7.2.3">7.2.3</a>. Adding and Sharing a Property</span>
3123
3124 A new phone number is created on the first device, then the vCard is
3125 shared with the second device. This is what the second device
3126 receives:
3127
3128 BEGIN:VCARD
3129 VERSION:4.0
3130 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
3131 FN;PID=1.1:J. Doe
3132 N:Doe;J.;;;
3133 EMAIL;PID=1.1:jdoe@example.com
3134 TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
3135 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
3136 END:VCARD
3137
3138 Upon inspecting the UID property, the second device matches the vCard
3139 it received to the vCard that it already has stored. It then starts
3140 comparing the properties of the two vCards in same-named pairs.
3141
3142 The FN properties are matched because the PID parameters have the
3143 same global value. Since the property value is the same, no update
3144 takes place.
3145
3146 The N properties are matched automatically because their maximum
3147 cardinality is 1. Since the property value is the same, no update
3148 takes place.
3149
3150 The EMAIL properties are matched because the PID parameters have the
3151 same global value. Since the property value is the same, no update
3152 takes place.
3153
3154 The TEL property in the new vCard is not matched to any in the stored
3155 vCard because no property in the stored vCard has the same name.
3156 Therefore, this property is copied from the new vCard to the stored
3157 vCard.
3158
3159 The CLIENTPIDMAP property is handled separately by the
3160 synchronization engine. It ensures that it is consistent with the
3161 stored one. If it was not, the results would be up to the
3162 synchronization engine, and thus undefined by this document.
3163
3164<span class="h4"><a class="selflink" id="section-7.2.4" href="#section-7.2.4">7.2.4</a>. Simultaneous Editing</span>
3165
3166 A new email address and a new phone number are added to the vCard on
3167 each of the two devices, and then a new synchronization event
3168 happens. Here are the vCards that are communicated to each other:
3169
3170
3171
3172
3173<span class="grey">Perreault Standards Track [Page 54]</span></pre>
3174<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-55"></span>
3175<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3176
3177
3178 BEGIN:VCARD
3179 VERSION:4.0
3180 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
3181 FN;PID=1.1:J. Doe
3182 N:Doe;J.;;;
3183 EMAIL;PID=1.1:jdoe@example.com
3184 EMAIL;PID=2.1:boss@example.com
3185 TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
3186 TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
3187 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
3188 END:VCARD
3189
3190 BEGIN:VCARD
3191 VERSION:4.0
3192 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
3193 FN;PID=1.1:J. Doe
3194 N:Doe;J.;;;
3195 EMAIL;PID=1.1:jdoe@example.com
3196 EMAIL;PID=2.2:ceo@example.com
3197 TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
3198 TEL;PID=2.2;VALUE=uri:tel:+1-666-666-6666
3199 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
3200 CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
3201 END:VCARD
3202
3203 On the first device, the same PID source identifier (1) is reused for
3204 the new EMAIL and TEL properties. On the second device, a new source
3205 identifier (2) is generated, and a corresponding CLIENTPIDMAP
3206 property is created. It contains the second device's identifier,
3207 "urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".
3208
3209 The new EMAIL properties are unmatched on both sides since the PID
3210 global value is new in both cases. The sync thus results in a copy
3211 on both sides.
3212
3213 Although the situation appears to be the same for the TEL properties,
3214 in this case, the synchronization engine is particularly smart and
3215 matches the two new TEL properties even though their PID global
3216 values are different. Note that in this case, the rules of
3217 <a href="#section-7.1.2">Section 7.1.2</a> state that two properties MAY be matched at the
3218 discretion of the synchronization engine. Therefore, the two
3219 properties are merged.
3220
3221 All this results in the following vCard, which is stored on both
3222 devices:
3223
3224
3225
3226
3227
3228
3229<span class="grey">Perreault Standards Track [Page 55]</span></pre>
3230<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-56"></span>
3231<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3232
3233
3234 BEGIN:VCARD
3235 VERSION:4.0
3236 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
3237 FN:J. Doe
3238 N:Doe;J.;;;
3239 EMAIL;PID=1.1:jdoe@example.com
3240 EMAIL;PID=2.1:boss@example.com
3241 EMAIL;PID=2.2:ceo@example.com
3242 TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
3243 TEL;PID=2.1,2.2;VALUE=uri:tel:+1-666-666-6666
3244 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
3245 CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
3246 END:VCARD
3247
3248<span class="h4"><a class="selflink" id="section-7.2.5" href="#section-7.2.5">7.2.5</a>. Global Context Simplification</span>
3249
3250 The two devices finish their synchronization procedure by simplifying
3251 their global contexts. Since they haven't talked to any other
3252 device, the following vCard is for all purposes equivalent to the
3253 above. It is also shorter.
3254
3255 BEGIN:VCARD
3256 VERSION:4.0
3257 UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
3258 FN:J. Doe
3259 N:Doe;J.;;;
3260 EMAIL;PID=1.1:jdoe@example.com
3261 EMAIL;PID=2.1:boss@example.com
3262 EMAIL;PID=3.1:ceo@example.com
3263 TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
3264 TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
3265 CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
3266 END:VCARD
3267
3268 The details of global context simplification are unspecified by this
3269 document. They are left up to the synchronization engine. This
3270 example is merely intended to illustrate the possibility, which
3271 investigating would be, in the author's opinion, worthwhile.
3272
3273<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Example: Author's vCard</span>
3274
3275 BEGIN:VCARD
3276 VERSION:4.0
3277 FN:Simon Perreault
3278 N:Perreault;Simon;;;ing. jr,M.Sc.
3279 BDAY:--0203
3280 ANNIVERSARY:20090808T1430-0500
3281 GENDER:M
3282
3283
3284
3285<span class="grey">Perreault Standards Track [Page 56]</span></pre>
3286<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-57"></span>
3287<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3288
3289
3290 LANG;PREF=1:fr
3291 LANG;PREF=2:en
3292 ORG;TYPE=work:Viagenie
3293 ADR;TYPE=work:;Suite D2-630;2875 Laurier;
3294 Quebec;QC;G1V 2M2;Canada
3295 TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102
3296 TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501
3297 EMAIL;TYPE=work:simon.perreault@viagenie.ca
3298 GEO;TYPE=work:geo:46.772673,-71.282945
3299 KEY;TYPE=work;VALUE=uri:
3300 <a href="http://www.viagenie.ca/simon.perreault/simon.asc">http://www.viagenie.ca/simon.perreault/simon.asc</a>
3301 TZ:-0500
3302 URL;TYPE=home:http://nomis80.org
3303 END:VCARD
3304
3305<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
3306
3307 o Internet mail is often used to transport vCards and is subject to
3308 many well-known security attacks, including monitoring, replay,
3309 and forgery. Care should be taken by any directory service in
3310 allowing information to leave the scope of the service itself,
3311 where any access controls or confidentiality can no longer be
3312 guaranteed. Applications should also take care to display
3313 directory data in a "safe" environment.
3314
3315 o vCards can carry cryptographic keys or certificates, as described
3316 in <a href="#section-6.8.1">Section 6.8.1</a>.
3317
3318 o vCards often carry information that can be sensitive (e.g.,
3319 birthday, address, and phone information). Although vCards have
3320 no inherent authentication or confidentiality provisions, they can
3321 easily be carried by any security mechanism that transfers MIME
3322 objects to address authentication or confidentiality (e.g., S/MIME
3323 [<a href="https://www.rfc-editor.org/rfc/rfc5751" title="&quot;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification&quot;">RFC5751</a>], OpenPGP [<a href="https://www.rfc-editor.org/rfc/rfc4880" title="&quot;OpenPGP Message Format&quot;">RFC4880</a>]). In cases where the confidentiality
3324 or authenticity of information contained in vCard is a concern,
3325 the vCard SHOULD be transported using one of these secure
3326 mechanisms. The KEY property (<a href="#section-6.8.1">Section 6.8.1</a>) can be used to
3327 transport the public key used by these mechanisms.
3328
3329 o The information in a vCard may become out of date. In cases where
3330 the vitality of data is important to an originator of a vCard, the
3331 SOURCE property (<a href="#section-6.1.3">Section 6.1.3</a>) SHOULD be specified. In addition,
3332 the "REV" type described in <a href="#section-6.7.4">Section 6.7.4</a> can be specified to
3333 indicate the last time that the vCard data was updated.
3334
3335 o Many vCard properties may be used to transport URIs. Please refer
3336 to <a href="https://www.rfc-editor.org/rfc/rfc3986#section-7">[RFC3986], Section&nbsp;7</a>, for considerations related to URIs.
3337
3338
3339
3340
3341<span class="grey">Perreault Standards Track [Page 57]</span></pre>
3342<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-58"></span>
3343<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3344
3345
3346<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span>
3347
3348<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Media Type Registration</span>
3349
3350 IANA has registered the following Media Type (in
3351 &lt;<a href="http://www.iana.org/">http://www.iana.org/</a>&gt;) and marked the text/directory Media Type as
3352 DEPRECATED.
3353
3354 To: ietf-types@iana.org
3355
3356 Subject: Registration of media type text/vcard
3357
3358 Type name: text
3359
3360 Subtype name: vcard
3361
3362 Required parameters: none
3363
3364 Optional parameters: version
3365
3366 The "version" parameter is to be interpreted identically as the
3367 VERSION vCard property. If this parameter is present, all vCards
3368 in a text/vcard body part MUST have a VERSION property with value
3369 identical to that of this MIME parameter.
3370
3371 "charset": as defined for text/plain [<a href="https://www.rfc-editor.org/rfc/rfc2046" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types&quot;">RFC2046</a>]; encodings other
3372 than UTF-8 [<a href="https://www.rfc-editor.org/rfc/rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>] MUST NOT be used.
3373
3374 Encoding considerations: 8bit
3375
3376 Security considerations: See <a href="#section-9">Section 9</a>.
3377
3378 Interoperability considerations: The text/vcard media type is
3379 intended to identify vCard data of any version. There are older
3380 specifications of vCard [<a href="https://www.rfc-editor.org/rfc/rfc2426" title="&quot;vCard MIME Directory Profile&quot;">RFC2426</a>][vCard21] still in common use.
3381 While these formats are similar, they are not strictly compatible.
3382 In general, it is necessary to inspect the value of the VERSION
3383 property (see <a href="#section-6.7.9">Section 6.7.9</a>) for identifying the standard to which
3384 a given vCard object conforms.
3385
3386 In addition, the following media types are known to have been used
3387 to refer to vCard data. They should be considered deprecated in
3388 favor of text/vcard.
3389
3390 * text/directory
3391 * text/directory; profile=vcard
3392 * text/x-vcard
3393
3394
3395
3396
3397<span class="grey">Perreault Standards Track [Page 58]</span></pre>
3398<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-59"></span>
3399<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3400
3401
3402 Published specification: <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>
3403
3404 Applications that use this media type: They are numerous, diverse,
3405 and include mail user agents, instant messaging clients, address
3406 book applications, directory servers, and customer relationship
3407 management software.
3408
3409 Additional information:
3410
3411 Magic number(s):
3412
3413 File extension(s): .vcf .vcard
3414
3415 Macintosh file type code(s):
3416
3417 Person &amp; email address to contact for further information: vCard
3418 discussion mailing list &lt;vcarddav@ietf.org&gt;
3419
3420 Intended usage: COMMON
3421
3422 Restrictions on usage: none
3423
3424 Author: Simon Perreault
3425
3426 Change controller: IETF
3427
3428<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Registering New vCard Elements</span>
3429
3430 This section defines the process for registering new or modified
3431 vCard elements (i.e., properties, parameters, value data types, and
3432 values) with IANA.
3433
3434<span class="h4"><a class="selflink" id="section-10.2.1" href="#section-10.2.1">10.2.1</a>. Registration Procedure</span>
3435
3436 The IETF has created a mailing list, vcarddav@ietf.org, which can be
3437 used for public discussion of vCard element proposals prior to
3438 registration. Use of the mailing list is strongly encouraged. The
3439 IESG has appointed a designated expert who will monitor the
3440 vcarddav@ietf.org mailing list and review registrations.
3441
3442 Registration of new vCard elements MUST be reviewed by the designated
3443 expert and published in an RFC. A Standards Track RFC is REQUIRED
3444 for the registration of new value data types that modify existing
3445 properties. A Standards Track RFC is also REQUIRED for registration
3446 of vCard elements that modify vCard elements previously documented in
3447 a Standards Track RFC.
3448
3449
3450
3451
3452
3453<span class="grey">Perreault Standards Track [Page 59]</span></pre>
3454<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-60"></span>
3455<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3456
3457
3458 The registration procedure begins when a completed registration
3459 template, defined in the sections below, is sent to vcarddav@ietf.org
3460 and iana@iana.org. Within two weeks, the designated expert is
3461 expected to tell IANA and the submitter of the registration whether
3462 the registration is approved, approved with minor changes, or
3463 rejected with cause. When a registration is rejected with cause, it
3464 can be re-submitted if the concerns listed in the cause are
3465 addressed. Decisions made by the designated expert can be appealed
3466 to the IESG Applications Area Director, then to the IESG. They
3467 follow the normal appeals procedure for IESG decisions.
3468
3469 Once the registration procedure concludes successfully, IANA creates
3470 or modifies the corresponding record in the vCard registry. The
3471 completed registration template is discarded.
3472
3473 An RFC specifying new vCard elements MUST include the completed
3474 registration templates, which MAY be expanded with additional
3475 information. These completed templates are intended to go in the
3476 body of the document, not in the IANA Considerations section.
3477
3478 Finally, note that there is an XML representation for vCard defined
3479 in [<a href="https://www.rfc-editor.org/rfc/rfc6351" title="&quot;xCard: vCard XML Representation&quot;">RFC6351</a>]. An XML representation SHOULD be defined for new vCard
3480 elements.
3481
3482<span class="h4"><a class="selflink" id="section-10.2.2" href="#section-10.2.2">10.2.2</a>. Vendor Namespace</span>
3483
3484 The vendor namespace is used for vCard elements associated with
3485 commercially available products. "Vendor" or "producer" are
3486 construed as equivalent and very broadly in this context.
3487
3488 A registration may be placed in the vendor namespace by anyone who
3489 needs to interchange files associated with the particular product.
3490 However, the registration formally belongs to the vendor or
3491 organization handling the vCard elements in the namespace being
3492 registered. Changes to the specification will be made at their
3493 request, as discussed in subsequent sections.
3494
3495 vCard elements belonging to the vendor namespace will be
3496 distinguished by the "VND-" prefix. This is followed by an IANA-
3497 registered Private Enterprise Number (PEN), a dash, and a vCard
3498 element designation of the vendor's choosing (e.g., "VND-123456-
3499 MUDPIE").
3500
3501 While public exposure and review of vCard elements to be registered
3502 in the vendor namespace are not required, using the vcarddav@ietf.org
3503 mailing list for review is strongly encouraged to improve the quality
3504 of those specifications. Registrations in the vendor namespace may
3505 be submitted directly to the IANA.
3506
3507
3508
3509<span class="grey">Perreault Standards Track [Page 60]</span></pre>
3510<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-61"></span>
3511<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3512
3513
3514<span class="h4"><a class="selflink" id="section-10.2.3" href="#section-10.2.3">10.2.3</a>. Registration Template for Properties</span>
3515
3516 A property is defined by completing the following template.
3517
3518 Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-
3519 specific property (where NNNN is replaced by the vendor's PEN).
3520
3521 Property name: The name of the property.
3522
3523 Purpose: The purpose of the property. Give a short but clear
3524 description.
3525
3526 Value type: Any of the valid value types for the property value
3527 needs to be specified. The default value type also needs to be
3528 specified.
3529
3530 Cardinality: See <a href="#section-6">Section 6</a>.
3531
3532 Property parameters: Any of the valid property parameters for the
3533 property MUST be specified.
3534
3535 Description: Any special notes about the property, how it is to be
3536 used, etc.
3537
3538 Format definition: The ABNF for the property definition needs to be
3539 specified.
3540
3541 Example(s): One or more examples of instances of the property need
3542 to be specified.
3543
3544<span class="h4"><a class="selflink" id="section-10.2.4" href="#section-10.2.4">10.2.4</a>. Registration Template for Parameters</span>
3545
3546 A parameter is defined by completing the following template.
3547
3548 Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-
3549 specific property (where NNNN is replaced by the vendor's PEN).
3550
3551 Parameter name: The name of the parameter.
3552
3553 Purpose: The purpose of the parameter. Give a short but clear
3554 description.
3555
3556 Description: Any special notes about the parameter, how it is to be
3557 used, etc.
3558
3559 Format definition: The ABNF for the parameter definition needs to be
3560 specified.
3561
3562
3563
3564
3565<span class="grey">Perreault Standards Track [Page 61]</span></pre>
3566<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-62"></span>
3567<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3568
3569
3570 Example(s): One or more examples of instances of the parameter need
3571 to be specified.
3572
3573<span class="h4"><a class="selflink" id="section-10.2.5" href="#section-10.2.5">10.2.5</a>. Registration Template for Value Data Types</span>
3574
3575 A value data type is defined by completing the following template.
3576
3577 Value name: The name of the value type.
3578
3579 Purpose: The purpose of the value type. Give a short but clear
3580 description.
3581
3582 Description: Any special notes about the value type, how it is to be
3583 used, etc.
3584
3585 Format definition: The ABNF for the value type definition needs to
3586 be specified.
3587
3588 Example(s): One or more examples of instances of the value type need
3589 to be specified.
3590
3591<span class="h4"><a class="selflink" id="section-10.2.6" href="#section-10.2.6">10.2.6</a>. Registration Template for Values</span>
3592
3593 A value is defined by completing the following template.
3594
3595 Value: The value literal.
3596
3597 Purpose: The purpose of the value. Give a short but clear
3598 description.
3599
3600 Conformance: The vCard properties and/or parameters that can take
3601 this value needs to be specified.
3602
3603 Example(s): One or more examples of instances of the value need to
3604 be specified.
3605
3606 The following is a fictitious example of a registration of a vCard
3607 value:
3608
3609 Value: supervisor
3610
3611 Purpose: It means that the related entity is the direct hierarchical
3612 superior (i.e., supervisor or manager) of the entity this vCard
3613 represents.
3614
3615 Conformance: This value can be used with the "TYPE" parameter
3616 applied on the "RELATED" property.
3617
3618
3619
3620
3621<span class="grey">Perreault Standards Track [Page 62]</span></pre>
3622<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-63"></span>
3623<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3624
3625
3626 Example(s):
3627
3628 RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
3629
3630<span class="h3"><a class="selflink" id="section-10.3" href="#section-10.3">10.3</a>. Initial vCard Elements Registries</span>
3631
3632 The IANA has created and will maintain the following registries for
3633 vCard elements with pointers to appropriate reference documents. The
3634 registries are grouped together under the heading "vCard Elements".
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677<span class="grey">Perreault Standards Track [Page 63]</span></pre>
3678<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-64"></span>
3679<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3680
3681
3682<span class="h4"><a class="selflink" id="section-10.3.1" href="#section-10.3.1">10.3.1</a>. Properties Registry</span>
3683
3684 The following table has been used to initialize the properties
3685 registry.
3686
3687 +-----------+--------------+-------------------------+
3688 | Namespace | Property | Reference |
3689 +-----------+--------------+-------------------------+
3690 | | SOURCE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.3">RFC 6350, Section&nbsp;6.1.3</a> |
3691 | | KIND | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.4">RFC 6350, Section&nbsp;6.1.4</a> |
3692 | | XML | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.5">RFC 6350, Section&nbsp;6.1.5</a> |
3693 | | FN | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.1">RFC 6350, Section&nbsp;6.2.1</a> |
3694 | | N | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.2">RFC 6350, Section&nbsp;6.2.2</a> |
3695 | | NICKNAME | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.3">RFC 6350, Section&nbsp;6.2.3</a> |
3696 | | PHOTO | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.4">RFC 6350, Section&nbsp;6.2.4</a> |
3697 | | BDAY | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.5">RFC 6350, Section&nbsp;6.2.5</a> |
3698 | | ANNIVERSARY | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.6">RFC 6350, Section&nbsp;6.2.6</a> |
3699 | | GENDER | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.7">RFC 6350, Section&nbsp;6.2.7</a> |
3700 | | ADR | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.3.1">RFC 6350, Section&nbsp;6.3.1</a> |
3701 | | TEL | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.4.1">RFC 6350, Section&nbsp;6.4.1</a> |
3702 | | EMAIL | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.4.2">RFC 6350, Section&nbsp;6.4.2</a> |
3703 | | IMPP | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.4.3">RFC 6350, Section&nbsp;6.4.3</a> |
3704 | | LANG | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.4.4">RFC 6350, Section&nbsp;6.4.4</a> |
3705 | | TZ | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.5.1">RFC 6350, Section&nbsp;6.5.1</a> |
3706 | | GEO | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.5.2">RFC 6350, Section&nbsp;6.5.2</a> |
3707 | | TITLE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.6.1">RFC 6350, Section&nbsp;6.6.1</a> |
3708 | | ROLE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.6.2">RFC 6350, Section&nbsp;6.6.2</a> |
3709 | | LOGO | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.6.3">RFC 6350, Section&nbsp;6.6.3</a> |
3710 | | ORG | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.6.4">RFC 6350, Section&nbsp;6.6.4</a> |
3711 | | MEMBER | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.6.5">RFC 6350, Section&nbsp;6.6.5</a> |
3712 | | RELATED | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.6.6">RFC 6350, Section&nbsp;6.6.6</a> |
3713 | | CATEGORIES | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.1">RFC 6350, Section&nbsp;6.7.1</a> |
3714 | | NOTE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.2">RFC 6350, Section&nbsp;6.7.2</a> |
3715 | | PRODID | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.3">RFC 6350, Section&nbsp;6.7.3</a> |
3716 | | REV | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.4">RFC 6350, Section&nbsp;6.7.4</a> |
3717 | | SOUND | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.5">RFC 6350, Section&nbsp;6.7.5</a> |
3718 | | UID | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.6">RFC 6350, Section&nbsp;6.7.6</a> |
3719 | | CLIENTPIDMAP | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.7">RFC 6350, Section&nbsp;6.7.7</a> |
3720 | | URL | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.8">RFC 6350, Section&nbsp;6.7.8</a> |
3721 | | VERSION | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.7.9">RFC 6350, Section&nbsp;6.7.9</a> |
3722 | | KEY | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.8.1">RFC 6350, Section&nbsp;6.8.1</a> |
3723 | | FBURL | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.9.1">RFC 6350, Section&nbsp;6.9.1</a> |
3724 | | CALADRURI | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.9.2">RFC 6350, Section&nbsp;6.9.2</a> |
3725 | | CALURI | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.9.3">RFC 6350, Section&nbsp;6.9.3</a> |
3726 +-----------+--------------+-------------------------+
3727
3728
3729
3730
3731
3732
3733<span class="grey">Perreault Standards Track [Page 64]</span></pre>
3734<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-65"></span>
3735<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3736
3737
3738<span class="h4"><a class="selflink" id="section-10.3.2" href="#section-10.3.2">10.3.2</a>. Parameters Registry</span>
3739
3740 The following table has been used to initialize the parameters
3741 registry.
3742
3743 +-----------+-----------+------------------------+
3744 | Namespace | Parameter | Reference |
3745 +-----------+-----------+------------------------+
3746 | | LANGUAGE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.1">RFC 6350, Section&nbsp;5.1</a> |
3747 | | VALUE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.2">RFC 6350, Section&nbsp;5.2</a> |
3748 | | PREF | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.3">RFC 6350, Section&nbsp;5.3</a> |
3749 | | ALTID | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.4">RFC 6350, Section&nbsp;5.4</a> |
3750 | | PID | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.5">RFC 6350, Section&nbsp;5.5</a> |
3751 | | TYPE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.6">RFC 6350, Section&nbsp;5.6</a> |
3752 | | MEDIATYPE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.7">RFC 6350, Section&nbsp;5.7</a> |
3753 | | CALSCALE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.8">RFC 6350, Section&nbsp;5.8</a> |
3754 | | SORT-AS | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.9">RFC 6350, Section&nbsp;5.9</a> |
3755 | | GEO | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.10">RFC 6350, Section&nbsp;5.10</a> |
3756 | | TZ | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.11">RFC 6350, Section&nbsp;5.11</a> |
3757 +-----------+-----------+------------------------+
3758
3759<span class="h4"><a class="selflink" id="section-10.3.3" href="#section-10.3.3">10.3.3</a>. Value Data Types Registry</span>
3760
3761 The following table has been used to initialize the parameters
3762 registry.
3763
3764 +------------------+-------------------------+
3765 | Value Data Type | Reference |
3766 +------------------+-------------------------+
3767 | BOOLEAN | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.4">RFC 6350, Section&nbsp;4.4</a> |
3768 | DATE | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.3.1">RFC 6350, Section&nbsp;4.3.1</a> |
3769 | DATE-AND-OR-TIME | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.3.4">RFC 6350, Section&nbsp;4.3.4</a> |
3770 | DATE-TIME | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.3.3">RFC 6350, Section&nbsp;4.3.3</a> |
3771 | FLOAT | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.6">RFC 6350, Section&nbsp;4.6</a> |
3772 | INTEGER | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.5">RFC 6350, Section&nbsp;4.5</a> |
3773 | LANGUAGE-TAG | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.8">RFC 6350, Section&nbsp;4.8</a> |
3774 | TEXT | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.1">RFC 6350, Section&nbsp;4.1</a> |
3775 | TIME | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.3.2">RFC 6350, Section&nbsp;4.3.2</a> |
3776 | TIMESTAMP | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.3.5">RFC 6350, Section&nbsp;4.3.5</a> |
3777 | URI | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.2">RFC 6350, Section&nbsp;4.2</a> |
3778 | UTC-OFFSET | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-4.7">RFC 6350, Section&nbsp;4.7</a> |
3779 +------------------+-------------------------+
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789<span class="grey">Perreault Standards Track [Page 65]</span></pre>
3790<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-66"></span>
3791<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3792
3793
3794<span class="h4"><a class="selflink" id="section-10.3.4" href="#section-10.3.4">10.3.4</a>. Values Registries</span>
3795
3796 Separate tables are used for property and parameter values.
3797
3798 The following table is to be used to initialize the property values
3799 registry.
3800
3801 +----------+------------+-------------------------+
3802 | Property | Value | Reference |
3803 +----------+------------+-------------------------+
3804 | BEGIN | VCARD | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.1">RFC 6350, Section&nbsp;6.1.1</a> |
3805 | END | VCARD | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.2">RFC 6350, Section&nbsp;6.1.2</a> |
3806 | KIND | individual | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.4">RFC 6350, Section&nbsp;6.1.4</a> |
3807 | KIND | group | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.4">RFC 6350, Section&nbsp;6.1.4</a> |
3808 | KIND | org | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.4">RFC 6350, Section&nbsp;6.1.4</a> |
3809 | KIND | location | <a href="https://www.rfc-editor.org/rfc/rfc6350#section-6.1.4">RFC 6350, Section&nbsp;6.1.4</a> |
3810 +----------+------------+-------------------------+
3811
3812 The following table has been used to initialize the parameter values
3813 registry.
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845<span class="grey">Perreault Standards Track [Page 66]</span></pre>
3846<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-67"></span>
3847<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3848
3849
3850 +------------------------+-----------+--------------+---------------+
3851 | Property | Parameter | Value | Reference |
3852 +------------------------+-----------+--------------+---------------+
3853 | FN, NICKNAME, PHOTO, | TYPE | work | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3854 | ADR, TEL, EMAIL, IMPP, | | | <a href="#section-5.6">Section 5.6</a> |
3855 | LANG, TZ, GEO, TITLE, | | | |
3856 | ROLE, LOGO, ORG, | | | |
3857 | RELATED, CATEGORIES, | | | |
3858 | NOTE, SOUND, URL, KEY, | | | |
3859 | FBURL, CALADRURI, and | | | |
3860 | CALURI | | | |
3861 | FN, NICKNAME, PHOTO, | TYPE | home | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3862 | ADR, TEL, EMAIL, IMPP, | | | <a href="#section-5.6">Section 5.6</a> |
3863 | LANG, TZ, GEO, TITLE, | | | |
3864 | ROLE, LOGO, ORG, | | | |
3865 | RELATED, CATEGORIES, | | | |
3866 | NOTE, SOUND, URL, KEY, | | | |
3867 | FBURL, CALADRURI, and | | | |
3868 | CALURI | | | |
3869 | TEL | TYPE | text | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3870 | | | | <a href="#section-6.4.1">Section 6.4.1</a> |
3871 | TEL | TYPE | voice | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3872 | | | | <a href="#section-6.4.1">Section 6.4.1</a> |
3873 | TEL | TYPE | fax | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3874 | | | | <a href="#section-6.4.1">Section 6.4.1</a> |
3875 | TEL | TYPE | cell | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3876 | | | | <a href="#section-6.4.1">Section 6.4.1</a> |
3877 | TEL | TYPE | video | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3878 | | | | <a href="#section-6.4.1">Section 6.4.1</a> |
3879 | TEL | TYPE | pager | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3880 | | | | <a href="#section-6.4.1">Section 6.4.1</a> |
3881 | TEL | TYPE | textphone | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3882 | | | | <a href="#section-6.4.1">Section 6.4.1</a> |
3883 | BDAY, ANNIVERSARY | CALSCALE | gregorian | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3884 | | | | <a href="#section-5.8">Section 5.8</a> |
3885 | RELATED | TYPE | contact | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3886 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3887 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3888 | RELATED | TYPE | acquaintance | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3889 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3890 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3891 | RELATED | TYPE | friend | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3892 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3893 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3894 | RELATED | TYPE | met | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3895 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3896 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3897
3898
3899
3900
3901<span class="grey">Perreault Standards Track [Page 67]</span></pre>
3902<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-68"></span>
3903<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3904
3905
3906 | RELATED | TYPE | co-worker | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3907 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3908 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3909 | RELATED | TYPE | colleague | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3910 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3911 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3912 | RELATED | TYPE | co-resident | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3913 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3914 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3915 | RELATED | TYPE | neighbor | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3916 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3917 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3918 | RELATED | TYPE | child | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3919 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3920 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3921 | RELATED | TYPE | parent | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3922 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3923 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3924 | RELATED | TYPE | sibling | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3925 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3926 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3927 | RELATED | TYPE | spouse | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3928 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3929 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3930 | RELATED | TYPE | kin | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3931 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3932 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3933 | RELATED | TYPE | muse | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3934 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3935 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3936 | RELATED | TYPE | crush | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3937 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3938 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3939 | RELATED | TYPE | date | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3940 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3941 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3942 | RELATED | TYPE | sweetheart | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3943 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3944 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3945 | RELATED | TYPE | me | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3946 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3947 | | | | and [<a href="#ref-xfn" title="&quot;XFN 1.1 profile&quot;">xfn</a>] |
3948 | RELATED | TYPE | agent | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3949 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3950 | RELATED | TYPE | emergency | <a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a>, |
3951 | | | | <a href="#section-6.6.6">Section 6.6.6</a> |
3952 +------------------------+-----------+--------------+---------------+
3953
3954
3955
3956
3957<span class="grey">Perreault Standards Track [Page 68]</span></pre>
3958<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-69"></span>
3959<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
3960
3961
3962<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgments</span>
3963
3964 The authors would like to thank Tim Howes, Mark Smith, and Frank
3965 Dawson, the original authors of [<a href="https://www.rfc-editor.org/rfc/rfc2425" title="&quot;A MIME Content-Type for Directory Information&quot;">RFC2425</a>] and [<a href="https://www.rfc-editor.org/rfc/rfc2426" title="&quot;vCard MIME Directory Profile&quot;">RFC2426</a>], Pete
3966 Resnick, who got this effort started and provided help along the way,
3967 as well as the following individuals who have participated in the
3968 drafting, review, and discussion of this memo:
3969
3970 Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
3971 Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie
3972 Hoeneisen, Bjoern Hoehrmann, Caleb Richardson, Chris Bryant, Chris
3973 Newman, Cyrus Daboo, Daisuke Miyakawa, Dan Brickley, Dan Mosedale,
3974 Dany Cauchie, Darryl Champagne, Dave Thewlis, Filip Navara, Florian
3975 Zeitz, Helge Hess, Jari Urpalainen, Javier Godoy, Jean-Luc Schellens,
3976 Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Julian Reschke,
3977 Kepeng Li, Kevin Marks, Kevin Wu Won, Kurt Zeilenga, Lisa Dusseault,
3978 Marc Blanchet, Mark Paterson, Markus Lorenz, Michael Haardt, Mike
3979 Douglass, Nick Levinson, Peter K. Sheerin, Peter Mogensen, Peter
3980 Saint-Andre, Renato Iannella, Rohit Khare, Sly Gryphon, Stephane
3981 Bortzmeyer, Tantek Celik, and Zoltan Ordogh.
3982
3983<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
3984
3985<span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span>
3986
3987 [<a id="ref-CCITT.X520.1988">CCITT.X520.1988</a>]
3988 International Telephone and Telegraph Consultative
3989 Committee, "Information Technology - Open Systems
3990 Interconnection - The Directory: Selected Attribute
3991 Types", CCITT Recommendation X.520, November 1988.
3992
3993 [<a id="ref-IEEE.754.2008">IEEE.754.2008</a>]
3994 Institute of Electrical and Electronics Engineers,
3995 "Standard for Binary Floating-Point Arithmetic",
3996 IEEE Standard 754, August 2008.
3997
3998 [<a id="ref-ISO.8601.2000">ISO.8601.2000</a>]
3999 International Organization for Standardization, "Data
4000 elements and interchange formats - Information interchange
4001 - Representation of dates and times", ISO Standard 8601,
4002 December 2000.
4003
4004 [<a id="ref-ISO.8601.2004">ISO.8601.2004</a>]
4005 International Organization for Standardization, "Data
4006 elements and interchange formats - Information interchange
4007 - Representation of dates and times", ISO Standard 8601,
4008 December 2004.
4009
4010
4011
4012
4013<span class="grey">Perreault Standards Track [Page 69]</span></pre>
4014<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-70"></span>
4015<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
4016
4017
4018 [<a id="ref-RFC2045">RFC2045</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
4019 Extensions (MIME) Part One: Format of Internet Message
4020 Bodies", <a href="https://www.rfc-editor.org/rfc/rfc2045">RFC 2045</a>, November 1996.
4021
4022 [<a id="ref-RFC2046">RFC2046</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
4023 Extensions (MIME) Part Two: Media Types", <a href="https://www.rfc-editor.org/rfc/rfc2046">RFC 2046</a>,
4024 November 1996.
4025
4026 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
4027 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="https://www.rfc-editor.org/rfc/rfc2119">RFC 2119</a>, March 1997.
4028
4029 [<a id="ref-RFC2739">RFC2739</a>] Small, T., Hennessy, D., and F. Dawson, "Calendar
4030 Attributes for vCard and LDAP", <a href="https://www.rfc-editor.org/rfc/rfc2739">RFC 2739</a>, January 2000.
4031
4032 [<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
4033 10646", STD 63, <a href="https://www.rfc-editor.org/rfc/rfc3629">RFC 3629</a>, November 2003.
4034
4035 [<a id="ref-RFC3966">RFC3966</a>] Schulzrinne, H., "The tel URI for Telephone Numbers",
4036 <a href="https://www.rfc-editor.org/rfc/rfc3966">RFC 3966</a>, December 2004.
4037
4038 [<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
4039 Resource Identifier (URI): Generic Syntax", STD 66,
4040 <a href="https://www.rfc-editor.org/rfc/rfc3986">RFC 3986</a>, January 2005.
4041
4042 [<a id="ref-RFC4122">RFC4122</a>] Leach, P., Mealling, M., and R. Salz, "A Universally
4043 Unique IDentifier (UUID) URN Namespace", <a href="https://www.rfc-editor.org/rfc/rfc4122">RFC 4122</a>,
4044 July 2005.
4045
4046 [<a id="ref-RFC4288">RFC4288</a>] Freed, N. and J. Klensin, "Media Type Specifications and
4047 Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="https://www.rfc-editor.org/rfc/rfc4288">RFC 4288</a>, December 2005.
4048
4049 [<a id="ref-RFC5234">RFC5234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
4050 Specifications: ABNF", STD 68, <a href="https://www.rfc-editor.org/rfc/rfc5234">RFC 5234</a>, January 2008.
4051
4052 [<a id="ref-RFC5322">RFC5322</a>] Resnick, P., Ed., "Internet Message Format", <a href="https://www.rfc-editor.org/rfc/rfc5322">RFC 5322</a>,
4053 October 2008.
4054
4055 [<a id="ref-RFC5545">RFC5545</a>] Desruisseaux, B., "Internet Calendaring and Scheduling
4056 Core Object Specification (iCalendar)", <a href="https://www.rfc-editor.org/rfc/rfc5545">RFC 5545</a>,
4057 September 2009.
4058
4059 [<a id="ref-RFC5546">RFC5546</a>] Daboo, C., "iCalendar Transport-Independent
4060 Interoperability Protocol (iTIP)", <a href="https://www.rfc-editor.org/rfc/rfc5546">RFC 5546</a>,
4061 December 2009.
4062
4063 [<a id="ref-RFC5646">RFC5646</a>] Phillips, A. and M. Davis, "Tags for Identifying
4064 Languages", <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="https://www.rfc-editor.org/rfc/rfc5646">RFC 5646</a>, September 2009.
4065
4066
4067
4068
4069<span class="grey">Perreault Standards Track [Page 70]</span></pre>
4070<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-71"></span>
4071<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
4072
4073
4074 [<a id="ref-RFC5870">RFC5870</a>] Mayrhofer, A. and C. Spanring, "A Uniform Resource
4075 Identifier for Geographic Locations ('geo' URI)",
4076 <a href="https://www.rfc-editor.org/rfc/rfc5870">RFC 5870</a>, June 2010.
4077
4078 [<a id="ref-RFC6351">RFC6351</a>] Perreault, S., "xCard: vCard XML Representation",
4079 <a href="https://www.rfc-editor.org/rfc/rfc6351">RFC 6351</a>, August 2011.
4080
4081 [<a id="ref-W3C.REC-xml-20081126">W3C.REC-xml-20081126</a>]
4082 Maler, E., Yergeau, F., Sperberg-McQueen, C., Paoli, J.,
4083 and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth
4084 Edition)", World Wide Web Consortium Recommendation REC-
4085 xml-20081126, November 2008,
4086 &lt;<a href="http://www.w3.org/TR/2008/REC-xml-20081126">http://www.w3.org/TR/2008/REC-xml-20081126</a>&gt;.
4087
4088 [<a id="ref-xfn">xfn</a>] Celik, T., Mullenweg, M., and E. Meyer, "XFN 1.1 profile",
4089 &lt;<a href="http://gmpg.org/xfn/11">http://gmpg.org/xfn/11</a>&gt;.
4090
4091<span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span>
4092
4093 [<a id="ref-IANA-TZ">IANA-TZ</a>] Lear, E. and P. Eggert, "IANA Procedures for Maintaining
4094 the Timezone Database", Work in Progress, May 2011.
4095
4096 [<a id="ref-ISO9070">ISO9070</a>] International Organization for Standardization,
4097 "Information Processing - SGML support facilities -
4098 Registration Procedures for Public Text Owner
4099 Identifiers", ISO 9070, April 1991.
4100
4101 [<a id="ref-RFC1738">RFC1738</a>] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
4102 Resource Locators (URL)", <a href="https://www.rfc-editor.org/rfc/rfc1738">RFC 1738</a>, December 1994.
4103
4104 [<a id="ref-RFC2397">RFC2397</a>] Masinter, L., "The "data" URL scheme", <a href="https://www.rfc-editor.org/rfc/rfc2397">RFC 2397</a>,
4105 August 1998.
4106
4107 [<a id="ref-RFC2425">RFC2425</a>] Howes, T., Smith, M., and F. Dawson, "A MIME Content-Type
4108 for Directory Information", <a href="https://www.rfc-editor.org/rfc/rfc2425">RFC 2425</a>, September 1998.
4109
4110 [<a id="ref-RFC2426">RFC2426</a>] Dawson, F. and T. Howes, "vCard MIME Directory Profile",
4111 <a href="https://www.rfc-editor.org/rfc/rfc2426">RFC 2426</a>, September 1998.
4112
4113 [<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
4114 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
4115 Transfer Protocol -- HTTP/1.1", <a href="https://www.rfc-editor.org/rfc/rfc2616">RFC 2616</a>, June 1999.
4116
4117 [<a id="ref-RFC3282">RFC3282</a>] Alvestrand, H., "Content Language Headers", <a href="https://www.rfc-editor.org/rfc/rfc3282">RFC 3282</a>,
4118 May 2002.
4119
4120
4121
4122
4123
4124
4125<span class="grey">Perreault Standards Track [Page 71]</span></pre>
4126<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-72"></span>
4127<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
4128
4129
4130 [<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
4131 "Uniform Resource Names (URN) Namespace Definition
4132 Mechanisms", <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="https://www.rfc-editor.org/rfc/rfc3406">RFC 3406</a>, October 2002.
4133
4134 [<a id="ref-RFC3536">RFC3536</a>] Hoffman, P., "Terminology Used in Internationalization in
4135 the IETF", <a href="https://www.rfc-editor.org/rfc/rfc3536">RFC 3536</a>, May 2003.
4136
4137 [<a id="ref-RFC4770">RFC4770</a>] Jennings, C. and J. Reschke, Ed., "vCard Extensions for
4138 Instant Messaging (IM)", <a href="https://www.rfc-editor.org/rfc/rfc4770">RFC 4770</a>, January 2007.
4139
4140 [<a id="ref-RFC4880">RFC4880</a>] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R.
4141 Thayer, "OpenPGP Message Format", <a href="https://www.rfc-editor.org/rfc/rfc4880">RFC 4880</a>, November 2007.
4142
4143 [<a id="ref-RFC5335bis">RFC5335bis</a>]
4144 Yang, A. and S. Steele, <a style="text-decoration: none" href="https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Internationalized+Email+Headers%22">"Internationalized Email Headers"</a>,
4145 Work in Progress, July 2011.
4146
4147 [<a id="ref-RFC5751">RFC5751</a>] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet
4148 Mail Extensions (S/MIME) Version 3.2 Message
4149 Specification", <a href="https://www.rfc-editor.org/rfc/rfc5751">RFC 5751</a>, January 2010.
4150
4151 [<a id="ref-RFC6068">RFC6068</a>] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto'
4152 URI Scheme", <a href="https://www.rfc-editor.org/rfc/rfc6068">RFC 6068</a>, October 2010.
4153
4154 [<a id="ref-TZ-DB">TZ-DB</a>] Olson, A., "Time zone code and data",
4155 &lt;<a href="ftp://elsie.nci.nih.gov/pub/">ftp://elsie.nci.nih.gov/pub/</a>&gt;.
4156
4157 [<a id="ref-vCard21">vCard21</a>] Internet Mail Consortium, "vCard - The Electronic Business
4158 Card Version 2.1", September 1996.
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181<span class="grey">Perreault Standards Track [Page 72]</span></pre>
4182<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-73"></span>
4183<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
4184
4185
4186<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Differences from RFCs 2425 and 2426</span>
4187
4188 This appendix contains a high-level overview of the major changes
4189 that have been made in the vCard specification from RFCs 2425 and
4190 2426. It is incomplete, as it only lists the most important changes.
4191
4192<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. New Structure</span>
4193
4194 o [<a href="https://www.rfc-editor.org/rfc/rfc2425" title="&quot;A MIME Content-Type for Directory Information&quot;">RFC2425</a>] and [<a href="https://www.rfc-editor.org/rfc/rfc2426" title="&quot;vCard MIME Directory Profile&quot;">RFC2426</a>] have been merged.
4195
4196 o vCard is now not only a MIME type but a stand-alone format.
4197
4198 o A proper MIME type registration form has been included.
4199
4200 o UTF-8 is now the only possible character set.
4201
4202 o New vCard elements can be registered from IANA.
4203
4204<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Removed Features</span>
4205
4206 o The CONTEXT and CHARSET parameters are no more.
4207
4208 o The NAME, MAILER, LABEL, and CLASS properties are no more.
4209
4210 o The "intl", "dom", "postal", and "parcel" TYPE parameter values
4211 for the ADR property have been removed.
4212
4213 o In-line vCards (such as the value of the AGENT property) are no
4214 longer supported.
4215
4216<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. New Properties and Parameters</span>
4217
4218 o The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP
4219 properties have been added.
4220
4221 o [<a href="https://www.rfc-editor.org/rfc/rfc2739" title="&quot;Calendar Attributes for vCard and LDAP&quot;">RFC2739</a>], which defines the FBURL, CALADRURI, CAPURI, and CALURI
4222 properties, has been merged in.
4223
4224 o [<a href="https://www.rfc-editor.org/rfc/rfc4770" title="&quot;vCard Extensions for Instant Messaging (IM)&quot;">RFC4770</a>], which defines the IMPP property, has been merged in.
4225
4226 o The "work" and "home" TYPE parameter values are now applicable to
4227 many more properties.
4228
4229 o The "pref" value of the TYPE parameter is now a parameter of its
4230 own, with a positive integer value indicating the level of
4231 preference.
4232
4233 o The ALTID and PID parameters have been added.
4234
4235
4236
4237<span class="grey">Perreault Standards Track [Page 73]</span></pre>
4238<hr class="noprint"><!--NewPage--><pre class="newpage"><span id="page-74"></span>
4239<span class="grey"><a href="https://www.rfc-editor.org/rfc/rfc6350">RFC 6350</a> vCard August 2011</span>
4240
4241
4242 o The MEDIATYPE parameter has been added and replaces the TYPE
4243 parameter when it was used for indicating the media type of the
4244 property's content.
4245
4246Author's Address
4247
4248 Simon Perreault
4249 Viagenie
4250 2875 Laurier, suite D2-630
4251 Quebec, QC G1V 2M2
4252 Canada
4253
4254 Phone: +1 418 656 9254
4255 EMail: simon.perreault@viagenie.ca
4256 URI: <a href="http://www.viagenie.ca/">http://www.viagenie.ca</a>
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293Perreault Standards Track [Page 74]
4294</pre>
4295</body><style data-source="base" class="dblt-ykjmwcnxmi"><br>:root {<br> --dark-background-light-text-add-on-foreground-color: #ffffff !important;<br> --dark-background-light-text-add-on-background-color: #000000 !important;<br> --dark-background-light-text-add-on-link-color: #7fd7ff !important;<br> --dark-background-light-text-add-on-visited-color: #ffafff !important;<br> --dark-background-light-text-add-on-active-color: #ff0000 !important;<br> --dark-background-light-text-add-on-selection-color: #8080ff !important;<br>}<br><br>html {<br> background-color: #000000;<br> color: #ffffff;<br>}<br><br>*:link,<br>*:link * {<br> color: #7fd7ff !important;<br>}<br><br>*:visited,<br>*:visited * {<br> color: #ffafff !important;<br>}<br><br>input[type="range"] {<br> -moz-appearance: none;<br>}<br><br>button,<br>input:not([type="checkbox"]):not([type="radio"]):not([type="range"]):not([type="file"]),<br>textarea,<br>select,<br>[contenteditable="true"] {<br> -moz-appearance: none !important;<br> color: #ffffff !important;<br> background-color: #000000;<br> border-radius: 4px;<br> border-width: 1px;<br> border-color: #ffffff;<br> border-style: solid;<br> transition-duration: 0.3s;<br> transition-property: border-color, box-shadow;<br>}<br><br>input:not([type="checkbox"]):not([type="radio"]):not([type="range"]):not([type="file"]):not([type="button"]):not([type="color"]):not([type="image"]):not([type="reset"]):not([type="submit"]),<br>textarea,<br>[contenteditable="true"] {<br> background-image: none !important;<br>}<br><br>input:focus:not([type="checkbox"]):not([type="radio"]):not([type="range"]):not([type="file"]):not([type="button"]):not([type="color"]):not([type="image"]):not([type="reset"]):not([type="submit"]),<br>textarea:focus,<br>[contenteditable="true"]:focus {<br> box-shadow: inset 0 0 0.15em 0.15em #8080ff !important;<br> border-color: #8080ff !important;<br>}<br><br>button,<br>input[type="button"],<br>input[type="color"],<br>input[type="image"],<br>input[type="reset"],<br>input[type="submit"],<br>select {<br> box-shadow: 0 0 0.15em 0.15em transparent !important;<br>}<br><br>button:focus,<br>input[type="button"]:focus,<br>input[type="color"]:focus,<br>input[type="image"]:focus,<br>input[type="reset"]:focus,<br>input[type="submit"]:focus,<br>select:focus {<br> box-shadow: 0 0 0.15em 0.15em #8080ff !important;<br> border-color: #8080ff !important;<br>}<br><br>select {<br> background-image: url('data:image/svg+xml;utf8,<?xml version="1.0" encoding="utf-8"?><svg xmlns="http://www.w3.org/2000/svg" width="500" height="500"><path stroke="%23ffffff" fill="transparent" stroke-width="40" d="M 100 175 L 250 350 L 400 175"/></svg>') !important;<br> background-position: right center !important;<br> background-repeat: no-repeat !important;<br> padding-right: 1em !important;<br> background-size: 1em !important;<br>}<br><br>*::-moz-selection {<br> color: #ffffff !important;<br> background: #8080ff !important;<br> text-shadow:<br> #000000 0 0 1pt,<br> #000000 0 0 2pt,<br> #000000 0 0 3pt,<br> #000000 0 0 4pt,<br> #000000 0 0 5pt,<br> #000000 0 0 5pt,<br> #000000 0 0 5pt !important;<br>}<br><br>img[alt="inline_formula"],<br>.mwe-math-fallback-image-inline,<br>.highcharts-container {<br> filter: invert(1) hue-rotate(180deg) !important;<br>}<br>.catalog-content .i-checkbox__faux::before {<br> filter: invert(1);<br>}<br>#gs_bdy .gsc_g_a[style*="height"] {<br> background-color: rgb(119, 119, 119) !important;<br>}<br><br>.awradio label::after {<br> background-color: #ffffff !important;<br>}<br>.jfk-button-img {<br> filter: invert(1);<br>}<br><br>#kix-current-user-cursor-caret[style*="border-color: rgb(0, 0, 0)"] {<br> border-color: #ffffff !important;<br>}<br></style><style data-source="stylesheet-processor" class="dblt-ykjmwcnxmi"><br>html {<br> background-color: #000000 !important;<br> color: #ffffff !important;<br>}<br><br>[bgcolor] {<br> background-color: #000000 !important;<br>}<br>[text],<br>[color] {<br> color: #ffffff !important;<br>}<br><br>[alink]:link:active {<br> color: #ff0000 !important;<br>}<br>[vlink]:visited {<br> color: #ffafff !important;<br>}<br>[link]:link {<br> color: #7fd7ff !important;<br>}<br><br>.qrCode > canvas {<br> border: 10px white solid;<br>}<br></style></html>
Note: See TracBrowser for help on using the repository browser.