[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Reg Date and Time representation in vCal 1.0

Given the language in the spec I would suggest that the T should never be omitted by an encoder. But clearly an “ideal” decoder would “do its best” if the T was missing on input. I am not certain when “ambiguities” might appear.


From: sam_cit [mailto:sam_cit@xxxxxxxxxxx]
Sent: Tuesday, May 16, 2006 9:23 AM
To: Roland H. Alden; imc-vcalendar@xxxxxxxxxxxx
Subject: RE: Reg Date and Time representation in vCal 1.0




 But the vCal specs says, The date and time values for all vCalendar properties are formatted as a string consistent with the ISO 8601 representation for combinations of dates and times


and according to ISO 8601,


Combined Date/Time Formats

The symbol "T" is used to separate the date and time parts of the combined representation. This may be omitted by mutual consent of those interchanging data, if ambiguity can be avoided

Does it mean that an ideal decoder should be able to decode date and time both with T as a seperator and without T as a seperator?


Thanks And Regards,


"Roland H. Alden" <ralden@xxxxxxxxxx> wrote:

I believe that notation is from an ISO standard and the T is quite mandatory.


From: owner-imc-vcalendar@xxxxxxxxxxxx [mailto:owner-imc-vcalendar@xxxxxxxxxxxx] On Behalf Of sam_cit
Sent: Tuesday, May 16, 2006 8:28 AM
To: imc-vcalendar@xxxxxxx
Subject: Reg Date and Time representation in vCal 1.0




  I have a very genuine doubt regarding vCal 1.0 date and time representation, is it mandatory to represent the character 'T' between date and Time.




 Is the t as a seperator mandatory or optional?


Thanks And Regards,


Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1/min.


New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.