On Wednesday 19 November 2003 12:47 am, Robin Berjon wrote:Do you have specific technical ideas that we should work on to facilitate this?
In my (short) experience building Mozilla+XUL applications, the thing I noticed the need for most was RDF input.
I'm confused :) You say RDF input here, but then later all you talk about is RDF output. Or is it RDF output from AxKit that's input to Mozilla?
It is true that RDF input (to AxKit) is hard, because of the flexibility of RDF's expression in XML. The same statement can be said in many ways, and that requires a specialised RDF parser. We don't currently have that in AxKit, and it would be really nice to have it available as a Provider (possible one providing a canonical view of RDF so that it'd fit better into the whole pipeline, which easier XSLT processing and so on).
If your problem is outputting RDF/XML from AxKit, then it really shouldn't be that hard (as you note later). Honestly, if you're talking about 4000 statements, that doesn't seem like much at all. True, with XSLT you have to output it all at once, but it's *really* fast, and the IO may actually be simpler (ie faster). If your current stuff is slow, you should give LibXSLT a try, it still surprises me sometimes :)
So, anyway, to answer the question, I would like to see better support for outputting RDF in AxKit. Perhaps I had better spit the RDF out as a result of an XSL transform, but somehow that never occurred to me before.
If you have specific needs going from an RDF model to its XML expression, then AxKit is lacking, but if it's just generating XML then you should have all the tools :) If the former, you might want to look at http://search.cpan.org/~zooleika/RDF-Simple-0.04/ which is a nice package despite the fact that it uses TT2.
-- Robin Berjon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
