teiJournal

Created files for all the graphics in the 2nd article. The simplest way to do this is to select and copy them in OpenOffice, then do Acquire/From Clipboard in the GIMP. Saved them as JPEG at full quality.

The appendix issue is clear from the guidelines; each appendix should be a <div type="appendix"> inside the <back> element.

Got the metadata from the editors and created the header for the article, then started doing the markup. This article has two items we haven't yet dealt with, tables and images, as well as a number of inline features which raised questions that I referred back to the editors. The tables are straightforward grid tables, so they're easy, but the images are fairly low-res (inline in the wp document), so I asked for originals, and began the discussion of acceptable and desired formats. There are also issues relating to URIs mentioned in the text (should ref URIs be in footnotes?), and there are appendices at the end; I need to do more reading in the Guidelines about appendices to find out whether they go in the <back> element or not, and what they should actually be (<div>s, presumably, but it's not clear yet).

The biblio for the second article is shorter than that in the first, but it has some new features (electronic sources, conference presentations) for which I've had to devise markup strategies. That's now done, although some of these strategies may change if I get responses from the TEI list on some of my questions.

Picked up a copy of the APA Style Guide from the bookstore, and began looking at differences between that and Chicago. The guide is from 2001, and is supplemented by a PDF which is only available for purchase online, relating to electronic resources; we'll need that, but right now we don't have a credit card to purchase it, and I can't find it at the library (I've written to them to ask if they have it, and how to access it).

In the meantime, I started work on marking up the second IALLT document. The reference section of this one is shorter, but it has electronic references, which the previous one didn't, and I haven't made any decisions on how to mark up URLs and last-accessed dates yet. The TEI P5 Guidelines don't have any reference to bibliographic info for electronic documents either, so it's not clear how you're supposed to mark them up. I posted a query to the TEI list.

Spent a long time writing more explanatory material about on the markup instructions page, based on the tags used so far in the article completed today. Much more to do, but we're making progress.

Completed the markup of this article, in the process expanding my documentation, and also further refining the schema so that the @type attribute on <name> tags is now restricted to a fixed value list (with a default value of "person").

To check that all instances of <abbr> tags have counterparts which are part of a <choice> tag (meaning they have an expansion somewhere in the text):

The @target attribute on <ref> tags should always (so far, I think) point to the @xml:id attribute on a <biblStruct> tag in the bibliography. The editor doesn't check this automatically. There may be a way to force it to do so, using the schema, but I haven't figured that out yet. In the meantime, this piece of XPath evaluated as XPath 2.0 in oXygen will do the trick:

It gives back a list of any @target attributes that don't point to a <biblStruct> (a condition which suggests they're mistyped, or that a <biblStruct> is missing or has the wrong xml:id).

Did further work on the ODD file to add all the values proposed for different document types in the taxonomy here. The taxonomy itself needs to be updated, though; it assumes that the document type will be specified through a <classCode> tag, as was the case with the P4 projects, but I've decided to go with the @rend on the root tag instead, because a) it's actually a categorization which is made solely for the purposes of output rendering, and b) using an attribute list allows me to force its presence and restrict its values in a way that's helpful to encoders.

As I get further into marking up the first text, I've begun to flesh out the documentation for encoders. I've added a new Markup instructions document, which will grow as we go along, and also made some basic changes to the Textual features page, which overlaps it a bit. I've also posted a detailed query to the TEI list about whether block items such as lists and linegroups should ever, or need ever, appear outside of paragraphs. My sense right now is that they sometimes have to be inside paragraphs, but I can't think of any situations in which they must be outside paragraphs, so I might be able to customize the schema heavily to restrict them in this way, and make life simpler for encoders.