Working with the BibClass DTD
From DLXS Documentation
| Line 1: | Line 1: | ||
[[DLXS Wiki|Main Page]] > [[Mounting Collections: Class-specific Steps]] > [[Mounting a Bib Class Collection]] > Working with the BibClass DTD | [[DLXS Wiki|Main Page]] > [[Mounting Collections: Class-specific Steps]] > [[Mounting a Bib Class Collection]] > Working with the BibClass DTD | ||
| + | <hr> | ||
The DTD for BibClass ([[bib.dtd]]) was designed to achieve several goals simultaneously: | The DTD for BibClass ([[bib.dtd]]) was designed to achieve several goals simultaneously: | ||
Revision as of 19:22, 14 September 2007
Main Page > Mounting Collections: Class-specific Steps > Mounting a Bib Class Collection > Working with the BibClass DTD
The DTD for BibClass (bib.dtd) was designed to achieve several goals simultaneously:
- Succinctness and simplicity:
- The bib.dtd uses short element and attribute names. Large collections like the index to the London Times (several gigabytes, and more than 10 million records) will balloon in size without either minimization or other strategies to reduce markup overhead.
- Similarly, because BibClass is not attempting to replace complex bibliographic systems like those based on MARC, the DTD does not provide the encoder with a large tag set and the ability to support complex representations of bibliographic information.
- Likewise, it does not offer mechanisms like indexing skip characters, sort values, etc.
- Maximizing precision: Because "precision" is integral to bibliographic retrieval, especially with millions of records, the bib.dtd has a fairly "tight" data model. In contrast to data models like Dublin Core, it frequently constrains which fields may or must be used, and what sort of information is in those fields.
- Accommodating pre-existing structures: It was essential that BibClass support mapping of other descriptive metadata into its data model. Consequently, the bib.dtd accommodates all fields and content in Chadwyck-Healey bibliographic databases, many key MARC fields, core information in the TEI header, and typical bibliographic information found in local database projects.
BibClass was intended for simple applications and was not intended to replace large, complex representations of bibligraphic information (e.g., the MARC record). We will continue to work with others to modify and extend the DTD, but must work to keep the principles outlined above as determining characteristics. Similarly, we will consider replacing the bib.dtd with another, more standard DTD should it accomplish the ends set out with the bib.dtd.
We have created a simple tree structure of bib.dtd, for an alternate view at how BibClass elements are related.
The BibClass DTD is also available as a schema: bib.xsd
