http://blog.gmane.org/gmane.ietf.calsify hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.ietf.calsify/2296 <pre>This letter is an outcome of CalConnect round table discussion. Currently some calendaring libraries and services silently ignore RRULE parameters they don't understand. Such behavior contradicts the spec ( http://tools.ietf.org/html/rfc5545#section-3.3.10), and prevents any extension to the RRULE behavior. We want to add a new parameter to the RRULE, which modifies set of instances produced by it. If a client or service silently ignores the new parameter, it will produce incorrect set of instances causing data inconsistency. The best such a client can do is to reject RRULE it doesn't understand, and do not produce any set of instances for it. Bug will be filed shortly for ical4j, fixing which should also fix all dependent services (including our Google Calendar). If you are aware of other implementations of iCalendar parsing, please post here so we can cover them too. Best Regards Grisha Google Inc. _______________________________________________ calsify mailing list calsify&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/calsify </pre> Gregory Yakushev 2013-06-17T09:55:14 http://comments.gmane.org/gmane.ietf.calsify/2287 <pre>A draft RFC to support non-Gregorian recurrence rules in iCalendar is available for discussion. It will allow us to specify events like Chinese New Year, Ramadan or Korean birthdays. Please see the links below. Comments are welcome on the calsify&lt; at &gt;ietf.org mailing list. If adopted, we are likely to start using it at Google, and recurrences with RSCALE parameter will appear in iCalendar data provided by us. Grigory Yakushev Google Inc. Title: Non-Gregorian Recurrence Rules in iCalendar URL: http://www.ietf.org/internet-drafts/draft-daboo-icalendar-rscale-00.txt Status: http://datatracker.ietf.org/doc/draft-daboo-icalendar-rscale Htmlized: http://tools.ietf.org/html/draft-daboo-icalendar-rscale-00 _______________________________________________ calsify mailing list calsify&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/calsify </pre> Gregory Yakushev 2013-05-06T14:27:54 http://comments.gmane.org/gmane.ietf.calsify/2286 <pre>Biggest Fake Conference in Computer Science We are researchers from different parts of the world and conducted a study on the world’s biggest bogus computer science conference WORLDCOMP ( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia from University of Georgia, USA. We submitted a fake paper to WORLDCOMP 2011 and again (the same paper with a modified title) to WORLDCOMP 2012. This paper had numerous fundamental mistakes. Sample statements from that paper include: (1). Binary logic is fuzzy logic and vice versa (2). Pascal developed fuzzy logic (3). Object oriented languages do not exhibit any polymorphism or inheritance (4). TCP and IP are synonyms and are part of OSI model (5). Distributed systems deal with only one computer (6). Laptop is an example for a super computer (7). Operating system is an example for computer hardware Also, our paper did not express any conceptual meaning. However, it was accepted both the times without any modifications (and without any reviews) and we were invited to submit the final paper and a payment of $500+ fee to present the paper. We decided to use the fee for better purposes than making Prof. Hamid Arabnia (Chairman of WORLDCOMP) rich. After that, we received few reminders from WORLDCOMP to pay the fee but we never responded. We MUST say that you should look at the above website if you have any thoughts to submit a paper to WORLDCOMP. DBLP and other indexing agencies have stopped indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of http://sites.google.com/site/dumpconf for comments from well-known researchers about WORLDCOMP. The status of your WORLDCOMP papers can be changed from scientific to other (i.e., junk or non-technical) at any time. Better not to have a paper than having it in WORLDCOMP and spoil the resume and peace of mind forever! Our study revealed that WORLDCOMP is a money making business, using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing out a small chunk of that money (around 20 dollars per paper published in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) who publicizes WORLDCOMP and also defends it at various forums, using fake/anonymous names. The puppet uses fake names and defames other conferences to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). That is, the puppet does all his best to get a maximum number of papers published at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has refused to provide the venue for WORLDCOMP’13 because of the fears of their image being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 is taking place at a different resort. WORLDCOMP will not be held after 2013. The draft paper submission deadline is over but still there are no committee members, no reviewers, and there is no conference Chairman. The only contact details available on WORLDCOMP’s website is just an email address! Let us make a direct request to Prof. Hamid arabnia: publish all reviews for all the papers (after blocking identifiable details) since 2000 conference. Reveal the names and affiliations of all the reviewers (for each year) and how many papers each reviewer had reviewed on average. We also request him to look at the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 Sorry for posting to multiple lists. Spreading the word is the only way to stop this bogus conference. Please forward this message to other mailing lists and people. We are shocked with Prof. Hamid Arabnia and his puppet’s activities http://worldcomp-fake-bogus.blogspot.com Search Google using the keyword worldcomp fake for additional links. _______________________________________________ calsify mailing list calsify&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/calsify </pre> johnsonhammond2< at >hushmail.com 2013-04-27T17:13:13 http://comments.gmane.org/gmane.ietf.calsify/2285 <pre>Hi folks, Below is the announcement for a new draft that was just posted. This draft, which stems from work done at the Calendaring and Scheduling Consortium, attempts to address the need for iCalendar data to support non-Gregorian recurrence behavior. Rather than making use of the existing "CALSCALE" option in iCalendar (which was considered too disruptive), it instead defines extensions to the "RRULE" property. Please review and discuss on the ietf-calsify list, thanks. ------------ Forwarded Message ----------- Date: April 26, 2013 at 7:12:37 AM -0700 From: internet-drafts&lt; at &gt;ietf.org To: Cyrus Daboo &lt;cyrus&lt; at &gt;daboo.name&gt;, Gregory Yakushev &lt;yakushev&lt; at &gt;google.com&gt; Subject: New Version Notification for draft-daboo-icalendar-rscale-00.txt A new version of I-D, draft-daboo-icalendar-rscale-00.txt has been successfully submitted by Cyrus Daboo and posted to the IETF repository. Filename: draft-daboo-icalendar-rscale Revision: 00 Title: Non-Gregorian Recurrence Rules in iCalendar Creation date: 2013-04-26 Group: Individual Submission Number of pages: 11 URL: http://www.ietf.org/internet-drafts/draft-daboo-icalendar-rscale-00.txt Status: http://datatracker.ietf.org/doc/draft-daboo-icalendar-rscale Htmlized: http://tools.ietf.org/html/draft-daboo-icalendar-rscale-00 Abstract: This document defines how non-Gregorian recurrence rules can be specified in iCalendar data. ---------- End Forwarded Message ---------- </pre> Cyrus Daboo 2013-04-26T14:17:00 http://comments.gmane.org/gmane.ietf.calsify/2284 <pre>Hey Folks, as a basis for discussion for the WG I have put together an etherpad with a summary of iCalendar and vCard specs. It contains examples on how the jCard/jCal looks like. Note for those items that have different proposals, I have included all options. It may be that for some items there has been previous discussion that would rule out the one or other. https://calendar.etherpad.mozilla.org/jcardcal-model I'm looking forward to your comments. If you decide to write something on the etherpad, please fill in your name. For those of you on the calsify/vcarddav lists, this will likely be my last post aside from new version notifications. If you would like to continue to discuss these emerging standards, please subscribe to the jcardcal mailing list. Thanks, Philipp </pre> Philipp Kewisch 2013-03-20T11:29:04 http://comments.gmane.org/gmane.ietf.calsify/2283 <pre>Hello, As mentioned in the attached email, during discussions on the new vCard resource draft we realized the need to re-use and sometimes enhance the currently defined KIND values to define schedulable resources. This lead to the idea of replicating the concept of Objectclass that LDAP offers. After further discussions the following drafts have been submitted. Any review and comments would be greatly appreciated. - Base vCard objectclass property definition - http://tools.ietf.org/html/draft-vcard-objectclass-00 - Definition of the "schedulable" objectclass value used to define any schedulable entity - http://tools.ietf.org/html/draft-vcard-schedulable-00 - Modified vCard representation of a schedulable resource that makes use of the schedulable objectclass - http://tools.ietf.org/html/draft-cal-resource-vcard-02 Thanks, Ciny _______________________________________________ calsify mailing list calsify&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/calsify </pre> Ciny Joy 2013-02-27T23:54:09 http://comments.gmane.org/gmane.ietf.calsify/2247 <pre>Hi folks, We have posted a new version of the timezone service draft: &lt;https://datatracker.ietf.org/doc/draft-douglass-timezone-service/&gt; and would greatly appreciate reviews of this as we intend to ask the IETF/IESG to start the process of review/approval/publication. There has been one big change in this new version: the switch to using JSON for the responses from the server rather than XML. This was something we had been considering for a while - primarily because we think the most common "light weight" clients wanting to use this protocol will be web/browser based. </pre> Cyrus Daboo 2012-11-30T16:05:02 http://comments.gmane.org/gmane.ietf.calsify/2244 <pre>Hi folks, The parameter encoding spec is now in IETF Last Call so this is (almost) your last chance to review and comment... ------------ Forwarded Message ----------- Date: November 16, 2012 1:13:43 PM -0800 From: IETF Secretariat &lt;ietf-secretariat-reply&lt; at &gt;ietf.org&gt; Subject: ID Tracker State Update Notice: &lt;draft-daboo-ical-vcard-parameter-encoding-02.txt&gt; Last call has been made for draft-daboo-ical-vcard-parameter-encoding and state has been changed to In Last Call ID Tracker URL: http://datatracker.ietf.org/doc/draft-daboo-ical-vcard-parameter-encoding/ ---------- End Forwarded Message ---------- </pre> Cyrus Daboo 2012-11-16T21:17:12 http://comments.gmane.org/gmane.ietf.calsify/2242 <pre>FYI ------------ Forwarded Message ----------- Date: November 13, 2012 10:08:57 PM -0800 From: internet-drafts&lt; at &gt;ietf.org To: mozilla&lt; at &gt;kewis.ch cc: cyrus&lt; at &gt;daboo.name, douglm&lt; at &gt;rpi.edu Subject: New Version Notification for draft-kewisch-et-al-icalendar-in-json-00.txt A new version of I-D, draft-kewisch-et-al-icalendar-in-json-00.txt has been successfully submitted by Philipp Kewisch and posted to the IETF repository. Filename: draft-kewisch-et-al-icalendar-in-json Revision: 00 Title: jCal: The JSON format for iCalendar Creation date: 2012-11-13 WG ID: Individual Submission Number of pages: 29 URL: http://www.ietf.org/internet-drafts/draft-kewisch-et-al-icalendar-in-json-0 0.txt Status: http://datatracker.ietf.org/doc/draft-kewisch-et-al-icalendar-in-json Htmlized: http://tools.ietf.org/html/draft-kewisch-et-al-icalendar-in-json-00 Abstract: This specification defines "jCal", a JSON format for iCalendar data. The IETF Secretariat ---------- End Forwarded Message ---------- </pre> Cyrus Daboo 2012-11-14T17:23:52 http://comments.gmane.org/gmane.ietf.calsify/2235 <pre>Hi folks, I would like to progress &lt;http://tools.ietf.org/html/draft-daboo-ical-vcard-parameter-encoding-01&gt; through the publication process. After consultation with ADs, we would like to have vCard WG and Calsify mailing list participants do one more review of this document as an "informal" list last call (note this is not a WG document). Please review and post comments to the relevant list by October 2nd, thanks. </pre> Cyrus Daboo 2012-09-18T17:28:59 http://comments.gmane.org/gmane.ietf.calsify/2228 <pre>Hi, As discussed a few weeks ago I have written a draft that defines a way for vCard and iCalendar parameter values to be encoded using an escape sequence that allows certain characters, previously forbidden from appearing in a parameter value, to now be included. Comments welcome... ------------ Forwarded Message ----------- Date: July 7, 2012 9:43:57 AM -0700 From: internet-drafts&lt; at &gt;ietf.org To: cyrus&lt; at &gt;daboo.name Subject: New Version Notification for draft-daboo-ical-vcard-parameter-encoding-00.txt A new version of I-D, draft-daboo-ical-vcard-parameter-encoding-00.txt has been successfully submitted by Cyrus Daboo and posted to the IETF repository. Filename: draft-daboo-ical-vcard-parameter-encoding Revision: 00 Title: Parameter Value Encoding in iCalendar and vCard Creation date: 2012-07-07 WG ID: Individual Submission Number of pages: 5 URL: http://www.ietf.org/internet-drafts/draft-daboo-ical-vcard-parameter-encodi ng-00.txt Status: http://datatracker.ietf.org/doc/draft-daboo-ical-vcard-parameter-encoding Htmlized: http://tools.ietf.org/html/draft-daboo-ical-vcard-parameter-encoding-00 Abstract: This specification defines an extension to iCalendar and vCard data formats to allow parameter values to include certain characters forbidden by the existing specifications. The IETF Secretariat ---------- End Forwarded Message ---------- </pre> Cyrus Daboo 2012-07-07T16:47:11 http://comments.gmane.org/gmane.ietf.calsify/2228 <pre>Hi, As discussed a few weeks ago I have written a draft that defines a way for vCard and iCalendar parameter values to be encoded using an escape sequence that allows certain characters, previously forbidden from appearing in a parameter value, to now be included. Comments welcome... ------------ Forwarded Message ----------- Date: July 7, 2012 9:43:57 AM -0700 From: internet-drafts&lt; at &gt;ietf.org To: cyrus&lt; at &gt;daboo.name Subject: New Version Notification for draft-daboo-ical-vcard-parameter-encoding-00.txt A new version of I-D, draft-daboo-ical-vcard-parameter-encoding-00.txt has been successfully submitted by Cyrus Daboo and posted to the IETF repository. Filename: draft-daboo-ical-vcard-parameter-encoding Revision: 00 Title: Parameter Value Encoding in iCalendar and vCard Creation date: 2012-07-07 WG ID: Individual Submission Number of pages: 5 URL: http://www.ietf.org/internet-drafts/draft-daboo-ical-vcard-parameter-encodi ng-00.txt Status: http://datatracker.ietf.org/doc/draft-daboo-ical-vcard-parameter-encoding Htmlized: http://tools.ietf.org/html/draft-daboo-ical-vcard-parameter-encoding-00 Abstract: This specification defines an extension to iCalendar and vCard data formats to allow parameter values to include certain characters forbidden by the existing specifications. The IETF Secretariat ---------- End Forwarded Message ---------- </pre> Cyrus Daboo 2012-07-07T16:47:11 http://comments.gmane.org/gmane.ietf.calsify/2223 <pre>Hi, As I am sure most people are aware, a double-quote character is forbidden to appear in a parameter value in both vCard and iCalendar. Yet there is a need to preserve double-quotes in a parameter value. So I am going to propose an extension to the specifications whereby a new escape mechanism is introduced solely for the purpose of allowing d-quote in a parameter value in a backwards compatible manner. My proposal is to use ^ (0x5e) as an escape character, with only the following two sequences allowed: ^^ - represents a single ^ character ^' - represents a single d-quote character I ruled out use of \ because some parsers erroneously eat that, and it would also be tempting to use \" which is definitely not possible because the dquote cannot appear. I also ruled out &amp; (XML/HTML entity style) and % (URI style) style escaping as being too general - we don't need to escape arbitrary characters - only dquote. Also, I think &amp; and % are already in common use in parameter values that have URIs, so would end up being escaped themselves a lot more. I suspect ^ is one of the least used characters and so the need to escape the escape character is less. Obviously there would need to be some backwards compatibility statement in regard to what to do with existing values with a single ^. I would suggest any combination that is not one of the above two, should be left alone when parsing. But when generating, it would be escaped as ^^. There are probably some other ascii symbols that are infrequently used too, that we could pick if there are strong arguments against ^, but for now I am happy with ^. Thoughts? </pre> Cyrus Daboo 2012-06-20T02:56:34 http://comments.gmane.org/gmane.ietf.calsify/2222 <pre>Hello, As a result of discussions at Calconnect, we have submitted a draft defining the vCard representation of Calendaring Resources. See http://tools.ietf.org/html/draft-cal-resource-vcard-00. Previously we had submitted a draft defining the schema for representing resources in the calendaring and scheduling context both in vCard and LDAP. Since it had entries in there that would more rightfully go into a generic vCard to LDAP mapping draft, we have abandoned that draft for now. Any comments or corrections on the above draft would be greatly appreciated. Thanks, Ciny_______________________________________________ calsify mailing list calsify&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/calsify </pre> Ciny Joy 2012-04-30T20:46:48 http://comments.gmane.org/gmane.ietf.calsify/2221 <pre>This notice is going to the calendaring-related IETF lists. Our apologies if you receive multiple copies; many people are on the same lists. Registration is now open for CalConnect XXIV, May 21-25, 2012, hosted by Patricia Egen Consulting in Chattanooga, Tennessee As usual, Monday and Tuesday all day and Wednesday morning will be the Interoperability Test Event; Wednesday afternoon, Thursday, and Friday will be the CalConnect Roundtable Technical Conference. General Information: Logistics information for this event may be found at http://www.calconnect.org/calconnect24.shtml including travel, hotel, and other planning information. A general schedule is posted, but will be updated nearer to the event with the actual session schedule and with topical agendas for the schedule. The meeting venue and conference hotel is the Doubletree Hotel, 407 Chestnut Street, Chattanooga, TN. All meeting sessions and the Wednesday evening reception will be held at the Doubletree. The Doubletree is offering a room rate of $129 per night for CalConnect attendees if you book prior to 3 May and the room block is not already full. To book directly with the hotel, you may go to this link http://doubletree.hilton.com/en/dt/groups/personalized/C/CHACHDT-PEC-20120520/index.jhtml?WT.mc_id=POG or call 423-756-5150 to reserve and tell them you are attending the CalConnect conference. Although the booking page says May 20-25 you may book from the 19th through the 26th at the special rate. I encourage you to register early for this event as well, as early registration helps us with event planning and logistics, in addition to restaurant reserfvations. (Please remember that you need not pay when you register; if desired you may wait until the event and pay by credit card.0 About the Roundtable: The exact schedule for TC Sessions is not yet fixed but should be determined early in April. Early registration for the Roundtable will be $350 through 5 May 2012, and $395 after that date. Another reason to register early: you won't forget and miss the early registration deadline. Please note that the early registration about applies so long as you register &lt;= 5 May, even if you don't actually pay until the event. About the Interoperability Test Event: We will be testing the following: • CalDAV Access • CalDAV Scheduling, including Implicit Scheduling • iMIP and iMIP Gateways • CardDAV • Timezone Service Protocol and Timezones by Reference This list will be updated as additional testing areas are identified and requested by two or more testing organizations. We may be testing the following if two or more testing organizations express interest: iSchedule Web Services (CalWS REST and CalWS SOAP) In all cases at least two participating organizations must be interested in testing a particular area or scenario to form testing pairs. Additionally, we are planning on three special BOF sessions during the the Interoperability Test Event Auto-discovery (continuation of BOF from CalConnect XXIII in February 2012) vCard 3 to vCard 4 transition Shared Address Books The information page for the Interoperability Test event is at http://www.calconnect.org/iop1205.shtml. A short descripttion of the BOFs at the test event will be added to this page in early April. Please note that the Interoperability Test Event registration fee for non-vendor members is now $350 per person. Test Event registration fees for vendor members and for non-members remain unchanged at $1795 and $2795 respectively for the first two participants, and $150 per additional participant. Please contact me with any questions; my contact information is below. Dave Thewlis -- Dave Thewlis, Executive Director CalConnect - The Calendaring and Scheduling Consortium +1 707 840 9391 voice | +1 707 498 2238 mobile | +1 415 946 3454 fax http://www.calconnect.org | Dave.Thewlis&lt; at &gt;calconnect.org _______________________________________________ ietf-calsify mailing list ietf-calsify&lt; at &gt;osafoundation.org http://lists.osafoundation.org/mailman/listinfo/ietf-calsify </pre> Dave Thewlis 2012-03-19T18:45:46 http://comments.gmane.org/gmane.ietf.calsify/2209 <pre>The new timezones service draft is now available from https://datatracker.ietf.org/doc/draft-douglass-timezone-service/ This versions incorporates a number of changes made as a result of interoperability testing carried out during the last CalConnect event. We intend to be doing more testing during the next event in Prague (see http://calconnect.org/iop1110.shtml) We would welcome the opportunity to test against other implementations. </pre> Mike Douglass 2011-08-23T17:32:09 http://comments.gmane.org/gmane.ietf.calsify/2208 <pre>On behalf of the co-chairs I announce a colloquium about the implications of possible changes to the definition of UTC which is scheduled for a vote by delegates to the Radiocommunication Assembly in January. The draft under consideration by the ITU-R would redefine the notions of time and calendar day in ways that would have broad side effects. The website for the colloquium is http://futureofutc.org/ Abstracts already received include contributions from national observatories, international agencies, geophysics and navigation communities. Software and operating systems remain underrepresented. I invite contributions from members of the internet calendar community and anyone who may have code, systems, or products which could be affected by changes in the definition of the radio broadcast time signals which underly them. -- Steve Allen &lt;sla&lt; at &gt;ucolick.org&gt; WGS-84 (GPS) UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m </pre> Steve Allen 2011-08-17T04:08:37 http://comments.gmane.org/gmane.ietf.calsify/2204 <pre>Hi folks, xCal was just published as an RFC: &lt;http://tools.ietf.org/html/rfc6321&gt;. Thanks to all those who helped with this. </pre> Cyrus Daboo 2011-08-08T20:24:35 http://comments.gmane.org/gmane.ietf.calsify/2203 <pre>If you're taking on new clients, I'd like to include you in my private referral network to send you business leads through Referral Key. Please accept my invitation below. Thanks! Best, Lorenzo De Tomasi Isotype.org Roma +39 0686904090 View invitation from Lorenzo De Tomasi "The new, fast growing networking website is using the power of communication to help small businesses build powerful referral networks online." - Boston Business Journal _______________________________________________ ietf-calsify mailing list ietf-calsify&lt; at &gt;osafoundation.org http://lists.osafoundation.org/mailman/listinfo/ietf-calsify </pre> Lorenzo De Tomasi 2011-06-07T18:17:28 http://comments.gmane.org/gmane.ietf.calsify/2200 <pre>Hi folks, The iCalendar-in-XMl spec has been updated to account for comments during the last call which ended last week. Changes are noted in the spec at &lt;http://www.ietf.org/id/draft-daboo-et-al-icalendar-in-xml-09.txt&gt;. In regard to vcard-in-XML: please look at Section 5 which is how we agreed to deal with unrecognized property/parameter default values. I believe similar text and new XML value element is required in the vCard-in-XML spec too. One other thing, we ended up changing the date and time XML value formats to be more inline with the format used in XML schema: specifically adding "-" separators between the date components and ":" separators between the time components. This change was prompted by feedback from developers who wanted to be able to reuse xsd date/time types for validation and processing. This seemed like a reasonable request so we made the change. I would have thought a similar situation exists for vcard-in-XML so we may want to consider that. </pre> Cyrus Daboo 2011-05-18T14:15:20 http://comments.gmane.org/gmane.ietf.calsify/2197 <pre>In the examples at http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml-08#appendix-B , it would have been nice to show the unfolding and unescaping of properties and parameter values in the example (e.g. removal of \n in DESCRIPTION value, removal of double quote and comma escaping in parameters). + a really minor detail: Section 3 is titled "Converting from iCalendar to xCal" when section 4 is called "Converting from XML into iCalendar" instead of "Converting from xCal to iCalendar" Looks really good otherwise, Arnaud Quillaud </pre> Arnaud Quillaud 2011-04-18T12:14:43 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.ietf.calsify