idnits 2.17.1 

draft-hare-xcalendar-03.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

  ** It looks like you're using RFC 3978 boilerplate.  You should update this
     to the boilerplate described in the IETF Trust License Policy document
     (see https://trustee.ietf.org/license-info), which is required now.

  -- Found old boilerplate from RFC 3978, Section 5.1 on line 14.

  -- Found old boilerplate from RFC 3978, Section 5.5 on line 1753.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1730.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1737.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1743.

  ** This document has an original RFC 3978 Section 5.4 Copyright Line,
     instead of the newer IETF Trust Copyright according to RFC 4748.

  ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
     of the newer disclaimer which includes the IETF Trust according to RFC
     4748.


  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

  == No 'Intended status' indicated for this document; assuming Proposed
     Standard


  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

  ** The document seems to lack an IANA Considerations section.  (See Section
     2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
     when there are no actions for IANA.)

  ** There are 95 instances of too long lines in the document, the longest
     one being 57 characters in excess of 72.

  ** There are 53 instances of lines with control characters in the document.

  ** The abstract seems to contain references ([RFC2447], [RFC2119], [CAP],
     [RFC2445], [RFC2446]), which it shouldn't.  Please replace those with
     straight textual mentions of the documents in question.

  ** The document seems to lack a both a reference to RFC 2119 and the
     recommended RFC 2119 boilerplate, even if it appears to use RFC 2119
     keywords -- however, there's a paragraph with a matching beginning.
     Boilerplate error?

     RFC 2119 keyword, line 130: '...o use namespaces MAY include other	non...'
     RFC 2119 keyword, line 133: '...   Documents MAY include a Document Ty...'
     RFC 2119 keyword, line 137: '... a DTD or schema MAY include	definitio...'
     RFC 2119 keyword, line 138: '...t conforming to this memo MUST	provide...'
     RFC 2119 keyword, line 166: '... representations SHOULD provide the sa...'
     (17 more instances...)


  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
     match the current year

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If you
     have contacted all the original authors and they are all willing to grant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer. 
     (See the Legal Provisions document at
     https://trustee.ietf.org/license-info for more information.)

  -- The document date (May 16, 2005) is 6914 days in the past.  Is this
     intentional?

  -- Found something which looks like a code comment -- if you have code
     sections in the document, please surround them with '<CODE BEGINS>' and
     '<CODE ENDS>' lines.


  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  -- Missing reference section? 'RFC 2445' on line 1690 looks like a reference

  -- Missing reference section? 'RFC2446' on line 114 looks like a reference

  -- Missing reference section? 'RFC2447' on line 152 looks like a reference

  -- Missing reference section? 'CAP' on line 1702 looks like a reference

  -- Missing reference section? 'RFC 2119' on line 1686 looks like a reference

  -- Missing reference section? 'XML' on line 1712 looks like a reference

  -- Missing reference section? 'RCF 2446' on line 92 looks like a reference

  -- Missing reference section? 'RFC 2447' on line 1698 looks like a reference

  -- Missing reference section? 'RFC 2446' on line 1694 looks like a reference

  -- Missing reference section? 'RFC2445' on line 114 looks like a reference

  -- Missing reference section? 'XMLNS' on line 271 looks like a reference

  -- Missing reference section? 'XSL' on line 1715 looks like a reference

  -- Missing reference section? 'FPI' on line 1672 looks like a reference

  -- Missing reference section? 'ISO9070' on line 1677 looks like a reference

  -- Missing reference section? 'RFC 2045' on line 1682 looks like a reference

  -- Missing reference section? 'XSLT' on line 1718 looks like a reference


     Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 24 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.

--------------------------------------------------------------------------------


2	Network Working Group                                            T. Hare
3	Internet-Draft                                                Individual
4	Expires: November 17, 2005                                  May 16, 2005

6	            Guideline for use of XML with iCalendar elements
7	                        draft-hare-xcalendar-03

9	Status of this Memo

11	   By submitting this Internet-Draft, each author represents that any
12	   applicable patent or other IPR claims of which he or she is aware
13	   have been or will be disclosed, and any of which he or she becomes
14	   aware will be disclosed, in accordance with Section 6 of BCP 79.

16	   Internet-Drafts are working documents of the Internet Engineering
17	   Task Force (IETF), its areas, and its working groups.  Note that
18	   other groups may also distribute working documents as Internet-
19	   Drafts.

21	   Internet-Drafts are draft documents valid for a maximum of six months
22	   and may be updated, replaced, or obsoleted by other documents at any
23	   time.  It is inappropriate to use Internet-Drafts as reference
24	   material or to cite them other than as "work in progress."

26	   The list of current Internet-Drafts can be accessed at
27	   http://www.ietf.org/ietf/1id-abstracts.txt.

29	   The list of Internet-Draft Shadow Directories can be accessed at
30	   http://www.ietf.org/shadow.html.

32	   This Internet-Draft will expire on November 17, 2005.

34	Copyright Notice

36	   Copyright (C) The Internet Society (2005).

38	Abstract

40	   This memo defines a guideline for using XML to represent calendaring
41	   information that corresponds to the iCalendar, Internet Calendaring
42	   and Scheduling Core Object Specification defined by [RFC 2445] and
43	   the protocols defined by [RFC2446], [RFC2447] and [CAP].  This memo
44	   applies to all [RFC 2445] extensions and	modifications.

46	   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
47	   "SHOULD",	"SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
48	   document are to be	interpreted as described in [RFC 2119].

50	Table of Contents

52	   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
53	   2.  Using XML For Representing iCalendar . . . . . . . . . . . . .  5
54	   3.  XML and XSL Dependencies . . . . . . . . . . . . . . . . . . .  6
55	   4.  Working With Standard and XML iCalendar Representations  . . .  7
56	   5.  Conversion . . . . . . . . . . . . . . . . . . . . . . . . . .  8
57	   6.  Mixed Use of Both Representations  . . . . . . . . . . . . . .  9
58	   7.  Using Data Types . . . . . . . . . . . . . . . . . . . . . . . 10
59	   8.  Namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . 11
60	   9.  Emailing documents with iCalendar XML Representation . . . . . 13
61	   10.   iCalendar XML Representation and File Systems  . . . . . . . 14
62	   11.   Example Usage  . . . . . . . . . . . . . . . . . . . . . . . 15
63	     11.1  Example DTD  . . . . . . . . . . . . . . . . . . . . . . . 15
64	     11.2  An example XSL transformation  . . . . . . . . . . . . . . 28
65	     11.3  A well-formed and valid iCalendar XML document . . . . . . 34
66	     11.4  Including binary content in attachments  . . . . . . . . . 34
67	     11.5  Including binary content inline  . . . . . . . . . . . . . 35
68	     11.6  iCalendar XML document with multiple iCalendar objects . . 36
69	     11.7  Using the iCalendar namespace  . . . . . . . . . . . . . . 37
70	     11.8  Publish meeting information  . . . . . . . . . . . . . . . 38
71	     11.9  Publish transparent annual event . . . . . . . . . . . . . 38
72	     11.10   Meeting invitation . . . . . . . . . . . . . . . . . . . 39
73	     11.11   Assign a to-do . . . . . . . . . . . . . . . . . . . . . 39
74	     11.12   Publish busy time  . . . . . . . . . . . . . . . . . . . 40
75	     11.13   Request busy time  . . . . . . . . . . . . . . . . . . . 41
76	     11.14   Issue a CAP command  . . . . . . . . . . . . . . . . . . 41
77	     11.15   A well-formed and valid XML document which can be
78	             transformed into iCalendar . . . . . . . . . . . . . . . 41
79	   12.   Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . 44
80	   13.   Security Considerations  . . . . . . . . . . . . . . . . . . 45
81	       Author's Address . . . . . . . . . . . . . . . . . . . . . . . 45
82	   A.  Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . 46
83	       Intellectual Property and Copyright Statements . . . . . . . . 48

85	1.  Introduction

87	   The Extended Markup Language (XML) as defined in [XML] has gained
88	   widespread attention as a "web friendly" syntax for representing and
89	   exchanging documents	and data on the Internet.  This interest
90	   includes requests for and discussion of possible document type
91	   definitions (DTD) and name-spaces for IETF standard	formats such as
92	   that defined by [RFC 2445], [RCF 2446], and [RFC 2447].

94	   This memo defines how XML can be used to represent iCalendar
95	   objects,and how iCalendar namespaces can be used with other XML
96	   documents.  An example DTD is provided although use of a DTD is not
97	   required.

99	   This memo does not try to enforce any specific one-to-one mapping
100	   between XML	objects and iCalendar objects, but instead attempts to
101	   document the method whereby XML developers can provide
102	   interoperability with iCalendar.

104	   NOTE: The [RFC 2445] is the definitive reference for the definition
105	   of iCalendar semantics.  This memo only provides a guideline for
106	   representing such semantics in XML.  This memo does not introduce any
107	   new semantics for items already defined by [RFC 2445].  [RFC 2446],
108	   [RFC 2447], and [CAP] are the references for protocols	for the
109	   exchange of iCalendar objects.  This memo does not introduce any new
110	   protocols or functions beyond those in the respective documents.

112	   An attempt has been made to guide the developer in use of XML to
113	   represent iCalendar semantics, allowing XML-based applications to
114	   make use of the iCalendar [RFC2445] and related protocols [RFC2446],
115	   [RFC2447], and [CAP] semantics and to provide interoperability
116	   between XML-based applications and iCalendar-compliant	applications.

118	   The publication of XML version 1.0 was followed by publication of two
119	   World-wide Web Consortium (W3C) recommendations relevant to this
120	   memo.  The first was a recommendation on "Namespaces in XML" and the
121	   other was a recommendation on "Extensible Stylesheet Language" and
122	   "Extensible Stylesheet Language Transformation" (XSL and XSLT).  An
123	   XML name-space is a collection of names, identified by a URI.  An XSL
124	   transformation(XSLT)is a document in the Extensible Stylesheet
125	   Language (XSL) which provides a method for transforming an XML
126	   document into some other form.  In anticipation of the use of XML
127	   namespaces, this memo includes the definition of URIs to be used to
128	   identify the namespaces for iCalendar [RFC 2445], iTIP [RFC 2446],
129	   iMIP [RFC 2447] and CAP elements.  XML applications that conform to
130	   this memo and also use namespaces MAY include other	non-iCalendar
131	   namespaces.

133	   Documents MAY include a Document Type Definition (DTD), an XML
134	   schema, or may	reference external versions of either.  This memo
135	   allows documents containing	iCalendar XML objects to be constructed
136	   with either.  DTDs and Schemas are outside	the scope of this memo.  A
137	   document containing a DTD or schema MAY include	definitions for
138	   calendar elements.  Any document conforming to this memo MUST	provide
139	   an XSL transformation which will render those calendar elements
140	   into	standard iCalendar/iTIP/iMIP/CAP (as appropriate) elements.

142	2.  Using XML For Representing iCalendar

144	   XML is a simplified version of the text markup syntax defined by ISO
145	   8879, Standard Generalized Markup Language (SGML).  XML was published
146	   as a proposed recommendation [XML] by the World-wide Web Consortium
147	   (W3C) on February 10, 1998.

149	3.  XML and XSL Dependencies

151	   This memo specifies the XML representation for the standard iCalendar
152	   elements defined by [RFC 2445], [RFC 2446], [RFC2447], and [CAP].
153	   There are no XML dependencies other than the [XML] and the [XMLNS]
154	   recommendations.

156	   This memo requires that conforming documents include a reference to
157	   an [XSL] stylesheet for transforming the document into standard
158	   iCalendar format.  How the transformation is done is left to the
159	   implementor.  Providing an XSL transform into iCalendar objects does
160	   not preclude providing other transforms.

162	4.  Working With Standard and XML iCalendar Representations

164	   This memo provides a guideline for using alternative, XML
165	   representations for the standard iCalendar elements defined in [RFC
166	   2445].  These alternative representations SHOULD provide the same
167	   semantics as that defined in the standard format.  It is the goal of
168	   this memo to allow all [RFC 2445] extensions and modifications to be
169	   translated into and from this XML format.

171	5.  Conversion

173	   This memo requires any compliant document to be transformable into
174	   standard iCalendar information.  It is recognized that such
175	   conversion MAY be asymmetric,	since compliant documents MAY include
176	   information which is not representable in iCalendar and which would
177	   be lost during any "round trip" conversions.  This does not preclude
178	   implementation of "round-trippable" transformations, but they are not
179	   required.

181	   To formalize and standardize the interchange of iCalendar information
182	   through	XML, each conforming document MUST include reference to an
183	   XSL stylesheet which can transform the document into a standard
184	   iCalendar [RFC 2445] document of MIME	content-type "text/calendar".

186	6.  Mixed Use of Both Representations

188	   As previously indicated, conversion between the XML and standard
189	   representations of iCalendar is a straightforward process using XSL
190	   transformations.  In addition, mixed use of both representations is
191	   also possible using MIME objects.

193	   While MIME multipart content-types can be used to provide a mix of
194	   both the standard and XML representations, this is NOT required.
195	   Instead, each document MUST include a reference to an XSL stylesheet
196	   which can transform the XML representation into standard iCalendar
197	   (and possibly, iTIP, iMIP, or CAP) syntax.

199	   With the use of the MIME multipart content-types, compound MIME
200	   entities containing a mix of the standard and XML representations can
201	   be specified.  Internet applications conforming to this memo MAY send
202	   both the standard and XML representation of the iCalendar objects, to
203	   provide compatibility with Internet applications which cannot process
204	   the required XSL transformation.

206	7.  Using Data Types

208	   Strong "data typing" is an integral design principle to the iCalendar
209	   format.	Strong data typing in iCalendar means that the format type
210	   for each property	value is well known.  Within [RFC 2445], the data
211	   type is called the "value type".  The standard format defined by [RFC
212	   2445] specifies a default value type for each calendar and component
213	   property.  In addition, many of the property definitions allow for
214	   the specification of alternate value types.  The required XSL
215	   transformation in this memo MUST create iCalendar elements with
216	   proper types.  Consult iCalendar [RFC 2445] for documentation of
217	   value types.

219	8.  Namespaces

221	   [XMLNS] defines "Namespaces in XML" to be a collection of names,
222	   identified by a URI, which are used in XML documents as element types
223	   and attribute names.  The [XML] specification does not include a
224	   definition for namespaces, but does set down some guidelines for
225	   experimental naming of namespaces.

227	   XML namespaces allow multiple markup vocabulary in a single document.
228	   Documents	and applications conforming to this memo MAY use multiple
229	   namespaces with the	iCalendar, iTIP, iMIP, and CAP namespaces.
230	   Multiple namespaces MUST be used for the different iCalendar and
231	   protocol elements.  This requirement is intended to provide clarity
232	   in the document, by discriminating calendar object elements
233	   from	protocol elements.

235	   The document at the namespace URI does not contain any defintions but
236	   serves as a unique identifier to allow specification of different
237	   namespaces.  Applications complying with this memo MUST use the
238	   following URIs for namespace elements:

240	      iCalendar:	http://www.ietf.org/rfc/rfc2445.txt

242	      iTIP:		http://www.ietf.org/rfc/rfc2446.txt

244	      iMIP:		http://www.ietf.org/rfc/rfc2447.txt

246	      CAP:		http://www.ietf.org/internet-drafts/
247	      draft-ietf-calsch-cap-13.txt

249	   NOTE: the URI for CAP will be replaced with the RFCxxxx reference
250	   when CAP is	completed.

252	   The following is an example of a well-formed but invalid "xdoc"
253	   document type	that includes elements and attribute lists from the
254	   iCalendar and iTIP	namespaces.

256	                   <?xml version="1.0" encoding="UTF-8"?>
257	                   <xdoc>
258	                     <iCal:vcalendar iTIP:method="publish"
259	                             xmlns:iCal="http://www.ietf.org/rfc/RFC2445.txt"
260	                             xmlns:iTIP="http://www.ietf.org/rfc/RFC2446.txt">
261	                     <iCal:vevent>
262	                     <!--- VEVENT elements go here -->
263	                     </iCal:vevent>

265	                     <!-- Remainder of the XML document, each element from the -->
266	                     <!-- iCalendar namespace with the "iCal:" prefix. -->

268	                   </xdoc>

270	   The semantics of the "xmlns" attribute, and any attribute with
271	   "xmlns:" as a 	prefix, is as specified in [XMLNS].  It is used to
272	   declare a namespace in XML.

274	   iCalendar provides for "experimental" elements.  These elements are
275	   represented in iCalendar with element names beginning with "X-".  Any
276	   experimental element in a	document which conforms to this memo MUST
277	   be represented by a namespace different than those used for
278	   iCalendar, iTIP, iMIP, or CAP.  This requirement is intended to
279	   simplify implementation of extensions and experimental items.

281	9.  Emailing documents with iCalendar XML Representation

283	   It is expected that iCalendar XML documents will need to be sent over
284	   SMTP/MIME email.  The "text/xml" and "application/xml" content-types
285	   have been registered for XML documents.

287	   All documents conforming to this memo SHOULD be sent as content-type
288	   "text/xml" or "application/xml".  When iCalendar elements may be
289	   mixed with others, it is not	practical for an MUA to determine,
290	   without opening the document, if iCalendar XML elements exist within
291	   the document.

293	   If a part of a MIME multi-part message contains only XML-represented
294	   iCalendar objects, and it is wished to provide the ability for an
295	   application to determine content based upon the MIME headers, the
296	   content-types "text/xml+calendar" or	"application/xml+calendar" MAY
297	   be used.

299	   Internet applications conforming to this memo MUST include in any
300	   iCalendar XML document that is sent, the XSL stylesheet reference to
301	   be used to provide transformation from the XML representation to the
302	   standard representation.  This	restriction guarantees that a standard
303	   iCalendar object can be produced from the iCalendar XML document.

305	   Internet applications conforming to this memo MAY send the iCalendar
306	   XML document in a "multipart/alternative" MIME entity that also
307	   contains an equivalent iCalendar object in the standard format
308	   defined by [RFC 2445], to provide compatibility with applications
309	   which cannot process XML or XSL transformations.

311	   An XML application comforming to the guidelines in this memo MUST be
312	   able to receive and properly process the "application/xml" document
313	   contained within a	"multipart" message content-type, and MUST be
314	   capable of performing the XSL transformation of the iCalendar
315	   elements of the document into a standard iCalendar document.

317	10.  iCalendar XML Representation and File Systems

319	   The iCalendar XML documents will be stored in file systems.  The
320	   accepted practice for file extensions for XML documents is the text
321	   "XML".  However, IF a document	contains only XML representations of
322	   iCalendar data, then for file association with applications that can
323	   directly process this document type, it is RECOMMENDED	that the file
324	   extension be the text "xcs".

326	11.  Example Usage

328	   The following sections provide various examples of documents using
329	   iCalendar elements in XML.

331	11.1  Example DTD

333	   The following is a DTD which can be used to represent iCalendar [RFC
334	   2445] objects.  While this DTD represents the iCalendar objects as
335	   currently defined, this document does not imply that this is the only
336	   way to represent them, nor that this is the best DTD to do so.  This
337	   is provided as an example, only.

339	   <?xml version="1.0" encoding="UTF-8"?>

341	      <!-- ******************* -->
342	      <!-- Entity declarations -->
343	      <!-- ******************* -->

345	      <!ENTITY % attr.altrep "
346	      altrep ENTITY #IMPLIED
347	      ">

349	      <!ENTITY % attr.cn "
350	      cn CDATA ''
351	      ">

353	      <!ENTITY % attr.cutype "
354	      cutype NMTOKEN 'INDIVIDUAL'
355	      ">
356	      <!-- Valid name tokens are "INDIVIDUAL", "GROUP", "RESOURCE" -->
357	      <!-- "ROOM", "UNKNOWN", a non-standard "X-" name or another -->
358	      <!-- IANA registered name. -->

360	      <!ENTITY % attr.delegated-from "
361	      delegated-from CDATA #IMPLIED
362	      ">
363	      <!-- delegated-from value is a calendar user address -->

365	      <!ENTITY % attr.delegated-to "
366	      delegated-to CDATA #IMPLIED
367	      ">
368	      <!-- delegated-to value is one or more calendar user addresses -->

370	      <!ENTITY % attr.dir "
371	      dir ENTITY #IMPLIED
372	      ">
373	      <!-- dir value is a URI to a directory entry -->
374	      <!ENTITY % attr.fmttype "
375	      fmttype CDATA #REQUIRED
376	      ">
377	      <!-- fmttype value is any IANA registered content type -->

379	      <!ENTITY % attr.fbtype "
380	      fbtype NMTOKEN 'BUSY'
381	      ">

383	      <!-- Valid token values are "FREE", "BUSY", "BUSY-UNAVAILABLE", -->
384	      <!-- "BUSY-TENTATIVE", a non-standard "X-" name or another -->
385	      <!-- IANA registered name. -->

387	      <!ENTITY % attr.language "
388	      language CDATA #IMPLIED
389	      ">
390	      <!-- language value is a valid RFC 1766 language string -->

392	      <!ENTITY % attr.member "
393	      member CDATA #IMPLIED
394	      ">
395	      <!-- member value is one or more calendar user addresses -->

397	      <!ENTITY % attr.partstat "
398	      partstat NMTOKEN 'NEEDS-ACTION'
399	      ">
400	      <!-- Valid token value for VEVENT: "NEEDS-ACTION", "ACCEPTED", -->
401	      <!-- "DECLINED", "TENTATIVE", "DELEGATED", a non-standard "X- -->
402	      <!-- name or another IANA registered name. -->

404	      <!-- Valid token value for VTODO: "NEEDS-ACTION", "ACCEPTED", -->
405	      <!-- "DECLINED", "TENTATIVE", "DELEGATED", "COMPLETED", -->
406	      <!-- "IN-PROGRESS, a non-standard "X- name or another IANA -->
407	      <!-- registered name. -->
408	      <!-- Valid token value for VJOURNAL: "NEEDS-ACTION", "ACCEPTED", -->
409	      <!-- "DECLINED", a non-standard "X- name or another IANA -->
410	      <!-- registered name. -->

412	      <!ENTITY % attr.range "
413	      range NMTOKEN 'THISONLY'
414	      ">
415	      <!-- Valid token values are "THISONLY" or "THISANDPRIOR" or -->
416	      <!-- "THISANDFUTURE" -->

418	      <!ENTITY % attr.related "
419	      related NMTOKEN 'START'
420	      ">
421	      <!-- Valid token values are "START" or "END" -->
422	      <!ENTITY % attr.reltype "
423	      reltype NMTOKEN 'PARENT'
424	      ">
425	      <!-- Valid token values are "PARENT", "CHILD", SIBLING", -->
426	      <!-- a non-standard "X-" name or any IANA registered name. -->

428	      <!ENTITY % attr.role "
429	      role NMTOKEN 'REQ-PARTICIPANT'
430	      ">

432	      <!-- Valid token values are "CHAIR", "REQ-PARTICIPANT", -->
433	      <!-- "OPT-PARTICIPANT", "NON-PARTICIPANT", a non-standard "X-" -->
434	      <!-- name or any IANA registered name. -->

436	      <!ENTITY % attr.rsvp "
437	      rsvp NMTOKEN 'FALSE'
438	      ">
439	      <!-- Valid token values are "TRUE" or "FALSE", -->

441	      <!ENTITY % attr.sent-by "
442	      sent-by CDATA #IMPLIED
443	      ">
444	      <!-- sent-by value is a calendar user address -->

446	      <!ENTITY % attr.tzid "
447	      tzid CDATA #IMPLIED
448	      ">
449	      <!-- tzid value is a time zone identifier -->

451	      <!ENTITY % cal.comp "
452	      vevent | vtodo | vjournal | vfreebusy | vtimezone
453	      ">

455	      <!ENTITY % vevent.opt1 "
456	      class | created | description | dtstamp | dtstart | geo |
457	      last-modified | location | organizer | priority | recurrence-id |
458	      sequence | status | summary | transp | uid | url |
459	      (dtend | duration)
460	      ">
461	      <!-- These properties may only appear once in a VEVENT -->
462	      <!ENTITY % vevent.optm "
463	      attach | attendee | categories | comment | contact |
464	      exdate | exrule | rdate | related-to | resources | request-status |
465	      rrule
466	      ">
467	      <!-- These properties may appear one or more times in a VEVENT -->

469	      <!ENTITY % vtodo.opt1 "
470	      class | completed | created | description | dtstamp | dtstart |
471	      geo | last-modified | location | organizer | percent | priority |
472	      recurrence-id | sequence | status | summary | uid | url |
473	      (due | duration)
474	      ">
475	      <!-- These properties may only appear once in a VTODO -->

477	      <!ENTITY % vtodo.optm "
478	      attach | attendee | categories | comment | contact |
479	      exdate | exrule | request-status | related-to | resources |
480	      rdate | rrule

482	      ">
483	      <!-- These properties may appear one or more times in a VTODO -->

485	      <!ENTITY % vjournal.opt1 "
486	      class | created | description | dtstart | dtstamp | last-modified |
487	      organizer | recurrence-id | sequence | status | summary | uid | url
488	      ">
489	      <!-- These properties may only appear once in a VJOURNAL -->

491	      <!ENTITY % vjournal.optm "
492	      attach | attendee | categories | comment | contact |
493	      exdate | exrule | related-to | rdate | rrule | request-status
494	      ">
495	      <!-- These properties may appear one or more times in a VJOURNAL -->

497	      <!ENTITY % vfreebusy.opt1 "
498	      contact | dtstamp | dtstart | dtend | duration |
499	      organizer | uid | url
500	      ">
501	      <!-- These properties may only appear once in a VFREEBUSY -->

503	      <!ENTITY % vfreebusy.optm "
504	      attendee | comment | freebusy | request-status
505	      ">
506	      <!-- These properties may appear one or more times in a -->
507	      <!-- VFREEBUSY -->

509	      <!ENTITY % vtimezone.man "
510	      tzid
511	      ">
512	      <!-- These properties must appear in a VTIMEZONE -->

514	      <!ENTITY % vtimezone.opt1 "
515	      last-modified | tzurl
516	      ">
517	      <!-- These properties may only appear once in a VTIMEZONE -->
518	      <!ENTITY % vtimezone.mann "
519	      (standard | daylight), (standard | daylight)*
520	      ">
521	      <!-- These properties must appear in a VTIMEZONE and may -->
522	      <!-- appear multiple times -->

524	      <!ENTITY % standard.man "
525	      dtstart | tzoffsetto | tzoffsetfrom
526	      ">
527	      <!-- These properties must appear in a STANDARD, but only once -->

529	      <!ENTITY % standard.optm "

531	      comment | rdate | rrule | tzname
532	      ">
533	      <!-- These properties may appear one or more times in a STANDARD -->

535	      <!ENTITY % daylight.man "
536	      dtstart | tzoffsetto | tzoffsetfrom
537	      ">
538	      <!-- These properties must appear in a DAYLIGHT, but only once -->

540	      <!ENTITY % daylight.optm "
541	      comment | rdate | rrule | tzname
542	      ">
543	      <!-- These properties may appear one or more times in a DAYLIGHT -->

545	      <!ENTITY % audio.man "
546	      action, trigger
547	      ">
548	      <!-- These properties must appear in an audio VALARM. -->

550	      <!ENTITY % audio.optx "
551	      duration | repeat
552	      ">
553	      <!-- These properties may appear once in an audio VALARM. If one -->
554	      <!-- appears, then both must appear. -->

556	      <!ENTITY % audio.opt1 "
557	      attach
558	      ">
559	      <!-- These properties may appear once in an audio VALARM. -->

561	      <!ENTITY % valarm.audio "
562	      (%audio.man;), (%audio.optx;)*, (%audio.opt1;)
563	      ">

565	      <!ENTITY % display.man "
566	      action, description, trigger
567	      ">
568	      <!-- These properties must appear in a display VALARM. -->
569	      <!ENTITY % display.optx "
570	      duration | repeat
571	      ">
572	      <!-- These properties may appear once in a display VALARM. If -->
573	      <!-- one appears, then both must appear. -->

575	      <!ENTITY % valarm.display "
576	      (%display.man;), (%display.optx;)*
577	      ">

579	      <!ENTITY % email.man "

581	      action, description, summary, trigger
582	      ">
583	      <!-- These properties must appear in an email VALARM. -->

585	      <!ENTITY % email.optx "
586	      duration | repeat
587	      ">
588	      <!-- These properties may appear once in an email VALARM. If one -->
589	      <!-- appears, then both must appear. -->

591	      <!ENTITY % email.optm "
592	      attach
593	      ">
594	      <!-- These properties may appear one or more times in an email -->
595	      <!-- VALARM. -->

597	      <!ENTITY % email.mann "
598	      attendee
599	      ">
600	      <!-- These properties must appear in an email VALARM. The may -->
601	      <!-- appear more than once. -->

603	      <!ENTITY % valarm.email "
604	      (%email.man;), (%email.optx;)*, (%email.optm;)*,
605	      (%email.mann;)*
606	      ">

608	      <!ENTITY % procedure.man "
609	      action, attach, trigger
610	      ">
611	      <!-- These properties must appear in an audio VALARM. -->

613	      <!ENTITY % procedure.optx "
614	      duration | repeat
615	      ">
616	      <!-- These properties may appear once in an procedure VALARM. -->
617	      <!-- If one appears, then both must appear. -->

619	      <!ENTITY % procedure.opt1 "
620	      description
621	      ">
622	      <!-- These properties may appear once in a procedure VALARM -->
623	      <!ENTITY % valarm.procedure "
624	      (%procedure.man;), (%procedure.optx;)*, (%procedure.opt1;)?
625	      ">

627	      <!-- ******************************************** -->
628	      <!-- iCalendar value type notation declarations   -->
629	      <!-- ******************************************** -->

631	      <!-- NOTE: The "XCAL" text in the following NOTATION values
632	      will be replaced with the text "RFC xxxx", where "xxxx" is the RFC
633	      number, when this memo is published as a RFC. -->

635	      <!NOTATION BINARY PUBLIC "-//IETF//NOTATION XCAL/Value Type/Binary//EN">

637	      <!NOTATION BOOLEAN PUBLIC "-//IETF//NOTATION XCAL/Value Type/Boolean//EN">

639	      <!NOTATION CALADR PUBLIC "-//IETF//NOTATION XCAL/Value Type/Calendar
640	      User Address//EN">

642	      <!NOTATION DATE PUBLIC "-//IETF//NOTATION XCAL/Value Type/Date//EN">

644	      <!NOTATION DATE-TIME PUBLIC "-//IETF//NOTATION XCAL/Value
645	      Type/Date-Time//EN">

647	      <!NOTATION DURATION PUBLIC "-//IETF//NOTATION XCAL/Value
648	      Type/Duration//EN">

650	      <!NOTATION FLOAT PUBLIC "-//IETF//NOTATION XCAL/Value Type/Float//EN">

652	      <!NOTATION INTEGER PUBLIC "-//IETF//NOTATION XCAL/Value Type/Integer//EN">

654	      <!NOTATION PERIOD PUBLIC "-//IETF//NOTATION XCAL/Value
655	      Type/Period of Time//EN">

657	      <!NOTATION RECUR PUBLIC "-//IETF//NOTATION XCAL/Value
658	      Type/Recurrence Rule//EN">

660	      <!NOTATION TEXT PUBLIC "-//IETF//NOTATION XCAL/Value Type/Text//EN">
661	      <!NOTATION TIME PUBLIC "-//IETF//NOTATION XCAL/Value Type/Time//EN">

663	      <!NOTATION URI PUBLIC "-//IETF//NOTATION XCAL/Value Type/URI//EN">

665	      <!NOTATION UTC-OFFSET PUBLIC "-//IETF//NOTATION XCAL/Value
666	      Type/UTC-Offset//EN">

668	      <!NOTATION X-NAME PUBLIC "-//IETF//NOTATION XCAL/Value Type/X-Name//EN">

670	      <!-- ************************************************* -->
671	      <!-- iCalendar property element/attribute declarations -->
672	      <!-- ************************************************* -->

674	      <!ELEMENT br EMPTY>
675	      <!-- Signifies a new line in the TEXT value content information -->

677	      <!-- Description component properties element type declarations -->

679	      <!ELEMENT attach (extref | b64bin)>
680	      <!-- extref holds a reference to an external entity that -->
681	      <!-- has the attachment. b64bin holds the inline BASE64 encoded -->
682	      <!-- binary data for the attachment as defined in RFC 2045. -->

684	      <!ELEMENT extref EMPTY>
685	      <!ATTLIST extref
686	      uri ENTITY #REQUIRED>

688	      <!ELEMENT b64bin (#PCDATA)>
689	      <!ATTLIST b64bin
690	      %attr.fmttype;
691	      value NOTATION (BINARY) #IMPLIED>

693	      <!ELEMENT categories (item)*>

695	      <!ELEMENT item (#PCDATA)>
696	      <!ATTLIST item
697	      %attr.language;
698	      value NOTATION (TEXT) #IMPLIED>

700	      <!ELEMENT class (#PCDATA)>
701	      <!ATTLIST class
702	      %attr.language;
703	      value NOTATION (TEXT) #IMPLIED>

705	      <!ELEMENT comment (#PCDATA)*>
706	      <!ATTLIST comment
707	      %attr.language;
708	      %attr.altrep;
709	      value NOTATION (TEXT) #IMPLIED>

711	      <!ELEMENT description (#PCDATA)*>
712	      <!ATTLIST description
713	      %attr.language;
714	      %attr.altrep;
715	      value NOTATION (TEXT) #IMPLIED>

717	      <!ELEMENT geo (lat, lon)>

719	      <!ELEMENT lat (#PCDATA)>
720	      <!ATTLIST lat value NOTATION (FLOAT) #IMPLIED>
721	      <!-- A decimal degree float number to 6 decimal places -->

723	      <!ELEMENT lon (#PCDATA)>
724	      <!ATTLIST lon value NOTATION (FLOAT) #IMPLIED>
725	      <!-- A decimal degree float number to 6 decimal places -->

727	      <!ELEMENT location (#PCDATA)>
728	      <!ATTLIST location
729	      %attr.language;
730	      %attr.altrep;
731	      value NOTATION (TEXT) #IMPLIED>

733	      <!ELEMENT percent (#PCDATA)>
734	      <!ATTLIST percent
735	      value NOTATION (INTEGER) #IMPLIED>

737	      <!ELEMENT priority (#PCDATA)>
738	      <!ATTLIST priority
739	      value NOTATION (INTEGER) #IMPLIED>

741	      <!ELEMENT resources (#PCDATA)>
742	      <!ATTLIST resources
743	      %attr.language;
744	      %attr.altrep;
745	      value NOTATION (TEXT) #IMPLIED>

747	      <!ELEMENT status (#PCDATA)>
748	      <!ATTLIST status
749	      %attr.language;
750	      %attr.altrep;
751	      value NOTATION (TEXT) #IMPLIED>
752	      <!-- Text value must match the valid values for the particular -->
753	      <!-- calendar component. -->

755	      <!ELEMENT summary (#PCDATA)>
756	      <!ATTLIST summary
757	      %attr.language;
758	      %attr.altrep;
759	      value NOTATION (TEXT) #IMPLIED >

761	      <!-- Data and time component property element type declarations -->

763	      <!ELEMENT dtstart (#PCDATA)>
764	      <!ATTLIST dtstart
765	      %attr.tzid;
766	      value NOTATION (DATE-TIME | DATE) "DATE-TIME">

768	      <!ELEMENT dtend (#PCDATA)>
769	      <!ATTLIST dtend
770	      %attr.tzid;
771	      value NOTATION (DATE-TIME | DATE) "DATE-TIME">

773	      <!ELEMENT due (#PCDATA)>
774	      <!ATTLIST due
775	      %attr.tzid;
776	      value NOTATION (DATE-TIME | DATE) "DATE-TIME">

778	      <!ELEMENT completed (#PCDATA)>
779	      <!ATTLIST completed
780	      value NOTATION (DATE-TIME) #IMPLIED>

782	      <!ELEMENT duration (#PCDATA)>
783	      <!ATTLIST duration
784	      value NOTATION (DURATION) #IMPLIED>

786	      <!ELEMENT freebusy (#PCDATA)>
787	      <!ATTLIST freebusy
788	      %attr.fbtype;
789	      value NOTATION (PERIOD) #IMPLIED>

791	      <!ELEMENT transp (#PCDATA)>
792	      <!ATTLIST transp
793	      value NOTATION (TEXT) #IMPLIED>
794	      <!-- Text value must be one of the valid enumerations. -->

796	      <!-- Time zone component property element type declarations -->

798	      <!ELEMENT tzid (#PCDATA)>
799	      <!ATTLIST tzid
800	      value NOTATION (TEXT) #IMPLIED>

802	      <!ELEMENT tzname (#PCDATA)>
803	      <!ATTLIST tzname
804	      %attr.language;
805	      value NOTATION (TEXT) #IMPLIED>

807	      <!ELEMENT tzoffsetfrom (#PCDATA)>
808	      <!ATTLIST tzoffsetfrom
809	      value NOTATION (UTC-OFFSET) #IMPLIED>

811	      <!ELEMENT tzoffsetto (#PCDATA)>
812	      <!ATTLIST tzoffsetto
813	      value NOTATION (UTC-OFFSET) #IMPLIED>

815	      <!ELEMENT tzurl EMPTY>
816	      <!ATTLIST tzurl
817	      uri ENTITY #REQUIRED>

819	      <!-- Relationship component property element type declarations -->

821	      <!ELEMENT attendee (#PCDATA)>
822	      <!ATTLIST attendee
823	      %attr.language;
824	      %attr.cn;
825	      %attr.role;
826	      %attr.partstat;
827	      %attr.rsvp;
828	      %attr.cutype;
829	      %attr.member;
830	      %attr.delegated-to;
831	      %attr.delegated-from;
832	      %attr.sent-by;
833	      %attr.dir;
834	      value NOTATION (CALADR) #IMPLIED>

836	      <!ELEMENT contact (#PCDATA)*>
837	      <!ATTLIST contact
838	      %attr.language;
839	      %attr.altrep;
840	      value NOTATION (TEXT) #IMPLIED>

842	      <!ELEMENT organizer (#PCDATA)>
843	      <!ATTLIST organizer
844	      %attr.language;
845	      %attr.cn;
846	      %attr.sent-by;
847	      %attr.dir;
848	      value NOTATION (CALADR) #IMPLIED>

850	      <!ELEMENT recurrence-id (#PCDATA)>
851	      <!ATTLIST recurrence-id
852	      %attr.tzid;
853	      %attr.range;
854	      value NOTATION (DATE-TIME | DATE) "DATE-TIME">

856	      <!ELEMENT related-to (#PCDATA)>
857	      <!ATTLIST related-to
858	      %attr.reltype;
859	      value NOTATION (TEXT) #IMPLIED>

861	      <!ELEMENT url EMPTY>
862	      <!ATTLIST url
863	      uri ENTITY #REQUIRED>

865	      <!ELEMENT uid (#PCDATA)>
866	      <!ATTLIST uid
867	      value NOTATION (TEXT) #IMPLIED>

869	      <!-- Recurrence component property element type declarations -->

871	      <!ELEMENT exdate (#PCDATA)>
872	      <!ATTLIST exdate
873	      %attr.tzid;
874	      value NOTATION (DATE-TIME | DATE) "DATE-TIME">

876	      <!ELEMENT exrule (#PCDATA)>
877	      <!ATTLIST exrule
878	      value NOTATION (RECUR) #IMPLIED>

880	      <!ELEMENT rdate (#PCDATA)>
881	      <!ATTLIST rdate
882	      %attr.tzid;
883	      value NOTATION (DATE-TIME | DATE) "DATE-TIME">

885	      <!ELEMENT rrule (#PCDATA)>
886	      <!ATTLIST rrule
887	      value NOTATION (RECUR) #IMPLIED>

889	      <!-- Alarm component property element type declarations -->

891	      <!ELEMENT action (#PCDATA)>
892	      <!ATTLIST action
893	      value NOTATION (TEXT) #IMPLIED>
894	      <!-- Text value must be a valid enumeration -->

896	      <!ELEMENT repeat (#PCDATA)>
897	      <!ATTLIST repeat
898	      value NOTATION (INTEGER) #IMPLIED>

900	      <!ELEMENT trigger (#PCDATA)>
901	      <!ATTLIST trigger
902	      %attr.related-to;
903	      value NOTATION (DURATION | DATE-TIME) "DURATION">

905	      <!-- Change management component property element type -->
906	      <!-- declarations -->

908	      <!ELEMENT created (#PCDATA)>
909	      <!ATTLIST created
910	      value NOTATION (DATE-TIME) #IMPLIED>

912	      <!ELEMENT dtstamp (#PCDATA)>
913	      <!ATTLIST dtstamp
914	      value NOTATION (DATE-TIME) #IMPLIED>

916	      <!ELEMENT last-modified (#PCDATA)>
917	      <!ATTLIST last-modified
918	      value NOTATION (DATE-TIME) #IMPLIED>

920	      <!ELEMENT sequence (#PCDATA)>
921	      <!ATTLIST sequence
922	      value NOTATION (INTEGER) #IMPLIED>

924	      <!-- Miscellaneous component property element type declarations -->

926	      <!ELEMENT request-status (#PCDATA)>
927	      <!ATTLIST request-status
928	      %attr.language;
929	      value NOTATION (TEXT) #IMPLIED>

931	      <!-- iCalendar object element type declarations -->

933	      <!ELEMENT iCalendar (vcalendar+)>

935	      <!ELEMENT vcalendar (%cal.comp;)*>
936	      <!ATTLIST vcalendar
937	      %attr.language;
938	      xmlns CDATA #FIXED 'http://www.ietf.org/internet-drafts/draft-
939	      hare-xcalendar-01.txt'
940	      calscale CDATA "GREGORIAN"
941	      method CDATA "PUBLISH"
942	      version CDATA #REQUIRED
943	      prodid CDATA #IMPLIED>
944	      <!-- version - Must be "2.0" if document conforms to this spec. -->
945	      <!-- calscale - Calendar scale. Default is GREGORIAN. -->
946	      <!-- method - C&S method. Default is iTIP PUBLISH. -->
947	      <!-- prodid - ISO 9070 FPI for product that generated iCalendar. -->
948	      <!-- "vevent" element type declaration -->
949	      <!ELEMENT vevent ((%vevent.opt1;)*, (%vevent.optm;)*, valarm*)>

951	      <!-- "vtodo" element type declaration -->
952	      <!ELEMENT vtodo ((%vtodo.opt1;)*, (%vtodo.optm;)*, valarm*)>

954	      <!-- "vjournal" element type declaration -->
955	      <!ELEMENT vjournal ((%vjournal.opt1;)*, (%vjournal.optm;)*)>

957	      <!-- "vfreebusy" element type declaration -->
958	      <!ELEMENT vfreebusy ((%vfreebusy.opt1;)*, (%vfreebusy.optm;)*)>

960	      <!-- "vtimezone" element type declaration -->
961	      <!ELEMENT vtimezone (%vtimezone.man;, (%vtimezone.opt1;)*,
962	      (%vtimezone.mann;)*)>

964	      <!ELEMENT standard (((%standard.man;)*), (%standard.optm;)*)>

966	      <!ELEMENT daylight (((%daylight.man;)*), (%daylight.optm;)*)>

968	      <!ELEMENT valarm ((%valarm.audio;) | (%valarm.display;) |
969	      (%valarm.email;) | (%valarm.procedure;))>

971	11.2  An example XSL transformation

973	   The following is an example of an XSL transformation which can
974	   convert an xCalendar document into an iCalendar [RFC 2445] text
975	   object.  Again, this is an 	example and not presented as the only or
976	   best way to accomplish the 	transformation.

978	   <?xml version="1.0" encoding="UTF-8"?>
979	   <xsl:stylesheet version="1.0"
980	           xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
981	           xmlns:ical="http://www.ietf.org/rfc/rfc2445.txt"
982	           xmlns:itip="http://www.ietf.org/rfc/rfc2446.txt"
983	           xmlns="http://www.ietf.org/rfc/rcf2445.txt">
984	   <!-- ======================================================================== -->
985	   <!-- xcal2ics.xsl XSL transformation of xCalendar documents to iCalendar file -->
986	   <!-- Tim Hare, April 2004                                                     -->
987	   <!-- Tim Hare, August 2004 -  updated to wrap at 75 chars                     -->
988	   <!-- Tim Hare, November 2004 - removed unused template, cleanup               -->
989	   <!-- Tim Hare, May 2005 - added function to quote some characters             -->
990	   <!-- This transformation may be freely used, attribution is appreciated       -->
991	   <!-- Concepts and inspiration due to rdf2ical from Masahide Kanzaki           -->
992	   <!-- who should also receive attribution                                      -->
993	   <!-- ======================================================================== -->
994	   <!-- define output format for iCalendar for use in result-document instr.     -->
995	   <xsl:output method="text" media-type="text/calendar" />
996	   <xsl:template match="icalendar|iCalendar|ical:icalendar|ical:iCalendar">
997	           <xsl:apply-templates select="vcalendar|ical:vcalendar" />
998	   </xsl:template>
999	   <xsl:template match="vcalendar|ical:vcalendar">
1000	                   <xsl:call-template name="emit_text">
1001	                   <!-- parameter "line" is entire result of here to end of with-param -->
1002	                   <xsl:with-param name="line">
1003	                           <xsl:text>BEGIN:VCALENDAR</xsl:text>
1004	                   </xsl:with-param>
1005	                   </xsl:call-template>
1006	                           <xsl:if test="not(@method) and
1007	                                   not(@Method) and
1008	                                     not(@ical:method) and
1009	                                             not(@ical:Method)">
1010	                                   <xsl:call-template name="emit_text">
1011	                                   <xsl:with-param name="line">
1012	                                           <xsl:text>METHOD:PUBLISH</xsl:text>
1013	                                   </xsl:with-param>
1014	                                   </xsl:call-template>
1015	                           </xsl:if>
1016	                           <xsl:for-each select="@*">
1017	                                   <xsl:call-template name="emit_text">
1018	                                   <xsl:with-param name="line">
1019	                                           <xsl:call-template name="stringcap">
1020	                                           <xsl:with-param name="s" select="local-name()" />
1021	                                           </xsl:call-template>
1022	                                           <xsl:text>:</xsl:text>
1023	                                           <xsl:call-template name="stringcap">
1024	                                           <xsl:with-param name="s" select="current()" />
1025	                                           </xsl:call-template>
1026	                                   </xsl:with-param>
1027	                                   </xsl:call-template>
1028	                           </xsl:for-each>
1029	                   <xsl:apply-templates select="./*" />
1030	                   <xsl:call-template name="emit_text">
1031	                   <xsl:with-param name="line">
1032	                           <xsl:text>END:VCALENDAR</xsl:text>
1033	                   </xsl:with-param>
1034	                   </xsl:call-template>
1035	   </xsl:template>
1036	   <xsl:template name="eachcomponent"      match="vevent|vtodo|vjournal|valarm|ical:vevent|ical:vtodo|ical:vjournal|ical:valarm">
1037	           <xsl:call-template name="emit_text">
1038	           <xsl:with-param name="line">
1039	                   <xsl:text>BEGIN:</xsl:text>
1040	                   <xsl:call-template name="stringcap">
1041	                   <xsl:with-param name="s" select="local-name()" />
1042	                   </xsl:call-template>
1043	           </xsl:with-param>
1044	           </xsl:call-template>
1045	                   <xsl:for-each select="./*" >
1046	                                   <xsl:call-template name="eachproperty" />
1047	                   </xsl:for-each>
1048	                   <xsl:call-template name="emit_text">
1049	                   <xsl:with-param name="line">
1050	                           <xsl:text>END:</xsl:text>
1051	                           <xsl:call-template name="stringcap">
1052	                           <xsl:with-param name="s" select="local-name()" />
1053	                           </xsl:call-template>
1054	                   </xsl:with-param>
1055	                   </xsl:call-template>
1056	   </xsl:template>
1057	   <xsl:template name="eachproperty">
1058	           <xsl:if test="local-name() != 'categories' and
1059	                             local-name() != 'CATEGORIES' and
1060	                             local-name() != 'geo' and
1061	                             local-name() != 'GEO' and
1062	                             local-name() != 'resources' and
1063	                             local-name() != 'RESOURCES'">
1064	           <!-- this block outputs a property with all of its parameters -->
1065	                   <xsl:call-template name="emit_text">
1066	                   <xsl:with-param name="line">
1067	                           <xsl:call-template name="stringcap">
1068	                           <xsl:with-param name="s" select="local-name()" />
1069	                           </xsl:call-template>
1070	                           <xsl:for-each select="@*">
1071	                                   <xsl:call-template name="eachparam">
1072	                                   <xsl:with-param name="p" select="local-name()" />
1073	                                   </xsl:call-template>
1074	                           </xsl:for-each>
1075	                           <xsl:text>:</xsl:text>
1076	                           <!-- call replace-text to quote newline, semicolon, colon, reverse solidus, and comma -->
1077	                           <xsl:call-template name="quote-some">
1078	                           <xsl:with-param name="text"><xsl:value-of select="." /></xsl:with-param>
1079	                     </xsl:call-template>
1080	                   </xsl:with-param>
1081	                   </xsl:call-template>
1082	           <!-- end of regular properties ouput block                     -->
1083	           </xsl:if>
1084	           <xsl:if test="local-name() = 'categories' or
1085	                             local-name() = 'CATEGORIES' or
1086	                             local-name() = 'resources' or
1087	                             local-name() = 'RESOURCES'">
1088	           <!-- this block outputs a Categories or Resources property     -->
1089	                   <xsl:call-template name="emit_text">
1090	                   <xsl:with-param name="line">
1091	                           <xsl:call-template name="stringcap">
1092	                                   <xsl:with-param name="s" select="local-name()" />
1093	                           </xsl:call-template>
1094	                           <xsl:for-each select="@*">
1095	                                   <xsl:call-template name="eachparam">
1096	                                   <xsl:with-param name="p" select="local-name()" />
1097	                                   </xsl:call-template>
1098	                           </xsl:for-each>
1099	                           <xsl:text>:</xsl:text>
1100	                           <xsl:for-each select="./item|./ITEM">
1101	                                   <xsl:call-template name="stringcap">
1102	                                   <xsl:with-param name="s" select="current()" />
1103	                                   </xsl:call-template>
1104	                                   <xsl:if test="position() != last()">
1105	                                           <xsl:text>,</xsl:text>
1106	                                   </xsl:if>
1107	                           </xsl:for-each>
1108	                   </xsl:with-param>
1109	                   </xsl:call-template>
1110	           <!-- end of Categories or Resources property output block       -->
1111	           </xsl:if>
1112	           <xsl:if test="local-name() = 'geo' or
1113	                             local-name() = 'GEO'">
1114	           <!-- this block outputs a Geo property                          -->
1115	                   <xsl:call-template name="emit_text">
1116	                   <xsl:with-param name="line">
1117	                           <xsl:call-template name="stringcap">
1118	                           <xsl:with-param name="s" select="local-name()" />
1119	                           </xsl:call-template>
1120	                           <xsl:text>:</xsl:text>
1121	                           <xsl:value-of select="lat" />
1122	                           <xsl:text>;</xsl:text>
1123	                           <xsl:value-of select="lon" />
1124	                   </xsl:with-param>
1125	                   </xsl:call-template>
1126	           <!-- end of Geo property output block                            -->
1127	           </xsl:if>
1128	   </xsl:template>
1129	   <xsl:template name="eachparam">
1130	           <xsl:param name="p" />
1131	           <xsl:text>;</xsl:text>
1132	           <xsl:call-template name="stringcap">
1133	                   <xsl:with-param name="s" select="string($p)"/>
1134	           </xsl:call-template>
1135	           <xsl:text>=</xsl:text>
1136	           <xsl:value-of select="." />

1138	   </xsl:template>
1139	   <!-- Capitalize and output a string -->
1140	   <xsl:template name="stringcap">
1141	   <xsl:param name="s"/>
1142	   <xsl:value-of select="translate($s,'abcdefghijklmnopqrstuvwxyz','ABCDEFGHIJKLMNOPQRSTUVWXYZ')"/>
1143	   </xsl:template>
1144	   <!-- Emit text, 75 character max per line, recursively -->
1145	   <xsl:template name="emit_text">
1146	           <xsl:param name="limit" select="number(75)"/> <!-- default limit is 75 " -->
1147	           <xsl:param name="line"/>
1148	           <xsl:value-of select="substring(normalize-space($line),1,$limit)" />
1149	           <!-- Output the newline string -->
1150	           <xsl:text>&#13;&#10;</xsl:text>
1151	           <xsl:if test="string-length($line) > $limit">
1152	                   <xsl:text> </xsl:text>
1153	                   <xsl:call-template name="emit_text">
1154	                           <xsl:with-param name="limit" select="($limit - 1)" /> <!-- use 74 allow for space -->
1155	                           <xsl:with-param name="line" select="substring($line,($limit + 1))" />
1156	                   </xsl:call-template>
1157	           </xsl:if>
1158	   </xsl:template>
1159	   <!-- ACK: ASPN replace-string function used to model this
1160	     http://aspn.activestate.com/ASPN/Cookbook/XSLT/Recipe/65426
1161	     via Dan Connolly, W3C

1163	     all characters to be quoted are in this template rather than doing multiple calls to the template
1164	     in the hopes that this will improve performance.
1165	     -->
1166	   <xsl:template name="quote-some">
1167	       <!-- rfc2445#sec4.3.11 says to quote DQUOTE, newline, semicolon, colon,
1168	                              reverse solidus, comma -->
1169	       <xsl:param name="text">
1170	       <xsl:choose>
1171	         <xsl:when test="contains($text,'&quot')">
1172	           <xsl:variable name="before" select="substring-before($text,'&quot')
1173	           <xsl:variable name="before" select="substring-after($text,'&quot')/>
1174	           <xsl:value-of select="$before"/>
1175	           <xsl:value-of select="\&quot" />
1176	           <xsl:call-template name="quote-some">
1177	           <xsl:with-param name="text" select="&after" />
1178	           </xsl:call-template>
1179	         </xsl:when>
1180	         <xsl:when test="contains($text,'&#10')">
1181	           <xsl:variable name="before" select="substring-before($text,'&#10')
1182	           <xsl:variable name="before" select="substring-after($text,'&#10')/>
1183	           <xsl:value-of select="$before"/>
1184	           <xsl:value-of select="\n" />
1185	           <xsl:call-template name="quote-some">
1186	           <xsl:with-param name="text" select="&after" />
1187	           </xsl:call-template>
1188	         </xsl:when>
1189	         <xsl:when test="contains($text,';')">
1190	           <xsl:variable name="before" select="substring-before($text,';')/>
1191	           <xsl:variable name="before" select="substring-after($text,';')/>
1192	           <xsl:value-of select="$before"/>
1193	           <xsl:value-of select="\;" />
1194	           <xsl:call-template name="quote-some">
1195	           <xsl:with-param name="text" select="&after" />
1196	           </xsl:call-template>
1197	          </xsl:when>
1198	         <xsl:when test="contains($text,':')">
1199	           <xsl:variable name="before" select="substring-before($text,':')/>
1200	           <xsl:variable name="before" select="substring-after($text,':')/>
1201	           <xsl:value-of select="$before"/>
1202	           <xsl:value-of select="\:" />
1203	           <xsl:call-template name="quote-some">
1204	           <xsl:with-param name="text" select="&after" />
1205	           </xsl:call-template>
1206	          </xsl:when>
1207	         <xsl:when test="contains($text,'\')">
1208	           <xsl:variable name="before" select="substring-before($text,'\')/>
1209	           <xsl:variable name="before" select="substring-after($text,'\')/>
1210	           <xsl:value-of select="$before"/>
1211	           <xsl:value-of select="\\" />
1212	           <xsl:call-template name="quote-some">
1213	           <xsl:with-param name="text" select="&after" />
1214	           </xsl:call-template>
1215	          </xsl:when>
1216	         <xsl:when test="contains($text,',')">
1217	           <xsl:variable name="before" select="substring-before($text,',')/>
1218	           <xsl:variable name="before" select="substring-after($text,',')/>
1219	           <xsl:value-of select="$before"/>
1220	           <xsl:value-of select="\," />
1221	           <xsl:call-template name="quote-some">
1222	           <xsl:with-param name="text" select="&after" />
1223	           </xsl:call-template>
1224	          </xsl:when>
1225	       <xsl:otherwise>
1226	           <xsl:value-of select="$text"/>
1227	       </xsl:otherwise>
1228	       </xsl:choose>
1229	    </xsl:template>
1230	   </xsl:stylesheet>

1232	11.3  A well-formed and valid iCalendar XML document

1234	   The following is a simple example of a iCalendar XML document.  This
1235	   document is both a well-formed and valid XML document.  It also
1236	   contains the required reference to the XSL transformation.  The
1237	   iCalendar object specifies an appointment.

1239	         <?xml version="1.0" encoding="UTF-8"?>
1240	         <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
1241	         "http://www.ietf.org/internet-drafts/draft-hare-xcalendar-01.txt">
1242	         <?xml-stylesheet href="xcal2ics.xsl" type="text/xsl" output="text" ?>
1243	         <iCalendar>
1244	         <vcalendar method="PUBLISH"
1245	               version="2.0"
1246	               prodid="-//HandGen//NONSGML vGen v1.0//EN">
1247	         <vevent>
1248	              <uid>19981116T150000@cal10.host.com</uid>
1249	              <dtstamp>19981116T145958Z</dtstamp>
1250	              <summary>Project XYZ Review</summary>
1251	              <location>Conference Room 23A</location>
1252	              <dtstart>19981116T163000Z</dtstart>
1253	              <dtend>19981116T190000Z</dtend>
1254	              <categories>
1255	                   <item>Appointment</item>
1256	              </categories>
1257	         </vevent>
1258	         </vcalendar>
1259	         </iCalendar>

1261	11.4  Including binary content in attachments

1263	   The following is an example of a valid iCalendar XML document that
1264	   also	includes an external reference to an attachment.  The iCalendar
1265	   object specifies	a meeting invitation with an attachment.

1267	      <?xml version="1.0" encoding="UTF-8"?>
1268	      <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
1269	      "http://www.ietf.org/internet-drafts/draft-hare-xcalendar-01.txt"
1270	      <?xml-stylesheet href="xcal2ics.xsl" type="text/xsl" output="text" ?>

1272	      <iCalendar>
1273	       <vcalendar>
1274	        <method>REQUEST</method>
1275	        <version>2.0</version>
1276	        <prodid>-//HandGen//NONSGML vGen v1.0//EN</prodid>
1277	        <vevent>
1278	         <uid>19981211T133000@cal1.host.com</uid>
1279	         <dtstamp>19981211T132928Z</dtstamp>
1280	         <organizer>cap://host.com/jim</organizer>
1281	         <dtstart>19981212T150000Z</dtstart>
1282	         <dtend>19981212T160000Z</dtend>
1283	         <summary>Department Meeting</summary>
1284	         <location>Conference Room 23A</location>
1285	         <attendee role="CHAIR">jim@host.com</attendee>
1286	         <attendee role="REQ-PART"
1287	                   rsvp="TRUE">MAILTO:joe@host.com</attendee>
1288	         <attendee role="REQ-PART"
1289	                   rsvp="TRUE">MAILTO:steve@host.com</attendee>
1290	         <attach>http://host.com/pub/photos/holiday.jpg</attach>
1291	        </vevent>
1292	       </vcalendar>
1293	      </iCalendar>

1295	11.5  Including binary content inline

1297	   The following is an example of a well-formed and valid iCalendar XML
1298	   document that includes an attachment as inline binary content.  The
1299	   iCalendar	object specifies a meeting invitation with an attachment.

1301	      <?xml version="1.0" encoding="UTF-8"?>
1302	      <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
1303	      "http://www.ietf.org/internet-drafts/draft-hare-xcalendar-01.txt">
1304	      <?xml-stylesheet href="xcal2ics.xsl" type="text/xsl" output="text" ?>
1305	      <iCalendar>
1306	      <vcalendar>
1307	       <method>REQUEST</method>
1308	       <version>2.0</version>
1309	       <prodid>-//HandGen//NONSGML vGen v1.0//EN</prodid>
1310	       <vevent>
1311	        <uid>19981211T133000@cal1.host.com</uid>
1312	        <dtstamp>19981211T132928Z</dtstamp>
1313	        <organizer>MAILTO:jim@host.com</organizer>
1314	        <dtstart>19981212T150000Z</dtstart>
1315	        <dtend>19981212T160000Z</dtend>
1316	        <summary>Department Meeting</summary>
1317	        <location>Conference Room 23A</location>
1318	        <attendee role="CHAIR">MAILTO:jim@host.com</attendee>
1319	        <attendee role="REQ-PART"
1320	                  rsvp="TRUE">MAILTO:joe@host.com</attendee>
1321	        <attendee role="REQ-PART"
1322	                  rsvp="TRUE">MAILTO:steve@host.com</attendee>
1323	        <attach fmttype="IMAGE/JPEG">MIICajCCAdOgAwIBAgI
1324	        CBEUwDQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXB
1325	        lIEjYXRpb25z...and so on...IENvcnBvc==</attach>
1326	       </vevent>
1327	       </vcalendar>
1328	      </iCalendar>

1330	11.6  iCalendar XML document with multiple iCalendar objects

1332	   The following is an example of a well-formed and valid iCalendar XML
1333	   document that includes more than one iCalendar object.

1335	      <?xml version="1.0" encoding="UTF-8"?>
1336	      <!DOCTYPE iCalendar PUBLIC "-//IETF//DTD XCAL/iCalendar XML//EN"
1337	      "http://www.ietf.org/internet-drafts/draft-hare-xcalendar-01.txt">
1338	      <?xml-stylesheet href="xcal2ics.xsl" type="text/xsl" output="text" ?>
1339	      <iCalendar annotation="IT Conference Prep">
1340	      <vcalendar>
1341	       <method>PUBLISH</method>
1342	       <version>2.0</version>
1343	       <prodid>-//HandGen//NONSGML vGen v1.0//EN</prodid>
1344	       <vtodo>
1345	        <uid>19981009T233000@cal1.host.com</uid>
1346	        <dtstamp>19981009T232928Z</dtstamp>
1347	        <dtstart>19981010T000000Z</dtstart>
1348	        <due>19981010T235959Z</due>
1349	        <summary>Register for conference</summary>
1350	        <priority>2</priority>
1351	       </vtodo>
1352	      </vcalendar>
1353	      <vcalendar>
1354	       <version>2.0</version>
1355	       <prodid>-//HandGen//NONSGML vGen v1.0//EN</prodid>
1356	       <method>PUBLISH</method>
1357	       <vevent>
1358	        <uid>19981009T233010@cal1.host.com</uid>
1359	        <dtstamp>19981009T233000Z</dtstamp>
1360	        <dtstart>19981120T133000Z</dtstart>
1361	        <dtend>19981122T183000Z</dtend>
1362	        <summary>IT Conference</summary>
1363	        <location>Downtowner Hotel</location>
1364	       </vevent>
1365	      </vcalendar>
1366	      </iCalendar>

1368	11.7  Using the iCalendar namespace

1370	   The following is an example of a snippet of a XML document that
1371	   includes elements from the iCalendar name-space.

1373	      <x xmlns:xcal="http://www.ietf.org/internet-drafts/
1374	      draft-hare-xcalendar-01.txt"
1375	      xmlns:pdi="http://pdi.org/schema">
1376	      <xcal:dtstart>19981123T133000Z</xcal:dtstart>
1377	      <xcal:dtend>19981123T203000Z</xcal:dtend>
1378	      <pdi:idnum>1234567</pdi:idnum>
1379	      <pdi:usage>999.99</pdi:usage>
1380	      </x>

1382	11.8  Publish meeting information

1384	   The following is a snippet of an iCalendar XML document that
1385	   publishes information about a meeting.

1387	      <iCalendar>
1388	       <vcalendar>
1389	        <version>2.0</version>
1390	        <prodid>-//hacksw/handcal//NONSGML 1.0//EN</prodid>
1391	        <method>PUBLISH</method>
1392	        <vevent>
1393	         <uid>19970901T130000Z-123401@host.com</uid>
1394	         <dtstamp>19970901T130000Z</dtstamp>
1395	         <dtstart>19970903T163000Z</dtstart>
1396	         <dtend>19970903T190000Z</dtend>
1397	         <summary>Annual Employee Review</summary>
1398	         <class>PRIVATE</class>
1399	         <categories>Business,Human Resources</categories>
1400	        </vevent>
1401	       </vcalendar>
1402	      </iCalendar>

1404	11.9  Publish transparent annual event

1406	   The following is a snippet of an iCalendar XML document that
1407	   publishes information about an annually repeating event that is
1408	   transparent to busy time searches.

1410	      <iCalendar>
1411	       <vcalendar>
1412	        <version>2.0</version>
1413	        <prodid-//hacksw/handcal//NONSGML 1.0//EN</prodid>
1414	        <method>PUBLISH</publish>
1415	        <vevent>
1416	         <uid>19990101T125957Z-123403@host.com</uid>
1417	         <dtstamp>19990101T130000Z</dtstamp>
1418	         <dtstart value="DATE">19991102</dtstart>
1419	         <summary>Our Blissful Anniversary</summary>
1420	         <class>CONFIDENTIAL</class>
1421	         <transp>TRANSPARENT</transp>
1422	         <categories>Anniversary,Personal,Special Occasion</categories>
1423	         <rrule>FREQ=YEARLY</rrule>
1424	        </vevent>
1425	       </vcalendar>
1426	      </iCalendar>

1428	11.10  Meeting invitation

1430	   The following is a snippet of an iCalendar XML document that
1431	   specifies an invitation for a meeting.  The meeting occurs on the
1432	   first Monday of each year for five years.

1434	      <iCalendar>
1435	       <vcalendar>
1436	       <method>REQUEST</method>
1437	       <version>2.0</version>
1438	       <prodid>-//hacksw/handcal//NONSGML 1.0//EN</prodid>
1439	       <vevent>
1440	        <uid>19981220T130000Z-123403@host.com</uid>
1441	        <dtstamp>19981220T130050Z</dtstamp>
1442	        <organizer>MAILTO:corprel@host.com</organizer>
1443	        <dtstart>19990104T140000Z</dtstart>
1444	        <dtend>19990104T220000Z</dtend>
1445	        <summary>Annual Stockholders Meeting</summary>
1446	        <location>One Corporate Drive, Wilmington, DL</location>
1447	        <attendee role="CHAIR">MAILTO:mrbig@host.com</attendee>
1448	        <attendee cutype="GROUP"
1449	                  rsvp="TRUE">CAP:host.com/stockholders</attendee>
1450	        <categories>Business,Meeting,Special Occasion</categories>
1451	        <rrule>FREQ=YEARLY;COUNT=5;BYDAY=1MO</rrule>
1452	        </vevent>
1453	       </vcalendar>
1454	      </iCalendar>

1456	11.11  Assign a to-do

1458	   The following is a snippet of an iCalendar XML document for a to-do.

1460	      <iCalendar>
1461	       <vcalendar>
1462	        <method>REQUEST</method>
1463	        <version>2.0</version>
1464	        <prodid>-//hacksw/handcal//NONSGML 1.0//EN</prodid>
1465	        <vtodo>
1466	         <uid>19990104T133402@ical1.host.com</uid>
1467	         <dtstamp>19990104T133410Z</dtstamp>
1468	         <dtstart value="DATE">19990104</dtstart>
1469	         <due value="DATE">19990129</due>
1470	         <organizer>MAILTO:dboss@host.com</organizer>
1471	         <summary>Periodic Self Review</summary>
1472	         <description>Complete your self review.
1473	         Contact me if you questions.</description>
1474	         <priority>1</priority>
1475	         <class>CONFIDENTIAL</class>
1476	         <attendee>CAP:dilbert@host.com</attendee>
1477	        </vtodo>
1478	       </vcalendar>
1479	      </iCalendar>

1481	11.12  Publish busy time

1483	   The following is an iCalendar XML document that publishes busy time
1484	   information.  The default value for the "method" attribute is
1485	   "PUBLISH" and does	not need to be specified in this example.

1487	      <iCalendar>
1488	       <vcalendar>
1489	        <version>2.0</version>
1490	        <prodid>-//hacksw/handcal//NONSGML 1.0//EN</prodid>
1491	        <vfreebusy>
1492	         <uid>19980313T133000@ical1.host.com</uid>
1493	         <dtstamp>19990104T133010Z</dtstamp>
1494	         <organizer>CAP:host.com/jsmith</organizer>
1495	         <dtstart>19980313T141711Z</dtstart>
1496	         <dtend>19980410T141711Z</dtend>
1497	         <url>jsmith.ifb</url>
1498	         <freebusy>19980314T233000Z/19980315T003000Z</freebusy>
1499	         <freebusy>19980316T153000Z/19980316T163000Z</freebusy>
1500	         <freebusy>19980318T030000Z/19980318T040000Z</freebusy>
1501	        </vfreebusy>
1502	       </vcalendar>
1503	      </iCalendar>

1505	11.13  Request busy time

1507	   The following is a snippet of an iCalendar XML document that requests
1508	   a calendar user's busy time information.

1510	      <iCalendar>
1511	       <vcalendar>
1512	        <method>REQUEST</method>
1513	        <version>2.0</version>
1514	        <prodid>-//hacksw/handcal//NONSGML 1.0//EN</prodid>
1515	        <vfreebusy>
1516	         <uid>19970901T083000@ical1.host.com</uid>
1517	         <dtstamp>19970901T083000Z</dtstamp>
1518	         <organizer>MAILTO:jane_doe@host1.com</organizer>
1519	         <dtstart>19971015T050000Z</dtstart>
1520	         <dtend>19971016T050000Z</dtend>
1521	         <attendee>MAILTO:john_public@host2.com</attendee>
1522	        </vfreebusy>
1523	       </vcalendar>
1524	      </iCalendar>

1526	11.14  Issue a CAP command

1528	   The following is a snippet of an iCalendar XML document that issues a
1529	   CAP	command to delete a UID.

1531	      <iCalendar xmlns="http://www.ietf.org/internet-drafts/draft-hare-xcalendar-01.txt"
1532	                     xmlns:CAP="="http://www.ietf.org/internet-drafts/draft-ietf-calsch-cap-13.txt">
1533	       <vcalendar>
1534	        <version>2.0</version>
1535	        <prodid>-//hacksw/handcal//NONSGML 1.0//EN</prodid>
1536	        <target>relcalid-22</target>
1537	        <CAP:cmd id="random but unique per CUA">DELETE</CAP:cmd>
1538	        <CAP:vquery>
1539	         <CAP:query>SELECT VEVENT FROM VAGENDA WHERE UID = 'abcd12345'</CAP:query>
1540	        </CAP:vquery>
1541	        </vcalendar>
1542	       </iCalendar>

1544	11.15  A well-formed and valid XML document which can be transformed
1545	       into iCalendar

1547	   The following is a simple example document which contains some date
1548	   and time elements .  This document is both a well-formed and valid
1549	   XML document.  It contains a DTD and references a stylesheet which
1550	   transforms the schedule elements into iCalendar.  The time used is a
1551	   "floating" time, without timezone information, to simplify the
1552	   example.

1554	      <?xml version="1.0" encoding="UTF-8"?>
1555	      <!DOCTYPE tour [
1556	           <!ELEMENT tourdata (performer,tourname,gig+)>
1557	           <!ELEMENT performer (#PCDATA)>
1558	           <!ELEMENT tourname (#PCDATA)>
1559	           <!ELEMENT gig (venue,date,time)>
1560	           <!ELEMENT venue (#PCDATA)>
1561	           <!ELEMENT date (#PCDATA)>
1562	           <!ELEMENT time (#PCDATA)]>
1563	      <?xml-stylesheet type="text/xsl" href="tour2ical.xsl" output="text">
1564	           <tour>
1565	           <performer>Frank Dylan</performer>
1566	           <tourname>Rolling Blunder Revue</tourname>
1567	           <gig>
1568	                   <venue>East Sandusky, Ohio Civic Auditorium</venue>
1569	                   <date>01/03/1997</date>
1570	                   <time>21:00:00</time>
1571	           </gig>
1572	           <gig>
1573	                   <venue>Sandlot, NM Lost Highway Cafe</venue>
1574	                   <date>08/09/1997</date>
1575	                   <time>12:00:00</time>
1576	           </gig>
1577	           </tour>

1579	   The required stylesheet to transform the document into an iCalendar
1580	   object (tour2ical.xsl) .  Note that some of the transformations,
1581	   notably date and time,	would need more work to provide the robustness
1582	   usually needed for applications;	the simple method here is used as an
1583	   example only.

1585	             <?xml version="1.0" encoding="UTF-8"?>
1586	             <xsl:stylesheet version="1.0"
1587	                  xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
1588	             <xsl:output method="text" media-type="text/calendar" />
1589	             <xsl:template match="tour">
1590	                   BEGIN:VCALENDAR
1591	                   METHOD:PUBLISH
1592	                   <xsl:for-each select="./gig">
1593	                           BEGIN:VEVENT
1594	                   <!-- since no datestamps in original -->
1595	                   <!-- use same date & time            -->
1596	                           DTSTAMP:<xsl:call-template name="getdate" />
1597	                           DTSTART:<xsl:call-template name="getdate" />
1598	                           SUMMARY:<xsl:value-of select="../tourname" />
1599	                           DESCRIPTION:<xsl:value-of select="../performer" />
1600	                           <xsl:text> </xsl:text>
1601	                           <xsl:value-of select="./venue" />
1602	                   </xsl:for-each>
1603	             </xsl:template>
1604	             <xsl:template name="getdate">
1605	                   <xsl:value-of select="substring(date,7,4)" />
1606	                   <xsl:value-of select="substring(date,1,2)" />
1607	                   <xsl:value-of select="substring(date,4,2)" />
1608	                   <xsl:text>T</xsl:text>
1609	                   <xsl:value-of select="substring(time,1,2)" />
1610	                   <xsl:value-of select="substring(time,4,2)" />
1611	                   <xsl:value-of select="substring(time,7,2)" />
1612	             </xsl:template>
1613	             </xsl:stylesheet>

1615	12.  Acknowledgments

1617	   This document is based on previous work by Frank Dawson, Eric R.
1618	   Plamondon, Doug Royer, and Surendra K. Reddy, whose previous XML-
1619	   iCalendar work provided the basis for this document.  Their previous
1620	   xCalendar work also acknowledged the contributions of Greg
1621	   FitzPatrick, Charles Goldfarb, Paul Hoffman, Lisa Dusseault and
1622	   Thomas Rowe.  The rdf2ical.xsl transformation created by Masahide
1623	   Kanzaki provided inspiration and concepts for the XSL transformation
1624	   in this document.  The primary author of this version of the document
1625	   (T. Hare), however, assumes responsibility for all content,
1626	   omissions, and especially errors.

1628	13.  Security Considerations

1630	   CDATA Sections - - A XML iCalendar document may contain CDATA
1631	   sections to represent content for specific element types.  The CDATA
1632	   section specifies arbitrary character data that is not meant to be
1633	   interpreted.  It is not scanned	by the XML parser for markup.  While
1634	   this memo restricts that any CDATA section MUST NOT contain markup or
1635	   other such alternate representation for the property value, in
1636	   general, CDATA section from a non-conformant implementation can
1637	   contain content such as HTML markup.  HTML text can be used to invoke
1638	   programs.	Implementors should be aware that this may leave an
1639	   implementation open to malicious attack that might occur as a result
1640	   of executing the markup in the CDATA section.

1642	   PROCEDURAL ALARMS - - A XML iCalendar document can be created that
1643	   contains a "VEVENT" and "VTODO" calendar component with "VALARM"
1644	   calendar components.  The "VALARM" calendar component can be of type
1645	   PROCEDURE and can have an attachment containing some sort of
1646	   executable program.  Implementations that incorporate these types of
1647	   alarms are subject to any virus or malicious attack that might occur
1648	   as a result of executing the attachment.

1650	   ATTACHMENTS - - A XML iCalendar document can include references to
1651	   Uniform Resource Locators that can be programmed resources.
1652	   Implementers and users of this memo should be aware of the network
1653	   security implications of accepting and	parsing such information.

1655	   In addition, since the XML objects in this memo may be exchanged via
1656	   many possible mechanisms, the security considerations observed by
1657	   implementations of those mechanisms should be followed for this memo.

1659	Author's Address

1661	   Tim Hare
1662	   An individual
1663	   3048 Bell Grove Dr.
1664	   Tallahassee, FL  32308
1665	   US

1667	   Phone: (850)414-4209
1668	   Email: TimHare@comcast.net

1670	Appendix A.  Bibliography

1672	   [FPI] F. Dawson, "iCalendar Formal Public Identifier", Internet
1673	   Draft,
1674	   http://www.internic.net/internet-drafts/draft-calsch-icalfpi-00.txt,
1675	   September 1998.

1677	   [ISO9070] "Information Technology_SGML Support
1678	   Facilities_Registration Procedures for Public Text Owner
1679	   Identifiers", ISO/IEC 9070, Second Edition, International
1680	   Organization for Standardization, April 1991.

1682	   [RFC 2045] N. Freed, N. Borenstein, "Multipurpose Internet Mail
1683	   Extensions 	(MIME) - Part One: Format of Internet Message Bodies",
1684	   RFC 2045, November 1996.

1686	   [RFC 2119] S. Bradner, "Key words for use in RFCs to Indicate
1687	   Requirement Levels", RFC 2119, http://www.ietf.org/rfc/rfc2119.txt,
1688	   March 1997.

1690	   [RFC 2445] F. Dawson and D. Stenerson, "Internet Calendaring and
1691	   Scheduling Core Object Specification (iCalendar)", RFC 2445,
1692	   http://www.ietf.org/rfc/rfc2445.txt, November 1998.

1694	   [RFC 2446] F. Dawson, R. Hopson, S. Mansour, S. Silverberg
1695	   "iCalendar Transport-	independent Interoperability Protocol", RFC
1696	   2446, http://www.ietf.org/rfc/rfc2446.txt, November 1998

1698	   [RFC 2447] F. Dawson, S. Mansour, S. Silverberg "iCalendar Message-
1699	   based Interoperability Protocol", RFC 2447,
1700	   http://www.ietf.org/rfc/rfc2447.txt, November 1998

1702	   [CAP] G. Babics, P. Hill, S. Mansour, D. Royer "Calendar Access
1703	   Protocol", 	Internet-Draft,
1704	   http://www.ietf.org/internet-drafts/draft-ietf-calsch-cap-13.txt,
1705	   January 2004

1707	   [Previous xCalendar work] F. Dawson, S. Reddy, D. Royer, E. Plamondon
1708	   "iCalendar DTD Document (xCal)", Internet-Draft,
1709	   http://www.ietf.org/internet-drafts/draft-ietf-many-xcal-03.txt, July
1710	   2002

1712	   [XML] "Extensible Markup Language (XML)", Worldwide Web Consortium,
1713	   http://www.w3.org/TR/REC-xml, October 2000.

1715	   [XSL] "Extensible Stylesheet Language (XSL)", Worldwide Web
1716	   Consortium, http://www.w3.org/TR/xsl, October 2001.

1718	   [XSLT] "Extensible Stylesheet Language Transformations (XSLT)",
1719	   Worldwide Web Consortium, http://www.w3.org/TR/xslt, November 1999.

1721	Intellectual Property Statement

1723	   The IETF takes no position regarding the validity or scope of any
1724	   Intellectual Property Rights or other rights that might be claimed to
1725	   pertain to the implementation or use of the technology described in
1726	   this document or the extent to which any license under such rights
1727	   might or might not be available; nor does it represent that it has
1728	   made any independent effort to identify any such rights.  Information
1729	   on the procedures with respect to rights in RFC documents can be
1730	   found in BCP 78 and BCP 79.

1732	   Copies of IPR disclosures made to the IETF Secretariat and any
1733	   assurances of licenses to be made available, or the result of an
1734	   attempt made to obtain a general license or permission for the use of
1735	   such proprietary rights by implementers or users of this
1736	   specification can be obtained from the IETF on-line IPR repository at
1737	   http://www.ietf.org/ipr.

1739	   The IETF invites any interested party to bring to its attention any
1740	   copyrights, patents or patent applications, or other proprietary
1741	   rights that may cover technology that may be required to implement
1742	   this standard.  Please address the information to the IETF at
1743	   ietf-ipr@ietf.org.

1745	Disclaimer of Validity

1747	   This document and the information contained herein are provided on an
1748	   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1749	   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1750	   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1751	   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1752	   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1753	   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

1755	Copyright Statement

1757	   Copyright (C) The Internet Society (2005).  This document is subject
1758	   to the rights, licenses and restrictions contained in BCP 78, and
1759	   except as set forth therein, the authors retain all their rights.

1761	Acknowledgment

1763	   Funding for the RFC Editor function is currently provided by the
1764	   Internet Society.