diff --git a/lib/asciidoctor/m3d/isostandard.rng b/lib/asciidoctor/m3d/isostandard.rng index dd7adf4..57fe126 100644 --- a/lib/asciidoctor/m3d/isostandard.rng +++ b/lib/asciidoctor/m3d/isostandard.rng @@ -744,6 +744,9 @@ + + + @@ -811,6 +814,11 @@ + + + + + diff --git a/lib/isodoc/m3d/html/html_m3d_titlepage.html b/lib/isodoc/m3d/html/html_m3d_titlepage.html index 21f68fa..2016edf 100644 --- a/lib/isodoc/m3d/html/html_m3d_titlepage.html +++ b/lib/isodoc/m3d/html/html_m3d_titlepage.html @@ -51,10 +51,10 @@
- {{ status }} + {% if unpublished %}{{ status }}{% endif %}
-{% if status != "Published" and status != "Withdrawn" %} +{% if unpublished %}
Warning for Drafts diff --git a/lib/isodoc/m3d/html/word_m3d_titlepage.html b/lib/isodoc/m3d/html/word_m3d_titlepage.html index 845f779..c71b18f 100644 --- a/lib/isodoc/m3d/html/word_m3d_titlepage.html +++ b/lib/isodoc/m3d/html/word_m3d_titlepage.html @@ -22,12 +22,13 @@

{{ stageabbr }} stage

+lang="EN-GB" style='font-size:40.0pt'>{% if unpublished %}{{ status }}{% endif %}

 

+{% if unpublished %}
@@ -35,24 +36,18 @@

Warning for WDs -and CDs

+lang="EN-GB" style='font-size:10.0pt;mso-bidi-font-size:11.0pt'>Warning for Drafts

This -document is not an ISO International Standard. It is distributed for review and -comment. It is subject to change without notice and may not be referred to as -an International Standard.

- -

Recipients -of this draft are invited to submit, with their comments, notification of any -relevant patent rights of which they are aware and to provide supporting -documentation.

+style='font-size:10.0pt;mso-bidi-font-size:11.0pt;mso-bidi-font-weight:bold'>This document is not an M3AAWG Standard. It is distributed for review and + comment, and is subject to change without notice and may not be referred to as + a Standard. Recipients of this draft are invited to submit, with their + comments, notification of any relevant patent rights of which they are aware + and to provide supporting documentation. +

+{% endif %} diff --git a/lib/isodoc/m3d/m3dhtmlconvert.rb b/lib/isodoc/m3d/m3dhtmlconvert.rb index e23e473..08fb82a 100644 --- a/lib/isodoc/m3d/m3dhtmlconvert.rb +++ b/lib/isodoc/m3d/m3dhtmlconvert.rb @@ -84,11 +84,6 @@ def make_body(xml, docxml) def html_toc(docxml) docxml end - - def info(isoxml, out) - @meta.url isoxml, out - super - end end end end diff --git a/lib/isodoc/m3d/m3dpdfconvert.rb b/lib/isodoc/m3d/m3dpdfconvert.rb index 2f5616d..5764b36 100644 --- a/lib/isodoc/m3d/m3dpdfconvert.rb +++ b/lib/isodoc/m3d/m3dpdfconvert.rb @@ -84,11 +84,6 @@ def make_body(xml, docxml) def html_toc(docxml) docxml end - - def info(isoxml, out) - @meta.url isoxml, out - super - end end end end diff --git a/lib/isodoc/m3d/m3dwordconvert.rb b/lib/isodoc/m3d/m3dwordconvert.rb index 073eb29..62abd2f 100644 --- a/lib/isodoc/m3d/m3dwordconvert.rb +++ b/lib/isodoc/m3d/m3dwordconvert.rb @@ -60,11 +60,6 @@ def title(isoxml, _out) main = isoxml&.at(ns("//title[@language='en']"))&.text set_metadata(:doctitle, main) end - - def info(isoxml, out) - @meta.url isoxml, out - super - end end end end diff --git a/lib/isodoc/m3d/metadata.rb b/lib/isodoc/m3d/metadata.rb index 34c6cdc..3699179 100644 --- a/lib/isodoc/m3d/metadata.rb +++ b/lib/isodoc/m3d/metadata.rb @@ -40,6 +40,10 @@ def status_abbr(status) end end + def unpublished(status) + %w(published withdrawn).include? status.downcase + end + def version(isoxml, _out) super revdate = get[:revdate] @@ -66,11 +70,6 @@ def monthyr(isodate) return isodate unless m && m[:yr] && m[:mo] return "#{MONTHS[m[:mo].to_sym]} #{m[:yr]}" end - - def url(isoxml, _out) - url = isoxml.at(ns("//bibdata/source")) - set(:url, url.text) if url - end end end end diff --git a/spec/examples/rfc6350.doc b/spec/examples/rfc6350.doc index bb9c5ba..180abf8 100644 --- a/spec/examples/rfc6350.doc +++ b/spec/examples/rfc6350.doc @@ -1,7 +1,7 @@ MIME-Version: 1.0 -Content-Type: multipart/related; boundary="----=_NextPart_637b2d6b.2e1e.4ff6" +Content-Type: multipart/related; boundary="----=_NextPart_d46a03c1.e4cb.4e5e" -------=_NextPart_637b2d6b.2e1e.4ff6 +------=_NextPart_d46a03c1.e4cb.4e5e Content-Location: file:///C:/Doc/rfc6350.htm Content-Type: text/html; charset="utf-8" @@ -1906,22 +1906,22 @@ span.note_label, span.example_label, td.example_label, td.note_label {

 TOC \o "1-2" \h \z \u -Foreword +Foreword . - PAGEREF _Toc77872970 \h + PAGEREF _Toc298697242 \h 1

-Introduction +Introduction . - PAGEREF _Toc408860809 \h + PAGEREF _Toc972912827 \h 1 @@ -1930,11 +1930,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-1. Scope +1. Scope . - PAGEREF _Toc798531347 \h + PAGEREF _Toc434894284 \h 1 @@ -1943,11 +1943,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-2. Normative references +2. Normative references . - PAGEREF _Toc174042565 \h + PAGEREF _Toc72095426 \h 1 @@ -1956,11 +1956,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-3. Terms and definitions +3. Terms and definitions . - PAGEREF _Toc210934681 \h + PAGEREF _Toc271993700 \h 1 @@ -1969,11 +1969,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-4. vCard Format Specification +4. vCard Format Specification . - PAGEREF _Toc510066018 \h + PAGEREF _Toc459844355 \h 1 @@ -1982,11 +1982,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-4.1. General +4.1. General . - PAGEREF _Toc953317095 \h + PAGEREF _Toc85229478 \h 1 @@ -1995,11 +1995,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-4.2. Charset +4.2. Charset . - PAGEREF _Toc617252609 \h + PAGEREF _Toc647298252 \h 1 @@ -2008,11 +2008,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-4.3. Line Delimiting and Folding +4.3. Line Delimiting and Folding . - PAGEREF _Toc481579269 \h + PAGEREF _Toc76878315 \h 1 @@ -2021,11 +2021,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-4.4. ABNF Format Definition +4.4. ABNF Format Definition . - PAGEREF _Toc92036068 \h + PAGEREF _Toc237887423 \h 1 @@ -2034,11 +2034,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-4.5. Property Value Escaping +4.5. Property Value Escaping . - PAGEREF _Toc704752300 \h + PAGEREF _Toc983955298 \h 1 @@ -2047,11 +2047,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5. Property Value Data Types +5. Property Value Data Types . - PAGEREF _Toc668984192 \h + PAGEREF _Toc459279831 \h 1 @@ -2060,11 +2060,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.1. General +5.1. General . - PAGEREF _Toc87257777 \h + PAGEREF _Toc74020279 \h 1 @@ -2073,11 +2073,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.2. TEXT +5.2. TEXT . - PAGEREF _Toc402489405 \h + PAGEREF _Toc271225462 \h 1 @@ -2086,11 +2086,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.3. URI +5.3. URI . - PAGEREF _Toc215350092 \h + PAGEREF _Toc739035641 \h 1 @@ -2099,11 +2099,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.4. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP +5.4. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . - PAGEREF _Toc118259832 \h + PAGEREF _Toc762240308 \h 1 @@ -2112,11 +2112,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.5. BOOLEAN +5.5. BOOLEAN . - PAGEREF _Toc381373194 \h + PAGEREF _Toc477768600 \h 1 @@ -2125,11 +2125,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.6. INTEGER +5.6. INTEGER . - PAGEREF _Toc815296608 \h + PAGEREF _Toc661531372 \h 1 @@ -2138,11 +2138,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.7. FLOAT +5.7. FLOAT . - PAGEREF _Toc24383950 \h + PAGEREF _Toc441252513 \h 1 @@ -2151,11 +2151,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.8. UTC-OFFSET +5.8. UTC-OFFSET . - PAGEREF _Toc71682424 \h + PAGEREF _Toc889440842 \h 1 @@ -2164,11 +2164,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-5.9. LANGUAGE-TAG +5.9. LANGUAGE-TAG . - PAGEREF _Toc682422138 \h + PAGEREF _Toc600273702 \h 1 @@ -2177,11 +2177,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6. Property Parameters +6. Property Parameters . - PAGEREF _Toc466052143 \h + PAGEREF _Toc397537742 \h 1 @@ -2190,11 +2190,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.1. General +6.1. General . - PAGEREF _Toc790246015 \h + PAGEREF _Toc495005071 \h 1 @@ -2203,11 +2203,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.2. LANGUAGE +6.2. LANGUAGE . - PAGEREF _Toc804233008 \h + PAGEREF _Toc741085994 \h 1 @@ -2216,11 +2216,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.3. VALUE +6.3. VALUE . - PAGEREF _Toc68853427 \h + PAGEREF _Toc434222201 \h 1 @@ -2229,11 +2229,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.4. PREF +6.4. PREF . - PAGEREF _Toc209327059 \h + PAGEREF _Toc847806514 \h 1 @@ -2242,11 +2242,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.5. ALTID +6.5. ALTID . - PAGEREF _Toc878611776 \h + PAGEREF _Toc533790506 \h 1 @@ -2255,11 +2255,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.6. PID +6.6. PID . - PAGEREF _Toc491189824 \h + PAGEREF _Toc530153611 \h 1 @@ -2268,11 +2268,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.7. TYPE +6.7. TYPE . - PAGEREF _Toc846569519 \h + PAGEREF _Toc323575282 \h 1 @@ -2281,11 +2281,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.8. MEDIATYPE +6.8. MEDIATYPE . - PAGEREF _Toc327353417 \h + PAGEREF _Toc61565932 \h 1 @@ -2294,11 +2294,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.9. CALSCALE +6.9. CALSCALE . - PAGEREF _Toc321687441 \h + PAGEREF _Toc250077729 \h 1 @@ -2307,11 +2307,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.10. SORT-AS +6.10. SORT-AS . - PAGEREF _Toc290819552 \h + PAGEREF _Toc77656315 \h 1 @@ -2320,11 +2320,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.11. GEO +6.11. GEO . - PAGEREF _Toc717829698 \h + PAGEREF _Toc637230720 \h 1 @@ -2333,11 +2333,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-6.12. TZ +6.12. TZ . - PAGEREF _Toc666708620 \h + PAGEREF _Toc662263017 \h 1 @@ -2346,11 +2346,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7. vCard Properties +7. vCard Properties . - PAGEREF _Toc635767798 \h + PAGEREF _Toc876252042 \h 1 @@ -2359,11 +2359,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.1. General +7.1. General . - PAGEREF _Toc412791553 \h + PAGEREF _Toc557916174 \h 1 @@ -2372,11 +2372,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.2. General Properties +7.2. General Properties . - PAGEREF _Toc838882591 \h + PAGEREF _Toc879759492 \h 1 @@ -2385,11 +2385,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.3. Identification Properties +7.3. Identification Properties . - PAGEREF _Toc421842569 \h + PAGEREF _Toc389513882 \h 1 @@ -2398,11 +2398,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.4. Delivery Addressing Properties +7.4. Delivery Addressing Properties . - PAGEREF _Toc514877834 \h + PAGEREF _Toc234385595 \h 1 @@ -2411,11 +2411,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.5. Communications Properties +7.5. Communications Properties . - PAGEREF _Toc106458659 \h + PAGEREF _Toc28008572 \h 1 @@ -2424,11 +2424,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.6. Geographical Properties +7.6. Geographical Properties . - PAGEREF _Toc308826062 \h + PAGEREF _Toc456085442 \h 1 @@ -2437,11 +2437,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.7. Organizational Properties +7.7. Organizational Properties . - PAGEREF _Toc444912377 \h + PAGEREF _Toc780722844 \h 1 @@ -2450,11 +2450,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.8. Explanatory Properties +7.8. Explanatory Properties . - PAGEREF _Toc208342018 \h + PAGEREF _Toc277028564 \h 1 @@ -2463,11 +2463,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.9. Security Properties +7.9. Security Properties . - PAGEREF _Toc88297609 \h + PAGEREF _Toc797726908 \h 1 @@ -2476,11 +2476,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.10. Calendar Properties +7.10. Calendar Properties . - PAGEREF _Toc378391771 \h + PAGEREF _Toc935523888 \h 1 @@ -2489,11 +2489,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-7.11. Extended Properties and Parameters +7.11. Extended Properties and Parameters . - PAGEREF _Toc270380281 \h + PAGEREF _Toc255793544 \h 1 @@ -2502,11 +2502,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-8. Synchronization +8. Synchronization . - PAGEREF _Toc55268137 \h + PAGEREF _Toc629467164 \h 1 @@ -2515,11 +2515,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-8.1. General +8.1. General . - PAGEREF _Toc19760894 \h + PAGEREF _Toc962870909 \h 1 @@ -2528,11 +2528,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-8.2. Mechanisms +8.2. Mechanisms . - PAGEREF _Toc923229106 \h + PAGEREF _Toc137262088 \h 1 @@ -2541,11 +2541,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-8.3. Example +8.3. Example . - PAGEREF _Toc537925282 \h + PAGEREF _Toc292614816 \h 1 @@ -2554,11 +2554,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-9. Example: Author’s vCard +9. Example: Author’s vCard . - PAGEREF _Toc77875889 \h + PAGEREF _Toc771596704 \h 1 @@ -2567,11 +2567,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-10. Security Considerations +10. Security Considerations . - PAGEREF _Toc870235508 \h + PAGEREF _Toc101594767 \h 1 @@ -2580,11 +2580,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-11. IANA Considerations +11. IANA Considerations . - PAGEREF _Toc741300432 \h + PAGEREF _Toc270218910 \h 1 @@ -2593,11 +2593,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-11.1. Media Type Registration +11.1. Media Type Registration . - PAGEREF _Toc867309905 \h + PAGEREF _Toc630060352 \h 1 @@ -2606,11 +2606,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-11.2. Registering New vCard Elements +11.2. Registering New vCard Elements . - PAGEREF _Toc747283062 \h + PAGEREF _Toc500858370 \h 1 @@ -2619,11 +2619,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-11.3. Initial vCard Elements Registries +11.3. Initial vCard Elements Registries . - PAGEREF _Toc947366347 \h + PAGEREF _Toc707006876 \h 1 @@ -2632,11 +2632,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-Appendix A (informative) Acknowledgments +Appendix A (informative) Acknowledgments . - PAGEREF _Toc343853568 \h + PAGEREF _Toc644332006 \h 1 @@ -2645,11 +2645,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-Appendix B (normative) Differences from RFCs 2425 and 2426 +Appendix B (normative) Differences from RFCs 2425 and 2426 . - PAGEREF _Toc131496511 \h + PAGEREF _Toc440550783 \h 1 @@ -2658,11 +2658,11 @@ span.note_label, span.example_label, td.example_label, td.note_label {

-Bibliography +Bibliography . - PAGEREF _Toc564472847 \h + PAGEREF _Toc462821413 \h 1 @@ -2681,22 +2681,22 @@ span.note_label, span.example_label, td.example_label, td.note_label {

Foreword

-

TBD

+

TBD


Introduction

-

General

Electronic address books have become ubiquitous. Their increased +

General

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.

-

A high-level overview of the differences from RFC 2425 and RFC 2426 can +

A high-level overview of the differences from RFC 2425 and RFC 2426 can be found in Appendix B.

Conventions

-

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", +

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

@@ -2709,7 +2709,7 @@ be found in Appendix B.

vCard Format Specification

1.  Scope

-

This document defines the vCard data format for representing and +

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 @@ -2748,89 +2748,89 @@ updates RFC 2739.

4.  vCard Format Specification

4.1. General

-

The text/vcard MIME content type (hereafter known as "vCard"; see +

The text/vcard MIME content type (hereafter known as "vCard"; see Clause 11.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.

4.2. Charset

-

The charset (see RFC 3536 for internationalization terminology) for +

The charset (see RFC 3536 for internationalization terminology) for vCard is UTF-8 as defined in RFC 3629. There is no way to override this. It is invalid to specify a value other than "UTF-8" in the "charset" MIME parameter (see Clause 11.1).

-

4.3. Line Delimiting and Folding

Individual lines within vCard are delimited by the RFC 5322 line +

4.3. Line Delimiting and Folding

Individual lines within vCard are delimited by the RFC 5322 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 SHOULD be folded to a maximum width of 75 octets, excluding the line break. Multi-octet characters MUST remain contiguous. The rationale for this folding process can be found in RFC 5322, Section 2.1.1.

-

A logical line MAY be continued on the next physical line anywhere +

A logical line MAY 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 MUST 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:

-
+
  NOTE:This is a long description that exists on a long line.
-

can be represented as:

-
+

can be represented as:

+
  NOTE:This is a long description
     that exists on a long line.
-

It could also be represented as:

-
+

It could also be represented as:

+
  NOTE:This is a long descrip
    tion that exists o
    n a long line.
-

The process of moving from this folded multiple-line representation +

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).

-

Note: It is possible for very simple implementations to generate +

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 SHOULD unfold lines in such a way as to properly restore the original sequence.

-

Note: Unfolding is done differently than in RFC 5322. Unfolding +

Note: Unfolding is done differently than in RFC 5322. Unfolding in RFC 5322 only removes the CRLF, not the space following it.

-

Folding is done after any content encoding of a type value. +

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.

-

4.4. ABNF Format Definition

The following ABNF uses the notation of RFC 5234, which also defines +

4.4. ABNF Format Definition

The following ABNF uses the notation of RFC 5234, which also defines CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.

-

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 IETF RFC 3629

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

-

A line that begins with a white space character is a continuation of +

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 IETF RFC 3629

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

+

A line that begins with a white space character is a continuation of the previous line, as described in Clause 4.3. 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 RFC 5322, in that the sequence <CRLF><WSP> found anywhere in the content indicates a continued line and should be removed.

-

Property names and parameter names are case-insensitive (e.g., the +

Property names and parameter names are case-insensitive (e.g., the property name "fn" is the same as "FN" and "Fn"). Parameter values MAY 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 RECOMMENDED that property and parameter names be upper-case on output.

-

The group construct is used to group related properties together. +

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 SHOULD be grouped together when displayed by an application. It has no other significance. Implementations that do not understand or support grouping MAY simply strip off any text before a "." to the left of the type name and present the types and values as normal.

-

Property cardinalities are indicated using the following notation, +

Property cardinalities are indicated using the following notation, which is based on ABNF (see RFC 5234, Section 3.6):

-

Table 1

CardinalityMeaning
1Exactly one instance per vCard MUST be present.
*1Exactly one instance per vCard MAY be present.
1*One or more instances per vCard MUST be present.
*One or more instances per vCard MAY be present.
-

Properties defined in a vCard instance may have multiple values +

Table 1

CardinalityMeaning
1Exactly one instance per vCard MUST be present.
*1Exactly one instance per vCard MAY be present.
1*One or more instances per vCard MUST be present.
*One or more instances per vCard MAY be present.
+

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 @@ -2838,84 +2838,84 @@ 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).

-

4.5. Property Value Escaping

Some properties may contain one or more values delimited by a COMMA +

4.5. Property Value Escaping

Some properties may contain one or more values delimited by a COMMA character (U+002C). Therefore, a COMMA character in a value MUST be escaped with a BACKSLASH character (U+005C), even for properties that don’t allow multiple instances (for consistency).

-

Some properties (e.g., N and ADR) comprise multiple fields delimited +

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 MUST be escaped with a BACKSLASH character. SEMICOLON characters in non-compound properties MAY 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.

-

Furthermore, some fields of compound properties may contain a list of +

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’s values MUST be escaped with a BACKSLASH character, even for fields that don’t allow multiple values (for consistency). Compound properties allowing multiple instances MUST NOT be encoded in a single content line.

-

Finally, BACKSLASH characters in values MUST be escaped with a +

Finally, BACKSLASH characters in values MUST be escaped with a BACKSLASH character. NEWLINE (U+000A) characters in values MUST be encoded by two characters: a BACKSLASH followed by either an 'n' (U+006E) or an 'N' (U+004E).

-

In all other cases, escaping MUST NOT be used.

+

In all other cases, escaping MUST NOT be used.

5.  Property Value Data Types

-

5.1. General

Standard value types are defined below.

-

  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 IETF RFC 3986
        / 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 IETF RFC 5646, 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.

-

5.2. TEXT

"text": The "text" value type should be used to identify values that +

5.1. General

Standard value types are defined below.

+

  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 IETF RFC 3986
        / 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 IETF RFC 5646, 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.

+

5.2. TEXT

"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 Clause 6.2.

-

Examples for "text":

-
+

Examples for "text":

+
    this is a text value
     this is one value,this is another
     this is a single value\, with a comma encoded
-

A formatted text line break in a text value type MUST be represented +

A formatted text line break in a text value type MUST 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".

-

For example, a multiple line NOTE value of:

-
+

For example, a multiple line NOTE value of:

+
    Mythical Manager
     Hyjinx Software Division
     BabsCo, Inc.
-

could be represented as:

-
+

could be represented as:

+
    NOTE:Mythical Manager\nHyjinx Software Division\n
      BabsCo\, Inc.\n
-

demonstrating the \n literal formatted line break technique, the +

demonstrating the \n literal formatted line break technique, the CRLF-followed-by-space line folding technique, and the backslash escape technique.

-

5.3. URI

"uri": The "uri" value type should be used to identify values that +

5.3. URI

"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 RFC 3986, Section 3. Note that the value of a property of type "uri" is what the URI points to, not the URI itself.

-

Examples for "uri":

-
+

Examples for "uri":

+
    http://www.example.com/my/picture.jpg
     ldap://ldap.example.com/cn=babs%20jensen
-

5.4. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP

5.4.1. General

"date", "time", "date-time", "date-and-or-time", and "timestamp": +

5.4. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP

5.4.1. General

"date", "time", "date-time", "date-and-or-time", and "timestamp": Each of these value types is based on the definitions in ISO 8601:2004. Multiple such values can be specified using the comma-separated notation.

-

Only the basic format is supported.

-

5.4.2. DATE

A calendar date as specified in ISO 8601:2004, Clause 4.1.2].

-

Reduced accuracy, as specified in ISO 8601:2004, Clause 4.1.2.3 a) +

Only the basic format is supported.

+

5.4.2. DATE

A calendar date as specified in ISO 8601:2004, Clause 4.1.2].

+

Reduced accuracy, as specified in ISO 8601:2004, Clause 4.1.2.3 a) and b), but not c), is permitted.

-

Expanded representation, as specified in ISO 8601:2004, Clause 4.1.4, is forbidden.

-

Truncated representation, as specified in ISO 8601:2004, Clause 5.2.1.3 d), e), and f), is permitted.

-

Examples for "date":

-
+

Expanded representation, as specified in ISO 8601:2004, Clause 4.1.4, is forbidden.

+

Truncated representation, as specified in ISO 8601:2004, Clause 5.2.1.3 d), e), and f), is permitted.

+

Examples for "date":

+
          19850412
           1985-04
           1985
@@ -2925,20 +2925,20 @@ and b), but not c), is permitted.
-

Note the use of YYYY-MM in the second example above. YYYYMM is +

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.

-

5.4.3. TIME

A time of day as specified in ISO 8601:2004, Clause 4.2.

-

Reduced accuracy, as specified in ISO 8601:2004, Clause 4.2.2.3, +

5.4.3. TIME

A time of day as specified in ISO 8601:2004, Clause 4.2.

+

Reduced accuracy, as specified in ISO 8601:2004, Clause 4.2.2.3, is permitted.

-

Representation with decimal fraction, as specified in +

Representation with decimal fraction, as specified in ISO 8601:2004, Clause 4.2.2.4, is forbidden.

-

The midnight hour is always represented by 00, never 24 (see +

The midnight hour is always represented by 00, never 24 (see ISO 8601:2004, Clause 4.2.3).

-

Truncated representation, as specified in ISO 8601:2000, Clause 5.3.1.4 a), b), and c), is permitted.

-

Examples for "time":

-
+

Truncated representation, as specified in ISO 8601:2000, Clause 5.3.1.4 a), b), and c), is permitted.

+

Examples for "time":

+
          102200
           1022
           10
@@ -2947,18 +2947,18 @@ is permitted.

           102200Z
           102200-0800
-

5.4.4. DATE-TIME

A date and time of day combination as specified in ISO 8601:2004, Clause 4.3.

-

Truncation of the date part, as specified in ISO 8601:2000, Clause 5.4.2 c), is permitted.

-

Examples for "date-time":

-
+

5.4.4. DATE-TIME

A date and time of day combination as specified in ISO 8601:2004, Clause 4.3.

+

Truncation of the date part, as specified in ISO 8601:2000, Clause 5.4.2 c), is permitted.

+

Examples for "date-time":

+
          19961022T140000
           --1022T1400
           ---22T14
-

5.4.5. DATE-AND-OR-TIME

Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous +

5.4.5. DATE-AND-OR-TIME

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".

-

Examples for "date-and-or-time":

-
+

Examples for "date-and-or-time":

+
          19961022T140000
           --1022T1400
           ---22T14
@@ -2975,24 +2975,24 @@ interpretation, a stand-alone TIME value is always preceded by a "T".

           T102200Z
           T102200-0800
-

5.4.6. TIMESTAMP

A complete date and time of day combination as specified in +

5.4.6. TIMESTAMP

A complete date and time of day combination as specified in ISO 8601:2004, Clause 4.3.2.

-

Examples for "timestamp":

-
+

Examples for "timestamp":

+
          19961022T140000
           19961022T140000Z
           19961022T140000-05
           19961022T140000-0500
-

5.5. BOOLEAN

"boolean": The "boolean" value type is used to express boolean +

5.5. BOOLEAN

"boolean": The "boolean" value type is used to express boolean values. These values are case-insensitive.

Examples:

-
+
    TRUE
     false
     True
-

5.6. INTEGER

"integer": The "integer" value type is used to express signed +

5.6. INTEGER

"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 @@ -3000,28 +3000,28 @@ using the comma-separated notation. The maximum value is These limits correspond to a signed 64-bit integer using two’s- complement arithmetic.

Examples:

-
+
    1234567890
     -1234556790
     +1234556790,432109876
-

5.7. FLOAT

"float": The "float" value type is used to express real numbers. If +

5.7. FLOAT

"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 MUST support a precision equal or better than that of the IEEE "binary64" format IEEE 754.

-

Note: Scientific notation is disallowed. Implementers wishing to +

Note: Scientific notation is disallowed. Implementers wishing to use their favorite language’s %f formatting should be careful.

Examples:

-
+
    20.30
     1000000.0000001
     1.333,3.14
-

5.8. UTC-OFFSET

"utc-offset": The "utc-offset" value type specifies that the property +

5.8. UTC-OFFSET

"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.

-

The value type is an offset from Coordinated Universal Time (UTC). +

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 @@ -3030,36 +3030,36 @@ to maintain digit count. The basic format for ISO 8601 UTC offsets MUST be used.

5.9. LANGUAGE-TAG

-

"language-tag": A single language tag, as defined in RFC 5646.

+

"language-tag": A single language tag, as defined in RFC 5646.

6.  Property Parameters

-

6.1. General

A property can have attributes associated with it. These "property +

6.1. General

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).

-

Property parameter value elements that contain the COLON (U+003A), +

Property parameter value elements that contain the COLON (U+003A), SEMICOLON (U+003B), or COMMA (U+002C) character separators MUST be specified as quoted-string text values. Property parameter values MUST NOT contain the DQUOTE (U+0022) character. The DQUOTE character is used as a delimiter for parameter values that contain restricted characters or URI text.

-

Applications MUST ignore x-param and iana-param values they don’t +

Applications MUST ignore x-param and iana-param values they don’t recognize.

-

6.2. LANGUAGE

The LANGUAGE property parameter is used to identify data in multiple +

6.2. LANGUAGE

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 RFC 3282. The value of the LANGUAGE property parameter is a language tag as defined in RFC 5646, Section 2.

Examples:

-
+
  ROLE;LANGUAGE=tr:hoca

ABNF:

-

        language-param = "LANGUAGE=" Language-Tag
          ; Language-Tag is defined in section 2.1 of IETF RFC 5646

-

6.3. VALUE

The VALUE parameter is OPTIONAL, used to identify the value type +

        language-param = "LANGUAGE=" Language-Tag
          ; Language-Tag is defined in section 2.1 of IETF RFC 5646

+

6.3. VALUE

The VALUE parameter is OPTIONAL, 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, @@ -3068,83 +3068,83 @@ predefined data type values MUST NOT be repeated in value lists except within the N, NICKNAME, ADR, and CATEGORIES properties.

ABNF:

-

  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

-

6.4. PREF

The PREF parameter is OPTIONAL and is used to indicate that the +

  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

+

6.4. PREF

The PREF parameter is OPTIONAL and is used to indicate that the corresponding instance of a property is preferred by the vCard author. Its value MUST 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.

-

When the parameter is absent, the default MUST be to interpret the +

When the parameter is absent, the default MUST be to interpret the property instance as being least preferred.

-

Note that the value of this parameter is to be interpreted only in +

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, MUST NOT be interpreted on its own.

-

This parameter MAY be applied to any property that allows multiple +

This parameter MAY be applied to any property that allows multiple instances.

ABNF:

-

        pref-param = "PREF=" (1*2DIGIT / "100")
                             ; An integer between 1 and 100.

-

6.5. ALTID

The ALTID parameter is used to "tag" property instances as being +

        pref-param = "PREF=" (1*2DIGIT / "100")
                             ; An integer between 1 and 100.

+

6.5. ALTID

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 (Clause 6.2) parameter that are tagged with the same ALTID value.

-

This parameter’s value is treated as an opaque string. Its sole +

This parameter’s value is treated as an opaque string. Its sole purpose is to be compared for equality against other ALTID parameter values.

-

Two property instances are considered alternative representations of +

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 MUST NOT be considered an alternative representation of any other property instance. Values for the ALTID parameter are not globally unique: they MAY be reused for different property names.

-

Property instances having the same ALTID parameter value count as 1 +

Property instances having the same ALTID parameter value count as 1 toward cardinality. Therefore, since N (Clause 7.3.3) has cardinality *1 and TITLE (Clause 7.7.2) has cardinality *, these three examples would be legal:

-
+
  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.)
-
+
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE;ALTID=1;LANGUAGE=en:Boss
-
+
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE;ALTID=1;LANGUAGE=en:Boss
   TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
-

while this one would not:

-
+

while this one would not:

+
  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
   N:Yamada;Taro;;;
   (Two instances of the N property.)
-

and these three would be legal but questionable:

-
+

and these three would be legal but questionable:

+
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE;ALTID=2;LANGUAGE=en:Boss
   (Should probably have the same ALTID value.)
-
+
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE:LANGUAGE=en:Boss
   (Second line should probably have ALTID=1.)
-
+
  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.)
-

The ALTID property MAY also be used in may contexts other than with +

The ALTID property MAY also be used in may contexts other than with the LANGUAGE parameter. Here’s an example with two representations of the same photo in different file formats:

-
+
  PHOTO;ALTID=1:data:image/jpeg;base64,...
   PHOTO;ALTID=1;data:image/jp2;base64,...
 
@@ -3152,8 +3152,8 @@ of the same photo in different file formats:

ABNF:

-

        altid-param = "ALTID=" param-value

-

6.6. PID

The PID parameter is used to identify a specific property among +

        altid-param = "ALTID=" param-value

+

6.6. PID

The PID parameter is used to identify a specific property among multiple instances. It plays a role analogous to the UID property (Clause 7.8.7) on a per-property instead of per-vCard basis. It MAY appear more than once in a given property. It MUST NOT appear on @@ -3163,8 +3163,8 @@ integers separated by a dot. Multiple values may be encoded in a single PID parameter by separating the values with a comma ",". See Clause 8 for more details on its usage.

ABNF:

-

        pid-param = "PID=" pid-value *("," pid-value)
        pid-value = 1*DIGIT ["." 1*DIGIT]

-

6.7. TYPE

The TYPE parameter has multiple, different uses. In general, it is a +

        pid-param = "PID=" pid-value *("," pid-value)
        pid-value = 1*DIGIT ["." 1*DIGIT]

+

6.7. TYPE

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 @@ -3173,7 +3173,7 @@ IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES, NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI. The TYPE parameter MUST NOT be applied on other properties defined in this document.

-

The "work" and "home" values act like tags. The "work" value implies +

The "work" and "home" values act like tags. The "work" value implies that the property is related to an individual’s work place, while the "home" value implies that the property is related to an individual’s personal life. When neither "work" nor "home" is present, it is @@ -3181,8 +3181,8 @@ implied that the property is related to both an individual’s work place and personal life in the case that the KIND property’s value is "individual", or to none in other cases.

ABNF:

-

       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.

-

6.8. MEDIATYPE

The MEDIATYPE parameter is used with properties whose value is a URI. +

       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.

+

6.8. MEDIATYPE

The MEDIATYPE parameter is used with properties whose value is a URI. Its use is OPTIONAL. It provides a hint to the vCard consumer application about the media type RFC 2046 of the resource identified by the URI. Some URI schemes do not need this parameter. For @@ -3193,8 +3193,8 @@ the Content-Type HTTP header RFC 2616. The MEDIATYPE par intended to be used with URI schemes that do not provide such functionality (e.g., "ftp" RFC 1738).

ABNF:

-

  mediatype-param = "MEDIATYPE=" mediatype
  mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
    ; "attribute" and "value" are from IETF RFC 2045
    ; "type-name" and "subtype-name" are from [RFC4288]

-

6.9. CALSCALE

The CALSCALE parameter is identical to the CALSCALE property in +

  mediatype-param = "MEDIATYPE=" mediatype
  mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
    ; "attribute" and "value" are from IETF RFC 2045
    ; "type-name" and "subtype-name" are from [RFC4288]

+

6.9. CALSCALE

The CALSCALE parameter is identical to the CALSCALE property in iCalendar (see RFC 5545, 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 @@ -3204,46 +3204,46 @@ registered with IANA (see Clause 11.3.5). A vCard MUST ignore properties with a CALSCALE parameter value that it does not understand.

ABNF:

-

        calscale-param = "CALSCALE=" calscale-value

        calscale-value = "gregorian" / iana-token / x-name

-

6.10. SORT-AS

The "sort-as" parameter is used to specify the string to be used for +

        calscale-param = "CALSCALE=" calscale-value

        calscale-value = "gregorian" / iana-token / x-name

+

6.10. SORT-AS

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.

-

This parameter’s value is a comma-separated list that MUST have as +

This parameter’s value is a comma-separated list that MUST have as many or fewer elements as the corresponding property value has components. This parameter’s value is case-sensitive.

ABNF:

-

  sort-as-param = "SORT-AS=" sort-as-value

  sort-as-value = param-value *("," param-value)

-

Examples: For the case of surname and given name sorting, the +

  sort-as-param = "SORT-AS=" sort-as-value

  sort-as-value = param-value *("," param-value)

+

Examples: For the case of surname and given name sorting, the following examples define common sort string usage with the N property.

-
+
        FN:Rene van der Harten
         N;SORT-AS="Harten,Rene":van der Harten;Rene,J.;Sir;R.D.O.N.
-
+
        FN:Robert Pau Shou Chang
         N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;
-
+
        FN:Osamu Koura
         N;SORT-AS="Koura,Osamu":Koura;Osamu;;
-
+
        FN:Oscar del Pozo
         N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;
-
+
        FN:Chistine d'Aboville
         N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;
-
+
        FN:H. James de Mann
         N;SORT-AS="Mann,James":de Mann;Henry,James;;
-

If sorted by surname, the results would be:

-
+

If sorted by surname, the results would be:

+
        Christine d'Aboville
         Rene van der Harten
         Osamu Koura
@@ -3251,8 +3251,8 @@ property.

         Robert Pau Shou Chang
         Oscar del Pozo
-

If sorted by given name, the results would be:

-
+

If sorted by given name, the results would be:

+
        Christine d'Aboville
         H. James de Mann
         Osamu Koura
@@ -3260,36 +3260,36 @@ property.

         Rene van der Harten
         Robert Pau Shou Chang
-

6.11. GEO

The GEO parameter can be used to indicate global positioning +

6.11. GEO

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 Clause 7.6.3).

ABNF:

-

  geo-parameter = "GEO=" DQUOTE URI DQUOTE

-

6.12. TZ

The TZ parameter can be used to indicate time zone information that +

  geo-parameter = "GEO=" DQUOTE URI DQUOTE

+

6.12. TZ

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.

ABNF:

-

  tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)

+

  tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)

7.  vCard Properties

7.1. General

-

What follows is an enumeration of the standard vCard properties.

+

What follows is an enumeration of the standard vCard properties.

7.2. General Properties

7.2.1. BEGIN

Purpose:

-

To denote the beginning of a syntactic entity within a +

To denote the beginning of a syntactic entity within a text/vcard content-type.

Value type:

-

text

+

text

Cardinality:

-

1

+

1

Special notes:

-

The content entity MUST begin with the BEGIN property +

The content entity MUST begin with the BEGIN property with a value of "VCARD". The value is case-insensitive.

-

The BEGIN property is used in conjunction with the END property to +

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/ @@ -3298,24 +3298,24 @@ with a value of "VCARD". The value is case-insensitive.

the same text/vcard content-type or to define content that can be identifiable outside of a MIME environment.

ABNF:

-

  BEGIN-param = 0" "  ; no parameter allowed
  BEGIN-value = "VCARD"

+

  BEGIN-param = 0" "  ; no parameter allowed
  BEGIN-value = "VCARD"

Example:

-
+ 
      BEGIN:VCARD

7.2.2. END

Purpose:

-

To denote the end of a syntactic entity within a text/vcard +

To denote the end of a syntactic entity within a text/vcard content-type.

Value type:

-

text

+

text

Cardinality:

-

1

+

1

Special notes:

-

The content entity MUST end with the END type with a +

The content entity MUST end with the END type with a value of "VCARD". The value is case-insensitive.

-

The END property is used in conjunction with the BEGIN property to +

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 @@ -3324,22 +3324,22 @@ value of "VCARD". The value is case-insensitive.

the same text/vcard content-type or to define content that can be identifiable outside of a MIME environment.

ABNF:

-

  END-param = 0" "  ; no parameter allowed
  END-value = "VCARD"

+

  END-param = 0" "  ; no parameter allowed
  END-value = "VCARD"

Example:

-
+
      END:VCARD

7.2.3. SOURCE

Purpose:

-

To identify the source of directory information contained +

To identify the source of directory information contained in the content type.

Value type:

-

uri

+

uri

Cardinality:

-

*

+

*

Special notes:

-

The SOURCE property is used to provide the means by +

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 RFC 3986 @@ -3349,28 +3349,28 @@ from more than one source, the sending entity can pick what it considers to be the best source, or multiple SOURCE properties can be included.

ABNF:

-

  SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  SOURCE-value = URI

-

Examples:

+

  SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  SOURCE-value = URI

+

Examples: 

  SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
-
+
  SOURCE:http://directory.example.com/addressbooks/jdoe/
    Jean%20Dupont.vcf

7.2.4. KIND

Purpose:

-

To specify the kind of object the vCard represents.

+

To specify the kind of object the vCard represents.

Value type:

-

A single text value.

+

A single text value.

Cardinality:

-

*1

+

*1

Special notes:

-

The value may be one of the following:

+

The value may be one of the following:

"individual"

-

for a vCard representing a single person or entity. +

for a vCard representing a single person or entity. This is the default kind of vCard.

"group"

-

for a vCard representing a group of persons or entities. +

for a vCard representing a group of persons or entities. The group’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 @@ -3378,46 +3378,46 @@ 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").

-

All properties in a group vCard apply to the group as a whole, +

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.

"org"

-

for a vCard representing an organization. An organization +

for a vCard representing an organization. An organization vCard will not (in fact, MUST NOT) 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.

-

All properties in an organization vCard apply to the +

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.

"location"

-

for a named geographical place. A location vCard will +

for a named geographical place. A location vCard will usually contain a GEO property, but it is not required to. A location vCard without a GEO property can be considered an abstract location, or one whose definition is known empirically (perhaps "New England" or "The Seashore").

-

All properties in a location vCard apply to the location +

All properties in a location vCard apply to the location itself, and not with any entity that might exist at that location. For example, in a vCard for an office building, an ADR property might give the mailing address for the building, and a TEL property might specify the telephone number of the receptionist.

An x-name.

-

vCards MAY include private or experimental values for +

vCards MAY include private or experimental values for KIND. Remember that x-name values are not intended for general use and are unlikely to interoperate.

An iana-token.

-

Additional values may be registered with IANA (see +

Additional values may be registered with IANA (see Clause 11.3.5). A new value’s specification document MUST specify which properties make sense for that new kind of vCard and which do not.

-

Implementations MUST support the specific string values defined +

Implementations MUST support the specific string values defined above. If this property is absent, "individual" MUST be assumed as the default. If this property is present but the implementation does not understand its value (the value is an @@ -3426,7 +3426,7 @@ and which do not.

means treating the vCard as though its kind were "individual". The presence of MEMBER properties MAY, however, be taken as an indication that the unknown kind is an extension of "group".

-

Clients often need to visually distinguish contacts based on what +

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 @@ -3436,10 +3436,10 @@ and which do not.

addition, a client might choose to segregate different kinds of vCards to different panes, tabs, or selections in the user interface.

-

Some clients might also make functional distinctions among the +

Some clients might also make functional distinctions among the kinds, ignoring "location" vCards for some purposes and considering only "location" vCards for others.

-

When designing those sorts of visual and functional distinctions, +

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? @@ -3447,10 +3447,10 @@ and which do not.

specification to answer these questions, but these are things implementers need to consider.

ABNF:

-

  KIND-param = "VALUE=text" / any-param
  KIND-value = "individual" / "group" / "org" / "location"
             / iana-token / x-name

-

Example:

This represents someone named Jane Doe working in the marketing +

  KIND-param = "VALUE=text" / any-param
  KIND-value = "individual" / "group" / "org" / "location"
             / iana-token / x-name

+

Example:

This represents someone named Jane Doe working in the marketing department of the North American division of ABC Inc.

-
+
      BEGIN:VCARD
       VERSION:4.0
       KIND:individual
@@ -3458,9 +3458,9 @@ and which do not.

       ORG:ABC\, Inc.;North American Division;Marketing
       END:VCARD
-

This represents the department itself, commonly known as ABC +

This represents the department itself, commonly known as ABC Marketing.

-
+
      BEGIN:VCARD
       VERSION:4.0
       KIND:org
@@ -3471,51 +3471,51 @@ Marketing.

 
7.2.5. XML

 
   
Purpose: 

-    
To include extended XML-encoded vCard data in a plain
+    
To include extended XML-encoded vCard data in a plain
 vCard.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

-  
Special notes: 
The content of this property is a single XML 1.0
+    
*

+  
Special notes: 
The content of this property is a single XML 1.0
 W3C REC-xml-20081126 element whose namespace MUST be explicitly
 specified using the xmlns attribute and MUST NOT be the vCard 4
 namespace ("urn:ietf:params:xml:ns:vcard-4.0").  (This implies
 that it cannot duplicate a standard vCard property.)  The element
 is to be interpreted as if it was contained in a <vcard> element,
-as defined in RFC 6351.
The fragment is subject to normal line folding and escaping, i.e.,
+as defined in RFC 6351.
The fragment is subject to normal line folding and escaping, i.e.,
    replace all backslashes with "\\", then replace all newlines with
    "\n", then fold long lines.

-
Support for this property is OPTIONAL, but implementations of this
+
Support for this property is OPTIONAL, but implementations of this
    specification MUST preserve instances of this property when
    propagating vCards.

-
See RFC 6351 for more information on the intended use of this
+
See RFC 6351 for more information on the intended use of this
    property.
ABNF: 

-    
  XML-param = "VALUE=text" / altid-param
  XML-value = text

+    
  XML-param = "VALUE=text" / altid-param
  XML-value = text

7.3. Identification Properties

7.3.1. General

-

These types are used to capture information associated with the +

These types are used to capture information associated with the identification and naming of the entity associated with the vCard.

7.3.2. FN

Purpose:

-

To specify the formatted text corresponding to the name of +

To specify the formatted text corresponding to the name of the object the vCard represents.

Value type:

-

A single text value.

+

A single text value.

Cardinality:

-

1*

+

1*

Special notes:

-

This property is based on the semantics of the X.520 +

This property is based on the semantics of the X.520 Common Name attribute CCITT Recommendation X520. The property MUST be present in the vCard object.

ABNF:

-

  FN-param = "VALUE=text" / type-param / language-param / altid-param
           / pid-param / pref-param / any-param
  FN-value = text

+

  FN-param = "VALUE=text" / type-param / language-param / altid-param
           / pid-param / pref-param / any-param
  FN-value = text

Example:

-
+ 
      FN:Mr. John Q. Public\, Esq.
@@ -3523,15 +3523,15 @@ present in the vCard object.

7.3.3. N

Purpose:

-

To specify the components of the name of the object the +

To specify the components of the name of the object the vCard represents.

Value type:

-

A single structured text value. Each component can have +

A single structured text value. Each component can have multiple values.

Cardinality:

-

*1

+

*1

Special note:

-

The structured property value corresponds, in +

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 @@ -3541,11 +3541,11 @@ This property is based on the semantics of the X.520 individual name attributes CCITT Recommendation X520. The property SHOULD be present in the vCard object when the name of the object the vCard represents follows the X.520 model.

-

The SORT-AS parameter MAY be applied to this property.

+

The SORT-AS parameter MAY be applied to this property.

ABNF:

-

  N-param = "VALUE=text" / sort-as-param / language-param
          / altid-param / any-param
  N-value = list-component 4(";" list-component)

+

  N-param = "VALUE=text" / sort-as-param / language-param
          / altid-param / any-param
  N-value = list-component 4(";" list-component)

Examples:

-
+ 
          N:Public;John;Quinlan;Mr.;Esq.
 
           N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
@@ -3555,22 +3555,22 @@ represents follows the X.520 model.

7.3.4. NICKNAME

Purpose:

-

To specify the text corresponding to the nickname of the +

To specify the text corresponding to the nickname of the object the vCard represents.

Value type:

-

One or more text values separated by a COMMA character +

One or more text values separated by a COMMA character (U+002C).

Cardinality:

-

*

+

*

Special note:

-

The nickname is the descriptive name given instead of +

The nickname is the descriptive name given instead of or in addition to the one belonging to the object the vCard represents. It can also be used to specify a familiar form of a proper name specified by the FN or N properties.

ABNF:

-

  NICKNAME-param = "VALUE=text" / type-param / language-param
                 / altid-param / pid-param / pref-param / any-param
  NICKNAME-value = text-list

+

  NICKNAME-param = "VALUE=text" / type-param / language-param
                 / altid-param / pid-param / pref-param / any-param
  NICKNAME-value = text-list

Examples:

-
+ 
          NICKNAME:Robbie
 
           NICKNAME:Jim,Jimmie
@@ -3582,16 +3582,16 @@ proper name specified by the FN or N properties.

 
7.3.5. PHOTO

 
   
Purpose: 

-    
To specify an image or photograph information that
+    
To specify an image or photograph information that
 annotates some aspect of the object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  PHOTO-param = "VALUE=uri" / altid-param / type-param
              / mediatype-param / pref-param / pid-param / any-param
  PHOTO-value = URI

+    
  PHOTO-param = "VALUE=uri" / altid-param / type-param
              / mediatype-param / pref-param / pid-param / any-param
  PHOTO-value = URI

   
Examples: 

-    

+    

   
    PHOTO:http://www.example.com/pub/photos/jqpublic.gif
 
     PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
@@ -3604,17 +3604,17 @@ annotates some aspect of the object the vCard represents.

 
7.3.6. BDAY

 
   
Purpose: 

-    
To specify the birth date of the object the vCard
+    
To specify the birth date of the object the vCard
 represents.

   
Value type: 

-    
The default is a single date-and-or-time value.  It can
+    
The default is a single date-and-or-time value.  It can
 also be reset to a single text value.

   
Cardinality: 

-    
*1

+    
*1

   
ABNF: 

-    
  BDAY-param = BDAY-param-date / BDAY-param-text
  BDAY-value = date-and-or-time / text
    ; Value and parameter MUST match.

  BDAY-param-date = "VALUE=date-and-or-time"
  BDAY-param-text = "VALUE=text" / language-param

  BDAY-param =/ altid-param / calscale-param / any-param
    ; calscale-param can only be present when BDAY-value is
    ; date-and-or-time and actually contains a date or date-time.

+    
  BDAY-param = BDAY-param-date / BDAY-param-text
  BDAY-value = date-and-or-time / text
    ; Value and parameter MUST match.

  BDAY-param-date = "VALUE=date-and-or-time"
  BDAY-param-text = "VALUE=text" / language-param

  BDAY-param =/ altid-param / calscale-param / any-param
    ; calscale-param can only be present when BDAY-value is
    ; date-and-or-time and actually contains a date or date-time.

   
Examples: 

-    

+    

   
          BDAY:19960415
           BDAY:--0415
           BDAY;19531015T231000Z
@@ -3625,17 +3625,17 @@ also be reset to a single text value.

 
7.3.7. ANNIVERSARY

 
   
Purpose: 

-    
The date of marriage, or equivalent, of the object the
+    
The date of marriage, or equivalent, of the object the
 vCard represents.

   
Value type: 

-    
The default is a single date-and-or-time value.  It can
+    
The default is a single date-and-or-time value.  It can
 also be reset to a single text value.

   
Cardinality: 

-    
*1

+    
*1

   
ABNF: 

-    
  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.

+    
  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.

   
Examples: 

-    

+    

   
          ANNIVERSARY:19960415

 

   

@@ -3643,27 +3643,27 @@ also be reset to a single text value.

 
7.3.8. GENDER

 
   
Purpose: 

-    
To specify the components of the sex and gender identity of
+    
To specify the components of the sex and gender identity of
 the object the vCard represents.

   
Value type: 

-    
A single structured value with two components.  Each
+    
A single structured value with two components.  Each
 component has a single text value.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
The components correspond, in sequence, to the sex
+    
The components correspond, in sequence, to the sex
 (biological), and gender identity.  Each component is optional.

     
Sex component: 

-    
A single letter.  M stands for "male", F stands
+    
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".

   
Gender identity component: 

-    
Free-form text.

+    
Free-form text.

   

   
ABNF: 

-    
                GENDER-param = "VALUE=text" / any-param
                GENDER-value = sex [";" text]

                sex = "" / "M" / "F" / "O" / "N" / "U"

+    
                GENDER-param = "VALUE=text" / any-param
                GENDER-value = sex [";" text]

                sex = "" / "M" / "F" / "O" / "N" / "U"

   
Examples: 

-    

+    

   
  GENDER:M
   GENDER:F
   GENDER:M;Fellow
@@ -3675,19 +3675,19 @@ applicable", U stands for "unknown".

 

         
7.4. Delivery Addressing Properties
7.4.1. General

 
-  
These types are concerned with information related to the delivery
+  
These types are concerned with information related to the delivery
 addressing or label for the vCard object.

 

 
7.4.2. ADR
Purpose: 

-    
To specify the components of the delivery address for the
+    
To specify the components of the delivery address for the
 vCard object.

   
Value type: 

-    
A single structured text value, separated by the
+    
A single structured text value, separated by the
 SEMICOLON character (U+003B).

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The structured type value consists of a sequence of
+    
The structured type value consists of a sequence of
 address components.  The component values MUST be specified in
 their corresponding position.  The structured type value
 corresponds, in sequence, to

@@ -3716,31 +3716,31 @@ corresponds, in sequence, to

   

 
   

-
When a component value is missing, the associated component
+
When a component value is missing, the associated component
    separator MUST still be specified.

-
Experience with vCard 3 has shown that the first two components
+
Experience with vCard 3 has shown that the first two components
    (post office box and extended address) are plagued with many
    interoperability issues.  To ensure maximal interoperability,
    their values SHOULD be empty.

-
The text components are separated by the SEMICOLON character
+
The text components are separated by the SEMICOLON character
    (U+003B).  Where it makes semantic sense, individual text
    components can include multiple text values (e.g., a "street"
    component with multiple lines) separated by the COMMA character
    (U+002C).

-
The property can include the "PREF" parameter to indicate the
+
The property can include the "PREF" parameter to indicate the
    preferred delivery address when more than one address is
    specified.

-
The GEO and TZ parameters MAY be used with this property.

-
The property can also include a "LABEL" parameter to present a
+
The GEO and TZ parameters MAY be used with this property.

+
The property can also include a "LABEL" parameter to present a
    delivery address label for the address.  Its value is a plain-text
    string representing the formatted address.  Newlines are encoded
    as \n, as they are for property values.

 
ABNF: 

-    
  label-param = "LABEL=" param-value

  ADR-param = "VALUE=text" / label-param / language-param
            / geo-parameter / tz-parameter / altid-param / pid-param
            / pref-param / type-param / any-param

  ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
              ADR-component-street ";" ADR-component-locality ";"
              ADR-component-region ";" ADR-component-code ";"
              ADR-component-country
  ADR-component-pobox    = list-component
  ADR-component-ext      = list-component
  ADR-component-street   = list-component
  ADR-component-locality = list-component
  ADR-component-region   = list-component
  ADR-component-code     = list-component
  ADR-component-country  = list-component

+    
  label-param = "LABEL=" param-value

  ADR-param = "VALUE=text" / label-param / language-param
            / geo-parameter / tz-parameter / altid-param / pid-param
            / pref-param / type-param / any-param

  ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
              ADR-component-street ";" ADR-component-locality ";"
              ADR-component-region ";" ADR-component-code ";"
              ADR-component-country
  ADR-component-pobox    = list-component
  ADR-component-ext      = list-component
  ADR-component-street   = list-component
  ADR-component-locality = list-component
  ADR-component-region   = list-component
  ADR-component-code     = list-component
  ADR-component-country  = list-component

   
Example: 

-    
In this example, the post office box and the extended
+    
In this example, the post office box and the extended
 address are absent.

-    

+    

   
  ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n
    Mail Drop: TNE QB\n123 Main Street\nAny Town, CA  91921-1234\n
    U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.

@@ -3748,40 +3748,40 @@ address are absent.

   

         
7.5. Communications Properties
7.5.1. General

 
-  
These properties describe information about how to communicate with
+  
These properties describe information about how to communicate with
 the object the vCard represents.

 

 
7.5.2. TEL
Purpose: 

-    
To specify the telephone number for telephony communication
+    
To specify the telephone number for telephony communication
 with the object the vCard represents.

   
Value type: 

-    
By default, it is a single free-form text value (for
+    
By default, it is a single free-form text value (for
 backward compatibility with vCard 3), but it SHOULD be reset to a
 URI value.  It is expected that the URI scheme will be "tel", as
 specified in RFC 3966, but other schemes MAY be used.

   
Cardinality: 

-    
*

-  
Special notes: 
This property is based on the X.520 Telephone Number
-attribute CCITT Recommendation X520.
The property can include the "PREF" parameter to indicate a
+    
*

+  
Special notes: 
This property is based on the X.520 Telephone Number
+attribute CCITT Recommendation X520.
The property can include the "PREF" parameter to indicate a
    preferred-use telephone number.

-
The property can include the parameter "TYPE" to specify intended
+
The property can include the parameter "TYPE" to specify intended
    use for the telephone number.  The predefined values for the TYPE
    parameter are:

-
Table 2
ValueDescription
textIndicates that the telephone number supports text messages (SMS).
voiceIndicates a voice telephone number.
faxIndicates a facsimile telephone number.
cellIndicates a cellular or mobile telephone number.
videoIndicates a video conferencing telephone number.
pagerIndicates a paging device telephone number.
textphoneIndicates a telecommunication device for people with  hearing or speech difficulties.

-
The default type is "voice".  These type parameter values can be
+
Table 2
ValueDescription
textIndicates that the telephone number supports text messages (SMS).
voiceIndicates a voice telephone number.
faxIndicates a facsimile telephone number.
cellIndicates a cellular or mobile telephone number.
videoIndicates a video conferencing telephone number.
pagerIndicates a paging device telephone number.
textphoneIndicates a telecommunication device for people with  hearing or speech difficulties.

+
The default type is "voice".  These type parameter values can be
    specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a
    value list (e.g., TYPE="text,voice").  The default can be
    overridden to another set of values by specifying one or more
    alternate values.  For example, the default TYPE of "voice" can be
    reset to a VOICE and FAX telephone number by the value list
    TYPE="voice,fax".

-
If this property’s value is a URI that can also be used for
+
If this property’s value is a URI that can also be used for
    instant messaging, the IMPP (Clause 7.5.4) property SHOULD be
    used in addition to this property.

 
ABNF: 

-    
  TEL-param = TEL-text-param / TEL-uri-param
  TEL-value = TEL-text-value / TEL-uri-value
    ; Value and parameter MUST match.

  TEL-text-param = "VALUE=text"
  TEL-text-value = text

  TEL-uri-param = "VALUE=uri" / mediatype-param
  TEL-uri-value = URI

  TEL-param =/ type-param / pid-param / pref-param / altid-param
             / any-param

  type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
                 / "pager" / "textphone" / iana-token / x-name
    ; type-param-tel MUST NOT be used with a property other than TEL.

+    
  TEL-param = TEL-text-param / TEL-uri-param
  TEL-value = TEL-text-value / TEL-uri-value
    ; Value and parameter MUST match.

  TEL-text-param = "VALUE=text"
  TEL-text-value = text

  TEL-uri-param = "VALUE=uri" / mediatype-param
  TEL-uri-value = URI

  TEL-param =/ type-param / pid-param / pref-param / altid-param
             / any-param

  type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
                 / "pager" / "textphone" / iana-token / x-name
    ; type-param-tel MUST NOT be used with a property other than TEL.

   
Example: 

-    

+    

   
  TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555
   TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67

 

@@ -3789,25 +3789,25 @@ attribute CCITT Recommendation X520.
7.5.3. EMAIL

 
   
Purpose: 

-    
To specify the electronic mail address for communication
+    
To specify the electronic mail address for communication
 with the object the vCard represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The property can include tye "PREF" parameter to
+    
The property can include tye "PREF" parameter to
 indicate a preferred-use email address when more than one is
 specified.

-    
Even though the value is free-form UTF-8 text, it is likely to be
+    
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 RFC 5322, Section 3.4.1.  Readers should also be aware
    of the current work toward internationalized email addresses
    RFC 5335.

   
ABNF: 

-    
  EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
              / altid-param / any-param
  EMAIL-value = text

+    
  EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
              / altid-param / any-param
  EMAIL-value = text

   
Example: 

-    

+    

   
        EMAIL;TYPE=work:jqpublic@xyz.example.com
 
         EMAIL;PREF=1:jane_doe@example.com

@@ -3817,22 +3817,22 @@ specified.

 
7.5.4. IMPP

 
   
Purpose: 

-    
To specify the URI for instant messaging and presence
+    
To specify the URI for instant messaging and presence
 protocol communications with the object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

-  
Special notes: 
The property may include the "PREF" parameter to
+    
*

+  
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.
If this property’s value is a URI that can be used for voice
+semantics as the "PREF" parameter in a TEL property.
If this property’s value is a URI that can be used for voice
 and/or video, the TEL property (Clause 7.5.2) SHOULD be used in
 addition to this property.

-
This property is adapted from RFC 4770, which is made obsolete by
+
This property is adapted from RFC 4770, which is made obsolete by
    this document.
ABNF: 

-    
  IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
             / mediatype-param / altid-param / any-param
  IMPP-value = URI

+    
  IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
             / mediatype-param / altid-param / any-param
  IMPP-value = URI

   
Example: 

-    

+    

   
    IMPP;PREF=1:xmpp:alice@example.com

 

   

@@ -3840,16 +3840,16 @@ addition to this property.

 
7.5.5. LANG

 
   
Purpose: 

-    
To specify the language(s) that may be used for contacting
+    
To specify the language(s) that may be used for contacting
 the entity associated with the vCard.

   
Value type: 

-    
A single language-tag value.

+    
A single language-tag value.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  LANG-param = "VALUE=language-tag" / pid-param / pref-param
             / altid-param / type-param / any-param
  LANG-value = Language-Tag

+    
  LANG-param = "VALUE=language-tag" / pid-param / pref-param
             / altid-param / type-param / any-param
  LANG-value = Language-Tag

   
Example: 

-    

+    

   
    LANG;TYPE=work;PREF=1:en
     LANG;TYPE=work;PREF=2:fr
     LANG;TYPE=home:fr

@@ -3858,34 +3858,34 @@ the entity associated with the vCard.

 

         
7.6. Geographical Properties
7.6.1. General

 
-  
These properties are concerned with information associated with
+  
These properties are concerned with information associated with
 geographical positions or regions associated with the object the
 vCard represents.

 

 
7.6.2. TZ

 
   
Purpose: 

-    
To specify information related to the time zone of the
+    
To specify information related to the time zone of the
 object the vCard represents.

   
Value type: 

-    
The default is a single text value.  It can also be
+    
The default is a single text value.  It can also be
 reset to a single URI or utc-offset value.

   
Cardinality: 

-    
*

-  
Special notes: 
It is expected that names from the public-domain
+    
*

+  
Special notes: 
It is expected that names from the public-domain
 Olson database TZ-DB will be used, but this is not a
-restriction.  See also IANA TZ.
Efforts are currently being directed at creating a standard URI
+restriction.  See also IANA TZ.
Efforts are currently being directed at creating a standard URI
    scheme for expressing time zone information.  Usage of such a
    scheme would ensure a high level of interoperability between
    implementations that support it.

-
Note that utc-offset values SHOULD NOT be used because the UTC
+
Note that utc-offset values SHOULD NOT be used because the UTC
    offset varies with time — not just because of the usual daylight
    saving time shifts that occur in may regions, but often entire
    regions will "re-base" their overall offset.  The actual offset
    may be +/- 1 hour (or perhaps a little more) than the one given.
ABNF: 

-    
  TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
  TZ-value = text / URI / utc-offset
    ; Value and parameter MUST match.

  TZ-param =/ altid-param / pid-param / pref-param / type-param
            / mediatype-param / any-param

+    
  TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
  TZ-value = text / URI / utc-offset
    ; Value and parameter MUST match.

  TZ-param =/ altid-param / pid-param / pref-param / type-param
            / mediatype-param / any-param

   
Examples: 

-    

+    

   
  TZ:Raleigh/North America
 
   TZ;VALUE=utc-offset:-0500
@@ -3896,79 +3896,79 @@ restriction.  See also IANA TZ.
<
 
7.6.3. GEO

 
   
Purpose: 

-    
To specify information related to the global positioning of
+    
To specify information related to the global positioning of
 the object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The "geo" URI scheme RFC 5870 is particularly well
+    
The "geo" URI scheme RFC 5870 is particularly well
 suited for this property, but other schemes MAY be used.

   
ABNF: 

-    
  GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  GEO-value = URI

+    
  GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  GEO-value = URI

   
Example: 

-    

+    

   
        GEO:geo:37.386013,-122.082932

 

   

 

         
7.7. Organizational Properties
7.7.1. General

 
-  
These properties are concerned with information associated with
+  
These properties are concerned with information associated with
 characteristics of the organization or organizational units of the
 object that the vCard represents.

 

 
7.7.2. TITLE
Purpose: 

-    
To specify the position or job of the object the vCard
+    
To specify the position or job of the object the vCard
 represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   

-
Cardinality:  *

+
Cardinality:  *

 
Special notes: 

-    
This property is based on the X.520 Title attribute
+    
This property is based on the X.520 Title attribute
 CCITT Recommendation X520.

   
ABNF: 

-    
  TITLE-param = "VALUE=text" / language-param / pid-param
              / pref-param / altid-param / type-param / any-param
  TITLE-value = text

+    
  TITLE-param = "VALUE=text" / language-param / pid-param
              / pref-param / altid-param / type-param / any-param
  TITLE-value = text

   
Example: 

-    

+    

   
        TITLE:Research Scientist

 

   

 
7.7.3. ROLE
Purpose: 

-    
To specify the function or part played in a particular
+    
To specify the function or part played in a particular
 situation by the object the vCard represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

+    
*

   

-
Special notes:  This property is based on the X.520 Business Category
+
Special notes:  This property is based on the X.520 Business Category
    explanatory attribute CCITT Recommendation X520.  This property is
    included as an organizational type to avoid confusion with the
    semantics of the TITLE property and incorrect usage of that
    property when the semantics of this property is intended.

 
ABNF: 

-    
  ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  ROLE-value = text

+    
  ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  ROLE-value = text

   
Example: 

-    

+    

   
        ROLE:Project Leader

 

   

 
7.7.4. LOGO

 
   
Purpose: 

-    
To specify a graphic image of a logo associated with the
+    
To specify a graphic image of a logo associated with the
 object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
             / type-param / mediatype-param / altid-param / any-param
  LOGO-value = URI

+    
  LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
             / type-param / mediatype-param / altid-param / any-param
  LOGO-value = URI

   
Examples: 

-    

+    

   
  LOGO:http://www.example.com/pub/logos/abccorp.jpg
 
   LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
@@ -3981,25 +3981,25 @@ object the vCard represents.

 
7.7.5. ORG

 
   
Purpose: 

-    
To specify the organizational name and units associated
+    
To specify the organizational name and units associated
 with the vCard.

   
Value type: 

-    
A single structured text value consisting of components
+    
A single structured text value consisting of components
 separated by the SEMICOLON character (U+003B).

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The property is based on the X.520 Organization Name
+    
The property is based on the X.520 Organization Name
 and Organization Unit attributes CCITT Recommendation X520.  The property
 value is a structured type consisting of the organization name,
 followed by zero or more levels of organizational unit names.

-    
The SORT-AS parameter MAY be applied to this property.

+    
The SORT-AS parameter MAY be applied to this property.

   
ABNF: 

-    
  ORG-param = "VALUE=text" / sort-as-param / language-param
            / pid-param / pref-param / altid-param / type-param
            / any-param
  ORG-value = component *(";" component)

+    
  ORG-param = "VALUE=text" / sort-as-param / language-param
            / pid-param / pref-param / altid-param / type-param
            / any-param
  ORG-value = component *(";" component)

   
Example: 

-    
A property value consisting of an organizational name,
+    
A property value consisting of an organizational name,
 organizational unit #1 name, and organizational unit #2 name.

-    

+    

   
        ORG:ABC\, Inc.;North American Division;Marketing

 

   

@@ -4007,20 +4007,20 @@ organizational unit #1 name, and organizational unit #2 name.

 
7.7.6. MEMBER

 
   
Purpose: 

-    
To include a member in the group this vCard represents.

+    
To include a member in the group this vCard represents.

   
Value type: 

-    
A single URI.  It MAY refer to something other than a
+    
A single URI.  It MAY refer to something other than a
 vCard object.  For example, an email distribution list could
 employ the "mailto" URI scheme RFC 6068 for efficiency.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
This property MUST NOT be present unless the value of
+    
This property MUST NOT be present unless the value of
 the KIND property is "group".

   
ABNF: 

-    
  MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  MEMBER-value = URI

+    
  MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  MEMBER-value = URI

   
Examples: 

-    

+    

   
  BEGIN:VCARD
   VERSION:4.0
   KIND:group
@@ -4054,29 +4054,29 @@ the KIND property is "group".

 
7.7.7. RELATED

 
   
Purpose: 

-    
To specify a relationship between another entity and the
+    
To specify a relationship between another entity and the
 entity represented by this vCard.

   
Value type: 

-    
A single URI.  It can also be reset to a single text
+    
A single URI.  It can also be reset to a single text
 value.  The text value can be used to specify textual information.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The TYPE parameter MAY be used to characterize the
+    
The TYPE parameter MAY be used to characterize the
 related entity.  It contains a comma-separated list of values that
 are registered with IANA as described in Clause 11.2.  The
 registry is pre-populated with the values defined in XFN.  This
 document also specifies two additional values:

     
agent: 

-    
an entity who may sometimes act on behalf of the entity
+    
an entity who may sometimes act on behalf of the entity
 associated with the vCard.

   
emergency: 

-    
indicates an emergency contact

+    
indicates an emergency contact

   

   
ABNF: 

-    
  RELATED-param = RELATED-param-uri / RELATED-param-text
  RELATED-value = URI / text
    ; Parameter and value MUST match.

  RELATED-param-uri = "VALUE=uri" / mediatype-param
  RELATED-param-text = "VALUE=text" / language-param

  RELATED-param =/ pid-param / pref-param / altid-param / type-param
                 / any-param

  type-param-related = related-type-value *("," related-type-value)
    ; type-param-related MUST NOT be used with a property other than
    ; RELATED.

  related-type-value = "contact" / "acquaintance" / "friend" / "met"
                     / "co-worker" / "colleague" / "co-resident"
                     / "neighbor" / "child" / "parent"
                     / "sibling" / "spouse" / "kin" / "muse"
                     / "crush" / "date" / "sweetheart" / "me"
                     / "agent" / "emergency"

+    
  RELATED-param = RELATED-param-uri / RELATED-param-text
  RELATED-value = URI / text
    ; Parameter and value MUST match.

  RELATED-param-uri = "VALUE=uri" / mediatype-param
  RELATED-param-text = "VALUE=text" / language-param

  RELATED-param =/ pid-param / pref-param / altid-param / type-param
                 / any-param

  type-param-related = related-type-value *("," related-type-value)
    ; type-param-related MUST NOT be used with a property other than
    ; RELATED.

  related-type-value = "contact" / "acquaintance" / "friend" / "met"
                     / "co-worker" / "colleague" / "co-resident"
                     / "neighbor" / "child" / "parent"
                     / "sibling" / "spouse" / "kin" / "muse"
                     / "crush" / "date" / "sweetheart" / "me"
                     / "agent" / "emergency"

   
Examples: 

-    

+    

   
RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
 RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf
 RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane
@@ -4086,24 +4086,24 @@ RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane
 

         
7.8. Explanatory Properties
7.8.1. General

 
-  
These properties are concerned with additional explanations, such as
+  
These properties are concerned with additional explanations, such as
 that related to informational notes or revisions specific to the
 vCard.

 

 
7.8.2. CATEGORIES

 
   
Purpose: 

-    
To specify application category information about the
+    
To specify application category information about the
 vCard, also known as "tags".

   
Value type: 

-    
One or more text values separated by a COMMA character
+    
One or more text values separated by a COMMA character
 (U+002C).

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  CATEGORIES-param = "VALUE=text" / pid-param / pref-param
                   / type-param / altid-param / any-param
  CATEGORIES-value = text-list

+    
  CATEGORIES-param = "VALUE=text" / pid-param / pref-param
                   / type-param / altid-param / any-param
  CATEGORIES-value = text-list

   
Example: 

-    

+    

   
        CATEGORIES:TRAVEL AGENT
 
         CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY

@@ -4111,19 +4111,19 @@ vCard, also known as "tags".

   

 

 
7.8.3. NOTE
Purpose: 

-    
To specify supplemental information or a comment that is
+    
To specify supplemental information or a comment that is
 associated with the vCard.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

+    
*

   

-
Special notes:  The property is based on the X.520 Description
+
Special notes:  The property is based on the X.520 Description
    attribute CCITT Recommendation X520.

 
ABNF: 

-    
  NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  NOTE-value = text

+    
  NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  NOTE-value = text

   
Example: 

-    

+    

   
        NOTE:This fax number is operational 0800 to 1715
           EST\, Mon-Fri.

 

@@ -4131,21 +4131,21 @@ associated with the vCard.

 
7.8.4. PRODID

 
   
Purpose: 

-    
To specify the identifier for the product that created the
+    
To specify the identifier for the product that created the
 vCard object.

   
Type value: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
Implementations SHOULD use a method such as that
+    
Implementations SHOULD use a method such as that
 specified for Formal Public Identifiers in ISO 9070 or for
 Universal Resource Names in RFC 3406 to ensure that the text
 value is unique.

   
ABNF: 

-    
  PRODID-param = "VALUE=text" / any-param
  PRODID-value = text

+    
  PRODID-param = "VALUE=text" / any-param
  PRODID-value = text

   
Example: 

-    

+    

   
        PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN

 

   

@@ -4153,18 +4153,18 @@ value is unique.

 
7.8.5. REV

 
   
Purpose: 

-    
To specify revision information about the current vCard.

+    
To specify revision information about the current vCard.

   
Value type: 

-    
A single timestamp value.

+    
A single timestamp value.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
The value distinguishes the current revision of the
+    
The value distinguishes the current revision of the
 information in this vCard for other renditions of the information.

   
ABNF: 

-    
  REV-param = "VALUE=timestamp" / any-param
  REV-value = timestamp

+    
  REV-param = "VALUE=timestamp" / any-param
  REV-value = timestamp

   
Example: 

-    

+    

   
        REV:19951031T222710Z

 

   

@@ -4172,18 +4172,18 @@ information in this vCard for other renditions of the information.

 
7.8.6. SOUND

 
   
Purpose: 

-    
To specify a digital sound content information that
+    
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.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
              / type-param / mediatype-param / altid-param
              / any-param
  SOUND-value = URI

+    
  SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
              / type-param / mediatype-param / altid-param
              / any-param
  SOUND-value = URI

   
Example: 

-    

+    

   
  SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
 
   SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
@@ -4196,22 +4196,22 @@ the vCard.

 
7.8.7. UID

 
   
Purpose: 

-    
To specify a value that represents a globally unique
+    
To specify a value that represents a globally unique
 identifier corresponding to the entity associated with the vCard.

   
Value type: 

-    
A single URI value.  It MAY also be reset to free-form
+    
A single URI value.  It MAY also be reset to free-form
 text.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
This property is used to uniquely identify the object
+    
This property is used to uniquely identify the object
 that the vCard represents.  The "uuid" URN namespace defined in
 RFC 4122 is particularly well suited to this task, but other URI
 schemes MAY be used.  Free-form text MAY also be used.

   
ABNF: 

-    
  UID-param = UID-uri-param / UID-text-param
  UID-value = UID-uri-value / UID-text-value
    ; Value and parameter MUST match.

  UID-uri-param = "VALUE=uri"
  UID-uri-value = URI

  UID-text-param = "VALUE=text"
  UID-text-value = text

  UID-param =/ any-param

+    
  UID-param = UID-uri-param / UID-text-param
  UID-value = UID-uri-value / UID-text-value
    ; Value and parameter MUST match.

  UID-uri-param = "VALUE=uri"
  UID-uri-value = URI

  UID-text-param = "VALUE=text"
  UID-text-value = text

  UID-param =/ any-param

   
Example: 

-    

+    

   
        UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

 

   

@@ -4219,27 +4219,27 @@ schemes MAY be used.  Free-form text 
7.8.8. CLIENTPIDMAP

 
   
Purpose: 

-    
To give a global meaning to a local PID source identifier.

+    
To give a global meaning to a local PID source identifier.

   
Value type: 

-    
A semicolon-separated pair of values.  The first field
+    
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 RFC 4122 is particularly well suited to this
 task, but other URI schemes MAY be used.

   
Cardinality: 

-    
*

-  
Special notes: 
PID source identifiers (the source identifier is the
+    
*

+  
Special notes: 
PID source identifiers (the source identifier is the
 second field in a PID parameter instance) are small integers that
 only have significance within the scope of a single vCard
 instance.  Each distinct source identifier present in a vCard MUST
 have an associated CLIENTPIDMAP.  See Clause 8 for more details
-on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive.  Zero is not
+on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive.  Zero is not
    allowed.

-
As a special exception, the PID parameter MUST NOT be applied to
+
As a special exception, the PID parameter MUST NOT be applied to
    this property.
ABNF: 

-    
  CLIENTPIDMAP-param = any-param
  CLIENTPIDMAP-value = 1*DIGIT ";" URI

+    
  CLIENTPIDMAP-param = any-param
  CLIENTPIDMAP-value = 1*DIGIT ";" URI

   
Example: 

-    

+    

   
  TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
   EMAIL;PID=4.1,5.2:jdoe@example.com
   CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
@@ -4250,18 +4250,18 @@ on the usage of CLIENTPIDMAP.
7.8.9. URL

 
   
Purpose: 

-    
To specify a uniform resource locator associated with the
+    
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.

   
Cardinality: 

-    
*

+    
*

   
Value type: 

-    
A single uri value.

+    
A single uri value.

   
ABNF: 

-    
  URL-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  URL-value = URI

+    
  URL-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  URL-value = URI

   
Example: 

-    

+    

   
        URL:http://example.org/restaurant.french/~chezchic.html

 

   

@@ -4269,44 +4269,44 @@ identifiers.

 
7.8.10. VERSION

 
   
Purpose: 

-    
To specify the version of the vCard specification used to
+    
To specify the version of the vCard specification used to
 format this vCard.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
1

+    
1

   
Special notes: 

-    
This property MUST be present in the vCard object,
+    
This property MUST be present in the vCard object,
 and it must appear immediately after BEGIN:VCARD.  The value MUST
 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.

   
ABNF: 

-    
  VERSION-param = "VALUE=text" / any-param
  VERSION-value = "4.0"

+    
  VERSION-param = "VALUE=text" / any-param
  VERSION-value = "4.0"

   
Example: 

-    

+    

   
        VERSION:4.0

 

   

 

         
7.9. Security Properties
7.9.1. General

 
-  
These properties are concerned with the security of communication
+  
These properties are concerned with the security of communication
 pathways or access to the vCard.

 

 
7.9.2. KEY

 
   
Purpose: 

-    
To specify a public key or authentication certificate
+    
To specify a public key or authentication certificate
 associated with the object that the vCard represents.

   
Value type: 

-    
A single URI.  It can also be reset to a text value.

+    
A single URI.  It can also be reset to a text value.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  KEY-param = KEY-uri-param / KEY-text-param
  KEY-value = KEY-uri-value / KEY-text-value
    ; Value and parameter MUST match.

  KEY-uri-param = "VALUE=uri" / mediatype-param
  KEY-uri-value = URI

  KEY-text-param = "VALUE=text"
  KEY-text-value = text

  KEY-param =/ altid-param / pid-param / pref-param / type-param
             / any-param

+    
  KEY-param = KEY-uri-param / KEY-text-param
  KEY-value = KEY-uri-value / KEY-text-value
    ; Value and parameter MUST match.

  KEY-uri-param = "VALUE=uri" / mediatype-param
  KEY-uri-value = URI

  KEY-text-param = "VALUE=text"
  KEY-text-value = text

  KEY-param =/ altid-param / pid-param / pref-param / type-param
             / any-param

   
Examples: 

-    

+    

   
  KEY:http://www.example.com/keys/jdoe.cer
 
   KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe
@@ -4319,19 +4319,19 @@ associated with the object that the vCard represents.

 

         
7.10. Calendar Properties
7.10.1. General

 
-  
These properties are further specified in RFC 2739.

+  
These properties are further specified in RFC 2739.

 

 
7.10.2. FBURL

 
   
Purpose: 

-    
To specify the URI for the busy time associated with the
+    
To specify the URI for the busy time associated with the
 object that the vCard represents.

   
Value type: 

-    
A single URI value.

+    
A single URI value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
Where multiple FBURL properties are specified, the
+    
Where multiple FBURL properties are specified, the
 default FBURL property is indicated with the PREF parameter.  The
 FTP RFC 1738 or HTTP RFC 2616 type of URI points to an iCalendar
 RFC 5545 object associated with a snapshot of the next few weeks
@@ -4339,9 +4339,9 @@ or months of busy time data.  If the iCalendar object is
 represented as a file or document, its file extension should be
 ".ifb".

   
ABNF: 

-    
  FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
              / mediatype-param / altid-param / any-param
  FBURL-value = URI

+    
  FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
              / mediatype-param / altid-param / any-param
  FBURL-value = URI

   
Examples: 

-    

+    

   
  FBURL;PREF=1:http://www.example.com/busy/janedoe
   FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb

 

@@ -4350,21 +4350,21 @@ represented as a file or document, its file extension should be
 
7.10.3. CALADRURI

 
   
Purpose: 

-    
To specify the calendar user address RFC 5545 to which a
+    
To specify the calendar user address RFC 5545 to which a
 scheduling request RFC 5546 should be sent for the object
 represented by the vCard.

   
Value type: 

-    
A single URI value.

+    
A single URI value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
Where multiple CALADRURI properties are specified,
+    
Where multiple CALADRURI properties are specified,
 the default CALADRURI property is indicated with the PREF
 parameter.

   
ABNF: 

-    
  CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
                  / mediatype-param / altid-param / any-param
  CALADRURI-value = URI

+    
  CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
                  / mediatype-param / altid-param / any-param
  CALADRURI-value = URI

   
Example: 

-    

+    

   
  CALADRURI;PREF=1:mailto:janedoe@example.com
   CALADRURI:http://example.com/calendar/jdoe

 

@@ -4373,23 +4373,23 @@ parameter.

 
7.10.4. CALURI

 
   
Purpose: 

-    
To specify the URI for a calendar associated with the
+    
To specify the URI for a calendar associated with the
 object represented by the vCard.

   
Value type: 

-    
A single URI value.

+    
A single URI value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
Where multiple CALURI properties are specified, the
+    
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 RFC 5545
 object associated with a snapshot of the user’s calendar store.
 If the iCalendar object is represented as a file or document, its
 file extension should be ".ics".

   
ABNF: 

-    
  CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
               / mediatype-param / altid-param / any-param
  CALURI-value = URI

+    
  CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
               / mediatype-param / altid-param / any-param
  CALURI-value = URI

   
Examples: 

-    

+    

   
  CALURI;PREF=1:http://cal.example.com/calA
   CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics

 

@@ -4397,7 +4397,7 @@ file extension should be ".ics".

 

         
7.11. Extended Properties and Parameters

 
-  
The properties and parameters defined by this document can be
+  
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.

@@ -4407,51 +4407,51 @@ cooperating agents without outside registration or standardization.

         
8.  Synchronization

         
8.1. General

 
-  
vCard data often needs to be synchronized between devices.  In this
+  
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.

 

-        
8.2. Mechanisms
8.2.1. General
Two mechanisms are available: the UID property is used to match
+        
8.2. Mechanisms
8.2.1. General
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.

-
The term "matching" is used here to mean recognizing that two
+
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.

-
8.2.2. Matching vCard Instances
vCard instances for which the UID properties (Clause 7.8.7) are
+
8.2.2. Matching vCard Instances
vCard instances for which the UID properties (Clause 7.8.7) are
 equivalent MUST be matched.  Equivalence is determined as specified
 in RFC 3986, Section 6.

-
In all other cases, vCard instances MAY be matched at the discretion
+
In all other cases, vCard instances MAY be matched at the discretion
 of the synchronization engine.

-
8.2.3. Matching Property Instances
Property instances belonging to unmatched vCards MUST NOT be matched.

-
Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
+
8.2.3. Matching Property Instances
Property instances belonging to unmatched vCards MUST NOT be matched.

+
Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
 same MUST NOT be matched.

-
Property instances whose name is CLIENTPIDMAP are handled separately
+
Property instances whose name is CLIENTPIDMAP are handled separately
 and MUST NOT be matched.  The synchronization MUST ensure that there
 is consistency of CLIENTPIDMAPs among matched vCard instances.

-
Property instances belonging to matched vCards, whose name is the
+
Property instances belonging to matched vCards, whose name is the
 same, and whose maximum cardinality is 1, MUST be matched.

-
Property instances belonging to matched vCards, whose name is the
+
Property instances belonging to matched vCards, whose name is the
 same, and whose PID parameters match, MUST be matched.  See
 Clause 8.2.4 for details on PID matching.

-
In all other cases, property instances MAY be matched at the
+
In all other cases, property instances MAY be matched at the
 discretion of the synchronization engine.

-
8.2.4. PID Matching
Two PID values for which the first fields are equivalent represent
+
8.2.4. PID Matching
Two PID values for which the first fields are equivalent represent
 the same local value.

-
Two PID values representing the same local value and for which the
+
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 RFC 3986, Section 6) also
 represent the same global value.

-
PID parameters for which at least one pair of their values represent
+
PID parameters for which at least one pair of their values represent
 the same global value MUST be matched.

-
In all other cases, PID parameters MAY be matched at the discretion
+
In all other cases, PID parameters MAY be matched at the discretion
 of the synchronization engine.

-
For example, PID value "5.1", in the first vCard below, and PID value
+
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.

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   EMAIL;PID=4.2,5.1:jdoe@example.com
@@ -4459,7 +4459,7 @@ of the synchronization engine.

   CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
   END:VCARD

 

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   EMAIL;PID=5.1,5.2:john@example.com
@@ -4467,8 +4467,8 @@ of the synchronization engine.

   CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
   END:VCARD

 

-        
8.3. Example
8.3.1. Creation
The following simple vCard is first created on a given device.

-

+        
8.3. Example
8.3.1. Creation
The following simple vCard is first created on a given device.

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -4478,7 +4478,7 @@ of the synchronization engine.

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-
This new vCard is assigned the UID
+
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
@@ -4489,15 +4489,15 @@ matched.  The N property has no PID because it is forbidden by its
 maximum cardinality of 1.

 
8.3.2. Initial Sharing

 
-  
This vCard is shared with a second device.  Upon inspecting the UID
+  
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.

 

-
8.3.3. Adding and Sharing a Property
A new phone number is created on the first device, then the vCard is
+
8.3.3. Adding and Sharing a Property
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:

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -4508,30 +4508,30 @@ receives:

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-
Upon inspecting the UID property, the second device matches the vCard
+
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.

-
The FN properties are matched because the PID parameters have the
+
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.

-
The N properties are matched automatically because their maximum
+
The N properties are matched automatically because their maximum
 cardinality is 1.  Since the property value is the same, no update
 takes place.

-
The EMAIL properties are matched because the PID parameters have the
+
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.

-
The TEL property in the new vCard is not matched to any in the stored
+
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.

-
The CLIENTPIDMAP property is handled separately by the
+
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.

-
8.3.4. Simultaneous Editing
A new email address and a new phone number are added to the vCard on
+
8.3.4. Simultaneous Editing
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:

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -4544,7 +4544,7 @@ happens.  Here are the vCards that are communicated to each other:

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -4558,24 +4558,24 @@ happens.  Here are the vCards that are communicated to each other:

   CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
   END:VCARD

 

-
On the first device, the same PID source identifier (1) is reused for
+
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’s identifier,
 "urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".

-
The new EMAIL properties are unmatched on both sides since the PID
+
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.

-
Although the situation appears to be the same for the TEL properties,
+
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
 Clause 8.2.3 state that two properties MAY be matched at the
 discretion of the synchronization engine.  Therefore, the two
 properties are merged.

-
All this results in the following vCard, which is stored on both
+
All this results in the following vCard, which is stored on both
 devices:

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -4590,11 +4590,11 @@ devices:

   CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
   END:VCARD

 

-
8.3.5. Global Context Simplification
The two devices finish their synchronization procedure by simplifying
+
8.3.5. Global Context Simplification
The two devices finish their synchronization procedure by simplifying
 their global contexts.  Since they haven’t talked to any other
 device, the following vCard is for all purposes equivalent to the
 above.  It is also shorter.

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -4608,14 +4608,14 @@ above.  It is also shorter.

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-
The details of global context simplification are unspecified by this
+
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’s opinion, worthwhile.

       

       

         
9.  Example: Author’s vCard

-        

+        

   
 BEGIN:VCARD
  VERSION:4.0
  FN:Simon Perreault
@@ -4682,35 +4682,35 @@ to RFC 3986, Section 7, for considerations related to URI
       

       

         
11.  IANA Considerations

-        
11.1. Media Type Registration
IANA has registered the following Media Type (in
+        
11.1. Media Type Registration
IANA has registered the following Media Type (in
 http://www.iana.org) and marked the text/directory Media Type as
 DEPRECATED.

 
To: 

-    
ietf-types@iana.org

+    
ietf-types@iana.org

   
Subject: 

-    
Registration of media type text/vcard

+    
Registration of media type text/vcard

   
Type name: 

-    
text

+    
text

   
Subtype name: 

-    
vcard

+    
vcard

   
Required parameters: 

-    
none

-  
Optional parameters: 
version
The "version" parameter is to be interpreted identically as the
+    
none

+  
Optional parameters: 
version
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 MUST have a VERSION property with value
    identical to that of this MIME parameter.

-
"charset": as defined for text/plain RFC 2046; encodings other
+
"charset": as defined for text/plain RFC 2046; encodings other
    than UTF-8 RFC 3629 MUST NOT be used.
Encoding considerations: 

-    
8bit

+    
8bit

   
Security considerations: 

-    
See Clause 10.

-  
Interoperability considerations: 
The text/vcard media type is
+    
See Clause 10.

+  
Interoperability considerations: 
The text/vcard media type is
 intended to identify vCard data of any version.  There are older
 specifications of vCard RFC 2426 Internet Mail Consortium vCard 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 Clause 7.8.10) for identifying the standard to which
-a given vCard object conforms.
In addition, the following media types are known to have been used
+a given vCard object conforms.
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.

 
@@ -4724,46 +4724,46 @@ a given vCard object conforms.
Published specification: 

-    
RFC 6350

+    
RFC 6350

   
Applications that use this media type: 

-    
They are numerous, diverse,
+    
They are numerous, diverse,
 and include mail user agents, instant messaging clients, address
 book applications, directory servers, and customer relationship
 management software.

   
Additional information: 

     
Magic number(s): 
File extension(s): 

-    
.vcf .vcard

+    
.vcf .vcard

   
Macintosh file type code(s): 

   
Person & email address to contact for further information: 

-    
vCard
+    
vCard
 discussion mailing list <vcarddav@ietf.org>

   
Intended usage: 

-    
COMMON

+    
COMMON

   
Restrictions on usage: 

-    
none

+    
none

   
Author: 

-    
Simon Perreault

+    
Simon Perreault

   
Change controller: 

-    
IETF

+    
IETF

   

         
11.2. Registering New vCard Elements
11.2.1. General

 
-  
This section defines the process for registering new or modified
+  
This section defines the process for registering new or modified
 vCard elements (i.e., properties, parameters, value data types, and
 values) with IANA.

 

-
11.2.2. Registration Procedure
The IETF has created a mailing list, vcarddav@ietf.org, which can be
+
11.2.2. Registration Procedure
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.

-
Registration of new vCard elements MUST be reviewed by the designated
+
Registration of new vCard elements MUST be reviewed by the designated
 expert and published in an RFC.  A Standards Track RFC is REQUIRED
 for the registration of new value data types that modify existing
 properties.  A Standards Track RFC is also REQUIRED for registration
 of vCard elements that modify vCard elements previously documented in
 a Standards Track RFC.

-
The registration procedure begins when a completed registration
+
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
@@ -4773,149 +4773,149 @@ 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.

-
Once the registration procedure concludes successfully, IANA creates
+
Once the registration procedure concludes successfully, IANA creates
 or modifies the corresponding record in the vCard registry.  The
 completed registration template is discarded.

-
An RFC specifying new vCard elements MUST include the completed
+
An RFC specifying new vCard elements MUST include the completed
 registration templates, which MAY be expanded with additional
 information.  These completed templates are intended to go in the
 body of the document, not in the IANA Considerations section.

-
Finally, note that there is an XML representation for vCard defined
+
Finally, note that there is an XML representation for vCard defined
 in RFC 6351.  An XML representation SHOULD be defined for new vCard
 elements.

-
11.2.3. Vendor Namespace
The vendor namespace is used for vCard elements associated with
+
11.2.3. Vendor Namespace
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.

-
A registration may be placed in the vendor namespace by anyone who
+
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.

-
vCard elements belonging to the vendor namespace will be
+
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’s choosing (e.g., "VND-123456-
 MUDPIE").

-
While public exposure and review of vCard elements to be registered
+
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.

-
11.2.4. Registration Template for Properties
A property is defined by completing the following template.

+
11.2.4. Registration Template for Properties
A property is defined by completing the following template.

 
Namespace: 

-    
Empty for the global namespace, "VND-NNNN-" for a vendor-
+    
Empty for the global namespace, "VND-NNNN-" for a vendor-
 specific property (where NNNN is replaced by the vendor’s PEN).

   
Property name: 

-    
The name of the property.

+    
The name of the property.

   
Purpose: 

-    
The purpose of the property.  Give a short but clear
+    
The purpose of the property.  Give a short but clear
 description.

   
Value type: 

-    
Any of the valid value types for the property value
+    
Any of the valid value types for the property value
 needs to be specified.  The default value type also needs to be
 specified.

   
Cardinality: 

-    
See Clause 7.

+    
See Clause 7.

   
Property parameters: 

-    
Any of the valid property parameters for the
+    
Any of the valid property parameters for the
 property MUST be specified.

   
Description: 

-    
Any special notes about the property, how it is to be
+    
Any special notes about the property, how it is to be
 used, etc.

   
Format definition: 

-    
The ABNF for the property definition needs to be
+    
The ABNF for the property definition needs to be
 specified.

   
Example(s): 

-    
One or more examples of instances of the property need
+    
One or more examples of instances of the property need
 to be specified.

   

-
11.2.5. Registration Template for Parameters
A parameter is defined by completing the following template.

+
11.2.5. Registration Template for Parameters
A parameter is defined by completing the following template.

 
Namespace: 

-    
Empty for the global namespace, "VND-NNNN-" for a vendor-
+    
Empty for the global namespace, "VND-NNNN-" for a vendor-
 specific property (where NNNN is replaced by the vendor’s PEN).

   
Parameter name: 

-    
The name of the parameter.

+    
The name of the parameter.

   
Purpose: 

-    
The purpose of the parameter.  Give a short but clear
+    
The purpose of the parameter.  Give a short but clear
 description.

   
Description: 

-    
Any special notes about the parameter, how it is to be
+    
Any special notes about the parameter, how it is to be
 used, etc.

   
Format definition: 

-    
The ABNF for the parameter definition needs to be
+    
The ABNF for the parameter definition needs to be
 specified.

   
Example(s): 

-    
One or more examples of instances of the parameter need
+    
One or more examples of instances of the parameter need
 to be specified.

   

-
11.2.6. Registration Template for Value Data Types
A value data type is defined by completing the following template.

+
11.2.6. Registration Template for Value Data Types
A value data type is defined by completing the following template.

 
Value name: 

-    
The name of the value type.

+    
The name of the value type.

   
Purpose: 

-    
The purpose of the value type.  Give a short but clear
+    
The purpose of the value type.  Give a short but clear
 description.

   
Description: 

-    
Any special notes about the value type, how it is to be
+    
Any special notes about the value type, how it is to be
 used, etc.

   
Format definition: 

-    
The ABNF for the value type definition needs to
+    
The ABNF for the value type definition needs to
 be specified.

   
Example(s): 

-    
One or more examples of instances of the value type need
+    
One or more examples of instances of the value type need
 to be specified.

   

-
11.2.7. Registration Template for Values
A value is defined by completing the following template.

+
11.2.7. Registration Template for Values
A value is defined by completing the following template.

 
Value: 

-    
The value literal.

+    
The value literal.

   
Purpose: 

-    
The purpose of the value.  Give a short but clear
+    
The purpose of the value.  Give a short but clear
 description.

   
Conformance: 

-    
The vCard properties and/or parameters that can take
+    
The vCard properties and/or parameters that can take
 this value needs to be specified.

   
Example(s): 

-    
One or more examples of instances of the value need to
+    
One or more examples of instances of the value need to
 be specified.

   

-
The following is a fictitious example of a registration of a vCard
+
The following is a fictitious example of a registration of a vCard
 value:

 
Value: 

-    
supervisor

+    
supervisor

   
Purpose: 

-    
It means that the related entity is the direct hierarchical
+    
It means that the related entity is the direct hierarchical
 superior (i.e., supervisor or manager) of the entity this vCard
 represents.

   
Conformance: 

-    
This value can be used with the "TYPE" parameter
+    
This value can be used with the "TYPE" parameter
 applied on the "RELATED" property.

   
Example(s): 

-    

+    

   
RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

 

   

         
11.3. Initial vCard Elements Registries
11.3.1. General

 
-  
The IANA has created and will maintain the following registries for
+  
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".

 

-
11.3.2. Properties Registry
The following table has been used to initialize the properties
+
11.3.2. Properties Registry
The following table has been used to initialize the properties
 registry.

-
Table 3
NamespacePropertyReference
SOURCERFC 6350, Section 6.1.3
KINDRFC 6350, Section 6.1.4
XMLRFC 6350, Section 6.1.5
FNRFC 6350, Section 6.2.1
NRFC 6350, Section 6.2.2
NICKNAMERFC 6350, Section 6.2.3
PHOTORFC 6350, Section 6.2.4
BDAYRFC 6350, Section 6.2.5
ANNIVERSARYRFC 6350, Section 6.2.6
GENDERRFC 6350, Section 6.2.7
ADRRFC 6350, Section 6.3.1
TELRFC 6350, Section 6.4.1
EMAILRFC 6350, Section 6.4.2
IMPPRFC 6350, Section 6.4.3
LANGRFC 6350, Section 6.4.4
TZRFC 6350, Section 6.5.1
GEORFC 6350, Section 6.5.2
TITLERFC 6350, Section 6.6.1
ROLERFC 6350, Section 6.6.2
LOGORFC 6350, Section 6.6.3
ORGRFC 6350, Section 6.6.4
MEMBERRFC 6350, Section 6.6.5
RELATEDRFC 6350, Section 6.6.6
CATEGORIESRFC 6350, Section 6.7.1
NOTERFC 6350, Section 6.7.2
PRODIDRFC 6350, Section 6.7.3
REVRFC 6350, Section 6.7.4
SOUNDRFC 6350, Section 6.7.5
UIDRFC 6350, Section 6.7.6
CLIENTPIDMAPRFC 6350, Section 6.7.7
URLRFC 6350, Section 6.7.8
VERSIONRFC 6350, Section 6.7.9
KEYRFC 6350, Section 6.8.1
FBURLRFC 6350, Section 6.9.1
CALADRURIRFC 6350, Section 6.9.2
CALURIRFC 6350, Section 6.9.3

-
11.3.3. Parameters Registry
The following table has been used to initialize the parameters
+
Table 3
NamespacePropertyReference
SOURCERFC 6350, Section 6.1.3
KINDRFC 6350, Section 6.1.4
XMLRFC 6350, Section 6.1.5
FNRFC 6350, Section 6.2.1
NRFC 6350, Section 6.2.2
NICKNAMERFC 6350, Section 6.2.3
PHOTORFC 6350, Section 6.2.4
BDAYRFC 6350, Section 6.2.5
ANNIVERSARYRFC 6350, Section 6.2.6
GENDERRFC 6350, Section 6.2.7
ADRRFC 6350, Section 6.3.1
TELRFC 6350, Section 6.4.1
EMAILRFC 6350, Section 6.4.2
IMPPRFC 6350, Section 6.4.3
LANGRFC 6350, Section 6.4.4
TZRFC 6350, Section 6.5.1
GEORFC 6350, Section 6.5.2
TITLERFC 6350, Section 6.6.1
ROLERFC 6350, Section 6.6.2
LOGORFC 6350, Section 6.6.3
ORGRFC 6350, Section 6.6.4
MEMBERRFC 6350, Section 6.6.5
RELATEDRFC 6350, Section 6.6.6
CATEGORIESRFC 6350, Section 6.7.1
NOTERFC 6350, Section 6.7.2
PRODIDRFC 6350, Section 6.7.3
REVRFC 6350, Section 6.7.4
SOUNDRFC 6350, Section 6.7.5
UIDRFC 6350, Section 6.7.6
CLIENTPIDMAPRFC 6350, Section 6.7.7
URLRFC 6350, Section 6.7.8
VERSIONRFC 6350, Section 6.7.9
KEYRFC 6350, Section 6.8.1
FBURLRFC 6350, Section 6.9.1
CALADRURIRFC 6350, Section 6.9.2
CALURIRFC 6350, Section 6.9.3

+
11.3.3. Parameters Registry
The following table has been used to initialize the parameters
 registry.

-
Table 4
NamespaceParameterReference
LANGUAGERFC 6350, Section 5.1
VALUERFC 6350, Section 5.2
PREFRFC 6350, Section 5.3
ALTIDRFC 6350, Section 5.4
PIDRFC 6350, Section 5.5
TYPERFC 6350, Section 5.6
MEDIATYPERFC 6350, Section 5.7
CALSCALERFC 6350, Section 5.8
SORT-ASRFC 6350, Section 5.9
GEORFC 6350, Section 5.10
TZRFC 6350, Section 5.11

-
11.3.4. Value Data Types Registry
The following table has been used to initialize the parameters
+
Table 4
NamespaceParameterReference
LANGUAGERFC 6350, Section 5.1
VALUERFC 6350, Section 5.2
PREFRFC 6350, Section 5.3
ALTIDRFC 6350, Section 5.4
PIDRFC 6350, Section 5.5
TYPERFC 6350, Section 5.6
MEDIATYPERFC 6350, Section 5.7
CALSCALERFC 6350, Section 5.8
SORT-ASRFC 6350, Section 5.9
GEORFC 6350, Section 5.10
TZRFC 6350, Section 5.11

+
11.3.4. Value Data Types Registry
The following table has been used to initialize the parameters
 registry.

-
Table 5
Value Data TypeReference
BOOLEANRFC 6350, Section 4.4
DATERFC 6350, Section 4.3.1
DATE-AND-OR-TIMERFC 6350, Section 4.3.4
DATE-TIMERFC 6350, Section 4.3.3
FLOATRFC 6350, Section 4.6
INTEGERRFC 6350, Section 4.5
LANGUAGE-TAGRFC 6350, Section 4.8
TEXTRFC 6350, Section 4.1
TIMERFC 6350, Section 4.3.2
TIMESTAMPRFC 6350, Section 4.3.5
URIRFC 6350, Section 4.2
UTC-OFFSETRFC 6350, Section 4.7

-
11.3.5. Values Registries
Separate tables are used for property and parameter values.

-
The following table is to be used to initialize the property values
+
Table 5
Value Data TypeReference
BOOLEANRFC 6350, Section 4.4
DATERFC 6350, Section 4.3.1
DATE-AND-OR-TIMERFC 6350, Section 4.3.4
DATE-TIMERFC 6350, Section 4.3.3
FLOATRFC 6350, Section 4.6
INTEGERRFC 6350, Section 4.5
LANGUAGE-TAGRFC 6350, Section 4.8
TEXTRFC 6350, Section 4.1
TIMERFC 6350, Section 4.3.2
TIMESTAMPRFC 6350, Section 4.3.5
URIRFC 6350, Section 4.2
UTC-OFFSETRFC 6350, Section 4.7

+
11.3.5. Values Registries
Separate tables are used for property and parameter values.

+
The following table is to be used to initialize the property values
 registry.

-
Table 6
PropertyValueReference
BEGINVCARDRFC 6350, Section 6.1.1
ENDVCARDRFC 6350, Section 6.1.2
KINDindividualRFC 6350, Section 6.1.4
KINDgroupRFC 6350, Section 6.1.4
KINDorgRFC 6350, Section 6.1.4
KINDlocationRFC 6350, Section 6.1.4

-
The following table has been used to initialize the parameter values
+
Table 6
PropertyValueReference
BEGINVCARDRFC 6350, Section 6.1.1
ENDVCARDRFC 6350, Section 6.1.2
KINDindividualRFC 6350, Section 6.1.4
KINDgroupRFC 6350, Section 6.1.4
KINDorgRFC 6350, Section 6.1.4
KINDlocationRFC 6350, Section 6.1.4

+
The following table has been used to initialize the parameter values
 registry.

-
Table 7
PropertyParameterValueReference
FN, NICKNAME, PHOTO,
+
Table 7
PropertyParameterValueReference
FN, NICKNAME, PHOTO,
  ADR, TEL, EMAIL, IMPP,
  LANG, TZ, GEO, TITLE,
  ROLE, LOGO, ORG,
@@ -4934,12 +4934,12 @@ registry.

       

       

         
Appendix A
(informative) 
Acknowledgments

-        
The authors would like to thank Tim Howes, Mark Smith, and Frank
+        
The authors would like to thank Tim Howes, Mark Smith, and Frank
 Dawson, the original authors of RFC 2425 and RFC 2426, 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:

-        
Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
+        
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,
@@ -4955,7 +4955,7 @@ Bortzmeyer, Tantek Celik, and Zoltan Ordogh.

       

       

         
Appendix B
(normative) 
Differences from RFCs 2425 and 2426

-        
This appendix contains a high-level overview of the major changes
+        
This appendix contains a high-level overview of the major changes
 that have been made in the vCard specification from RFC 2425 and
 RFC 2426.  It is incomplete, as it only lists the most important changes.

         
B.1. New Structure

@@ -5059,19 +5059,19 @@ property’s content.
 
 
 
-------=_NextPart_637b2d6b.2e1e.4ff6
+------=_NextPart_d46a03c1.e4cb.4e5e
 Content-Location: file:///C:/Doc/rfc6350_files/filelist.xml
 Content-Transfer-Encoding: base64
 Content-Type: application/xml
 
 PHhtbCB4bWxuczpvPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiPgog
 ICAgICAgIDxvOk1haW5GaWxlIEhSZWY9Ii4uL3JmYzYzNTAuaHRtIi8+ICA8bzpGaWxlIEhSZWY9
-IjY0MmRmMWU1LTZmMTMtNDRiOC1iNGJmLWVjMzFlNTNjYTBjMS5qcGciLz4KICA8bzpGaWxlIEhS
+IjIzYWNjZGQyLTBiODEtNDg3NS1hYmVhLWVmYzgzMWZhODU2Mi5qcGciLz4KICA8bzpGaWxlIEhS
 ZWY9ImZpbGVsaXN0LnhtbCIvPgogIDxvOkZpbGUgSFJlZj0iaGVhZGVyLmh0bWwiLz4KPC94bWw+
 Cg==
 
-------=_NextPart_637b2d6b.2e1e.4ff6
-Content-Location: file:///C:/Doc/rfc6350_files/642df1e5-6f13-44b8-b4bf-ec31e53ca0c1.jpg
+------=_NextPart_d46a03c1.e4cb.4e5e
+Content-Location: file:///C:/Doc/rfc6350_files/23accdd2-0b81-4875-abea-efc831fa8562.jpg
 Content-Transfer-Encoding: base64
 Content-Type: image/jpeg
 
@@ -8274,7 +8274,7 @@ AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD/9k=
 
-------=_NextPart_637b2d6b.2e1e.4ff6
+------=_NextPart_d46a03c1.e4cb.4e5e
 Content-Location: file:///C:/Doc/rfc6350_files/header.html
 Content-Transfer-Encoding: base64
 Content-Type: text/html charset="utf-8"
@@ -8377,7 +8377,7 @@ by1iaWRpLWZvbnQtc2l6ZToxMi4wcHQ7bXNvLWJpZGktZm9udC1mYW1pbHk6QXJpYWw7DQpiYWNr
 Z3JvdW5kOiNFMEUwRTAnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoN
 CjxkaXYgc3R5bGU9J21zby1lbGVtZW50OmhlYWRlcicgaWQ9ZmgxPg0KDQo8cCBjbGFzcz1Nc29I
 ZWFkZXI+PGltZyB3aWR0aD0iMzIzIiBoZWlnaHQ9IjM5IiBzcmM9J2ZpbGU6Ly8vQzovRG9jL3Jm
-YzYzNTBfZmlsZXMvMjkxOWFmM2MtOWY4NC00MGM2LWFmMGEtYjBjOTU1NzA4NDk2LmpwZyc+PC9p
+YzYzNTBfZmlsZXMvMGVjNDlhNzktYTk0OS00MWUyLWFiZjAtMDI2ZjJiYzYxZDMyLmpwZyc+PC9p
 bWc+DQo8IS0tW2lmIGd0ZSB2bWwgMV0+PHY6bGluZSBpZD0iX3gwMDAwX3MyMDQ5IiBhbHQ9IiIN
 CiBzdHlsZT0ncG9zaXRpb246YWJzb2x1dGU7ZmxpcDp5O3otaW5kZXg6MjUxNjU5MjY0O21zby13
 cmFwLXN0eWxlOm5vbmU7DQogbXNvLXdyYXAtZWRpdGVkOmY7bXNvLXdpZHRoLXBlcmNlbnQ6MDtt
@@ -8472,4 +8472,4 @@ ICA8cCBjbGFzcz1Nc29Gb290ZXI+JmNvcHk7IDIwMTggY29weXJpZ2h0IGJ5IHRoZSBNZXNzYWdp
 bmcsIE1hbHdhcmUgYW5kIE1vYmlsZSBBbnRpLUFidXNlIFdvcmtpbmcgR3JvdXAgKE0zQUFXRyk8
 L3A+DQo8L2Rpdj4NCg0KPC9ib2R5Pg0KDQo8L2h0bWw+DQo=
 
-------=_NextPart_637b2d6b.2e1e.4ff6--
\ No newline at end of file
+------=_NextPart_d46a03c1.e4cb.4e5e--
\ No newline at end of file
diff --git a/spec/examples/rfc6350.html b/spec/examples/rfc6350.html
index 9db9653..394096c 100644
--- a/spec/examples/rfc6350.html
+++ b/spec/examples/rfc6350.html
@@ -857,7 +857,7 @@
   

     

 
-  
+  
   

     

       RFC 6350
@@ -891,6 +891,18 @@
 

 
 
+  

+    Warning for Drafts
+
+    

+    This document is not an M3AAWG Standard. It is distributed for review and
+    comment, and is subject to change without notice and may not be referred to as
+    a Standard. Recipients of this draft are invited to submit, with their
+    comments, notification of any relevant patent rights of which they are aware
+    and to provide supporting documentation.
+    

+  

+
 
 

   

@@ -950,22 +962,22 @@ 
Contents

       

       

         
Foreword

-        
TBD

+        
TBD

       

       

       

         
Introduction

-        
General
Electronic address books have become ubiquitous.  Their increased
+        
General
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.

-
A high-level overview of the differences from RFC 2425 and RFC 2426 can
+
A high-level overview of the differences from RFC 2425 and RFC 2426 can
 be found in Appendix B.

         
Conventions

 
-  
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
+  
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
 "OPTIONAL" in this document are to be interpreted as described in
 RFC 2119.

@@ -974,7 +986,7 @@ 
Introduction

       
vCard Format Specification

       

         
1.  Scope

-        
This document defines the vCard data format for representing and
+        
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
@@ -1013,89 +1025,89 @@ 
2.  Normative references

         
4.  vCard Format Specification

         
4.1. General

 
-  
The text/vcard MIME content type (hereafter known as "vCard"; see
+  
The text/vcard MIME content type (hereafter known as "vCard"; see
 Clause 11.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.

 

         
4.2. Charset

 
-  
The charset (see RFC 3536 for internationalization terminology) for
+  
The charset (see RFC 3536 for internationalization terminology) for
 vCard is UTF-8 as defined in RFC 3629.  There is no way to override
 this.  It is invalid to specify a value other than "UTF-8" in the
 "charset" MIME parameter (see Clause 11.1).

 

-        
4.3. Line Delimiting and Folding
Individual lines within vCard are delimited by the RFC 5322 line
+        
4.3. Line Delimiting and Folding
Individual lines within vCard are delimited by the RFC 5322 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
 SHOULD be folded to a maximum width of 75 octets, excluding the line
 break.  Multi-octet characters MUST remain contiguous.  The rationale
 for this folding process can be found in RFC 5322, Section 2.1.1.

-
A logical line MAY be continued on the next physical line anywhere
+
A logical line MAY 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 MUST 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:

-

+

   
  NOTE:This is a long description that exists on a long line.

 

-
can be represented as:

-

+
can be represented as:

+

   
  NOTE:This is a long description
     that exists on a long line.

 

-
It could also be represented as:

-

+
It could also be represented as:

+

   
  NOTE:This is a long descrip
    tion that exists o
    n a long line.

 

-
The process of moving from this folded multiple-line representation
+
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).

-
Note: It is possible for very simple implementations to generate
+
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 SHOULD unfold lines in
 such a way as to properly restore the original sequence.

-
Note: Unfolding is done differently than in RFC 5322.  Unfolding
+
Note: Unfolding is done differently than in RFC 5322.  Unfolding
 in RFC 5322 only removes the CRLF, not the space following it.

-
Folding is done after any content encoding of a type value.
+
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.

-        
4.4. ABNF Format Definition
The following ABNF uses the notation of RFC 5234, which also defines
+        
4.4. ABNF Format Definition
The following ABNF uses the notation of RFC 5234, which also defines
 CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.

-
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 IETF RFC 3629

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

-
A line that begins with a white space character is a continuation of
+
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 IETF RFC 3629

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

+
A line that begins with a white space character is a continuation of
 the previous line, as described in Clause 4.3.  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 RFC 5322, in that the sequence
 <CRLF><WSP> found anywhere in the content indicates a continued line
 and should be removed.

-
Property names and parameter names are case-insensitive (e.g., the
+
Property names and parameter names are case-insensitive (e.g., the
 property name "fn" is the same as "FN" and "Fn").  Parameter values
 MAY 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 RECOMMENDED that property and
 parameter names be upper-case on output.

-
The group construct is used to group related properties together.
+
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 SHOULD be grouped
 together when displayed by an application.  It has no other
 significance.  Implementations that do not understand or support
 grouping MAY simply strip off any text before a "." to the left of
 the type name and present the types and values as normal.

-
Property cardinalities are indicated using the following notation,
+
Property cardinalities are indicated using the following notation,
 which is based on ABNF (see RFC 5234, Section 3.6):

-
Table 1
CardinalityMeaning
1Exactly one instance per vCard MUST be present.
*1Exactly one instance per vCard MAY be present.
1*One or more instances per vCard MUST be present.
*One or more instances per vCard MAY be present.

-
Properties defined in a vCard instance may have multiple values
+
Table 1
CardinalityMeaning
1Exactly one instance per vCard MUST be present.
*1Exactly one instance per vCard MAY be present.
1*One or more instances per vCard MUST be present.
*One or more instances per vCard MAY be present.

+
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
@@ -1103,84 +1115,84 @@ 
4.  vCard Format Specification

 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).

-        
4.5. Property Value Escaping
Some properties may contain one or more values delimited by a COMMA
+        
4.5. Property Value Escaping
Some properties may contain one or more values delimited by a COMMA
 character (U+002C).  Therefore, a COMMA character in a value MUST be
 escaped with a BACKSLASH character (U+005C), even for properties that
 don’t allow multiple instances (for consistency).

-
Some properties (e.g., N and ADR) comprise multiple fields delimited
+
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 MUST be escaped with a BACKSLASH
 character.  SEMICOLON characters in non-compound properties MAY 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.

-
Furthermore, some fields of compound properties may contain a list of
+
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’s values MUST be escaped with a BACKSLASH
 character, even for fields that don’t allow multiple values (for
 consistency).  Compound properties allowing multiple instances MUST NOT
 be encoded in a single content line.

-
Finally, BACKSLASH characters in values MUST be escaped with a
+
Finally, BACKSLASH characters in values MUST be escaped with a
 BACKSLASH character.  NEWLINE (U+000A) characters in values MUST be
 encoded by two characters: a BACKSLASH followed by either an 'n'
 (U+006E) or an 'N' (U+004E).

-
In all other cases, escaping MUST NOT be used.

+
In all other cases, escaping MUST NOT be used.

       

       

         
5.  Property Value Data Types

-        
5.1. General
Standard value types are defined below.

-
  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 IETF RFC 3986
        / 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 IETF RFC 5646, 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.

-        
5.2. TEXT
"text": The "text" value type should be used to identify values that
+        
5.1. General
Standard value types are defined below.

+
  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 IETF RFC 3986
        / 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 IETF RFC 5646, 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.

+        
5.2. TEXT
"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 Clause 6.2.

-
Examples for "text":

-

+
Examples for "text":

+

   
    this is a text value
     this is one value,this is another
     this is a single value\, with a comma encoded

 

-
A formatted text line break in a text value type MUST be represented
+
A formatted text line break in a text value type MUST 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".

-
For example, a multiple line NOTE value of:

-

+
For example, a multiple line NOTE value of:

+

   
    Mythical Manager
     Hyjinx Software Division
     BabsCo, Inc.

 

-
could be represented as:

-

+
could be represented as:

+

   
    NOTE:Mythical Manager\nHyjinx Software Division\n
      BabsCo\, Inc.\n

 

-
demonstrating the \n literal formatted line break technique, the
+
demonstrating the \n literal formatted line break technique, the
 CRLF-followed-by-space line folding technique, and the backslash
 escape technique.

-        
5.3. URI
"uri": The "uri" value type should be used to identify values that
+        
5.3. URI
"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 RFC 3986, Section 3.  Note
 that the value of a property of type "uri" is what the URI points to,
 not the URI itself.

-
Examples for "uri":

-

+
Examples for "uri":

+

   
    http://www.example.com/my/picture.jpg
     ldap://ldap.example.com/cn=babs%20jensen

 

-        
5.4. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP
5.4.1. General
"date", "time", "date-time", "date-and-or-time", and "timestamp":
+        
5.4. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP
5.4.1. General
"date", "time", "date-time", "date-and-or-time", and "timestamp":
 Each of these value types is based on the definitions in
 ISO 8601:2004.  Multiple such values can be specified using the
 comma-separated notation.

-
Only the basic format is supported.

-
5.4.2. DATE
A calendar date as specified in ISO 8601:2004, Clause 4.1.2].

-
Reduced accuracy, as specified in ISO 8601:2004, Clause 4.1.2.3 a)
+
Only the basic format is supported.

+
5.4.2. DATE
A calendar date as specified in ISO 8601:2004, Clause 4.1.2].

+
Reduced accuracy, as specified in ISO 8601:2004, Clause 4.1.2.3 a)
 and b), but not c), is permitted.

-
Expanded representation, as specified in ISO 8601:2004, Clause 4.1.4, is forbidden.

-
Truncated representation, as specified in ISO 8601:2004, Clause 5.2.1.3 d), e), and f), is permitted.

-
Examples for "date":

-

+
Expanded representation, as specified in ISO 8601:2004, Clause 4.1.4, is forbidden.

+
Truncated representation, as specified in ISO 8601:2004, Clause 5.2.1.3 d), e), and f), is permitted.

+
Examples for "date":

+

   
          19850412
           1985-04
           1985
@@ -1190,20 +1202,20 @@ 
5.  Property Value Data Types

 
 

 

-
Note the use of YYYY-MM in the second example above.  YYYYMM is
+
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.

-
5.4.3. TIME
A time of day as specified in ISO 8601:2004, Clause 4.2.

-
Reduced accuracy, as specified in ISO 8601:2004, Clause 4.2.2.3,
+
5.4.3. TIME
A time of day as specified in ISO 8601:2004, Clause 4.2.

+
Reduced accuracy, as specified in ISO 8601:2004, Clause 4.2.2.3,
 is permitted.

-
Representation with decimal fraction, as specified in
+
Representation with decimal fraction, as specified in
 ISO 8601:2004, Clause 4.2.2.4, is forbidden.

-
The midnight hour is always represented by 00, never 24 (see
+
The midnight hour is always represented by 00, never 24 (see
 ISO 8601:2004, Clause 4.2.3).

-
Truncated representation, as specified in ISO 8601:2000, Clause 5.3.1.4 a), b), and c), is permitted.

-
Examples for "time":

-

+
Truncated representation, as specified in ISO 8601:2000, Clause 5.3.1.4 a), b), and c), is permitted.

+
Examples for "time":

+

   
          102200
           1022
           10
@@ -1212,18 +1224,18 @@ 
5.  Property Value Data Types

           102200Z
           102200-0800

 

-
5.4.4. DATE-TIME
A date and time of day combination as specified in ISO 8601:2004, Clause 4.3.

-
Truncation of the date part, as specified in ISO 8601:2000, Clause 5.4.2 c), is permitted.

-
Examples for "date-time":

-

+
5.4.4. DATE-TIME
A date and time of day combination as specified in ISO 8601:2004, Clause 4.3.

+
Truncation of the date part, as specified in ISO 8601:2000, Clause 5.4.2 c), is permitted.

+
Examples for "date-time":

+

   
          19961022T140000
           --1022T1400
           ---22T14

 

-
5.4.5. DATE-AND-OR-TIME
Either a DATE-TIME, a DATE, or a TIME value.  To allow unambiguous
+
5.4.5. DATE-AND-OR-TIME
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".

-
Examples for "date-and-or-time":

-

+
Examples for "date-and-or-time":

+

   
          19961022T140000
           --1022T1400
           ---22T14
@@ -1240,53 +1252,53 @@ 
5.  Property Value Data Types

           T102200Z
           T102200-0800

 

-
5.4.6. TIMESTAMP
A complete date and time of day combination as specified in
+
5.4.6. TIMESTAMP
A complete date and time of day combination as specified in
 ISO 8601:2004, Clause 4.3.2.

-
Examples for "timestamp":

-

+
Examples for "timestamp":

+

   
          19961022T140000
           19961022T140000Z
           19961022T140000-05
           19961022T140000-0500

 

-        
5.5. BOOLEAN
"boolean": The "boolean" value type is used to express boolean
+        
5.5. BOOLEAN
"boolean": The "boolean" value type is used to express boolean
 values.  These values are case-insensitive.

-
Examples: 

-

+
Examples: 

+

   
    TRUE
     false
     True

 

-        
5.6. INTEGER
"integer": The "integer" value type is used to express signed
+        
5.6. INTEGER
"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’s-
 complement arithmetic.

-
Examples: 

-

+
Examples: 

+

   
    1234567890
     -1234556790
     +1234556790,432109876

 

-        
5.7. FLOAT
"float": The "float" value type is used to express real numbers.  If
+        
5.7. FLOAT
"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 MUST support a precision equal or better than that of
 the IEEE "binary64" format IEEE 754.

-
Note: Scientific notation is disallowed.  Implementers wishing to
+
Note: Scientific notation is disallowed.  Implementers wishing to
 use their favorite language’s %f formatting should be careful.

-
Examples: 

-

+
Examples: 

+

   
    20.30
     1000000.0000001
     1.333,3.14

 

-        
5.8. UTC-OFFSET
"utc-offset": The "utc-offset" value type specifies that the property
+        
5.8. UTC-OFFSET
"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.

-
The value type is an offset from Coordinated Universal Time (UTC).
+
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
@@ -1295,36 +1307,36 @@ 
5.  Property Value Data Types

 MUST be used.

         
5.9. LANGUAGE-TAG

 
-  
"language-tag": A single language tag, as defined in RFC 5646.

+  
"language-tag": A single language tag, as defined in RFC 5646.

 

       

       

         
6.  Property Parameters

-        
6.1. General
A property can have attributes associated with it.  These "property
+        
6.1. General
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).

-
Property parameter value elements that contain the COLON (U+003A),
+
Property parameter value elements that contain the COLON (U+003A),
 SEMICOLON (U+003B), or COMMA (U+002C) character separators MUST be
 specified as quoted-string text values.  Property parameter values
 MUST NOT contain the DQUOTE (U+0022) character.  The DQUOTE character
 is used as a delimiter for parameter values that contain restricted
 characters or URI text.

-
Applications MUST ignore x-param and iana-param values they don’t
+
Applications MUST ignore x-param and iana-param values they don’t
 recognize.

-        
6.2. LANGUAGE
The LANGUAGE property parameter is used to identify data in multiple
+        
6.2. LANGUAGE
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 RFC 3282.  The value of the LANGUAGE property parameter is a
 language tag as defined in RFC 5646, Section 2.

-
Examples: 

-

+
Examples: 

+

   
  ROLE;LANGUAGE=tr:hoca

 

-
ABNF: 

-
        language-param = "LANGUAGE=" Language-Tag
          ; Language-Tag is defined in section 2.1 of IETF RFC 5646

-        
6.3. VALUE
The VALUE parameter is OPTIONAL, used to identify the value type
+
ABNF: 

+
        language-param = "LANGUAGE=" Language-Tag
          ; Language-Tag is defined in section 2.1 of IETF RFC 5646

+        
6.3. VALUE
The VALUE parameter is OPTIONAL, 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,
@@ -1332,93 +1344,93 @@ 
6.  Property Parameters

 predefined data type values MUST NOT be repeated in COMMA-separated
 value lists except within the N, NICKNAME, ADR, and CATEGORIES
 properties.

-
ABNF: 

-
  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

-        
6.4. PREF
The PREF parameter is OPTIONAL and is used to indicate that the
+
ABNF: 

+
  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

+        
6.4. PREF
The PREF parameter is OPTIONAL and is used to indicate that the
 corresponding instance of a property is preferred by the vCard
 author.  Its value MUST 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.

-
When the parameter is absent, the default MUST be to interpret the
+
When the parameter is absent, the default MUST be to interpret the
 property instance as being least preferred.

-
Note that the value of this parameter is to be interpreted only in
+
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, MUST NOT
 be interpreted on its own.

-
This parameter MAY be applied to any property that allows multiple
+
This parameter MAY be applied to any property that allows multiple
 instances.

-
ABNF: 

-
        pref-param = "PREF=" (1*2DIGIT / "100")
                             ; An integer between 1 and 100.

-        
6.5. ALTID
The ALTID parameter is used to "tag" property instances as being
+
ABNF: 

+
        pref-param = "PREF=" (1*2DIGIT / "100")
                             ; An integer between 1 and 100.

+        
6.5. ALTID
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 (Clause 6.2)
 parameter that are tagged with the same ALTID value.

-
This parameter’s value is treated as an opaque string.  Its sole
+
This parameter’s value is treated as an opaque string.  Its sole
 purpose is to be compared for equality against other ALTID parameter
 values.

-
Two property instances are considered alternative representations of
+
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 MUST NOT be considered an alternative
 representation of any other property instance.  Values for the ALTID
 parameter are not globally unique: they MAY be reused for different
 property names.

-
Property instances having the same ALTID parameter value count as 1
+
Property instances having the same ALTID parameter value count as 1
 toward cardinality.  Therefore, since N (Clause 7.3.3) has
 cardinality *1 and TITLE (Clause 7.7.2) has cardinality *, these
 three examples would be legal:

-

+

   
  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.)

 

-

+

   
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE;ALTID=1;LANGUAGE=en:Boss

 

-

+

   
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE;ALTID=1;LANGUAGE=en:Boss
   TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist

 

-
while this one would not:

-

+
while this one would not:

+

   
  N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
   N:Yamada;Taro;;;
   (Two instances of the N property.)

 

-
and these three would be legal but questionable:

-

+
and these three would be legal but questionable:

+

   
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE;ALTID=2;LANGUAGE=en:Boss
   (Should probably have the same ALTID value.)

 

-

+

   
  TITLE;ALTID=1;LANGUAGE=fr:Patron
   TITLE:LANGUAGE=en:Boss
   (Second line should probably have ALTID=1.)

 

-

+

   
  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.)

 

-
The ALTID property MAY also be used in may contexts other than with
+
The ALTID property MAY also be used in may contexts other than with
 the LANGUAGE parameter.  Here’s an example with two representations
 of the same photo in different file formats:

-

+

   
  PHOTO;ALTID=1:data:image/jpeg;base64,...
   PHOTO;ALTID=1;data:image/jp2;base64,...
 
 
 

 

-
ABNF: 

-
        altid-param = "ALTID=" param-value

-        
6.6. PID
The PID parameter is used to identify a specific property among
+
ABNF: 

+
        altid-param = "ALTID=" param-value

+        
6.6. PID
The PID parameter is used to identify a specific property among
 multiple instances.  It plays a role analogous to the UID property
 (Clause 7.8.7) on a per-property instead of per-vCard basis.  It MAY
 appear more than once in a given property.  It MUST NOT appear on
@@ -1427,9 +1439,9 @@ 
6.  Property Parameters

 integers separated by a dot.  Multiple values may be encoded in a
 single PID parameter by separating the values with a comma ",".  See
 Clause 8 for more details on its usage.

-
ABNF: 

-
        pid-param = "PID=" pid-value *("," pid-value)
        pid-value = 1*DIGIT ["." 1*DIGIT]

-        
6.7. TYPE
The TYPE parameter has multiple, different uses.  In general, it is a
+
ABNF: 

+
        pid-param = "PID=" pid-value *("," pid-value)
        pid-value = 1*DIGIT ["." 1*DIGIT]

+        
6.7. TYPE
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
@@ -1438,16 +1450,16 @@ 
6.  Property Parameters

 NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI.  The TYPE
 parameter MUST NOT be applied on other properties defined in this
 document.

-
The "work" and "home" values act like tags.  The "work" value implies
+
The "work" and "home" values act like tags.  The "work" value implies
 that the property is related to an individual’s work place, while the
 "home" value implies that the property is related to an individual’s
 personal life.  When neither "work" nor "home" is present, it is
 implied that the property is related to both an individual’s work
 place and personal life in the case that the KIND property’s value is
 "individual", or to none in other cases.

-
ABNF: 

-
       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.

-        
6.8. MEDIATYPE
The MEDIATYPE parameter is used with properties whose value is a URI.
+
ABNF: 

+
       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.

+        
6.8. MEDIATYPE
The MEDIATYPE parameter is used with properties whose value is a URI.
 Its use is OPTIONAL.  It provides a hint to the vCard consumer
 application about the media type RFC 2046 of the resource identified
 by the URI.  Some URI schemes do not need this parameter.  For
@@ -1457,9 +1469,9 @@ 
6.  Property Parameters

 the Content-Type HTTP header RFC 2616.  The MEDIATYPE parameter is
 intended to be used with URI schemes that do not provide such
 functionality (e.g., "ftp" RFC 1738).

-
ABNF: 

-
  mediatype-param = "MEDIATYPE=" mediatype
  mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
    ; "attribute" and "value" are from IETF RFC 2045
    ; "type-name" and "subtype-name" are from [RFC4288]

-        
6.9. CALSCALE
The CALSCALE parameter is identical to the CALSCALE property in
+
ABNF: 

+
  mediatype-param = "MEDIATYPE=" mediatype
  mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
    ; "attribute" and "value" are from IETF RFC 2045
    ; "type-name" and "subtype-name" are from [RFC4288]

+        
6.9. CALSCALE
The CALSCALE parameter is identical to the CALSCALE property in
 iCalendar (see RFC 5545, 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
@@ -1468,47 +1480,47 @@ 
6.  Property Parameters

 registered with IANA (see Clause 11.3.5).  A vCard implementation
 MUST ignore properties with a CALSCALE parameter value that it does
 not understand.

-
ABNF: 

-
        calscale-param = "CALSCALE=" calscale-value

        calscale-value = "gregorian" / iana-token / x-name

-        
6.10. SORT-AS
The "sort-as" parameter is used to specify the string to be used for
+
ABNF: 

+
        calscale-param = "CALSCALE=" calscale-value

        calscale-value = "gregorian" / iana-token / x-name

+        
6.10. SORT-AS
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.

-
This parameter’s value is a comma-separated list that MUST have as
+
This parameter’s value is a comma-separated list that MUST have as
 many or fewer elements as the corresponding property value has
 components.  This parameter’s value is case-sensitive.

-
ABNF: 

-
  sort-as-param = "SORT-AS=" sort-as-value

  sort-as-value = param-value *("," param-value)

-
Examples: For the case of surname and given name sorting, the
+
ABNF: 

+
  sort-as-param = "SORT-AS=" sort-as-value

  sort-as-value = param-value *("," param-value)

+
Examples: For the case of surname and given name sorting, the
 following examples define common sort string usage with the N
 property.

-

+

   
        FN:Rene van der Harten
         N;SORT-AS="Harten,Rene":van der Harten;Rene,J.;Sir;R.D.O.N.

 

-

+

   
        FN:Robert Pau Shou Chang
         N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;

 

-

+

   
        FN:Osamu Koura
         N;SORT-AS="Koura,Osamu":Koura;Osamu;;

 

-

+

   
        FN:Oscar del Pozo
         N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;

 

-

+

   
        FN:Chistine d'Aboville
         N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;

 

-

+

   
        FN:H. James de Mann
         N;SORT-AS="Mann,James":de Mann;Henry,James;;

 

-
If sorted by surname, the results would be:

-

+
If sorted by surname, the results would be:

+

   
        Christine d'Aboville
         Rene van der Harten
         Osamu Koura
@@ -1516,8 +1528,8 @@ 
6.  Property Parameters

         Robert Pau Shou Chang
         Oscar del Pozo

 

-
If sorted by given name, the results would be:

-

+
If sorted by given name, the results would be:

+

   
        Christine d'Aboville
         H. James de Mann
         Osamu Koura
@@ -1525,36 +1537,36 @@ 
6.  Property Parameters

         Rene van der Harten
         Robert Pau Shou Chang

 

-        
6.11. GEO
The GEO parameter can be used to indicate global positioning
+        
6.11. GEO
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 Clause 7.6.3).

-
ABNF: 

-
  geo-parameter = "GEO=" DQUOTE URI DQUOTE

-        
6.12. TZ
The TZ parameter can be used to indicate time zone information that
+
ABNF: 

+
  geo-parameter = "GEO=" DQUOTE URI DQUOTE

+        
6.12. TZ
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.

-
ABNF: 

-
  tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)

+
ABNF: 

+
  tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)

       

       

         
7.  vCard Properties

         
7.1. General

 
-  
What follows is an enumeration of the standard vCard properties.

+  
What follows is an enumeration of the standard vCard properties.

 

         
7.2. General Properties
7.2.1. BEGIN

 
-  
Purpose: 

-    
To denote the beginning of a syntactic entity within a
+  
Purpose: 

+    
To denote the beginning of a syntactic entity within a
 text/vcard content-type.

   
Value type: 

-    
text

+    
text

   
Cardinality: 

-    
1

+    
1

   
Special notes: 

-    
The content entity MUST begin with the BEGIN property
+    
The content entity MUST begin with the BEGIN property
 with a value of "VCARD".  The value is case-insensitive.

-    
The BEGIN property is used in conjunction with the END property to
+    
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/
@@ -1563,24 +1575,24 @@ 
7.  vCard Properties

    the same text/vcard content-type or to define content that can be
    identifiable outside of a MIME environment.

   
ABNF: 

-    
  BEGIN-param = 0" "  ; no parameter allowed
  BEGIN-value = "VCARD"

+    
  BEGIN-param = 0" "  ; no parameter allowed
  BEGIN-value = "VCARD"

   
Example: 

-    

+    

   
      BEGIN:VCARD

 

   

 

-
7.2.2. END
Purpose: 

-    
To denote the end of a syntactic entity within a text/vcard
+
7.2.2. END
Purpose: 

+    
To denote the end of a syntactic entity within a text/vcard
 content-type.

   
Value type: 

-    
text

+    
text

   
Cardinality: 

-    
1

+    
1

   
Special notes: 

-    
The content entity MUST end with the END type with a
+    
The content entity MUST end with the END type with a
 value of "VCARD".  The value is case-insensitive.

-    
The END property is used in conjunction with the BEGIN property to
+    
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
@@ -1589,22 +1601,22 @@ 
7.  vCard Properties

    the same text/vcard content-type or to define content that can be
    identifiable outside of a MIME environment.

   
ABNF: 

-    
  END-param = 0" "  ; no parameter allowed
  END-value = "VCARD"

+    
  END-param = 0" "  ; no parameter allowed
  END-value = "VCARD"

   
Example: 

-

+

   
      END:VCARD

 

 
7.2.3. SOURCE

 
-  
Purpose: 

-    
To identify the source of directory information contained
+  
Purpose: 

+    
To identify the source of directory information contained
 in the content type.

   
Value type: 

-    
uri

+    
uri

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The SOURCE property is used to provide the means by
+    
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 RFC 3986
@@ -1614,28 +1626,28 @@ 
7.  vCard Properties

 considers to be the best source, or multiple SOURCE properties can
 be included.

   
ABNF: 

-    
  SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  SOURCE-value = URI

-  
Examples: 

+    
  SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  SOURCE-value = URI

+  
Examples: 

   
  SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US

 

-

+

   
  SOURCE:http://directory.example.com/addressbooks/jdoe/
    Jean%20Dupont.vcf

 

 

-
7.2.4. KIND
Purpose: 

-    
To specify the kind of object the vCard represents.

+
7.2.4. KIND
Purpose: 

+    
To specify the kind of object the vCard represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
The value may be one of the following:

+    
The value may be one of the following:

   
"individual" 

-    
for a vCard representing a single person or entity.
+    
for a vCard representing a single person or entity.
 This is the default kind of vCard.

   
"group" 

-    
for a vCard representing a group of persons or entities.
+    
for a vCard representing a group of persons or entities.
 The group’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
@@ -1643,46 +1655,46 @@ 
7.  vCard Properties

 without MEMBER properties can be considered an abstract
 grouping, or one whose members are known empirically (perhaps
 "IETF Participants" or "Republican U.S. Senators").

-    
All properties in a group vCard apply to the group as a whole,
+    
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.

   
"org" 

-    
for a vCard representing an organization.  An organization
+    
for a vCard representing an organization.  An organization
 vCard will not (in fact, MUST NOT) 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.

-    
All properties in an organization vCard apply to the
+    
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.

   
"location" 

-    
for a named geographical place.  A location vCard will
+    
for a named geographical place.  A location vCard will
 usually contain a GEO property, but it is not required to.  A
 location vCard without a GEO property can be considered an
 abstract location, or one whose definition is known empirically
 (perhaps "New England" or "The Seashore").

-    
All properties in a location vCard apply to the location
+    
All properties in a location vCard apply to the location
       itself, and not with any entity that might exist at that
       location.  For example, in a vCard for an office building, an
       ADR property might give the mailing address for the building,
       and a TEL property might specify the telephone number of the
       receptionist.

   
An x-name. 

-    
vCards MAY include private or experimental values for
+    
vCards MAY include private or experimental values for
 KIND.  Remember that x-name values are not intended for general
 use and are unlikely to interoperate.

   
An iana-token. 

-    
Additional values may be registered with IANA (see
+    
Additional values may be registered with IANA (see
 Clause 11.3.5).  A new value’s specification document MUST
 specify which properties make sense for that new kind of vCard
 and which do not.

   

-
Implementations MUST support the specific string values defined
+
Implementations MUST support the specific string values defined
    above.  If this property is absent, "individual" MUST be assumed
    as the default.  If this property is present but the
    implementation does not understand its value (the value is an
@@ -1691,7 +1703,7 @@ 
7.  vCard Properties

    means treating the vCard as though its kind were "individual".
    The presence of MEMBER properties MAY, however, be taken as an
    indication that the unknown kind is an extension of "group".

-
Clients often need to visually distinguish contacts based on what
+
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
@@ -1701,21 +1713,21 @@ 
7.  vCard Properties

    addition, a client might choose to segregate different kinds of
    vCards to different panes, tabs, or selections in the user
    interface.

-
Some clients might also make functional distinctions among the
+
Some clients might also make functional distinctions among the
    kinds, ignoring "location" vCards for some purposes and
    considering only "location" vCards for others.

-
When designing those sorts of visual and functional distinctions,
+
When designing those sorts of visual and functional distinctions,
    client implementations have to decide how to fit unsupported kinds
    into the scheme.  What icon is used for them?  The one for
    "individual"?  A unique one, such as an icon of a question mark?
    Which tab do they go into?  It is beyond the scope of this
    specification to answer these questions, but these are things
    implementers need to consider.

-
ABNF: 

-    
  KIND-param = "VALUE=text" / any-param
  KIND-value = "individual" / "group" / "org" / "location"
             / iana-token / x-name

-  
Example: 
This represents someone named Jane Doe working in the marketing
+
ABNF: 

+    
  KIND-param = "VALUE=text" / any-param
  KIND-value = "individual" / "group" / "org" / "location"
             / iana-token / x-name

+  
Example: 
This represents someone named Jane Doe working in the marketing
    department of the North American division of ABC Inc.

-

+

   
      BEGIN:VCARD
       VERSION:4.0
       KIND:individual
@@ -1723,9 +1735,9 @@ 
7.  vCard Properties

       ORG:ABC\, Inc.;North American Division;Marketing
       END:VCARD

 

-
This represents the department itself, commonly known as ABC
+
This represents the department itself, commonly known as ABC
 Marketing.

-

+

   
      BEGIN:VCARD
       VERSION:4.0
       KIND:org
@@ -1735,68 +1747,68 @@ 
7.  vCard Properties

 

 
7.2.5. XML

 
-  
Purpose: 

-    
To include extended XML-encoded vCard data in a plain
+  
Purpose: 

+    
To include extended XML-encoded vCard data in a plain
 vCard.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

-  
Special notes: 
The content of this property is a single XML 1.0
+    
*

+  
Special notes: 
The content of this property is a single XML 1.0
 W3C REC-xml-20081126 element whose namespace MUST be explicitly
 specified using the xmlns attribute and MUST NOT be the vCard 4
 namespace ("urn:ietf:params:xml:ns:vcard-4.0").  (This implies
 that it cannot duplicate a standard vCard property.)  The element
 is to be interpreted as if it was contained in a <vcard> element,
-as defined in RFC 6351.
The fragment is subject to normal line folding and escaping, i.e.,
+as defined in RFC 6351.
The fragment is subject to normal line folding and escaping, i.e.,
    replace all backslashes with "\\", then replace all newlines with
    "\n", then fold long lines.

-
Support for this property is OPTIONAL, but implementations of this
+
Support for this property is OPTIONAL, but implementations of this
    specification MUST preserve instances of this property when
    propagating vCards.

-
See RFC 6351 for more information on the intended use of this
+
See RFC 6351 for more information on the intended use of this
    property.
ABNF: 

-    
  XML-param = "VALUE=text" / altid-param
  XML-value = text

+    
  XML-param = "VALUE=text" / altid-param
  XML-value = text

   

 

         
7.3. Identification Properties
7.3.1. General

 
-  
These types are used to capture information associated with the
+  
These types are used to capture information associated with the
 identification and naming of the entity associated with the vCard.

 

 
7.3.2. FN

 
-  
Purpose: 

-    
To specify the formatted text corresponding to the name of
+  
Purpose: 

+    
To specify the formatted text corresponding to the name of
 the object the vCard represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
1*

+    
1*

   
Special notes: 

-    
This property is based on the semantics of the X.520
+    
This property is based on the semantics of the X.520
 Common Name attribute CCITT Recommendation X520.  The property MUST be
 present in the vCard object.

   
ABNF: 

-    
  FN-param = "VALUE=text" / type-param / language-param / altid-param
           / pid-param / pref-param / any-param
  FN-value = text

+    
  FN-param = "VALUE=text" / type-param / language-param / altid-param
           / pid-param / pref-param / any-param
  FN-value = text

   
Example: 

-    

+    

   
      FN:Mr. John Q. Public\, Esq.

 

   

 

 
7.3.3. N

 
-  
Purpose: 

-    
To specify the components of the name of the object the
+  
Purpose: 

+    
To specify the components of the name of the object the
 vCard represents.

   
Value type: 

-    
A single structured text value.  Each component can have
+    
A single structured text value.  Each component can have
 multiple values.

   
Cardinality: 

-    
*1

+    
*1

   
Special note: 

-    
The structured property value corresponds, in
+    
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
@@ -1806,11 +1818,11 @@ 
7.  vCard Properties

 name attributes CCITT Recommendation X520.  The property SHOULD be present
 in the vCard object when the name of the object the vCard
 represents follows the X.520 model.

-    
The SORT-AS parameter MAY be applied to this property.

+    
The SORT-AS parameter MAY be applied to this property.

   
ABNF: 

-    
  N-param = "VALUE=text" / sort-as-param / language-param
          / altid-param / any-param
  N-value = list-component 4(";" list-component)

+    
  N-param = "VALUE=text" / sort-as-param / language-param
          / altid-param / any-param
  N-value = list-component 4(";" list-component)

   
Examples: 

-    

+    

   
          N:Public;John;Quinlan;Mr.;Esq.
 
           N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.

@@ -1819,23 +1831,23 @@ 
7.  vCard Properties

 

 
7.3.4. NICKNAME

 
-  
Purpose: 

-    
To specify the text corresponding to the nickname of the
+  
Purpose: 

+    
To specify the text corresponding to the nickname of the
 object the vCard represents.

   
Value type: 

-    
One or more text values separated by a COMMA character
+    
One or more text values separated by a COMMA character
 (U+002C).

   
Cardinality: 

-    
*

+    
*

   
Special note: 

-    
The nickname is the descriptive name given instead of
+    
The nickname is the descriptive name given instead of
 or in addition to the one belonging to the object the vCard
 represents.  It can also be used to specify a familiar form of a
 proper name specified by the FN or N properties.

   
ABNF: 

-    
  NICKNAME-param = "VALUE=text" / type-param / language-param
                 / altid-param / pid-param / pref-param / any-param
  NICKNAME-value = text-list

+    
  NICKNAME-param = "VALUE=text" / type-param / language-param
                 / altid-param / pid-param / pref-param / any-param
  NICKNAME-value = text-list

   
Examples: 

-    

+    

   
          NICKNAME:Robbie
 
           NICKNAME:Jim,Jimmie
@@ -1846,17 +1858,17 @@ 
7.  vCard Properties

 

 
7.3.5. PHOTO

 
-  
Purpose: 

-    
To specify an image or photograph information that
+  
Purpose: 

+    
To specify an image or photograph information that
 annotates some aspect of the object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  PHOTO-param = "VALUE=uri" / altid-param / type-param
              / mediatype-param / pref-param / pid-param / any-param
  PHOTO-value = URI

+    
  PHOTO-param = "VALUE=uri" / altid-param / type-param
              / mediatype-param / pref-param / pid-param / any-param
  PHOTO-value = URI

   
Examples: 

-    

+    

   
    PHOTO:http://www.example.com/pub/photos/jqpublic.gif
 
     PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
@@ -1868,18 +1880,18 @@ 
7.  vCard Properties

 

 
7.3.6. BDAY

 
-  
Purpose: 

-    
To specify the birth date of the object the vCard
+  
Purpose: 

+    
To specify the birth date of the object the vCard
 represents.

   
Value type: 

-    
The default is a single date-and-or-time value.  It can
+    
The default is a single date-and-or-time value.  It can
 also be reset to a single text value.

   
Cardinality: 

-    
*1

+    
*1

   
ABNF: 

-    
  BDAY-param = BDAY-param-date / BDAY-param-text
  BDAY-value = date-and-or-time / text
    ; Value and parameter MUST match.

  BDAY-param-date = "VALUE=date-and-or-time"
  BDAY-param-text = "VALUE=text" / language-param

  BDAY-param =/ altid-param / calscale-param / any-param
    ; calscale-param can only be present when BDAY-value is
    ; date-and-or-time and actually contains a date or date-time.

+    
  BDAY-param = BDAY-param-date / BDAY-param-text
  BDAY-value = date-and-or-time / text
    ; Value and parameter MUST match.

  BDAY-param-date = "VALUE=date-and-or-time"
  BDAY-param-text = "VALUE=text" / language-param

  BDAY-param =/ altid-param / calscale-param / any-param
    ; calscale-param can only be present when BDAY-value is
    ; date-and-or-time and actually contains a date or date-time.

   
Examples: 

-    

+    

   
          BDAY:19960415
           BDAY:--0415
           BDAY;19531015T231000Z
@@ -1889,46 +1901,46 @@ 
7.  vCard Properties

 

 
7.3.7. ANNIVERSARY

 
-  
Purpose: 

-    
The date of marriage, or equivalent, of the object the
+  
Purpose: 

+    
The date of marriage, or equivalent, of the object the
 vCard represents.

   
Value type: 

-    
The default is a single date-and-or-time value.  It can
+    
The default is a single date-and-or-time value.  It can
 also be reset to a single text value.

   
Cardinality: 

-    
*1

+    
*1

   
ABNF: 

-    
  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.

+    
  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.

   
Examples: 

-    

+    

   
          ANNIVERSARY:19960415

 

   

 

 
7.3.8. GENDER

 
-  
Purpose: 

-    
To specify the components of the sex and gender identity of
+  
Purpose: 

+    
To specify the components of the sex and gender identity of
 the object the vCard represents.

   
Value type: 

-    
A single structured value with two components.  Each
+    
A single structured value with two components.  Each
 component has a single text value.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
The components correspond, in sequence, to the sex
+    
The components correspond, in sequence, to the sex
 (biological), and gender identity.  Each component is optional.

-    
Sex component: 

-    
A single letter.  M stands for "male", F stands
+    
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".

   
Gender identity component: 

-    
Free-form text.

+    
Free-form text.

   

   
ABNF: 

-    
                GENDER-param = "VALUE=text" / any-param
                GENDER-value = sex [";" text]

                sex = "" / "M" / "F" / "O" / "N" / "U"

+    
                GENDER-param = "VALUE=text" / any-param
                GENDER-value = sex [";" text]

                sex = "" / "M" / "F" / "O" / "N" / "U"

   
Examples: 

-    

+    

   
  GENDER:M
   GENDER:F
   GENDER:M;Fellow
@@ -1940,72 +1952,72 @@ 
7.  vCard Properties

 

         
7.4. Delivery Addressing Properties
7.4.1. General

 
-  
These types are concerned with information related to the delivery
+  
These types are concerned with information related to the delivery
 addressing or label for the vCard object.

 

-
7.4.2. ADR
Purpose: 

-    
To specify the components of the delivery address for the
+
7.4.2. ADR
Purpose: 

+    
To specify the components of the delivery address for the
 vCard object.

   
Value type: 

-    
A single structured text value, separated by the
+    
A single structured text value, separated by the
 SEMICOLON character (U+003B).

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The structured type value consists of a sequence of
+    
The structured type value consists of a sequence of
 address components.  The component values MUST be specified in
 their corresponding position.  The structured type value
 corresponds, in sequence, to

-    
    
+    
      
   
    • 
-    
      the post office box;
      
+    
      the post office box;
      
   
      • 
   
    • 
-    
      the extended address (e.g., apartment or suite number);
      
+    
      the extended address (e.g., apartment or suite number);
      
   
      • 
   
    • 
-    
      the street address;
      
+    
      the street address;
      
   
      • 
   
    • 
-    
      the locality (e.g., city);
      
+    
      the locality (e.g., city);
      
   
      • 
   
    • 
-    
      the region (e.g., state or province);
      
+    
      the region (e.g., state or province);
      
   
      • 
   
    • 
-    
      the postal code;
      
+    
      the postal code;
      
   
      • 
   
    • 
-    
      the country name (full name in the language specified in
+    
      the country name (full name in the language specified in
 Clause 6.2).
      
   
      • 
 
    
   

-
When a component value is missing, the associated component
+
When a component value is missing, the associated component
    separator MUST still be specified.

-
Experience with vCard 3 has shown that the first two components
+
Experience with vCard 3 has shown that the first two components
    (post office box and extended address) are plagued with many
    interoperability issues.  To ensure maximal interoperability,
    their values SHOULD be empty.

-
The text components are separated by the SEMICOLON character
+
The text components are separated by the SEMICOLON character
    (U+003B).  Where it makes semantic sense, individual text
    components can include multiple text values (e.g., a "street"
    component with multiple lines) separated by the COMMA character
    (U+002C).

-
The property can include the "PREF" parameter to indicate the
+
The property can include the "PREF" parameter to indicate the
    preferred delivery address when more than one address is
    specified.

-
The GEO and TZ parameters MAY be used with this property.

-
The property can also include a "LABEL" parameter to present a
+
The GEO and TZ parameters MAY be used with this property.

+
The property can also include a "LABEL" parameter to present a
    delivery address label for the address.  Its value is a plain-text
    string representing the formatted address.  Newlines are encoded
    as \n, as they are for property values.

-
ABNF: 

-    
  label-param = "LABEL=" param-value

  ADR-param = "VALUE=text" / label-param / language-param
            / geo-parameter / tz-parameter / altid-param / pid-param
            / pref-param / type-param / any-param

  ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
              ADR-component-street ";" ADR-component-locality ";"
              ADR-component-region ";" ADR-component-code ";"
              ADR-component-country
  ADR-component-pobox    = list-component
  ADR-component-ext      = list-component
  ADR-component-street   = list-component
  ADR-component-locality = list-component
  ADR-component-region   = list-component
  ADR-component-code     = list-component
  ADR-component-country  = list-component

+
ABNF: 

+    
  label-param = "LABEL=" param-value

  ADR-param = "VALUE=text" / label-param / language-param
            / geo-parameter / tz-parameter / altid-param / pid-param
            / pref-param / type-param / any-param

  ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
              ADR-component-street ";" ADR-component-locality ";"
              ADR-component-region ";" ADR-component-code ";"
              ADR-component-country
  ADR-component-pobox    = list-component
  ADR-component-ext      = list-component
  ADR-component-street   = list-component
  ADR-component-locality = list-component
  ADR-component-region   = list-component
  ADR-component-code     = list-component
  ADR-component-country  = list-component

   
Example: 

-    
In this example, the post office box and the extended
+    
In this example, the post office box and the extended
 address are absent.

-    

+    

   
  ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n
    Mail Drop: TNE QB\n123 Main Street\nAny Town, CA  91921-1234\n
    U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.

@@ -2013,66 +2025,66 @@ 
7.  vCard Properties

   

         
7.5. Communications Properties
7.5.1. General

 
-  
These properties describe information about how to communicate with
+  
These properties describe information about how to communicate with
 the object the vCard represents.

 

-
7.5.2. TEL
Purpose: 

-    
To specify the telephone number for telephony communication
+
7.5.2. TEL
Purpose: 

+    
To specify the telephone number for telephony communication
 with the object the vCard represents.

   
Value type: 

-    
By default, it is a single free-form text value (for
+    
By default, it is a single free-form text value (for
 backward compatibility with vCard 3), but it SHOULD be reset to a
 URI value.  It is expected that the URI scheme will be "tel", as
 specified in RFC 3966, but other schemes MAY be used.

   
Cardinality: 

-    
*

-  
Special notes: 
This property is based on the X.520 Telephone Number
-attribute CCITT Recommendation X520.
The property can include the "PREF" parameter to indicate a
+    
*

+  
Special notes: 
This property is based on the X.520 Telephone Number
+attribute CCITT Recommendation X520.
The property can include the "PREF" parameter to indicate a
    preferred-use telephone number.

-
The property can include the parameter "TYPE" to specify intended
+
The property can include the parameter "TYPE" to specify intended
    use for the telephone number.  The predefined values for the TYPE
    parameter are:

-
Table 2
ValueDescription
textIndicates that the telephone number supports text messages (SMS).
voiceIndicates a voice telephone number.
faxIndicates a facsimile telephone number.
cellIndicates a cellular or mobile telephone number.
videoIndicates a video conferencing telephone number.
pagerIndicates a paging device telephone number.
textphoneIndicates a telecommunication device for people with  hearing or speech difficulties.

-
The default type is "voice".  These type parameter values can be
+
Table 2
ValueDescription
textIndicates that the telephone number supports text messages (SMS).
voiceIndicates a voice telephone number.
faxIndicates a facsimile telephone number.
cellIndicates a cellular or mobile telephone number.
videoIndicates a video conferencing telephone number.
pagerIndicates a paging device telephone number.
textphoneIndicates a telecommunication device for people with  hearing or speech difficulties.

+
The default type is "voice".  These type parameter values can be
    specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a
    value list (e.g., TYPE="text,voice").  The default can be
    overridden to another set of values by specifying one or more
    alternate values.  For example, the default TYPE of "voice" can be
    reset to a VOICE and FAX telephone number by the value list
    TYPE="voice,fax".

-
If this property’s value is a URI that can also be used for
+
If this property’s value is a URI that can also be used for
    instant messaging, the IMPP (Clause 7.5.4) property SHOULD be
    used in addition to this property.

-
ABNF: 

-    
  TEL-param = TEL-text-param / TEL-uri-param
  TEL-value = TEL-text-value / TEL-uri-value
    ; Value and parameter MUST match.

  TEL-text-param = "VALUE=text"
  TEL-text-value = text

  TEL-uri-param = "VALUE=uri" / mediatype-param
  TEL-uri-value = URI

  TEL-param =/ type-param / pid-param / pref-param / altid-param
             / any-param

  type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
                 / "pager" / "textphone" / iana-token / x-name
    ; type-param-tel MUST NOT be used with a property other than TEL.

+
ABNF: 

+    
  TEL-param = TEL-text-param / TEL-uri-param
  TEL-value = TEL-text-value / TEL-uri-value
    ; Value and parameter MUST match.

  TEL-text-param = "VALUE=text"
  TEL-text-value = text

  TEL-uri-param = "VALUE=uri" / mediatype-param
  TEL-uri-value = URI

  TEL-param =/ type-param / pid-param / pref-param / altid-param
             / any-param

  type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
                 / "pager" / "textphone" / iana-token / x-name
    ; type-param-tel MUST NOT be used with a property other than TEL.

   
Example: 

-    

+    

   
  TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555
   TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67

 

   

 
7.5.3. EMAIL

 
-  
Purpose: 

-    
To specify the electronic mail address for communication
+  
Purpose: 

+    
To specify the electronic mail address for communication
 with the object the vCard represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The property can include tye "PREF" parameter to
+    
The property can include tye "PREF" parameter to
 indicate a preferred-use email address when more than one is
 specified.

-    
Even though the value is free-form UTF-8 text, it is likely to be
+    
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 RFC 5322, Section 3.4.1.  Readers should also be aware
    of the current work toward internationalized email addresses
    RFC 5335.

   
ABNF: 

-    
  EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
              / altid-param / any-param
  EMAIL-value = text

+    
  EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
              / altid-param / any-param
  EMAIL-value = text

   
Example: 

-    

+    

   
        EMAIL;TYPE=work:jqpublic@xyz.example.com
 
         EMAIL;PREF=1:jane_doe@example.com

@@ -2081,40 +2093,40 @@ 
7.  vCard Properties

 

 
7.5.4. IMPP

 
-  
Purpose: 

-    
To specify the URI for instant messaging and presence
+  
Purpose: 

+    
To specify the URI for instant messaging and presence
 protocol communications with the object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

-  
Special notes: 
The property may include the "PREF" parameter to
+    
*

+  
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.
If this property’s value is a URI that can be used for voice
+semantics as the "PREF" parameter in a TEL property.
If this property’s value is a URI that can be used for voice
 and/or video, the TEL property (Clause 7.5.2) SHOULD be used in
 addition to this property.

-
This property is adapted from RFC 4770, which is made obsolete by
+
This property is adapted from RFC 4770, which is made obsolete by
    this document.
ABNF: 

-    
  IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
             / mediatype-param / altid-param / any-param
  IMPP-value = URI

+    
  IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
             / mediatype-param / altid-param / any-param
  IMPP-value = URI

   
Example: 

-    

+    

   
    IMPP;PREF=1:xmpp:alice@example.com

 

   

 

 
7.5.5. LANG

 
-  
Purpose: 

-    
To specify the language(s) that may be used for contacting
+  
Purpose: 

+    
To specify the language(s) that may be used for contacting
 the entity associated with the vCard.

   
Value type: 

-    
A single language-tag value.

+    
A single language-tag value.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  LANG-param = "VALUE=language-tag" / pid-param / pref-param
             / altid-param / type-param / any-param
  LANG-value = Language-Tag

+    
  LANG-param = "VALUE=language-tag" / pid-param / pref-param
             / altid-param / type-param / any-param
  LANG-value = Language-Tag

   
Example: 

-    

+    

   
    LANG;TYPE=work;PREF=1:en
     LANG;TYPE=work;PREF=2:fr
     LANG;TYPE=home:fr

@@ -2123,34 +2135,34 @@ 
7.  vCard Properties

 

         
7.6. Geographical Properties
7.6.1. General

 
-  
These properties are concerned with information associated with
+  
These properties are concerned with information associated with
 geographical positions or regions associated with the object the
 vCard represents.

 

 
7.6.2. TZ

 
-  
Purpose: 

-    
To specify information related to the time zone of the
+  
Purpose: 

+    
To specify information related to the time zone of the
 object the vCard represents.

   
Value type: 

-    
The default is a single text value.  It can also be
+    
The default is a single text value.  It can also be
 reset to a single URI or utc-offset value.

   
Cardinality: 

-    
*

-  
Special notes: 
It is expected that names from the public-domain
+    
*

+  
Special notes: 
It is expected that names from the public-domain
 Olson database TZ-DB will be used, but this is not a
-restriction.  See also IANA TZ.
Efforts are currently being directed at creating a standard URI
+restriction.  See also IANA TZ.
Efforts are currently being directed at creating a standard URI
    scheme for expressing time zone information.  Usage of such a
    scheme would ensure a high level of interoperability between
    implementations that support it.

-
Note that utc-offset values SHOULD NOT be used because the UTC
+
Note that utc-offset values SHOULD NOT be used because the UTC
    offset varies with time — not just because of the usual daylight
    saving time shifts that occur in may regions, but often entire
    regions will "re-base" their overall offset.  The actual offset
    may be +/- 1 hour (or perhaps a little more) than the one given.
ABNF: 

-    
  TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
  TZ-value = text / URI / utc-offset
    ; Value and parameter MUST match.

  TZ-param =/ altid-param / pid-param / pref-param / type-param
            / mediatype-param / any-param

+    
  TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
  TZ-value = text / URI / utc-offset
    ; Value and parameter MUST match.

  TZ-param =/ altid-param / pid-param / pref-param / type-param
            / mediatype-param / any-param

   
Examples: 

-    

+    

   
  TZ:Raleigh/North America
 
   TZ;VALUE=utc-offset:-0500
@@ -2160,80 +2172,80 @@ 
7.  vCard Properties

 

 
7.6.3. GEO

 
-  
Purpose: 

-    
To specify information related to the global positioning of
+  
Purpose: 

+    
To specify information related to the global positioning of
 the object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The "geo" URI scheme RFC 5870 is particularly well
+    
The "geo" URI scheme RFC 5870 is particularly well
 suited for this property, but other schemes MAY be used.

   
ABNF: 

-    
  GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  GEO-value = URI

+    
  GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  GEO-value = URI

   
Example: 

-    

+    

   
        GEO:geo:37.386013,-122.082932

 

   

 

         
7.7. Organizational Properties
7.7.1. General

 
-  
These properties are concerned with information associated with
+  
These properties are concerned with information associated with
 characteristics of the organization or organizational units of the
 object that the vCard represents.

 

-
7.7.2. TITLE
Purpose: 

-    
To specify the position or job of the object the vCard
+
7.7.2. TITLE
Purpose: 

+    
To specify the position or job of the object the vCard
 represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   

-
Cardinality:  *

-
Special notes: 

-    
This property is based on the X.520 Title attribute
+
Cardinality:  *

+
Special notes: 

+    
This property is based on the X.520 Title attribute
 CCITT Recommendation X520.

   
ABNF: 

-    
  TITLE-param = "VALUE=text" / language-param / pid-param
              / pref-param / altid-param / type-param / any-param
  TITLE-value = text

+    
  TITLE-param = "VALUE=text" / language-param / pid-param
              / pref-param / altid-param / type-param / any-param
  TITLE-value = text

   
Example: 

-    

+    

   
        TITLE:Research Scientist

 

   

-
7.7.3. ROLE
Purpose: 

-    
To specify the function or part played in a particular
+
7.7.3. ROLE
Purpose: 

+    
To specify the function or part played in a particular
 situation by the object the vCard represents.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

+    
*

   

-
Special notes:  This property is based on the X.520 Business Category
+
Special notes:  This property is based on the X.520 Business Category
    explanatory attribute CCITT Recommendation X520.  This property is
    included as an organizational type to avoid confusion with the
    semantics of the TITLE property and incorrect usage of that
    property when the semantics of this property is intended.

-
ABNF: 

-    
  ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  ROLE-value = text

+
ABNF: 

+    
  ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  ROLE-value = text

   
Example: 

-    

+    

   
        ROLE:Project Leader

 

   

 
7.7.4. LOGO

 
-  
Purpose: 

-    
To specify a graphic image of a logo associated with the
+  
Purpose: 

+    
To specify a graphic image of a logo associated with the
 object the vCard represents.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
             / type-param / mediatype-param / altid-param / any-param
  LOGO-value = URI

+    
  LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
             / type-param / mediatype-param / altid-param / any-param
  LOGO-value = URI

   
Examples: 

-    

+    

   
  LOGO:http://www.example.com/pub/logos/abccorp.jpg
 
   LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
@@ -2245,47 +2257,47 @@ 
7.  vCard Properties

 

 
7.7.5. ORG

 
-  
Purpose: 

-    
To specify the organizational name and units associated
+  
Purpose: 

+    
To specify the organizational name and units associated
 with the vCard.

   
Value type: 

-    
A single structured text value consisting of components
+    
A single structured text value consisting of components
 separated by the SEMICOLON character (U+003B).

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The property is based on the X.520 Organization Name
+    
The property is based on the X.520 Organization Name
 and Organization Unit attributes CCITT Recommendation X520.  The property
 value is a structured type consisting of the organization name,
 followed by zero or more levels of organizational unit names.

-    
The SORT-AS parameter MAY be applied to this property.

+    
The SORT-AS parameter MAY be applied to this property.

   
ABNF: 

-    
  ORG-param = "VALUE=text" / sort-as-param / language-param
            / pid-param / pref-param / altid-param / type-param
            / any-param
  ORG-value = component *(";" component)

+    
  ORG-param = "VALUE=text" / sort-as-param / language-param
            / pid-param / pref-param / altid-param / type-param
            / any-param
  ORG-value = component *(";" component)

   
Example: 

-    
A property value consisting of an organizational name,
+    
A property value consisting of an organizational name,
 organizational unit #1 name, and organizational unit #2 name.

-    

+    

   
        ORG:ABC\, Inc.;North American Division;Marketing

 

   

 

 
7.7.6. MEMBER

 
-  
Purpose: 

-    
To include a member in the group this vCard represents.

+  
Purpose: 

+    
To include a member in the group this vCard represents.

   
Value type: 

-    
A single URI.  It MAY refer to something other than a
+    
A single URI.  It MAY refer to something other than a
 vCard object.  For example, an email distribution list could
 employ the "mailto" URI scheme RFC 6068 for efficiency.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
This property MUST NOT be present unless the value of
+    
This property MUST NOT be present unless the value of
 the KIND property is "group".

   
ABNF: 

-    
  MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  MEMBER-value = URI

+    
  MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
               / mediatype-param / any-param
  MEMBER-value = URI

   
Examples: 

-    

+    

   
  BEGIN:VCARD
   VERSION:4.0
   KIND:group
@@ -2318,30 +2330,30 @@ 
7.  vCard Properties

 

 
7.7.7. RELATED

 
-  
Purpose: 

-    
To specify a relationship between another entity and the
+  
Purpose: 

+    
To specify a relationship between another entity and the
 entity represented by this vCard.

   
Value type: 

-    
A single URI.  It can also be reset to a single text
+    
A single URI.  It can also be reset to a single text
 value.  The text value can be used to specify textual information.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
The TYPE parameter MAY be used to characterize the
+    
The TYPE parameter MAY be used to characterize the
 related entity.  It contains a comma-separated list of values that
 are registered with IANA as described in Clause 11.2.  The
 registry is pre-populated with the values defined in XFN.  This
 document also specifies two additional values:

-    
agent: 

-    
an entity who may sometimes act on behalf of the entity
+    
agent: 

+    
an entity who may sometimes act on behalf of the entity
 associated with the vCard.

   
emergency: 

-    
indicates an emergency contact

+    
indicates an emergency contact

   

   
ABNF: 

-    
  RELATED-param = RELATED-param-uri / RELATED-param-text
  RELATED-value = URI / text
    ; Parameter and value MUST match.

  RELATED-param-uri = "VALUE=uri" / mediatype-param
  RELATED-param-text = "VALUE=text" / language-param

  RELATED-param =/ pid-param / pref-param / altid-param / type-param
                 / any-param

  type-param-related = related-type-value *("," related-type-value)
    ; type-param-related MUST NOT be used with a property other than
    ; RELATED.

  related-type-value = "contact" / "acquaintance" / "friend" / "met"
                     / "co-worker" / "colleague" / "co-resident"
                     / "neighbor" / "child" / "parent"
                     / "sibling" / "spouse" / "kin" / "muse"
                     / "crush" / "date" / "sweetheart" / "me"
                     / "agent" / "emergency"

+    
  RELATED-param = RELATED-param-uri / RELATED-param-text
  RELATED-value = URI / text
    ; Parameter and value MUST match.

  RELATED-param-uri = "VALUE=uri" / mediatype-param
  RELATED-param-text = "VALUE=text" / language-param

  RELATED-param =/ pid-param / pref-param / altid-param / type-param
                 / any-param

  type-param-related = related-type-value *("," related-type-value)
    ; type-param-related MUST NOT be used with a property other than
    ; RELATED.

  related-type-value = "contact" / "acquaintance" / "friend" / "met"
                     / "co-worker" / "colleague" / "co-resident"
                     / "neighbor" / "child" / "parent"
                     / "sibling" / "spouse" / "kin" / "muse"
                     / "crush" / "date" / "sweetheart" / "me"
                     / "agent" / "emergency"

   
Examples: 

-    

+    

   
RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
 RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf
 RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane
@@ -2351,104 +2363,104 @@ 
7.  vCard Properties

 

         
7.8. Explanatory Properties
7.8.1. General

 
-  
These properties are concerned with additional explanations, such as
+  
These properties are concerned with additional explanations, such as
 that related to informational notes or revisions specific to the
 vCard.

 

 
7.8.2. CATEGORIES

 
-  
Purpose: 

-    
To specify application category information about the
+  
Purpose: 

+    
To specify application category information about the
 vCard, also known as "tags".

   
Value type: 

-    
One or more text values separated by a COMMA character
+    
One or more text values separated by a COMMA character
 (U+002C).

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  CATEGORIES-param = "VALUE=text" / pid-param / pref-param
                   / type-param / altid-param / any-param
  CATEGORIES-value = text-list

+    
  CATEGORIES-param = "VALUE=text" / pid-param / pref-param
                   / type-param / altid-param / any-param
  CATEGORIES-value = text-list

   
Example: 

-    

+    

   
        CATEGORIES:TRAVEL AGENT
 
         CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY

 

   

 

-
7.8.3. NOTE
Purpose: 

-    
To specify supplemental information or a comment that is
+
7.8.3. NOTE
Purpose: 

+    
To specify supplemental information or a comment that is
 associated with the vCard.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*

+    
*

   

-
Special notes:  The property is based on the X.520 Description
+
Special notes:  The property is based on the X.520 Description
    attribute CCITT Recommendation X520.

-
ABNF: 

-    
  NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  NOTE-value = text

+
ABNF: 

+    
  NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
             / type-param / altid-param / any-param
  NOTE-value = text

   
Example: 

-    

+    

   
        NOTE:This fax number is operational 0800 to 1715
           EST\, Mon-Fri.

 

   

 
7.8.4. PRODID

 
-  
Purpose: 

-    
To specify the identifier for the product that created the
+  
Purpose: 

+    
To specify the identifier for the product that created the
 vCard object.

   
Type value: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
Implementations SHOULD use a method such as that
+    
Implementations SHOULD use a method such as that
 specified for Formal Public Identifiers in ISO 9070 or for
 Universal Resource Names in RFC 3406 to ensure that the text
 value is unique.

   
ABNF: 

-    
  PRODID-param = "VALUE=text" / any-param
  PRODID-value = text

+    
  PRODID-param = "VALUE=text" / any-param
  PRODID-value = text

   
Example: 

-    

+    

   
        PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN

 

   

 

 
7.8.5. REV

 
-  
Purpose: 

-    
To specify revision information about the current vCard.

+  
Purpose: 

+    
To specify revision information about the current vCard.

   
Value type: 

-    
A single timestamp value.

+    
A single timestamp value.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
The value distinguishes the current revision of the
+    
The value distinguishes the current revision of the
 information in this vCard for other renditions of the information.

   
ABNF: 

-    
  REV-param = "VALUE=timestamp" / any-param
  REV-value = timestamp

+    
  REV-param = "VALUE=timestamp" / any-param
  REV-value = timestamp

   
Example: 

-    

+    

   
        REV:19951031T222710Z

 

   

 

 
7.8.6. SOUND

 
-  
Purpose: 

-    
To specify a digital sound content information that
+  
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.

   
Value type: 

-    
A single URI.

+    
A single URI.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
              / type-param / mediatype-param / altid-param
              / any-param
  SOUND-value = URI

+    
  SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
              / type-param / mediatype-param / altid-param
              / any-param
  SOUND-value = URI

   
Example: 

-    

+    

   
  SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
 
   SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
@@ -2460,51 +2472,51 @@ 
7.  vCard Properties

 

 
7.8.7. UID

 
-  
Purpose: 

-    
To specify a value that represents a globally unique
+  
Purpose: 

+    
To specify a value that represents a globally unique
 identifier corresponding to the entity associated with the vCard.

   
Value type: 

-    
A single URI value.  It MAY also be reset to free-form
+    
A single URI value.  It MAY also be reset to free-form
 text.

   
Cardinality: 

-    
*1

+    
*1

   
Special notes: 

-    
This property is used to uniquely identify the object
+    
This property is used to uniquely identify the object
 that the vCard represents.  The "uuid" URN namespace defined in
 RFC 4122 is particularly well suited to this task, but other URI
 schemes MAY be used.  Free-form text MAY also be used.

   
ABNF: 

-    
  UID-param = UID-uri-param / UID-text-param
  UID-value = UID-uri-value / UID-text-value
    ; Value and parameter MUST match.

  UID-uri-param = "VALUE=uri"
  UID-uri-value = URI

  UID-text-param = "VALUE=text"
  UID-text-value = text

  UID-param =/ any-param

+    
  UID-param = UID-uri-param / UID-text-param
  UID-value = UID-uri-value / UID-text-value
    ; Value and parameter MUST match.

  UID-uri-param = "VALUE=uri"
  UID-uri-value = URI

  UID-text-param = "VALUE=text"
  UID-text-value = text

  UID-param =/ any-param

   
Example: 

-    

+    

   
        UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

 

   

 

 
7.8.8. CLIENTPIDMAP

 
-  
Purpose: 

-    
To give a global meaning to a local PID source identifier.

+  
Purpose: 

+    
To give a global meaning to a local PID source identifier.

   
Value type: 

-    
A semicolon-separated pair of values.  The first field
+    
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 RFC 4122 is particularly well suited to this
 task, but other URI schemes MAY be used.

   
Cardinality: 

-    
*

-  
Special notes: 
PID source identifiers (the source identifier is the
+    
*

+  
Special notes: 
PID source identifiers (the source identifier is the
 second field in a PID parameter instance) are small integers that
 only have significance within the scope of a single vCard
 instance.  Each distinct source identifier present in a vCard MUST
 have an associated CLIENTPIDMAP.  See Clause 8 for more details
-on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive.  Zero is not
+on the usage of CLIENTPIDMAP.
PID source identifiers MUST be strictly positive.  Zero is not
    allowed.

-
As a special exception, the PID parameter MUST NOT be applied to
+
As a special exception, the PID parameter MUST NOT be applied to
    this property.
ABNF: 

-    
  CLIENTPIDMAP-param = any-param
  CLIENTPIDMAP-value = 1*DIGIT ";" URI

+    
  CLIENTPIDMAP-param = any-param
  CLIENTPIDMAP-value = 1*DIGIT ";" URI

   
Example: 

-    

+    

   
  TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
   EMAIL;PID=4.1,5.2:jdoe@example.com
   CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
@@ -2514,64 +2526,64 @@ 
7.  vCard Properties

 

 
7.8.9. URL

 
-  
Purpose: 

-    
To specify a uniform resource locator associated with the
+  
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.

   
Cardinality: 

-    
*

+    
*

   
Value type: 

-    
A single uri value.

+    
A single uri value.

   
ABNF: 

-    
  URL-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  URL-value = URI

+    
  URL-param = "VALUE=uri" / pid-param / pref-param / type-param
            / mediatype-param / altid-param / any-param
  URL-value = URI

   
Example: 

-    

+    

   
        URL:http://example.org/restaurant.french/~chezchic.html

 

   

 

 
7.8.10. VERSION

 
-  
Purpose: 

-    
To specify the version of the vCard specification used to
+  
Purpose: 

+    
To specify the version of the vCard specification used to
 format this vCard.

   
Value type: 

-    
A single text value.

+    
A single text value.

   
Cardinality: 

-    
1

+    
1

   
Special notes: 

-    
This property MUST be present in the vCard object,
+    
This property MUST be present in the vCard object,
 and it must appear immediately after BEGIN:VCARD.  The value MUST
 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.

   
ABNF: 

-    
  VERSION-param = "VALUE=text" / any-param
  VERSION-value = "4.0"

+    
  VERSION-param = "VALUE=text" / any-param
  VERSION-value = "4.0"

   
Example: 

-    

+    

   
        VERSION:4.0

 

   

 

         
7.9. Security Properties
7.9.1. General

 
-  
These properties are concerned with the security of communication
+  
These properties are concerned with the security of communication
 pathways or access to the vCard.

 

 
7.9.2. KEY

 
-  
Purpose: 

-    
To specify a public key or authentication certificate
+  
Purpose: 

+    
To specify a public key or authentication certificate
 associated with the object that the vCard represents.

   
Value type: 

-    
A single URI.  It can also be reset to a text value.

+    
A single URI.  It can also be reset to a text value.

   
Cardinality: 

-    
*

+    
*

   
ABNF: 

-    
  KEY-param = KEY-uri-param / KEY-text-param
  KEY-value = KEY-uri-value / KEY-text-value
    ; Value and parameter MUST match.

  KEY-uri-param = "VALUE=uri" / mediatype-param
  KEY-uri-value = URI

  KEY-text-param = "VALUE=text"
  KEY-text-value = text

  KEY-param =/ altid-param / pid-param / pref-param / type-param
             / any-param

+    
  KEY-param = KEY-uri-param / KEY-text-param
  KEY-value = KEY-uri-value / KEY-text-value
    ; Value and parameter MUST match.

  KEY-uri-param = "VALUE=uri" / mediatype-param
  KEY-uri-value = URI

  KEY-text-param = "VALUE=text"
  KEY-text-value = text

  KEY-param =/ altid-param / pid-param / pref-param / type-param
             / any-param

   
Examples: 

-    

+    

   
  KEY:http://www.example.com/keys/jdoe.cer
 
   KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe
@@ -2584,19 +2596,19 @@ 
7.  vCard Properties

 

         
7.10. Calendar Properties
7.10.1. General

 
-  
These properties are further specified in RFC 2739.

+  
These properties are further specified in RFC 2739.

 

 
7.10.2. FBURL

 
-  
Purpose: 

-    
To specify the URI for the busy time associated with the
+  
Purpose: 

+    
To specify the URI for the busy time associated with the
 object that the vCard represents.

   
Value type: 

-    
A single URI value.

+    
A single URI value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
Where multiple FBURL properties are specified, the
+    
Where multiple FBURL properties are specified, the
 default FBURL property is indicated with the PREF parameter.  The
 FTP RFC 1738 or HTTP RFC 2616 type of URI points to an iCalendar
 RFC 5545 object associated with a snapshot of the next few weeks
@@ -2604,9 +2616,9 @@ 
7.  vCard Properties

 represented as a file or document, its file extension should be
 ".ifb".

   
ABNF: 

-    
  FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
              / mediatype-param / altid-param / any-param
  FBURL-value = URI

+    
  FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
              / mediatype-param / altid-param / any-param
  FBURL-value = URI

   
Examples: 

-    

+    

   
  FBURL;PREF=1:http://www.example.com/busy/janedoe
   FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb

 

@@ -2614,22 +2626,22 @@ 
7.  vCard Properties

 

 
7.10.3. CALADRURI

 
-  
Purpose: 

-    
To specify the calendar user address RFC 5545 to which a
+  
Purpose: 

+    
To specify the calendar user address RFC 5545 to which a
 scheduling request RFC 5546 should be sent for the object
 represented by the vCard.

   
Value type: 

-    
A single URI value.

+    
A single URI value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
Where multiple CALADRURI properties are specified,
+    
Where multiple CALADRURI properties are specified,
 the default CALADRURI property is indicated with the PREF
 parameter.

   
ABNF: 

-    
  CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
                  / mediatype-param / altid-param / any-param
  CALADRURI-value = URI

+    
  CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
                  / mediatype-param / altid-param / any-param
  CALADRURI-value = URI

   
Example: 

-    

+    

   
  CALADRURI;PREF=1:mailto:janedoe@example.com
   CALADRURI:http://example.com/calendar/jdoe

 

@@ -2637,24 +2649,24 @@ 
7.  vCard Properties

 

 
7.10.4. CALURI

 
-  
Purpose: 

-    
To specify the URI for a calendar associated with the
+  
Purpose: 

+    
To specify the URI for a calendar associated with the
 object represented by the vCard.

   
Value type: 

-    
A single URI value.

+    
A single URI value.

   
Cardinality: 

-    
*

+    
*

   
Special notes: 

-    
Where multiple CALURI properties are specified, the
+    
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 RFC 5545
 object associated with a snapshot of the user’s calendar store.
 If the iCalendar object is represented as a file or document, its
 file extension should be ".ics".

   
ABNF: 

-    
  CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
               / mediatype-param / altid-param / any-param
  CALURI-value = URI

+    
  CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
               / mediatype-param / altid-param / any-param
  CALURI-value = URI

   
Examples: 

-    

+    

   
  CALURI;PREF=1:http://cal.example.com/calA
   CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics

 

@@ -2662,7 +2674,7 @@ 
7.  vCard Properties

 

         
7.11. Extended Properties and Parameters

 
-  
The properties and parameters defined by this document can be
+  
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.

@@ -2672,51 +2684,51 @@ 
7.  vCard Properties

         
8.  Synchronization

         
8.1. General

 
-  
vCard data often needs to be synchronized between devices.  In this
+  
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.

 

-        
8.2. Mechanisms
8.2.1. General
Two mechanisms are available: the UID property is used to match
+        
8.2. Mechanisms
8.2.1. General
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.

-
The term "matching" is used here to mean recognizing that two
+
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.

-
8.2.2. Matching vCard Instances
vCard instances for which the UID properties (Clause 7.8.7) are
+
8.2.2. Matching vCard Instances
vCard instances for which the UID properties (Clause 7.8.7) are
 equivalent MUST be matched.  Equivalence is determined as specified
 in RFC 3986, Section 6.

-
In all other cases, vCard instances MAY be matched at the discretion
+
In all other cases, vCard instances MAY be matched at the discretion
 of the synchronization engine.

-
8.2.3. Matching Property Instances
Property instances belonging to unmatched vCards MUST NOT be matched.

-
Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
+
8.2.3. Matching Property Instances
Property instances belonging to unmatched vCards MUST NOT be matched.

+
Property instances whose name (e.g., EMAIL, TEL, etc.) is not the
 same MUST NOT be matched.

-
Property instances whose name is CLIENTPIDMAP are handled separately
+
Property instances whose name is CLIENTPIDMAP are handled separately
 and MUST NOT be matched.  The synchronization MUST ensure that there
 is consistency of CLIENTPIDMAPs among matched vCard instances.

-
Property instances belonging to matched vCards, whose name is the
+
Property instances belonging to matched vCards, whose name is the
 same, and whose maximum cardinality is 1, MUST be matched.

-
Property instances belonging to matched vCards, whose name is the
+
Property instances belonging to matched vCards, whose name is the
 same, and whose PID parameters match, MUST be matched.  See
 Clause 8.2.4 for details on PID matching.

-
In all other cases, property instances MAY be matched at the
+
In all other cases, property instances MAY be matched at the
 discretion of the synchronization engine.

-
8.2.4. PID Matching
Two PID values for which the first fields are equivalent represent
+
8.2.4. PID Matching
Two PID values for which the first fields are equivalent represent
 the same local value.

-
Two PID values representing the same local value and for which the
+
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 RFC 3986, Section 6) also
 represent the same global value.

-
PID parameters for which at least one pair of their values represent
+
PID parameters for which at least one pair of their values represent
 the same global value MUST be matched.

-
In all other cases, PID parameters MAY be matched at the discretion
+
In all other cases, PID parameters MAY be matched at the discretion
 of the synchronization engine.

-
For example, PID value "5.1", in the first vCard below, and PID value
+
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.

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   EMAIL;PID=4.2,5.1:jdoe@example.com
@@ -2724,7 +2736,7 @@ 
8.  Synchronization

   CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
   END:VCARD

 

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   EMAIL;PID=5.1,5.2:john@example.com
@@ -2732,8 +2744,8 @@ 
8.  Synchronization

   CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
   END:VCARD

 

-        
8.3. Example
8.3.1. Creation
The following simple vCard is first created on a given device.

-

+        
8.3. Example
8.3.1. Creation
The following simple vCard is first created on a given device.

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -2743,7 +2755,7 @@ 
8.  Synchronization

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-
This new vCard is assigned the UID
+
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
@@ -2754,15 +2766,15 @@ 
8.  Synchronization

 maximum cardinality of 1.

 
8.3.2. Initial Sharing

 
-  
This vCard is shared with a second device.  Upon inspecting the UID
+  
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.

 

-
8.3.3. Adding and Sharing a Property
A new phone number is created on the first device, then the vCard is
+
8.3.3. Adding and Sharing a Property
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:

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -2773,30 +2785,30 @@ 
8.  Synchronization

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-
Upon inspecting the UID property, the second device matches the vCard
+
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.

-
The FN properties are matched because the PID parameters have the
+
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.

-
The N properties are matched automatically because their maximum
+
The N properties are matched automatically because their maximum
 cardinality is 1.  Since the property value is the same, no update
 takes place.

-
The EMAIL properties are matched because the PID parameters have the
+
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.

-
The TEL property in the new vCard is not matched to any in the stored
+
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.

-
The CLIENTPIDMAP property is handled separately by the
+
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.

-
8.3.4. Simultaneous Editing
A new email address and a new phone number are added to the vCard on
+
8.3.4. Simultaneous Editing
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:

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -2809,7 +2821,7 @@ 
8.  Synchronization

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -2823,24 +2835,24 @@ 
8.  Synchronization

   CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
   END:VCARD

 

-
On the first device, the same PID source identifier (1) is reused for
+
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’s identifier,
 "urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".

-
The new EMAIL properties are unmatched on both sides since the PID
+
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.

-
Although the situation appears to be the same for the TEL properties,
+
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
 Clause 8.2.3 state that two properties MAY be matched at the
 discretion of the synchronization engine.  Therefore, the two
 properties are merged.

-
All this results in the following vCard, which is stored on both
+
All this results in the following vCard, which is stored on both
 devices:

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -2855,11 +2867,11 @@ 
8.  Synchronization

   CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
   END:VCARD

 

-
8.3.5. Global Context Simplification
The two devices finish their synchronization procedure by simplifying
+
8.3.5. Global Context Simplification
The two devices finish their synchronization procedure by simplifying
 their global contexts.  Since they haven’t talked to any other
 device, the following vCard is for all purposes equivalent to the
 above.  It is also shorter.

-

+

   
  BEGIN:VCARD
   VERSION:4.0
   UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
@@ -2873,14 +2885,14 @@ 
8.  Synchronization

   CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
   END:VCARD

 

-
The details of global context simplification are unspecified by this
+
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’s opinion, worthwhile.

       

       

         
9.  Example: Author’s vCard

-        

+        

   
 BEGIN:VCARD
  VERSION:4.0
  FN:Simon Perreault
@@ -2906,9 +2918,9 @@ 
9.  Example: Author’s vCard

       

       

         
10.  Security Considerations

-        
    
+        
      
   
    • 
-    
      Internet mail is often used to transport vCards and is subject to
+    
      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,
@@ -2917,11 +2929,11 @@ 
      10.  Security Considerations
      
 directory data in a "safe" environment.
      
   
      • 
   
    • 
-    
      vCards can carry cryptographic keys or certificates, as described
+    
      vCards can carry cryptographic keys or certificates, as described
 in Clause 7.9.2.
      
   
      • 
   
    • 
-    
      vCards often carry information that can be sensitive (e.g.,
+    
      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
@@ -2933,102 +2945,102 @@ 
      10.  Security Considerations
      
 transport the public key used by these mechanisms.
      
   
      • 
   
    • 
-    
      The information in a vCard may become out of date.  In cases where
+    
      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 (Clause 7.2.3) SHOULD be specified.  In addition,
 the "REV" type described in Clause 7.8.5 can be specified to
 indicate the last time that the vCard data was updated.
      
   
      • 
   
    • 
-    
      Many vCard properties may be used to transport URIs.  Please refer
+    
      Many vCard properties may be used to transport URIs.  Please refer
 to RFC 3986, Section 7, for considerations related to URIs.
      
   
      • 
 
    
       

       

         
11.  IANA Considerations

-        
11.1. Media Type Registration
IANA has registered the following Media Type (in
+        
11.1. Media Type Registration
IANA has registered the following Media Type (in
 http://www.iana.org) and marked the text/directory Media Type as
 DEPRECATED.

-
To: 

-    
ietf-types@iana.org

+
To: 

+    
ietf-types@iana.org

   
Subject: 

-    
Registration of media type text/vcard

+    
Registration of media type text/vcard

   
Type name: 

-    
text

+    
text

   
Subtype name: 

-    
vcard

+    
vcard

   
Required parameters: 

-    
none

-  
Optional parameters: 
version
The "version" parameter is to be interpreted identically as the
+    
none

+  
Optional parameters: 
version
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 MUST have a VERSION property with value
    identical to that of this MIME parameter.

-
"charset": as defined for text/plain RFC 2046; encodings other
+
"charset": as defined for text/plain RFC 2046; encodings other
    than UTF-8 RFC 3629 MUST NOT be used.
Encoding considerations: 

-    
8bit

+    
8bit

   
Security considerations: 

-    
See Clause 10.

-  
Interoperability considerations: 
The text/vcard media type is
+    
See Clause 10.

+  
Interoperability considerations: 
The text/vcard media type is
 intended to identify vCard data of any version.  There are older
 specifications of vCard RFC 2426 Internet Mail Consortium vCard 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 Clause 7.8.10) for identifying the standard to which
-a given vCard object conforms.
In addition, the following media types are known to have been used
+a given vCard object conforms.
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.

-
    
+
      
   
    • 
-    
      text/directory
      
+    
      text/directory
      
   
      • 
   
    • 
-    
      text/directory; profile=vcard
      
+    
      text/directory; profile=vcard
      
   
      • 
   
    • 
-    
      text/x-vcard
      
+    
      text/x-vcard
      
   
      • 
 
Published specification: 

-    
RFC 6350

+    
RFC 6350

   
Applications that use this media type: 

-    
They are numerous, diverse,
+    
They are numerous, diverse,
 and include mail user agents, instant messaging clients, address
 book applications, directory servers, and customer relationship
 management software.

   
Additional information: 

-    
Magic number(s): 
File extension(s): 

-    
.vcf .vcard

+    
Magic number(s): 
File extension(s): 

+    
.vcf .vcard

   
Macintosh file type code(s): 

   
Person & email address to contact for further information: 

-    
vCard
+    
vCard
 discussion mailing list <vcarddav@ietf.org>

   
Intended usage: 

-    
COMMON

+    
COMMON

   
Restrictions on usage: 

-    
none

+    
none

   
Author: 

-    
Simon Perreault

+    
Simon Perreault

   
Change controller: 

-    
IETF

+    
IETF

   

         
11.2. Registering New vCard Elements
11.2.1. General

 
-  
This section defines the process for registering new or modified
+  
This section defines the process for registering new or modified
 vCard elements (i.e., properties, parameters, value data types, and
 values) with IANA.

 

-
11.2.2. Registration Procedure
The IETF has created a mailing list, vcarddav@ietf.org, which can be
+
11.2.2. Registration Procedure
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.

-
Registration of new vCard elements MUST be reviewed by the designated
+
Registration of new vCard elements MUST be reviewed by the designated
 expert and published in an RFC.  A Standards Track RFC is REQUIRED
 for the registration of new value data types that modify existing
 properties.  A Standards Track RFC is also REQUIRED for registration
 of vCard elements that modify vCard elements previously documented in
 a Standards Track RFC.

-
The registration procedure begins when a completed registration
+
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
@@ -3038,149 +3050,149 @@ 
11.  IANA Considerations

 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.

-
Once the registration procedure concludes successfully, IANA creates
+
Once the registration procedure concludes successfully, IANA creates
 or modifies the corresponding record in the vCard registry.  The
 completed registration template is discarded.

-
An RFC specifying new vCard elements MUST include the completed
+
An RFC specifying new vCard elements MUST include the completed
 registration templates, which MAY be expanded with additional
 information.  These completed templates are intended to go in the
 body of the document, not in the IANA Considerations section.

-
Finally, note that there is an XML representation for vCard defined
+
Finally, note that there is an XML representation for vCard defined
 in RFC 6351.  An XML representation SHOULD be defined for new vCard
 elements.

-
11.2.3. Vendor Namespace
The vendor namespace is used for vCard elements associated with
+
11.2.3. Vendor Namespace
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.

-
A registration may be placed in the vendor namespace by anyone who
+
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.

-
vCard elements belonging to the vendor namespace will be
+
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’s choosing (e.g., "VND-123456-
 MUDPIE").

-
While public exposure and review of vCard elements to be registered
+
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.

-
11.2.4. Registration Template for Properties
A property is defined by completing the following template.

-
Namespace: 

-    
Empty for the global namespace, "VND-NNNN-" for a vendor-
+
11.2.4. Registration Template for Properties
A property is defined by completing the following template.

+
Namespace: 

+    
Empty for the global namespace, "VND-NNNN-" for a vendor-
 specific property (where NNNN is replaced by the vendor’s PEN).

   
Property name: 

-    
The name of the property.

+    
The name of the property.

   
Purpose: 

-    
The purpose of the property.  Give a short but clear
+    
The purpose of the property.  Give a short but clear
 description.

   
Value type: 

-    
Any of the valid value types for the property value
+    
Any of the valid value types for the property value
 needs to be specified.  The default value type also needs to be
 specified.

   
Cardinality: 

-    
See Clause 7.

+    
See Clause 7.

   
Property parameters: 

-    
Any of the valid property parameters for the
+    
Any of the valid property parameters for the
 property MUST be specified.

   
Description: 

-    
Any special notes about the property, how it is to be
+    
Any special notes about the property, how it is to be
 used, etc.

   
Format definition: 

-    
The ABNF for the property definition needs to be
+    
The ABNF for the property definition needs to be
 specified.

   
Example(s): 

-    
One or more examples of instances of the property need
+    
One or more examples of instances of the property need
 to be specified.

   

-
11.2.5. Registration Template for Parameters
A parameter is defined by completing the following template.

-
Namespace: 

-    
Empty for the global namespace, "VND-NNNN-" for a vendor-
+
11.2.5. Registration Template for Parameters
A parameter is defined by completing the following template.

+
Namespace: 

+    
Empty for the global namespace, "VND-NNNN-" for a vendor-
 specific property (where NNNN is replaced by the vendor’s PEN).

   
Parameter name: 

-    
The name of the parameter.

+    
The name of the parameter.

   
Purpose: 

-    
The purpose of the parameter.  Give a short but clear
+    
The purpose of the parameter.  Give a short but clear
 description.

   
Description: 

-    
Any special notes about the parameter, how it is to be
+    
Any special notes about the parameter, how it is to be
 used, etc.

   
Format definition: 

-    
The ABNF for the parameter definition needs to be
+    
The ABNF for the parameter definition needs to be
 specified.

   
Example(s): 

-    
One or more examples of instances of the parameter need
+    
One or more examples of instances of the parameter need
 to be specified.

   

-
11.2.6. Registration Template for Value Data Types
A value data type is defined by completing the following template.

-
Value name: 

-    
The name of the value type.

+
11.2.6. Registration Template for Value Data Types
A value data type is defined by completing the following template.

+
Value name: 

+    
The name of the value type.

   
Purpose: 

-    
The purpose of the value type.  Give a short but clear
+    
The purpose of the value type.  Give a short but clear
 description.

   
Description: 

-    
Any special notes about the value type, how it is to be
+    
Any special notes about the value type, how it is to be
 used, etc.

   
Format definition: 

-    
The ABNF for the value type definition needs to
+    
The ABNF for the value type definition needs to
 be specified.

   
Example(s): 

-    
One or more examples of instances of the value type need
+    
One or more examples of instances of the value type need
 to be specified.

   

-
11.2.7. Registration Template for Values
A value is defined by completing the following template.

-
Value: 

-    
The value literal.

+
11.2.7. Registration Template for Values
A value is defined by completing the following template.

+
Value: 

+    
The value literal.

   
Purpose: 

-    
The purpose of the value.  Give a short but clear
+    
The purpose of the value.  Give a short but clear
 description.

   
Conformance: 

-    
The vCard properties and/or parameters that can take
+    
The vCard properties and/or parameters that can take
 this value needs to be specified.

   
Example(s): 

-    
One or more examples of instances of the value need to
+    
One or more examples of instances of the value need to
 be specified.

   

-
The following is a fictitious example of a registration of a vCard
+
The following is a fictitious example of a registration of a vCard
 value:

-
Value: 

-    
supervisor

+
Value: 

+    
supervisor

   
Purpose: 

-    
It means that the related entity is the direct hierarchical
+    
It means that the related entity is the direct hierarchical
 superior (i.e., supervisor or manager) of the entity this vCard
 represents.

   
Conformance: 

-    
This value can be used with the "TYPE" parameter
+    
This value can be used with the "TYPE" parameter
 applied on the "RELATED" property.

   
Example(s): 

-    

+    

   
RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

 

   

         
11.3. Initial vCard Elements Registries
11.3.1. General

 
-  
The IANA has created and will maintain the following registries for
+  
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".

 

-
11.3.2. Properties Registry
The following table has been used to initialize the properties
+
11.3.2. Properties Registry
The following table has been used to initialize the properties
 registry.

-
Table 3
NamespacePropertyReference
SOURCERFC 6350, Section 6.1.3
KINDRFC 6350, Section 6.1.4
XMLRFC 6350, Section 6.1.5
FNRFC 6350, Section 6.2.1
NRFC 6350, Section 6.2.2
NICKNAMERFC 6350, Section 6.2.3
PHOTORFC 6350, Section 6.2.4
BDAYRFC 6350, Section 6.2.5
ANNIVERSARYRFC 6350, Section 6.2.6
GENDERRFC 6350, Section 6.2.7
ADRRFC 6350, Section 6.3.1
TELRFC 6350, Section 6.4.1
EMAILRFC 6350, Section 6.4.2
IMPPRFC 6350, Section 6.4.3
LANGRFC 6350, Section 6.4.4
TZRFC 6350, Section 6.5.1
GEORFC 6350, Section 6.5.2
TITLERFC 6350, Section 6.6.1
ROLERFC 6350, Section 6.6.2
LOGORFC 6350, Section 6.6.3
ORGRFC 6350, Section 6.6.4
MEMBERRFC 6350, Section 6.6.5
RELATEDRFC 6350, Section 6.6.6
CATEGORIESRFC 6350, Section 6.7.1
NOTERFC 6350, Section 6.7.2
PRODIDRFC 6350, Section 6.7.3
REVRFC 6350, Section 6.7.4
SOUNDRFC 6350, Section 6.7.5
UIDRFC 6350, Section 6.7.6
CLIENTPIDMAPRFC 6350, Section 6.7.7
URLRFC 6350, Section 6.7.8
VERSIONRFC 6350, Section 6.7.9
KEYRFC 6350, Section 6.8.1
FBURLRFC 6350, Section 6.9.1
CALADRURIRFC 6350, Section 6.9.2
CALURIRFC 6350, Section 6.9.3

-
11.3.3. Parameters Registry
The following table has been used to initialize the parameters
+
Table 3
NamespacePropertyReference
SOURCERFC 6350, Section 6.1.3
KINDRFC 6350, Section 6.1.4
XMLRFC 6350, Section 6.1.5
FNRFC 6350, Section 6.2.1
NRFC 6350, Section 6.2.2
NICKNAMERFC 6350, Section 6.2.3
PHOTORFC 6350, Section 6.2.4
BDAYRFC 6350, Section 6.2.5
ANNIVERSARYRFC 6350, Section 6.2.6
GENDERRFC 6350, Section 6.2.7
ADRRFC 6350, Section 6.3.1
TELRFC 6350, Section 6.4.1
EMAILRFC 6350, Section 6.4.2
IMPPRFC 6350, Section 6.4.3
LANGRFC 6350, Section 6.4.4
TZRFC 6350, Section 6.5.1
GEORFC 6350, Section 6.5.2
TITLERFC 6350, Section 6.6.1
ROLERFC 6350, Section 6.6.2
LOGORFC 6350, Section 6.6.3
ORGRFC 6350, Section 6.6.4
MEMBERRFC 6350, Section 6.6.5
RELATEDRFC 6350, Section 6.6.6
CATEGORIESRFC 6350, Section 6.7.1
NOTERFC 6350, Section 6.7.2
PRODIDRFC 6350, Section 6.7.3
REVRFC 6350, Section 6.7.4
SOUNDRFC 6350, Section 6.7.5
UIDRFC 6350, Section 6.7.6
CLIENTPIDMAPRFC 6350, Section 6.7.7
URLRFC 6350, Section 6.7.8
VERSIONRFC 6350, Section 6.7.9
KEYRFC 6350, Section 6.8.1
FBURLRFC 6350, Section 6.9.1
CALADRURIRFC 6350, Section 6.9.2
CALURIRFC 6350, Section 6.9.3

+
11.3.3. Parameters Registry
The following table has been used to initialize the parameters
 registry.

-
Table 4
NamespaceParameterReference
LANGUAGERFC 6350, Section 5.1
VALUERFC 6350, Section 5.2
PREFRFC 6350, Section 5.3
ALTIDRFC 6350, Section 5.4
PIDRFC 6350, Section 5.5
TYPERFC 6350, Section 5.6
MEDIATYPERFC 6350, Section 5.7
CALSCALERFC 6350, Section 5.8
SORT-ASRFC 6350, Section 5.9
GEORFC 6350, Section 5.10
TZRFC 6350, Section 5.11

-
11.3.4. Value Data Types Registry
The following table has been used to initialize the parameters
+
Table 4
NamespaceParameterReference
LANGUAGERFC 6350, Section 5.1
VALUERFC 6350, Section 5.2
PREFRFC 6350, Section 5.3
ALTIDRFC 6350, Section 5.4
PIDRFC 6350, Section 5.5
TYPERFC 6350, Section 5.6
MEDIATYPERFC 6350, Section 5.7
CALSCALERFC 6350, Section 5.8
SORT-ASRFC 6350, Section 5.9
GEORFC 6350, Section 5.10
TZRFC 6350, Section 5.11

+
11.3.4. Value Data Types Registry
The following table has been used to initialize the parameters
 registry.

-
Table 5
Value Data TypeReference
BOOLEANRFC 6350, Section 4.4
DATERFC 6350, Section 4.3.1
DATE-AND-OR-TIMERFC 6350, Section 4.3.4
DATE-TIMERFC 6350, Section 4.3.3
FLOATRFC 6350, Section 4.6
INTEGERRFC 6350, Section 4.5
LANGUAGE-TAGRFC 6350, Section 4.8
TEXTRFC 6350, Section 4.1
TIMERFC 6350, Section 4.3.2
TIMESTAMPRFC 6350, Section 4.3.5
URIRFC 6350, Section 4.2
UTC-OFFSETRFC 6350, Section 4.7

-
11.3.5. Values Registries
Separate tables are used for property and parameter values.

-
The following table is to be used to initialize the property values
+
Table 5
Value Data TypeReference
BOOLEANRFC 6350, Section 4.4
DATERFC 6350, Section 4.3.1
DATE-AND-OR-TIMERFC 6350, Section 4.3.4
DATE-TIMERFC 6350, Section 4.3.3
FLOATRFC 6350, Section 4.6
INTEGERRFC 6350, Section 4.5
LANGUAGE-TAGRFC 6350, Section 4.8
TEXTRFC 6350, Section 4.1
TIMERFC 6350, Section 4.3.2
TIMESTAMPRFC 6350, Section 4.3.5
URIRFC 6350, Section 4.2
UTC-OFFSETRFC 6350, Section 4.7

+
11.3.5. Values Registries
Separate tables are used for property and parameter values.

+
The following table is to be used to initialize the property values
 registry.

-
Table 6
PropertyValueReference
BEGINVCARDRFC 6350, Section 6.1.1
ENDVCARDRFC 6350, Section 6.1.2
KINDindividualRFC 6350, Section 6.1.4
KINDgroupRFC 6350, Section 6.1.4
KINDorgRFC 6350, Section 6.1.4
KINDlocationRFC 6350, Section 6.1.4

-
The following table has been used to initialize the parameter values
+
Table 6
PropertyValueReference
BEGINVCARDRFC 6350, Section 6.1.1
ENDVCARDRFC 6350, Section 6.1.2
KINDindividualRFC 6350, Section 6.1.4
KINDgroupRFC 6350, Section 6.1.4
KINDorgRFC 6350, Section 6.1.4
KINDlocationRFC 6350, Section 6.1.4

+
The following table has been used to initialize the parameter values
 registry.

-
Table 7
PropertyParameterValueReference
FN, NICKNAME, PHOTO,
+
Table 7
PropertyParameterValueReference
FN, NICKNAME, PHOTO,
  ADR, TEL, EMAIL, IMPP,
  LANG, TZ, GEO, TITLE,
  ROLE, LOGO, ORG,
@@ -3199,12 +3211,12 @@ 
11.  IANA Considerations

       

       

         
Appendix A
(informative) 
Acknowledgments

-        
The authors would like to thank Tim Howes, Mark Smith, and Frank
+        
The authors would like to thank Tim Howes, Mark Smith, and Frank
 Dawson, the original authors of RFC 2425 and RFC 2426, 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:

-        
Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
+        
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,
@@ -3220,76 +3232,76 @@ 
Appendix A
(informative) 
Acknowledgments<
       

       

         
Appendix B
(normative) 
Differences from RFCs 2425 and 2426

-        
This appendix contains a high-level overview of the major changes
+        
This appendix contains a high-level overview of the major changes
 that have been made in the vCard specification from RFC 2425 and
 RFC 2426.  It is incomplete, as it only lists the most important changes.

         
B.1. New Structure

 
-  
    
+  
      
   
    • 
-    
      RFC 2425 and RFC 2426 have been merged.
      
+    
      RFC 2425 and RFC 2426 have been merged.
      
   
      • 
   
    • 
-    
      vCard is now not only a MIME type but a stand-alone format.
      
+    
      vCard is now not only a MIME type but a stand-alone format.
      
   
      • 
   
    • 
-    
      A proper MIME type registration form has been included.
      
+    
      A proper MIME type registration form has been included.
      
   
      • 
   
    • 
-    
      UTF-8 is now the only possible character set.
      
+    
      UTF-8 is now the only possible character set.
      
   
      • 
   
    • 
-    
      New vCard elements can be registered from IANA.
      
+    
      New vCard elements can be registered from IANA.
      
   
      • 
 
    
 

         
B.2. Removed Features

 
-  
    
+  
      
   
    • 
-    
      The CONTEXT and CHARSET parameters are no more.
      
+    
      The CONTEXT and CHARSET parameters are no more.
      
   
      • 
   
    • 
-    
      The NAME, MAILER, LABEL, and CLASS properties are no more.
      
+    
      The NAME, MAILER, LABEL, and CLASS properties are no more.
      
   
      • 
   
    • 
-    
      The "intl", "dom", "postal", and "parcel" TYPE parameter values
+    
      The "intl", "dom", "postal", and "parcel" TYPE parameter values
 for the ADR property have been removed.
      
   
      • 
   
    • 
-    
      In-line vCards (such as the value of the AGENT property) are no
+    
      In-line vCards (such as the value of the AGENT property) are no
 longer supported.
      
   
      • 
 
    
 

         
B.3. New Properties and Parameters

 
-  
    
+  
      
   
    • 
-    
      The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP
+    
      The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP
 properties have been added.
      
   
      • 
   
    • 
-    
      RFC 2739, which defines the FBURL, CALADRURI, CAPURI, and CALURI
+    
      RFC 2739, which defines the FBURL, CALADRURI, CAPURI, and CALURI
 properties, has been merged in.
      
   
      • 
   
    • 
-    
      RFC 4770, which defines the IMPP property, has been merged in.
      
+    
      RFC 4770, which defines the IMPP property, has been merged in.
      
   
      • 
   
    • 
-    
      The "work" and "home" TYPE parameter values are now applicable to
+    
      The "work" and "home" TYPE parameter values are now applicable to
 many more properties.
      
   
      • 
   
    • 
-    
      The "pref" value of the TYPE parameter is now a parameter of its
+    
      The "pref" value of the TYPE parameter is now a parameter of its
 own, with a positive integer value indicating the level of
 preference.
      
   
      • 
   
    • 
-    
      The ALTID and PID parameters have been added.
      
+    
      The ALTID and PID parameters have been added.
      
   
      • 
   
    • 
-    
      The MEDIATYPE parameter has been added and replaces the TYPE
+    
      The MEDIATYPE parameter has been added and replaces the TYPE
 parameter when it was used for indicating the media type of the
 property’s content.
      
   
      • 
diff --git a/spec/isodoc/m3dconvert_spec.rb b/spec/isodoc/m3dconvert_spec.rb
index 80673de..0d0d72c 100644
--- a/spec/isodoc/m3dconvert_spec.rb
+++ b/spec/isodoc/m3dconvert_spec.rb
@@ -45,7 +45,7 @@
 
     INPUT
         expect(htmlencode(Hash[csdc.info(docxml, nil).sort].to_s)).to be_equivalent_to <<~"OUTPUT"
-           {:accesseddate=>"XXX", :confirmeddate=>"XXX", :createddate=>"XXX", :docnumber=>"1000(wd)", :doctitle=>"Main Title", :doctype=>"Standard", :docyear=>"2001", :draft=>"3.4", :draftinfo=>" (draft 3.4, 2000-01-01)", :editorialgroup=>[], :ics=>"XXX", :implementeddate=>"XXX", :issueddate=>"XXX", :obsoleteddate=>"XXX", :obsoletes=>nil, :obsoletes_part=>nil, :publisheddate=>"XXX", :revdate=>"2000-01-01", :revdate_monthyear=>"January 2000", :sc=>"XXXX", :secretariat=>"XXXX", :status=>"Working Draft", :tc=>nil, :updateddate=>"XXX", :url=>"http://www.m3aawg.org/BlocklistHelp", :wg=>"XXXX"}
+{:accesseddate=>"XXX", :confirmeddate=>"XXX", :createddate=>"XXX", :docnumber=>"1000(wd)", :doctitle=>"Main Title", :doctype=>"Standard", :docyear=>"2001", :draft=>"3.4", :draftinfo=>" (draft 3.4, 2000-01-01)", :editorialgroup=>[], :ics=>"XXX", :implementeddate=>"XXX", :issueddate=>"XXX", :obsoleteddate=>"XXX", :obsoletes=>nil, :obsoletes_part=>nil, :publisheddate=>"XXX", :receiveddate=>"XXX", :revdate=>"2000-01-01", :revdate_monthyear=>"January 2000", :sc=>"XXXX", :secretariat=>"XXXX", :status=>"Working Draft", :tc=>nil, :unpublished=>false, :updateddate=>"XXX", :url=>"http://www.m3aawg.org/BlocklistHelp", :wg=>"XXXX"}
     OUTPUT
   end