MMnDhRVS

1vCard
2The Electronic Business Card
3Version 2.1
4
5A versit Consortium Specification
6September 18, 1996
7
8
9Copyrights
10� 1996, International Business Machines Corp., Lucent Technologies, Inc., and Siemens. All rights reserved. 
11Permission is granted to copy and distribute this publication provided that it is reproduced in its entirety without modification and includes the above copyright notice and this permission notice.
12No licenses, express or implied, are granted with respect to any of the technology described in this publication. International Business Machines Corp., Lucent Technologies, Inc., and Siemens retain all their intellectual property rights in the technology described in this publication. 
13Even though International Business Machines Corp., Lucent Technologies, Inc., and Siemens have reviewed this specification, INTERNATIONAL BUSINESS MACHINES CORP., LUCENT TECHNOLOGIES, INC, AND SIEMENS, MAKE NO WARRANTY OR REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS PUBLICATION, ITS QUALITY OR ACCURACY, NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. AS A RESULT, THIS SPECIFICATION IS DELIVERED "AS IS" AND THE READER ASSUMES THE ENTIRE RISK AS TO ITS QUALITY, ACCURACY OR SUITABILITY FOR ANY PARTICULAR PURPOSE..
14IN NO EVENT WILL INTERNATIONAL BUSINESS MACHINES CORP., LUCENT TECHNOLOGIES, INC, AND SIEMENS, BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES RESULTING FROM ANY DEFECT OR INACCURACY IN THIS PUBLICATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
15This publication is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government are subject to restrictions set forth in DFARS 252.227-7013 or 48 CFR 52.227-19, as applicable.
16
17
18Trademarks
19versit, the versit  logo, versitcard, vCard, and vCalendar are trademarks of Apple Computer, Inc., AT&T Corp., International Business Machines Corp., and Siemens.
20Apple, is a trademarks of Apple Computer, Inc. registered in the U.S. and other countries.
21AT&T and ATTMail are registered trademarks of AT&T Corp.
22IBM, IBM Mail, and OS/2 are registered trademarks of International Business Machines Corporation.
23America Online is a registered trademark of America Online, Inc.
24CompuServe, CompuServe Information Services are registered trademarks of Compuserve Incorporated.
25MCIMail is a registered trademark of MCI Communications Corporation.
26Microsoft is a registered trademark, and Microsoft Windows is a trademark of Microsoft Corporation.
27Prodigy is a registered trademark of Prodigy Services Company.
28Unicode is a registered trademark of Unicode, Inc.
29
30
31Contributors
32Roland Alden
33Greg Ames, Ames & Associates
34Masanari Arai, Puma Technologies
35Stephen W. Bartlett
36Donal Carroll
37Liang-Jye Chang, Starfish Software
38Frank Dawson, IBM Corporation
39Ken Dobson, IntelliLink Inc.
40Scott Feldstein, Nimble Software, Inc.
41Anik Ganguly, OnTime/Division of FTP Software.
42Beijing Goo, Microsoft
43Arvind K. Goyal, Lotus Development Corporation
44Gary Hand, IBM Corporation
45Tim Howes, Netscape Communications Corporation
46Mark Joseph, Attachmate Corporation
47Kerry Kelly, Now Software, Inc.
48Phac Letuan, Apple Computer, Inc.
49Pat Megowan, Counterpoint Sytems Foundry Inc.
50Tohri Mori, IBM Japan/Salutation Consortium
51Ravi Pandya, NetManage, Inc.
52Geoff Ralston, Four11 Corporation
53Steven Rummel, Lucent Technologies
54Michael Santullo, Four11 Corporation
55Vinod Seraphin, Lotus Development Corporation
56Dexter Seely, Corex Technologies, Inc.
57Vlad Shmunis, Ring Zero Systems Inc.
58Dean Stevens, Now Software, Inc.
59Michelle Watkins, Netscape Communications Corporation
60Horst Widlewski, Siemens
61
62
63Reference Information
64The cited references contain provisions which, through reference in this specification, constitute provisions of this specification. At the time of publication, the indicated versions in the following references were valid. Parties to agreements based on this specification are encouraged to research the possibility of revised standards.
65*	ANSI X3.4-1977, Code for Information Interchange, American National Standards Institute, 1977.
66*	CCITT (ITU) Recommendation E.163, Numbering Plan for The International Telephone Service, CCITT Blue Book, Fascicle II.2, pp. 128-134, November, 1988.
67*	CCITT (ITU) Recommendation G.721, 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM), CCITT Red Book, Fascicle III.4, November, 1988.
68*	CCITT (ITU) Recommendation X.121, International Numbering Plan for Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, November, 1988.
69*	CCITT (ITU) Recommendations X.500-X.521, Data Communication Networks: Directory, CCITT Blue Book, Fascicle VIII.8, November, 1988.
70*	CCITT Recommendation X.520, The Directory-Selected Attribute Types, 1988.
71*	CCITT Recommendation X.521, The Directory-Selected Object Classes, 1988.
72*	IETF RFC 1738, Universal Resource Locator, December 1994.
73*	IETF Network Working Group RFC 1766, Tags for the Identification of Languages, March 1995.
74*	IETF Network Working Group Draft, A MIME Content-Type for Directory Information, January 1996. Available from the University of Michigan, 535 W. William St., Ann Arbor, MI 48103-4943, FTP://ds.internic.net/Internet-Drafts/draft-ietf-asid-mime-direct-01.txt.
75*	IETF Network Working Group Draft, An Application/Directory MIME Content-Type Electronic Business Card Profile, May 1996. Available FTP://ds.internic.net/Internet-Drafts/draft-ietf-asid-mime-vcard-00.txt.
76*	IETF Network Working Group Draft, UTF-8, A Transformation Format of UNICODE and ISO 10646, July 1996. Available from FTP://ds.internic.net/Internet-Drafts/draft-yergeau-utf8-01.txt.
77*	ISO 639, Code for The Representation of names of languages, International Organization for Standardization, April, 1988.
78*	ISO 3166, Codes for The Representation of names of countries, International Organization for Standardization, December, 1993.
79*	ISO 8601, Data elements and interchange formats-Information interchange-Representation of dates and times, International Organization for Standardization, June, 1988.
80*	ISO 8601, Technical Corrigendum 1, Data elements and interchange formats-Information interchange-Representation of dates and times, International Organization for Standardization, May, 1991.
81*	ISO 8859-1, Information Processing-8-Bit single-byte coded graphic character sets-Part 1: Latin Alphabet No. 1, International Organization for Standardization, February, 1987.
82*	ISO 9070, Information Processing-SGML support facilities-Registration Procedures for Public Text Owner Identifiers, 1990-02-01.[DS1]
83�	ISO/IEC 9070, Information Technology�SGML Support Facilities�Registration Procedures for Public Text Owner Identifiers, Second Edition, International Organization for Standardization, April, 1991.
84�	ISO/IEC 11180, Postal addressing, International Organization for Standardization, 1993.
85�	Apple�s Representation of a Canonical Static DeviceID in The Telephony Suite, version 1.0, Apple Computer, Inc., 1993.
86*	Microsoft TAPI in Microsoft Windows 3.1 Telephony Programmers' Guide, version 1.0, Microsoft Corporation, 1993.
87*	RFC1521, MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies, Network Working Group, September, 1993.
88*	The Unicode Standard, Version 1.1: Version 1.0, Volume 1 (ISBN 0-201-56788-1), version 1.0, volume 2 (ISBN 0-20-60845-6) and Unicode Technical Report #4, The Unicode Standard, version 1.1, The Unicode Consortium, October, 1991. Both references to be published by Addison-Wesley.
89
90
91versit Update
92versit  is a multivendor development initiative of the communication and computer industries, founded by Apple, AT&T, IBM and Siemens. The versit parties believe that great potential exists in improving the nature of communications in the business world-permitting companies to better manage their quality, productivity, customer satisfaction and cost of operations, while expanding the market opportunities for a variety of product and service vendors. versit parties will jointly define and support open specifications that facilitate and promote the interoperability of advanced personal information and communication devices, networks and services.
93The versit vision is to enable diverse communication and computing devices, applications and services from competing vendors to interoperate in all environments. Through developing a series of specifications for interoperability among diverse communications and computing devices, applications, networks and services, versit 's vision will become a reality.
94versit 's primary development areas are in:
95*	Personal Data Interchange (PDI)
96*	Computer Telephone Integration (CTI)
97*	Conferencing and Messaging (C&M)
98*	Wired and Wireless connectivity
99versit specifications are directed at both the decision makers and the implementation teams of: 
100*	Equipment Manufacturers
101*	Independent Software Vendors
102*	Information Service Providers
103*	Online Service Providers
104*	Software Houses
105*	Users
106versit specifications are made available to any interested party. In turn, versit encourages the support of our goals by soliciting feedback on versit specifications.
107
108All comments relating to versit or the material within this specification should be submitted to:
109versit  
110(800) 803-6240
111+1 (201) 327-2803 (Outside USA)
112pdi@versit.com
113http://www.versit.com/pdi
114
115
116Contents
117Section 1 : Introduction	
1181.1 Overview	
1191.2 Scope	
1201.3 Contents	
1211.4 Definitions and Abbreviations	
122Section 2 : vCard Specificiation	
1232.1 Encoding Characteristics	
1242.1.1 vCard Object	
1252.1.2 Property	
1262.1.3 Delimiters	
1272.1.4 Grouping	
1282.1.4.1 vCard Grouping	
1292.1.4.2 Property Grouping	
1302.1.5 Encodings	
1312.1.6 Character Set	
1322.1.7 Language	
1332.1.8 Value Location	
1342.1.9 Binary Values	
1352.2 Identification Properties	
1362.2.1 Formatted Name	
1372.2.2 Name	
1382.2.3 Photograph	
1392.2.3.1 Photo Format Type	
1402.2.4 Birthdate	
1412.3 Delivery Addressing Properties	
1422.3.1 Delivery Address	
1432.3.1.1 Delivery Address Type	
1442.3.2 Delivery Label	
1452.3.2.1 Delivery Label Type	
1462.4 Telecommunications Addressing Properties	
1472.4.1 Telephone Number	
1482.4.1.1 Telephone Type	
1492.4.2 Electronic Mail	
1502.4.2.1 Electronic Mail Type	
1512.4.3 Mailer	
1522.4.4 Geographical Properties	
1532.4.5 Time Zone	
1542.4.6 Geographic Position	
1552.5 Organizational Properties	
1562.5.1 Title	
1572.5.2 Business Category	
1582.5.3 Logo	
1592.5.3.1 Logo Format Type	
1602.5.4 Agent	
1612.5.5 Organization Name and Organizational Unit	
1622.6 Explanatory Properties	
1632.6.1 Comment	
1642.6.2 Last Revision	
1652.6.3 Sound	
1662.6.3.1 Sound Digital Audio Type	
1672.6.4 Uniform Resource Locator	
1682.6.5 Unique Identifier	
1692.6.6 Version	
1702.7 Security Properties	
1712.7.1 Public Key	
1722.7.2 Key Type	
1732.8 Miscellaneous Properties	
1742.8.1 Extensions	
1752.9 Formal Definition	
176Section 3 : Internet Recommendations	
1773.1 Recommended Practice with SMTP/MIME	
1783.1.1 Text/Plain Content Type	
1793.1.2 Text/X-vCard Content Type	
1803.1.3 Application/Directory Content Type	
1813.2 Recommended Practice with HTTP/HTML	
1823.2.1 Form Element Usage	
1833.2.2 Mapping To INPUT Element Attribute Names	
1843.2.3 Example HTML Code	
185Section 4 : UI Support Recommendations	
1864.1 File System	
1874.2 Clipboard	
1884.3 Drag/Drop	
189Section 5 : Conformance	
190
191
192
193Section 1 : Introduction
194[DS2]		
195Personal Data Interchange (PDI) occurs every time two or more individuals communicate, in either a business or personal context, face-to-face, or across space and time. Such interchanges frequently include the exchange of informal information, such as business cards, telephone numbers, addresses, dates and times of appointments, etc. Augmenting PDI with electronics and telecommunications can help ensure that information is quickly and reliably communicated, stored, organized and easily located when needed.
196Personal information, by nature, is complex and diverse. Currently, proprietary standards exist to structure some types of PDI information, but no single, open specification comprehensively addresses the needs of collecting and communicating PDI information across many common communication channels such as telephones, voice-mail, e-mail, and face-to-face meetings. versit  is developing a comprehensive family of PDI technologies based on open specifications and interoperability agreements to help meet this technology need.
197Overview
198This specification defines a format for an electronic business card, or vCard. The format is suitable as an interchange format between applications or systems. The format is defined independent of the particular method used to transport it. The transport for this exchange might be a file system, point-to-point asynchronous communication, wired-network transport, or some form of unwired transport.
199A vCard is a data stream consisting of one or more vCard objects. The individual vCard definitions can be identified and parsed within the datastream. The vCard data stream may exist as a persistent form in a file system, document management system, network connection between two network endpoints, or in any other digital transport that has an abstraction of a stream of bytes.
200Conceptually, a vCard Writer creates vCard data streams and a vCard Reader interprets vCard data streams. The vCard Reader and Writer may be implemented as a single application or as separate applications. It is not the intent of this specification to define the implementation of these processes beyond some fundamental capabilities related to the format of the vCard data stream and a common set of conformance requirements .
201This specification provides for a clear-text encoding that is intended to be based on the syntax used by the MIME specification (RFC 1521).
202The encoding of this specification can be used in environments which are constrained to 7-bit transfer encodings, short line lengths, and low bandwidth. In addition, the encoding is simple in order to facilitate the implementation of reader and writer applications on small platforms, such as Personal Digital Assistants (PDA), cellular telephones, or alphanumeric pagers.
203Scope
204The vCard is intended to be used for exchanging information about people and resources. In today's business environment, this information is typically exchanged on business cards. It is appropriate, then that this specification define this information in terms of a paradigm based on an electronic business card object.
205The ultimate destination for this information is often a collection of business cards, Rolodex� file, or electronic contact manager. Prior to the introduction of the vCard specification, users of such applications typically had to re-key the original information, often transcribing it from paper business cards. With the advent of the vCard specification, this information can be exchanged in an automated fashion.
206The basis for the data types supported by this specification have their origin in openly defined, international standards and in additional capabilities based on enhancements suggested by the demonstration of the exchange of prototypical vCards using the Internet based World-Wide-Web, Infra-red data transport, and simultaneous voice and data (SVD) modems.
207The "person" object defined by the CCITT X.500 Series Recommendation for Directory Services was the primary reference for the properties that are defined by this specification. Every attempt was made to make it possible to map the X.520/X.521 attributes and objects into and out of an instance of a vCard. The vCard specification has extended the capabilities that have been defined within the CCITT X.500 Series Recommendation to allow the exchange of additional information often recorded on business cards and electronic contact managers. For example, this specification provides support for exchanging graphic images representing company logos, photographs of individuals, geo-positioning information, and other extensions to properties defined by the X.500 Recommendation.
208The specification of all date and time values are defined in terms of the ISO 8601 standard for representation of dates and times. ISO 8601 supersedes all other international standards defined at the time this specification was drafted.
209The paradigm of an electronic business card is related to the concepts of an entry in a LAN/WAN directory or an electronic mail address book or distribution list. However, the requirements of the electronic business card go beyond the definitions of a "person" object found in either the CCITT X.500 Series Recommendation, network directory services, or electronic mail address book products. The vCard specification is needed to address the requirements for an interchange format for the "person" personal data type or object.
210Personal data applications such as Personal Information Managers (PIM) often provide an import/export capability using Comma Separated Value (CSV) or Tab Delimited Files (TDF) formats. However, these solutions do not preserve the intent of the originating application. When a CSV and TDF format is used by a PIM, the meta-data or semantics of the originating object are only apparent to a similar version of the originating application. Exchange of data between such applications is another important application of an industry-standard specification for an electronic business card interchange format, such as the vCard specification.
211Contents
212This specification is separated into eight sections:
213*	"Section 1 : Introduction" introduces PDI and the vCard specification with an overview, scope statement and section on definitions and abbreviations.
214*	"Section 2 : vCard Specification" defines the semantics and syntax for the vCard.
215*	"Section 3 : Internet Recommendations" specifies a set of guidelines to facilitate the exchange of vCard objects over Internet protocols such as HTTP using HTML and SMTP using MIME.
216*	"Section 4 : UI Support Recommendations" specifies a set of guidelines to facilitate the exchange of vCard objects at the desktop user interface using the file system, clipboard and drag/drop capabilities of the operating system.
217*	"Section 5 : Conformance" defines minimum conformance requirements to consider while developing support for this vCard specification.
218Definitions and Abbreviations
219Definitions and abbreviations used within this specification follow.
220Electronic Business Card: Also known as vCard.
221FPI: Formal Public Identifier. A string expression that represents a public identifier for an object. FPI syntax is defined by ISO 9070.
222GUID: Globally Unique IDentifier
223Internet: A WAN connecting thousands of disparate networks in industry, education, government, and research. The Internet uses TCP/IP as the standard for transmitting information.
224ISO: Organization for International Standardization; a worldwide federation of national standards bodies (ISO Member bodies).
225MIME: Multipurpose Internet Mail Extensions, as defined in RFC1521.
226PDA: Personal Digital Assistant computing device
227PDI: Personal Data Interchange, a collaborative application area which involves the communication of data between people who have a business or personal relationship, but do not necessarily share a common computing infrastructure.
228PIM: Personal Information Manager
229RFC#### documents: Internet "Request For Comment" documents (i.e., RFC822, RFC1521, etc.).
230URL: Uniform Resource Locator; a string expression that can represent any resource on the Internet or local system. RFC 1738 defines the syntax for an URL.
231UTC: Universal Time Coordinated; also known as UCT, for Universal Coordinated Time.
232vCard: The generic term for an electronic, virtual information card that can be transferred between computers, PDAs, or other electronic devices through telephone lines, or e-mail networks, or infrared links. How, when, why, and where vCard are used depends on the applications developed utilizing a vCard.
233versitcard: a vCard.
234WAN: Wide-Area Network
235
236
237Section 2 : vCard Specificiation
238[DS3]		
239This section defines the semantics and syntax for the vCard.
240A vCard is a collection of one or more properties. A property is a uniquely named value. A set of properties can be grouped within a vCard. For example, the properties for a telephone number and comment can be grouped in order to preserve the coupling of the annotation with the telephone number. In addition to property groupings, a vC. versit  is developing a comprehensive family of PDI technologies based on open specifications and interoperability agreements to help meet this technology need.
241Overview
242This specification defines a format for an electronic business card, or vCard. The format is suitable as an interchange format between applications or systems. The format is defined independent of the particular method used to transport it. The transport for this exchange might be a file system, point-to-point asynchronous communication, wired-network transport, or some form of unwired transport.
243A vCard is a data stream consisting of one or more vCard objects. The individual vCard definitions can be identified and parsed within the datastream. The vCard data stream may exist as a persistent form in a file system, document management system, network connection between two network endpoints, or in any other digital transport that has an abstraction of a stream of bytes.
244Conceptually, a vCard Writer creates vCard data streams and a vCard Reader interprets vCard data streams. The vCard Reader and Writer may be implemented as a single application or as separate applications. It is not the intent of this specification to define the implementation of these processes beyond some fundamental capabilities related to the format of the vCard data stream and a common set of conformance requirements .
245This specification provides for a clear-text encoding that is intended to be based on the syntax used by the MIME specification (RFC 1521).
246The encoding of this specification can be used in environments which are constrained to 7-bit transfer encodings, short line lengths, and low bandwidth. In addition, the encoding is simple in order to facilitate the implementation of reader and writer applications on small platforms, such as Personal Digital Assistants (PDA), cellular telephones, or alphanumeric pagers.
247Scope
248The vCard is intended to be used for exchanging information about people and resources. In today's business environment, this information is typically exchanged on business cards. It is appropriate, then that this specification define this information in terms of a paradigm based on an electronic business card object.
249The ultimate destination for this information is often a collection of business cards, Rolodex� file, or electronic contact manager. Prior to the introduction of the vCard specification, users of such applications typically had to re-key the original information, often transcribing it from paper business cards. With the advent of the vCard specification, this information can be exchanged in an automated fashion.
250The basis for the data types supported by this specification have their origin in openly defined, international standards and in additional capabilities based on enhancements suggested by the demonstration of the exchange of prototypical vCards using the Internet based World-Wide-Web, Infra-red data transport, and simultaneous voice and data (SVD) modems.
251The "person" object defined by the CCITT X.500 Series Recommendation for Directory Services was the primary reference for the properties that are defined by this specification. Every attempt was made to make it possible to map the X.520/X.521 attributes and objects into and out of an instance of a vCard. The vCard specification has extended the capabilities that have been defined within the CCITT X.500 Series Recommendation to allow the exchange of additional information often recorded on business cards and electronic contact managers. For example, this specification provides support for exchanging graphic images representing company logos, photographs of individuals, geo-positioning information, and other extensions to properties defined by the X.500 Recommendation.
252The specification of all date and time values are defined in terms of the ISO 8601 standard for representation of dates and times. ISO 8601 supersedes all other international standards defined at the time this specification was drafted.
253The paradigm of an electronic business card is related to the concepts of aQuoted-Printable lines of text must also be limited to less than 76 characters. The 76 characters does not include the CRLF (RFC 822) line break sequence. For example a multiple line LABEL property value of:
254123 Winding Way
255Any Town, CA 12345
256USA
257Would be represented in a Quoted-Printable encoding as:
258LABEL;ENCODING=QUOTED-PRINTABLE:123 Winding Way=0D=0A=
259  Any Town, CA 12345=0D=0A=
260  USA
261Property parameter substrings are delimited by a field delimiter, specified by the Semi-colon character (ASCII decimal 59). A Semi-colon in a property parameter value must be escaped with a Backslash character (ASCII 92).
262Compound property values are property values that also make use of the Semi-colon, field delimiter to separate positional components of the value. For example, the Name property is made up of the Family Name, Given Name, etc. components. A Semi-colon in a component of a compound property value must be escaped with a Backslash character (ASCII 92).
263Grouping
264There are two forms of grouping or collections supported within the vCard. A collection of vCard objects can be grouped and a collection of properties within an individual vCard can be grouped.
265vCard Grouping
266The vCard data stream can consist of multiple vCard objects. The vCard data stream can, sequentially, contain one or more vCard objects.,  In addition, the vCard data stream can contain a property whose value is a nested vCard. In both of these cases, each vCard object will be delimited by the vCard Delimiters. The vCard Reader conforming to this specification must be able to parse and process any of these combinations of vCard Groupings. The support for vCard Grouping is optional for a vCard Writer conforming to this specification.
267Property Grouping
268A Property Grouping is the definition of a method for specifying a collection of related properties within a vCard object. There is no requirement on a vCard reader that it preserve the property group name. However, the vCard reader is required to preserve the grouping of the properties.
269The Property Grouping is identified by a character string prefix to the property name; separated by the Period character (ASCII decimal 46).
270The grouping of a comment property with a telephone property is shown in the following example:
271A.TEL;HOME:+1-213-555-1234
272A.NOTE:This is my vacation home.
273The vCard Reader conforming to this specification must be able to parse and process the property grouping. The support for Property Grouping is optional for a vCard Writer conforming to this specification.
274Encodings
275The default encoding for the vCard object is 7-Bit. The default encoding can be overridden for an individual property value by using the "ENCODING" property parameter. This parameter value can be either "BASE64", "QUOTED-PRINTABLE", or "8BIT". This parameter may be used on any property.
276Some transports (e.g., MIME based electronic mail) may also provide an encoding property at the transport wrapper level. This property can be used in these cases for transporting a vCard data stream that has been defined using a default encoding other than 7-bit (e.g., 8-bit).
277Character Set
278The default character set is ASCII. The default character set can be overridden for an individual property value by using the "CHARSET" property parameter. This property parameter may be used on any property. However, the use of this parameter on some properties may not make sense.
279Any character set registered with the Internet Assigned Numbers Authority (IANA) can be specified by this property parameter. For example, ISO 8859-8 or the Latin/Hebrew character set is specified by:
280ADR;CHARSET=ISO-8859-8:...
281Some transports (e.g., MIME based electronic mail) may also provide a character set property at the transport wrapper level. This property can be used in these cases for transporting a vCard data stream that has been defined using a default character set other than ASCII (e.g., UTF-8).
282Language
283The default language is "en-US" (US English). The default language can be overridden for an individual property value by using the "LANGUAGE" property parameter. The values for this property are a string consistent with RFC 1766, Tags for the Identification of Languages. This property parameter may be used on any property. However, the use of this parameter on some properties, such as PHOTO, LOGO, SOUND, TEL, may not make sense. Canadian French would be specified by this parameter by the following:
284ADR;LANGUAGE=fr-CA:...
285Value Location
286The default location of the property value is inline with the property. However, for some properties, such as those that specify multimedia values, it is efficient to organize the property value as a separate entity (e.g., a file out on the network). The property parameter "VALUE" can be specified to override the "INLINE" location of the property value. In the case of the vCard being transported within a MIME email message, the property value can be specified as being located in a separate MIME entity with the "Content-ID" value, or "CID" for short. In this case, the property value is the Content-ID for the MIME entity containing the property value. In addition, the property value can be specified as being located out on the network within some Internet resource with the "URL" value. In this case, the property value is the Uniform Resource Locator for the Internet resource containing the property value. This property parameter may be used on any property. However, the use of this parameter on some properties may not make sense; for example the Version, Time Zone, Comment, Unique Identifier, properties . The following specifies a value not located inline with the vCard but out in the Internet:
287PHOTO;VALUE=URL;TYPE=GIF:http://www.abc.com/dir_photos/my_photo.gif
288SOUND;VALUE=CONTENT-ID:<jsmith.part3.960817T083000.xyzMail@host1.com
289Binary Values
290The vCard format supports inclusion of binary information, such as computer graphic images, digital audio, or video graphic images. The binary information may either be referenced with a Uniform Reference Locator (URL) or  placed inline in the vCard as the value of a property. Inline binary information is included as a property value after being encoded into clear-text with a Base 64 (default) or Quoted-Printable encoding
291Identification Properties
292These property types are concerned with information associated with the identification and naming of the individual or resource associated with the vCard object.
293Formatted Name
294This property specifies the formatted name string associated with the vCard object. This is the way that the name is to be displayed. It can contain desired honorific prefixes, suffixes, titles, etc. For example, "Mr. John Q. Public, Jr.", Dr. Ann Tyler, or Hon. Judge Blackwell. This property is based on the semantics of the X.520 Common Name attribute.
295This property is identified by the property name FN. The following is an example of the Formatted Name property:
296FN:Mr. John Q. Public, Esq.
297Support for this property is optional for vCard Writers conforming to this specification.
298Name
299This property specifies a structured representation of the name of the person, place or thing associated with the vCard object.
300This property is identified by the property name N. This property is defined to encapsulate the individual components of an object's name. The property value consists of the components of the name specified as positional fields separated by the Field Delimiter character (ASCII decimal 59). The property value is a concatenation of the Family Name (first field), Given Name (second field), Additional Names (third field), Name Prefix (fourth field), and Name Suffix (fifth field) strings. The following is an example of the Name property for a person:
301N:Public;John;Quinlan;Mr.;Esq.
302The following is an example of the Name property for a resource or place:
303N:Veni, Vidi, Vici;The Restaurant.
304Support for this property is mandatory for vCard Writers conforming to this specification. All vCard data streams should include this property to facilitate a common property for collating and sorting of vCard objects.
305Photograph
306This property specifies an image or photograph of the individual associated with the vCard.
307The property is identified by the property name PHOTO. For example, the following syntax is an example of a referenced image file:
308PHOTO;VALUE=URL:file:///jqpublic.gif
309 The following example is the syntax for including an inline GIF image file, using the Base 64 encoding:
310PHOTO;ENCODING=BASE64;TYPE=GIF:
311    R0lGODdhfgA4AOYAAAAAAK+vr62trVIxa6WlpZ+fnzEpCEpzlAha/0Kc74+PjyGM
312    SuecKRhrtX9/fzExORBSjCEYCGtra2NjYyF7nDGE50JrhAg51qWtOTl7vee1MWu1
313    50o5e3PO/3sxcwAx/4R7GBgQOcDAwFoAQt61hJyMGHuUSpRKIf8A/wAY54yMjHtz
314...
315Support for this property is optional for vCard Writers conforming to this specification.
316Photo Format Type
317This property parameter is provided to specify the graphics format for the Photo property value. The property parameter includes the following values:
318
319Description
320Property Parameter Value
321
322TYPE=
323
324
325Indicates Graphics Interchange Format
326GIF
327
328Indicates ISO Computer Graphics Metafile
329CGM
330
331Indicates MS Windows Metafile
332WMF
333
334Indicates MS Windows Bitmap
335BMP
336
337Indicates IBM PM Metafile
338MET
339
340Indicates IBM PM Bitmap
341PMB
342
343Indicates MS Windows DIB
344DIB
345
346Indicates an Apple Picture format
347PICT
348
349Indicates a Tagged Image File Format
350TIFF
351
352Indicates Adobe PostScript format
353PS
354
355Indicates Adobe Page Description Format
356PDF
357
358Indicates ISO JPEG format
359JPEG
360
361Indicates ISO MPEG format
362MPEG
363
364Indicates ISO MPEG version 2 format
365MPEG2
366
367Indicates Intel AVI format
368AVI
369
370Indicates Apple QuickTime format
371QTIME
372
373
374Birthdate
375This property specifies the date of birth of the individual associated with the vCard. The value for this property is a calendar date in a complete representation consistent with ISO 8601.
376This property is identified by the property name BDAY. The property value is a string conforming to the ISO 8601 calendar date, complete representation, in either basic or extended format. The following example is in the basic format of ISO 8601:
377BDAY:19950415
378The following example is in the extended format of ISO 8601:
379BDAY:1995-04-15
380Support for this property is optional for vCard Writers conforming to this specification.
381Delivery Addressing Properties
382Delivery Address
383This property specifies a structured representation of the physical delivery address for the vCard object. The property is made up of components that are based on the X.500 Post Office Box attribute, the X.520 Street Address geographical attribute, the X.520 Locality Name geographical attribute, the X.520 State or Province Name geographical attribute, the X.520 Postal Code attribute, and the X.520 Country Name geographical attribute.
384This property is identified by the property name ADR. The property value consists of components of the address specified as positional fields separated by the Field Delimiter character (ASCII decimal 59). The property value is a concatenation of the Post Office Address (first field) Extended Address (second field), Street (third field), Locality (fourth field), Region (fifth field), Postal Code (six field), and Country (seventh field) strings. An example of this property follows:
385ADR;DOM;HOME:P.O. Box 101;Suite 101;123 Main Street;Any Town;CA;91921-1234;
386Support for this property is optional for vCard Writers conforming to this specification.
387Delivery Address Type
388This property parameter specifies the sub-types of physical delivery that is associated with the delivery address. For example, the label may need to be differentiated for Home, Work, Parcel, Postal, Domestic, and International physical delivery. One or more sub-types can be specified for a given delivery address.
389The property parameter can have one or more of the following values:
390
391Description
392Property Parameter Value
393
394TYPE=
395
396
397Indicates a domestic address
398DOM
399
400Indicates an international address (Default)
401INTL
402
403Indicates a postal delivery address  (Default)
404POSTAL
405
406Indicates a parcel delivery address  (Default)
407PARCEL
408
409Indicates a home delivery address
410HOME
411
412Indicates a work delivery address  (Default)
413WORK
414
415
416The default property parameter is overridden to some other set of values by specifying one or more alternate values. For example, the default of a delivery for INTL, WORK, POSTAL and PARCEL can be reset to DOM, POSTAL, WORK and HOME in the following example:
417ADR;DOM;WORK;HOME;POSTAL:P.O. Box 101;;;Any Town;CA;91921-1234;
418Delivery Label
419This property specifies the addressing label for physical delivery to the person/object associated with the vCard. The property is intended to include the information necessary to create a formatted delivery address label. Typical information includes the name, street address, possibly a Post Office or mail drop, city, state or province, zip or postal code. An international delivery label would also include the country name. 
420This property is based on the semantics of the X.520 Postal Address attribute. This specification has added semantics to those defined by the X.500 Series standard for differentiating Home, Work, Parcel, Postal, Domestic, and International delivery label types.
421This property is identified by the property name LABEL. This property specifies the formatted delivery address label for the vCard object. An example of a domestic delivery label follows:
422LABEL;DOM;POSTAL;ENCODING=QUOTED-PRINTABLE:P. O. Box 456=0D=0A=
423123 Main Street=0D=0A=
424Any Town, CA 91921-1234
425An example of an international delivery label follows:
426LABEL;INTL;PARCEL,ENCODING=QUOTED-PRINTABLE:Suite 101=0D=0A=
427123 Main Street=0D=0A=
428Any Town, CA 91921-1234=0D=0A=
429U.S.A.
430Support for this property is optional for vCard Writers conforming to this specification. A vCard Reader supporting this property and conforming to this specification should support a minimum of four lines of text for this property.
431Delivery Label Type
432This property parameter specifies the sub-types of physical delivery that is associated with the delivery label. For example, the label may need to be differentiated for Home, Work, Parcel, Postal, Domestic, and International physical delivery. One or more sub-types can be specified for a given delivery label.
433The property parameter can have one or more of the following values:
434
435Description
436Property Parameter Value
437
438TYPE=
439
440
441Indicates a domestic address
442DOM
443
444Indicates an international address  (Default)
445INTL
446
447Indicates a postal delivery address  (Default)
448POSTAL
449
450Indicates a parcel delivery address  (Default)
451PARCEL
452
453Indicates a home delivery address
454HOME
455
456Indicates a work delivery address  (Default)
457WORK
458
459
460The default property parameter is overridden to some other set of values by specifying one or more alternate values. For example, the default of a delivery for INTL, WORK, POSTAL and PARCEL can be reset to DOM and HOME in the following example:
461LABEL;DOM;HOME,ENCODING=QUOTED-PRINTABLE:Suite 101=0D=0A=
462123 Main Street=0D=0A=
463Any Town, CA 91921-1234
464Telecommunications Addressing Properties
465These property types are concerned with information associated with the telecommunications addressing of the vCard object.
466Telephone Number
467This property specifies the canonical number string for a telephone number for telephony communication with the vCard object. The value of this property is specified in a canonical form in order to specify an unambiguous representation of the globally unique telephony endpoint. This property is based on the X.520 Telephone Number attribute.
468The canonical form cannot be dialed without first being transformed by a dialing algorithm. The dialing algorithm combines the canonical number string with knowledge of the local dialing procedures, in effect at the time of call placement to produce actual dialing instructions. The actual dialing algorithm is outside the scope of this specification.
469Two important canonical forms allowed by this specification are:
470*	Apple Computer's Representation of a Canonical Static DeviceID in The Telephony Suite, version 1.0,
471*	Microsoft TAPI in the Microsoft Windows 3.1 Telephony Programmer's Guide, version 1.0.
472Software which creates this property can store a string in these allowed formats. Dialing software should be prepared to parse numbers from either of the supported formats; as neither format is considered to be technically costly to support.
473This property is identified by the property name TEL. An example of this property follows:
474TEL;PREF;WORK;MSG;FAX:+1-800-555-1234
475Support for this property is optional for vCard Writers conforming to this specification.
476Telephone Type
477This property parameter specifies the sub-type of telephone that is associated with the telephone number (e.g., Home, Work, Cellular, Facsimile, Video, Modem, Message Service, or Preferred). One or more sub-type values can be specified for a given telephone number.
478The property parameter can have one or more of the following values:
479
480Description
481Property Parameter Value
482
483TYPE=
484
485
486Indicates preferred number
487PREF
488
489Indicates a work number
490WORK
491
492Indicates a home number
493HOME
494
495Indicates a voice number (Default)
496VOICE
497
498Indicates a facsimile number
499FAX
500
501Indicates a messaging service on the number
502MSG
503
504Indicates a cellular number
505CELL
506
507Indicates a pager number
508PAGER
509
510Indicates a bulletin board service number
511BBS
512
513Indicates a MODEM number
514MODEM
515
516Indicates a car-phone number
517CAR
518
519Indicates an ISDN number
520ISDN
521
522Indicates a video-phone number
523VIDEO
524
525The default property parameter is overridden to some other set of values by specifying one or more alternate values. For example, the default of a VOICE telephone number can be reset to a WORK and HOME, VOICE and FAX telephone number in the following example:
526TEL;WORK;HOME;VOICE;FAX:+1-800-555-1234
527Electronic Mail
528This property specifies the address for electronic mail communication with the vCard object. The address is in the form of a specific addressing type. For example, the Internet mail address for John Public might be "John.Public@abc.com" or the CompuServe Information Service address might be "71234,5678".This property is identified by the property name EMAIL.
529An example of this property follows:
530EMAIL;INTERNET:john.public@abc.com
531Support for this property is optional for vCard Writers conforming to this specification.
532Electronic Mail Type
533This property parameter specifies the type of electronic mail address. The following are some example values for this property parameter:
534
535Description
536Property Parameter Value
537
538TYPE=
539
540
541Indicates America On-Line
542AOL
543
544Indicates AppleLink
545AppleLink
546
547Indicates AT&T Mail
548ATTMail
549
550Indicates CompuServe Information Service
551CIS
552
553Indicates eWorld
554eWorld
555
556Indicates Internet SMTP (default)
557INTERNET
558
559Indicates IBM Mail
560IBMMail
561
562Indicates MCI Mail
563MCIMail
564
565Indicates PowerShare
566POWERSHARE
567
568Indicates Prodigy information service
569PRODIGY
570
571Indicates Telex number
572TLX
573
574Indicates X.400 service
575X400
576
577
578Mailer
579This property parameter specifies the type of electronic mail software that is in use by the individual associated with the vCard object. This information may provide assistance to a correspondent regarding the type of data representation which can be used, and how they may be packaged. This property parameter is based on currently accepted practices within the Internet MIME community with the "X-Mailer" header field.
580This property is identified by the property name MAILER. Support for this property is optional for vCard Writers conforming to this specification. An example of this property follows:
581MAILER:ccMail 2.2
582Geographical Properties
583These property types are concerned with geographical positions or region information associated with the vCard object.
584Time Zone
585This property specifies information related to the standard time zone of the vCard object. The time zone is a string as specified in a manner consistent with ISO 8601. It is an offset from Coordinated Universal Time (UTC). An ISO 8601 UTC offset, in basic format, is specified as a positive or negative difference in units of hours and minutes (e.g., +hhmm). If minutes are zero, then they may be omitted and the format would be specified in units of hours (e.g., +hh). The time is specified as a 24-hour clock. Hour valult property parameter is overridden to some other set of values by specifying one or more alternate values. For example, the default of a delivery for INTL, WORK, POSTAL and PARCEL can be reset to DOM, POSTAL, WORK and HOME in the following example:
586ADR;DOM;WORK;HOME;POSTAL:P.O. Box 101;;;Any Town;CA;91921-1234;
587Delivery Label
588This property specifies the addressing label for physical delivery to the person/object associated with the vCard. The property is intended to include the information necessary to create a formatted delivery address label. Typical information includes the name, street address, possibly a Post Office or mail drop, city, state or province, zip or postal code. An international delivery label would also include the country name. 
589This property is based on the semantics of the X.520 Postal Address attribute. This specification has added semantics to those defined by the X.500 Series standard for differentiating Home, Work, Parcel, Postal, Domestic, and International delivery label types.
590This property is identified by the property name LABEL. This property specifies the formatted delivery address label for the vCard object. An example of a domestic delivery label follows:
591LABEL;DOM;POSTAL;ENCODING=QUOTED-PRINTABLE:P. O. Box 456=0D=0A=
592123 Main Street=0D=0A=
593Any Town, CA 91921-1234
594An example of an international delivery label follows:
595LABEL;INTL;PARCEL,ENCODING=QUOTED-PRINTABLE:Suite 101=0D=0A=
596123 Main Street=0D=0A=
597Any Town, CA 91921-1234=0D=0A=
598U.S.A.
599Support for this property is optional for vCard Writers conforming to this specification. A vCard Reader supporting this property and conforming to this specification should support a minimum of four lines of text for this property.
600Delivery Label Type
601This property parameter specifies the sub-types of physical delivery that is associated with the delivery label. For example, the label may need to be differentiated for Home, Work, Parcel, Postal, Domestic, and International physical delivery. One or more sub-types can be specified for a given delivery label.
602The property parameter can have one or more of the following values:
603
604Description
605Property Parameter Value
606
607TYPE=
608
609
610Indicates a domestic address
611DOM
612
613Indicates an international address  (Default)
614INTL
615
616Indicates a postal delivery address  (Default)
617POSTAL
618
619Indicates a parcel delivery address  (Default)
620PARCEL
621
622Indicates a home delivery address
623HOME
624
625Indicates a work delivery address  (Default)
626WORK
627
628
629The default property parameter is overridden to some other set of values by specifying one or more alternate values. For example, the default of a delivery for INTL, WORK, POSTAL and PARCEL can be reset to DOM and HOME in the following example:
630LABEL;DOM;HOME,ENCODING=QUOTED-PRINTABLE:Suite 101=0D=0A=
631123 Main Street=0D=0A=
632Any Town, CA 91921-1234
633Telecommunications Addressing Properties
634These property types are concerned with information associated with the telecommunications addressing of the vCard object.
635Telephone Number
636This property specifies the canonical number string for a telephone number for telephony communication with the vCard object. The value of this property is specified in a canonical form in order to specify an unambiguous representation of the globally unique telephony endpoint. This property is based on the X.520 Telephone Number attribute.
637The canonical form cannot be dialed without first being transformed by a dialing algorithm. The dialing algorithm combines the canonical number string with knowledge of the local dialing procedures, in effect at the time of call placement to produce actual dialing instructions. The actual dialing algorithm is outside the scope of this specification.
638Two important canonical forms allowed by this specification are:
639*	Apple Computer's Representation of a Canonical Static DeviceID in The Telephony Suite, version 1.0,
640*	Microsoft TAPI in the Microsoft Windows 3.1 Telephony Programmer's Guide, version 1.0.
641Software which creates this property can store a string in these allowed formats. Dialing s
642
643Description
644Property Parameter Value
645
646TYPE=
647
648
649Indicates Graphics Interchange Format
650GIF
651
652Indicates ISO Computer Graphics Metafile
653CGM
654
655Indicates MS Windows Metafile
656WMF
657
658Indicates MS Windows Bitmap
659BMP
660
661Indicates IBM PM Metafile
662MET
663
664Indicates IBM PM Bitmap
665PMB
666
667Indicates MS Windows DIB
668DIB
669
670Indicates an Apple Picture format
671PICT
672
673Indicates Tagged Image File Format
674TIFF
675
676Indicates Adobe Page Description Format
677PDF
678
679Indicates Adobe PostScript
680PS
681
682Indicates ISO JPEG format
683JPEG
684
685Indicates ISO MPEG format
686MPEG
687
688Indicates ISO MPEG version 2 format
689MPEG2
690
691Indicates Intel AVI format
692AVI
693
694Indicates Apple QuickTime format
695QTIME
696
697
698Agent
699This property specifies information about another person who will act on behalf of the vCard object. Typically this would be an area administrator, assistant, or secretary for the individual. A key characteristic of the Agent property is that it represents somebody or something which is separately addressable. For example, if all phone calls or e-mail messages are normally screened by an agent, this property may not be needed. On the other hand, if an agent can act as a proxy, and may otherwise need to be contacted separately, then an Agent property is useful.
700This property is equivalent to nesting another vCard with the specified vCard.
701This property is identified by the property name AGENT. The value of this property is a string containing another vCard object. An example of this property follows:
702AGENT:
703BEGIN:VCARD
704VERSION:2.1
705N:Friday;Fred
706TEL;WORK;VOICE:+1-213-555-1234
707TEL;WORK;FAX:+1-213-555-5678
708END:VCARD
709Support for this property is optional for vCard Writers conforming to this specification.
710Organization Name and Organizational Unit
711This property specifies the name and optionally the unit(s) of the organization associated with the vCard object. This property is based on the X.520 Organization Name attribute and the X.520 Organization Unit attribute. For example, "The AB Corporation" and the "North American Division".
712This property is identified by the property name ORG. This property is defined to encapsulate the Organization Name and Organization Unit properties as sub-properties. The property value consists of the components of the organization specified as positional fields separated by the Field Delimiter (ASCII decimal 59). The property value is a concatenation of the Organization Name (first field), Organizational Unit (second field) strings. Additional positional fields, if specified, contain additional Organizational Units. The following is an example of the Organization property:
713ORG:ABC, Inc.;North American Division;Marketing
714Support for this property is optional for vCard Writers conforming to this specification.
715Explanatory Properties
716These property types are concerned with additional explanations, such as that related to national language support, annotation, or encoding of binary information about the vCard object.
717Comment
718This property specifies supplemental information or a comment that is associated with the vCard. With the use of property grouping, the association can be limited to a group of properties. The property is based on the X.520 Description attribute.
719This property is identified by the property name NOTE. An example of this property follows:
720NOTE;ENCODING=QUOTED-PRINTABLE:This facsimile machine if operational=
721 0830 to 1715 hours=0D=0A=
722Monday through Friday. Call +1-213-555-1234 if you have problems=0D=0A=
723with access to the machine.
724Support for this property is optional for vCard Writers conforming to this specification.
725Last Revision
726This property specifies the combination of the calendar date and time of day of the last update to the vCard object. The property value is a character string conforming to the basic or extended format of ISO 8601. The value can either be in terms of local time or UTC.
727This property is identified by the property name REV. Valid values for this property are a character string representing a combination of the calendar date and time of day conforming to the basic or extended format of ISO 8601. The time of day can be either local time or UTC. The following example is in the basic format and local time of ISO 8601:
728REV:19951031T222710
729The following example is in the extended format and UTC time of ISO 8601:
730REV:1995-10-31T22:27:10Z
731Support for this property is optional for vCard Writers conforming to this specification.
732Sound
733This property specifies a sound annotation for the vCard object. By default, if this property is not grouped with other properties it specifies the pronunciation of the Formatted Name property of the vCard object. Such information may be in the form of a string of characters representing a phonetic sound or in the form of a digitized sound, or both; subject to the limitations imposed by the encoding used to communicate the vCard.
734This property is identified by the property name SOUND. Valid values for this property are either a string representation, a reference to a digital audio representation, or an inline digital audio representation of the phonetic pronunciation of the Formatted Name property. The following example shows the string based phonetic representation:
735SOUND:JON Q PUBLIK
736The following example shows the digtial sound representation and URL based value:
737SOUND;VALUE=URL:file///multimed/audio/jqpublic.wav
738The following example shows the digtial sound representation and INLINE value:
739SOUND;WAVE;BASE64:	
740    UklGRhAsAABXQVZFZm10IBAAAAABAAEAESsAABErAAABAAgAZGF0YesrAACAg4eC
741    eXR4e3uAhoiIiYmKjIiDfnx5eX6CgoKEhYWDenV5fH6BhISGiIiDfHZ2eXt/hIiK
742    jY2IhH12d3Vyc3uDiIiFf3l7fn18eXl+houFf319fnyAgHl5eoCIiISChIeAfnt2
743...
744Support for this property is optional for vCard Writers conforming to this specification.
745Sound Digital Audio Type
746This property parameteris provided to specify the type of the digital audio Pronunciation for the vCard object. The property parameter can have the following values:
747
748Description
749Property Parameter Value
750
751TYPE=
752
753
754Indicates Wave format
755WAVE
756
757Indicates MIME basic audio type
758PCM
759
760Indicates AIFF format
761AIFF
762
763
764Uniform Resource Locator
765This property specifies a value that represents a Uniform Resource Locator (URL). An URL is a representation of an Internet location that can be used to obtain real-time information about the vCard object. Application of this property might be to specify the location of a publicly accessible directory where up-to-date or additional information on the individual or resource associated with a vCard can be found.
766This property is identified by the property name URL. Valid values for this property are a string conforming to the IETF RFC 1738, Uniform Resource Locators. The following is an example of this property:
767URL:http://abc.com/pub/directory/northam/jpublic.ecd
768Support for this property is optional for vCard Writers conforming to this specification.
769Unique Identifier
770This property specifies a value that represents a persistent, globally unique identifier associated with the object. The property can be used as a mechanism to relate different vCard objects. Some examples of valid forms of unique identifiers would include ISO 9070 formal public identifiers (FPI), X.500 distinguished names, machine-generated "random" numbers with a statistically high likelihood of being globally unique and Uniform Resource Locators (URL). If an URL is specified, it is suggested that the URL reference a service which will produce an updated version of the vCard.
771This property is identified by the property name UID. This property is provided to enable a vCard Reader and Writer to uniquely identify either a vCard object instance or properties within a vCard object. Valid values for this property are a unique character string. The following is an example of this property:
772UID:19950401-080045-40000F192713-0052
773Support for this property is optional for vCard Writers conforming to this specification.
774Version
775This property specifies the identifier corresponding to the highest version number of the vCard Specification supported by the implementation that created the vCard object. The value of this property must be 2.1 to correspond to this specification.. 
776This property is identified by the property name VERSION. The following is an example of this property:
777VERSION:2.1
778Support for this property is mandatory for implementations conforming to this specification. This property must appear within the vCard data stream.
779Security Properties
780These property types are concerned with the security of the information in the vCard object.
781Public Key
782This property specifies the public encryption key associated with the vCard object.
783This property is identified by the property name KEY. Valid values for this property are a public key that conforms to a bilaterally agreed to representation. If the representation is a binary format, then the public key must be further encoded. The default format is clear-text. If a binary format is used, then it is specified by the property parameter. Support for this property is optional for vCard Writers conforming to this specification.
784Key Type
785This property parameter is provided to specify the type of the public key for the vCard object. The property parameter can have the following values:
786
787Description
788Property Parameter Value
789
790TYPE=
791
792
793Indicates a X.509 public key certificate type of key
794X509
795
796Indicates an IETF PGP type of key
797PGP
798
799Miscellaneous Properties
800Extensions
801The vCard provides a �standard mechanism for doing non-standard things�. This extension support is provided for implementers to "push the envelope" on the existing version of the specification. Extension properties are specified by property and/or property parameter names that have the initial sub-string of X- (the two character sequence: Capital X character followed by the Dash character. It is recommended that vendors concatenate onto this sentinel an added short sub-string to identify the vendor. This will facilitate readability of the extensions and minimize possible collision of names between different vendors. For example, the following might be the ABC vendor's extension for a video-clip form of identification property:
802X-ABC-VIDEO;MPEG2:http://lonestar.bubbas.org/billibob.mpg
803or, the following example might be an extension for grouping vCard objects into a distribution list for the Design Work Group. 
804BEGIN:VCARD
805VERSION:2.1
806X-DL;Design Work Group:List Item 1;List Item 2;List Item 3
807BEGIN:VCARD
808UID:List Item 1
809N:John Smith
810TEL:+1-213-555-1111
811END:VCARD
812BEGIN:VCARD
813UID:List Item 2
814N:I. M. Big
815TEL:+1-213-555-9999
816END:VCARD
817BEGIN:VCARD
818UID:List Item 3
819N:Jane Doe
820TEL:+1-213-555-5555
821END:VCARD
822END:VCARD
823At present, there is no registration authority for names of extension properties.
824Support for this property is mandatory for implementations conforming to this specification. However, an implementation may not be able to act on the extension property. Conformance only requires that an implementation be able to parse vCard data streams with extensions. The implementation need not act on them.
825Formal Definition
826The following modified Backus-Naur Notation (BNF) is provided to assist developers in building parsers for the vCard.
827This syntax is written according to the form described in RFC 822, but it references just this small subset of RFC 822 literals:
828  CR			=  <ASCII CR, carriage return>  ; (     15,      13.)
829  LF			=  <ASCII LF, linefeed>         ; (     12,      10.)
830  CRLF		=  CR LF
831  SPACE		=  <ASCII SP, space>            ; (     40,      32.)
832  HTAB		=  <ASCII HT, horizontal-tab>   ; (     11,       9.)
833All literal property names are valid as upper, lower, or mixed case.
834ws		= 1*(SPACE / HTAB)
835	; "whitespace," one or more spaces or tabs
836wsls		= 1*(SPACE / HTAB / CRLF)
837	; whitespace with line separators
838word		= <any printable 7bit us-ascii except []=:., >
839groups		= groups "." word
840		/ word
841vcard_file	= [wsls] vcard [wsls]
842vcard		= "BEGIN" [ws] ":" [ws] "VCARD" [ws] 1*CRLF
843		 items *CRLF "END" [ws] ":" [ws] "VCARD"
844items		= items *CRLF item
845		/ item
846	; these may be "folded"
847item		= [groups "."] name
848		  [params] ":" value CRLF
849		/ [groups "."] "ADR"
850		  [params] ":" addressparts CRLF
851		/ [groups "."] "ORG"
852		  [params] ":" orgparts CRLF
853		/ [groups "."] "N"
854		  [params] ":" nameparts CRLF
855		/ [groups "."] "AGENT"
856		  [params] ":" vcard CRLF
857	; these may be "folded"
858name		= "LOGO" / "PHOTO" / "LABEL" / "FN" / "TITLE"
859		/ "SOUND" / "VERSION" / "TEL" / "EMAIL" / "TZ" / "GEO" / "NOTE"
860		/ "URL" / "BDAY" / "ROLE" / "REV" / "UID" / "KEY"
861		/ "MAILER" / "X-" word 
862	; these may be "folded"
863value		= 7bit / quoted-printable / base64
8647bit		= <7bit us-ascii printable chars, excluding CR LF>
8658bit		= <MIME RFC 1521 8-bit text>
866quoted-printable = <MIME RFC 1521 quoted-printable text>
867base64		= <MIME RFC 1521 base64 text>
868	; the end of the text is marked with two CRLF sequences
869	; this results in one blank line before the start of the next property
870params		= ";" [ws] paramlist
871paramlist	= paramlist [ws] ";" [ws] param
872		/ param
873param		= "TYPE" [ws] "=" [ws] ptypeval
874		/ "VALUE" [ws] "=" [ws] pvalueval
875		/ "ENCODING" [ws] "=" [ws] pencodingval
876		/ "CHARSET" [ws] "=" [ws] charsetval
877		/ "LANGUAGE" [ws] "=" [ws] langval
878		/ "X-" word [ws] "=" [ws] word
879		/ knowntype
880ptypeval	= knowntype / "X-" word
881pvalueval	= "INLINE" / "URL" / "CONTENT-ID" / "CID" / "X-" word
882pencodingval 	= "7BIT" / "8BIT" / "QUOTED-PRINTABLE" / "BASE64" / "X-" word
883charsetval	= <a character set string as defined in Section 7.1 of 
884		RFC 1521>
885langval		= <a language string as defined in RFC 1766>
886addressparts	= 0*6(strnosemi ";") strnosemi
887	; PO Box, Extended Addr, Street, Locality, Region, Postal Code,
888	Country Name
889orgparts	= *(strnosemi ";") strnosemi
890	; First is Organization Name, remainder are Organization Units.
891nameparts	= 0*4(strnosemi ";") strnosemi
892	; Family, Given, Middle, Prefix, Suffix.
893	; Example:Public;John;Q.;Reverend Dr.;III, Esq.
894strnosemi	= *(*nonsemi ("\;" / "\" CRLF)) *nonsemi
895	; To include a semicolon in this string, it must be escaped
896	; with a "\" character.
897nonsemi		= <any non-control ASCII except ";">
898knowntype	= "DOM" / "INTL" / "POSTAL" / "PARCEL" / "HOME" / "WORK"
899		/ "PREF" / "VOICE" / "FAX" / "MSG" / "CELL" / "PAGER"
900		/ "BBS" / "MODEM" / "CAR" / "ISDN" / "VIDEO"
901		/ "AOL" / "APPLELINK" / "ATTMAIL" / "CIS" / "EWORLD"
902		/ "INTERNET" / "IBMMAIL" / "MCIMAIL"
903		/ "POWERSHARE" / "PRODIGY" / "TLX" / "X400"
904		/ "GIF" / "CGM" / "WMF" / "BMP" / "MET" / "PMB" / "DIB"
905		/ "PICT" / "TIFF" / "PDF" / "PS" / "JPEG" / "QTIME"
906		/ "MPEG" / "MPEG2" / "AVI"
907		/ "WAVE" / "AIFF" / "PCM"
908		/ "X509" / "PGP"
909
910
911Section 3 : Internet Recommendations
912[DS4]	1	
913Recommended Practice with SMTP/MIME
914The vCard information can be transported through SMTP/MIME based electronic mail services. Interoperability of vCard information over SMTP/MIME transports can be better assured by following a common set of recommended practices for encapsulation of the vCard.
915Text/Plain Content Type
916Without any change to existing SMTP or MIME compliant user agents, a vCard can be included within Internet email messages. This might be the case for an existing, simple user agent such as a legacy SMTP mail system. While this approach provides for transport of vCards over SMTP services, it does not allow for the end user to take advantage of the full capabilities of either the vCard or Internet email (i.e., MIME) functionality.
917The following demonstrates how a vCard can be included as an epilog to a SMTP message made up of a RFC 822 message. This may be an initial method for incorporating vCard objects into SMTP messages.
918Date: Thr, 25 Jan 96 0932 EDT
919From: john.smith@host.com
920Subject: Re: RFC822 vCard Example
921Sender: john.smith@host.com
922To: smartin@host2.com
923Message-ID: <JOHNSMITH.960125T091020.xyzMail@host3.com>
924
925Steve:  Thanks for the call earlier today. I am unable to
926use your material at this time. Please feel free to contact
927me in the future.
928BEGIN:VCARD
929VERSION:2.1
930N:Smith;John;M.;Mr.;Esq.
931TEL;WORK;VOICE;MSG:+1 (919) 555-1234
932TEL;WORK;FAX:+1 (919) 555-9876
933ADR;WORK;PARCEL;POSTAL;DOM:Suite 101;1 Central St.;Any Town;NC;27654
934END:VCARD
935The following example demonstrates how a vCard can be included as a separate text/plain content portion within current MIME user agents.
936Date: Fri, 26 Jan 1996 07:53:00 -0500
937From: smartin@host2.com
938Subject: RE: Text/Plain MIME vCard Example
939To: fdawson@VNET.IBM.COM
940Mime-Version: 1.0
941Content-Type: multipart/mixed; boundary=vcard
942Message-ID: <ABC-1.00-Note-martin-steve-0824475754>
943
944--vcard
945Content-Type:text/plain; charset=us-ascii
946Content-Transfer-Encoding: 7bit
947John:  I have looked over my material and feel that you may
948have over looked a couple of appropriate pieces. Please give
949me a call so that we can discuss further.
950--vcard
951Content-Type:text/plain; charset=us-ascii; name="MARTIN.VCF"
952
953BEGIN:VCARD
954VERSION:2.1
955N:Martin;Stephen
956TEL;HOME;VOICE:+1 (210) 555-1357
957TEL;HOME;FAX:+1 (210) 555-0864
958ADR;WORK;PARCEL;POSTAL;DOM:123 Cliff Ave.;Big Town;CA;97531
959END:VCARD
960--vcard--
961Text/X-vCard Content Type
962A vCard object may also be transferred in a (RFC 1521) MIME entity as a non-standard "text/x-vCard" content-type. This (RFC 1521) MIME type maybe useful in those cases where the MIME compliant messaging service does not yet support the "application/directory" and "multipart/related" MIME content-types and yet the specificity of a calendaring and scheduling media type is required.
963The following example demonstrates how a vCard can be included as a separate non-standard text/x-vCard content portion within current MIME user agents.
964Date: Fri, 26 Jan 1996 07:53:00 +0000
965From: smartin@host2.com
966Subject: RE: Text/x-vCard MIME vCard Example
967To: fdawson@VNET.IBM.COM
968Mime-Version: 1.0
969Content-Type: multipart/mixed; boundary=vcard
970Message-ID: <ABC-1.00-Note-martin-steve-0824475754>
971
972--vcard
973Content-Type:text/plain; charset=us-ascii
974Content-Transfer-Encoding: 7bit
975John:  I have looked over my material and feel that you may
976have over looked a couple of appropriate pieces. Please give
977me a call so that we can discuss further.
978--vcard
979Content-Type:text/x-vCard; charset=us-ascii; name="MARTIN.VCF"
980
981BEGIN:VCARD
982VERSION:2.1N:Martin;Stephen
983TEL;HOME;VOICE:+1 (210) 555-1357
984TEL;HOME;FAX:+1 (210) 555-0864
985ADR;WORK;PARCEL;POSTAL;DOM:123 Cliff Ave.;Big Town;CA;97531
986END:VCARD
987--vcard--
988Application/Directory Content Type
989The Internet Engineering Task Force (IETF) Access and Searching of Internet Directories (ASID) working group has produced an Internet Draft defining the "application/directory" MIME content type. The current draft name is draft-ietf-asid-mime-direct-01.txt. This specification is intended to be aligned with this work. Internet Drafts are working documents of an IETF working group, valid for at most six months, and should be considered "works in progress". 
990This MIME content type was designed to be used to transport directory information across MIME based electronic mail services. The internet draft is directly applicable to the exchange of business card data, such as that defined by the vCard specification.
991The versit PDI Team has worked within the IETF ASID Working Group to draft an application/directory profile that registers the method for transporting a vCard as an application/directory Content-Type. The current draft name is draft-ietf-asid-mime-vcard-00.txt. This work is expected to be progressed to a Request For Comment after the publication of this version of the vCard specification. In the interim, the following guidelines are provided to describe how a vCard might be conveyed using the application/directory draft specification.
992A vCard should be included in a MIME message that has a Content-Type header field value of "multipart/related". The vCard is included in the message as the primary body part. The position of the body part entity can also be specified with the "start=" parameter. This MIME body part entity has a Content-Type body part header field value of "application/directory" with a "profile" parameter value of "vcard". Any vCard binary information, such as a logo, picture, or digital audio pronunciation can be included inline within the vCard, as is specified by the vCard specification. Preferably, the binary information should be extracted from the vCard object and contained in the MIME message as secondary body part entities. The binary content in the secondary body part entities can be referenced from within the vCard object through the use of the "VALUE=" property parameter. In this latter case, the binary information should be transformed into a content type nominally supported by MIME user agents. For image content, this would be the Graphics Image Format (GIF) or Joint Picture Encoding Group (JPEG) formats. For audio content, this would be the 8-bit mu-law (PCM) format specified by the MIME specification.
993The following example defines how this might be specified:
994Date: Mon, 29 Jan 96 0830 EDT
995From: john.smith@host.com
996Subject: Re: MIME application/directory vCard Example
997Sender: john.smith@host.com
998To: smartin@host2.com
999Message-ID: <JOHNSMITH.960129T083020.xyzMail@host3.com>
1000Content-Type: multipart/related; boundary="vcard"; 
1001			type=application/directory;
1002			start=<JOHNSMITH.part1.960129T083020.xyzMail@host3.com>
1003--vcard
1004Content-Type: application/directory; charset=us-ascii;
1005			source="file://versit.or2"; profile="vcard"
1006Content-ID: <<JOHNSMITH.part1.960129T083020.xyzMail@host3.com>
1007BEGIN:VCARD
1008VERSION:2.1
1009N:Smith;John;M.;Mr.;Esq.
1010TEL;WORK;VOICE;MSG:+1 (919) 555-1234
1011TEL;CELL:+1 (919) 554-6758
1012TEL;WORK;FAX:+1 (919) 555-9876
1013PHOTO;GIF;MIME:<<JOHNSMITH.part3.960129T083020.xyzMail@host3.com>
1014ADR;WORK;PARCEL;POSTAL;DOM:Suite 101;1 Central St.;Any Town;NC;27654
1015END:VCARD
1016--vcard
1017Content-Type: text/plain; charset=us-ascii
1018Content-ID: <<JOHNSMITH.part2.960129T083020.xyzMail@host3.com>
1019Steve:
1020I am not in the office today. You may want to try
1021reaching me either on my cellular telephone or fax your
1022new ideas to my office.
1023Let's setup a face-to-face meeting later this week, after I review
1024your updated material. I am including a picture in my business card
1025data, since we have not met yet.
1026-- John
1027--vcard
1028Content-Type: image/gif
1029Content-ID: <<JOHNSMITH.part3.960129T083020.xyzMail@host3.com>
1030...image data would go here...
1031--vcard--
1032Recommended Practice with HTTP/HTML
1033A vCard object should be transferred over HTTP with the non-standard  MIME type/subtype value of "text/x-vCard". The non-standard subtype should be used because the vCard has not been registered as a MIME media type with the IANA.
1034The vCard information can be captured with a FORM type of HTML document. Interoperability of of vCard information can be better assured by following a common set of recommended practices for mapping vCard information into and out of HTML documents.
1035Form Element Usage
1036The HTML FORM element is a useful method for capturing data intended for input into individual vCard property values. The following recommended practices are provided for such use.
1037Mapping To INPUT Element Attribute Names
1038An HTML form data set is a useful mechanism for capturing vCard data within the Internet WWW. The use of a consistent naming scheme for the name attributes within a form element will permit implementations to support automatic fill-in of forms with existing vCard data. In addition, such a consistent naming scheme will provide a greater assurance of interoperability between HTML based applications that use vCard data.
1039The following table provides a recommended mapping of vCard properties and name attributes within a form element.
1040Identification Properties
1041Description
1042Attribute Name
1043Comment
1044
1045Formatted Name
1046FN
1047
1048
1049Name
1050N
1051Individual components of name property are captured as separate input elements with the names N.Family, N.First, N.Middle, N.Prefix, N.Suffix.
1052
1053Photograph
1054PHOTO
1055Only the URL based specification is supported by this mapping. Value is the URL for the graphic.
1056
1057Photograph Format Type
1058PHOTO.Type
1059Where the value is one of the enumerated strings defined by the vCard specification. 
1060
1061Birthdate
1062BDAY
1063
1064
1065
1066Delivery Addressing Properties
1067Description
1068Attribute Name
1069Comment
1070
1071Delivery Address
1072ADR
1073TYPE=TEXTAREA
1074
1075Address Type
1076ADR.x
1077TYPE=CHECKBOX. Separate input elements are used to capture the possible delivery types. The elements are named ADR.x, where x is one of the enumerated strings defined by the vCard specification.
1078
1079Delivery Label
1080LABEL
1081
1082
1083Label Type
1084LABEL.x
1085TYPE=CHECKBOX. Separate input elements are used to capture the possible delivery types. The elements are named LABEL.x, where x is one of the enumerated strings defined by the vCard specification.
1086
1087
1088Telecommunications Addressing Properties
1089Description
1090Attribute Name
1091Comment
1092
1093Telephone Number
1094TEL
1095
1096
1097Telephone Type
1098TEL.x
1099TYPE=CHECKBOX. Separate input elements are used to capture the possible telephone types. The elements are named TEL.x, where x is one of the enumerated strings defined by the vCard specification.
1100
1101Electronic Mail Address
1102EMAIL
1103
1104
1105Electronic Mail Address Type
1106EMAIL.Type
1107Selection option from a list of alternatives.
1108
1109Mailer
1110MAILER
1111
1112
1113
1114Geographical Properties
1115Description
1116Attribute Name
1117Comment
1118
1119Time Zone
1120TZ
1121
1122
1123Geographic Position
1124GEO
1125
1126
1127
1128Organizational Properties
1129Description
1130Attribute Name
1131Comment
1132
1133Title
1134TITLE
1135
1136
1137Business Category
1138ROLE
1139
1140
1141Logo
1142LOGO
1143Only the URL based specification is supported by this mapping. Value is the URL for the graphic.
1144
1145Logo Format Type
1146LOGO.Type
1147Where the value is one of the enumerated strings defined by the vCard specification. 
1148
1149Agent
1150
1151Captured through a separate form element using the mapping defined in these tables.
1152
1153Organization
1154ORG
1155TYPE=TEXT. Separate input elements for the organizational name and unit. The name ORG.Name is used to capture the organizational name. The name ORG.UNIT is used to capture the organizational unit. If there are multiple organizational units, it is captured in a form with name attributes ORG.UNIT1, ORG.UNIT2, etc.
1156
1157
1158Explanatory Properties
1159Description
1160Attribute Name
1161Comment
1162
1163Comment
1164NOTE
1165TYPE=TEXT
1166
1167Last Revision
1168REV
1169A hidden field.
1170
1171Version
1172VERSION
1173A hidden field with the value set to the string �2.1�.
1174
1175Language
1176LANG
1177A hidden field with the value set to the string associated with the default language used in the form (e.g., US-eng).
1178
1179Sound
1180SOUND
1181TYPE=TEXT
1182
1183Sound Type
1184N/A
1185
1186
1187Uniform Resource Locator
1188URL
1189TYPE=TEXT
1190
1191Unique Identifier
1192UID
1193TYPE=TEXT
1194
1195Binary Encoding
1196BE.x
1197Where x is one of the enumerated encoding types defined by the vCard specification.
1198
1199
1200Security Properties
1201Description
1202Attribute Name
1203Comment
1204
1205Public Key
1206KEY
1207
1208
1209Key Type
1210KEY.Type.x
1211Where x is one of the enumerated encoding types defined by the vCard specification.
1212
1213MISCELLANEOUS PROPERTIES
1214
1215
1216
1217Extensions
1218X-x
1219Where x is a string defined by the extension author.
1220
1221
1222Where multiple properties (e.g., telephone numbers) appear, a label prefix should be used. For example, telephone #1 might have a name attribute of �A.TEL�, telephone #2 might have a name attribute of �B.TEL�, etc.
1223Example HTML Code
1224The following HTML code is an example of the use of the mapping of INPUT element attributes names to vCard property names. The code can be used to capture input data for creating a vCard on a Web homepage.
1225<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
1226<head>
1227<title>Create Your Own Versitcard</title>
1228</head>
1229<IMG src="versit.gif">
1230<h1>Create Your Own Versitcard</h1>
1231<P> Fill out this form and we'll
1232create a <b>Versitcard</b> for you and send it to the email address of your choice,
1233along with more information on the Versitcard format.</P>
1234<hr><!-- Identification And Organizational Properties -->
1235<FORM METHOD="POST" ACTION="/cgi-bin/vcard-maker">
1236Formatted Name:<INPUT name="FN" type=text size=32 maxlength=64
1237value=""><br>
1238Phoenetic Pronunciation:<INPUT name="SOUND" type=text size=32 maxlength=128 value=""><br>
1239Company Name:<INPUT name="ORG.Name" type=text  size=32 maxlength=64
1240value=""><br>
1241Company Unit:<INPUT name="ORG.Unit" type=text size=32
1242maxlength=64 value=""><br>
1243Title:<INPUT name="TITLE" type=text size=32 maxlength=64
1244value="">
1245<hr><!-- Name Property Component Values -->
1246Family Name:<INPUT name="N.Family" type=text size=32 maxlength=64
1247value=""><br>
1248Given Name:<INPUT name="N.Given" type=text size=32
1249maxlength=64 value=""><br>
1250Middle Name:<INPUT name="N.Middle" type=type size=32
1251maxlength=64 value=""><br>
1252Name Prefix:<INPUT name="N.Prefix" type=type size=32
1253maxlength=64 value=""><br>
1254Name Suffix:<INPUT name="N.Suffix" type=type size=32
1255maxlength=64 value=""><br>
1256<hr><!-- Delivery Addressing Properties -->
1257Delivery Label:<TEXTAREA name="LABEL" cols=64 ROWS=5>
1258</TEXTAREA><br><br>
1259Post Office Address:<INPUT name="ADR.POAddr" type=text size=32
1260maxlength=64 value=""><br>
1261Extended Address:<INPUT name="ADR.ExtAddr" type=text size=32
1262maxlength=64 value=""><br>
1263Street Address:<INPUT name="ADR.Street" type=text size=62
1264maxlength=128 value=""><br>
1265City:<INPUT name="ADR.Locality" type=text size=16 maxlength=32
1266value="">
1267Region:<INPUT name="ADR.Region" type=text size=16 maxlength=32
1268value="">
1269Postal Code:<INPUT name="ADR.PostalCode" type=text size=16 maxlength=32
1270value=""><br>
1271Country Name:<INPUT name="ADR.CountryName" type=text size=16 maxlength=32 value="USA">
1272<INPUT type=checkbox name="ADR.Work" value=WORK checked>Work
1273<INPUT type=checkbox name="ADR.Home" value=HOME>Home
1274<INPUT type=checkbox name="ADR.Parcel" value=PARCEL checked>Parcel <INPUT type=checkbox name="ADR.Postal" value=POSTAL checked>Postal<br>
1275<hr><!-- Geographical Properties -->
1276TimeZone:<INPUT name="TZ" type=text size=3 maxlength=8
1277value="-06">
1278Location:<INPUT name="GEO" type=text size=16 maxlength=32 value=""><br>
1279<hr><!-- Telephony Addressing Properties -->
1280<!-- Telephone #1 -->
1281Telephone #1:<INPUT type=text name="A.TEL" size=20 maxlength=40 value="+1 (000) 000-0000"><br>
1282<INPUT type=checkbox name="A.TEL.Work" value=WORK checked>Work
1283<INPUT type=checkbox name="A.TEL.Home" value=HOME>Home
1284<INPUT type=checkbox name="A.TEL.Voice" value=VOICE checked>Voice
1285<INPUT type=checkbox name="A.TEL.Msg" value=MSG checked>Msg <INPUT type=checkbox name="A.TEL.Fax" value=FAX>Fax <INPUT type=checkbox name="A.TEL.Prefer" value=PREFER checked>Preferred<br>
1286<hr><!-- Telephone #2 -->
1287Telephone #2:<INPUT type=text name="B.TEL" size=20 maxlength=40 value="+1 (000) 000-0000"><br>
1288<INPUT type=checkbox name="B.TEL.Work" value=WORK checked>Work <INPUT type=checkbox name="B.TEL.Home" value=HOME>Home
1289<INPUT type=checkbox name="B.TEL.Voice" value=VOICE>Voice <INPUT type=checkbox name="B.TEL.Msg" value=MSG>Msg 
1290<INPUT type=checkbox name="B.TEL.Fax" value=FAX checked>Fax
1291<INPUT type=checkbox name="B.TEL.Prefer" value=PREFER>Preferred<br>
1292<hr><!-- Telephone #3 -->
1293Telephone #3:<INPUT type=text name= "C.TEL" size=20 maxlength=40 value="+1 (000) 000-0000"><br>
1294<INPUT type=checkbox name="C.TEL.Work" value=WORK>Work
1295<INPUT type=checkbox name="C.TEL.Home" value=HOME checked>Home <INPUT type=checkbox name="C.TEL.Voice" value=VOICE checked>Voice <INPUT type=checkbox name="C.TEL.Msg" value=MSG checked>Msg
1296<INPUT type=checkbox name="C.TEL.Fax" value=FAX checked>Fax <INPUT type=checkbox name="D.Prefer" value=PREFER>Preferred<br>
1297<hr><!-- Email D -->
1298EmailAddress: <select name="D.EMAILTYPE">
1299<option selected>INTERNET:
1300<option>CompuServe:
1301<option>AOL:
1302<option>Prodigy:
1303<option>eWorld:
1304<option>AppleLink:
1305<option>AppleTalk:
1306<option>PowerShare:
1307<option>IBMMail:
1308<option>ATTMail:
1309<option>MCIMail:
1310<option>X.400:
1311<option>TLX:
1312</select><INPUT type=text name="D.EMAIL" size=32 maxlength=64 value="">
1313<INPUT type=checkbox name="D.EMAIL.Work" value=WORK checked>Work <INPUT type=checkbox name="D.EMAIL.Home" value=HOME checked>Home<br>
1314<hr><!-- End of vCard Input -->
1315Send my Versitcard to this <b>internet</b> email address: 
1316<INPUT type=text name="SENDTOADDR" size=32 maxlength=64 value=""><br> Press <INPUT TYPE=SUBMIT value="Send"> to send the form now. Or, press <INPUT TYPE=RESET value="Reset"> to reset values to the form defaults.
1317</form>
1318</body>
1319
1320
1321Section 4 : UI Support Recommendations
1322[DS5]		
1323When  integrating vCard support into an application, an implementor needs to consider a number of user interface (UI) implications. Most appliss Type
1324ADR.x
1325TYPE=CHECKBOX. Separate input elements are used to capture the possible delivery types. The elements are named ADR.x, where x is one of the enumerated strings defined by the vCard specification.
1326
1327Delivery Label
1328LABEL
1329
1330
1331Label Type
1332LABEL.x
1333TYPE=CHECKBOX. Separate input elements are used to capture the possible delivery types. The elements are named LABEL.x, where x is one of the enumerated strings defined by the vCard specification.
1334
1335
1336Telecommunications Addressing Properties
1337Description
1338Attribute Name
1339Comment
1340
1341Telephone Number
1342TEL
1343
1344
1345Telephone Type
1346TEL.x
1347TYPE=CHECKBOX. Separate input elements are used to capture the possible telephone types. The elements are named TEL.x, where x is one of the enumerated strings defined by the vCard specification.
1348
1349Electronic Mail Address
1350EMAIL
1351
1352
1353Electronic Mail Address Type
1354EMAIL.Type
1355Selection option from a list of alternatives.
1356
1357Mailer
1358MAILER
1359
1360
1361
1362Geographical Properties
1363Description
1364Attribute Name
1365Comment
1366
1367Time Zone
1368TZ
1369
1370
1371Geographic Position
1372GEO
1373
1374
1375
1376Organizational Properties
1377Description
1378Attribute Name
1379Comment
1380
1381Title
1382TITLE
1383
1384
1385Business Category
1386ROLE
1387
1388
1389Logo
1390LOGO
1391Only the URL based specification is supported by this mapping. Value is the URL for the graphic.
1392
1393Logo Format Type
1394LOGO.Type
1395Where the value is one of the enumerated strings defined by the vCard specification. 
1396
1397Agent
1398
1399Captured through a separate form element using the mapping defined in these tables.
1400
1401Organization
1402ORG
1403TYPE=TEXT. Separate input elements for the organizational name and unit. The name ORG.Name is used to capture the organizational name. The name ORG.UNIT is used to capture the organizational unit. If there are multiple organizational units, it is captured in a form with name attributes ORG.UNIT1, ORG.UNIT2, etc.
1404
1405
1406Explanatory Properties
1407Description
1408Attribute Name
1409Comment
1410
1411Comment
1412NOTE
1413TYPE=TEXT
1414
1415Last Revision
1416REV
1417A hidden field.
1418
1419Version
1420VERSION
1421A hidden field with the value set to the string �2.1�.
1422
1423Language
1424LANG
1425A hidden field with the value set to the string associated with the default language used in the form (e.g., US-eng).
1426
1427Sound
1428SOUND
1429TYPE=TEXT
1430
1431Sound Type
1432N/A
1433
1434
1435Uniform Resource Locator
1436URL
1437TYPE=TEXT
1438
1439Unique Identifier
1440UID
1441TYPE=TEXT
1442
1443Binary Encoding
1444BE.x
1445Where x is one of the enumerated encoding types defined by the vCard specification.
1446
1447
1448Security Properties
1449Description
1450Attribute Name
1451Comment
1452
1453Public Key
1454KEY
1455
1456
1457Key Type
1458KEY.Type.x
1459Where x is one of the enumerated encoding types defined by the vCard specification.
1460
1461MISCELLANEOUS PROPERTIES
1462
1463
1464
1465Extensions
1466X-x
1467Where x is a string defined by the extension author.
1468
1469
1470Where multiple properties (e.g., telephone numbers) appear, a label prefix should be used. For example, telephone #1 might have a name attribute of �A.TEL�, telephone #2 might have a name attribute of �B.TEL�, etc.
1471Example HTML Code
1472The following HTML code is an example of the use of the mapping of INPUT element attributes names to vCard property names. The code can be used to capture input data for creating a vCard on a Web homepage.
1473<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
1474<head>
1475<title>Create Your Own Versitcard</title>
1476</head>
1477<IMG src="versit.gif">
1478<h1>Create Your Own Versitcard</h1>
1479<P> Fill out this form and we'll
1480create a <b>Versitcard</b> for you and send it to the email address of your choice,
1481along with more information on the Versitcard format.</P>
1482<hr><!-- Identification And Organizational Properties -->
1483<FORM METHOD="POST" ACTION="/cgi-bin/vcard-maker">
1484Formatted Name:<INPUT name="FN" type=text size=32 maxlength=64
1485value=""><br>
1486Phoenetic Pronunciation:<INPUT name="SOUND" type=text size=32 maxlength=128 value=""><br>
1487Company Name:<INPUT name="ORG.Name" type=text  size=32 maxlength=64
1488value=""><br>
1489Company Unit:<INPUT name="ORG.Unit" type=text size=32
1490maxlength=64 value=""><br>
1491Title:<INPUT name="TITLE" type=text size=32 maxlength=64
1492value="">
1493<hr><!-- Name Property Component Values -->
1494Family Name:<INPUT nies.
1495All forms of vCard Grouping must be able to be parsed and processed.
1496Property Grouping must be able to be parsed and processed.
1497Additionally, in order for a vCard Writer to conform to this specification it must meet the following additional criteria:
1498Must be able to send at least the Version, Formatted Name, Name, Address,  Telephone, Email, and Mailer properties.
1499
1500
1501[DS1]This entry (merged from the �TRIAL USE (TU)� document) appears to be a duplicate of the already-existing entry that follows, except for the publicaton/edition date. I would assume that it�s OK to delete this item, but, �
1502[DS2]This entry/line in the section is assigned the style for the level 1 heading. This is done so that a section number can be given in the chapter title (style "chptr_title") and so that "heading 1" (more specifically, the format/heading numbering of the form "1. Overview") can be "skipped," and the appropriate form for the next-level of heading can be properly displayed (eg., "1.1   Overview"). It is, and must be, formatted as "hidden text" prior to pagination and/or printing.
1503[DS3]This entry/line in the section is assigned the style for the level 1 heading. This is done so that a section number can be given in the chapter title (style "chptr_title") and so that "heading 1" (more specifically, the format/heading numbering of the form "1. Overview") can be "skipped," and the appropriate form for the next-level of heading can be properly displayed (eg., "1.1   Overview"). It is, and must be, formatted as "hidden text" prior to pagination and/or printing.
1504[DS4]This entry/line in the section is assigned the style for the level 1 heading. This is done so that a section number can be given in the chapter title (style "chptr_title") and so that "heading 1" (more specifically, the format/heading numbering of the form "1. Overview") can be "skipped," and the appropriate form for the next-level of heading can be properly displayed (eg., "1.1   Overview"). It is, and must be, formatted as "hidden text" prior to pagination and/or printing.
1505[DS5]This entry/line in the section is assigned the style for the level 1 heading. This is done so that a section number can be given in the chapter title (style �chptr_title") and so that "heading 1" (more specifically, the format/heading numbering of the form "1. Overview") can be "skipped," and the appropriate form for the next-level of heading can be properly displayed (eg., "1.1   Overview"). It is, and must be, formatted as "hidden text" prior to pagination and/or printing.
1506[DS6]This entry/line in the section is assigned the style for the level 1 heading. This is done so that a section number can be given in the chapter title (style �chptr_title") and so that "heading 1" (more specifically, the format/heading numbering of the form "1. Overview") can be "skipped," and the appropriate form for the next-level of heading can be properly displayed (eg., "1.1   Overview"). It is, and must be, formatted as "hidden text" prior to pagination and/or printing.
1507
1508
1509
1510
1511
1512
1513
1514$paratext[Pr.Preface]		
1515
1516
1517
1518
1519
1520
1521
1522		
1523vi		vCard Specification, Version 2.1
1524
1525		v
1526
1527versit Update	vii
1528
1529
1530
1531
1532
1533
1534
153536		vCard Specification, Version 2.1
1536
1537		xi
1538
1539
1540
1541
1542		39