draft-ietf-calsch-many-xcal-01.txt   draft-ietf-calsch-many-xcal-02.txt 
Network Working Group F Dawson Network Working Group F. Dawson
Internet-Draft Nokia Corporation Internet-Draft Nokia
Expires: August 16, 2002 S Reddy Expires: January 23, 2003 S. Reddy
Oracle Oracle
D Royer D. Royer
INET-Consulting LLC INET-Consulting
E Plamondon E. Plamondon
Steltor Oracle
February 15, 2002 July 25, 2002
iCalendar DTD Document (xCal) iCalendar DTD Document (xCal)
draft-ietf-calsch-many-xcal-01 draft-ietf-calsch-many-xcal-02
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-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
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."
To view the entire list of Internet-Draft Shadow Directories, see The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt.
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 August 16, 2002. This Internet-Draft will expire on January 23, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). 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-
"ietf-calendar@imc.org". Send an email to calendar@imc.org". Send an email to "ietf-calendar-request@imc.org"
"ietf-calendar-request@imc.org" with the message "SUBSCRIBE" to add with the message "SUBSCRIBE" to add your email address to this
your email address to this mailing list. Send an email to mailing list. Send an email to "ietf-calendar-request@imc.org" with
"ietf-calendar-request@imc.org" with the message "UNSUBSCRIBE" to the message "UNSUBSCRIBE" to remove your email address from this
remove your email address from this mailing list. 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
2.1 XML Dependencies . . . . . . . . . . . . . . . . . . . . . . 6 2.1 XML Dependencies . . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 2, line 31 skipping to change at page 2, line 35
2.4 Using Data Types . . . . . . . . . . . . . . . . . . . . . . 7 2.4 Using Data Types . . . . . . . . . . . . . . . . . . . . . . 7
2.5 Including Binary Content . . . . . . . . . . . . . . . . . . 8 2.5 Including Binary Content . . . . . . . . . . . . . . . . . . 8
2.6 Including Multiple iCalendar Objects . . . . . . . . . . . . 9 2.6 Including Multiple iCalendar Objects . . . . . . . . . . . . 9
2.7 Mapping Property Parameters to XML . . . . . . . . . . . . . 10 2.7 Mapping Property Parameters to XML . . . . . . . . . . . . . 10
2.8 Mapping Calendar Properties to XML . . . . . . . . . . . . . 11 2.8 Mapping Calendar Properties to XML . . . . . . . . . . . . . 11
2.9 Mapping Component Properties to XML . . . . . . . . . . . . 13 2.9 Mapping Component Properties to XML . . . . . . . . . . . . 13
2.10 Parameter Entities . . . . . . . . . . . . . . . . . . . . . 16 2.10 Parameter Entities . . . . . . . . . . . . . . . . . . . . . 16
2.11 Namespace . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.11 Namespace . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.12 Emailing the iCalendar XML Representation . . . . . . . . . 17 2.12 Emailing the iCalendar XML Representation . . . . . . . . . 17
2.13 iCalendar XML Representation and File Systems . . . . . . . 18 2.13 iCalendar XML Representation and File Systems . . . . . . . 18
3. Example Usage . . . . . . . . . . . . . . . . . . . . . . . 19 3. Example Usage . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 A well-formed and valid iCalendar XML document . . . . . . . 19 3.1 A well-formed and valid iCalendar XML document . . . . . . . 20
3.2 Adding non-standard, experimental extensions . . . . . . . . 19 3.2 Adding non-standard, experimental extensions . . . . . . . . 20
3.3 Including binary content in attachments . . . . . . . . . . 20 3.3 Including binary content in attachments . . . . . . . . . . 21
3.4 iCalendar XML document with multiple iCalendar objects . . . 22 3.4 iCalendar XML document with multiple iCalendar objects . . . 23
3.5 Using the iCalendar namespace . . . . . . . . . . . . . . . 23 3.5 Using the iCalendar namespace . . . . . . . . . . . . . . . 24
3.6 Publish meeting information . . . . . . . . . . . . . . . . 24 3.6 Publish meeting information . . . . . . . . . . . . . . . . 25
3.7 Publish transparent annual event . . . . . . . . . . . . . . 24 3.7 Publish transparent annual event . . . . . . . . . . . . . . 25
3.8 Meeting invitation . . . . . . . . . . . . . . . . . . . . . 25 3.8 Meeting invitation . . . . . . . . . . . . . . . . . . . . . 26
3.9 Assign a to-do . . . . . . . . . . . . . . . . . . . . . . . 26 3.9 Assign a to-do . . . . . . . . . . . . . . . . . . . . . . . 27
3.10 Publish a journal entry . . . . . . . . . . . . . . . . . . 27 3.10 Publish a journal entry . . . . . . . . . . . . . . . . . . 28
3.11 Publish busy time . . . . . . . . . . . . . . . . . . . . . 27 3.11 Publish busy time . . . . . . . . . . . . . . . . . . . . . 29
3.12 Request busy time . . . . . . . . . . . . . . . . . . . . . 28 3.12 Request busy time . . . . . . . . . . . . . . . . . . . . . 29
3.13 Response to a busy time request . . . . . . . . . . . . . . 28 3.13 Response to a busy time request . . . . . . . . . . . . . . 30
3.14 Published event that references time zone information . . . 29 3.14 Published event that references time zone information . . . 30
3.15 An event with an alarm . . . . . . . . . . . . . . . . . . . 30 3.15 An event with an alarm . . . . . . . . . . . . . . . . . . . 31
4. iCalendar XML Document Type Definition . . . . . . . . . . . 32 4. iCalendar XML Document Type Definition . . . . . . . . . . . 34
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 45 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 48
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 46 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 49
7. Security Considerations . . . . . . . . . . . . . . . . . . 47 7. Security Considerations . . . . . . . . . . . . . . . . . . 50
8. Bibliography . . . . . . . . . . . . . . . . . . . . . . . . 48 8. Bibliography . . . . . . . . . . . . . . . . . . . . . . . . 51
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 48 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 51
Full Copyright Statement . . . . . . . . . . . . . . . . . . 50 Full Copyright Statement . . . . . . . . . . . . . . . . . . 53
1. Introduction 1. Introduction
The Extended Markup Language (XML) as defined in [XML] is gaining The Extended Markup Language (XML) as defined in [XML] is gaining
widespread attention as a "web friendly" syntax for representing and widespread attention as a "web friendly" syntax for representing and
exchanging documents and data on the Internet. This interest exchanging documents and data on the Internet. This interest
includes requests for and discussion of possible document type includes requests for and discussion of possible document type
definitions (DTD) and name-space for IETF standard formats such as definitions (DTD) and name-space for IETF standard formats such as
that defined by [RFC 2445]. that defined by [RFC 2445].
This memo defines how XML can be used to represent iCalendar This memo defines how XML can be used to represent iCalendar objects.
objects. This memo includes the definition of the XML DTD for a XML This memo includes the definition of the XML DTD for a XML document
document representation of an iCalendar object. representation of an iCalendar object.
NOTE: The [RFC 2445] is the definitive reference for the definition NOTE: The [RFC 2445] is the definitive reference for the definition
of iCalendar semantics. This memo only provides an alternative, XML of iCalendar semantics. This memo only provides an alternative, XML
representation for the standard syntax defined in [RFC 2445]. This representation for the standard syntax defined in [RFC 2445]. This
memo does not introduce any semantics not already defined by [RFC memo does not introduce any semantics not already defined by [RFC
2445]. 2445].
An attempt has been made to leverage the standard features of the An attempt has been made to leverage the standard features of the XML
XML syntax in order to represent the component iCalendar semantics. syntax in order to represent the component iCalendar semantics. For
For example, strong data typing is specified using the XML notation example, strong data typing is specified using the XML notation
declaration. The element type attributes are used to represent many declaration. The element type attributes are used to represent many
of the calendar properties that provide a "global attribute" of the calendar properties that provide a "global attribute"
capability in an iCalendar object. Binary content in the ATTACH capability in an iCalendar object. Binary content in the ATTACH
component property may either be specified through an external component property may either be specified through an external entity
entity reference to a non-XML binary content or may be included in reference to a non-XML binary content or may be included in the XML
the XML document's content information, after first being encoding document's content information, after first being encoding using the
using the BASE64 scheme of [RFC 2146]. Parameter entities are used BASE64 scheme of [RFC 2146]. Parameter entities are used to
to logically group content particles in the XML DTD in order to logically group content particles in the XML DTD in order to
facilitate reading and comprehension of the structure specified by facilitate reading and comprehension of the structure specified by
the iCalendar XML DTD. the iCalendar XML DTD.
The publication of XML version 1.0 was followed by the publication The publication of XML version 1.0 was followed by the publication of
of a World-wide Web Consortium (W3C) recommendation on "Namespaces a World-wide Web Consortium (W3C) recommendation on "Namespaces in
in XML". A XML name-space is a collection of names, identified by a XML". A XML name-space is a collection of names, identified by a
URI. In anticipation of the broader use of XML namespaces, this memo URI. In anticipation of the broader use of XML namespaces, this memo
includes the definition of the URI to be used to identify the includes the definition of the URI to be used to identify the
namespace associated with the iCalendar DTD element types in other namespace associated with the iCalendar DTD element types in other
XML documents. XML applications that conform to this memo and also XML documents. XML applications that conform to this memo and also
use namespaces MUST NOT include other non-iCalendar namespaces in an use namespaces MUST NOT include other non-iCalendar namespaces in an
iCalendar XML document. iCalendar XML document.
It is expected that the DTD defined in this memo will not normally It is expected that the DTD defined in this memo will not normally be
be included with iCalendar XML documents that are distributed. included with iCalendar XML documents that are distributed. Instead,
Instead, the DTD will be referenced in the document type declaration the DTD will be referenced in the document type declaration in the
in the document entity. Such iCalendar XML documents will be document entity. Such iCalendar XML documents will be well-formed
well-formed and valid, as defined in [XML]. In addition, other and valid, as defined in [XML]. In addition, other iCalendar XML
iCalendar XML documents will be specified that do not include the documents will be specified that do not include the XML prolog. Such
XML prolog. Such iCalendar XML documents will be well-formed but not iCalendar XML documents will be well-formed but not valid.
valid.
2. Using XML For Representating iCalendar 2. Using XML For Representating iCalendar
XML is a simplified version of the text markup syntax defined by ISO XML is a simplified version of the text markup syntax defined by ISO
8879, Standard Generalized Markup Language (SGML). XML was published 8879, Standard Generalized Markup Language (SGML). XML was published
as a proposed recommendation [XML] by the World-wide Web Consortium as a proposed recommendation [XML] by the World-wide Web Consortium
(W3C) on February 10, 1998. (W3C) on February 10, 1998.
2.1 XML Dependencies 2.1 XML Dependencies
This memo specifies the XML representation for the standard This memo specifies the XML representation for the standard iCalendar
iCalendar format defined by [RFC 2445]. There are no XML format defined by [RFC 2445]. There are no XML dependencies other
dependencies other than the [XML] and the [XMLNS] recommendations. than the [XML] and the [XMLNS] recommendations.
2.2 Document Type Definition 2.2 Document Type Definition
A XML DTD for iCalendar is defined by the DTD specified in section A XML DTD for iCalendar is defined by the DTD specified in section 3.
3.
The formal public identifier (FPI) for the DTD is: The formal public identifier (FPI) for the DTD is:
-//IETF//DTD XCAL//iCalendar XML//EN -//IETF//DTD XCAL//iCalendar XML//EN
NOTE: The "DTD XCAL" text in the FPI value will be replaced with the NOTE: The "DTD XCAL" text in the FPI value will be replaced with the
text "RFC xxxx", where "xxxx" is the RFC number, when the memo is text "RFC xxxx", where "xxxx" is the RFC number, when the memo is
published as a RFC. published as a RFC.
This FPI MUST be used on the DOCTYPE statement within a XML document This FPI MUST be used on the DOCTYPE statement within a XML document
referencing the DTD defined by this memo. referencing the DTD defined by this memo.
This FPI SHOULD also be used to identify iCalendar XML documents This FPI SHOULD also be used to identify iCalendar XML documents
within operating system registries of file, clipboard and within operating system registries of file, clipboard and interactive
interactive rendering (e.g., memory clipboard or drag/drop) formats. rendering (e.g., memory clipboard or drag/drop) formats.
2.3 Working With Standard and XML iCalendar Representations 2.3 Working With Standard and XML iCalendar Representations
This memo defines an alternative, XML representation for the This memo defines an alternative, XML representation for the standard
standard iCalendar format defined in [RFC 2445]. This alternative iCalendar format defined in [RFC 2445]. This alternative
representation provides the same semantics as that defined in the representation provides the same semantics as that defined in the
standard format. standard format.
2.3.1 Conversion 2.3.1 Conversion
The standard format can be converted to and from this XML format The standard format can be converted to and from this XML format
without loss of any calendaring information. When the XML without loss of any calendaring information. When the XML
representation was defined, every attempt was made to use existing representation was defined, every attempt was made to use existing
component, property and parameter naming conventions. This greatly component, property and parameter naming conventions. This greatly
facilitates transformations between the two representations. facilitates transformations between the two representations.
2.3.2 Mixed Use of Both Representations 2.3.2 Mixed Use of Both Representations
As previously indicated, conversion between the standard and XML As previously indicated, conversion between the standard and XML
representations of iCalendar is a straightforward process. In representations of iCalendar is a straightforward process. In
addition, mixed use of both representations is also possible. addition, mixed use of both representations is also possible.
With the use of the MIME multipart content-types, compound MIME With the use of the MIME multipart content-types, compound MIME
entities containing a mix of the standard and XML representations entities containing a mix of the standard and XML representations can
can be specified. This capability is useful in applications where be specified. This capability is useful in applications where both
both representations might be encountered. In addition, this representations might be encountered. In addition, this capability
capability demonstrates the isomeric nature of the two demonstrates the isomeric nature of the two representations. XML
representations. XML applications conforming to this specification applications conforming to this specification MUST be able to
MUST be able to properly parse and process a MIME multipart entity properly parse and process a MIME multipart entity containing the
containing the MIME type associated with this iCalendar XML document MIME type associated with this iCalendar XML document type.
type.
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 [RFC2445]. This restriction will guarantee that the defined by [RFC2445]. This restriction 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 representation. only support the standard iCalendar representation.
2.4 Using Data Types 2.4 Using Data Types
Strong "data typing" is an integral design principle to the Strong "data typing" is an integral design principle to the iCalendar
iCalendar format. Strong data typing in iCalendar means that the format. Strong data typing in iCalendar means that the format type
format type for each property value is well known. Within [RFC for each property value is well known. Within [RFC 2445], the data
2445], the data type is called the "value type". The standard format type is called the "value type". The standard format defined by [RFC
defined by [RFC 2445] specifies a default value type for each 2445] specifies a default value type for each calendar and component
calendar and component property. In addition, many of the property property. In addition, many of the property definitions allow for
definitions allow for the specification of alternate value types. the specification of alternate value types. This XML representation
This XML representation continues this design principle. continues this design principle.
Explicit value/data typing in the XML representation is specified Explicit value/data typing in the XML representation is specified
with the "value" attribute on each element type. In addition, the with the "value" attribute on each element type. In addition, the
XML DTD specifies a default value/data type for each element type. XML DTD specifies a default value/data type for each element type.
XML documents conforming to this memo need only specify the "value" XML documents conforming to this memo need only specify the "value"
attribute on element types when the value needs to override the attribute on element types when the value needs to override the
default value/data type. The standard value types defined in default value/data type. The standard value types defined in
[RFC2445] are specified in the XML DTD by individual NOTATION [RFC2445] are specified in the XML DTD by individual NOTATION
declarations. The formal public identifier for standard value types declarations. The formal public identifier for standard value types
all have the common string format of: all have the common string format of:
-//IETF//NOTATION XCAL/Value Type/xxx//EN -//IETF//NOTATION XCAL/Value Type/xxx//EN
NOTE: The "XCAL" text in the FPI value will be replaced with the NOTE: The "XCAL" text in the FPI value will be replaced with the text
text "RFC xxxx", where "xxxx" is the RFC number, when the memo is "RFC xxxx", where "xxxx" is the RFC number, when the memo is
published as a RFC. published as a RFC.
Where "xxx" is replaced with the text specified in the table below. Where "xxx" is replaced with the text specified in the table below.
The following table specifies the XML value/data type that The following table specifies the XML value/data type that
corresponds to each of the standard value types defined in [RFC corresponds to each of the standard value types defined in [RFC
2445]. 2445].
+--------------+------------+-------------------------+ +--------------+------------+-------------------------+
| RFC 2445 | XML Value | Notation FPI Text | | RFC 2445 | XML Value | Notation FPI Text |
skipping to change at page 8, line 43 skipping to change at page 8, line 43
NOTATION declaration that specifies the formal public identifier NOTATION declaration that specifies the formal public identifier
associated with the other standard format. In addition, the name of associated with the other standard format. In addition, the name of
the format specified in the NOTATION declaration is specified in the the format specified in the NOTATION declaration is specified in the
"value" attribute of any element type that caste to the other "value" attribute of any element type that caste to the other
standard format. standard format.
2.5 Including Binary Content 2.5 Including Binary Content
Binary content can be included in an iCalendar object with the Binary content can be included in an iCalendar object with the
"ATTACH" component property. In the standard iCalendar format this "ATTACH" component property. In the standard iCalendar format this
content may either be specified through an external entity content may either be specified through an external entity reference,
reference, using a URI value type, or maybe specified within the using a URI value type, or maybe specified within the iCalendar
iCalendar object, after first BASE64 encoding the content. object, after first BASE64 encoding the content.
The XML representation for iCalendar also supports including binary The XML representation for iCalendar also supports including binary
content in an iCalendar object with the "attach" element type. It content in an iCalendar object with the "attach" element type. It
also supports either an external reference to the non-XML binary also supports either an external reference to the non-XML binary
content or inclusion of the binary content after first encoding the content or inclusion of the binary content after first encoding the
binary information using the BASE64 encoding of [RFC 2045]. binary information using the BASE64 encoding of [RFC 2045].
Any iCalendar properties defined in [RFC 2445] that can be used to Any iCalendar properties defined in [RFC 2445] that can be used to
include binary content are defined in the XML representation as an include binary content are defined in the XML representation as an
element type with a content model that consists of either the element type with a content model that consists of either the
"extref" or the "b64bin" element type. The "extref" element type is "extref" or the "b64bin" element type. The "extref" element type is
used to reference an external entity containing the binary content. used to reference an external entity containing the binary content.
An external reference to the binary content is specified by the An external reference to the binary content is specified by the "uri"
"uri" attribute on the "extref" element type. For every external attribute on the "extref" element type. For every external
reference, an ENTITY declaration and a corresponding NOTATION reference, an ENTITY declaration and a corresponding NOTATION
declaration MUST also be specified in an internal DTD to identify declaration MUST also be specified in an internal DTD to identify the
the location and format of the external entity. For example, the location and format of the external entity. For example, the
following XML snippets would be needed to include a reference to the following XML snippets would be needed to include a reference to the
executable "foo.exe" in the "attach" element type; which corresponds executable "foo.exe" in the "attach" element type; which corresponds
to the "ATTACH" iCalendar component property: to the "ATTACH" iCalendar component property:
<!-- Following specified within the internal DTD. --> <!-- Following specified within the internal DTD. -->
<!NOTATION EXE SYSTEM "Executable Module Format"> <!NOTATION EXE SYSTEM "Executable Module Format">
<!ENTITY attach-1 SYSTEM "http://host.com/bin/foo.exe" NDATA EXE> <!ENTITY attach-1 SYSTEM "http://host.com/bin/foo.exe" NDATA EXE>
<!-- Following specified within the body of the XML document. --> <!-- Following specified within the body of the XML document. -->
<attach><extref uri="attach-1" /></attach> <attach><extref uri="attach-1" /></attach>
The "b64bin" element type is used to include the binary content The "b64bin" element type is used to include the binary content
within the XML document, after first character encoding the binary within the XML document, after first character encoding the binary
information using the BASE64 encoding method of [RFC 2045]. For information using the BASE64 encoding method of [RFC 2045]. For
example, the following XML snippets would be needed to include the example, the following XML snippets would be needed to include the
executable "foo.exe" in the "attach" element type; after first executable "foo.exe" in the "attach" element type; after first BASE64
BASE64 encoding the binary information: encoding the binary information:
<!-- Following specified within the body of the XML document. --> <!-- Following specified within the body of the XML document. -->
<attach><b64bin fmttype="APPLICATION/OCTET-STRING"> MIICajCC <attach><b64bin fmttype="APPLICATION/OCTET-STRING"> MIICajCC
AdOgAwIBAgICBEUwDQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l AdOgAwIBAgICBEUwDQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l
dHNjYXBlIENvbW11bmljYXR5z...and so on...IENvcnBvc==</b64bin> dHNjYXBlIENvbW11bmljYXR5z...and so on...IENvcnBvc==</b64bin>
</attach> </attach>
2.6 Including Multiple iCalendar Objects 2.6 Including Multiple iCalendar Objects
skipping to change at page 10, line 53 skipping to change at page 11, line 5
| SENT-BY | sent-by | CDATA | IMPLIED | | SENT-BY | sent-by | CDATA | IMPLIED |
| TZID | tzid | CDATA | IMPLIED | | TZID | tzid | CDATA | IMPLIED |
| VALUE | value | NOTATION | See elements | | VALUE | value | NOTATION | See elements |
+----------------+----------------+-----------+-----------------+ +----------------+----------------+-----------+-----------------+
The inline "ENCODING" property parameter is not needed in the XML The inline "ENCODING" property parameter is not needed in the XML
representation. Inline binary information is always included as representation. Inline binary information is always included as
parsable character data, after first being encoded using the BASE64 parsable character data, after first being encoded using the BASE64
encoding of [RFC 2045]. encoding of [RFC 2045].
The "RANGE" property parameter defined by [RFC 2445] does not The "RANGE" property parameter defined by [RFC 2445] does not include
include the "THISONLY" enumeration. This is the implicit default, if the "THISONLY" enumeration. This is the implicit default, if the
the parameter is not specified on the "RECURRENCE-ID" property. parameter is not specified on the "RECURRENCE-ID" property. However,
However, the value is needed in the XML representation because all the value is needed in the XML representation because all attributes
attributes need to explicitly specify a default value in the need to explicitly specify a default value in the attribute's
attribute's declaration in the DTD. This enumeration has been added declaration in the DTD. This enumeration has been added to the XML
to the XML representation. representation.
A non-standard, experimental parameter can be added to the XML A non-standard, experimental parameter can be added to the XML
representation by declaring it in an ATTLIST declaration and representation by declaring it in an ATTLIST declaration and
assigning it a XML attribute type and corresponding default value. assigning it a XML attribute type and corresponding default value.
2.8 Mapping Calendar Properties to XML 2.8 Mapping Calendar Properties to XML
Calendar properties defined in the standard iCalendar format provide Calendar properties defined in the standard iCalendar format provide
information about an iCalendar object, as a whole. The calendar information about an iCalendar object, as a whole. The calendar
properties are represented in the XML representation as an attribute properties are represented in the XML representation as an attribute
skipping to change at page 12, line 6 skipping to change at page 12, line 8
| prefix> | | | | | prefix> | | | |
+-----------+-----------+---------+----------------------------+ +-----------+-----------+---------+----------------------------+
The semantics of the "xmlns" attribute, and any attribute with The semantics of the "xmlns" attribute, and any attribute with
"xmlns:" as a prefix, is as specified in [XMLNS]. It is used to "xmlns:" as a prefix, is as specified in [XMLNS]. It is used to
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
XML document. To specify the iCalendar namespace, the attribute document. To specify the iCalendar namespace, the attribute value
value for the "xmlns" and any attribute with the prefix "xmlns:" 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-01.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://
"http://www.ietf.org/rfc/rfcxxxx.txt", where "xxxx" is the RFC www.ietf.org/rfc/rfcxxxx.txt", where "xxxx" is the RFC number, when
number, when this memo is published as a RFC. 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-01.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-01.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>
skipping to change at page 13, line 4 skipping to change at page 13, line 11
The following table specifies additional attributes that are The following table specifies additional attributes that are
permitted on the "vcalendar" element type. permitted on the "vcalendar" element type.
+-----------+-----------+---------+----------------------------+ +-----------+-----------+---------+----------------------------+
| Attribute | Attribute | Default | Description | | Attribute | Attribute | Default | Description |
| Name | Type | Value | | | Name | Type | Value | |
+-----------+-----------+---------+----------------------------+ +-----------+-----------+---------+----------------------------+
| language | CDATA | IMPLIED | Used to specify the default| | language | CDATA | IMPLIED | Used to specify the default|
+-----------+-----------+---------+----------------------------+ +-----------+-----------+---------+----------------------------+
The "language" attribute permits the default language to be
specified for the whole iCalendar object. If the "language" The "language" attribute permits the default language to be specified
attribute is specified on the XML document, then if the XML for the whole iCalendar object. If the "language" attribute is
representation is converted into the standard format the "LANGUAGE" specified on the XML document, then if the XML representation is
property parameter MUST be specified on each TEXT valued property to converted into the standard format the "LANGUAGE" property parameter
prevent information loss; when translating into the standard format. MUST be specified on each TEXT valued property to prevent information
loss; when translating into the standard format.
2.9 Mapping Component Properties to XML 2.9 Mapping Component Properties to XML
Component properties in the standard iCalendar format provide Component properties in the standard iCalendar format provide
calendar information about the calendar component. The component calendar information about the calendar component. The component
properties defined in the standard iCalendar format are represented properties defined in the standard iCalendar format are represented
in the XML representation as element types. The following tables in the XML representation as element types. The following tables
specify the element types corresponding to each of the properties in specify the element types corresponding to each of the properties in
the specified property category. the specified property category.
skipping to change at page 16, line 39 skipping to change at page 16, line 39
| STANDARD | standard | standard.man or standard.optm | | STANDARD | standard | standard.man or standard.optm |
| | | entity | | | | entity |
| DAYLIGHT | daylight | daylight.man or daylight.optm | | DAYLIGHT | daylight | daylight.man or daylight.optm |
| | | entity | | | | entity |
| VALARM | valarm | valarm.audio, valarm.display, | | VALARM | valarm | valarm.audio, valarm.display, |
| | | valarm.email and | | | | valarm.email and |
| | | valarm.procedure entity | | | | valarm.procedure entity |
+----------------+------------+-------------------------------+ +----------------+------------+-------------------------------+
The [RFC 2445] specification specifies that the equivalent component The [RFC 2445] specification specifies that the equivalent component
properties to the "comment", "description", "location", "summary" properties to the "comment", "description", "location", "summary" and
and "contact" element types can contain formatted content, such as "contact" element types can contain formatted content, such as is
is specified by multiple lines of text. In such cases, the formatted specified by multiple lines of text. In such cases, the formatted
text should be specified in as CDATA Section content. The CDATA text should be specified in as CDATA Section content. The CDATA
section specifies arbitrary character data that is not meant to be section specifies arbitrary character data that is not meant to be
interpretted. It is not scanned for markup by the XML parser. The interpretted. It is not scanned for markup by the XML parser. The
CDATA Section in these element types MUST NOT contain markup or CDATA Section in these element types MUST NOT contain markup or other
other such alternate representation of the property value. The such alternate representation of the property value. The "altrep"
"altrep" attribute is used to reference any such alternate attribute is used to reference any such alternate representation for
representation for the textual content of these element types. the textual content of these element types.
2.10 Parameter Entities 2.10 Parameter Entities
The external, iCalendar XML DTD specified in section 3 makes use of The external, iCalendar XML DTD specified in section 3 makes use of
parameter entity declarations. This XML feature is used to group parameter entity declarations. This XML feature is used to group
declarations within the DTD. This technique has been used in DTD declarations within the DTD. This technique has been used in DTD
design in order to facilitate the reading and comprehension of the design in order to facilitate the reading and comprehension of the
structure specified by the DTD. structure specified by the DTD.
2.11 Namespace 2.11 Namespace
[XMLNS] defines "Namespaces in XML" to be a collection of names, [XMLNS] defines "Namespaces in XML" to be a collection of names,
identified by a URI, which are used in XML documents as element identified by a URI, which are used in XML documents as element types
types and attribute names. The [XML] specification does not include and attribute names. The [XML] specification does not include a
a definition for namespaces, but does set down some guidelines for definition for namespaces, but does set down some guidelines for
experimental naming of namespaces. experimental naming of namespaces.
XML namespaces allow multiple markup vocabulary in a single XML namespaces allow multiple markup vocabulary in a single document.
document. Considering the utility of the iCalendar properties in Considering the utility of the iCalendar properties in other
other applications, it is important for the iCalendar XML DTD to applications, it is important for the iCalendar XML DTD to define a
define a namespace for the iCalendar element types. namespace for the iCalendar element types.
This memo defines the value that MUST be used in non-iCalendar XML This memo defines the value that MUST be used in non-iCalendar XML
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"?>
skipping to change at page 17, line 42 skipping to change at page 17, line 43
-drafts/draft-ietf-calsch-many-xcal-01.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 over
over SMTP/MIME email. The "text/xml" and "application/xml" SMTP/MIME email. The "text/xml" and "application/xml" content-types
content-types have been registered for XML documents. However, use have been registered for XML documents. However, use of these
of these content-type definitions present some problems for XML content-type definitions present some problems for XML applications
applications such as calendaring and scheduling. such as calendaring and scheduling.
The "text/xml" and "application/xml" content-type definitions do not The "text/xml" and "application/xml" content-type definitions do not
provide for any header field parameters to identify the type of XML provide for any header field parameters to identify the type of XML
document contained in the MIME entity. This means that a recipient document contained in the MIME entity. This means that a recipient
mail user agent must (MUA) open up each "text/xml" or mail user agent must (MUA) open up each "text/xml" or "application/
"application/xml" content in order to determine what object handler xml" content in order to determine what object handler is needed to
is needed to process the information. To a MUA, all XML documents process the information. To a MUA, all XML documents look like just
look like just plain "text/xml" or "application/xml" content. plain "text/xml" or "application/xml" content.
Additionally, it is accepted practice for a MUA to provide iconic Additionally, it is accepted practice for a MUA to provide iconic
feedback to the user for individual content-types that are supported feedback to the user for individual content-types that are supported
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 XML documents with the experimental content-type "application/
"application/calendar+xml". The content-type header field SHOULD calendar+xml". The content-type header field SHOULD also contain a
also contain a "component" and "method" parameter to clearly "component" and "method" parameter to clearly identify a comma-
identify a comma-separated list of components and the singular separated list of components and the singular method used in the
method used in the iCalendar XML document. For example, an iCalendar iCalendar XML document. For example, an iCalendar XML document
XML document specifying a REQUEST for a VEVENT and VTODO would be specifying a REQUEST for a VEVENT and VTODO would be specified with
specified with the following content-type header field: the following content-type header field:
content-type:application/calendar+xml;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
be able to receive and properly process the able to receive and properly process the "application/calendar+xml"
"application/calendar+xml" document contained within a "multipart" document contained within a "multipart" message content-type.
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
extension be the text "XCS". be the text "XCS".
3. Example Usage 3. Example Usage
The following sections provide various examples of iCalendar XML The following sections provide various examples of iCalendar XML
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
skipping to change at page 19, line 41 skipping to change at page 20, line 41
<categories> <categories>
<item>Appointment</item> <item>Appointment</item>
</categories> </categories>
</vevent> </vevent>
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
3.2 Adding non-standard, experimental extensions 3.2 Adding non-standard, experimental extensions
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 a non-standard, experimental extension, as provided also includes a non-standard, experimental extension, as provided for
for by [RFC 2445]. The iCalendar object specifies the publication of by [RFC 2445]. The iCalendar object specifies the publication of a
a to-do with a non-standard experimental property for a customer to-do with a non-standard experimental property for a customer charge
charge code. code.
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"?>
skipping to change at page 28, line 31 skipping to change at page 29, line 37
<url uri="jsmith.ifb" /> <url uri="jsmith.ifb" />
<freebusy>19980314T233000Z/19980315T003000Z</freebusy> <freebusy>19980314T233000Z/19980315T003000Z</freebusy>
<freebusy>19980316T153000Z/19980316T163000Z</freebusy> <freebusy>19980316T153000Z/19980316T163000Z</freebusy>
<freebusy>19980318T030000Z/19980318T040000Z</freebusy> <freebusy>19980318T030000Z/19980318T040000Z</freebusy>
</vfreebusy> </vfreebusy>
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
3.12 Request busy time 3.12 Request busy time
The following is a snippet of an iCalendar XML document that The following is a snippet of an iCalendar XML document that requests
requests a calendar user's busy time information. a calendar user's busy time information.
<iCalendar> <iCalendar>
<vcalendar method="REQUEST" <vcalendar method="REQUEST"
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>
<dtstamp>19970901T083000Z</dtstamp> <dtstamp>19970901T083000Z</dtstamp>
<organizer>MAILTO:jane_doe@host1.com</organizer> <organizer>MAILTO:jane_doe@host1.com</organizer>
<dtstart>19971015T050000Z</dtstart> <dtstart>19971015T050000Z</dtstart>
skipping to change at page 29, line 30 skipping to change at page 30, line 50
<attendee>MAILTO:john_public@host2.com</attendee> <attendee>MAILTO:john_public@host2.com</attendee>
<freebusy value="PERIOD">19971015T050000Z/PT8H30M, <freebusy value="PERIOD">19971015T050000Z/PT8H30M,
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M</freebusy> 19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M</freebusy>
</vfreebusy> </vfreebusy>
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
3.14 Published event that references time zone information 3.14 Published event that references time zone information
The following is a snippet of an iCalendar XML document that The following is a snippet of an iCalendar XML document that
publishes calendar information about an event that includes publishes calendar information about an event that includes date/time
date/time values that reference a time zone definition. values that reference a time zone definition.
<iCalendar> <iCalendar>
<vcalendar version="2.0" <vcalendar version="2.0"
prodid="-//hacksw/handcal//NONSGML 1.0//EN"> prodid="-//hacksw/handcal//NONSGML 1.0//EN">
<vtimezone> <vtimezone>
<tzid>US-Eastern</tzid> <tzid>US-Eastern</tzid>
<standard> <standard>
<dtstart>19981025T020000</dtstart> <dtstart>19981025T020000</dtstart>
<tzoffsetfrom>-0400</tzoffsetfrom> <tzoffsetfrom>-0400</tzoffsetfrom>
<tzoffsetto>0500</tzoffsetto> <tzoffsetto>0500</tzoffsetto>
skipping to change at page 32, line 7 skipping to change at page 34, line 7
<action>PROCEDURE</action> <action>PROCEDURE</action>
<attach><extref uri="doit"/></attach> <attach><extref uri="doit"/></attach>
<trigger>19990704T230000Z</trigger> <trigger>19990704T230000Z</trigger>
</valarm> </valarm>
</vevent> </vevent>
</vcalendar> </vcalendar>
</iCalendar> </iCalendar>
4. iCalendar XML Document Type Definition 4. iCalendar XML Document Type Definition
The following DTD conforms to XML version 1.0, as specified by The following DTD conforms to XML version 1.0, as specified by [XML].
[XML].
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!-- ******************* --> <!-- ******************* -->
<!-- Entity declarations --> <!-- Entity declarations -->
<!-- ******************* --> <!-- ******************* -->
<!ENTITY % attr.altrep " <!ENTITY % attr.altrep "
altrep ENTITY #IMPLIED altrep ENTITY #IMPLIED
"> ">
skipping to change at page 47, line 11 skipping to change at page 50, line 11
In addition, this memo defines the XML FPIs corresponding to each of In addition, this memo defines the XML FPIs corresponding to each of
the value types specified in [RFC 2445]. the value types specified in [RFC 2445].
7. Security Considerations 7. Security Considerations
CDATA Sections - - A XML iCalendar document may contain CDATA CDATA Sections - - A XML iCalendar document may contain CDATA
sections to represent content for specific element types. The CDATA sections to represent content for specific element types. The CDATA
section specifies arbitrary character data that is not meant to be section specifies arbitrary character data that is not meant to be
interpretted. It is not scanned by the XML parser for markup. While interpretted. It is not scanned by the XML parser for markup. While
this memo restricts that any CDATA section MUST NOT contain markup this memo restricts that any CDATA section MUST NOT contain markup or
or other such alternate representation for the property value, in other such alternate representation for the property value, in
general, CDATA section from a non-conformant implementation can general, CDATA section from a non-conformant implementation can
contain content such as HTML markup. HTML text can be used to invoke contain content such as HTML markup. HTML text can be used to invoke
programs. Implementors should be aware that this may leave an programs. Implementors should be aware that this may leave an
implementation open to malicious attack that might occur as a result implementation open to malicious attack that might occur as a result
of executing the markup in the CDATA section. of executing the markup in the CDATA section.
PROCEDURAL ALARMS - - A XML iCalendar document can be created that PROCEDURAL ALARMS - - A XML iCalendar document can be created that
contains a "VEVENT" and "VTODO" calendar component with "VALARM" contains a "VEVENT" and "VTODO" calendar component with "VALARM"
calendar components. The "VALARM" calendar component can be of type calendar components. The "VALARM" calendar component can be of type
PROCEDURE and can have an attachment containing some sort of PROCEDURE and can have an attachment containing some sort of
skipping to change at page 48, line 8 skipping to change at page 51, line 8
Uniform Resource Locators that can be programmed resources. Uniform Resource Locators that can be programmed resources.
Implementers and users of this memo should be aware of the network Implementers and users of this memo should be aware of the network
security implications of accepting and parsing such information. security implications of accepting and parsing such information.
In addition, the security considerations observed by implementations In addition, the security considerations observed by implementations
of electronic mail systems should be followed for this memo. of electronic mail systems should be followed for this memo.
8. Bibliography 8. Bibliography
[FPI] F. Dawson, "iCalendar Formal Public Identifier", Internet [FPI] F. Dawson, "iCalendar Formal Public Identifier", Internet
Draft, Draft, http://www.internic.net/internet-drafts/draft-calsch-icalfpi-
http://www.internic.net/internet-drafts/draft-calsch-icalfpi-00.txt, 00.txt, September 1998.
September 1998.
[ISO9070] "Information Technology_SGML Support Facilities_ [ISO9070] "Information Technology_SGML Support Facilities_
Registration Procedures for Public Text Owner Identifiers", ISO/IEC Registration Procedures for Public Text Owner Identifiers", ISO/IEC
9070, Second Edition, International Organization for 9070, Second Edition, International Organization for Standardization,
Standardization, April 1991. April 1991.
[RFC 2045] N. Freed, N. Borenstein, "Multipurpose Internet Mail [RFC 2045] N. Freed, N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) - Part One: Format of Internet Message Bodies", Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC
RFC 2045, November 1996. 2045, November 1996.
[RFC 2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC 2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, http://www.ietf.org/rfc/rfc2119.txt, Requirement Levels", RFC 2119, http://www.ietf.org/rfc/rfc2119.txt,
March 1997. March 1997.
[RFC 2445] F. Dawson and D. Stenerson, "Internet Calendaring and [RFC 2445] F. Dawson and D. Stenerson, "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", RFC 2445, Scheduling Core Object Specification (iCalendar)", RFC 2445, http://
http://www.ietf.org/rfc/rfc2445.txt, November 1998. www.ietf.org/rfc/rfc2445.txt, November 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.
[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
skipping to change at page 49, line 15 skipping to change at page 52, line 26
INET-Consulting LLC INET-Consulting LLC
1795 W. Broadway #266 1795 W. Broadway #266
Idaho Falls, ID 83402 Idaho Falls, ID 83402
US US
Phone: +1 (208) 520 4044 Phone: +1 (208) 520 4044
Fax: +1 (208) 552 1179 Fax: +1 (208) 552 1179
EMail: doug@royer.com EMail: doug@royer.com
Eric R. Plamondon Eric R. Plamondon
Steltor Oracle
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 (2002). 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 implementation 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
are included on all such copies and derivative works.However, this 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
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process MUST be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 52 change blocks. 
186 lines changed or deleted 183 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/