HTTP/1.1 200 OK Date: Mon, 08 Apr 2002 23:30:42 GMT Server: Apache/1.3.20 (Unix) Last-Modified: Wed, 18 Nov 1998 16:53:00 GMT ETag: "2e97ce-98eb-3652fb6c" Accept-Ranges: bytes Content-Length: 39147 Connection: close Content-Type: text/plain Network Working Group Frank Dawson, Lotus Internet Draft Dawson 3 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 Dawson 4 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 Dawson 5 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 "> Dawson 9 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 Dawson 10 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 Dawson 12 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 <-- Alarm component property element declarations --> 3 iCalendar Notation The formal public identifier (FPI) for the DTD described in this specification is "-//IETF//DTD iCalendar//EN". A XML document can reference an external non-XML entity containing an iCalendar object, as specified by [RFC2445]. The iCalendar object, Dawson 15 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 while encoded in the standard, non-XML format can be referenced in an external entity reference that identifies the [RFC2445] format in a notation declaration. The [RFC2445] format is identified by the formal public identifier "-//IETF//NONSGML iCalendar//EN", as defined in [FPI]. 4 Example Usage 4.1 Simple iCalendar Object The following is a simple example of a XML document using this DTD. 19981116T163000Z 19981116T190000Z Project XYZ Review Conference Room 23A 4.2 iCalendar with non-standard extension The following is an example of an iCalendar object that also includes a non-standard extension. ]> 19981105T133000Z 19981106T133000Z Draft a test plan 1998-ABC Corp-1234 1 Dawson 16 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 4.3 iCalendar with ATTACH property The following is an example of an iCalendar object that also includes an external reference to an attachment. ]> 19981212T150000Z 19981212T160000Z Department Holiday Party Conference Room 23A The following is an example of an iCalendar object that includes an attachment as inline binary content. method="PUBLISH"> 19981212T150000Z 19981212T160000Z Department Holiday Party Conference Room 23A MIICajCCAdOgAwIBAgICBEUwDQ EEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW 11bmljYXRpb25z...and so on...IENvcnBvc== 4.4 Document with multiple iCalendar objects The following is an example of a document that includes more than one iCalendar object. Dawson 17 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 method="PUBLISH"> 19981010T000000Z 19981010T235959Z Register for conference 2 method="PUBLISH"> 19981120T133000Z 19981122T183000Z IT Conference Downtowner Hotel 4.5 Document utilizing iCalendar namespace The following is an example of a XML document that declares the iCalendar namespace as it's default namespace. The following is an example of a XML document that includes elements from the iCalendar namespace. 19981123T133000Z 19981123T203000Z 1234567 999.99 4.6 XML document reference to a non-XML iCalendar object The following is an example of a XML document with a proper reference to a non-XML entity containing an iCalendar object in the format defined by [RFC2445]. This example shows how existing iCalendar Dawson 18 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 objects can be integrated into XML documents using the XML structure defined in this document. ]> 5 Namespace [NSPACE] defines "XML namespaces" to be a collection of names, identified by a URI, which are used in XML documents as element types and attribute names. XML namespaces allow multiple markup vocabulary in a single document. Considering the utility of the iCalendar properties in other applications, it is important for the iCalendar XML DTD to define a namespace for the iCalendar element types. This memo includes the definition of both a qualified name for the iCalendar namespace and also a default namespace. The namespace declaration is specified by attributes on the "iCal" element. The default namespace is specified with the "xmlns" attribute and the qualified name for the iCalendar namespace is specified with the "xmlns:iCal" attribute. The default namespace attribute is useful in XML documents that are based on the iCalendar document types. The qualified name for the iCalendar namespace is useful in XML documents that partially consist of iCalendar elements types but also consist of element types from other schemas. The following is an example of the iCalendar namespace declaration using the qualified namespace: Dawson 19 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 The following is an example of an iCalendar namespace declaration using the default namespace: 6 Acknowledgments The following have participated in the drafting and discussion of this memo: Paul Hoffman 7 Security Considerations Security issues are not currently discussed in this memo. 8 Bibliography [FPI] F. Dawson, "iCalendar Formal Public Identifier", Internet Draft, http://www.internic.net/internet-drafts/draft-calsch-ical-fpi- 00.txt, July 1998. [ISO9070] "Information Technology_SGML Support Facilities_ Registration Procedures for Public Text Owner Identifiers", ISO/IEC 9070, Second Edition, International Organization for Standardization, April, 1991. [RFC 2045] N. Freed, N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC 2045, November 1996. [RFC 2119] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, ftp://ftp.isi.edu/in-notes/ rfc2119.txt, March 1997. [NSPACE] T. Bray, D. Hollander, A. Layman, "Namespaces in XML", WD- xml-names-19980916, http://www.w3.org/TR/1998/WD-xml-names-19980916, Septebmer 1998. [RFC2445] F. Dawson and T. Howes, "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, ftp://ftp.isi.edu/in-notes/rfc2445.txt, November 1998. [XML] "Extensible Markup Language (XML)", Worldwid Web Consortium, http://www.w3.org/TR/PR-xml-971208, December 1997. Dawson 20 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 9 Author's Address The following address information is provided in a vCard XML DTD electronic business card, format. Frank Dawson Dawson Frank Lotus Development Corporation 6544 Battleford Drive Raleigh NC 27613-3502 +1-617-693-8728 +1-919-676-9515 Frank_Dawson@Lotus.com fdawson@earthlink.net 10 Dawson 21 Expires May 1999 Internet Draft iCalendar XML DTD November 16, 1998 Full Copyright Statement "Copyright (C) The Internet Society (1998).All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works.However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process MUST be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Dawson 22 Expires May 1999