Dear Folks, This is a followup reminder to my e-mail of May 24th requesting assistance in responding to a Calconnect questionnaire on Timezones. Our original target date for responses was June 10th. We're received several responses but hope that with a little more time others will be able to help us. If you've not responded but have a calendaring implementation, we would appreciate it very much if you could take a few minutes to respond to our questionnaire. We've extended the target date another week to Monday, June 20th -- and so you don't have to rummage around and find my previous e-mail, the questionniare (which is in e-mail format so you can fill it out and e-mail it back) is included below. Thank you very much for your help. Dave Thewlis --- Dave Thewlis, Executive Director Calconnect - The Calendaring and Scheduling Consortium +1 707 840 9391 (voice) · +1 707 498 2238 (mobile) http://www.calconnect.org · Dave.Thewlis@xxxxxxxxxxxxxx ------------------------------------------------------------------------------------------ Questionnaire on Timezones in iCalendar Introduction: This questionnaire is being used to determine support for iCalendar (RFC2445) timezone support. The specific sections in RFC2445 that are being queried are: 4.6.5 Time Zone Component 4.8.2.4 Date/Time Start 4.8.3 Time Zone Component Properties ( and sub-sections ) 4.8.5.3 Recurrence Date/Times 4.8.5.4 Recurrence Rule 4.8.7.3 Last Modified 4.8.8.1 Non-standard Properties These may involve reference to other sections. How to answer: Please copy the text from the '-------' divider below to the end of this message into a new message and address it to: <mailto:questionnaire@xxxxxxxxxxxxxx> To fill it out: For 'y/n/o': 'y' means yes 'n' means no 'o' means other or not applicable Delete two letters to leave the one for your answer. If you have specific comments you can add about your answers, please do so at the end and reference the question number to which the comment applies. For _____________________: enter text for the answer. ------- Product Details: P1: Product/Implementation Name: _____________________ Components supported: Consume Produce Q1: VTIMEZONE y/n/o y/n/o Q1.1: STANDARD y/n/o y/n/o Q1.2: DAYLIGHT y/n/o y/n/o Properties supported: In VTIMEZONE Consume Produce Q2.1: TZID y/n/o y/n/o Q2.2: LAST-MODIFIED y/n/o y/n/o Q2.3: TZURL y/n/o y/n/o Q2.4: XPROP y/n/o y/n/o In STANDARD Consume Produce Q3.1: DTSTART y/n/o y/n/o Q3.2: TZOFFSETTO y/n/o y/n/o Q3.3: TZOFFSETFROM y/n/o y/n/o Q3.4: COMMENT y/n/o y/n/o Q3.5: RDATE y/n/o y/n/o Q3.6: RRULE y/n/o y/n/o Q3.7: TZNAME y/n/o y/n/o Q3.8: XPROP y/n/o y/n/o In DAYLIGHT Consume Produce Q4.1: DTSTART y/n/o y/n/o Q4.2: TZOFFSETTO y/n/o y/n/o Q4.3: TZOFFSETFROM y/n/o y/n/o Q4.4: COMMENT y/n/o y/n/o Q4.5: RDATE y/n/o y/n/o Q4.6: RRULE y/n/o y/n/o Q4.7: TZNAME y/n/o y/n/o Q4.8: XPROP y/n/o y/n/o General: Q5: Do you always send DATE-TIME values with a timezone? y/n/o Q6: Do you always send DATE-TIME values in UTC or floating? y/n/o Q7: Do you provide a standard set of timezones built-in to your product? y/n/o if yes to Q7, then { Q8: Where did you get your timezone definitions? _____________________ Q9: How many timezone definitions do you have? _____________________ Q10: Do you have a special naming scheme for TZIDs, and if so what is it? _____________________ Q11: Do you provide a mechanism for updating built-in timezones? y/n/o if yes to Q11, then { Q12: Do you adjust future times to account for timezone definition changes? y/n/o } } Q13: Do you accept and use timezone definitions from imported iCalendar data? y/n/o if yes to Q13, then { Q14: Do you attempt to merge timezone definitions with the same TZID when importing iCalendar data? y/n/o } Q15: When exporting timezones in iCalendar data (either to a file or via iTIP) do you send the entire timezone definition or just the set of dates needed for coverage of the event? _____________________ Q16: Would you use timezone definitions from a standard timezone registry if one were created? y/n/o Q17: What problems would be involved in changing a timezone definition if DST was changed at some point in the future? _____________________ C1: Comments on specific answers (include Q number for cross-reference to original question): _____________________ C2: Comments on the format and ease of use of this questionnaire: _____________________ C3: Are there any additional questions we should be asking, and if so what are they? _____________________ |