You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should reserve the tei:profileDesc/tei:textClass mechanism for mods:subject and mods:classification, as implemented here.
The proper representation for mods:relatedItem/@type=series is not tei:creation, but tei:msDesc/tei:msIdentifier/tei:collection IMO, as implemented here.
In addition to the above, when validating against TEI itself (xmlstarlet val -r tei_all.rng tei.xml), one can immediately see lots of invalidities caused by wrong order of elements. (For example, under tei:publicationStmt, we need publisher < date < pubPlace < idno < availability, whereas we do add_place < add_date < add_publisher < set_availability < add_identifier.)
The proper representation for mods:relatedItem/@type=series is not tei:creation, but tei:msDesc/tei:msIdentifier/tei:collection IMO, as implemented here.
After consultation with @tboenig, it turns out that with a few modifications we can reach full compatibility with the DTABf, almost:
extent
→biblFull
editionStmt
one level highertitlePage
→div type="titlePage"
The text was updated successfully, but these errors were encountered: