I've was asking Svante a few questions off-list, but may as well bring this back here.

I'm not sure exactly if or how it would relate to the notion of "filter" in this sense, but here is why we're interested in XSLT 2.0 at the bibliographic project:

Right now, citation and bibliographic support in OOo is really bad. It needs to improve greatly or OOo will never have a real chance in higher ed and research.

To do that, among other things, we need to change how the formatting happens to be not only more feature-full, but also much more dynamic. Formatting needs to be able to be regenerated -- in a completely different style -- if need be, without any source modification.

So, step one is changing how citations are coded internally in the file format. That's been approved. Now, citations will look like this:

<cite:citation xmlns:cite="http://purl.org/NET/xbiblio/cite";>
  <cite:citation-source>
    <cite:biblioref cite:key="doe99a" cite:style="year">
      <cite:detail cite:units="pages" cite:begin="23" cite:end="24"/>
    </cite:biblioref>
  </cite:citation-source>
  <cite:citation-body>
    <span class="citation">(1999: 23-24)</span>
  </cite:citation-body>
</cite:citation>

I thus want the citation-body content to be generated by XSLT. I want that XSLT code, in turn, to be this project I'm working on:

        http://xbiblio.sourceforge.net/citeproc.html

This has the advantage that it is a general solution to citation and bibliographic formatting (useable outside of OOo), and that its styling language is also general.

What I'm wondering about is how to make this sort of integration as seamless as possible. I assume some internal changes would need to be made to OOo, but am not sure exactly what.

The way CiteProc works with flatfile documents like DocBook is that the XSLT is run on the document, and extracts all the unique citation pointers, then assembles a single url query it sends to the database that says "give me all of the bibliographic records that correspond to these idenfitiers."

The XSLT sucks those into memory, and then does a bunch of work on them, spitting out the formatted references.

So how could that work in OOo?

Bruce


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



Reply via email to