idnits 2.17.1
draft-ietf-asid-mime-vcard-05.txt:
-(1773): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(1798): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(1804): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
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.
== There are 16 instances of lines with non-ascii characters in the
document.
== No 'Intended status' indicated for this document; assuming Proposed
Standard
== The page length should not exceed 58 lines per page, but there was 37
longer pages, the longest (page 6) being 66 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 an Authors' Addresses Section.
** 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 1062 has weird spacing: '...de text that ...'
== Line 1745 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 exact meaning of the all-uppercase expression 'MAY NOT' is not
defined in RFC 2119. If it is intended as a requirements expression, it
should be rewritten using one of the combinations defined in RFC 2119;
otherwise it should not be all-uppercase.
== The expression 'MAY NOT', while looking like RFC 2119 requirements text,
is not defined in RFC 2119, and should not be used. Consider using 'MUST
NOT' instead (if that is what you mean).
Found 'MAY NOT' in this paragraph:
The predefined data type values specified in [MIME-DIR] MAY NOT be
repeated in COMMA separated value lists, unless specified by this
specification.
-- 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 1854, but no explicit
reference was found in the text
== Unused Reference: 'ISO 9070' is defined on line 1865, but no explicit
reference was found in the text
== Unused Reference: 'RFC 1738' is defined on line 1886, but no explicit
reference was found in the text
== Unused Reference: 'RFC 1766' is defined on line 1889, but no explicit
reference was found in the text
== Unused Reference: 'RFC 1872' is defined on line 1892, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2045' is defined on line 1895, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2046' is defined on line 1899, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2048' is defined on line 1906, but no explicit
reference was found in the text
== Unused Reference: 'RFC 2234' is defined on line 1913, 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: 17 errors (**), 0 flaws (~~), 17 warnings (==), 8 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-05.txt Tim Howes
5 March 8, 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 learn the current status of any Internet-Draft, please check the
22 "1id-abstracts.txt" listing contained in the Internet- Drafts Shadow
23 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
24 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
25 ftp.isi.edu (US West Coast).
27 Distribution of this memo is unlimited.
29 Copyright (C) The Internet Society 1997. All Rights Reserved.
31 Abstract
33 This memo defines the profile of the MIME Content-Type [MIME-DIR] for
34 directory information for a white-pages person object, based on a
35 vCard electronic business card. The profile definition is independent
36 of any particular directory service or protocol. The profile is
37 defined for representing and exchanging a variety of information
38 about an individual (e.g., formatted and structured name and delivery
39 addresses, email address, multiple telephone numbers, photograph,
40 logo, audio clips, etc.). The directory information used by this
41 profile is based on the attributes for the person object defined in
42 the X.520 and X.521 directory services recommendations. The profile
43 also provides the method for including a [VCARD] representation of a
44 white-pages directory entry within the MIME Content-Type defined by
45 the [MIME-DIR] document.
47 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
48 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
49 document are to be interopreted as described in [RFC 2119].
51 vCard MIME Directory Profile
53 Table of Contents
55 1. THE VCARD MIME DIRECTORY PROFILE REGISTRATION.......................4
57 2. MIME DIRECTORY FEATURES.............................................5
59 2.1 PREDEFINED TYPE USAGE............................................5
60 2.1.1 BEGIN and END Type............................................5
61 2.1.2 NAME Type.....................................................5
62 2.1.3 PROFILE Type..................................................6
63 2.1.4 SOURCE Type...................................................6
64 2.2 PREDEFINED TYPE PARAMETER USAGE..................................6
65 2.3 PREDEFINED VALUE TYPE USAGE......................................6
66 2.4 EXTENSIONS TO THE PREDEFINED VALUE TYPES.........................6
67 2.4.1 BINARY........................................................6
68 2.4.2 VCARD.........................................................7
69 2.4.3 PHONE-NUMBER..................................................7
70 2.4.4 UTC-OFFSET....................................................7
71 2.5 STRUCTURED TYPE VALUES...........................................7
72 2.6 LINE DELIMITING AND FOLDING......................................8
74 3. VCARD PROFILE FEATURES..............................................8
76 3.1 IDENTIFICATION TYPES.............................................8
77 3.1.1 FN Type Definition............................................8
78 3.1.2 N Type Definition.............................................8
79 3.1.3 NICKNAME Type Definition......................................9
80 3.1.4 PHOTO Type Definition........................................10
81 3.1.5 BDAY Type Definition.........................................10
82 3.2 DELIVERY ADDRESSING TYPES.......................................11
83 3.2.1 ADR Type Definition..........................................11
84 3.2.2 LABEL Type Definition........................................12
85 3.3 TELECOMMUNICATIONS ADDRESSING TYPES.............................13
86 3.3.1 TEL Type Definition..........................................13
87 3.3.2 EMAIL Type Definition........................................14
88 3.3.3 MAILER Type Definition.......................................14
89 3.4 GEOGRAPHICAL TYPES..............................................15
90 3.4.1 TZ Type Definition...........................................15
91 3.4.2 GEO Type Definition..........................................15
92 3.5 ORGANIZATIONAL TYPES............................................16
93 3.5.1 TITLE Type Definition........................................16
94 3.5.2 ROLE Type Definition.........................................16
95 3.5.3 LOGO Type Definition.........................................17
96 3.5.4 AGENT Type Definition........................................18
97 3.5.5 ORG Type Definition..........................................18
98 3.6 EXPLANATORY TYPES...............................................19
99 3.6.1 CATEGORIES Type Definition...................................19
100 3.6.2 NOTE Type Definition.........................................19
101 3.6.3 PRODID Type Definition.......................................20
102 3.6.4 REV Type Definition..........................................20
103 3.6.5 SORT-STRING Type Definition..................................21
104 3.6.6 SOUND Type Definition........................................21
105 3.6.7 UID Type Definition..........................................22
106 vCard MIME Directory Profile
108 3.6.8 URL Type Definition..........................................22
109 3.6.9 VERSION Type Definition......................................23
110 3.7 SECURITY TYPES..................................................23
111 3.7.1 CLASS Type Definition........................................23
112 3.7.2 KEY Type Definition..........................................24
113 3.8 EXTENDED TYPES..................................................25
115 4. FORMAL GRAMMAR.....................................................25
117 5. DIFFERENCES WITH VCARD V2.1........................................34
119 6. ACKNOWLEDGEMENTS...................................................35
121 7. AUTHORS?S ADDRESSES................................................35
123 8. REFERENCES.........................................................35
125 9. FULL COPYRIGHT STATEMENT...........................................37
126 vCard MIME Directory Profile
128 Overview
130 The [MIME-DIR] document defines a MIME Content-Type for holding
131 different kinds of directory information. The directory information
132 may be based on any of a number of directory schemas. This document
133 defines a [MIME-DIR] usage profile for conveying directory
134 information based on one such schema; that of the white-pages type of
135 person object.
137 The schema is based on the attributes for the person object defined
138 in the X.520 and X.521 directory services recommendations. The schema
139 has augmented the basic attributes defined in the X.500 series
140 recommendation in order to provide for an electronic representation
141 of the information commonly found on a paper business card. This
142 schema was first defined in the [VCARD] document. Hence, this [MIME-
143 DIR] profile is referred to as the vCard MIME Directory Profile.
145 A directory entry based on this usage profile can include traditional
146 directory, white-pages information such as the distinguished name
147 used to uniquely identify the entry, a formatted representation of
148 the name used for user-interface or presentation purposes, both the
149 structured and presentation form of the delivery address, various
150 telephone numbers and organizational information associated with the
151 entry. In addition, traditional paper business card information such
152 as an image of an organizational logo or identify photograph can be
153 included in this person object.
155 The vCard MIME Directory Profile also provides support for
156 representing other important information about the person associated
157 with the directory entry. For instance, the date of birth of the
158 person; an audio clip describing the pronunciation of the name
159 associated with the directory entry, or some other application of the
160 digital sound; longitude and latitude geo-positioning information
161 related to the person associated with the directory entry; date and
162 time that the directory information was last updated; annotations
163 often written on a business card; Uniform Resource Locators (URL) for
164 a website; public key information. The profile also provides support
165 for non-standard extensions to the schema. This provides the
166 flexibility for implementations to augment the current capabilities
167 of the profile in a standardized way. More information about this
168 electronic business card format can be found in [VCARD].
170 1. The vCard Mime Directory Profile Registration
172 This profile is identified by the following [MIME-DIR] registration
173 template information. Subsequent sections define the profile
174 definition.
176 To: ietf-mime-directory@imc.org
178 Subject: Registration of text/directory MIME profile VCARD
179 vCard MIME Directory Profile
181 Profile name: VCARD
183 Profile purpose: To hold person object or white-pages type of
184 directory information. The person schema captured in the directory
185 entries is that commonly found in an electronic business card.
187 Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN,
188 END.
190 Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
191 LANGUAGE, CONTEXT.
193 New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL,
194 MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE,
195 PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS, KEY
197 New parameters: TYPE
199 Profile special notes: The vCard object MUST contain the FN, N and
200 VERSION types. The type-grouping feature of [MIME-DIR] is supported
201 by this profile to group related vCard properties about a directory
202 entry. For example, vCard properties describing WORK or HOME related
203 characteristics MAY be grouped with a unique group label.
205 The profile permits the use of non-standard types (i.e., those
206 identified with the prefix string "X-") as a flexible method for
207 implementations to extend the functionality currently defined within
208 this profile.
210 2. MIME Directory Features
212 The vCard MIME Directory Profile makes use of many of the features
213 defined by [MIME-DIR]. The following sections either clarify or
214 extend the content-type definition of [MIME-DIR].
216 2.1 Predefined Type Usage
218 The vCard MIME Directory Profile uses the following predefined types
219 from [MIME-DIR].
221 2.1.1 BEGIN and END Type
223 The content entity MUST begin with the BEGIN type with a value of
224 "VCARD". The content entity MUST end with the END type with a value
225 of "VCARD".
227 2.1.2 NAME Type
229 If the NAME type appears within a MIME entity conforming to this
230 profile, it's value is the displayable, presentation text associated
231 with the source for the vCard, as specified in the SOURCE type.
233 vCard MIME Directory Profile
235 2.1.3 PROFILE Type
237 If the PROFILE type appears within a MIME entity conforming to this
238 profile, it?s value MUST be "VCARD".
240 2.1.4 SOURCE Type
242 If the SOURCE type appears within a MIME entity conforming to this
243 profile, it's value provides information how to find the source for
244 the vCard.
246 2.2 Predefined Type Parameter Usage
248 The vCard MIME Directory Profile uses the following predefined types
249 parameters as defined by [MIME-DIR].
251 � LANGUAGE
253 � ENCODING
255 � VALUE
257 2.3 Predefined VALUE Type Usage
259 The predefined data type values specified in [MIME-DIR] MAY NOT be
260 repeated in COMMA separated value lists, unless specified by this
261 specification.
263 2.4 Extensions To The Predefined VALUE Types
265 The predefined data type values specified in [MIME-DIR] have been
266 extended by the vCard profile to include a number of value types that
267 are specific to this profile.
269 2.4.1 BINARY
271 The "binary" value type specifies that the type value is inline,
272 encoded binary data. This value type may be specified in the PHOTO,
273 LOGO, SOUND, and KEY types.
275 If inline encoded binary data is specified, the ENCODING type
276 parameter MUST be used to specify the encoding format. The binary
277 data MUST be encoded using the "B" encoding format. Long lines of
278 encoded binary data may be folded using the folding method defined in
279 [MIME-DIR].
281 The value type is defined by the following notation:
283 binary =
284 vCard MIME Directory Profile
286 2.4.2 VCARD
288 The "vcard" value type specifies that the type value is another
289 vCard. This value type may be specified in the AGENT type. The value
290 type is defined by this specification. Since each of the type
291 declarations with in the vcard value type are being specified within
292 a type value themselves, they MUST be terminated with the backslash
293 escapement sequence "\n" or "\N", instead of the character sequence
294 CRLF. For example, with the AGENT type a value would be specified as
295 :
297 AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
298 TITLE:Area Administrator\, Assistant\n
299 EMAIL;INTERNET:jfriday@host.com\n
300 END:VCARD
302 2.4.3 PHONE-NUMBER
304 The "phone-number" value type specifies that the type value is a
305 telephone number. This value type may be specified in the TEL type.
306 The value type is a text value that has the special semantics of a
307 telephone number as defined in [CCITT E.163] and [CCITT X.121].
309 2.4.4 UTC-OFFSET
311 The "utc-offset" value type specifies that the type value is a signed
312 offset from UTC. This value type may be specified in the TZ type.
314 The value type is an offset from Coordinated Universal Time (UTC). It
315 is specified as a positive or negative difference in units of hours
316 and minutes (e.g., +hh:mm). The time is specified as a 24-hour clock.
317 Hour values are from 00 to 23, and minute values are from 00 to 59.
318 Hour and minutes are 2-digits with high order zeroes required to
319 maintain digit count. The extended format for ISO 8601 UTC offsets
320 MUST be used. The extended format makes use of a colon character as a
321 separator of the hour and minute text fields.
323 The value is defined by the following notation:
325 time-hour = 2DIGIT ;00-23
326 time-minute = 2DIGIT ;00-59
327 utc-offset = ("+" / "-") time-hour ":" time-minute
329 2.5 Structured Type Values
331 Compound type values are delimited by a field delimiter, specified by
332 the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a
333 component of a compound property value MUST be escaped with a
334 BACKSLASH character (ASCII decimal 92).
336 Lists of values are delimited by a list delimiter, specified by the
337 COMMA character (ASCII decimal 44). A COMMA character in a value MUST
338 be escaped with a BACKSLASH character (ASCII decimal 92).
340 vCard MIME Directory Profile
342 This profile supports the type grouping mechanism defined in [MIME-
343 DIR]. Grouping of related types is a useful technique to communicate
344 common semantics concerning the properties of a vCard.
346 2.6 Line Delimiting and Folding
348 This profile supports the same line delimiting and folding methods
349 defined in [MIME-DIR].
351 3. vCard Profile Features
353 The vCard MIME Directory Profile Type contains directory information,
354 typically pertaining to a single directory entry. The information is
355 described using an attribute schema that is tailored for capturing
356 personal contact information. The vCard can include attributes that
357 describe identification, delivery addressing, telecommunications
358 addressing, geographical, organizational, general explanatory and
359 security and access information about the particular object
360 associated with the vCard.
362 3.1 Identification Types
364 These types are used in the vCard profile to capture information
365 associated with the identification and naming of the person or
366 resource associated with the vCard.
368 3.1.1 FN Type Definition
370 To: ietf-mime-directory@imc.org
372 Subject: Registration of text/directory MIME type FN
374 Type name:FN
376 Type purpose: To specify the formatted text corresponding to the name
377 of the object the vCard represents.
379 Type encoding: 8bit
381 Type value: A single text value.
383 Type special notes: This type is based on the semantics of the X.520
384 Common Name attribute. The property MUST be present if the vCard
385 conforms to this specification.
387 Type example:
389 FN:Mr. John Q. Public, Esq.
391 3.1.2 N Type Definition
393 To: ietf-mime-directory@imc.org
394 vCard MIME Directory Profile
396 Subject: Registration of text/directory MIME type N
398 Type name: N
400 Type purpose: To specify the structured components of the name of the
401 object the vCard represents.
403 Type encoding: 8bit
405 Type value: A single structured text value. Each component may have
406 multiple values.
408 Type special note: The structured text value corresponds, in
409 sequence, to the Family Name, Given Name, Additional Names, Honorific
410 Prefixes, and Honorific Suffixes. The text components are separated
411 by the SEMI-COLON character (ASCII decimal 59) and possibly one or
412 more LWSP. Individual text components MAY include multiple text
413 values (e.g., multiple Additional Names), separated by the COMMA
414 character (ASCII decimal 44). This type is based on the semantics of
415 the X.520 individual name attributes. The property MUST be present in
416 the vCard object.
418 Type example:
420 N:Public;John;Quinlan;Mr.;Esq.
422 N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
424 3.1.3 NICKNAME Type Definition
426 To: ietf-mime-directory@imc.org
428 Subject: Registration of text/directory MIME type NICKNAME
430 Type name: NICKNAME
432 Type purpose: To specify the text corresponding to the nickname of
433 the object the vCard represents.
435 Type encoding: 8bit
437 Type value: One or more text values separated by a COMMA character
438 (ASCII decimal 44).
440 Type special note: The nickname is the descriptive name given instead
441 of or in addition to the one belonging to a person, place, or thing.
442 It may also be used to specify a familiar form of a proper name
443 specified by the FN or N types.
445 Type example:
447 NICKNAME:Robbie
448 vCard MIME Directory Profile
450 NICKNAME:Jim,Jimmie
452 3.1.4 PHOTO Type Definition
454 To: ietf-mime-directory@imc.org
456 Subject: Registration of text/directory MIME type PHOTO
458 Type name: PHOTO
460 Type purpose: To specify an image or photograph information that
461 annotates some aspect of the object the vCard represents.
463 Type encoding: The encoding MUST be reset to "b" using the ENCODING
464 parameter in order to specify inline, encoded binary data. If the
465 value is referenced by a URI value, then the default encoding of 8bit
466 is used and no explicit ENCODING parameter is needed.
468 Type value: A single value. The default is binary. It may also be
469 reset to uri. The uri value may be used to specify a value outside of
470 this MIME entity.
472 Type special notes: The type MAY include the type parameter "TYPE" to
473 specify the graphic image format type. The TYPE parameter values MUST
474 be one of the IANA registered image formats or a non-standard image
475 format.
477 Type example:
479 PHOTO;VALUE=uri:=http://www.abc.com/pub/photos
480 /jqpublic.gif
482 PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
483 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
484 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
485 <...remainder of "B" encoded binary data...>
487 3.1.5 BDAY Type Definition
489 To: ietf-mime-directory@imc.org
491 Subject: Registration of text/directory MIME type BDAY
493 Type name: BDAY
495 Type purpose: To specify the birth date of the object the vCard
496 represents.
498 Type encoding: 8bit
500 Type value: The default is a single date value. It may also be reset
501 to a single date-time value.
503 vCard MIME Directory Profile
505 Type examples:
507 BDAY:1996-04-15
509 BDAY:1953-10-15T23:10:00Z
511 BDAY:1987-09-27T08:30:00-06:00
513 3.2 Delivery Addressing Types
515 These types are concerned with information related to the delivery
516 addressing or label for the vCard object.
518 3.2.1 ADR Type Definition
520 To: ietf-mime-directory@imc.org
522 Subject: Registration of text/directory MIME type ADR
524 Type name: ADR
526 Type purpose: To specify the structured components of the delivery
527 address for the vCard object.
529 Type encoding: 8bit
531 Type value: A single structured text value, separated by the SEMI-
532 COLON character (ASCII decimal 59) and optionally one or more LWSP.
534 Type special notes: The structured text value consists of a sequence
535 of address components. The component values MUST be specified in
536 their corresponding position. The structured text value corresponds,
537 in sequence, to the post office box; the extended address; the street
538 address; the locality (e.g., city); the region (e.g., state or
539 province); the postal code; the country name. When a component value
540 is missing, the associated component separator MUST still be
541 specified.
543 The type may include the type parameter "TYPE" to specify the
544 delivery address type. The TYPE parameter values may include "dom" to
545 indicate a domestic delivery address; "intl" to indicate an
546 international delivery address; "postal" to indicate a postal
547 delivery address; "parcel" to indicate a parcel delivery address;
548 "home" to indicate a delivery address for a residence; "work" to
549 indicate delivery address for a place of work; and "pref" to indicate
550 the preferred delivery address when more than one address is
551 specified. These type parameter values may be specified as a
552 parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
553 (i.e., "TYPE=dom,postal"). This type is based on semantics of the
554 X.520 geographical and postal addressing attributes. The default is
555 "TYPE=intl,postal,parcel,work". The default can be overridden to some
556 other set of values by specifying one or more alternate values. For
557 example, the default can be reset to "TYPE=dom,postal,work,home" to
558 vCard MIME Directory Profile
560 specify a domestic delivery address for postal delivery to a
561 residence that is also used for work.
563 Type example: In this example the post office box and the extended
564 address are absent.
566 ADR;TYPE=dom,home,postal,parcel:;;123 Main
567 Street;Any Town;CA;91921-1234
569 3.2.2 LABEL Type Definition
571 To: ietf-mime-directory@imc.org
573 Subject: Registration of text/directory MIME type LABEL
575 Type name: LABEL
577 Type purpose: To specify the formatted text corresponding to delivery
578 address of the object the vCard represents.
580 Type encoding: 8bit
582 Type value: A single text value.
584 Type special notes: The type value is formatted text that may be used
585 to present a delivery address label for the vCard object. The type
586 may include the type parameter "TYPE" to specify delivery label type.
587 The TYPE parameter values may include "dom" to indicate a domestic
588 delivery label; "intl" to indicate an international delivery label;
589 "postal" to indicate a postal delivery label; "parcel" to indicate a
590 parcel delivery label; "home" to indicate a delivery label for a
591 residence; "work" to indicate delivery label for a place of work; and
592 "pref" to indicate the preferred delivery label when more than one
593 label is specified. These type parameter values may specified as a
594 parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
595 (i.e., "TYPE=dom,postal"). This type is based on semantics of the
596 X.520 geographical and postal addressing attributes. The default is
597 "TYPE=intl,postal,parcel,work". The default can be overridden to some
598 other set of values by specifying one or more alternate values. For
599 example, the default can be reset to "TYPE=intl,post,parcel,home" to
600 specify an international delivery label for both postal and parcel
601 delivery to a residential location.
603 Type example: A multi-line address label.
605 LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public, Esq.\n
606 Mail Drop: TNE QB\n
607 123 Main Street\n
608 Any Town, CA 91921-1234\n
609 U.S.A.
611 vCard MIME Directory Profile
613 3.3 Telecommunications Addressing Types
615 These types are concerned with information associated with the
616 telecommunications addressing of the object the vCard represents.
618 3.3.1 TEL Type Definition
620 To: ietf-mime-directory@imc.org
622 Subject: Registration of text/directory MIME type TEL
624 Type name: TEL
626 Type purpose: To specify the telephone number for telephony
627 communication with the object the vCard represents.
629 Type encoding: 8bit
631 Type value: A single phone-number.
633 Type special notes: The value of this type is specified in a
634 canonical form in order to specify an unambiguous representation of
635 the globally unique telephone endpoint. This type is based on the
636 X.500 Telephone Number attribute.
638 The type may include the type parameter "TYPE" to specify intended
639 use for the telephone number. The TYPE parameter values may include:
640 "home" to indicate a telephone number associated with a residence,
641 "msg" to indicate the telephone number has voice messaging support,
642 "work" to indicate a telephone number associated with a place of
643 work, "pref" to indicate a preferred-use telephone number, "voice" to
644 indicate a voice telephone number, "fax" to indicate a facsimile
645 telephone number, "cell" to indicate a cellular telephone number,
646 "video" to indicate a video conferencing telephone number, "pager" to
647 indicate a paging device telephone number, "bbs" to indicate a
648 bulletin board system telephone number, "modem" to indicate a MODEM
649 connected telephone number, "car" to indicate a car-phone telephone
650 number, "isdn" to indicate an ISDN service telephone number, "pcs" to
651 indicate a personal communication services telephone number. The
652 default type is "voice". These type parameter values may specified as
653 a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list
654 (i.e., "TYPE=work,voice"). The default may be overridden to another
655 set of values by specifying one or more alternate values. For
656 example, the default TYPE of "voice" can be reset to a WORK and HOME,
657 VOICE and FAX telephone number by the value list
658 "TYPE=work,home,voice,fax".
660 Type example:
662 TEL;TYPE=work,voice,pref,msg:+1-213-555-1234
663 vCard MIME Directory Profile
665 3.3.2 EMAIL Type Definition
667 To: ietf-mime-directory@imc.org
669 Subject: Registration of text/directory MIME type EMAIL
671 Type name: EMAIL
673 Type purpose: To specify the electronic mail address for
674 communication with the object the vCard represents.
676 Type encoding: 8bit
678 Type value: A single text value.
680 Type special notes: The type may include the type parameter "TYPE" to
681 specify the format or preference of the electronic mail address. The
682 TYPE parameter values may include: "internet" to indicate an Internet
683 addressing type, "x400" to indicate a X.400 addressing type or "pref"
684 to indicate a preferred-use email address when more than one is
685 specified. Another IANA registered address type may also be
686 specified. The default email type is "internet". A non-standard value
687 may also be specified.
689 Type example:
691 EMAIL;TYPE=internet:jqpublic@xyz.dom1.com
693 EMAIL;TYPE=internet:jdoe@isp.net
695 EMAIL;TYPE=internet,pref:jane_doe@abc.com
697 3.3.3 MAILER Type Definition
699 To: ietf-mime-directory@imc.org
701 Subject: Registration of text/directory MIME type MAILER
703 Type name: MAILER
705 Type purpose: To specify the type of electronic mail software that is
706 used by the individual associated with the vCard.
708 Type encoding: 8bit
710 Type value: A single text value.
712 Type special notes: This information may provide assistance to a
713 correspondent regarding the type of data representation which can be
714 used, and how they may be packaged. This property is based on the
715 private MIME type X-Mailer that is generally implemented by MIME user
716 agent products.
718 vCard MIME Directory Profile
720 Type example:
722 MAILER:PigeonMail 2.1
724 3.4 Geographical Types
726 These types are concerned with information associated with
727 geographical positions or regions associated with the object the
728 vCard represents.
730 3.4.1 TZ Type Definition
732 To: ietf-mime-directory@imc.org
734 Subject: Registration of text/directory MIME type TZ
736 Type name: TZ
738 Type purpose: To specify information related to the time zone of the
739 object the vCard represents.
741 Type encoding: 8bit.
743 Type value: The default is a single utc-offset value. It may also be
744 reset to a single text value.
746 Type special notes: The type value consists of a single value.
748 Type examples:
750 TZ:-05:00
752 TZ;VALUE=text:-05:00; EST; Raleigh/North America
753 ;This example has a single value, not a structure text value.
755 3.4.2 GEO Type Definition
757 To: ietf-mime-directory@imc.org
759 Subject: Registration of text/directory MIME type GEO
761 Type name: GEO
763 Type purpose: To specify information related to the global
764 positioning of the object the vCard represents.
766 Type encoding: 8bit.
768 Type value: Two float values separated by the SEMI-COLON character
769 (ASCII decimal 59).
771 Type special notes: This type specifies information related to the
772 global position of the object associated with the vCard. The value
773 vCard MIME Directory Profile
775 specifies latitude and longitude, in that order (i.e., "LAT LON"
776 ordering). The longitude represents the location east and west of the
777 prime meridian as a positive or negative real number, respectively.
778 The latitude represents the location north and south of the equator
779 as a positive or negative real number, respectively. The longitude
780 and latitude values MUST be specified as decimal degrees and should
781 be specified to six decimal places. This will allow for granularity
782 within a meter of the geographical position. The text components are
783 separated by the SEMI-COLON character (ASCII decimal 59). The simple
784 formula for converting degrees-minutes-seconds into decimal degrees
785 is:
787 decimal = degrees + minutes/60 + seconds/3600.
789 Type example:
791 GEO:37.386013;-122.082932
793 3.5 Organizational Types
795 These types are concerned with information associated with
796 characteristics of the organization or organizational units of the
797 object the vCard represents.
799 3.5.1 TITLE Type Definition
801 To: ietf-mime-directory@imc.org
803 Subject: Registration of text/directory MIME type TITLE
805 Type name: TITLE
807 Type purpose: To specify the job title, functional position or
808 function of the object the vCard represents.
810 Type encoding: 8bit
812 Type value: A single text value.
814 Type special notes: This type is based on the X.520 Title attribute.
816 Type example:
818 TITLE:Director, Research and Development
820 3.5.2 ROLE Type Definition
822 To: ietf-mime-directory@imc.org
824 Subject: Registration of text/directory MIME type ROLE
826 Type name: ROLE
827 vCard MIME Directory Profile
829 Type purpose: To specify information concerning the role, occupation,
830 or business category of the object the vCard represents.
832 Type encoding: 8bit
834 Type value: A single text value.
836 Type special notes: This type is based on the X.520 Business Category
837 explanatory attribute. This property is included as an organizational
838 type to avoid confusion with the semantics of the TITLE type and
839 incorrect usage of that type when the semantics of this type is
840 intended.
842 Type example:
844 ROLE:Programmer
846 3.5.3 LOGO Type Definition
848 To: ietf-mime-directory@imc.org
850 Subject: Registration of text/directory MIME type LOGO
852 Type name: LOGO
854 Type purpose: To specify a graphic image of a logo associated with
855 the object the vCard represents.
857 Type encoding: The encoding MUST be reset to "b" using the ENCODING
858 parameter in order to specify inline, encoded binary data. If the
859 value is referenced by a URI value, then the default encoding of 8bit
860 is used and no explicit ENCODING parameter is needed.
862 Type value: A single value. The default is binary. It may also be
863 reset to uri. The uri value may be used to specify a value outside of
864 this MIME entity.
866 Type special notes: The type MAY include the type parameter "TYPE" to
867 specify the graphic image format type. The TYPE parameter values MUST
868 be one of the IANA registered image formats or a non-standard image
869 format.
871 Type example:
873 LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg
875 LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
876 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
877 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
878 <...the remainder of "B" encoded binary data...>
879 vCard MIME Directory Profile
881 3.5.4 AGENT Type Definition
883 To: ietf-mime-directory@imc.org
885 Subject: Registration of text/directory MIME type AGENT
887 Type name: AGENT
889 Type purpose: To specify information about another person who will
890 act on behalf of the individual or resource associated with the
891 vCard.
893 Type encoding: 8-bit.
895 Type value: The default is a single vcard value. It may also be reset
896 to either a single text or uri value. The text value may be used to
897 specify textual information. The uri value may be used to specify
898 information outside of this MIME entity.
900 Type special notes: This type typically is used to specify an area
901 administrator, assistant, or secretary for the individual associated
902 with the vCard. A key characteristic of the Agent type is that it
903 represents somebody or something that is separately addressable.
905 Type example:
907 AGENT;VALUE=uri:
908 CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
910 AGENT:BEGIN:VCARD\n
911 FN:Susan Thomas\n
912 TEL:+1-919-555-1234\n
913 EMAIL;INTERNET:sthomas@host.com\n
914 END:VCARD\n
916 3.5.5 ORG Type Definition
918 To: ietf-mime-directory@imc.org
920 Subject: Registration of text/directory MIME type ORG
922 Type name: ORG
924 Type purpose: To specify the organizational name and units associated
925 with the vCard.
927 Type encoding: 8bit
929 Type value: A single structured text value consisting of components
930 separated the SEMI-COLON character (ASCII decimal 59).
932 Type special notes: The type is based on the X.520 Organization Name
933 and Organization Unit attributes. The type value is a structured text
934 vCard MIME Directory Profile
936 consisting of the organization name, followed by one or more levels
937 of organizational unit names.
939 Type example: A type value consisting of an organizational name,
940 organizational unit #1 name and organizational unit #2 name.
942 ORG:ABC, Inc.;North American Division;Marketing
944 3.6 Explanatory Types
946 These types are concerned with additional explanations, such as that
947 related to informational notes or revisions specific to the vCard.
949 3.6.1 CATEGORIES Type Definition
951 To: ietf-mime-directory@imc.org
953 Subject: Registration of text/directory MIME type CATEGORIES
955 Type name: CATEGORIES
957 Type purpose: To specify application category information about the
958 vCard.
960 Type encoding: 8bit
962 Type value: One or more text values separated by a COMMA character
963 (ASCII decimal 44).
965 Type example:
967 CATEGORIES:TRAVEL AGENT
969 CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
971 3.6.2 NOTE Type Definition
973 To: ietf-mime-directory@imc.org
975 Subject: Registration of text/directory MIME type NOTE
977 Type name: NOTE
979 Type purpose: To specify supplemental information or a comment that
980 is associated with the vCard.
982 Type encoding: 8bit
984 Type value: A single text value.
986 Type special notes: The type is based on the X.520 Description
987 attribute.
989 vCard MIME Directory Profile
991 Type example:
993 NOTE:This fax number is operational 0800 to 1715
994 EST, Mon-Fri.
996 3.6.3 PRODID Type Definition
998 To: ietf-mime-directory@imc.org
1000 Subject: Registration of text/directory MIME type PRODID
1002 Type name: PRODID
1004 Type purpose: To specify the identifier for the product that created
1005 the vCard object.
1007 Type encoding: 8-bit.
1009 Type value: A single text value.
1011 Type special notes: Implementations SHOULD use a method such as that
1012 specified for Formal Public Identifiers in ISO 9070 to assure that
1013 the text value is unique.
1015 Type example:
1017 PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
1019 3.6.4 REV Type Definition
1021 To: ietf-mime-directory@imc.org
1023 Subject: Registration of text/directory MIME type REV
1025 Type name: REV
1027 Type purpose: To specify revision information about the current
1028 vCard.
1030 Type encoding: 8-bit.
1032 Type value: The default is a single date-time value. May also be
1033 reset to a single date value.
1035 Type special notes: The value distinguishes the current revision of
1036 the information in this vCard for other renditions of the
1037 information.
1039 Type example:
1041 REV:1995-10-31T22:27:10Z
1043 REV:1997-11-15
1044 vCard MIME Directory Profile
1046 3.6.5 SORT-STRING Type Definition
1048 To: ietf-mime-directory@imc.org
1050 Subject: Registration of text/directory MIME type SORT-STRING
1052 Type Name: SORT-STRING
1054 Type purpose: To specify the text to be used in national language
1055 specific sorting of the values specified by the FN or N types.
1057 Type encoding: The default is 8bit. May also be reset to 7bit or
1058 quoted-printable.
1060 Type value: text
1062 Type special notes: The sort string is used to provide text that is
1063 to be used in locale- or national language-specific sorting of the
1064 values for the formatted name or structured name types. Without this
1065 information, sorting algorithms may incorrectly sort this vCard
1066 within a sequence of sorted vCards. If this type is present in a
1067 vCard, then this value should be used for sorting the vCard, instead
1068 of the values of the FN or N types.
1070 Type example: The following would define the sort string "Harten" for
1071 the "FN:Rene J. van der Harten" or "N:van der
1072 Harten;Rene;J.;Sir;R.D.O.N.".
1074 SORT-STRING:Harten
1076 3.6.6 SOUND Type Definition
1078 To: ietf-mime-directory@imc.org
1080 Subject: Registration of text/directory MIME type SOUND
1082 Type name: SOUND
1084 Type purpose: To specify a digital sound content information that
1085 annotates some aspect of the vCard. By default this type is used to
1086 specify the proper pronunciation of the name type value of the vCard.
1088 Type encoding: The encoding MUST be reset to "b" using the ENCODING
1089 parameter in order to specify inline, encoded binary data. If the
1090 value is referenced by a URI value, then the default encoding of 8bit
1091 is used and no explicit ENCODING parameter is needed.
1093 Type value: A single value. The default is binary. It may also be
1094 reset to uri. The uri value may be used to specify a value outside of
1095 this MIME entity.
1097 vCard MIME Directory Profile
1099 Type special notes: The type MAY include the type parameter "TYPE" to
1100 specify the audio format type. The TYPE parameter values MUST be one
1101 of the IANA registered audio formats or a non-standard audio format.
1103 Type example:
1105 SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
1106 19960229T080000.xyzMail@host1.com
1108 SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
1109 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
1110 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
1111 <...the remainder of "B" encoded binary data...>
1113 3.6.7 UID Type Definition
1115 To: ietf-mime-directory@imc.org
1117 Subject: Registration of text/directory MIME type UID
1119 Type name: UID
1121 Type purpose: To specify a value that represents a globally unique
1122 identifier corresponding to the individual or resource associated
1123 with the vCard.
1125 Type encoding: 8bit.
1127 Type value: A single text value.
1129 Type special notes: The type is used to uniquely identify the object
1130 that the vCard represents.
1132 The type may include the type parameter "TYPE" to specify the format
1133 of the identifier. The TYPE parameter value may be any IANA
1134 registered identifier format. The value may also be a non-standard
1135 format.
1137 Type example:
1139 UID:19950401-080045-40000F192713-0052
1141 3.6.8 URL Type Definition
1143 To: ietf-mime-directory@imc.org
1145 Subject: Registration of text/directory MIME type URL
1147 Type name: URL
1149 Type purpose: To specify a uniform resource locator associated with
1150 the object that the vCard refers to.
1152 vCard MIME Directory Profile
1154 Type encoding: 8bit
1156 Type value: A single uri value.
1158 Type example:
1160 URL:http://www.swbyps.restaurant.french/~chezchic.html
1162 3.6.9 VERSION Type Definition
1164 To: ietf-mime-directory@imc.org
1166 Subject: Registration of text/directory MIME type VERSION
1168 Type name: VERSION
1170 Type purpose: To specify the version of the vCard specification used
1171 to format this vCard.
1173 Type encoding: 8bit
1175 Type value: A single text value.
1177 Type special notes: The property MUST be present in the vCard object.
1178 The value MUST be "3.0" if the vCard corresponds to this
1179 specification.
1181 Type example:
1183 VERSION: 3.0
1185 3.7 Security Types
1187 These types are concerned with the security of communication pathways
1188 or access to the vCard.
1190 3.7.1 CLASS Type Definition
1192 To: ietf-mime-directory@imc.org
1194 Subject: Registration of text/directory MIME type CLASS
1196 Type name: CLASS
1198 Type purpose: To specify the access classification for a vCard
1199 object.
1201 Type encoding: 8bit
1203 Type value: A single text value.
1205 Type special notes: An access classification is only one component of
1206 the general security model for a directory service. The
1207 vCard MIME Directory Profile
1209 classification attribute provides a method of capturing the intent of
1210 the owner for general access to information described by the vCard
1211 object.
1213 Type examples:
1215 CLASS:PUBLIC
1217 CLASS:PRIVATE
1219 CLASS:CONFIDENTIAL
1221 3.7.2 KEY Type Definition
1223 To: ietf-mime-directory@imc.org
1225 Subject: Registration of text/directory MIME type KEY
1227 Type name: KEY
1229 Type purpose: To specify a public key or authentication certificate
1230 associated with the object that the vCard represents.
1232 Type encoding: The encoding MUST be reset to "b" using the ENCODING
1233 parameter in order to specify inline, encoded binary data. If the
1234 value is a text value, then the default encoding of 8bit is used and
1235 no explicit ENCODING parameter is needed.
1237 Type value: A single value. The default is binary. It may also be
1238 reset to text. The text value may be used to specify a text key.
1240 Type special notes: The type may also include the type parameter TYPE
1241 to specify the public key or authentication certificate format. The
1242 parameter type may specify any IANA registered public key or
1243 authentication certificate format. The parameter type may also
1244 specify a non-standard format.
1246 Type example:
1248 KEY;ENCODING=b: MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
1249 wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
1250 Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
1251 ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
1252 E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
1253 VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
1254 MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
1255 Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
1256 EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
1257 dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
1258 EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
1259 +hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
1260 mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
1261 vCard MIME Directory Profile
1263 rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
1264 UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
1266 3.8 Extended Types
1268 The types defined by this document can be extended with private types
1269 using the non-standard, private values mechanism defined in [RFC
1270 2045]. Non-standard, private types with a name starting with "X-" may
1271 be defined bilaterally between two cooperating agents without outside
1272 registration or standardization.
1274 4. Formal Grammar
1276 The following formal grammar is provided to assist developers in
1277 building parsers for the vCard.
1279 This syntax is written according to the form described in RFC 2234,
1280 but it references just this small subset of RFC 2234 literals:
1282 ;*******************************************
1283 ; Commonly Used Literal Definition
1284 ;*******************************************
1286 ALPHA = %x41-5A / %x61-7A
1287 ; Latin Capital Letter A-Latin Capital Letter Z /
1288 ; Latin Small Letter a-Latin Small Letter z
1290 CHAR = %x01-7F
1291 ; Any C0 Controls and Basic Latin, excluding NULL from
1292 ; Code Charts, pages 7-6 through 7-9 in [UNICODE]
1294 CR = %x0D
1295 ; Carriage Return
1297 LF = %0A
1298 ; Line Feed
1300 CRLF = CR LF
1301 ; Internet standard newline
1303 ;CTL = %x00-1F / %x7F
1304 ; Controls. Not used, but referenced in comments.
1306 DIGIT = %x30-39
1307 ; Digit Zero-Digit Nine
1309 DQUOTE = %x22
1310 ; Quotation Mark
1312 HTAB = %x09
1313 ; Horizontal Tabulation
1314 vCard MIME Directory Profile
1316 SP = %x20
1317 ; space
1319 VCHAR = %x21-7E
1320 ; Visible (printing) characters
1322 WSP = SP / HTAB
1323 ; White Space
1325 ;*******************************************
1326 ; Basic vCard Definition
1327 ;*******************************************
1329 vcard_entity = 1*(vcard)
1331 vcard = [group "."] "BEGIN" ":" *WSP "VCARD" 1*CRLF
1332 1*(contentline)
1333 ;A vCard object MUST include the VERSION, FN and N types.
1334 [group "."] "END" ":" *WSP "VCARD" 1*CRLF
1336 contentline = [group "."] name *(";" *WSP param ) ":" value CRLF
1337 ; When parsing a content line, folded lines must first
1338 ; be unfolded according to the unfolding procedure
1339 ; described above. When generating a content line, lines
1340 ; longer than 75 characters SHOULD be folded according to
1341 ; the folding procedure described above.
1343 group = 1*(ALPHA / DIGIT / "-")
1345 name = iana-token / x-name
1346 ; Parsing of the param and value is
1347 ; based on the "name" or type identifier
1348 ; as defined in ABNF sections below
1350 iana-token = 1*(ALPHA / DIGIT / "-")
1351 ; vCard type or parameter identifier registered with IANA
1353 x-name = "X-" 1*(ALPHA / DIGIT / "-")
1354 ; Reserved for non-standard use
1356 param = [param-name "="] param-value *("," *WSP param-value)
1358 param-name = iana-token / x-name
1360 param-value = text / quoted-string
1362 text = *SAFE-CHAR
1364 value = *VALUE-CHAR
1366 quoted-string = DQUOTE *qtext DQUOTE
1368 qtext = QSAFE-CHAR / QUOTED-CHAR
1369 vCard MIME Directory Profile
1371 NON-ASCII = %x80-FF
1372 ; Use is restricted by CHARSET parameter
1373 ; on outer MIME object (UTF-8 preferred)
1375 QSAFE-CHAR = WSP / %x21 / %x23-5B / %x5D-7E / NON-ASCII
1376 ; Any character except CTLs, DQUOTE, or "\"
1378 QUOTED-CHAR = "\" ("\" / DQUOTE)
1379 ; \\ encodes \ and \" encodes "
1381 SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
1382 ; Any character except CTLs, DQUOTE, ";", ":", ","
1384 VALUE-CHAR = WSP / VCHAR / NON-ASCII
1385 ; Any textual character
1387 ;*******************************************
1388 ; vCard Type Definition
1389 ;
1390 ; Provides type-specific definitions for how the
1391 ; "value" and "param" are defined.
1392 ;*******************************************
1394 ;For name="NAME"
1395 param = ""
1396 ;No parameters allowed
1398 value = text-value
1400 ;For name="PROFILE"
1401 param = ""
1402 ;No parameters allowed
1404 value = "VCARD"
1406 ;For name="SOURCE"
1407 param = source-param
1408 ;No parameters allowed
1410 value = uri
1412 source-param = ( "VALUE" "=" "uri")
1413 / ( "CONTEXT" "=" word)
1414 ;Parameter values specifies the protocol
1415 ; context for the URI value.
1416 / (x-name "=" *SAFE-CHAR
1418 ;For name="FN"
1419 ;This type MUST be included in a vCard object.
1420 param = text-param
1421 ;Text parameters allowed
1423 value = text-value
1424 vCard MIME Directory Profile
1426 ;For name="N"
1427 ;This type MUST be included in a vCard object.
1428 param = text-param
1429 ;Text parameters allowed
1431 value = n-value
1433 n-value = 0*4(text-value *("," text-value) ";")
1434 text-value *("," text-value)
1435 ; Family, Given, Middle, Prefix, Suffix.
1436 ; Example:Public;John;Quincy,Adams;Reverend Dr.;III,
1437 ; Esq.
1439 ;For name="NICKNAME"
1440 param = text-param
1441 ;Text parameters allowed
1443 value = text-list
1445 ;For name="PHOTO"
1446 param = img-inline-param
1447 ;Only image parameters allowed
1449 param =/ img-refer-param
1450 ;Only image parameters allowed
1452 value = img-inline-value
1453 ;Value and parameter MUST match
1455 value =/ img-refer-value
1456 ;Value and parameter MUST match
1458 ;For name="BDAY"
1459 param = ("VALUE" "=" "DATE")
1460 ;Only value parameter allowed
1462 param =/ ("VALUE" "=" "DATE-TIME")
1463 ;Only value parameter allowed
1465 value = date-value
1466 ;Value MUST match value type
1468 value =/ date-time-value
1469 ;Value MUST match value type
1471 ;For name="ADR"
1472 param = adr-param / text-param
1473 ;Only adr and text parameters allowed
1475 value = adr-value
1477 ;For name="LABEL"
1478 param = adr-param / text-param
1479 ;Only adr and text parameters allowed
1480 vCard MIME Directory Profile
1482 value = text-value
1484 ;For name="TEL"
1485 param = tel-param
1486 ;Only tel parameters allowed
1488 value = phone-number-value
1490 tel-param = ["TYPE" "="] tel-type *("," *WSP tel-type)
1492 tel-type = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG"
1493 / "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN"
1494 / "VIDEO" / "PCS" / iana-token / x-name
1496 ;For name="EMAIL"
1497 param = email-param
1498 ;Only email parameters allowed
1500 value = text-value
1502 email-param = ["TYPE" "="] email-type ["," *WSP "PREF"]
1504 email-type = "INTERNET" / "X400" / iana-token / "X-" word
1506 ;For name="MAILER"
1507 param = text-param
1508 ;Only text parameters allowed
1510 value = text-value
1512 ;For name="TZ"
1513 param = ""
1514 ;No parameters allowed
1516 value = utc-offset-value
1518 ;For name="GEO"
1519 param = ""
1520 ;No parameters allowed
1522 value = float-value ";" float-value
1524 ;For name="TITLE"
1525 param = text-param
1526 ;Only text parameters allowed
1528 value = text-value
1530 ;For name="ROLE"
1531 param = text-param
1532 ;Only text parameters allowed
1534 value = text-value
1535 vCard MIME Directory Profile
1537 ;For name="LOGO"
1538 param = img-inline-param / img-refer-param
1539 ;Only image parameters allowed
1541 value = img-inline-value / img-refer-value
1542 ;Value and parameter MUST match
1544 ;For name="AGENT"
1545 param = agent-inline-param
1547 param =/ agent-refer-param
1549 value = agent-inline-value
1551 value =/ agent-refer-value
1553 agent-inline-param = ""
1554 ;No parameters allowed
1556 agent-refer-param = "VALUE" "=" "uri"
1557 ;Only value parameter allowed
1559 agent-inline-value = text-value
1560 ;Value MUST be a valid vCard object
1562 agent-refer-value = uri
1563 ;URI MUST refer to image content of given type
1565 ;For name="ORG"
1567 param = text-param
1568 ;Only text parameters allowed
1570 value = org-value
1572 org-value = *(text-value ";") text-value
1573 ; First is Organization Name, remainder are Organization Units.
1575 ;For name="CATEGORIES"
1576 param = text-param
1577 ;Only text parameters allowed
1579 value = text-list
1581 ;For name="NOTE"
1582 param = text-param
1583 ;Only text parameters allowed
1585 value = text-value
1587 ;For name="PRODID"
1588 param = ""
1589 ;No parameters allowed
1590 vCard MIME Directory Profile
1592 value = text-value
1594 ;For name="REV"
1595 param = ["VALUE" =" "DATE-TIME"]
1596 ;Only value parameters allowed
1598 param =/ "VALUE" =" "DATE"
1599 ;Only value parameters allowed
1601 value = date-time-value
1603 value =/ date-value
1605 ;For name="SORT-STRING"
1606 param = text-param
1607 ;Only text parameters allowed
1609 value = text
1611 ;For name="SOUND"
1612 param = snd-inline-param
1613 ;Only sound parameters allowed
1615 param =/ snd-refer-param
1616 ;Only sound parameters allowed
1618 value = snd-line-value
1619 ;Value MUST match value type
1621 value =/ snd-refer-value
1622 ;Value MUST match value type
1624 snd-inline-value = binary CRLF
1625 ;Value MUST be "b" encoded audio content
1627 snd-inline-param = ("VALUE" "=" "binary"])
1628 / ("ENCODING" "=" "b")
1629 / ("TYPE" "=" *SAFE-CHAR)
1630 ;Value MUST be an IANA registered audio type
1632 snd-refer-value = uri
1633 ;URI MUST refer to audio content of given type
1635 snd-refer-param = ("VALUE" "=" "uri")
1636 / ("TYPE" "=" word)
1637 ;Value MUST be an IANA registered audio type
1639 ;For name="UID"
1640 param = ""
1641 ;No parameters allowed
1643 value = text-value
1644 vCard MIME Directory Profile
1646 ;For name="URL"
1647 param = ""
1648 ;No parameters allowed
1650 value = uri
1652 ;For name="VERSION"
1653 ;This type MUST be included in a vCard object.
1654 param = ""
1655 ;No parameters allowed
1657 value = "3.0"
1659 ;For name="CLASS"
1660 param = ""
1661 ;No parameters allowed
1663 value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL"
1664 / iana-token / x-name
1666 ;For name="KEY"
1667 param = key-txt-param
1668 ;Only value and type parameters allowed
1670 param =/ key-bin-param
1671 ;Only value and type parameters allowed
1673 value = text-value
1675 value =/ binary
1677 key-txt-param = "TYPE" "=" keytype
1679 key-bin-param = ("TYPE" "=" keytype)
1680 / ("ENCODING" "=" "b)
1681 ;Value MUST be a "b" encoded key or certificate
1683 keytype = "X509" / "PGP" / iana-token / x-name
1685 ;For name="X-" non-standard type
1686 param = text-param / (x-name "=" *SAFE-CHAR)
1687 ;Only text or non-standard parameters allowed
1689 value = text-list
1691 ;*******************************************
1692 ; vCard Commonly Used Parameter Definition
1693 ;*******************************************
1695 text-param = ("VALUE" "=" "text")
1696 / ("LANGUAGE" "=" langval)
1697 / (x-name "=" *SAFE-CHAR)
1699 langval =
1700 vCard MIME Directory Profile
1702 img-inline-value = binary
1703 ;Value MUST be "b" encoded image content
1705 img-inline-param = ("VALUE" "=" "binary")
1706 / ("ENCODING" "=" "b")
1707 / ("TYPE" "=" *SAFE-CHAR
1708 ;TYPE value MUST be an IANA registered image type
1710 img-refer-value = uri
1711 ;URI MUST refer to image content of given type
1713 img-refer-param = ("VALUE" "=" "uri")
1714 / ("TYPE" "=" *SAFE-CHAR)
1715 ;TYPE value MUST be an IANA registered image type
1717 adr-param = (["TYPE" "="] adr-type *("," *WSP adr-type))
1718 / (text-param)
1720 adr-type = "dom" / "intl" / "postal" / "parcel" / "home"
1721 / "work" / "pref" / iana-type / x-name
1723 adr-value = 0*6(text-value ";") text-value
1724 ; PO Box, Extended Address, Street, Locality, Region, Postal
1725 ; Code, Country Name
1727 ;*******************************************
1728 ; vCard Type Value Definition
1729 ;*******************************************
1731 text-list =
1733 text-value =
1735 binary-value =
1737 date-value =
1739 time-value =
1741 date-time-value =
1745 phone-number-value =
1748 uri-value =
1750 utc-offset-value = ("+" / "-") time-hour ":" time-minute
1751 time-hour = 2DIGIT ;00-23
1752 time-minute = 2DIGIT ;00-59
1753 vCard MIME Directory Profile
1755 5. Differences With vCard v2.1
1757 This specification has been reviewed by the IETF community. The
1758 review process introduced a number of differences with the [VCARD]
1759 version 2.1. These differences are minor, but require that vCard
1760 objects conforming to this specification have a different version
1761 number than a vCard conforming to [VCARD]. The differences include
1762 the following:
1764 � The QUOTED-PRINTABLE inline encoding has been eliminated.
1765 Only the "B" encoding of [RFC 2047] is an allowed value for
1766 the ENCODING parameter.
1768 � The method for specifying CRLF character sequences in text
1769 type values has been changed. The CRLF character sequence in
1770 a text type value is specified with the backslash character
1771 sequence "\n" or "\N".
1773 � Any COMMA or SEMICOLON in a text type value must be backslash
1774 escaped.
1776 � VERSION value corresponding to this specification MUST be
1777 "3.0".
1779 � The [MIME-DIR] predefined types of SOURCE, NAME and PROFILE
1780 are allowed.
1782 � The [MIME-DIR] VALUE type parameter for value data typing is
1783 allowed. In addition, there are extensions made to these type
1784 values for additional value types used in this specification.
1786 � The [VCARD] CHARSET type parameter has been eliminated.
1787 Character set may only be specified on the CHARSET parameter
1788 on the Content-Type MIME header field.
1790 � The [VCARD] support for non-significant WSP character, other
1791 than after the COMMA character list separator, SEMICOLON
1792 character value component separator and the COLON value
1793 separator has been eliminated.
1795 � LOGO, PHOTO and SOUND multimedia formats MUST be either IANA
1796 registered types or non-standard types.
1798 � Inline binary content must be "B" encoded and folded. A blank
1799 line after the encoded binary content is no longer required.
1801 � TEL values may be identified as personal communication
1802 services telephone numbers with the PCS type parameter value.
1804 � The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types
1805 have been added.
1807 vCard MIME Directory Profile
1809 � The VERSION, N and FN types MUST be specified in a vCard.
1810 This identifies the version of the specification that the
1811 object was formatted to. It also assures that every vCard
1812 will include both a structured and formatted name that can be
1813 used to identify the object.
1815 6. Acknowledgements
1817 The many valuable comments contributed by members of the IETF ASID
1818 working group are gratefully acknowledged, as are the contributions
1819 by Roland Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce
1820 Johnston, Daniel Klaussen, Vinod Seraphin, Michelle Watkins. Chris
1821 Newman was especially helpful in navigating the intricacies of ABNF
1822 lore.
1824 7. Authors?s Addresses
1826 BEGIN:vCard
1827 VERSION:3.0
1828 FN:Frank Dawson
1829 ORG:Lotus Development Corporation
1830 ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
1831 ;Raleigh;NC;27613-3502;U.S.A.
1832 TEL;TYPE=VOICE,MSG,WORK: +1-919-676-9515
1833 TEL;TYPE=FAX,WORK: +1-919-676-9564
1834 EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
1835 EMAIL;TYPE=INTERNET:fdawson@earthlink.net
1836 URL:http://home.earthlink.net/~fdawson
1837 END:vCard
1839 BEGIN:vCard
1840 VERSION:3.0
1841 FN:Tim Howes
1842 ORG:Netscape Communications Corp.
1843 ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View;
1844 CA; 94043;U.S.A.
1845 TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
1846 TEL;TYPE=FAX,WORK:+1-415-528-4164
1847 EMAIL;TYPE=INTERNET:howes@netscape.com
1848 END:vCard
1850 8. References
1852 The following documents are referenced by this work.
1854 [ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
1855 Information interchange - Representation of dates and times - The
1856 International Organization for Standardization, June, 1988.
1858 [ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
1859 interchange formats - Information interchange - Representation of
1860 dates and times - The International Organization for Standardization,
1861 May, 1991.
1863 vCard MIME Directory Profile
1865 [ISO 9070] ISO 9070, Information Processing - SGML support facilities
1866 - Registration Procedures for Public Text Owner Identifiers, April,
1867 1991.
1869 [CCITT E.163] Recommendation E.163 - Numbering Plan for The
1870 International Telephone Service, CCITT Blue Book, Fascicle II.2, pp.
1871 128-134, November, 1988.
1873 [CCITT X.121] Recommendation X.121 - International Numbering Plan for
1874 Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332,
1875 November, 1988.
1877 [CCITT X.520] Recommendation X.520 - The Directory - Selected
1878 Attribute Types, November 1988.
1880 [CCITT X.521] Recommendation X.521 - The Directory - Selected Object
1881 Classes, November 1988.
1883 [MIME-DIR] Howes, T., Smith, M., Dawson, F. "A MIME Content-Type for
1884 Directory Information", RFC xxxx, March 1998.
1886 [RFC 1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform
1887 Resource Locators (URL)", RFC 1738, December 1994.
1889 [RFC 1766] Alvestrand, H., "Tags for the Identification of
1890 Languages", March 1995.
1892 [RFC 1872] Levinson, E., "The MIME Multipart/Related Content-type,"
1893 RFC 1872, December 1995.
1895 [RFC 2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail
1896 Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC
1897 2045, November 1996.
1899 [RFC 2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail
1900 Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996.
1902 [RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) -
1903 Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
1904 November 1996.
1906 [RFC 2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet
1907 Mail Extensions (MIME) - Part Four: Registration Procedures", RFC
1908 2048, January 1997.
1910 [RFC 2119] "Key words for use in RFCs to Indicate Requirement
1911 Levels", RFC 2119, March 1997.
1913 [RFC 2234] Crocker, D., Overell, P., "Augmented BNF for Syntax
1914 Specifications: ABNF", RFC 2234, November 1997.
1916 [UNICODE] "The Unicode Standard - Version 2.0", The Unicode
1917 Consortium, July 1996.
1919 vCard MIME Directory Profile
1921 [VCARD] Internet Mail Consortium, "vCard - The Electronic Business
1922 Card Version 2.1", http://www.imc.org/pdi/vcard-21.txt, September 18,
1923 1996.
1925 9. Full Copyright Statement
1927 "Copyright (C) The Internet Society (date). All Rights Reserved.
1929 This document and translations of it MAY be copied and furnished to
1930 others, and derivative works that comment on or otherwise explain it
1931 or assist in its implementation MAY be prepared, copied, published
1932 and distributed, in whole or in part, without restriction of any
1933 kind, provided that the above copyright notice and this paragraph are
1934 included on all such copies and derivative works. However, this
1935 document itself MAY not be modified in any way, such as by removing
1936 the copyright notice or references to the Internet Society or other
1937 Internet organizations, except as needed for the purpose of
1938 developing Internet standards in which case the procedures for
1939 copyrights defined in the Internet Standards process MUST be
1940 followed, or as required to translate it into languages other than
1941 English.
1943 The limited permissions granted above are perpetual and will not be
1944 revoked by the Internet Society or its successors or assigns.
1946 This document and the information contained herein is provided on an
1947 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1948 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1949 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1950 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1951 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.