• editions of works (e.g. Moby Dick, The Electronic Beowulf)
• editions of authors (e.g. Collected Works of Thomas Middleton)
• archives of an author, movement, theme, with (extensive) ancillary material (e.g. The Blake Archive, Der junge Goethe)
• exhaustive corpora of a language and period (Anglo-Saxon Poetic Records, Thesaurus Linguae Graecae, Trésor de la langue française, ...)
• dictionaries (e.g. the Diction of Old English or the Dictionary of the Old Spanish Language), with ancillary materials [see corpora])
• modern corpora for linguistic work, with annotation (Penn TreeBank, Brown Corpus, Lancaster-Oslo/Bergen corpus, Corpus of London Teenage Language (COLT), British National Corpus (BNC), TIGer (Trees in German), ...)
• corpora for historical dictionaries (DOE, DOSL, Thesaurus Linguae Latinae Hiberniae)
• art-historical slide collections
• 3-D reconstructions (e.g. the Chicago Columbian Exposition, the Crystal Palace, ...)
• raw and digitally enhanced page images of an important manuscript (e.g. the Beowulf manuscript)
• A suite of Fortran programs that generate fugues; a set of fugues written by those programs (a) in the program's output notation, (b) in synthesized sound, (c) as recorded by the school's chamber orchestra
• A rhyme database covering verse of a particular author / language / period
• A set of dialect maps
• Transcriptions of field-linguists' informant interviews
• Important programs

An obvious interpretation is that this is simple tag abuse or human error, but the history of this description reveals it to be an example of a more general and complicated problem. This is the latest in a series of descriptions each derived from an earlier version:

1. A paper description accompanied the original photograph, which had been taken in 1938.
2. In 1998 the photograph was scanned for inclusion in an image database made available on the web [grainger99]. A metadata record for the photograph was entered into a relational database. The fields for that database were derived from the FGDC [Federal Geographic Data Committee] Content Standard for Digital Geospatial Metadata [fgdc98].
3. In May of 2005 an OAI 2.0 metadata record was derived from that database entry, via a mapping from the database fields into Dublin Core.
4. Several months later the OAI record was transformed via XSLT [XSL Transformations] into a form suitable for ingestion into a DSpace installation.
5. When the record was exported from DSpace, additonal DC [Dublin Core] metadata statements had been automatically added.

• validation
• supravalidation
• false-color proofs

oai2:OAI-PMH

(∃ q : OAI-request) (∃ r : OAI-response) (∃ s : OAI-server) (∃ t : moment)
( q = (℩ q : OAI-request)(models({ ./oai:request }, q))
    ∧ s = (℩ s : OAI-server)(uri_server({ string(./oai:request) }, s))
    ∧ t = (℩ t : moment)(xsd_lv(xsd:dateTime, { string(./oai:responseDate) }, t))
    ∧ (∀ x)(uri_server(x, s) ⇒ x = { string(./oai:request) })
    ∧ { . } = r
    ∧ served_response(q,s,t,r))

oai2:error

(∃ q : OAI-request) (models({ preceding-sibling::oai:request }, q)
∧ invalid(q)
∧ request_error(q, { string(@code) })
∧ ({ string(.) } ≠ "" ⇒ error_nldesc(q, { string(.) }) ) ) )

oai2:GetRecord

(∃ q : OAI-request) (∃ s : oai-server) (∃ d : string) (∃ i : oai-item) (∃ p : string)
(q = (℩ q : OAI-request)(req_resp(q,{ ancestor::oai:OAI-PMH }))
    s = (℩ s : oai-server)(resp_server({ ancestor::oai:OAI-PMH }, s))
    d = (℩ d : string)(request_identifier(q, d))
    i = (℩ i : oai-item)(item_id(i, d))
    p = (℩ p : string(p)(request_metadataPrefix(q, p))
∧ request_verb(q, "GetRecord")
∧ errorfree(q)
∧ isin_repository_item(s, i)
∧ hasformat_repository_item_format(s, i, p) )