- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 09 Aug 2005 11:08:31 +0200
- To: Doug Royer <Doug@royer.com>
- CC: xcal-dev@inet-consulting.com, Calsify <ietf-calsify@osafoundation.org>, CalDAV DevList <ietf-caldav@osafoundation.org>, www-rdf-calendar@w3.org, "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Doug Royer wrote: > > > The xCal draft has been rewritten and submitted to the IETF. > > I have an XSLT translation file that I will be releasing > soon on SourceForge that can translate an xCal object > back to an iCal object. I am waiting for SourceForge > to approve the project name. > > Discussion takes place on xCal@INET-Consulting.com > > Copies of the draft at: > > http://INET-Consulting.com/draft-royer-calsch-xcal-01.txt > http://INET-Consulting.com/draft-royer-calsch-xcal-01.html > http://INET-Consulting.com/draft-royer-calsch-xcal-01.xml > > > JOIN the xCal mailing list at: > > http://inet-consulting.com/mailman/listinfo/xcal > Just two quick formal comments...: 1) Is it intentional that in the examples, the iCalendar container element is in no namespace? 2) I don't think the IETF will let you use something like "http://ietf.org/rfc/rfcXXXX.txt" as namespace name; but if they do, you probably should use "http://ietf.org/rfc/rfcXXXX" (no extension) instead. Best regards, Julian
Received on Tuesday, 9 August 2005 09:08:47 UTC