On Sat, May 11, 2019, at 08:52, Keith Moore wrote:
On 5/10/19 2:56 PM, Doug Royer wrote:> With iCalendar for example, there is more than one way to represent> the same event. It is ambiguous and you have to examine other> implementations objects to see how they do things.. Then add code to> also accept their way. Every time I try to point it out, it quickly> escalates into a 'which way is better / you don't understand'. Which> is implementer shorthand for "you change your code, I will not".iCalendar may have been doomed from the start because every calendar appvendor had its own dysfunctional way of representing events beforeiCalendar existed, and few (if any) were willing to change.
Speaking of which, JSCalendar (a replacement format for iCalendar which removes many of the ambiguities) has just (re-)entered working group last call:
Bron.
--
Bron Gondwana, CEO, FastMail Pty Ltd
brong@xxxxxxxxxxxxxxxx
