From 006600fdf4add2090d166e90c0016b683c127ac9 Mon Sep 17 00:00:00 2001
From: Chris Toshok Fill out this form and we'll
+create a Versitcard for you and send it to the email address of your choice,
+along with more information on the Versitcard format.Create Your Own Versitcard
+
+
+
+ + +Section 4 : UI Support Recommendations +[DS5] +When integrating vCard support into an application, an implementor needs to consider a number of user interface (UI) implications. Most appliss Type +ADR.x +TYPE=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. + +Delivery Label +LABEL + + +Label Type +LABEL.x +TYPE=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. + + +Telecommunications Addressing Properties +Description +Attribute Name +Comment + +Telephone Number +TEL + + +Telephone Type +TEL.x +TYPE=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. + +Electronic Mail Address +EMAIL + + +Electronic Mail Address Type +EMAIL.Type +Selection option from a list of alternatives. + +Mailer +MAILER + + + +Geographical Properties +Description +Attribute Name +Comment + +Time Zone +TZ + + +Geographic Position +GEO + + + +Organizational Properties +Description +Attribute Name +Comment + +Title +TITLE + + +Business Category +ROLE + + +Logo +LOGO +Only the URL based specification is supported by this mapping. Value is the URL for the graphic. + +Logo Format Type +LOGO.Type +Where the value is one of the enumerated strings defined by the vCard specification. + +Agent + +Captured through a separate form element using the mapping defined in these tables. + +Organization +ORG +TYPE=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. + + +Explanatory Properties +Description +Attribute Name +Comment + +Comment +NOTE +TYPE=TEXT + +Last Revision +REV +A hidden field. + +Version +VERSION +A hidden field with the value set to the string ì2.1î. + +Language +LANG +A hidden field with the value set to the string associated with the default language used in the form (e.g., US-eng). + +Sound +SOUND +TYPE=TEXT + +Sound Type +N/A + + +Uniform Resource Locator +URL +TYPE=TEXT + +Unique Identifier +UID +TYPE=TEXT + +Binary Encoding +BE.x +Where x is one of the enumerated encoding types defined by the vCard specification. + + +Security Properties +Description +Attribute Name +Comment + +Public Key +KEY + + +Key Type +KEY.Type.x +Where x is one of the enumerated encoding types defined by the vCard specification. + +MISCELLANEOUS PROPERTIES + + + +Extensions +X-x +Where x is a string defined by the extension author. + + +Where 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. +Example HTML Code +The 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. + +
+
+ + +
+
Fill out this form and we'll +create a Versitcard for you and send it to the email address of your choice, +along with more information on the Versitcard format.
+
+