mguyott@samsung.COM (Marc Guyott) (03/15/90)
In article <114808@ti-csl.csc.ti.com>, fritz@m2.csc.ti.com (Fritz Whittington) writes:
% I think that a markup language that conforms to SGML is probably the
% better way to go. The publishing industry is charging in that direction,
% including those publishers that put out CD-ROMS, and we don't need yet
% another way to store text in a database. I have even seen announcements
% for conversion to/from TeX, scribe, nroff/troff, and many others by
% using SGML as the common format.
Can anyone tell me where I can find a description of SGML? Marc
-------------------------------------------------------------------------------
Marc Guyott || Phone: +1 (508) 685-7200 x115
Samsung Software America, Inc. || Fax: +1 (508) 685-4940
1 Corporate Drive || Internet: mguyott@samsung.com
Andover, Mass. 01810-2442 USA || UUCP: {uunet,ulowell}!samsung!mguyott
-------------------------------------------------------------------------------jr@bbn.com (John Robinson) (03/15/90)
In article <114808@ti-csl.csc.ti.com>, fritz@m2 (Fritz Whittington) writes: >In article <3117@bingvaxu.cc.binghamton.edu> cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn) writes: >> It seems quite obvious to me that a >>hybrid TeX/Hypertext markup language would be an ideal first step >>towards the development of a truly flexible, portable environment for >>the collaborative, professional construction of structured documents. >1) I use LaTeX and TeX and like them; there are all sorts of reasons >why... >2) I haven't seen the markup language you refer to... >BUT >I think that a markup language that conforms to SGML is probably the >better way to go. I agree. Another thread that is a little more interactive is built on GNU emacs info/texinfo, where the info side is live, yet you still get the TeX side to spool off to hardcopy (or, eventually, to the rendering program for your WS). -- /jr, nee John Robinson Life did not take over the globe by combat, jr@bbn.com or bbn!jr but by networking -- Lynn Margulis
piet@cs.ruu.nl (Piet van Oostrum) (03/16/90)
In article <13056@samsung.samsung.com>, mguyott@samsung (Marc Guyott) writes:
`
`Can anyone tell me where I can find a description of SGML? Marc
`
TITEL: SGML : an author's guide to the standard generalized markup language
/ [by] Martin Bryan
IMPR.: Wokingham [etc.] : Addison-Wesley, 1988 * XVIII, 364 p. ; 24 cm
ISBN: 0-201-17535-5
--
Piet* van Oostrum, Dept of Computer Science, Utrecht University,
Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands.
Telephone: +31-30-531806 Uucp: uunet!mcsun!ruuinf!piet
Telefax: +31-30-513791 Internet: piet@cs.ruu.nl (*`Pete')lac@ecs.soton.ac.uk (Les Carr) (03/16/90)
In article <3117@bingvaxu.cc.binghamton.edu> cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn) writes: >Recently I've been examining some decent Hypertext authoring >environments. They use ASCII source with a markup language to indicate >pages, frames, links, and threads. It seems quite obvious to me that a >hybrid TeX/Hypertext markup language would be an ideal first step >towards the development of a truly flexible, portable environment for >the collaborative, professional construction of structured documents. In pursuance of a PhD I have written a system called `Lace' which is based around LaTeX. It uses the generic(ish) markup to automatically create links from (eg) a reference to a labelled section or (another eg) an entry in the table of contents to the appropriate section. Each document is stored as an hierarchical structure of nodes according to LaTeX's structuring definitions (chapters/sections/subsection and the like) and can be individually retrieved. The structured markup idea is also used to provide similar facilities for videodisc documents and (another eg) live database access (enough to be able to fashionably label the system as "multimedia"!). The idea is that providing yet another document style for an *unchanged* generic document has turned it from a report/book/article into a hypertext network---well, it works. At the moment it only works on SUNs under NeWS, although it is being ported to X11. There is also *some* support for other markup schemes like troff's man macros, but, I too would like to head off in the SGML direction if only life weren't so short and LaTeX so ubiquitous/well supported. -- L.Carr@ecs.soton.ac.uk Les Carr Tel: +44 703 593649 Dept of Electronics and Computer Science Fax: +44 703 593045 University of Southampton Telex: 47661 SOTONU G Southampton SO9 5NH England
fritz@friday.UUCP (Fritz Whittington) (03/20/90)
In article <13056@samsung.samsung.com> mguyott@samsung.COM (Marc Guyott) writes: >In article <114808@ti-csl.csc.ti.com>, >fritz@m2.csc.ti.com (Fritz Whittington) writes: >% I think that a markup language that conforms to SGML is probably the >% better way to go. >Can anyone tell me where I can find a description of SGML? > Marc (And to also reply en masse to some who asked similar questions by e-mail): SGML stands for Standard Generalized Markup Language. It is defined by ISO 8879. However, it is a standard for definition of markup languages, not itself a mark-up language. One particular markup language has been defined by the American Association of Publishers and the Council on Library Resources, and evolved into an ANSI standard as ANS/NISO Z39.59-1988. This standard (which conforms to ISO 8879) defines structural organizations for ``book'' and ``article'' and ``serial'' documents. Anyone familiar with the LaTeX book and article styles would have little difficulty using the AAP mark-up language on books or articles; the serial structure is something like you find in archives of comp.sources.misc articles. A short sample: <h1>AAP</h1> It's important to remember that these tags are used for identifying the <it> structure </it> of a document, and <b> not </b> the way to typeset the document. \section{LaTeX} It's important to remember that these tags are used for identifying the {\it structure} of a document, and {\bf not} the way to typeset the document. (Note that my example is a little poor: since 2/3 of what is marked is concerned more with typography: italic and bold. The AAP just couldn't get rid of these. But they define <e1> <e2> and <e3> tags for varying types of generic ``emphasis'' somewhat parallel to LaTeX's {\em } command.) Of course, you also need some software to interpret the tags in the light of a particular style sheet and print the document. The Electronic Publishing Special Interest Group offers copies of the ANSI standard and several tutorial and reference manuals on how to use it. Contact EPSIG at 6565 Frantz Road, Dublin OH 43017-0702 (614)764-6000. If you wanted to invent a technique for marking-up hypertext, you might need to look at the ISO 8879 standard. I would think that it would be best to extend the ANSI (AAP) standard, so that you could start with a collection of such documents and add the hypertext tags. ---- Fritz Whittington Texas Instruments, Incorporated I don't even claim these opinions myself! MS 8338 UUCP: attctc!ernest!friday!fritz 8330 LBJ Freeway AT&T: (214)XYlophone7-6307 Dallas, Texas 75265