Ad-hoc committee on encoding of bibliographic citations

= Charge =

At its meeting on 2010-02-07, the TEI Council discussed bug 2714682 and reached consensus that biblScope should not be allowed as a child of imprint since the prose definition of the imprint element does not include such content as might be included in one or more biblScope elements. Laurent Romary, Martin Holmes, and Kevin Hawkins were charged with writing a proposal to make it clear how to use biblScope for various types of bibliographic citations. The proposal should include corrected, annotated (with XML comments) examples for the Guidelines of encoding various types of citations in biblStruct (and maybe also bibl and biblFull). It was suggested that the ad-hoc committee also look at how citations are handled in other encoding schemes.

= Background =

The TEI Guidelines offer three elements for bibliographic descriptions:


 * bibl -- no enforced content structure
 * biblStruct -- structured citation follows a TEI content model
 * biblFull -- structured citation with a content model similar to fileDesc

These elements may be used for a number of different purposes in a TEI document. They may occur within the  to describe the source of a TEI document (as part of the metadata) or within the to describe citations appearing as content. As with other elements used in the body, any of these three elements could be used either:


 * to represent citations in a source document (such as a pre-existing print document)
 * to encode citations as part of a publishing process (such as a manuscript of a book to be published), whether destined for print publication, online publication, or both.

Some people distinguish these as two different purposes for markup (which Wendell Piez called "retrospective markup" versus "encoding done for the sake of fitting data to a particular application"). In discussing the elements for bibliographic purposes, one's opinion might be affected by whether one assumes the markup will be used for retrospective digitization or for a publishing workflow.

Encoding citations as represented in a source document (such as a pre-existing print document)
When encoding a citation as it appears in a source document, most users prefer to leave the transcribed text in the order it is read on the page when tagging; therefore, any elements used for bibliographic descriptions need to be flexible in their internal structure. bibl will clearly work for this purpose, and biblFull will not (unless the source document contains only ISBD-compatible citations without certain errors). biblStruct has a complicated content model whose allowed order of elements seems to map well onto common citation formats (at least those used in European languages). However, when including page numbers, it's not clear when to include a biblScope as a child or sibling of imprint.

Examples in the Guidelines sometimes include delimiting punctuation in the elements, which is sensible when encoding citations as represented in a source document. Users often wish to represent the original document as faithfully as possible, including inconsistent punctuation, so they don't want to insert any punctuation automatically. Leaving in punctuation is also simpler when converting from print or electronic source files.

Encoding citations as part of a publishing process (such as a manuscript of a book to be published)
When encoding a citation as part of a publishing process, the usual desire is to enforce uniformity of citation style through use of markup. If a particular citation format (MLA, APA, GOST 7.1, etc.) is to be used, it is likely that the possible combination of citation components in that format does not match perfectly with the content model of any of three elements for bibliographic descriptions. biblFull likely requires too much detail for most purposes, bibl would allow for more flexibility of encoding structure than is required for the citation format being used, and biblStruct is already too constrained for certain use cases (like a work without an an author, editor, or other responsibility, or like a monograph part of a larger monograph series). Constraining the content model of bibl would break TEI Conformance (?), so a user might instead maintain the TEI content model for the element but use a Schematron schema or other outside tool to check that the citation is encoded as desired.

It is advised not to include delimiting punctuation in citations encoded as part of a publishing process but rather to insert these through a stylesheet, thereby guaranteeing not only consistent use of punctuation but also making it easier to adapt to a different citation style in the future.

Proposed revisions to P5 presented Dublin
Martin, Laurent, and Kevin prepared a proposal for revisions to §3.11 and §2.7 for consideration by the TEI Council during its meeting in Dublin in April 2010.

After much discussion, it was decided that Lou would make revisions in SourceForge to parts that he recalled Council agreeing to, leaving Martin, Laurent, and Kevin to present a slimmed down proposal, with corrections noted during discussion in Dublin, for consideration at a future Council meeting.

Activity since the Dublin meeting
Lou made changes to the Guidelines based on the non-controversial parts of the Dublin proposal in time for TEI P5 release 1.7.0:


 * http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Guidelines/en/HD-Header.xml?r1=7436&r2=7521
 * http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Guidelines/en/CO-CoreElements.xml?r1=7436&r2=7521
 * http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Guidelines/en/CO-CoreElements.xml?r1=7933&r2=7964

The committee members agreed to break their proposal into individual SourceForge tickets to simplify discussion:


 * 2987832: date within biblStruct -- Proposal was withdrawn and replaced with proposal to add as a child of, which was implemented in February 2011.
 * 2987241: and should be allowed in -- In the course of the comments, the proposal was revised to requesting that be allowed within . Was implemented in April 2011.
 * 2976715: resp -> model.respLike in biblStruct. and other things. -- There were difficulties in implementing this, so it was decided not to implement it.
 * 2714682: biblScope should be in Imprint or not? (biblStruct) -- This proposal will be postponed pending resolution of the above items.

Once these are resolved, the committee members will return to their proposal made in Dublin to see if any revisions are still needed to the relevant chapters of the Guidelines.

Proposed future revisions to the Guidelines (which will break backwards compatibility)
Examine content model for biblStruct and citations standards like Z39.29 derived from ISBD. Consider introducing revisions that would break backwards compatibility, such as the following:

a. Clarify §3.11.2.1 and the definitions of the elements monogr and series to say that a citation for an article in a journal should be encoded using analytic and series, not analytic and monogr. Change content model of biblStruct so that either monogr or series is required (not only monogr, as is the case currently).

b. Have analytic, monogr, series contain only information about the titles of these works with other metadata in elements that are children of biblStruct. For example, a citation to a portion of a journal article that would be formatted in print according to Z39.29-2005 as:


 * Gardos, George; Cole, Jonathan O.; Haskell, David; Marby, David; Paine, Susan Schniebolk; Moore, Patricia. The natural history of tardive dyskinesia. J Clin Psychopharmacol. 1988 Aug;8(4 Suppl):31S-37S. Table 3, Occurrence in the United States; p. 32S.

might be encoded like this:

 Gardos, George Cole, Jonathan O.  Haskell, David Marby, David Paine, Susan Schniebolk Moore, Patricia The natural history of tardive dyskinesia J Clin Psychopharmacol 1988 Aug 8 4 Suppl 31S-37S Table 3 Occurrence in the United States 32S </biblStruct>

c. Prescribe use of BibTeXML or another XML format for citations for use with citations. Such elements would used the other scheme's namespace within a TEI document, much like MathML or SVG can be used in P5.