This file contains: (1) a list of slide titles (hyperlinked), and (2) contents of each slide.

1. Creating Electronic Technical Books
2. Creating electronic technical books
3. Overview
4. Why do electronic publishing?
5. How to do electronic publishing?
6. Who has done electronic publishing?
7. IETM I
8. IETM II
9. IETM: Class 1 (Electronically indexed pages)
10. IETM: Class 2 (Electronically Scrolling Documents)
11. IETM: Class 3 (Linearly Structured IETMs)
12. IETM: Class 4 (Hierarchically Structured IETMs)
13. IETM: Class 5 (Integrated Database)
14. IETM: Results
15. Zwillinger publishing experience
16. Aztec publishing experience
17. Abramowitz and Stegun: Survey results
18. Handbook of Mathematical Functions
19. Abramowitz and Stegun: Extensions I
20. Abramowitz and Stegun: Extensions II
21. Abramowitz and Stegun: Recommendations I
22. Abramowitz and Stegun: Recommendations II
23. Example of phases for G&R
24. Mathematical books

1. How to locate information (the linear read of a print book is not the ideal way to locate a chunk of information),
2. How to turn the text information into "chunks" (many screenfuls of material is not useful)
3. How to implement the product (avoid proprietary technologies)
4. How to define a framework for contributors (multi-platform conventions must be established and enforced)

• Review electronic publishing capabilities/desires
• Zwillinger (and Aztec) experience in print/electronic publishing
• User survey of Handbook of Mathematical Functions (A&S)
• Comments on Handbook of Mathematical Functions
• Recommendations

• Print versions getting too large (CRC has many 2000+ pages "handbooks")
• Too much information available (difficult to find desired result)
• Cheaper to produce, distribute, revise
• Electronic publishing allows new capabilities
• Frequently more useful than print version
• How information will be presented in future

• Desires
  • Want re-usable components
  • Can handle all types of relevant components (hyperlinks, mathematical typesetting, graphics, indexing, cross-references, numerical computations)
  • Easy to distribute (i.e., on net or CD-ROM)
  • Usable on large number of platforms
  • Avoid using proprietary software packages
  • Product should have "publish on demand" capability
  • Product should be easy to revise
• Conclusion
  • Use net browser
  • Construct product in HTML, Javascript, Java, and publically available plug-ins
  • Design investment required

• Government
  • "Interactive Electronic Technical Manuals" (IETM) (http://navysgml.dt.navy.mil/ietm.html/#example)
  • "Military Technical Manual Publish on Demand System" (http://www.scivis.nps.navy.mil/~reinvent/initiatives.html) is how the Navy fills orders for technical manuals.
  • NSF/National Records/Smithsonian has "digital library initiative" (announcement NSF 98-63)
• Industry
  • Software manufacturers: Mathematica notebooks, Maple worksheets, Macsyma notebooks
  • Publishers: CRC, AP, AW, etc
  • Education: Houston Community College System, Logal (http://www.logal.com)
• Other
  • latex2html converts "vanilla" LaTeX into "vanilla" HTML

• David Taylor Model Basin, Carderock Division, Naval Surface Warfare Center (CDNSWC) provides Navy with expertise in technical information publishing areas.
• They are the Navy's focal point for SGML (ISO 8879), the Navy DTD/FOSI Repository, and lead laboratory for the Tri-Service (Navy, Air Force, Army) effort in the standardization and development of Interactive Electronic Technical Manuals (IETM).
• An IETM is a technical manual designed for electronic-window display, with the characteristics:
  1. Format/style optimized for window presentation to assure maximum comprehension; format is "frame-oriented", not "page-oriented".
  2. The technical data is interrelated so that a user's access to the information is facilitated to the greatest extent possible, and is achievable by a variety of paths.
  3. The IETM display device can function interactively in providing procedural guidance, navigational directions, and supplemental information.

• MIL-M-87268 and MIL-D-87269 define the process for authoring and displaying IETMs. They implement an underlying strategy that separates the IETM source database from the electronic display of the formatted IETM. MIL-M-87268 defines how the IETM should look and behave to the reader. MIL-D-87269 establishes the IETM database forms, structure, and key controlling mechanisms. MIL-Q-87270 establishes quality standards for IETMs.
• There are five classes of IETMs
• Conclusion: Want a single database containing all information. User interaction is a database request.

• Display
  • Full page viewing
  • Page-turner/Next function
  • Intelligent index for user access to page images
  • Page integrity preserved
• Data Format
  • BitMap (raster)
  • Indexing and header files (Navy Mil 29532)
  • MIL-R-28001 or Postscript pages
  • Generic COTS imaging system formats
• Functionality
  • Access pages by intelligent index/header information
  • View page with pan, zoom, etc., tools
  • Limited use of hot-spots
  • Useful for library or reference use

• Display
  • Primary view is scrolling text window
  • Hot-spot access (hyperlinks) to other text or graphics
  • User selection and navigation aids (key-word search, on-line indices)
  • Minimal text-formatting for display
  • User selectable call to (launch) another process
• Data Format
  • Text - ASCII
  • Graphics - whatever viewer supports - e.g., BMP or CALS
  • Can be SGML tagged - no page breaks (browser)
  • Access/index often COTS dependent with hypertext browser
  • Generic: COTS with hypertext browser
• Functionality
  • Browse through scrolling information
  • User selection of graphics or hot-spot reference to more text
  • Hot-spot and cross-reference usually added after original authoring

• Display
  • View smaller logical block of text -- less use of scrolling
  • Interaction through dialog boxes
  • Text and graphic simultaneously displayed in separate window when keyed together
• Data Format
  • Linear ASCII with SGML tags
  • SGML with content vice format tags
  • Maximum use of MIL-D-87269
  • Generic: SGML tags equivalent to MIL-D-87269
• Functionality
  • Dialog-driven interaction
  • Logical display of data in accordance with content
  • Logical NEXT and BACK functions
  • User-selectable cross-references and indices
  • Content specific help available

• Display
  • View smaller logical block of text -- very limited use of scrolling
  • Interaction through dialog boxes with user prompts
  • Text and graphic simultaneously displayed in separate window when keyed together
• Data Format
  • Fully attributed database elements (MIL-D-87269)
  • Authored directly to database for interactive electronic output
  • Data managed by a DBMS
  • Interactive features "authored in" vice added-on
• Functionality
  • Dialog-driven interaction
  • Logical display of data in accordance with content
  • Logical NEXT and BACK functions
  • Useful as interactive maintenance aid
  • User-selectable cross-references and indices
  • Content specific help available

• Display
  • Same as Class 4 for IETM function
  • Expert system allows same display session and view system to provide simultaneous access to many differing functions (e.g., supply, training, troubleshooting)
• Data Format
  • IETM info integrated at the data level with other application info
  • Does not use separate databases for other application data.
  • Identical to Class 4 standards for IETM applications data
  • Coding for Expert Systems and AI modules when used
• Functionality
  • Single viewing system for simultaneous access to multiple info sources
  • Same as Class 4 for IETM functions
  • Expert system to assist in NEXT functions, based on information gathered in session

• "IETMs allow the user to locate required information faster and more easily than is possible with a paper technical manual. IETMs, when designed to the DoD IETM specifications, are easier to comprehend, more specifically matched to the system configuration under diagnosis, and are available in a form that requires much less physical storage space than paper."
• Nugent et at. 1987 indicated that maintenance technicians using a computer-based electronic document with artificial intelligence assistance on troubleshooting completed tasks in less than half the time it took those with paper manuals. Even novices, using the electronic job aid, could troubleshoot 12% faster than experienced technicians using paper manuals.

• Print publishing
  • Have written two reference books (HODE, HOI)
  • Have edited a reference book (CRC)
• Electronic publishing
  • Have handed my own book off to others (CRC->Maple)
  • Have translated book I have written (HODE)
  • Have translated books written by others (Stroyan, Schechter) (G&R in process)

• Effort required to
  • Understand layout and macros (regularity is key)
  • Re-think logical structure (linear read no longer appropriate)
  • Decide on product granularity
  • Design and construct interface
  • Pre-process data and create static databases
  • Fine tuning & testing
• Add capability not present in print product
  • Indices: Complete indexing of entire work, and specialized ones
  • Searching on functional aspects (HODE: systems of PDEs, G&R: types of integrand)
  • Pop-up figures/references
  • Multi-level granularity for easy information location
  • Electronic interactivity
    • External: Mathematica notebooks, Maple worksheets, VRML
    • Internal: Java programs, applets

• Dave Isaacson (RPI)
  • Definitions / Formulas / Algorithms for computing / Asymptotics / Graphs and Numbers
  • "Right now I probably use Maple more to obtain numbers and graphs from the special functions after I've figured out which ones I need from Abramowitz."
  • "Perhaps an online version of Abramowitz added to Maple would be very helpful?"
• Rob Gross (BC)
  • "I use it for notation and definitions, with the occasional numerical value. These days, though, I don't often run into a numerical value that I can't get out of a computer program."
• Catherine Roberts (Northern Arizona U)
  • "I use the information on special functions the most - Error and Gamma, to be precise. It would be nice to have MORE information about special functions in there - plus on transforms like the Mellin transform. The kind of information that I look up in my Erdeli Higher Transcendental Functions would be helpful."
  • "I also look up information about the integrals w/infinite limits, to seek alternate forms and such."

• Presently contains
  • notation
  • definitions
  • relationships (asymptotics, etc)
  • algorithms for numerical values
  • numerical values
• Possible enhancements
  • additional functions
  • more algorithms
  • actual code
  • more/better graphics (such as 3D)
  • interactive capability

• Tables/algorithms: static and dynamic (local or remote running)
• Graphs of values: 2D and 3D, static and dynamic
• Searching (with wild cards) for: (1) all words in product, (2) human created index
• Write content in a "meta language" translatable to Mathematica, Macsyma, etc. Note sin x cos x.
• Enter integral (differential equation, or recursion relation) and have product determine appropriate functions
• For each function, show relationship to other specified special functions
• Print interaction results with book quality formatting

• Add links to relevant web sites, or include if possible
  • Inverse symbolic calculator http://www.cecm.sfu.ca/projects/ISC/
  • Sloane's handbook of integer sequences http://www.research.att.com/~njas/sequences/
  • Richard Fateman's integration site http://http.cs.berkeley.edu/~fateman/htest.html
  • Wolfram integration site: http://www.integrals.com
• If discrete special functions included add graphical listing capabilities (i.e., necklaces at http://www-ang.kfunigraz.ac.at/~fripert/fga/kerber1.html)
• Other capabilities include:
  • Save searches for re-use
  • Allow notes to be taken and stored
  • Allow regions to be highlighted
  • Integrate with speech readers
  • ...

• Determine content
• Determine allowable queries
• Determine response to queries
• Determine additional electronic functionality
• Define unique representation of all functions for authors. Example: the Clebsch-Gordan coefficients are (j₁j₂m₁m₂| j_1j_2jm), this j₂ is not a Bessel function.
• Determine components and content of sample chapter(s)
• Have graphic artist design the style of the work (both print and electronic versions)
• Design and construct interface
• Design and construct databases
• Design and construct codes to populate databases

• Create style guide for authors Example: cross-platform functionality requires:
  • all lowercase file names
  • no special characters in file names (such as "." or "&")
• Phase in steps slowly
• Do extensive testing

• Phase I: * Make the content of the book electronic. * Index integrals * Use interface similar to http://www.mathtable.com/egr/
• Phase II: * Allow integrals to be entered in Macsyma notation, Mathematica notation, etc * Integrals translated: as input to TeX, input to Maple, etc. * Call to appropriate computational engine * Locate class of integrals corresponding to the input integral.
• Phase III: * Translate integrals to a "processing" language (Macsyma? Lisp?). * Perform simple "verification" of the integrals. * Search engine locates a specific desired integral.
• Phase IV: * Add point-and-click interface for easy integral entry
• Phase V: * Include a computation engine to evaluate integrals not tabulated.
• Phase VI: * Web site for users to contribute new integrals to the "master list".

• Handbook of Mathematical Functions (A&S)
• Standard Mathematical Tables & Formulae (CRC) (editor-in-chief)
• Tables of Integrals, Series, and Products (G&R) (navigator, in process)
• Handbook of Differential Equations (HODE) (author, navigator)