1.1 Examples In The Guidelines.

In these guidelines we will give a number of examples. It should be stressed that the examples are meant to illustrate the issues being discussed in the section where they occur. They are not necessarily complete and ready to be copied into the editions. To make the examples legible extra tabs, spaces, or linefeeds may have been added.

5.1 TEI Elements: <bibl>, <biblStruct> and <biblFull>

According to the TEI Guidelines, three elements may be used to encode bibliographical information¹. In the bibliography, we will use the <biblStruct> element to group the information pertaining to a single item. The same information might be encoded using the <bibl> element. However, the <bibl> element may contain text besides subelements like <title> or <author>. As a result, there is no guarantee its contents will be sufficiently structured for automatic processing.

The <biblFull> element is strictly structured and seems geared towards extensive description of source features, rather than the simple bibliographical information we are interested in. As well, the <biblFull> can not contain the <analytic> elements needed to describe journal articles.

5.2 TEI Elements: <analytic>, <monogr>, <series>

When describing books, articles, or a series we will follow the procedures outlined in Text Encoding Initiative, 6/10/2/1. Articles will be encoded as <analytic> elements; the journal or book containing the article will be described in a <monogr> element following the <analytic> element, both will be subordinate to the single <biblStruct> element. Where applicable, a <series> element may follow the <monogr> element to indicate the series in which the book was published.

To avoid repeating the same information several times the procedure will be streamlined, this is outlined below.

If we want to record that an article was published more than once, we will encode this using more than one <monogr> element within a single <biblStruct> element.

5.3 Scopes Within Bibliographical Items

A scope within a bibliographical item such as an article within a journal, or a page range in a book, will be encoded as a <biblScope> element². We will use the <biblScope> element’s type attribute to encode, in detail, the meaning of the scope being described. For example:

<biblScope 
  type="ccyy/inst/mon/pb-pe">1969/184/dec/343-346</biblScope>

In the type attribute we will use the following values, separated by slashes:

<biblScope type="bk">10</biblScope>

<biblScope type="vol/ccyy/instb-inste/pb-pe">
 56/1998/3-4/2-3
</biblScope>

<biblScope type="ccyy/inst/mon/pb-pe">
 1969/184/dec/343-346
</biblScope>

<biblScope type="pp">13, 14-17</biblScope>

<biblScope type="ccyy/toappear">2002/dummy</biblScope>

5.4 References to The Bible

For the present, a single item in the bibliography refers to the Bible:

<biblStruct id="bible" ana="interpbco">
 <monogr>
  <title type="main">Bible</title>
  <title type="parallel">Bijbel</title>
  <title type="short">Bible</title>
  <imprint/>
 </monogr>
 <note type="webaddress">
  <xptr type="websitestart" doc="biblestart"/>
 </note>
</biblStruct>

The website we refer to enables direct access to a passage in the Bible by book and verse number. It also allows the reader to select from various translations of the passages.

The sites disadvantage’s are that there is no Dutch translation available, and that apocryphal books are missing. An advantage over other sites is that it is mindful of differences in verse, and chapter numbers between the Vulgate and other traditions.

When referring to a passage in the bible, we will use the standard modern chapter and verse numbers. The values to be used in the type attribute of the <biblScope> element are described in the table above: bk, ch, v, vb-ve, ed. For example:

To refer to Deut. 6
<xref doc="biblio" rend="ref" type="source" from="id (bible)">
 <bibl><biblScope type="bk/ch">de/6</biblScope></bibl>
</xref>

To refer to Deut. 6:1
<xref doc="biblio" rend="ref" type="source" from="id (bible)">
 <bibl><biblScope type="bk/ch/v">de/6/1</biblScope></bibl>
</xref>

To refer to Deut. 6:1-2
<xref doc="biblio" rend="ref" type="source" from="id (bible)">
 <bibl><biblScope type="bk/ch/vb-ve">de/6/1-2</biblScope></bibl>
</xref>

The ed value may be used (optionally) to indicate which version of the Bible we refer to. The versions used at present include:

However, even when explicitly referring to the Vulgate, we will use modern chapter numbers. For example:

To refer to Ps. 119:8 in the Vulgate Bible 
 (there known as Ps. 118:8):
<xref doc="biblio" rend="ref" type="source" from="id (bible)">
 <bibl><biblScope type="bk/ch/v/ed">ps/119/8/vulg</biblScope></bibl>
</xref>

The Bible's book information is always in lower case. The abbreviations used for the Bible books were borrowed from the Online Bible. They are the following:

5.5 The People Involved in Producing a Book

<biblStruct id="august011845t" ana="interpbce">
  <monogr>
    <author status="debated"><name corresp="august01"/></author>
    <author status="debated"><name corresp="hugost01"/></author>
    <title type="main">De substantia dilectionis</title>
    <!-- etc. -->
  </monogr>
</biblStruct>

<list>
 <!-- etc. -->
 <item>
  <name id="schoon01" 
     type="pers">Schoonhoven, Florent van</name>
 </item>
 <item>
  <name id="schoon02" 
     corresp="schoon01" 
     type="pers">Schoonhovius, Florentius</name>
 </item>
 <!-- etc. -->
</list>

5.6 Referring to Other Elements

In a bibliography, often the same data has to be presented several times. An author’s name may be repeated on several items, or a journal title will be referred to in the description of several articles, etc.

It is clearly undesirable to repeat the information in the bibliography document(s). The main reasons to avoid this are:

• Repeating the data allows for making mistakes, if not in entering the data, then in changing them. Unavoidably names (etc.) which were meant to be identical will end up being different.
• Even if mistakes are avoided, having identical names will not make it clear to the reader that these names were meant to be identical and therefore, refer to the same person.

Wherever possible, we will not repeat information but rather refer to separate lists of names or titles containing the needed information.

The Guidelines which describe the following facilities to achieve this desired effect:

• The copyOf attribute may be used on any element. It’s value identifies another element within the same document. Use of the copyOf attribute is meant to state that the element’s content is equal to the content of another element that is referred to. In effect, it creates an exact copy of this element. (Text Encoding Initiative, 14/6). Using the copyOf attribute avoids entering the same information in several locations. However, the attributes semantics are not quite what we have intended. Using the attribute says that both elements should have identical content, but does not say that the elements describe the same object.
• The same objection holds for the sameAs attribute. It is used in the same way as the copyOf attribute and indicates the element content is actually equal to the content of the element to which it refers.
• The corresp attribute, 'points to elements that correspond to the current element in some way.' Text Encoding Initiative, 14/4/1). For the application we need, 'correspondence in some way' is certainly applicable. The disadvantage of the corresp attribute is its vagueness. To an outside observer the kind of correspondence the attribute is meant to convey, is not always immediately clear.
• The type of correspondence that needs to be established between elements of any kind, may be expressed explicitly using the <link> element. On the <link> element the type of correspondence (coreferentiality) may be indicated using the type atribute.
  This method, though effective, is rather cumbersome because the elements which are being linked both need to have id attributes.
• Specifically for <name> elements there exist the key and reg attributes. The reg attribute makes it possible to add a regularised spelling to a <name> element. For our purposes it is not helpful because we would like to store regularised spelling only once, and not with each occurrence of the name.
  The key attribute is meant to contain a type of database key identifying the intended person, which is exactly what we would like to di. The disadvantages of using the key attribute are that it is unavailable on other elements (<title>'s); as well the attributes value is of type CDATA (rather than IDREF), which means that errors in referring to names will not be discovered when validating the document.

Weighing the advantages and disadvantages of the solutions outlined above, we have decided to encode the relation of coreferentiality between elements in the bibliography using the corresp attribute.

This mechanism will be used to associate personal names with items in a list of personal names, to quote journal titles in the description of articles and to quote series titles in the description of books. In descriptive content we may associate mentioned titles with their own entry in the bibliography.

An example of a description of a journal article:

<biblStruct id="portem011975a" ana="interpbcv">
 <analytic>
  <author><name corresp="portem01"/></author>
  <title type="main">Miscellanea emblematica</title>
 </analytic>
 <monogr corresp="spieglet"><imprint/>
  <biblScope 
     type="vol/ccyy/inst/pb-pe">17/1975/3/161-193</biblScope>
 </monogr>
</biblStruct>

You can see that the <author> element is referring to a personal name elsewhere in the bibliography. The list of personal names will contain:

<item>
 <name id="portem01" type="pers">Porteman, Karel</name>
</item>

The <monogr> element also refers to a journal listed in the in the bibliography:

<bibl id="spieglet"><monogr>
 <title level="j">Spiegel der letteren</title>
 <imprint/>
</monogr></bibl>

The two empty <imprint> elements used in the <monogr> elements are there to conform to the TEI dtd which demands their presence.

5.7 Categorisation, Keywords and Subjects

It might be desirable to add keywords to some or all items in the bibliography, and to categorise the items in one or more respects. When the bibliography grows in size, this may help in keeping it manageable and to locate relevant items.

The TEI <keyword>-mechanism is only available in the <teiHeader>. To encode categorisations and keywords we will therefore use lists of <interp> elements, grouped in <interpGrp> elements which indicate the relevant category. The bibliographical items will use the ana attribute to point to the <interp> elements. At present, this mechanism is used to broadly classify the nature of an item such as: a bibliography, (edition of) source material, emblem study, a technical study or another study. We have also used the mechanism to describe an item’s media type.

Subjects like persons or works, which are discussed in secondary literature will often be entries in the bibliography themselves. Relationships of this nature may be encoded using the corresp attribute on the <name> or <title> element, as discussed above.

5.8 Titles

A <title>’s level (level attribute) is given implicitly by the <title>’s use within the <analytic>, <monogr> or <series> element. It will not be used, except on journal titles (level attribute with value j), to distinguish journals from other <monogr>’s.

The type attribute will be used as follows:

Titles of other works mentioned within the item’s description, as part of the title or in a description-type note, will be encoded as plain <title> elements. If the work which the title refers to is described within our bibliography, the corresp attribute will be used to associate the title to the relevant entry. If the bibliography describes several editions of the work being referred to, a reference will be made to the first included edition.

An example of a cross reference to a title from a <note>:

From the description of 'Princeliicke Deviisen':
<note type="description">Digital version of the Dutch edition, 
  which appeared in 1615. [...] Text, facsimile, 
  iconclass encoding of images. Hyperlinked to 
  <title corresp="paradi012000b">the French version</title> and 
  <title corresp="paradi011998a">the English version</title>.
</note>

An example of a cross reference to a title from another <title>:

<title type="main">De 
  <title corresp="veen--01amor">Amorum Emblemata</title> van 
  <name corresp="veen--01">Otho Vaenius</name> (Antwerpen 1608) 
  in de Britse en Duitse emblematiek
</title>

This last example also shows how a personal name should be cross-referenced from a title.

Using the titles in the bibliography, style sheets will construct hyperlinks and other references to the books in the bibliography. Generally, it will be undesirable for these references to end with a punctuation character. If a main <title> ends with a punctuation character which should be recorded in the bibliography, then it is desirable to add a <title> with type short without the final punctuation.

5.9 NOTES

<BiblStruct> elements may contain one or more <note> elements. These elements may be used for the following purposes:

Including reference to an online resource:
<list>
 <item>
  <xref doc="hugo--01nyap2">
   Lord, thou knowest all my desire [...]
   <bibl>
    <biblScope ana="interpembl" type="p">2</biblScope>
   </bibl>
  </xref>
 </item>
 <item>
  <xref doc="hugo--01nyaembl1-3">
   Have mercy upon me, O Lord, for I am weak [...]
   <bibl>
    <biblScope ana="interpembl" type="bk/embl">1/3</biblScope>
   </bibl>
  </xref>
 </item>
 <!-- etc. -->
</list>

Without reference to an online resource:
<list>
 <item>
  De Ziel smeekt [...]
  <bibl>
   <biblScope ana="interpembl" type="embl">11</biblScope>
  </bibl>
 </item>
 <item>
  De Ziel, rustende [...], waakt [...]
  <bibl>
   <biblScope ana="interpembl" type="embl">14</biblScope>
  </bibl>
 </item>
 <!-- etc. -->
</list>

<list>
 <item>
  <name corresp="cats--01">Cats</name>: 
  <bibl>
   <biblScope ana="interpdisc" type="pp">13, 69, 83</biblScope>
  </bibl>
 </item>
 <item>
  <name corresp="heinsi01">Heinsius</name>: 
  <bibl>
   <biblScope ana="interpdisc" type="p">83</biblScope>
  </bibl>
 </item>
 <!-- etc. -->
</list>

<note type="webaddress">
  <xptr type="websitestart" 
     doc="sluijt012001astart"/>
</note>

5.10 id Attributes

Some elements in the bibliography need unambiguous identification because we need to point to them, either from other files like our editons, or from within the bibliography (e.g. to make clear relations between items). The TEI dtd’s allow each element to have an id attribute which uniquely identifies the element within the document. The value which is used does not matter, as long as it is unique and conforms to the limitation of the XML name datatype. Nevertheless, because of mnemotechnical reasons, it is useful to have some conventions regarding the use of values for id attributes. In the bibliography, we try to stick to the following guidelines:

<name id="hugo--01" 
   type="pers">Hugo, Hermann</name>

<name id="muller01" 
   type="pers">M&uuml;ller, Wolfgang J.</name>

<name id="muller02" 
   type="pers">M&uuml;ller Hofstede, Justus</name>

alciat012000a

portem011975b

hugo--011971a

5.11 Media

The TEI Guidelines do not recommend a structured way of encoding the media type (paper, CD Rom, web site or microfilm) in a bibliographical description. The Text Encoding Initiative, 6/10/2/5 suggests using <note> elements.

We chose to use a more structural encoding, using the categorisation mechanism described above. There will be a list of media types encoded as an <interpGrp>; the <interp> elements will be associated with the bibliographical entries using the <biblStruct>’s ana attribute. If no such association is made, it will be assumed that the entry refers to a publication on paper.

5.12 Web Sites

Web sites will be encoded using <monogr> elements. The web site’s <title> will be taken from, in descending order of preference, (1) Dublin Core metadata embedded in the web page, (2) the HTML <title> element (if this gives the impression of being used with care), or (3) a title visually presented on the web site’s opening page.

Other data such as: <author>, <editor>, and <imprint> information may also be found inspecting the site’s HTML source. The <publisher> is the person or institution that owns the web site.

For each web site the opening page is encoded in a <note> element with type webaddress, using an <xptr> element (cf. Web address notes). If desired, addresses of other pages on the site may be recorded using a <note> element with type contents (cf. Contents Notes).

5.13 Relations Between Items in the Bibliography

Between items in the bibliograpy, several kinds of relations may exist. For instance:

• work mentions or discusses other work
• work is a reprint of other work
• work is or contains material form other work
• work contains partial or complete facsimile of other work
• work contains partial or complete translation of other work

We have not yet attempted to systematically enter this kind of information in the bibliography. Using <title>’s with a corresp attribute in the description-type <note>’s relations between items may be encoded, but not classified.

There is one kind of relation between items which we do store in the bibliography, when work is an edition of other work. To this end, a <linkGrp> element contains <link>’s between <biblStruct>’s where the first element is an edition of the second one. For example:

<linkGrp type="isEditionOf" 
    targOrder="Y" targFunc="edition original">
  <link targets="ayres-011998a ayres-011683a"/>
  <!- etc. -->
</linkGrp>