draft-ietf-vcarddav-vcardxml-02.txt   draft-ietf-vcarddav-vcardxml-03.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Intended status: Standards Track March 8, 2010 Intended status: Standards Track May 9, 2010
Expires: September 9, 2010 Expires: November 10, 2010
vCard XML Representation vCard XML Representation
draft-ietf-vcarddav-vcardxml-02 draft-ietf-vcarddav-vcardxml-03
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 to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 9, 2010. This Internet-Draft will expire on November 10, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 15 skipping to change at page 2, line 15
described in the BSD License. described in the BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Example: Author's XML vCard . . . . . . . . . . . . . . . . . 3 3. Example: Author's XML vCard . . . . . . . . . . . . . . . . . 3
4. Design Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Design Considerations . . . . . . . . . . . . . . . . . . . . 5
4.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 5
4.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. Format Conversions . . . . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6.1. Registration of the XML Namespace . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Registration of the XML Namespace . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9
Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . . 9
Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 9
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) . . . . . . . . . . . . . . . . . . . . 13 publication) . . . . . . . . . . . . . . . . . . . . 15
B.1. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 13 B.1. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 15
B.2. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 14 B.2. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 15
B.3. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 14 B.3. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 16
B.4. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 16
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. It is a text-based and exchanging information about individuals. It is a text-based
format (as opposed to a binary format). This document defines an XML format (as opposed to a binary format). This document defines an XML
representation for vCard. The underlying data structure is exactly representation for vCard. The underlying data structure is exactly
the same, enabling a 1-to-1 mapping between the original vCard format the same, enabling a 1-to-1 mapping between the original vCard format
and the XML representation. The XML formatting may be preferred in and the XML representation. The XML formatting may be preferred in
some contexts where an XML engine is readily available and may be some contexts where an XML engine is readily available and may be
skipping to change at page 3, line 34 skipping to change at page 3, line 34
3. Example: Author's XML vCard 3. 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>
<prefix><text/></prefix> <prefix/>
<suffix> <suffix>
<text>ing. jr.</text> <text>ing. jr.</text>
<text>M.Sc.</text> <text>M.Sc.</text>
</suffix> </suffix>
</n> </n>
<bday><date>--0203</date></bday> <bday><date>--0203</date></bday>
<anniversary> <anniversary>
<date-time>20090808T1430-0500</date-time> <date-time>20090808T1430-0500</date-time>
</anniversary> </anniversary>
<sex>1</sex> <sex><integer>1</integer></sex>
<lang> <lang>
<parameters><pref>1</pref></parameters> <parameters><pref>1</pref></parameters>
<language-tag>fr</language-tag> <language-tag>fr</language-tag>
</lang> </lang>
<lang> <lang>
<parameters><pref>2</pref></parameters> <parameters><pref>2</pref></parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<org> <org>
<parameters><type>work</type></parameters> <parameters><type>work</type></parameters>
<text>Viagenie</text> <text>Viagenie</text>
</org> </org>
<adr> <adr>
<parameters><type>work</type></parameters> <parameters><type>work</type></parameters>
<pobox><text/></pobox> <pobox/>
<ext><text>Suite 625</text></ext> <ext><text>Suite 625</text></ext>
<street><text>2600 boul. Laurier</text></street> <street><text>2600 boul. Laurier</text></street>
<locality><text>Quebec</text></locality> <locality><text>Quebec</text></locality>
<region><text>QC</text></region> <region><text>QC</text></region>
<code><text>G1V 4W1</text></code> <code><text>G1V 4W1</text></code>
<country><text>Canada</text></country> <country><text>Canada</text></country>
</adr> </adr>
<tel> <tel>
<parameters> <parameters>
<type>work</type> <type>work</type>
skipping to change at page 4, line 51 skipping to change at page 4, line 51
</tel> </tel>
<email> <email>
<parameters><type>work</type></parameters> <parameters><type>work</type></parameters>
<text>simon.perreault@viagenie.ca</text> <text>simon.perreault@viagenie.ca</text>
</email> </email>
<geo> <geo>
<parameters><type>work</type></parameters> <parameters><type>work</type></parameters>
<uri>geo:46.772673,-71.282945</uri> <uri>geo:46.772673,-71.282945</uri>
</geo> </geo>
<key> <key>
<parameters><type><work/></type></parameters> <parameters><type>work</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>
<class>PUBLIC</class> <class><text>PUBLIC</text></class>
</vcard> </vcard>
</vcards> </vcards>
4. Design Considerations 4. 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.
skipping to change at page 7, line 5 skipping to change at page 7, line 5
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. Security Considerations 5. Format Conversions
When converting from XML vCard (this specification) to plain-text
vCard [I-D.ietf-vcarddav-vcardrev], the following rules apply:
o Properties in the vCard 4 namespace:
o
* If the converter knows of a specific plain-text representation
for this property, it uses it. For example, the <adr> element
corresponds to the "ADR" property, which is encoded using
comma-separated lists separated by semi-colons.
* Otherwise, the property name is taken from the element name,
property parameters are taken from the <parameters> element,
and the content of the property is taken from the content of
the value element. If the property element has attributes or
contains other XML elements, they are dropped.
* If a standard property's XML element contains XML elements and
attributes for which the converter doesn't recognize the
expanded name, they are dropped. Therefore, it is RECOMMENDED
to limit extensions to the property level to ensure that all
data is preserved intact in round-trip conversions.
o Properties in other namespaces are wrapped as-is inside an "XML"
property.
When converting from plain-text vCard [I-D.ietf-vcarddav-vcardrev] to
XML vCard (this specification), the following rules apply:
o The content of "XML" properties is converted as-is to XML.
o Properties for which the converter knows of a specific XML
representation use it. For example, the "ADR" property is
represented using the <adr> element and related sub-elements.
o Other properties are converted to XML in the following way:
o
* The XML namespace of the property element is set to the vCard 4
namespace.
* The name of the property element is set to that of the
property.
* If the property has attributes, they get translated as-is into
sub-elements of the <parameters> element
* The property element contains a single <text> element whose
content is copied as-is from the property's value.
For example, these two vCards are equivalent:
<xml version="1.0">
<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcard>
<fn><text>J. Doe</text></fn>
<n>
<surname><text>Doe</text></surname>
<given><text>J.</text></given>
<prefix/>
<suffix/>
</n>
<x-file>
<parameters><type>image/jpeg</type></parameters>
<text>alien.jpg</text>
</x-file>
<a xmlns="http://www.w3.org/1999/xhtml"
href="http://www.example.com">My web page!</a>
</vcard>
</vcards>
</xml>
BEGIN:VCARD
VERSION:4.0
FN:J. Doe
N:Doe;J.;;
X-FILE;TYPE=image/jpeg:alien.jpg
XML:<a xmlns="http://www.w3.org/1999/xhtml"\n
href="http://www.example.com">My web page!</a>
END:VCARD
6. 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.
6. IANA Considerations 7. IANA Considerations
7.1. Registration of the XML Namespace
6.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. Acknowledgements 8. 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, Cyrus Daboo, Joe Hildebrand, Joseph
Smarr, Marc Blanchet, Peter Saint-Andre, Robins George, Zahhar Smarr, Marc Blanchet, Peter Saint-Andre, Robins George, Zahhar
Kirillov, Zoltan Ordogh. Kirillov, Zoltan Ordogh.
8. References 9. References
8.1. Normative References 9.1. Normative References
[I-D.ietf-vcarddav-vcardrev] Perreault, S. and P. Resnick, "vCard [I-D.ietf-vcarddav-vcardrev] Perreault, S. and P. Resnick, "vCard
Format Specification", Format Specification",
draft-ietf-vcarddav-vcardrev-09 (work draft-ietf-vcarddav-vcardrev-11 (work
in progress), October 2009. in progress), May 2010.
[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>.
8.2. Informative References 9.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.
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"
# Value types # Value types
value-text = element text { text } value-text = element text { text }
value-text-list = value-text+ value-text-list = value-text+
value-uri = element uri { xsd:anyURI } value-uri = element uri { xsd:anyURI }
value-date = element date { value-date = element date {
xsd:string { pattern = "\d{8}|\d{4}-\d\d|--\d\d(\d\d)?|---\d\d" } xsd:string { pattern = "\d{8}|\d{4}-\d\d|--\d\d(\d\d)?|---\d\d" }
} }
value-time = element time { value-time = element time {
xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)" xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)"
~ "(Z|[+\-]\d\d(\d\d)?)?" } ~ "(Z|[+\-]\d\d(\d\d)?)?" }
} }
value-date-time = element date-time { value-date-time = element date-time {
xsd:string { pattern = "(\d{8}|--\d{4}|---\d\d)T\d\d(\d\d(\d\d)?)?" xsd:string { pattern = "(\d{8}|--\d{4}|---\d\d)T\d\d(\d\d(\d\d)?)?"
~ "(Z|[+\-]\d\d(\d\d)?)?" } ~ "(Z|[+\-]\d\d(\d\d)?)?" }
} }
value-date-and-or-time = value-date | value-date-time | value-time value-date-and-or-time = value-date | value-date-time | value-time
skipping to change at page 9, line 4 skipping to change at page 10, line 47
xsd:string { pattern = "\d+(\.\d+)?" } xsd:string { pattern = "\d+(\.\d+)?" }
}? }?
param-type = element type { "work" | "home" }* param-type = element type { "work" | "home" }*
param-calscale = element calscale { "gregorian" }? param-calscale = element calscale { "gregorian" }?
# Properties # Properties
property-source = element source { property-source = element source {
element parameters { param-pid, param-pref }, element parameters { param-pid, param-pref },
value-uri value-uri
} }
property-name = element name { value-text } property-name = element name { value-text }
property-kind = element kind { "individual" | "group" | "org" property-kind = element kind {
| "location" | "thing" }* element text { "individual" | "group" | "org" |
"location" | "thing" }*
}
property-fn = element fn { property-fn = element fn {
element parameters { param-language, param-pid, element parameters { param-language, param-pid,
param-pref, param-type }?, param-pref, param-type }?,
value-text value-text
} }
property-n = element n { property-n = element n {
element parameters { param-language }?, element parameters { param-language }?,
element surname { value-text-list }, element surname { value-text-list? },
element given { value-text-list }, element given { value-text-list? },
element prefix { value-text-list }, element prefix { value-text-list? },
element suffix { value-text-list } element suffix { value-text-list? }
} }
property-nickname = element nickname { property-nickname = element nickname {
element parameters { param-language, param-pid, element parameters { param-language, param-pid,
param-pref, param-type }?, param-pref, param-type }?,
value-text-list value-text-list
} }
property-photo = element photo { property-photo = element photo {
element parameters { element parameters {
param-pid, param-pid,
param-pref, param-pref,
skipping to change at page 10, line 4 skipping to change at page 11, line 48
element parameters { param-language }?, element parameters { param-language }?,
value-text value-text
} }
property-death = element death { property-death = element death {
element parameters { param-language }?, element parameters { param-language }?,
value-text value-text
} }
property-anniversary = element anniversary { property-anniversary = element anniversary {
element parameters { param-calscale }?, element parameters { param-calscale }?,
(value-date-and-or-time | value-text) (value-date-and-or-time | value-text)
} }
property-sex = element sex { "0" | "1" | "2" | "9" } property-sex = element sex {
element integer { "0" | "1" | "2" | "9" }
}
property-adr = element adr { property-adr = element adr {
element parameters { element parameters {
param-language, param-language,
param-pid, param-pid,
param-pref, param-pref,
param-type, param-type,
element geo { value-uri }?, element geo { value-uri }?,
element tz { value-text | value-uri }? element tz { value-text | value-uri }?
}?, }?,
element pobox { value-text-list }, element pobox { value-text-list? },
element ext { value-text-list }, element ext { value-text-list? },
element street { value-text-list }, element street { value-text-list? },
element locality { value-text-list }, element locality { value-text-list? },
element region { value-text-list }, element region { value-text-list? },
element code { value-text-list }, element code { value-text-list? },
element country { value-text-list } element country { value-text-list? }
} }
property-label = element label { property-label = element label {
element parameters { param-language, param-pid, element parameters { param-language, param-pid,
param-pref, param-type }?, param-pref, param-type }?,
value-text value-text
} }
property-tel = element tel { property-tel = element tel {
element parameters { element parameters {
param-pid, param-pid,
param-pref, param-pref,
skipping to change at page 12, line 18 skipping to change at page 14, line 17
property-rev = element rev { value-timestamp } property-rev = element rev { value-timestamp }
property-sort-string = element sort-string { property-sort-string = element sort-string {
element surname { value-text }+, element surname { value-text }+,
element given { value-text }* element given { value-text }*
} }
property-sound = element sound { property-sound = element sound {
element parameters { element parameters {
param-language, param-language,
param-pid, param-pid,
param-pref, param-pref,
element type { element type { "work" | "home" |
element work { empty }?, element media { value-text } }*
element home { empty }?,
element media { value-text }?
} }
}?, }?,
(value-binary | value-uri) (value-binary | value-uri)
} }
property-uid = element uid { value-uri } property-uid = element uid { value-uri }
property-clientpidmap = element clientpidmap { property-clientpidmap = element clientpidmap {
element sourceid { xsd:positiveInteger }, element sourceid { xsd:positiveInteger },
value-uri value-uri
} }
property-url = element url { property-url = element url {
element parameters { param-pid, param-pref, param-type }?, element parameters { param-pid, param-pref, param-type }?,
value-uri value-uri
} }
property-class = element class { "PUBLIC" | "PRIVATE" | "CONFIDENTIAL" } property-class = element class {
element text { "PUBLIC" | "PRIVATE" | "CONFIDENTIAL" }
}
property-key = element key { property-key = element key {
element parameters { element parameters {
param-pid, param-pid,
param-pref, param-pref,
element type { element type { "work" | "home" |
element work { empty }?, element media { value-text } }*
element home { empty }?,
element media { value-text }?
} }
}?, }?,
(value-binary | value-uri) (value-binary | value-uri)
} }
property-fburl = element fburl { property-fburl = element fburl {
element parameters { param-pid, param-pref, param-type }?, element parameters { param-pid, param-pref, param-type }?,
value-uri value-uri
} }
property-caladruri = element caladruri { property-caladruri = element caladruri {
element parameters { param-pid, param-pref, param-type }?, element parameters { param-pid, param-pref, param-type }?,
value-uri value-uri
} }
property-caluri = element caluri { property-caluri = element caluri {
element parameters { param-pid, param-pref, param-type }?, element parameters { param-pid, param-pref, param-type }?,
value-uri value-uri
} }
# Top-level grammar # Top-level grammar
property = property-adr | property-anniversary | property-bday property = property-adr | property-anniversary | property-bday
| property-birth | property-caladruri | property-caluri | property-birth | property-caladruri | property-caluri
| property-categories | property-class | property-clientpidmap | property-categories | property-class | property-clientpidmap
| property-dday | property-death | property-email | property-dday | property-death | property-email
skipping to change at page 13, line 41 skipping to change at page 15, line 37
| 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 -02 B.1. Changes in -03
o Created "Format Conversions" section.
o Turned more <type> parameter values into plain text.
o Removed need for empty value elements in components.
o Wrapped value of <sex>, <class>, and <kind> in value elements.
B.2. 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.2. Changes in -01 B.3. 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.3. Changes in -00 B.4. 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. 
60 lines changed or deleted 159 lines changed or added

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