metanorma-cli 1.3.7.3 → 1.3.8

data/exe/rfc6350.xml

@@ -0,0 +1,3319 @@
+<?xml version="1.0" encoding="US-ASCII"?>
+<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
+<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
+<?rfc comments="yes"?>
+<?rfc rfcedstyle="yes"?>
+<?rfc strict="yes"?>
+<?rfc compact="yes"?>
+<?rfc subcompact="no"?>
+<?rfc toc="yes"?>
+<?rfc tocdepth="4"?>
+<?rfc symrefs="yes"?>
+<?rfc sortrefs="yes"?>
+<rfc ipr="pre5378Trust200902" obsoletes="2425, 2426, 4770" updates="2739" category="std" submissionType="IETF" number="6350">
+<front>
+  <title abbrev="vCard">vCard Format Specification</title>
+  <author fullname="Simon Perreault" surname="Perreault" initials="S.">
+    <organization>Viagenie</organization>
+    <address>
+      <postal>
+        <street>2875 Laurier, suite D2-630</street>
+        <region>Quebec, QC</region>
+        <code>G1V 2M2</code>
+        <country>Canada</country>
+      </postal>
+      <phone>+1 418 656 9254</phone>
+      <email>simon.perreault@viagenie.ca</email>
+      <uri>http://www.viagenie.ca</uri>
+    </address>
+  </author>
+  <date month="August" year="2011"/>
+
+<abstract>
+  <t>This document defines the vCard data format for representing and
+exchanging a variety of information about individuals and other
+entities (e.g., formatted and structured name and delivery addresses,
+email address, multiple telephone numbers, photograph, logo, audio
+clips, etc.).  This document obsoletes RFCs 2425, 2426, and 4770, and
+updates RFC 2739.</t>
+</abstract>
+</front><middle>
+<section anchor="section1" title="Introduction"><t>Electronic address books have become ubiquitous.  Their increased
+presence on portable, connected devices as well as the diversity of
+platforms that exchange contact data call for a standard.  This memo
+defines the vCard format, which allows the capture and exchange of
+information normally stored within an address book or directory
+application.</t>
+<t>A high-level overview of the differences from RFCs 2425 and 2426 can
+be found in <xref target="appendixA"/>.</t></section>
+<section anchor="section2" title="Conventions">
+  <t>The key words "<spanx style="strong">MUST</spanx>", "<spanx style="strong">MUST NOT</spanx>", "<spanx style="strong">REQUIRED</spanx>", "<spanx style="strong">SHALL</spanx>", "<spanx style="strong">SHALL NOT</spanx>",
+"<spanx style="strong">SHOULD</spanx>", "<spanx style="strong">SHOULD NOT</spanx>", "<spanx style="strong">RECOMMENDED</spanx>", "<spanx style="strong">NOT RECOMMENDED</spanx>", "<spanx style="strong">MAY</spanx>", and
+"<spanx style="strong">OPTIONAL</spanx>" in this document are to be interpreted as described in
+cite:norm[RFC2119].</t>
+</section>
+<section anchor="section3" title="vCard Format Specification"><t>The text/vcard MIME content type (hereafter known as "vCard"; see
+<xref target="section10_1"/>) contains contact information, typically pertaining to a
+single contact or group of contacts.  The content consists of one or
+more lines in the format given below.</t>
+<section anchor="section3_1" title="Charset">
+  <t>The charset (see cite:info[RFC3536] for internationalization terminology) for
+vCard is UTF-8 as defined in cite:norm[RFC3629].  There is no way to override
+this.  It is invalid to specify a value other than "UTF-8" in the
+"charset" MIME parameter (see <xref target="section10_1"/>).</t>
+</section>
+<section anchor="section3_2" title="Line Delimiting and Folding"><t>Individual lines within vCard are delimited by the cite:norm[RFC5322] line
+break, which is a CRLF sequence (U+000D followed by U+000A).  Long
+logical lines of text can be split into a multiple-physical-line
+representation using the following folding technique.  Content lines
+<spanx style="strong">SHOULD</spanx> be folded to a maximum width of 75 octets, excluding the line
+break.  Multi-octet characters <spanx style="strong">MUST</spanx> remain contiguous.  The rationale
+for this folding process can be found in cite:norm[RFC5322, suffix=", Section 2.1.1"].</t>
+<t>A logical line <spanx style="strong">MAY</spanx> be continued on the next physical line anywhere
+between two characters by inserting a CRLF immediately followed by a
+single white space character (space (U+0020) or horizontal tab
+(U+0009)).  The folded line <spanx style="strong">MUST</spanx> contain at least one character.  Any
+sequence of CRLF followed immediately by a single white space
+character is ignored (removed) when processing the content type.  For
+example, the line:</t>
+<figure>
+  <artwork><![CDATA[
+  NOTE:This is a long description that exists on a long line.
+]]></artwork>
+</figure>
+<t>can be represented as:</t>
+<figure>
+  <artwork><![CDATA[
+  NOTE:This is a long description
+    that exists on a long line.
+]]></artwork>
+</figure>
+<t>It could also be represented as:</t>
+<figure>
+  <artwork><![CDATA[
+  NOTE:This is a long descrip
+   tion that exists o
+   n a long line.
+]]></artwork>
+</figure>
+<t>The process of moving from this folded multiple-line representation
+of a property definition to its single-line representation is called
+unfolding.  Unfolding is accomplished by regarding CRLF immediately
+followed by a white space character (namely, HTAB (U+0009) or SPACE
+(U+0020)) as equivalent to no characters at all (i.e., the CRLF and
+single white space character are removed).</t>
+<t>Note: It is possible for very simple implementations to generate
+improperly folded lines in the middle of a UTF-8 multi-octet
+sequence.  For this reason, implementations <spanx style="strong">SHOULD</spanx> unfold lines in
+such a way as to properly restore the original sequence.</t>
+<t>Note: Unfolding is done differently than in cite:norm[RFC5322].  Unfolding
+in cite:norm[RFC5322] only removes the CRLF, not the space following it.</t>
+<t>Folding is done after any content encoding of a type value.
+Unfolding is done before any decoding of a type value in a content
+line.</t></section>
+<section anchor="section3_3" title="ABNF Format Definition"><t>The following ABNF uses the notation of cite:norm[RFC5234], which also defines
+CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+vcard-entity = 1*vcard
+
+vcard = "BEGIN:VCARD" CRLF
+        "VERSION:4.0" CRLF
+        1*contentline
+        "END:VCARD" CRLF
+  ; A vCard object MUST include the VERSION and FN properties.
+  ; VERSION MUST come immediately after BEGIN:VCARD.
+
+contentline = [group "."] name *(";" param) ":" value CRLF
+  ; When parsing a content line, folded lines must first
+  ; be unfolded according to the unfolding procedure
+  ; described in Section 3.2.
+  ; When generating a content line, lines longer than 75
+  ; characters SHOULD be folded according to the folding
+  ; procedure described in Section 3.2.
+
+group = 1*(ALPHA / DIGIT / "-")
+name  = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
+      / "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
+      / "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
+      / "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
+      / "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
+      / "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
+      / iana-token / x-name
+  ; Parsing of the param and value is based on the "name" as
+  ; defined in ABNF sections below.
+  ; Group and name are case-insensitive.
+
+iana-token = 1*(ALPHA / DIGIT / "-")
+  ; identifier registered with IANA
+
+x-name = "x-" 1*(ALPHA / DIGIT / "-")
+  ; Names that begin with "x-" or "X-" are
+  ; reserved for experimental use, not intended for released
+  ; products, or for use in bilateral agreements.
+
+param = language-param / value-param / pref-param / pid-param
+      / type-param / geo-parameter / tz-parameter / sort-as-param
+      / calscale-param / any-param
+  ; Allowed parameters depend on property name.
+
+param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
+
+any-param  = (iana-token / x-name) "=" param-value *("," param-value)
+
+NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
+  ; UTF8-{2,3,4} are defined in [RFC3629]
+
+QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
+  ; Any character except CTLs, DQUOTE
+
+SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
+  ; Any character except CTLs, DQUOTE, ";", ":"
+
+VALUE-CHAR = WSP / VCHAR / NON-ASCII
+  ; Any textual character
+]]></artwork>
+</figure>
+<t>A line that begins with a white space character is a continuation of
+the previous line, as described in <xref target="section3_2"/>.  The white space
+character and immediately preceeding CRLF should be discarded when
+reconstructing the original line.  Note that this line-folding
+convention differs from that found in cite:norm[RFC5322], in that the sequence
+&lt;CRLF&gt;&lt;WSP&gt; found anywhere in the content indicates a continued line
+and should be removed.</t>
+<t>Property names and parameter names are case-insensitive (e.g., the
+property name "fn" is the same as "FN" and "Fn").  Parameter values
+<spanx style="strong">MAY</spanx> be case-sensitive or case-insensitive, depending on their
+definition.  Parameter values that are not explicitly defined as
+being case-sensitive are case-insensitive.  Based on experience with
+vCard 3 interoperability, it is <spanx style="strong">RECOMMENDED</spanx> that property and
+parameter names be upper-case on output.</t>
+<t>The group construct is used to group related properties together.
+The group name is a syntactic convention used to indicate that all
+property names prefaced with the same group name <spanx style="strong">SHOULD</spanx> be grouped
+together when displayed by an application.  It has no other
+significance.  Implementations that do not understand or support
+grouping <spanx style="strong">MAY</spanx> simply strip off any text before a "." to the left of
+the type name and present the types and values as normal.</t>
+<t>Property cardinalities are indicated using the following notation,
+which is based on ABNF (see cite:norm[RFC5234, suffix=", Section 3.6"]):</t>
+<texttable suppress-title="false" style="full">
+  <ttcol align="left">Cardinality</ttcol>
+  <ttcol align="left">Meaning</ttcol>
+  <c>1</c>
+  <c>Exactly one instance per vCard <spanx style="strong">MUST</spanx> be present.</c>
+  <c>*1</c>
+  <c>Exactly one instance per vCard <spanx style="strong">MAY</spanx> be present.</c>
+  <c>1*</c>
+  <c>One or more instances per vCard <spanx style="strong">MUST</spanx> be present.</c>
+  <c>*</c>
+  <c>One or more instances per vCard <spanx style="strong">MAY</spanx> be present.</c>
+</texttable>
+<t>Properties defined in a vCard instance may have multiple values
+depending on the property cardinality.  The general rule for encoding
+multi-valued properties is to simply create a new content line for
+each value (including the property name).  However, it should be
+noted that some value types support encoding multiple values in a
+single content line by separating the values with a comma ",".  This
+approach has been taken for several of the content types defined
+below (date, time, integer, float).</t></section>
+<section anchor="section3_4" title="Property Value Escaping"><t>Some properties may contain one or more values delimited by a COMMA
+character (U+002C).  Therefore, a COMMA character in a value <spanx style="strong">MUST</spanx> be
+escaped with a BACKSLASH character (U+005C), even for properties that
+don&#8217;t allow multiple instances (for consistency).</t>
+<t>Some properties (e.g., N and ADR) comprise multiple fields delimited
+by a SEMICOLON character (U+003B).  Therefore, a SEMICOLON in a field
+of such a "compound" property <spanx style="strong">MUST</spanx> be escaped with a BACKSLASH
+character.  SEMICOLON characters in non-compound properties <spanx style="strong">MAY</spanx> be
+escaped.  On input, an escaped SEMICOLON character is never a field
+separator.  An unescaped SEMICOLON character may be a field
+separator, depending on the property in which it appears.</t>
+<t>Furthermore, some fields of compound properties may contain a list of
+values delimited by a COMMA character.  Therefore, a COMMA character
+in one of a field&#8217;s values <spanx style="strong">MUST</spanx> be escaped with a BACKSLASH
+character, even for fields that don&#8217;t allow multiple values (for
+consistency).  Compound properties allowing multiple instances <spanx style="strong">MUST NOT</spanx>
+be encoded in a single content line.</t>
+<t>Finally, BACKSLASH characters in values <spanx style="strong">MUST</spanx> be escaped with a
+BACKSLASH character.  NEWLINE (U+000A) characters in values <spanx style="strong">MUST</spanx> be
+encoded by two characters: a BACKSLASH followed by either an 'n'
+(U+006E) or an 'N' (U+004E).</t>
+<t>In all other cases, escaping <spanx style="strong">MUST NOT</spanx> be used.</t></section></section>
+<section anchor="section4" title="Property Value Data Types"><t>Standard value types are defined below.</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+  value = text
+        / text-list
+        / date-list
+        / time-list
+        / date-time-list
+        / date-and-or-time-list
+        / timestamp-list
+        / boolean
+        / integer-list
+        / float-list
+        / URI               ; from Section 3 of [RFC3986]
+        / utc-offset
+        / Language-Tag
+        / iana-valuespec
+    ; Actual value type depends on property name and VALUE parameter.
+
+  text = *TEXT-CHAR
+
+  TEXT-CHAR = "\\" / "\," / "\n" / WSP / NON-ASCII
+            / %x21-2B / %x2D-5B / %x5D-7E
+     ; Backslashes, commas, and newlines must be encoded.
+
+  component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
+            / %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
+  list-component = component *("," component)
+
+  text-list             = text             *("," text)
+  date-list             = date             *("," date)
+  time-list             = time             *("," time)
+  date-time-list        = date-time        *("," date-time)
+  date-and-or-time-list = date-and-or-time *("," date-and-or-time)
+  timestamp-list        = timestamp        *("," timestamp)
+  integer-list          = integer          *("," integer)
+  float-list            = float            *("," float)
+
+  boolean = "TRUE" / "FALSE"
+  integer = [sign] 1*DIGIT
+  float   = [sign] 1*DIGIT ["." 1*DIGIT]
+
+  sign = "+" / "-"
+
+  year   = 4DIGIT  ; 0000-9999
+  month  = 2DIGIT  ; 01-12
+  day    = 2DIGIT  ; 01-28/29/30/31 depending on month and leap year
+  hour   = 2DIGIT  ; 00-23
+  minute = 2DIGIT  ; 00-59
+  second = 2DIGIT  ; 00-58/59/60 depending on leap second
+  zone   = utc-designator / utc-offset
+  utc-designator = %x5A  ; uppercase "Z"
+
+  date          = year    [month  day]
+                / year "-" month
+                / "--"     month [day]
+                / "--"      "-"   day
+  date-noreduc  = year     month  day
+                / "--"     month  day
+                / "--"      "-"   day
+  date-complete = year     month  day
+
+  time          = hour [minute [second]] [zone]
+                /  "-"  minute [second]  [zone]
+                /  "-"   "-"    second   [zone]
+  time-notrunc  = hour [minute [second]] [zone]
+  time-complete = hour  minute  second   [zone]
+
+
+  time-designator = %x54  ; uppercase "T"
+  date-time = date-noreduc  time-designator time-notrunc
+  timestamp = date-complete time-designator time-complete
+
+  date-and-or-time = date-time / date / time-designator time
+
+  utc-offset = sign hour [minute]
+
+  Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1>
+
+  iana-valuespec = <value-spec, see Section 12>
+                 ; a publicly defined valuetype format, registered
+                 ; with IANA, as defined in Section 12 of this
+                 ; document.
+]]></artwork>
+</figure>
+<section anchor="section4_1" title="TEXT"><t>"text": The "text" value type should be used to identify values that
+contain human-readable text.  As for the language, it is controlled
+by the LANGUAGE property parameter defined in <xref target="section5_1"/>.</t>
+<t>Examples for "text":</t>
+<figure>
+  <artwork><![CDATA[
+    this is a text value
+    this is one value,this is another
+    this is a single value\, with a comma encoded
+]]></artwork>
+</figure>
+<t>A formatted text line break in a text value type <spanx style="strong">MUST</spanx> be represented
+as the character sequence backslash (U+005C) followed by a Latin
+small letter n (U+006E) or a Latin capital letter N (U+004E), that
+is, "\n" or "\N".</t>
+<t>For example, a multiple line NOTE value of:</t>
+<figure>
+  <artwork><![CDATA[
+    Mythical Manager
+    Hyjinx Software Division
+    BabsCo, Inc.
+]]></artwork>
+</figure>
+<t>could be represented as:</t>
+<figure>
+  <artwork><![CDATA[
+    NOTE:Mythical Manager\nHyjinx Software Division\n
+     BabsCo\, Inc.\n
+]]></artwork>
+</figure>
+<t>demonstrating the \n literal formatted line break technique, the
+CRLF-followed-by-space line folding technique, and the backslash
+escape technique.</t></section>
+<section anchor="section4_2" title="URI"><t>"uri": The "uri" value type should be used to identify values that
+are referenced by a Uniform Resource Identifier (URI) instead of
+encoded in-line.  These value references might be used if the value
+is too large, or otherwise undesirable to include directly.  The
+format for the URI is as defined in cite:norm[RFC3986, prefix="Section 3 of "].  Note
+that the value of a property of type "uri" is what the URI points to,
+not the URI itself.</t>
+<t>Examples for "uri":</t>
+<figure>
+  <artwork><![CDATA[
+    http://www.example.com/my/picture.jpg
+    ldap://ldap.example.com/cn=babs%20jensen
+]]></artwork>
+</figure></section>
+<section anchor="section4_3" title="DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP"><t>"date", "time", "date-time", "date-and-or-time", and "timestamp":
+Each of these value types is based on the definitions in
+cite:norm[ISO.8601.2004].  Multiple such values can be specified using the
+comma-separated notation.</t>
+<t>Only the basic format is supported.</t>
+<section anchor="section4_3_1" title="DATE"><t>A calendar date as specified in cite:norm[ISO.8601.2004, suffix=", Section 4.1.2"].</t>
+<t>Reduced accuracy, as specified in cite:norm[ISO.8601.2004, suffix=", Sections 4.1.2.3"] a)
+and b), but not c), is permitted.</t>
+<t>Expanded representation, as specified in cite:norm[ISO.8601.2004, suffix=", Section 4.1.4"], is forbidden.</t>
+<t>Truncated representation, as specified in cite:norm[ISO.8601.2000, suffix=", Sections 5.2.1.3"] d), e), and f), is permitted.</t>
+<t>Examples for "date":</t>
+<figure>
+  <artwork><![CDATA[
+          19850412
+          1985-04
+          1985
+          --0412
+          ---12
+
+
+
+]]></artwork>
+</figure>
+<t>Note the use of YYYY-MM in the second example above.  YYYYMM is
+disallowed to prevent confusion with YYMMDD.  Note also that
+YYYY-MM-DD is disallowed since we are using the basic format instead
+of the extended format.</t></section>
+<section anchor="section4_3_2" title="TIME"><t>A time of day as specified in cite:norm[ISO.8601.2004, suffix=", Section 4.2"].</t>
+<t>Reduced accuracy, as specified in cite:norm[ISO.8601.2004, suffix=", Section 4.2.2.3"],
+is permitted.</t>
+<t>Representation with decimal fraction, as specified in
+cite:norm[ISO.8601.2004, suffix=", Section 4.2.2.4"], is forbidden.</t>
+<t>The midnight hour is always represented by 00, never 24 (see
+cite:norm[ISO.8601.2004, suffix=", Section 4.2.3"]).</t>
+<t>Truncated representation, as specified in cite:norm[ISO.8601.2000, suffix=", Sections 5.3.1.4"] a), b), and c), is permitted.</t>
+<t>Examples for "time":</t>
+<figure>
+  <artwork><![CDATA[
+          102200
+          1022
+          10
+          -2200
+          --00
+          102200Z
+          102200-0800
+]]></artwork>
+</figure></section>
+<section anchor="section4_3_3" title="DATE-TIME"><t>A date and time of day combination as specified in cite:norm[ISO.8601.2004, suffix=", Section 4.3"].</t>
+<t>Truncation of the date part, as specified in cite:norm[ISO.8601.2000, suffix=", Section 5.4.2"] c), is permitted.</t>
+<t>Examples for "date-time":</t>
+<figure>
+  <artwork><![CDATA[
+          19961022T140000
+          --1022T1400
+          ---22T14
+]]></artwork>
+</figure></section>
+<section anchor="section4_3_4" title="DATE-AND-OR-TIME"><t>Either a DATE-TIME, a DATE, or a TIME value.  To allow unambiguous
+interpretation, a stand-alone TIME value is always preceded by a "T".</t>
+<t>Examples for "date-and-or-time":</t>
+<figure>
+  <artwork><![CDATA[
+          19961022T140000
+          --1022T1400
+          ---22T14
+          19850412
+          1985-04
+          1985
+          --0412
+          ---12
+          T102200
+          T1022
+          T10
+          T-2200
+          T--00
+          T102200Z
+          T102200-0800
+]]></artwork>
+</figure></section>
+<section anchor="section4_3_5" title="TIMESTAMP"><t>A complete date and time of day combination as specified in
+cite:norm[ISO.8601.2004, suffix=", Section 4.3.2"].</t>
+<t>Examples for "timestamp":</t>
+<figure>
+  <artwork><![CDATA[
+          19961022T140000
+          19961022T140000Z
+          19961022T140000-05
+          19961022T140000-0500
+]]></artwork>
+</figure></section></section>
+<section anchor="section4_4" title="BOOLEAN"><t>"boolean": The "boolean" value type is used to express boolean
+values.  These values are case-insensitive.</t>
+<t>
+  <list style="hanging">
+    <t hangText="Examples: "/>
+  </list>
+</t>
+<figure>
+  <artwork><![CDATA[
+    TRUE
+    false
+    True
+]]></artwork>
+</figure></section>
+<section anchor="section4_5" title="INTEGER"><t>"integer": The "integer" value type is used to express signed
+integers in decimal format.  If sign is not specified, the value is
+assumed positive "+".  Multiple "integer" values can be specified
+using the comma-separated notation.  The maximum value is
+9223372036854775807, and the minimum value is -9223372036854775808.
+These limits correspond to a signed 64-bit integer using two&#8217;s-
+complement arithmetic.</t>
+<t>
+  <list style="hanging">
+    <t hangText="Examples: "/>
+  </list>
+</t>
+<figure>
+  <artwork><![CDATA[
+    1234567890
+    -1234556790
+    +1234556790,432109876
+]]></artwork>
+</figure></section>
+<section anchor="section4_6" title="FLOAT"><t>"float": The "float" value type is used to express real numbers.  If
+sign is not specified, the value is assumed positive "+".  Multiple
+"float" values can be specified using the comma-separated notation.
+Implementations <spanx style="strong">MUST</spanx> support a precision equal or better than that of
+the IEEE "binary64" format cite:norm[IEEE.754.2008].</t>
+<t>Note: Scientific notation is disallowed.  Implementers wishing to
+use their favorite language&#8217;s %f formatting should be careful.</t>
+<t>
+  <list style="hanging">
+    <t hangText="Examples: "/>
+  </list>
+</t>
+<figure>
+  <artwork><![CDATA[
+    20.30
+    1000000.0000001
+    1.333,3.14
+]]></artwork>
+</figure></section>
+<section anchor="section4_7" title="UTC-OFFSET"><t>"utc-offset": The "utc-offset" value type specifies that the property
+value is a signed offset from UTC.  This value type can be specified
+in the TZ property.</t>
+<t>The value type is an offset from Coordinated Universal Time (UTC).
+It is specified as a positive or negative difference in units of
+hours and minutes (e.g., +hhmm).  The time is specified as a 24-hour
+clock.  Hour values are from 00 to 23, and minute values are from 00
+to 59.  Hour and minutes are 2 digits with high-order zeroes required
+to maintain digit count.  The basic format for ISO 8601 UTC offsets
+<spanx style="strong">MUST</spanx> be used.</t></section>
+<section anchor="section4_8" title="LANGUAGE-TAG">
+  <t>"language-tag": A single language tag, as defined in cite:norm[RFC5646].</t>
+</section></section>
+<section anchor="section5" title="Property Parameters"><t>A property can have attributes associated with it.  These "property
+parameters" contain meta-information about the property or the
+property value.  In some cases, the property parameter can be multi-
+valued in which case the property parameter value elements are
+separated by a COMMA (U+002C).</t>
+<t>Property parameter value elements that contain the COLON (U+003A),
+SEMICOLON (U+003B), or COMMA (U+002C) character separators <spanx style="strong">MUST</spanx> be
+specified as quoted-string text values.  Property parameter values
+<spanx style="strong">MUST NOT</spanx> contain the DQUOTE (U+0022) character.  The DQUOTE character
+is used as a delimiter for parameter values that contain restricted
+characters or URI text.</t>
+<t>Applications <spanx style="strong">MUST</spanx> ignore x-param and iana-param values they don&#8217;t
+recognize.</t>
+<section anchor="section5_1" title="LANGUAGE"><t>The LANGUAGE property parameter is used to identify data in multiple
+languages.  There is no concept of "default" language, except as
+specified by any "Content-Language" MIME header parameter that is
+present cite:info[RFC3282].  The value of the LANGUAGE property parameter is a
+language tag as defined in cite:norm[RFC5646, prefix="Section 2 of "].</t>
+<t>
+  <list style="hanging">
+    <t hangText="Examples: "/>
+  </list>
+</t>
+<figure>
+  <artwork><![CDATA[
+  ROLE;LANGUAGE=tr:hoca
+]]></artwork>
+</figure>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+        language-param = "LANGUAGE=" Language-Tag
+          ; Language-Tag is defined in section 2.1 of RFC 5646
+
+]]></artwork>
+</figure></section>
+<section anchor="section5_2" title="VALUE"><t>The VALUE parameter is <spanx style="strong">OPTIONAL</spanx>, used to identify the value type
+(data type) and format of the value.  The use of these predefined
+formats is encouraged even if the value parameter is not explicitly
+used.  By defining a standard set of value types and their formats,
+existing parsing and processing code can be leveraged.  The
+predefined data type values <spanx style="strong">MUST NOT</spanx> be repeated in COMMA-separated
+value lists except within the N, NICKNAME, ADR, and CATEGORIES
+properties.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+  value-param = "VALUE=" value-type
+
+  value-type = "text"
+             / "uri"
+             / "date"
+             / "time"
+             / "date-time"
+             / "date-and-or-time"
+             / "timestamp"
+             / "boolean"
+             / "integer"
+             / "float"
+             / "utc-offset"
+             / "language-tag"
+             / iana-token  ; registered as described in section 12
+             / x-name
+]]></artwork>
+</figure></section>
+<section anchor="section5_3" title="PREF"><t>The PREF parameter is <spanx style="strong">OPTIONAL</spanx> and is used to indicate that the
+corresponding instance of a property is preferred by the vCard
+author.  Its value <spanx style="strong">MUST</spanx> be an integer between 1 and 100 that
+quantifies the level of preference.  Lower values correspond to a
+higher level of preference, with 1 being most preferred.</t>
+<t>When the parameter is absent, the default <spanx style="strong">MUST</spanx> be to interpret the
+property instance as being least preferred.</t>
+<t>Note that the value of this parameter is to be interpreted only in
+relation to values assigned to other instances of the same property
+in the same vCard.  A given value, or the absence of a value, <spanx style="strong">MUST NOT</spanx>
+be interpreted on its own.</t>
+<t>This parameter <spanx style="strong">MAY</spanx> be applied to any property that allows multiple
+instances.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+        pref-param = "PREF=" (1*2DIGIT / "100")
+                             ; An integer between 1 and 100.
+]]></artwork>
+</figure></section>
+<section anchor="section5_4" title="ALTID"><t>The ALTID parameter is used to "tag" property instances as being
+alternative representations of the same logical property.  For
+example, translations of a property in multiple languages generates
+multiple property instances having different LANGUAGE (<xref target="section5_1"/>)
+parameter that are tagged with the same ALTID value.</t>
+<t>This parameter&#8217;s value is treated as an opaque string.  Its sole
+purpose is to be compared for equality against other ALTID parameter
+values.</t>
+<t>Two property instances are considered alternative representations of
+the same logical property if and only if their names as well as the
+value of their ALTID parameters are identical.  Property instances
+without the ALTID parameter <spanx style="strong">MUST NOT</spanx> be considered an alternative
+representation of any other property instance.  Values for the ALTID
+parameter are not globally unique: they <spanx style="strong">MAY</spanx> be reused for different
+property names.</t>
+<t>Property instances having the same ALTID parameter value count as 1
+toward cardinality.  Therefore, since N (<xref target="section6_2_2"/>) has
+cardinality *1 and TITLE (<xref target="section6_6_1"/>) has cardinality *, these
+three examples would be legal:</t>
+<figure>
+  <artwork><![CDATA[
+  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
+  N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
+  (<U+XXXX> denotes a UTF8-encoded Unicode character.)
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+  TITLE;ALTID=1;LANGUAGE=fr:Patron
+  TITLE;ALTID=1;LANGUAGE=en:Boss
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+  TITLE;ALTID=1;LANGUAGE=fr:Patron
+  TITLE;ALTID=1;LANGUAGE=en:Boss
+  TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
+]]></artwork>
+</figure>
+<t>while this one would not:</t>
+<figure>
+  <artwork><![CDATA[
+  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
+  N:Yamada;Taro;;;
+  (Two instances of the N property.)
+]]></artwork>
+</figure>
+<t>and these three would be legal but questionable:</t>
+<figure>
+  <artwork><![CDATA[
+  TITLE;ALTID=1;LANGUAGE=fr:Patron
+  TITLE;ALTID=2;LANGUAGE=en:Boss
+  (Should probably have the same ALTID value.)
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+  TITLE;ALTID=1;LANGUAGE=fr:Patron
+  TITLE:LANGUAGE=en:Boss
+  (Second line should probably have ALTID=1.)
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
+  N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
+  N;ALTID=1;LANGUAGE=en:Smith;John;;;
+  (The last line should probably have ALTID=2.  But that would be
+   illegal because N has cardinality *1.)
+]]></artwork>
+</figure>
+<t>The ALTID property <spanx style="strong">MAY</spanx> also be used in may contexts other than with
+the LANGUAGE parameter.  Here&#8217;s an example with two representations
+of the same photo in different file formats:</t>
+<figure>
+  <artwork><![CDATA[
+  PHOTO;ALTID=1:data:image/jpeg;base64,...
+  PHOTO;ALTID=1;data:image/jp2;base64,...
+
+
+
+]]></artwork>
+</figure>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+        altid-param = "ALTID=" param-value
+]]></artwork>
+</figure></section>
+<section anchor="section5_5" title="PID"><t>The PID parameter is used to identify a specific property among
+multiple instances.  It plays a role analogous to the UID property
+(<xref target="section6_7_6"/>) on a per-property instead of per-vCard basis.  It <spanx style="strong">MAY</spanx>
+appear more than once in a given property.  It <spanx style="strong">MUST NOT</spanx> appear on
+properties that may have only one instance per vCard.  Its value is
+either a single small positive integer or a pair of small positive
+integers separated by a dot.  Multiple values may be encoded in a
+single PID parameter by separating the values with a comma ",".  See
+<xref target="section7"/> for more details on its usage.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+        pid-param = "PID=" pid-value *("," pid-value)
+        pid-value = 1*DIGIT ["." 1*DIGIT]
+]]></artwork>
+</figure></section>
+<section anchor="section5_6" title="TYPE"><t>The TYPE parameter has multiple, different uses.  In general, it is a
+way of specifying class characteristics of the associated property.
+Most of the time, its value is a comma-separated subset of a
+predefined enumeration.  In this document, the following properties
+make use of this parameter: FN, NICKNAME, PHOTO, ADR, TEL, EMAIL,
+IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES,
+NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI.  The TYPE
+parameter <spanx style="strong">MUST NOT</spanx> be applied on other properties defined in this
+document.</t>
+<t>The "work" and "home" values act like tags.  The "work" value implies
+that the property is related to an individual&#8217;s work place, while the
+"home" value implies that the property is related to an individual&#8217;s
+personal life.  When neither "work" nor "home" is present, it is
+implied that the property is related to both an individual&#8217;s work
+place and personal life in the case that the KIND property&#8217;s value is
+"individual", or to none in other cases.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+       type-param = "TYPE=" type-value *("," type-value)
+
+        type-value = "work" / "home" / type-param-tel
+                   / type-param-related / iana-token / x-name
+          ; This is further defined in individual property sections.
+]]></artwork>
+</figure></section>
+<section anchor="section5_7" title="MEDIATYPE"><t>The MEDIATYPE parameter is used with properties whose value is a URI.
+Its use is <spanx style="strong">OPTIONAL</spanx>.  It provides a hint to the vCard consumer
+application about the media type cite:norm[RFC2046] of the resource identified
+by the URI.  Some URI schemes do not need this parameter.  For
+example, the "data" scheme allows the media type to be explicitly
+indicated as part of the URI cite:info[RFC2397].  Another scheme, "http",
+provides the media type as part of the URI resolution process, with
+the Content-Type HTTP header cite:info[RFC2616].  The MEDIATYPE parameter is
+intended to be used with URI schemes that do not provide such
+functionality (e.g., "ftp" cite:info[RFC1738]).</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+  mediatype-param = "MEDIATYPE=" mediatype
+  mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
+    ; "attribute" and "value" are from [RFC2045]
+    ; "type-name" and "subtype-name" are from [RFC4288]
+]]></artwork>
+</figure>
+<t>cite:norm[RFC2045, text="&lt;xref target='RFC2045' format='none'/&gt;"] cite:norm[RFC4288, text="&lt;xref target='RFC4288' format='none'/&gt;"]</t></section>
+<section anchor="section5_8" title="CALSCALE"><t>The CALSCALE parameter is identical to the CALSCALE property in
+iCalendar (see cite:norm[RFC5545, suffix=", Section 3.7.1"]).  It is used to define the
+calendar system in which a date or date-time value is expressed.  The
+only value specified by iCalendar is "gregorian", which stands for
+the Gregorian system.  It is the default when the parameter is
+absent.  Additional values may be defined in extension documents and
+registered with IANA (see <xref target="section10_3_4"/>).  A vCard implementation
+<spanx style="strong">MUST</spanx> ignore properties with a CALSCALE parameter value that it does
+not understand.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+        calscale-param = "CALSCALE=" calscale-value
+
+        calscale-value = "gregorian" / iana-token / x-name
+]]></artwork>
+</figure></section>
+<section anchor="section5_9" title="SORT-AS"><t>The "sort-as" parameter is used to specify the string to be used for
+national-language-specific sorting.  Without this information,
+sorting algorithms could incorrectly sort this vCard within a
+sequence of sorted vCards.  When this property is present in a vCard,
+then the given strings are used for sorting the vCard.</t>
+<t>This parameter&#8217;s value is a comma-separated list that <spanx style="strong">MUST</spanx> have as
+many or fewer elements as the corresponding property value has
+components.  This parameter&#8217;s value is case-sensitive.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+  sort-as-param = "SORT-AS=" sort-as-value
+
+  sort-as-value = param-value *("," param-value)
+]]></artwork>
+</figure>
+<t>Examples: For the case of surname and given name sorting, the
+following examples define common sort string usage with the N
+property.</t>
+<figure>
+  <artwork><![CDATA[
+        FN:Rene van der Harten
+        N;SORT-AS="Harten,Rene":van der Harten;Rene,J.;Sir;R.D.O.N.
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+        FN:Robert Pau Shou Chang
+        N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+        FN:Osamu Koura
+        N;SORT-AS="Koura,Osamu":Koura;Osamu;;
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+        FN:Oscar del Pozo
+        N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+        FN:Chistine d'Aboville
+        N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+        FN:H. James de Mann
+        N;SORT-AS="Mann,James":de Mann;Henry,James;;
+]]></artwork>
+</figure>
+<t>If sorted by surname, the results would be:</t>
+<figure>
+  <artwork><![CDATA[
+        Christine d'Aboville
+        Rene van der Harten
+        Osamu Koura
+        H. James de Mann
+        Robert Pau Shou Chang
+        Oscar del Pozo
+]]></artwork>
+</figure>
+<t>If sorted by given name, the results would be:</t>
+<figure>
+  <artwork><![CDATA[
+        Christine d'Aboville
+        H. James de Mann
+        Osamu Koura
+        Oscar del Pozo
+        Rene van der Harten
+        Robert Pau Shou Chang
+]]></artwork>
+</figure></section>
+<section anchor="section5_10" title="GEO"><t>The GEO parameter can be used to indicate global positioning
+information that is specific to an address.  Its value is the same as
+that of the GEO property (see <xref target="section6_5_2"/>).</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+  geo-parameter = "GEO=" DQUOTE URI DQUOTE
+]]></artwork>
+</figure></section>
+<section anchor="section5_11" title="TZ"><t>The TZ parameter can be used to indicate time zone information that
+is specific to an address.  Its value is the same as that of the TZ
+property.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: "/>
+  </list>
+</t>
+<figure>
+  <artwork type="abnf"><![CDATA[
+  tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
+
+
+
+
+
+
+]]></artwork>
+</figure></section></section>
+<section anchor="section6" title="vCard Properties"><t>What follows is an enumeration of the standard vCard properties.</t>
+<section anchor="section6_1" title="General Properties"><section anchor="section6_1_1" title="BEGIN">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To denote the beginning of a syntactic entity within a
+text/vcard content-type.</t>
+    <t hangText="Value type: ">text</t>
+    <t hangText="Cardinality: ">1</t>
+    <t hangText="Special notes: ">The content entity <spanx style="strong">MUST</spanx> begin with the BEGIN property
+with a value of "VCARD".  The value is case-insensitive.<vspace blankLines="0"/>The BEGIN property is used in conjunction with the END property to
+   delimit an entity containing a related set of properties within a
+   text/vcard content-type.  This construct can be used instead of
+   including multiple vCards as body parts inside of a multipart/
+   alternative MIME message.  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.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  BEGIN-param = 0" "  ; no parameter allowed
+  BEGIN-value = "VCARD"
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+      BEGIN:VCARD
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_1_2" title="END"><t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To denote the end of a syntactic entity within a text/vcard
+content-type.</t>
+    <t hangText="Value type: ">text</t>
+    <t hangText="Cardinality: ">1</t>
+    <t hangText="Special notes: ">The content entity <spanx style="strong">MUST</spanx> end with the END type with a
+value of "VCARD".  The value is case-insensitive.<vspace blankLines="0"/>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.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  END-param = 0" "  ; no parameter allowed
+  END-value = "VCARD"
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: "/>
+  </list>
+</t>
+<figure>
+  <artwork><![CDATA[
+      END:VCARD
+]]></artwork>
+</figure></section>
+<section anchor="section6_1_3" title="SOURCE">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To identify the source of directory information contained
+in the content type.</t>
+    <t hangText="Value type: ">uri</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The SOURCE property is used to provide the means by
+which applications knowledgable in the given directory service
+protocol can obtain additional or more up-to-date information from
+the directory service.  It contains a URI as defined in cite:norm[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.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
+               / mediatype-param / any-param
+  SOURCE-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: "><figure>
+  <artwork><![CDATA[
+  SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+  SOURCE:http://directory.example.com/addressbooks/jdoe/
+   Jean%20Dupont.vcf
+]]></artwork>
+</figure></t>
+  </list>
+</t>
+</section>
+<section anchor="section6_1_4" title="KIND"><t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the kind of object the vCard represents.</t>
+    <t hangText="Value type: ">A single text value.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="Special notes: ">The value may be one of the following:</t>
+    <t hangText="&quot;individual&quot; ">for a vCard representing a single person or entity.
+This is the default kind of vCard.</t>
+    <t hangText="&quot;group&quot; ">for a vCard representing a group of persons or entities.
+The group&#8217;s member entities can be other vCards or other types
+of entities, such as email addresses or web sites.  A group
+vCard will usually contain MEMBER properties to specify the
+members of the group, but it is not required to.  A group vCard
+without MEMBER properties can be considered an abstract
+grouping, or one whose members are known empirically (perhaps
+"IETF Participants" or "Republican U.S. Senators").<vspace blankLines="0"/>All properties in a group vCard apply to the group as a whole,
+      and not to any particular MEMBER.  For example, an EMAIL
+      property might specify the address of a mailing list associated
+      with the group, and an IMPP property might refer to a group
+      chat room.</t>
+    <t hangText="&quot;org&quot; ">for a vCard representing an organization.  An organization
+vCard will not (in fact, <spanx style="strong">MUST NOT</spanx>) contain MEMBER properties,
+and so these are something of a cross between "individual" and
+"group".  An organization is a single entity, but not a person.
+It might represent a business or government, a department or
+division within a business or government, a club, an
+association, or the like.<vspace blankLines="0"/>All properties in an organization vCard apply to the
+      organization as a whole, as is the case with a group vCard.
+      For example, an EMAIL property might specify the address of a
+      contact point for the organization.</t>
+    <t hangText="&quot;location&quot; ">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").<vspace blankLines="0"/>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.</t>
+    <t hangText="An x-name. ">vCards <spanx style="strong">MAY</spanx> include private or experimental values for
+KIND.  Remember that x-name values are not intended for general
+use and are unlikely to interoperate.</t>
+    <t hangText="An iana-token. ">Additional values may be registered with IANA (see
+<xref target="section10_3_4"/>).  A new value&#8217;s specification document <spanx style="strong">MUST</spanx>
+specify which properties make sense for that new kind of vCard
+and which do not.</t>
+  </list>
+</t>
+<t>Implementations <spanx style="strong">MUST</spanx> support the specific string values defined
+   above.  If this property is absent, "individual" <spanx style="strong">MUST</spanx> 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 <spanx style="strong">SHOULD</spanx> act in a neutral way, which usually
+   means treating the vCard as though its kind were "individual".
+   The presence of MEMBER properties <spanx style="strong">MAY</spanx>, however, be taken as an
+   indication that the unknown kind is an extension of "group".</t>
+<t>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.</t>
+<t>Some clients might also make functional distinctions among the
+   kinds, ignoring "location" vCards for some purposes and
+   considering only "location" vCards for others.</t>
+<t>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.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  KIND-param = "VALUE=text" / any-param
+  KIND-value = "individual" / "group" / "org" / "location"
+             / iana-token / x-name
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: "><vspace blankLines="0"/>This represents someone named Jane Doe working in the marketing
+   department of the North American division of ABC Inc.
+<figure>
+  <artwork><![CDATA[
+      BEGIN:VCARD
+      VERSION:4.0
+      KIND:individual
+      FN:Jane Doe
+      ORG:ABC\, Inc.;North American Division;Marketing
+      END:VCARD
+]]></artwork>
+</figure>
+<vspace blankLines="0"/>This represents the department itself, commonly known as ABC
+Marketing.
+<figure>
+  <artwork><![CDATA[
+      BEGIN:VCARD
+      VERSION:4.0
+      KIND:org
+      FN:ABC Marketing
+      ORG:ABC\, Inc.;North American Division;Marketing
+      END:VCARD
+]]></artwork>
+</figure></t>
+  </list>
+</t></section>
+<section anchor="section6_1_5" title="XML">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To include extended XML-encoded vCard data in a plain
+vCard.</t>
+    <t hangText="Value type: ">A single text value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The content of this property is a single XML 1.0
+cite:norm[W3C.REC-xml-20081126] element whose namespace <spanx style="strong">MUST</spanx> be explicitly
+specified using the xmlns attribute and <spanx style="strong">MUST NOT</spanx> 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 &lt;vcard&gt; element,
+as defined in cite:norm[RFC6351].<vspace blankLines="0"/>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.
+<vspace blankLines="0"/>Support for this property is <spanx style="strong">OPTIONAL</spanx>, but implementations of this
+   specification <spanx style="strong">MUST</spanx> preserve instances of this property when
+   propagating vCards.
+<vspace blankLines="0"/>See cite:norm[RFC6351] for more information on the intended use of this
+   property.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  XML-param = "VALUE=text" / altid-param
+  XML-value = text
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_2" title="Identification Properties"><t>These types are used to capture information associated with the
+identification and naming of the entity associated with the vCard.</t>
+<section anchor="section6_2_1" title="FN">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the formatted text corresponding to the name of
+the object the vCard represents.</t>
+    <t hangText="Value type: ">A single text value.</t>
+    <t hangText="Cardinality: ">1*</t>
+    <t hangText="Special notes: ">This property is based on the semantics of the X.520
+Common Name attribute cite:norm[CCITT.X520.1988].  The property <spanx style="strong">MUST</spanx> be
+present in the vCard object.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  FN-param = "VALUE=text" / type-param / language-param / altid-param
+           / pid-param / pref-param / any-param
+  FN-value = text
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+      FN:Mr. John Q. Public\, Esq.
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_2_2" title="N">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the components of the name of the object the
+vCard represents.</t>
+    <t hangText="Value type: ">A single structured text value.  Each component can have
+multiple values.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="Special note: ">The structured property value corresponds, in
+sequence, to the Family Names (also known as surnames), Given
+Names, Additional Names, Honorific Prefixes, and Honorific
+Suffixes.  The text components are separated by the SEMICOLON
+character (U+003B).  Individual text components can include
+multiple text values separated by the COMMA character (U+002C).
+This property is based on the semantics of the X.520 individual
+name attributes cite:norm[CCITT.X520.1988].  The property <spanx style="strong">SHOULD</spanx> be present
+in the vCard object when the name of the object the vCard
+represents follows the X.520 model.<vspace blankLines="0"/>The SORT-AS parameter <spanx style="strong">MAY</spanx> be applied to this property.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  N-param = "VALUE=text" / sort-as-param / language-param
+          / altid-param / any-param
+  N-value = list-component 4(";" list-component)
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+          N:Public;John;Quinlan;Mr.;Esq.
+
+          N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_2_3" title="NICKNAME">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the text corresponding to the nickname of the
+object the vCard represents.</t>
+    <t hangText="Value type: ">One or more text values separated by a COMMA character
+(U+002C).</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="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.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  NICKNAME-param = "VALUE=text" / type-param / language-param
+                 / altid-param / pid-param / pref-param / any-param
+  NICKNAME-value = text-list
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+          NICKNAME:Robbie
+
+          NICKNAME:Jim,Jimmie
+
+          NICKNAME;TYPE=work:Boss
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_2_4" title="PHOTO">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify an image or photograph information that
+annotates some aspect of the object the vCard represents.</t>
+    <t hangText="Value type: ">A single URI.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  PHOTO-param = "VALUE=uri" / altid-param / type-param
+              / mediatype-param / pref-param / pid-param / any-param
+  PHOTO-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+    PHOTO:http://www.example.com/pub/photos/jqpublic.gif
+
+    PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
+     AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
+     ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
+     <...remainder of base64-encoded data...>
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_2_5" title="BDAY">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the birth date of the object the vCard
+represents.</t>
+    <t hangText="Value type: ">The default is a single date-and-or-time value.  It can
+also be reset to a single text value.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  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.
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+          BDAY:19960415
+          BDAY:--0415
+          BDAY;19531015T231000Z
+          BDAY;VALUE=text:circa 1800
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_2_6" title="ANNIVERSARY">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">The date of marriage, or equivalent, of the object the
+vCard represents.</t>
+    <t hangText="Value type: ">The default is a single date-and-or-time value.  It can
+also be reset to a single text value.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
+  ANNIVERSARY-value = date-and-or-time / text
+    ; Value and parameter MUST match.
+
+  ANNIVERSARY-param =/ altid-param / calscale-param / any-param
+    ; calscale-param can only be present when ANNIVERSARY-value is
+    ; date-and-or-time and actually contains a date or date-time.
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+          ANNIVERSARY:19960415
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_2_7" title="GENDER">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the components of the sex and gender identity of
+the object the vCard represents.</t>
+    <t hangText="Value type: ">A single structured value with two components.  Each
+component has a single text value.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="Special notes: ">The components correspond, in sequence, to the sex
+(biological), and gender identity.  Each component is optional.<list style="hanging">
+  <t hangText="Sex component: ">A single letter.  M stands for "male", F stands
+for "female", O stands for "other", N stands for "none or not
+applicable", U stands for "unknown".</t>
+  <t hangText="Gender identity component: ">Free-form text.</t>
+</list></t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+                GENDER-param = "VALUE=text" / any-param
+                GENDER-value = sex [";" text]
+
+                sex = "" / "M" / "F" / "O" / "N" / "U"
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+  GENDER:M
+  GENDER:F
+  GENDER:M;Fellow
+  GENDER:F;grrrl
+  GENDER:O;intersex
+  GENDER:;it's complicated
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_3" title="Delivery Addressing Properties"><t>These types are concerned with information related to the delivery
+addressing or label for the vCard object.</t>
+<section anchor="section6_3_1" title="ADR"><t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the components of the delivery address for the
+vCard object.</t>
+    <t hangText="Value type: ">A single structured text value, separated by the
+SEMICOLON character (U+003B).</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The structured type value consists of a sequence of
+address components.  The component values <spanx style="strong">MUST</spanx> be specified in
+their corresponding position.  The structured type value
+corresponds, in sequence, to<list style="empty">
+  <t>the post office box;</t>
+  <t>the extended address (e.g., apartment or suite number);</t>
+  <t>the street address;</t>
+  <t>the locality (e.g., city);</t>
+  <t>the region (e.g., state or province);</t>
+  <t>the postal code;</t>
+  <t>the country name (full name in the language specified in
+<xref target="section5_1"/>).</t>
+</list></t>
+  </list>
+</t>
+<t>When a component value is missing, the associated component
+   separator <spanx style="strong">MUST</spanx> still be specified.</t>
+<t>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 <spanx style="strong">SHOULD</spanx> be empty.</t>
+<t>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).</t>
+<t>The property can include the "PREF" parameter to indicate the
+   preferred delivery address when more than one address is
+   specified.</t>
+<t>The GEO and TZ parameters <spanx style="strong">MAY</spanx> be used with this property.</t>
+<t>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.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  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
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">In this example, the post office box and the extended
+address are absent.<figure>
+  <artwork><![CDATA[
+  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.
+]]></artwork>
+</figure></t>
+  </list>
+</t></section></section>
+<section anchor="section6_4" title="Communications Properties"><t>These properties describe information about how to communicate with
+the object the vCard represents.</t>
+<section anchor="section6_4_1" title="TEL"><t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the telephone number for telephony communication
+with the object the vCard represents.</t>
+    <t hangText="Value type: ">By default, it is a single free-form text value (for
+backward compatibility with vCard 3), but it <spanx style="strong">SHOULD</spanx> be reset to a
+URI value.  It is expected that the URI scheme will be "tel", as
+specified in cite:norm[RFC3966], but other schemes <spanx style="strong">MAY</spanx> be used.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">This property is based on the X.520 Telephone Number
+attribute cite:norm[CCITT.X520.1988].<vspace blankLines="0"/>The property can include the "PREF" parameter to indicate a
+   preferred-use telephone number.
+<vspace blankLines="0"/>The property can include the parameter "TYPE" to specify intended
+   use for the telephone number.  The predefined values for the TYPE
+   parameter are:</t>
+  </list>
+</t>
+<texttable suppress-title="false" style="full">
+  <ttcol align="left">Value</ttcol>
+  <ttcol align="left">Description</ttcol>
+  <c>text</c>
+  <c>Indicates that the telephone number supports text messages (SMS).</c>
+  <c>voice</c>
+  <c>Indicates a voice telephone number.</c>
+  <c>fax</c>
+  <c>Indicates a facsimile telephone number.</c>
+  <c>cell</c>
+  <c>Indicates a cellular or mobile telephone number.</c>
+  <c>video</c>
+  <c>Indicates a video conferencing telephone number.</c>
+  <c>pager</c>
+  <c>Indicates a paging device telephone number.</c>
+  <c>textphone</c>
+  <c>Indicates a telecommunication device for people with  hearing or speech difficulties.</c>
+</texttable>
+<t>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".</t>
+<t>If this property&#8217;s value is a URI that can also be used for
+   instant messaging, the IMPP (<xref target="section6_4_3"/>) property <spanx style="strong">SHOULD</spanx> be
+   used in addition to this property.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  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.
+
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+  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
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t></section>
+<section anchor="section6_4_2" title="EMAIL">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the electronic mail address for communication
+with the object the vCard represents.</t>
+    <t hangText="Value type: ">A single text value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The property can include tye "PREF" parameter to
+indicate a preferred-use email address when more than one is
+specified.<vspace blankLines="0"/>Even though the value is free-form UTF-8 text, it is likely to be
+   interpreted by a Mail User Agent (MUA) as an "addr-spec", as
+   defined in cite:norm[RFC5322, suffix=", Section 3.4.1"].  Readers should also be aware
+   of the current work toward internationalized email addresses
+   cite:info[RFC5335bis].</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
+              / altid-param / any-param
+  EMAIL-value = text
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        EMAIL;TYPE=work:jqpublic@xyz.example.com
+
+        EMAIL;PREF=1:jane_doe@example.com
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_4_3" title="IMPP">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the URI for instant messaging and presence
+protocol communications with the object the vCard represents.</t>
+    <t hangText="Value type: ">A single URI.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The property may include the "PREF" parameter to
+indicate that this is a preferred address and has the same
+semantics as the "PREF" parameter in a TEL property.<vspace blankLines="0"/>If this property&#8217;s value is a URI that can be used for voice
+and/or video, the TEL property (<xref target="section6_4_1"/>) <spanx style="strong">SHOULD</spanx> be used in
+addition to this property.
+<vspace blankLines="0"/>This property is adapted from cite:info[RFC4770], which is made obsolete by
+   this document.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
+             / mediatype-param / altid-param / any-param
+  IMPP-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+    IMPP;PREF=1:xmpp:alice@example.com
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_4_4" title="LANG">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the language(s) that may be used for contacting
+the entity associated with the vCard.</t>
+    <t hangText="Value type: ">A single language-tag value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  LANG-param = "VALUE=language-tag" / pid-param / pref-param
+             / altid-param / type-param / any-param
+  LANG-value = Language-Tag
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+    LANG;TYPE=work;PREF=1:en
+    LANG;TYPE=work;PREF=2:fr
+    LANG;TYPE=home:fr
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_5" title="Geographical Properties"><t>These properties are concerned with information associated with
+geographical positions or regions associated with the object the
+vCard represents.</t>
+<section anchor="section6_5_1" title="TZ">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify information related to the time zone of the
+object the vCard represents.</t>
+    <t hangText="Value type: ">The default is a single text value.  It can also be
+reset to a single URI or utc-offset value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">It is expected that names from the public-domain
+Olson database cite:info[TZ-DB] will be used, but this is not a
+restriction.  See also cite:info[IANA-TZ].<vspace blankLines="0"/>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.
+<vspace blankLines="0"/>Note that utc-offset values <spanx style="strong">SHOULD NOT</spanx> be used because the UTC
+   offset varies with time&#8201;&#8212;&#8201;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.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  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
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+  TZ:Raleigh/North America
+
+  TZ;VALUE=utc-offset:-0500
+    ; Note: utc-offset format is NOT RECOMMENDED.
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_5_2" title="GEO">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify information related to the global positioning of
+the object the vCard represents.</t>
+    <t hangText="Value type: ">A single URI.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The "geo" URI scheme cite:norm[RFC5870] is particularly well
+suited for this property, but other schemes <spanx style="strong">MAY</spanx> be used.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
+            / mediatype-param / altid-param / any-param
+  GEO-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        GEO:geo:37.386013,-122.082932
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_6" title="Organizational Properties"><t>These properties are concerned with information associated with
+characteristics of the organization or organizational units of the
+object that the vCard represents.</t>
+<section anchor="section6_6_1" title="TITLE"><t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the position or job of the object the vCard
+represents.</t>
+    <t hangText="Value type: ">A single text value.</t>
+  </list>
+</t>
+<t>Cardinality:  *</t>
+<t>
+  <list style="hanging">
+    <t hangText="Special notes: ">This property is based on the X.520 Title attribute
+cite:norm[CCITT.X520.1988].</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  TITLE-param = "VALUE=text" / language-param / pid-param
+              / pref-param / altid-param / type-param / any-param
+  TITLE-value = text
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        TITLE:Research Scientist
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t></section>
+<section anchor="section6_6_2" title="ROLE"><t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the function or part played in a particular
+situation by the object the vCard represents.</t>
+    <t hangText="Value type: ">A single text value.</t>
+    <t hangText="Cardinality: ">*</t>
+  </list>
+</t>
+<t>Special notes:  This property is based on the X.520 Business Category
+   explanatory attribute cite:norm[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.</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
+             / type-param / altid-param / any-param
+  ROLE-value = text
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        ROLE:Project Leader
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t></section>
+<section anchor="section6_6_3" title="LOGO">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify a graphic image of a logo associated with the
+object the vCard represents.</t>
+    <t hangText="Value type: ">A single URI.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
+             / type-param / mediatype-param / altid-param / any-param
+  LOGO-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+  LOGO:http://www.example.com/pub/logos/abccorp.jpg
+
+  LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
+   AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
+   ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
+   <...the remainder of base64-encoded data...>
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_6_4" title="ORG">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the organizational name and units associated
+with the vCard.</t>
+    <t hangText="Value type: ">A single structured text value consisting of components
+separated by the SEMICOLON character (U+003B).</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The property is based on the X.520 Organization Name
+and Organization Unit attributes cite:norm[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.<vspace blankLines="0"/>The SORT-AS parameter <spanx style="strong">MAY</spanx> be applied to this property.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  ORG-param = "VALUE=text" / sort-as-param / language-param
+            / pid-param / pref-param / altid-param / type-param
+            / any-param
+  ORG-value = component *(";" component)
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">A property value consisting of an organizational name,
+organizational unit #1 name, and organizational unit #2 name.<figure>
+  <artwork><![CDATA[
+        ORG:ABC\, Inc.;North American Division;Marketing
+]]></artwork>
+</figure></t>
+  </list>
+</t>
+</section>
+<section anchor="section6_6_5" title="MEMBER">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To include a member in the group this vCard represents.</t>
+    <t hangText="Value type: ">A single URI.  It <spanx style="strong">MAY</spanx> refer to something other than a
+vCard object.  For example, an email distribution list could
+employ the "mailto" URI scheme cite:info[RFC6068] for efficiency.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">This property <spanx style="strong">MUST NOT</spanx> be present unless the value of
+the KIND property is "group".</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
+               / mediatype-param / any-param
+  MEMBER-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+  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:subscriber1@example.com
+  MEMBER:xmpp:subscriber2@example.com
+  MEMBER:sip:subscriber3@example.com
+  MEMBER:tel:+1-418-555-5555
+  END:VCARD
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_6_6" title="RELATED">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify a relationship between another entity and the
+entity represented by this vCard.</t>
+    <t hangText="Value type: ">A single URI.  It can also be reset to a single text
+value.  The text value can be used to specify textual information.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">The TYPE parameter <spanx style="strong">MAY</spanx> be used to characterize the
+related entity.  It contains a comma-separated list of values that
+are registered with IANA as described in <xref target="section10_2"/>.  The
+registry is pre-populated with the values defined in cite:norm[xfn].  This
+document also specifies two additional values:<list style="hanging">
+  <t hangText="agent: ">an entity who may sometimes act on behalf of the entity
+associated with the vCard.</t>
+  <t hangText="emergency: ">indicates an emergency contact</t>
+</list></t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  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"
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+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.
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_7" title="Explanatory Properties"><t>These properties are concerned with additional explanations, such as
+that related to informational notes or revisions specific to the
+vCard.</t>
+<section anchor="section6_7_1" title="CATEGORIES">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify application category information about the
+vCard, also known as "tags".</t>
+    <t hangText="Value type: ">One or more text values separated by a COMMA character
+(U+002C).</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  CATEGORIES-param = "VALUE=text" / pid-param / pref-param
+                   / type-param / altid-param / any-param
+  CATEGORIES-value = text-list
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        CATEGORIES:TRAVEL AGENT
+
+        CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_7_2" title="NOTE"><t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify supplemental information or a comment that is
+associated with the vCard.</t>
+    <t hangText="Value type: ">A single text value.</t>
+    <t hangText="Cardinality: ">*</t>
+  </list>
+</t>
+<t>Special notes:  The property is based on the X.520 Description
+   attribute cite:norm[CCITT.X520.1988].</t>
+<t>
+  <list style="hanging">
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
+             / type-param / altid-param / any-param
+  NOTE-value = text
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        NOTE:This fax number is operational 0800 to 1715
+          EST\, Mon-Fri.
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t></section>
+<section anchor="section6_7_3" title="PRODID">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the identifier for the product that created the
+vCard object.</t>
+    <t hangText="Type value: ">A single text value.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="Special notes: ">Implementations <spanx style="strong">SHOULD</spanx> use a method such as that
+specified for Formal Public Identifiers in cite:info[ISO9070] or for
+Universal Resource Names in cite:info[RFC3406] to ensure that the text
+value is unique.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  PRODID-param = "VALUE=text" / any-param
+  PRODID-value = text
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_7_4" title="REV">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify revision information about the current vCard.</t>
+    <t hangText="Value type: ">A single timestamp value.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="Special notes: ">The value distinguishes the current revision of the
+information in this vCard for other renditions of the information.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  REV-param = "VALUE=timestamp" / any-param
+  REV-value = timestamp
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        REV:19951031T222710Z
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_7_5" title="SOUND">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify a digital sound content information that
+annotates some aspect of the vCard.  This property is often used
+to specify the proper pronunciation of the name property value of
+the vCard.</t>
+    <t hangText="Value type: ">A single URI.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
+              / type-param / mediatype-param / altid-param
+              / any-param
+  SOUND-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+  SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
+
+  SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
+   AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
+   ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
+   <...the remainder of base64-encoded data...>
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_7_6" title="UID">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify a value that represents a globally unique
+identifier corresponding to the entity associated with the vCard.</t>
+    <t hangText="Value type: ">A single URI value.  It <spanx style="strong">MAY</spanx> also be reset to free-form
+text.</t>
+    <t hangText="Cardinality: ">*1</t>
+    <t hangText="Special notes: ">This property is used to uniquely identify the object
+that the vCard represents.  The "uuid" URN namespace defined in
+cite:norm[RFC4122] is particularly well suited to this task, but other URI
+schemes <spanx style="strong">MAY</spanx> be used.  Free-form text <spanx style="strong">MAY</spanx> also be used.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  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
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_7_7" title="CLIENTPIDMAP">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To give a global meaning to a local PID source identifier.</t>
+    <t hangText="Value type: ">A semicolon-separated pair of values.  The first field
+is a small integer corresponding to the second field of a PID
+parameter instance.  The second field is a URI.  The "uuid" URN
+namespace defined in cite:norm[RFC4122] is particularly well suited to this
+task, but other URI schemes <spanx style="strong">MAY</spanx> be used.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="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 <spanx style="strong">MUST</spanx>
+have an associated CLIENTPIDMAP.  See <xref target="section7"/> for more details
+on the usage of CLIENTPIDMAP.<vspace blankLines="0"/>PID source identifiers <spanx style="strong">MUST</spanx> be strictly positive.  Zero is not
+   allowed.
+<vspace blankLines="0"/>As a special exception, the PID parameter <spanx style="strong">MUST NOT</spanx> be applied to
+   this property.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  CLIENTPIDMAP-param = any-param
+  CLIENTPIDMAP-value = 1*DIGIT ";" URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+  TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
+  EMAIL;PID=4.1,5.2:jdoe@example.com
+  CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
+  CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_7_8" title="URL">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify a uniform resource locator associated with the
+object to which the vCard refers.  Examples for individuals
+include personal web sites, blogs, and social networking site
+identifiers.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Value type: ">A single uri value.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  URL-param = "VALUE=uri" / pid-param / pref-param / type-param
+            / mediatype-param / altid-param / any-param
+  URL-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        URL:http://example.org/restaurant.french/~chezchic.html
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_7_9" title="VERSION">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the version of the vCard specification used to
+format this vCard.</t>
+    <t hangText="Value type: ">A single text value.</t>
+    <t hangText="Cardinality: ">1</t>
+    <t hangText="Special notes: ">This property <spanx style="strong">MUST</spanx> be present in the vCard object,
+and it must appear immediately after BEGIN:VCARD.  The value <spanx style="strong">MUST</spanx>
+be "4.0" if the vCard corresponds to this specification.  Note
+that earlier versions of vCard allowed this property to be placed
+anywhere in the vCard object, or even to be absent.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  VERSION-param = "VALUE=text" / any-param
+  VERSION-value = "4.0"
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+        VERSION:4.0
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_8" title="Security Properties"><t>These properties are concerned with the security of communication
+pathways or access to the vCard.</t>
+<section anchor="section6_8_1" title="KEY">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify a public key or authentication certificate
+associated with the object that the vCard represents.</t>
+    <t hangText="Value type: ">A single URI.  It can also be reset to a text value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  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
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+  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 ...>
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_9" title="Calendar Properties"><t>These properties are further specified in cite:norm[RFC2739].</t>
+<section anchor="secton6_9_1" title="FBURL">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the URI for the busy time associated with the
+object that the vCard represents.</t>
+    <t hangText="Value type: ">A single URI value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">Where multiple FBURL properties are specified, the
+default FBURL property is indicated with the PREF parameter.  The
+FTP cite:info[RFC1738] or HTTP cite:info[RFC2616] type of URI points to an iCalendar
+cite:norm[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".</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
+              / mediatype-param / altid-param / any-param
+  FBURL-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+  FBURL;PREF=1:http://www.example.com/busy/janedoe
+  FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_9_2" title="CALADRURI">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the calendar user address cite:norm[RFC5545] to which a
+scheduling request cite:norm[RFC5546] should be sent for the object
+represented by the vCard.</t>
+    <t hangText="Value type: ">A single URI value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">Where multiple CALADRURI properties are specified,
+the default CALADRURI property is indicated with the PREF
+parameter.</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
+                  / mediatype-param / altid-param / any-param
+  CALADRURI-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Example: ">
+      <figure>
+  <artwork><![CDATA[
+  CALADRURI;PREF=1:mailto:janedoe@example.com
+  CALADRURI:http://example.com/calendar/jdoe
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section>
+<section anchor="section6_9_3" title="CALURI">
+  <t>
+  <list style="hanging">
+    <t hangText="Purpose: ">To specify the URI for a calendar associated with the
+object represented by the vCard.</t>
+    <t hangText="Value type: ">A single URI value.</t>
+    <t hangText="Cardinality: ">*</t>
+    <t hangText="Special notes: ">Where multiple CALURI properties are specified, the
+default CALURI property is indicated with the PREF parameter.  The
+property should contain a URI pointing to an iCalendar cite:norm[RFC5545]
+object associated with a snapshot of the user&#8217;s calendar store.
+If the iCalendar object is represented as a file or document, its
+file extension should be ".ics".</t>
+    <t hangText="ABNF: ">
+      <figure>
+  <artwork type="abnf"><![CDATA[
+  CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
+               / mediatype-param / altid-param / any-param
+  CALURI-value = URI
+]]></artwork>
+</figure>
+    </t>
+    <t hangText="Examples: ">
+      <figure>
+  <artwork><![CDATA[
+  CALURI;PREF=1:http://cal.example.com/calA
+  CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t>
+</section></section>
+<section anchor="section6_10" title="Extended Properties and Parameters">
+  <t>The properties and parameters defined by this document can be
+extended.  Non-standard, private properties and parameters with a
+name starting with "X-" may be defined bilaterally between two
+cooperating agents without outside registration or standardization.</t>
+</section></section>
+<section anchor="section7" title="Synchronization"><t>vCard data often needs to be synchronized between devices.  In this
+context, synchronization is defined as the intelligent merging of two
+representations of the same object. vCard 4.0 includes mechanisms to
+aid this process.</t>
+<section anchor="section7_1" title="Mechanisms"><t>Two mechanisms are available: the UID property is used to match
+multiple instances of the same vCard, while the PID parameter is used
+to match multiple instances of the same property.</t>
+<t>The term "matching" is used here to mean recognizing that two
+instances are in fact representations of the same object.  For
+example, a single vCard that is shared with someone results in two
+vCard instances.  After they have evolved separately, they still
+represent the same object, and therefore may be matched by a
+synchronization engine.</t>
+<section anchor="section7_1_1" title="Matching vCard Instances"><t>vCard instances for which the UID properties (<xref target="section6_7_6"/>) are
+equivalent <spanx style="strong">MUST</spanx> be matched.  Equivalence is determined as specified
+in cite:norm[RFC3986, suffix=", Section 6"].</t>
+<t>In all other cases, vCard instances <spanx style="strong">MAY</spanx> be matched at the discretion
+of the synchronization engine.</t></section>
+<section anchor="section7_1_2" title="Matching Property Instances"><t>Property instances belonging to unmatched vCards <spanx style="strong">MUST NOT</spanx> be matched.</t>
+<t>Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
+same <spanx style="strong">MUST NOT</spanx> be matched.</t>
+<t>Property instances whose name is CLIENTPIDMAP are handled separately
+and <spanx style="strong">MUST NOT</spanx> be matched.  The synchronization <spanx style="strong">MUST</spanx> ensure that there
+is consistency of CLIENTPIDMAPs among matched vCard instances.</t>
+<t>Property instances belonging to matched vCards, whose name is the
+same, and whose maximum cardinality is 1, <spanx style="strong">MUST</spanx> be matched.</t>
+<t>Property instances belonging to matched vCards, whose name is the
+same, and whose PID parameters match, <spanx style="strong">MUST</spanx> be matched.  See
+<xref target="section7_1_3"/> for details on PID matching.</t>
+<t>In all other cases, property instances <spanx style="strong">MAY</spanx> be matched at the
+discretion of the synchronization engine.</t></section>
+<section anchor="section7_1_3" title="PID Matching"><t>Two PID values for which the first fields are equivalent represent
+the same local value.</t>
+<t>Two PID values representing the same local value and for which the
+second fields point to CLIENTPIDMAP properties whose second field
+URIs are equivalent (as specified in cite:norm[RFC3986, suffix=", Section 6"]) also
+represent the same global value.</t>
+<t>PID parameters for which at least one pair of their values represent
+the same global value <spanx style="strong">MUST</spanx> be matched.</t>
+<t>In all other cases, PID parameters <spanx style="strong">MAY</spanx> be matched at the discretion
+of the synchronization engine.</t>
+<t>For example, PID value "5.1", in the first vCard below, and PID value
+"5.2", in the second vCard below, represent the same global value.</t>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  EMAIL;PID=4.2,5.1:jdoe@example.com
+  CLIENTPIDMAP:1;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
+  CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
+  END:VCARD
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  EMAIL;PID=5.1,5.2:john@example.com
+  CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
+  CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
+  END:VCARD
+]]></artwork>
+</figure></section></section>
+<section anchor="section7_2" title="Example"><section anchor="section7_2_1" title="Creation"><t>The following simple vCard is first created on a given device.</t>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
+  FN;PID=1.1:J. Doe
+  N:Doe;J.;;;
+  EMAIL;PID=1.1:jdoe@example.com
+  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
+  END:VCARD
+]]></artwork>
+</figure>
+<t>This new vCard is assigned the UID
+"urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating
+device.  The FN and EMAIL properties are assigned the same local
+value of 1, and this value is given global context by associating it
+with "urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which
+represents the creating device.  We are at liberty to reuse the same
+local value since instances of different properties will never be
+matched.  The N property has no PID because it is forbidden by its
+maximum cardinality of 1.</t></section>
+<section anchor="section7_2_2" title="Initial Sharing">
+  <t>This vCard is shared with a second device.  Upon inspecting the UID
+property, the second device understands that this is a new vCard
+(i.e., unmatched) and thus the synchronization results in a simple
+copy.</t>
+</section>
+<section anchor="section7_2_3" title="Adding and Sharing a Property"><t>A new phone number is created on the first device, then the vCard is
+shared with the second device.  This is what the second device
+receives:</t>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
+  FN;PID=1.1:J. Doe
+  N:Doe;J.;;;
+  EMAIL;PID=1.1:jdoe@example.com
+  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
+  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
+  END:VCARD
+]]></artwork>
+</figure>
+<t>Upon inspecting the UID property, the second device matches the vCard
+it received to the vCard that it already has stored.  It then starts
+comparing the properties of the two vCards in same-named pairs.</t>
+<t>The FN properties are matched because the PID parameters have the
+same global value.  Since the property value is the same, no update
+takes place.</t>
+<t>The N properties are matched automatically because their maximum
+cardinality is 1.  Since the property value is the same, no update
+takes place.</t>
+<t>The EMAIL properties are matched because the PID parameters have the
+same global value.  Since the property value is the same, no update
+takes place.</t>
+<t>The TEL property in the new vCard is not matched to any in the stored
+vCard because no property in the stored vCard has the same name.
+Therefore, this property is copied from the new vCard to the stored
+vCard.</t>
+<t>The CLIENTPIDMAP property is handled separately by the
+synchronization engine.  It ensures that it is consistent with the
+stored one.  If it was not, the results would be up to the
+synchronization engine, and thus undefined by this document.</t></section>
+<section anchor="section7_2_4" title="Simultaneous Editing"><t>A new email address and a new phone number are added to the vCard on
+each of the two devices, and then a new synchronization event
+happens.  Here are the vCards that are communicated to each other:</t>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
+  FN;PID=1.1:J. Doe
+  N:Doe;J.;;;
+  EMAIL;PID=1.1:jdoe@example.com
+  EMAIL;PID=2.1:boss@example.com
+  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
+  TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
+  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
+  END:VCARD
+]]></artwork>
+</figure>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
+  FN;PID=1.1:J. Doe
+  N:Doe;J.;;;
+  EMAIL;PID=1.1:jdoe@example.com
+  EMAIL;PID=2.2:ceo@example.com
+  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
+  TEL;PID=2.2;VALUE=uri:tel:+1-666-666-6666
+  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
+  CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
+  END:VCARD
+]]></artwork>
+</figure>
+<t>On the first device, the same PID source identifier (1) is reused for
+the new EMAIL and TEL properties.  On the second device, a new source
+identifier (2) is generated, and a corresponding CLIENTPIDMAP
+property is created.  It contains the second device&#8217;s identifier,
+"urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".</t>
+<t>The new EMAIL properties are unmatched on both sides since the PID
+global value is new in both cases.  The sync thus results in a copy
+on both sides.</t>
+<t>Although the situation appears to be the same for the TEL properties,
+in this case, the synchronization engine is particularly smart and
+matches the two new TEL properties even though their PID global
+values are different.  Note that in this case, the rules of
+<xref target="section7_1_2"/> state that two properties <spanx style="strong">MAY</spanx> be matched at the
+discretion of the synchronization engine.  Therefore, the two
+properties are merged.</t>
+<t>All this results in the following vCard, which is stored on both
+devices:</t>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
+  FN:J. Doe
+  N:Doe;J.;;;
+  EMAIL;PID=1.1:jdoe@example.com
+  EMAIL;PID=2.1:boss@example.com
+  EMAIL;PID=2.2:ceo@example.com
+  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
+  TEL;PID=2.1,2.2;VALUE=uri:tel:+1-666-666-6666
+  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
+  CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
+  END:VCARD
+]]></artwork>
+</figure></section>
+<section anchor="section7_2_5" title="Global Context Simplification"><t>The two devices finish their synchronization procedure by simplifying
+their global contexts.  Since they haven&#8217;t talked to any other
+device, the following vCard is for all purposes equivalent to the
+above.  It is also shorter.</t>
+<figure>
+  <artwork><![CDATA[
+  BEGIN:VCARD
+  VERSION:4.0
+  UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
+  FN:J. Doe
+  N:Doe;J.;;;
+  EMAIL;PID=1.1:jdoe@example.com
+  EMAIL;PID=2.1:boss@example.com
+  EMAIL;PID=3.1:ceo@example.com
+  TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
+  TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
+  CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
+  END:VCARD
+]]></artwork>
+</figure>
+<t>The details of global context simplification are unspecified by this
+document.  They are left up to the synchronization engine.  This
+example is merely intended to illustrate the possibility, which
+investigating would be, in the author&#8217;s opinion, worthwhile.</t></section></section></section>
+<section anchor="section8" title="Example: Author&#8217;s vCard">
+  <figure>
+  <artwork><![CDATA[
+ BEGIN:VCARD
+ VERSION:4.0
+ FN:Simon Perreault
+ N:Perreault;Simon;;;ing. jr,M.Sc.
+ BDAY:--0203
+ ANNIVERSARY:20090808T1430-0500
+ GENDER:M
+ LANG;PREF=1:fr
+ LANG;PREF=2:en
+ ORG;TYPE=work:Viagenie
+ ADR;TYPE=work:;Suite D2-630;2875 Laurier;
+  Quebec;QC;G1V 2M2;Canada
+ TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102
+ TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501
+ EMAIL;TYPE=work:simon.perreault@viagenie.ca
+ GEO;TYPE=work:geo:46.772673,-71.282945
+ KEY;TYPE=work;VALUE=uri:
+  http://www.viagenie.ca/simon.perreault/simon.asc
+ TZ:-0500
+ URL;TYPE=home:http://nomis80.org
+ END:VCARD
+]]></artwork>
+</figure>
+</section>
+<section anchor="section9" title="Security Considerations">
+  <t>
+  <list style="symbols">
+    <t>Internet mail is often used to transport vCards and is subject to
+many well-known security attacks, including monitoring, replay,
+and forgery.  Care should be taken by any directory service in
+allowing information to leave the scope of the service itself,
+where any access controls or confidentiality can no longer be
+guaranteed.  Applications should also take care to display
+directory data in a "safe" environment.</t>
+    <t>vCards can carry cryptographic keys or certificates, as described
+in <xref target="section6_8_1"/>.</t>
+    <t>vCards often carry information that can be sensitive (e.g.,
+birthday, address, and phone information).  Although vCards have
+no inherent authentication or confidentiality provisions, they can
+easily be carried by any security mechanism that transfers MIME
+objects to address authentication or confidentiality (e.g., S/MIME
+cite:info[RFC5751], OpenPGP cite:info[RFC4880]).  In cases where the confidentiality
+or authenticity of information contained in vCard is a concern,
+the vCard <spanx style="strong">SHOULD</spanx> be transported using one of these secure
+mechanisms.  The KEY property (<xref target="section6_8_1"/>) can be used to
+transport the public key used by these mechanisms.</t>
+    <t>The information in a vCard may become out of date.  In cases where
+the vitality of data is important to an originator of a vCard, the
+SOURCE property (<xref target="section6_1_3"/>) <spanx style="strong">SHOULD</spanx> be specified.  In addition,
+the "REV" type described in <xref target="section6_7_4"/> can be specified to
+indicate the last time that the vCard data was updated.</t>
+    <t>Many vCard properties may be used to transport URIs.  Please refer
+to cite:norm[RFC3986, suffix=", Section 7"], for considerations related to URIs.</t>
+  </list>
+</t>
+</section>
+<section anchor="section10" title="IANA Considerations"><section anchor="section10_1" title="Media Type Registration"><t>IANA has registered the following Media Type (in
+<eref target="http://www.iana.org"/>) and marked the text/directory Media Type as
+DEPRECATED.</t>
+<t>
+  <list style="hanging">
+    <t hangText="To: ">ietf-types@iana.org</t>
+    <t hangText="Subject: ">Registration of media type text/vcard</t>
+    <t hangText="Type name: ">text</t>
+    <t hangText="Subtype name: ">vcard</t>
+    <t hangText="Required parameters: ">none</t>
+    <t hangText="Optional parameters: ">version<vspace blankLines="0"/>The "version" parameter is to be interpreted identically as the
+   VERSION vCard property.  If this parameter is present, all vCards
+   in a text/vcard body part <spanx style="strong">MUST</spanx> have a VERSION property with value
+   identical to that of this MIME parameter.
+<vspace blankLines="0"/>"charset": as defined for text/plain cite:norm[RFC2046]; encodings other
+   than UTF-8 cite:norm[RFC3629] <spanx style="strong">MUST NOT</spanx> be used.</t>
+    <t hangText="Encoding considerations: ">8bit</t>
+    <t hangText="Security considerations: ">See <xref target="section9"/>.</t>
+    <t hangText="Interoperability considerations: ">The text/vcard media type is
+intended to identify vCard data of any version.  There are older
+specifications of vCard cite:info[RFC2426] cite:info[vCard21] still in common use.
+While these formats are similar, they are not strictly compatible.
+In general, it is necessary to inspect the value of the VERSION
+property (see <xref target="section6_7_9"/>) for identifying the standard to which
+a given vCard object conforms.<vspace blankLines="0"/>In addition, the following media types are known to have been used
+   to refer to vCard data.  They should be considered deprecated in
+   favor of text/vcard.
+<list style="symbols">
+  <t>text/directory</t>
+  <t>text/directory; profile=vcard</t>
+  <t>text/x-vcard</t>
+</list></t>
+    <t hangText="Published specification: ">RFC 6350</t>
+    <t hangText="Applications that use this media type: ">They are numerous, diverse,
+and include mail user agents, instant messaging clients, address
+book applications, directory servers, and customer relationship
+management software.</t>
+    <t hangText="Additional information: ">
+      <list style="hanging">
+  <t hangText="Magic number(s): "/>
+  <t hangText="File extension(s): ">.vcf .vcard</t>
+  <t hangText="Macintosh file type code(s): "/>
+</list>
+    </t>
+    <t hangText="Person &amp; email address to contact for further information: ">vCard
+discussion mailing list &lt;vcarddav@ietf.org&gt;</t>
+    <t hangText="Intended usage: ">COMMON</t>
+    <t hangText="Restrictions on usage: ">none</t>
+    <t hangText="Author: ">Simon Perreault</t>
+    <t hangText="Change controller: ">IETF</t>
+  </list>
+</t></section>
+<section anchor="section10_2" title="Registering New vCard Elements"><t>This section defines the process for registering new or modified
+vCard elements (i.e., properties, parameters, value data types, and
+values) with IANA.</t>
+<section anchor="section10_2_1" title="Registration Procedure"><t>The IETF has created a mailing list, vcarddav@ietf.org, which can be
+used for public discussion of vCard element proposals prior to
+registration.  Use of the mailing list is strongly encouraged.  The
+IESG has appointed a designated expert who will monitor the
+vcarddav@ietf.org mailing list and review registrations.</t>
+<t>Registration of new vCard elements <spanx style="strong">MUST</spanx> be reviewed by the designated
+expert and published in an RFC.  A Standards Track RFC is <spanx style="strong">REQUIRED</spanx>
+for the registration of new value data types that modify existing
+properties.  A Standards Track RFC is also <spanx style="strong">REQUIRED</spanx> for registration
+of vCard elements that modify vCard elements previously documented in
+a Standards Track RFC.</t>
+<t>The registration procedure begins when a completed registration
+template, defined in the sections below, is sent to vcarddav@ietf.org
+and iana@iana.org.  Within two weeks, the designated expert is
+expected to tell IANA and the submitter of the registration whether
+the registration is approved, approved with minor changes, or
+rejected with cause.  When a registration is rejected with cause, it
+can be re-submitted if the concerns listed in the cause are
+addressed.  Decisions made by the designated expert can be appealed
+to the IESG Applications Area Director, then to the IESG.  They
+follow the normal appeals procedure for IESG decisions.</t>
+<t>Once the registration procedure concludes successfully, IANA creates
+or modifies the corresponding record in the vCard registry.  The
+completed registration template is discarded.</t>
+<t>An RFC specifying new vCard elements <spanx style="strong">MUST</spanx> include the completed
+registration templates, which <spanx style="strong">MAY</spanx> be expanded with additional
+information.  These completed templates are intended to go in the
+body of the document, not in the IANA Considerations section.</t>
+<t>Finally, note that there is an XML representation for vCard defined
+in cite:norm[RFC6351].  An XML representation <spanx style="strong">SHOULD</spanx> be defined for new vCard
+elements.</t></section>
+<section anchor="section10_2_2" title="Vendor Namespace"><t>The vendor namespace is used for vCard elements associated with
+commercially available products.  "Vendor" or "producer" are
+construed as equivalent and very broadly in this context.</t>
+<t>A registration may be placed in the vendor namespace by anyone who
+needs to interchange files associated with the particular product.
+However, the registration formally belongs to the vendor or
+organization handling the vCard elements in the namespace being
+registered.  Changes to the specification will be made at their
+request, as discussed in subsequent sections.</t>
+<t>vCard elements belonging to the vendor namespace will be
+distinguished by the "VND-" prefix.  This is followed by an IANA-
+registered Private Enterprise Number (PEN), a dash, and a vCard
+element designation of the vendor&#8217;s choosing (e.g., "VND-123456-
+MUDPIE").</t>
+<t>While public exposure and review of vCard elements to be registered
+in the vendor namespace are not required, using the vcarddav@ietf.org
+mailing list for review is strongly encouraged to improve the quality
+of those specifications.  Registrations in the vendor namespace may
+be submitted directly to the IANA.</t></section>
+<section anchor="section10_2_3" title="Registration Template for Properties"><t>A property is defined by completing the following template.</t>
+<t>
+  <list style="hanging">
+    <t hangText="Namespace: ">Empty for the global namespace, "VND-NNNN-" for a vendor-
+specific property (where NNNN is replaced by the vendor&#8217;s PEN).</t>
+    <t hangText="Property name: ">The name of the property.</t>
+    <t hangText="Purpose: ">The purpose of the property.  Give a short but clear
+description.</t>
+    <t hangText="Value type: ">Any of the valid value types for the property value
+needs to be specified.  The default value type also needs to be
+specified.</t>
+    <t hangText="Cardinality: ">See <xref target="section6"/>.</t>
+    <t hangText="Property parameters: ">Any of the valid property parameters for the
+property <spanx style="strong">MUST</spanx> be specified.</t>
+    <t hangText="Description: ">Any special notes about the property, how it is to be
+used, etc.</t>
+    <t hangText="Format definition: ">The ABNF for the property definition needs to be
+specified.</t>
+    <t hangText="Example(s): ">One or more examples of instances of the property need
+to be specified.</t>
+  </list>
+</t></section>
+<section anchor="section10_2_4" title="Registration Template for Parameters"><t>A parameter is defined by completing the following template.</t>
+<t>
+  <list style="hanging">
+    <t hangText="Namespace: ">Empty for the global namespace, "VND-NNNN-" for a vendor-
+specific property (where NNNN is replaced by the vendor&#8217;s PEN).</t>
+    <t hangText="Parameter name: ">The name of the parameter.</t>
+    <t hangText="Purpose: ">The purpose of the parameter.  Give a short but clear
+description.</t>
+    <t hangText="Description: ">Any special notes about the parameter, how it is to be
+used, etc.</t>
+    <t hangText="Format definition: ">The ABNF for the parameter definition needs to be
+specified.</t>
+    <t hangText="Example(s): ">One or more examples of instances of the parameter need
+to be specified.</t>
+  </list>
+</t></section>
+<section anchor="section10_2_5" title="Registration Template for Value Data Types"><t>A value data type is defined by completing the following template.</t>
+<t>
+  <list style="hanging">
+    <t hangText="Value name: ">The name of the value type.</t>
+    <t hangText="Purpose: ">The purpose of the value type.  Give a short but clear
+description.</t>
+    <t hangText="Description: ">Any special notes about the value type, how it is to be
+used, etc.</t>
+    <t hangText="Format definition: ">The ABNF for the value type definition needs to
+be specified.</t>
+    <t hangText="Example(s): ">One or more examples of instances of the value type need
+to be specified.</t>
+  </list>
+</t></section>
+<section anchor="section10_2_6" title="Registration Template for Values"><t>A value is defined by completing the following template.</t>
+<t>
+  <list style="hanging">
+    <t hangText="Value: ">The value literal.</t>
+    <t hangText="Purpose: ">The purpose of the value.  Give a short but clear
+description.</t>
+    <t hangText="Conformance: ">The vCard properties and/or parameters that can take
+this value needs to be specified.</t>
+    <t hangText="Example(s): ">One or more examples of instances of the value need to
+be specified.</t>
+  </list>
+</t>
+<t>The following is a fictitious example of a registration of a vCard
+value:</t>
+<t>
+  <list style="hanging">
+    <t hangText="Value: ">supervisor</t>
+    <t hangText="Purpose: ">It means that the related entity is the direct hierarchical
+superior (i.e., supervisor or manager) of the entity this vCard
+represents.</t>
+    <t hangText="Conformance: ">This value can be used with the "TYPE" parameter
+applied on the "RELATED" property.</t>
+    <t hangText="Example(s): ">
+      <figure>
+  <artwork><![CDATA[
+RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
+]]></artwork>
+</figure>
+    </t>
+  </list>
+</t></section></section>
+<section anchor="section10_3" title="Initial vCard Elements Registries"><t>The IANA has created and will maintain the following registries for
+vCard elements with pointers to appropriate reference documents.  The
+registries are grouped together under the heading "vCard Elements".</t>
+<section anchor="section10_3_1" title="Properties Registry"><t>The following table has been used to initialize the properties
+registry.</t>
+<texttable suppress-title="false" style="full">
+  <ttcol align="left">Namespace</ttcol>
+  <ttcol align="left">Property</ttcol>
+  <ttcol align="left">Reference</ttcol>
+  <c/>
+  <c>SOURCE</c>
+  <c>RFC 6350, Section 6.1.3</c>
+  <c/>
+  <c>KIND</c>
+  <c>RFC 6350, Section 6.1.4</c>
+  <c/>
+  <c>XML</c>
+  <c>RFC 6350, Section 6.1.5</c>
+  <c/>
+  <c>FN</c>
+  <c>RFC 6350, Section 6.2.1</c>
+  <c/>
+  <c>N</c>
+  <c>RFC 6350, Section 6.2.2</c>
+  <c/>
+  <c>NICKNAME</c>
+  <c>RFC 6350, Section 6.2.3</c>
+  <c/>
+  <c>PHOTO</c>
+  <c>RFC 6350, Section 6.2.4</c>
+  <c/>
+  <c>BDAY</c>
+  <c>RFC 6350, Section 6.2.5</c>
+  <c/>
+  <c>ANNIVERSARY</c>
+  <c>RFC 6350, Section 6.2.6</c>
+  <c/>
+  <c>GENDER</c>
+  <c>RFC 6350, Section 6.2.7</c>
+  <c/>
+  <c>ADR</c>
+  <c>RFC 6350, Section 6.3.1</c>
+  <c/>
+  <c>TEL</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c/>
+  <c>EMAIL</c>
+  <c>RFC 6350, Section 6.4.2</c>
+  <c/>
+  <c>IMPP</c>
+  <c>RFC 6350, Section 6.4.3</c>
+  <c/>
+  <c>LANG</c>
+  <c>RFC 6350, Section 6.4.4</c>
+  <c/>
+  <c>TZ</c>
+  <c>RFC 6350, Section 6.5.1</c>
+  <c/>
+  <c>GEO</c>
+  <c>RFC 6350, Section 6.5.2</c>
+  <c/>
+  <c>TITLE</c>
+  <c>RFC 6350, Section 6.6.1</c>
+  <c/>
+  <c>ROLE</c>
+  <c>RFC 6350, Section 6.6.2</c>
+  <c/>
+  <c>LOGO</c>
+  <c>RFC 6350, Section 6.6.3</c>
+  <c/>
+  <c>ORG</c>
+  <c>RFC 6350, Section 6.6.4</c>
+  <c/>
+  <c>MEMBER</c>
+  <c>RFC 6350, Section 6.6.5</c>
+  <c/>
+  <c>RELATED</c>
+  <c>RFC 6350, Section 6.6.6</c>
+  <c/>
+  <c>CATEGORIES</c>
+  <c>RFC 6350, Section 6.7.1</c>
+  <c/>
+  <c>NOTE</c>
+  <c>RFC 6350, Section 6.7.2</c>
+  <c/>
+  <c>PRODID</c>
+  <c>RFC 6350, Section 6.7.3</c>
+  <c/>
+  <c>REV</c>
+  <c>RFC 6350, Section 6.7.4</c>
+  <c/>
+  <c>SOUND</c>
+  <c>RFC 6350, Section 6.7.5</c>
+  <c/>
+  <c>UID</c>
+  <c>RFC 6350, Section 6.7.6</c>
+  <c/>
+  <c>CLIENTPIDMAP</c>
+  <c>RFC 6350, Section 6.7.7</c>
+  <c/>
+  <c>URL</c>
+  <c>RFC 6350, Section 6.7.8</c>
+  <c/>
+  <c>VERSION</c>
+  <c>RFC 6350, Section 6.7.9</c>
+  <c/>
+  <c>KEY</c>
+  <c>RFC 6350, Section 6.8.1</c>
+  <c/>
+  <c>FBURL</c>
+  <c>RFC 6350, Section 6.9.1</c>
+  <c/>
+  <c>CALADRURI</c>
+  <c>RFC 6350, Section 6.9.2</c>
+  <c/>
+  <c>CALURI</c>
+  <c>RFC 6350, Section 6.9.3</c>
+</texttable></section>
+<section anchor="section10_3_2" title="Parameters Registry"><t>The following table has been used to initialize the parameters
+registry.</t>
+<texttable suppress-title="false" style="full">
+  <ttcol align="left">Namespace</ttcol>
+  <ttcol align="left">Parameter</ttcol>
+  <ttcol align="left">Reference</ttcol>
+  <c/>
+  <c>LANGUAGE</c>
+  <c>RFC 6350, Section 5.1</c>
+  <c/>
+  <c>VALUE</c>
+  <c>RFC 6350, Section 5.2</c>
+  <c/>
+  <c>PREF</c>
+  <c>RFC 6350, Section 5.3</c>
+  <c/>
+  <c>ALTID</c>
+  <c>RFC 6350, Section 5.4</c>
+  <c/>
+  <c>PID</c>
+  <c>RFC 6350, Section 5.5</c>
+  <c/>
+  <c>TYPE</c>
+  <c>RFC 6350, Section 5.6</c>
+  <c/>
+  <c>MEDIATYPE</c>
+  <c>RFC 6350, Section 5.7</c>
+  <c/>
+  <c>CALSCALE</c>
+  <c>RFC 6350, Section 5.8</c>
+  <c/>
+  <c>SORT-AS</c>
+  <c>RFC 6350, Section 5.9</c>
+  <c/>
+  <c>GEO</c>
+  <c>RFC 6350, Section 5.10</c>
+  <c/>
+  <c>TZ</c>
+  <c>RFC 6350, Section 5.11</c>
+</texttable></section>
+<section anchor="section10_3_3" title="Value Data Types Registry"><t>The following table has been used to initialize the parameters
+registry.</t>
+<texttable suppress-title="false" style="full">
+  <ttcol align="left">Value Data Type</ttcol>
+  <ttcol align="left">Reference</ttcol>
+  <c>BOOLEAN</c>
+  <c>RFC 6350, Section 4.4</c>
+  <c>DATE</c>
+  <c>RFC 6350, Section 4.3.1</c>
+  <c>DATE-AND-OR-TIME</c>
+  <c>RFC 6350, Section 4.3.4</c>
+  <c>DATE-TIME</c>
+  <c>RFC 6350, Section 4.3.3</c>
+  <c>FLOAT</c>
+  <c>RFC 6350, Section 4.6</c>
+  <c>INTEGER</c>
+  <c>RFC 6350, Section 4.5</c>
+  <c>LANGUAGE-TAG</c>
+  <c>RFC 6350, Section 4.8</c>
+  <c>TEXT</c>
+  <c>RFC 6350, Section 4.1</c>
+  <c>TIME</c>
+  <c>RFC 6350, Section 4.3.2</c>
+  <c>TIMESTAMP</c>
+  <c>RFC 6350, Section 4.3.5</c>
+  <c>URI</c>
+  <c>RFC 6350, Section 4.2</c>
+  <c>UTC-OFFSET</c>
+  <c>RFC 6350, Section 4.7</c>
+</texttable></section>
+<section anchor="section10_3_4" title="Values Registries"><t>Separate tables are used for property and parameter values.</t>
+<t>The following table is to be used to initialize the property values
+registry.</t>
+<texttable suppress-title="false" style="full">
+  <ttcol align="left">Property</ttcol>
+  <ttcol align="left">Value</ttcol>
+  <ttcol align="left">Reference</ttcol>
+  <c>BEGIN</c>
+  <c>VCARD</c>
+  <c>RFC 6350, Section 6.1.1</c>
+  <c>END</c>
+  <c>VCARD</c>
+  <c>RFC 6350, Section 6.1.2</c>
+  <c>KIND</c>
+  <c>individual</c>
+  <c>RFC 6350, Section 6.1.4</c>
+  <c>KIND</c>
+  <c>group</c>
+  <c>RFC 6350, Section 6.1.4</c>
+  <c>KIND</c>
+  <c>org</c>
+  <c>RFC 6350, Section 6.1.4</c>
+  <c>KIND</c>
+  <c>location</c>
+  <c>RFC 6350, Section 6.1.4</c>
+</texttable>
+<t>The following table has been used to initialize the parameter values
+registry.</t>
+<texttable suppress-title="false" style="full">
+  <ttcol align="left">Property</ttcol>
+  <ttcol align="left">Parameter</ttcol>
+  <ttcol align="left">Value</ttcol>
+  <ttcol align="left">Reference</ttcol>
+  <c>FN, NICKNAME, PHOTO,
+ ADR, TEL, EMAIL, IMPP,
+ LANG, TZ, GEO, TITLE,
+ ROLE, LOGO, ORG,
+ RELATED, CATEGORIES,
+ NOTE, SOUND, URL, KEY,
+ FBURL, CALADRURI, and
+ CALURI</c>
+  <c>TYPE</c>
+  <c>work</c>
+  <c>RFC 6350, Section 5.6</c>
+  <c>FN, NICKNAME, PHOTO,
+ ADR, TEL, EMAIL, IMPP,
+ LANG, TZ, GEO, TITLE,
+ ROLE, LOGO, ORG,
+ RELATED, CATEGORIES,
+ NOTE, SOUND, URL, KEY,
+ FBURL, CALADRURI, and
+ CALURI</c>
+  <c>TYPE</c>
+  <c>home</c>
+  <c>RFC 6350, Section 5.6</c>
+  <c>TEL</c>
+  <c>TYPE</c>
+  <c>text</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c>TEL</c>
+  <c>TYPE</c>
+  <c>voice</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c>TEL</c>
+  <c>TYPE</c>
+  <c>fax</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c>TEL</c>
+  <c>TYPE</c>
+  <c>cell</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c>TEL</c>
+  <c>TYPE</c>
+  <c>video</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c>TEL</c>
+  <c>TYPE</c>
+  <c>pager</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c>TEL</c>
+  <c>TYPE</c>
+  <c>textphone</c>
+  <c>RFC 6350, Section 6.4.1</c>
+  <c>BDAY, ANNIVERSARY</c>
+  <c>CALSCALE</c>
+  <c>gregorian</c>
+  <c>RFC 6350, Section 5.8</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>contact</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>acquaintance</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>friend</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>met</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>co-worker</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>colleague</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>co-resident</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>neighbor</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>child</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>parent</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>sibling</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>spouse</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>kin</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>muse</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>crush</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>date</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>sweetheart</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>me</c>
+  <c>RFC 6350, Section 6.6.6 and cite:norm[xfn]</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>agent</c>
+  <c>RFC 6350, Section 6.6.6</c>
+  <c>RELATED</c>
+  <c>TYPE</c>
+  <c>emergency</c>
+  <c>RFC 6350, Section 6.6.6</c>
+</texttable></section></section></section>
+<section anchor="section11" title="Acknowledgments"><t>The authors would like to thank Tim Howes, Mark Smith, and Frank
+Dawson, the original authors of cite:info[RFC2425] and cite:info[RFC2426], Pete
+Resnick, who got this effort started and provided help along the way,
+as well as the following individuals who have participated in the
+drafting, review, and discussion of this memo:</t>
+<t>Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
+Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie
+Hoeneisen, Bjoern Hoehrmann, Caleb Richardson, Chris Bryant, Chris
+Newman, Cyrus Daboo, Daisuke Miyakawa, Dan Brickley, Dan Mosedale,
+Dany Cauchie, Darryl Champagne, Dave Thewlis, Filip Navara, Florian
+Zeitz, Helge Hess, Jari Urpalainen, Javier Godoy, Jean-Luc Schellens,
+Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Julian Reschke,
+Kepeng Li, Kevin Marks, Kevin Wu Won, Kurt Zeilenga, Lisa Dusseault,
+Marc Blanchet, Mark Paterson, Markus Lorenz, Michael Haardt, Mike
+Douglass, Nick Levinson, Peter K. Sheerin, Peter Mogensen, Peter
+Saint-Andre, Renato Iannella, Rohit Khare, Sly Gryphon, Stephane
+Bortzmeyer, Tantek Celik, and Zoltan Ordogh.</t></section>
+</middle><back>
+<references title="Normative References"/>
+<references title="Informative References"/>
+<section anchor="appendixA" title="Differences from RFCs 2425 and 2426"><t>This appendix contains a high-level overview of the major changes
+that have been made in the vCard specification from RFCs 2425 and
+2426.  It is incomplete, as it only lists the most important changes.</t>
+<section anchor="appendixA_1" title="New Structure">
+  <t>
+  <list style="symbols">
+    <t>cite:info[RFC2425] and cite:info[RFC2426] have been merged.</t>
+    <t>vCard is now not only a MIME type but a stand-alone format.</t>
+    <t>A proper MIME type registration form has been included.</t>
+    <t>UTF-8 is now the only possible character set.</t>
+    <t>New vCard elements can be registered from IANA.</t>
+  </list>
+</t>
+</section>
+<section anchor="appendixA_2" title="Removed Features">
+  <t>
+  <list style="symbols">
+    <t>The CONTEXT and CHARSET parameters are no more.</t>
+    <t>The NAME, MAILER, LABEL, and CLASS properties are no more.</t>
+    <t>The "intl", "dom", "postal", and "parcel" TYPE parameter values
+for the ADR property have been removed.</t>
+    <t>In-line vCards (such as the value of the AGENT property) are no
+longer supported.</t>
+  </list>
+</t>
+</section>
+<section anchor="appendixA_3" title="New Properties and Parameters">
+  <t>
+  <list style="symbols">
+    <t>The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP
+properties have been added.</t>
+    <t>cite:norm[RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI
+properties, has been merged in.</t>
+    <t>cite:info[RFC4770], which defines the IMPP property, has been merged in.</t>
+    <t>The "work" and "home" TYPE parameter values are now applicable to
+many more properties.</t>
+    <t>The "pref" value of the TYPE parameter is now a parameter of its
+own, with a positive integer value indicating the level of
+preference.</t>
+    <t>The ALTID and PID parameters have been added.</t>
+    <t>The MEDIATYPE parameter has been added and replaces the TYPE
+parameter when it was used for indicating the media type of the
+property&#8217;s content.</t>
+  </list>
+</t>
+</section></section>
+</back>
+</rfc>