http://tei.oucs.ox.ac.uk/EEBO/ lists some places where TCP EEBO texts have identified lines of poetry in a trailer. The attached picture demonstrates. We could deal with this by allowing <trailer>
to have more content. I suggest <choice>
<text/>
<ref name="lg"/>
<ref name="model.gLike"/>
<ref name="model.phrase"/>
<ref name="model.inter"/>
<ref name="model.lLike"/>
<ref name="model.global"/>
</choice>
Should these things all be
<trailer>
s though? There seems to be some confusion between <trailer> ("contains a closing title or footer appearing at the end of a division of a text") and <closer> ("groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division").I agree that <closer> probably should allow lines of verse, on this evidence, but I think we should keep <trailer as a phrase level thing.whoa! since when has
<trailer>
been phrase level? all the examples in the G'lines look very blocklike to me. The confusion between<trailer>
and<closer>
is a given, of course.Currently <trailer> and <closer> allow the same types of content.That seems right to me: I think it's up to the encoder to determine whether the nature of the thing being encoded is more like a <closer> or more like a <trailer>, but the same kinds of content might occur in either one. So, I suggest that any change(s) made to <trailer> also be made to <closer>.
Correction: above, I claimed that <trailer> and <closer> "may contain" all the same sorts of things--but PFS points out that this is not true: there is the very important difference that <closer> allows the textstructure elements <dateline>, <salute>, and <signed>, while <trailer> does not.
from A87070 is probably a better example.
Council discussion 11/13 accepted that
<trailer>
should allow more content, such as<l>