search

GVogeler / CEI2TEI

This repository documents the proposal to insert diplomatics concepts into the framework of the TEI-P5 (http://www.tei-c.org/Guidelines/P5/), based on the experiences of the Charters Encoding Initiative (http://www.cei.lmu.de)
6 stars 7 forks source link

Classifying references from Fontenay charters #51

Closed NTsch closed 1 year ago

NTsch commented 4 years ago

Came across cases like the following in the Fontenay charters:

<witness n="b">
    <bibl default="false" status="draft">{Jobin, 1891 #5154}, p. 613</bibl>
</witness>
<witness n="b">
    {Jobin, 1891 #2360@p. 618-620 n° 50}
</witness>

I'm bringing them in as cei:witness for now, but, being printed sources, these seem like they would be a case for cei:listBiblEdition (which becomes listBibl type="edition") in CEI2TEI. Would this be 'ontologically' inconsistent?

GVogeler commented 2 years ago

See https://github.com/icaruseu/mom-ca/issues/1073

GVogeler commented 2 years ago 
<witness n="b">
    <bibl default="false" status="draft">{Jobin, 1891 #5154}, p. 613</bibl>
</witness>

describes a textual witness in print - not an scholarly edition, so it makes sense to have it as a sub-element to cei:witness. The current model of cei:witness is modelled similar to tei:msDesc, i.e. assuming an archival source (therefore, including cei:archIdentifier, cei:auth, cei:nota, cei:rubrum etc.). Adding cei:bibl would make unclear, if cei:witness/cei:bibl contains a bibliographic information talking about the witness or the witness itself. When converting cei2tei we can infer only from the existence of cei:archIdentifier (and similar) how to handle cei:bibl. ToDo: