idnits 2.17.1
draft-ietf-asid-mime-vcard-06.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** Looks like you're using RFC 2026 boilerplate. This must be updated to
follow RFC 3978/3979, as updated by RFC 4748.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand
corner of the first page
** Missing expiration date. The document expiration date should appear on
the first and last page.
** The document seems to lack a 1id_guidelines paragraph about
Internet-Drafts being working documents.
** The document seems to lack a 1id_guidelines paragraph about 6 months
document validity -- however, there's a paragraph with a matching
beginning. Boilerplate error?
** The document seems to lack a 1id_guidelines paragraph about the list of
current Internet-Drafts.
** The document seems to lack a 1id_guidelines paragraph about the list of
Shadow Directories.
== No 'Intended status' indicated for this document; assuming Proposed
Standard
== The page length should not exceed 58 lines per page, but there was 36
longer pages, the longest (page 1) being 64 lines
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** The document seems to lack a Security Considerations section.
** The document seems to lack an IANA Considerations section. (See Section
2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
when there are no actions for IANA.)
** The document seems to lack separate sections for Informative/Normative
References. All references will be assumed normative when checking for
downward references.
** The abstract seems to contain references ([RFC2119], [VCARD],
[MIME-DIR]), which it shouldn't. Please replace those with straight
textual mentions of the documents in question.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
match the current year
== Line 1818 has weird spacing: '...le text value...'
== The document seems to lack the recommended RFC 2119 boilerplate, even if
it appears to use RFC 2119 keywords.
(The document does seem to have the reference to RFC 2119 which the
ID-Checklist requires).
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- Couldn't find a document date in the document -- date freshness check
skipped.
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
== Unused Reference: 'ISO 8601' is defined on line 1931, but no explicit
reference was found in the text
== Unused Reference: 'ISO 9070' is defined on line 1940, but no explicit
reference was found in the text
== Unused Reference: 'RFC 1738' is defined on line 1964, but no explicit
reference was found in the text
== Unused Reference: 'RFC 1766' is defined on line 1967, but no explicit
reference was found in the text
== Unused Reference: 'RFC 1872' is defined on line 1970, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2045' is defined on line 1973, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2046' is defined on line 1977, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2048' is defined on line 1984, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2234' is defined on line 1991, but no explicit
reference was found in the text
-- Possible downref: Non-RFC (?) normative reference: ref. 'ISO 8601'
-- Possible downref: Non-RFC (?) normative reference: ref. 'ISO 9070'
-- Possible downref: Non-RFC (?) normative reference: ref. 'MIME-DIR'
** Obsolete normative reference: RFC 1738 (Obsoleted by RFC 4248, RFC 4266)
** Obsolete normative reference: RFC 1766 (Obsoleted by RFC 3066, RFC 3282)
** Obsolete normative reference: RFC 1872 (Obsoleted by RFC 2112)
** Obsolete normative reference: RFC 2048 (Obsoleted by RFC 4288, RFC 4289)
** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234)
-- Possible downref: Non-RFC (?) normative reference: ref. 'UNICODE'
-- Possible downref: Non-RFC (?) normative reference: ref. 'VCARD'
Summary: 16 errors (**), 0 flaws (~~), 14 warnings (==), 7 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 Network Working Group Frank Dawson
3 Request for Comments: DRAFT Lotus Development Corporation
4 draft-ietf-asid-mime-vcard-06.txt Tim Howes
5 Expires six months after April 17, 1998 Netscape Communications
7 vCard MIME Directory Profile
9 Status of this Memo
11 This document is an Internet-Draft. Internet-Drafts are working
12 documents of the Internet Engineering Task Force (IETF), its areas,
13 and its working groups. Note that other groups may also distribute
14 working documents as Internet-Drafts.
16 Internet-Drafts are draft documents valid for a maximum of six months
17 and may be updated, replaced, or obsoleted by other documents at any
18 time. It is inappropriate to use Internet- Drafts as reference
19 material or to cite them other than as "work in progress."
21 To view the entire list of current Internet-Drafts, please check
22 the "1id-abstracts.txt" listing contained in the Internet-Drafts
23 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net
24 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au
25 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu
26 (US West Coast).
28 Distribution of this memo is unlimited.
30 Copyright (C) The Internet Society 1997. All Rights Reserved.
32 Abstract
34 This memo defines the profile of the MIME Content-Type [MIME-DIR] for
35 directory information for a white-pages person object, based on a
36 vCard electronic business card. The profile definition is independent
37 of any particular directory service or protocol. The profile is
38 defined for representing and exchanging a variety of information
39 about an individual (e.g., formatted and structured name and delivery
40 addresses, email address, multiple telephone numbers, photograph,
41 logo, audio clips, etc.). The directory information used by this
42 profile is based on the attributes for the person object defined in
43 the X.520 and X.521 directory services recommendations. The profile
44 also provides the method for including a [VCARD] representation of a
45 white-pages directory entry within the MIME Content-Type defined by
46 the [MIME-DIR] document.
48 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
49 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
50 document are to be interopreted as described in [RFC 2119].
52 Dawson & Howes [Page 1] October 1998
53 vCard MIME Directory Profile
55 Table of Contents
57 1. THE VCARD MIME DIRECTORY PROFILE REGISTRATION.......................4
59 2. MIME DIRECTORY FEATURES.............................................5
61 2.1 PREDEFINED TYPE USAGE ............................................5
62 2.1.1 BEGIN and END Type ............................................5
63 2.1.2 NAME Type .....................................................6
64 2.1.3 PROFILE Type ..................................................6
65 2.1.4 SOURCE Type ...................................................6
66 2.2 PREDEFINED TYPE PARAMETER USAGE ..................................6
67 2.3 PREDEFINED VALUE TYPE USAGE ......................................6
68 2.4 EXTENSIONS TO THE PREDEFINED VALUE TYPES .........................6
69 2.4.1 BINARY ........................................................6
70 2.4.2 VCARD .........................................................7
71 2.4.3 PHONE-NUMBER ..................................................7
72 2.4.4 UTC-OFFSET ....................................................7
73 2.5 STRUCTURED TYPE VALUES ...........................................8
74 2.6 LINE DELIMITING AND FOLDING ......................................8
76 3. VCARD PROFILE FEATURES..............................................8
78 3.1 IDENTIFICATION TYPES .............................................8
79 3.1.1 FN Type Definition ............................................8
80 3.1.2 N Type Definition .............................................9
81 3.1.3 NICKNAME Type Definition ......................................9
82 3.1.4 PHOTO Type Definition ........................................10
83 3.1.5 BDAY Type Definition .........................................10
84 3.2 DELIVERY ADDRESSING TYPES .......................................11
85 3.2.1 ADR Type Definition ..........................................11
86 3.2.2 LABEL Type Definition ........................................12
87 3.3 TELECOMMUNICATIONS ADDRESSING TYPES .............................13
88 3.3.1 TEL Type Definition ..........................................13
89 3.3.2 EMAIL Type Definition ........................................14
90 3.3.3 MAILER Type Definition .......................................14
91 3.4 GEOGRAPHICAL TYPES ..............................................15
92 3.4.1 TZ Type Definition ...........................................15
93 3.4.2 GEO Type Definition ..........................................15
94 3.5 ORGANIZATIONAL TYPES ............................................16
95 3.5.1 TITLE Type Definition ........................................16
96 3.5.2 ROLE Type Definition .........................................16
97 3.5.3 LOGO Type Definition .........................................17
98 3.5.4 AGENT Type Definition ........................................17
99 3.5.5 ORG Type Definition ..........................................18
100 3.6 EXPLANATORY TYPES ...............................................18
101 3.6.1 CATEGORIES Type Definition ...................................19
102 3.6.2 NOTE Type Definition .........................................19
103 3.6.3 PRODID Type Definition .......................................19
104 3.6.4 REV Type Definition ..........................................20
106 Dawson & Howes [Page 2] October 1998
107 vCard MIME Directory Profile
109 3.6.5 SORT-STRING Type Definition ..................................20
110 3.6.6 SOUND Type Definition ........................................21
111 3.6.7 UID Type Definition ..........................................21
112 3.6.8 URL Type Definition ..........................................22
113 3.6.9 VERSION Type Definition ......................................22
114 3.7 SECURITY TYPES ..................................................23
115 3.7.1 CLASS Type Definition ........................................23
116 3.7.2 KEY Type Definition ..........................................23
117 3.8 EXTENDED TYPES ..................................................24
119 4. FORMAL GRAMMAR.....................................................24
121 5. DIFFERENCES FROM VCARD V2.1........................................33
123 6. ACKNOWLEDGEMENTS...................................................34
125 7. AUTHORS' ADDRESSES.................................................35
127 8. REFERENCES.........................................................35
129 9. FULL COPYRIGHT STATEMENT...........................................36
131 Dawson & Howes [Page 3] October 1998
132 vCard MIME Directory Profile
134 Overview
136 The [MIME-DIR] document defines a MIME Content-Type for holding
137 different kinds of directory information. The directory information
138 may be based on any of a number of directory schemas. This document
139 defines a [MIME-DIR] usage profile for conveying directory
140 information based on one such schema; that of the white-pages type of
141 person object.
143 The schema is based on the attributes for the person object defined
144 in the X.520 and X.521 directory services recommendations. The schema
145 has augmented the basic attributes defined in the X.500 series
146 recommendation in order to provide for an electronic representation
147 of the information commonly found on a paper business card. This
148 schema was first defined in the [VCARD] document. Hence, this [MIME-
149 DIR] profile is referred to as the vCard MIME Directory Profile.
151 A directory entry based on this usage profile can include traditional
152 directory, white-pages information such as the distinguished name
153 used to uniquely identify the entry, a formatted representation of
154 the name used for user-interface or presentation purposes, both the
155 structured and presentation form of the delivery address, various
156 telephone numbers and organizational information associated with the
157 entry. In addition, traditional paper business card information such
158 as an image of an organizational logo or identify photograph can be
159 included in this person object.
161 The vCard MIME Directory Profile also provides support for
162 representing other important information about the person associated
163 with the directory entry. For instance, the date of birth of the
164 person; an audio clip describing the pronunciation of the name
165 associated with the directory entry, or some other application of the
166 digital sound; longitude and latitude geo-positioning information
167 related to the person associated with the directory entry; date and
168 time that the directory information was last updated; annotations
169 often written on a business card; Uniform Resource Locators (URL) for
170 a website; public key information. The profile also provides support
171 for non-standard extensions to the schema. This provides the
172 flexibility for implementations to augment the current capabilities
173 of the profile in a standardized way. More information about this
174 electronic business card format can be found in [VCARD].
176 1. The vCard Mime Directory Profile Registration
178 This profile is identified by the following [MIME-DIR] registration
179 template information. Subsequent sections define the profile
180 definition.
182 To: ietf-mime-directory@imc.org
184 Subject: Registration of text/directory MIME profile VCARD
186 Profile name: VCARD
188 Dawson & Howes [Page 4] October 1998
189 vCard MIME Directory Profile
191 Profile purpose: To hold person object or white-pages type of
192 directory information. The person schema captured in the directory
193 entries is that commonly found in an electronic business card.
195 Predefined MIME Directory value specifications used: uri, date, date-
196 time, float
198 New value specifications: This profile places further constraints on
199 the [MIME-DIR] text value specification. In addition, it adds a
200 binary, phone-number, utc-offset and vcard value specifications.
202 Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN,
203 END.
205 Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
206 LANGUAGE, CONTEXT.
208 New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL,
209 MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE,
210 PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS, KEY
212 New parameters: TYPE
214 Profile special notes: The vCard object MUST contain the FN, N and
215 VERSION types. The type-grouping feature of [MIME-DIR] is supported
216 by this profile to group related vCard properties about a directory
217 entry. For example, vCard properties describing WORK or HOME related
218 characteristics MAY be grouped with a unique group label.
220 The profile permits the use of non-standard types (i.e., those
221 identified with the prefix string "X-") as a flexible method for
222 implementations to extend the functionality currently defined within
223 this profile.
225 2. MIME Directory Features
227 The vCard MIME Directory Profile makes use of many of the features
228 defined by [MIME-DIR]. The following sections either clarify or
229 extend the content-type definition of [MIME-DIR].
231 2.1 Predefined Type Usage
233 The vCard MIME Directory Profile uses the following predefined types
234 from [MIME-DIR].
236 2.1.1 BEGIN and END Type
238 The content entity MUST begin with the BEGIN type with a value of
239 "VCARD". The content entity MUST end with the END type with a value
240 of "VCARD".
242 Dawson & Howes [Page 5] October 1998
243 vCard MIME Directory Profile
245 2.1.2 NAME Type
247 If the NAME type appears within a MIME entity conforming to this
248 profile, its value is the displayable, presentation text associated
249 with the source for the vCard, as specified in the SOURCE type.
251 2.1.3 PROFILE Type
253 If the PROFILE type appears within a MIME entity conforming to this
254 profile, its value MUST be "VCARD".
256 2.1.4 SOURCE Type
258 If the SOURCE type appears within a MIME entity conforming to this
259 profile, its value provides information how to find the source for
260 the vCard.
262 2.2 Predefined Type Parameter Usage
264 The vCard MIME Directory Profile uses the following predefined type
265 parameters as defined by [MIME-DIR].
267 - LANGUAGE
269 - ENCODING
271 - VALUE
273 2.3 Predefined VALUE Type Usage
275 The predefined data type values specified in [MIME-DIR] MUST NOT be
276 repeated in COMMA separated value lists, unless specified by this
277 specification.
279 The text value type defined in [MIME-DIR] is further restricted such
280 that any SEMI-COLON character (ASCII decimal 59) in the value MUST be
281 escaped with the BACKSLASH character (ASCII decimal 92).
283 2.4 Extensions To The Predefined VALUE Types
285 The predefined data type values specified in [MIME-DIR] have been
286 extended by the vCard profile to include a number of value types that
287 are specific to this profile.
289 2.4.1 BINARY
291 The "binary" value type specifies that the type value is inline,
292 encoded binary data. This value type may be specified in the PHOTO,
293 LOGO, SOUND, and KEY types.
295 If inline encoded binary data is specified, the ENCODING type
296 parameter MUST be used to specify the encoding format. The binary
297 data MUST be encoded using the "B" encoding format. Long lines of
299 Dawson & Howes [Page 6] October 1998
300 vCard MIME Directory Profile
302 encoded binary data may be folded using the folding method defined in
303 [MIME-DIR].
305 The value type is defined by the following notation:
307 binary =
309 2.4.2 VCARD
311 The "vcard" value type specifies that the type value is another
312 vCard. This value type can be specified in the AGENT type. The value
313 type is defined by this specification. Since each of the type
314 declarations with in the vcard value type are being specified within
315 a text value themselves, they MUST be terminated with the backslash
316 escape sequence "\n" or "\N", instead of the normal newline character
317 sequence CRLF. In addition, any COMMA character (ASCII decimal 44),
318 SEMI-COLON character (ASCII decimal 59) and COLON character (ASCII
319 decimal 58) MUST be escaped with the BACKSLASH character (ASCII
320 decimal 92). For example, with the AGENT type a value would be
321 specified as :
323 AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
324 TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERN\n
325 ET:jfriday@host.com\nEND:VCARD\n
327 2.4.3 PHONE-NUMBER
329 The "phone-number" value type specifies that the type value is a
330 telephone number. This value type can be specified in the TEL type.
331 The value type is a text value that has the special semantics of a
332 telephone number as defined in [CCITT E.163] and [CCITT X.121].
334 2.4.4 UTC-OFFSET
336 The "utc-offset" value type specifies that the type value is a signed
337 offset from UTC. This value type can be specified in the TZ type.
339 The value type is an offset from Coordinated Universal Time (UTC). It
340 is specified as a positive or negative difference in units of hours
341 and minutes (e.g., +hh:mm). The time is specified as a 24-hour clock.
342 Hour values are from 00 to 23, and minute values are from 00 to 59.
343 Hour and minutes are 2-digits with high order zeroes required to
344 maintain digit count. The extended format for ISO 8601 UTC offsets
345 MUST be used. The extended format makes use of a colon character as a
346 separator of the hour and minute text fields.
348 The value is defined by the following notation:
350 time-hour = 2DIGIT ;00-23
351 time-minute = 2DIGIT ;00-59
352 utc-offset = ("+" / "-") time-hour ":" time-minute
354 Dawson & Howes [Page 7] October 1998
355 vCard MIME Directory Profile
357 2.5 Structured Type Values
359 Compound type values are delimited by a field delimiter, specified by
360 the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a
361 component of a compound property value MUST be escaped with a
362 BACKSLASH character (ASCII decimal 92).
364 Lists of values are delimited by a list delimiter, specified by the
365 COMMA character (ASCII decimal 44). A COMMA character in a value MUST
366 be escaped with a BACKSLASH character (ASCII decimal 92).
368 This profile supports the type grouping mechanism defined in [MIME-
369 DIR]. Grouping of related types is a useful technique to communicate
370 common semantics concerning the properties of a vCard.
372 2.6 Line Delimiting and Folding
374 This profile supports the same line delimiting and folding methods
375 defined in [MIME-DIR].
377 3. vCard Profile Features
379 The vCard MIME Directory Profile Type contains directory information,
380 typically pertaining to a single directory entry. The information is
381 described using an attribute schema that is tailored for capturing
382 personal contact information. The vCard can include attributes that
383 describe identification, delivery addressing, telecommunications
384 addressing, geographical, organizational, general explanatory and
385 security and access information about the particular object
386 associated with the vCard.
388 3.1 Identification Types
390 These types are used in the vCard profile to capture information
391 associated with the identification and naming of the person or
392 resource associated with the vCard.
394 3.1.1 FN Type Definition
396 To: ietf-mime-directory@imc.org
398 Subject: Registration of text/directory MIME type FN
400 Type name:FN
402 Type purpose: To specify the formatted text corresponding to the name
403 of the object the vCard represents.
405 Type encoding: 8bit
407 Type value: A single text value.
409 Dawson & Howes [Page 8] October 1998
410 vCard MIME Directory Profile
412 Type special notes: This type is based on the semantics of the X.520
413 Common Name attribute. The property MUST be present if the vCard
414 conforms to this specification.
416 Type example:
418 FN:Mr. John Q. Public\, Esq.
420 3.1.2 N Type Definition
422 To: ietf-mime-directory@imc.org
424 Subject: Registration of text/directory MIME type N
426 Type name: N
428 Type purpose: To specify the components of the name of the object the
429 vCard represents.
431 Type encoding: 8bit
433 Type value: A single structured text value. Each component may have
434 multiple values.
436 Type special note: The structured type value corresponds, in
437 sequence, to the Family Name, Given Name, Additional Names, Honorific
438 Prefixes, and Honorific Suffixes. The text components are separated
439 by the SEMI-COLON character (ASCII decimal 59). Individual text
440 components MAY include multiple text values (e.g., multiple
441 Additional Names), separated by the COMMA character (ASCII decimal
442 44). This type is based on the semantics of the X.520 individual name
443 attributes. The property MUST be present in the vCard object.
445 Type example:
447 N:Public;John;Quinlan;Mr.;Esq.
449 N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
451 3.1.3 NICKNAME Type Definition
453 To: ietf-mime-directory@imc.org
455 Subject: Registration of text/directory MIME type NICKNAME
457 Type name: NICKNAME
459 Type purpose: To specify the text corresponding to the nickname of
460 the object the vCard represents.
462 Type encoding: 8bit
464 Type value: One or more text values separated by a COMMA character
465 (ASCII decimal 44).
467 Dawson & Howes [Page 9] October 1998
468 vCard MIME Directory Profile
470 Type special note: The nickname is the descriptive name given instead
471 of or in addition to the one belonging to a person, place, or thing.
472 It may also be used to specify a familiar form of a proper name
473 specified by the FN or N types.
475 Type example:
477 NICKNAME:Robbie
479 NICKNAME:Jim,Jimmie
481 3.1.4 PHOTO Type Definition
483 To: ietf-mime-directory@imc.org
485 Subject: Registration of text/directory MIME type PHOTO
487 Type name: PHOTO
489 Type purpose: To specify an image or photograph information that
490 annotates some aspect of the object the vCard represents.
492 Type encoding: The encoding MUST be reset to "b" using the ENCODING
493 parameter in order to specify inline, encoded binary data. If the
494 value is referenced by a URI value, then the default encoding of 8bit
495 is used and no explicit ENCODING parameter is needed.
497 Type value: A single value. The default is binary value. It may also
498 be reset to uri value. The uri value may be used to specify a value
499 outside of this MIME entity.
501 Type special notes: The type MAY include the type parameter "TYPE" to
502 specify the graphic image format type. The TYPE parameter values MUST
503 be one of the IANA registered image formats or a non-standard image
504 format.
506 Type example:
508 PHOTO;VALUE=uri:http://www.abc.com/pub/photos
509 /jqpublic.gif
511 PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
512 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
513 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
514 <...remainder of "B" encoded binary data...>
516 3.1.5 BDAY Type Definition
518 To: ietf-mime-directory@imc.org
520 Subject: Registration of text/directory MIME type BDAY
522 Type name: BDAY
524 Dawson & Howes [Page 10] October 1998
525 vCard MIME Directory Profile
527 Type purpose: To specify the birth date of the object the vCard
528 represents.
530 Type encoding: 8bit
532 Type value: The default is a single date value. It may also be reset
533 to a single date-time value.
535 Type examples:
537 BDAY:1996-04-15
539 BDAY:1953-10-15T23:10:00Z
541 BDAY:1987-09-27T08:30:00-06:00
543 3.2 Delivery Addressing Types
545 These types are concerned with information related to the delivery
546 addressing or label for the vCard object.
548 3.2.1 ADR Type Definition
550 To: ietf-mime-directory@imc.org
552 Subject: Registration of text/directory MIME type ADR
554 Type name: ADR
556 Type purpose: To specify the components of the delivery address for
557 the vCard object.
559 Type encoding: 8bit
561 Type value: A single structured text value, separated by the SEMI-
562 COLON character (ASCII decimal 59).
564 Type special notes: The structured type value consists of a sequence
565 of address components. The component values MUST be specified in
566 their corresponding position. The structured type value corresponds,
567 in sequence, to the post office box; the extended address; the street
568 address; the locality (e.g., city); the region (e.g., state or
569 province); the postal code; the country name. When a component value
570 is missing, the associated component separator MUST still be
571 specified.
573 The type may include the type parameter "TYPE" to specify the
574 delivery address type. The TYPE parameter values may include "dom" to
575 indicate a domestic delivery address; "intl" to indicate an
576 international delivery address; "postal" to indicate a postal
577 delivery address; "parcel" to indicate a parcel delivery address;
578 "home" to indicate a delivery address for a residence; "work" to
579 indicate delivery address for a place of work; and "pref" to indicate
580 the preferred delivery address when more than one address is
582 Dawson & Howes [Page 11] October 1998
583 vCard MIME Directory Profile
585 specified. These type parameter values may be specified as a
586 parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
587 (i.e., "TYPE=dom,postal"). This type is based on semantics of the
588 X.520 geographical and postal addressing attributes. The default is
589 "TYPE=intl,postal,parcel,work". The default can be overridden to some
590 other set of values by specifying one or more alternate values. For
591 example, the default can be reset to "TYPE=dom,postal,work,home" to
592 specify a domestic delivery address for postal delivery to a
593 residence that is also used for work.
595 Type example: In this example the post office box and the extended
596 address are absent.
598 ADR;TYPE=dom,home,postal,parcel:;;123 Main
599 Street;Any Town;CA;91921-1234
601 3.2.2 LABEL Type Definition
603 To: ietf-mime-directory@imc.org
605 Subject: Registration of text/directory MIME type LABEL
607 Type name: LABEL
609 Type purpose: To specify the formatted text corresponding to delivery
610 address of the object the vCard represents.
612 Type encoding: 8bit
614 Type value: A single text value.
616 Type special notes: The type value is formatted text that may be used
617 to present a delivery address label for the vCard object. The type
618 may include the type parameter "TYPE" to specify delivery label type.
619 The TYPE parameter values may include "dom" to indicate a domestic
620 delivery label; "intl" to indicate an international delivery label;
621 "postal" to indicate a postal delivery label; "parcel" to indicate a
622 parcel delivery label; "home" to indicate a delivery label for a
623 residence; "work" to indicate delivery label for a place of work; and
624 "pref" to indicate the preferred delivery label when more than one
625 label is specified. These type parameter values may specified as a
626 parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
627 (i.e., "TYPE=dom,postal"). This type is based on semantics of the
628 X.520 geographical and postal addressing attributes. The default is
629 "TYPE=intl,postal,parcel,work". The default can be overridden to some
630 other set of values by specifying one or more alternate values. For
631 example, the default can be reset to "TYPE=intl,post,parcel,home" to
632 specify an international delivery label for both postal and parcel
633 delivery to a residential location.
635 Type example: A multi-line address label.
637 LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public\, Esq.\n
638 Mail Drop: TNE QB\n
640 Dawson & Howes [Page 12] October 1998
641 vCard MIME Directory Profile
643 123 Main Street\n
644 Any Town\, CA 91921-1234\n
645 U.S.A.
647 3.3 Telecommunications Addressing Types
649 These types are concerned with information associated with the
650 telecommunications addressing of the object the vCard represents.
652 3.3.1 TEL Type Definition
654 To: ietf-mime-directory@imc.org
656 Subject: Registration of text/directory MIME type TEL
658 Type name: TEL
660 Type purpose: To specify the telephone number for telephony
661 communication with the object the vCard represents.
663 Type encoding: 8bit
665 Type value: A single phone-number value.
667 Type special notes: The value of this type is specified in a
668 canonical form in order to specify an unambiguous representation of
669 the globally unique telephone endpoint. This type is based on the
670 X.500 Telephone Number attribute.
672 The type may include the type parameter "TYPE" to specify intended
673 use for the telephone number. The TYPE parameter values may include:
674 "home" to indicate a telephone number associated with a residence,
675 "msg" to indicate the telephone number has voice messaging support,
676 "work" to indicate a telephone number associated with a place of
677 work, "pref" to indicate a preferred-use telephone number, "voice" to
678 indicate a voice telephone number, "fax" to indicate a facsimile
679 telephone number, "cell" to indicate a cellular telephone number,
680 "video" to indicate a video conferencing telephone number, "pager" to
681 indicate a paging device telephone number, "bbs" to indicate a
682 bulletin board system telephone number, "modem" to indicate a MODEM
683 connected telephone number, "car" to indicate a car-phone telephone
684 number, "isdn" to indicate an ISDN service telephone number, "pcs" to
685 indicate a personal communication services telephone number. The
686 default type is "voice". These type parameter values may specified as
687 a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list
688 (i.e., "TYPE=work,voice"). The default may be overridden to another
689 set of values by specifying one or more alternate values. For
690 example, the default TYPE of "voice" can be reset to a WORK and HOME,
691 VOICE and FAX telephone number by the value list
692 "TYPE=work,home,voice,fax".
694 Type example:
696 TEL;TYPE=work,voice,pref,msg:+1-213-555-1234
698 Dawson & Howes [Page 13] October 1998
699 vCard MIME Directory Profile
701 3.3.2 EMAIL Type Definition
703 To: ietf-mime-directory@imc.org
705 Subject: Registration of text/directory MIME type EMAIL
707 Type name: EMAIL
709 Type purpose: To specify the electronic mail address for
710 communication with the object the vCard represents.
712 Type encoding: 8bit
714 Type value: A single text value.
716 Type special notes: The type may include the type parameter "TYPE" to
717 specify the format or preference of the electronic mail address. The
718 TYPE parameter values may include: "internet" to indicate an Internet
719 addressing type, "x400" to indicate a X.400 addressing type or "pref"
720 to indicate a preferred-use email address when more than one is
721 specified. Another IANA registered address type may also be
722 specified. The default email type is "internet". A non-standard value
723 may also be specified.
725 Type example:
727 EMAIL;TYPE=internet:jqpublic@xyz.dom1.com
729 EMAIL;TYPE=internet:jdoe@isp.net
731 EMAIL;TYPE=internet,pref:jane_doe@abc.com
733 3.3.3 MAILER Type Definition
735 To: ietf-mime-directory@imc.org
737 Subject: Registration of text/directory MIME type MAILER
739 Type name: MAILER
741 Type purpose: To specify the type of electronic mail software that is
742 used by the individual associated with the vCard.
744 Type encoding: 8bit
746 Type value: A single text value.
748 Type special notes: This information may provide assistance to a
749 correspondent regarding the type of data representation which can be
750 used, and how they may be packaged. This property is based on the
751 private MIME type X-Mailer that is generally implemented by MIME user
752 agent products.
754 Type example:
756 Dawson & Howes [Page 14] October 1998
757 vCard MIME Directory Profile
759 MAILER:PigeonMail 2.1
761 3.4 Geographical Types
763 These types are concerned with information associated with
764 geographical positions or regions associated with the object the
765 vCard represents.
767 3.4.1 TZ Type Definition
769 To: ietf-mime-directory@imc.org
771 Subject: Registration of text/directory MIME type TZ
773 Type name: TZ
775 Type purpose: To specify information related to the time zone of the
776 object the vCard represents.
778 Type encoding: 8bit
780 Type value: The default is a single utc-offset value. It may also be
781 reset to a single text value.
783 Type special notes: The type value consists of a single value.
785 Type examples:
787 TZ:-05:00
789 TZ;VALUE=text:-05:00; EST; Raleigh/North America
790 ;This example has a single value, not a structure text value.
792 3.4.2 GEO Type Definition
794 To: ietf-mime-directory@imc.org
796 Subject: Registration of text/directory MIME type GEO
798 Type name: GEO
800 Type purpose: To specify information related to the global
801 positioning of the object the vCard represents.
803 Type encoding: 8bit
805 Type value: A single structured value consisting of two float values
806 separated by the SEMI-COLON character (ASCII decimal 59).
808 Type special notes: This type specifies information related to the
809 global position of the object associated with the vCard. The value
810 specifies latitude and longitude, in that order (i.e., "LAT LON"
811 ordering). The longitude represents the location east and west of the
812 prime meridian as a positive or negative real number, respectively.
814 Dawson & Howes [Page 15] October 1998
815 vCard MIME Directory Profile
817 The latitude represents the location north and south of the equator
818 as a positive or negative real number, respectively. The longitude
819 and latitude values MUST be specified as decimal degrees and should
820 be specified to six decimal places. This will allow for granularity
821 within a meter of the geographical position. The text components are
822 separated by the SEMI-COLON character (ASCII decimal 59). The simple
823 formula for converting degrees-minutes-seconds into decimal degrees
824 is:
826 decimal = degrees + minutes/60 + seconds/3600.
828 Type example:
830 GEO:37.386013;-122.082932
832 3.5 Organizational Types
834 These types are concerned with information associated with
835 characteristics of the organization or organizational units of the
836 object the vCard represents.
838 3.5.1 TITLE Type Definition
840 To: ietf-mime-directory@imc.org
842 Subject: Registration of text/directory MIME type TITLE
844 Type name: TITLE
846 Type purpose: To specify the job title, functional position or
847 function of the object the vCard represents.
849 Type encoding: 8bit
851 Type value: A single text value.
853 Type special notes: This type is based on the X.520 Title attribute.
855 Type example:
857 TITLE:Director\, Research and Development
859 3.5.2 ROLE Type Definition
861 To: ietf-mime-directory@imc.org
863 Subject: Registration of text/directory MIME type ROLE
865 Type name: ROLE
867 Type purpose: To specify information concerning the role, occupation,
868 or business category of the object the vCard represents.
870 Type encoding: 8bit
872 Dawson & Howes [Page 16] October 1998
873 vCard MIME Directory Profile
875 Type value: A single text value.
877 Type special notes: This type is based on the X.520 Business Category
878 explanatory attribute. This property is included as an organizational
879 type to avoid confusion with the semantics of the TITLE type and
880 incorrect usage of that type when the semantics of this type is
881 intended.
883 Type example:
885 ROLE:Programmer
887 3.5.3 LOGO Type Definition
889 To: ietf-mime-directory@imc.org
891 Subject: Registration of text/directory MIME type LOGO
893 Type name: LOGO
895 Type purpose: To specify a graphic image of a logo associated with
896 the object the vCard represents.
898 Type encoding: The encoding MUST be reset to "b" using the ENCODING
899 parameter in order to specify inline, encoded binary data. If the
900 value is referenced by a URI value, then the default encoding of 8bit
901 is used and no explicit ENCODING parameter is needed.
903 Type value: A single value. The default is binary value. It may also
904 be reset to uri value. The uri value may be used to specify a value
905 outside of this MIME entity.
907 Type special notes: The type MAY include the type parameter "TYPE" to
908 specify the graphic image format type. The TYPE parameter values MUST
909 be one of the IANA registered image formats or a non-standard image
910 format.
912 Type example:
914 LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg
916 LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
917 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
918 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
919 <...the remainder of "B" encoded binary data...>
921 3.5.4 AGENT Type Definition
923 To: ietf-mime-directory@imc.org
925 Subject: Registration of text/directory MIME type AGENT
927 Type name: AGENT
929 Dawson & Howes [Page 17] October 1998
930 vCard MIME Directory Profile
932 Type purpose: To specify information about another person who will
933 act on behalf of the individual or resource associated with the
934 vCard.
936 Type encoding: 8-bit
938 Type value: The default is a single vcard value. It may also be reset
939 to either a single text or uri value. The text value may be used to
940 specify textual information. The uri value may be used to specify
941 information outside of this MIME entity.
943 Type special notes: This type typically is used to specify an area
944 administrator, assistant, or secretary for the individual associated
945 with the vCard. A key characteristic of the Agent type is that it
946 represents somebody or something that is separately addressable.
948 Type example:
950 AGENT;VALUE=uri:
951 CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
953 AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555-
954 1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\n
956 3.5.5 ORG Type Definition
958 To: ietf-mime-directory@imc.org
960 Subject: Registration of text/directory MIME type ORG
962 Type name: ORG
964 Type purpose: To specify the organizational name and units associated
965 with the vCard.
967 Type encoding: 8bit
969 Type value: A single structured text value consisting of components
970 separated the SEMI-COLON character (ASCII decimal 59).
972 Type special notes: The type is based on the X.520 Organization Name
973 and Organization Unit attributes. The type value is a structured type
974 consisting of the organization name, followed by one or more levels
975 of organizational unit names.
977 Type example: A type value consisting of an organizational name,
978 organizational unit #1 name and organizational unit #2 name.
980 ORG:ABC\, Inc.;North American Division;Marketing
982 3.6 Explanatory Types
984 These types are concerned with additional explanations, such as that
985 related to informational notes or revisions specific to the vCard.
987 Dawson & Howes [Page 18] October 1998
988 vCard MIME Directory Profile
990 3.6.1 CATEGORIES Type Definition
992 To: ietf-mime-directory@imc.org
994 Subject: Registration of text/directory MIME type CATEGORIES
996 Type name: CATEGORIES
998 Type purpose: To specify application category information about the
999 vCard.
1001 Type encoding: 8bit
1003 Type value: One or more text values separated by a COMMA character
1004 (ASCII decimal 44).
1006 Type example:
1008 CATEGORIES:TRAVEL AGENT
1010 CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
1012 3.6.2 NOTE Type Definition
1014 To: ietf-mime-directory@imc.org
1016 Subject: Registration of text/directory MIME type NOTE
1018 Type name: NOTE
1020 Type purpose: To specify supplemental information or a comment that
1021 is associated with the vCard.
1023 Type encoding: 8bit
1025 Type value: A single text value.
1027 Type special notes: The type is based on the X.520 Description
1028 attribute.
1030 Type example:
1032 NOTE:This fax number is operational 0800 to 1715
1033 EST\, Mon-Fri.
1035 3.6.3 PRODID Type Definition
1037 To: ietf-mime-directory@imc.org
1039 Subject: Registration of text/directory MIME type PRODID
1041 Type name: PRODID
1043 Dawson & Howes [Page 19] October 1998
1044 vCard MIME Directory Profile
1046 Type purpose: To specify the identifier for the product that created
1047 the vCard object.
1049 Type encoding: 8-bit
1051 Type value: A single text value.
1053 Type special notes: Implementations SHOULD use a method such as that
1054 specified for Formal Public Identifiers in ISO 9070 to assure that
1055 the text value is unique.
1057 Type example:
1059 PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
1061 3.6.4 REV Type Definition
1063 To: ietf-mime-directory@imc.org
1065 Subject: Registration of text/directory MIME type REV
1067 Type name: REV
1069 Type purpose: To specify revision information about the current
1070 vCard.
1072 Type encoding: 8-bit
1074 Type value: The default is a single date-time value. May also be
1075 reset to a single date value.
1077 Type special notes: The value distinguishes the current revision of
1078 the information in this vCard for other renditions of the
1079 information.
1081 Type example:
1083 REV:1995-10-31T22:27:10Z
1085 REV:1997-11-15
1087 3.6.5 SORT-STRING Type Definition
1089 To: ietf-mime-directory@imc.org
1091 Subject: Registration of text/directory MIME type SORT-STRING
1093 Type Name: SORT-STRING
1095 Type purpose: To specify the text to be used in national language
1096 specific sorting of the values specified by the FN or N types.
1098 Type encoding: 8bit
1100 Dawson & Howes [Page 20] October 1998
1101 vCard MIME Directory Profile
1103 Type value: A single text value.
1105 Type special notes: The sort string is used to provide text that is
1106 to be used in locale- or national language-specific sorting of the
1107 values for the formatted name or structured name types. Without this
1108 information, sorting algorithms may incorrectly sort this vCard
1109 within a sequence of sorted vCards. If this type is present in a
1110 vCard, then this value should be used for sorting the vCard, instead
1111 of the values of the FN or N types.
1113 Type example: The following would define the sort string "Harten" for
1114 the "FN:Rene J. van der Harten" or "N:van der
1115 Harten;Rene;J.;Sir;R.D.O.N.".
1117 SORT-STRING:Harten
1119 3.6.6 SOUND Type Definition
1121 To: ietf-mime-directory@imc.org
1123 Subject: Registration of text/directory MIME type SOUND
1125 Type name: SOUND
1127 Type purpose: To specify a digital sound content information that
1128 annotates some aspect of the vCard. By default this type is used to
1129 specify the proper pronunciation of the name type value of the vCard.
1131 Type encoding: The encoding MUST be reset to "b" using the ENCODING
1132 parameter in order to specify inline, encoded binary data. If the
1133 value is referenced by a URI value, then the default encoding of 8bit
1134 is used and no explicit ENCODING parameter is needed.
1136 Type value: A single value. The default is binary value. It may also
1137 be reset to uri value. The uri value may be used to specify a value
1138 outside of this MIME entity.
1140 Type special notes: The type MAY include the type parameter "TYPE" to
1141 specify the audio format type. The TYPE parameter values MUST be one
1142 of the IANA registered audio formats or a non-standard audio format.
1144 Type example:
1146 SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
1147 19960229T080000.xyzMail@host1.com
1149 SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
1150 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
1151 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
1152 <...the remainder of "B" encoded binary data...>
1154 3.6.7 UID Type Definition
1156 To: ietf-mime-directory@imc.org
1158 Dawson & Howes [Page 21] October 1998
1159 vCard MIME Directory Profile
1161 Subject: Registration of text/directory MIME type UID
1163 Type name: UID
1165 Type purpose: To specify a value that represents a globally unique
1166 identifier corresponding to the individual or resource associated
1167 with the vCard.
1169 Type encoding: 8bit
1171 Type value: A single text value.
1173 Type special notes: The type is used to uniquely identify the object
1174 that the vCard represents.
1176 The type may include the type parameter "TYPE" to specify the format
1177 of the identifier. The TYPE parameter value may be any IANA
1178 registered identifier format. The value may also be a non-standard
1179 format.
1181 Type example:
1183 UID:19950401-080045-40000F192713-0052
1185 3.6.8 URL Type Definition
1187 To: ietf-mime-directory@imc.org
1189 Subject: Registration of text/directory MIME type URL
1191 Type name: URL
1193 Type purpose: To specify a uniform resource locator associated with
1194 the object that the vCard refers to.
1196 Type encoding: 8bit
1198 Type value: A single uri value.
1200 Type example:
1202 URL:http://www.swbyps.restaurant.french/~chezchic.html
1204 3.6.9 VERSION Type Definition
1206 To: ietf-mime-directory@imc.org
1208 Subject: Registration of text/directory MIME type VERSION
1210 Type name: VERSION
1212 Type purpose: To specify the version of the vCard specification used
1213 to format this vCard.
1215 Dawson & Howes [Page 22] October 1998
1216 vCard MIME Directory Profile
1218 Type encoding: 8bit
1220 Type value: A single text value.
1222 Type special notes: The property MUST be present in the vCard object.
1223 The value MUST be "3.0" if the vCard corresponds to this
1224 specification.
1226 Type example:
1228 VERSION:3.0
1230 3.7 Security Types
1232 These types are concerned with the security of communication pathways
1233 or access to the vCard.
1235 3.7.1 CLASS Type Definition
1237 To: ietf-mime-directory@imc.org
1239 Subject: Registration of text/directory MIME type CLASS
1241 Type name: CLASS
1243 Type purpose: To specify the access classification for a vCard
1244 object.
1246 Type encoding: 8bit
1248 Type value: A single text value.
1250 Type special notes: An access classification is only one component of
1251 the general security model for a directory service. The
1252 classification attribute provides a method of capturing the intent of
1253 the owner for general access to information described by the vCard
1254 object.
1256 Type examples:
1258 CLASS:PUBLIC
1260 CLASS:PRIVATE
1262 CLASS:CONFIDENTIAL
1264 3.7.2 KEY Type Definition
1266 To: ietf-mime-directory@imc.org
1268 Subject: Registration of text/directory MIME type KEY
1270 Type name: KEY
1272 Dawson & Howes [Page 23] October 1998
1273 vCard MIME Directory Profile
1275 Type purpose: To specify a public key or authentication certificate
1276 associated with the object that the vCard represents.
1278 Type encoding: The encoding MUST be reset to "b" using the ENCODING
1279 parameter in order to specify inline, encoded binary data. If the
1280 value is a text value, then the default encoding of 8bit is used and
1281 no explicit ENCODING parameter is needed.
1283 Type value: A single value. The default is binary. It may also be
1284 reset to text value. The text value may be used to specify a text
1285 key.
1287 Type special notes: The type may also include the type parameter TYPE
1288 to specify the public key or authentication certificate format. The
1289 parameter type may specify any IANA registered public key or
1290 authentication certificate format. The parameter type may also
1291 specify a non-standard format.
1293 Type example:
1295 KEY;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
1296 wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
1297 Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
1298 ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
1299 E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
1300 VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
1301 MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
1302 Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
1303 EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
1304 dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
1305 EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
1306 +hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
1307 mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
1308 rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
1309 UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
1311 3.8 Extended Types
1313 The types defined by this document can be extended with private types
1314 using the non-standard, private values mechanism defined in [RFC
1315 2045]. Non-standard, private types with a name starting with "X-" may
1316 be defined bilaterally between two cooperating agents without outside
1317 registration or standardization.
1319 4. Formal Grammar
1321 The following formal grammar is provided to assist developers in
1322 building parsers for the vCard.
1324 This syntax is written according to the form described in RFC 2234,
1325 but it references just this small subset of RFC 2234 literals:
1327 Dawson & Howes [Page 24] October 1998
1328 vCard MIME Directory Profile
1330 ;*******************************************
1331 ; Commonly Used Literal Definition
1332 ;*******************************************
1334 ALPHA = %x41-5A / %x61-7A
1335 ; Latin Capital Letter A-Latin Capital Letter Z /
1336 ; Latin Small Letter a-Latin Small Letter z
1338 CHAR = %x01-7F
1339 ; Any C0 Controls and Basic Latin, excluding NULL from
1340 ; Code Charts, pages 7-6 through 7-9 in [UNICODE]
1342 CR = %x0D
1343 ; Carriage Return
1345 LF = %0A
1346 ; Line Feed
1348 CRLF = CR LF
1349 ; Internet standard newline
1351 ;CTL = %x00-1F / %x7F
1352 ; Controls. Not used, but referenced in comments.
1354 DIGIT = %x30-39
1355 ; Digit Zero-Digit Nine
1357 DQUOTE = %x22
1358 ; Quotation Mark
1360 HTAB = %x09
1361 ; Horizontal Tabulation
1363 SP = %x20
1364 ; space
1366 VCHAR = %x21-7E
1367 ; Visible (printing) characters
1369 WSP = SP / HTAB
1370 ; White Space
1372 ;*******************************************
1373 ; Basic vCard Definition
1374 ;*******************************************
1376 vcard_entity = 1*(vcard)
1378 vcard = [group "."] "BEGIN" ":" "VCARD" 1*CRLF
1379 1*(contentline)
1380 ;A vCard object MUST include the VERSION, FN and N types.
1381 [group "."] "END" ":" "VCARD" 1*CRLF
1383 Dawson & Howes [Page 25] October 1998
1384 vCard MIME Directory Profile
1386 contentline = [group "."] name *(";" param ) ":" value CRLF
1387 ; When parsing a content line, folded lines must first
1388 ; be unfolded according to the unfolding procedure
1389 ; described above. When generating a content line, lines
1390 ; longer than 75 characters SHOULD be folded according to
1391 ; the folding procedure described above.
1393 group = 1*(ALPHA / DIGIT / "-")
1395 name = iana-token / x-name
1396 ; Parsing of the param and value is
1397 ; based on the "name" or type identifier
1398 ; as defined in ABNF sections below
1400 iana-token = 1*(ALPHA / DIGIT / "-")
1401 ; vCard type or parameter identifier registered with IANA
1403 x-name = "X-" 1*(ALPHA / DIGIT / "-")
1404 ; Reserved for non-standard use
1406 param = param-name "=" param-value *("," param-value)
1408 param-name = iana-token / x-name
1410 param-value = ptext / quoted-string
1412 ptext = *SAFE-CHAR
1414 value = *VALUE-CHAR
1416 quoted-string = DQUOTE QSAFE-CHAR DQUOTE
1418 NON-ASCII = %x80-FF
1419 ; Use is restricted by CHARSET parameter
1420 ; on outer MIME object (UTF-8 preferred)
1422 QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII
1423 ; Any character except CTLs, DQUOTE
1425 SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
1426 ; Any character except CTLs, DQUOTE, ";", ":", ","
1428 VALUE-CHAR = WSP / VCHAR / NON-ASCII
1429 ; Any textual character
1431 ;*******************************************
1432 ; vCard Type Definition
1433 ;
1434 ; Provides type-specific definitions for how the
1435 ; "value" and "param" are defined.
1436 ;*******************************************
1438 Dawson & Howes [Page 26] October 1998
1439 vCard MIME Directory Profile
1441 ;For name="NAME"
1442 param = ""
1443 ; No parameters allowed
1445 value = text-value
1447 ;For name="PROFILE"
1448 param = ""
1449 ; No parameters allowed
1451 value = text-value
1452 ; Value MUST be the case insensitive value "VCARD
1454 ;For name="SOURCE"
1455 param = source-param
1456 ; No parameters allowed
1458 value = uri
1460 source-param = ("VALUE" "=" "uri")
1461 / ("CONTEXT" "=" "word")
1462 ; Parameter value specifies the protocol context
1463 ; for the uri value.
1464 / (x-name "=" *SAFE-CHAR)
1466 ;For name="FN"
1467 ;This type MUST be included in a vCard object.
1468 param = text-param
1469 ; Text parameters allowed
1471 value = text-value
1473 ;For name="N"
1474 ;This type MUST be included in a vCard object.
1475 param = text-param
1476 ; Text parameters allowed
1478 value = n-value
1480 n-value = 0*4(text-value *("," text-value) ";")
1481 text-value *("," text-value)
1482 ; Family; Given; Middle; Prefix; Suffix.
1483 ; Example: Public;John;Quincy,Adams;Reverend Dr. III
1485 ;For name="NICKNAME"
1486 param = text-param
1487 ; Text parameters allowed
1489 value = text-list
1491 ;For name="PHOTO"
1492 param = img-inline-param
1493 ; Only image parameters allowed
1495 Dawson & Howes [Page 27] October 1998
1496 vCard MIME Directory Profile
1498 param =/ img-refer-param
1499 ; Only image parameters allowed
1501 value = img-inline-value
1502 ; Value and parameter MUST match
1504 value =/ img-refer-value
1505 ; Value and parameter MUST match
1507 ;For name="BDAY"
1508 param = ("VALUE" "=" "date")
1509 ; Only value parameter allowed
1511 param =/ ("VALUE" "=" "date-time")
1512 ; Only value parameter allowed
1514 value = date-value
1515 ; Value MUST match value type
1517 value =/ date-time-value
1518 ; Value MUST match value type
1520 ;For name="ADR"
1521 param = adr-param / text-param
1522 ; Only adr and text parameters allowed
1524 value = adr-value
1526 ;For name="LABEL"
1527 param = adr-param / text-param
1528 ; Only adr and text parameters allowed
1530 value = text-value
1532 ;For name="TEL"
1533 param = tel-param
1534 ; Only tel parameters allowed
1536 value = phone-number-value
1538 tel-param = "TYPE" "=" tel-type *("," tel-type)
1540 tel-type = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG"
1541 / "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN"
1542 / "VIDEO" / "PCS" / iana-token / x-name
1543 ; Values are case insensitive
1545 ;For name="EMAIL"
1546 param = email-param
1547 ; Only email parameters allowed
1549 value = text-value
1551 Dawson & Howes [Page 28] October 1998
1552 vCard MIME Directory Profile
1554 email-param = "TYPE" "=" email-type ["," "PREF"]
1555 ; Value is case insensitive
1557 email-type = "INTERNET" / "X400" / iana-token / "X-" word
1558 ; Values are case insensitive
1560 ;For name="MAILER"
1561 param = text-param
1562 ; Only text parameters allowed
1564 value = text-value
1566 ;For name="TZ"
1567 param = ""
1568 ; No parameters allowed
1570 value = utc-offset-value
1572 ;For name="GEO"
1573 param = ""
1574 ; No parameters allowed
1576 value = float-value ";" float-value
1578 ;For name="TITLE"
1579 param = text-param
1580 ; Only text parameters allowed
1582 value = text-value
1584 ;For name="ROLE"
1585 param = text-param
1586 ; Only text parameters allowed
1588 value = text-value
1590 ;For name="LOGO"
1591 param = img-inline-param / img-refer-param
1592 ; Only image parameters allowed
1594 value = img-inline-value / img-refer-value
1595 ; Value and parameter MUST match
1597 ;For name="AGENT"
1598 param = agent-inline-param
1600 param =/ agent-refer-param
1602 value = agent-inline-value
1603 ; Value and parameter MUST match
1605 value =/ agent-refer-value
1606 ; Value and parameter MUST match
1608 Dawson & Howes [Page 29] October 1998
1609 vCard MIME Directory Profile
1611 agent-inline-param = ""
1612 ; No parameters allowed
1614 agent-refer-param = "VALUE" "=" "uri"
1615 ; Only value parameter allowed
1617 agent-inline-value = text-value
1618 ; Value MUST be a valid vCard object
1620 agent-refer-value = uri
1621 ; URI MUST refer to image content of given type
1623 ;For name="ORG"
1625 param = text-param
1626 ; Only text parameters allowed
1628 value = org-value
1630 org-value = *(text-value ";") text-value
1631 ; First is Organization Name, remainder are Organization Units.
1633 ;For name="CATEGORIES"
1634 param = text-param
1635 ; Only text parameters allowed
1637 value = text-list
1639 ;For name="NOTE"
1640 param = text-param
1641 ; Only text parameters allowed
1643 value = text-value
1645 ;For name="PRODID"
1646 param = ""
1647 ; No parameters allowed
1649 value = text-value
1651 ;For name="REV"
1652 param = ["VALUE" =" "date-time"]
1653 ; Only value parameters allowed. Values are case insensitive.
1655 param =/ "VALUE" =" "date"
1656 ; Only value parameters allowed. Values are case insensitive.
1658 value = date-time-value
1660 value =/ date-value
1662 ;For name="SORT-STRING"
1663 param = text-param
1664 ; Only text parameters allowed
1666 Dawson & Howes [Page 30] October 1998
1667 vCard MIME Directory Profile
1669 value = text-value
1671 ;For name="SOUND"
1672 param = snd-inline-param
1673 ; Only sound parameters allowed
1675 param =/ snd-refer-param
1676 ; Only sound parameters allowed
1678 value = snd-line-value
1679 ; Value MUST match value type
1681 value =/ snd-refer-value
1682 ; Value MUST match value type
1684 snd-inline-value = binary-value CRLF
1685 ; Value MUST be "b" encoded audio content
1687 snd-inline-param = ("VALUE" "=" "binary"])
1688 / ("ENCODING" "=" "b")
1689 / ("TYPE" "=" *SAFE-CHAR)
1690 ; Value MUST be an IANA registered audio type
1692 snd-refer-value = uri
1693 ; URI MUST refer to audio content of given type
1695 snd-refer-param = ("VALUE" "=" "uri")
1696 / ("TYPE" "=" word)
1697 ; Value MUST be an IANA registered audio type
1699 ;For name="UID"
1700 param = ""
1701 ; No parameters allowed
1703 value = text-value
1705 ;For name="URL"
1706 param = ""
1707 ; No parameters allowed
1709 value = uri
1711 ;For name="VERSION"
1712 ;This type MUST be included in a vCard object.
1713 param = ""
1714 ; No parameters allowed
1716 value = text-value
1717 ; Value MUST be "3.0"
1719 ;For name="CLASS"
1720 param = ""
1721 ; No parameters allowed
1723 Dawson & Howes [Page 31] October 1998
1724 vCard MIME Directory Profile
1726 value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL"
1727 / iana-token / x-name
1728 ; Value are case insensitive
1730 ;For name="KEY"
1731 param = key-txt-param
1732 ; Only value and type parameters allowed
1734 param =/ key-bin-param
1735 ; Only value and type parameters allowed
1737 value = text-value
1739 value =/ binary-value
1741 key-txt-param = "TYPE" "=" keytype
1743 key-bin-param = ("TYPE" "=" keytype)
1744 / ("ENCODING" "=" "b")
1745 ; Value MUST be a "b" encoded key or certificate
1747 keytype = "X509" / "PGP" / iana-token / x-name
1748 ; Values are case insensitive
1750 ;For name="X-" non-standard type
1751 param = text-param / (x-name "=" param-value)
1752 ; Only text or non-standard parameters allowed
1754 value = text-value
1756 ;*******************************************
1757 ; vCard Commonly Used Parameter Definition
1758 ;*******************************************
1760 text-param = ("VALUE" "=" "ptext")
1761 / ("LANGUAGE" "=" langval)
1762 / (x-name "=" param-value)
1764 langval =
1766 img-inline-value = binary-value
1767 ;Value MUST be "b" encoded image content
1769 img-inline-param
1771 img-inline-param = ("VALUE" "=" "binary")
1772 / ("ENCODING" "=" "b")
1773 / ("TYPE" "=" param-value
1774 ;TYPE value MUST be an IANA registered image type
1776 img-refer-value = uri
1777 ;URI MUST refer to image content of given type
1779 Dawson & Howes [Page 32] October 1998
1780 vCard MIME Directory Profile
1782 img-refer-param = ("VALUE" "=" "uri")
1783 / ("TYPE" "=" param-value)
1784 ;TYPE value MUST be an IANA registered image type
1786 adr-param = ("TYPE" "=" adr-type *("," adr-type))
1787 / (text-param)
1789 adr-type = "dom" / "intl" / "postal" / "parcel" / "home"
1790 / "work" / "pref" / iana-type / x-name
1792 adr-value = 0*6(text-value ";") text-value
1793 ; PO Box, Extended Address, Street, Locality, Region, Postal
1794 ; Code, Country Name
1796 ;*******************************************
1797 ; vCard Type Value Definition
1798 ;*******************************************
1800 text-value-list = 1*text-value *("," 1*text-value)
1802 text-value = *(SAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
1804 ESCAPED-CHAR = "\\" / "\;" / "\," / "\n" / "\N")
1805 ; \\ encodes \, \n or \N encodes newline
1806 ; \; encodes ;, \, encodes ,
1808 binary-value =
1810 date-value =
1812 time-value =
1814 date-time-value =
1818 phone-number-value =
1821 uri-value =
1823 utc-offset-value = ("+" / "-") time-hour ":" time-minute
1824 time-hour = 2DIGIT ;00-23
1825 time-minute = 2DIGIT ;00-59
1827 5. Differences From vCard v2.1
1829 This specification has been reviewed by the IETF community. The
1830 review process introduced a number of differences from the [VCARD]
1831 version 2.1. These differences require that vCard objects conforming
1832 to this specification have a different version number than a vCard
1833 conforming to [VCARD]. The differences include the following:
1835 Dawson & Howes [Page 33] October 1998
1836 vCard MIME Directory Profile
1838 . The QUOTED-PRINTABLE inline encoding has been eliminated.
1839 Only the "B" encoding of [RFC 2047] is an allowed value for
1840 the ENCODING parameter.
1842 . The method for specifying CRLF character sequences in text
1843 type values has been changed. The CRLF character sequence in
1844 a text type value is specified with the backslash character
1845 sequence "\n" or "\N".
1847 . Any COMMA or SEMICOLON in a text type value must be backslash
1848 escaped.
1850 . VERSION value corresponding to this specification MUST be
1851 "3.0".
1853 . The [MIME-DIR] predefined types of SOURCE, NAME and PROFILE
1854 are allowed.
1856 . The [MIME-DIR] VALUE type parameter for value data typing is
1857 allowed. In addition, there are extensions made to these type
1858 values for additional value types used in this specification.
1860 . The [VCARD] CHARSET type parameter has been eliminated.
1861 Character set may only be specified on the CHARSET parameter
1862 on the Content-Type MIME header field.
1864 . The [VCARD] support for non-significant WSP character has
1865 been eliminated.
1867 . The "TYPE=" prefix to parameter values is required. In
1868 [VCARD] this was optional.
1870 . LOGO, PHOTO and SOUND multimedia formats MUST be either IANA
1871 registered types or non-standard types.
1873 . Inline binary content must be "B" encoded and folded. A blank
1874 line after the encoded binary content is no longer required.
1876 . TEL values may be identified as personal communication
1877 services telephone numbers with the PCS type parameter value.
1879 . The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types
1880 have been added.
1882 . The VERSION, N and FN types MUST be specified in a vCard.
1883 This identifies the version of the specification that the
1884 object was formatted to. It also assures that every vCard
1885 will include both a structured and formatted name that can be
1886 used to identify the object.
1888 6. Acknowledgements
1890 The many valuable comments contributed by members of the IETF ASID
1891 working group are gratefully acknowledged, as are the contributions
1893 Dawson & Howes [Page 34] October 1998
1894 vCard MIME Directory Profile
1896 by Roland Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce
1897 Johnston, Daniel Klaussen, Vinod Seraphin, Michelle Watkins. Chris
1898 Newman was especially helpful in navigating the intricacies of ABNF
1899 lore.
1901 7. Authors' Addresses
1903 BEGIN:vCard
1904 VERSION:3.0
1905 FN:Frank Dawson
1906 ORG:Lotus Development Corporation
1907 ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
1908 ;Raleigh;NC;27613-3502;U.S.A.
1909 TEL;TYPE=VOICE,MSG,WORK:+1-919-676-9515
1910 TEL;TYPE=FAX,WORK:+1-919-676-9564
1911 EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
1912 EMAIL;TYPE=INTERNET:fdawson@earthlink.net
1913 URL:http://home.earthlink.net/~fdawson
1914 END:vCard
1916 BEGIN:vCard
1917 VERSION:3.0
1918 FN:Tim Howes
1919 ORG:Netscape Communications Corp.
1920 ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View;
1921 CA; 94043;U.S.A.
1922 TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
1923 TEL;TYPE=FAX,WORK:+1-415-528-4164
1924 EMAIL;TYPE=INTERNET:howes@netscape.com
1925 END:vCard
1927 8. References
1929 The following documents are referenced by this work.
1931 [ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
1932 Information interchange - Representation of dates and times - The
1933 International Organization for Standardization, June, 1988.
1935 [ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
1936 interchange formats - Information interchange - Representation of
1937 dates and times - The International Organization for Standardization,
1938 May, 1991.
1940 [ISO 9070] ISO 9070, Information Processing - SGML support facilities
1941 - Registration Procedures for Public Text Owner Identifiers, April,
1942 1991.
1944 [CCITT E.163] Recommendation E.163 - Numbering Plan for The
1945 International Telephone Service, CCITT Blue Book, Fascicle II.2, pp.
1946 128-134, November, 1988.
1948 Dawson & Howes [Page 35] October 1998
1949 vCard MIME Directory Profile
1951 [CCITT X.121] Recommendation X.121 - International Numbering Plan for
1952 Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332,
1953 November, 1988.
1955 [CCITT X.520] Recommendation X.520 - The Directory - Selected
1956 Attribute Types, November 1988.
1958 [CCITT X.521] Recommendation X.521 - The Directory - Selected Object
1959 Classes, November 1988.
1961 [MIME-DIR] Howes, T., Smith, M., Dawson, F. "A MIME Content-Type for
1962 Directory Information", RFC xxxx, April 1998.
1964 [RFC 1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform
1965 Resource Locators (URL)", RFC 1738, December 1994.
1967 [RFC 1766] Alvestrand, H., "Tags for the Identification of
1968 Languages", March 1995.
1970 [RFC 1872] Levinson, E., "The MIME Multipart/Related Content-type,"
1971 RFC 1872, December 1995.
1973 [RFC 2045] Freed, N., Borenstein, N., "Multipurpose Internet Mail
1974 Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC
1975 2045, November 1996.
1977 [RFC 2046] Freed, N., Borenstein, N., "Multipurpose Internet Mail
1978 Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996.
1980 [RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) -
1981 Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
1982 November 1996.
1984 [RFC 2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet
1985 Mail Extensions (MIME) - Part Four: Registration Procedures", RFC
1986 2048, January 1997.
1988 [RFC 2119] "Key words for use in RFCs to Indicate Requirement
1989 Levels", RFC 2119, March 1997.
1991 [RFC 2234] Crocker, D., Overell, P., "Augmented BNF for Syntax
1992 Specifications: ABNF", RFC 2234, November 1997.
1994 [UNICODE] "The Unicode Standard - Version 2.0", The Unicode
1995 Consortium, July 1996.
1997 [VCARD] Internet Mail Consortium, "vCard - The Electronic Business
1998 Card Version 2.1", http://www.imc.org/pdi/vcard-21.txt, September 18,
1999 1996.
2001 9. Full Copyright Statement
2003 "Copyright (C) The Internet Society (date). All Rights Reserved.
2005 Dawson & Howes [Page 36] October 1998
2006 vCard MIME Directory Profile
2008 This document and translations of it MAY be copied and furnished to
2009 others, and derivative works that comment on or otherwise explain it
2010 or assist in its implementation MAY be prepared, copied, published
2011 and distributed, in whole or in part, without restriction of any
2012 kind, provided that the above copyright notice and this paragraph are
2013 included on all such copies and derivative works. However, this
2014 document itself MAY not be modified in any way, such as by removing
2015 the copyright notice or references to the Internet Society or other
2016 Internet organizations, except as needed for the purpose of
2017 developing Internet standards in which case the procedures for
2018 copyrights defined in the Internet Standards process MUST be
2019 followed, or as required to translate it into languages other than
2020 English.
2022 The limited permissions granted above are perpetual and will not be
2023 revoked by the Internet Society or its successors or assigns.
2025 This document and the information contained herein is provided on an
2026 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
2027 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
2028 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
2029 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
2030 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2032 Dawson & Howes [Page 37] October 1998