RE: Alternative calendars and holidays, moon phases etc.

<- I guess what we're** looking for is a common data model for handling
<- calendarable events (I'm not insisting that every app uses it, just that
<- a lingua franca exists - to keep the burden of interoperability at a
<- linear cost). In other words, what does this "shared"* view of events
<- look like? What commonalities are out there? What's missing from what's
<- out there? In terms of interoperating parties, who pays the cost for a
<- piece of functionality, and what are the limits on that cost?
<-
<- As to application behaviour, heaven forfend that we try to mandate how
<- these work - that's a persuit on a hiding to nothing.

It's just occurred to me that the (any) clock can be hidden behind
interfaces that either send out ticks (or event notifications) or can reply
to polls (or calendar queries) - so this can be shifted to the application
layer as well. I think I'll read a bit more and keep my gob shut for a
while...

<- http://ilrt.org/discovery/2001/02/calendar/

Received on Thursday, 12 April 2001 13:06:26 UTC