On Sat, 5 May 2001, Dan Brian wrote:
> build the struct, and give access to the elements. Much like the XML APIs
> do for XML docs. (It's worth noting that there is an iCalendar schema
> that I've been using for a while in several Perl apps already; bummer
> that more apps don't:
> http://www.oasis-open.org/cover/draft-dawson-ical-xml-dtd-01.txt.) Set
<nitpick>
That's not an official standard; it's an IETF draft, and it expired
in June 1999. So, unless you have pointer to a more recent version,
I don't think that format should be taken as standard in any way.
(Doesn't mean it's not useful; just that it's not something destined
for wide adoption.)
</nitpick>
> (Also, please note that "iCal" is not quite accurate; picky, but there's
> so much out there called "iCal" that it's bound to confuse lots of folks
> otherwise.)
hm. What else is there?
> I may be offering more input than is desired, or addressing stuff that has
> already been addressed. But I think a good initial goal for the project
> would be this module, which would probably most appropriately be called
> simply "iCalendar", or some derivative under "Time::".
It's Net::ICal[1], which was started by Eric Busboom as Perl
wrappers around his libical module, and which the Reefknot project
has picked up and made into pure Perl. We'd love to have more
developers. If you'd like to get involved, please check out
Net::ICal 0.13 on CPAN. We'll be working on other tools for
standards-compliant calendaring as we get Net::ICal more stabilized.
We have a developers' list hosted on sourceforge which has about 40
subscribers; you can find a subscribe link and more information
about what we're doing at http://reefknot.sourceforge.net.
This list is for discussing things *in addition to* calendaring; I
think the Reefknot people here are just trying a get a sense of the
best ways to make our modules work with the rest of the Date::* on
CPAN.
[1] That's the module name we inherited from Eric, capitalization
and all; rather than dicker with capitalization, we're leaving it as
is because it has a prior release history.
srl
--
Shane R. Landrum [EMAIL PROTECTED]
we generate our own light to compensate for the lack of light from above -AD
GPG public key: http://cs.smith.edu/~slandrum/srl_pgpkey.txt
