TEI writer extension (like element_citations for Jats)

[marviro]

The TEI writer does not keep the structured bibliographic information provided by citeproc.

This is possible using the JATS writer with the extension element_citations.

Would it be possible to create such an extension also for TEI?

The output, following the TEI documentation, could be something like:

<bibl type="article" subtype="book_chapter"
 xml:id="carlin_2003">
 <author>
  <name>
   <surname>Carlin</surname>
     (<forename>Claire</forename>)</name>
 </author>,
<title level="a">The Staging of Impotence : France’s last
   congrès</title> dans
<bibl type="monogr">
  <title level="m">Theatrum mundi : studies in honor of Ronald W.
     Tobin</title>, éd.
 <editor>
   <name>
    <forename>Claire</forename>
    <surname>Carlin</surname>
   </name>
  </editor> et
 <editor>
   <name>
    <forename>Kathleen</forename>
    <surname>Wine</surname>
   </name>
  </editor>,
 <pubPlace>Charlottesville, Va.</pubPlace>,
 <publisher>Rookwood Press</publisher>,
 <date when="2003">2003</date>.
 </bibl>
</bibl>

Is the extension the best way to go, or would you rather suggest to write a filter? I guess that in this case it makes sense to have an extension for the writer...

[tarleb]

I agree that an extension makes sense. Could you link me to the relevant docs for this?

Related issue: jgm/citeproc#132; cc @frederik-elwert.

[marviro]

Thank you!
I think everything is in the TEI Lite doc, here,

[tarleb]

I may have answered to quickly, because I didn't fully understand the difference between TEI and JATS. From what I gather, TEI citations are what's called "mixed citations" in JATS; there seems to be no equivalent to JATS element citations. That's problematic, because it means that we cannot just write the tags in any order, but that the CSL must always be applied. This isn't possible yet (and the subject of the citeproc issue linked above).

[marviro]

Ok, I understand. I am going to try to find a solution. If it is mandatory to apply a style, the other solution would be to create a filter which directly parses the structured bibliography, I guess? This is what you do with JATS (here)?

[YvesMarcoux]

@tarleb It's true that TEI's <bibl> are similar to JATS's "mixed citations". However, there is another TEI element <biblStruct> that is more structured and could likely be produced without applying the CSL. (<biblStruct> is not in TEI Lite, but it is in the "core" module of the TEI, so in theory in all flavours of the TEI).

Examples of this element are here: https://tei-c.org/release/doc/tei-p5-doc/en/html/examples-biblStruct.html

The element itself is described here: https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-biblStruct.html

Does that look like a promising avenue?

[tarleb]

That's perfect. I'll give it a try when I have time.

[frederik-elwert]

I think support for biblStruct would be nice, but it’s not necessarily a replacement for bibl support in many places. Not only TEI Lite, also the journal of the TEI (JTEI) schema only supports bibl. (Ideally, it would really be cool if pandoc supported JTEI as one of the output profiles, since I guess writing an article is still one of the main use cases for pandoc. Currently, the TEI output by pandoc is close, but requires some tweaks to fit the JTEI schema.)

Here’s the documentation for JTEI: https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back

[marviro]

I agree. But that would mean : 1) changing the CiteprocOutput class and 2) creating a new writer. I would definitely love that. (It's what we do with Stylo an online text editor that uses pandoc (+some xslt) to produce output for journals (also TEI journal) and this is why we need a structured bibliography.)