Spent most of the day working on the second article, which raises all sorts of interesting issues. Among them are these:

• The article has one place where there are two tables, each with their own captions, and an overall caption for the pair of tables. The only way I can think of to capture this is to have the tables as components of a <figure> element. This has the added bonus that it reduces the number of block elements that appear in a paragraph, and enables us to say that all breakout/embedded components (images, graphics, tables etc.) are (from a markup point of view) figures, and appear in a <figure> tag.
• Another such element in the document consists only of text, being a representation of a form filled out by students. This, IMHO, ought actually to be a scan of the original document, but there are situations in which I can imagine text being used in this way. There is a <floatingText> element in TEI, but this is not really floating text; instead, I'm marking it up in an <ab> tag, which is itself inside a <figure> tag.
• All this has brought to light also the issue of caption placement (it should be above tables and below figures in APA), and also numbering (which, the APA suggests, should be distinct for tables and figures, with Figure 1, Figure 2 etc. alongside Table 1, Table 2). Our markup needs to be flexible enough to accommodate not only this but other systems prescribed by other styles.
• The "form" illustration mentioned above contains some horizontal lines (for signing and dating). I'm not sure how I'm supposed to do those in TEI; that'll need some research. I've looked around a bit, but I can't find anything so far.
• I had to add the tagdocs module to the schema to get the <code> tag, but I stripped out most of its components, and took the opportunity to strip out some stuff from elsewhere at the same time, so the resulting schema came in a bit smaller. That's not a bad approach -- every time you add or change something, take a look through one or two of the modules you already have and see if there's anything you feel you can dump.
• Had to add <hi rend="compLabel"> to handle the captions of buttons, menus etc. in computer GUIs. There might be more of this kind of thing.
• Lots of back-and-forth on the TEI list about my suggestion to allow <ref> as a child of <biblStruct>, so we can include the URIs of electronic references.
• Also lots of discussion over whether lists can/should appear as siblings of paragraphs, or whether they might as well be deemed to be inside paragraphs (perhaps as the only constituent). My feeling is that my schema would be much simpler if everything like that had to be a child of <p>.