Menu
▾
▴
#231 how to handle forme work
Tite does not include <fw> but also does not give guidance on how to handle running headers and footers. Should these be included in the markup or discarded? If they are included, how should they be encoded? (AccessTEI is currently including these, creating texts using <divN type="page"><head><!-- running header info here -->, with a <divN> at the beginning of each page!)
Use <fw>, obviously, if it's going to be captured at all. Using <div> is complete madness, as it will screw up the structuring of the text entirely. Unless you want to structure the text as a sequence of <page> elements, of course!
AccessTEI is changing their practice to no longer include <divN type="page">.
Will return to this once tickets 3136934, 3136935 3136936, and 3164403 are resolved, bringing canonical and Apex versions of Tite into alignment.
Setting as AMBER
Council reviewed this at June 2014 meeting. Agreed that if you dont have an <fw> element you cannot encode forme-work like material. If you want to encode such material, you should add <fw> to tite.