Taco Hoekwater <taco <at> elvenkind.com> writes:

[.. snip ...]

> The next major release of the module (but don't expect a release
> anywhere this year) will indeed support MODS through citeproc:
>       http://xbiblio.sourceforge.net/citeproc/

As the author of citeproc (hi Taco!), let me just update people on recent
developments there, which are currently in the project subversion repository*,
but not yet officially released.

First, I have switched to using a particular RDF/XML as the internal
representation, and also therefore the primary input format. I will likely be
adding back a MODS input driver when I get a chance, but it's no longer the
focus. I will also be releasing a schema for this RDF representation for people
that need it.

The primary reason for this change is that in comparison to MODS, RDF has a
consistent model that makes it easier to model reference metadata. It's also
fundamentally a relational model, and so easier to integrate with relational
databases where needed.

Also, I am working with the OpenDocument Technical Committee on a plan to add
extensible metadata support using this RDF-based approach, so we hope to adopt
this in OpenOffice as well (I am co-project lead for the OOo bib project).

Second, I have started porting CiteProc to Ruby (and put a citeproc-py directory
in the repo for those python coders that might want to contribute), which might
integrate better with ConTeXt. (I suppose Lua might also be an option given the
integration with pdftex?) In any case, this will take me a bit of time as a) I
don't have much of it, and b) my coding skills aren't that great.

But the actual formatting code (Ruby, XSLT, etc.) is to my mind less important
than the logic as embedded in the XML citation style language I wrote to
configure the formatting.



* <http://svn.sourceforge.net/viewcvs.cgi/xbiblio/>

ntg-context mailing list

Reply via email to