R.P.

tags, any spacing requirements? Do you mean a page-break tag ()? No, I do not expect any spacing to be necessary around tags: THE DEPARTMENT OF MATHEMATICS 3. This also goes for a interrupting a 'paragraph'; any spacing requirements when inputting this? No. You may leave a space after the tag if you wish, but it does not really matter if you omit it. 4. For the spacing rules for 'terminal punctuation', should it be one or two? Do you mean, should there be one space or two after a period, question mark, etc.? One space will be cheaper than two, so use one space. But perhaps I misunderstood the question. If you mean, should there be a space before the closing

tag, the answer is "no." 5. Figure tags will not have an attribute and/or ID? No. Just

... 6. No specific file naming convention for figures? No. We'll do that here if we decide to provide separate image files for the figures. At present, we are not doing that. 7. No scanning will be required for images? Just tag them? Not sure I understand this, but if you mean, will you need to produce scans of the figures, the answer is "no". Just flag their location in the text with the

tag. 8. Noted that we will use for the author of the article, while & will be used for the author and article title in the <bibl> field. When/where do we use the <docTitle> tag? I do not foresee any reason to use that tag for this project (the dtd is a generic one, designed for use on many different projects, not all of which will use all the possible tags.) 9. Also, when/where do <docDate> be applied? Ditto, I see no reason to use this tag for this project. 10. <lg> (line group) will not have any "attribute"? No, no attributes needed. 11. <i> (item) will not have an attribute on n="label"> if a presence is encountered? Sorry, I'm not sure I understand this. Are you asking about a list like this? FIRST SEMESTER 1. Advanced Algebra. 2. General Geometry. 3. Advanced Geometry. 4. Determinants. and whether it should be recorded like this? (1) <LIST> <HEAD>FIRST SEMESTER</HEAD> <ITEM N="1">Advanced Algebra.</ITEM> <ITEM N="2">General Geometry.</ITEM> <ITEM N="3">Advanced Geometry.</ITEM> <ITEM N="4">Determinants.</ITEM> </LIST> or like this? (2) <LIST> <HEAD>FIRST SEMESTER</HEAD> <LABEL>1.</LABEL><ITEM>Advanced Algebra.</ITEM> <LABEL>2.</LABEL><ITEM>General Geometry.</ITEM> <LABEL>3.</LABEL><ITEM>Advanced Geometry.</ITEM> <LABEL>4.</LABEL><ITEM>Determinants.</ITEM> </LIST> or like this? (3) <LIST> <HEAD>FIRST SEMESTER</HEAD> <ITEM>1. Advanced Algebra.</ITEM> <ITEM>2. General Geometry.</ITEM> <ITEM>3. Advanced Geometry.</ITEM> <ITEM>4. Determinants.</ITEM> </LIST> or even like this? (4) <LIST> <HEAD>FIRST SEMESTER</HEAD> <ITEM N="1">1. Advanced Algebra.</ITEM> <ITEM N="2">2. General Geometry.</ITEM> <ITEM N="3">3. Advanced Geometry.</ITEM> <ITEM N="4">4. Determinants.</ITEM> </LIST> A simple numbered list, with no complications, can be recorded using method (1); otherwise use the easier method (3). You are free to use method (3) throughout if you prefer: that would be simplest. 12. If a non-Roman text is encountered, <foreign> tag will be used. Any valid abbreviations for the attribute "lang"? Use the USMARC 3-letter language codes published by the Library of Congress at http://lcweb.loc.gov/marc/languages/ (These are identical to the 3-letter codes contained in the ISO standard 639-2; see http://lcweb.loc.gov/standards/iso639-2/langhome.html) 13. No other attributes for <table>? <TABLE> should not have any attributes. Bear in mind that just because an attribute is available in the DTD does *not* mean that it should be used. Most available attributes will remain unused. 14. Will the files be validated and not normalized? This was asked since we noticed different presentations of the tag elements in the samples. [In lower case, in upper lower case and in all upper case] Valid is fine. No need to normalize (we will do that in any case.) The variety of upper and lower case in my samples is simply the result of my typing the examples by hand. Your more automated procedures will presumably result in consistently upper- or lower-case tags, but it doesn't matter to us which it is. Attribute values should generally be lower case. 15. Text will be keyed/ouput as shown on the document? I don't understand this question. What document? 16. What would you like for the output file naming for each volume? You may either produce a single file containing the entire text (?called "umsurvey.sgm"), or a separate file for each volume (?called "umsurv_1.sgm" "umsurv_2.sgm" etc.). It doesn't really matter what you call the files, so long as it is something that makes sense to both of us! Regardless of whether or not you break the work up into multiple files, it needs to be easy to reassemble into one, valid sgml file. Each file should either be an sgml fragment that together form a valid sgml file when concatenated (in which case the top-level tag in each file would be <DIV1>), or each file should be a separate, valid, sgml file, that need only have their <!DOCTYPE>, <TEXT></>, and <BODY></> tags removed to be joined together (in which case the top-level tags in each file would be <TEXT><BODY><DIV1> ... </DIV1></BODY></TEXT>). ========================================================================== ---SET 5--- (3 questions about Index via Fax) [Answered without seeing the attachment, which didn't arrive.] 1. and 2. Each entry can be recorded as a simple <P>. Most entry words in italics can be recorded as <TITLE> (obviously, that excludes words like <I>see also</I>). 3. No special treatment for "see" and "see also" references.