draft-ietf-vcarddav-vcardxml-10.txt   draft-ietf-vcarddav-vcardxml-11.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Intended status: Standards Track May 20, 2011 Intended status: Standards Track May 26, 2011
Expires: November 21, 2011 Expires: November 27, 2011
xCard: vCard XML Representation xCard: vCard XML Representation
draft-ietf-vcarddav-vcardxml-10 draft-ietf-vcarddav-vcardxml-11
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 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. 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."
This Internet-Draft will expire on November 21, 2011. This Internet-Draft will expire on November 27, 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
skipping to change at page 2, line 13 skipping to change at page 2, line 13
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. The Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Example: Author's XML vCard . . . . . . . . . . . . . . . . . 3 4. Example: Author's XML vCard . . . . . . . . . . . . . . . . . 3
5. Design Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Design Considerations . . . . . . . . . . . . . . . . . . . . 5
5.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 6
5.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 8
6. Format Conversions . . . . . . . . . . . . . . . . . . . . . . 8 6. Format Conversions . . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8.1. Registration of the XML Namespace . . . . . . . . . . . . 10 8.1. Registration of the XML Namespace . . . . . . . . . . . . 10
8.2. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 11 8.2. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 11
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Normative References . . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . . 12
10.2. Informative References . . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . . 13
Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 13 Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 14
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) . . . . . . . . . . . . . . . . . . . . 21 publication) . . . . . . . . . . . . . . . . . . . . 22
B.1. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 21 B.1. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 22
B.2. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 22 B.2. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 22
B.3. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 22 B.3. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 22
B.4. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 22 B.4. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 23
B.5. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 22 B.5. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 23
B.6. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 22 B.6. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 23
B.7. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 22 B.7. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 23
B.8. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 23 B.8. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 23
B.9. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 23 B.9. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 23
B.10. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 23 B.10. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 24
B.11. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 24 B.11. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 24
B.12. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 24
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 xCard, an XML [W3C.REC-xml-20081126] representation document defines xCard, an XML [W3C.REC-xml-20081126] representation
for vCard. The underlying data structure is exactly the same, for vCard. The underlying data structure is exactly the same,
enabling a 1-to-1 mapping between the original vCard format and the enabling a 1-to-1 mapping between the original vCard format and the
XML representation. The XML formatting may be preferred in some XML representation. The XML formatting may be preferred in some
skipping to change at page 3, line 29 skipping to change at page 3, line 29
world. world.
2. Conventions 2. 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", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. The Schema 3. The Schema
The schema is expressed in the RELAX NG language The schema is expressed in the RELAX NG language [ISO.19757-2.2008]
[relaxng][relaxng-compact] and is found in Appendix A. and is found in Appendix A.
4. 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>Perreault</surname> <surname>Perreault</surname>
<given>Simon</given> <given>Simon</given>
skipping to change at page 6, line 46 skipping to change at page 6, line 46
VERSION:4.0 VERSION:4.0
contact.FN=... contact.FN=...
contact.EMAIL=... contact.EMAIL=...
media.PHOTO=... media.PHOTO=...
CATEGORIES=... CATEGORIES=...
END:VCARD END:VCARD
5.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 elements, not to
registered with IANA. It is expected that these vCard extensions be confused with XML elements) can be registered with IANA (see
will also specify extensions to the XML format described in this [I-D.ietf-vcarddav-vcardrev] section 10.2). It is expected that
document. these vCard extensions will also specify extensions to the XML format
described in this document.
New XML vCard property and parameter element names MUST be lower- New XML vCard property and parameter element names MUST be lower-
case. This is necessary to ensure that round-tripping between XML case. This is necessary to ensure that round-tripping between XML
and plain-text vCard works correctly. and plain-text vCard works correctly.
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 [W3C.REC-xml-names-20091208] and "vnd-...-". Usage of XML namespaces [W3C.REC-xml-names-20091208]
for extensibility is RECOMMENDED for extensions that have no for extensibility is RECOMMENDED for extensions that have no
equivalent in plain text vCard. Refer to Section 6 for the equivalent in plain text vCard. Refer to Section 6 for the
skipping to change at page 8, line 26 skipping to change at page 8, line 31
When new properties or "X-" proeprties used, a vCard<->xCard When new properties or "X-" proeprties used, a vCard<->xCard
converter might not recognize them, and know what the appropriate converter might not recognize them, and know what the appropriate
default value types are, yet they need to be able to preserve the default value types are, yet they need to be able to preserve the
values. A similar issue arises for unrecognized property parameters. values. A similar issue arises for unrecognized property parameters.
As a result, the following rules are applied when dealing with As a result, the following rules are applied when dealing with
unrecognized properties and property parameters: unrecognized properties and property parameters:
o When converting from vCard to xCard: o When converting from vCard to xCard:
* Any property that does not include a "VALUE" parameter and * Any property that does not include a "VALUE" parameter and
whose default value type is not know MUST be converted using whose default value type is not known MUST be converted using
the value type XML element <unknown>. The content of that the value type XML element <unknown>. The content of that
element is the unprocessed value text. element is the unprocessed value text.
* Any unrecognized property parameter MUST be converted using the * Any unrecognized property parameter MUST be converted using the
value type XML element <unknown>, with its content set to the value type XML element <unknown>, with its content set to the
parameter value text, treated as if it were a text value, or parameter value text, treated as if it were a text value, or
list of text values. list of text values.
* The content of "XML" properties is copied as-is to XML. * The content of "XML" properties is copied as-is to XML.
* Property and parameter XML element names are converted to
lower-case.
* Property value escaping is undone. For example, "\n" becomes a * Property value escaping is undone. For example, "\n" becomes a
NEWLINE character (ASCII decimal 10). NEWLINE character (ASCII decimal 10).
* Double-quoting of parameter values, as well as backslash * Double-quoting of parameter values, as well as backslash
escaping in parameter values, is undone. For example, escaping in parameter values, is undone. For example,
PARAM="\"foo\",\"bar\"" becomes <param>"foo","bar"</param>. PARAM="\"foo\",\"bar\"" becomes <param>"foo","bar"</param>.
o When converting xCard to vCard: o When converting xCard to vCard:
* Properties in the vCard 4 namespace: * Properties in the vCard 4 namespace:
skipping to change at page 9, line 29 skipping to change at page 9, line 38
* Properties in other namespaces are wrapped as-is inside an * Properties in other namespaces are wrapped as-is inside an
"XML" property. "XML" property.
* Any <unknown> property value XML elements are converted * Any <unknown> property value XML elements are converted
directly into vCard values. The containing property MUST NOT directly into vCard values. The containing property MUST NOT
have a "VALUE" parameter. have a "VALUE" parameter.
* Any <unknown> parameter value XML elements are converted as if * Any <unknown> parameter value XML elements are converted as if
they were <text> value type XML elements. they were <text> value type XML elements.
* Property and parameter names are converted to upper-case.
* Property value escaping (Section 3.3 of * Property value escaping (Section 3.3 of
[I-D.ietf-vcarddav-vcardrev]) is carried out. For example, a [I-D.ietf-vcarddav-vcardrev]) is carried out. For example, a
NEWLINE character (ASCII decimal 10) becomes "\n". NEWLINE character (ASCII decimal 10) becomes "\n".
* Double-quoting of parameter values, as well as backslash * Double-quoting of parameter values, as well as backslash
escaping in parameter values, is carried out. For example, escaping in parameter values, is carried out. For example,
<param>"foo","bar"</param> becomes PARAM="\"foo\",\"bar\"". <param>"foo","bar"</param> becomes PARAM="\"foo\",\"bar\"".
For example, these two vCards are equivalent: For example, these two vCards are equivalent:
skipping to change at page 10, line 41 skipping to change at page 10, line 41
X-FILE;MEDIATYPE=image/jpeg:alien.jpg X-FILE;MEDIATYPE=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
7. 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.
XML Signature [W3C.CR-xmldsig-core1-20110303] and XML Encryption
[W3C.CR-xmlenc-core1-20110303] can be used with xCard to provide
authentication and confidentiality.
8. IANA Considerations 8. IANA Considerations
8.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.
8.2. Media Type 8.2. Media Type
This section defines the MIME media type [RFC4288] for use with This section defines the MIME media type [RFC4288] for use with
vCard-in-XML 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
skipping to change at page 12, line 30 skipping to change at page 12, line 35
Thanks to the following people for their input: Thanks to the following people for their input:
Alexey Melnikov, Barry Leiba, Bjorn Hoehrmann, Cyrus Daboo, Joe Alexey Melnikov, Barry Leiba, Bjorn Hoehrmann, Cyrus Daboo, Joe
Hildebrand, Joseph Smarr, Marc Blanchet, Mike Douglas, Peter Saint- Hildebrand, Joseph Smarr, Marc Blanchet, Mike Douglas, Peter Saint-
Andre, Robins George, Zahhar Kirillov, Zoltan Ordogh. Andre, Robins George, Zahhar Kirillov, Zoltan Ordogh.
10. References 10. References
10.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-20 (work draft-ietf-vcarddav-vcardrev-20
in progress), May 2011. (work in progress), May 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. [ISO.19757-2.2008] International Organization for
Kohn, "XML Media Types", RFC 3023, Standardization, "Information
January 2001. technology -- Document Schema
Definition Language (DSDL) -- Part
2: Regular-grammar-based validation
-- RELAX NG", ISO International
Standard 19757-2, October 2008.
[W3C.REC-xml-20081126] Yergeau, F., Maler, E., Paoli, J., [RFC2119] Bradner, S., "Key words for use in
Sperberg-McQueen, C., and T. Bray, RFCs to Indicate Requirement
"Extensible Markup Language (XML) 1.0 Levels", BCP 14, RFC 2119,
(Fifth Edition)", World Wide Web March 1997.
Consortium Recommendation REC-xml-
20081126, November 2008, <http://
www.w3.org/TR/2008/REC-xml-20081126>.
[W3C.REC-xml-names-20091208] Tobin, R., Hollander, D., Thompson, H., [RFC3023] Murata, M., St. Laurent, S., and D.
Bray, T., and A. Layman, "Namespaces in Kohn, "XML Media Types", RFC 3023,
XML 1.0 (Third Edition)", World Wide January 2001.
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", [W3C.REC-xml-20081126] Yergeau, F., Maler, E., Paoli, J.,
December 2001. Sperberg-McQueen, C., and T. Bray,
"Extensible Markup Language (XML)
1.0 (Fifth Edition)", World Wide Web
Consortium Recommendation REC-xml-
20081126, November 2008, <http://
www.w3.org/TR/2008/
REC-xml-20081126>.
[relaxng-compact] Clark, J., "RELAX NG Compact Syntax", [W3C.REC-xml-names-20091208] Tobin, R., Hollander, D., Thompson,
November 2002, <http://www.relaxng.org/ H., Bray, T., and A. Layman,
compact-20021121.html>. "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>.
10.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
draft-dawson-vcard-xml-dtd-03 (work in DTD", draft-dawson-vcard-xml-dtd-03
progress), June 1998. (work in progress), June 1998.
[RFC4288] Freed, N. and J. Klensin, "Media Type [RFC4288] Freed, N. and J. Klensin, "Media
Specifications and Registration Type Specifications and Registration
Procedures", BCP 13, RFC 4288, Procedures", BCP 13, RFC 4288,
December 2005. December 2005.
[W3C.CR-xmldsig-core1-20110303] Reagle, J., Roessler, T., Solo, D.,
Yiu, K., Eastlake, D., Nystroem, M.,
and F. Hirsch, "XML Signature Syntax
and Processing Version 1.1", World
Wide Web Consortium CR CR-xmldsig-
core1-20110303, March 2011, <http://
www.w3.org/TR/2011/
CR-xmldsig-core1-20110303>.
[W3C.CR-xmlenc-core1-20110303] Eastlake, D., Reagle, J., Hirsch,
F., and T. Roessler, "XML Encryption
Syntax and Processing Version 1.1",
World Wide Web Consortium CR CR-
xmlenc-core1-20110303, March 2011, <
http://www.w3.org/TR/2011/
CR-xmlenc-core1-20110303>.
Appendix A. Relax NG Schema Appendix A. Relax NG Schema
default namespace = "urn:ietf:params:xml:ns:vcard-4.0" default namespace = "urn:ietf:params:xml:ns:vcard-4.0"
### Section 3.3: vCard Format Specification ### Section 3.3: vCard Format Specification
# #
# 3.3 # 3.3
iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" } iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" }
x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" } x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" }
skipping to change at page 21, line 30 skipping to change at page 22, line 8
| 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 -10 B.1. Changes in -11
o Refer to ISO standard for Relax NG.
o Adjust text on vCard extensibility through IANA.
o Add missing case conversion rules.
o Refer to XML Signature and XML Encryption in security
considerations section.
B.2. Changes in -10
o Fixed bugs in examples. o Fixed bugs in examples.
o New XML elements MUST be lower-case. o New XML elements MUST be lower-case.
o Adjusted case conversion rules for unknown parameters. o Adjusted case conversion rules for unknown parameters.
o Added utc-offset as possible value type to tz property. o Added utc-offset as possible value type to tz property.
o Added "agent" and "emergency" related values. o Added "agent" and "emergency" related values.
skipping to change at page 22, line 7 skipping to change at page 22, line 43
o Added cross-references to vcardrev sections. o Added cross-references to vcardrev sections.
o Add <unknown> element for round-tripping. o Add <unknown> element for round-tripping.
o Tweak sex grammar. o Tweak sex grammar.
o "Structured" properties don't need <text> elements. o "Structured" properties don't need <text> elements.
o Fixed wrong example. o Fixed wrong example.
B.2. Changes in -09 B.3. Changes in -09
o Added "Conventions" section with reference to RFC2119. o Added "Conventions" section with reference to RFC2119.
o Fixed bad XML in example. o Fixed bad XML in example.
o Updated MIME type registration following feedback from o Updated MIME type registration following feedback from
ietf-types@iana.org. ietf-types@iana.org.
B.3. Changes in -08 B.4. 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.4. Changes in -07 B.5. 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.5. Changes in -06 B.6. Changes in -06
o Synchronized with draft-ietf-vcarddav-vcardrev-15. o Synchronized with draft-ietf-vcarddav-vcardrev-15.
B.6. Changes in -05 B.7. Changes in -05
o Synchronized with draft-ietf-vcarddav-vcardrev-13. o Synchronized with draft-ietf-vcarddav-vcardrev-13.
B.7. Changes in -04 B.8. 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.8. Changes in -03 B.9. 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.9. Changes in -02 B.10. 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.10. Changes in -01 B.11. 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.11. Changes in -00 B.12. 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. 33 change blocks. 
74 lines changed or deleted 117 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/