draft-ietf-vcarddav-vcardxml-00.txt   draft-ietf-vcarddav-vcardxml-01.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 October 14, 2009 Intended status: Standards Track October 21, 2009
(if approved) Expires: April 24, 2010
Updates: 2739 (if approved)
Intended status: Standards Track
Expires: April 17, 2010
vCard XML Schema vCard XML Schema
draft-ietf-vcarddav-vcardxml-00 draft-ietf-vcarddav-vcardxml-01
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.
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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 32
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 April 17, 2010. This Internet-Draft will expire on April 24, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 14 skipping to change at page 2, line 10
Abstract Abstract
This document defines the XML schema of the vCard data format. This document defines the XML schema of the vCard data format.
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 . . . . . . . . . . . . . . . . . . . . 4 4. Design Considerations . . . . . . . . . . . . . . . . . . . . 5
4.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 5
4.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Limitations . . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. The "XML" vCard Property . . . . . . . . . . . . . . . . . . . 6
6. Normative References . . . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. Registration of the "XML" vCard Property . . . . . . . . . 8
7.2. Registration of the XML Namespace . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Relax NG Schema . . . . . . . . . . . . . . . . . . . 8
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) . . . . . . . . . . . . . . . . . . . . 10 publication) . . . . . . . . . . . . . . . . . . . . 14
B.1. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 10 B.1. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 14
B.2. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 15
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
reused instead of writing a stand-alone vCard parser. 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. The Schema 2. 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 3. Example: Author's XML vCard
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<fn><text>Simon Perreault</text></fn> <vcard>
<n> <fn><text>Simon Perreault</text></fn>
<surname><text>Perreault</text></surname> <n>
<given><text>Simon</text></given> <surname><text>Perreault</text></surname>
<prefix><text/></prefix> <given><text>Simon</text></given>
<suffix> <prefix><text/></prefix>
<text>ing. jr.</text> <suffix>
<text>M.Sc.</text> <text>ing. jr.</text>
</suffix> <text>M.Sc.</text>
</n> </suffix>
<bday><date>--0203</date></bday> </n>
<anniversary> <bday><date>--0203</date></bday>
<date-time>20090808T1430-0500</date-time> <anniversary>
</anniversary> <date-time>20090808T1430-0500</date-time>
<sex>1</sex> </anniversary>
<lang><pref>1</pref><language-tag>fr</language-tag></lang> <sex>1</sex>
<lang><pref>2</pref><language-tag>en</language-tag></lang> <lang>
<group name="work"> <parameters><pref>1</pref></parameters>
<org><text>Viagenie</text></org> <language-tag>fr</language-tag>
</lang>
<lang>
<parameters><pref>2</pref></parameters>
<language-tag>en</language-tag>
</lang>
<org>
<parameters><type><work/></type></parameters>
<text>Viagenie</text>
</org>
<adr> <adr>
<parameters><type><work/></type></parameters>
<pobox><text/></pobox> <pobox><text/></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>
<type><voice/></type> <parameters><type><work/><voice/></type></parameters>
<uri>tel:+1-418-656-9254;ext=102</uri> <uri>tel:+1-418-656-9254;ext=102</uri>
</tel> </tel>
<tel> <tel>
<type><text/><voice/><cell/><video/></type> <parameters>
<type><work/><text/><voice/><cell/><video/></type>
</parameters>
<uri>tel:+1-418-262-6501</uri> <uri>tel:+1-418-262-6501</uri>
</tel> </tel>
<tel> <tel>
<type><fax/></type> <parameters><type><work/><fax/></type></parameters>
<uri>tel:+1-418-656-9257</uri> <uri>tel:+1-418-656-9257</uri>
</tel> </tel>
<email><text>simon.perreault@viagenie.ca</text></email> <email>
<geo><uri>geo:46.772673,-71.282945</uri></geo> <parameters><type><work/></type></parameters>
<text>simon.perreault@viagenie.ca</text>
</email>
<geo>
<parameters><type><work/></type></parameters>
<uri>geo:46.772673,-71.282945</uri>
</geo>
<key> <key>
<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>
</group> <tz><text>America/Montreal</text></tz>
<tz><text>America/Montreal</text></tz> <class>PUBLIC</class>
<class><PUBLIC/></class> </vcard>
</vcard> </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.
vCard parameters are also mapped to XML elements. They are contained vCard parameters are also mapped to XML elements. They are contained
in property elements. For example, the "TYPE" parameter applied to in the <parameters> element, which is contained in property elements.
the "TEL" property would look like the following in XML: For example, the "TYPE" parameter applied to the "TEL" property would
look like the following in XML:
<tel> <tel>
<type><voice/></type> <parameters><type><voice/></type></parameters>
<uri>tel:+1-555-555-555</uri> <uri>tel:+1-555-555-555</uri>
</tel> </tel>
Properties having structured values (e.g. the N property) are Properties having structured values (e.g. the "N" property) are
expressed by XML element trees. Element names in that tree (e.g. expressed by XML element trees. Element names in that tree (e.g.
"surname", "given", etc.) do not have a vCard equivalent since they "surname", "given", etc.) do not have a vCard equivalent since they
are identified by position in plain vCard. are identified by position in plain vCard.
Line folding is a non-issue in XML. Therefore, the mapping from Line folding is a non-issue in XML. Therefore, the mapping from
vCard to XML is done after the unfolding procedure is carried out. vCard to XML is done after the unfolding procedure is carried out.
Conversely, the mapping from XML to vCard is done before the folding Conversely, the mapping from XML to vCard is done before the folding
procedure is carried out. procedure is carried out.
4.1. Extensibility 4.1. Extensibility
skipping to change at page 5, line 21 skipping to change at page 5, line 48
document. This is not a requirement: a separate document may be used document. This is not a requirement: a separate document may be used
instead. instead.
Unregistered extensions (i.e. those starting with "X-" and Unregistered extensions (i.e. those starting with "X-" and
"VND-...-") can be expressed in XML by making use of XML namespaces. "VND-...-") can be expressed in XML by making use of XML namespaces.
They simply correspond to elements outside of the core namespace. They simply correspond to elements outside of the core namespace.
For example: For example:
<ext:my-prop <ext:my-prop
ext:xmlns="http://example.com/extensions/my-vcard"> ext:xmlns="http://example.com/extensions/my-vcard">
<pref>1</pref> <!-- Core vCard elements --> <parameters>
<pref>1</pref>
</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>
Note that extension elements do not need the "X- or "VND-" prefix in Note that extension elements do not need the "X- or "VND-" prefix in
XML. The XML namespace mechanism is sufficient. XML. The XML namespace mechanism is sufficient.
A vCard XML parser MUST ignore elements that are not part of this A vCard XML parser MUST ignore XML data qualified by a namespace it
specification. does not understand.
In the original vCard format, the VERSION property was mandatory and In the original vCard format, the "VERSION" property was mandatory
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.
Since vCard also has provisions for extending value enumerations, Parameters containing a list of values are expressed using a list of
such as the allowed TYPE parameter values, these values are expressed elements in XML (e.g. the <type> element).
using tags in XML.
4.2. Limitations 4.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
origiginal 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. The "XML" vCard Property
TBD This document defines the following vCard property.
6. Normative References Namespace:
Property name: XML
Purpose: To include XML-encoded vCard data in a plain vCard.
Value type: A single text value.
Cardinality: (0,n)
Property parameters: none allowed
Description: The content of this property is an XML chunk. Its
default XML namespace is "urn:ietf:params:xml:ns:vcard-4.0". The
elements allowed at the root level of this chunk are those that
are allowed to be immediate children of the <vcard> element
defined in this document. The normal rules for extensibility
apply (i.e. things in unknown namespaces are ignored). The chunk
is subject to normal line folding and escaping, i.e. replace all
backslashes with "\\", then replace all newlines with "\n", then
fold long lines.
Format definition:
XML-param = ""
XML-value = text
Example: The three following vCards are equivalent.
<?xml version="1.0"?>
<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcard>
<fn><text>John Doe</text></fn>
<email><text>jdoe@example.com</text></email>
</vcard>
</vcards>
BEGIN:VCARD
VERSION:4.0
XML:<fn><text>John Doe>/text></fn>\n
<email><text>jdoe@example.com</text></email>
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:John Doe
EMAIL:jdoe@example.com
END:VCARD
6. Security Considerations
All the security considerations applicable to plain vCard
[I-D.ietf-vcarddav-vcardrev] are applicable to this document as well.
7. IANA Considerations
7.1. Registration of the "XML" vCard Property
The completed registration template can be found in section
Section 5.
7.2. Registration of the XML Namespace
URI: urn:ietf:params:xml:ns:vcard-4.0
Registrant Contact: Simon Perreault <simon.perreault@viagenie.ca>
XML: None. Namespace URIs do not represent an XML specification.
8. Acknowledgements
Thanks to the following people for their input:
Alexey Melnikov, Barry Leiba, Cyrus Daboo, Joe Hildebrand, Joseph
Smarr, Marc Blanchet, Peter Saint-Andre, Robins George, Zahhar
Kirillov, Zoltan Ordogh.
9. 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-08 (work draft-ietf-vcarddav-vcardrev-09 (work
in progress), July 2009. in progress), October 2009.
[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. November 2002.
9.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.
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
\text = element text { text } \text = element text { text }
text-list = \text+ text-list = \text+
uri = element uri { xsd:anyURI } uri = element uri { xsd:anyURI }
date = date = element 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" } }
} time = element time {
time = xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)"
element time { ~ "(Z|[+\-]\d\d(\d\d)?)?" }
xsd:string { pattern = }
"(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)" date-time = element date-time {
~ "(Z|[+\-]\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)?)?" }
date-time = }
element date-time { date-and-or-time = date | date-time | time
xsd:string { pattern = timestamp = element timestamp {
"(\d{8}|--\d{4}|---\d\d)T\d\d(\d\d(\d\d)?)?" xsd:string { pattern = "\d{8}T\d{6}(Z|[+\-]\d\d(\d\d)?)?" }
~ "(Z|[+\-]\d\d(\d\d)?)?" } }
} boolean = element boolean { xsd:boolean }
date-and-or-time = date | date-time | time integer = element integer { xsd:integer }
timestamp = float = element float { xsd:float }
element timestamp { binary = element binary { xsd:base64Binary }
xsd:string { pattern = "\d{8}T\d{6}(Z|[+\-]\d\d(\d\d)?)?" } 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}" }
}
boolean = element boolean { xsd:boolean } # Parameters
integer = element integer { xsd:integer } language = element language { language-tag }?
float = element float { xsd:float } pref = element pref {
binary = element binary { xsd:base64Binary } xsd:integer { minInclusive = "1" maxInclusive = "100" }
language-tag = }?
element language-tag { pid = element pid {
xsd:string { pattern = xsd:string { pattern = "\d+(\.\d+)?" }
"([a-z]{2,3}((-[a-z]{3}){0,3})?|[a-z]{4,8})" }?
~ "(-[a-z]{4})?(-([a-z]{2}|\d{3}))?" type = element type {
~ "(-([0-9a-z]{5,8}|\d[0-9a-z]{3}))*" element work { empty }?,
~ "(-[0-9a-wyz](-[0-9a-z]{2,8})+)*(-x(-[0-9a-z]{1,8})+)?|" element home { empty }?
~ "x(-[0-9a-z]{1,8})+|[a-z]{1,3}(-[0-9a-z]{2,8}){1,2}" } }?
}
data =
(element type {
xsd:string { pattern = "[A-Za-z\d!#$&.+\-^_]{1,127}/"
~ "[A-Za-z\d!#$&.+\-^_]{1,127}" }
},
binary)
| uri
# Parameters # Properties
language = element language { language-tag }? source = element source {
pref = element parameters { pid, pref },
element pref { uri
xsd:integer { minInclusive = "1" maxInclusive = "100" } }
}?
pid =
element pid {
xsd:string { pattern = "\d+(\.\d+)?" }
}?
# Properties name = element name { \text }
source = element source { pid, pref, uri } kind = element kind {
name = element name { \text } element individual { empty }
kind = | element group { empty }
element kind { | element org { empty }
element individual { empty } | element location { empty }
| element group { empty } }
| element org { empty } fn = element fn {
| element location { empty } element parameters { language, pid, pref, type }?,
} \text
fn = element fn { language, pid, pref, \text } }
n = n = element n {
element n { element parameters { language }?,
language, element surname { text-list },
element surname { text-list }, element given { text-list },
element given { text-list }, element prefix { text-list },
element prefix { text-list }, element suffix { text-list }
element suffix { text-list } }
} nickname = element nickname {
nickname = element nickname { language, pid, pref, text-list } element parameters { language, pid, pref, type }?,
photo = element photo { pid, pref, data } text-list
bday = element bday { date-and-or-time | \text } }
dday = element dday { date-and-or-time | \text } photo = element photo {
birth = element birth { language, \text } element parameters {
death = element death { language, \text } pid,
anniversary = element anniversary { date-and-or-time | \text } pref,
sex = element sex { "0" | "1" | "2" | "9" } element type {
adr = element work { empty }?,
element adr { element home { empty }?,
element media { \text }?
}
}?,
(binary | uri)
}
bday = element bday { date-and-or-time | \text }
dday = element dday { date-and-or-time | \text }
birth = element birth {
element parameters { language }?,
\text
}
death = element death {
element parameters { language }?,
\text
}
anniversary = element anniversary { date-and-or-time | \text }
sex = element sex { "0" | "1" | "2" | "9" }
adr = element adr {
element parameters {
language, language,
pid,
pref,
type,
element geo { uri }?, element geo { uri }?,
element tz { \text | uri }?, element tz { \text | uri }?
}?,
element pobox { text-list },
element ext { text-list },
element street { text-list },
element locality { text-list },
element region { text-list },
element code { text-list },
element country { text-list }
}
label = element label {
element parameters { language, pid, pref, type }?,
\text
}
tel = element tel {
element parameters {
pid, pid,
pref, pref,
element pobox { text-list },
element ext { text-list },
element street { text-list },
element locality { text-list },
element region { text-list },
element code { text-list },
element country { text-list }
}
label = element label { language, pid, pref, \text }
tel =
element tel {
element type { element type {
element work { empty }?,
element home { empty }?,
element text { empty }?, element text { empty }?,
element voice { empty }?, element voice { empty }?,
element fax { empty }?, element fax { empty }?,
element cell { empty }?, element cell { empty }?,
element video { empty }?, element video { empty }?,
element pager { empty }? element pager { empty }?
}?, }?
},
uri
}
email = element email {
element parameters { pid, pref, type }?,
\text
}
impp = element impp {
element parameters { pid, pref, type }?,
uri
}
lang = element lang {
element parameters { pid, pref, type }?,
language-tag
}
tz = element tz {
element parameters { pid, pref, type }?,
(\text | uri)
}
geo = element geo {
element parameters { pid, pref, type }?,
uri
}
title = element title {
element parameters { language, pid, pref, type }?,
\text
}
role = element role {
element parameters { language, pid, pref, type }?,
\text
}
logo = element logo {
element parameters {
language,
pid, pid,
pref, pref,
uri
}
email = element email { pid, pref, \text }
impp = element impp { pid, pref, uri }
lang = element lang { pid, pref, language-tag }
tz = element tz { pid, pref, (\text | uri) }
geo = element geo { pid, pref, uri }
title = element title { language, pid, pref, \text }
role = element role { language, pid, pref, \text }
logo = element logo { language, pid, pref, data }
org = element org { language, pid, pref, text-list }
member = element member { pid, pref, uri }
related =
element related {
element type { element type {
element parent { empty } element work { empty }?,
| element child { empty } element home { empty }?,
| element sibling { empty } element media { \text }?
| element spouse { empty } }
| element family { empty } }?,
| element friend { empty } (binary | uri)
| element supervisor { empty } }
| element supervisee { empty } org = element org {
| element assistant { empty } element parameters { language, pid, pref, type }?,
| element colleague { empty } text-list
| element agent { empty } }
| element emergency { empty } member = element member { pid, pref, uri }
}?, related = element related {
element parameters {
pid, pid,
pref, pref,
(uri | \text) element type {
} element work { empty }?,
categories = element categories { pid, pref, \text } element home { empty }?,
note = element note { language, pid, pref, \text } ( element parent { empty }
prodid = element prodid { \text } | element child { empty }
rev = element rev { timestamp } | element sibling { empty }
sort-string = element sort-string { \text } | element spouse { empty }
sound = element sound { language, pid, pref, data } | element family { empty }
uid = element uid { uri } | element friend { empty }
clientpidmap = | element supervisor { empty }
element clientpidmap { | element supervisee { empty }
element sourceid { xsd:positiveInteger }, | element assistant { empty }
uri | element colleague { empty }
} | element agent { empty }
url = element url { pid, pref, uri } | element emergency { empty })
class = }?
element class { }?,
element PUBLIC { empty } (uri | \text)
| element PRIVATE { empty } }
| element CONFIDENTIAL { empty } categories = element categories {
} element parameters { pid, pref, type }?,
key = element key { pid, pref, data } \text
fburl = element fburl { pid, pref, uri } }
caladruri = element caladruri { pid, pref, uri } note = element note {
caluri = element caluri { pid, pref, uri } element parameters { language, pid, pref, type }?,
\text
}
prodid = element prodid { \text }
rev = element rev { timestamp }
sort-string = element sort-string { \text }
sound = element sound {
element parameters {
language,
pid,
pref,
element type {
element work { empty }?,
element home { empty }?,
element media { \text }?
}
}?,
(binary | uri)
}
uid = element uid { uri }
clientpidmap = element clientpidmap {
element sourceid { xsd:positiveInteger },
uri
}
url = element url {
element parameters { pid, pref, type }?,
uri
}
class = element class { "PUBLIC" | "PRIVATE" | "CONFIDENTIAL" }
key = element key {
element parameters {
pid,
pref,
element type {
element work { empty }?,
element home { empty }?,
element media { \text }?
}
}?,
(binary | uri)
}
fburl = element fburl {
element parameters { pid, pref, type }?,
uri
}
caladruri = element caladruri {
element parameters { pid, pref, type }?,
uri
}
caluri = element caluri {
element parameters { pid, pref, type }?,
uri
}
# Top-level grammar # Top-level grammar
group-property = fn | nickname | photo | adr | label | tel | email | property = adr | anniversary | bday | birth | caladruri | caluri
impp | lang | tz | geo | title | role | logo | org | related | | categories | class | clientpidmap | dday | death | email
categories | note | sound | url | key | fburl | caladruri | caluri | fburl | fn | geo | impp | key | kind | label | lang | logo
any-property = group-property | source | name | kind | n | bday | | member | n | name | nickname | note | org | photo | prodid
dday | birth | death | anniversary | sex | member | prodid | | related | rev | role | sex | sort-string | sound | source
rev | sort-string | uid | clientpidmap | class | tel | title | tz | uid | url
start = start = element vcards {
element vcard { element vcard {
(any-property (property
| element group { | element group {
attribute name { text }, attribute name { text },
group-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 -00 B.1. Changes in -01
o Synchronized with draft-ietf-vcarddav-vcardrev-09.
o Added the <vcards> element to allow multiple vCards in a single
XML file.
o Created the <parameters> container element.
o Use text value for enumeration in <class> element.
o Created the "XML" vCard property.
o Added IANA considerations section.
o Added security considerations section.
B.2. 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. 45 change blocks. 
224 lines changed or deleted 450 lines changed or added

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