Jason Johnston wrote:
Robin Berjon wrote:
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).

I've actually been working on something like this for a while now. A working version can be seen on my website (http://lojjic.net), which uses RDF for all content and metadata storage (for instance, take any page such as /blog/index.rdf.html and remove the .html to see the raw RDF-XML, .rdf.browse gives you a hyperlinked representation of the RDF, etc.). I have a Provider that queries the RDF database for statements about the requested resource and serializes those statements into RDF-XML, which I then transform via XSLT into the various presentation formats.

[snip more coolness]


Hey, that's interesting stuff! What are you waiting to put it up on CPAN
and advertise it more? You know the song, release early and often, and
all that ;)

--
Robin Berjon




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to