Network Working Group S. Perreault
Internet-Draft Viagenie
Intended status: Standards Track April 9, 2011
Expires: October 11, 2011
vCard XML Representation
draft-ietf-vcarddav-vcardxml-09
Abstract
This document defines the XML schema of the vCard data format.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 11, 2011.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Perreault Expires October 11, 2011 [Page 1]
Internet-Draft vCard XML April 2011
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Example: Author's XML vCard . . . . . . . . . . . . . . . . . 3
5. Design Considerations . . . . . . . . . . . . . . . . . . . . 5
5.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 6
5.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 7
6. Format Conversions . . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8.1. Registration of the XML Namespace . . . . . . . . . . . . 10
8.2. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 12
Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 18
B.1. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 18
B.2. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 18
B.3. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 18
B.4. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 19
B.5. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 19
B.6. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 19
B.7. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 19
B.8. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 19
B.9. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 20
B.10. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 20
Perreault Expires October 11, 2011 [Page 2]
Internet-Draft vCard XML April 2011
1. Introduction
vCard [I-D.ietf-vcarddav-vcardrev] is a data format for representing
and exchanging information about individuals and other entities. It
is a text-based format (as opposed to a binary format). This
document defines an XML [W3C.REC-xml-20081126] representation for
vCard. The underlying data structure is exactly the same, enabling a
1-to-1 mapping between the original vCard format and the XML
representation. The XML formatting may be preferred in some contexts
where an XML engine is readily available and may be reused instead of
writing a stand-alone vCard parser.
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
world.
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
[relaxng][relaxng-compact] and is found in Appendix A.
4. Example: Author's XML vCard
Simon PerreaultPerreaultSimoning. jr.M.Sc.--020320090808T1430-0500M
Perreault Expires October 11, 2011 [Page 3]
Internet-Draft vCard XML April 2011
1fr2enworkViageniework2875 boul. Laurier, suite D2-630QuebecQCG1V 2M2Canadaworkvoicetel:+1-418-656-9254;ext=102worktextvoicecellvideotel:+1-418-262-6501
Perreault Expires October 11, 2011 [Page 4]
Internet-Draft vCard XML April 2011
worksimon.perreault@viagenie.caworkgeo:46.766336,-71.28955workhttp://www.viagenie.ca/simon.perreault/simon.ascAmerica/Montreal
5. Design Considerations
The general idea is to map vCard parameters, properties, and value
types to XML elements. For example, the "FN" property is mapped to
the "fn" element. That element in turn contains a text element whose
content corresponds to the vCard property's value.
vCard parameters are also mapped to XML elements. They are contained
in the element, which is contained in property elements.
For example, the "TYPE" parameter applied to the "TEL" property would
look like the following in XML:
voicevideotel:+1-555-555-555
Parameters taking a list of values are simply repeated multiple
times, once for each value in the list.
Properties having structured values (e.g. the "N" property) are
expressed by XML element trees. Element names in that tree (e.g.
"surname", "given", etc.) do not have a vCard equivalent since they
are identified by position in plain vCard.
Line folding is a non-issue in XML. Therefore, the mapping from
vCard to XML is done after the unfolding procedure is carried out.
Conversely, the mapping from XML to vCard is done before the folding
procedure is carried out.
Perreault Expires October 11, 2011 [Page 5]
Internet-Draft vCard XML April 2011
A top-level element is used as root. It contains one or
more element, each representing a complete vCard. The
element MUST be present even when only a single vCard is
present in an XML document.
The group construct (Section 3.2 in [I-D.ietf-vcarddav-vcardrev]) is
represented with the element. The "name" attribute contains
the group's name. For example:
............
is equivalent to:
BEGIN:VCARD
VERSION:4.0
contact.FN=...
contact.EMAIL=...
media.PHOTO=...
CATEGORIES=...
END:VCARD
5.1. Extensibility
The original vCard format is extensible. New properties, parameters,
data types and values (collectively known as vCard objects) can be
registered with IANA. It is expected that these vCard extensions
will also specify extensions to the XML format described in this
document.
Unregistered extensions (i.e. those starting with "X-" and
"VND-...-") are expressed in XML by using elements starting with "x-"
and "vnd-...-". Usage of XML namespaces [W3C.REC-xml-names-20091208]
for extensibility is RECOMMENDED for extensions that have no
equivalent in plain text vCard. Refer to Section 6 for the
implications when converting between plain-text vCard and XML.
Perreault Expires October 11, 2011 [Page 6]
Internet-Draft vCard XML April 2011
Examples:
1value goes here1value goes here
Note that extension elements do not need the "X- or "VND-" prefix in
XML. The XML namespace mechanism is sufficient.
A vCard XML parser MUST ignore XML elements and attributes for which
it doesn't recognize the expanded name. The normal behaviour of
ignoring XML processing instructions whose target is not recognized
MUST also be followed.
In the original vCard format, the "VERSION" property was mandatory
and played a role in extensibility. In XML, this property is absent.
Its role is played by the vCard core namespace identifier, which
includes the version number. vCard revisions will use a different
namespace.
Parameters containing a list of values are expressed using a list of
elements in XML (e.g. the element).
5.2. Limitations
The schema does not validate the cardinality of properties. This is
a limitation of the schema definition language. Cardinalities of the
original vCard format [I-D.ietf-vcarddav-vcardrev] MUST still be
respected.
Some constructs (e.g. value enumerations in type parameters) have
additional ordering constraints in XML. This is a result of
limitations of the schema definition language and the order is
arbitrary. The order MUST be respected in XML for the vCard to be
valid. However, reordering as part of conversion to or from plain
vCard MAY happen.
Perreault Expires October 11, 2011 [Page 7]
Internet-Draft vCard XML April 2011
6. 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:
* If the converter knows of a specific plain-text representation
for this property, it uses it. For example, the 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 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.
o Property value escaping (Section 3.3 of
[I-D.ietf-vcarddav-vcardrev]) is carried out. For example, a
NEWLINE character (ASCII decimal 10) becomes "\n".
o Double-quoting of parameter values, as well as backslash escaping
in parameter values, is carried out. For example,
"foo","bar" becomes PARAM="\"foo\",\"bar\"".
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 copied 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 element and related sub-elements.
o Other properties are converted to XML in the following way:
* The XML namespace of the property element is set to the vCard 4
namespace.
Perreault Expires October 11, 2011 [Page 8]
Internet-Draft vCard XML April 2011
* The name of the property element is set to the lowercased name
of the property.
* If the property has parameters, they get translated as-is
(without lowercasing of parameter names, removal of backslash
escaping, and removal of quoting) into sub-elements of the
element
* The property element contains a single element whose
content is copied as-is from the property's value.
o Property value escaping is undone. For example, "\n" becomes a
NEWLINE character (ASCII decimal 10).
o Double-quoting of parameter values, as well as backslash escaping
in parameter values, is undone. For example,
PARAM="\"foo\",\"bar\"" becomes "foo","bar".
For example, these two vCards are equivalent:
J. DoeDoeJ.image/jpegalien.jpgMy web page!
BEGIN:VCARD
VERSION:4.0
FN:J. Doe
N:Doe;J.;;
X-FILE;TYPE=image/jpeg:alien.jpg
XML:My web page!
Perreault Expires October 11, 2011 [Page 9]
Internet-Draft vCard XML April 2011
END:VCARD
7. Security Considerations
All the security considerations applicable to plain vCard
[I-D.ietf-vcarddav-vcardrev] are applicable to this document as well.
8. IANA Considerations
8.1. Registration of the XML Namespace
URI: urn:ietf:params:xml:ns:vcard-4.0
Registrant Contact: Simon Perreault
XML: None. Namespace URIs do not represent an XML specification.
8.2. Media Type
This section defines the MIME media type [RFC4288] for use with
vCard-in-XML data.
To: ietf-types@iana.org
Subject: Registration of media type application/vcard+xml
Type name: application
Subtype name: vcard+xml
Required 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 encoding considerations of
application/xml as specified in [RFC3023]
Security considerations: See Section 7.
Interoperability considerations: This media type provides an
alternative syntax to vCard data [I-D.ietf-vcarddav-vcardrev]
based on XML.
Perreault Expires October 11, 2011 [Page 10]
Internet-Draft vCard XML April 2011
Published specification: This specification.
Applications which use this media type: Applications that currently
make use of the text/vcard media type can use this as an
alternative. In general, applications that maintain or process
contact information can use this media type.
Additional information:
Magic number(s): none
File extension(s): XML data should use ".xml" as the file
extension.
Macintosh file type code(s): none
Person & email address to contact for further information: Simon
Perreault
Intended usage: COMMON
Restrictions on usage: none
Author: Simon Perreault
Change controller: IETF
9. Acknowledgements
Thanks to the following people for their input:
Alexey Melnikov, Barry Leiba, Bjorn Hoehrmann, Cyrus Daboo, Joe
Hildebrand, Joseph Smarr, Marc Blanchet, Mike Douglas, Peter Saint-
Andre, Robins George, Zahhar Kirillov, Zoltan Ordogh.
10. References
10.1. Normative References
[I-D.ietf-vcarddav-vcardrev] Perreault, S., "vCard Format
Specification",
draft-ietf-vcarddav-vcardrev-19 (work
in progress), April 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs
to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997.
Perreault Expires October 11, 2011 [Page 11]
Internet-Draft vCard XML April 2011
[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.,
Sperberg-McQueen, C., and T. Bray,
"Extensible Markup Language (XML) 1.0
(Fifth Edition)", World Wide Web
Consortium Recommendation REC-xml-
20081126, November 2008, .
[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, .
[relaxng] Clark, J., "RELAX NG Specification",
December 2001.
[relaxng-compact] Clark, J., "RELAX NG Compact Syntax",
November 2002, .
10.2. Informative References
[I-D.dawson-vcard-xml-dtd] Dawson, F., "The vCard v3.0 XML DTD",
draft-dawson-vcard-xml-dtd-03 (work in
progress), June 1998.
[RFC4288] Freed, N. and J. Klensin, "Media Type
Specifications and Registration
Procedures", BCP 13, RFC 4288,
December 2005.
Appendix A. Relax NG Schema
default namespace = "urn:ietf:params:xml:ns:vcard-4.0"
# Value types
value-text = element text { text }
value-text-list = value-text+
value-uri = element uri { xsd:anyURI }
value-date = element date {
xsd:string { pattern = "\d{8}|\d{4}-\d\d|--\d\d(\d\d)?|---\d\d" }
Perreault Expires October 11, 2011 [Page 12]
Internet-Draft vCard XML April 2011
}
value-time = element time {
xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)"
~ "(Z|[+\-]\d\d(\d\d)?)?" }
}
value-date-time = element date-time {
xsd:string { pattern = "(\d{8}|--\d{4}|---\d\d)T\d\d(\d\d(\d\d)?)?"
~ "(Z|[+\-]\d\d(\d\d)?)?" }
}
value-date-and-or-time = value-date | value-date-time | value-time
value-timestamp = element timestamp {
xsd:string { pattern = "\d{8}T\d{6}(Z|[+\-]\d\d(\d\d)?)?" }
}
value-boolean = element boolean { xsd:boolean }
value-integer = element integer { xsd:integer }
value-float = element float { xsd:float }
value-language-tag = element language-tag {
xsd:string { pattern = "([a-z]{2,3}((-[a-z]{3}){0,3})?|[a-z]{4,8})"
~ "(-[a-z]{4})?(-([a-z]{2}|\d{3}))?"
~ "(-([0-9a-z]{5,8}|\d[0-9a-z]{3}))*"
~ "(-[0-9a-wyz](-[0-9a-z]{2,8})+)*"
~ "(-x(-[0-9a-z]{1,8})+)?|x(-[0-9a-z]{1,8})+|"
~ "[a-z]{1,3}(-[0-9a-z]{2,8}){1,2}" }
}
# Parameters
param-language = element language { value-language-tag }?
param-pref = element pref {
element integer {
xsd:integer { minInclusive = "1" maxInclusive = "100" }
}
}?
param-altid = element altid { value-text }?
param-pid = element pid {
element text { xsd:string { pattern = "\d+(\.\d+)?" } }+
}?
param-type = element type { element text { "work" | "home" }+ }?
param-mediatype = element mediatype { value-text }?
param-calscale = element calscale { element text { "gregorian" } }?
param-sort-as = element sort-as { value-text+ }?
param-geo = element geo { value-uri }?
param-tz = element tz { value-text | value-uri }?
param-label = element label { value-text }?
# Properties
property-source = element source {
element parameters { param-altid, param-pid, param-pref,
param-mediatype },
Perreault Expires October 11, 2011 [Page 13]
Internet-Draft vCard XML April 2011
value-uri
}
property-kind = element kind {
element text { "individual" | "group" | "org" | "location" }*
}
property-fn = element fn {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type }?,
value-text
}
property-n = element n {
element parameters { param-language, param-sort-as, param-altid }?,
element surname { value-text-list? },
element given { value-text-list? },
element additional { value-text-list? },
element prefix { value-text-list? },
element suffix { value-text-list? }
}
property-nickname = element nickname {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type }?,
value-text-list
}
property-photo = element photo {
element parameters { param-altid, param-pid, param-pref, param-type,
param-mediatype }?,
value-uri
}
property-bday = element bday {
element parameters { param-altid, param-calscale }?,
(value-date-and-or-time | value-text)
}
property-anniversary = element anniversary {
element parameters { param-altid, param-calscale }?,
(value-date-and-or-time | value-text)
}
property-gender = element gender {
element sex {
element text { "M" | "F" | "O" | "N" | "U" }?
},
element identity { value-text-list? }
}
property-adr = element adr {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type, param-geo, param-tz,
param-label }?,
element pobox { value-text-list? },
element ext { value-text-list? },
Perreault Expires October 11, 2011 [Page 14]
Internet-Draft vCard XML April 2011
element street { value-text-list? },
element locality { value-text-list? },
element region { value-text-list? },
element code { value-text-list? },
element country { value-text-list? }
}
property-tel = element tel {
element parameters {
param-altid,
param-pid,
param-pref,
element type {
element text { "work" | "home" | "text" | "voice"
| "fax" | "cell" | "video" | "pager"
| "textphone" }+
}?,
param-mediatype
}?,
(value-text | value-uri)
}
property-email = element email {
element parameters { param-altid, param-pid, param-pref,
param-type }?,
value-text
}
property-impp = element impp {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
value-uri
}
property-lang = element lang {
element parameters { param-altid, param-pid, param-pref,
param-type }?,
value-language-tag
}
property-tz = element tz {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
(value-text | value-uri)
}
property-geo = element geo {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
value-uri
}
property-title = element title {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type }?,
Perreault Expires October 11, 2011 [Page 15]
Internet-Draft vCard XML April 2011
value-text
}
property-role = element role {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type }?,
value-text
}
property-logo = element logo {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type, param-mediatype }?,
value-uri
}
property-org = element org {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type, param-sort-as }?,
value-text-list
}
property-member = element member {
element parameters { param-altid, param-pid, param-pref,
param-mediatype }?,
value-uri
}
property-related = element related {
element parameters {
param-altid,
param-pid,
param-pref,
element type {
element text {
"work" | "home" | "contact" | "acquaintance" |
"friend" | "met" | "co-worker" | "colleague" | "co-resident" |
"neighbor" | "child" | "parent" | "sibling" | "spouse" |
"kin" | "muse" | "crush" | "date" | "sweetheart" | "me"
}+
}?,
param-mediatype
}?,
(value-uri | value-text)
}
property-categories = element categories {
element parameters { param-altid, param-pid, param-pref,
param-type }?,
value-text-list
}
property-note = element note {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type }?,
value-text
Perreault Expires October 11, 2011 [Page 16]
Internet-Draft vCard XML April 2011
}
property-prodid = element prodid { value-text }
property-rev = element rev { value-timestamp }
property-sound = element sound {
element parameters { param-language, param-altid, param-pid,
param-pref, param-type, param-mediatype }?,
value-uri
}
property-uid = element uid { value-uri }
property-clientpidmap = element clientpidmap {
element sourceid { xsd:positiveInteger },
value-uri
}
property-url = element url {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
value-uri
}
property-key = element key {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
(value-uri | value-text)
}
property-fburl = element fburl {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
value-uri
}
property-caladruri = element caladruri {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
value-uri
}
property-caluri = element caluri {
element parameters { param-altid, param-pid, param-pref,
param-type, param-mediatype }?,
value-uri
}
# Top-level grammar
property = property-adr | property-anniversary | property-bday
| property-caladruri | property-caluri | property-categories
| property-clientpidmap | property-email | property-fburl
| property-fn | property-geo | property-impp | property-key
| property-kind | property-lang | property-logo
| property-member | property-n | property-nickname
| property-note | property-org | property-photo
| property-prodid | property-related | property-rev
Perreault Expires October 11, 2011 [Page 17]
Internet-Draft vCard XML April 2011
| property-role | property-gender | property-sound
| property-source | property-tel | property-title
| property-tz | property-uid | property-url
start = element vcards {
element vcard {
(property
| element group {
attribute name { text },
property*
})+
}+
}
Appendix B. Change Log (to be removed by RFC Editor prior to
publication)
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 Added some references.
o Fixed bad XML in example.
o Added element around pid param value.
B.3. Changes in -07
o Synchronized with draft-ietf-vcarddav-vcardrev-16.
o Fixed bad XML in example.
o Fixed which now takes a value-text-list.
o All parameters now use value elements. This affects type,
calscale, and pref.
Perreault Expires October 11, 2011 [Page 18]
Internet-Draft vCard XML April 2011
B.4. Changes in -06
o Synchronized with draft-ietf-vcarddav-vcardrev-15.
B.5. Changes in -05
o Synchronized with draft-ietf-vcarddav-vcardrev-13.
B.6. Changes in -04
o Synchronized with draft-ietf-vcarddav-vcardrev-12.
o Added application/vcard+xml media type.
o Added rules for backslash escaping and quoting when converting.
o Added description of element.
o Described group construct in XML.
B.7. Changes in -03
o Created "Format Conversions" section.
o Turned more parameter values into plain text.
o Removed need for empty value elements in components.
o Wrapped value of , , and in value elements.
B.8. Changes in -02
o Synchronized with draft-ietf-vcarddav-vcardrev-10.
o Turned parameter values into plain text.
o Moved the "XML" property to vCard base.
o Changed title to avoid confusion with XML Schema.
o Added prefixes "value-", "param-", and "property-" in schema.
o Better language for specifying what a parser must ignore.
Perreault Expires October 11, 2011 [Page 19]
Internet-Draft vCard XML April 2011
B.9. Changes in -01
o Synchronized with draft-ietf-vcarddav-vcardrev-09.
o Added the element to allow multiple vCards in a single
XML file.
o Created the container element.
o Use text value for enumeration in element.
o Created the "XML" vCard property.
o Added IANA considerations section.
o Added security considerations section.
B.10. Changes in -00
o Same as draft-perreault-vcarddav-vcardxml-02.
Author's Address
Simon Perreault
Viagenie
2600 boul. Laurier, suite 625
Quebec, QC G1V 4W1
Canada
Phone: +1 418 656 9254
EMail: simon.perreault@viagenie.ca
URI: http://www.viagenie.ca
Perreault Expires October 11, 2011 [Page 20]