Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#465 Bad punctuation in one <bibl> example

John P. McCaskey

The Guidelines are generally good about saying <bibl> is for marking up text and the encoding should accordingly include inter-component punctuation, and about saying <biblStruct> or <biblFull> are for recording data fields and disallow inter-component punctuation.

But the following example, in and meant to illustrate <respStmt>, fails to follow this Guideline.

<author>Lominadze, D. G.</author>
<title level="m">Cyclotron waves in plasma</title>.
<resp>translated by</resp>
<name>A. N. Dellis</name>
<resp>edited by</resp>
<name>S. M. Hamberger</name>
<edition>1st ed.</edition>
<publisher>Pergamon Press</publisher>.
<extent>206 p.</extent>
<title level="s">International series in natural philosophy</title>.
<note place="inline">Translation of:
<title xml:lang="ru" level="m">Ciklotronnye volny v plazme</title>.

This encodes

Lominadze, D. G. Cyclotron waves in plasma. translated by A. N. Dellis edited by S. M. Hamberger 1st ed. Oxford: Pergamon Press. 1981. 206 p. International series in natural philosophy. Translation of: Ciklotronnye volny v plazme.

One or two other examples are questionable. This one is more clearly problematic. Either the punctuation and capitalization should be changed so something sensical is encoded, or the <bibl> should be changed to <biblStruct> and punctuation removed.


  • Martin Holmes
    Martin Holmes

    I don't think we really prescribe that no-one shall use <bibl> without punctuation, do we? The example seems perfectly OK to me. People (like me) who are frustrated by the structural constraints of <biblStruct> might well use <bibl> in a database-like manner to encode structured references, perhaps enforcing their own structure through customizations, and still have TEI-compliant code.

  • > I don't think we really prescribe that no-one shall use <bibl> without punctuation, do we? <

    No, the opposite. The prescription I see in the paragraph "By contrast, bibl . . . punctuate the data" is that <bibl> should include punctuation,

    Maybe someone prefers to use <bibl> to encode database fields, because biblStruct and biblFull are too constraining. I can see the argument for that (though the Guidelines don't condone it). But then note the encoding decision, be consistent, and drop the punctuation completely.

    There is just nothing a non-human consumer can do with that example. And a human consumer would need to consider each element, one by one, and try to divine what was intended and what to do with what is there.

    >perhaps enforcing their own structure through customizations <

    Unless otherwise noted, examples in the Guidelines assume uncustomized TEI, right?

  • ah, my favourite bugbear. I am with you all the way here, John. Those half-punctuated <bibl>s drive me mad. <biblStruct> for data, <bibl> for encoding punctuated bibliographies.

  • Lou Burnard
    Lou Burnard

    • status: open --> closed-accepted
  • Lou Burnard
    Lou Burnard

    This example is taken from an ISO standard, and therefore really ought to respect the punctuation and layout (including the way initials are cited) of the original. I've revised it accordingly.