The best bet for an unambiguous date format that's easily parsed by search engines is that defined in ISO8601. Current best practice seems to be to stick to the subset identified in this W3C note.
But it's not time formats we're talking about here - it's event formats. There's no point having a list of various dates and the events that are happening on each of them, unless there's enough syntax there to be able to parse which event is when, and where.
The most common format for event data seems to be iCal, but that has the disadvantage of being none too pleasant to parse. There's an RDF schema based on iCal which suffers the same conceptual problems as iCal, but with the added advantage/disadvantage of RDF syntax, depending on who you talk to (I'm firmly in the pro-RDF camp, and even I think that RDF-calendar is a bit awkward). Failing that, there are the microformats such as hCal, which again is essentially another syntax for iCal, but one which has been shoehorned into XHTML.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
(no subject)
(no subject)
It's also interesting to note how Upcoming handles events.
(no subject)
The most common format for event data seems to be iCal, but that has the disadvantage of being none too pleasant to parse. There's an RDF schema based on iCal which suffers the same conceptual problems as iCal, but with the added advantage/disadvantage of RDF syntax, depending on who you talk to (I'm firmly in the pro-RDF camp, and even I think that RDF-calendar is a bit awkward). Failing that, there are the microformats such as hCal, which again is essentially another syntax for iCal, but one which has been shoehorned into XHTML.