draft-ietf-vcarddav-vcardrev-17.txt   draft-ietf-vcarddav-vcardrev-18.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 April 6, 2011 Obsoletes: 2425, 2426, 4770 April 6, 2011
(if approved) (if approved)
Updates: 2739 (if approved) Updates: 2739 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: October 8, 2011 Expires: October 8, 2011
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-17 draft-ietf-vcarddav-vcardrev-18
Abstract Abstract
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 exchanging a variety of information about individuals and other
entities (e.g., formatted and structured name and delivery addresses, entities (e.g., formatted and structured name and delivery addresses,
email address, multiple telephone numbers, photograph, logo, audio email address, multiple telephone numbers, photograph, logo, audio
clips, etc.). clips, etc.).
Status of This Memo Status of This Memo
skipping to change at page 4, line 51 skipping to change at page 4, line 51
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69 12.1. Normative References . . . . . . . . . . . . . . . . . . . 69
12.2. Informative References . . . . . . . . . . . . . . . . . . 72 12.2. Informative References . . . . . . . . . . . . . . . . . . 72
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 73 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 73
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 74 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 74
A.3. New Properties and Parameters . . . . . . . . . . . . . . 74 A.3. New Properties and Parameters . . . . . . . . . . . . . . 74
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 74 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 74
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 75 publication) . . . . . . . . . . . . . . . . . . . . 75
B.1. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 75 B.1. Changes in -18 . . . . . . . . . . . . . . . . . . . . . . 75
B.2. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 76 B.2. Changes in -17 . . . . . . . . . . . . . . . . . . . . . . 75
B.3. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 76 B.3. Changes in -16 . . . . . . . . . . . . . . . . . . . . . . 76
B.4. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 77 B.4. Changes in -15 . . . . . . . . . . . . . . . . . . . . . . 76
B.5. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 77 B.5. Changes in -14 . . . . . . . . . . . . . . . . . . . . . . 77
B.6. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 78 B.6. Changes in -13 . . . . . . . . . . . . . . . . . . . . . . 78
B.7. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 79 B.7. Changes in -12 . . . . . . . . . . . . . . . . . . . . . . 78
B.8. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 79 B.8. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 79
B.9. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 80 B.9. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 80
B.10. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 80 B.10. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 80
B.11. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 81 B.11. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 80
B.12. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 81 B.12. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 81
B.13. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 82 B.13. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 81
B.14. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 82 B.14. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 82
B.15. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 83 B.15. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 82
B.16. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 83 B.16. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 83
B.17. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 83 B.17. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 83
B.18. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 84 B.18. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 84
B.19. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 84
1. Introduction 1. Introduction
Electronic address books have become ubiquitous. Their increased Electronic address books have become ubiquitous. Their increased
presence on portable, connected devices as well as the diversity of presence on portable, connected devices as well as the diversity of
platforms exchanging contact data call for a standard. This memo platforms exchanging contact data call for a standard. This memo
defines the vCard format, which allows the capture and exchange of defines the vCard format, which allows the capture and exchange of
information normally stored within an address book or directory information normally stored within an address book or directory
application. application.
skipping to change at page 25, line 39 skipping to change at page 25, line 39
6.1.4. KIND 6.1.4. KIND
Purpose: To specify the kind of object the vCard represents. Purpose: To specify the kind of object the vCard represents.
Value type: A single text value. Value type: A single text value.
Cardinality: *1 Cardinality: *1
Special notes: The value may be one of the following: Special notes: The value may be one of the following:
* for a vCard representing a single person or entity. This is "individual" for a vCard representing a single person or entity.
the default kind of vCard. This is the default kind of vCard.
* for a vCard representing a group of persons or entities. The "group" for a vCard representing a group of persons or entities.
group's member entities can be other vCards or other types of The group's member entities can be other vCards or other types
entities, such as email addresses or web sites. A group vCard of entities, such as email addresses or web sites. A group
will usually contain MEMBER properties to specify the members vCard will usually contain MEMBER properties to specify the
of the group, but it is not required to. A group vCard without members of the group, but it is not required to. A group vCard
MEMBER properties can be considered an abstract grouping, or without MEMBER properties can be considered an abstract
one whose members are known empirically (perhaps "IETF grouping, or one whose members are known empirically (perhaps
Participants" or "Republican U.S. Senators"). "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 and not to any particular MEMBER. For example, an EMAIL
property might specify the address of a mailing list associated property might specify the address of a mailing list associated
with the group, and an IMPP property might refer to a group with the group, and an IMPP property might refer to a group
chat room. chat room.
* for a vCard representing an organization. An organization "org" for a vCard representing an organization. An organization
vCard will not (in fact, MUST NOT) contain MEMBER properties, vCard will not (in fact, MUST NOT) contain MEMBER properties,
and so these are something of a cross between "individual" and and so these are something of a cross between "individual" and
"group". An organization is a single entity, but not a person. "group". An organization is a single entity, but not a person.
It might represent a business or government, a department or It might represent a business or government, a department or
division within a business or government, a club, an division within a business or government, a club, an
association, or the like. 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. organization as a whole, as is the case with a group vCard.
For example, an EMAIL property might specify the address of a For example, an EMAIL property might specify the address of a
contact point for the organization. contact point for the organization.
* for a named geographical place. A location vCard will usually "location" for a named geographical place. A location vCard will
contain a GEO property, but it is not required to. A location usually contain a GEO property, but it is not required to. A
vCard without a GEO property can be considered an abstract location vCard without a GEO property can be considered an
location, or one whose definition is known empirically (perhaps abstract location, or one whose definition is known empirically
"New England" or "The Seashore"). (perhaps "New England" or "The Seashore").
* All properties in an location vCard apply to the location All properties in an location vCard apply to the location
itself, and not with any entity that might exist at that itself, and not with any entity that might exist at that
location. For example, in a vCard for an office building, an location. For example, in a vCard for an office building, an
ADR property might give the mailing address for the building, ADR property might give the mailing address for the building,
and a TEL property might specify the telephone number of the and a TEL property might specify the telephone number of the
receptionist. receptionist.
* vCards MAY include private or experimental values for KIND. An x-name. vCards MAY include private or experimental values for
Remember that x-name values are not intended for general use, KIND. Remember that x-name values are not intended for general
and are unlikely to interoperate. use, and are unlikely to interoperate.
* Additional values may be registered with IANA (see An iana-token. Additional values may be registered with IANA (see
Section 10.3.4). A new value's specification document MUST Section 10.3.4). A new value's specification document MUST
specify which properties make sense for that new kind of vCard, specify which properties make sense for that new kind of vCard,
and which do not. 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 above. If this property is absent, "individual" MUST be assumed
as the default. If this property is present but the as the default. If this property is present but the
implementation does not understand its value (the value is an implementation does not understand its value (the value is an
x-name or iana-token that the implementation does not support), x-name or iana-token that the implementation does not support),
the implementation SHOULD act in a neutral way, which usually the implementation SHOULD act in a neutral way, which usually
skipping to change at page 60, line 19 skipping to change at page 60, line 19
In addition, the following media types are known to have been used In addition, the following media types are known to have been used
to refer to vCard data. They should be considered deprecated in to refer to vCard data. They should be considered deprecated in
favor of text/vcard. favor of text/vcard.
* text/directory * text/directory
* text/directory; profile=vcard * text/directory; profile=vcard
* text/x-vcard * text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-17 Published specification: draft-ietf-vcarddav-vcardrev-18
Applications that use this media type: They are numerous, diverse, Applications that use this media type: They are numerous, diverse,
and include mail user agents, instant messaging clients, address and include mail user agents, instant messaging clients, address
book applications, directory servers, customer relationship book applications, directory servers, customer relationship
management software. management software.
Additional information: Additional information:
Magic number(s): Magic number(s):
skipping to change at page 75, line 15 skipping to change at page 75, line 15
o The value of TEL is now a URI. o The value of TEL is now a URI.
o The AGENT property was replaced with a type of RELATED. o The AGENT property was replaced with a type of RELATED.
o Date and time values now only support the basic format. o Date and time values now only support the basic format.
Truncation is now supported. Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -17 B.1. Changes in -18
o Fix missing text in KIND section.
B.2. Changes in -17
o s/individual/entity/ o s/individual/entity/
o Moved section 3.4 for better flow. o Moved section 3.4 for better flow.
o Removed text overriding general MIME and HTTP rules. o Removed text overriding general MIME and HTTP rules.
o Fixed redundant ABNF. o Fixed redundant ABNF.
o Fixed parameter value quoting in examples. o Fixed parameter value quoting in examples.
skipping to change at page 76, line 9 skipping to change at page 76, line 13
o Removed underspecified "Status" column in IANA registry. o Removed underspecified "Status" column in IANA registry.
o Moved obsoleted references to Informative section. o Moved obsoleted references to Informative section.
o Moved iCalendar references to Normative section. o Moved iCalendar references to Normative section.
o Expanded specification of KIND values. o Expanded specification of KIND values.
o Recommend defining an XML representation for new vCard objects. o Recommend defining an XML representation for new vCard objects.
B.2. Changes in -16 B.3. Changes in -16
o RELATED: Added XFN values into IANA registry. o RELATED: Added XFN values into IANA registry.
o RELATED: Added values "agent" and "emergency". o RELATED: Added values "agent" and "emergency".
o EMAIL is now free-form text, with informative reference to EAI. o EMAIL is now free-form text, with informative reference to EAI.
o GENDER now has two components: one for biological sex, the other o GENDER now has two components: one for biological sex, the other
for gender identity. for gender identity.
o Bugfixes to the core ABNF. o Bugfixes to the core ABNF.
o Clarified IANA considerations. o Clarified IANA considerations.
o UID may be reset to free-form text. o UID may be reset to free-form text.
B.3. Changes in -15 B.4. Changes in -15
o Reverted N to the 5-component format of vCard 3. o Reverted N to the 5-component format of vCard 3.
o Removed DDAY, BIRTH, and DEATH. o Removed DDAY, BIRTH, and DEATH.
o First two components in ADR SHOULD be empty. o First two components in ADR SHOULD be empty.
o Removed the LABEL property. o Removed the LABEL property.
o Removed the binary value type and the ENCODING and FMTTYPE o Removed the binary value type and the ENCODING and FMTTYPE
skipping to change at page 77, line 11 skipping to change at page 77, line 15
o RELATED now uses XFN 1.1 for its value. o RELATED now uses XFN 1.1 for its value.
o Dropped the VERSION parameter. XML MUST be version 1.0. o Dropped the VERSION parameter. XML MUST be version 1.0.
o Dropped the CLASS property. o Dropped the CLASS property.
o Property and parameter names SHOULD be upper-case. o Property and parameter names SHOULD be upper-case.
o Use ABNF for cardinality notation. o Use ABNF for cardinality notation.
B.4. Changes in -14 B.5. Changes in -14
o DQUOTE is US-ASCII decimal 34, not 22. o DQUOTE is US-ASCII decimal 34, not 22.
o Removed unused reference to RFC 2046. o Removed unused reference to RFC 2046.
o Updated reference to draft-ietf-vcarddav-vcardxml. o Updated reference to draft-ietf-vcarddav-vcardxml.
o Small fixes to the IANA registration text. o Small fixes to the IANA registration text.
o Added notes on the usage of TEL and IMPP properties. o Added notes on the usage of TEL and IMPP properties.
skipping to change at page 77, line 45 skipping to change at page 78, line 5
o Removed advice for always including VALUE parameter. o Removed advice for always including VALUE parameter.
o FMTTYPE MUST include the full MIME type. o FMTTYPE MUST include the full MIME type.
o Made ADR's ABNF more verbose. o Made ADR's ABNF more verbose.
o Organized TEL TYPE values in a table. o Organized TEL TYPE values in a table.
o Replaced TOP-SECRET example with NOINDEX. o Replaced TOP-SECRET example with NOINDEX.
B.5. Changes in -13 B.6. Changes in -13
o Changed global ABNF to make explicit that VERSION comes first. o Changed global ABNF to make explicit that VERSION comes first.
o Reworked example for LANGUAGE property. o Reworked example for LANGUAGE property.
o s/TYPE/FMTTYPE/ in two examples. o s/TYPE/FMTTYPE/ in two examples.
o Allow LANGUAGE parameter for text-valued BDAY, DDAY, and RELATED. o Allow LANGUAGE parameter for text-valued BDAY, DDAY, and RELATED.
o Tightened language on LANGUAGE parameter regarding cardinality. o Tightened language on LANGUAGE parameter regarding cardinality.
o Removed the NAME property. o Removed the NAME property.
o Adjusted semi-colon escaping rules. o Adjusted semi-colon escaping rules.
o Added the ALTID parameter. o Added the ALTID parameter.
B.6. Changes in -12 B.7. Changes in -12
o Fixed example of LANGUAGE cardinality. o Fixed example of LANGUAGE cardinality.
o Added note about YYYY-MM date format. o Added note about YYYY-MM date format.
o Fixed appendix A. o Fixed appendix A.
o VERSION property must come first. o VERSION property must come first.
o Fixed mistake in PID example. o Fixed mistake in PID example.
skipping to change at page 79, line 19 skipping to change at page 79, line 26
o BIRTH and DEATH can now have URI values. o BIRTH and DEATH can now have URI values.
o Created the FMTTYPE parameter. o Created the FMTTYPE parameter.
o KEY can now take a text value. o KEY can now take a text value.
o Added references to RFC 5545 (iCalendar). o Added references to RFC 5545 (iCalendar).
o Added namespace column in parameters registry. o Added namespace column in parameters registry.
B.7. Changes in -11 B.8. Changes in -11
o Change "XML chunk" to "XML fragment". o Change "XML chunk" to "XML fragment".
o Cite W3C document containing definition of "fragment". o Cite W3C document containing definition of "fragment".
o Added "XML" to property name ABNF. o Added "XML" to property name ABNF.
o Clarified newline escaping rule. o Clarified newline escaping rule.
o Replaced one remaining "type" with "property". o Replaced one remaining "type" with "property".
skipping to change at page 79, line 43 skipping to change at page 80, line 5
o XML property can now only contain one element that is not in the o XML property can now only contain one element that is not in the
vCard 4 namespace. vCard 4 namespace.
o Clarified interrelationship between LANGUAGE, cardinality, and o Clarified interrelationship between LANGUAGE, cardinality, and
PID. PID.
o Added "textphone" TEL type. o Added "textphone" TEL type.
o Fixed quoting of comma in ORG examples. o Fixed quoting of comma in ORG examples.
B.8. Changes in -10 B.9. Changes in -10
o Added component in SORT-STRING for sorting by given name. Fixed o Added component in SORT-STRING for sorting by given name. Fixed
and expanded the examples. and expanded the examples.
o Fixed KIND-value ABNF. o Fixed KIND-value ABNF.
o Fixed deprecated media type. o Fixed deprecated media type.
o Created the CALSCALE parameter. o Created the CALSCALE parameter.
o Strenghtened the stance on character set. o Strenghtened the stance on character set.
o Defined the Language-Tag ABNF. o Defined the Language-Tag ABNF.
o Made explicit the fact that IANA does not register templates. o Made explicit the fact that IANA does not register templates.
o Created the XML property. o Created the XML property.
o Added social networking examples to URL property. o Added social networking examples to URL property.
B.9. Changes in -09 B.10. Changes in -09
o Removed special meaning for groups. Removed the "work" and "home" o Removed special meaning for groups. Removed the "work" and "home"
groups. Removed the group registry. Re-introduced the "work" and groups. Removed the group registry. Re-introduced the "work" and
"home" TYPE parameter values. Applied the TYPE parameter to "home" TYPE parameter values. Applied the TYPE parameter to
properties which supported the "work" and "home" groups. properties which supported the "work" and "home" groups.
o Vendor namespace now uses private enterprise number in prefix. o Vendor namespace now uses private enterprise number in prefix.
o Added "thing" value for KIND property. o Added "thing" value for KIND property.
B.10. Changes in -08 B.11. Changes in -08
o Allow 1985 (year only) in date ABNF. o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example. o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value. o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME. o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to o Prefixed "param" and "value" production rules specific to
skipping to change at page 81, line 5 skipping to change at page 81, line 13
o Replaced the GENDER property with the SEX property. o Replaced the GENDER property with the SEX property.
o Added the ANNIVERSARY property. o Added the ANNIVERSARY property.
o Added the "friend" and "spouse" types of RELATED. o Added the "friend" and "spouse" types of RELATED.
o TZ property now has text / uri value. o TZ property now has text / uri value.
o Refined the definitions of TITLE and ROLE. o Refined the definitions of TITLE and ROLE.
B.11. Changes in -07 B.12. Changes in -07
o PREF is now bounded. 100 is the maximum value. o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type. o Added the "emergency" RELATED type.
o Made GEO a URI. o Made GEO a URI.
o Added GEO and TZ parameters to ADR. o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property. o Changed wording of "default" use of SOUND property.
skipping to change at page 81, line 27 skipping to change at page 81, line 35
o Completely reworked the date, time, and date-time grammars. o Completely reworked the date, time, and date-time grammars.
o Added the timestamp value type. o Added the timestamp value type.
o REV now has the timestamp value type. o REV now has the timestamp value type.
o Rewrote ABNF. o Rewrote ABNF.
o ORG can now have a single level. o ORG can now have a single level.
B.12. Changes in -06 B.13. Changes in -06
o Corrected omission of resetability to text value for RELATED. o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value. o Let KEY value type be reset to a URI value.
o ABNF fixes. o ABNF fixes.
o Made gender values extensible. o Made gender values extensible.
o Gave the PREF parameter a positive integer value. o Gave the PREF parameter a positive integer value.
skipping to change at page 82, line 19 skipping to change at page 82, line 26
o Removed TYPE parameter from EMAIL properties in examples. o Removed TYPE parameter from EMAIL properties in examples.
o Created the CLIENTPIDMAP property. o Created the CLIENTPIDMAP property.
o Changed PID value to a pair of small integers. o Changed PID value to a pair of small integers.
o Completely reworked synchronization mechanisms. o Completely reworked synchronization mechanisms.
o Created brand new synchronization example. o Created brand new synchronization example.
B.13. Changes in -05 B.14. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.14. Changes in -04 B.15. Changes in -04
o Added "location" value for KIND property. o Added "location" value for KIND property.
o Some fixes to ABNF. o Some fixes to ABNF.
o Moved "pref" from being a TYPE value to a parameter in its own o Moved "pref" from being a TYPE value to a parameter in its own
right. right.
o Removed the "work" and "home" TYPE values. o Removed the "work" and "home" TYPE values.
skipping to change at page 83, line 5 skipping to change at page 83, line 13
o Removed TYPE parameter from EMAIL and IMPP properties. o Removed TYPE parameter from EMAIL and IMPP properties.
o Replaced AGENT with a type of RELATED. o Replaced AGENT with a type of RELATED.
o Use example.org domain in URL example. o Use example.org domain in URL example.
o Created initial IANA table of values. o Created initial IANA table of values.
o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL. o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.
B.15. Changes in -03 B.16. Changes in -03
o Various changes to the synchronization mechanisms. o Various changes to the synchronization mechanisms.
o Allowed truncated format for dated. See issue #236. o Allowed truncated format for dated. See issue #236.
B.16. Changes in -02 B.17. Changes in -02
o Removed useless text in IMPP description. o Removed useless text in IMPP description.
o Added CalDAV-SCHED example to CALADRURI. o Added CalDAV-SCHED example to CALADRURI.
o Removed CAPURI property. o Removed CAPURI property.
o Dashes in dates and colons in times are now mandatory. o Dashes in dates and colons in times are now mandatory.
o Allow for dates such as 2008 and 2008-05 and times such as 07 and o Allow for dates such as 2008 and 2008-05 and times such as 07 and
skipping to change at page 83, line 44 skipping to change at page 84, line 5
o Changed the presence of UID and PID when synchronization is to be o Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD. used from MUST to SHOULD.
o Added the RELATED (Section 6.6.6) property. o Added the RELATED (Section 6.6.6) property.
o Fixed many ABNF typos (issue #252). o Fixed many ABNF typos (issue #252).
o Changed formatting of ABNF comments to make them easier to read o Changed formatting of ABNF comments to make them easier to read
(issue #226). (issue #226).
B.17. Changes in -01 B.18. Changes in -01
o Merged [RFC2739] in. o Merged [RFC2739] in.
o Converted all foobar.com, abc.com, etc. to example.com. o Converted all foobar.com, abc.com, etc. to example.com.
o Fixed bugs in ABNF. o Fixed bugs in ABNF.
o Made explicit that coordinates in the GEO property are expressed o Made explicit that coordinates in the GEO property are expressed
in the WGS 84 reference system. in the WGS 84 reference system.
skipping to change at page 84, line 25 skipping to change at page 84, line 33
o Added Section 7. o Added Section 7.
o Created IANA process for registering new parameters, value types, o Created IANA process for registering new parameters, value types,
and properties. and properties.
o Created the initial IANA registries. o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288. o Created vendor namespace based on text from RFC 4288.
B.18. Changes in -00 B.19. Changes in -00
o Name change because draft has been accepted as WG item. o Name change because draft has been accepted as WG item.
Otherwise, same as draft-resnick-vcarddav-vcardrev-01. Otherwise, same as draft-resnick-vcarddav-vcardrev-01.
o Removed reference to RFC 2234. o Removed reference to RFC 2234.
o Fixed errata from o Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426. http://www.rfc-editor.org/errata_search.php?rfc=2426.
o Removed passage referring to RFC 2425 profiles. o Removed passage referring to RFC 2425 profiles.
 End of changes. 30 change blocks. 
61 lines changed or deleted 66 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/