On Tue, 29 Feb 2000, Kevin A. Burton wrote:
> Jeff Prickett wrote:
>
> So the problem I think is that iCalendar isn't an XML protocol. It (and
> other protocols like LDAP/IMAP) are dead in most respects. Defining
> wire protocols for every single applications is an old approach and
> won't happen except in certain situations like hardware devices where it
> might actually be needed.
>
Yes, true. iCalendar may also be dead simply because those who have fat
client calendaring software have too much invested in their own
proprietary systems. An open source implementation could break that open.
One of the reasons I chose to implement iCalendar was mainly because of
the upfront design work. It defines what your objects look like and there
are even standards on how those objects should interact. For this parsing
is not really necessary. Just look at the properties/objects and hack it
together.
> So I am wondering if it doesn't just make sense to eat our "own"
> dogfood. Although not an official Apache project Castor is APL and is
> very active and a cool approach. If we take an iCalendar request and
> map it to XML via an XML schema we have writen we should be able to
> think of everything as a Java and not the iCalendar protocol.
>
I am aware of Castor and old outdated version is sitting on my machine
now. I have been thinking about joining those lists too. Actually, I was
going to put together a proposal for them about their OQL parser on
sourceXchange. I was hoping to hack out as much as could of iCalendar with
JLex just to see what would be involved. The RFP for the OQL code had a
bonus for adhereing to a tight deadline. JLex or from what you say
below XML/XSLT seems to me the only way to
go even come close to the deadline. Writing a parser by hand is a bear!!!
> Check out the Castor DSML module. It is an LDAP directory exchange via
> XML. It uses JNDI so they don't have to parse it out.
Hmmm, sounds interesting I would never have thought of this. What about
performance issues? As much as I try I just cant keep up with all this as
much as I would like. Only so many hours in the day.
>
> Also, is it possible to use a JNDI provider with this? It seems easier
> and probably will map very well. We could then use the DSML project and
> tweak it to work with iCalendar.
>
I will look into this.
> Honestly lex was a cool approach. Everything now will be done with
> XSLT/XML Schema and code generators like castor.
>
> Just my $.02
I appreciate the input. The iCalendar
Jeff Prickett
[EMAIL PROTECTED]
>
> Kevin
>
> --
> Kevin A Burton ([EMAIL PROTECTED])
> http://relativity.yi.org
> Message to SUN: "Open Source Java!"
> "For evil to win is for good men to do nothing."
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
