draft-ietf-calsch-many-xcal-00.txt   draft-ietf-calsch-many-xcal-01.txt 
Network Working Group F Dawson Network Working Group F Dawson
Internet-Draft Lotus Internet-Draft Nokia Corporation
Expires: February 18, 2002 S Reddy Expires: August 16, 2002 S Reddy
Oracle Oracle
D Royer D Royer
Sun Microsystems INET-Consulting LLC
E Plamondon E Plamondon
Steltor Steltor
August 20, 2001 February 15, 2002
iCalendar DTD Document (xCal) iCalendar DTD Document (xCal)
draft-ietf-calsch-many-xcal-00 draft-ietf-calsch-many-xcal-01
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any 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."
To view the entire list of Internet-Draft Shadow Directories, see To view the entire list of Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 18, 2002. This Internet-Draft will expire on August 16, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This memo defines a [XML] Document Type Definition (DTD) that This memo defines a [XML] Document Type Definition (DTD) that
corresponds to the iCalendar, Internet Calendaring and Scheduling corresponds to the iCalendar, Internet Calendaring and Scheduling
Core Object Specification defined by [RFC 2445]. This DTD provides Core Object Specification defined by [RFC 2445]. This DTD provides
equivalent functionality to the standard format defined by [RFC equivalent functionality to the standard format defined by [RFC
2445]. Documents structured in accordance with this DTD may also be 2445]. Documents structured in accordance with this DTD may also be
known as "XML iCalendar" documents or "xCal". known as "XML iCalendar" documents or "xCal".
The mailing list for discussion of this memo is The mailing list for discussion of this memo is
"ietf-calendar@imc.org". Send an email to "ietf-calendar@imc.org". Send an email to
"ietf-calendar-request@imc.org" with the message "SUBSCRIBE" to add "ietf-calendar-request@imc.org" with the message "SUBSCRIBE" to add
your email address to this mailing list. Send an email to your email address to this mailing list. Send an email to
"ietf-vcard-xml-request@imc.org" with the message "UNSUBSCRIBE" to "ietf-calendar-request@imc.org" with the message "UNSUBSCRIBE" to
remove your email address from this mailing list. remove your email address from this mailing list.
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 [RFC 2119]. document are to be interpreted as described in [RFC 2119].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Using XML For Representating iCalendar . . . . . . . . . . . 6 2. Using XML For Representating iCalendar . . . . . . . . . . . 6
skipping to change at page 12, line 11 skipping to change at page 12, line 11
declare a namespace in XML. It can be used to declare the iCalendar declare a namespace in XML. It can be used to declare the iCalendar
XML namespace in a XML document with a document type other than the XML namespace in a XML document with a document type other than the
iCalendar XML document type. The iCalendar XML document type MUST iCalendar XML document type. The iCalendar XML document type MUST
only use element types from the iCalendar namespace. Non-standard, only use element types from the iCalendar namespace. Non-standard,
experimental element types and attributes lists MUST only be experimental element types and attributes lists MUST only be
specified by declarations in an internal DTD within the iCalendar specified by declarations in an internal DTD within the iCalendar
XML document. To specify the iCalendar namespace, the attribute XML document. To specify the iCalendar namespace, the attribute
value for the "xmlns" and any attribute with the prefix "xmlns:" value for the "xmlns" and any attribute with the prefix "xmlns:"
MUST be: MUST be:
'http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-00.txt' 'http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt'
NOTE: This attribute value will be replaced with the URL NOTE: This attribute value will be replaced with the URL
"http://www.ietf.org/rfc/rfcxxxx.txt", where "xxxx" is the RFC "http://www.ietf.org/rfc/rfcxxxx.txt", where "xxxx" is the RFC
number, when this memo is published as a RFC. number, when this memo is published as a RFC.
For example: For example:
<iCalendar xmlns:iCalv3='http://www.ietf.org/internet- <iCalendar xmlns:iCalv3='http://www.ietf.org/internet-
drafts/draft-ietf-calsch-many-xcal-00.txt'> drafts/draft-ietf-calsch-many-xcal-01.txt'>
<!-- the "iCalendar" prefix is bound to <!-- the "iCalendar" prefix is bound to
'http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-00.txt' 'http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt'
for the "iCalendar" element and contents--> for the "iCalendar" element and contents-->
</iCalendar> </iCalendar>
The following table specifies the attribute name corresponding to The following table specifies the attribute name corresponding to
each calendar property. These attributes are only permitted on the each calendar property. These attributes are only permitted on the
"vcalendar" element type. "vcalendar" element type.
+---------------+-----------+-----------+-----------------+ +---------------+-----------+-----------+-----------------+
| Calendar | Attribute | Attribute | Default | | Calendar | Attribute | Attribute | Default |
| Property Name | Name | Type | Value | | Property Name | Name | Type | Value |
skipping to change at page 17, line 32 skipping to change at page 17, line 32
documents that reference element types or attribute lists from the documents that reference element types or attribute lists from the
iCalendar namespace. iCalendar namespace.
The following is an example of a well-formed but invalid "xdoc" The following is an example of a well-formed but invalid "xdoc"
document type that includes elements and attribute lists from the document type that includes elements and attribute lists from the
iCalendar namespace: iCalendar namespace:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xdoc> <xdoc>
<xCal:xCal version="3.0" xmlns:xCal="http://www.ietf.org/internet <xCal:xCal version="3.0" xmlns:xCal="http://www.ietf.org/internet
-drafts/draft-ietf-calsch-many-xcal-000.txt"> -drafts/draft-ietf-calsch-many-xcal-01.txt">
<!-- Remainder of the XML document, each element from the --> <!-- Remainder of the XML document, each element from the -->
<!-- iCalendar namespace with the "xCal:" prefix. --> <!-- iCalendar namespace with the "xCal:" prefix. -->
</xCal:xCal> </xCal:xCal>
</xdoc> </xdoc>
2.12 Emailing the iCalendar XML Representation 2.12 Emailing the iCalendar XML Representation
It is expected that iCalendar XML documents will need to be sent It is expected that iCalendar XML documents will need to be sent
skipping to change at page 18, line 19 skipping to change at page 18, line 19
by the MUA. For example, not only would feedback be provided for a by the MUA. For example, not only would feedback be provided for a
calendaring and scheduling content. Some further unique calendaring and scheduling content. Some further unique
identification would also be provided for each different scheduling identification would also be provided for each different scheduling
message; such as a meeting invitation, response to an invitation, message; such as a meeting invitation, response to an invitation,
reschedule notice, cancellation notice, etc. In such cases, reschedule notice, cancellation notice, etc. In such cases,
acceptable performance by the MUA is dependent on the existence of acceptable performance by the MUA is dependent on the existence of
header field information, such as it provided in the definition of header field information, such as it provided in the definition of
the "text/calendar" content-type by [RFC 2445]. the "text/calendar" content-type by [RFC 2445].
Internet application conforming to this memo MUST identify iCalendar Internet application conforming to this memo MUST identify iCalendar
XML documents with the experimental content-type "text/x-xcal". The XML documents with the experimental content-type
content-type header field SHOULD also contain a "component" and "application/calendar+xml". The content-type header field SHOULD
"method" parameter to clearly identify a comma-separated list of also contain a "component" and "method" parameter to clearly
components and the singular method used in the iCalendar XML identify a comma-separated list of components and the singular
document. For example, an iCalendar XML document specifying a method used in the iCalendar XML document. For example, an iCalendar
REQUEST for a VEVENT and VTODO would be specified with the following XML document specifying a REQUEST for a VEVENT and VTODO would be
content-type header field: specified with the following content-type header field:
content-type:text/x-xcal;method=REQUEST;component=VEVENT,VTODO content-type:application/calendar+xml;method=REQUEST;component=VEVENT,VTODO
The content-type can also include the "optinfo" parameter to specify The content-type can also include the "optinfo" parameter to specify
any other optional iCalendar information. The semantics of these any other optional iCalendar information. The semantics of these
content-type parameters is as defined in [RFC 2445]. content-type parameters is as defined in [RFC 2445].
Internet applications conforming to this memo MUST only send the Internet applications conforming to this memo MUST only send the
iCalendar XML document in a "multipart/alternative" MIME entity that iCalendar XML document in a "multipart/alternative" MIME entity that
also contains an equivalent iCalendar object in the standard format also contains an equivalent iCalendar object in the standard format
defined by [RFC 2445]. This restrict will guarantee that the defined by [RFC 2445]. This restrict will guarantee that the
iCalendar object can also be processed by internet applications that iCalendar object can also be processed by internet applications that
only support the standard iCalendar format. only support the standard iCalendar format.
An XML application supporting the iCalendar XML document type MUST An XML application supporting the iCalendar XML document type MUST
be able to receive and properly process the "text/x-xcal" document be able to receive and properly process the
contained within a "multipart" message content-type. "application/calendar+xml" document contained within a "multipart"
message content-type.
2.13 iCalendar XML Representation and File Systems 2.13 iCalendar XML Representation and File Systems
The iCalendar XML documents will be stored in file systems. The The iCalendar XML documents will be stored in file systems. The
accepted practice for file extensions for XML documents is the text accepted practice for file extensions for XML documents is the text
"XML". However, in order to uniquely identify iCalendar XML "XML". However, in order to uniquely identify iCalendar XML
documents for file association with applications that can directly documents for file association with applications that can directly
process this document type, it is RECOMMENDED that the file process this document type, it is RECOMMENDED that the file
extension be the text "XCS". extension be the text "XCS".
skipping to change at page 19, line 18 skipping to change at page 19, line 18
documents. documents.
3.1 A well-formed and valid iCalendar XML document 3.1 A well-formed and valid iCalendar XML document
The following is a simple example of a iCalendar XML document. This The following is a simple example of a iCalendar XML document. This
document is both a well-formed and valid XML document. The iCalendar document is both a well-formed and valid XML document. The iCalendar
object specifies an appointment. object specifies an appointment.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN" <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
"http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-00.txt"> "http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt">
<iCalendar> <iCalendar>
<vcalendar method="PUBLISH" <vcalendar method="PUBLISH"
version="2.0" version="2.0"
prodid="-//HandGen//NONSGML vGen v1.0//EN"> prodid="-//HandGen//NONSGML vGen v1.0//EN">
<vevent> <vevent>
<uid>19981116T150000@cal10.host.com</uid> <uid>19981116T150000@cal10.host.com</uid>
<dtstamp>19981116T145958Z</dtstamp> <dtstamp>19981116T145958Z</dtstamp>
<summary>Project XYZ Review</summary> <summary>Project XYZ Review</summary>
<location>Conference Room 23A</location> <location>Conference Room 23A</location>
skipping to change at page 20, line 7 skipping to change at page 20, line 7
The non-standard experimental property is identified by the "X-" The non-standard experimental property is identified by the "X-"
prefix to the element name. All non-standard properties MUST be prefix to the element name. All non-standard properties MUST be
specified with element types with an "X-" type element name. In specified with element types with an "X-" type element name. In
addition, a text identifier for the vendor specifying the extension addition, a text identifier for the vendor specifying the extension
SHOULD be appended to the "X-" text prefix. In this case, the SHOULD be appended to the "X-" text prefix. In this case, the
example specifies a "foo" for the name of the vendor specifying the example specifies a "foo" for the name of the vendor specifying the
non- standard property. non- standard property.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN" <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
"http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-000.txt" "http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt"
[ [
<!ELEMENT vtodo ((class | completed | created | description | dtstamp <!ELEMENT vtodo ((class | completed | created | description | dtstamp
| dtstart | geo | last-modified | location | organizer | percent | priority | | dtstart | geo | last-modified | location | organizer | percent | priority |
recurrence-id | sequence | status | summary | uid | url | (due | duration))*, recurrence-id | sequence | status | summary | uid | url | (due | duration))*,
(attach | attendee | categories | comment | contact | exdate | exrule (attach | attendee | categories | comment | contact | exdate | exrule
| request-status | related-to | resources | rdate | rrule | x-foo-cust-code)*, | request-status | related-to | resources | rdate | rrule | x-foo-cust-code)*,
(valarm)*)> (valarm)*)>
<!ELEMENT x-foo-cust-code (#PCDATA)> <!ELEMENT x-foo-cust-code (#PCDATA)>
<!ATTLIST x-foo-cust-code value NOTATION (X-NAME) #IMPLIED> <!ATTLIST x-foo-cust-code value NOTATION (X-NAME) #IMPLIED>
skipping to change at page 21, line 7 skipping to change at page 21, line 7
</iCalendar> </iCalendar>
3.3 Including binary content in attachments 3.3 Including binary content in attachments
The following is an example of a valid iCalendar XML document that The following is an example of a valid iCalendar XML document that
also includes an external reference to an attachment. The iCalendar also includes an external reference to an attachment. The iCalendar
object specifies a meeting invitation with an attachment. object specifies a meeting invitation with an attachment.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN" <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
"http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-00.txt" "http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt"
[ [
<!ENTITY attach1 SYSTEM "http://host.com/pub/photos/holiday.jpg" <!ENTITY attach1 SYSTEM "http://host.com/pub/photos/holiday.jpg"
NDATA JPEG> NDATA JPEG>
<!NOTATION JPEG PUBLIC "ISO/IEC 10918:1993//NOTATION Digital <!NOTATION JPEG PUBLIC "ISO/IEC 10918:1993//NOTATION Digital
Compression and Coding of Continuous-tone Still Images (JPEG)//EN" > Compression and Coding of Continuous-tone Still Images (JPEG)//EN" >
]> ]>
<iCalendar> <iCalendar>
<vcalendar method="REQUEST" <vcalendar method="REQUEST"
skipping to change at page 22, line 7 skipping to change at page 22, line 7
</vevent> </vevent>
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
The following is an example of a well-formed and valid iCalendar XML The following is an example of a well-formed and valid iCalendar XML
document that includes an attachment as inline binary content. The document that includes an attachment as inline binary content. The
iCalendar object specifies a meeting invitation with an attachment. iCalendar object specifies a meeting invitation with an attachment.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN" <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
"http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-00.txt"> "http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt">
<iCalendar> <iCalendar>
<vcalendar method="REQUEST" <vcalendar method="REQUEST"
version="2.0" version="2.0"
prodid="-//HandGen//NONSGML vGen v1.0//EN"> prodid="-//HandGen//NONSGML vGen v1.0//EN">
<vevent> <vevent>
<uid>19981211T133000@cal1.host.com</uid> <uid>19981211T133000@cal1.host.com</uid>
<dtstamp>19981211T132928Z</dtstamp> <dtstamp>19981211T132928Z</dtstamp>
<organizer>MAILTO:jim@host.com</organizer> <organizer>MAILTO:jim@host.com</organizer>
<dtstart>19981212T150000Z</dtstart> <dtstart>19981212T150000Z</dtstart>
skipping to change at page 23, line 7 skipping to change at page 23, line 7
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
3.4 iCalendar XML document with multiple iCalendar objects 3.4 iCalendar XML document with multiple iCalendar objects
The following is an example of a well-formed and valid iCalendar XML The following is an example of a well-formed and valid iCalendar XML
document that includes more than one iCalendar object. document that includes more than one iCalendar object.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN" <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
"http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-000.txt"> "http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt">
<iCalendar annotation="IT Conference Prep"> <iCalendar annotation="IT Conference Prep">
<vcalendar method="PUBLISH" <vcalendar method="PUBLISH"
version="2.0" version="2.0"
prodid="-//HandGen//NONSGML vGen v1.0//EN"> prodid="-//HandGen//NONSGML vGen v1.0//EN">
<vtodo> <vtodo>
<uid>19981009T233000@cal1.host.com</uid> <uid>19981009T233000@cal1.host.com</uid>
<dtstamp>19981009T232928Z</dtstamp> <dtstamp>19981009T232928Z</dtstamp>
<dtstart>19981010T000000Z</dtstart> <dtstart>19981010T000000Z</dtstart>
<due>19981010T235959Z</due> <due>19981010T235959Z</due>
skipping to change at page 23, line 42 skipping to change at page 23, line 42
</vevent> </vevent>
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
3.5 Using the iCalendar namespace 3.5 Using the iCalendar namespace
The following is an example of a snippet of a XML document that The following is an example of a snippet of a XML document that
includes elements from the iCalendar name-space. includes elements from the iCalendar name-space.
<x xmlns:xcal="http://www.ietf.org/internet-drafts/ <x xmlns:xcal="http://www.ietf.org/internet-drafts/
draft-ietf-calsch-many-xcal-00.txt" draft-ietf-calsch-many-xcal-01.txt"
xmlns:pdi="http://pdi.org/schema"> xmlns:pdi="http://pdi.org/schema">
<xcal:dtstart>19981123T133000Z</xcal:dtstart> <xcal:dtstart>19981123T133000Z</xcal:dtstart>
<xcal:dtend>19981123T203000Z</xcal:dtend> <xcal:dtend>19981123T203000Z</xcal:dtend>
<pdi:idnum>1234567</pdi:idnum> <pdi:idnum>1234567</pdi:idnum>
<pdi:usage>999.99</pdi:usage> <pdi:usage>999.99</pdi:usage>
</x> </x>
3.6 Publish meeting information 3.6 Publish meeting information
The following is a snippet of an iCalendar XML document that The following is a snippet of an iCalendar XML document that
skipping to change at page 28, line 6 skipping to change at page 28, line 6
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
3.11 Publish busy time 3.11 Publish busy time
The following is an iCalendar XML document that publishes busy time The following is an iCalendar XML document that publishes busy time
information. The default value for the "method" attribute is information. The default value for the "method" attribute is
"PUBLISH" and does not need to be specified in this example. "PUBLISH" and does not need to be specified in this example.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar SYSTEM "icalendar.dtd" [ <!DOCTYPE iCalendar SYSTEM "xcal.dtd" [
<!ENTITY jsmith.ifb SYSTEM <!ENTITY jsmith.ifb SYSTEM
"http://www.host.com/calendar/busytime/jsmith.ifb" NDATA BINARY> "http://www.host.com/calendar/busytime/jsmith.ifb" NDATA BINARY>
]> ]>
<iCalendar> <iCalendar>
<vcalendar version="2.0" <vcalendar version="2.0"
prodid="-//hacksw/handcal//NONSGML 1.0//EN"> prodid="-//hacksw/handcal//NONSGML 1.0//EN">
<vfreebusy> <vfreebusy>
<uid>19980313T133000@ical1.host.com</uid> <uid>19980313T133000@ical1.host.com</uid>
skipping to change at page 29, line 6 skipping to change at page 29, line 6
</vfreebusy> </vfreebusy>
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
3.13 Response to a busy time request 3.13 Response to a busy time request
The following is an iCalendar XML document that responds to request The following is an iCalendar XML document that responds to request
for busy time information. for busy time information.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar SYSTEM "icalendar.dtd" [ <!DOCTYPE iCalendar SYSTEM "xcal.dtd" [
<!ENTITY jpublic-01.ifb SYSTEM "http://host2.com/pub/busy/jpublic- <!ENTITY jpublic-01.ifb SYSTEM "http://host2.com/pub/busy/jpublic-
01.ifb" NDATA BINARY> 01.ifb" NDATA BINARY>
]> ]>
<iCalendar> <iCalendar>
<vcalendar method="REPLY" <vcalendar method="REPLY"
version="2.0" version="2.0"
prodid="-//hacksw/handcal//NONSGML 1.0//EN"> prodid="-//hacksw/handcal//NONSGML 1.0//EN">
<vfreebusy> <vfreebusy>
<uid>19970901T083000@ical1.host.com</uid> <uid>19970901T083000@ical1.host.com</uid>
skipping to change at page 30, line 33 skipping to change at page 30, line 33
3.15 An event with an alarm 3.15 An event with an alarm
The following is an iCalendar XML with associated alarms. The event The following is an iCalendar XML with associated alarms. The event
specifies alarm definitions for a "display", "audio", "email" and specifies alarm definitions for a "display", "audio", "email" and
"procedure" type of alarms. The "method" attribute isn't specified "procedure" type of alarms. The "method" attribute isn't specified
since it is the default value. since it is the default value.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN" <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
"http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-00.txt" "http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-01.txt"
[ [
<!ENTITY boom SYSTEM "ftp://host.com/sounds/cannon.wav" NDATA wave> <!ENTITY boom SYSTEM "ftp://host.com/sounds/cannon.wav" NDATA wave>
<!NOTATION wave SYSTEM "WAVE Audio Format"> <!NOTATION wave SYSTEM "WAVE Audio Format">
<!ENTITY doit SYSTEM "http://procs.host.com/litesout.exe" NDATA <!ENTITY doit SYSTEM "http://procs.host.com/litesout.exe" NDATA
binary> binary>
<!NOTATION binary SYSTEM "Foo Bar Executable Format"> <!NOTATION binary SYSTEM "Foo Bar Executable Format">
]> ]>
<iCalendar> <iCalendar>
<vcalendar version="2.0" <vcalendar version="2.0"
prodid="-//hacksw/handcal//NONSGML 1.0//EN"> prodid="-//hacksw/handcal//NONSGML 1.0//EN">
skipping to change at page 44, line 17 skipping to change at page 44, line 17
value NOTATION (TEXT) #IMPLIED> value NOTATION (TEXT) #IMPLIED>
<!-- iCalendar object element type declarations --> <!-- iCalendar object element type declarations -->
<!ELEMENT iCalendar (vcalendar+)> <!ELEMENT iCalendar (vcalendar+)>
<!ELEMENT vcalendar (%cal.comp;)*> <!ELEMENT vcalendar (%cal.comp;)*>
<!ATTLIST vcalendar <!ATTLIST vcalendar
%attr.language; %attr.language;
xmlns CDATA #FIXED 'http://www.ietf.org/internet-drafts/draft- xmlns CDATA #FIXED 'http://www.ietf.org/internet-drafts/draft-
ietf-calsch-many-xcal-00.txt' ietf-calsch-many-xcal-01.txt'
calscale CDATA "GREGORIAN" calscale CDATA "GREGORIAN"
method CDATA "PUBLISH" method CDATA "PUBLISH"
version CDATA #REQUIRED version CDATA #REQUIRED
prodid CDATA #IMPLIED> prodid CDATA #IMPLIED>
<!-- version - Must be "2.0" if document conforms to this spec. --> <!-- version - Must be "2.0" if document conforms to this spec. -->
<!-- calscale - Calendar scale. Default is GREGORIAN. --> <!-- calscale - Calendar scale. Default is GREGORIAN. -->
<!-- method - C&S method. Default is iTIP PUBLISH. --> <!-- method - C&S method. Default is iTIP PUBLISH. -->
<!-- prodid - ISO 9070 FPI for product that generated iCalendar. --> <!-- prodid - ISO 9070 FPI for product that generated iCalendar. -->
<!-- "vevent" element type declaration --> <!-- "vevent" element type declaration -->
skipping to change at page 48, line 38 skipping to change at page 48, line 38
[XML] "Extensible Markup Language (XML)", Worldwide Web Consortium, [XML] "Extensible Markup Language (XML)", Worldwide Web Consortium,
http://www.w3.org/TR/1998/REC-xml-19980210, February 1998. http://www.w3.org/TR/1998/REC-xml-19980210, February 1998.
[XML] "Extensible Markup Language (XML)", Worldwide Web Consortium, [XML] "Extensible Markup Language (XML)", Worldwide Web Consortium,
http://www.w3.org/TR/1998/REC-xml-19980210, February 1998. http://www.w3.org/TR/1998/REC-xml-19980210, February 1998.
Authors' Addresses Authors' Addresses
Frank Dawson Frank Dawson
Lotus Nokia Corporation
6544 Battleford Drive
Raleigh, NC 27613-3502 Phone: +1 (972) 894 4083
US EMail: frank.dawson@nokia.com
Phone: +1 (617) 693 8728
EMail: Frank_Dawson@Lotus.com
Surendra K. Reddy Surendra K. Reddy
Oracle Oracle
M/S 6op3 M/S 6op3
500 Oracle Parkway 500 Oracle Parkway
Redwoodshores, CA 94065 Redwoodshores, CA 94065
US US
Phone: +1 (650) 506 5441 Phone: +1 (650) 506 5441
Fax: +1 (650) 654 6205 Fax: +1 (650) 654 6205
EMail: skreddy@us.oracle.com EMail: skreddy@us.oracle.com
skipping to change at page 49, line 14 skipping to change at page 49, line 4
Surendra K. Reddy Surendra K. Reddy
Oracle Oracle
M/S 6op3 M/S 6op3
500 Oracle Parkway 500 Oracle Parkway
Redwoodshores, CA 94065 Redwoodshores, CA 94065
US US
Phone: +1 (650) 506 5441 Phone: +1 (650) 506 5441
Fax: +1 (650) 654 6205 Fax: +1 (650) 654 6205
EMail: skreddy@us.oracle.com EMail: skreddy@us.oracle.com
Doug Royer Doug Royer
Sun Microsystems INET-Consulting LLC
MS MPK17-105 1795 W. Broadway #266
901 San Antonio Road Idaho Falls, ID 83402
Palo Alto, CA 94303-4900
US US
Phone: +1 (650) 786 7599 Phone: +1 (208) 520 4044
EMail: doug.royer@sun.com Fax: +1 (208) 552 1179
EMail: doug@royer.com
Eric R. Plamondon Eric R. Plamondon
Steltor Steltor
2000 Peel Street, 4th Floor 2000 Peel Street, 4th Floor
Montreal, QC H3A 2W5 Montreal, QC H3A 2W5
Canada Canada
Phone: +1 (514) 733 8500 Phone: +1 (514) 733 8500
Fax: +1 (514) 733 8878 Fax: +1 (514) 733 8878
EMail: ericp@steltor.com EMail: ericp@steltor.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published or assist in its implmentation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works.However, this are included on all such copies and derivative works.However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 30 change blocks. 
46 lines changed or deleted 44 lines changed or added

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