Agenda for and Notes of February 24, 2009

Agenda

• L1 and L2 — should they be combined?
• Whether numbered or unnumbered divisions are used, the @type attribute of the division element is not recommended at L1, is optional at L2, is recommended at L3, and required at levels 4 and 5.
• Use of <floatingText>: Should we recommend or require use of <floatingText> in L3 and above? In L4 and above? In L5 only?
• L4 Updates
  • Name Tagging in L4 — Do we recommend normalization and if so, how?
• Updates from other levels? Any other updates (confessional moment)
• Update: Will DLF sponsor the TEI SIG meeting?
• DLF BOF proposal?

Notes

• KH, NS, SB, PW, CP, MD, RW
• will not be attending: MG, LM (maybe late)
• started 13:07, delayed a few minutes to handle an echo
• SB taking notes
• ended at 13:58

Actions

• SB: re-word the “no human intervention” part of L1 description
• CP: provide an example encoding of <group>
• All: read or re-read MD's e-mail “Addition of "name" tagging to Level 4” sent 2009-02-21 15:03-05 and reply all with thoughts

L1 and L2 — should they be combined?

• confirmed agreement via e-mail that we do not wish to combine levels 1 & 2
• should clarify the “no human intervention” part of L1: it means no intervention in the initial tagging of structure

the type= attribute of the division element (whether numbered or unnumbered) is not recommended at L1, is optional at L2, is recommended at L3, and required at levels 4 and 5

• general consensus that yes, we like this idea
• decided to change current wording to say type= “not applicaple” (or some such) for L1

Use of <floatingText>: Should we recommend or require use of <floatingText> in L3 and above? In L4 and above? In L5 only?

• agreed we like idea of adding a series of examples of a single text encoded at each level (1–4)
• agreed to add <floatingText> to L3, but remove <closer>.

L4 Updates

• agreed to provide links to Guidelines only to section level in References section for each level
• 5.4.4 — NS & MG will be talking 09:45 on Fri 02-27, others invited.
  • change wording for <hi>: use to indicate change in rendition when a more specific element is not being used
  • move <hi> below others
  • re-organize rows
  • replace <q> w/ <said> and <quote>
  • add <flouatingText>
  • we'll work on required vs optional vs recommended later
  • just say “<titlePage> and appropriate child elements from <ptr/>”
  • on detailed examples: no clear consensus, but we all do agree that they are not an important focus of current effort
  • agreed to include <group> in L4; add an example into prose (e.g. “The book A by B is a common example of a work with such a structure”); CP to provide an example encoding

Name Tagging in L4 — Do we recommend normalization and if so, how?

We should read MD's recent e-mail and discuss via e-mail

Updates from other levels? Any other updates (confessional moment)

No other level updates were presented.

Update: Will DLF sponsor the TEI SIG meeting?

• we do not know whether or not there will be a DLF-sponsored SIG meeting
• Matt was handling, but MD may also approach Barry; KH suggests Wed afternoon instead of Mon morning

DLF BOF proposal?

• BOF proposal circulating