draft-ietf-vcarddav-vcardxml-08.txt   draft-ietf-vcarddav-vcardxml-09.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Intended status: Standards Track April 6, 2011 Intended status: Standards Track April 9, 2011
Expires: October 8, 2011 Expires: October 11, 2011
vCard XML Representation vCard XML Representation
draft-ietf-vcarddav-vcardxml-08 draft-ietf-vcarddav-vcardxml-09
Abstract Abstract
This document defines the XML schema of the vCard data format. This document defines the XML schema of the vCard data format.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on October 11, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 8, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Example: Author's XML vCard . . . . . . . . . . . . . . . . . 3 3. The Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Design Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Example: Author's XML vCard . . . . . . . . . . . . . . . . . 3
4.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 6 5. Design Considerations . . . . . . . . . . . . . . . . . . . . 5
4.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 7 5.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 6
5. Format Conversions . . . . . . . . . . . . . . . . . . . . . . 8 5.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Format Conversions . . . . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7.1. Registration of the XML Namespace . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7.2. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 10 8.1. Registration of the XML Namespace . . . . . . . . . . . . 10
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 8.2. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 12 Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 12
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) . . . . . . . . . . . . . . . . . . . . 17 publication) . . . . . . . . . . . . . . . . . . . . 18
B.1. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 17 B.1. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 18
B.2. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 18 B.2. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 18
B.3. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 18 B.3. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 18
B.4. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 18 B.4. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 19
B.5. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 18 B.5. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 19
B.6. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 18 B.6. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 19
B.7. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 19 B.7. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 19
B.8. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 19 B.8. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 19
B.9. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 19 B.9. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 20
B.10. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
vCard [I-D.ietf-vcarddav-vcardrev] is a data format for representing vCard [I-D.ietf-vcarddav-vcardrev] is a data format for representing
and exchanging information about individuals and other entities. It and exchanging information about individuals and other entities. It
is a text-based format (as opposed to a binary format). This is a text-based format (as opposed to a binary format). This
document defines an XML representation for vCard. The underlying document defines an XML [W3C.REC-xml-20081126] representation for
data structure is exactly the same, enabling a 1-to-1 mapping between vCard. The underlying data structure is exactly the same, enabling a
the original vCard format and the XML representation. The XML 1-to-1 mapping between the original vCard format and the XML
formatting may be preferred in some contexts where an XML engine is representation. The XML formatting may be preferred in some contexts
readily available and may be reused instead of writing a stand-alone where an XML engine is readily available and may be reused instead of
vCard parser. writing a stand-alone vCard parser.
Earlier work on an XML format for vCard was started in 1998 by Frank Earlier work on an XML format for vCard was started in 1998 by Frank
Dawson [I-D.dawson-vcard-xml-dtd]. Sadly it did not take over the Dawson [I-D.dawson-vcard-xml-dtd]. Sadly it did not take over the
world. world.
2. The Schema 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. The Schema
The schema is expressed in the RELAX NG language The schema is expressed in the RELAX NG language
[relaxng][relaxng-compact] and is found in Appendix A. [relaxng][relaxng-compact] and is found in Appendix A.
3. Example: Author's XML vCard 4. Example: Author's XML vCard
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Simon Perreault</text></fn> <fn><text>Simon Perreault</text></fn>
<n> <n>
<surname><text>Perreault</text></surname> <surname><text>Perreault</text></surname>
<given><text>Simon</text></given> <given><text>Simon</text></given>
<additional/> <additional/>
<prefix/> <prefix/>
skipping to change at page 5, line 4 skipping to change at page 5, line 10
</parameters> </parameters>
<uri>tel:+1-418-262-6501</uri> <uri>tel:+1-418-262-6501</uri>
</tel> </tel>
<email> <email>
<parameters><type><text>work</text></type></parameters> <parameters><type><text>work</text></type></parameters>
<text>simon.perreault@viagenie.ca</text> <text>simon.perreault@viagenie.ca</text>
</email> </email>
<geo> <geo>
<parameters><type><text>work</text></type></parameters> <parameters><type><text>work</text></type></parameters>
<uri>geo:46.766336,-71.28955</uri> <uri>geo:46.766336,-71.28955</uri>
</geo> </geo>
<key> <key>
<parameters><type><text>work</text></type></parameters> <parameters><type><text>work</text></type></parameters>
<uri>http://www.viagenie.ca/simon.perreault/simon.asc</uri> <uri>http://www.viagenie.ca/simon.perreault/simon.asc</uri>
</key> </key>
<tz><text>America/Montreal</text></tz> <tz><text>America/Montreal</text></tz>
</vcard> </vcard>
</vcards> </vcards>
4. Design Considerations 5. Design Considerations
The general idea is to map vCard parameters, properties, and value The general idea is to map vCard parameters, properties, and value
types to XML elements. For example, the "FN" property is mapped to types to XML elements. For example, the "FN" property is mapped to
the "fn" element. That element in turn contains a text element whose the "fn" element. That element in turn contains a text element whose
content corresponds to the vCard property's value. content corresponds to the vCard property's value.
vCard parameters are also mapped to XML elements. They are contained vCard parameters are also mapped to XML elements. They are contained
in the <parameters> element, which is contained in property elements. in the <parameters> element, which is contained in property elements.
For example, the "TYPE" parameter applied to the "TEL" property would For example, the "TYPE" parameter applied to the "TEL" property would
look like the following in XML: look like the following in XML:
skipping to change at page 6, line 32 skipping to change at page 6, line 37
is equivalent to: is equivalent to:
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
contact.FN=... contact.FN=...
contact.EMAIL=... contact.EMAIL=...
media.PHOTO=... media.PHOTO=...
CATEGORIES=... CATEGORIES=...
END:VCARD END:VCARD
4.1. Extensibility 5.1. Extensibility
The original vCard format is extensible. New properties, parameters, The original vCard format is extensible. New properties, parameters,
data types and values (collectively known as vCard objects) can be data types and values (collectively known as vCard objects) can be
registered with IANA. It is expected that these vCard extensions registered with IANA. It is expected that these vCard extensions
will also specify extensions to the XML format described in this will also specify extensions to the XML format described in this
document. document.
Unregistered extensions (i.e. those starting with "X-" and Unregistered extensions (i.e. those starting with "X-" and
"VND-...-") are expressed in XML by using elements starting with "x-" "VND-...-") are expressed in XML by using elements starting with "x-"
and "vnd-...-". Usage of XML namespaces for extensibility is and "vnd-...-". Usage of XML namespaces [W3C.REC-xml-names-20091208]
RECOMMENDED for extensions that have no equivalent in plain text for extensibility is RECOMMENDED for extensions that have no
vCard. Refer to Section 5 for the implications when converting equivalent in plain text vCard. Refer to Section 6 for the
between plain-text vCard and XML. implications when converting between plain-text vCard and XML.
Examples: Examples:
<x-my-prop> <x-my-prop>
<parameters> <parameters>
<pref>1</pref> <pref>1</pref>
</parameters>
<text>value goes here</text> <text>value goes here</text>
<x-my-prop> <x-my-prop>
<ext:my-prop <ext:my-prop
ext:xmlns="http://example.com/extensions/my-vcard"> ext:xmlns="http://example.com/extensions/my-vcard">
<parameters> <parameters>
<pref>1</pref> <pref>1</pref>
</parameters> <!-- Core vCard elements --> </parameters> <!-- Core vCard elements -->
<text>value goes here</text> <!-- are still accessible --> <text>value goes here</text> <!-- are still accessible -->
</ext:my-prop> </ext:my-prop>
skipping to change at page 7, line 38 skipping to change at page 7, line 39
In the original vCard format, the "VERSION" property was mandatory In the original vCard format, the "VERSION" property was mandatory
and played a role in extensibility. In XML, this property is absent. and played a role in extensibility. In XML, this property is absent.
Its role is played by the vCard core namespace identifier, which Its role is played by the vCard core namespace identifier, which
includes the version number. vCard revisions will use a different includes the version number. vCard revisions will use a different
namespace. namespace.
Parameters containing a list of values are expressed using a list of Parameters containing a list of values are expressed using a list of
elements in XML (e.g. the <type> element). elements in XML (e.g. the <type> element).
4.2. Limitations 5.2. Limitations
The schema does not validate the cardinality of properties. This is The schema does not validate the cardinality of properties. This is
a limitation of the schema definition language. Cardinalities of the a limitation of the schema definition language. Cardinalities of the
original vCard format [I-D.ietf-vcarddav-vcardrev] MUST still be original vCard format [I-D.ietf-vcarddav-vcardrev] MUST still be
respected. respected.
Some constructs (e.g. value enumerations in type parameters) have Some constructs (e.g. value enumerations in type parameters) have
additional ordering constraints in XML. This is a result of additional ordering constraints in XML. This is a result of
limitations of the schema definition language and the order is limitations of the schema definition language and the order is
arbitrary. The order MUST be respected in XML for the vCard to be arbitrary. The order MUST be respected in XML for the vCard to be
valid. However, reordering as part of conversion to or from plain valid. However, reordering as part of conversion to or from plain
vCard MAY happen. vCard MAY happen.
5. Format Conversions 6. Format Conversions
When converting from XML vCard (this specification) to plain-text When converting from XML vCard (this specification) to plain-text
vCard [I-D.ietf-vcarddav-vcardrev], the following rules apply: vCard [I-D.ietf-vcarddav-vcardrev], the following rules apply:
o Properties in the vCard 4 namespace: o Properties in the vCard 4 namespace:
* If the converter knows of a specific plain-text representation * If the converter knows of a specific plain-text representation
for this property, it uses it. For example, the <adr> element for this property, it uses it. For example, the <adr> element
corresponds to the "ADR" property, which is encoded using corresponds to the "ADR" property, which is encoded using
comma-separated lists separated by semi-colons. comma-separated lists separated by semi-colons.
skipping to change at page 10, line 7 skipping to change at page 10, line 7
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:J. Doe FN:J. Doe
N:Doe;J.;; N:Doe;J.;;
X-FILE;TYPE=image/jpeg:alien.jpg X-FILE;TYPE=image/jpeg:alien.jpg
XML:<a xmlns="http://www.w3.org/1999/xhtml"\n XML:<a xmlns="http://www.w3.org/1999/xhtml"\n
href="http://www.example.com">My web page!</a> href="http://www.example.com">My web page!</a>
END:VCARD END:VCARD
6. Security Considerations 7. Security Considerations
All the security considerations applicable to plain vCard All the security considerations applicable to plain vCard
[I-D.ietf-vcarddav-vcardrev] are applicable to this document as well. [I-D.ietf-vcarddav-vcardrev] are applicable to this document as well.
7. IANA Considerations 8. IANA Considerations
7.1. Registration of the XML Namespace 8.1. Registration of the XML Namespace
URI: urn:ietf:params:xml:ns:vcard-4.0 URI: urn:ietf:params:xml:ns:vcard-4.0
Registrant Contact: Simon Perreault <simon.perreault@viagenie.ca> Registrant Contact: Simon Perreault <simon.perreault@viagenie.ca>
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
7.2. Media Type 8.2. Media Type
This section defines the MIME media type for use with vCard-in-XML This section defines the MIME media type [RFC4288] for use with
data. vCard-in-XML data.
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of media type application/vcard+xml Subject: Registration of media type application/vcard+xml
Type name: application Type name: application
Subtype name: vcard+xml Subtype name: vcard+xml
Required parameters: none Required parameters: none
Optional parameters: none Optional parameters: charset as defined for application/xml in
[RFC3023]; per [RFC3023], use of the charset parameter with the
value "utf-8" is "STRONGLY RECOMMENDED"
Encoding considerations: Same as for application/xml. Encoding considerations: Same as encoding considerations of
application/xml as specified in [RFC3023]
Security considerations: See Section 6. Security considerations: See Section 7.
Interoperability considerations: This media type provides an Interoperability considerations: This media type provides an
alternative syntax to vCard data [I-D.ietf-vcarddav-vcardrev] alternative syntax to vCard data [I-D.ietf-vcarddav-vcardrev]
based on XML. based on XML.
Published specification: This specification. Published specification: This specification.
Applications which use this media type: Applications that currently Applications which use this media type: Applications that currently
make use of the text/vcard media type can use this as an make use of the text/vcard media type can use this as an
alternative. alternative. In general, applications that maintain or process
contact information can use this media type.
Additional information: Additional information:
Magic number(s): none Magic number(s): none
File extension(s): XML data should use ".xml" as the file File extension(s): XML data should use ".xml" as the file
extension. extension.
Macintosh file type code(s): none Macintosh file type code(s): none
skipping to change at page 11, line 25 skipping to change at page 11, line 32
Perreault <simon.perreault@viagenie.ca> Perreault <simon.perreault@viagenie.ca>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author: Simon Perreault Author: Simon Perreault
Change controller: IETF Change controller: IETF
8. Acknowledgements 9. Acknowledgements
Thanks to the following people for their input: Thanks to the following people for their input:
Alexey Melnikov, Barry Leiba, Cyrus Daboo, Joe Hildebrand, Joseph Alexey Melnikov, Barry Leiba, Bjorn Hoehrmann, Cyrus Daboo, Joe
Smarr, Marc Blanchet, Peter Saint-Andre, Robins George, Zahhar Hildebrand, Joseph Smarr, Marc Blanchet, Mike Douglas, Peter Saint-
Kirillov, Zoltan Ordogh. Andre, Robins George, Zahhar Kirillov, Zoltan Ordogh.
9. References 10. References
9.1. Normative References 10.1. Normative References
[I-D.ietf-vcarddav-vcardrev] Perreault, S., "vCard Format [I-D.ietf-vcarddav-vcardrev] Perreault, S., "vCard Format
Specification", Specification",
draft-ietf-vcarddav-vcardrev-17 (work draft-ietf-vcarddav-vcardrev-19 (work
in progress), April 2011. in progress), April 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs
to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997.
[RFC3023] Murata, M., St. Laurent, S., and D.
Kohn, "XML Media Types", RFC 3023,
January 2001.
[W3C.REC-xml-20081126] Yergeau, F., Maler, E., Paoli, J., [W3C.REC-xml-20081126] Yergeau, F., Maler, E., Paoli, J.,
Sperberg-McQueen, C., and T. Bray, Sperberg-McQueen, C., and T. Bray,
"Extensible Markup Language (XML) 1.0 "Extensible Markup Language (XML) 1.0
(Fifth Edition)", World Wide Web (Fifth Edition)", World Wide Web
Consortium Recommendation REC-xml- Consortium Recommendation REC-xml-
20081126, November 2008, <http:// 20081126, November 2008, <http://
www.w3.org/TR/2008/REC-xml-20081126>. www.w3.org/TR/2008/REC-xml-20081126>.
[W3C.REC-xml-names-20091208] Tobin, R., Hollander, D., Thompson, H.,
Bray, T., and A. Layman, "Namespaces in
XML 1.0 (Third Edition)", World Wide
Web Consortium Recommendation REC-xml-
names-20091208, December 2009, <http://
www.w3.org/TR/2009/
REC-xml-names-20091208>.
[relaxng] Clark, J., "RELAX NG Specification", [relaxng] Clark, J., "RELAX NG Specification",
December 2001. December 2001.
[relaxng-compact] Clark, J., "RELAX NG Compact Syntax", [relaxng-compact] Clark, J., "RELAX NG Compact Syntax",
November 2002, <http://www.relaxng.org/ November 2002, <http://www.relaxng.org/
compact-20021121.html>. compact-20021121.html>.
9.2. Informative References 10.2. Informative References
[I-D.dawson-vcard-xml-dtd] Dawson, F., "The vCard v3.0 XML DTD", [I-D.dawson-vcard-xml-dtd] Dawson, F., "The vCard v3.0 XML DTD",
draft-dawson-vcard-xml-dtd-03 (work in draft-dawson-vcard-xml-dtd-03 (work in
progress), June 1998. progress), June 1998.
[RFC4288] Freed, N. and J. Klensin, "Media Type [RFC4288] Freed, N. and J. Klensin, "Media Type
Specifications and Registration Specifications and Registration
Procedures", BCP 13, RFC 4288, Procedures", BCP 13, RFC 4288,
December 2005. December 2005.
skipping to change at page 17, line 46 skipping to change at page 18, line 20
| element group { | element group {
attribute name { text }, attribute name { text },
property* property*
})+ })+
}+ }+
} }
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 -08 B.1. Changes in -09
o Added "Conventions" section with reference to RFC2119.
o Fixed bad XML in example.
o Updated MIME type registration following feedback from
ietf-types@iana.org.
B.2. Changes in -08
o Synchronized with draft-ietf-vcarddav-vcardrev-17. o Synchronized with draft-ietf-vcarddav-vcardrev-17.
o Added some references. o Added some references.
o Fixed bad XML in example. o Fixed bad XML in example.
o Added <text> element around pid param value. o Added <text> element around pid param value.
B.2. Changes in -07 B.3. Changes in -07
o Synchronized with draft-ietf-vcarddav-vcardrev-16. o Synchronized with draft-ietf-vcarddav-vcardrev-16.
o Fixed bad XML in example. o Fixed bad XML in example.
o Fixed <categories> which now takes a value-text-list. o Fixed <categories> which now takes a value-text-list.
o All parameters now use value elements. This affects type, o All parameters now use value elements. This affects type,
calscale, and pref. calscale, and pref.
B.3. Changes in -06 B.4. Changes in -06
o Synchronized with draft-ietf-vcarddav-vcardrev-15. o Synchronized with draft-ietf-vcarddav-vcardrev-15.
B.4. Changes in -05 B.5. Changes in -05
o Synchronized with draft-ietf-vcarddav-vcardrev-13. o Synchronized with draft-ietf-vcarddav-vcardrev-13.
B.5. Changes in -04 B.6. Changes in -04
o Synchronized with draft-ietf-vcarddav-vcardrev-12. o Synchronized with draft-ietf-vcarddav-vcardrev-12.
o Added application/vcard+xml media type. o Added application/vcard+xml media type.
o Added rules for backslash escaping and quoting when converting. o Added rules for backslash escaping and quoting when converting.
o Added description of <vcards> element. o Added description of <vcards> element.
o Described group construct in XML. o Described group construct in XML.
B.6. Changes in -03 B.7. Changes in -03
o Created "Format Conversions" section. o Created "Format Conversions" section.
o Turned more <type> parameter values into plain text. o Turned more <type> parameter values into plain text.
o Removed need for empty value elements in components. o Removed need for empty value elements in components.
o Wrapped value of <sex>, <class>, and <kind> in value elements. o Wrapped value of <sex>, <class>, and <kind> in value elements.
B.7. Changes in -02 B.8. Changes in -02
o Synchronized with draft-ietf-vcarddav-vcardrev-10. o Synchronized with draft-ietf-vcarddav-vcardrev-10.
o Turned <type> parameter values into plain text. o Turned <type> parameter values into plain text.
o Moved the "XML" property to vCard base. o Moved the "XML" property to vCard base.
o Changed title to avoid confusion with XML Schema. o Changed title to avoid confusion with XML Schema.
o Added prefixes "value-", "param-", and "property-" in schema. o Added prefixes "value-", "param-", and "property-" in schema.
o Better language for specifying what a parser must ignore. o Better language for specifying what a parser must ignore.
B.8. Changes in -01 B.9. Changes in -01
o Synchronized with draft-ietf-vcarddav-vcardrev-09. o Synchronized with draft-ietf-vcarddav-vcardrev-09.
o Added the <vcards> element to allow multiple vCards in a single o Added the <vcards> element to allow multiple vCards in a single
XML file. XML file.
o Created the <parameters> container element. o Created the <parameters> container element.
o Use text value for enumeration in <class> element. o Use text value for enumeration in <class> element.
o Created the "XML" vCard property. o Created the "XML" vCard property.
o Added IANA considerations section. o Added IANA considerations section.
o Added security considerations section. o Added security considerations section.
B.9. Changes in -00 B.10. Changes in -00
o Same as draft-perreault-vcarddav-vcardxml-02. o Same as draft-perreault-vcarddav-vcardxml-02.
Author's Address Author's Address
Simon Perreault Simon Perreault
Viagenie Viagenie
2600 boul. Laurier, suite 625 2600 boul. Laurier, suite 625
Quebec, QC G1V 4W1 Quebec, QC G1V 4W1
Canada Canada
 End of changes. 44 change blocks. 
83 lines changed or deleted 114 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/