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.

I also have some (very young) code that builds an administration
interface for each resource class from RDFSchema data (also stored in
the same RDF database). And since the RDFS is also just a collection of
RDF statements, the same interface can be used to edit the RDFS to
create new classes, properties, datatypes, etc.  Sort of a
self-describing database.

The RDF processing library I currently use is Redland
(http://www.redland.opensource.ac.uk/) with its Perl bindings.  Redland
 serializes to a *very* simple RDF-XML format which is actually fairly
easy to transform using XSLT once you get used to using key() calls.
Theoretically other RDF storage libraries could be used, though I find
Redland is the most complete (and fast!) one out there right now.  It
can be a bit difficult to install though.

Like I said the code is still young and immature, but I'd be willing to
share what I have if anyone's interested.

--
Jason Johnston, Web Developer
http://lojjic.net




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



Reply via email to