[Ietf-calsify] dtstart and date vs datetime
connolly at w3.org
Fri Apr 21 10:55:18 PDT 2006
I just discovered that some code I wrote will produce this:
Given this input:
Seems like my testing would have caught a bug like that
long ago... but maybe it's not so much a bug as bad data.
The default datatype for DTSTART is DATE-TIME, and
all my tests explicitly give a type in the case of DATE:
The sections on DTSTART and DATETIME are reasonably
clear that DTSTART:20060804 is no good...
But there's a DTSTART:19980205 example discussed in passing
under 184.108.40.206 Trigger
and another DTSTART:19971102
Those examples seem to still be there in the October 11, 2005 draft
So... what's the deal?
- these examples are bad data and should be fixed
- the specification of DTSTART should be updated so that
the default type depends on the value given
- the specification of the DATE-TIME data type should be
updated so that values like 19971102 are OK
p.s. there isn't a calisfy test repository yet, is there?
I participate in development of hCalendar test develompent.
... RDF calendar test development.
I hope to get those two more sync'd up.
In particular, whatever answer I get from the CALSIFY WG on
this issue, I intend to reflect in those 2 test suites.
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
More information about the Ietf-calsify