> I thought there was an iCal "standard" for calendar events.
It's best described as a pseudo-standard. But it beats none at all.
Unfortunately, it's a pseudo-standard for indicating a single event, not a
collection of events. Nor does it describe a mechanism for allowing
"remote" access to the stored collection of events.
Mail messages are transferred via SMTP (Simple Mail Transfer Protocol) in an
RFC-822 format. iCal is the equivalent of the RFC-822 format.
For what it's worth (and mainly to shorten the length of this email),
there's a lot of work going on in this arena. I'm just impatient. If
you're interested, start at:
<http://www.ietf.org/html.charters/calsch-charter.html>
Of, for a relatively high level overview of some of the issues:
<http://www.ietf.org/internet-drafts/draft-ietf-calsch-imp-guide-02.txt>
There are actually several possible protocols and standards to choose from;
however, eventually the ones specified in the RFC's tend to win (until a new
and better one is specified in the RFC's).
mikel
PS: To confuse the issue, there's iCal the product
<http://www.brownbearsw.com/ical/icalpage.html>. It is actually a calendar
server.
PPS: If you're really, really bored, start reading at:
<http://www.ietf.org/html.charters/wg-dir.html>
That links to all of the current IETF working groups.
PPPS: And if you really want to know how the Internet "works", this
<http://www.ietf.org/tao.html>
is good background. It's not quite as catchy as "open source", but open
collaboration has done a lot more for us thus far. ;-)
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
