1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Internet Engineering Task Force (IETF) K. Li
Request for Comments: 6474 B. Leiba
Category: Standards Track Huawei Technologies
ISSN: 2070-1721 December 2011
<span class="h1">vCard Format Extensions: Place of Birth, Place and Date of Death</span>
Abstract
The base vCard 4.0 specification defines a large number of
properties, including date of birth. This specification adds three
new properties to vCard 4.0: place of birth, place of death, and date
of death.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6474">http://www.rfc-editor.org/info/rfc6474</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Li & Leiba Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6474">RFC 6474</a> Birth/Death Extensions December 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Terminology Used in This Document ..........................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Identification Property Extensions ..............................<a href="#page-2">2</a>
<a href="#section-2.1">2.1</a>. Property: BIRTHPLACE .......................................<a href="#page-2">2</a>
<a href="#section-2.2">2.2</a>. Property: DEATHPLACE .......................................<a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Property: DEATHDATE ........................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. Acknowledgements ................................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. Normative References ............................................<a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The base vCard 4.0 specification [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>] defines a large number of
properties, including date of birth. This specification adds three
new properties to vCard 4.0: place of birth, place of death, and date
of death.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
Syntax specifications shown here use the augmented Backus-Naur Form
(ABNF) as described in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>], and are specified as in the base
vCard specification [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Identification Property Extensions</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Property: BIRTHPLACE</span>
Namespace:
Property name: BIRTHPLACE
Purpose: To specify the place of birth of the object the vCard
represents.
Value type: A single text value (default) or a single URI value.
Cardinality: *1
Property parameters: VALUE, LANGUAGE
<span class="grey">Li & Leiba Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6474">RFC 6474</a> Birth/Death Extensions December 2011</span>
Description:
Format definition:
BIRTHPLACE-param = "VALUE=" ("text" / "uri")
BIRTHPLACE-value = text / uri
; Value type and VALUE parameter MUST match.
BIRTHPLACE-param =/ altid-param / language-param / any-param
Examples:
BIRTHPLACE:Babies'R'Us Hospital
BIRTHPLACE;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Property: DEATHPLACE</span>
Namespace:
Property name: DEATHPLACE
Purpose: To specify the place of death of the object the vCard
represents.
Value type: A single text value (default) or a single URI value.
Cardinality: *1
Property parameters: VALUE, LANGUAGE
Description:
Format definition:
DEATHPLACE-param = "VALUE=" ("text" / "uri")
DEATHPLACE-value = text / uri
; Value type and VALUE parameter MUST match.
DEATHPLACE-param =/ altid-param / language-param / any-param
Examples:
DEATHPLACE:Aboard the Titanic\, near Newfoundland
DEATHPLACE;VALUE=uri:http://example.com/ships/titanic.vcf
DEATHPLACE;VALUE=uri:geo:41.731944,-49.945833
<span class="grey">Li & Leiba Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6474">RFC 6474</a> Birth/Death Extensions December 2011</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Property: DEATHDATE</span>
Namespace:
Property name: DEATHDATE
Purpose: To specify the date of death of the object the vCard
represents.
Value type: The default is a single date-and-or-time value. It can
also be reset to a single text value.
Cardinality: *1
Property parameters: VALUE, CALSCALE, LANGUAGE
CALSCALE can only be present when the value is a
date-and-or-time value and actually contains a date or date-time.
LANGUAGE can only be present when the value is text.
Description: The presence of a DEATHDATE property indicates that the
subject of the vCard is known to be dead. The absence
of this property makes no statement one way or the
other.
Format definition:
DEATHDATE-param = DEATHDATE-param-date / DEATHDATE-param-text
DEATHDATE-value = date-and-or-time / text
; Value type and VALUE parameter MUST match.
DEATHDATE-param-date = "VALUE=date-and-or-time" / calscale-param
; calscale-param can only be present when DEATHDATE-value is
; date-and-or-time and actually contains a date or date-time.
DEATHDATE-param-date = "VALUE=text" / language-param
DEATHDATE-param =/ altid-param / any-param
Examples:
DEATHDATE:19960415
DEATHDATE:--0415
DEATHDATE;19531015T231000Z
DEATHDATE;VALUE=text:circa 1800
<span class="grey">Li & Leiba Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6474">RFC 6474</a> Birth/Death Extensions December 2011</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
The properties defined in this document present no security
considerations beyond those in <a href="#section-9">Section 9</a> of the base vCard
specification [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
IANA has added the following entries to the vCard Properties
registry, defined in <a href="./rfc6350#section-10.3.1">Section 10.3.1 of [RFC6350]</a>.
+-----------+--------------+------------------------+
| Namespace | Property | Reference |
+-----------+--------------+------------------------+
| | BIRTHPLACE | <a href="./rfc6474#section-2.1">[RFC6474], Section 2.1</a> |
| | DEATHPLACE | <a href="./rfc6474#section-2.2">[RFC6474], Section 2.2</a> |
| | DEATHDATE | <a href="./rfc6474#section-2.3">[RFC6474], Section 2.3</a> |
+-----------+--------------+------------------------+
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
The authors of this document would like to thank Simon Perreault and
Pete Resnick, the authors of a draft version of <a href="./rfc6350">RFC 6350</a> whence the
properties defined herein originated.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
January 2008.
[<a id="ref-RFC6350">RFC6350</a>] Perreault, S., "vCard Format Specification", <a href="./rfc6350">RFC 6350</a>,
August 2011.
<span class="grey">Li & Leiba Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6474">RFC 6474</a> Birth/Death Extensions December 2011</span>
Authors' Addresses
Kepeng Li
Huawei Technologies
Huawei Base, Bantian, Longgang District
Shenzhen, Guangdong 518129
P.R. China
Phone: +86-755-28974289
EMail: likepeng@huawei.com
Barry Leiba
Huawei Technologies
Phone: +1 646 827 0648
EMail: barryleiba@computer.org
URI: <a href="http://internetmessagingtechnology.org/">http://internetmessagingtechnology.org/</a>
Li & Leiba Standards Track [Page 6]
</pre>
|
