dateline should be a member of model.pLike.front

[dariok]

Currently, model.pLike.front contains byline but not dateline. dateline is in model.divBottom (via model.divWrapper).
This means that the dateline has to appear after all other content of that model – which may not reflect its true position on the page.

[sydb]

But model.pLike.front isn’t used by anything but <front> and <back>, is it? So if you were encoding front matter (or back matter) that was not divided up somehow (thus no <div>s), would there be a situation in which <dateline> was really more appropriate than <docDate>? If so, I see no reason not to include <dateline> in model.pLike.front.

That said, your argument that “the <dateline> has to appear after all other content of that model – which may not reflect its true position on the page” makes me think you are worried about where a <dateline> can go in a <div>. If this is your problem

1. Please post here some specifics of the problem.
2. I don’t think putting <dateline> into model.pLike.front will solve it.

[dariok]

I found this while I was batch transforming about 3,000 files from P4 with various styles of encoding.
The files contain protocols and sometimes letters; usually, there is a front which contains some information about the text, in this order:

• 1 title-like string that goes into docTitle/titlePart
• 1+ an idno-like string with the archival identifier, file number and/or an internal reference number which are considered a part of the title;
• the date when and place where the session took place;
• 0-1 docEdition-like statement;
• 0-1 subjects
• 0-1 statements referencing prior letters or protocols

The date and place refer to the session the protocol (or other material) is for. As these protocols go through several revisions before being finalised and accepted, this is not exactly the docDate (the date the document was created in the present form, which may be several weeks later).
Hence, I thought a dateline with placeName and date might be better here.
However, the order docTitle, dateline, docEdition is not possible; dateline has to go after docEdition as it is part of model.divBottom. A byline, though, would be possible in that location as it is a member of model.pLike.front.

The other point is that I think it is inconsistent that the byline is in said model while dateline is not. byline may contain docAuthor and appear where it is more appropriate than the latter alone – the examples in the GL use byline where there is a longer string on the title page containing the author as it would be incorrect to tag the whole line as docAuthor.
Similarly, dateline may contain docDate yet it may not appear where it is more appropriate than docDate alone. I think this inconsistency should be resolved.

[sydb]

Seems pretty convincing to me. Does anyone want to argue that

      <titlePart type="session">
        <placeName>Prague</placeName> face-to-face meeting,
        <date when="2017-02">Feb 17</date>
      </titlePart>

should be sufficient?

[tuurma]

F2F subgroup recommends aligning dateline with byline

[martinascholger]

Council at F2F Graz agrees with the equivalence between byline and dateline; where one is available, the other should be. Add dateline to model.pLike.front, and add a good example showing both byline and dateline together.

[peterstadler]

some content model seems to be broken? see https://jenkins.tei-c.de//ob/TEIP5-Test-dev/376/parsed_console/