Jon Noring wrote:
Marcello wrote:
Lee Passey wrote:
I also note that you encoded the glossary at the end of the work with <p> tags (naughty, naughty). Based on what I saw in the TEI docs I would have encoded it as follows:
<div type="glossary"> <head>Glossary</head> <list type="gloss"> <label>'Abdu'l-Bahá</label> <gloss>The "Servant of Bahá", Abbás Effendi (1844-1921), the eldest son and appointed Successor of Bahá'u'lláh, and the Centre of His Covenant.</gloss>
And it wouldn't have validated because gloss has no business inside list.
<snip good info on glossary markup>
There is a concept that Marcello and I have discussed of markup "levels". When it comes to something like TEI, there are so many ways you can add meta data it is completely daunting at times. In this example, yes, a more specific markup could have been used. But, in the final render, it works just fine as <p> blocks. Another example is a text with foreign words interspersed throughout. Often, those words would be printed in italics in the original book. Now, the simplest markup in TEI would be to put <hi rend="italics">around</hi> the word. But you could also mark the word with a <foreign lang="en">foreign</foreign> tag. In the final render, it would look exactly the same, but the second option provides more specific metadata. You could even go further by provide a translation of the foreign word inside the attribute (the markup escapes me at the moment). The markup that would cover what PG currently has would be want I would call a "level one markup" and that is the minimum, obviously, that a TEI could be marked to. Level two would be given a little more metadata, but nothing drastic. Maybe marking certain words as foreign instead of italics. Marking a letter as such instead of just a block of indented paragraphs. etc. etc. Level three would be going the extra, extra mile. It's the kind of markup I don't expect to see, but is possible in TEI. I expect most TEI documents we post will fall in level one or level two. Josh