> The second part of that though it that cross-breeding XML feeds into
> different applications (eg, using those resx files or even Atom-feeds for
> new uses in these real-time clients) is not something to discourage.  A lot
> of economy is found when one realizes one can simply use what is there even
> if for something it was not specifically designed for.  I've been doing
> quite a bit of work with ASP 2.0 and in general find it a much improved
> framework.  As I stare into the XML it produces, much of it is reusable even
> if proprietary.  In fact, one way to get a proprietary thing to quit being
> that is to put it to use at another job.
>

Just out of curiousity which XML in ASP 2.0 do you have in mind?

I have to do some work for the next little bit with Sharepoint, that
means I will have to do a lot with their caml markup
http://msdn2.microsoft.com/en-us/library/ms948028.aspx I remember
thinking two things when I looked at the language:

1. Gee, nice choice of an acronym for your language. way to complicate
my websearching  (ok I guess I tend to just search for ocaml stuff,
but still it is a bother)

2.  I could pretty easily write implementations of much of this for
other platforms. (major sticking point I think would be database
stuff)

Cheers,
Bryan Rasmussen