The END property is used in conjunction with the BEGIN property to delimit an entity containing a related set of properties within a text/vcard content-type. This construct can be used instead of or in addition to wrapping separate sets of information inside additional MIME headers. It is provided for applications that wish to define content that can contain multiple entities within the same text/vcard content-type or to define content that can be identifiable outside of a MIME environment. ABNF: END-param = 0" " ; no parameter allowed END-value = "VCARD" Example: END:VCARD RFC3986] and/or other information referencing the vCard to which the information pertains. When directory information is available from more than one source, the sending entity can pick what it considers to be the best source, or multiple SOURCE properties can be included. ABNF: SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param / mediatype-param / any-param SOURCE-value = URI Examples: SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
"location" for a named geographical place. A location vCard will usually contain a GEO property, but it is not required to. A location vCard without a GEO property can be considered an abstract location, or one whose definition is known empirically (perhaps "New England" or "The Seashore"). All properties in a location vCard apply to the location itself, and not with any entity that might exist at that location. For example, in a vCard for an office building, an ADR property might give the mailing address for the building, and a TEL property might specify the telephone number of the receptionist. An x-name. vCards MAY include private or experimental values for KIND. Remember that x-name values are not intended for general use and are unlikely to interoperate. An iana-token. Additional values may be registered with IANA (see Section 10.3.4). A new value's specification document MUST specify which properties make sense for that new kind of vCard and which do not. Implementations MUST support the specific string values defined above. If this property is absent, "individual" MUST be assumed as the default. If this property is present but the implementation does not understand its value (the value is an x-name or iana-token that the implementation does not support), the implementation SHOULD act in a neutral way, which usually means treating the vCard as though its kind were "individual". The presence of MEMBER properties MAY, however, be taken as an indication that the unknown kind is an extension of "group". Clients often need to visually distinguish contacts based on what they represent, and the KIND property provides a direct way for them to do so. For example, when displaying contacts in a list, an icon could be displayed next to each one, using distinctive icons for the different kinds; a client might use an outline of a single person to represent an "individual", an outline of multiple people to represent a "group", and so on. Alternatively, or in addition, a client might choose to segregate different kinds of vCards to different panes, tabs, or selections in the user interface. Some clients might also make functional distinctions among the kinds, ignoring "location" vCards for some purposes and considering only "location" vCards for others.
When designing those sorts of visual and functional distinctions, client implementations have to decide how to fit unsupported kinds into the scheme. What icon is used for them? The one for "individual"? A unique one, such as an icon of a question mark? Which tab do they go into? It is beyond the scope of this specification to answer these questions, but these are things implementers need to consider. ABNF: KIND-param = "VALUE=text" / any-param KIND-value = "individual" / "group" / "org" / "location" / iana-token / x-name Example: This represents someone named Jane Doe working in the marketing department of the North American division of ABC Inc. BEGIN:VCARD VERSION:4.0 KIND:individual FN:Jane Doe ORG:ABC\, Inc.;North American Division;Marketing END:VCARD This represents the department itself, commonly known as ABC Marketing. BEGIN:VCARD VERSION:4.0 KIND:org FN:ABC Marketing ORG:ABC\, Inc.;North American Division;Marketing END:VCARD W3C.REC-xml-20081126] element whose namespace MUST be explicitly specified using the xmlns attribute and MUST NOT be the vCard 4
namespace ("urn:ietf:params:xml:ns:vcard-4.0"). (This implies that it cannot duplicate a standard vCard property.) The element is to be interpreted as if it was contained in a <vcard> element, as defined in [RFC6351]. The fragment is subject to normal line folding and escaping, i.e., replace all backslashes with "\\", then replace all newlines with "\n", then fold long lines. Support for this property is OPTIONAL, but implementations of this specification MUST preserve instances of this property when propagating vCards. See [RFC6351] for more information on the intended use of this property. ABNF: XML-param = "VALUE=text" / altid-param XML-value = text CCITT.X520.1988]. The property MUST be present in the vCard object. ABNF: FN-param = "VALUE=text" / type-param / language-param / altid-param / pid-param / pref-param / any-param FN-value = text Example: FN:Mr. John Q. Public\, Esq.
CCITT.X520.1988]. The property SHOULD be present in the vCard object when the name of the object the vCard represents follows the X.520 model. The SORT-AS parameter MAY be applied to this property. ABNF: N-param = "VALUE=text" / sort-as-param / language-param / altid-param / any-param N-value = list-component 4(";" list-component) Examples: N:Public;John;Quinlan;Mr.;Esq. N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
Special note: The nickname is the descriptive name given instead of or in addition to the one belonging to the object the vCard represents. It can also be used to specify a familiar form of a proper name specified by the FN or N properties. ABNF: NICKNAME-param = "VALUE=text" / type-param / language-param / altid-param / pid-param / pref-param / any-param NICKNAME-value = text-list Examples: NICKNAME:Robbie NICKNAME:Jim,Jimmie NICKNAME;TYPE=work:Boss
Value type: The default is a single date-and-or-time value. It can also be reset to a single text value. Cardinality: *1 ABNF: BDAY-param = BDAY-param-date / BDAY-param-text BDAY-value = date-and-or-time / text ; Value and parameter MUST match. BDAY-param-date = "VALUE=date-and-or-time" BDAY-param-text = "VALUE=text" / language-param BDAY-param =/ altid-param / calscale-param / any-param ; calscale-param can only be present when BDAY-value is ; date-and-or-time and actually contains a date or date-time. Examples: BDAY:19960415 BDAY:--0415 BDAY;19531015T231000Z BDAY;VALUE=text:circa 1800
Cardinality: * Special notes: The structured type value consists of a sequence of address components. The component values MUST be specified in their corresponding position. The structured type value corresponds, in sequence, to the post office box; the extended address (e.g., apartment or suite number); the street address; the locality (e.g., city); the region (e.g., state or province); the postal code; the country name (full name in the language specified in Section 5.1). When a component value is missing, the associated component separator MUST still be specified. Experience with vCard 3 has shown that the first two components (post office box and extended address) are plagued with many interoperability issues. To ensure maximal interoperability, their values SHOULD be empty. The text components are separated by the SEMICOLON character (U+003B). Where it makes semantic sense, individual text components can include multiple text values (e.g., a "street" component with multiple lines) separated by the COMMA character (U+002C). The property can include the "PREF" parameter to indicate the preferred delivery address when more than one address is specified. The GEO and TZ parameters MAY be used with this property. The property can also include a "LABEL" parameter to present a delivery address label for the address. Its value is a plain-text string representing the formatted address. Newlines are encoded as \n, as they are for property values. ABNF: label-param = "LABEL=" param-value ADR-param = "VALUE=text" / label-param / language-param / geo-parameter / tz-parameter / altid-param / pid-param / pref-param / type-param / any-param
ADR-value = ADR-component-pobox ";" ADR-component-ext ";" ADR-component-street ";" ADR-component-locality ";" ADR-component-region ";" ADR-component-code ";" ADR-component-country ADR-component-pobox = list-component ADR-component-ext = list-component ADR-component-street = list-component ADR-component-locality = list-component ADR-component-region = list-component ADR-component-code = list-component ADR-component-country = list-component Example: In this example, the post office box and the extended address are absent. ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A. RFC3966], but other schemes MAY be used. Cardinality: * Special notes: This property is based on the X.520 Telephone Number attribute [CCITT.X520.1988]. The property can include the "PREF" parameter to indicate a preferred-use telephone number. The property can include the parameter "TYPE" to specify intended use for the telephone number. The predefined values for the TYPE parameter are:
+-----------+-------------------------------------------------------+ | Value | Description | +-----------+-------------------------------------------------------+ | text | Indicates that the telephone number supports text | | | messages (SMS). | | voice | Indicates a voice telephone number. | | fax | Indicates a facsimile telephone number. | | cell | Indicates a cellular or mobile telephone number. | | video | Indicates a video conferencing telephone number. | | pager | Indicates a paging device telephone number. | | textphone | Indicates a telecommunication device for people with | | | hearing or speech difficulties. | +-----------+-------------------------------------------------------+ The default type is "voice". These type parameter values can be specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a value list (e.g., TYPE="text,voice"). The default can be overridden to another set of values by specifying one or more alternate values. For example, the default TYPE of "voice" can be reset to a VOICE and FAX telephone number by the value list TYPE="voice,fax". If this property's value is a URI that can also be used for instant messaging, the IMPP (Section 6.4.3) property SHOULD be used in addition to this property. ABNF: TEL-param = TEL-text-param / TEL-uri-param TEL-value = TEL-text-value / TEL-uri-value ; Value and parameter MUST match. TEL-text-param = "VALUE=text" TEL-text-value = text TEL-uri-param = "VALUE=uri" / mediatype-param TEL-uri-value = URI TEL-param =/ type-param / pid-param / pref-param / altid-param / any-param type-param-tel = "text" / "voice" / "fax" / "cell" / "video" / "pager" / "textphone" / iana-token / x-name ; type-param-tel MUST NOT be used with a property other than TEL.
Example: TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555 TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67 RFC5322], Section 3.4.1. Readers should also be aware of the current work toward internationalized email addresses [RFC5335bis]. ABNF: EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param / altid-param / any-param EMAIL-value = text Example: EMAIL;TYPE=work:email@example.com EMAIL;PREF=1:firstname.lastname@example.org
If this property's value is a URI that can be used for voice and/or video, the TEL property (Section 6.4.1) SHOULD be used in addition to this property. This property is adapted from [RFC4770], which is made obsolete by this document. ABNF: IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param / mediatype-param / altid-param / any-param IMPP-value = URI Example: IMPP;PREF=1:xmpp:email@example.com
Value type: The default is a single text value. It can also be reset to a single URI or utc-offset value. Cardinality: * Special notes: It is expected that names from the public-domain Olson database [TZ-DB] will be used, but this is not a restriction. See also [IANA-TZ]. Efforts are currently being directed at creating a standard URI scheme for expressing time zone information. Usage of such a scheme would ensure a high level of interoperability between implementations that support it. Note that utc-offset values SHOULD NOT be used because the UTC offset varies with time -- not just because of the usual daylight saving time shifts that occur in may regions, but often entire regions will "re-base" their overall offset. The actual offset may be +/- 1 hour (or perhaps a little more) than the one given. ABNF: TZ-param = "VALUE=" ("text" / "uri" / "utc-offset") TZ-value = text / URI / utc-offset ; Value and parameter MUST match. TZ-param =/ altid-param / pid-param / pref-param / type-param / mediatype-param / any-param Examples: TZ:Raleigh/North America TZ;VALUE=utc-offset:-0500 ; Note: utc-offset format is NOT RECOMMENDED. RFC5870] is particularly well suited for this property, but other schemes MAY be used.
ABNF: GEO-param = "VALUE=uri" / pid-param / pref-param / type-param / mediatype-param / altid-param / any-param GEO-value = URI Example: GEO:geo:37.386013,-122.082932 CCITT.X520.1988]. ABNF: TITLE-param = "VALUE=text" / language-param / pid-param / pref-param / altid-param / type-param / any-param TITLE-value = text Example: TITLE:Research Scientist
Special notes: This property is based on the X.520 Business Category explanatory attribute [CCITT.X520.1988]. This property is included as an organizational type to avoid confusion with the semantics of the TITLE property and incorrect usage of that property when the semantics of this property is intended. ABNF: ROLE-param = "VALUE=text" / language-param / pid-param / pref-param / type-param / altid-param / any-param ROLE-value = text Example: ROLE:Project Leader
Cardinality: * Special notes: The property is based on the X.520 Organization Name and Organization Unit attributes [CCITT.X520.1988]. The property value is a structured type consisting of the organization name, followed by zero or more levels of organizational unit names. The SORT-AS parameter MAY be applied to this property. ABNF: ORG-param = "VALUE=text" / sort-as-param / language-param / pid-param / pref-param / altid-param / type-param / any-param ORG-value = component *(";" component) Example: A property value consisting of an organizational name, organizational unit #1 name, and organizational unit #2 name. ORG:ABC\, Inc.;North American Division;Marketing RFC6068] for efficiency. Cardinality: * Special notes: This property MUST NOT be present unless the value of the KIND property is "group". ABNF: MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param / mediatype-param / any-param MEMBER-value = URI
Examples: BEGIN:VCARD VERSION:4.0 KIND:group FN:The Doe family MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519 END:VCARD BEGIN:VCARD VERSION:4.0 FN:John Doe UID:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af END:VCARD BEGIN:VCARD VERSION:4.0 FN:Jane Doe UID:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519 END:VCARD BEGIN:VCARD VERSION:4.0 KIND:group FN:Funky distribution list MEMBER:mailto:firstname.lastname@example.org MEMBER:xmpp:email@example.com MEMBER:sip:firstname.lastname@example.org MEMBER:tel:+1-418-555-5555 END:VCARD Section 10.2. The registry is pre-populated with the values defined in [xfn]. This document also specifies two additional values: agent: an entity who may sometimes act on behalf of the entity associated with the vCard.
emergency: indicates an emergency contact ABNF: RELATED-param = RELATED-param-uri / RELATED-param-text RELATED-value = URI / text ; Parameter and value MUST match. RELATED-param-uri = "VALUE=uri" / mediatype-param RELATED-param-text = "VALUE=text" / language-param RELATED-param =/ pid-param / pref-param / altid-param / type-param / any-param type-param-related = related-type-value *("," related-type-value) ; type-param-related MUST NOT be used with a property other than ; RELATED. related-type-value = "contact" / "acquaintance" / "friend" / "met" / "co-worker" / "colleague" / "co-resident" / "neighbor" / "child" / "parent" / "sibling" / "spouse" / "kin" / "muse" / "crush" / "date" / "sweetheart" / "me" / "agent" / "emergency" Examples: RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane Doe for any inquiries.
ABNF: CATEGORIES-param = "VALUE=text" / pid-param / pref-param / type-param / altid-param / any-param CATEGORIES-value = text-list Example: CATEGORIES:TRAVEL AGENT CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CCITT.X520.1988]. ABNF: NOTE-param = "VALUE=text" / language-param / pid-param / pref-param / type-param / altid-param / any-param NOTE-value = text Example: NOTE:This fax number is operational 0800 to 1715 EST\, Mon-Fri. ISO9070] or for Universal Resource Names in [RFC3406] to ensure that the text value is unique.
ABNF: PRODID-param = "VALUE=text" / any-param PRODID-value = text Example: PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
Example: SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 <...the remainder of base64-encoded data...> RFC4122] is particularly well suited to this task, but other URI schemes MAY be used. Free-form text MAY also be used. ABNF: UID-param = UID-uri-param / UID-text-param UID-value = UID-uri-value / UID-text-value ; Value and parameter MUST match. UID-uri-param = "VALUE=uri" UID-uri-value = URI UID-text-param = "VALUE=text" UID-text-value = text UID-param =/ any-param Example: UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
RFC4122] is particularly well suited to this task, but other URI schemes MAY be used. Cardinality: * Special notes: PID source identifiers (the source identifier is the second field in a PID parameter instance) are small integers that only have significance within the scope of a single vCard instance. Each distinct source identifier present in a vCard MUST have an associated CLIENTPIDMAP. See Section 7 for more details on the usage of CLIENTPIDMAP. PID source identifiers MUST be strictly positive. Zero is not allowed. As a special exception, the PID parameter MUST NOT be applied to this property. ABNF: CLIENTPIDMAP-param = any-param CLIENTPIDMAP-value = 1*DIGIT ";" URI Example: TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555 EMAIL;PID=4.1,5.2:email@example.com CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
ABNF: URL-param = "VALUE=uri" / pid-param / pref-param / type-param / mediatype-param / altid-param / any-param URL-value = URI Example: URL:http://example.org/restaurant.french/~chezchic.html
ABNF: KEY-param = KEY-uri-param / KEY-text-param KEY-value = KEY-uri-value / KEY-text-value ; Value and parameter MUST match. KEY-uri-param = "VALUE=uri" / mediatype-param KEY-uri-value = URI KEY-text-param = "VALUE=text" KEY-text-value = text KEY-param =/ altid-param / pid-param / pref-param / type-param / any-param Examples: KEY:http://www.example.com/keys/jdoe.cer KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l <... remainder of base64-encoded data ...> RFC2739]. RFC1738] or HTTP [RFC2616] type of URI points to an iCalendar [RFC5545] object associated with a snapshot of the next few weeks or months of busy time data. If the iCalendar object is represented as a file or document, its file extension should be ".ifb".
ABNF: FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param / mediatype-param / altid-param / any-param FBURL-value = URI Examples: FBURL;PREF=1:http://www.example.com/busy/janedoe FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb RFC5545] to which a scheduling request [RFC5546] should be sent for the object represented by the vCard. Value type: A single URI value. Cardinality: * Special notes: Where multiple CALADRURI properties are specified, the default CALADRURI property is indicated with the PREF parameter. ABNF: CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param / mediatype-param / altid-param / any-param CALADRURI-value = URI Example: CALADRURI;PREF=1:mailto:firstname.lastname@example.org CALADRURI:http://example.com/calendar/jdoe RFC5545]
object associated with a snapshot of the user's calendar store. If the iCalendar object is represented as a file or document, its file extension should be ".ics". ABNF: CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param / mediatype-param / altid-param / any-param CALURI-value = URI Examples: CALURI;PREF=1:http://cal.example.com/calA CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics