NOTES.HTM (5474B)
1 <HTML><HEAD> 2 <TITLE>DPANS94 editorial notes</TITLE> 3 <link disabled rel="stylesheet" href="mpexc6.css"> 4 <style>@import url(mpexc6.css);</style> 5 </head> 6 7 <BODY> 8 <hr> 9 <h3>Editorial Notes</h3> 10 <p> 11 <b>V3.2 - December 16, 1996</b> 12 <p> 13 RFIs (requests for interpretation) added by Anton Ertl. Minor changes 14 in appearance of See: references in wordset glossaries. 15 16 <p> 17 <b>V3.1 - October 17, 1996</b> 18 <p> 19 Format of anchors changed so that Mosaic can see them. File suffixes 20 changed from .html to .htm to be more compatible with DOS/Unix. 21 22 <p> 23 <b>V3.0 - September 14, 1996</b> 24 <p> 25 26 This is a modification of Norman E. Smith's rendering of the draft standard 27 (see 28 his note below). Four changes have been made: (a) some errors have been 29 corrected, (b) minor changes in the style of HTML presentation have been 30 made to make it (hopefully) more readable, (c) hundreds of 31 crosslinks have been added, and (d) the naming conventions for the internal 32 sections of the document have been standardized so that it would be easy to 33 crosslink to this document. 34 <p> 35 For example if I, or anyone, were writing a message 36 on comp.lang.forth and I wanted to crosslink to the standard definition of 37 CATCH then I would write something like 38 <p> 39 a=href http://wherever.document.is.stored/dpans9.htm#9.6.1.0875 40 CATCH 41 /a 42 <p> 43 except that the phrases /a and a=href http:... are enclosed in angle brackets. 44 <p> 45 The standard is broken into 40 files: 46 <p> 47 <ul> 48 <li>one file, 49 dpans.htm, holds the preface and table of contents; 50 <li>seventeen files hold the 17 sections of the standard, 51 i.e. dpans1.htm thru 52 dpans17.htm; 53 <li>one file each for annexes B, C, D, E, and F, i.e. dpansb.htm 54 thru dpansf.htm; 55 <li>and seventeen files for annex A corresponding to the 17 56 sections of the standard, i.e. dpansa1.htm thru dpansa17.htm. 57 </ul> 58 <p> 59 60 The 61 subdivision of Annex A is the only irregularity in this scheme and this was 62 done both because it's not that hard to remember and also to break up what 63 would 64 otherwise be an unmanageably large annex. Within each file every subsection, 65 sub-subsection, and sub-sub-subsection, etc. is named following the same 66 conventions 67 that the draft paper document uses. 68 <p> 69 70 The only problem with this whole scheme is that some of the files, in 71 particular, sections 3 and 6, are large and therefore referencing 72 them online can take a long time. As a practical matter I would recommend 73 downloading all the files and using an html browser, like 74 netscape, to access locally. Another solution 75 that I am contemplating would be the breaking out of word definitions from 76 sections 6 thru 17 into individual files. This would entail a more 77 complicated cross-referencing, but I think it would still be manageable. 78 It would also mean that online access might become rapid. 79 <p> 80 81 Mark Andrew Amerman 82 <br> 83 mandrewa@cais.com 84 85 <p> 86 <hr> 87 <P> 88 89 <B>V2.1 - September 1, 1995</B> 90 <P> 91 92 This HTML version of this document was prepared by: 93 <P> 94 95 Norman E. Smith 96 <BR> 97 72745,1566@Compuserve.com 98 <P> 99 100 It was prepared from the Microsoft Word document posted by 101 the Technical Committee in early 1995. See their 102 <A href=dpans94.txt>readme</A> 103 file for the details and conditions of using the 104 postings. The Microsoft Word and Postscript versions of the 105 document are available on ftp://ftp.uu.net/vendor/minerva... 106 and a Postscript and 107 FPC hyperlinked ASCII version are 108 also available on Taygeta. 109 <P> 110 111 This second version has extensive 112 hyperlinks added. These are content related. The 'See:' 113 references to words link directly to their glossary 114 entry for example. Because the original document was well structured 115 and the conversion was to a proper HTML file, much of the 116 hyperlink generation can be automated. Even though little 117 had to be done manually, the large number of links and anchors 118 caused the additional was more work than I expected. 119 <P> 120 121 The files that make up this document were 122 created using Standardized Generalized Markup Language (SGML) 123 based autotaging software. For this reason, all of the files 124 also parse correctly with the current HTML Document Type 125 Definitions (DTDs). 126 <P> 127 128 I am planning a third pass at the document to 129 do a proper SGML representation of the word glossaries 130 and additional links in the text. At that 131 point, I will be able to generate a word glossary in just about 132 any format. 133 <P> 134 135 The process of spliting the document into managable (about 20k) 136 files, generating the Table of Contents, and inserting the 137 structural hyperlinks was done with a program written in Until. 138 <A href=ftp://taygeta.oc.nps.navy.mil/pub/Forth/Reviewed/until22.zip>Until</A> 139 is my almost-Forth, written in very generic C, that is also available 140 on Taygeta. The Until 141 <A href=http://taygeta.oc.nps.navy.mil/pub/until/until.html>Reference 142 Manual</A> can be browsed on Taygeta as well. 143 <P> 144 145 Lastly, thanks to the X3J14 Technical Committee for making the 146 Word version of the document available and to Skip Carter for 147 making space available on Taygeta for not only this document, but 148 the wealth of other Forth infomation available there. 149 <P> 150 151 <B>Changes:</B> 152 <P> 153 154 03/30/95 - V2.0 - Added hundreds of anchors and links. 155 <P> 156 157 02/28/95 - V1.2 - The 02/23/95 version used an old version of the table of 158 contents file with incorrect hyperlinks. This version corrects that. Sorry! 159 <P> 160 161 02/23/95 - V1.1- Added title page from original document that was lost during 162 initial 163 conversion per request of the Technical Committee. 164 <P> 165 166 Enjoy! 167 <BR> 168 Norman Smith 169 <P> 170 <hr> 171 </BODY> 172 </HTML> 173